[Openstack-operators] OpenStack rabbitmq Mirriored queues

[Ahmed Mostafa]

Dear All,

I am investigating enabling Mirriored queues in my OpenStack cluster.

I have 3 controllers and a 10G network.

One of the videos in Barcelona summit suggested not to do so :

https://www.youtube.com/watch?v=bpmgxrPOrZw

Because it slows down the cloud significantly.

So my question is, would enabling rabbitmq mirrored queus and enabling
rabbit_ha_queues slow down my environment ?

And what are the proper ways to test this ? how can I measure the impact on
my environment ?

Kind Regards,
Ahmed
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Cinder-api Cannot extend resource snapshots: No such resource

[Ahmed Mostafa]

This is on newton :

cinder-api --version
9.0.0


On Tue, Jan 31, 2017 at 5:00 PM, Ahmed Mostafa <ahmedmostafa...@gmail.com>
wrote:

> Hello
>
> Anyone else seeing there errors in cinder api?
>
> [ 8092] WARNING: Extension SchedulerHints: Cannot extend resource volumes:
> No such resource
> [ 8092] WARNING: Extension VolumeTenantAttribute: Cannot extend resource
> volumes: No such resource
> [ 8092] WARNING: Extension SnapshotActions: Cannot extend resource
> snapshots: No such resource
> [ 8092] WARNING: Extension VolumeTypeAccess: Cannot extend resource types:
> No such resource
> [ 8092] WARNING: Extension VolumeHostAttribute: Cannot extend resource
> volumes: No such resource
> [ 8092] WARNING: Extension VolumeTypeEncryption: Cannot extend resource
> types: No such resource
> [ 8092] WARNING: Extension TypesManage: Cannot extend resource types: No
> such resource
> [ 8092] WARNING: Extension VolumeActions: Cannot extend resource volumes:
> No such resource
> [ 8092] WARNING: Extension UsedLimits: Cannot extend resource limits: No
> such resource
> [ 8092] WARNING: Extension VolumeMigStatusAttribute: Cannot extend
> resource volumes: No such resource
> [ 8092] WARNING: Extension VolumeUnmanage: Cannot extend resource volumes:
> No such resource
> [ 8092] WARNING: Extension ExtendedSnapshotAttributes: Cannot extend
> resource snapshots: No such resource
> [ 8092] WARNING: Extension SnapshotUnmanage: Cannot extend resource
> snapshots: No such resource
> [ 8092] WARNING: Extension VolumeImageMetadata: Cannot extend resource
> volumes: No such resource
> [ 8092] WARNING: Extension AdminActions: Cannot extend resource volumes:
> No such resource
> [ 8092] WARNING: Extension AdminActions: Cannot extend resource snapshots:
> No such resource
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Cinder-api Cannot extend resource snapshots: No such resource

[Ahmed Mostafa]

Hello

Anyone else seeing there errors in cinder api?

[ 8092] WARNING: Extension SchedulerHints: Cannot extend resource volumes:
No such resource
[ 8092] WARNING: Extension VolumeTenantAttribute: Cannot extend resource
volumes: No such resource
[ 8092] WARNING: Extension SnapshotActions: Cannot extend resource
snapshots: No such resource
[ 8092] WARNING: Extension VolumeTypeAccess: Cannot extend resource types:
No such resource
[ 8092] WARNING: Extension VolumeHostAttribute: Cannot extend resource
volumes: No such resource
[ 8092] WARNING: Extension VolumeTypeEncryption: Cannot extend resource
types: No such resource
[ 8092] WARNING: Extension TypesManage: Cannot extend resource types: No
such resource
[ 8092] WARNING: Extension VolumeActions: Cannot extend resource volumes:
No such resource
[ 8092] WARNING: Extension UsedLimits: Cannot extend resource limits: No
such resource
[ 8092] WARNING: Extension VolumeMigStatusAttribute: Cannot extend resource
volumes: No such resource
[ 8092] WARNING: Extension VolumeUnmanage: Cannot extend resource volumes:
No such resource
[ 8092] WARNING: Extension ExtendedSnapshotAttributes: Cannot extend
resource snapshots: No such resource
[ 8092] WARNING: Extension SnapshotUnmanage: Cannot extend resource
snapshots: No such resource
[ 8092] WARNING: Extension VolumeImageMetadata: Cannot extend resource
volumes: No such resource
[ 8092] WARNING: Extension AdminActions: Cannot extend resource volumes: No
such resource
[ 8092] WARNING: Extension AdminActions: Cannot extend resource snapshots:
No such resource
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Nova not powering on baremetal instances, ironic

[Ahmed Mostafa]

Thank you everyone

The problem was in the image, it does not dhcp

On Sun, 11 Dec 2016 at 16:13, Ahmed Mostafa <ahmedmostafa...@gmail.com>
wrote:

> So i was able to solve the problem of nova not creating ports, however
> when it creates ports it creates normal ovs ports and they always stays
> down because they are unable to be bound to the hypervisor host( the
> provisioned node)
>
> After durther investigation, i creates a port with vnic_type of baremetal,
> and binding type of unbound, yet it always stays down and i can not reach
> or ping the instance
>
> Any thoughts ?
>
> Thank you
>
> On Sat, 10 Dec 2016 at 23:25, Ahmed Mostafa <ahmedmostafa...@gmail.com>
> wrote:
>
> Hello all,
>
> I have tried to use ironic in stand alone mode and i tried to integerate
> it with nova
>
> When i use it in stand alone mode, i craate a neutron port of vnic_type
> baremetal and i assign it to the ironic node using extra/vif_port_id, i am
> able to provision the node, but not able to get connectivity due to the
> fact that the port always stays DOWN in neutron no matter what i do
>
> When i tried to integerate nova compute, nova does not create the port and
> therfore does not power on the node
>
> Any idea on how to solve his ?
>
> Thank you
>
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Nova not powering on baremetal instances, ironic

[Ahmed Mostafa]

So i was able to solve the problem of nova not creating ports, however when
it creates ports it creates normal ovs ports and they always stays down
because they are unable to be bound to the hypervisor host( the provisioned
node)

After durther investigation, i creates a port with vnic_type of baremetal,
and binding type of unbound, yet it always stays down and i can not reach
or ping the instance

Any thoughts ?

Thank you
On Sat, 10 Dec 2016 at 23:25, Ahmed Mostafa <ahmedmostafa...@gmail.com>
wrote:

> Hello all,
>
> I have tried to use ironic in stand alone mode and i tried to integerate
> it with nova
>
> When i use it in stand alone mode, i craate a neutron port of vnic_type
> baremetal and i assign it to the ironic node using extra/vif_port_id, i am
> able to provision the node, but not able to get connectivity due to the
> fact that the port always stays DOWN in neutron no matter what i do
>
> When i tried to integerate nova compute, nova does not create the port and
> therfore does not power on the node
>
> Any idea on how to solve his ?
>
> Thank you
>
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] Nova not powering on baremetal instances, ironic

[Ahmed Mostafa]

Hello all,

I have tried to use ironic in stand alone mode and i tried to integerate it
with nova

When i use it in stand alone mode, i craate a neutron port of vnic_type
baremetal and i assign it to the ironic node using extra/vif_port_id, i am
able to provision the node, but not able to get connectivity due to the
fact that the port always stays DOWN in neutron no matter what i do

When i tried to integerate nova compute, nova does not create the port and
therfore does not power on the node

Any idea on how to solve his ?

Thank you
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Neutron fails to notify nova on events network-vif-plugged

[Ahmed Mostafa]

Actually it is not authenticating it self against keystone, it is
communicating directly to nova by using a ketstone client

in neutron.conf you have to options which are set to True by default, they
are

notify_nova_on_port_status_changes

notify_nova_on_port_data_changes

If you set both of them to False, you wont have any errors any more, but if
for some reason you require using neutron nova notification, then you must
configure nova authentication and api url in neutron.conf

You will find in neutron.conf a section named nova, under it you will see
all condiguration option you can use to configure the notification driver
to notify nova on status or data changes on ports


On Tuesday, 1 November 2016, Davíð Örn Jóhannsson  wrote:

