Open Stack

Ruslanas, that would be excellent!

I will reply to you directly for details later unless the maillist would
like the full thread.

Some preliminary questions:

   - Do you have a separate physical interface for the segment(s) used for
   your remote subnets?
   The docs state each segment must have a unique physical network name,
   which suggests a separate physical interface for each segment unless I'm
   misunderstanding something.
   - Are your provisioning segments all on the same Neutron network?
   - Are you using tagged switchports or access switchports to your Ironic
   server(s)?

Thanks,
Tom King

On Wed, Jul 15, 2020 at 12:26 AM Ruslanas Gžibovskis <ruslanas at lpic.lt>
wrote:

> I have deployed that with tripleO, but now we are recabling and
> redeploying it. So once I have it running I can share my configs, just name
> which you want :)
>
> On Tue, 14 Jul 2020 at 18:40, Thomas King <thomas.king at gmail.com> wrote:
>
>> I have. That's the Triple-O docs and they don't go through the normal
>> .conf files to explain how it works outside of Triple-O. It has some ideas
>> but no running configurations.
>>
>> Tom King
>>
>> On Tue, Jul 14, 2020 at 3:01 AM Ruslanas Gžibovskis <ruslanas at lpic.lt>
>> wrote:
>>
>>> hi, have you checked:
>>> https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/routed_spine_leaf_network.html
>>>  ?
>>> I am following this link. I only have one network, having different
>>> issues tho ;)
>>>
>>>
>>>
>>> On Tue, 14 Jul 2020 at 03:31, Thomas King <thomas.king at gmail.com> wrote:
>>>
>>>> Thank you, Amy!
>>>>
>>>> Tom
>>>>
>>>> On Mon, Jul 13, 2020 at 5:19 PM Amy Marrich <amy at demarco.com> wrote:
>>>>
>>>>> Hey Tom,
>>>>>
>>>>> Adding the OpenStack discuss list as I think you got several replies
>>>>> from there as well.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Amy (spotz)
>>>>>
>>>>> On Mon, Jul 13, 2020 at 5:37 PM Thomas King <thomas.king at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Good day,
>>>>>>
>>>>>> I'm bringing up a thread from June about DHCP relay with neutron
>>>>>> networks in Ironic, specifically using unicast relay. The Triple-O docs do
>>>>>> not have the plain config/neutron config to show how a regular Ironic setup
>>>>>> would use DHCP relay.
>>>>>>
>>>>>> The Neutron segments docs state that I must have a unique physical
>>>>>> network name. If my Ironic controller has a single provisioning network
>>>>>> with a single physical network name, doesn't this prevent my use of
>>>>>> multiple segments?
>>>>>>
>>>>>> Further, the segments docs state this: "The operator must ensure
>>>>>> that every compute host that is supposed to participate in a router
>>>>>> provider network has direct connectivity to one of its segments." (section
>>>>>> 3 at
>>>>>> https://docs.openstack.org/neutron/pike/admin/config-routed-networks.html#prerequisites -
>>>>>> current docs state the same thing)
>>>>>> This defeats the purpose of using DHCP relay, though, where the
>>>>>> Ironic controller does *not* have direct connectivity to the remote
>>>>>> segment.
>>>>>>
>>>>>> Here is a rough drawing - what is wrong with my thinking here?
>>>>>> Remote server: 10.146.30.32/27 VLAN 2116<-----> Router with DHCP
>>>>>> relay <------> Ironic controller, provisioning network:
>>>>>> 10.146.29.192/26 VLAN 2115
>>>>>>
>>>>>> Thank you,
>>>>>> Tom King
>>>>>> _______________________________________________
>>>>>> openstack-mentoring mailing list
>>>>>> openstack-mentoring at lists.openstack.org
>>>>>>
>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring
>>>>>>
>>>>>
>>>
>>> --
>>> Ruslanas Gžibovskis
>>> +370 6030 7030
>>>
>>
>
> --
> Ruslanas Gžibovskis
> +370 6030 7030
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20200715/a03e1a50/attachment-0001.html>