StratusLab Sprint 19 Demo

mercredi 16 nov. 2011, 10:45 → 17:30 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 19 Demo". (More info and phone bridge numbers in attached document.) The EVO reservation starts at 14: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 10:45 (Paris) just after the standup. Please be on time for the meeting!

1 Unimplemented Tasks

LAL:

• STRATUSLAB-798: As a StratusLab user, I can access new storage resources on LAL cloud (GT)
• STRATUSLAB-849: As a StratusLab admin, I can install an alternate scheduler for OpenNebula for controlling deployments in the cloud (MA)
• STRATUSLAB-871: As a StratusLab user, I can understand how to run a CernVM image on StratusLab (MA)
• STRATUSLAB-911: As a StratusLab developer, I can see the results of a Claudia user test in Hudson (CL)
• STRATUSLAB-912: As a StratusLab developer, I can use a SuSE machine installed via quattor for tests. (GP)
• STRATUSLAB-913: As a StratusLab admin at LAL, I can use IPMI to manage the cloud machines at LAL (GT)
• STRATUSLAB-915: As a StratusLab participant, I can see the list of client use cases covered by the distribution (CL)
• STRATUSLAB-917: As a StratusLab developer, I can trigger an automated installation of StratusLab via quattor (GP)

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-864: Support development of Torque cluster deployment modules
• STRATUSLAB-816: to support "saveas" feature of ONE qemu.conf should be modified so that libvirt doesn't alter ownership of disk images
• STRATUSLAB-610: As a StratusLab user, I can trigger a VM build via stratus-create-image and get asynchronous notification/metadata information later
• STRATUSLAB-657: As StratusLab user, I can use qcow images with stratus-create-image
• STRATUSLAB-861: When creating a new image via ONE+PersistentStore sign image Manifest with self-signed certificate and upload it to Markteplace
• STRATUSLAB-891: Update quarantine logic following EBS backed disk feature
• STRATUSLAB-830: add "~" expansion to CLI utils

GRNET:

• STRATUSLAB-781: As a StratusLab administrator I can install a cloud site which provides NFS-based volume management to VMs
• STRATUSLAB-782: As a StratusLab administrator I can install a cloud site which uses image caching
• 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

IBCP:

• STRATUSLAB-778: As an user I can create Bioinformatics Web Services as described in Deliverable 2.3
• STRATUSLAB-779: test slipstream interface for appliances management
• STRATUSLAB-833: Bioinformatics Web Services usecase
• STRATUSLAB-904: As a cloud infrastructure admin, I can include cloud nodes based on VMware ESXi
• STRATUSLAB-906: Create a first appliance of tool ARIA
• STRATUSLAB-919: Integrate a new host (DELL R815) in IBCP cloud

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

TID:

• STRATUSLAB-521: As Claudia user, I want that user interaction with Claudia are done by the StratusLab authentication proxy
• STRATUSLAB-876 : Introduce monitoring components in StratusLab insfrastructure

TCD:

• STRATUSLAB-899 Email verification should be turned on in the Marketplace
• STRATUSLAB-901 As a Marketplace endorser I receive a reminder of my current metadata list
• STRATUSLAB-853: Preparation of user-focused demo
• STRATUSLAB-854: Preparation of user-focused demo

2 GRNET Tasks

• STRATUSLAB-718: Images uploaded to the marketplace should be either gzip or qcow compressed
• STRATUSLAB-863: Torque cluster can be instantiated from SlipStream
• STRATUSLAB-893: Deploy pre-production elastic grid site
• STRATUSLAB-894: As a StratusLab user I can use Claudia on the reference cloud service

Orateurs: Christina Boumpouka (GRNET), Evangelos Angelou (GRNET), M. Evangelos Floros (GRNET)

3 SixSq

• STRATUSLAB-859: Cleanup tm_clone_{caching+persistence/policy}.sh scripts used in CLONE OpenNebula hook
• STRATUSLAB-953: Upgrade PersistentDisk Python class to operate ad disk user on behalf of the user
• STRATUSLAB-954: Create new sysadmin commands to handle storage handling in ONE scripts
• STRATUSLAB-824: Update the Hudson job to remove the manual update of the ONE driver config file replacing tm_clone.sh with tm_clone_policy.sh. This should be done during installation of StratusLab.

Orateurs: Konstantin, Meb

4 TID

• STRATUSLAB-719 Updating Claudia RPMs restores default configuration files without backup
• STRATUSLAB-942 Generate a new package in Claudia with Claudia common libraries to avoid conflicts in installing
• STRATUSLAB-908 Generation of the rpm collectd package
• STRATUSLAB-909 Generation of the monitoring aggregator package
• STRATUSLAB-910 Generation of the probes extension package
• STRATUSLAB-898 Integrate Claudia with OpenNebula 3.0

5 LAL