settingsLogin | Registersettings

Re: [Openstack] Openstack Digest, Vol 34, Issue 21 . Re: issue when launching instance

0 votes

Hi,

Here are neutron and cinder services status :

[root@dhcp-10-128-10-0 ~(keystoneadmin)]# cinder service-list
+------------------+----------------------+------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated
at | Disabled Reason |
+------------------+----------------------+------+---------+-------+----------------------------+-----------------+
| cinder-backup | dhcp-10-128-10-0 | nova | enabled | up | 2016-04-22T06:15:24.000000 | - |
| cinder-scheduler | dhcp-10-128-10-0 | nova | enabled | up | 2016-04-22T06:15:24.000000 | - |
| cinder-volume | dhcp-10-128-10-0@lvm | nova | enabled | up | 2016-04-22T06:15:24.000000 | - |
+------------------+----------------------+------+---------+-------+----------------------------+-----------------+
[root@dhcp-10-128-10-0 ~(keystoneadmin)]# neutron agent-list
+--------------------------------------+--------------------+------------------+-------+----------------+---------------------------+
| id | agent
type | host | alive | adminstateup | binary |
+--------------------------------------+--------------------+------------------+-------+----------------+---------------------------+
| 2a2a9406-e911-4719-b1af-405748f059fd | L3 agent | dhcp-10-128-10-0 | :-) | True | neutron-l3-agent |
| 5d5aa212-7d77-4501-ad87-e2bff8ef94e6 | Open vSwitch agent | dhcp-10-128-10-0 | :-) | True | neutron-openvswitch-agent |
| 8f06cb9a-5124-4b1f-b632-558677282708 | Metadata agent | dhcp-10-128-10-0 | :-) | True | neutron-metadata-agent |
| e88048fe-073a-4889-9282-7db62acbef4f | DHCP agent | dhcp-10-128-10-0 | :-) | True | neutron-dhcp-agent |
+--------------------------------------+--------------------+------------------+-------+----------------+---------------------------+
[root@dhcp-10-128-10-0 ~(keystone_admin)]

Regards,

J.P.

-----Original Message-----
From: openstack-request@lists.openstack.org [mailto:openstack-request@lists.openstack.org]
Sent: jeudi 21 avril 2016 21:51
To: openstack@lists.openstack.org
Subject: Openstack Digest, Vol 34, Issue 21

Send Openstack mailing list submissions to
openstack@lists.openstack.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
or, via email, send a message with subject or body 'help' to
openstack-request@lists.openstack.org

You can reach the person managing the list at
openstack-owner@lists.openstack.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Openstack digest..."

Today's Topics:

  1. Re: Xenial / Mitaka = Instance failed network setup /
    nova.compute.manager Unauthorized (Eugen Block)
  2. Re: nova backup (Eugen Block)
  3. Re: Help with Openstack Liberty: Failed to allocate the
    network (Remo Mattei)
  4. Re: Xenial / Mitaka = Instance failed network setup /
    nova.compute.manager Unauthorized (Paras pradhan)
  5. issue when launching instance (Jean-Pierre Ribeauville)
  6. Re: Xenial / Mitaka = Instance failed network setup /
    nova.compute.manager Unauthorized (Martinx - ?????)
  7. Re: issue when launching instance (Remo Mattei)
  8. Re: issue when launching instance (Eugen Block)
  9. Re: issue when launching instance (Jean-Pierre Ribeauville)

    1. Mitaka with OpenvSwitch, no VXLAN tunnels between compute and
      network nodes (Martinx - ?????)
    2. Re: Mitaka with OpenvSwitch, no VXLAN tunnels between compute
      and network nodes (Martinx - ?????)
    3. Re: Mitaka with OpenvSwitch, no VXLAN tunnels between compute
      and network nodes (Martinx - ?????)
    4. OpenStack Mitaka for Ubuntu 14.04 LTS and Ubuntu 16.04 LTS
      (Corey Bryant)
    5. Openstack security - port-security, security-groups with
      added container (Farhad Sunavala)
    6. Re: OpenStack Mitaka for Ubuntu 14.04 LTS and Ubuntu 16.04
      LTS (Martinx - ?????)
    7. Re: Mitaka with OpenvSwitch, no VXLAN tunnels between compute
      and network nodes (Martinx - ?????)
    8. Re: Xenial / Mitaka = Instance failed network setup /
      nova.compute.manager Unauthorized (Paras pradhan)
    9. Re: Xenial / Mitaka = Instance failed network setup /
      nova.compute.manager Unauthorized (Martinx - ?????)

Message: 1
Date: Thu, 21 Apr 2016 14:36:08 +0200
From: Eugen Block eblock@nde.ag
To: Paras pradhan pradhanparas@gmail.com
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Xenial / Mitaka = Instance failed network
setup / nova.compute.manager Unauthorized
Message-ID: 20160421143608.Horde.WoEhDsHhhLpYXkE2uJu4GSe@www3.nde.ag
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes

Okay, did you restart the respective services on all nodes after the
changes in your config files? If the same error still occurs then you
might haven't found all occurrences of the option auth_plugin, did you
replace it in all config files? I'm just guessing here...

Zitat von Paras pradhan pradhanparas@gmail.com:

No I still have that error. Other than that I don't see any other errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block eblock@nde.ag wrote:

So I guess the mentioned error should be resolved? Does it work now?

Zitat von Paras pradhan pradhanparas@gmail.com:

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block eblock@nde.ag wrote:

And did you change it to authtype instead of authplugin? Also you should

make sure that this option is in the correct section of your config file,
for example

[keystoneauthtoken]
...
auth
type = password

or

[neutron]
...
auth_type = password

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block eblock@nde.ag wrote:

Hi Paras,

the option auth_plugin is deprecated (from nova.conf):

---cut here---

Authentication type to load (unknown value)

Deprecated group/name - [DEFAULT]/auth_plugin

auth_type = password
---cut here---

But as far as I can tell, you should only get a warning, not an error,
I've seen some of these warnings in my logs, but it works (I work with
openSUSE). To get Mitaka working at all I simply tried to set the same
options as in my working Liberty configs, and then I searched for
deprecation warnings and additional options mentioned in the Mitaka
guide.

Hope this helps!

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Can somebody share the nova.conf and neutron.conf from working mitaka?
I
am

also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.

Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
nasir.mahmood@gmail.com
>
wrote:

Martinx,

glad to see that you are able to dig into the typo issue. I
remember, I
had to completely re-re-clean install my virtual setup of OpenStack
for a
POC back in 2015 , just because I have had miss-configured my
neutron.conf's mysql DB connector information.

Cheers!

Regards,
Nasir Mahmood

On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

FIXED!! I knew it was a typo somewhere! LOL

https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02

Thank you guys!

Sorry about the buzz on TWO mail lists...

At least, now we know that Nova silent fail on its start up, if
somethings aren't configured according... And there is no
verification
steps to test the communication between Nova and Neutron.

Mitaka is working now on Xenial! YAY!!

I'm about to commit changes to enable OpenvSwitch with DPDK and
multi-node deployments, fully automated!

Cheers!
Thiago

On 17 April 2016 at 21:26, Martinx - ????? <
thiagocmartinsc@gmail.com
>
wrote:

On 17 April 2016 at 17:39, Martinx - ????? <
thiagocmartinsc@gmail.com
>

wrote:

Guys,

I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using
the
following document:

http://docs.openstack.org/mitaka/install-guide-ubuntu

Yes, I know, the above document is for installing Mitaka on top
of
Ubuntu 14.04 but, from what I understand, the only difference is
that
on
Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive,
since
Mitaka is the default on Xenial, so, I can follow that document,
right?
=)

At first, OpenStack installation goes okay, without any errors,
all
services comes up, etc... However, it is not possible to launch an
Instance.

*** Errors on launching the Instance:

  • Right after launching it:

    https://paste.ubuntu.com/15902503/

  • Spawning it, after Glance finishes the download, similar error
    a
    second time:

    https://paste.ubuntu.com/15902556/

    What am I missing?

    Apparently, Nova is not authorized to talk with Neutron but, I am
    following the docs (maybe it is just a typo somewhere?)...

    Also, I have an Ansible automation to deploy it, so, it is less
    error
    prone. And however can help me, will see how I am deploying it.

    I see no error on Admin Dashboard, all services are up.

    NOTE: My Ansible playbooks is in a sense, "
    docs.openstack.org/mitaka/install-guide-ubuntu fully automated",
    it
    is
    very close to it, step-by-step.

    How can I debug this? I mean, how can I try to do, what Nova is
    doing
    (its connection with Neutron), to make sure that the settings are
    in
    place
    correctly?

    Here is how I am installing Mitaka on Xenial:


1- Install Ubuntu 16.04 server 64-bit on bare-metal;
  • Configure your /etc/hostname and /etc/hosts.

    DETAILS:
    https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md

    2- Clone the automation:

    cd ~
    git clone https://github.com/tmartinx/svauto.git

    3- Run the automation to install OpenStack (all-in-one)

    cd ~/svauto

    ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16
    --base-os-upgrade=yes --openstack-release=mitaka
    --openstack-installation
    --dry-run

    ansible-playbook -c local site-openstack.yml --extra-vars
    "openstack_installation=yes"


    NOTE: If you don't use "--dry-run" option, Ansible will be
    executed
    automatically by "os-deploy.sh".

    I am sharing the Ansible playbooks, because it will be easier to
    see
    what I am doing.

    About the relevant configuration blocks, I believe that I have it
    properly configured (I followed Mitaka docs), like this:

    • neutron.conf:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
-

  • nova.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
-

I already installed OpenStack many, many, many times, since
Havana
release, I'm confident that I am doing it right but, of course,
maybe
I did
something wrong this time... =P

I appreciate any help!

Thanks!
Thiago

Hey guys,

I am reviewing everything, to make sure that my automation matches
docs.openstack.org/mitaka/install-guide-ubuntu/ in details.

Two things...


1- All the verification steps (from official doc) passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html
- passed (mine doesn't have /horizon)

http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html
- passed but, I'm not using any cinder-volume yet

http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html
- "6. Launch the instance" - FAIL

NOTE: I can create Networks, Subnets, Routers... I can see the
Linux
Namespaces at the Neutron L3 Router (All-in-One)

2- This problem happen no matter if deploying it with Linux
Bridges
(--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS)


So, I think that OpenStack should provide more verification steps,
specially to test the communication / authentication between its
different
projects, for example:

A- Does Nova can communicate with Neutron? How to test this?

B- Can Nova download images from Glance? Etc...

Doing more reviews now...

Cheers!
Thiago


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Nasir Mahmood


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

     Vorsitzende des Aufsichtsrates: Angelika Mozdzen
       Sitz und Registergericht: Hamburg, HRB 90934
               Vorstand: Jens-U. Mozdzen
                USt-IdNr. DE 814 013 983

Message: 2
Date: Thu, 21 Apr 2016 14:41:37 +0200
From: Eugen Block eblock@nde.ag
To: openstack@lists.openstack.org
Subject: Re: [Openstack] nova backup
Message-ID: 20160421144137.Horde.JG12YoBmi51tluwhacEkRZl@www3.nde.ag
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes

Hi,
I haven't used nova backup yet, I only tested cinder backup. But
obviously you launched that instance via boot-from-volume, so your
instance's image resides within a volume, and volumes are handled by
cinder. So these instances should be backed up via cinder.

Eugen

Zitat von K K nnex@mail.ru:

Hello.
When I try to create backup:
nova backup testdeb testdeb_bak daily 2
nova-api said:
==> nova/nova-api.log <==
2016-04-21 16:40:14.828 2814 INFO nova.compute.api
[req-e89878e7-9d26-4e6e-8922-8aa9bba56b72
8d384cc45d0c467eb46ef3f980cf314d 3029462986ac400ca2c2c6ac4c9af5a7 -
- -] [instance: a962f06b-052d-4df8-afbb-5d0e6581eb92] It's not
supported to backup volume backed instance.
I have 2 ceph cluster: 1st for instances, 2nd for backup (connected
via?cinder-backup daemon).
But I can successfully create backup using cinder backup-create --force
why I can't make a backup via nova backup?

--
K K

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

     Vorsitzende des Aufsichtsrates: Angelika Mozdzen
       Sitz und Registergericht: Hamburg, HRB 90934
               Vorstand: Jens-U. Mozdzen
                USt-IdNr. DE 814 013 983

Message: 3
Date: Thu, 21 Apr 2016 07:00:13 -0700
From: Remo Mattei remo@italy1.com
To: "The O.G." theoriginalguru@gmail.com
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] Help with Openstack Liberty: Failed to
allocate the network
Message-ID: 19E16F0C-49E7-4985-8BA8-40F19C3ADB7D@italy1.com
Content-Type: text/plain; charset="us-ascii"

has this been a new installation or an upgrade?
Not sure what you mean with option 2 since the install guide does not say anything about options.
did you check if rabbit is up?
did you check and see if the services are all good
did you check and see if the agents are happy?

