Modify the Kernel using the CLI

About this task

The Kernel can be configured during runtime as [ standard <-> lowlatency ].

Procedure

1. Lock the AIO Controller or Worker Node.

   ~(keystone_admin)]$ system host-lock <controller | worker>
   

2. Verify if there are no alarms.

   ~(keystone_admin)]$ fm alarm-list
   

3. Modify the Kernel.

   ~(keystone_admin)]$ system host-kernel-modify <controller | worker> < standard | lowlatency>
   

   For example:

   ~(keystone_admin)]$ system host-kernel-modify controller-0 lowlatency
   ~(keystone_admin)]$ system host-kernel-show controller-0
   +--------------------+--------------+
   |Property            | Value        |
   +--------------------+--------------+
   | hostname           | controller-0 |
   | kernel_provisioned | lowlatency   |
   | kernel_running     | standard     |
   +--------------------+--------------+
   

4. Unlock the AIO Controller or Worker Node.

   ~(keystone_admin)]$ system host-unlock <controller | worker>
   

5. Verify if there are no alarms, and if the Kernel is running.

   ~(keystone_admin)]$ fm alarm-list
   ~(keystone_admin)]$ system host-kernel-show controller-0
   +--------------------+--------------+
   |Property            | Value        |
   +--------------------+--------------+
   | hostname           | controller-0 |
   | kernel_provisioned | lowlatency   |
   | kernel_running     | lowlatency   |
   +--------------------+--------------+
   

Modify Kernel using the Ansible Bootstrap yaml

Add the following line to you localhost.yaml file that is used to bootstrap an AIO controller If the line is missing the default kernel is standard.

kernel : lowlatency

Modify the Kernel using the Development Manager yaml

Add the following line to the deployment-config.yaml.

Default Kernel is standard.

Warning

The subfunctions section must contain lowlatency.

kernel: lowlatency
subfunctions:
- controller
- worker
- lowlatency