StratusLab Sprint 20 Demo

lundi 19 déc. 2011, 14:00 → 23:55 Europe/Paris

The audio will be provided using the standard daily stand-up meeting number (+33 1 56 78 86 88).

The EVO meeting is here. You can join the conference via this or by searching for a meeting (in all communities) called "StratusLab Sprint 20 Demo". (More info and phone bridge numbers in attached document.) The EVO reservation starts at 13:30, so the connections can be tried out in advance.

For those who will be sharing their screen during the demo, please be sure that you have a wired, high-bandwidth connection. EVO does very poorly over a wireless connection.

We will start promptly at 14:00 (Paris). Please be on time for the meeting!

14:00 → 14:35 Unimplemented Tasks

14:00 LAL

• STRATUSLAB-927: special characters in pdisk tags cause CLI to fail (CL)
• STRATUSLAB-1004: Release 1.2 (CL, GP); packages exist but decision needs to be taken at this meeting if they should be released at v1.2
• STRATUSLAB-965: registration service doesn't create correct entries for certificate authentication (CL); no time to investigate
• STRATUSLAB-943: Cannot use certificate to authenticate on pdisk service (CL); no time to investigate
• STRATUSLAB-928: current version of pdisk service allows other users to view the disks of others (CL); no time to investigate
• STRATUSLAB-911: As a StratusLab developer, I can see the results of a Claudia user test in Hudson (CL); no time to implement
• STRATUSLAB-888: when deletion of a disk via web UI fails sysadmin is not notified (CL); no time to implement
• STRATUSLAB-883: attach-volume doesn't work with CentOS 5.5 VM (CL); no time to investigate
• STRATUSLAB-513: As a StratusLab developer, I am sure that the claudia authn proxy works with a simple "helloworld" test (CL); no time to implement
• STRATUSLAB-992: As a StratusLab developer, I can have access to machines running (and accessible via) IPv6 (GP)
• STRATUSLAB-990: As a DIRAC developer, I can have support for demonstrating LHCb jobs using StratusLab resources (MA); relies on the CernVM task below
• STRATUSLAB-987: As a StratusLab developer, I can see a deployment of a StratusLab cloud in the Grid'5000 infrastructure (MA); initial work has started, but has turned out to be more complicated than expected; no deployment of StratusLab services in Grid'5000 to show yet
• STRATUSLAB-871: As a StratusLab user, I can understand how to run a CernVM image on StratusLab (MA); changes have been made to the contextualization to allow this; because of lack of time, there is no test in the use cases to confirm this; to be carried over to next sprint

14:05 GRNET

• STRATUSLAB-1005: StratusLab 1.2 available from reference infrastructure
• STRATUSLAB-1002: Certify pre-release version of 1.2
• STRATUSLAB-1000: Certify and Deploy StratusLab 1.2
• STRATUSLAB-782: As a StratusLab administrator I can install a cloud site which uses image caching

14:10 SixSq

• STRATUSLAB-978: Create smoke test to verify quarantine cleanup
• STRATUSLAB-982: Refactor tm_clone_cache.sh
• STRATUSLAB-983: Refactor tm_save_cache.sh

14:15 UCM

• STRATUSLAB-873: Identify the components that will require integration changes with ONE 3.0
• STRATUSLAB-872: Define a way to work in parallel towards 2.0
• STRATUSLAB-714: Support for VLAN 802.1Q in OpenNebula

14:20 TID

• STRATUSLAB-971: Video about grid site deployment and scalability
• STRATUSLAB-1011: Remove test-case dependencies from stratus-ovf

14:25 TCD

• STRATUSLAB-899 Email verification should be turned on in the Marketplace
• STRATUSLAB-853: Preparation of user-focused demo

14:30 IBCP

• STRATUSLAB-749: Improve integration of PAT in StratusLab distribution
  • STRATUSLAB-988: Manage PAT through a web interface on the front-end
  • STRATUSLAB-994: Display PAT information in StratusLab commands
  • STRATUSLAB-997: Display PAT information in StratusLab webmonitor
• STRATUSLAB-906: Create a first appliance of tool ARIA
• STRATUSLAB-986: New release of the "biodata" appliance, including biomaj 1.2

14:45 → 15:35 Implemented Tasks

14:45 GRNET Tasks

