Performing a disconnected installation

Before you can perform the air-gapped environment installation, you must obtain An IBM Storage Ceph container image, either from a proxy host that has access to the IBM registry or by copying the image to your local registry.

Before you begin

Before you begin, make sure that you have the following prerequisites in place:

About this task

Important: Before you begin the bootstrapping process, make sure that the container image that you want to use has the same version of IBM Storage Ceph as cephadm. If the two versions do not match, bootstrapping fails at the Creating initial admin user stage.
Important: Call Home is enabled by default when the license is accepted, including in disconnected environments. If your environment does not allow sending system information externally, you can disable Call Home after installation.

For more information about Call Home and disabling after installation, see Call Home.

Note: If your local registry uses a self-signed certificate with a local registry, ensure you have added the trusted root certificate to the bootstrap host. For more information, see Configuring a private registry for a disconnected installation.

Procedure

  1. Log in to the bootstrap host.
  2. Bootstrap the storage cluster. 
    cephadm --image PRIVATE_REGISTRY_NODE_FQDN:5000/CUSTOM_IMAGE_NAME:IMAGE_TAG bootstrap --mon-ip IP_ADDRESS --registry-url PRIVATE_REGISTRY_NODE_FQDN:5000 --registry-username PRIVATE_REGISTRY_USERNAME --registry-password PRIVATE_REGISTRY_PASSWORD
    • Replace PRIVATE_REGISTRY_NODE_FQDN with the fully qualified domain name of your private registry.
    • Replace CUSTOM_IMAGE_NAME and IMAGE_TAG with the name and tag of the IBM Storage Ceph container image that resides in the private registry.
    • Replace IP_ADDRESS with the IP address of the node you are using to run cephadm bootstrap.
    • Replace PRIVATE_REGISTRY_USERNAME with the username to create for the private registry.
    • Replace PRIVATE_REGISTRY_PASSWORD with the password to create for the private registry username.
    For example, 
    [root@host01 ~]# cephadm --image admin.lab.ibm.com:5000/ibm-ceph/ceph-9-rhel9:latest bootstrap --mon-ip 10.10.128.68 --registry-url admin.lab.ibm.com:5000 --registry-username myregistryusername --registry-password myregistrypassword1
    The script takes a few minutes to complete. Once the script completes, it provides the credentials to the IBM Storage Ceph Dashboard URL, a command to access the Ceph command-line interface (CLI), and a request to enable telemetry. 
    Ceph Dashboard is now available at:

             URL: https://host01:8443/
            User: admin
        Password: i8nhu7zham

Enabling client.admin keyring and conf on hosts with "admin" label
You can access the Ceph CLI with:

        sudo /usr/sbin/cephadm shell --fsid 266ee7a8-2a05-11eb-b846-5254002d4916 -c /etc/ceph/ceph.conf -k /etc/ceph/ceph.client.admin.keyring

Please consider enabling telemetry to help improve Ceph:

        ceph telemetry on

For more information see:

        https://docs.ceph.com/docs/master/mgr/telemetry/

Bootstrap complete.

What to do next

Use Ceph Orchestrator commands to clear the health warning emitted by Call Home.
  • Clear the health warning and allow the module to remain active. 
    ceph orch accept call-home-enabled
  • Clear the health warning and turn off the Call Home module. 
    ceph orch deny call-home-enabled
Automatic service events are not enabled automatically. To enable service events, see Enabling service events.

After the bootstrap process is complete, configure the container images, as detailed in Changing configurations of custom container images for disconnected installations.

Once your storage cluster is up and running, configure additional daemons and services. For more information, see Operations.