Deploying Cloud Volumes ONTAP in Azure via Cloud.NetApp.com (draft)

My last guide was built around installing Cloud Volumes ONTAP (CVO) in Azure done predominantly through the Azure portal. NetApp has since transitioned much of the process to NetApp Cloud Central (cloud.netapp.com) portal. The process is largely the same, just some of the workflow steps have shifted around.

For this guide I’m going to walk through deploying CVO and Cloud Manager in Azure. CVO deployment in AWS is also available, Google Cloud is on the road map. Cloud Manager can either be installed in your preferred hyperscaler or in your local environment. Best practice is to have it in the cloud alongside CVO so you don’t have to worry about onsite issues (eg. Godzilla stepped on your data center) from impacting management.

 

Before starting you’ll have to make sure that that your Azure networking is set up correctly for both CVO and Cloud Manager (name now simplified from the previous OnCommand Cloud Manager – OCCM). Here’s the official documentation for Cloud Manager, and here’s the documentation for CVO.

Step 1

Once that’s all good to go you’ll have to create a policy within Azure to allow authentication from Cloud Central.

Step 1.1

Download the Cloud Central for Azure JSON file from NetApp, https://s3.amazonaws.com/occm-sample-policies/Policy_for_cloud_Manager_Azure_3.6.1.json

Step 1.2

Modify the JSON file by adding your Azure subscription ID in the Assignable Scopes portion;

 “AssignableScopes”: [“/subscriptions/xxxxxxx-xxxxxx-xxxxx-xxxx-xxxxxxxxxx”],

Your subscription ID can be found in the Azure Marketplace by going to Cost Management + Billing on the left hand side.

Step 1.3

Set up a custom role using the JSON file. So, assuming you know your way around Azure, this is pretty straight forward. If you don’t then here’s how I did it.

In the top right of the Azure portal look for the CLI button and bring up Azure PowerShell. Once you’re in it you can create your JSON file in the PowerShell instance by using vi and copying up the JSON contents.

PS Azure:\> ls
Azure:/
PS Azure:\> vi Policy_for_cloud_Manager_Azure_3.6.1.json
(Use your awesome vi skills here to insert the JSON script, make your lift easier and put your subscription info in first, then save it out)

Now simply run

PS Azure:\> az role definition create –role-definition Policy_for_Setup_As_Service_Azure.json

If it worked correctly it will output all the configuration and return to you to the prompt with no error messages. You should now have a new role called “OnCommand Cloud Manager Operator.”

Step 1.4

Next step is to assign this role to a user account. For this step I recommend having a pre-defined user account just for CVO management. This will make things more secure and more manageable than using your root or individual employee account.

To assign a role via the Azure Portal go to Cost Management + Billing on the left hand side and select the appropriate subscription. From here select Access Control (IAM) and then Add.

In the wizard that pops up look for the role you created previously, in this case “OnCommand Cloud Manager Operator” and assign it to your user. You’ll see a success notification in the top right of the portal once complete.

Step 2

Now for the fun part, deploying Cloud Manager!

Head over to Cloud Central at (cloud.netapp.com). If this is your first install you head toward the Cloud Volumes ONTAP section of the site, select Start Free Trial, and start the process. Alternatively, after logging in, you can go to Fabric View (top right) and begin your deployment there. This is where you’ll come in the future to manage your NetApp cloud infrastructure.

From here on out it’s basically a step-by-step wizard which is fairly straight forward.

Step 2.1

Select our deployment destination, in this case Azure.

 

 

Judson McKratz