• STRATUSLAB-865: Re-organize pre-production services
• STRATUSLAB-868: Automated certification deployment on pre-production service
• STRATUSLAB-893: Deploy pre-production elastic grid site
• STRATUSLAB-894: As a StratusLab user I can use Claudia on the reference cloud service
• STRATUSLAB-896: Deploy elastic grid site on the reference service using Claudia

Orateur: Evangelos Angelou (GRNET)

14:50 IBCP

• STRATUSLAB-779: Test slipstream interface for appliances management
• STRATUSLAB-919: Integrate a new host (DELL R815) in IBCP cloud
• STRATUSLAB-984: Automatically mount a persistent disk attached to an instance at launch time
• STRATUSLAB-985: As an user I want to have access to a service that format my newly-created persistent disk
• STRATUSLAB-993: Prepare the slides "What benefits of cloud for Bioinformatics: an user perspective" for the eScience conference

Orateur: M. Clément Gauthey (IDB-IBCP CNRS FR3302)

14:55 LAL

• Verified via tests in the stratus-use-cases.git repository and run in cloud_Test_use_cases_Fedora14 job:
  • STRATUSLAB-972: signing metadata entry which is already signed should replace signature and endorsement (CL)
  • STRATUSLAB-969: stratus-ovf command should not be included in client distribution (CL)
  • STRATUSLAB-960: client commands should all provide --version option (CL)
  • STRATUSLAB-915: As a StratusLab participant, I can see the list of client use cases covered by the distribution (CL)
  • STRATUSLAB-797: As a StratusLab user, I can run an instance directly from a persistent disk image. (CL)
  • STRATUSLAB-795: As a StratusLab admin, I can have a cloud installation that supports machine state notifications (CL)
• STRATUSLAB-963: unclear error message when disk is already attached to another VM (CL)
• STRATUSLAB-995: All of the standard StratusLab services should be secured via terena certificate (GT)
• STRATUSLAB-913: As a StratusLab admin at LAL, I can use IPMI to manage the cloud machines at LAL (GT)
• STRATUSLAB-1006: Fix DHCP configuration at LAL for local IP addresses (GP)
• STRATUSLAB-912: As a StratusLab developer, I can use a SuSE machine installed via quattor for tests. (GP); see the LAL-OpenSuSE-1 node
• STRATUSLAB-1032: Define a job in hudson to test builds on multiple architectures (Fedora14 and OpenSuSE) (CL); see the build_authn job
• STRATUSLAB-1001: Pre-release 1.2 (CL); packages exist in certification repository, but downstream installation jobs fail; decision needs to be taken if a public release is made

Orateurs: Dr Charles Loomis (LAL-Orsay), M. Guillaume PHILIPPON (LAL - CNRS)

15:00 SixSq

• STRATUSLAB-819: As a User I can take advantage of a caching feature on the cloud side, such that my VM startup time is significantly improved strategy
  • STRATUSLAB-859
  • STRATUSLAB-953
  • STRATUSLAB-954
  • STRATUSLAB-955
  • STRATUSLAB-956
• STRATUSLAB-860: Improve create-image via utilizing ONE hooks (like DONE, MV, DELETE) and Persistent Storage service
  • STRATUSLAB-610
  • STRATUSLAB-816
  • STRATUSLAB-861
• STRATUSLAB-891: Update quarantine logic following EBS backed disk feature
• STRATUSLAB-979: Complete/fix quarantine logic
• STRATUSLAB-980: Upgrade/create cron job to cleanup PDISK quarantine
• STRATUSLAB-981: Add direct PDISK submission in tm_clone_cache.sh
• STRATUSLAB-1003: Support 1.2 certification process

Orateur: Meb

15:05 TCD

• STRATUSLAB-1007 As a Marketplace user I can access the service over HTTPS
• STRATUSLAB-901 As a Marketplace endorser I receive a reminder of my current metadata list
• STRATUSLAB-854: Preparations for StratusLab face to face meeting

15:10 TID

• STRATUSLAB-966 Introduce API for monitoring systems
• STRATUSLAB-970 Generate KVM images for commertial use case
• STRATUSLAB-967 Introduce monitoring software in continous integration
• STRATUSLAB-968 Generation of monitoring stratuslab tools

15:15 UCM

• STRATUSLAB-999 Support specifying networks and images by its name