3562a6a957
This patch adds an online data migration script to process the ratio with 0.0 or None value. If it's an existing record with 0.0 values, we'd want to do what the compute does, which is use the configure ``xxx_allocation_ratio`` config if it's not None, and fallback to using the ``initial_xxx_allocation_ratio`` otherwise. Change-Id: I3a6d4d3012b3fffe94f15a724dd78707966bb522 blueprint: initial-allocation-ratios
28 lines
1.2 KiB
YAML
28 lines
1.2 KiB
YAML
---
|
|
upgrade:
|
|
- |
|
|
The default value for the "cpu_allocation_ratio", "ram_allocation_ratio"
|
|
and "disk_allocation_ratio" configurations have been changed to ``None``.
|
|
|
|
The ``initial_cpu_allocation_ratio``, ``initial_ram_allocation_ratio`` and
|
|
``initial_disk_allocation_ratio`` configuration options have been added to
|
|
the ``DEFAULT`` group:
|
|
|
|
- initial_cpu_allocation_ratio with default value 16.0
|
|
- initial_ram_allocation_ratio with default value 1.5
|
|
- initial_ram_allocation_ratio with default value 1.0
|
|
|
|
These options help operators specify initial virtual CPU/ram/disk to
|
|
physical CPU/ram/disk allocation ratios. These options are only used when
|
|
initially creating the ``computes_nodes`` table record for a given
|
|
nova-compute service.
|
|
|
|
Existing ``compute_nodes`` table records with ``0.0`` or ``None`` values
|
|
for ``cpu_allocation_ratio``, ``ram_allocation_ratio`` or
|
|
``disk_allocation_ratio`` will be migrated online when accessed or when
|
|
the ``nova-manage db online_data_migrations`` command is run.
|
|
|
|
For more details, refer to the `spec`__.
|
|
|
|
.. __: https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/initial-allocation-ratios.html
|