Installer Approach and Workflow

Approach

To install the CloudCenter platform, you must complete the following phases.

PhaseDescription
1

Prepare Infrastructure

Launch/Identify VMs, Load Balancers, Virtual IP (VIP) or the Elastic IP (EIP) to install and configure the CloudCenter component.

2

Configure Network Rules

Setup Network rules to enable communication across various components.

3

Perform Network Compliance Check

Perform network compliance check to ensure that network rules are setup appropriately.

4

Install and Configure Components

Run installers on Virtual Machines to install CloudCenter components and invoke configuration wizards to setup component properties.

  1. Package Store Installation (Conditional)
  2. Bundle Store Installation (Optional)
  3. CCM Installation (Required)
    1. CCM NON-HA
    2. CCM NON-HA STANDALONE
    3. CCM HA
  4. Per CloudCenter Region Installation (Required)
    1. Dedicated External Script Executor (Conditional)

    2. Dedicated Guacamole Server (Optional)

    3. AMQP (Required)
      1. AMQP NON-HA
      2. AMQP HA
    4. CCO (Required)
      1. CCO NON-HA
      2. CCO HA
  5. Health Monitor Installation (Optional)
  6. Dedicated Docker Registry Installation (Optional)
  7. Custom Image for the Application VM – sometimes referred to as Worker image – (Conditional)  – see Management Agent Java Compatibility
    1. On a Linux Image
    2. On a Windows Image

Understanding Installer and Upgrade Files

The following table explains the purpose of each installer file that is required to install the CloudCenter platform.

FileDescriptionFurther Reference
*_installer.bin

This file is used for one-time installation of OS-based components. It is a binary file that installs OS-related packages required for the CloudCenter platform to function. This file contains the Tomcat, OS packages, Java, Database, AMQP servers, and so forth.

The Phase 4 section provides details on when this file is used for each component.

*-response.xmlThis file is used during the installation process. It includes responses to installer questions (similar to the unattended response file for installers) for different CloudCenter components. This file allows you to customize specific details: for example, the database location.
*_installer.jarThis file is used during the installation and upgrade process. It includes product-specific WAR and CONFIG files like ROOT.war, config wizards, SSL certificates, and so forth.
*_upgrade.bin

This file is only used during an upgrade when a change is required to the underlying OS and OS packages. It is binary file that installs OS_related packages required required for the CloudCenter platform to function. This file contains release-specific files.

 

See the following sections:

 

 

  • No labels