Configuring a public network

While Ceph functions well with only a public network, you can establish more specific criteria, including multiple IP networks, for your public network.

Before you begin

Before you begin, make sure that you have the IBM Storage Ceph software installed.

About this task

To configure Ceph networks, use the config set command within the cephadm shell.
Note: The IP addresses you set in your network configuration are different from the public-facing IP addresses that network clients might use to access your service.

Ceph can work with only a public network. You can also establish more specific criteria, including multiple IP networks for your public network.

You can also establish a separate, private cluster network to handle OSD heartbeat, object replication, and recovery traffic. For more information about the private network, see Configuring a private network.
Note:
  • Ceph uses CIDR notation for subnets, for example, 10.0.0.0/24. Typical internal IP networks are often 192.168.0.0/24 or 10.0.0.0/24.
  • If you specify more than one IP address for either the public or the cluster network, the subnets within the network must be capable of routing to each other. Make sure that you include each IP address in your IP tables, and open ports for them as necessary.

Using the public network configuration allows you to specifically define IP addresses and subnets for the public network.

For common option descriptions and usage information, see Network configuration options.

Procedure

  1. Log in to the cephadm shell.
    For example,
    [root@host01 ~]# cephadm shell
  2. Configure the public network with the subnet.
    ceph config set global public_network IP_ADDRESS_WITH_SUBNET
    For example,
    [ceph: root@host01 /]# ceph config set global public_network 192.168.0.0/24
  3. Get the list of services in the storage cluster, by using the ceph orch ls command.
    For example,
    [ceph: root@host01 /]# ceph orch ls
  4. Restart the daemons.
    Ceph daemons bind dynamically. As a result, the entire cluster does not need to be restarted if the network configuration was changed for a specific daemon.
    ceph orch restart mon
    For example,
    [ceph: root@host01 /]# ceph orch restart mon
  5. Optional: To restart the cluster, from the admin node as a root user run the systemctl command.
    systemctl restart ceph-FSID_OF_CLUSTER.target
    For example,
    [root@host01 ~]# systemctl restart ceph-1ca9f6a8-d036-11ec-8263-fa163ee967ad.target