From: Piviul <piviul@riminilug.it>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] ceph
Date: Wed, 11 Jan 2023 12:19:48 +0100 [thread overview]
Message-ID: <fba47757-10d5-bb80-9c66-a3dab12d1520@riminilug.it> (raw)
In-Reply-To: <mailman.232.1673430028.458.pve-user@lists.proxmox.com>
On 1/11/23 10:39, Eneko Lacunza via pve-user wrote:
> You should change your public_network to 192.168.255.0/24 .
So the public_network is the pve communication network? I can edit
directly the /etc/pve/ceph.conf and then corosync should change the
ceph.conf on the others nodes?
>
> Then, one by one, remove a monitor and recreate it, check values for
> new monitor are on correct network.
>
> Finally restart one by one OSD services and check their listening IPs
> (they listen on public and private Ceph networks).
the osd services in each proxmox node?
Piviul
next prev parent reply other threads:[~2023-01-11 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 9:14 Piviul
[not found] ` <mailman.191.1673258105.458.pve-user@lists.proxmox.com>
2023-01-09 11:47 ` Piviul
[not found] ` <mailman.203.1673265308.458.pve-user@lists.proxmox.com>
2023-01-10 7:23 ` Piviul
[not found] ` <mailman.215.1673337884.458.pve-user@lists.proxmox.com>
2023-01-10 13:29 ` Piviul
[not found] ` <mailman.232.1673430028.458.pve-user@lists.proxmox.com>
2023-01-11 11:19 ` Piviul [this message]
[not found] ` <mailman.235.1673444838.458.pve-user@lists.proxmox.com>
2023-01-11 15:51 ` Piviul
-- strict thread matches above, loose matches on Subject: below --
2021-09-08 12:46 Leandro Roggerone
2021-09-08 12:55 ` Gilberto Ferreira
2021-09-08 20:07 ` Alex K
2021-09-08 22:11 ` ic
2021-09-13 11:32 ` Leandro Roggerone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fba47757-10d5-bb80-9c66-a3dab12d1520@riminilug.it \
--to=piviul@riminilug.it \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.