subject:"Re\: \[openstack\-dev\] \[kolla\] Vxlan and OVS issues post deployment."

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

2017-11-30 Thread Goutham Pratapa

Hi Eduardo,

No, they were not created by default I had to follow the workaround only
then they are getting created

I'm just bringing to your notice that the issue is still there because they
are not present after the deployment  :)

Now even after the tunnels are created VM's are not getting the IP

Thanks
Goutham.

On Thu, Nov 30, 2017 at 4:02 PM, Eduardo Gonzalez 
wrote:

> Hi Goutham,
>
> VXLAN tunnels are created between network/compute hosts in expected
> interface (ens3):
>
> df_default="true", in_key=flow, local_ip="192.168.122.215", out_key=flow, 
> remote_ip="192.168.122.177"
>
> Where is exactly failing? Instances not get IP, DHCP does not work, vm-to-vm 
> traffic issues, public traffic issues?
>
> Regards
>
>
> 2017-11-30 11:26 GMT+01:00 Goutham Pratapa :
>
>> Hi Eduardo,
>>
>> I am trying to deploy self-service network topology.
>>
>> I think then I shouldn't be bothered about the `ens8` because I'm not
>> dealing with provider networks
>>
>> and attached are the outputs requested...
>>
>> Ps: Controller and the network node are both same in my setup.
>>
>> Thanks in advance
>>
>> Goutham
>>
>> On Thu, Nov 30, 2017 at 3:33 PM, Eduardo Gonzalez 
>> wrote:
>>
>>> Hi,
>>>
>>> In kolla,VXLAN  tunnels are connfigured in ``tunnel_interface`` variable
>>> which defaults to ``network_interface``, ``neutron_external_interface`` is
>>> used for public floating IPs in neutron.
>>>
>>> Please share your globals.yml, ``ip a`` output in compute/network hosts
>>> and ``ovs-vsctl show`` from openvswitch daemon containers.
>>>
>>> What network topology are you trying to deploy? Self-service, provider
>>> networks, etc?
>>>
>>> Regards
>>>
>>>
>>> 2017-11-30 10:42 GMT+01:00 Jeffrey Zhang :
>>>
 i guess you didn't enabled one of following[0]

   enable_neutron_dvr: yes
   enable_neutron_provider_networks: yes

 I hit this recently. i am thinking we should remove this or make
 enable_neutron_provider_network=yes in default.

 [0] https://github.com/openstack/kolla-ansible/blob/master/a
 nsible/group_vars/all.yml#L607


 On Thu, Nov 30, 2017 at 5:11 PM, Goutham Pratapa <
 pratapagout...@gmail.com> wrote:

> Hi Kolla Team,
>
> I have tried deploying Kolla OpenStack multinode and I am facing this
> issue vxlan_peers_not_created
> 
> in every deployment and I* tried the workaround* i.e restart the
> network  containers to get the vxlan peers
>
> But when I see *ip addr show *in my compute node.
>
> *P.S:* "ens8"  is the interface I specified as
> *neutron_external_interface** in globals.yml*
>
>
> * Globals.yml-*
>
>
>
>
> *# This is the raw interface given to neutron as its external network
> port. Even# though an IP address can exist on this interface, it will be
> unusable in most# configurations. It is recommended this interface not be
> configured with any IP# addresses for that reason.*
>
> *neutron_external_interface: "ens8"*3: ens8:
>  mtu 1500 qdisc pfifo_fast state UP
> group default qlen 1000
> link/ether 52:54:00:54:b3:50 brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.218/24 scope global ens8
>valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fe54:b350/64 scope link
>valid_lft forever preferred_lft forever
>
> Which should be something like the below (as per my understanding) for
> the Vms to be up and running.
>
> 3: ens8:  mtu 1500 qdisc pfifo_fast 
> *master
> ovs-system* state UP group default qlen 1000
> link/ether 52:54:00:22:4b:cf brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.165/32 scope global ens8
>valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fe22:4bcf/64 scope link
>valid_lft forever preferred_lft forever
>
> Is this a known issue ??
>
> If yes any workaround to solve??
>
> Thanks in advance.
> --
> Thanks!!!
> Goutham Pratapa
>
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.op
> enstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


 --
 Regards,
 Jeffrey Zhang
 Blog: http://xcodest.me

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

2017-11-30 Thread Eduardo Gonzalez

Hi Goutham,

VXLAN tunnels are created between network/compute hosts in expected
interface (ens3):

