vFuel On Demand Use
Cloud Execution Environment

Contents

1Introduction
1.1Description
1.2Prerequisites

2

Procedure
2.1Disable vFuel
2.2Enable vFuel

1   Introduction

This document summarizes the procedure for disabling and enabling vFuel on a single server environment.

1.1   Description

vFuel manages the Cloud Execution Environment (CEE) infrastructure life cycle and runs in a separate virtual machine on CentOS Linux.

vFuel is responsible for the following:

To save resources on a single server environment, vFuel is not migrated to the production environment but it is switched off on the kickstart server. vFuel can be reactivated when needed, for example, to add new packages on vCIC or compute nodes, or to do an update.

1.2   Prerequisites

CEE is installed, as described in CEE Installation.

2   Procedure

vCIC and compute nodes run several services or use configurations related to vFuel, as follows:

Disabling vFuel stops these services and removes all related configurations. Before any update or modification of the environment, vFuel needs to be enabled again.

2.1   Disable vFuel

To disable vFuel, proceed with the following steps on vFuel as root user:

  1. Execute the following commands:

    cd /usr/share/ericsson-orchestration/playbooks

    openstack-ansible fuel-disable.yml

    The expected output shows only ok and changed statuses and no failed at PLAY RECAP.

    Example:

  1. Switch off the Fuel Virtual Machine (VM) by executing the following command:

    shutdown -h now

    Using Linux libvirt the VM is listed as shut off:

    root@compute-0-1:~$ virsh list --all
     Id    Name                           State
    ---------------------------------------------------
     -     fuel_master                    shut off

  2. To disable autostart of the vFuel after kickstart server reboot, execute the following command:

    virsh autostart fuel_master --disable

vFuel is now disabled. Enabling again is described in Section 2.2.

2.2   Enable vFuel

To enable vFuel again, proceed with the following steps. All commands entered on vFuel should be run as the root user.

  1. Switch on the vFuel on the kickstart server by executing the following commands:
    1. Using Linux libvirt, get the <vm_name> by executing the following command:

      virsh list --inactive

    2. Start the vFuel by executing the following command:

      virsh start <vm_name>

    3. To enable autostart of the vFuel after kickstart server reboot, execute the following command:

      virsh autostart fuel_master

  2. Log on to the restarted vFuel and ensure that the Fuel services have started successfully by executing the following command:

    fuel-utils check_all

    Note:  
    Following a system startup vFuel needs time to initialize services.

  3. Some more minutes are needed for vFuel to start operating.

    To check if vFuel is operational, execute the following command:

    fuel node

    Note:  
    It can be necessary to execute the command several times, until it is successful.

    The expected output contains a properly formatted table with the node list.

    Note:  
    The nodes online value remains False until vFuel is re-enabled.

Figure 1   Node List Example

  1. On vFuel, execute the following commands to enable it:

    cd /usr/share/ericsson-orchestration/playbooks

    openstack-ansible fuel-enable.yml

vFuel is enabled again.

The expected output shows only ok and changed statuses and no failed at PLAY RECAP.

Example: