StratusLab Sprint 11 Demo

jeudi 31 mars 2011, 10:30 → 13: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 11 Demo". (More info and phone bridge numbers in attached document.) The EVO reservation starts at 10:00, 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:30 (Paris). Please be on time for the meeting!

10:30 → 10:40 Unimplemented Tasks¶

LAL:

• STRATUSLAB-440 : PXE boot for virtual machines.
• STRATUSLAB-445 : Mount disk in Marketplace on virtual machine instance.
• STRATUSLAB-446 : Create machine instance from Marketplace image.
• STRATUSLAB-451 : Registration page for reference infrastructure.

SixSq:

• STRATUSLAB-427 : As a SlipStream user I can have multi-machine deployment created using StratusLab.
• STRATUSLAB-438: Upgrade CLI and Web Monitor to include this error info
• STRATUSLAB-487: Fix manual installation of the StratusLab cloud system (bridge installation)

GRNET:

• STRATUSLAB-432 : As a StratusLab user I can instantiate VMs with private and local IPs in the reference infrastructure
• STRATUSLAB-430 : Collect requirements for grid middleware and grid site operations

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

UCM:

• STRATUSLAB-278 : As a StratusLab user I can reserve a specific IP from the pool of public IPs offered by the cloud service
• STRATUSLAB-442 : Package probes in separate package

10:40 → 11:00 Marketplace¶

• STRATUSLAB-397 : As a Marketplace user, I can visualize the information in the server via an html representation
• STRATUSLAB-418 : Marketplace should provide a landing page with information about service and internal links
• STRATUSLAB-419 : As a StratusLab user I can retrieve metadata from the Marketplace in JSON format
• STRATUSLAB-469 : Marketplace does not work correctly for chrome or safari browsers
• STRATUSLAB-470 : MarketPlace should give more info with 400 error code, instead of generic message: Bad Request

Orateur: Stuart Kenny (TCD)

11:00 → 11:20 LAL Tasks¶

• STRATUSLAB-330: Verification of email addresses in Marketplace.
• STRATUSLAB-441: Persistent storage prototype.
• STRATUSLAB-463: Removed double "usage" in many stratus-* commands.

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

drawings

• marketplace-email.graffle
• marketplace-email.pdf
• persistent-disks.graffle
• persistent-disks.pdf

11:20 → 11:30 Install Claudia packages and run a deploy test with Stratuslab tools¶

• STRATUSLAB-436: As a Stratuslab admin, I can read about Claudia configuration properties on the Wiki.
• STRATUSLAB-435: As a Stratuslab admin, I can add properties to the main configuration file that will be used by Claudia
• STRATUSLAB-437: As Stratuslab release manager or developer, I can be sure that ActiveMQ libraries are part of Claudia
• STRATUSLAB-439: As a Stratuslab release manager of developer, I can run an integration test for Claudia automatically.

11:40 → 12:00 GRNET Tasks¶

• STRATUSLAB-428: As a StratusLab user I can access a reference infrastructure hosting release 0.3 of StratusLab distribution
• STRATUSLAB-429: As a StratusLab user I can instantiate a virtual cluster with a single command
• STRATUSLAB-335: Enable shared storage among the reference service nodes

Orateur: M. Evangelos Floros (GRNET)

12:00 → 12:20 SixSq¶

• STRATUSLAB-310: Re-create the base images, with new metadata format, simple disk layout (SCSI if possible) and swap space (Ttylinux, Ubuntu, CentOS and OpenSuSE?) and STRATUSLAB-303: As a user, I can instantiate images, with SCSI drives
• STRATUSLAB-338: As a Stratuslab sysadmin, I can configure MySQL as ONE's backend
• STRATUSLAB-295: As a StratusLab User CLI user, i want to use my own init.sh script.
• STRATUSLAB-471: Manual installation should install the CA certificates and fetch-crl for updating CRLs
• STRATUSLAB-304: Fix tarball installation of user cli
• STRATUSLAB-466: stratus-upload-image requires that metadata file have an .xml suffix
• STRATUSLAB-366: As a StratusLab user, I can use a simple configuration file to configure the client
• STRATUSLAB-450: As a StratusLab user, I can use credentials that are stored in standard locations
• STRATUSLAB-446: As a StratusLab user, I can run an instance by referencing an image in the marketplace
• STRATUSLAB-445: As a StratusLab user, I can mount a disk described in the marketplace on a machine instance
• STRATUSLAB-498: stratus-validate-metadata gives a return code of 0 even when validation fails

Orateurs: Konstantin, Meb

12:20 → 12:40 UCM Tasks¶

OpenNebula

• STRATUSLAB-331: As a developer of OpenNebula plugins, I can pass appropriate error information back to the user
• STRATUSLAB-453: DB re-factoring to better support schema changes in the future
• STRATUSLAB-452: Backport StratusLab patches to OpenNebula mainstream
  • fix_argument_mistmatch
  • fix-kvm-startup-cmd-redhat : Needs update of kvmrc file to point to emulator path.