Operator Initial Setup for BMaaS
================================
1. Create overcloud pools of HW matching flavors
2. Create overcloud BMC network, accessible to overcloud Ironic
3. Create overcloud provisioning network (tenant networks created by Neutron)
4. After HW profile machine ready state is complete the node provisioning ports are detached
5. Cleaning policy for the HW types is stored in configuration in Ironic
6. 3rd party extensions to IPA will require an image rebuild
7. Each role that a machine might have needs its own cleaning stage rules to get to ready state
8. An LLDP introspection process will be required (enoexist, today)
Operator Overcloud BMaaS Client
===============================
The BMaaS use case requires a new BMaaS client that operates in the overcloud. This is similar to the undercloud’s tripleo-client functionality. The BMaaS client is the tool used to complete the Operator Initial Setup process. The overcloud BMaaS client should have the following features/capabilities:
- Profile matching
- Ready state configuration: BIOS and RAID
- Top of Rack (TOR) switch induction, which entails:
-- Neutron ML2 plugin configuration
-- Updates about physically connections
-- Ironic portgroups
-- Updating of Ironic ports