Ask Your Question

BrunoGraz's profile - activity

2020-02-18 02:16:10 -0600 received badge  Good Answer (source)
2017-11-22 08:06:31 -0600 received badge  Famous Question (source)
2017-10-12 05:30:26 -0600 received badge  Notable Question (source)
2017-10-06 02:41:52 -0600 received badge  Popular Question (source)
2017-10-04 10:47:46 -0600 commented question vxlan peers not being created on compute node (vm not getting dhcp)

also for the deployment we used the branch stable/ocata for kolla-ansible

2017-10-04 10:44:58 -0600 commented question vxlan peers not being created on compute node (vm not getting dhcp)

Edited, added a bit more information. This issue is quite strange as there are no errors whatsoever on neutron/openvswitch logs. It looks like some openvswitch flows are not being applied - comparing with other compute nodes - but my understanding on this is more limited.

2017-10-04 08:15:12 -0600 asked a question vxlan peers not being created on compute node (vm not getting dhcp)

Hi,

I have deployed Openstack Ocata with kolla-ansible and I'm getting a similar issue as described here.

The difference is that I see it in a single the compute node - when I create a VM on the compute node the vxlan peers are not created on the compute host and therefore the VM is not able to get a DHCP address.

The only workaround I have found so far was to restart neutron-openvswitch-agent when the vm is already on the compute node, this will create the missing vxlan links, but it is a temporary solution as other vms would also require the service restart.

There are no errors in the neutron-agent nor in openvswitch logs, l2pop and arp_responder are enabled and there are no difference in the configuration file across the compute nodes.

I tried enabling debug in both agents but also didn't help so much.


br-tun before neutron agent restart

Bridge br-tun
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port br-tun
        Interface br-tun
            type: internal
    Port patch-int
        Interface patch-int
            type: patch
            options: {peer=patch-tun}

br-tun after restart

Bridge br-tun
    Controller "tcp:127.0.0.1:6633"
        is_connected: true
    fail_mode: secure
    Port "vxlan-c0a80b05"
        Interface "vxlan-c0a80b05"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.5"}
    Port br-tun
        Interface br-tun
            type: internal
    Port "vxlan-c0a80b0a"
        Interface "vxlan-c0a80b0a"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.10"}
    Port "vxlan-c0a80b06"
        Interface "vxlan-c0a80b06"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.6"}
    Port "vxlan-c0a80b02"
        Interface "vxlan-c0a80b02"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.2"}
    Port patch-int
        Interface patch-int
            type: patch
            options: {peer=patch-tun}
    Port "vxlan-c0a80b09"
        Interface "vxlan-c0a80b09"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.9"}
    Port "vxlan-c0a80b0b"
        Interface "vxlan-c0a80b0b"
            type: vxlan
            options: {df_default="true", in_key=flow, local_ip="192.X.X.8", out_key=flow, remote_ip="192.X.X.11"}

EDIT:

Neutron network:

+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| availability_zone_hints   |                                      |
| availability_zones        | nova                                 |
| created_at                | 2017-08-25T12:15:22Z                 |
| description               |                                      |
| id                        | b4e73eb0-7799-4284-bb81-9f6144a9c223 |
| ipv4_address_scope        |                                      |
| ipv6_address_scope        |                                      |
| mtu                       | 1450                                 |
| name                      | default_internal                     |
| project_id                | 4913dfacc1d248bea911630dd84236c9     |
| provider:network_type     | vxlan                                |
| provider:physical_network |                                      |
| provider:segmentation_id  | 1                                    |
| revision_number           | 4                                    |
| router:external           | False                                |
| shared                    | True                                 |
| status                    | ACTIVE                               |
| subnets                   | e4dab764-faf1-5832-839d-7eb593abfa64 |
| tags                      |                                      |
| tenant_id                 | 4913dfacc1d248bea911630dd84236c9     |
| updated_at                | 2017-08-25T12:15:23Z                 |
+---------------------------+--------------------------------------+

ip netns exec qdhcp-b4e73eb0-7799-4284-bb81-9f6144a9c223 ip addr

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
114: tapb46cdb0c-7b: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN qlen 1000
    link/ether fa:16:3e:58:38:a4 brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.2/24 brd 10.0.0.255 scope global tapb46cdb0c-7b ...
(more)
2016-11-21 08:53:35 -0600 answered a question Misunderstanding while setting up watcher configuration

This command is adding the admin role to the user 'watcher' in the project 'service'.

This project (depending on how Openstack was deployed could be named 'services') is commonly used by other Openstack services as well such as Nova, Keystone, Neutron etc.

2016-11-11 08:06:43 -0600 received badge  Nice Answer (source)
2016-08-05 08:50:28 -0600 received badge  Nice Answer (source)
2016-03-09 10:23:57 -0600 received badge  Famous Question (source)
2015-11-20 12:09:14 -0600 received badge  Notable Question (source)
2015-11-20 12:09:14 -0600 received badge  Popular Question (source)
2015-10-20 01:26:16 -0600 received badge  Necromancer (source)
2015-10-07 08:34:46 -0600 asked a question Unable to associate floating ip into instance using Nova Cells and nova-network

