Registered by Antonio Rosales on on 2013-04-17

Sprint on cloud development.

09:00 PDT on Monday, 2013-05-06
18:00 PDT on Friday, 2013-05-10

Meeting drivers

Each meeting has a person, or team, responsible for deciding which items are accepted for the agenda. This team is called the "meeting driver" and for Cloud Sprint May 2013 they are:

You should contact the meeting driver if you have any additional questions about the structure or agenda of the meeting.


Latest 5 additions to the meeting agenda

[GOAL] Bring stability, scalability, trustworthiness to The site must always be available and its data accurate for authors, reviewers, and clients like [RATIONALE] falls over often, and charms go missing for many hours. Many charms contradict the informa...
[GOAL] Develop a charm for backup. [RATIONALE] Enterprises and people who are emotionally attached to their data want a way to back up the data.
[GOAL] Include support for deployer files in GUI. [RATIONALE] Deployer files, as used by Kapil's deployer tool, allow devops to automate larger deployments, and allow great demos of how Juju allows services to work together quickly. GUI support could make it easier to visualize them before deploying them, and woul...
[GOAL] General improvements to OpenStack Charms; specifically: 1) Rationalize charms to all be python based 2) Unit testing 3) Consolidate openstack-charm-helpers (see also charmsupport from Canonical IS) 4) Automated testing of proposed changes (including regression testing back to essex) [RATIONALE] The current ...
Test the Go bindings for LXC, especially for suitability for use by juju. [GOAL] Determine whether the existing lxc api Go bindings suffice for use by juju. [RATIONALE] The lxc api and its bindings have been written so that the same core lxc code could be used by many projects (libvirt, juju, arkose, etc). At a pr...

There are a total of 47 specifications on the meeting agenda. There are 3 specifications proposed which the organisers will review. You can view the full current agenda here.