2024-06-12T13:30:45.100Z | <Raghu> ```ceph orch daemon add host1:10.99.88.77
Error EINVAL: host address is empty``` |
2024-06-12T13:31:02.049Z | <Raghu> ```ceph orch daemon add mon host1:10.99.88.77
Error EINVAL: host address is empty``` |
2024-06-12T13:32:33.247Z | <Raghu> ```ceph orch daemon add mon host1:10.99.88.77
Error EINVAL: host address is empty```
This is why i was using the other command to add the node in to the cluster. |
2024-06-12T13:35:24.989Z | <Raghu> ```ceph orch daemon add mon host1:10.99.88.77
Error EINVAL: host address is empty
ceph orch daemon add mon host1:10.99.0.0/16
Error EINVAL: host address is empty```
This is why i was using the other command to add the node in to the cluster.
Same is the case if we use the network as well |
2024-06-12T14:50:02.584Z | <Adam King> can I see what `ceph orch host ls` gives you on this cluster? |
2024-06-12T14:57:14.622Z | <Raghu> ```sudo ceph orch ls
NAME PORTS RUNNING REFRESHED AGE PLACEMENT
crash 1/1 8m ago 90m *
mgr 1/2 8m ago 90m count:2
mon 1/5 8m ago 87m <unmanaged>``` |
2024-06-12T14:58:09.053Z | <Adam King> `ceph orch **host** ls` |
2024-06-12T14:58:50.750Z | <Raghu> ```sudo ceph orch host ls
HOST ADDR LABELS STATUS
host0 10.99.88.76 _admin``` |
2024-06-12T14:59:02.380Z | <Raghu> ```sudo ceph orch host ls
HOST ADDR LABELS STATUS
host0 10.99.88.76 _admin``` |
2024-06-12T15:00:56.675Z | <Adam King> okay, so there is no host named `host1` added to the cluster yet. That's why it's failing trying to put the mon down |
2024-06-12T15:01:13.417Z | <Adam King> you need to do `ceph orch host add host1 <addr>` |
2024-06-12T15:02:42.067Z | <Raghu> i can add the daemon now |
2024-06-12T15:02:55.454Z | <Raghu> how can do this for an OSD node |
2024-06-12T15:03:07.222Z | <Raghu> how can do this for an OSD node, can i follow the same process there as well |
2024-06-12T15:05:42.214Z | <Adam King> adding hosts themselves is always the same. There is a `ceph orch daemon add osd...` (second and third example line in <https://docs.ceph.com/en/latest/cephadm/services/osd/#creating-new-osds> ) command but it takes the path to a device rather than a network (OSDs will bind automatically to whatever the `cluster_network` is set to be). I usually recommend using an actual spec to create OSDs though. There are a lot of filter options for specifying what disks to place OSDs on that are documented within <https://docs.ceph.com/en/latest/cephadm/services/osd/#advanced-osd-service-specifications> |