Hi,

We've a Liberty/stable deployment from git repository using nova cells and nova-network on each compute cell. We are able to perform standard operations such as start, suspend, terminate vms, etc. but unable to associate a floating ip to it. Checking the source code is clear that this operation is supported in Nova Cells although this method is not called in our setup - we've added logging to this method.

Investigating a bit further we found out that floating ip association is done via the network api and it is not linked to the cell api call. We've tried to change the network_api_class in nova.conf on the API Cell pointing to ComputeCellsAPI as the documentation shows the same for compute_api_class but no luck. In our setup we've nova-network running on each compute cell and floating ip management is done on the api cell.

Here are my nova.conf files:

API Cell: http://paste.openstack.org/show/9lyKm...

Compute Cell (All-in-one installation): http://paste.openstack.org/show/iXQCv...

Is there a way to enable floating ips association in a Nova Cell architecture using nova-network?

Many thanks, Bruno.

2015-08-11 23:06:11 -0600 received badge  Good Question (source)
2015-04-29 06:55:07 -0600 received badge  Nice Question (source)
2015-04-29 06:53:35 -0600 received badge  Enlightened (source)
2015-04-29 06:53:35 -0600 received badge  Good Answer (source)
2015-01-08 10:06:55 -0600 edited question Instance failed to spawn

Unable to create instance, instance failed to spawn. Nova services are running properly.

nova service-list
+----+------------------+-------------------+----------+---------+-------+----------------------------+-----------------+<br>
| Id | Binary           | Host              | Zone     | Status  | State | Updated_at                 | Disabled Reason |
+----+------------------+-------------------+----------+---------+-------+----------------------------+-----------------+<br>
| 1  | nova-conductor   | Ubuntu-34.80      | internal | enabled | up    | 2015-01-08T15:18:06.000000 | -               |<br>
| 2  | nova-consoleauth | Ubuntu-34.80      | internal | enabled | up    | 2015-01-08T15:18:06.000000 | -               |<br>
| 3  | nova-scheduler   | Ubuntu-34.80      | internal | enabled | up    | 2015-01-08T15:18:05.000000 | -               |<br>
| 4  | nova-cert        | Ubuntu-34.80      | internal | enabled | up    | 2015-01-08T15:18:06.000000 | -               |<br>
| 5  | nova-compute     | Ubuntu-34.80      | nova     | enabled | up    | 2015-01-08T15:18:05.000000 | None      <br>

virsh list<br>
 Id    Name                           State<br>
----------------------------------------------------"

virsh -c qemu:///system list<br>
 Id    Name                           State<br>
----------------------------------------------------"

virsh dumpxml instance-00000039<br>
error: failed to get domain 'instance-00000039'<br>
error: Domain not found: no domain with matching name 'instance-00000039'<br>

I am not seeing error state for the instance. But nova show throws the error message. Output of nova show:

nova show 7d76ff4a-4369-48d2-b4f2-ed72d81bc3ae<br>
{"message": "Build of instance 7d76ff4a-4369-48d2-b4f2-ed72d81bc3ae was re-scheduled: create_port_precommit failed.", "code": 500, "details": "  File \"/usr/lib/python2.7/dist-packages/nova/compute/manager.py\", line 2036, in _do_build_and_run_instance |

Logs from nova-compute.log

2015-01-08 10:18:56.046 3368 TRACE nova.network.neutronv2.api [instance: 7d76ff4a-4369-48d2-b4f2-ed72d81bc3ae] InternalServerError: create_port_precommit failed.<br>
\n 2015-01-08 10:18:56.046 3368 TRACE nova.network.neutronv2.api [instance: 7d76ff4a-4369-48d2-b4f2-ed72d81bc3ae]<br>
2015-01-08 10:18:56.065 3368 ERROR nova.compute.manager [-] Instance failed network setup after 1 attempt(s)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager Traceback (most recent call last):<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages<br>/nova/compute/manager.py", line 1649, in _allocate_network_async
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     dhcp_options=dhcp_options)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 443, in allocate_for_instance<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     self._delete_ports(neutron, instance, created_port_ids)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 82, in __exit__<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     six.reraise(self.type_, self.value, self.tb)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 423, in allocate_for_instance<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     security_group_ids, available_macs, dhcp_opts)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 236, in _create_port<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     network_id, instance=instance)<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/excutils.py", line 82, in __exit__<br>
2015-01-08 10:18:56.065 3368 TRACE nova.compute.manager     six.reraise(self.type_, self.value, self.tb)<br>
2015-01-08 10:18 ...
(more)
2014-12-12 17:57:31 -0600 received badge  Nice Answer (source)
2014-12-12 06:02:40 -0600 commented question dashboard gives 500 error

Check the indentation, Python differentiates tabs and spaces; look before CACHE and make sure everything is ok.

2014-12-12 05:58:19 -0600 edited question dashboard gives 500 error

Hi I was trying to install dashboard of juno first time but I received the following error in httpd error.log