just a few things to check let us know!

Remo

On Apr 20, 2016, at 19:05, The O.G. theoriginalguru@gmail.com wrote:

We are following:

http://docs.openstack.org/liberty/install-guide-rdo/index.html http://docs.openstack.org/liberty/install-guide-rdo/index.html

Using CentOS7. We've chosen the option 2 for networking, where we have both a private and public network. We've pretty much following the guide step by step up to and finishing "Add the dashboard" step. All the verification steps passed.

Now, we are trying to launch an instance on the public and private networks as outlined here:

http://docs.openstack.org/liberty/install-guide-rdo/launch-instance-public.html http://docs.openstack.org/liberty/install-guide-rdo/launch-instance-public.html

http://docs.openstack.org/liberty/install-guide-rdo/launch-instance-private.html http://docs.openstack.org/liberty/install-guide-rdo/launch-instance-private.html

In both attempts to launch an instance, the instance gets aborted and shows status = Error. With this message:

Build of instance 93bf7968-09b2-4890-9c3a-0d909ce57017 aborted: Failed to allocate the network(s), not rescheduling.

On the compute node, in /var/log/nova/nova-compute.log, we get these messages (I'm filtering on ERROR|WARNING only):

2016-04-20 18:35:31.484 860 WARNING nova.virt.libvirt.driver [req-b5ec5b9d-2299-411f-b259-7a48b2b47d26 e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Timeout waiting for vif plugging callback for instance 93bf7968-09b2-4890-9c3a-0d909ce57017
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [req-b5ec5b9d-2299-411f-b259-7a48b2b47d26 e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Instance failed to spawn
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Traceback (most recent call last):
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2155, in buildresources
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] yield resources
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2009, in buildandruninstance
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2515, in spawn
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4612, in createdomainandnetwork
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] raise exception.VirtualInterfaceCreateException()
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] VirtualInterfaceCreateException: Virtual Interface creation failed
2016-04-20 18:35:32.007 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017]
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [req-b5ec5b9d-2299-411f-b259-7a48b2b47d26 e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Failed to allocate network(s)
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Traceback (most recent call last):
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2009, in buildandruninstance
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2515, in spawn
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4612, in createdomainandnetwork
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] raise exception.VirtualInterfaceCreateException()
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] VirtualInterfaceCreateException: Virtual Interface creation failed
2016-04-20 18:35:32.587 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017]
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [req-b5ec5b9d-2299-411f-b259-7a48b2b47d26 e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Build of instance 93bf7968-09b2-4890-9c3a-0d909ce57017 aborted: Failed to allocate the network(s), not rescheduling.
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] Traceback (most recent call last):
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1905, in dobuildandruninstance
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] filter
properties)
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2044, in buildandruninstance
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] reason=msg)
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017] BuildAbortException: Build of instance 93bf7968-09b2-4890-9c3a-0d909ce57017 aborted: Failed to allocate the network(s), not rescheduling.
2016-04-20 18:35:32.590 860 ERROR nova.compute.manager [instance: 93bf7968-09b2-4890-9c3a-0d909ce57017]
2016-04-20 18:42:55.909 860 WARNING nova.virt.libvirt.driver [req-9a205dde-ed7f-43aa-96d4-f6776347359e e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] Timeout waiting for vif plugging callback for instance ae94da8c-3fe6-44d6-93e5-b84a606c725c
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [req-9a205dde-ed7f-43aa-96d4-f6776347359e e11c48fa3827406c9e6304f88332e059 a8f41d79dc7a490c91013616f66c0134 - - -] [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] Instance failed to spawn
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] Traceback (most recent call last):
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2155, in buildresources
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] yield resources
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2009, in buildandruninstance
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2515, in spawn
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] blockdeviceinfo=blockdeviceinfo)
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4612, in createdomainandnetwork
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] raise exception.VirtualInterfaceCreateException()
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c] VirtualInterfaceCreateException: Virtual Interface creation failed
2016-04-20 18:42:56.358 860 ERROR nova.compute.manager [instance: ae94da8c-3fe6-44d6-93e5-b84a606c725c]

On the controller node, in /var/log/neutron/server.log:

2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'tag': u'4c0a7262-ac40-4556-bb11-5b20afceec73', 'name': 'network-vif-deleted', 'serveruuid': u'93bf7968-09b2-4890-9c3a-0d909ce57017'}]
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova Traceback (most recent call last):
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py", line 247, in send
events
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova batchedevents)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/v2/contrib/server
externalevents.py", line 39, in create
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return
raw=True)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 169, in _create
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova _resp, body = self.api.client.post(url, body=body)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 176, in post
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 91, in request
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 206, in request
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova resp = super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 95, in request
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return self.session.request(url, method, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 304, in request
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova auth_headers = self.get_auth_headers(auth)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 617, in get_auth_headers
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return auth.get_headers(self, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/base.py", line 142, in get_headers
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova token = self.get_token(session)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 200, in get_token
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return self.get_access(session).auth_token
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 240, in get_access
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova self.auth_ref = self.get_auth_ref(session)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 186, in get_auth_ref
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return self._plugin.get_auth_ref(session, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/v3/base.py", line 190, in get_auth_ref
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova authenticated=False, log=False, **rkwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 501, in post
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 401, in request
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova raise exceptions.from_response(resp, method, url)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova BadRequest: Expecting to find id or name in user - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-0a9e36df-420c-46f2-a523-c168f0c295c6)
2016-04-20 18:35:35.023 2699 ERROR neutron.notifiers.nova
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'67291fab-d2d6-42ec-ae4e-6e5ed60fa424', 'name': 'network-vif-plugged', 'server_uuid': u'ae94da8c-3fe6-44d6-93e5-b84a606c725c'}]
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova Traceback (most recent call last):
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py", line 247, in send_events
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova batched_events)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/v2/contrib/server_external_events.py", line 39, in create
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return_raw=True)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 169, in _create
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova _resp, body = self.api.client.post(url, body=body)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 176, in post
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 91, in request
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 206, in request
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova resp = super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 95, in request
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return self.session.request(url, method, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 304, in request
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova auth_headers = self.get_auth_headers(auth)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 617, in get_auth_headers
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return auth.get_headers(self, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/base.py", line 142, in get_headers
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova token = self.get_token(session)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 200, in get_token
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return self.get_access(session).auth_token
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 240, in get_access
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova self.auth_ref = self.get_auth_ref(session)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 186, in get_auth_ref
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return self._plugin.get_auth_ref(session, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/v3/base.py", line 190, in get_auth_ref
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova authenticated=False, log=False, **rkwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 501, in post
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 401, in request
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova raise exceptions.from_response(resp, method, url)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova BadRequest: Expecting to find id or name in user - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-7e1674f8-70f3-4c45-b5e1-3c6739bc745f)
2016-04-20 18:38:00.063 2701 ERROR neutron.notifiers.nova
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'tag': u'67291fab-d2d6-42ec-ae4e-6e5ed60fa424', 'name': 'network-vif-deleted', 'server_uuid': u'ae94da8c-3fe6-44d6-93e5-b84a606c725c'}]
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova Traceback (most recent call last):
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/neutron/notifiers/nova.py", line 247, in send_events
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova batched_events)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/v2/contrib/server_external_events.py", line 39, in create
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return_raw=True)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/base.py", line 169, in _create
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova _resp, body = self.api.client.post(url, body=body)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 176, in post
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/novaclient/client.py", line 91, in request
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 206, in request
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova resp = super(LegacyJsonAdapter, self).request(*args, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/adapter.py", line 95, in request
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return self.session.request(url, method, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 304, in request
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova auth_headers = self.get_auth_headers(auth)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 617, in get_auth_headers
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return auth.get_headers(self, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/base.py", line 142, in get_headers
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova token = self.get_token(session)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 200, in get_token
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return self.get_access(session).auth_token
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/base.py", line 240, in get_access
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova self.auth_ref = self.get_auth_ref(session)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/generic/base.py", line 186, in get_auth_ref
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return self._plugin.get_auth_ref(session, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/auth/identity/v3/base.py", line 190, in get_auth_ref
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova authenticated=False, log=False, **rkwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 501, in post
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return self.request(url, 'POST', **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 337, in inner
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova return func(*args, **kwargs)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 401, in request
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova raise exceptions.from_response(resp, method, url)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova BadRequest: Expecting to find id or name in user - the server could not comply with the request since it is either malformed or otherwise incorrect. The client is assumed to be in error. (HTTP 400) (Request-ID: req-022851be-63e5-4f22-851d-60536516b686)
2016-04-20 18:42:59.448 2699 ERROR neutron.notifiers.nova

It's not obvious to me how to fix this problem. Can someone please provide some guidance? What else should I look at? What service is nova calling when it times out? What is the "BadRequest" about? (where can I find the actual request? and what should it look like?)

Any help would be appreciated...
Bond
!DSPAM:1,571839d9243111631916134! _______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

!DSPAM:1,571839d9243111631916134!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/1161ca94/attachment-0001.html


Message: 4
Date: Thu, 21 Apr 2016 09:04:56 -0500
From: Paras pradhan pradhanparas@gmail.com
To: Eugen Block eblock@nde.ag
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Xenial / Mitaka = Instance failed network
setup / nova.compute.manager Unauthorized
Message-ID:
CADyt5g=WGvTVMsh9n_+g7etD-=dArgVy2cpapsihWK66vxJioQ@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

Yes . I did. here is my nova.conf. Can you share yours?
http://paste.openstack.org/show/494988/

On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block eblock@nde.ag wrote:

Okay, did you restart the respective services on all nodes after the
changes in your config files? If the same error still occurs then you might
haven't found all occurrences of the option auth_plugin, did you replace it
in all config files? I'm just guessing here...

Zitat von Paras pradhan pradhanparas@gmail.com:

No I still have that error. Other than that I don't see any other errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block eblock@nde.ag wrote:

So I guess the mentioned error should be resolved? Does it work now?

Zitat von Paras pradhan pradhanparas@gmail.com:

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block eblock@nde.ag wrote:

And did you change it to authtype instead of authplugin? Also you
should

make sure that this option is in the correct section of your config
file,
for example

[keystoneauthtoken]
...
auth
type = password

or

[neutron]
...
auth_type = password

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block eblock@nde.ag wrote:

Hi Paras,

the option auth_plugin is deprecated (from nova.conf):

---cut here---

Authentication type to load (unknown value)

Deprecated group/name - [DEFAULT]/auth_plugin

auth_type = password
---cut here---

But as far as I can tell, you should only get a warning, not an
error,
I've seen some of these warnings in my logs, but it works (I work
with
openSUSE). To get Mitaka working at all I simply tried to set the
same
options as in my working Liberty configs, and then I searched for
deprecation warnings and additional options mentioned in the Mitaka
guide.

Hope this helps!

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Can somebody share the nova.conf and neutron.conf from working
mitaka?
I
am

also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.

Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
nasir.mahmood@gmail.com
>
wrote:

Martinx,

glad to see that you are able to dig into the typo issue. I

remember, I
had to completely re-re-clean install my virtual setup of OpenStack
for a
POC back in 2015 , just because I have had miss-configured my
neutron.conf's mysql DB connector information.

Cheers!

Regards,
Nasir Mahmood

On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

FIXED!! I knew it was a typo somewhere! LOL

https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02

Thank you guys!

Sorry about the buzz on TWO mail lists...

At least, now we know that Nova silent fail on its start up, if
somethings aren't configured according... And there is no
verification
steps to test the communication between Nova and Neutron.

Mitaka is working now on Xenial! YAY!!

I'm about to commit changes to enable OpenvSwitch with DPDK and
multi-node deployments, fully automated!

Cheers!
Thiago

On 17 April 2016 at 21:26, Martinx - ????? <
thiagocmartinsc@gmail.com
>
wrote:

On 17 April 2016 at 17:39, Martinx - ????? <
thiagocmartinsc@gmail.com
>

wrote:

Guys,

I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using

the
following document:

http://docs.openstack.org/mitaka/install-guide-ubuntu

Yes, I know, the above document is for installing Mitaka on top
of
Ubuntu 14.04 but, from what I understand, the only difference is
that
on
Xenial, there is no need to add the Ubuntu Mitaka Cloud Archive,
since
Mitaka is the default on Xenial, so, I can follow that document,
right?
=)

At first, OpenStack installation goes okay, without any errors,
all
services comes up, etc... However, it is not possible to launch
an
Instance.

*** Errors on launching the Instance:

  • Right after launching it:

    https://paste.ubuntu.com/15902503/

  • Spawning it, after Glance finishes the download, similar
    error
    a
    second time:

    https://paste.ubuntu.com/15902556/

    What am I missing?

    Apparently, Nova is not authorized to talk with Neutron but, I
    am
    following the docs (maybe it is just a typo somewhere?)...

    Also, I have an Ansible automation to deploy it, so, it is less
    error
    prone. And however can help me, will see how I am deploying it.

    I see no error on Admin Dashboard, all services are up.

    NOTE: My Ansible playbooks is in a sense, "
    docs.openstack.org/mitaka/install-guide-ubuntu fully
    automated",
    it
    is
    very close to it, step-by-step.

    How can I debug this? I mean, how can I try to do, what Nova is
    doing
    (its connection with Neutron), to make sure that the settings
    are
    in
    place
    correctly?

    Here is how I am installing Mitaka on Xenial:


1- Install Ubuntu 16.04 server 64-bit on bare-metal;
  • Configure your /etc/hostname and /etc/hosts.

    DETAILS:
    https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md

    2- Clone the automation:

    cd ~
    git clone https://github.com/tmartinx/svauto.git

    3- Run the automation to install OpenStack (all-in-one)

    cd ~/svauto

    ./os-deploy.sh --br-mode=LBR --use-dummies --base-os=ubuntu16
    --base-os-upgrade=yes --openstack-release=mitaka
    --openstack-installation
    --dry-run

    ansible-playbook -c local site-openstack.yml --extra-vars
    "openstack_installation=yes"


    NOTE: If you don't use "--dry-run" option, Ansible will be
    executed
    automatically by "os-deploy.sh".

    I am sharing the Ansible playbooks, because it will be easier
    to
    see
    what I am doing.

    About the relevant configuration blocks, I believe that I have
    it
    properly configured (I followed Mitaka docs), like this:

    • neutron.conf:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
-

  • nova.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
-

I already installed OpenStack many, many, many times, since
Havana
release, I'm confident that I am doing it right but, of course,
maybe
I did
something wrong this time... =P

I appreciate any help!

Thanks!
Thiago

Hey guys,

I am reviewing everything, to make sure that my automation
matches
docs.openstack.org/mitaka/install-guide-ubuntu/ in details.

Two things...


1- All the verification steps (from official doc) passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html
- passed (mine doesn't have /horizon)

http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html
- passed but, I'm not using any cinder-volume yet

http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html
- "6. Launch the instance" - FAIL

NOTE: I can create Networks, Subnets, Routers... I can see the
Linux
Namespaces at the Neutron L3 Router (All-in-One)

2- This problem happen no matter if deploying it with Linux
Bridges
(--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS)


So, I think that OpenStack should provide more verification
steps,
specially to test the communication / authentication between its
different
projects, for example:

A- Does Nova can communicate with Neutron? How to test this?

B- Can Nova download images from Glance? Etc...

Doing more reviews now...

Cheers!
Thiago


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Nasir Mahmood


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/1e36b676/attachment-0001.html


Message: 5
Date: Thu, 21 Apr 2016 14:47:51 +0000
From: Jean-Pierre Ribeauville jpribeauville@axway.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: [Openstack] issue when launching instance
Message-ID:
1051EFB4D3A1704680C38CCAAC5836D292F1BEF0@WPTXMAIL2.ptx.axway.int
Content-Type: text/plain; charset="us-ascii"

Hi,

I just installed RDO all-in one( KILO release) on a Centos 7 .

Installation is OK.
Image creation also.

But when trying to launch an cirrus ( or fedora22) instance I got following error :

Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-2c739a95-5974-423f-b01c-da832f3a027d)

FYI, nova-api.log shows this error :

2016-04-21 10:16:40.176 4080 INFO nova.api.openstack [req-2c739a95-5974-423f-b01c-da832f3a027d e41c083d61d44b30ab24e13a889d8093 233c7454196b467580d8d68a6113ba6b - - -] http://..... /v2/233c7454196b467580d8d68a6113ba6b/servers returned with HTTP 500http://.....%20/v2/233c7454196b467580d8d68a6113ba6b/servers%20returned%20with%20HTTP%20500

Nova service list :

nova-manage service list
nova-consoleauth internal enabled :-) 2016-04-21 14:42:49
nova-scheduler internal enabled :-) 2016-04-21 14:42:47
nova-conductor internal enabled :-) 2016-04-21 14:42:48
nova-compute nova enabled :-) 2016-04-21 14:42:48
nova-cert internal enabled :-) 2016-04-21 14:42:48

