[kolla] Victoria priorities
Hi, Hot on the heels of the Ussuri release, we have the results of the votes for Victoria priorities. We voted in etherpad [1], and the results have been added to the whiteboard (L181). Feel free to add your name as an owner on the whiteboard if you would like to be involved. [1] https://etherpad.opendev.org/p/kolla-victoria-priorities Thanks, Mark = Kolla = Infra images (8 votes) https://blueprints.launchpad.net/kolla/+spec/infra-images Owners: Image tiering (6 votes) Avoid breakage of non-core images blocking publishing of all others Owners: Ubuntu focal 20.04 (6 votes) (likely must-have anyway unless we are dropping ubuntu) Owners: Stable branch life-cycle (6 votes) Use stable/<release> rather than versions Owners: Integrate support for pull-retag-push (4 votes) https://storyboard.openstack.org/#!/story/2007731 (original kayobe story) Owners: Kolla depends-on upstream projects to behave as it should (2 votes) Owners: Build, test, promote CI pipeline (2 votes) Build images, test them, promote for general availability Owners: = Kolla Ansible = Let's Encrypt integration - container running certbot, triggers certificate distribution (10 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/letsencrypt-https this would be useful to have for tls everywhere deployment too. Owners: headphoneJames Document, automate and test Octavia resource registration (10 votes) Owners: Document, automate and test Designate resource registration (8 votes) Also designate sink set up for instance dns Owners: yoctozepto Documentation review & refresh (8 votes) Owners: everyone Federated keystone (7 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/add-openid-support Owners: Container health checks (7 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/container-health-check mix with sanity checks? https://blueprints.launchpad.net/kolla-ansible/+spec/sanity-check-container Owners: mnasiadka Fix the "Ansible may run more handlers than originally planned" with all the extras around config (6 votes) https://bugs.launchpad.net/kolla-ansible/+bug/1863510 Owners: Improve test coverage (the never-ending story) (6 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/kolla-deployment-scenar... Multiple regions Owners: Performance & scalability improvements (5 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/performance-improvement... Owners: mgoddard Implement TLS Backend for all core services with externally exposed API (nova for example) (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/add-ssl-internal-networ... Owners: headphoneJames TLS in other services: (4 votes) MariaDB https://blueprints.launchpad.net/kolla-ansible/+spec/mariadb-ssl-support RabbitMQ https://blueprints.launchpad.net/kolla-ansible/+spec/message-queue-ssl-suppo... Memcached https://blueprints.launchpad.net/kolla-ansible/+spec/memcached-ssl-support Owners: Upgrade checkers (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/upgrade-checkers Owners: Node removal (decommission) (4 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/remove-node Mark has already done related work for CentOS 8 migration do more than destroy - clean them up! from databases etc. aligns with day-2 ops Owners: Support for reload (e.g. for TLS), also graceful shutdown (4 votes) Owners: Mechanism for distributing certificates to services after deployment (2 votes) Owners: Day 2 ops tools (restart containers, upgrade Docker, prune DBs…) (2 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/docker-upgrade-reconfig... Owners: Capture docker logs (2 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/capture-docker-logs Owners: Nova cells v2 - shared cell controllers, multiple DBs and MQs (0 votes) https://blueprints.launchpad.net/kolla-ansible/+spec/nova-cells-shared-contr... https://blueprints.launchpad.net/kolla-ansible/+spec/cellsv2-rabbitmq-suppor... Owners: = Kayobe = Document configuration walk through (7 votes) https://storyboard.openstack.org/#!/story/2004360 Owners: Support multiple environments from a single kayobe configuration (3 votes) https://storyboard.openstack.org/#!/story/2002009 Owners: priteau Support for multiple deploy image types on overcloud nodes (2 votes) https://storyboard.openstack.org/#!/story/2002098 Owners: Next generation discovery & network configuration (2 votes) https://storyboard.openstack.org/#!/story/2004295 https://github.com/markgoddard/kayobe-switch-config-poc Owners: Replace bifrost with kolla-ansible for seed services (2 votes) https://storyboard.openstack.org/#!/story/2004293 Owners: Easier customization of Kayobe commands (0 votes) https://storyboard.openstack.org/#!/story/2001663 Owners: jovial Command plan that tells you which playbooks will run / Fix dry run (0 votes) Pierre pointed out that -lt provides similar functionality, e.g kayobe overcloud host configure -lt Owners: Inventory exporter (0 votes) Owners:
participants (1)
-
Mark Goddard