Loading…
OpenStack Kilo Design Summit has ended
This is the schedule for the Kilo Design Summit, where OpenStack contributors discuss the future of OpenStack development.
Click here for the main OpenStack Summit conference schedule.

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

Heat [clear filter]
Wednesday, November 5
 

13:50 CET

Heat integration strategy, functional & unit tests
Discussion:

- Discuss plan for in-tree functional and integration tests, and relationship with tempest

- Making use of Rally for performance and scalability testing

- Our in-tree "unit" tests have, in some cases, totally insane and unmanageable amounts of coupling, such that one minor change to some code can result in completely unreasonable test fallout.

- Some desirable changes become impractcal or avoided purely due to test fallout

- Need to move towards less coupled actual unit tests, combined with some integration tests which are easier to maintain

- External projects Heat usage patterns (sahara, murano, tuskar)


Wednesday November 5, 2014 13:50 - 14:30 CET
Degas

14:40 CET

Heat Upgrades (testing, status, zero downtime)
Problem: What types of updates do we want to support? How can we achieve this?
Discussion:
Should we be looking at nova objects to handle rolling updates better? https://review.openstack.org/#/c/127532/2/specs/kilo/adopt-oslo-versionedobjects.rst
I have added a cross project topic also.

Versioning all-the-things (RPC, API)
(shardy) Not neccesarily saying I have answers to this or that I need to lead the session, but this has been playing on my mind lately..

So far we've taken a less than disciplined approach to versioning things:

- Adding stuff (and worse later having to remove or disable it) to ReST API endpoints without changing the API version, so the actual capabilities of a Heat endpoint are not easily discoverable for clients

- Changing RPC interfaces over time without ever bumping the RPC version, this causes major problems for those doing rolling live upgrades of multi-engine heat deployments for example.

- Also what about resource plugin interfaces, should these be versioned , as they're not tied to the template DSL version?


Wednesday November 5, 2014 14:40 - 15:20 CET
Degas

15:30 CET

Heat Convergence - resolving any questions
This is a placeholder to discuss the progress and issues found with the PoC work and help clarify some of the design. A lot more will get done in the Friday session, this is just a starting point to that.


Wednesday November 5, 2014 15:30 - 16:10 CET
Degas

16:30 CET

Heat Autoscaling API
With the first stage of convergence, an Autoscaling API that supports multiple updates without queueing could well be feasible in Kilo. We need to discuss what work needs to happen to get the Autoscaling API back on track, and who is going to do it.

Discussion:
Possible steps
Rearrange class hierarchy
Implement separate DB tables (like e.g. software deployments)
Move implementations into a separate Python library (don't mix with resource plugins)
Add a ReST API


Wednesday November 5, 2014 16:30 - 17:10 CET
Degas

17:20 CET

Heat and Containers
Problem: Discuss possible approaches for container management with Heat
Discussion:
There are multiple options on how to manage containers (specifically docker) with heat.
At present there is an implementation proposed[1] to use software-config and instance docker hook along with a container-manifest - inline with google container manifest used in kubernetes[2]
However, this does not support lifecycle management of the pod/containers.
There is an alternate approach proposed by this [3] blueprint where k8s pod config resource, k8s deployment resource would be implemented. Inital spec proposed for this available here[4]. However, there are some issues as the k8s pod is not idempotent and there is still a need to write a hook.

[1] https://bugs.launchpad.net/heat-templates/+bug/1380886, https://review.openstack.org/#/c/128182/
[2] https://cloud.google.com/compute/docs/containers/container_vms.
[3] https://blueprints.launchpad.net/heat/+spec/k8s-container-pod-resources
[4] https://review.openstack.org/#/c/130117/


Wednesday November 5, 2014 17:20 - 18:00 CET
Degas
 
Thursday, November 6
 

09:00 CET

Heat Template format useability improvements
Problem: Some template authoring tasks are not obvious, difficult, or not possible
Discussion:
The point of this session would be to try and find/prioritise some useful small/medium features that improve the template writing experience.
https://etherpad.openstack.org/p/heat-useablity-improvements


Thursday November 6, 2014 09:00 - 09:40 CET
Degas

09:50 CET

Heat API and general useability improvements
Interacting with the Heat API via python-heatclient and diagnosing issues can be difficult.
This is part 2 of our useability sessions focused at improving our user experience.
https://etherpad.openstack.org/p/heat-useablity-improvements


Thursday November 6, 2014 09:50 - 10:30 CET
Degas
 
Friday, November 7
 

09:00 CET

Heat contributors meetup
The contributors meetup is a informal gathering of the project contributors, with an open agenda.

Friday November 7, 2014 09:00 - 12:30 CET
Corot

13:40 CET

Heat contributors meetup
The contributors meetup is a informal gathering of the project contributors, with an open agenda.

Friday November 7, 2014 13:40 - 17:10 CET
Corot