Any idea what it could be ?

Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axwaylogotagline_87px]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/74d1f975/attachment-0001.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11720 bytes
Desc: image001.png
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/74d1f975/attachment-0001.png


Message: 6
Date: Thu, 21 Apr 2016 11:58:12 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: Paras pradhan pradhanparas@gmail.com
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Xenial / Mitaka = Instance failed network
setup / nova.compute.manager Unauthorized
Message-ID:
CAJSM8J1pyS1MGDZ7zgKAqtwuzF13+CCVPTLO1pMi6QhwNepkvA@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

My nova.conf is this one:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf

However, I'm facing connectivity problems when with OpenvSwitch
deployments, investigating it now...

On 21 April 2016 at 11:04, Paras pradhan pradhanparas@gmail.com wrote:

Yes . I did. here is my nova.conf. Can you share yours?
http://paste.openstack.org/show/494988/

On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block eblock@nde.ag wrote:

Okay, did you restart the respective services on all nodes after the
changes in your config files? If the same error still occurs then you might
haven't found all occurrences of the option auth_plugin, did you replace it
in all config files? I'm just guessing here...

Zitat von Paras pradhan pradhanparas@gmail.com:

No I still have that error. Other than that I don't see any other errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block eblock@nde.ag wrote:

So I guess the mentioned error should be resolved? Does it work now?

Zitat von Paras pradhan pradhanparas@gmail.com:

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block eblock@nde.ag wrote:

And did you change it to authtype instead of authplugin? Also you
should

make sure that this option is in the correct section of your config
file,
for example

[keystoneauthtoken]
...
auth
type = password

or

[neutron]
...
auth_type = password

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block eblock@nde.ag wrote:

Hi Paras,

the option auth_plugin is deprecated (from nova.conf):

---cut here---

Authentication type to load (unknown value)

Deprecated group/name - [DEFAULT]/auth_plugin

auth_type = password
---cut here---

But as far as I can tell, you should only get a warning, not an
error,
I've seen some of these warnings in my logs, but it works (I work
with
openSUSE). To get Mitaka working at all I simply tried to set the
same
options as in my working Liberty configs, and then I searched for
deprecation warnings and additional options mentioned in the Mitaka
guide.

Hope this helps!

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Can somebody share the nova.conf and neutron.conf from working
mitaka?
I
am

also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.

Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
nasir.mahmood@gmail.com
>
wrote:

Martinx,

glad to see that you are able to dig into the typo issue. I

remember, I
had to completely re-re-clean install my virtual setup of
OpenStack
for a
POC back in 2015 , just because I have had miss-configured my
neutron.conf's mysql DB connector information.

Cheers!

Regards,
Nasir Mahmood

On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

FIXED!! I knew it was a typo somewhere! LOL

https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02

Thank you guys!

Sorry about the buzz on TWO mail lists...

At least, now we know that Nova silent fail on its start up, if
somethings aren't configured according... And there is no
verification
steps to test the communication between Nova and Neutron.

Mitaka is working now on Xenial! YAY!!

I'm about to commit changes to enable OpenvSwitch with DPDK and
multi-node deployments, fully automated!

Cheers!
Thiago

On 17 April 2016 at 21:26, Martinx - ????? <
thiagocmartinsc@gmail.com
>
wrote:

On 17 April 2016 at 17:39, Martinx - ????? <
thiagocmartinsc@gmail.com
>

wrote:

Guys,

I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using

the
following document:

http://docs.openstack.org/mitaka/install-guide-ubuntu

Yes, I know, the above document is for installing Mitaka on
top
of
Ubuntu 14.04 but, from what I understand, the only difference
is
that
on
Xenial, there is no need to add the Ubuntu Mitaka Cloud
Archive,
since
Mitaka is the default on Xenial, so, I can follow that
document,
right?
=)

At first, OpenStack installation goes okay, without any
errors,
all
services comes up, etc... However, it is not possible to
launch an
Instance.

*** Errors on launching the Instance:

  • Right after launching it:

    https://paste.ubuntu.com/15902503/

  • Spawning it, after Glance finishes the download, similar
    error
    a
    second time:

    https://paste.ubuntu.com/15902556/

    What am I missing?

    Apparently, Nova is not authorized to talk with Neutron but,
    I am
    following the docs (maybe it is just a typo somewhere?)...

    Also, I have an Ansible automation to deploy it, so, it is
    less
    error
    prone. And however can help me, will see how I am deploying it.

    I see no error on Admin Dashboard, all services are up.

    NOTE: My Ansible playbooks is in a sense, "
    docs.openstack.org/mitaka/install-guide-ubuntu fully
    automated",
    it
    is
    very close to it, step-by-step.

    How can I debug this? I mean, how can I try to do, what Nova
    is
    doing
    (its connection with Neutron), to make sure that the settings
    are
    in
    place
    correctly?

    Here is how I am installing Mitaka on Xenial:


1- Install Ubuntu 16.04 server 64-bit on bare-metal;
  • Configure your /etc/hostname and /etc/hosts.

    DETAILS:
    https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md

    2- Clone the automation:

    cd ~
    git clone https://github.com/tmartinx/svauto.git

    3- Run the automation to install OpenStack (all-in-one)

    cd ~/svauto

    ./os-deploy.sh --br-mode=LBR --use-dummies
    --base-os=ubuntu16
    --base-os-upgrade=yes --openstack-release=mitaka
    --openstack-installation
    --dry-run

    ansible-playbook -c local site-openstack.yml --extra-vars
    "openstack_installation=yes"


    NOTE: If you don't use "--dry-run" option, Ansible will be
    executed
    automatically by "os-deploy.sh".

    I am sharing the Ansible playbooks, because it will be easier
    to
    see
    what I am doing.

    About the relevant configuration blocks, I believe that I
    have it
    properly configured (I followed Mitaka docs), like this:

    • neutron.conf:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
-

  • nova.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
-

I already installed OpenStack many, many, many times, since
Havana
release, I'm confident that I am doing it right but, of course,
maybe
I did
something wrong this time... =P

I appreciate any help!

Thanks!
Thiago

Hey guys,

I am reviewing everything, to make sure that my automation
matches
docs.openstack.org/mitaka/install-guide-ubuntu/ in details.

Two things...


1- All the verification steps (from official doc) passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html
- passed (mine doesn't have /horizon)

http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html
- passed but, I'm not using any cinder-volume yet

http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html
- "6. Launch the instance" - FAIL

NOTE: I can create Networks, Subnets, Routers... I can see the
Linux
Namespaces at the Neutron L3 Router (All-in-One)

2- This problem happen no matter if deploying it with Linux
Bridges
(--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS)


So, I think that OpenStack should provide more verification
steps,
specially to test the communication / authentication between its
different
projects, for example:

A- Does Nova can communicate with Neutron? How to test this?

B- Can Nova download images from Glance? Etc...

Doing more reviews now...

Cheers!
Thiago


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Nasir Mahmood


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/50ce91c7/attachment-0001.html


Message: 7
Date: Thu, 21 Apr 2016 08:07:43 -0700
From: Remo Mattei Remo@Italy1.com
To: Jean-Pierre Ribeauville jpribeauville@axway.com
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] issue when launching instance
Message-ID: 20F4F222-2F51-4ED6-8556-11E75EEF4A52@Italy1.com
Content-Type: text/plain; charset="us-ascii"

I did find some issues I suggest to use the latest mitaka tested all week works OK

Inviato da iPhone

Il giorno 21 apr 2016, alle ore 07:47, Jean-Pierre Ribeauville jpribeauville@axway.com ha scritto:

Hi,

I just installed RDO all-in one( KILO release) on a Centos 7 .

Installation is OK.
Image creation also.

But when trying to launch an cirrus ( or fedora22) instance I got following error :

Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-2c739a95-5974-423f-b01c-da832f3a027d)


FYI, nova-api.log shows this error :

2016-04-21 10:16:40.176 4080 INFO nova.api.openstack [req-2c739a95-5974-423f-b01c-da832f3a027d e41c083d61d44b30ab24e13a889d8093 233c7454196b467580d8d68a6113ba6b - - -] http://..... /v2/233c7454196b467580d8d68a6113ba6b/servers returned with HTTP 500

Nova service list :


nova-manage service list
nova-consoleauth internal enabled :-) 2016-04-21 14:42:49
nova-scheduler internal enabled :-) 2016-04-21 14:42:47
nova-conductor internal enabled :-) 2016-04-21 14:42:48
nova-compute nova enabled :-) 2016-04-21 14:42:48
nova-cert internal enabled :-) 2016-04-21 14:42:48


Any idea what it could be ?

Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

<image001.png>

!DSPAM:1,5718eb0099891453559995!


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

!DSPAM:1,5718eb0099891453559995!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/ae1adfe5/attachment-0001.html


