15. Appendix - F Detailed Genesis Flow (needs update)ΒΆ
Phase 1:
- Apply power to the management and data switches.
- All ports on the management switch will be enabled and added to a single LAN through genesis routines.
- Power on the compute, storage and controller nodes.
- Each BMC will automatically be assigned an arbitrary IP from the DHCP pool.
- Genesis code accesses management switch to read MAC address table information. (MAC to port number mapping). This will include both BMC MAC addresses as well as PXE port MAC addresses.
- Read BMC port list from the config file.
- Read ip address assignement for BMC ports from the DHCP server
- IPMI call will be issued to determine whether the BMC represents an x86_64 or PPC64 system.
- Each BMC will be instructed to initiate a PXE install of a minimal OS, such as CoreOS or similar.
- Genesis function will access CoreOS and correlate IPMI and PXE MAC addresses using internal IPMI call.
- Each data network port on the client will be issues an ‘UP’ and checked for physical connectivity.
- Cobbler database will be updated. Need more detail.
- Data switch will be configured.
- VLANS.
- verification
- Inventory file will be updated with IPMI, PXE and data port details.
- IPMI will be used to configure for OS reload and reboot.
- OS and packages will be installed on the various systems
- 10 Gb Network ports are renamed
- Networks are configured on system nodes. There will be a unique config per role. Network configuration consists of modifying the interfaces file template for that role and copying it to the servers.
- IP addresses
- VLANS
- Bridges created
- Other post OS configuration (NTP)
- reboot for network config to take effect
- Deployer container is copied to the first controller node.
- The inventory file is copied to the first controller node.
Phase 2:
- Software installation orchestrator is installed on first controller node and given control. Genesis activity continues on first controller node.