StratusLab Sprint 10 Demo

jeudi 3 mars 2011, 15:00 → 17:30 Europe/Paris

We will try to handle the audio with the EVO bridge. If it doesn't work, the standard daily stand-up meeting number (+33 1 56 78 86 88) has been reserved as a fall back.

The EVO meeting is here. You can join the conference via this or by searching for a meeting (in all communities) called "StratusLab Sprint 10 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 15:00 (Paris). Please be on time for the meeting!

15:00 → 15:10 Unimplemented Tasks

LAL:

• none

SixSq:

• STRATUSLAB-387 : Investigate: extra disk is not provided to Ubuntu instance.
• STRATUSLAB-295 : As a StratusLab User CLI user, i want to use my own init.sh script.
• STRATUSLAB-304 : Fix tarball installation of user cli
• STRATUSLAB-301 : Wrong number of cores reported for VMs (is this still an issue?)
• STRATUSLAB-390 : Add test to Tester (MarketPlace download)

GRNET:

• STRATUSLAB-337 : Rehearse reference service upgrade to StratusLab 0.3

IBCP:

• STRATUSLAB-313 : As a bioinformatics user, I can deploy a bioinformatics appliance with pre-defined bioinformatics applications.
• STRATUSLAB-314 : As a bioinformatics user , I have access to a persistent biological databases repository
• STRATUSLAB-336 : As a bioinformatics VO admin, I can deploy a bioinformatics appliance to set up a central biological databases repository for my VO

TCD:

• STRATUSLAB-397 : As a Marketplace user, I can visualize the information in the server via an html representation

15:10 → 15:30 Marketplace

Orateur: Stuart Kenny (TCD)

15:30 → 15:50 LAL Tasks

Quattor Configuration:

• STRATUSLAB-373: As a StratusLab system administrator, I can use a Quattor configuration module to configure the authentication proxy. (see package in yum repository)
• STRATUSLAB-322: As a Quattor/StratusLab developer, I can evaluate changes to the Quattor configuration via automated installs.
• STRATUSLAB-395: As a StratusLab tester, I can have the LAL test machine reinstalled regularly via a cron.

Hudson:

• STRATUSLAB-375: As a StratusLab member, I can trigger automated generation of release packages. (release view)
• STRATUSLAB-396: As a StratusLab developer, I can see the status of all software builds via appropriate jobs within hudson (all jobs view, "site" information also generated)

Documentation:

• STRATUSLAB-342: Clean up the wiki and documentation in preparation for release 0.3 (download)
• STRATUSLAB-374: Add documentation on the wiki for the configuration of the authentication proxy. (authentication page)
• STRATUSLAB-365: Provide updated forensics document (on the wiki) explaining where analysis information can be found. (log information page)
• STRATUSLAB-369: As a StratusLab user or administrator, I can understand metadata handling through an expanded Marketplace technical note (document)

Authentication Proxy:

• STRATUSLAB-402: Authentication server will not start if /etc/grid-security/certificates does not exist. (confirmed fixed by Meb in smoke tests)
• STRATUSLAB-367: As a StratusLab administrator, I can use hashed or obfuscated passwords in login-pswd.properties file (authentication page)
• STRATUSLAB-398: URL encode the usernames passed through the authentication proxy
• STRATUSLAB-403: Treat oneadmin user specially in the authentication proxy and pass the actual hashed password to OpenNebula (confirmed by Meb in installation tests)

Misc:

• STRATUSLAB-371: Verify checksums based on binary value rather than hex representation (test added to metadata code)
• STRATUSLAB-364: Quarantine scripts should be split from the OpenNebula package to allow installation on SSH controlled hosts (see quarantine cleanup rpm in yum repository)
• STRATUSLAB-401: Testpolicy.py should be written as unit test

Orateurs: Dr Charles Loomis (LAL-Orsay), Gabriel Tezier (CNRS/LAL), M. Guillaume PHILIPPON (LAL - CNRS), Dr Mohammed Airaj (CNRS/LAL)

15:50 → 16:00 Install Claudia packages

1.- From the yum repository (STRATUSLAB-381)
2.- From stratus-install (STRATUSLAB-277)

16:00 → 16:10 Cleaning claudia configuration

-STRATUSLAB-376: As a StratusLab release manager or developer, I can control versions of dependencies and plugins from single parent pom file.
- STRATUSLAB-377: As a StratusLab release manager or developer, I can be sure that all plugin versions are specified for a stable build.
- STRATUSLAB-378: As a StratusLab release manager or developer, I can be sure that consistent versions of external dependencies are used.
- STRATUSLAB-378: Next claudia version

16:10 → 16:30 GRNET Tasks

• STRATUSLAB-334: Certify the virtualized grid
• STRATUSLAB-335: Enable shared storage among the reference service nodes
• STRATUSLAB-337: Rehearse reference service upgrade to StratusLab 0.3

Orateur: M. Evangelos Floros (GRNET)

16:30 → 16:50 SixSq

Testing:

• STRATUSLAB-400: Re-create smoke test job in Hudson working on LAL slave
• STRATUSLAB-383: Implement ssh retry logic to work around possible network flakeyness.
• STRATUSLAB-384: Add test to Tester for create image
• STRATUSLAB-317: Configure local ip with local ip/mac pairs and test the NAT feature already implemented in Tester.py
• STRATUSLAB-389: Add test to Tester for this feature (Quota)

MarketPlace:

• STRATUSLAB-394: MarketPlace upload

Misc.:

• STRATUSLAB-290: StratusLab client should provide reasonable error message if python version is not acceptable
• STRATUSLAB-296: stratus-sign-metadata doesn't work with tarball installation

Orateurs: Konstantin, Meb