Open Stack

> 
> On 17.10.2018 15:45, Florian Engelmann wrote:
>>> On 10.10.2018 09:06, Florian Engelmann wrote:
>>>> Now I get you. I would say all configuration templates need to be 
>>>> changed to allow, eg.
>>>>
>>>> $ grep http /etc/kolla/cinder-volume/cinder.conf
>>>> glance_api_servers = http://10.10.10.5:9292
>>>> auth_url = http://internal.somedomain.tld:35357
>>>> www_authenticate_uri = http://internal.somedomain.tld:5000
>>>> auth_url = http://internal.somedomain.tld:35357
>>>> auth_endpoint = http://internal.somedomain.tld:5000
>>>>
>>>> to look like:
>>>>
>>>> glance_api_servers = http://glance.service.somedomain.consul:9292
>>>> auth_url = http://keystone.service.somedomain.consul:35357
>>>> www_authenticate_uri = http://keystone.service.somedomain.consul:5000
>>>> auth_url = http://keystone.service.somedomain.consul:35357
>>>> auth_endpoint = http://keystone.service.somedomain.consul:5000
>>>>
>>>
>>> The idea with Consul looks interesting.
>>>
>>> But I don't get your issue with VIP address and spine-leaf network.
>>>
>>> What we have:
>>> - controller1 behind leaf1 A/B pair with MLAG
>>> - controller2 behind leaf2 A/B pair with MLAG
>>> - controller3 behind leaf3 A/B pair with MLAG
>>>
>>> The VIP address is active on one controller server.
>>> When the server fail then the VIP will move to another controller 
>>> server.
>>> Where do you see a SPOF in this configuration?
>>>
>>
>> So leaf1 2 and 3 have to share the same L2 domain, right (in IPv4 
>> network)?
>>
> Yes, they share L2 domain but we have ARP and ND suppression enabled.
> 
> It is an EVPN network where there is a L3 with VxLANs between leafs and 
> spines.
> 
> So we don't care where a server is connected. It can be connected to any 
> leaf.

Ok that sounds very interesting. Is it possible to share some internals? 
Which switch vendor/model do you use? How does you IP address schema 
look like?
If VxLAN is used between spine and leafs are you using VxLAN networking 
for Openstack as well? Where is your VTEP?


> 
> 
>> But we wanna deploy a layer3 spine-leaf network were every leaf is 
>> it's own L2 domain and everything above is layer3.
>>
>> eg:
>>
>> leaf1 = 10.1.1.0/24
>> leaf2 = 10.1.2.0/24
>> leaf2 = 10.1.3.0/24
>>
>> So a VIP like, eg. 10.1.1.10 could only exist in leaf1
>>
> In my opinion it's a very constrained environment, I don't like the idea.
> 
> 
> Regards,
> 
> Piotr
> 
> 
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-- 

EveryWare AG
Florian Engelmann
Systems Engineer
Zurlindenstrasse 52a
CH-8003 Zürich

tel: +41 44 466 60 00
fax: +41 44 466 60 10
mail: mailto:florian.engelmann at everyware.ch
web: http://www.everyware.ch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5210 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20181019/d7e89d17/attachment.bin>