df_default="true", in_key=flow, local_ip="192.168.122.215",
out_key=flow, remote_ip="192.168.122.177"

Where is exactly failing? Instances not get IP, DHCP does not work,
vm-to-vm traffic issues, public traffic issues?

Regards


2017-11-30 11:26 GMT+01:00 Goutham Pratapa :

> Hi Eduardo,
>
> I am trying to deploy self-service network topology.
>
> I think then I shouldn't be bothered about the `ens8` because I'm not
> dealing with provider networks
>
> and attached are the outputs requested...
>
> Ps: Controller and the network node are both same in my setup.
>
> Thanks in advance
>
> Goutham
>
> On Thu, Nov 30, 2017 at 3:33 PM, Eduardo Gonzalez 
> wrote:
>
>> Hi,
>>
>> In kolla,VXLAN  tunnels are connfigured in ``tunnel_interface`` variable
>> which defaults to ``network_interface``, ``neutron_external_interface`` is
>> used for public floating IPs in neutron.
>>
>> Please share your globals.yml, ``ip a`` output in compute/network hosts
>> and ``ovs-vsctl show`` from openvswitch daemon containers.
>>
>> What network topology are you trying to deploy? Self-service, provider
>> networks, etc?
>>
>> Regards
>>
>>
>> 2017-11-30 10:42 GMT+01:00 Jeffrey Zhang :
>>
>>> i guess you didn't enabled one of following[0]
>>>
>>>   enable_neutron_dvr: yes
>>>   enable_neutron_provider_networks: yes
>>>
>>> I hit this recently. i am thinking we should remove this or make
>>> enable_neutron_provider_network=yes in default.
>>>
>>> [0] https://github.com/openstack/kolla-ansible/blob/master/a
>>> nsible/group_vars/all.yml#L607
>>>
>>>
>>> On Thu, Nov 30, 2017 at 5:11 PM, Goutham Pratapa <
>>> pratapagout...@gmail.com> wrote:
>>>
 Hi Kolla Team,

 I have tried deploying Kolla OpenStack multinode and I am facing this
 issue vxlan_peers_not_created
 
 in every deployment and I* tried the workaround* i.e restart the
 network  containers to get the vxlan peers

 But when I see *ip addr show *in my compute node.

 *P.S:* "ens8"  is the interface I specified as
 *neutron_external_interface** in globals.yml*


 * Globals.yml-*




 *# This is the raw interface given to neutron as its external network
 port. Even# though an IP address can exist on this interface, it will be
 unusable in most# configurations. It is recommended this interface not be
 configured with any IP# addresses for that reason.*

 *neutron_external_interface: "ens8"*3: ens8:
  mtu 1500 qdisc pfifo_fast state UP
 group default qlen 1000
 link/ether 52:54:00:54:b3:50 brd ff:ff:ff:ff:ff:ff
 inet 192.168.122.218/24 scope global ens8
valid_lft forever preferred_lft forever
 inet6 fe80::5054:ff:fe54:b350/64 scope link
valid_lft forever preferred_lft forever

 Which should be something like the below (as per my understanding) for
 the Vms to be up and running.

 3: ens8:  mtu 1500 qdisc pfifo_fast 
 *master
 ovs-system* state UP group default qlen 1000
 link/ether 52:54:00:22:4b:cf brd ff:ff:ff:ff:ff:ff
 inet 192.168.122.165/32 scope global ens8
valid_lft forever preferred_lft forever
 inet6 fe80::5054:ff:fe22:4bcf/64 scope link
valid_lft forever preferred_lft forever

 Is this a known issue ??

 If yes any workaround to solve??

 Thanks in advance.
 --
 Thanks!!!
 Goutham Pratapa

 
 __
 OpenStack Development Mailing List (not for usage questions)
 Unsubscribe: openstack-dev-requ...@lists.op
 enstack.org?subject:unsubscribe
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


>>>
>>>
>>> --
>>> Regards,
>>> Jeffrey Zhang
>>> Blog: http://xcodest.me
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Cheers !!!
> Goutham Pratapa
>
> __
> OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

2017-11-30 Thread Goutham Pratapa

Hi Eduardo,

I am trying to deploy self-service network topology.

I think then I shouldn't be bothered about the `ens8` because I'm not
dealing with provider networks

and attached are the outputs requested...

Ps: Controller and the network node are both same in my setup.

Thanks in advance

Goutham

On Thu, Nov 30, 2017 at 3:33 PM, Eduardo Gonzalez 
wrote:

> Hi,
>
> In kolla,VXLAN  tunnels are connfigured in ``tunnel_interface`` variable
> which defaults to ``network_interface``, ``neutron_external_interface`` is
> used for public floating IPs in neutron.
>
> Please share your globals.yml, ``ip a`` output in compute/network hosts
> and ``ovs-vsctl show`` from openvswitch daemon containers.
>
> What network topology are you trying to deploy? Self-service, provider
> networks, etc?
>
> Regards
>
>
> 2017-11-30 10:42 GMT+01:00 Jeffrey Zhang :
>
>> i guess you didn't enabled one of following[0]
>>
>>   enable_neutron_dvr: yes
>>   enable_neutron_provider_networks: yes
>>
>> I hit this recently. i am thinking we should remove this or make
>> enable_neutron_provider_network=yes in default.
>>
>> [0] https://github.com/openstack/kolla-ansible/blob/master/
>> ansible/group_vars/all.yml#L607
>>
>>
>> On Thu, Nov 30, 2017 at 5:11 PM, Goutham Pratapa <
>> pratapagout...@gmail.com> wrote:
>>
>>> Hi Kolla Team,
>>>
>>> I have tried deploying Kolla OpenStack multinode and I am facing this
>>> issue vxlan_peers_not_created
>>> 
>>> in every deployment and I* tried the workaround* i.e restart the
>>> network  containers to get the vxlan peers
>>>
>>> But when I see *ip addr show *in my compute node.
>>>
>>> *P.S:* "ens8"  is the interface I specified as
>>> *neutron_external_interface** in globals.yml*
>>>
>>>
>>> * Globals.yml-*
>>>
>>>
>>>
>>>
>>> *# This is the raw interface given to neutron as its external network
>>> port. Even# though an IP address can exist on this interface, it will be
>>> unusable in most# configurations. It is recommended this interface not be
>>> configured with any IP# addresses for that reason.*
>>>
>>> *neutron_external_interface: "ens8"*3: ens8:
>>>  mtu 1500 qdisc pfifo_fast state UP
>>> group default qlen 1000
>>> link/ether 52:54:00:54:b3:50 brd ff:ff:ff:ff:ff:ff
>>> inet 192.168.122.218/24 scope global ens8
>>>valid_lft forever preferred_lft forever
>>> inet6 fe80::5054:ff:fe54:b350/64 scope link
>>>valid_lft forever preferred_lft forever
>>>
>>> Which should be something like the below (as per my understanding) for
>>> the Vms to be up and running.
>>>
>>> 3: ens8:  mtu 1500 qdisc pfifo_fast *master
>>> ovs-system* state UP group default qlen 1000
>>> link/ether 52:54:00:22:4b:cf brd ff:ff:ff:ff:ff:ff
>>> inet 192.168.122.165/32 scope global ens8
>>>valid_lft forever preferred_lft forever
>>> inet6 fe80::5054:ff:fe22:4bcf/64 scope link
>>>valid_lft forever preferred_lft forever
>>>
>>> Is this a known issue ??
>>>
>>> If yes any workaround to solve??
>>>
>>> Thanks in advance.
>>> --
>>> Thanks!!!
>>> Goutham Pratapa
>>>
>>> 
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.op
>>> enstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Regards,
>> Jeffrey Zhang
>> Blog: http://xcodest.me
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Cheers !!!
Goutham Pratapa

1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: ens3:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 52:54:00:30:a5:ee brd ff:ff:ff:ff:ff:ff
inet 192.168.122.215/24 brd 192.168.122.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe30:a5ee/64 scope link
   valid_lft forever preferred_lft forever
3: ens8:

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

2017-11-30 Thread Eduardo Gonzalez

Hi,

In kolla,VXLAN  tunnels are connfigured in ``tunnel_interface`` variable
which defaults to ``network_interface``, ``neutron_external_interface`` is
used for public floating IPs in neutron.

Please share your globals.yml, ``ip a`` output in compute/network hosts and
``ovs-vsctl show`` from openvswitch daemon containers.

What network topology are you trying to deploy? Self-service, provider
networks, etc?

Regards


2017-11-30 10:42 GMT+01:00 Jeffrey Zhang :

