OnCommand® Cloud Manager 2.2
Installation and User Guide
For Volume Management
March 2016 | 215-11030_A0
[email protected]
Table of Contents | 3
Contents
Deciding whether to use this guide ............................................................. 4
Product overview .......................................................................................... 5
How the Volume View works ...................................................................................... 6
Cloud Manager REST APIs ........................................................................................ 6
Installation and volume management workflow ....................................... 7
Preparing for installation and setup ........................................................... 8
Preparing your AWS environment .............................................................................. 8
AWS networking requirements ....................................................................... 9
Cloud Manager requirements .................................................................................... 10
Installation and setup worksheet ............................................................................... 11
Installing OnCommand Cloud Manager ................................................. 12
Launching a Cloud Manager instance in a standard AWS region ............................. 12
Installing Cloud Manager on an existing Linux host ................................................ 13
Setting up OnCommand Cloud Manager ................................................ 14
Registering for support .............................................................................................. 16
Managing NFS volumes ............................................................................. 17
Logging in to Cloud Manager ................................................................................... 17
How Cloud Manager allocates cloud resources ........................................................ 18
How Cloud ONTAP licenses impact available capacity and allocation of AWS
resources .............................................................................................................. 19
Creating NFS volumes .............................................................................................. 20
Mounting volumes to Linux hosts ............................................................................. 20
Cloning volumes ....................................................................................................... 21
Managing data access to volumes ............................................................................. 21
Deleting volumes ....................................................................................................... 21
Changing the management view ............................................................... 22
Copyright information ............................................................................... 23
Trademark information ............................................................................. 24
How to send comments about documentation and receive update
notifications ............................................................................................ 25
Index ............................................................................................................. 26
4
Deciding whether to use this guide
The OnCommand Cloud Manager Installation and User Guide for Volume Management describes
how to install and use Cloud Manager in the Volume View. This view provides an interface for users
who simply want to create volumes and do not want to manage storage systems, and are comfortable
with Cloud Manager making capacity allocation decisions.
The following image shows the Volume View in Cloud Manager:
If you want full control of Cloud ONTAP systems, you should install and use Cloud Manager in the
Storage System View:
For instructions, see the OnCommand Cloud Manager 2.2 Installation and Setup Guide for Storage
System Management and the OnCommand Cloud Manager 2.2 Storage System Management Guide.
5
Product overview
OnCommand Cloud Manager provides simplified management of cloud storage environments built
on NetApp. You can use Cloud Manager to manage data across your hybrid cloud, which includes
full control of Cloud ONTAP systems, or you can simply provision volumes and let Cloud Manager
handle the rest.
When you set up Cloud Manager, you can choose between two management views: the Storage
System View and the Volume View.
Storage System View
You can use Cloud Manager in this view to have full control of Cloud ONTAP systems:
•
Configure and launch Cloud ONTAP instances in Amazon Web Services (AWS)
•
Provision NFS and CIFS storage
•
Replicate data across a hybrid cloud environment: between on-premises Data ONTAP clusters,
Cloud ONTAP systems, and NetApp Private Storage for Cloud configurations
•
Manage Cloud ONTAP systems as needed, which includes capacity allocation decisions,
simplified upgrades, cost monitoring, and several other tasks
Volume View
The Volume View enables you to simply specify the NFS volume that you need and then Cloud
Manager handles the rest: it deploys Cloud ONTAP systems as needed and it automatically makes
capacity allocation decisions as volumes grow. This view gives you the benefits of enterprise-class
storage in the cloud with very little storage management.
Where to deploy Cloud Manager
Cloud Manager can run in AWS or in your network. Cloud Manager must run in the AWS GovCloud
(US) region if you want to launch Cloud ONTAP instances in AWS GovCloud (US).
Note: The Volume View is not supported in the AWS GovCloud (US) region.
The following image shows Cloud Manager running in AWS and managing a Cloud ONTAP system
and data replication to and from Data ONTAP clusters:
6 | OnCommand Cloud Manager 2.2 Installation and User Guide
How the Volume View works
The Volume View simplifies storage management: you specify the volume that you need and Cloud
Manager creates Cloud ONTAP systems and makes storage capacity decisions as volumes grow.
The following image shows how you interact with Cloud Manager in the Volume View:
1. You create volumes.
2. Cloud Manager launches Cloud ONTAP instances in AWS for new volumes or it creates volumes
on existing instances. It also purchases physical EBS storage for the volumes.
3. You make the volumes available to your hosts and applications.
4. Cloud Manager makes capacity allocation decisions as your volumes grow.
This means that you simply need to interact with volumes (the box on the left), while Cloud Manager
interacts with the storage system and its underlying storage (the box on the right).
Cloud Manager REST APIs
Cloud Manager includes REST APIs that enable software developers to automate the management of
NetApp storage in the cloud. There is an API for every action that is available from the user interface.
Cloud Manager provides interactive API documentation using the Swagger interface. A link to the
API documentation is available in the lower-right corner of the console:
If you need help getting started with the APIs, see the OnCommand Cloud Manager 2.2 API Getting
Started Guide.
7
Installation and volume management workflow
Before you can start creating volumes for your applications, you need to prepare your environment,
install Cloud Manager, and then set it up.
8
Preparing for installation and setup
Before you install and set up Cloud Manager, you must prepare your environment and understand the
information that you need for installation and setup.
Steps
1. Prepare your AWS environment on page 8
Your AWS environment must meet a few requirements so that Cloud Manager and Cloud ONTAP
operate correctly in AWS.
2. Review Cloud Manager requirements on page 10
You must verify support for your configuration, which includes host requirements, web browser
requirements, EC2 instance requirements, and so on. Most of this information is available in the
NetAppInteroperability Matrix; however, because you might not have a NetApp Support Site
login, a minimum amount of information is provided to get you started.
3. Gather information for installation and setup on page 11
You need to enter information about your environment when you install and set up Cloud
Manager. You can use a worksheet to collect the information that you need.
Preparing your AWS environment
Your AWS environment must meet a few requirements so that Cloud Manager and Cloud ONTAP
operate correctly in AWS.
Before you begin
You should be familiar with Virtual Private Clouds (VPCs) and subnets.
AWS Documentation: Your VPC and Subnets
Steps
1. Set up a VPC that includes one or more subnets that have outbound Internet access.
For a list of requirements and tips, see AWS networking requirements on page 9.
2. Grant the required permissions to IAM users so Cloud Manager can perform operations in AWS:
a. Download the IAM user policy from the following location:
NetApp OnCommand Cloud Manager: AWS IAM Policy
b. From the IAM console, attach the policy to an IAM user or group.
AWS Documentation: Managing IAM Policies
3. Depending on your storage needs, request an increase to default AWS limits.
By default, AWS limits accounts to 20 instances and 20 TB of EBS storage.
Amazon Web Services (AWS) Documentation: AWS Service Limits
Amazon Web Services (AWS): Amazon EC2 Service Limits Report Now Available
4. If you want to launch Cloud Manager in AWS, create an EC2 key pair, if you do not have one.
AWS Documentation: Amazon EC2 Key Pairs
5. Subscribe to Cloud ONTAP in AWS:
Preparing for installation and setup | 9
a. Go to the AWS Marketplace page for Cloud ONTAP:
AWS Marketplace: Cloud ONTAP for AWS
b. Review the terms, and then click Accept.
You cannot create volumes from Cloud Manager unless you subscribe to the Cloud ONTAP
software.
AWS networking requirements
You must set up your AWS networking so that Cloud Manager can create volumes.
Virtual Private Cloud (VPC) setup
The easiest way to set up your AWS networking is to choose one of the common VPC scenarios by
using the VPC wizard.
AWS Documentation: VPC Wizard Scenarios for Amazon VPC
Subnets and internet access
•
You can choose whether the subnets in your VPC are public or private, but they must allow
outbound Internet access to enable communication between Cloud Manager and AWS services, to
enable software upgrades, and to enable technical support from NetApp for your volumes.
You can enable Internet access by using an Internet gateway, NAT device, VPN, or proxy server.
AWS Documentation: Adding an Internet Gateway to Your VPC
AWS Documentation: NAT
•
Note the following about providing Internet access for NetApp AutoSupport, which is a
troubleshooting tool that proactively monitors the health of your storage:
◦
If you use a NAT instance, you must define an inbound security group rule that allows HTTPS
traffic from the private subnet to the Internet.
AWS Documentation: NAT Instances
◦
If you use a VPN, routing and firewall policies must allow AWS HTTP/HTTPS traffic to
support.netapp.com.
•
If you plan to install Cloud Manager in one subnet and create volumes in another subnet, then
there must be a route between those subnets.
•
If you install Cloud Manager in a private subnet, the web browser from which you access Cloud
Manager must have a connection to that AWS subnet.
Security groups
You do not need to create security groups because Cloud Manager does that for you.
Example setup
The following example shows Cloud Manager in a public subnet, volumes in a private subnet, an
Internet gateway that connects the VPC to the internet, and a NAT device that enables outbound
Internet traffic from the private subnet:
10 | OnCommand Cloud Manager 2.2 Installation and User Guide
Cloud Manager requirements
You must verify support for your configuration, which includes host requirements, web browser
requirements, EC2 instance requirements, and so on. Most of this information is available in the
NetApp Interoperability Matrix; however, because you might not have a NetApp Support Site login, a
minimum amount of information is provided to get you started.
If you have a NetApp Support Site login, go to the NetApp Interoperability Matrix Tool to search for
supported Cloud Manager configurations.
EC2 instance requirements
Cloud Manager is supported on the t2.medium and m3.medium instance types. Cloud Manager can
run on other EC2 instance types, but they are not supported.
Host requirements
To run Cloud Manager on an existing host, the physical or virtual machine must meet minimum
requirements:
Component
Requirement
Hypervisor
A bare metal or hosted hypervisor that is certified to run Red Hat
Enterprise Linux.
Red Hat Solution: Which hypervisors are certified to run Red Hat
Enterprise Linux?
Operating system
Red Hat Enterprise Linux 7.1 or 7.2
CPU
2.27 GHz or higher with two cores
RAM
4 GB
Free disk space
50 GB
Preparing for installation and setup | 11
Web browser requirements
You need to access the Cloud Manager console from a supported web browser:
Web browser
Minimum supported version
Google Chrome
45
Microsoft Edge
20
Microsoft Internet Explorer
11
Mozilla Firefox
40
For the full list of supported web browser versions, see the NetApp Interoperability Matrix Tool.
Port requirements
Before you install Cloud Manager on an existing host, you should verify that the following ports are
available. If other services are using these ports, Cloud Manager installation fails.
Port
Purpose
80
Provides HTTP access to the Cloud Manager web console.
443
Provides HTTPS access to the Cloud Manager web console.
3306
Used by a MySQL database that stores Cloud Manager data.
8080
Used by the Simplicator service, which is an API proxy for Cloud
Manager.
There is a potential conflict with port 3306. If another instance of MySQL is running on the host, it
uses port 3306 by default. You must change the port that the existing MySQL instance uses.
You can change the default HTTP and HTTPS ports when you install Cloud Manager. You cannot
change the default port for the MySQL database. If you change the HTTP and HTTPS ports, you
must ensure that users can access the Cloud Manager web console from a remote host:
•
•
In AWS, modify the instance's security group to allow inbound connections through the ports.
Specify the port when you enter the URL to the Cloud Manager web console.
Installation and setup worksheet
You need to enter information about your environment when you install and set up Cloud Manager.
You can use a worksheet to collect the information that you need.
Information needed to launch the Cloud Manager instance in AWS
Information
Instance type
Virtual Private Cloud
Subnet
EC2 key pair
Your value
12
Installing OnCommand Cloud Manager
You can install the Cloud Manager software by launching a Cloud Manager instance in Amazon Web
Services (AWS) or by installing Cloud Manager on an existing Linux host. The standard method is to
launch a Cloud Manager instance in AWS using the AMI.
Choices
• Launching a Cloud Manager instance in a standard AWS region on page 12
• Installing Cloud Manager on an existing Linux host on page 13
Launching a Cloud Manager instance in a standard AWS
region
You can use the Cloud Manager AMI from the AWS Marketplace to launch an EC2 instance in a
standard AWS region (a region other than the AWS GovCloud (US) region). This gives you access to
the Cloud Manager software, which is automatically installed on the instance.
Before you begin
•
You must have an EC2 key pair.
AWS uses the key pair to secure the instance's login information.
Amazon Web Services (AWS) Documentation: Amazon EC2 Key Pairs
•
If you want to assign a public IP address to the Cloud Manager instance and use the AWS 1-Click
Launch option, the public subnet must be already enabled to automatically assign public IP
addresses.
Amazon Web Services (AWS) Documentation: IP Addressing in Your VPC
Otherwise, you must use the Manual Launch option to assign a public IP address to the instance.
Steps
1. Go to the Cloud Manager page on the AWS Marketplace.
AWS Marketplace: OnCommand Cloud Manager
2. Keep the default delivery method (Single AMI), and then click Continue.
You should use the advanced delivery methods only when using Cloud Manager in the Storage
System View.
3. On the 1-Click Launch tab, specify the settings for the instance, and then click Accept Terms
and Launch with 1-Click.
Note the following when you choose settings for the Cloud Manager instance:
•
The t2.medium instance type is recommended.
•
Under security group, select Create new based on seller settings to create a pre-defined
security group that includes the rules required by Cloud Manager.
Result
AWS launches the software with the specified settings. The Cloud Manager instance and software
should be running in approximately five minutes.
Installing OnCommand Cloud Manager | 13
After you finish
Log in to Cloud Manager using a web browser and complete the Setup wizard.
Related tasks
Setting up OnCommand Cloud Manager on page 14
Installing Cloud Manager on an existing Linux host
You can install the Cloud Manager software on an existing Linux host in your network or in AWS.
This is an alternative to running Cloud Manager on a new AWS instance launched from the Cloud
Manager AMI.
About this task
Root privileges are not required to install Cloud Manager.
Steps
1. Download the software from the NetApp Support Site, and then copy it to the Linux host.
NetApp Downloads: Software
For help with connecting and copying the file to an EC2 instance in AWS, see AWS
Documentation: Connecting to Your Linux Instance Using SSH.
2. Assign permissions to execute the script.
Example
chmod +x OnCommandCloudManager-V2.2.0.sh
3. Run the installation script:
./OnCommandCloudManager-V2.2.0.sh [silent] [proxy=ipaddress]
[proxyport=port]
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.
4. 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:
•
•
In AWS, modify the instance's security group to allow inbound connections through the ports.
Specify the port when you enter the URL to the Cloud Manager web console.
After you finish
Log in to Cloud Manager using a web browser, and then complete the Setup wizard.
Related tasks
Setting up OnCommand Cloud Manager on page 14
14
Setting up OnCommand Cloud Manager
The Cloud Manager Setup wizard appears when you access the web console for the first time. The
wizard enables you to create a user account and your first volume.
About this task
If you recently launched a Cloud Manager instance in Amazon Web Services (AWS), the Cloud
Manager console should be available a few minutes after the AWS instance starts.
Steps
1. Open a web browser and enter the following URL:
https://ipaddress:port
You need to use this URL each time that you log in to Cloud Manager.
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 installed in AWS and
the instance does not have a public IP address, you must enter a private IP address from a host in
AWS 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
After you enter the URL, the Cloud Manager Setup wizard appears:
2. Click Volume View.
3. On the Create your user account page, specify details to create your user account, read and
approve the End User License Agreement, and then click Create.
Your user name is your email address. Cloud Manager does not send emails to this address.
4. On the Create your first volume page, specify details for your first volume, and then click
Create.
The following table describes fields for which you might need guidance:
Setting up OnCommand Cloud Manager | 15
Field
Description
Size
The maximum size for the initial volume is 17.2 TB.
Thin provisioning is automatically enabled on the volume, which enables
you to create a volume that is bigger than the physical storage currently
available to it. Instead of preallocating storage space, space is allocated to
each volume as data is written.
AWS Disk Type
General Purpose (SSD) disks are a good choice when performance is more
important than cost (the data is frequently accessed). Magnetic disks are a
good choice when cost is more important than performance (the data is
infrequently accessed). For details about EBS performance, see Amazon
Web Services (AWS) Documentation: EBS Volume Types.
In addition to cost and performance, you should take maximum storage
capacity into consideration. The EBS raw capacity limit is 368 TB for
General Purpose (SSD) disks and 46 TB for Magnetic disks.
Location
The default selections are the region, VPC, and subnet in which you
deployed Cloud Manager. The fields are blank if you deployed Cloud
Manager in your network. If you change the default, Cloud Manager must
have a connection to the location.
The following image shows the Create your first volume page filled out:
5. On the Storage System Password dialog box, specify the password that Cloud Manager should
set for each Cloud ONTAP system that it launches in AWS, and then click Save.
The password must be at least eight characters and must contain at least one English letter and
one number. The password cannot contain non-English letters or the user account name (admin).
You need to use this password if you want to access storage systems directly, or if NetApp
support personnel needs to help you recover your storage.
After you enter the password, Cloud Manager saves it and uses it for additional Cloud ONTAP
systems that it launches. If you ever need to change the password, you can update it through the
Storage System View.
Result
Cloud Manager is now set up and you can create additional volumes, as needed. The initial volume
should be ready in approximately 25 minutes because Cloud Manager must launch a Cloud ONTAP
instance in AWS.
After you finish
Register for support.
16 | OnCommand Cloud Manager 2.2 Installation and User Guide
Registering for support
You must enter your NetApp Support Site credentials in Cloud Manager before you can get help
from NetApp technical support. Entering your credentials registers the Cloud ONTAP systems that
host your volumes for support.
Steps
1. In the upper right of the Cloud Manager console, click the menu, and then select Support
Registration.
2. Enter your NetApp Support Site user name and password, and then click Register.
If you do not have a NetApp Support Site account, follow the link to create an account, and then
enter your credentials in Cloud Manager.
Result
All existing and future Cloud ONTAP systems that host your volumes are now registered for support.
17
Managing NFS volumes
You can create, mount, clone, delete, and manage access to NFS volumes using the Cloud Manager
user interface or by using the Cloud Manager APIs.
Related references
Cloud Manager REST APIs on page 6
Logging in to Cloud Manager
You can log in to Cloud Manager from any web browser that has a connection to the Cloud Manager
host.
Steps
1. 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 installed in AWS and
the instance does not have a public IP address, you must enter a private IP address from a host in
AWS 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
After you enter the URL, the Cloud Manager log in screen appears:
2. Enter your email address and password, and then click Log in.
18 | OnCommand Cloud Manager 2.2 Installation and User Guide
How Cloud Manager allocates cloud resources
Cloud Manager allocates cloud resources for you when you create volumes using the Volume View.
You should understand how Cloud Manager allocates resources to set cost expectations.
Allocation of cloud resources for the initial volume
When you create your first volume, Cloud Manager launches a Cloud ONTAP instance in AWS and
purchases EBS storage for the volume. Cloud Manager configures the EC2 instance as follows:
Option
Default setting
EC2 instance type
Depending on the size of the initial volume, Cloud Manager launches a
m4.xlarge instance or a m4.2xlarge instance.
EBS disk size
One to four 1 TB EBS disks are purchased for the initial volume. The
number of disks depends on the volume size.
Encryption
Amazon EBS encryption is enabled.
Allocation of cloud resources for additional volumes
When you create additional volumes, Cloud Manager determines whether it can create the volumes
on existing Cloud ONTAP instances or it needs to launch new Cloud ONTAP instances. Cloud
Manager can create a volume on an existing instance if the instance's AWS location and disk type
matches the requested volume and there is enough space.
If Cloud Manager creates a volume on an existing instance, it purchases the required EBS storage,
which can be 1 TB or larger disks, depending on the requested volume size.
If Cloud Manager creates a volume on a new instance, it purchases one to four 1 TB EBS disks, just
like it did for the initial volume.
NetApp storage efficiency features and storage costs
Cloud Manager automatically enables NetApp storage efficiency features on all volumes. These
efficiencies can reduce the total amount of storage that you need:
Thin provisioning
Presents more logical storage to hosts or users than you actually have in your physical
storage pool. Instead of preallocating storage space, storage space is allocated dynamically
to each volume as data is written.
Deduplication
Improves efficiency by locating identical blocks of data and replacing them with
references to a single shared block. This technique reduces storage capacity requirements
by eliminating redundant blocks of data that reside in the same volume.
Compression
Reduces the physical capacity required to store data by compressing data within a volume
on primary, secondary, and archive storage.
With these features enabled, you might see a difference between your allocated capacity and the
purchased AWS capacity, which can result in storage cost savings.
Capacity allocation decisions that Cloud Manager automatically handles
•
Cloud Manager purchases additional EBS disks as capacity thresholds are exceeded.
This happens as your volumes grow.
Managing NFS volumes | 19
•
Cloud Manager deletes unused sets of EBS disks if the disks contain no volumes for 12 hours.
•
Cloud Manager moves volumes between sets of disks to avoid capacity issues.
In some cases, this requires purchasing additional EBS disks. It also frees space on the original
set of disks for new and existing volumes.
Actions that require your approval
•
Cloud Manager prompts you for approval if it needs to upgrade to a Cloud ONTAP license that
supports a higher EBS raw capacity limit.
You are prompted because it requires a reboot, during which I/O is interrupted.
•
Cloud Manager prompts you to delete Cloud ONTAP instances that contain no volumes.
Related information
NetApp Storage Efficiency: Overview
How Cloud ONTAP licenses impact available capacity and
allocation of AWS resources
When you use Cloud Manager in the Volume View, it might prompt you to change an underlying
AWS resource to increase available capacity. That underlying AWS resource is a Cloud ONTAP
instance. You might want to know more about Cloud ONTAP licenses to understand how they impact
available capacity and allocation of AWS resources.
Cloud ONTAP is available in three pay-as-you-go configurations: Explore, Standard, and Premium.
When you use Cloud Manager in the Volume View, upgrading a Cloud ONTAP license affects the
EC2 instance type and EBS raw capacity limit:
License
EC2 instance type
EBS raw capacity limit
Explore
m4.xlarge
2 TB
Standard
m4.2xlarge
10 TB
Premium
r3.2xlarge
368 TB for General Purpose (SSD)
46 TB for Magnetic
When Cloud Manager launches a Cloud ONTAP system, it launches an Explore or Standard instance,
depending on the initial volume size. As the volumes in those instances grow, Cloud Manager might
prompt you to make an AWS instance change which means it needs to upgrade the instance's license
to Standard or Premium. Upgrading increases the EBS raw capacity limit, which allows your
volumes to grow.
Upgrading licenses also impacts the maximum size of the volumes that you can create. For example,
you can create a volume up to 34.3 TB for a Cloud ONTAP Standard instance or a 137.5 TB volume
for a Cloud ONTAP Premium instance.
Note: Cloud Manager does not launch Cloud ONTAP BYOL instances in the Volume View. You
should use Cloud Manager in the Storage System View if you purchased a Cloud ONTAP license.
20 | OnCommand Cloud Manager 2.2 Installation and User Guide
Creating NFS volumes
You can use Cloud Manager to create NFS volumes that provide enterprise-class features on top of
EBS storage.
Steps
1. In the Volumes tab, click Create New Volume.
2. Specify details for the volume, and then click Create.
The following table describes fields for which you might need guidance:
Field
Description
Size
The maximum size for the volume depends on the capacity available in
existing storage systems.
For details, see How Cloud Manager allocates cloud resources on page 18
and How Cloud ONTAP licenses impact available capacity and allocation
of AWS resources on page 19.
Thin provisioning is automatically enabled on the volume, which enables
you to create a volume that is bigger than the physical storage currently
available to it. Instead of preallocating storage space, space is allocated to
each volume as data is written.
AWS Disk Type
General Purpose (SSD) disks are a good choice when performance is more
important than cost (the data is frequently accessed). Magnetic disks are a
good choice when cost is more important than performance (the data is
infrequently accessed). For details about EBS performance, see Amazon
Web Services (AWS) Documentation: EBS Volume Types.
In addition to cost and performance, you should take maximum storage
capacity into consideration. The EBS raw capacity limit is 368 TB for
General Purpose (SSD) disks and 46 TB for Magnetic disks.
Location
The default selections are the region, VPC, and subnet in which you
deployed Cloud Manager. The fields are blank if you deployed Cloud
Manager in your network. If you change the default, Cloud Manager must
have a connection to the location.
Result
Cloud Manager creates the volume on an existing system or on a new system. If a new system is
required, creating the volume can take approximately 25 minutes.
After you finish
Mount the volume to hosts.
Mounting volumes to Linux hosts
After you create a volume, you should mount it to your hosts so that they can access the volume.
Steps
1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then
click Mount.
Managing NFS volumes | 21
2. Click Copy.
3. On your Linux hosts, modify the copied text by changing the destination directory, and then enter
the command to mount the volume.
Cloning volumes
If you need an instantaneous copy of your data without using a lot of disk space, you can create a
clone of an existing volume. The cloned volume is a writable, point-in-time copy that is spaceefficient because it uses a small amount of space for metadata, and then only consumes additional
space as data is changed or added.
Steps
1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then
click Clone.
2. Modify the name of the cloned volume, if needed, and then click Clone.
Result
Cloud Manager creates a new volume that is a clone of an existing volume.
Managing data access to volumes
When you create a volume, Cloud Manager makes the volume available to all EC2 instances in the
VPC in which the volume was created. You can modify this default value if you need to restrict data
access to the volume.
Steps
1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then
click Manage Access.
2. Modify the volume access list, and then click Save.
Deleting volumes
You can delete volumes that you no longer need.
Steps
1. In the Volumes tab, place your mouse cursor over the volume, select the menu icon, and then
click Delete.
2. Click Delete to confirm that you want to delete the volume.
22
Changing the management view
Cloud Manager provides two management views for its graphical interface: the Storage System View
for managing storage systems across a hybrid cloud and the Volume View for creating volumes
without having to manage storage systems. You can switch between these views, but those instances
should be rare because a single view should meet your needs.
Steps
1. In the upper right of the Cloud Manager console, click the menu, and then select View Selection.
2. On the View Selection page, select Storage System View, and then click Switch.
Result
Cloud Manager switches to the Storage System View. For help using this view, see the OnCommand
Cloud Manager 2.2 Storage System Management Guide.
Here are a few tips when using the Storage System View:
•
The volumes that you created are hosted by one or more Cloud ONTAP instances. The default
name for each instance includes the date and time that Cloud Manager created the instance (for
example, “COT_17_44_40_Mar_17_16”).
•
It is possible to create additional user accounts in the Storage System View. However, only a user
account with the Cloud Manager Admin role can access the Volume View.
23
Copyright information
Copyright © 1994–2016 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
24
Trademark information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express,
Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash
Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale,
FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster,
MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,
SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive,
SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,
Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL and
other names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or
other countries. All other brands or products are trademarks or registered trademarks of their
respective holders and should be treated as such. A current list of NetApp trademarks is available on
the web at http://www.netapp.com/us/legal/netapptmlist.aspx.
25
How to send comments about documentation and
receive update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can
receive automatic notification when production-level (GA/FCS) documentation is initially released or
important changes are made to existing production-level documents.
If you have suggestions for improving this document, send us your comments by email to
[email protected]. To help us direct your comments to the correct division, include in the
subject line the product name, version, and operating system.
If you want to be notified automatically when production-level documentation is released or
important changes are made to existing production-level documents, follow Twitter account
@NetAppDoc.
You can also contact us in the following ways:
•
NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
•
Telephone: +1 (408) 822-6000
•
Fax: +1 (408) 822-4501
•
Support telephone: +1 (888) 463-8277
26 | OnCommand Cloud Manager 2.2 Installation and User Guide
Index
A
F
about this guide
deciding whether to use 4
access, volumes
managing 21
Amazon Web Services
considerations for choosing disk types 20
how Cloud Manager allocates resources in 18
launching Cloud Manager in standard region 12
networking requirements for Cloud Manager 9
preparing your environment 8
APIs
overview of 6
audience
for this guide 4
AWS
See Amazon Web Services
feedback
how to send comments about documentation 25
Firefox
supported versions 10
G
General Purpose (SSD) disks
what they are 20
H
hosts, Linuxinstalling OnCommand Cloud Manager on
existing 13
I
C
Chrome
supported versions 10
clones, volume
creating 21
Cloud Manager
See OnCommand Cloud Manager
Cloud ONTAP
licenses 19
registering for support 16
comments
how to send feedback about documentation 25
console
logging in to Cloud Manager 17
CPU
required for Cloud Manager 10
D
data access, volumes
managing 21
disk space
required for Cloud Manager 10
disk types
considerations for choosing 20
documentation
how to receive automatic notification of changes to
25
how to send feedback about 25
information
how to send feedback about improving
documentation 25
installation
gathering information for 11
preparing for OnCommand Cloud Manager 8
worksheets 11
installing OnCommand Cloud Manager
on existing Linux hosts 13
workflow 7
Internet Explorer
supported versions 10
L
licenses
Cloud ONTAP 19
Linux hostsinstalling OnCommand Cloud Manager on
existing 13
logging in
to Cloud Manager 17
M
Magnetic disks
what they are 20
management views
changing 22
N
E
EBS storage
raw capacity limit 19
EC2 instance types
per Cloud ONTAP license 19
NFS volumes
creating 20
O
OnCommand Cloud Manager
AWS networking requirements for 9
Index | 27
EC2 instance requirements 10
host requirements 10
how it allocates resources 18
how the Volume View works 6
information needed to launch in AWS 11
installation and volume management workflow 7
installing on an existing Linux host 13
launching in AWS 12
logging in 17
preparing for installation and setup 8
setting up 14
supported web browsers 10
what it is 5
operating system
required for Cloud Manager 10
R
RAM
required for Cloud Manager 10
requirements
OnCommand Cloud Manager 10
S
security groups
requirements for Cloud Manager 9
setup
preparing for OnCommand Cloud Manager 8
workflow 7
Storage System View
switching to 22
subnets
requirements for Cloud Manager 9
suggestions
how to send feedback about documentation 25
support
registering for 16
T
Twitter
how to receive automatic notification of
documentation changes 25
V
views, management
switching between 22
Virtual Private Clouds
requirements for Cloud Manager 9
volume management
workflow 7
volume size
considerations for specifying 20
Volume View
how it works 6
switching to 22
volumes
cloning 21
deleting 21
license impact on maximum size 19
managing data access 21
mounting 20
volumes, NFS
creating 20
W
web browsers
supported versions 10
worksheets
installation and setup 11