When a customer selects Ironic, some parameters needs to be tuned
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
Mirantis OpenStack | Status tracked in 10.0.x | |||||
10.0.x |
Fix Released
|
High
|
Vasyl Saienko | |||
8.0.x |
Confirmed
|
High
|
Vasyl Saienko | |||
9.x |
Fix Released
|
High
|
Vasyl Saienko |
Bug Description
When a customer selects Ironic in MOS he assumes that Ironic will works 'from a box'.
Some parameters needs to be tuned to get maximum capability.
1) Nova:
max_concurrent_
scheduler_
This parameter should be is near total amount of baremetal servers in the cloud. It defines how nova scheduler map instance to hypervisor. If this value is less than number of simultaneous boot requests to nova, there is a high chance that nova will try to map 2 Instances to same hypervisor, it leads to failure of one of instances as result of scheduller_
Nova claims in API should solve this problem.
2) ironic.
3) Fuel-agent: doesn’t support UEFI shell. UEFI shell should be disabled manually by administrator before enrolling node to Ironic.
===NOTE===
The above actually describes 3 different bugs/improvement requests,
so to track these separately:
1) this bug is left for the Nova parameters tuning only
2) is duplicate of https:/
3) is tracked as separate bug https:/
The priority is high because we need to spend several hours for the configuration of Ironic / Nova and other services "from the box" to allow manage large Ironic clusters.
Customers should get the properly configured Ironic and Nova "from the box" without any additional manual configuration.