> i guess you didn't enabled one of following[0]
>
>   enable_neutron_dvr: yes
>   enable_neutron_provider_networks: yes
>
> I hit this recently. i am thinking we should remove this or make
> enable_neutron_provider_network=yes in default.
>
> [0] https://github.com/openstack/kolla-ansible/blob/
> master/ansible/group_vars/all.yml#L607
>
>
> On Thu, Nov 30, 2017 at 5:11 PM, Goutham Pratapa  > wrote:
>
>> Hi Kolla Team,
>>
>> I have tried deploying Kolla OpenStack multinode and I am facing this
>> issue vxlan_peers_not_created
>> 
>> in every deployment and I* tried the workaround* i.e restart the
>> network  containers to get the vxlan peers
>>
>> But when I see *ip addr show *in my compute node.
>>
>> *P.S:* "ens8"  is the interface I specified as
>> *neutron_external_interface** in globals.yml*
>>
>>
>> * Globals.yml-*
>>
>>
>>
>>
>> *# This is the raw interface given to neutron as its external network
>> port. Even# though an IP address can exist on this interface, it will be
>> unusable in most# configurations. It is recommended this interface not be
>> configured with any IP# addresses for that reason.*
>>
>> *neutron_external_interface: "ens8"*3: ens8:
>>  mtu 1500 qdisc pfifo_fast state UP
>> group default qlen 1000
>> link/ether 52:54:00:54:b3:50 brd ff:ff:ff:ff:ff:ff
>> inet 192.168.122.218/24 scope global ens8
>>valid_lft forever preferred_lft forever
>> inet6 fe80::5054:ff:fe54:b350/64 scope link
>>valid_lft forever preferred_lft forever
>>
>> Which should be something like the below (as per my understanding) for
>> the Vms to be up and running.
>>
>> 3: ens8:  mtu 1500 qdisc pfifo_fast *master
>> ovs-system* state UP group default qlen 1000
>> link/ether 52:54:00:22:4b:cf brd ff:ff:ff:ff:ff:ff
>> inet 192.168.122.165/32 scope global ens8
>>valid_lft forever preferred_lft forever
>> inet6 fe80::5054:ff:fe22:4bcf/64 scope link
>>valid_lft forever preferred_lft forever
>>
>> Is this a known issue ??
>>
>> If yes any workaround to solve??
>>
>> Thanks in advance.
>> --
>> Thanks!!!
>> Goutham Pratapa
>>
>> 
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscrib
>> e
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Regards,
> Jeffrey Zhang
> Blog: http://xcodest.me
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

2017-11-30 Thread Jeffrey Zhang

i guess you didn't enabled one of following[0]

  enable_neutron_dvr: yes
  enable_neutron_provider_networks: yes

I hit this recently. i am thinking we should remove this or make
enable_neutron_provider_network=yes in default.

[0]
https://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L607


On Thu, Nov 30, 2017 at 5:11 PM, Goutham Pratapa 
wrote:

> Hi Kolla Team,
>
> I have tried deploying Kolla OpenStack multinode and I am facing this
> issue vxlan_peers_not_created
> 
> in every deployment and I* tried the workaround* i.e restart the network
> containers to get the vxlan peers
>
> But when I see *ip addr show *in my compute node.
>
> *P.S:* "ens8"  is the interface I specified as
> *neutron_external_interface** in globals.yml*
>
>
> * Globals.yml-*
>
>
>
>
> *# This is the raw interface given to neutron as its external network
> port. Even# though an IP address can exist on this interface, it will be
> unusable in most# configurations. It is recommended this interface not be
> configured with any IP# addresses for that reason.*
>
> *neutron_external_interface: "ens8"*3: ens8:
>  mtu 1500 qdisc pfifo_fast state UP
> group default qlen 1000
> link/ether 52:54:00:54:b3:50 brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.218/24 scope global ens8
>valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fe54:b350/64 scope link
>valid_lft forever preferred_lft forever
>
> Which should be something like the below (as per my understanding) for the
> Vms to be up and running.
>
> 3: ens8:  mtu 1500 qdisc pfifo_fast *master
> ovs-system* state UP group default qlen 1000
> link/ether 52:54:00:22:4b:cf brd ff:ff:ff:ff:ff:ff
> inet 192.168.122.165/32 scope global ens8
>valid_lft forever preferred_lft forever
> inet6 fe80::5054:ff:fe22:4bcf/64 scope link
>valid_lft forever preferred_lft forever
>
> Is this a known issue ??
>
> If yes any workaround to solve??
>
> Thanks in advance.
> --
> Thanks!!!
> Goutham Pratapa
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Regards,
Jeffrey Zhang
Blog: http://xcodest.me
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

Re: [openstack-dev] [kolla] Vxlan and OVS issues post deployment.

5 matches

Site Navigation

Mail list logo

Footer information