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.

Oslo [clear filter]
Wednesday, November 5
 

11:00 CET

Oslo graduation schedule
Which modules are ready to graduate and what order do they need to be done?

https://etherpad.openstack.org/p/kilo-oslo-library-proposals



Wednesday November 5, 2014 11:00 - 11:40 CET
Corot

11:50 CET

oslo.messaging
- Where can we find more reviewers?
- What do we do to keep the drivers up to date? Should they move to their own source trees?
- How can we get python 3 support?
- What is the relationship between oslo.messaging and kombu?

https://etherpad.openstack.org/p/kilo-oslo-oslo.messaging


Wednesday November 5, 2014 11:50 - 12:30 CET
Corot

13:50 CET

A Common Quota Management Library
We have a few different groups that want to revamp quota management. What should a shared quota library look like, and how should we develop it?

https://etherpad.openstack.org/p/kilo-oslo-common-quota-library



Wednesday November 5, 2014 13:50 - 14:30 CET
Corot
 
Thursday, November 6
 

11:50 CET

taskflow
How can we recruit more reviewers for taskflow? Should some of its features lib in other libraries?

https://etherpad.openstack.org/p/kilo-oslo-taskflow



Thursday November 6, 2014 11:50 - 12:30 CET
Corot

13:40 CET

Using alpha versioning for Oslo libraries
We use alpha version numbers on Oslo libraries to limit releases of new libraries to our development environment, in part to avoid risk in the stable maintenance builds. We also use them to indicate to distros that they may not need to package the alpha release but can use it for testing their packaging tools. There are a lot of objections to the use of alpha version numbers., and the main argument seems to be that we shouldn't be relying on alpha versions, which IMO ignores the fact that we need development and functional test time on new libraries just as we do with applications. This topic is then tied up with thes question of whether and how we do functional testing and unit cross-testing for libraries as well as the role of the incubator in evolving APIs.

https://etherpad.openstack.org/p/kilo-oslo-alpha-versioning



Thursday November 6, 2014 13:40 - 14:20 CET
Corot

16:30 CET

Python 3 support in Oslo
Status, blockers, and plans for work in kilo.

https://etherpad.openstack.org/p/kilo-oslo-python-3



Thursday November 6, 2014 16:30 - 17:10 CET
Gauguin

17:20 CET

Moving Oslo away from namespace packages
Should we? How do we do it?

https://etherpad.openstack.org/p/kilo-oslo-namespace-packages



Thursday November 6, 2014 17:20 - 18:00 CET
Gauguin