hi Clint,
try these commands:
quantum router-interface-delete demo-router fadfa51f-c588-4f1b-8084-4305a8e00486
quantum router-gateway-clear demo-router
quantum router-delete demo-router
Re, Darragh.
>________________________________
> From: Clint Dilks <cli...@waikato.ac.nz>
>To: "openstack@lists.openstack.org" <openstack@lists.openstack.org>
>Sent: Tuesday, 24 September 2013, 2:54
>Subject: Re: [Openstack] OpenStack Grizzly Quantum Networking
>
>
>
>Hi,
>
>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.
>
>[root@blitzen nova]# quantum router-list
>+--------------------------------------+-------------+--------------------------------------------------------+
>| id | name | external_gateway_info
> |
>+--------------------------------------+-------------+--------------------------------------------------------+
>| e6493ab3-a6b6-476e-a7d6-f1f199810efd | demo-router | {"network_id":
>"f045b171-7456-4006-9732-420bf5b70017"} |
>+--------------------------------------+-------------+--------------------------------------------------------+
>[root@blitzen nova]# quantum port-list -c id -c fixed_ips -c device_owner
>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+
>| id | fixed_ips
> | device_owner |
>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+
>| 0d08328c-e51f-4995-8dc8-b0eb4fae87d7 | {"subnet_id":
>"fadfa51f-c588-4f1b-8084-4305a8e00486", "ip_address": "10.5.5.1"} |
>network:router_interface |
>| eaad9cce-e9a6-44db-970b-2785403739c1 | {"subnet_id":
>"a91622d4-f874-48e1-9791-d6acdeff4d2d", "ip_address": "130.217.79.200"} |
>network:router_gateway |
>+--------------------------------------+---------------------------------------------------------------------------------------+--------------------------+
>[root@blitzen nova]# quantum router-delete e6493ab3-a6b6-476e-a7d6-f1f199810efd
>Router e6493ab3-a6b6-476e-a7d6-f1f199810efd still has active ports
>[root@blitzen nova]# quantum port-delete 0d08328c-e51f-4995-8dc8-b0eb4fae87d7
>Port 0d08328c-e51f-4995-8dc8-b0eb4fae87d7 has owner network:router_interface
>and therefore cannot be deleted directly via the port API.
>
>So how would I go about deleting these networks?
>
>
>
>
>
>
>
>
>
>On Tue, Sep 24, 2013 at 11:00 AM, Clint Dilks <cli...@waikato.ac.nz> wrote:
>
>Hi
>>
>>I am currently trying to get Grizzly up and running on CentOS 6.4.
>>I have followed http://docs.openstack.org/grizzly/basic-install/yum/content/
>>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.
>>
>>
>>Below is information I think may be useful to fix the issue. Thanks for any
>>insight you care to share.
>>
>>
>>Currently I have a single machine running all services
>>
>>Management Network 10.10.11.2/24 em2
>>Bridge linked to em1 130.217.79.2/24
>>
>>
>>We want people to be able to create VM's that they can access via
>>130.217.79.0/24 addresses.
>>
>>
>>So as an initial test I follow the example listed in the guide above and
>>created a demo-net'
>>http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_network.html
>>
>>Key details below
>>
>>TENANT_NAME="demo"
TENANT_NETWORK_NAME="demo-net"
TENANT_SUBNET_NAME="${TENANT_NETWORK_NAME}-subnet"
TENANT_ROUTER_NAME="demo-router"
FIXED_RANGE="10.5.5.0/24"
NETWORK_GATEWAY="10.5.5.1"Then I ran
>>
>>quantum net-create public --router:external=True
>>
>>quantum subnet-create --ip_version 4 --gateway 130.217.79.1 public
>>130.217.79.0/24 \
>>--allocation-pool start=130.217.79.200,end=130.217.79.250 --disable-dhcp
>>--name public-subnet
>>
>>quantum router-gateway-set demo-router publicUsing 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 (
>>http://docs.openstack.org/grizzly/basic-install/yum/content/basic-install_operate.html
>> ) it states that ip netns should show two pieces of information qrouter and
>>qdhcp. I am only seeing qrouter.
>>
>>
>>Should what I have set up work ? Or have I missed something fundamental ?
>>
>>
>>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.
>>
>>/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini contains the
>>following, would it be simpler to get what we need using a VLAN configuration
>>?
>>
>>[DATABASE]
>>sql_connection = mysql://quantum:openstack-csl@10.10.11.2/quantum
>>reconnect_interval = 2
>>
>>[OVS]
>>tenant_network_type = gre
>>enable_tunneling = True
>>tunnel_id_ranges = 1:1000
>>local_ip = 10.10.11.2
>>
>>[AGENT]
>>polling_interval = 2
>>
>>[SECURITYGROUP]
>>firewall_driver =
>>quantum.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver
>>
>>
>>
>>
>>
>
>_______________________________________________
>Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>Post to : openstack@lists.openstack.org
>Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
