Difference between revisions of "EGI-InSPIRE:Sa1 2013-03-19"
Jump to navigation
Jump to search
Line 87: | Line 87: | ||
=SA1.8 Availability and core services= | =SA1.8 Availability and core services= | ||
<!--C. Kanellopoulos--> | <!--C. Kanellopoulos--> | ||
business as usual | |||
== Documentation == | == Documentation == | ||
<!-- M. Krakowian --> | <!-- M. Krakowian --> |
Revision as of 20:57, 19 March 2013
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Inspire reports menu: | Home • | SA1 weekly Reports • | SA1 Task QR Reports • | NGI QR Reports • | NGI QR User support Reports |
Progress of SA1 issues
Nothing new to report.
Milestones/Deliverables
D4.8 Annual assessment of the infrastructure: in progress
SA1.1 Activity Management
MEETINGS
- ISGC 2013: preparation of contributions about EGI integration, software platforms and roadmaps
- OSG: contribution to OSG all hands meeting addressing various interoperations topics: GLUE2 support, OIM, collaboration on software verification, SHA-2
- GDB meeting
- GGUS meeting to define evolution of technology helpdesk, new workflows and support models in preparation to the end of EMI and IGE
- GOCDB meeting to assess implications of service renaming and implementation plans
ACTIVITIES
- revision of Asia Pacific MoU
- 1st draft of OSG MoU
- status assessment of ROC Latin America
- agreements on software support extensions (dCache), start of DPM EMI 1 and EMI 2 v < 1.8.6 monitoring campaign
- finalization of plan for enforcement of accounting policy on handling of private data information
- finalization of CF13 operations track agendas
- emergency suspension of users: discussion of procedures, use cases, policies
SA1.2 Security
- Final preparations for and delivery of security training at ISGC 2013. Was successful with 6 teams of 2 or 3 people doing the training (15 in total). There were varied levels of skills but all found the training fun and useful
- Lots of discussion about policy issues and procedures for Security Emergency User Suspension - hopefully now converging
- Related to this, work on draft of the procedure for handling compromised user credentials
- one minor security incident
- A new High-risk Linux kernel vulnerability - EGI CSIRT ADVISORY [EGI-ADV-20130318] published
- more work on draft poster for EGI CF
- talk on EGI CSIRT at ISGC 2013
SA1.3 Staged rollout
- Pursuing the activities for the UMD-2 release
- Ready for production:
- Gram5 and WMS
- Ready for production:
- Preparation of the UMD-3 release with all the EMI-3 products
- Already submitted all SL5/SL6 products to verification [1]
- Some issues found with debian packages affecting:
- L&B, PX, all ARC components, AMGA and gLexec (waiting from EMI-3 developers feedback)
SA1.3 Integration
- QCG: Request for setting QCG tests an operations tests was send to COD team
- QCG: QCG manual tests added to HOWTO 04 Site certification manual tests
- QCG: Procedure 9 Resource Center Registration and Certification changed to take into account QCG requirements
SA1.4 Central tools
SA1.5 Accounting
Repository
- Storage Accounting presentation at GDB
- Work with Federated Cloud Test resource providers to migrate to SSM 2.0 and new cloud accounting record.
- Work on modifying cloud database schema and code to expand FQAN to VO, VOGroup and VORole so that in future, when RPs provide FQAN data we can summarise by VO.
- Work begun to implement Regional APEL Server at Hannover, this will provide a test environment to integrate Application Accounting data
- APEL client upgrade guide in preparation - working with client site on migrating to EMI 3 version of APEL client.
- Test CAR data (using SSM 2.0) received
Portal
- Cloud accounting first implementation
- Cloud accounting second iteration (WIP)
- Schema adaptations for cloud
SA1.6 Helpdesk
- Ticket monitoring
- Weekly phone conference for discussing enhancements on GGUS
- Preparing GGUS March release
SA1.7 Support
no report received
SA1.8 Availability and core services
business as usual
Documentation
nothing to report