Installing Cloud Manager on an existing Linux host Edit on GitHub

If you want to run the Cloud Manager software on an existing host, you can download and install the software on a Linux host in your network or in the cloud.

Before you begin

A Red Hat Enterprise Linux system must be registered with Red Hat Subscription Management. If it is not registered, the system cannot access repositories to update required 3rd party software during Cloud Manager installation.

About this task
  • Root privileges are not required to install Cloud Manager.

  • Cloud Manager installs the AWS command line tools (awscli) to enable recovery procedures from NetApp support.

    If you receive a message that installing the awscli failed, you can safely ignore the message. Cloud Manager can operate successfully without the tools.

Steps
  1. Review networking requirements for your cloud service provider:

  2. Set up permissions for Cloud Manager:

    1. If you want to deploy Cloud Volumes ONTAP in AWS, set up an IAM role that includes the required permissions.

    2. If you want to deploy Cloud Volumes ONTAP in Azure, create and set up a service principal in Azure Active Directory.

  3. Review Cloud Manager host requirements.

  4. Download the software from the NetApp Support Site, and then copy it to the Linux host.

    For help with connecting and copying the file to an EC2 instance in AWS, see AWS Documentation: Connecting to Your Linux Instance Using SSH.

  5. Assign permissions to execute the script.

    Example

    chmod +x OnCommandCloudManager-V3.5.0.sh
  6. Run the installation script:

    ./OnCommandCloudManager-V3.5.0.sh [silent] [proxy=ipaddress] [proxyport=port] [proxyuser=user_name] [proxypwd=password]

    silent runs the installation without prompting you for information.

    proxy is required if the Cloud Manager host is behind a proxy server.

    proxyport is the port for the proxy server.

    proxyuser is the user name for the proxy server, if basic authentication is required.

    proxypwd is the password for the user name that you specified.

  7. Unless you specified the silent parameter, type Y to continue the script, and then enter the HTTP and HTTPS ports when prompted.

    If you change the HTTP and HTTPS ports, you must ensure that users can access the Cloud Manager web console from a remote host:

    • Modify the security group to allow inbound connections through the ports.

    • Specify the port when you enter the URL to the Cloud Manager web console.

      Cloud Manager is now installed. At the end of the installation, the Cloud Manager service (occm) restarts twice if you specified a proxy server.

  8. Open a web browser and enter the following URL:

    https://ipaddress:port

    ipaddress can be localhost, a private IP address, or a public IP address, depending on the configuration of the Cloud Manager host. For example, if Cloud Manager is in the public cloud without a public IP address, you must enter a private IP address from a host that has a connection to the Cloud Manager host.

    port is required if you changed the default HTTP (80) or HTTPS (443) ports. For example, if the HTTPS port was changed to 8443, you would enter https://ipaddress:8443

  9. Sign up for a NetApp Cloud Central account or log in if you already have one.

  10. When you sign up or log in, Cloud Manager automatically adds your user account as the administrator for this system.

  11. After you log in, enter a name for this Cloud Manager system.

After you finish

You can start creating Cloud Volumes ONTAP systems but you might want to perform additional setup first.