Changing Magnum Heat template to create node network with vxlan instead of vlan

Maysa De Macedo Souza mdemaced at redhat.com
Mon Sep 6 08:17:17 UTC 2021


Hello,

Just some extra thought, did you check if there is some process running on
port 8080? It's possible that the API failed to start, is Kuryr being used?

Thanks,
Maysa Macedo.

On Tue, Aug 31, 2021 at 1:57 PM Karera Tony <tonykarera at gmail.com> wrote:

> Hello Guys,
>
> I was able to configure the cluster internal network with Vlans. The
> communication was ok but I still get the same error
>
> + sleep 5
> ++ kubectl get --raw=/healthz
> The connection to the server localhost:8080 was refused - did you specify
> the right host or port?
> + '[' ok = '' ']'
>
> Regards
>
> Tony Karera
>
>
>
>
> On Sat, Aug 28, 2021 at 4:43 AM Mohammed Naser <mnaser at vexxhost.com>
> wrote:
>
>> AFAIK, Magnum does not control what encapsulation type is being used.
>>
>> Is there a chance you have “vlan” inside tenant_network_types ?
>>
>> On Tue, Aug 24, 2021 at 12:05 AM Karera Tony <tonykarera at gmail.com>
>> wrote:
>>
>>> Hello Team,
>>>
>>> I was able to deploy Openstack with Magnum and Zun enabled.
>>>
>>> Unfortunately, When I create a cluster, Heat configure the fix/_network
>>> for the nodes with Vlan and the nodes fail to get IPs.
>>>
>>> I was wondering if it is possible to trick the heat templates to create
>>> vxlan network instead of vlan.
>>>
>>> Regards
>>>
>>> Tony Karera
>>>
>>>
>>> --
>> Mohammed Naser
>> VEXXHOST, Inc.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20210906/1b2d2a06/attachment-0001.html>


More information about the openstack-discuss mailing list