Message: 8
Date: Thu, 21 Apr 2016 17:10:22 +0200
From: Eugen Block eblock@nde.ag
To: openstack@lists.openstack.org
Subject: Re: [Openstack] issue when launching instance
Message-ID: 20160421171022.Horde.23qZKyumwrOZuqGxc1MdW2R@www3.nde.ag
Content-Type: text/plain; charset=utf-8; format=flowed; DelSp=Yes

Hi,

I have a three node setup, controller, compute (actually I have two
compute nodes) and a storage node. I remember this error message when
my storage node had problems getting cinder-volume service up and
running. After changing config files and restarting services or
rebooting my nodes the first thing I do is checking service status for
nova, neutron and cinder. I see your nova services are up and running,
what about

control1:# cinder service-list
+------------------+--------------+------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State |
Updated_at | Disabled Reason |
+------------------+--------------+------+---------+-------+----------------------------+-----------------+
| cinder-scheduler | control1 | nova | enabled | up |
2016-04-21T15:08:15.000000 | - |
| cinder-volume | ndesan04@rbd | nova | enabled | up |
2016-04-21T15:08:17.000000 | - |
+------------------+--------------+------+---------+-------+----------------------------+-----------------+

and

control1:# neutron agent-list
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| id | agenttype | host
| alive | admin
state_up | binary |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
| 2639c986-0af9-4360-8d79-ce4627e867cf | DHCP agent | control1
| :-) | True | neutron-dhcp-agent |
| 46a63d1e-603a-41a0-ae13-fbbe0705c29e | Linux bridge agent | control1
| :-) | True | neutron-linuxbridge-agent |
| 6f2dfbb6-9563-48aa-84b7-1310af9129bc | Linux bridge agent | compute1
| :-) | True | neutron-linuxbridge-agent |
| 953a186e-bbce-4265-8c5e-bd53eb13ae61 | Metadata agent | control1
| :-) | True | neutron-metadata-agent |
| a6f7e98d-5ddc-46b7-9614-3bbd8f1a59d0 | L3 agent | control1
| :-) | True | neutron-l3-agent |
| b57d83d9-a348-4c66-a455-cb96a264859f | Linux bridge agent | compute2
| :-) | True | neutron-linuxbridge-agent |
+--------------------------------------+--------------------+----------+-------+----------------+---------------------------+

Regards,
Eugen

Zitat von Jean-Pierre Ribeauville jpribeauville@axway.com:

Hi,

I just installed RDO all-in one( KILO release) on a Centos 7 .

Installation is OK.
Image creation also.

But when trying to launch an cirrus ( or fedora22) instance I got
following error :

Error: The server has either erred or is incapable of performing the
requested operation. (HTTP 500) (Request-ID:
req-2c739a95-5974-423f-b01c-da832f3a027d)

FYI, nova-api.log shows this error :

2016-04-21 10:16:40.176 4080 INFO nova.api.openstack
[req-2c739a95-5974-423f-b01c-da832f3a027d
e41c083d61d44b30ab24e13a889d8093 233c7454196b467580d8d68a6113ba6b -
- -] http://..... /v2/233c7454196b467580d8d68a6113ba6b/servers
returned with HTTP
500http://.....%20/v2/233c7454196b467580d8d68a6113ba6b/servers%20returned%20with%20HTTP%20500

Nova service list :

nova-manage service list
nova-consoleauth internal enabled :-) 2016-04-21 14:42:49
nova-scheduler internal enabled :-) 2016-04-21 14:42:47
nova-conductor internal enabled :-) 2016-04-21 14:42:48
nova-compute nova enabled :-) 2016-04-21 14:42:48
nova-cert internal enabled :-) 2016-04-21 14:42:48

Any idea what it could be ?

Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axwaylogotagline_87px]

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

     Vorsitzende des Aufsichtsrates: Angelika Mozdzen
       Sitz und Registergericht: Hamburg, HRB 90934
               Vorstand: Jens-U. Mozdzen
                USt-IdNr. DE 814 013 983

Message: 9
Date: Thu, 21 Apr 2016 15:16:24 +0000
From: Jean-Pierre Ribeauville jpribeauville@axway.com
To: Remo Mattei Remo@Italy1.com
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] issue when launching instance
Message-ID:
1051EFB4D3A1704680C38CCAAC5836D292F1BF73@WPTXMAIL2.ptx.axway.int
Content-Type: text/plain; charset="utf-8"

Hi,

I tried mitaka yesterday but , by using this release , my system is totally overloades when running Openstatck.

By running top command , wait time is >60% when trying to list images or instances .

I don?t have this issue with kilo.

Regards,

J.P.

From: Remo Mattei [mailto:Remo@Italy1.com]
Sent: jeudi 21 avril 2016 17:08
To: Jean-Pierre Ribeauville jpribeauville@axway.com
Cc: openstack@lists.openstack.org
Subject: Re: [Openstack] issue when launching instance

I did find some issues I suggest to use the latest mitaka tested all week works OK

Inviato da iPhone

Il giorno 21 apr 2016, alle ore 07:47, Jean-Pierre Ribeauville <jpribeauville@axway.comjpribeauville@axway.com> ha scritto:
Hi,

I just installed RDO all-in one( KILO release) on a Centos 7 .

Installation is OK.
Image creation also.

But when trying to launch an cirrus ( or fedora22) instance I got following error :

Error: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-2c739a95-5974-423f-b01c-da832f3a027d)

FYI, nova-api.log shows this error :

2016-04-21 10:16:40.176 4080 INFO nova.api.openstack [req-2c739a95-5974-423f-b01c-da832f3a027d e41c083d61d44b30ab24e13a889d8093 233c7454196b467580d8d68a6113ba6b - - -] http://..... /v2/233c7454196b467580d8d68a6113ba6b/servers returned with HTTP 500http://.....%20/v2/233c7454196b467580d8d68a6113ba6b/servers%20returned%20with%20HTTP%20500

Nova service list :

nova-manage service list
nova-consoleauth internal enabled :-) 2016-04-21 14:42:49
nova-scheduler internal enabled :-) 2016-04-21 14:42:47
nova-conductor internal enabled :-) 2016-04-21 14:42:48
nova-compute nova enabled :-) 2016-04-21 14:42:48
nova-cert internal enabled :-) 2016-04-21 14:42:48

Any idea what it could be ?

Thx for help.

Regards,

Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

<image001.png>

!DSPAM:1,5718eb0099891453559995!


Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.orgopenstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

!DSPAM:1,5718eb0099891453559995!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/01912427/attachment-0001.html


Message: 10
Date: Thu, 21 Apr 2016 15:52:18 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: [Openstack] Mitaka with OpenvSwitch, no VXLAN tunnels between
compute and network nodes
Message-ID:
CAJSM8J0oyXYZtF2WCU1N_RYoTneQ8HCzgV=4nSfJPU67qxcDZA@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

Guys,

I'm trying to deploy Mitaka on Xenial, using OpenvSwitch.

I am using the following documents:

http://docs.openstack.org/mitaka/install-guide-ubuntu

http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html

  • The topology is like this:

    1- Controller + Network Node;

    2- Compute Node.

    NOTE: Both have two NICs, em1 for management and services, and p1p1 for
    VXLAN tunnels.

    However, I see no "vxlan peers" on the output of "ovs-vsctl show"...

    So, Instances doesn't get IP from DHCP server, and if I try to configure
    static IPs, Instances can only talk with each other (that are running on
    the same, and uniq, compute node). Also, instances can't ping Neutron L2
    Namespace router.

    What I am missing?

Thanks!
Thiago
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/2a436e2f/attachment-0001.html


Message: 11
Date: Thu, 21 Apr 2016 15:54:31 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Mitaka with OpenvSwitch, no VXLAN tunnels
between compute and network nodes
Message-ID:
CAJSM8J3utbpbMsQBs01C76j88PY8ozXTH=WtHNKF_5_fsjD8CA@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

On 21 April 2016 at 15:52, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

Guys,

I'm trying to deploy Mitaka on Xenial, using OpenvSwitch.

I am using the following documents:

http://docs.openstack.org/mitaka/install-guide-ubuntu

http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html

  • The topology is like this:

    1- Controller + Network Node;

    2- Compute Node.

    NOTE: Both have two NICs, em1 for management and services, and p1p1 for
    VXLAN tunnels.

    However, I see no "vxlan peers" on the output of "ovs-vsctl show"...

    So, Instances doesn't get IP from DHCP server, and if I try to configure
    static IPs, Instances can only talk with each other (that are running on
    the same, and uniq, compute node). Also, instances can't ping Neutron L2
    Namespace router.

    What I am missing?

Thanks!
Thiago

BTW, I am using an Ansibe automation tool that I created for this. If I use
the same roles, to deploy an "All in One" OpenStack box, with OpenvSwitch,
of course, it works!

Only when I split the Compute Node, out from the "Controller+Network" node,
that it doesn't work anymore...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/5ec9a6c8/attachment-0001.html


Message: 12
Date: Thu, 21 Apr 2016 16:05:03 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Mitaka with OpenvSwitch, no VXLAN tunnels
between compute and network nodes
Message-ID:
CAJSM8J1enyq0pBCSLP7HCijOu5h3nErnjiq8qMOgcr9Lrk9Duw@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

On 21 April 2016 at 15:54, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

On 21 April 2016 at 15:52, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

Guys,

I'm trying to deploy Mitaka on Xenial, using OpenvSwitch.

I am using the following documents:

http://docs.openstack.org/mitaka/install-guide-ubuntu

http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html

  • The topology is like this:

    1- Controller + Network Node;

    2- Compute Node.

    NOTE: Both have two NICs, em1 for management and services, and p1p1 for
    VXLAN tunnels.

    However, I see no "vxlan peers" on the output of "ovs-vsctl show"...

    So, Instances doesn't get IP from DHCP server, and if I try to configure
    static IPs, Instances can only talk with each other (that are running on
    the same, and uniq, compute node). Also, instances can't ping Neutron L2
    Namespace router.

    What I am missing?

Thanks!
Thiago

BTW, I am using an Ansibe automation tool that I created for this. If I
use the same roles, to deploy an "All in One" OpenStack box, with
OpenvSwitch, of course, it works!

Only when I split the Compute Node, out from the "Controller+Network"
node, that it doesn't work anymore...

Also, I can create the Network and its Subnet, the Router attached to both
"External Net" and with a internal interface...

All network agents are up and running...

But, VXLAN tunnels, no connectivity....
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/17061017/attachment-0001.html


Message: 13
Date: Thu, 21 Apr 2016 15:08:39 -0400
From: Corey Bryant corey.bryant@canonical.com
To: Openstack openstack@lists.openstack.org,
openstack-operators@lists.openstack.org,
ubuntu-server@lists.ubuntu.com
Subject: [Openstack] OpenStack Mitaka for Ubuntu 14.04 LTS and Ubuntu
16.04 LTS
Message-ID:
CADn0iZ3m_gS+ZbVNfgVoLfjP=_XFy2Oq=TgwBqbGxQmMtMFcZw@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

Hi All,

The Ubuntu OpenStack Engineering team is pleased to announce the general
availability of OpenStack Mitaka in Ubuntu 16.04 LTS and for Ubuntu 14.04
LTS via the Ubuntu Cloud Archive.

Ubuntu 14.04 LTS


You can enable the Ubuntu Cloud Archive for OpenStack Mitaka on Ubuntu
14.04 installations by running the following commands (make sure you have
an up-to-date software-properties-common package first):

sudo add-apt-repository cloud-archive:mitaka
sudo apt-get update

The Ubuntu Cloud Archive for Mitaka includes updates for Nova, Glance,
Keystone, Neutron, Neutron-FWaaS, Neutron-LBaaS, Neutron-VPNaaS, Cinder,
Swift, Horizon, Ceilometer, Aodh, Heat, Designate, Barbican, Manila,
Mistral, Murano, Ironic, Trove, Sahara, Senlin, and Zaqar; Ceph (10.1.2),
Nova-LXD (13.0.0), RabbitMQ (3.5.7), QEMU (1.2.5), libvirt (1.3.1),
OpenvSwitch (2.5.0) and DPDK (2.2.0) backports from Ubuntu 16.04
development have also been provided.

You can see the full list of packages and versions at [0].

Ubuntu 16.04 LTS


No extra steps are required; just start installing OpenStack!

Release notes for Ubuntu 16.04 LTS can be found at [1].

Reporting bugs


If you have any issues, please report bugs using the 'ubuntu-bug' tool:

sudo ubuntu-bug nova-conductor

This will ensure that bugs get logged in the right place in Launchpad.

Also feel free to poke anyone on our team in #ubuntu-server (coreycb,
ddellav, beisner, jamespage) if you have any issues.

Finally, thank you to the entire OpenStack community and everyone who's
made OpenStack Mitaka a reality!

[0]
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/mitaka_versions.html
[1] https://wiki.ubuntu.com/XenialXerus/ReleaseNotes

