public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Alexandre DERUMIER <aderumier@odiso.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] does somebody have an hetzner or ovh server to do test ?
Date: Tue, 25 Aug 2020 10:01:57 +0200 (CEST)	[thread overview]
Message-ID: <1477705340.27718.1598342517857.JavaMail.zimbra@odiso.com> (raw)
In-Reply-To: <1a863230-10d8-173d-e9ea-f5fffaff23e2@it-functions.nl>

>>I did it manually through the control panel. I have only 2 servers at
>>OVH, but at that moment 3 as I was migrating from an old one to a new one.

>>So, I tested migrating the whole block from the new one to the old one
>>(so that one hat 2 /28 blocks after migration) and back.

Great :)

I'm looking to test bgp-evpn to replace vrack, and allow routing of a full /28 for example across multiple
nodes through internal routing, with auto failover of the gateway (through ovh api or other provider api).
(This will also allow vm migration between nodes with routed setup)

I'll work on it in coming months, I'm working on other sdn part currently.




----- Mail original -----
De: "Stephan Leemburg" <sleemburg@it-functions.nl>
À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Envoyé: Mardi 25 Août 2020 09:49:19
Objet: Re: [pve-devel] does somebody have an hetzner or ovh server to do test ?

On 25-08-2020 09:28, Alexandre DERUMIER wrote: 
> Hi Stephan, 
> 
> Thanks for the help 
> 
>>> What would you like to test? If it does not disturb my production 
>>> servers, then I think I can help you. 
> I would like to do a lot of setup test, so I'll break your production ;) 

Oh, that would not be good ;-) 

> I'm going to test routed setup, but also bgp-evpn,etc... 
> I have a friend working at ovh, I'll try to have some server to test. 
Hopefully they will sponsor you. 
> but thanks anyway. 
> 
You're welcome. 
>>> 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. 
> Interesting, you have failover le full /28 block between server ? 
> If yes, do you have done it manually ? or through the api ? 
> (In the future, I would like to implemented auto failover with keepalived/vrrp or something like that) 

I did it manually through the control panel. I have only 2 servers at 
OVH, but at that moment 3 as I was migrating from an old one to a new one. 

So, I tested migrating the whole block from the new one to the old one 
(so that one hat 2 /28 blocks after migration) and back. 


> 
> 
> ----- Mail original ----- 
> De: "Stephan Leemburg" <sleemburg@it-functions.nl> 
> À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com> 
> Envoyé: Samedi 22 Août 2020 18:01:16 
> Objet: Re: [pve-devel] does somebody have an hetzner or ovh server to do test ? 
> 
> 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 
>> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel@lists.proxmox.com 
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
> 
> 
> _______________________________________________ 
> pve-devel mailing list 
> pve-devel@lists.proxmox.com 
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 

_______________________________________________ 
pve-devel mailing list 
pve-devel@lists.proxmox.com 
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 




      reply	other threads:[~2020-08-25  8:02 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
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 [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=1477705340.27718.1598342517857.JavaMail.zimbra@odiso.com \
    --to=aderumier@odiso.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal