Loading…
This event has ended. View the official site or create your own event → Check it out
This event has ended. Create your own
Please note: This schedule is for OpenStack Active Technical Contributors participating in the Icehouse Design Summit sessions in Hong Kong. These are working sessions to determine the roadmap of the Icehouse release and make decisions across the project. To see the full OpenStack Summit schedule, including presentations, panels and workshops, go to http://openstacksummitnovember2013.sched.org.
View analytic
Friday, November 8 • 2:20pm - 3:00pm
Heat integration and scalability

Sign up or log in to save this to your schedule and see who's attending!

Etherpad: https://etherpad.openstack.org/p/savanna-icehouse-architecture

This session will include the following subject(s):

Resources orchestration using Heat:

Savanna should use Heat for resources orchestration. There are number of loosely-researched problems in Heat that should be transformed to bug reports / blueprints in both Heat and Savanna projects to track this change.

The overall goal is to replace one-off orchestration with Heat-based one wherever makes sense.

(Session proposed by Clint Byrum)

New architecture and scalability:

Savanna should be horizontally scalable to support a lot of clusters provisioning at the time. On the other side we should solve the problem with provisioning large clusters, for example, by using multiple engines for one cluster.

There are several potential solutions that are grouped from the following components: controller, conductor, engine, agent.

We should take a look at all of the potential components and at production installations of OpenStack to choose the right way to solve scalability problem.

It's strongly connected with Heat integration.

Additional subtopics related to the failure scenarios handling:

* VM provisioning failure - cluster should be usable in case of 1/1000 VMs with only slave processes failed to be able to just add missed VMs instead of cluster reprovisioning;
* timeouts - we should add timeouts for all parts of provisioning process.

(Session proposed by Sergey Lukjanov)


Friday November 8, 2013 2:20pm - 3:00pm
AWE Level 2, Room 201A

Attendees (41)