Purpose: Nextgen initiatives being developed by multiple OSP teams in tandem. NFV too should join this bandwagon. These initiatives are

1. 1. External Data Plane Management

• Notes document: https://docs.google.com/document/d/1BgRD-5u8yDOpcPF0pL_VCzo_esyhkTrkDrBD4Cedwcs/edit
• Work on standalone roles continues
      - Standalone roles is the effort to remove Puppet and revamp the Ansible roles to free them from dependency on Heat.
          - Notes: https://etherpad.opendev.org/p/tripleo-standalone-roles
          - Much of the other Next Gen initiatives work depends on this
      - Networking reviews needed
          - https://review.opendev.org/c/openstack/tripleo-ansible/+/845653
          - https://review.opendev.org/c/openstack/tripleo-heat-templates/+/842044
          - https://review.opendev.org/c/openstack/tripleo-heat-templates/+/842825
          - https://review.opendev.org/c/openstack/tripleo-ansible/+/842822
          - https://review.opendev.org/c/openstack/tripleo-ansible/+/842041
• "External Data Plane Management Work Planning" doc breaks down future work for Jira structure
      https://docs.google.com/document/d/1Fj7L98sLVjI1-t6eSnK9CTHPAMdmJO3GwBW_HITuwV4/edit
• Flow diagram: https://drive.google.com/file/d/1tvc91goeYp4owbYg3s9iWddulM_md1an/view?usp=sharing

1. 1. Data Plane Adoption

• Notes: https://docs.google.com/document/u/0/d/1b3D10FuSRzEcy7hfhGbi4k2uBZX9F2ohf19CucScPOI/edit
• More discussion about CRC development environments
      - Francesco shared a trick to use haproxy as a way to redirect API access
          https://gist.github.com/fmount/80a2b1c4f975ef1eee7b78f160bea81d
      - Jirka's scripts/notes
          https://gitlab.cee.redhat.com/rhos-upgrades/data-plane-adoption-dev
      - Sean Mooney stood up keystone operator and his notes could be useful
      - Juan Larriba experimenting on an Operator that executes Ansible
          https://github.com/jlarriba/ansibleee-operator
• Some discussion about how networking works between control plane and data plane especially for services that need to serve a (possibly isolated) tenant network from the control plane.  Example: Manila.

1. 1. Multi-RHEL

• Notes: https://docs.google.com/document/u/0/d/1K9Yobmyc3c1efvMr4bw7bgogzJnhl-RHGwCbdJFBE1k/edit
• No meeting last week
• Effort will be in 3 general phases
      - What issues can we anticipate and address before we have CI?
      - Implement CI jobs based on 3 controllers 2 computes, where all are RHEL 9 except one is RHEL 8
      - Finally, use CI to detect and fix bugs that come up in a multi-RHEL context

1. 1. Podified Control Plane

• Notes:
• Work on operators contionues, focused on Keystone operator as well as MariaDB and conversion of Glance CN-OSP operator to new scheme
• Some discussion about CRC resource limits and the issues people are having
      - About CRC: https://crc.dev/crc/
• Requirements gathering: Podified-based CI requirements
      https://docs.google.com/document/u/0/d/1hd6z5VO4RM0fVC2eooJEdWbgq6GRsD8FVTLwrRpMrOc/edit

Goal:

Goal for NFV is, Have end to end integration of these intitiave with NFV workloads, explore possible road blocks from customer side, present them to LT, PM and other management folks. 

Thanks