[OpenStack-DefCore] [interop-challenge] Floating IPs

Jean-Daniel Bonnetot jean-daniel.bonnetot at corp.ovh.com
Thu Oct 13 16:07:39 UTC 2016


Ok, so all your communications between instances pass through the public network, right?

--
Jean-Daniel Bonnetot
ovh.com | @pilgrimstack




> Le 13 oct. 2016 à 17:52, Stefano Maffulli <stefano+interop at openstack.org> a écrit :
> 
> Hi Jean-Daniel
> 
> DreamHost is also configured to provide a public IPv4 to VMs, we don't
> provide floating IPs unless they're required. Check vars/dreamhost.yml
> configuration file, to make the playbook work I leave   private_net_name
> empty.
> 
> HTH
> stef
> 
> 
> On 10/13/2016 07:42 AM, Jean-Daniel Bonnetot wrote:
>> Ok, I ran it too and its ok on my side too.
>> If it's ok for the challenge it's a good news.
>> 
>> Do you remember which CSP are in the same case (not providing floating
>> IPs)?
>> 
>> --
>> Jean-Daniel Bonnetot
>> ovh.com <http://ovh.com> | @pilgrimstack
>> 
>> 
>> 
>> 
>>> Le 13 oct. 2016 à 16:26, Tong Li <litong01 at us.ibm.com
>>> <mailto:litong01 at us.ibm.com>> a écrit :
>>> 
>>> Jean-Daniel,
>>> I have run these tests on OVH cloud using the scripts, they worked
>>> very well. The scripts allow your cloud to use whatever way your
>>> neutron is done. I was the first one marked your cloud successful
>>> regarding the interop effort, so I think it is perfectly ok to show
>>> off that on stage.
>>> 
>>> Thanks.
>>> 
>>> Tong Li
>>> IBM Open Technology
>>> Building 501/B205
>>> litong01 at us.ibm.com <mailto:litong01 at us.ibm.com>
>>> 
>>> <graycol.gif>Monty Taylor ---10/13/2016 10:04:52 AM---On 10/13/2016
>>> 08:31 AM, Jean-Daniel Bonnetot wrote: > Hi,
>>> 
>>> From: Monty Taylor <mordred at inaugust.com>
>>> To: defcore-committee at lists.openstack.org
>>> Date: 10/13/2016 10:04 AM
>>> Subject: Re: [OpenStack-DefCore] [interop-challenge] Floating IPs
>>> 
>>> ------------------------------------------------------------------------
>>> 
>>> 
>>> 
>>> On 10/13/2016 08:31 AM, Jean-Daniel Bonnetot wrote:
>>>> Hi,
>>>> 
>>>> There is something strange when I run the ansible lampstack playbook.
>>>> 
>>>> At OVH we do not provide Floating IPs. Our default behavior is to
>>> provide directly the public IP on eth0 of the instances.
>>>> 
>>>> To make the app work, I need to use my "Ext-Net" (in
>>> private_net_name parameter) which is similar to a private network but
>>> it's directly routed.
>>>> As a consequence, the app will use the public network to communicate
>>> between nodes.
>>>> 
>>>> I know some other CSP have direct public IP on the instance too.
>>> Does it work like that for you?
>>>> Is it ok for the challenge on stage?
>>> 
>>> I don't know the answer for the challenge - but I will say:
>>> 
>>> THANK YOU for providing direct IPs on your VMs. As a user, it's
>> wonderful.
>>> 
>>> _______________________________________________
>>> Defcore-committee mailing list
>>> Defcore-committee at lists.openstack.org
>>> <mailto:Defcore-committee at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>>> 
>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Defcore-committee mailing list
>>> Defcore-committee at lists.openstack.org
>>> <mailto:Defcore-committee at lists.openstack.org>
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>> 
>> 
>> 
>> _______________________________________________
>> Defcore-committee mailing list
>> Defcore-committee at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
>> 
> 
> 
> _______________________________________________
> Defcore-committee mailing list
> Defcore-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee



More information about the Defcore-committee mailing list