CentOS/ RHEL

Overview

A Cloudify Manager is a compute host running Cloudify components.

Deploying Cloudify Manager RPM

The Cloudify Manager RPM file includes all Cloudify Manager components and their dependencies. The RPM is self-contained and the installation process does not require an internet connection.

  1. Download the Cloudify Manager RPM file

  2. Copy the RPM file to your target host

  3. From the terminal of your target host, run:

    sudo yum install <RPM file path>
    
  4. Customize Cloudify Manager’s settings

  5. Install on a single All-In-One host

  6. Cloudify Manager is ready for use at http(s)://<manager_public_address>

Cloudify Manager Configuration

Once RPM is deployed, file /etc/cloudify/config.yaml (View in GitHub) contains all installation options, including:

Setting Description Comments
admin_password Administrator password Recommended. If you do not specify an administrator password in the command-line or the config.yaml file, the installation process generates a random password and shows it as output in the installation logs.
private_ip;public_ip Private and public IP addresses Can be set in config.yaml or as command line argument to cfy_manager install
ssl_enabled External REST communications over HTTPS Recommended.
import_resolver Local path replacement for remote resources with a URL
skip_sanity Skip sanity check after installation Not recommended.
extra_env Additional environment variables (see below)
ssl_inputs SSL communication settings
cloudify_license_path Path to Cloudify license file
task_retries Maximum number of retries for a task. -1 means infinite retries This applies to all workflows.
task_retry_interval Minimum wait time (in seconds) between task retries This applies to all workflows.

You can validate the configurations are valid using cfy_manager validate command.

Adding Environment Variables

In certain cases, it may be required to add environment variables to the processes that run Cloudify Manager. For example, certain organizations impose restrictions on the installation-default temporary files directory (usually /tmp), requiring the adjustment of the TEMP / TMP / TMPDIR environment variables accordingly.

This can be achieved by providing additional settings in config.yaml:

For example, to override the TEMP environment variable with /var/tmp:

mgmtworker:
  extra_env:
    TEMP: /var/tmp

restservice:
  extra_env:
    TEMP: /var/tmp

Multi-Network Management

Cloudify Manager uses Cloudify Agents to execute tasks and collect information about the resources that it manages. You must specify the Cloudify Manager IP addresses or DNS names that your agents will use to communicate with it.

Multi-network management can be configured before installing a new Manager and after.

Option 1: Configure Multi-network Management before Installing a New Manager

The Cloudify Manager networks are configured in the networks section of the /etc/cloudify/config.yaml file, for example:

networks:
    default: <privately_routable_ip>
    external: <externally_routable_ip>

You must specify the name of the Cloudify Manager network for each agent that is deployed in your blueprint with this syntax:

  host:
    type: cloudify.nodes.Compute
    properties:
      agent_config:
        network: external
        install_method: remote
        user: { get_input: username }
        key: { get_secret: agent_key_private }
        port: 22
      ip: { get_input: host_ip }

Option 2: Add New Networks to a Running Manager

cfy_manager add-networks --networks '{"<network-name>": "<ip>", "<network-name>":"<ip>"}'

All-In-One Installation

To install the Cloudify Manager, run:

cfy_manager install [--private-ip <PRIVATE_IP>] [--public-ip <PUBLIC_IP>] [--admin-password <password>] [-v]

Uninstalling Cloudify Manager

Data Loss

Uninstalling the Cloudify Manager erases all Cloudify data and is irreversible.

sudo cfy_manager remove -f
sudo yum remove cloudify-manager-install