--
Regards,
Corey Bryant
Ubuntu Core Developer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/fa48b54c/attachment-0001.html


Message: 14
Date: Thu, 21 Apr 2016 19:15:07 +0000 (UTC)
From: Farhad Sunavala fsbiz@yahoo.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: [Openstack] Openstack security - port-security,
security-groups with added container
Message-ID:
68469257.3987722.1461266107105.JavaMail.yahoo@mail.yahoo.com
Content-Type: text/plain; charset="utf-8"

Hi folks,
My setup is as follows.

SRC ? ?C ?DST| ? ? ? ? ? ? | ? ? ? |?OpenvSwitch
SRC VM = 192.168.0.3DST VM = 192.168.0.4
Container C = 192.168.0.5

Openstack version: latest from masterOpenvSwitch: 2.4.1

Openstack brings up SRC (192.168.0.3) and DST VM (192.168.0.5)I manually bringup container C using docker and connect it to br-int.I allocate a neutron port (192.168.0.5) and configure this IP address on the container C.
SRC,DST VMs work fine.Now, my problem is that the container C is not able to pass traffic.
Troubleshooting reveals it is sending packet to br-int, it hits the NORMAL action?flows on br-int but then br-int does not transmit them forward.I have disabled security-groups and port-security on all ports.
It is definitely something to do with security (anti-spoofing) but I am not able to narrow it down.Any pointers will be appreciated.
Thanks,Farhad.
Details of troubleshooting:
Setup:
SRC ? ?C ?DST| ? ? ? ? ? ? | ? ? ? |?OpenvSwitch
SRC VM = 192.168.0.3DST VM = 192.168.0.4
Container C = 192.168.0.5

root@fs-10-145-105-64:~# neutron port-list+--------------------------------------+------+-------------------+-------------------------------------------------------+| id ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? | name | macaddress ? ? ? | fixedips ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? |+--------------------------------------+------+-------------------+-------------------------------------------------------+| 31d7fef4-2689-40d5-886c-b0419295eabb | ? ? ?| fa:16:3e:e7:f8:47 | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", || ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| ? ? ?| ? ? ? ? ? ? ? ? ? | "ipaddress": "192.168.0.4"} ? ? ? ? ? ? ? ? ? ? ? ? ?|| 3466abf1-aa9a-420a-bb9b-c4ad55561f19 | ? ? ?| fa:16:3e:84:62:af | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", || ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| ? ? ?| ? ? ? ? ? ? ? ? ? | "ipaddress": "192.168.0.2"} ? ? ? ? ? ? ? ? ? ? ? ? ?|| 50686370-de40-4665-a5a1-39b5b795122b | ? ? ?| fa:16:3e:0d:ae:bc | {"subnetid": "19c6dc03-b25
5-45e9-9bd7-366631b745b6", || ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| ? ? ?| ? ? ? ? ? ? ? ? ? | "ip
address": "192.168.0.5"} ? ? ? ? ? ? ? ? ? ? ? ? ?|| c6043a1e-ac4d-4138-af14-b91ae8e4d57e | ? ? ?| fa:16:3e:36:95:77 | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", || ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| ? ? ?| ? ? ? ? ? ? ? ? ? | "ipaddress": "192.168.0.1"} ? ? ? ? ? ? ? ? ? ? ? ? ?|| e8a167b1-8457-4bd7-a18b-82712e0c46dd | ? ? ?| fa:16:3e:85:92:ee | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", || ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?| ? ? ?| ? ? ? ? ? ? ? ? ? | "ipaddress": "192.168.0.3"} ? ? ? ? ? ? ? ? ? ? ? ? ?|+--------------------------------------+------+-------------------+-------------------------------------------------------+root@fs-10-145-105-64:~# neutron port-show e8a167b1-8457-4bd7-a18b-82712e0c46dd+-----------------------+------------------------------------------------------------------------------------+| Field ? ? ? ? ? ? ? ? | Value ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+------------------------------------------------------------------------------------+| adminstateup ? ? ? ?| True ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || allowedaddresspairs | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:hostid ? ? ? | fs-10-145-105-64 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:profile ? ? ? | {} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:vifdetails ? | {"portfilter": true, "ovshybridplug": false} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:viftype ? ? ?| ovs ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:vnictype ? ? | normal ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || createdat ? ? ? ? ? ?| 2016-04-21T15:27:51 ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| description ? ? ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| deviceid ? ? ? ? ? ? | 1a65bcfb-4607-4529-a313-6927d86c9302 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || deviceowner ? ? ? ? ?| compute:nova ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || dnsname ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| extradhcpopts ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| fixedips ? ? ? ? ? ? | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", "ipaddress": "192.168.0.3"} || id ? ? ? ? ? ? ? ? ? ?| e8a167b1-8457-4bd7-a18b-82712e0c46dd ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || macaddress ? ? ? ? ? | fa:16:3e:85:92:ee ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| name ? ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| network
id ? ? ? ? ? ?| e4c38c74-c9c2-47a7-802d-446488b82e5f ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || portsecurityenabled | True ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || securitygroups ? ? ? | fcf62b2a-1dd4-432a-b47b-5d9b79813da7 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || status ? ? ? ? ? ? ? ?| ACTIVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || tenantid ? ? ? ? ? ? | 62b9eff93cc74b65a2b52a0d41604e2c ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || updated_at ? ? ? ? ? ?| 2016-04-21T15:27:58 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+------------------------------------------------------------------------------------+

root@fs-10-145-105-64:~# neutron port-show 31d7fef4-2689-40d5-886c-b0419295eabb+-----------------------+------------------------------------------------------------------------------------+| Field ? ? ? ? ? ? ? ? | Value ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+------------------------------------------------------------------------------------+| adminstateup ? ? ? ?| True ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || allowedaddresspairs | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:hostid ? ? ? | fs-10-145-105-64 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:profile ? ? ? | {} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:vifdetails ? | {"portfilter": true, "ovshybridplug": false} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:viftype ? ? ?| ovs ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:vnictype ? ? | normal ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || createdat ? ? ? ? ? ?| 2016-04-21T15:28:37 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| description ? ? ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| deviceid ? ? ? ? ? ? | 9c8a5e3c-0867-4938-b26e-4834a24d0c5d ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || deviceowner ? ? ? ? ?| compute:nova ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || dnsname ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| extradhcpopts ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| fixedips ? ? ? ? ? ? | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", "ipaddress": "192.168.0.4"} || id ? ? ? ? ? ? ? ? ? ?| 31d7fef4-2689-40d5-8
86c-b0419295eabb ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || macaddress ? ? ? ? ? | fa:16:3e:e7:f8:47 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| name ? ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| networkid ? ? ? ? ? ?| e4c38c74-c9c2-47a7-802d-446488b82e5f ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || portsecurityenabled | False ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| securitygroups ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| status ? ? ? ? ? ? ? ?| ACTIVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || tenantid ? ? ? ? ? ? | 62b9eff93cc74b65a2b52a0d41604e2c ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || updatedat ? ? ? ? ? ?| 2016-04-21T18:25:20 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+----------------------------
--------------------------------------------------------+
root@fs-10-145-105-64:~# neutron port-show 31d7fef4-2689-40d5-886c-b0419295eabb+-----------------------+------------------------------------------------------------------------------------+| Field ? ? ? ? ? ? ? ? | Value ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+------------------------------------------------------------------------------------+| admin
stateup ? ? ? ?| True ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || allowedaddresspairs | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:hostid ? ? ? | fs-10-145-105-64 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:profile ? ? ? | {} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || binding:vifdetails ? | {"portfilter": true, "ovshybridplug": false} ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:viftype ? ? ?| ovs ? ? ? ? ?
? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| binding:vnic
type ? ? | normal ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || createdat ? ? ? ? ? ?| 2016-04-21T15:28:37 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| description ? ? ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| deviceid ? ? ? ? ? ? | 9c8a5e3c-0867-4938-b26e-4834a24d0c5d ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || deviceowner ? ? ? ? ?| compute:nova ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || dnsname ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| extradhcpopts ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| fixedips ? ? ? ? ? ? | {"subnetid": "19c6dc03-b255-45e9-9bd7-366631b745b6", "ipaddress": "192.168.0.4"} || id ? ? ? ? ? ? ? ? ? ?| 31d7fef4-2689-40d5-8
86c-b0419295eabb ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || mac
address ? ? ? ? ? | fa:16:3e:e7:f8:47 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| name ? ? ? ? ? ? ? ? ?| ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| networkid ? ? ? ? ? ?| e4c38c74-c9c2-47a7-802d-446488b82e5f ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || portsecurityenabled | False ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| securitygroups ? ? ? | ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|| status ? ? ? ? ? ? ? ?| ACTIVE ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || tenantid ? ? ? ? ? ? | 62b9eff93cc74b65a2b52a0d41604e2c ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? || updatedat ? ? ? ? ? ?| 2016-04-21T18:25:20 ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?|+-----------------------+----------------------------
--------------------------------------------------------+

root@fs-10-145-105-64:~# ovs-vsctl showcd040c9d-427b-418b-943c-7ad5522e1d8f? ? ?Bridge br-int? ? ? ? failmode: secure? ? ? ? Port "tap3466abf1-aa"? ? ? ? ? ? tag: 2? ? ? ? ? ? Interface "tap3466abf1-aa"? ? ? ? ? ? ? ? type: internal? ? ? ? Port "tape8a167b1-84"? ? ? ? ? ? tag: 2? ? ? ? ? ? Interface "tape8a167b1-84"? ? ? ? Port br-int? ? ? ? ? ? Interface br-int? ? ? ? ? ? ? ? type: internal? ? ? ? Port patch-tun? ? ? ? ? ? Interface patch-tun? ? ? ? ? ? ? ? type: patch? ? ? ? ? ? ? ? options: {peer=patch-int}? ? ? ? Port "qr-c6043a1e-ac"? ? ? ? ? ? tag: 2? ? ? ? ? ? Interface "qr-c6043a1e-ac"? ? ? ? ? ? ? ? type: internal? ? ? ? Port "vethh0"? ? ? ? ? ? Interface "veth_h0"

root@fs-10-145-105-64:~# docker psCONTAINER ID ? ? ? ?IMAGE ? ? ? ? ? ? ? COMMAND ? ? ? ? ? ? CREATED ? ? ? ? ? ? STATUS ? ? ? ? ? ? ?PORTS ? ? ? ? ? ? ? NAMES9f0a884a85eb ? ? ? ?ubuntu ? ? ? ? ? ? ?"/bin/bash" ? ? ? ? 48 minutes ago ? ? ?Up 48 minutes ? ? ? ? ? ? ? ? ? ? ? ? ? desperate_bell

root@fs-10-145-105-64:~# docker inspect -f '{{.State.Pid}}' ?9f0a884a85eb83376root@fs-10-145-105-64:~# cat /var/netns/cat: /var/netns/: No such file or directoryroot@fs-10-145-105-64:~# ls -l /var/run/netns/total 0lrwxrwxrwx 1 root root 18 Apr 21 11:18 83376 -> /proc/83376/ns/net-r--r--r-- 1 root root ?0 Apr 21 08:27 qdhcp-e4c38c74-c9c2-47a7-802d-446488b82e5f-r--r--r-- 1 root root ?0 Apr 21 08:30 qrouter-6210bb9f-9be0-49c4-b7d5-d99ca5417bfc

root@9f0a884a85eb:/# ifconfig eth0eth0 ? ? ?Link encap:Ethernet ?HWaddr 22:b3:09:8e:dd:ae? ? ? ? ? inet addr:192.168.0.5 ?Bcast:192.168.0.255 ?Mask:255.255.255.0? ? ? ? ? inet6 addr: fe80::20b3:9ff:fe8e:ddae/64 Scope:Link? ? ? ? ? UP BROADCAST RUNNING MULTICAST ?MTU:1500 ?Metric:1? ? ? ? ? RX packets:7 errors:0 dropped:0 overruns:0 frame:0? ? ? ? ? TX packets:860 errors:0 dropped:0 overruns:0 carrier:0? ? ? ? ? collisions:0 txqueuelen:1000? ? ? ? ? RX bytes:738 (738.0 B) ?TX bytes:36432 (36.4 KB)
root@fs-10-145-105-64:~# ovs-ofctl dump-flows br-intNXSTFLOW reply (xid=0x4):cookie=0xb1bf9229541d06ad, duration=13102.723s, table=0, npackets=982, nbytes=49690, idleage=38, priority=0 actions=NORMAL

root@9f0a884a85eb:/# ping 192.168.0.4PING 192.168.0.4 (192.168.0.4) 56(84) bytes of data.From 192.168.0.5 icmpseq=1 Destination Host UnreachableFrom 192.168.0.5 icmpseq=2 Destination Host UnreachableFrom 192.168.0.5 icmp_seq=3 Destination Host Unreachable

