Generating input JSON using HPE Telco Infrastructure Configuration Generator

The HPE Telco Infrastructure Configuration Generator (TICG) is a browser-based tool which can be used to generate the validated JSON output. This tool also helps to validate the user inputs before generating the JSON. This schema (input JSON file) is used to deploy NFVI stack as per the customer's topology.
Prerequisites
  • Ensure that you have a valid account on HPE Smart CID portal (https://smartcid.itcs.hpe.com) to generate the validated JSON output.

  • Supported web browser – Google Chrome (Version 56 and above) and Firefox (Version 48 and above).

Procedure
  1. Log in to HPE Smart CID. You can login using one of the following options:
    • HPE Employee Login - If you are an HPE employee, use your Virtual DigitalBadge to login.

    • Customer / Partners Login - If you are a customer or a partner, use your HPE Passport login credentials. If you do not have the HPE passport credentials, click Create an account, and follow the steps to create a user account. For any assistance, reach out to HPE Sales and Support team.

  2. Select Start a new CID.
  3. From the Select Converged System drop-down menu, select HPE Telco Infrastructure Configuration Generator, and click Start.

    The Welcome to HPE Telco Infrastructure Configuration Generator page is displayed.

  4. In the Welcome page, click Start.

    The Settings > Modules page is displayed.

  5. In the Modules page, perform the following substeps:
    1. Select Starter Kit as the configuration type.
    2. Ensure that all modules Hardware Preparation, Switch Automation, Image Service, and VIM are selected.
    3. Select RHOCP as the Virtual Infrastructure Manager and Baremetal as the deployment type.
    4. Click Next.

      The Settings > Global Settings page is displayed.

  6. In the Global Settings page, perform the following substeps:
    1. Select either Manual or DHCP for OOBM IP Allocation.
      You have the option to choose between assigning static iLO IPs or iLO DHCP IPs. Based on the options selected for OOBM IP Allocation, subsequent options are displayed.
      • You can select the static IP option if you already have the static IPs for the servers available. If Manual is selected, enter the valid ILO-OOBM CIDR range.

        If you do not have static IPs available, you can select static IP option after manually assigning the static IPs, Assigning static iLO-OOBM IP address to DL servers.

      • You can select the iLO DHCP option if you have the serial number and label password available for all the servers. To enable iLO for DHCP, netconfig must be enabled on the management switches. If DHCP is selected, ensure that Comware/Cumulus/Aruba is selected as the Management Switch NOS.

    2. Optional. Select Yes for SNMP Configuration if required. Default value is No.
    3. Optional. Select Yes for ODIM Plugin if required. Default value is No.
    4. Click Next.

      The Settings > Switch page is displayed.

  7. In the Switch page, perform the following substeps:
    1. Select Aruba as the data switch NOS.
    2. Fill in the details for data, management, border leaf and spine switches.
    3. Optional. Select Yes for CFM Plugin if required. Default value is No.
    4. Click Next.

      The Settings > Servers page is displayed.

  8. Fill in the details in the Servers page and click Next.
    NOTE:

    The bootstrap node will be reused as one of the worker nodes. Hence, provide the worker node count as 'n-1' for starter kit, where n is the total number of worker nodes available for the starter kit.

    The Advanced Settings page with the following subsections is displayed:
    • Networking

    • Compute Configuration

    • Platform Management

    • Hardware Components

    • External Storage

  9. Click the pencil icon to make the edits to the fields in each of the section and then click Save to finalize the entries. You can click Previous to go back to previous page or click Preview to see the structure of the JSON.
    NOTE:

    The information filled in TICG for the local registry, ODIM RA, and CFM must match the actual configuration.

    The input JSON file is downloaded. For sample input JSON files, see Sample Input JSON.