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.
We've been discussing image introspection and image conversion for quite a bit. Unfortunately, we didn't have the base tools needed to implement this feature before but we do now. Now that async-workers has landed, we can start discussing how to take advantage of them and implement things like the 2 blueprints listed below.
This is a follow up of the Julo mid-cycle meet-up discussion. As the on-going progress of artifacts, we'd discuss how to support the OVF/OVA based on the artifacts discussion. There are several things that need be discussed, including the different OVF format versioning support and multiple-images-per-virtual-system, and how to co-operate to achieve this.
Catalog Index Service: The Catalog Indexing service is under discussion of whether or not it should be an optional API and be able to be enabled as a separate endpoint from the primary API service.
etherpad: Catalog Index Service: https://etherpad.openstack.org/p/kilo-glance-catalog-index-service
---
Artifacs repository current implementation status, plans for Kilo and further improvements:
What problem is this trying to solve?: 1. Give a quick update on the current implementation status of Artifact repository: 1.1. Review proposed and implemented solution and architecture 1.2. Get feedback on Artifact Type plugin definition framework (so early adopters can start using it asap) 2. Check what is likely to land in K (additional changes to J spec, etc) 3. Discuss further (K+) plans and roadmap
Modularity, different endpoints, different processes, different service catalog entries:
What problem is this trying to solve?: Pick back up the remaining discussion (from mini-summit) related to the above topic; partially from Artifacts and partially from Catalog Index service discussion.
Glance supportability, logging and proposal of error codes:
What problem is this trying to solve?:
There was recently tweet from Justin Clayton (@justinclayton42) "If there was a video game called Sysadmin, the final boss fight would be OpenStack." This gives clear indication that OpenStack supportability is not on the level required for Enterprise level product. What can we do to make sure that expanding Glance is not the reason OpenStack qualifying this title:
1) Further improvements how we log events in Glance and more clear log messages? 2) How can we improve our part of the documentation? 3) How could we attack our bugs more efficiently? 4) New/existing tooling for failure analysis? Should this be pan OpenStack (new project) or Glance specific? 5) Implementing unified error codes for exceptions raised and logging? 6) More reasonable OSprofiler trace points (https://github.com/stackforge/osprofiler) 7) Using Rally in Glance gates (it's alredy there) more efficiently? Probably it make sense to do some live demo of OSprofiler & Rally during summit.