Thanks Michel, I am taking your email as a base to understand from your experience more on the details to work the stories below.
I created four stories:
deployment/libvirt: sizing for reference configurations https://storyboard.openstack.org/#!/story/2003835
Currently this is our current libvirt configuration [0] [ All-In-One] - setup_allinone.sh - Controllers: 2 - vCPUs: 6 - Memory: 18 GB - Disks: - 0 600 GB - 1 200 GB - 2 200 GB - NICs: 4 [ Standard Controller ] - setup_standard_controller.sh - Controllers: 2 - vCPUs: 4 - Memory: ~ 17 GB - Disks: - 0 200 GB - 1 200 GB - 4 NICs - Computes: 2 - vCPUs: 4 - Memory: ~ 17 GB - Disks - 0 200 GB - 1 200 GB - 4 NICs Some questions: - Do we need any changes to the above configurations? - We are covered for Simplex, Duplex and Controller Storage configurations but Dedicated Storage is not identified as such, do we need to: 1. Create a specific setup_dedicated_controller.sh? 2. or should we reuse existing setup_standard_controller.sh passing a parameter to identify between Controller or Dedicated Storage? - Once we have these optimizations do we need to port them to our VirtualBox configurations? - In the story description, we mentioned: "Optimize cpu, memory, hardware emulation, etc for test coverage including..." Any more thoughts from your side on what the test coverage means? Any specific Things you want us to consider from a testing perspective? Does it involves things like tempest?
deployment/libvirt: virtual disk placement for reference configurations https://storyboard.openstack.org/#!/story/2003836
Can you please let us understand the use case for this story?
deployment/libvirt: tenant networking for reference configurations https://storyboard.openstack.org/#!/story/2003837
What do you think about this [1] reference configuration for tenant networking? [0] https://git.openstack.org/cgit/openstack/stx-tools/tree/deployment/libvirt [1] https://git.openstack.org/cgit/opnstack/stx-tools/tree/deployment/provision/...