[openstack-dev] [tripleo] On the road to Pike
emilien at redhat.com
Mon Feb 27 21:53:04 UTC 2017
Here's a summary of what was said at PTG. Feel free to comment if I
Summary: Support for OVS 2.6, Multi-queue and Jumbo Frames are already
making good progress. Need to investigate how to make "Role Specific
Parameters" for complex deployments.
1. Support for OVS 2.6 features for DPDK - Multi-queue and Jumbo Frames:
2. Add OVS 2.6 support in TripleO for DPDK:
# Whole disk images
Summary: Allow TripleO to use partition / volumes parameters when
building the image with tripleo-common. Also make the security
hardened image to be as flexible as possible. One of our OVB CI jobs
will cover the testing.
# Container roadmap
Summary: Goal is to support all services deployed in containers. Bring
new CI job for undercloud-container. Stabilize ovb-containers CI job.
Investigate Upgrades workflow.
1. Support for all services in containers:
2. Deploy a containerized undercloud:
# Upgrades roadmap
1. More support for rolling upgrades, moving towards less
control-plane service downtime.
2. Operator driven upgrades, so Ansible playbooks are externally usable.
3. Add upgrade tasks for services introduced in Ocata.
4. Reducing the pain for service specific upgrades in future.
5. Stabilize CI jobs for scenario upgrades jobs. Run pingtest and make
(please create blueprint)
# Python 3.5
Drivers: EmilienM, apevec
1. Improve unit tests coverage in TripleO Python projects.
2. Run unit test coverage job in TripleO CI.
3. Investigate functional testing jobs for python-tripleoclient (using Fedora?).
# Tendrl for External Storage Deployment/Management
Summary: Deploy Ceph using a Mistral workflow (which triggers
alternative Ceph deployment/management tools e.g. ceph-ansible or
Tendrl). CI coverage wanted that will require ceph-ansible + deps
# Sample Environment Generator
Drivers: bnemec, jtomasek
Summary: Keeping in sync environments parameters with actual
parameters in the services, so sample environments & templates & UI
are synchronized with the same parameters & metadatas.
Blueprint: WIP (bnemec)
1. Consider using a naming convention to work around the
passed-from-parent problem above? e.g private parameter could be
2. Add THT yaml-validate check that enforces all
non-passed-from-parent parameters are identical e.g same type,
description and constraints as they are global scope and passed via
3. Have environment generator update capabilities map as well as
# Future of configuration management
Summary: This cross-deployment-project tried to figure out how to
generate a YAML file that would expose all parameters handled by
OpenStack, using oslo.config to generate it. In the future, this file
could be consumed by OpenStack Ansible, OpenStack Kubernetes, Kolla,
TripleO, etc by a single source of parameters. In the future, we could
think of a unified way to push configuration on containers / nodes
using this file, but for Pike the goal is to generate it and
investigate how we can use it.
Blueprint / Spec: WIP (EmilienM + bnemec)
# Rework $bootstrap_node for composable roles
Summary: $bootstrap_node variable, used to find out the first
controller that is deployed needs to be reworked since the notion of
controller has been lost with the composable roles. Add
<service>_short_service_bootstrap_node support for all services and
also move the db_sync out of the base profiles in puppet-tripleo are
the main actions.
Blueprint: WIP (bandini)
# Composable Networking
Summary: Enable custom networks vs hard-coded network names. Will
require CI: need at least two jobs with net-iso, one with default
networks and one with custom networks.
Bug report: https://bugs.launchpad.net/tripleo/+bug/1633090
# Routed networks
Summary: 4 specs to support Routed Spine and Leaf architecture in TripleO.
1. Routed Spine and Leaf
2. User-specifiable Control Plane IP on Routed Isolated Networks
3. Refactor THT for routed nets
4. Ironic Inspector changes to support routed networks
Dan, any chance to create blueprints and target them to Pike
milestones? Feel free to share links here.
# UI roadmap
Summary: Lot of work. Need to create blueprints in Launchpad and start
planning for Pike.
Blueprints / Specs (I probabaly missed links):
1. Import/Export Deployment Plan
2. GUI logging
3. Network diagram
Please create the remaining blueprints in Launchpad and let us know
the links, so we can target them to Pike.
# Deriving TripleO Parameters from Introspected Data
Driver: fultonj, skramaja
Summary: Set automatically some parameters based on the deployment
type and number of nodes; still letting users override any of the
params we set automatically.
Blueprint: WIP (fultonj)
# CI Q/A
Summary: We need to document what is in the etherpad. The session was
raising interesting questions, that would be useful for our community.
# CI roadmap
Driver: trown, EmilienM
Summary: tripleo-quickstart transition; more coverage with scenarios &
PTG etherpad: https://etherpad.openstack.org/p/tripleo-ptg-pike
Please let us know any question or feedback.
To drivers: please create blueprints and link them to this thread, so
I can work on Launchpad for Pike planning.
Thanks for reading so far,
More information about the OpenStack-dev