From: Fabian Ebner <f.ebner@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [RFC manager] fix #2422: allow multiple Ceph public networks
Date: Fri, 7 May 2021 10:04:44 +0200 [thread overview]
Message-ID: <4412e72e-a19f-3c46-c259-f1efdcd4a7ab@proxmox.com> (raw)
In-Reply-To: <65ceea98-06f2-5e6e-e2f4-1d2b07c9a2b9@proxmox.com>
Am 04.05.21 um 10:24 schrieb Dominik Csapak:
> On 4/30/21 15:54, Fabian Ebner wrote:
>> picked up from an old patch by Alwin[0].
>>
>> The first four patches are cleanups/preparation.
>>
>> The last patch is the big one which introduces the handling of
>> multiple IP
>> addresses. Quickly tested with a dual IPv4/IPv6 setup and an external
>> client
>> and didn't see any issues (altough I might've missed something in my
>> struggle
>> to get the network configuration right). It is a bit messy (not sure
>> that is
>> fully possible to avoid) and I'd like to test it some more, so sending
>> it as an
>> RFC. Would be great if somebody else could test it too.
>>
>> Note that you also need a dual stack cluster network even if it's
>> separate from
>> the public network, so the OSDs will start up.
>>
>> [0]: https://lists.proxmox.com/pipermail/pve-devel/2020-March/042304.html
>>
>> Fabian Ebner (5):
>> api: ceph: mon: split up arguments for run_command
>> api: ceph: create mon: handle ms_bind_ipv* options more generally
>> api: ceph: create mon: factor out monmaptool command
>> api: ceph: create mon: explicitly add subsequent monitors to the
>> monmap
>> fix #2422: allow multiple Ceph public networks
>>
>> PVE/API2/Ceph/MON.pm | 228 +++++++++++++++++++++++++++++++------------
>> 1 file changed, 163 insertions(+), 65 deletions(-)
>>
>
> LGTM, and tested ok, only noticed one small thing
>
> it is possible to give the same ip address twice,
> this breaks the monitor (i cannot start it, but cannot destroy it either)
>
> e.g.
>
> pveceph mon create --mon-address '10.0.0.10,10.0.0.10'
>
> it adds it with the ip twice to the monmap
> this fails to start (because the port is bound already)
> but destroying it fails with 'no such monitor id'
>
>
Thanks for testing, and nice find! I'll make sure to handle that in the
next version.
prev parent reply other threads:[~2021-05-07 8:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 13:54 Fabian Ebner
2021-04-30 13:54 ` [pve-devel] [RFC manager 1/5] api: ceph: mon: split up arguments for run_command Fabian Ebner
2021-04-30 13:54 ` [pve-devel] [RFC manager 2/5] api: ceph: create mon: handle ms_bind_ipv* options more generally Fabian Ebner
2021-04-30 13:54 ` [pve-devel] [RFC manager 3/5] api: ceph: create mon: factor out monmaptool command Fabian Ebner
2021-04-30 13:54 ` [pve-devel] [RFC manager 4/5] api: ceph: create mon: explicitly add subsequent monitors to the monmap Fabian Ebner
2021-04-30 13:54 ` [pve-devel] [RFC manager 5/5] fix #2422: allow multiple Ceph public networks Fabian Ebner
2021-05-04 8:24 ` [pve-devel] [RFC manager] " Dominik Csapak
2021-05-07 8:04 ` Fabian Ebner [this message]
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=4412e72e-a19f-3c46-c259-f1efdcd4a7ab@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pve-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox