EGI-InSPIRE:Amb 2013-12-10

From EGIWiki
Jump to: navigation, search
EGI Inspire Main page


Contents


Back to the AMB wiki home page

Activity Reports

NA1

Preparations for the QR14 - NA1 contributions being added

TNA1.1 Activity management

TNA1.2 Project and consortium management

TNA1.4 Quality assurance

By RMcL

NA2

NA2.2

  1. News Items/Articles
  2. Events
    • Drafted document on events, collecting contacts and evaluating said
  3. Human Networks
    • Met with CRM team about future use of CRM with Research Champions
    • Had meeting with Research Champions to discuss plans for 2014
  4. Publications
    • New design for business cards
    • Designed Xmas 2014 card
  5. Webinars
    • Putting together 2014 programme, including the Solutions, AppDB, GLOBUS, ER-Flow & EUDAT
  6. Other Projects
    • Reviewed internal CloudWATCH deliverable
    • Meeting with ENVRI about future work and involvement
  7. Deliverables/Milestones
    • Wrote draft for Community networks and support white paper
    • Wrote draft for Community-driven innovation white paper
  8. Other
    • Had meeting with Rober Lovas and Ad Emmen about future of EDGeS@home

NA2.3

Major work done during the past week by task

Major Events Attended

Major Events Planned

NA2.5

AppDB (10/12/2013)

  1. We are continuing the work towards the restructuring of the authentication mechanism of the AppDB service, in order to support multiple ways (egisso, x509 - for start) of login and be recognized as the same person (with the same privileges no matter the AuthN mechanism he/she used for login).
under this scope the user will be able to:
  • login using both his egisso (if any) and/or personal x509 certificate.
  • the above statement implies that multiple account types could be associated with a single AppDB person profile. That said, explicit functionality will be availabe for 'connetcting' his profile with more that one of the supported AuthZ methods. For example, one could login with an egisso, go to his personal preferences dialog and connect his x509 as an alternative way of login. This is true also on the oposite direction, login with x509 and connect your egisso.
  • for start, only egisso and x509 will be supported. But the implementation we are following will allow us to add more in the future (i.e. edugain, social, fb, linkedin, g+, etc).

     2. Integration with the operations portal regarding the VO roles (VO manager, VO software admin, etc) is in place. In this way we could extract the info on who has permissions to compile/edit VO-wide image list.

     3. Integration with the operations portal regarding the VO membership is on going (waiting feedback from ops portal people). In this way we could implement image/imagelist privacy between VO members.

     4. Integration with the GOCDB is ongoing. Having that, the user will be able to restrict access/subscription to an image list only by specific Resource Provider(s)

Question:

Fetching the data from the GOCDB we realized that although some of the eu.egi.cloud.vm-management.occi sites are in production they have not fill their DN yet. Is this correct?
     (we need this info for fully satisfy the 4th item above)


ER-flow

BioVeL

SA1

report

SA2

SA2.2

SA2.3

SA2.4

SA4

Summary

The MOOC is live, and some 200 students have subscribed. Content for upcoming lectures is prepared. The rOCCI development is progressing well with the refactoring of the framework and adapting the various realisations (CLI, Server, OpenNebula plugin) AppDeployment/Contextualisation continues well; SA2 verification now uses this component, too. VAPOR is now preparing for a full production environment (mostly consisting of fine-tuning of existing features)

TSA4.1 - Management

TSA4.2 - MOOC

- Created walkthrough guide for the first three weeks: this should get new participants up and running with the VM and grid certificates. - Created recordings & quiz for week 4, this week includes the Hadoop lecture - Polishing lectures of week 5

TSA4.3 - Liferay

bi-weekly reporting

TSA4.4 - OCCI for CMF

rOCCI framework
rOCCI-server
ToDo for next week
Problems
Delays

TSA4.5 - CDMI in CMF

bi-weekly reporting

TSA4.6 - OCCI CompClouds

no report

TSA4.7 - AppDeployment

Progress:

- frontend development and testing it with local phenomenology users - continue testing contextualization for verification

Plans for next week:

- development of fronted - continue testing with local users

TSA4.8 - CloudCapabilities

bi-weekly reporting

TSA4.9 - VAPOR

Progress
Plans for next period

Very few should now happen until the end of the month as the main developer will be on leave from Dec. 9th to 31st.

Problems we encounter, but can solve

None.

Problems and issues we need external help with

None.

TSA4.10 - CompReports

bi-weekly reporting

TSA4.12 - AllocateFedRes

no report given

JRA1

Report: Inspire jra1 2013-12-10

Participants

Discussion

ACTIONS

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export