lufaxo's profile - activity

2017-07-04 06:50:57 -0600 received badge  Famous Question (source)
2016-11-09 05:38:34 -0600 received badge  Famous Question (source)
2016-11-09 05:38:34 -0600 received badge  Notable Question (source)
2016-11-09 05:38:34 -0600 received badge  Popular Question (source)
2016-08-17 05:21:22 -0600 received badge  Notable Question (source)
2016-08-10 00:33:38 -0600 received badge  Famous Question (source)
2016-07-25 06:37:54 -0600 received badge  Notable Question (source)
2016-06-02 03:10:46 -0600 received badge  Famous Question (source)
2016-04-28 05:20:42 -0600 received badge  Famous Question (source)
2016-04-15 15:30:29 -0600 received badge  Popular Question (source)
2016-04-15 15:29:19 -0600 received badge  Notable Question (source)
2016-04-15 15:28:54 -0600 received badge  Popular Question (source)
2016-04-15 15:28:54 -0600 received badge  Notable Question (source)
2016-04-15 15:28:49 -0600 received badge  Notable Question (source)
2016-03-12 08:21:42 -0600 received badge  Popular Question (source)
2016-03-10 01:38:04 -0600 answered a question linux bridge physical interface mapping

Found the problem. instead of

[linux_bridge]
physical_interface_mappings = vxlan-98:eth1,external:eth2

it should be

[linux_bridge]
physical_interface_mappings = vxlan:eth1,external:eth2
2016-03-10 01:36:33 -0600 asked a question Neutron LinuxBridge: RTNETLINK: No such file

My neutron-plugin-linuxbridge-agent.log shows:

 2016-03-10 08:32:08.832 2765 ERROR neutron.agent.linux.utils [req-899a9012-e4d5-4554-9839-41c41a828d0d - - - - -]
Command: ['sudo', '/usr/bin/neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'bridge', 'fdb', 'del', 'fa:16:3e:03:61:1d', 'dev', 'vxlan-94', 'dst', '192.168.2.30']
Exit code: 2
Stdin:
Stdout:
Stderr: RTNETLINK answers: No such file or directory

Where does this come from?

2016-03-09 13:26:47 -0600 commented answer CPU hot plugging in Openstack

that would be a cold plug and not a hot plug.

2016-03-07 13:51:40 -0600 commented answer Instance gets dhcp IP but fails to connect to metadata server

Also had that problem more than once when setting up openstack. guess that layer 8 ist the most error prone

2016-03-07 13:06:59 -0600 asked a question metadata working, user-data not

My metadata proxy shows, that the meta-data can be obtained, but the user-data cannot:

2016-03-07 19:36:44.860 1893 INFO neutron.wsgi [-] 192.168.2.46 - - [07/Mar/2016 19:36:44] "GET /2009-04-04/user-data HTTP/1.1" >>>>>>>404<<<<<<<<< 278 97.273280
2016-03-07 19:36:44.883 1893 INFO neutron.wsgi [-] 192.168.2.46 - - [07/Mar/2016 19:36:44] "GET /2009-04-04/meta-data/ HTTP/1.1"  >>>>>>>200<<<<<<<<< 341 80.233456
2016-03-07 19:36:44.900 1893 INFO neutron.wsgi [-] 192.168.2.46 - - [07/Mar/2016 19:36:44] "GET /2009-04-04/user-data HTTP/1.1"  >>>>>>>404<<<<<<<<<  278 103.328568
2016-03-07 19:36:44.908 1893 INFO neutron.wsgi [-] 192.168.2.46 - - [07/Mar/2016 19:36:44] "GET /2009-04-04/meta-data/ HTTP/1.1" >>>>>>>200<<<<<<<<< 341 86.267612
2016-03-07 19:37:30.435 1893 INFO neutron.wsgi [-] 192.168.2.46 - - [07/Mar/2016 19:37:30] "GET /2009-04-04/user-data HTTP/1.1"  >>>>>>>404<<<<<<<<<  278 136.837150

Since the meta-data agent is working correctly, i'd say that my metadata_agent.ini and nova.conf is correct. but why is the user-data 404 "not found"?

2016-03-07 12:47:01 -0600 received badge  Popular Question (source)
2016-03-04 00:13:51 -0600 received badge  Popular Question (source)
2016-03-03 14:33:37 -0600 answered a question linux bridge ovs-cleanup

The problem was that aptitude did (somehow) not delete the neutron-openvswitch-agent and I had to manually delete it with dpkg -f --purge . now everything is fine.

2016-03-03 14:31:52 -0600 received badge  Enthusiast
2016-03-02 05:00:00 -0600 asked a question linux bridge physical interface mapping

I am running OpenStack Liberty on a three node setup on ubuntu server 14.04 with the official canonical cloudarchive repository.

I've setup an ext-net which is a flat network. And my demo-net uses vxlan(segmention-id: 98).

The problem is that the eth2 on the network node is correctly connected to eth2, but the internal instance-tunnel bridge (vxlan-98) is not.

My linux-bridge configuration (ML2) is.

[linux_bridge]
physical_interface_mappings = vxlan-98:eth1,external:eth2

[vxlan]
enable_vxlan = True
local_ip = 192.168.2.10
l2_population = True

[agent]
prevent_arp_spoofing = True

[securitygroup]
enable_security_group = True
enable_ipset = True
firewall_driver = neutron.agent.linux.iptables_firewall.IptablesFirewallDriver

brctl shows:

network:~$ brctl show
bridge name     bridge id               STP enabled     interfaces
brq60960441-d6          8000.00e07d8bcd8b       no              eth2
                                                        tapce854a52-72
brqbe23e062-4e          8000.0060085c8491       no              
                                                        tap4d535359-3d
                                                        tapcc83ffb3-43
                                                        vxlan-94

If i manually connect brqbe23e062-4e (instance tunnel bridge) with eth1, everything works fine, so I guess, that the

physical_interface_mappings = vxlan-98:eth1,external:eth2

line is wrong.

2016-03-01 13:28:54 -0600 asked a question linux bridge ovs-cleanup

Although my servers are using linux bridges, neutron still executes the ovs-cleanup script. Of course this doesn't work, because there is no ovs installed. But still it tries to do the cleanup stuff. I've already uninstalled the neutron-plugin-openvswitch and neutron-plugin-openvswitch-agent. Did I miss something?

2016-03-01 13:18:24 -0600 asked a question neutron extension not supported

My neutron server log running on the network node of a 3 node setup, shows these log entries:

2016-03-01 20:10:43.379 8403 WARNING neutron.api.extensions [-] Extension address-scope not supported by any of loaded plugins
2016-03-01 20:10:43.422 8403 WARNING neutron.api.extensions [-] Extension metering not supported by any of loaded plugins
2016-03-01 20:10:43.427 8403 WARNING neutron.api.extensions [-] Extension port-security not supported by any of loaded plugins
2016-03-01 20:10:43.434 8403 WARNING neutron.api.extensions [-] Extension qos not supported by any of loaded plugins
2016-03-01 20:10:43.441 8403 WARNING neutron.api.extensions [-] Extension router-service-type not supported by any of loaded plugins
2016-03-01 20:10:43.447 8403 WARNING neutron.api.extensions [-] Extension service-type not supported by any of loaded plugins
2016-03-01 20:10:43.450 8403 WARNING neutron.api.extensions [-] Extension vlan-transparent not supported by any of loaded plugins

Did I forgot to enable some settings?

2016-03-01 12:11:45 -0600 commented question no DHCP lease - Loopingcall (oslo)

Fixed by restarting all nodes...

2016-03-01 12:08:10 -0600 commented answer glance error: unrecognized argument

openstack image create --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 --public cirros2

works. probably you are not using the newest version of the openstack-cli.

2016-03-01 10:15:32 -0600 received badge  Notable Question (source)
2016-03-01 03:07:43 -0600 answered a question glance error: unrecognized argument

Try using the openstack - cli:

openstack image create --file cirros-0.3.4-x86_64-disk.img --disk-format qcow2 \
–container-format bare --public cirros
2016-03-01 02:50:12 -0600 asked a question no DHCP lease - Loopingcall (oslo)

My dhcp-agent.log on the network node shows:

2016-02-29 17:10:33.021 1334 WARNING oslo.service.loopingcall [req-279bfd07-c370-421b-9ad9-58c74f909227 - - - - -] Function 'neutron.agent.dhcp.agent.DhcpAgentWithStateReport._report_state' run outlasted interval by 28.13 sec

I am not quite sure if this is the reason why my instances aren't getting dhcp leases, but it still worries me a little bit. Is this something bad?

2016-02-29 10:04:26 -0600 commented answer neutron <-> nova problems

Seems like the [nova] section isn't working. You are right, thanks, man!

2016-02-29 08:08:53 -0600 received badge  Popular Question (source)
2016-02-29 06:20:16 -0600 commented question neutron <-> nova problems

added keystone endpoints.

2016-02-29 02:48:42 -0600 received badge  Editor (source)
2016-02-29 02:25:02 -0600 asked a question neutron <-> nova problems

On my controller node (where neutron-server) is installed, I am getting the following error:

2016-02-29 09:13:04.754 2269 ERROR neutron.notifiers.nova [-] Failed to notify nova on events: [{'status': 'completed', 'tag': u'3848c4d3-6ff1-4a70-9915-858205b844fa', 'name': 'network-vif-plugged', 'server_uuid': u'a8c26412-b8be-40d4-930a-96a399cb135d'}]
// Stacktrace shortened
2016-02-29 09:13:04.754 2269 ERROR neutron.notifiers.nova     raise exceptions.DiscoveryFailure(msg)
2016-02-29 09:13:04.754 2269 ERROR neutron.notifiers.nova DiscoveryFailure: Could not determine a suitable URL for the plugin

The configuration is (neutron.conf):

[DEFAULT]
...
notify_nova_on_port_status_changes = True
notify_nova_on_port_data_changes = True
nova_url = http://controller.herz.lan:8774/v2
[nova]
auth_url = http://controller.herz.lan:35357/v2.0
auth_plugin = password
project_domain_id = default
user_domain_id = default
region_name = Herzogenburg
project_name = service
user-name = nova
password = PA33W0RD

... which corresponds to my configuration.

I am running Liberty on 3 nodes with Ubuntu LTS 14.04.4

My endpoint-list:

+----------------------------------+--------------+---------------------------------------------------+
| ID                               | Service Name | URL                                               |
+----------------------------------+--------------+---------------------------------------------------+
| 11f605fce21d4d0a80668930c562c536 | nova         | http://controller.herz.lan:8774/v2/%(tenant_id)s   |
| 1a77eea5c86145aea607c49684154045 | cinder       | http://controller.herz.lan:8776/v1/%(tenant_id)s   |
| 235779324562480cbbb08f77c64fbf6e | glance       | http://controller.herz.lan:9292                    |
| 257b1bc3b52c43a38ce56f6d6f62acb6 | glance       | http://controller.herz.lan:9292                    |
| 4ef428c2cefc419e89985f9e6db584f8 | cinder       | http://controller.herz.lan:8776/v1/%(tenant_id)s   |
| 61d3f8cef7184d23b1dccbb1585ad3d7 | nova         | http://controller.herz.lan:8774/v2/%(tenant_id)s   |
| 6559537dbd7846569930e0479c2c356b | cinder       | http://controller.herz.lan:8776/v1/%(tenant_id)s   |
| 6d970dc5d8ff47b3844a62f854d19900 | keystone     | http://controller.herz.lan:5000/v2.0               |
| 77a58094d2864438b198658070033ec4 | cinderv2     | http://controller.herz.lan:8776/v2/%(tenant_id)s   |
| 82b9b10f0b3e446aa98965b483f85d61 | glance       | http://controller.herz.lan:9292                    |
| 8f9056ca2db0450c8bcefed22c6b2f6d | neutron      | http://controller.herz.lan:9696                    |
| 94642aaf31354f5ba1dd77bd19f4a2e6 | neutron      | http://controller.herz.lan:9696                    |
| 9c1c50b4f1c94c158a7c33ca7f91dda8 | cinderv2     | http://controller.herz.lan:8776/v2/%(tenant_id)s   |
| 9f3de1e97e9a409cab5645e381d6cea8 | trove        | http://controller.herz.lan:8779/v1.0/%(tenant_id)s |
| a7290a0df25d4cd9bd2aa6224834e1ab | nova         | http://controller.herz.lan:8774/v2/%(tenant_id)s   |
| a9cc7413e80144ee8047f63146aa0017 | keystone     | http://controller.herz.lan:5000/v2.0               |
| b5a3cc78f62a4ba980af5153a0855529 | trove        | http://controller.herz.lan:8779/v1.0/%(tenant_id)s |
| b7cd782a9b26443b8333fc8bf1a7eddf | neutron      | http://controller.herz.lan:9696                    |
| b7d9db76da294b17bfcde486aa8732bb | keystone     | http://controller.herz.lan:35357/v2.0              |
| bf05c982cffa42ad84eb06569c8f9a1f | trove        | http://controller.herz.lan:8779/v1.0/%(tenant_id)s |
| dfa0f69f9a2b4cc1b7c70214ec90ee9e | cinderv2     | http://controller.herz.lan:8776/v2/%(tenant_id)s   |
+----------------------------------+--------------+---------------------------------------------------+
2016-02-25 09:48:01 -0600 commented answer liberty endpoint and keystone_authtoken

Thank you!

2016-02-25 09:47:44 -0600 marked best answer liberty endpoint and keystone_authtoken

I'm currently setting up glance to work with keystone:

Keystone Endpoints:

| x | r1 | keystone     | identity     | True    | internal  | http://controller:5000/v3
| x | r1 | keystone     | identity     | True    | public    | http://controller:5000/v3
| x | r1 | keystone     | identity     | True    | admin     | http://controller:35357/v3

and the glance endpoints:

| x | r1| glance       | image        | True    | public    | http://controller:9292
| x | r1| glance       | image        | True    | admin     | http://controller:9292
| x | r1| glance       | image        | True    | internal  | http://controller:9292

and the following glance-api and glance registry configuration:

auth_strategy = keystone

[keystone_authtoken]
auth_uri = http://controller:5000/v3     #versioned
auth_url = http://controller:35357
admin_tenant_name = service
admin_user = glance
admin_password = x
auth_version = 3

But I always get 401 Unauthenticated.

Where do I put the versioned endpoint, and which url/uris are correct?

Could someone post a valid authentication section from liberty and identity api 3?

Whats the difference between auth_url, auth_uri and identity_uri? which has to be versioned?

2016-02-25 09:47:43 -0600 received badge  Scholar (source)