> I’m working on setting up a OpenStack Liberty development env on Ubuntu
> 14.04. At the present I have 3 nodes, Controller, Network and Compute. I am
> up to the place where I’m trying to spin up an instance where
> neutron-server seems to fail to notify nova because of an authentication
> error against keystone , I’ve been struggling for some time to figure out
> the cause of this and was hoping that some could lend me more experienced
> eyes
>
> Controller node /etc/neutron/neutron.conf http://paste.openstack.org/show/
> 587547/
> Openstack endpoint list http://paste.openstack.org/show/587548/
>
> 2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.session [-] RESP: [300]
> Content-Length: 635 Vary: X-Auth-Token Connection: keep-alive Date: Tue, 01
> Nov 2016 12:42:04 GMT Content-Type: application/json X-Distribution: Ubuntu
> RESP BODY: {"versions": {"values": [{"status": "stable", "updated":
> "2015-03-30T00:00:00Z", "media-types": [{"base": "application/json",
> "type": "application/vnd.openstack.identity-v3+json"}], "id": "v3.4",
> "links": [{"href": "http://controller-01:35357/v3/;, "rel": "self"}]},
> {"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types":
> [{"base": "application/json", "type": 
> "application/vnd.openstack.identity-v2.0+json"}],
> "id": "v2.0", "links": [{"href": "http://controller-01:35357/v2.0/;,
> "rel": "self"}, {"href": "http://docs.openstack.org/;, "type":
> "text/html", "rel": "describedby"}]}]}}
>  _http_log_response /usr/lib/python2.7/dist-packages/keystoneclient/
> session.py:215
> 2016-11-01 12:42:04.067 15888 DEBUG keystoneclient.auth.identity.v3.base
> [-] Making authentication request to http://controller-01:35357/v3/
> auth/tokens get_auth_ref /usr/lib/python2.7/dist-
> packages/keystoneclient/auth/identity/v3/base.py:188
> 2016-11-01 12:42:04.091 15888 DEBUG keystoneclient.session [-] Request
> returned failure status: 401 request /usr/lib/python2.7/dist-
> packages/keystoneclient/session.py:400
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova [-] Failed to
> notify nova on events: [{'status': 'completed', 'tag':
> u'bf092fd0-51ba-4fbf-8d3d-9c3004b3811f', 'name': 'network-vif-plugged',
> 'server_uuid': u'24616ae2-a6e4-4843-ade6-357a9ce80bc0'}]
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova Traceback (most
> recent call last):
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/neutron/notifiers/nova.py", line 248,
> in send_events
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova
> batched_events)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/v2/contrib/server_external_events.py",
> line 39, in create
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova
> return_raw=True)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/base.py", line 169, in
> _create
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova _resp, body
> = self.api.client.post(url, body=body)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 176,
> in post
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return
> self.request(url, 'POST', **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/novaclient/client.py", line 91, in
> request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 206,
> in request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova resp =
> super(LegacyJsonAdapter, self).request(*args, **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> "/usr/lib/python2.7/dist-packages/keystoneclient/adapter.py", line 95, in
> request
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova return
> self.session.request(url, method, **kwargs)
> 2016-11-01 12:42:04.091 15888 ERROR neutron.notifiers.nova   File
> 

[Openstack-operators] Neutron Nova Notification and Virtual Interface plugging events

[Ahmed Mostafa]

Hello all,

I am a bit confuse by the following parameters :

notify_nova_on_port_status_change
notify_nova_on_port_data_change

The reason i am confused is that i see if there either of these values is
set to true (Which is the default), neutron will create a notiva notifier
and send these events to nova.

But i can not understand that part from the nova side, because as i see,
when you create a virtual machine you basically call

_do_build_and_run_instance, which calls _create_domain_and_network

These two methods create a virtual machine and a port, then attach that
port on the virtual machine

but in _create_domain_and_network, is see nova waiting for neutron to
create the port and it has a neutron_callbak_fail, if neutron should fail
in creating the port.

Now, if i set these values to false, instance creation still will work, so
i do not really understand, are these two values critical in creating a
virtual machine ? and if not what exactly do they do ?

Thank you
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators