Here's a summary of what was said at PTG. Feel free to comment if I missed something.
# NFV Driver: skramaja 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. Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-nfv-updates Blueprints: 1. Support for OVS 2.6 features for DPDK - Multi-queue and Jumbo Frames: https://blueprints.launchpad.net/tripleo/+spec/ovs-2-6-features-dpdk 2. Add OVS 2.6 support in TripleO for DPDK: https://blueprints.launchpad.net/tripleo/+spec/ovs-2-6-dpdk # Whole disk images Driver: yolanda 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. Etherpad: https://etherpad.openstack.org/p/TripleO_whole_disk_images Blueprint: https://blueprints.launchpad.net/tripleo/+spec/build-whole-disk-images # Container roadmap Driver: flaper87 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. Etherpad: https://etherpad.openstack.org/p/tripleo-composable-containers-undercloud Blueprints: 1. Support for all services in containers: https://blueprints.launchpad.net/tripleo/+spec/containerize-tripleo 2. Deploy a containerized undercloud: https://blueprints.launchpad.net/tripleo/+spec/heat-undercloud # Upgrades roadmap Driver: shardy Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-pike-composable-upgrades Actions: 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 jobs voting. (please create blueprint) # Python 3.5 Drivers: EmilienM, apevec Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-pike-python3 Actions: 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 Driver: fultonj 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 packaging. Etherpad: https://etherpad.openstack.org/p/tripleo-tendrl-integration Blueprint: https://blueprints.launchpad.net/tripleo/+spec/tripleo-ceph-ansible Spec: https://review.openstack.org/#/c/387631/ # 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. Etherpad: https://etherpad.openstack.org/p/tripleo-environment-generator Blueprint: WIP (bnemec) Actions: 1. Consider using a naming convention to work around the passed-from-parent problem above? e.g private parameter could be _ServiceNetMap ? 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 parameter_defaults 3. Have environment generator update capabilities map as well as environment files? # Future of configuration management Driver: EmilienM 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. Etherpad: https://etherpad.openstack.org/p/ansible-config-mgt Blueprint / Spec: WIP (EmilienM + bnemec) # Rework $bootstrap_node for composable roles Driver: bandini 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. Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-pike-bootstrapnode-multinode Blueprint: WIP (bandini) # Composable Networking Driver: shardy 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. Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-pike-composable-networking Bug report: https://bugs.launchpad.net/tripleo/+bug/1633090 # Routed networks Driver: dsneddon Summary: 4 specs to support Routed Spine and Leaf architecture in TripleO. Etherpad: https://etherpad.openstack.org/p/tripleo-routed-networks Specs: 1. Routed Spine and Leaf https://review.openstack.org/#/c/421009/ 2. User-specifiable Control Plane IP on Routed Isolated Networks https://review.openstack.org/#/c/421010 3. Refactor THT for routed nets https://review.openstack.org/#/c/425464 4. Ironic Inspector changes to support routed networks https://review.openstack.org/#/c/421011 Dan, any chance to create blueprints and target them to Pike milestones? Feel free to share links here. # UI roadmap Driver: jtomasek Summary: Lot of work. Need to create blueprints in Launchpad and start planning for Pike. Etherpad: https://etherpad.openstack.org/p/tripleo-ui-pike Blueprints / Specs (I probabaly missed links): 1. Import/Export Deployment Plan https://blueprints.launchpad.net/tripleo/+spec/gui-plan-import-export 2. GUI logging https://review.openstack.org/#/c/395138/ 3. Network diagram https://review.openstack.org/#/c/396383/ 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. Etherpad: https://etherpad.openstack.org/p/tripleo-derive-params Spec: https://review.openstack.org/#/c/423304 Blueprint: WIP (fultonj) # CI Q/A Driver: bandini Summary: We need to document what is in the etherpad. The session was raising interesting questions, that would be useful for our community. Etherpad: https://etherpad.openstack.org/p/tripleo-ptg-ci-qa # CI roadmap Driver: trown, EmilienM Summary: tripleo-quickstart transition; more coverage with scenarios & containers. Etherpad: https://etherpad.openstack.org/p/tripleo-ci-roadmap Blueprint: https://blueprints.launchpad.net/tripleo/+spec/use-tripleo-quickstart-and-tripleo-quickstart-extras-for-the-tripleo-ci-toolset 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, -- Emilien Macchi __________________________________________________________________________ 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