root@fs-10-145-105-64:~# tcpdump -i vethh0tcpdump: WARNING: vethh0: no IPv4 address assignedtcpdump: verbose output suppressed, use -v or -vv for full protocol decodelistening on veth_h0, link-type EN10MB (Ethernet), capture size 65535 bytes12:00:03.806091 ARP, Request who-has 192.168.0.4 tell 192.168.0.5, length 2812:00:04.805733 ARP, Request who-has 192.168.0.4 tell 192.168.0.5, length 2812:00:05.805744 ARP, Request who-has 192.168.0.4 tell 192.168.0.5, length 28

root@fs-10-145-105-64:~# ovs-ofctl dump-flows br-intNXSTFLOW reply (xid=0x4):cookie=0xb1bf9229541d06ad, duration=13102.723s, table=0, npackets=987, nbytes=49690, idleage=38, priority=0 actions=NORMAL

root@fs-10-145-105-64:~# iptables -LChain INPUT (policy ACCEPT)target ? ? prot opt source ? ? ? ? ? ? ? destination
Chain FORWARD (policy ACCEPT)target ? ? prot opt source ? ? ? ? ? ? ? destination
Chain OUTPUT (policy ACCEPT)target ? ? prot opt source ? ? ? ? ? ? ? destination

root@fs-10-145-105-64:~# conntrack -Ltcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57902 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57902 [ASSURED] mark=0 use=1tcp ? ? ?6 429701 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44449 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44449 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57894 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57894 [ASSURED] mark=0 use=1tcp ? ? ?6 431955 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=60404 dport=33608 src=127.0.0.1 dst=127.0.0.1 sport=33608 dport=60404 [ASSURED] mark=0 use=1tcp ? ? ?6 431969 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57490 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57490 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59050 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport
=59050 [ASSURED] mark=0 use=1tcp ? ? ?6 429702 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45400 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45400 [ASSURED] mark=0 use=1tcp ? ? ?6 34 TIMEWAIT src=10.145.105.64 dst=10.145.105.64 sport=59741 dport=35357 src=10.145.105.64 dst=10.145.105.64 sport=35357 dport=59741 [ASSURED] mark=0 use=1tcp ? ? ?6 428787 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45547 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45547 [ASSURED] mark=0 use=1tcp ? ? ?6 428791 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43599 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43599 [ASSURED] mark=0 use=1tcp ? ? ?6 426346 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=55546 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=55546 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59071 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59071 [ASSURED] mark=0 use=1tcp ? ? ?6 43199
0 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47750 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47750 [ASSURED] mark=0 use=1tcp ? ? ?6 431978 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47880 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47880 [ASSURED] mark=0 use=1tcp ? ? ?6 431996 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57905 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57905 [ASSURED] mark=0 use=1tcp ? ? ?6 431992 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=60530 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=60530 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=32970 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=32970 [ASSURED] mark=0 use=1tcp ? ? ?6 300 ESTABLISHED src=10.145.90.5 dst=10.145.105.64 sport=58160 dport=22 src=10.145.105.64 dst=10.145.90.5 sport=22 dport=58160 [ASSURED] mark=0 use=2tcp ? ? ?6 426277 ESTABLISHED src=12
7.0.0.1 dst=127.0.0.1 sport=43066 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43066 [ASSURED] mark=0 use=1tcp ? ? ?6 431990 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=51382 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=51382 [ASSURED] mark=0 use=1tcp ? ? ?6 431997 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=40113 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=40113 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57896 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57896 [ASSURED] mark=0 use=1tcp ? ? ?6 426232 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=49312 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=49312 [ASSURED] mark=0 use=1tcp ? ? ?6 431989 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=46646 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=46646 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59067
dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59067 [ASSURED] mark=0 use=1tcp ? ? ?6 431995 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=36486 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=36486 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59073 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59073 [ASSURED] mark=0 use=1tcp ? ? ?6 431985 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=58661 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=58661 [ASSURED] mark=0 use=1tcp ? ? ?6 431975 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47928 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47928 [ASSURED] mark=0 use=1tcp ? ? ?6 431989 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59054 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59054 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 spor
t=57917 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57917 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57910 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57910 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59065 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59065 [ASSURED] mark=0 use=1tcp ? ? ?6 428748 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43729 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43729 [ASSURED] mark=0 use=1tcp ? ? ?6 429821 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45488 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45488 [ASSURED] mark=0 use=1tcp ? ? ?6 428723 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44254 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44254 [ASSURED] mark=0 use=1tcp ? ? ?6 431976 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57888 dport=5672 src=10
.145.105.64 dst=10.145.105.64 sport=5672 dport=57888 [ASSURED] mark=0 use=1tcp ? ? ?6 431996 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=39825 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=39825 [ASSURED] mark=0 use=1tcp ? ? ?6 426277 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43235 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43235 [ASSURED] mark=0 use=1tcp ? ? ?6 431972 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57678 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57678 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59053 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59053 [ASSURED] mark=0 use=1tcp ? ? ?6 431510 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44536 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44536 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43447 dport=3306 src=127.0.0.1 dst=127.0
.0.1 sport=3306 dport=43447 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.90.5 dst=10.145.105.64 sport=58161 dport=22 src=10.145.105.64 dst=10.145.90.5 sport=22 dport=58161 [ASSURED] mark=0 use=1tcp ? ? ?6 431992 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=42017 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=42017 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59069 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59069 [ASSURED] mark=0 use=1tcp ? ? ?6 431969 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59056 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59056 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57895 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57895 [ASSURED] mark=0 use=1tcp ? ? ?6 426179 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43439 dport=3306 src=127.0.0.1 dst=127.0.
0.1 sport=3306 dport=43439 [ASSURED] mark=0 use=1tcp ? ? ?6 431994 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47758 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47758 [ASSURED] mark=0 use=1tcp ? ? ?6 431990 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=37917 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=37917 [ASSURED] mark=0 use=1tcp ? ? ?6 431965 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=33275 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=33275 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59064 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59064 [ASSURED] mark=0 use=1tcp ? ? ?6 431978 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48979 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48979 [ASSURED] mark=0 use=1tcp ? ? ?6 426281 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=52173 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=5217
3 [ASSURED] mark=0 use=1tcp ? ? ?6 431984 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57913 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57913 [ASSURED] mark=0 use=2tcp ? ? ?6 431999 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=60882 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=60882 [ASSURED] mark=0 use=1tcp ? ? ?6 431991 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57890 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57890 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.15.14 dst=10.145.105.64 sport=52275 dport=6080 src=10.145.105.64 dst=10.145.15.14 sport=6080 dport=52275 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43448 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43448 [ASSURED] mark=0 use=1tcp ? ? ?6 431993 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=42057 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport
=42057 [ASSURED] mark=0 use=1tcp ? ? ?6 431967 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=43484 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=43484 [ASSURED] mark=0 use=1tcp ? ? ?6 417924 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=40692 dport=4369 src=127.0.0.1 dst=127.0.0.1 sport=4369 dport=40692 [ASSURED] mark=0 use=1tcp ? ? ?6 431968 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=37038 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=37038 [ASSURED] mark=0 use=1tcp ? ? ?6 428802 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43610 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43610 [ASSURED] mark=0 use=1tcp ? ? ?6 431983 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57908 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57908 [ASSURED] mark=0 use=1tcp ? ? ?6 426274 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=49395 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=49395 [ASSURED] mark=0 u
se=1tcp ? ? ?6 431989 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48011 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48011 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57916 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57916 [ASSURED] mark=0 use=1tcp ? ? ?6 431992 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57919 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57919 [ASSURED] mark=0 use=1tcp ? ? ?6 426330 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=54866 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=54866 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47748 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47748 [ASSURED] mark=0 use=1tcp ? ? ?6 432000 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47881 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47881 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127
.0.0.1 dst=127.0.0.1 sport=43451 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43451 [ASSURED] mark=0 use=1tcp ? ? ?6 431914 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48632 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48632 [ASSURED] mark=0 use=1tcp ? ? ?6 431956 ESTABLISHED src=10.145.15.14 dst=10.145.105.64 sport=52265 dport=6080 src=10.145.105.64 dst=10.145.15.14 sport=6080 dport=52265 [ASSURED] mark=0 use=1tcp ? ? ?6 431991 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57920 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57920 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48201 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48201 [ASSURED] mark=0 use=1tcp ? ? ?6 431992 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=60531 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=60531 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.6
4 sport=59051 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59051 [ASSURED] mark=0 use=1tcp ? ? ?6 431989 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59070 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59070 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59063 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59063 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=36508 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=36508 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57900 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57900 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48613 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48613 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.14
5.105.64 sport=57891 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57891 [ASSURED] mark=0 use=1tcp ? ? ?6 428798 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=41205 dport=5900 src=127.0.0.1 dst=127.0.0.1 sport=5900 dport=41205 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47749 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47749 [ASSURED] mark=0 use=1tcp ? ? ?6 426297 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=52774 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=52774 [ASSURED] mark=0 use=1tcp ? ? ?6 431989 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47753 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47753 [ASSURED] mark=0 use=1tcp ? ? ?6 431993 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=42018 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=42018 [ASSURED] mark=0 use=1tcp ? ? ?6 431951 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57897 dport=5672 src=10.14
5.105.64 dst=10.145.105.64 sport=5672 dport=57897 [ASSURED] mark=0 use=1tcp ? ? ?6 431533 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44126 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44126 [ASSURED] mark=0 use=1tcp ? ? ?6 426297 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=52587 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=52587 [ASSURED] mark=0 use=2tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57885 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57885 [ASSURED] mark=0 use=1tcp ? ? ?6 428782 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43751 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43751 [ASSURED] mark=0 use=1tcp ? ? ?6 428788 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44345 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44345 [ASSURED] mark=0 use=1tcp ? ? ?6 428788 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43713 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43713 [ASSURE
D] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57899 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57899 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47751 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47751 [ASSURED] mark=0 use=1tcp ? ? ?6 426303 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=51977 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=51977 [ASSURED] mark=0 use=1tcp ? ? ?6 431951 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57901 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57901 [ASSURED] mark=0 use=1tcp ? ? ?6 426331 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48880 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48880 [ASSURED] mark=0 use=1tcp ? ? ?6 431994 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47757 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47757 [ASSURED] mark=0 use=1tcp ? ? ?6 431987 ESTABLIS
HED src=10.145.105.64 dst=10.145.105.64 sport=59062 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59062 [ASSURED] mark=0 use=1tcp ? ? ?6 429699 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48286 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48286 [ASSURED] mark=0 use=1tcp ? ? ?6 431990 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48489 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48489 [ASSURED] mark=0 use=1tcp ? ? ?6 431991 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57903 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57903 [ASSURED] mark=0 use=1tcp ? ? ?6 431975 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=45380 dport=9696 src=10.145.105.64 dst=10.145.105.64 sport=9696 dport=45380 [ASSURED] mark=0 use=1tcp ? ? ?6 431964 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59060 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59060 [ASSURED] mark=0 use=1tcp ? ? ?6 431985 ESTABLISHED src=1
0.145.105.64 dst=10.145.105.64 sport=57915 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57915 [ASSURED] mark=0 use=1tcp ? ? ?6 431984 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57911 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57911 [ASSURED] mark=0 use=1tcp ? ? ?6 428781 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45182 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45182 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47754 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47754 [ASSURED] mark=0 use=1tcp ? ? ?6 428801 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=46210 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=46210 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.90.5 dst=10.145.105.64 sport=58162 dport=22 src=10.145.105.64 dst=10.145.90.5 sport=22 dport=58162 [ASSURED] mark=0 use=1tcp ? ? ?6 430445 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=4781
7 dport=5901 src=127.0.0.1 dst=127.0.0.1 sport=5901 dport=47817 [ASSURED] mark=0 use=1tcp ? ? ?6 431987 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=58231 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=58231 [ASSURED] mark=0 use=1tcp ? ? ?6 431969 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=37219 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=37219 [ASSURED] mark=0 use=1tcp ? ? ?6 431969 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59072 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59072 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=50737 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=50737 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47759 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47759 [ASSURED] mark=0 use=1tcp ? ? ?6 431967 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=34837 dport=5672 src=
10.145.105.64 dst=10.145.105.64 sport=5672 dport=34837 [ASSURED] mark=0 use=1tcp ? ? ?6 426389 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43438 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43438 [ASSURED] mark=0 use=1tcp ? ? ?6 431984 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=60883 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=60883 [ASSURED] mark=0 use=1tcp ? ? ?6 431972 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57659 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57659 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57906 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57906 [ASSURED] mark=0 use=1tcp ? ? ?6 429732 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=46378 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=46378 [ASSURED] mark=0 use=1tcp ? ? ?6 431992 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47756 dport=3306 src=127.0.0.1 dst=127
.0.0.1 sport=3306 dport=47756 [ASSURED] mark=0 use=1tcp ? ? ?6 426296 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=49193 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=49193 [ASSURED] mark=0 use=1tcp ? ? ?6 431989 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57884 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57884 [ASSURED] mark=0 use=1tcp ? ? ?6 428748 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44910 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44910 [ASSURED] mark=0 use=2tcp ? ? ?6 431434 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43946 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43946 [ASSURED] mark=0 use=1tcp ? ? ?6 428790 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44447 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44447 [ASSURED] mark=0 use=1tcp ? ? ?6 426275 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43444 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43444 [ASSURED] mark=0 use=1tcp ?
? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59057 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59057 [ASSURED] mark=0 use=1tcp ? ? ?6 428781 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43860 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43860 [ASSURED] mark=0 use=1tcp ? ? ?6 428782 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45273 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45273 [ASSURED] mark=0 use=1tcp ? ? ?6 429195 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44661 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44661 [ASSURED] mark=0 use=1tcp ? ? ?6 94 TIME
WAIT src=10.145.105.64 dst=10.145.105.64 sport=59833 dport=35357 src=10.145.105.64 dst=10.145.105.64 sport=35357 dport=59833 [ASSURED] mark=0 use=1tcp ? ? ?6 428790 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44448 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44448 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=12
7.0.0.1 sport=43446 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43446 [ASSURED] mark=0 use=1tcp ? ? ?6 431981 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57904 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57904 [ASSURED] mark=0 use=1tcp ? ? ?6 431980 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47755 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47755 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43452 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43452 [ASSURED] mark=0 use=1tcp ? ? ?6 431984 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57912 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57912 [ASSURED] mark=0 use=1tcp ? ? ?6 428790 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44595 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44595 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43450 dport=3306 src=127.0.
0.1 dst=127.0.0.1 sport=3306 dport=43450 [ASSURED] mark=0 use=1tcp ? ? ?6 431991 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47747 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47747 [ASSURED] mark=0 use=1tcp ? ? ?6 428723 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=44253 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=44253 [ASSURED] mark=0 use=1tcp ? ? ?6 431988 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57918 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57918 [ASSURED] mark=0 use=1tcp ? ? ?6 431976 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57892 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57892 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=58933 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=58933 [ASSURED] mark=0 use=1tcp ? ? ?6 431964 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59074 dport=5672 src=10.145.105.64 dst=10.14
5.105.64 sport=5672 dport=59074 [ASSURED] mark=0 use=1tcp ? ? ?6 428787 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=45446 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=45446 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48153 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48153 [ASSURED] mark=0 use=1tcp ? ? ?6 426295 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=50319 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=50319 [ASSURED] mark=0 use=1tcp ? ? ?6 431979 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=36498 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=36498 [ASSURED] mark=0 use=1udp ? ? ?17 29 src=0.0.0.0 dst=255.255.255.255 sport=68 dport=67 [UNREPLIED] src=255.255.255.255 dst=0.0.0.0 sport=67 dport=68 mark=0 use=1tcp ? ? ?6 431998 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=58139 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=58139 [ASSURED] mark=0 use=1tc
p ? ? ?6 431999 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=47752 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=47752 [ASSURED] mark=0 use=1tcp ? ? ?6 431999 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59055 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59055 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59052 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59052 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43449 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43449 [ASSURED] mark=0 use=1tcp ? ? ?6 431969 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57509 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57509 [ASSURED] mark=0 use=1tcp ? ? ?6 431974 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=59068 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=59068 [ASSURED] mark=0 use=1tcp ? ? ?6
431991 ESTABLISHED src=10.145.105.64 dst=10.145.105.64 sport=57889 dport=5672 src=10.145.105.64 dst=10.145.105.64 sport=5672 dport=57889 [ASSURED] mark=0 use=1tcp ? ? ?6 425920 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=43453 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=43453 [ASSURED] mark=0 use=1tcp ? ? ?6 431914 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=48651 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=48651 [ASSURED] mark=0 use=1tcp ? ? ?6 426232 ESTABLISHED src=127.0.0.1 dst=127.0.0.1 sport=49376 dport=3306 src=127.0.0.1 dst=127.0.0.1 sport=3306 dport=49376 [ASSURED] mark=0 use=2

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/9e402df7/attachment-0001.html


Message: 15
Date: Thu, 21 Apr 2016 16:24:35 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: Corey Bryant corey.bryant@canonical.com
Cc: ubuntu-server ubuntu-server@lists.ubuntu.com,
"openstack-operators@lists.openstack.org"
openstack-operators@lists.openstack.org, Openstack
openstack@lists.openstack.org
Subject: Re: [Openstack] OpenStack Mitaka for Ubuntu 14.04 LTS and
Ubuntu 16.04 LTS
Message-ID:
CAJSM8J0bNnADe5idKSiux2_Z5uAG1b_XO1+EbfuR=MvJg6+0EQ@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

This is awesome!

However, I am facing a hard time to make it work with OpenvSwitch and
multi-node environment... All works in an "All in One" fashion...

I'll keep researching and testing it, until it works.

Nice job guys, congrats!

Cheers!
Thiago

On 21 April 2016 at 16:08, Corey Bryant corey.bryant@canonical.com wrote:

Hi All,

The Ubuntu OpenStack Engineering team is pleased to announce the general
availability of OpenStack Mitaka in Ubuntu 16.04 LTS and for Ubuntu 14.04
LTS via the Ubuntu Cloud Archive.

Ubuntu 14.04 LTS


You can enable the Ubuntu Cloud Archive for OpenStack Mitaka on Ubuntu
14.04 installations by running the following commands (make sure you have
an up-to-date software-properties-common package first):

sudo add-apt-repository cloud-archive:mitaka
sudo apt-get update

The Ubuntu Cloud Archive for Mitaka includes updates for Nova, Glance,
Keystone, Neutron, Neutron-FWaaS, Neutron-LBaaS, Neutron-VPNaaS, Cinder,
Swift, Horizon, Ceilometer, Aodh, Heat, Designate, Barbican, Manila,
Mistral, Murano, Ironic, Trove, Sahara, Senlin, and Zaqar; Ceph (10.1.2),
Nova-LXD (13.0.0), RabbitMQ (3.5.7), QEMU (1.2.5), libvirt (1.3.1),
OpenvSwitch (2.5.0) and DPDK (2.2.0) backports from Ubuntu 16.04
development have also been provided.

You can see the full list of packages and versions at [0].

Ubuntu 16.04 LTS


No extra steps are required; just start installing OpenStack!

Release notes for Ubuntu 16.04 LTS can be found at [1].

Reporting bugs


If you have any issues, please report bugs using the 'ubuntu-bug' tool:

sudo ubuntu-bug nova-conductor

This will ensure that bugs get logged in the right place in Launchpad.

Also feel free to poke anyone on our team in #ubuntu-server (coreycb,
ddellav, beisner, jamespage) if you have any issues.

Finally, thank you to the entire OpenStack community and everyone who's
made OpenStack Mitaka a reality!

[0]
http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/mitaka_versions.html
[1] https://wiki.ubuntu.com/XenialXerus/ReleaseNotes

--
Regards,
Corey Bryant
Ubuntu Core Developer


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/6f7f2a68/attachment-0001.html


Message: 16
Date: Thu, 21 Apr 2016 16:41:16 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Mitaka with OpenvSwitch, no VXLAN tunnels
between compute and network nodes
Message-ID:
CAJSM8J1rXT7+Q=KYFyTWQZO4DDmdHyPYpDk1J6fHeSunBaaxQQ@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

On 21 April 2016 at 16:05, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

On 21 April 2016 at 15:54, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

On 21 April 2016 at 15:52, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

Guys,

I'm trying to deploy Mitaka on Xenial, using OpenvSwitch.

I am using the following documents:

http://docs.openstack.org/mitaka/install-guide-ubuntu

http://docs.openstack.org/mitaka/networking-guide/scenario-classic-ovs.html

  • The topology is like this:

    1- Controller + Network Node;

    2- Compute Node.

    NOTE: Both have two NICs, em1 for management and services, and p1p1 for
    VXLAN tunnels.

    However, I see no "vxlan peers" on the output of "ovs-vsctl show"...

    So, Instances doesn't get IP from DHCP server, and if I try to
    configure static IPs, Instances can only talk with each other (that are
    running on the same, and uniq, compute node). Also, instances can't ping
    Neutron L2 Namespace router.

    What I am missing?

Thanks!
Thiago

BTW, I am using an Ansibe automation tool that I created for this. If I
use the same roles, to deploy an "All in One" OpenStack box, with
OpenvSwitch, of course, it works!

Only when I split the Compute Node, out from the "Controller+Network"
node, that it doesn't work anymore...

Also, I can create the Network and its Subnet, the Router attached to both
"External Net" and with a internal interface...

All network agents are up and running...

But, VXLAN tunnels, no connectivity....

It is working now!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/b4b9da6b/attachment-0001.html


Message: 17
Date: Thu, 21 Apr 2016 14:44:26 -0500
From: Paras pradhan pradhanparas@gmail.com
To: Martinx - ????? thiagocmartinsc@gmail.com
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Xenial / Mitaka = Instance failed network
setup / nova.compute.manager Unauthorized
Message-ID:
CADyt5gn1DW0MQRjy_ViivY8kN_-6Kud+ocOfk4hiH1fcT39T9w@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

The neutron section was missing from nova.conf and now the instances work
but having issues with metadata server. instances boot but no network
access.
Thanks
Paras.

On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ????? thiagocmartinsc@gmail.com
wrote:

My nova.conf is this one:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf

However, I'm facing connectivity problems when with OpenvSwitch
deployments, investigating it now...

On 21 April 2016 at 11:04, Paras pradhan pradhanparas@gmail.com wrote:

Yes . I did. here is my nova.conf. Can you share yours?
http://paste.openstack.org/show/494988/

On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block eblock@nde.ag wrote:

Okay, did you restart the respective services on all nodes after the
changes in your config files? If the same error still occurs then you might
haven't found all occurrences of the option auth_plugin, did you replace it
in all config files? I'm just guessing here...

Zitat von Paras pradhan pradhanparas@gmail.com:

No I still have that error. Other than that I don't see any other errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block eblock@nde.ag wrote:

So I guess the mentioned error should be resolved? Does it work now?

Zitat von Paras pradhan pradhanparas@gmail.com:

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block eblock@nde.ag wrote:

And did you change it to authtype instead of authplugin? Also you
should

make sure that this option is in the correct section of your config
file,
for example

[keystoneauthtoken]
...
auth
type = password

or

[neutron]
...
auth_type = password

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block eblock@nde.ag wrote:

Hi Paras,

the option auth_plugin is deprecated (from nova.conf):

---cut here---

Authentication type to load (unknown value)

Deprecated group/name - [DEFAULT]/auth_plugin

auth_type = password
---cut here---

But as far as I can tell, you should only get a warning, not an
error,
I've seen some of these warnings in my logs, but it works (I work
with
openSUSE). To get Mitaka working at all I simply tried to set the
same
options as in my working Liberty configs, and then I searched for
deprecation warnings and additional options mentioned in the Mitaka
guide.

Hope this helps!

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Can somebody share the nova.conf and neutron.conf from working
mitaka?
I
am

also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.

Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
nasir.mahmood@gmail.com
>
wrote:

Martinx,

glad to see that you are able to dig into the typo issue. I

remember, I
had to completely re-re-clean install my virtual setup of
OpenStack
for a
POC back in 2015 , just because I have had miss-configured my
neutron.conf's mysql DB connector information.

Cheers!

Regards,
Nasir Mahmood

On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

FIXED!! I knew it was a typo somewhere! LOL

https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02

Thank you guys!

Sorry about the buzz on TWO mail lists...

At least, now we know that Nova silent fail on its start up, if
somethings aren't configured according... And there is no
verification
steps to test the communication between Nova and Neutron.

Mitaka is working now on Xenial! YAY!!

I'm about to commit changes to enable OpenvSwitch with DPDK and
multi-node deployments, fully automated!

Cheers!
Thiago

On 17 April 2016 at 21:26, Martinx - ????? <
thiagocmartinsc@gmail.com
>
wrote:

On 17 April 2016 at 17:39, Martinx - ????? <
thiagocmartinsc@gmail.com
>

wrote:

Guys,

I am trying to deploy Mitaka, on top of Ubuntu 16.04, by using

the
following document:

http://docs.openstack.org/mitaka/install-guide-ubuntu

Yes, I know, the above document is for installing Mitaka on
top
of
Ubuntu 14.04 but, from what I understand, the only difference
is
that
on
Xenial, there is no need to add the Ubuntu Mitaka Cloud
Archive,
since
Mitaka is the default on Xenial, so, I can follow that
document,
right?
=)

At first, OpenStack installation goes okay, without any
errors,
all
services comes up, etc... However, it is not possible to
launch an
Instance.

