Installing the Connector software on an existing Linux host
Suggest changes
PDFs
The most common way to create a Connector is directly from Cloud Manager or from a cloud provider's marketplace. But you have the option to download and install the Connector software on an existing Linux host in your network or in the cloud.
|
If you want to create a Cloud Volumes ONTAP system in Google Cloud, then you must have a Connector running in Google Cloud, as well. You can't use a Connector that's running in another location. |
-
The host must meet requirements for the Connector.
-
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 installation.
-
The Connector installer accesses several URLs during the installation process. You must ensure that outbound internet access is allowed to these endpoints:
-
http://dev.mysql.com/get/mysql-community-release-el7-5.noarch.rpm
-
https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
-
https://s3.amazonaws.com/aws-cli/awscli-bundle.zip
The host might try to update operating system packages during installation. The host can contact different mirroring sites for these OS packages.
-
-
Root privileges are not required to install the Connector.
-
The installation 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. The Connector can operate successfully without the tools.
-
The installer that is available on the NetApp Support Site might be an earlier version. After installation, the Connector automatically updates itself if a new version is available.
-
Download the Cloud Manager 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.
-
Assign permissions to execute the script.
Example
chmod +x OnCommandCloudManager-V3.8.4.sh
-
Run the installation script:
./OnCommandCloudManager-V3.8.4.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 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.
-
Unless you specified the silent parameter, type Y to continue the script, and then enter the HTTP and HTTPS ports when prompted.
Cloud Manager is now installed. At the end of the installation, the Cloud Manager service (occm) restarts twice if you specified a proxy server.
-
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 host. For example, if the Connector 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 Connector 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
-
Sign up at NetApp Cloud Central or log in.
-
After you log in, set up Cloud Manager:
-
Specify the Cloud Central account to associate with the Connector.
-
Enter a name for the system.
-
The Connector is now installed and set up with your Cloud Central account. Cloud Manager will automatically use this Connector when you create new working environments.
Set up permissions so Cloud Manager can manage resources and processes within your public cloud environment:
-
AWS: Set up an AWS account and then add it to Cloud Manager.
-
Azure: Set up an Azure account and then add it to Cloud Manager.
-
GCP: Set up a service account that has the permissions that Cloud Manager needs to create and manage Cloud Volumes ONTAP systems in projects.
-
Create a role in GCP that includes the permissions defined in the Cloud Manager policy for GCP.
-
Create a GCP service account and apply the custom role that you just created.
-
If you want to deploy Cloud Volumes ONTAP in other projects, grant access by adding the service account with the Cloud Manager role to that project. You'll need to repeat this step for each project.
-