On 1/22/20 7:39 PM, Alexandre DERUMIER wrote: > Hi, > > I'm currently doing a training week, > > and we have notice that ceph wizard on initial deployment, > > for public_network && cluster_network set ip address instead network adress. > > > Like: 10.3.95.101/24 (the ip of the server), instead 10.3.95.0/24 (the > network address) > > > It don't seem to be a problem for ceph, but I don't think it's really good
no it isn't that good, makes also issues when editing settings on another node, as that one then shows the local CIDR again, and marks the UI form as invalid.. E.g., edit the "migration network" when connected to two different nodes. I have some work calculating the network from CIDR in javascript, but it's pretty ugly - at least for IPv6. So I thought of passing back the network the IP is in from our API network call, or add a new API get call just for available networks, which would make this way easier to integrate correctly in webinterface. What do you think? > > > https://docs.ceph.com/docs/mimic/rados/configuration/network-config-ref/ > PUBLIC NETWORK > The public network configuration allows you specifically define IP addresses > and subnets for the public network. You may specifically assign static IP > addresses or override public network settings using the public addr setting > for a specific daemon. > > public network > > Description > The IP address and netmask of the public (front-side) network (e.g., > 192.168.0.0/24). Set in [global]. You may specify comma-delimited subnets. > > Type > {ip-address}/{netmask} [, {ip-address}/{netmask}] > > Required > No > > Default > N/A _______________________________________________ pve-devel mailing list pve-devel@pve.proxmox.com https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