*** Errors on launching the Instance:

  • Right after launching it:

    https://paste.ubuntu.com/15902503/

  • Spawning it, after Glance finishes the download, similar
    error
    a
    second time:

    https://paste.ubuntu.com/15902556/

    What am I missing?

    Apparently, Nova is not authorized to talk with Neutron but,
    I am
    following the docs (maybe it is just a typo somewhere?)...

    Also, I have an Ansible automation to deploy it, so, it is
    less
    error
    prone. And however can help me, will see how I am deploying
    it.

    I see no error on Admin Dashboard, all services are up.

    NOTE: My Ansible playbooks is in a sense, "
    docs.openstack.org/mitaka/install-guide-ubuntu fully
    automated",
    it
    is
    very close to it, step-by-step.

    How can I debug this? I mean, how can I try to do, what Nova
    is
    doing
    (its connection with Neutron), to make sure that the settings
    are
    in
    place
    correctly?

    Here is how I am installing Mitaka on Xenial:


1- Install Ubuntu 16.04 server 64-bit on bare-metal;
  • Configure your /etc/hostname and /etc/hosts.

    DETAILS:

https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md

2- Clone the automation:

cd ~
git clone https://github.com/tmartinx/svauto.git

3- Run the automation to install OpenStack (all-in-one)

cd ~/svauto

./os-deploy.sh --br-mode=LBR --use-dummies
--base-os=ubuntu16
--base-os-upgrade=yes --openstack-release=mitaka
--openstack-installation
--dry-run

ansible-playbook -c local site-openstack.yml --extra-vars
"openstack_installation=yes"


NOTE: If you don't use "--dry-run" option, Ansible will be
executed
automatically by "os-deploy.sh".

I am sharing the Ansible playbooks, because it will be
easier to
see
what I am doing.

About the relevant configuration blocks, I believe that I
have it
properly configured (I followed Mitaka docs), like this:

  • neutron.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
-

  • nova.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
-

I already installed OpenStack many, many, many times, since
Havana
release, I'm confident that I am doing it right but, of
course,
maybe
I did
something wrong this time... =P

I appreciate any help!

Thanks!
Thiago

Hey guys,

I am reviewing everything, to make sure that my automation
matches
docs.openstack.org/mitaka/install-guide-ubuntu/ in details.

Two things...


1- All the verification steps (from official doc) passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html
- passed (mine doesn't have /horizon)

http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html
- passed but, I'm not using any cinder-volume yet

http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html
- "6. Launch the instance" - FAIL

NOTE: I can create Networks, Subnets, Routers... I can see
the
Linux
Namespaces at the Neutron L3 Router (All-in-One)

2- This problem happen no matter if deploying it with Linux
Bridges
(--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS)


So, I think that OpenStack should provide more verification
steps,
specially to test the communication / authentication between
its
different
projects, for example:

A- Does Nova can communicate with Neutron? How to test this?

B- Can Nova download images from Glance? Etc...

Doing more reviews now...

Cheers!
Thiago


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Nasir Mahmood


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/3f136b07/attachment-0001.html


Message: 18
Date: Thu, 21 Apr 2016 16:50:11 -0300
From: Martinx - ????? thiagocmartinsc@gmail.com
To: Paras pradhan pradhanparas@gmail.com
Cc: "openstack@lists.openstack.org" openstack@lists.openstack.org
Subject: Re: [Openstack] Xenial / Mitaka = Instance failed network
setup / nova.compute.manager Unauthorized
Message-ID:
CAJSM8J31qYbG0Mwgxo9GbTnWZWM7BHdCbFxmr03yNVRa5+bF8Q@mail.gmail.com
Content-Type: text/plain; charset="utf-8"

I just manage to make OpenStack Mitaka to work with both Linux Bridges, and
OpenvSwitch...

Everything is work on both "All in One" and multi-node environments.

Very soon, I'll post instructions about how to use the Ansible automation
that I am developing to play with this...

Then, you guys will be able to deploy it, on a spare box (or VMs), and
then, compare with failing deployemnts...

Cheers!

On 21 April 2016 at 16:44, Paras pradhan pradhanparas@gmail.com wrote:

The neutron section was missing from nova.conf and now the instances work
but having issues with metadata server. instances boot but no network
access.
Thanks
Paras.

On Thu, Apr 21, 2016 at 9:58 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

My nova.conf is this one:

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_cmpt/templates/mitaka/nova.conf

However, I'm facing connectivity problems when with OpenvSwitch
deployments, investigating it now...

On 21 April 2016 at 11:04, Paras pradhan pradhanparas@gmail.com wrote:

Yes . I did. here is my nova.conf. Can you share yours?
http://paste.openstack.org/show/494988/

On Thu, Apr 21, 2016 at 7:36 AM, Eugen Block eblock@nde.ag wrote:

Okay, did you restart the respective services on all nodes after the
changes in your config files? If the same error still occurs then you might
haven't found all occurrences of the option auth_plugin, did you replace it
in all config files? I'm just guessing here...

Zitat von Paras pradhan pradhanparas@gmail.com:

No I still have that error. Other than that I don't see any other

errors.

On Wed, Apr 20, 2016 at 9:22 AM, Eugen Block eblock@nde.ag wrote:

So I guess the mentioned error should be resolved? Does it work now?

Zitat von Paras pradhan pradhanparas@gmail.com:

Yes I I have it set up in nova.conf and neutron.conf

On Wed, Apr 20, 2016 at 9:11 AM, Eugen Block eblock@nde.ag wrote:

And did you change it to authtype instead of authplugin? Also you
should

make sure that this option is in the correct section of your config
file,
for example

[keystoneauthtoken]
...
auth
type = password

or

[neutron]
...
auth_type = password

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Hi Eugen,

Thanks. Log says its an error. Here is the full log.
http://pastebin.com/K1f4pJhB

-Paras.

On Tue, Apr 19, 2016 at 2:05 AM, Eugen Block eblock@nde.ag
wrote:

Hi Paras,

the option auth_plugin is deprecated (from nova.conf):

---cut here---

Authentication type to load (unknown value)

Deprecated group/name - [DEFAULT]/auth_plugin

auth_type = password
---cut here---

But as far as I can tell, you should only get a warning, not an
error,
I've seen some of these warnings in my logs, but it works (I work
with
openSUSE). To get Mitaka working at all I simply tried to set the
same
options as in my working Liberty configs, and then I searched for
deprecation warnings and additional options mentioned in the
Mitaka
guide.

Hope this helps!

Regards,
Eugen

Zitat von Paras pradhan pradhanparas@gmail.com:

Can somebody share the nova.conf and neutron.conf from working
mitaka?
I
am

also following the same guide and ran into a problem.

2016-04-18 16:51:07.982 2447 ERROR nova.api.openstack.extensions
NoSuchOptError: no such option in group neutron: auth_plugin

Not sure what did I do wrong. It was while launching an instance.

Thanks

Paras.

On Mon, Apr 18, 2016 at 2:46 AM, Nasir Mahmood <
nasir.mahmood@gmail.com
>
wrote:

Martinx,

glad to see that you are able to dig into the typo issue. I

remember, I
had to completely re-re-clean install my virtual setup of
OpenStack
for a
POC back in 2015 , just because I have had miss-configured my
neutron.conf's mysql DB connector information.

Cheers!

Regards,
Nasir Mahmood

On Mon, Apr 18, 2016 at 7:02 AM, Martinx - ????? <
thiagocmartinsc@gmail.com> wrote:

FIXED!! I knew it was a typo somewhere! LOL

https://github.com/tmartinx/svauto/commit/40ce6566cd0e6435cf75bb34116b6c3bacbeaf02

Thank you guys!

Sorry about the buzz on TWO mail lists...

At least, now we know that Nova silent fail on its start up, if
somethings aren't configured according... And there is no
verification
steps to test the communication between Nova and Neutron.

Mitaka is working now on Xenial! YAY!!

I'm about to commit changes to enable OpenvSwitch with DPDK and
multi-node deployments, fully automated!

Cheers!
Thiago

On 17 April 2016 at 21:26, Martinx - ????? <
thiagocmartinsc@gmail.com
>
wrote:

On 17 April 2016 at 17:39, Martinx - ????? <
thiagocmartinsc@gmail.com
>

wrote:

Guys,

I am trying to deploy Mitaka, on top of Ubuntu 16.04, by

using
the
following document:

http://docs.openstack.org/mitaka/install-guide-ubuntu

Yes, I know, the above document is for installing Mitaka on
top
of
Ubuntu 14.04 but, from what I understand, the only
difference is
that
on
Xenial, there is no need to add the Ubuntu Mitaka Cloud
Archive,
since
Mitaka is the default on Xenial, so, I can follow that
document,
right?
=)

At first, OpenStack installation goes okay, without any
errors,
all
services comes up, etc... However, it is not possible to
launch an
Instance.

*** Errors on launching the Instance:

  • Right after launching it:

    https://paste.ubuntu.com/15902503/

  • Spawning it, after Glance finishes the download, similar
    error
    a
    second time:

    https://paste.ubuntu.com/15902556/

    What am I missing?

    Apparently, Nova is not authorized to talk with Neutron
    but, I am
    following the docs (maybe it is just a typo somewhere?)...

    Also, I have an Ansible automation to deploy it, so, it is
    less
    error
    prone. And however can help me, will see how I am deploying
    it.

    I see no error on Admin Dashboard, all services are up.

    NOTE: My Ansible playbooks is in a sense, "
    docs.openstack.org/mitaka/install-guide-ubuntu fully
    automated",
    it
    is
    very close to it, step-by-step.

    How can I debug this? I mean, how can I try to do, what
    Nova is
    doing
    (its connection with Neutron), to make sure that the
    settings are
    in
    place
    correctly?

    Here is how I am installing Mitaka on Xenial:


1- Install Ubuntu 16.04 server 64-bit on bare-metal;
  • Configure your /etc/hostname and /etc/hosts.

    DETAILS:

https://github.com/tmartinx/svauto/blob/dev/README.OpenStack.md

2- Clone the automation:

cd ~
git clone https://github.com/tmartinx/svauto.git

3- Run the automation to install OpenStack (all-in-one)

cd ~/svauto

./os-deploy.sh --br-mode=LBR --use-dummies
--base-os=ubuntu16
--base-os-upgrade=yes --openstack-release=mitaka
--openstack-installation
--dry-run

ansible-playbook -c local site-openstack.yml --extra-vars
"openstack_installation=yes"


NOTE: If you don't use "--dry-run" option, Ansible will be
executed
automatically by "os-deploy.sh".

I am sharing the Ansible playbooks, because it will be
easier to
see
what I am doing.

About the relevant configuration blocks, I believe that I
have it
properly configured (I followed Mitaka docs), like this:

  • neutron.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_neutron_aio/templates/mitaka/neutron.conf
-

  • nova.conf:
    -

https://github.com/tmartinx/svauto/blob/dev/ansible/roles/os_nova_aio/templates/mitaka/nova.conf
-

I already installed OpenStack many, many, many times, since
Havana
release, I'm confident that I am doing it right but, of
course,
maybe
I did
something wrong this time... =P

I appreciate any help!

Thanks!
Thiago

Hey guys,

I am reviewing everything, to make sure that my automation
matches
docs.openstack.org/mitaka/install-guide-ubuntu/ in details.

Two things...


1- All the verification steps (from official doc) passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/keystone-openrc.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/glance-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/nova-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/neutron-verify-option2.html
- passed

http://docs.openstack.org/mitaka/install-guide-ubuntu/horizon-verify.html
- passed (mine doesn't have /horizon)

http://docs.openstack.org/mitaka/install-guide-ubuntu/cinder-verify.html
- passed but, I'm not using any cinder-volume yet

http://docs.openstack.org/mitaka/install-guide-ubuntu/launch-instance-selfservice.html
- "6. Launch the instance" - FAIL

NOTE: I can create Networks, Subnets, Routers... I can see
the
Linux
Namespaces at the Neutron L3 Router (All-in-One)

2- This problem happen no matter if deploying it with Linux
Bridges
(--br-mode=LBR) or with OpenvSwitch (--br-mode=OVS)


So, I think that OpenStack should provide more verification
steps,
specially to test the communication / authentication between
its
different
projects, for example:

A- Does Nova can communicate with Neutron? How to test this?

B- Can Nova download images from Glance? Etc...

Doing more reviews now...

Cheers!
Thiago


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--

Nasir Mahmood


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51
75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51
77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983

--
Eugen Block voice : +49-40-559 51 75
NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77
Postfach 61 03 15
D-22423 Hamburg e-mail : eblock@nde.ag

    Vorsitzende des Aufsichtsrates: Angelika Mozdzen
      Sitz und Registergericht: Hamburg, HRB 90934
              Vorstand: Jens-U. Mozdzen
               USt-IdNr. DE 814 013 983


Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openstack.org/pipermail/openstack/attachments/20160421/2f973f1d/attachment.html



Openstack mailing list
openstack@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

End of Openstack Digest, Vol 34, Issue 21



Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
asked Apr 22, 2016 in openstack by Jean-Pierre_Ribeauvi (1,300 points)   3 9 12
...