Setting up On-Premises Location with NetApp ONTAP-SAN storage

Prepare an on-premises Satellite location for IBM Cloud Databases

ibmcloud sat storage templates | grep "NetApp Ontap"

Grant a service authorization

Begin by configuring IAM Authorizations:

• Configure your IAM Authorizations under the Manage tab.
• Choose the Authorizations tab from the left menu.
• Click create to allow a service instance access to another service instance.
  • The source service is the service that is granted access to the target service. The roles that you select define the level of access for this service. The target service is the service that you are granting permission to be accessed by the source service based on the assigned roles.
  • In the Source Service field, select Databases for < DATABASE TYPE >.
  • In the Target Service field, select Satellite.
  • Select all options:
    • Satellite Cluster Creator
    • Satellite Link Administrator
    • Satellite Link Source Access Controller
  • Then, Authorize.

Ensure location readiness

Your location needs to report Normal before you provision your ICD Satellite Deployment. This status can be confirmed in the UI, as shown here:

Normal status can also be confirmed by using the CLI, with a command like:

ibmcloud sat location get --location <location name> --output=json -q | jq -r .state

If successful, the command output reports normal.

Obtaining Normal state

To get to this state, attach a minimum of three 4x16 hosts to your location and assign them to the Control plane. After that step is complete, provisioning of the Control plane will begin. Upon successful completion, the location state is going to report as Normal

Attempting to provision a database instance into a location without a running Control plane (that is, Normal state), causes a provisioning to fail.

Provisioning ICD Satellite Deployment

You can provision your ICD Satellite Deployment by selecting the Satellite location that you create in the Location menu of the provisioning page. For more information, see the relevant Provisioning documentation. After you create a new service instance, this instance will appear in the IBM Cloud Resource List as Provisioned.

When you deploy the first database service instance, a service cluster deploys automatically into your Satellite location. The deployment of the service cluster can take up to 1 hour.

You can verify in the IBM Cloud UI whether the service cluster is already created:

• From the left Navigation menu, select Satellite, then Locations.
• Select your Satellite location.
• Select Services

You must create a storage assignment manually (see next step) before the database instance will be started. Subsequent database service instances provision more quickly since instances land on the same service cluster.

Create a Storage Assignment

The next step is to create a Satellite storage assignment that allows the service cluster to create volumes on the previously configured storage.

The first database you provision into a location remains "Provision In Progress" until this step is complete.

First, obtain your ROKS-Service-cluster-ID by entering the following command into the IBM Cloud CLI:

ic sat service ls  --location <location name/location id>

The output of the command includes the Cluster ID of the newly created Satellite service cluster.

Use the Cluster ID as an input parameter for --service-cluster-id in the following AWS Satellite location storage assignment commands:

ibmcloud sat storage assignment create 
	--name ${OPERATORASSIGNMENTNAME} 
	--service-cluster-id ${SERVICECLUSTERID} 
	--config ${OPERATORCONFIGNAME} 

ibmcloud sat storage assignment create 
	--name ${SANASSIGNMENTNAME} 
	--service-cluster-id ${SERVICECLUSTERID} 
	--config ${SANCONFIGNAME}

After you create the storage assignment, allow up to 30 minutes for the database instance to be ready for usage.