docs/doc/source/node_management/kubernetes/host_memory_provisioning/allocating-host-memory-using-horizon.rst

Allocate Host Memory Using Horizon

starlingx

You can edit the platform and Application page memory allocations for a node from the Horizon Web interface using the Memory tab on the Host Inventory pane.

partner

start-after

introduction-text-begin

end-before

introduction-text-end

Due to limitations in Kubernetes, only a single huge page size can be used per host.

starlingx

A node may only allocate huge pages for a single size, either 2MiB or 1GiB.

partner

start-after

usage-text-begin

end-before

usage-text-end

You must also provision one 1GiB huge page per node prior to unlocking a worker or an controller.

Before requesting huge pages on a host, ensure that the host has enough available memory. For details, see About Host Memory Provisioning <about-host-memory-provisioning>. If a huge page request cannot be allocated from the available memory, an informative message is displayed.

1. On the Inventory pane, lock the host you want to edit.

2. Click Host Name to open the settings for the host.

3. On the Memory tab, click Update Memory.

   

4. Use the Update Memory Allocation dialog box to set the memory allocations for each node.

starlingx

For each available node, five fields are available, as illustrated in the following example screen for two nodes. Due to limitations in Kubernetes, only a single huge page size can be used per host, across Application memory.

partner

start-after

limitation-text-begin

end-before

limitation-text-end

Platform Memory for Node n

The amount of memory to reserve for platform use on the Node, in MiB. To see the minimum requirement, hover over the information icon next to the field.

# of Application 2M Hugepages Node n

starlingx

The number of 2 MiB huge pages to reserve for application use on the Node. If no 2 MiB pages are required, type 0. Due to limitations in Kubernetes, only a single huge page size can be used per host, across Application memory.

partner

start-after

application-2m-text-begin

end-before

application-2m-text-end

# of Application 1G Hugepages Node n

starlingx

The number of 1 GiB huge pages to reserve for application use on the Node. If no 1 GiB pages are required, type 0. Due to limitations in Kubernetes, only a single huge page size can be used per host, across Application memory.

partner

start-after

application-1g-text-begin

end-before

application-1g-text-end

partner

start-after

vswitch-hugepage-1g-text-begin

end-before

vswitch-hugepage-1g-text-end

partner

start-after

vswitch-hugepage-size-node-text-begin

end-before

vswitch-hugepage-size-node-text-end

To see how many huge pages of a given size you can successfully request on a node (assuming that pages of another size are not also requested), hover over the information icon next to the field.

Any unused memory is automatically allocated as 4 KiB pages of regular memory for Applications.

1. Click Save.
2. Unlock the host and wait for it to be reported as Available.

partner