Difference between revisions of "IBM Cloud Provisioning Guide"

Revision as of 15:35, 9 May 2019

Overview

The Provisioning Guide walks through the process of selecting hardware for your QuantaStor system using IBM Cloud's Bare Metal online ordering tools. Reference Configurations for SAN/NAS Appliances, Scale-out Object and Scale-out Block appliances or Scale-out NAS Appliances can be found [here](https://www.osnexus.com/ibm-cloud-softlayer-quantastor-sds-refererence-configurations.

Complete technical documentation for QuantaStor can be found here[wiki](https://wiki.osnexus.com/index.php?title=OSNEXUS_Online_Documentation_Site).

Selecting a QuantaStor Server Chassis

The provisioning your QuantaStor solution begins with the selection of a Bare Metal server chassis suitable for your workload. Follow these steps to navigate to the QuantaStor-compatible server chassis in IBM Cloud:

1. In your web browser, navigate to https://www.ibm.com/cloud/bare-metal-servers and click on "Customize your server"
2. Chose the option for "All servers"
3. Chose the options for "Dual processor" models and sort (descending order) by the menu option for "Storage".

The best chassis options for QuantaStor use are the 12-bay and 36-bay server models. The 36-bay is recommended due to its greater configuration flexibility, cost-effectiveness, and maximum storage capacity. In general the 8 and 12-bay chassis should only be chosen for small-scale or all-SSD/NVMe high-performance use-cases, while the 36-bay is usually the optimal choice, as you can order it less than fully populated and have the ability add disks later.

When selecting the correct server chassis for a deployment, follow these general guidelines:

• If the number of storage (not OS, not hot-spare) drives needed is > 10 you'll need to use the 36-bay chassis
• If the usable storage capacity required is > 48 TB or expected to grow beyond that, use the 36-bay chassis
• If the deployment is a scale-out Ceph configuration using spinning disks, use the 36-bay chassis
• If using ZFS and any significant expansion in storage capacity needs is expected within the first 12 months of deployment, go with the 36-bay chassis
• If storage expansion is an "unknown", go with the 36-bay chassis!
• If the storage configuration is all-SSD or NVMe, an 8-bay or 12-bay chassis may provide better performance for your clients
• If the maximum expected capacity is under 48 TB, the 8 or 12-bay chassis should suffice

Selecting RAM Quantity for Mixed or Read-heavy Workloads

Use the solution design tools provided here on the OSNEXUS web site as the tools will automatically select the optimal amount of RAM for your use case.

• For most workloads the ideal ratio of RAM to usable capacity is 1GB RAM per 1TB of storage. Backup & Archive use cases require less at 300MB-500MB per 1TB.
• While there is no maximum RAM limit, extra RAM is used as a read cache which can greatly benefit many workloads.

Selecting a CPU for Mixed or Read-heavy Workloads

Use the solution design tools provided here as this will select the optimal CPU automatically for you.

• Scale-out configurations generally require 1GHz core per storage device. A system with 30 disks will require about double the CPU power of a system with 12 disks.
• Systems benefit from higher clock speeds and greater core counts, especially all-flash configurations.
• Systems with encryption enabled will benefit from the selection of a faster CPU. Typical performance degradation from encryption enabled is 10 to 20%.

Selecting an IBM Cloud Datacenter

Be sure to select the correct datacenter for your intended use-case, and then verify your desired server option is available there. Unless your use-case is similar to a DR/remote-replication/backup destination, it is most likely you will want to deploy the QuantaStor server in the same location as the most performance-demanding of your application servers. If the application servers are other IBM Cloud / SoftLayer servers, put the QuantaStor in the same location as the majority of them. If the application servers are in a remote site(S), put the QuantaStor in the nearest data-center to their geographic location. Network latency is a key factor in storage performance on nearly any protocol and intended use-case, thus geographic proximity is important.

Sizing the License

Use the solution design tools provided here as this will select the optimal license for you.

Be sure to choose a QuantaStor license of sufficient size to prevent problems during configuration. QuantaStor licenses are:

• Based on the amount of raw storage, not usable
• Count only disks actively used to hold data, this excludes hot-spares, cold-spares and boot devices

Simply sum up all capacity for every data, journal and cache disk and choose the nearest license capacity available that is above that number.

Selecting and Configuring Boot System Drives

Create the OS RAID1 Array

• Step 1. Select "RAID1" under Type

• Step 2. Enter the quantity 2 under # Disks

• Step 3. Select SATA under Disk Media

• Step 4. Select 1 TB under Disk Size

Add Storage disks

• Step 5. Click on Add New +

• Step 6. Select JBOD under Type

• Step 7. Enter the quantity under # Disks

• Step 8. Select your desired Disk Media (QuantaStor supports all available IBM SoftLayer disk options)

• Step 9. Select your desired Disk Size

• Step 10. Repeat steps 5 through 9 as many times as necessary for each individual media/size you require, do not forget any read and write cache devices!

QuantaStor manages all production data storage devices and RAID/erasure-coding itself, only the first entry for the OS disks should say RAID1, all entries past that should be set to JBOD or Individual.

Network Configuration

While QuantaStor does support all IBM SoftLayer options for network configuration, in most use-cases where all or the bulk of client throughput will come from your other servers and VM's at IBM SoftLayer, OSNEXUS recommends opting for the *Private Network Only* set of choices in order to double up the available back-end bandwidth. Unless constant, low-latency accessibility to the storage via the whole public internet is a requirement, OSNEXUS' recommends *Private Network Only* still be used even when irregular internet access is required, and another server or VM be deployed (or turned online only as necessary) to provide gateway/VPN/intermediary access to the storage.

IBM Cloud/SoftLayer maintains an internal upgrade software repository accessible via their private network for all QuantaStor customers, which will be automatically pre-configured. You do not require a public network connection to receive software updates in IBM Cloud/SoftLayer.

Complete QuantaStor Server Configuration

You mean run into a situation where the Checkout button is not visible, in such cases, try scrolling horizontally to the right.

Server Login

Once deployment has been completed you should get a notification from IBM. Check your account for login credentials and IP information. The QuantaStor Web UI should be listening on every initially provisioned IP address, if you do not get the login prompt in your browser, verify you have VPN connectivity to your IBM Cloud backend network. You can find additional information on QuantaStor setup in the Getting Started Overview, as well as the Administrator's Guide