dro's profile - activity

2015-10-16 05:37:43 -0600 received badge  Famous Question (source)
2014-08-19 04:03:50 -0600 received badge  Famous Question (source)
2014-06-16 19:17:41 -0600 received badge  Good Answer (source)
2014-06-09 11:24:05 -0600 received badge  Notable Question (source)
2014-05-16 05:23:01 -0600 received badge  Notable Question (source)
2014-05-15 21:51:51 -0600 answered a question Why do not need set promiscuous mode of data nic in OpenStack vlan?

Where did you see this? I think I got something similar and no, nothing has to be done to the NIC. Can you give us more info?

2014-05-15 16:56:44 -0600 answered a question HTTP 500 error when running keystone

did you follow the instruction on chp3 of the openstack setup manual, specifically exporting token?

$ export OS_SERVICE_TOKEN=ADMIN_TOKEN   # you get this token from /etc/keystone/keystone.conf 
$ export OS_SERVICE_ENDPOINT=http://controller:35357/v2.0
2014-05-15 16:49:25 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible

so my netconfig is as follows

internal: 10.10.10.0/24 external: 172.16.1.0/16

see my network lists

+--------------------------------------+----------------+----------------------------------------------------+
| id                                   | name           | subnets                                            |
+--------------------------------------+----------------+----------------------------------------------------+
| 3cd0c43d-d35b-4a9e-bdec-e9487a5cd947 | network-public | 41e5d473-116a-49de-8c3f-6db6b99ac1a1 172.16.0.0/16 |
| ce922458-2c3b-47f3-a803-0e0bc5b8bcc6 | network-demo   | ee438124-dc63-4649-be48-514325d11c66 10.10.10.0/24 |
+--------------------------------------+----------------+----------------------------------------------------+
[root@network openstack_scripts]# neutron subnet-list
+--------------------------------------+---------------+---------------+------------------------------------------------+
| id                                   | name          | cidr          | allocation_pools                               |
+--------------------------------------+---------------+---------------+------------------------------------------------+
| 41e5d473-116a-49de-8c3f-6db6b99ac1a1 | subnet-public | 172.16.0.0/16 | {"start": "172.16.1.80", "end": "172.16.1.90"} |
| ee438124-dc63-4649-be48-514325d11c66 | subnet-demo   | 10.10.10.0/24 | {"start": "10.10.10.2", "end": "10.10.10.254"} |
+--------------------------------------+---------------+---------------+------------------------------------------------+
[root@network openstack_scripts]# neutron router-list
+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| id                                   | name        | external_gateway_info                                                       |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| 1cbefb18-e0ec-4e26-a9f7-4eb77ccd4830 | router-demo | {"network_id": "3cd0c43d-d35b-4a9e-bdec-e9487a5cd947", "enable_snat": true} |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+

root@network openstack_scripts]# neutron router-port-list  router-demo
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 08310df4-1a95-402a-92bb-afdb71490620 |      | fa:16:3e:dc:00:31 | {"subnet_id": "41e5d473-116a-49de-8c3f-6db6b99ac1a1", "ip_address": "172.16.1.80"} |
| 7bec64b9-4ef5-4aab-9c0b-565c2b7e9d5b |      | fa:16:3e:8a:5a:a6 | {"subnet_id": "ee438124-dc63-4649-be48-514325d11c66", "ip_address": "10.10.10.1"}  |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+

ports list

[root@network openstack_scripts]# neutron port-list
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                          |
+--------------------------------------+------+-------------------+------------------------------------------------------------------------------------+
| 08310df4-1a95-402a-92bb-afdb71490620 |      | fa:16 ...
(more)
2014-05-15 15:49:12 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible
  1. I belive your OVS bridge br-ex is not configured properly. It's supposed to have eth0 as OVS port. ( not eth2). Ifconfig report shoud show br-ex with IP 172.16.1.211 and eth0 with no IP at all
  • Im following the instructions in the Openstack setup for ICEHOUSE. It says to add the bridge and use eht2

    ovs-vsctl add-br br-int

    ovs-vsctl add-br br-ex

    ovs-vsctl add-port br-ex eth2

