Difference between revisions of "IBM Cloud Provisioning Guide"

From OSNEXUS Online Documentation Site
Jump to: navigation, search
(Created page with " == 4/4/19 Under Construction ==")
 
m (→‎4/4/19 Under Construction)
Line 1: Line 1:
  
 
== 4/4/19 Under Construction ==
 
== 4/4/19 Under Construction ==
 +
 +
# IBM Cloud + QuantaStor SDS Appliance Provisioning Guide
 +
 +
The QuantaStor Configuration Guide describes the steps needed to configure QuantaStor SDS for deployments in the IBM Cloud/SoftLayer environment. In addition, it provides links to information on popular QuantaStor SDS configurations for a range of SDS use cases. Complete technical documentation for QuantaStor can be found on the OSNEXUS [wiki](https://wiki.osnexus.com/index.php?title=OSNEXUS_Online_Documentation_Site). Reference Configurations for High-Performance All-Flash SAN/NAS Appliances, High-Capacity Hybrid SAN/NAS Appliances, High-Capacity Scale-out Object or Scale-out NAS Appliances and QuantaStor Grids for Scale-out S3/SWIFT Object Storage can be found [here](https://www.osnexus.com/ibm-cloud-softlayer-quantastor-sds-refererence-configurations).
 +
 +
**Provisioning Guide**:
 +
 +
[TOC]
 +
 +
**For an overview of common configurations, please see the [IBM Cloud + QuantaStor SDS Reference Configuration Guide](https://www.osnexus.com/ibmcloud-refconfig-guide).**
 +
 +
---
 +
 +
## Selecting a QuantaStor Appliance Server Chassis
 +
 +
### Choosing Server Chassis
 +
 +
The best chassis options for QuantaStor use are the 8, 12 and 36-bay models, with the 36-bay recommended in most scenarios 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 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
 +
 +
#### When choosing RAM quantity, remember these guidelines for any mixed or read-heavy workloads:
 +
 +
* If deploying Ceph on this node, add 1 GB of RAM per physical disk (Ceph OSD)
 +
* If deploying a ZFS pool on this node, add 1 GB of RAM per TB of capacity
 +
* If deploying both, add the recommendations of both together
 +
* While there is no maximum RAM limit, and ZFS will use any free RAM it is offered for its read cache, with a maximum of 36 drives the likely point of greatly diminishing returns is somewhere between 128 and 384 GB of RAM, dependant on use-case(s).
 +
 +
If the workload is entirely writes (such as serving solely as a backup target, with only infrequent recovery operations and no reads/seeks during normal backup operations), and thus no expectation of any useful cache being built up (or any other use-case of similar expectation), the minimum recommended RAM is the greater of 16 GB -or- 1 GB per disk.
 +
 +
#### When choosing CPU, remember these guidelines for any mixed or read-heavy workloads:
 +
 +
* The most common low-, mid- and high-end processor choices chosen for QuantaStor are all dual-processor configurations of the: ????, ????, ???? ( TODO )
 +
* If deploying Ceph, try to achieve as close to or greater than 1:1 ratio of cores to disks as possible, with a floor of at least 500 MHz per disk
 +
* Both Ceph and ZFS benefit from higher clock speeds and greater core counts, though 8 & 12-bay chassis only need a higher-end processor if also deploying an all-flash configuration
 +
* If this will be an all-flash node, but also for all latency-sensitive, high performance use-cases, opt for and focus on the highest clock speed available within budget
 +
* QuantaStor does not recommend the use of quad processor configurations in any environment
 +
 +
If the workload is not performance sensitive, the minimum recommended processor is the ????? ( TODO )
 +
 +
## Selecting a 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 intended 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 clients. If the clients are other IBM SoftLayer servers, put the QuantaStor in the same location as the majority of them. If the clients are across the internet, put the QuantaStor in the nearest datacenter 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
 +
 +
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
 +
* Does not count hot-spares
 +
* Does not count boot devices
 +
* Does not count unused/unallocated devices (cold spares)
 +
 +
Simply sum up all capacity for every data, journal and cache disk and choose the nearest license capacity available that is above that number.
 +
 +
## Select and Configure the 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.
 +
 +
## Selecting the 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!
 +
 +
## Login to Server
 +
 +
Once deployment has been completed you should get a notification from IBM SoftLayer. 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 SoftLayer backend network. If your location is blocking default web ports, you can also try browsing to any IP on port ???? (TODO), the QuantaStor web interface is also listening on that port for this reason.
 +
 +
**You can find additional information on QuantaStor setup in the [Getting Started Overview](https://wiki.osnexus.com/index.php?title=%2BOverview(Getting_Started)), as well as the [Administrator's Guide](https://wiki.osnexus.com/index.php?title=%2B_Admin_Guide_Overview).**

Revision as of 10:30, 16 April 2019

4/4/19 Under Construction

  1. IBM Cloud + QuantaStor SDS Appliance Provisioning Guide

The QuantaStor Configuration Guide describes the steps needed to configure QuantaStor SDS for deployments in the IBM Cloud/SoftLayer environment. In addition, it provides links to information on popular QuantaStor SDS configurations for a range of SDS use cases. Complete technical documentation for QuantaStor can be found on the OSNEXUS [wiki](https://wiki.osnexus.com/index.php?title=OSNEXUS_Online_Documentation_Site). Reference Configurations for High-Performance All-Flash SAN/NAS Appliances, High-Capacity Hybrid SAN/NAS Appliances, High-Capacity Scale-out Object or Scale-out NAS Appliances and QuantaStor Grids for Scale-out S3/SWIFT Object Storage can be found [here](https://www.osnexus.com/ibm-cloud-softlayer-quantastor-sds-refererence-configurations).

    • Provisioning Guide**:

[TOC]

---

    1. Selecting a QuantaStor Appliance Server Chassis
      1. Choosing Server Chassis

The best chassis options for QuantaStor use are the 8, 12 and 36-bay models, with the 36-bay recommended in most scenarios 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 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
        1. When choosing RAM quantity, remember these guidelines for any mixed or read-heavy workloads:
  • If deploying Ceph on this node, add 1 GB of RAM per physical disk (Ceph OSD)
  • If deploying a ZFS pool on this node, add 1 GB of RAM per TB of capacity
  • If deploying both, add the recommendations of both together
  • While there is no maximum RAM limit, and ZFS will use any free RAM it is offered for its read cache, with a maximum of 36 drives the likely point of greatly diminishing returns is somewhere between 128 and 384 GB of RAM, dependant on use-case(s).

If the workload is entirely writes (such as serving solely as a backup target, with only infrequent recovery operations and no reads/seeks during normal backup operations), and thus no expectation of any useful cache being built up (or any other use-case of similar expectation), the minimum recommended RAM is the greater of 16 GB -or- 1 GB per disk.

        1. When choosing CPU, remember these guidelines for any mixed or read-heavy workloads:
  • The most common low-, mid- and high-end processor choices chosen for QuantaStor are all dual-processor configurations of the: ????, ????, ???? ( TODO )
  • If deploying Ceph, try to achieve as close to or greater than 1:1 ratio of cores to disks as possible, with a floor of at least 500 MHz per disk
  • Both Ceph and ZFS benefit from higher clock speeds and greater core counts, though 8 & 12-bay chassis only need a higher-end processor if also deploying an all-flash configuration
  • If this will be an all-flash node, but also for all latency-sensitive, high performance use-cases, opt for and focus on the highest clock speed available within budget
  • QuantaStor does not recommend the use of quad processor configurations in any environment

If the workload is not performance sensitive, the minimum recommended processor is the ????? ( TODO )

    1. Selecting a 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 intended 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 clients. If the clients are other IBM SoftLayer servers, put the QuantaStor in the same location as the majority of them. If the clients are across the internet, put the QuantaStor in the nearest datacenter 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.

    1. Sizing the License

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
  • Does not count hot-spares
  • Does not count boot devices
  • Does not count unused/unallocated devices (cold spares)

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

    1. Select and Configure the Boot System Drives
      1. 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
      1. 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.

    1. Selecting the 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.

    1. 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!

    1. Login to Server

Once deployment has been completed you should get a notification from IBM SoftLayer. 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 SoftLayer backend network. If your location is blocking default web ports, you can also try browsing to any IP on port ???? (TODO), the QuantaStor web interface is also listening on that port for this reason.

Retrieved from "https://wiki.osnexus.com/index.php?title=IBM_Cloud_Provisioning_Guide&oldid=12541"