From: Stephan Leemburg <sleemburg@it-functions.nl>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] does somebody have an hetzner or ovh server to do test ?
Date: Sat, 22 Aug 2020 18:01:16 +0200 [thread overview]
Message-ID: <a7cc597b-0327-a36b-ffe2-82553a334d55@it-functions.nl> (raw)
In-Reply-To: <1494951154.2394588.1597820244987.JavaMail.zimbra@odiso.com>
Hi Alexandre,
Sorry for the late reply.
But actually, I do have 2 OVH based subscribed proxmox systems.
They both have 16 failover ip addresses. I have once tested the failover
of the complete /28 block and - although there are costs involved - it
works.
What would you like to test? If it does not disturb my production
servers, then I think I can help you.
Kind regards,
Met vriendelijke groet,
Stephan Leemburg
IT Functions
e: sleemburg@it-functions.nl
p: +31 (0)71 889 23 33
m: +31(0)6 83 22 30 69
kvk: 27313647
On 19-08-2020 08:57, Alexandre DERUMIER wrote:
> Hi,
>
> I'm currently looking to test ip failover (single /32 ip or subnet range)
> on public provider like hetzner or ovh.
>
> I have see a lot of users asking questions on the forum about routed setup.
>
> /32 is a bit tricky with point to point configuration,
>
> and I'll would like to implement them in sdn configuration (as I'm working on ip management).
>
>
> I just need a small server, 1 single failover /32 ip and 1 small failover subnet.
>
>
> If nobody can help, no problem, I'll rent a small server for 1 month.
>
>
> Alexandre
>
>
> (BTW: I'll try to send a new sdn patch series next week, I'm currently working on ip dns api registration)
>
>
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
>
next prev parent reply other threads:[~2020-08-22 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 6:57 Alexandre DERUMIER
2020-08-22 16:01 ` Stephan Leemburg [this message]
2020-08-25 7:28 ` Alexandre DERUMIER
2020-08-25 7:46 ` Thomas G
2020-08-25 7:49 ` Stephan Leemburg
2020-08-25 8:01 ` Alexandre DERUMIER
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=a7cc597b-0327-a36b-ffe2-82553a334d55@it-functions.nl \
--to=sleemburg@it-functions.nl \
--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