Region Expansion
Cloud Execution Environment

Contents

1Introduction
1.1Scope
1.2Prerequisites
1.2.1Documents
1.2.2Tools
1.2.3Data
1.2.4Conditions and Limitations

2

Procedure
2.1Hardware Installation and Configuration of the Server
2.2Executing the Installation Command
2.3Fuel Synchronization
2.4Concluding Routine

Reference List

1   Introduction

The document provides instructions on how to expand the Cloud Execution Environment (CEE) with one or more Compute hosts. Throughout this document Compute host hardware is referred to as server.

1.1   Scope

This document describes how to add one or more new servers to the CEE certified hardware configurations.

The document does not include the steps for expanding the configuration outside the limits of the already deployed switches.

This document is only applicable for the following hardware configurations:

Refer to the Configuration File Guide for more information about the CEE configuration types.

Note:  
Systems with user-specific Neutron configuration are outside the scope of this document.

1.2   Prerequisites

This section provides information on the documents, tools, and conditions that apply to the procedure.

1.2.1   Documents

Before starting this procedure, ensure that the following documents have been read and understood:

The following documents are referred and used in this procedure:

1.2.2   Tools

The following tools are needed:

1.2.3   Data

A site-specific IP and VLAN plan is required.

The address variables used in the document IP and VLAN plan are used throughout this document, and are summarized in the following table.

Table 1    IP Variables Based on the IP and VLAN Plan

VLAN

Variable Name

Factory Default IP Address Allocation

fuel_ctrl_sp

<vFuel (static)>

192.168.0.11

Other site-specific data is listed in the following table:

Table 2    Other Variables Used

Resource

Variable Name

External vCIC IP address

<vcic_address>

Personal username to the vCIC

<personal-user>

Password for the personal username to the vCIC

 

Password for the root user on vFuel

 

1.2.4   Conditions and Limitations

During the region expansion process the CICs go into maintenance mode.

Before starting this procedure, ensure that the following conditions are met:

2   Procedure

This procedure describes how to add one ore more servers.

The procedure contains the following activities:

  1. Hardware installation of the new server or servers, see Section 2.1.
  2. Executing the installation command, see Section 2.2.
  3. Backup of vFuel, see Section 2.3.
  4. Concluding Routine, see Section 2.4.

Start the procedure with Section 2.1.

2.1   Hardware Installation and Configuration of the Server

Perform the following steps:

  1. Depending on the used HW infrastructure, refer to the relevant instruction indicated below and perform the steps provided for hardware installation of the server including BIOS configuration:
    Note:  
    In the case of unmanaged servers, before the execution of the installation command, the new server needs to be discovered in vFuel. After the new server has been configured, do the following:
    1. Set the boot device to PXE.
    2. Force restart the server.
    3. Verify in vFuel that the new server has been discovered.

  2. Continue with Section 2.2.

2.2   Executing the Installation Command

Perform the following steps:

  1. Log on to the vCIC by using SSH:

    ssh <personal-user>@<vcic_address>

    Example:

    ssh <personal-user>@10.0.22.10

  2. If prompted, provide the user password.
  3. Log on to vFuel by using SSH:

    ssh root@<vFuel (static)>

    Example:

    ssh root@192.168.0.11

  4. If prompted, provide the user password.

Perform the following steps at the vFuel node:

  1. Add the new server or servers in the /mnt/cee_config/config.yaml file. Refer to the Configuration File Guide for more information.
  2. Use the expandcee command to start the installation.

    This command causes reconfiguration of the switches.

    Note:  
    Verification of the functions of the newly added server or servers is also performed by the command.

  3. Do the relevant action:
    • If the installation ends without issues, continue with Step 11.
    • If the command execution fails, continue with Step 8.
  4. Collect the console printout.
  5. Collect all logs by referring to Data Collection Guideline.
  6. Consult the next level of maintenance support. Further actions are outside the scope of this instruction.
  7. Log out from vFuel:

    exit

2.3   Fuel Synchronization

In order to backup vFuel, follow the instructions in Fuel Synchronization.

Continue with Section 2.4.

2.4   Concluding Routine

Do the following:

  1. Collect all tools and equipment.
  2. Report that the new compute host or hosts have been added.
  3. Carry out any remaining actions according to the work order, if applicable.
  4. The job is completed.

Reference List

[1] BSP Cabinet Management, 1553-CRA 119 1772
[2] BSP Hardware Installation, 1/1531-CRA 119 1772
[3] Hyperscale Datacenter System 8000 Customer Documentation, 2/1551-LZN 901 5032
[4] Increase BSP Tenant Capacity, 12/1543-APP 111 01


Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    Region Expansion         Cloud Execution Environment