[Openstack] [Neutron] Unable to create Floating IPs.

Eugene Nikanorov enikanorov at mirantis.com
Thu Nov 14 07:11:18 UTC 2013 

When I use devstack with ml2 plugin configured for neutron, it produces
ml2_conf.ini in /etc/neutron/plugins/ml2/ml2_conf.ini

Eugene.


On Thu, Nov 14, 2013 at 11:01 AM, Trinath Somanchi <
trinath.somanchi at freescale.com> wrote:

>  Hi-
>
>
>
> Where to find the configuration sections required for ML2  for various
> network types?
>
>
>
>
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Eugene Nikanorov [mailto:enikanorov at mirantis.com]
> *Sent:* Thursday, November 14, 2013 12:23 PM
>
> *To:* Somanchi Trinath-B39208
> *Cc:* Oleg Bondarev; openstack at lists.openstack.org
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Hi,
>
>
>
> I guess you're missing additional parameters (copying from ml2_conf.ini):
>
>
>
> [ml2_type_vlan]
>
> # (ListOpt) List of <physical_network>[:<vlan_min>:<vlan_max>] tuples
>
> # specifying physical_network names usable for VLAN provider and
>
> # tenant networks, as well as ranges of VLAN tags on each
>
> # physical_network available for allocation as tenant networks.
>
> #
>
> # network_vlan_ranges =
>
> # Example: network_vlan_ranges = physnet1:1000:2999,physnet2
>
>
>
> Thanks,
>
> Eugene.
>
>
>
>
>
> On Wed, Nov 13, 2013 at 2:31 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi –
>
>
>
> Please find the neutron.conf  @ http://paste.openstack.org/show/51936/
>
>
>
> [ml2]
>
> type_drivers=vlan
>
> mechanism_drivers=openvswitch
>
> tenant_network_types = vlan
>
>
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Eugene Nikanorov [mailto:enikanorov at mirantis.com]
> *Sent:* Wednesday, November 13, 2013 3:55 PM
>
>
> *To:* Somanchi Trinath-B39208
> *Cc:* Oleg Bondarev; openstack at lists.openstack.org
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Ok, what is in [ml2] section then?
>
>
>
> On Wed, Nov 13, 2013 at 2:14 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi-
>
>
>
> I have nothing in my Openstack Neutron installation called, ml2_conf.ini
>
>
>
> I have a section [ml2] in neutron.conf itself.
>
>
>
> Do I need to have any new files/changes for debugging this issue.
>
>
>
> Kindly help me.
>
>
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Eugene Nikanorov [mailto:enikanorov at mirantis.com]
> *Sent:* Wednesday, November 13, 2013 2:46 PM
> *To:* Somanchi Trinath-B39208
> *Cc:* Oleg Bondarev; openstack at lists.openstack.org
>
>
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Could you please post your ml2_conf.ini?
>
> Eugene.
>
>
>
> On Wed, Nov 13, 2013 at 12:44 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi Oleg-
>
>
>
> When I configure ML2 and L3 Plug-ins in Openstack Havana – Neutron, I was
> unable to create network.
>
>
>
> I get the following errors in Neutron Server logs.
>
>
>
> 2013-11-13 14:17:24.724 5094 DEBUG routes.middleware [-] No route matched
> for POST /networks.json __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:97
>
> 2013-11-13 14:17:24.727 5094 DEBUG routes.middleware [-] Matched POST
> /networks.json __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:100
>
> 2013-11-13 14:17:24.728 5094 DEBUG routes.middleware [-] Route path:
> '/networks{.format}', defaults: {'action': u'create', 'controller': <wsgify
> at 68832400 wrapping <function resource at 0x4212488>>} __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:102
>
> 2013-11-13 14:17:24.729 5094 DEBUG routes.middleware [-] Match dict:
> {'action': u'create', 'controller': <wsgify at 68832400 wrapping <function
> resource at 0x4212488>>, 'format': u'json'} __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:103
>
> 2013-11-13 14:17:24.732 5094 DEBUG neutron.openstack.common.rpc.amqp [-]
> Sending network.create.start on notifications.info notify
> /usr/lib/python2.7/dist-packages/neutron/openstack/common/rpc/amqp.py:598
>
> 2013-11-13 14:17:24.734 5094 DEBUG neutron.openstack.common.rpc.amqp [-]
> UNIQUE_ID is 47317528cabb4553a2f4c2aa1240cfa1. _add_unique_id
> /usr/lib/python2.7/dist-packages/neutron/openstack/common/rpc/amqp.py:339
>
> 2013-11-13 14:17:24.745 5094 DEBUG amqp [-] Closed channel #1 _do_close
> /usr/lib/python2.7/dist-packages/amqp/channel.py:88
>
> 2013-11-13 14:17:24.747 5094 DEBUG amqp [-] using channel_id: 1 __init__
> /usr/lib/python2.7/dist-packages/amqp/channel.py:70
>
> 2013-11-13 14:17:24.752 5094 DEBUG amqp [-] Channel open _open_ok
> /usr/lib/python2.7/dist-packages/amqp/channel.py:420
>
> 2013-11-13 14:17:24.855 5094 ERROR neutron.api.v2.resource [-] create
> failed
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource Traceback (most
> recent call last):
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource   File
> "/usr/lib/python2.7/dist-packages/neutron/api/v2/resource.py", line 84, in
> resource
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource     result =
> method(request=request, **args)
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource   File
> "/usr/lib/python2.7/dist-packages/neutron/api/v2/base.py", line 405, in
> create
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource     obj =
> obj_creator(request.context, **kwargs)
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource   File
> "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/plugin.py", line 308,
> in create_network
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource     segment =
> self.type_manager.allocate_tenant_segment(session)
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource   File
> "/usr/lib/python2.7/dist-packages/neutron/plugins/ml2/managers.py", line
> 100, in allocate_tenant_segment
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource     raise
> exc.NoNetworkAvailable()
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource
> NoNetworkAvailable: Unable to create the network. No tenant network is
> available for allocation.
>
> 2013-11-13 14:17:24.855 5094 TRACE neutron.api.v2.resource
>
>
>
>
>
> Is there any thing I missed while creating a Network in Neutron.
>
>
>
> Kindly help me resolve the issue
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Oleg Bondarev [mailto:obondarev at mirantis.com]
> *Sent:* Tuesday, November 12, 2013 2:54 PM
> *To:* Somanchi Trinath-B39208; openstack at lists.openstack.org
>
>
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Trinath,
>
> The only place I can point to is:
>
> https://wiki.openstack.org/wiki/Neutron/ML2
>
>
>
> But still I can be missing something. Probably it is worth raising a new
> email thread regarding configuring ml2 plugin in neutron.
>
>
>
> Thanks,
>
> Oleg
>
>
>
> On Tue, Nov 12, 2013 at 1:13 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Okay..
>
>
>
> Can you help me on how to use ML2 Plugin instead of OVS plugin..
>
>
>
> I just configure ML2 as below in the neutron.conf and restarted the
> neutron-server.
>
>
>
> [ml2]
>
> type_drivers=vlan
>
> mechanism_drivers=openvswitch
>
> tenant_network_types = vlan
>
>
>
> Is there anything I’m missing is using ML2 plugin ?
>
>
>
> Kindly guide me in this regard.
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Oleg Bondarev [mailto:obondarev at mirantis.com]
> *Sent:* Tuesday, November 12, 2013 2:41 PM
>
>
> *To:* Somanchi Trinath-B39208
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Trinath,
>
> from this line:
>
>  neutron   8388     1  0 14:17 ?        00:00:02 /usr/bin/python
> /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file
> /var/log/neutron/server.log --config-file
> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
>
> it looks like you're not using ml2 plugin, but OpenVSwitch plugin instead
> which does not require L3 service plugin to be additionally configured.
> That may cause failing of neutron server.
>
>
>
> Thanks,
>
> Oleg
>
>
>
> On Tue, Nov 12, 2013 at 12:46 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi Oleg-
>
>
>
> When I do these changes to neutron in my setup, I have Neutron Client cmds
> not working.
>
>
>
> root at havana:~# ps -ef | grep neutron
>
> root      8284 14518  0 14:14 pts/17   00:00:00 tail -f
> /var/log/neutron/server.log
>
> neutron   8388     1  0 14:17 ?        00:00:02 /usr/bin/python
> /usr/bin/neutron-server --config-file /etc/neutron/neutron.conf --log-file
> /var/log/neutron/server.log --config-file
> /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
>
> neutron   8442     1  0 14:17 ?        00:00:00 /usr/bin/python
> /usr/bin/neutron-dhcp-agent --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/dhcp_agent.ini
> --log-file=/var/log/neutron/dhcp-agent.log
>
> neutron   8464     1  0 14:18 ?        00:00:00 /usr/bin/python
> /usr/bin/neutron-metadata-agent --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/metadata_agent.ini
> --log-file=/var/log/neutron/metadata-agent.log
>
> neutron   8483     1  0 14:18 ?        00:00:01 /usr/bin/python
> /usr/bin/neutron-openvswitch-agent --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini
> --log-file=/var/log/neutron/openvswitch-agent.log
>
> root      8495 14610  0 14:18 pts/18   00:00:00 /usr/bin/python
> /usr/bin/neutron ext-list
>
> neutron   8609  8388  0 14:19 ?        00:00:00 openssl cms -verify
> -certfile /var/lib/neutron/keystone-signing/signing_cert.pem -CAfile
> /var/lib/neutron/keystone-signing/cacert.pem -inform PEM -nosmimecap
> -nodetach -nocerts -noattr
>
> neutron   8633     1  0 14:19 ?        00:00:00 /usr/bin/python
> /usr/bin/neutron-l3-agent --config-file=/etc/neutron/neutron.conf
> --config-file=/etc/neutron/l3_agent.ini
> --log-file=/var/log/neutron/l3-agent.log
>
> root      8691  8483  0 14:21 ?        00:00:00 sudo
> /usr/bin/neutron-rootwrap /etc/neutron/rootwrap.conf ovs-vsctl --timeout=2
> list-ports br-int
>
> root      8693 14419  0 14:21 pts/11   00:00:00 grep --color=auto neutron
>
>
>
> With the neutronCLI, my commands fail with error “Max attempts reached” .
>
>
>
> Kindly help me troubleshoot the same..
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Oleg Bondarev [mailto:obondarev at mirantis.com]
>
> *Sent:* Tuesday, November 12, 2013 2:06 PM
> *To:* Somanchi Trinath-B39208
>
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Hi Trinath,
>
> If you have ML2 plugin configured as a core plugin than you should also
> configure L3 service plugin.
>
> Please try to add following line to your neutron.conf and restart
> neutron-server:
>
>  service_plugins =
> neutron.services.l3_router.l3_router_plugin.L3RouterPlugin
>
>
>
> Also please ensure l3 agent is running in your setup.
>
>
>
> Thanks,
>
> Oleg
>
>
>
> On Tue, Nov 12, 2013 at 12:05 PM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi Eugene-
>
>
>
> Thanks a lot for the reply.
>
>
>
> It’s a typo in my email. But then, I have the issue while adding floating
> IPs.
>
>
>
> When I issue the below command,
>
>
>
> root at havana:~# neutron floatingip-create net1
>
> 404 Not Found
>
>
>
> The resource could not be found.
>
>
>
> I get this error in neutron server logs
>
>
>
> 2013-11-12 13:40:30.982 14987 DEBUG routes.middleware [-] No route matched
> for POST /floatingips.json __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:97
>
> 2013-11-12 13:40:30.983 14987 DEBUG routes.middleware [-] No route matched
> for POST /floatingips.json __call__
> /usr/lib/python2.7/dist-packages/routes/middleware.py:97
>
>
>
> Is there any thing I missed or worngly configured.
>
>
>
> Kindly please help me resolve the same..
>
>
>
> Thanking you
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
> *From:* Eugene Nikanorov [mailto:enikanorov at mirantis.com]
> *Sent:* Tuesday, November 12, 2013 1:31 PM
> *To:* Somanchi Trinath-B39208
> *Cc:* openstack at lists.openstack.org
> *Subject:* Re: [Openstack] [Neutron] Unable to create Floating IPs.
>
>
>
> Hi,
>
>
>
> I believe you have typo in the command, which is floatingip-create,
> not floatingips-create.
>
>
>
> Thanks,
>
> Eugene.
>
>
>
> On Tue, Nov 12, 2013 at 8:31 AM, Trinath Somanchi <
> trinath.somanchi at freescale.com> wrote:
>
> Hi Stackers-
>
>
>
> With Installation of Openstack Havana in Ubuntu 12.04, I’m unable to
> create Floating IPs which also effects the Instance Creation.
>
>
>
> From the CLI, when I execute the command, $> neutron floatingips-create
> fp1  , I get 404 not found error.
>
>
>
> In the Neutron Server Side, I get the error    “ No route for method
> /floatingips.json “.
>
>
>
> Is this a bug ? with neutron.
>
>
>
> Kindly help me resolve the issue.
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.somanchi at freescale.com | extn: 4048
>
>
>
>
> _______________________________________________
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to     : openstack at 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 at 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 at lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20131114/5623d5cf/attachment.html>

More information about the Openstack mailing list