Ironic/NovaBaremetalIronicMigration
< Ironic
Nova Bare-metal to Ironic migration
Assumptions / Requirements
- Migration is only supported *within* Juno release
- Migrating live instances between virt drivers in Nova is not tested! It is NOT recommended.
- Migrating from Icehouse-baremetal -> Juno-ironic is not supported
- The nova-compute and nova-scheduler will need to be restarted
- Icehouse Nova deployed with:
- Nova "bare-metal" driver
- Populated nova_bm database
- Nova Juno release admin upgrades applied
- Deploy-ironic kernel and ramdisk, uploaded in to glance ( DIB )
- Empty Ironic database exists
High Level Walk Through
- Start maintenance period (to prevent API service access for upgrade)
- Stop Nova services
- Compute
- Scheduler
- Update nova-compute configuration (nova.conf)
- Change settings
- compute_driver
- nova.virt.ironic.IronicDriver
- scheduler_host_manager
- nova.scheduler.ironic_host_manager.IronicHostManager
- compute_driver
- add an [ironic] section (example)
- admin_username = ironic
- admin_password = password
- admin_url = http://keystone.host:35357/v2.0
- admin_tenant_name = service
- Remove the [baremetal] section (example)
- sql_connection = db
- tftp_root = /tftpboot
- flavor_extra_specs = cpu_arch:arch
- driver = nova.virt.baremetal.pxe.PXE
- pxe_network_config=True
- pxe_deploy_timeout= pxe_deploy_timeout
- power_manager = power_manager
- virtual_power_host_user=user
- virtual_power_host_key=/mnt/state/var/lib/nova/virtual-power-key
- virtual_power_ssh_host=ssh_host
- virtual_power_type=type
- Update flavor metadata to reference Ironic's deploy kernel & ramdisk
- Run ironic-nova-bm-migrate script to migrate nova-bm nodes and interfaces to ironic nodes and ports
- Start Ironic services
- Conductor
- Api
- Ensure proper start-up
- restart Nova services
- Compute
- Scheduler
- end maintenance period
- Change settings