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 "EGI-InSPIRE:Amb 2014-01-22"

From EGIWiki
Jump to navigation Jump to search
Line 121: Line 121:


== SA4 ==  
== SA4 ==  
<!-- Michel -->
 
==== Summary ====
 
==== TSA4.1 - Management ====
 
==== TSA4.2 - MOOC ====
- Final assignments are flooding in, up to about 25 now.
- Had some problems with the MOOC platform over the weekend. Has been fixed Monday morning.
- Gathering information for final report.
 
==== TSA4.3 - Liferay ====
bi-weekly reporting
 
====TSA4.4 - OCCI for CMF====
=====rOCCI client =====
* implemented linking and actions
* released a number of beta versions, iterating towards RC1 & stable 4.2
=====rOCCI-server=====
* first beta is available, started local deployment and compat. testing
* started working on installation & configuration docs
=====ToDo for next week=====
* finish basic tests and move on to interoperability testing
* in parallel, continue working on the rOCCI framework
=====Problems=====
None
=====Delays=====
* Still approx. one month (== Florian's contribution), no further delay
 
====TSA4.5 - CDMI in CMF====
bi-weekly reporting
 
====TSA4.6 - OCCI CompClouds====
no report given
 
====TSA4.7 - AppDeployment====
=====Progress:=====
- Testing of contextualization features at FedCloud infrastructure
- Review documentation of contextualization features
- Review mini-project documentation
- Preparation of cloud-init packages
- Started implementation for launching VMs from the frontend
=====Plans for next week:=====
- Continue the front-end implementation
- Testing with local users
 
====TSA4.8 - CloudCapabilities====
=====Progress:=====
* A number of basic OS images are now available including CloudInit. It needs to be verified whether contextualization also works in OpenStack using its metadata service based approach.
* During the FedCloud F2F we had the opportunity to talk to Martin Wynne, who provides the BNCweb use case. We now understand the use case and its goals much better. Specifically, it is now clear which of the components need to be scalable.
 
=====Plans for next week=====
* Check contextualization of basic images
* Document BNCweb use case in light of new information. Propose scalable architecture. The DB as as service that we once started will be part of the solution.
=====Problems we encountered, but can solve in the mini-project:=====
None
=====Problems and issues we need external help with:=====
None
 
====TSA4.9 - VAPOR====
bi-weekly reporting
 
====TSA4.10 - CompReports====
bi-weekly
 
====TSA4.12 - AllocateFedRes====
no report given


== JRA1 ==  
== JRA1 ==  

Revision as of 14:39, 22 January 2014


Back to the AMB wiki home page

Activity Reports

NA1

NA2

NA2.2

  1. News Items/Articles
  2. Events
    • Sorting submitted sessions, workshops, training sessions and tutorials into CF timetable
  3. Publications
    • Working on design for CF Book of Abstracts
    • Working on changes to the "Why EGI?" document
    • Initial design ideas for the EGI Solutions materials portfolio
  4. Webinars
    • ENVRI webinar on Federated Cloud rescheduled
  5. Deliverables/Milestones
    • MS248 assigned a reviewer, waiting in moderator
  6. Website
  7. Other

NA2.3 Events

NA2.5 Technical outreach

EGI-InSPIRE

  • Finalise and publish Engagement Strategy: https://documents.egi.eu/document/2079
  • EGI Engagement Strategy scoping phase:
    • Support for DIRAC service at EGI (Ricardo Graciani)
    • Support for Life Sciences topic: NGS/Protein Folding (Afonso Duarte)
  • Review EGI Engagement Strategy document
  • Preparation of CF workshops
    • Environmental science on grids and clouds (submitted)
    • Astro science on grids and clouds (waiting for input from astro partners)


ER-flow

  • EGU abstract
  • Preparation for project meeting (April 8-10, Trieste)
  • Review of potential events to reach new communities
  • Workflow bundle meeting with Taverna
  • Refactoring tutorials section for ER-flow website
  • WP5 monthly skype teleconference
  • Nagios and VAPOR monitoring for shiwa-workflow.eu VO
  • EGI CVMSF current status and possible use by ER-flow

BioVeL

  • Service portfolio (ongoing)
  • Services monitoring EGI internal 2nd meeting (Malgorzata)
  • ST-weekly meeting

Major Events Planned

  • (Nuno) 2nd LifeWatch Operational/Working Meeting, 3-4.02.2014, Granada
  • (Gergely) BioVeL Strategy Workshop, 12-14.02.2014, Finland
  • (Gergely) ER-flow project meeting, 8-10.04.2014, Trieste


AppDB 

  • New AuthN mechanism, based on [1]. AppDB now supports both EGI SSO and x509 certificates.
  • Modification to the vmcaster dashboard portal [2] in order to support x509 certificates as well.
  • A patch for the vmcaster [3] command line tool so that the user to be able to use his x509 certificate for submitting image list to AppDB (EGI SSO has been kept as an alternative).
  • Integration with the operations portal for getting the VO related information (membership + roles(s) within a VO) for the AppDB users.
  • Integration with the gocdb in order to get the Resource Providers related information.
  • Changes on the people profiles for presenting person's VO related information (membership and roles with the VO(s)). For example, see [4].
  • Changes to the VO details dialog for the same purpose as above. Example: [4].
  • Finalize the Scientific Discipline API based on the specs defined at [4]. See ticket [5].
  • In cooperation with Owen Synge we have submit an abstract for the Community Forum 2014.

    Title: Federated Cloud image lifecycle management

    Category: Training session

    URL: [6]

Next steps:

  • Start AuthZ related developments. Mainly needed for implementing privacy/security for the Virtual Appliance Marketplace extension.
  • Performance improvements



CRM  

  • Discussion with the champion team managers regarding the possibility to use CRM to track champions activity
  • Champions team managers are expected to send a requirement document so that we can actually check what is feasible within the effort and project timeframe.



SA1

https://wiki.egi.eu/wiki/Inspire_sa1_2014-01-21

SA2

SA4

Summary

TSA4.1 - Management

TSA4.2 - MOOC

- Final assignments are flooding in, up to about 25 now. - Had some problems with the MOOC platform over the weekend. Has been fixed Monday morning. - Gathering information for final report.

TSA4.3 - Liferay

bi-weekly reporting

TSA4.4 - OCCI for CMF

rOCCI client
  • implemented linking and actions
  • released a number of beta versions, iterating towards RC1 & stable 4.2
rOCCI-server
  • first beta is available, started local deployment and compat. testing
  • started working on installation & configuration docs
ToDo for next week
  • finish basic tests and move on to interoperability testing
  • in parallel, continue working on the rOCCI framework
Problems

None

Delays
  • Still approx. one month (== Florian's contribution), no further delay

TSA4.5 - CDMI in CMF

bi-weekly reporting

TSA4.6 - OCCI CompClouds

no report given

TSA4.7 - AppDeployment

Progress:

- Testing of contextualization features at FedCloud infrastructure - Review documentation of contextualization features - Review mini-project documentation - Preparation of cloud-init packages - Started implementation for launching VMs from the frontend

Plans for next week:

- Continue the front-end implementation - Testing with local users

TSA4.8 - CloudCapabilities

Progress:
  • A number of basic OS images are now available including CloudInit. It needs to be verified whether contextualization also works in OpenStack using its metadata service based approach.
  • During the FedCloud F2F we had the opportunity to talk to Martin Wynne, who provides the BNCweb use case. We now understand the use case and its goals much better. Specifically, it is now clear which of the components need to be scalable.
Plans for next week
  • Check contextualization of basic images
  • Document BNCweb use case in light of new information. Propose scalable architecture. The DB as as service that we once started will be part of the solution.
Problems we encountered, but can solve in the mini-project:

None

Problems and issues we need external help with:

None

TSA4.9 - VAPOR

bi-weekly reporting

TSA4.10 - CompReports

bi-weekly

TSA4.12 - AllocateFedRes

no report given

JRA1

Report: Inspire jra1 2014-01-21

Participants

Discussion