Sign up or log in to bookmark your favorites and sync them to your phone or calendar.

Nova - API [clear filter]
Monday, October 3

4:30pm EDT

OpenStack Compute API 2.0
What should the 2.0 version of the API look like? If we make the decision to remove backwards compatibility with API 1.1, what does that open up to us? Here are some concepts that have caused concern in 1.1; we can discuss those. More importantly, we can get a vision of what new features the 2.0 API should have. 1. Fully asynchronous model - are there parts of 1.1 we can clean up? 2. Progress indicators - user experience designers love'em: can they be made more realistic or should they be eliminated? 3. How can we best retrieve (near-) real-time information on errors and usage from a server? Right now, all that data is pushed out over a message queue. As a user, I want to see all the problems with a server at once, and not have to build a solution to store and manage those. 4. Fault analysis and healing: should the OS Compute API be able to recognize problems and suggest solutions? (high disk I/O, network bandwidth, etc.) What would the API for that look like? 5. Can we build elasticity into our cloud? How would we define what that looks like to the user?

Monday October 3, 2011 4:30pm - 5:25pm EDT
Tuesday, October 4

9:00am EDT

Host aggregates in OSAPI admin extension
In this session we would like to discuss the introduction of the concept of aggregate. An aggregate is a collection of compute hosts that have access to shared capabilities (e.g. Storage, network, etc.) and allow things like hosts' zero-downtime upgrades (for example, via live migration of instances from one member of the aggregate to another), thus causing no disruption to guest instances. The concept of hierarchy of aggregates could also be explored for scalability reasons. We propose to expose such a concept to the admin of the cloud, and at the same time to keep this transparent to the end-user. In fact, the OSAPI already provide some capabilities for host management via admin extensions, but this is very crude at the moment. Further extending the concept means that putting a host into 'maintenance mode' implies that all the instances running on it can migrate onto an available host in the aggregate, thus causing no disruptions to guest instances. Bringing such capability in the API (and consequently in the orchestration infrastructure) also means that the admin can intervene on the plaform, and at the same time be agnostic of the kind of hypervisor that the host is running, which is very beneficial.

Tuesday October 4, 2011 9:00am - 9:25am EDT

10:00am EDT

Inventory of cloud resources
The goal is to be able to retrieve information not only about running/scheduled instances & volumes, but about totally available & used H/W resources, such as amount of CPU/memory/disk space+disk types/networking resources/etc. Some of this information reported to schedulers. We can try to retrieve it from them (though it might be tricky in multi-schedulers per zone environments) or register a new service who will collect it from nodes. This session will focus on Nova, but it might be relevant for other services as well.

Tuesday October 4, 2011 10:00am - 10:25am EDT
Salon A
Wednesday, October 5

12:00pm EDT

EC2 Feature Review
Review EC2 features that is currently missing from nova.

Wednesday October 5, 2011 12:00pm - 12:25pm EDT