when I try to add it , again, it says:

[root@network network-scripts]# ovs-vsctl add-port br-ex eth2
ovs-vsctl: cannot create a port named eth2 because a port named eth2 already exists on bridge br-ex
  1. when I added the public network 172.16.1.0/16, I used the cidr 172.16.1.0/16, but it defaults to 172.16.0.0/16. I don't think it matters, since I have servers on different networks on 172.16.x.x and they ...
(more)
2014-05-15 02:55:03 -0600 received badge  Famous Question (source)
2014-05-12 09:50:41 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible

Thank, let me look into it.

2014-05-10 16:18:38 -0600 received badge  Popular Question (source)
2014-05-10 03:04:39 -0600 received badge  Popular Question (source)
2014-05-09 17:21:23 -0600 commented question icehouse RHEL external port down| VMs with external IPS not accessible

I completely deleted my network configs and recreated the networks, minus different names, per the openstack setup document : I did the ip netns exec ping command , to my new ip address and one does ping back, the others don't.

[root@network ~]# neutron net-list
+--------------------------------------+--------------+------------------------------------------------------+
| id                                   | name         | subnets                                              |
+--------------------------------------+--------------+------------------------------------------------------+
| 5c433a49-5bb7-4070-b9e3-529ff74bcc2b | net-internal | caa90c7f-a093-4cb0-8263-84e6d5bb2d48 192.168.20.0/24 |
| 842ac3e5-ba51-4dc9-9bd2-13b7d977ac35 | net-public   | 83e692d2-c2ae-4458-bbfb-4855ca28c549 172.16.0.0/16   |
+--------------------------------------+--------------+------------------------------------------------------+
[root@network ~]# neutron subnet-list
n+--------------------------------------+--------------+-----------------+----------------------------------------------------+
| id                                   | name         | cidr            | allocation_pools                                   |
+--------------------------------------+--------------+-----------------+----------------------------------------------------+
| 83e692d2-c2ae-4458-bbfb-4855ca28c549 | sub-public   | 172.16.0.0/16   | {"start": "172.16.1.90", "end": "172.16.1.100"}    |
| caa90c7f-a093-4cb0-8263-84e6d5bb2d48 | sub-internal | 192.168.20.0/24 | {"start": "192.168.20.2", "end": "192.168.20.254"} |
+--------------------------------------+--------------+-----------------+----------------------------------------------------+
[root@network ~]# neutron router-list
+--------------------------------------+-----------------+-----------------------------------------------------------------------------+
| id                                   | name            | external_gateway_info                                                       |
+--------------------------------------+-----------------+-----------------------------------------------------------------------------+
| 45a51d3d-237a-48b4-ace2-813c8640c2a1 | router-internal | {"network_id": "842ac3e5-ba51-4dc9-9bd2-13b7d977ac35", "enable_snat": true} |
+--------------------------------------+-----------------+-----------------------------------------------------------------------------+
[root@network ~]# neutron port-list
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                           |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| 27d68d59-ed96-4c9e-a816-f25c56722a78 |      | fa:16:3e:ec:3b:ac | {"subnet_id": "83e692d2-c2ae-4458-bbfb-4855ca28c549", "ip_address": "172.16.1.90"}  |
| 96b896f9-25cf-4d24-82be-b9645bc519f7 |      | fa:16:3e:de:11:12 | {"subnet_id": "caa90c7f-a093-4cb0-8263-84e6d5bb2d48 ...
(more)
2014-05-09 15:50:55 -0600 received badge  Commentator
2014-05-09 15:50:55 -0600 commented question icehouse RHEL external port down| VMs with external IPS not accessible

I'm not running Ubuntu :( , I'm running CentOS

2014-05-09 14:05:56 -0600 commented question icehouse RHEL external port down| VMs with external IPS not accessible

Yes my setup is multi node, 1 controller, 1 network and 1 compute node.

from controller node

+--------------------------------------+----------+-----------------------------------------------------+
| id                                   | name     | subnets                                             |
+--------------------------------------+----------+-----------------------------------------------------+
| 30222486-4282-4051-bf1b-1f7ff0833c97 | net1     | 43b4606c-4d31-45c5-8d2d-54388317291b 10.0.0.0/24    |
|                                      |          | affa2937-f2da-4c0d-9e10-f37169e8ebce 10.0.20.0/24   |
| 5885e881-0b1c-44e4-b143-ddf63953dba8 | ext-net  | c606f236-05ac-4595-acfc-ccaa71dc9ec1 172.16.0.0/16  |
| 952c9658-5405-44ce-978f-f55b99c629f1 | demo-net | e2c8f5db-1fdb-40cb-b8f7-ccdc5cada16b 192.168.1.0/24 |
| a39656e3-b5a7-448e-8ec4-0e66b3b3e4e9 | net2     | 40164aef-3a2f-4974-b0c2-05e7b1069fb0 10.0.30.0/24   |
|                                      |          | ccc3b749-2a81-403a-8f7d-163c3023c204 10.0.1.0/24    |
| f4c75bb0-a7bf-4190-a329-d423c284bf25 | public   |                                                     |
+--------------------------------------+----------+-----------------------------------------------------+

+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| id                                   | name        | external_gateway_info                                                       |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| 6dcf46c4-690c-44cd-b17e-85652ce0e6b7 | router1     | {"network_id": "5885e881-0b1c-44e4-b143-ddf63953dba8", "enable_snat": true} |
| c9e4e2fa-211c-4178-b571-7976967b2f8d | demo-router | {"network_id": "5885e881-0b1c-44e4-b143-ddf63953dba8", "enable_snat": true} |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+

ifconfig on controller only shows my management interface, and ovs-vsctl show, displays nothing. Below is from the controller node output .

[root@network ~]# ifconfig
br-ex     Link encap:Ethernet  HWaddr 4A:C9:91:59:31:44
          inet6 addr: fe80::48c9:91ff:fe59:3144/64 Scope:Link
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 ...
(more)
2014-05-09 12:39:14 -0600 commented question icehouse RHEL external port down| VMs with external IPS not accessible

OK, I'm still getting use to using this interface.

I am able to attach my router to the external network, but i cannot ping the public/external interface.

[root@network ~]# neutron router-port-list router1
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                           |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+
| 15f39ba8-fb72-48cb-ab34-a0649ee5205d |      | fa:16:3e:33:94:2e | {"subnet_id": "40164aef-3a2f-4974-b0c2-05e7b1069fb0", "ip_address": "10.0.30.1"}    |
| 1ced9937-a97a-4fc0-985b-fa9369dfc4a9 |      | fa:16:3e:b0:aa:f4 | {"subnet_id": "affa2937-f2da-4c0d-9e10-f37169e8ebce", "ip_address": "10.0.20.1"}    |
| 5399e2eb-df70-4fbe-9661-7ada364f3007 |      | fa:16:3e:af:d0:c3 | {"subnet_id": "c606f236-05ac-4595-acfc-ccaa71dc9ec1", "ip_address": "172.16.1.119"} |
| d0c82367-1103-48c3-964c-cb86a616b1c2 |      | fa:16:3e:33:4e:4a | {"subnet_id": "ccc3b749-2a81-403a-8f7d-163c3023c204", "ip_address": "10.0.1.1"}     |
| f80627f0-a688-4be5-bb9f-5a0279844d92 |      | fa:16:3e:21:f5:d9 | {"subnet_id": "43b4606c-4d31-45c5-8d2d-54388317291b", "ip_address": "10.0.0.1"}     |
+--------------------------------------+------+-------------------+-------------------------------------------------------------------------------------+

[root@network ~]# ping 172.16.1.119
PING 172.16.1.119 (172.16.1.119) 56(84) bytes of data.
From 172.16.1.211 icmp_seq=2 Destination Host Unreachable
From 172.16.1.211 icmp_seq=3 Destination Host Unreachable
From ...
(more)
2014-05-09 10:45:12 -0600 commented question icehouse RHEL external port down| VMs with external IPS not accessible

I was able to get the output for ip netns list

[root@network ~]# ip netns list
qdhcp-952c9658-5405-44ce-978f-f55b99c629f1
qdhcp-a39656e3-b5a7-448e-8ec4-0e66b3b3e4e9
qrouter-6dcf46c4-690c-44cd-b17e-85652ce0e6b7
qdhcp-30222486-4282-4051-bf1b-1f7ff0833c97
qrouter-c9e4e2fa-211c-4178-b571-7976967b2f8d

and here is the output of the routers

[

root@network ~]# ip netns exec qrouter-c9e4e2fa-211c-4178-b571-7976967b2f8d iptables -S -t nat
-P PREROUTING ACCEPT
-P POSTROUTING ACCEPT
-P OUTPUT ACCEPT
-N neutron-l3-agent-OUTPUT
-N neutron-l3-agent-POSTROUTING
-N neutron-l3-agent-PREROUTING
-N neutron-l3-agent-float-snat
-N neutron-l3-agent-snat
-N neutron-postrouting-bottom
-A PREROUTING -j neutron-l3-agent-PREROUTING
-A POSTROUTING -j neutron-l3-agent-POSTROUTING
-A POSTROUTING -j neutron-postrouting-bottom
-A OUTPUT -j neutron-l3-agent-OUTPUT
-A neutron-l3-agent-POSTROUTING ! -i qg-8b4cf2c0-3b ! -o qg-8b4cf2c0-3b -m conntrack ! --ctstate DNAT -j ACCEPT
-A neutron-l3-agent-PREROUTING -d 169.254.169.254/32 -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 9697
-A neutron-l3-agent-snat -j neutron-l3-agent-float-snat
-A neutron-l3-agent-snat -s 192.168.1.0/24 -j SNAT --to-source 172.16.1.110
-A neutron-postrouting-bottom -j neutron-l3-agent-snat
[root@network ~]# ip netns exec qrouter-6dcf46c4-690c-44cd-b17e-85652ce0e6b7 iptables -S -t nat
-P PREROUTING ACCEPT
-P POSTROUTING ACCEPT
-P OUTPUT ACCEPT
-N neutron-l3-agent-OUTPUT ...
(more)
2014-05-09 10:26:41 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible

strange I have output now when I run

ip netns list

[root@network ~]# ip netns list
qdhcp-952c9658-5405-44ce-978f-f55b99c629f1
qdhcp-a39656e3-b5a7-448e-8ec4-0e66b3b3e4e9
qrouter-6dcf46c4-690c-44cd-b17e-85652ce0e6b7
qdhcp-30222486-4282-4051-bf1b-1f7ff0833c97

this output is only available from the network node, not the controller, is this ok?

2014-05-09 10:23:04 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible

I have that setup in in my "network node" configuration, /etc/neutron/dhcp_agent.ini

[DEFAULT]
interface_driver = neutron.agent.linux.interface.OVSInterfaceDriver
dhcp_driver = neutron.agent.linux.dhcp.Dnsmasq
use_namespaces = True

heres the link to the instructions

http://docs.openstack.org/icehouse/in... , I am using the APR 18th version, the most current is may 4. I can go through and see if anything has changed but really, its cut and paste into the command line

2014-05-09 08:22:14 -0600 commented answer icehouse RHEL external port down| VMs with external IPS not accessible

I followed the setup on the latest openstack icehouse manual, I'm basically doing copy and paste, so not sure what i messed up. I only do the ML2 plugin, I DO NOT, follow through and do the Open vSwitch (OVS) plugin-in. Do I need to do that? Initially I was able to ping my the first available public ip, but i then deleted all networks, subnets, routers, ports and started over, not nothing works. As you can see below its creating networks, subnets etc... this is the same issue for both my openstack setups. (Their both demo and both are virtual machines, none are real hardware)

+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| id                                   | name        | external_gateway_info                                                       |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+
| 6dcf46c4-690c-44cd-b17e-85652ce0e6b7 | router1     | null                                                                        |
| c9e4e2fa-211c-4178-b571-7976967b2f8d | demo-router | {"network_id": "5885e881-0b1c-44e4-b143-ddf63953dba8", "enable_snat": true} |
+--------------------------------------+-------------+-----------------------------------------------------------------------------+
[root@controller ~]# neutron net-list
+--------------------------------------+----------+-----------------------------------------------------+
| id                                   | name     | subnets                                             |
+--------------------------------------+----------+-----------------------------------------------------+
| 30222486-4282-4051-bf1b-1f7ff0833c97 | net1     | 43b4606c-4d31-45c5-8d2d-54388317291b 10.0.0.0/24    |
| 5885e881-0b1c-44e4-b143-ddf63953dba8 | ext-net  | c606f236-05ac-4595-acfc-ccaa71dc9ec1 172.16.0.0/16  |
| 952c9658-5405-44ce-978f-f55b99c629f1 | demo-net | e2c8f5db-1fdb-40cb-b8f7-ccdc5cada16b 192.168.1.0/24 ...
(more)
2014-05-08 15:41:26 -0600 answered a question icehouse RHEL external port down| VMs with external IPS not accessible

as admin, i don't see anything when running

ip netns list

is there an error in the configuration?

2014-05-08 15:05:50 -0600 answered a question 500 error when trying to create image

check your keystone logs, this looks like a password configuration issue. What is the output of the keystone logs. I think you will find the error there.

2014-05-08 15:03:34 -0600 answered a question Is the host computer firewall necessary? Icehouse

So can I disable it then? I would be providing hardware firewall into the network where i would block/allow traffic.

thanks for you response! :P

2014-05-08 13:08:55 -0600 asked a question Icehouse, how to troubleshoot neutron issue

Is there a specific steps one can use to troubleshoot Icehouse, neutron networking specifically? I am unable to connect to my virtual machines. I guess, what I'd like is a guide, but I don't see specifics on what to look for in the documentation, if someone can point me in the right direction or provide and overview, I would appreciate it.

2014-05-08 13:05:52 -0600 asked a question Is the host computer firewall necessary? Icehouse

I just ran to an issue where the network node was not able to communicate with the message server, "controller" , when I disabled the firewall on the controller, I saw that it was able to connect without issue. Is the firewall necessary on the host machines?, controller, network and compute?

thanks

2014-05-05 11:38:42 -0600 received badge  Famous Question (source)
2014-05-05 09:16:04 -0600 received badge  Nice Answer (source)
2014-04-29 00:12:11 -0600 received badge  Famous Question (source)
2014-04-26 04:23:04 -0600 received badge  Notable Question (source)
2014-04-25 14:26:30 -0600 received badge  Popular Question (source)
2014-04-25 08:36:29 -0600 received badge  Enthusiast
2014-04-24 18:57:47 -0600 asked a question icehouse RHEL external port down| VMs with external IPS not accessible

I have several issues with my new installation. But ill add different questions in ask.openstack

I did not install openswitch plugin, i am using the ML2 plugin

The issue is networking with my new VMS. i have a demo network, demo subnet, demo router. The router has two interfaces, one for the internal network, the other for the external. I am able to ping the external port IP 172.16.11.10, but state says its DOWN, VM IPS 172.16.11.16 and 172.16.11.18, I am not able to ping any vas with public IPS on the 172.16.11.0/16 network. I have two VMS currently running.

Does the router saying its DOWN? Says its down, but i can ping 172.16.11.10 , but thats it.

 root@controller ~]# neutron port-show 82f675e4-3843-48b2-af99-da7d98139ae1
    +-----------------------+-------------------------------------------------------------------------------------+
    | Field                 | Value                                                                               |
    +-----------------------+-------------------------------------------------------------------------------------+
    | admin_state_up        | True                                                                                |
    | allowed_address_pairs |                                                                                     |
    | binding:host_id       | network                                                                             |
    | binding:profile       | {}                                                                                  |
    | binding:vif_details   | {"port_filter": true, "ovs_hybrid_plug": true}                                      |
    | binding:vif_type      | ovs                                                                                 |
    | binding:vnic_type     | normal                                                                              |
    | device_id             | dd6d5c92-e93a-4583-8a82-d45b728868c6                                                |
    | device_owner          | network:router_gateway                                                              |
    | extra_dhcp_opts       |                                                                                     |
    | fixed_ips             | {"subnet_id": "d09ccb0b-5e78-4f35-814e-d9298d9b9781", "ip_address": "172.16.11.10"} |
    | id                    | 82f675e4-3843-48b2-af99-da7d98139ae1                                                |
    | mac_address           | fa:16:3e:a4:3e:31                                                                   |
    | name                  |                                                                                     |
    | network_id            | abc33382-5f10-45a8-b9d6-1282f76dcedc                                                |
    | security_groups       |                                                                                     |
    | status                | DOWN                                                                                |
    | tenant_id             |                                                                                     |
    +-----------------------+-------------------------------------------------------------------------------------+