[Wed Dec 03 11:36:02.908363 2014] [:error] [pid 5627] [remote 10.20.30.128:26710] mod_wsgi (pid=5627): Exception occurred processing WSGI script '/usr/share/openstack-dashboard/openstack_dashboard/wsgi/django.wsgi'.
[Wed Dec 03 11:36:02.908431 2014] [:error] [pid 5627] [remote 10.20.30.128:26710] Traceback (most recent call last):
[Wed Dec 03 11:36:02.908457 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 187, in __call__
[Wed Dec 03 11:36:02.908562 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     self.load_middleware()
[Wed Dec 03 11:36:02.908578 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/core/handlers/base.py", line 44, in load_middleware
[Wed Dec 03 11:36:02.908680 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     for middleware_path in settings.MIDDLEWARE_CLASSES:
[Wed Dec 03 11:36:02.908696 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 54, in __getattr__
[Wed Dec 03 11:36:02.908778 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     self._setup(name)
[Wed Dec 03 11:36:02.908791 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 49, in _setup
[Wed Dec 03 11:36:02.908852 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     self._wrapped = Settings(settings_module)
[Wed Dec 03 11:36:02.908876 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/conf/__init__.py", line 128, in __init__
[Wed Dec 03 11:36:02.908902 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     mod = importlib.import_module(self.SETTINGS_MODULE)
[Wed Dec 03 11:36:02.908915 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
[Wed Dec 03 11:36:02.908983 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     __import__(name)
[Wed Dec 03 11:36:02.908995 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/settings.py", line 318, in <module>
[Wed Dec 03 11:36:02.909105 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     from local.local_settings import *  # noqa
[Wed Dec 03 11:36:02.909166 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]   File "/usr/share/openstack-dashboard/openstack_dashboard/wsgi/../../openstack_dashboard/local/local_settings.py", line 104
[Wed Dec 03 11:36:02.909175 2014] [:error] [pid 5627] [remote 10.20.30.128:26710]     CACHES = {
[Wed Dec 03 11:36:02.909179 2014] [:error] [pid 5627] [remote 10.20.30 ...
(more)
2014-12-11 08:13:30 -0600 answered a question how to remove nova-compute on controller

nova service-list and with service id nova service delete *id* should remove the service from the list.

2014-12-11 06:34:45 -0600 commented answer Ceilometer-api critical error OpenStack-IceHouse Ubuntu 14.04

@fresher check your libraries last time I faced this was a conflict of /usr/local/lib and /usr/lib/ paths, it can happen that your have two installations (package manage + git) of ceilometer.

2014-12-11 03:54:58 -0600 received badge  Favorite Question (source)
2014-12-11 03:53:04 -0600 received badge  Nice Answer (source)
2014-11-13 03:44:21 -0600 received badge  Necromancer (source)
2014-11-13 03:44:21 -0600 received badge  Self-Learner (source)
2014-11-10 05:05:20 -0600 marked best answer How does ceilometer recognize a new meter?

Hi all,

I am using ceilometer with kwapi to get the energy measurements from our servers and currently we have created a script to insert this samples from the api, I would like to know how I make ceilometer collect this data from the api without create any script and how ceilometer collect the samples.

Thanks.

2014-11-10 05:05:20 -0600 edited answer How does ceilometer recognize a new meter?

Hello guys,

Regarding how ceilometer collects the data from kwapi there is a post explaining all the necessary steps. Also there is a brief explanation of how to set the meters which ceilometer will collect the data (through the pipeline file).

Hope have been of great help.

Regards, Bruno.

2014-11-10 04:33:30 -0600 received badge  Popular Question
2014-10-29 10:36:25 -0600 edited question How to set up Cinder volumes correctly?

Hi, I am working on a server with a single physical HDD. I have installed Ubuntu 14.04 and using command:

sudo lsblk -o NAME,FSTYPE,SIZE,MOUNTPOINT,LABEL

I get this output:

NAME   FSTYPE   SIZE MOUNTPOINT LABEL
sda           837.9G
├─sda1 ext4   832.9G /
├─sda2            1K
├─sda4         1023K
└─sda5 swap       5G [SWAP]
sr0            1024M

I have set up the Cinder service but when I try inputting this command:

pvcreate /dev/sda1

I get as output: Can't open /dev/sda1 exclusively. Mounted filesystem?

What have I missed and how to set the volume(s) correctly?

2014-10-01 08:28:12 -0600 received badge  Famous Question (source)
2014-09-29 20:47:15 -0600 marked best answer Keystone - Unable to establish connection

Hello everyone,

In the past days I am struggling with keystone client, I need to get the list of tenants and performing keystone tenant-list results in the following error:

Unable to establish connection to http://192.168.0.2:35357/v2.0/tenants.

If the query is executed inside the server it returns the right values, but from outside (my computer for example) I get the above error. Does someone has an idea of what could be the issue?

Debugging keystone I could notice that the token is being generated but the query is not being performed:

DEBUG:keystoneclient.session:REQ: curl -i -X GET http://192.168.0.2:35357/v2.0/tenants -H "User-Agent: python-keystoneclient" -H "X-Auth-Token: 614292a25121408e974d715f44fce6e2" INFO:requests.packages.urllib3.connectionpool:Starting new HTTP connection (1): 192.168.0.2.