<div dir="ltr"><div><div><div>Hi, <br><br></div>As you can see that those two ports are for:<br></div> 1. interface port for internal subnet<br></div> 2. Access gateway port for external subnet.<br><div>
<div><br>[root@blitzen nova]# quantum port-list -c id -c fixed_ips -c device_owner<br>+-----------------------------<div>---------+---------------------------------------------------------------------------------------+--------------------------+<br>
| id | fixed_ips | device_owner |<br>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+<br>
| 0d08328c-e51f-4995-8dc8-b0eb4fae87d7 | {"subnet_id": "fadfa51f-c588-4f1b-8084-4305a8e00486", "ip_address": "10.5.5.1"} | <span style="background-color:rgb(255,255,255);color:rgb(255,0,0)">network:router_interface</span><span style="color:rgb(255,0,0)"> </span>|<span style="background-color:rgb(255,255,255)"></span><br>
| eaad9cce-e9a6-44db-970b-2785403739c1 | {"subnet_id": "a91622d4-f874-48e1-9791-d6acdeff4d2d", "ip_address": "130.217.79.200"} | <span style="color:rgb(255,0,0)">network:router_gateway </span> |<br>
+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+<br><br></div><div>so for deleting those two port , you have to use another command.<br>
<br></div><div>For deleting router_interface , use <br>quantum router-interface-delete<br></div><div><br><br></div><br></div></div></div><div class="gmail_extra"><br clear="all"><div>Thanks & Regards<br> Ranjit Ranjan</div>
<br><br><div class="gmail_quote">On Tue, Sep 24, 2013 at 7:24 AM, Clint Dilks <span dir="ltr"><<a href="mailto:clintd@waikato.ac.nz" target="_blank">clintd@waikato.ac.nz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>Hi,<br><br></div>As a follow up to this I was trying to delete all configured networks and start again, but I seem to be stuck in a loop where I can't delete a router because it has active ports, and yet I can't delete active ports because they belong to a router.<br>
<br>[root@blitzen nova]# quantum router-list<br>+--------------------------------------+-------------+--------------------------------------------------------+<br>| id | name | external_gateway_info |<br>
+--------------------------------------+-------------+--------------------------------------------------------+<br>| e6493ab3-a6b6-476e-a7d6-f1f199810efd | demo-router | {"network_id": "f045b171-7456-4006-9732-420bf5b70017"} |<br>
+--------------------------------------+-------------+--------------------------------------------------------+<br>[root@blitzen nova]# quantum port-list -c id -c fixed_ips -c device_owner<br>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+<br>
| id | fixed_ips | device_owner |<br>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+<br>
| 0d08328c-e51f-4995-8dc8-b0eb4fae87d7 | {"subnet_id": "fadfa51f-c588-4f1b-8084-4305a8e00486", "ip_address": "10.5.5.1"} | network:router_interface |<br>| eaad9cce-e9a6-44db-970b-2785403739c1 | {"subnet_id": "a91622d4-f874-48e1-9791-d6acdeff4d2d", "ip_address": "130.217.79.200"} | network:router_gateway |<br>
+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+<br>[root@blitzen nova]# quantum router-delete e6493ab3-a6b6-476e-a7d6-f1f199810efd<br>
Router e6493ab3-a6b6-476e-a7d6-f1f199810efd still has active ports<br>[root@blitzen nova]# quantum port-delete 0d08328c-e51f-4995-8dc8-b0eb4fae87d7<br>Port 0d08328c-e51f-4995-8dc8-b0eb4fae87d7 has owner network:router_interface and therefore cannot be deleted directly via the port API.<br>
<br></div>So how would I go about deleting these networks?<br><br><div><br><br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Sep 24, 2013 at 11:00 AM, Clint Dilks <span dir="ltr"><<a href="mailto:clintd@waikato.ac.nz" target="_blank">clintd@waikato.ac.nz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div>Hi<br><br></div>I am currently trying to get Grizzly up and running on CentOS 6.4.<br>
</div>I have followed <a href="http://docs.openstack.org/grizzly/basic-install/yum/content/" target="_blank">http://docs.openstack.org/grizzly/basic-install/yum/content/</a> as closely as I can and from both a dashboard and OpenStack command line viewpoint all OpenStack services are up and running and it appears that VM's can be lauched and stopped without any obvious errors being recorded but I can't interact with them using things like ping or ssh.<br>
<br></div><div>Below is information I think may be useful to fix the issue. Thanks for any insight you care to share.<br></div><div><br></div>Currently I have a single machine running all services<br><br></div>Management Network <a href="http://10.10.11.2/24" target="_blank">10.10.11.2/24</a> em2<br>
</div>Bridge linked to em1 <a href="http://130.217.79.2/24" target="_blank">130.217.79.2/24</a><br><br></div><div>We want people to be able to create VM's that they can access via <a href="http://130.217.79.0/24" target="_blank">130.217.79.0/24</a> addresses.<br>
<br></div><div>So as an initial test I follow the example listed in the guide above and created a demo-net'<br><a href="http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_network.html" target="_blank">http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_network.html</a><br>
<pre>Key details below<br></pre><pre>TENANT_NAME="demo"
TENANT_NETWORK_NAME="demo-net"
TENANT_SUBNET_NAME="${TENANT_NETWORK_NAME}-subnet"
TENANT_ROUTER_NAME="demo-router"
FIXED_RANGE="<a href="http://10.5.5.0/24" target="_blank">10.5.5.0/24</a>"
NETWORK_GATEWAY="10.5.5.1"</pre>Then I ran<br><pre>quantum net-create public --router:external=True<br><br>quantum subnet-create --ip_version 4 --gateway 130.217.79.1 public <a href="http://130.217.79.0/24" target="_blank">130.217.79.0/24</a> \<br>
--allocation-pool start=130.217.79.200,end=130.217.79.250 --disable-dhcp --name public-subnet<br></pre><pre>quantum router-gateway-set demo-router public</pre>Using this config instances will launch and if I assign a machine to the public network, the network topology appears to be what we want. But in the guides section about lauching your first vm ( <a href="http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_operate.html" target="_blank">http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_operate.html</a> ) it states that ip netns should show two pieces of information <code>qrouter and qdhcp. I am only seeing qrouter.<br>
<br></code></div><div><code>Should what I have set up work ? Or have I missed something fundamental ?<br><br></code></div><div><code>As it was the default quantum should be configured to use gre + tunnels, I am using 2.6.32-358.118.1.openstack.el6.x86_64 to add the functionality that is missing from the default CentOS kernel.<br>
<br>/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini contains the following, would it be simpler to get what we need using a VLAN configuration ?<br><br>[DATABASE]<br>sql_connection = mysql://<a href="http://quantum:openstack-csl@10.10.11.2/quantum" target="_blank">quantum:openstack-csl@10.10.11.2/quantum</a><br>
reconnect_interval = 2<br><br>[OVS]<br>tenant_network_type = gre<br>enable_tunneling = True<br>tunnel_id_ranges = 1:1000<br>local_ip = 10.10.11.2<br><br>[AGENT]<br>polling_interval = 2<br><br>[SECURITYGROUP]<br>firewall_driver = quantum.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver<br>
<br></code></div><div><br></div><br></div>
</blockquote></div><br></div>
<br>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>