2014-04-24 17:16:21 -0600 commented answer Famous Glance HTTP500 error. I believe I have things configured correctly. Help a brother out!

grep admin_password from /etc/glance/* see if they all match what you changed it it with the keystone user-password-update

I don't see what else it could be.

2014-04-24 13:24:03 -0600 answered a question Famous Glance HTTP500 error. I believe I have things configured correctly. Help a brother out!

it says right there bro, keystone and glance authorization failed, you need to make sure your glance configs have correct password specified for the admin id "glance" . You can change the glance user password. I'm still learning, but I had this issue for another service and I verified the password in the config file and changed it and also changed the glance admin user id password

make sure you know the password in /etc/glance/

list the users

  1. source the admin file

keystone-user list

| c23a77f5dd914e91915f20ff857b9b1c | admin | True | alex@ | 0d6e2a40e2024a7b9320f38c73384dea | demo | True | demo@ | e68f204570664dd1a00fd17656291075 | glance | True | glance@ < -- | 09bd71defdd84b06bde6ea1bbeedce6a | neutron | True | neutron@ | 1be47cc87e524122b423fc2d4a6d9a86 | nova | True | nova@

keystone user-password-update --pass <newpassword> glance

then try it again, hope it helps.

2014-04-24 10:38:18 -0600 edited answer internal server 500 dashboard icehouse

9lives, thanks for the response. I found the error, it appears DJANGO is just as picky about indentation as PYTHON is. I found an unexpected indentation error in /etc/openstack-dashboard/local_settings

[Thu Apr 24 08:08:12 2014] [error] [client 172.16.1.10]      CACHES = {
[Thu Apr 24 08:08:12 2014] [error] [client 172.16.1.10]     ^
[Thu Apr 24 08:08:12 2014] [error] [client 172.16.1.10]  IndentationError: unexpected indent

I fixed the the indentation and the dashboard came up fine.

Thanks!

2014-04-24 09:55:11 -0600 received badge  Notable Question (source)
2014-04-24 09:36:48 -0600 received badge  Self-Learner (source)
2014-04-24 09:36:48 -0600 received badge  Teacher (source)