On 05/02/18 10:25, Christian Berendt wrote:
Hello Paul.
On 5. Feb 2018, at 11:12, Paul Bourke <paul.bou...@oracle.com> wrote:
This does not mean I don't have a vision for Kolla - no project is perfect
Regardless of that, I would be interested in your visions. What specifically do
you want to tackle in the next cycle in kolla? What should be the focus?
Christian.
Hi Christian,
Sure thing :) To sum it up I would like to see us focus on Kolla in
production environments. This is the mission of the project, and we
still have ways to go. Specifically:
* Improving our tooling. Currently kolla-ansible (as in the shell
script) is very simplistic and requires operators to go under to the
hood for basic things such as checking the health of their cloud,
diffing configs, viewing logs, etc. [0]
* Related to the above, we need improved monitoring in Kolla.
* Finish the zero downtime upgrade work.
* Resolving issues around configuration [1]. We need to decide how much
we want to provide and make it as straight forward as possible for
operators to override.
* Documentation should continue to be a priority.
* Finally, I would like to start the discussion of moving each element
of Kolla out into separate projects. In particular I think this needs to
happen with kolla-kubernetes but potentially the images also.
Each of these are areas that I've specifically heard from real world
operators, and also I think are key to the future and overall health of
the project. If you'd like to discuss any in more detail please give me
a shout at any time.
-Paul
[0] https://blueprints.launchpad.net/kolla/+spec/kolla-multicloud-cli
[1]
http://lists.openstack.org/pipermail/openstack-dev/2018-January/126663.html
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
