Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Agenda-20-06-2011"

From EGIWiki
Jump to navigation Jump to search
Line 1: Line 1:
{{Template:Op menubar}}  
{{Template:Op menubar}}  


''' WARNING: The meeting is being moved from 20th of June to 20th of June, because 13th of June is holiday in Netherlands and other countries. Sorry for the inconvenience.'''
'''WARNING: The meeting is being moved from 20th of June to 20th of June, because 13th of June is holiday in Netherlands and other countries. Sorry for the inconvenience.'''  


= Detailed agenda: Grid Operations Meeting 13 June 2011 14h00 Amsterdam time  =
= Detailed agenda: Grid Operations Meeting 13 June 2011 14h00 Amsterdam time  =


[http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MeMMMu222BDiD89v9sDv9e EVO direct link] pwd:gridops || [https://www.egi.eu/indico/materialDisplay.py?materialId=2&confId=495 EVO details] || [https://www.egi.eu/indico/conferenceDisplay.py?confId=49 Indico page]
[http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MeMMMu222BDiD89v9sDv9e EVO direct link] pwd:gridops || [https://www.egi.eu/indico/materialDisplay.py?materialId=2&confId=495 EVO details] || [https://www.egi.eu/indico/conferenceDisplay.py?confId=49 Indico page]  


== 1. Middleware releases and staged rollout  ==
== 1. Middleware releases and staged rollout  ==
=== 1.1 EMI-1 release status (Cristina)===
 
=== 1.1 EMI-1 release status (Cristina) ===


=== 1.2. EMI/UMD current status  ===
=== 1.2. EMI/UMD current status  ===


==== 1.3. Staged Rollout (Mario)  ====
==== 1.3. Staged Rollout (Mario)  ====
===== 1.3.1 gLite 3.1 series<br> =====
*LFC 1.8.0-1, patches in staged rollout state with no EA - Decision was to close those patches since there was no interest shown from production sites, and the support calendar has ended.<br>
===== 1.3.2 gLite 3.2 series =====
*CREAM&nbsp;1.6.6 and glite-SGE_utils are under staged rollout - fix a bug seen in the previous staged rollout<br>
*L&amp;B 2.1.21:&nbsp;staged rollout done, report produced - possibly will be released together with cream and sge.
===== 1.3.3 EMI1 - UMD1 =====


==== 1.4 Interoperability (Michaela)  ====
==== 1.4 Interoperability (Michaela)  ====


=== 2. Operational Issues  ===
==== 2.1 Requirement #[https://rt.egi.eu/rt/Ticket/Display.html?id=1388 1388]  ====
NGI_IT requested documentation about guidelines on how to migrate a service preserving its state (e.g. an SE), on how to set up hot-failover for stateful services.


=== 2. Operational Issues  ===
*Instruction on what is needed to be copied and preserved.  
==== 2.1 Requirement #[https://rt.egi.eu/rt/Ticket/Display.html?id=1388 1388] ====
NGI_IT requested documentation about guidelines on how to migrate a service preserving its state (e.g. an SE), on how to set up hot-failover for stateful services.
*Instruction on what is needed to be copied and preserved.
*Instruction on how to set up failover or redundant instances of the same service.
*Instruction on how to set up failover or redundant instances of the same service.


NGI_IT provided parsed EMI-1 products documentation and highlighted the components that are missing documentation on this issues.
NGI_IT provided parsed EMI-1 products documentation and highlighted the components that are missing documentation on this issues.  


===== 2.1.1 Services that do not need documentation =====
===== 2.1.1 Services that do not need documentation =====
The following services already report in their documentation the procedures to migrate the service maintaining the state, and a description of an high availability configuration.
* AMGA
* APEL publisher (''HA'' not docuemented but not critical)
* dCache
* VOMS
** VOMS-Oracle replica not documented
* WMS
** Stateless service, documentation about critical log files to save/maintain
** Failover and load balancing available for both server/client side
* LB
** HA not documented, but WMS can be configured to point to multiple LB


===== 2.1.2 Services that miss documentation =====
The following services already report in their documentation the procedures to migrate the service maintaining the state, and a description of an high availability configuration.  


{| border="1"  
*AMGA
|+ align="bottom" style="caption-side: bottom" | '''V''': documentation ok. '''?''': documentation existing but not complete. '''X''': missing documentation
*APEL publisher (''HA'' not docuemented but not critical)
*dCache
*VOMS
**VOMS-Oracle replica not documented
*WMS
**Stateless service, documentation about critical log files to save/maintain
**Failover and load balancing available for both server/client side
*LB
**HA not documented, but WMS can be configured to point to multiple LB
 
===== 2.1.2 Services that miss documentation  =====
 
{| border="1"
|+ '''V''': documentation ok. '''?''': documentation existing but not complete. '''X''': missing documentation  
|-
|-
!Service  
! Service  
!How to migrate the service
! How to migrate the service  
!How to set up failover load balancing
! How to set up failover load balancing  
!Comments
! Comments
|-
|-
|LFC
| LFC  
|'''?'''
| '''?'''  
|'''?'''
| '''?'''  
| Documentation available for both HA and migration. But the docs may be not up-to-date. The load balancing tecnique based on DNS round robin is missing.
| Documentation available for both HA and migration. But the docs may be not up-to-date. The load balancing tecnique based on DNS round robin is missing.
|-
|-
|BDII
| BDII  
|'''V''' (not applicable)
| '''V''' (not applicable)  
|'''X'''
| '''X'''  
|Service stateless, no documentation available about HA and load balancing
| Service stateless, no documentation available about HA and load balancing
|-
|-
|DPM
| DPM  
|'''V'''
| '''V'''  
|'''?'''
| '''?'''  
|The DPM architecture is modular, but deployment scenarios are not well covered in the documentation
| The DPM architecture is modular, but deployment scenarios are not well covered in the documentation
|-
|-
|CREAM
| CREAM  
|'''?'''  
| '''?'''  
|'''X'''
| '''X'''  
|Cream is a stateless service, but for accounting and security purpose, some logs must be preserved to be compliant to EGI recommendation. It is not clear which files are important and which are not.
| Cream is a stateless service, but for accounting and security purpose, some logs must be preserved to be compliant to EGI recommendation. It is not clear which files are important and which are not.
|-
|-
|ARGUS
| ARGUS  
|'''X'''
| '''X'''  
|'''X'''
| '''X'''  
|  
| <br>
|}
|}


Line 81: Line 97:
=== 3. AOB  ===
=== 3. AOB  ===


==== 3.1 ====
==== 3.1 ====
Next Meeting:
 
Next Meeting:  


[[Category:GridOpsMeeting]]
[[Category:GridOpsMeeting]]
<br>

Revision as of 11:42, 20 June 2011

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



WARNING: The meeting is being moved from 20th of June to 20th of June, because 13th of June is holiday in Netherlands and other countries. Sorry for the inconvenience.

Detailed agenda: Grid Operations Meeting 13 June 2011 14h00 Amsterdam time

EVO direct link pwd:gridops || EVO details || Indico page

1. Middleware releases and staged rollout

1.1 EMI-1 release status (Cristina)

1.2. EMI/UMD current status

1.3. Staged Rollout (Mario)

1.3.1 gLite 3.1 series
  • LFC 1.8.0-1, patches in staged rollout state with no EA - Decision was to close those patches since there was no interest shown from production sites, and the support calendar has ended.
1.3.2 gLite 3.2 series
  • CREAM 1.6.6 and glite-SGE_utils are under staged rollout - fix a bug seen in the previous staged rollout
  • L&B 2.1.21: staged rollout done, report produced - possibly will be released together with cream and sge.
1.3.3 EMI1 - UMD1

1.4 Interoperability (Michaela)

2. Operational Issues

2.1 Requirement #1388

NGI_IT requested documentation about guidelines on how to migrate a service preserving its state (e.g. an SE), on how to set up hot-failover for stateful services.

  • Instruction on what is needed to be copied and preserved.
  • Instruction on how to set up failover or redundant instances of the same service.

NGI_IT provided parsed EMI-1 products documentation and highlighted the components that are missing documentation on this issues.

2.1.1 Services that do not need documentation

The following services already report in their documentation the procedures to migrate the service maintaining the state, and a description of an high availability configuration.

  • AMGA
  • APEL publisher (HA not docuemented but not critical)
  • dCache
  • VOMS
    • VOMS-Oracle replica not documented
  • WMS
    • Stateless service, documentation about critical log files to save/maintain
    • Failover and load balancing available for both server/client side
  • LB
    • HA not documented, but WMS can be configured to point to multiple LB
2.1.2 Services that miss documentation
V: documentation ok. ?: documentation existing but not complete. X: missing documentation
Service How to migrate the service How to set up failover load balancing Comments
LFC ? ? Documentation available for both HA and migration. But the docs may be not up-to-date. The load balancing tecnique based on DNS round robin is missing.
BDII V (not applicable) X Service stateless, no documentation available about HA and load balancing
DPM V ? The DPM architecture is modular, but deployment scenarios are not well covered in the documentation
CREAM ? X Cream is a stateless service, but for accounting and security purpose, some logs must be preserved to be compliant to EGI recommendation. It is not clear which files are important and which are not.
ARGUS X X
2.1.3 Other middleware stacks?

NGI_IT gathered information only about gLite components, where they have more experience. All the EMI services will be deployed from scratch.
Are the same informations needed also for ARC components? The interested NGIs could parse the available documentation and report the component that miss information.
UNICORE?

3. AOB

3.1

Next Meeting:


Retrieved from "https://wiki.egi.eu/w/index.php?title=Agenda-20-06-2011&oldid=20218"