Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

As requested...

Controller's ml2_conf.ini:

[DEFAULT]
[ml2]
type_drivers = flat,vlan
mechanism_drivers = linuxbridge
extension_drivers = port_security
[ml2_type_flat]
flat_networks = provider
[ml2_type_geneve]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vlan]
[ml2_type_vxlan]
[securitygroup]
enable_security_group = True
enable_ipset = True

Coincidently I found another strange behaviour in controller's nova-api.log. It could not found the image:

2016-09-16 10:39:31.504 24666 INFO nova.api.openstack.wsgi [req-ed1a4af9-579a-483c-b499-2804410d2232 946e284be6374bf6a28f2b33e2083de7 741278786d82470f8bcfb57dfce5b3da - - -] HTTP exception thrown: Image not found.

I listed the image file like that:

. demo-openrc

and..

openstack image list

Give me ...

ID: 21eab172-c92d-467e-9591-f311d003d86e
Name: cirros

So I created/launch the instance:

openstack server create --flavor m1.tiny --image cirros   --nic net-id=6a3159e1-5f41-4d5f-9da0-befb214657f6 --security-group default   --key-name mykey provider-instance

The --image cirros is important here.

if I use the ID 21eab172-c92d-467e-9591-f311d003d86e instead of name cirros, this HTTP exception thrown: Image not found does not appear in controller's nova-api.log

That's the command launching with image's ID:

openstack server create --flavor m1.tiny --image 21eab172-c92d-467e-9591-f311d003d86e   --nic net-id=6a3159e1-5f41-4d5f-9da0-befb214657f6 --security-group default   --key-name mykey provider-instance

I had also some issue with neutron but to my opinion I should concentrate on nova-api's issues first...

As requested...

Controller's ml2_conf.ini:

[DEFAULT]
[ml2]
type_drivers = flat,vlan
mechanism_drivers = linuxbridge
extension_drivers = port_security
[ml2_type_flat]
flat_networks = provider
[ml2_type_geneve]
[ml2_type_gre]
tunnel_id_ranges = 1:1000
[ml2_type_vlan]
[ml2_type_vxlan]
[securitygroup]
enable_security_group = True
enable_ipset = True

Coincidently I found another strange behaviour in controller's nova-api.log. It could not found the image:

2016-09-16 10:39:31.504 24666 INFO nova.api.openstack.wsgi [req-ed1a4af9-579a-483c-b499-2804410d2232 946e284be6374bf6a28f2b33e2083de7 741278786d82470f8bcfb57dfce5b3da - - -] HTTP exception thrown: Image not found.

I listed the image file like that:

. demo-openrc

and..

openstack image list

Give me ...

ID: 21eab172-c92d-467e-9591-f311d003d86e
Name: cirros

So I created/launch the instance:

openstack server create --flavor m1.tiny --image cirros   --nic net-id=6a3159e1-5f41-4d5f-9da0-befb214657f6 --security-group default   --key-name mykey provider-instance

The --image cirros is important here.

if I use the ID 21eab172-c92d-467e-9591-f311d003d86e instead of name cirros, this HTTP exception thrown: Image not found does not appear in controller's nova-api.log

That's the command launching with image's ID:

openstack server create --flavor m1.tiny --image 21eab172-c92d-467e-9591-f311d003d86e   --nic net-id=6a3159e1-5f41-4d5f-9da0-befb214657f6 --security-group default   --key-name mykey provider-instance

I had also some issue with neutron but to my opinion I should concentrate on nova-api's issues first...

EDIT:

Concentrating on controller's nova-api.log does not make it work.

Now I see a working instance and I now I will provide some information

Controller's ml2_conf.ini need this in the [ml2]-section:

tenant_network_types =

And I needed to edit /etc/init.d/neutron-server

The documentation provides information to start services like this:

 service neutron-server restart

But only this commando ...

 /etc/init.d/neutron-server restart

shows this information:

Plugin not recognized: please edit /etc/init.d/neutron-server to select the correct .ini file to load for your plugin

In line 17 of /etc/init.d/neutron-server I edit like that:

NEUTRON_PLUGIN_CONFIG="/etc/neutron/plugins/ml2/ml2_conf.ini"

But I still get this "Plugin not recognized"

In this startup-script I have found this:

if [ -z "${NEUTRON_PLUGIN_CONFIG}" ] ; then
        echo "Plugin not recognized: please edit /etc/init.d/neutron-server to select the correct .ini file to load for your plugin"
else
        DAEMON_ARGS="${DAEMON_ARGS} --config-file=${NEUTRON_PLUGIN_CONFIG}"
        DESC="${DESC} with ${NEUTRON_PLUGIN_NAME} plugin"
fi

And directly before that part I added:

NEUTRON_PLUGIN_CONFIG="/etc/neutron/plugins/ml2/ml2_conf.ini"

I restarted neutron-server again. Than I could finally launch an instance:

root@controller:/etc/neutron# openstack server list

+--------------------------------------+-------------------+--------+----------------------+

| ID | Name | Status | Networks |

+--------------------------------------+-------------------+--------+----------------------+

| 99a901d6-692e-442d-ad47-c6a0714a2431 | provider-instance | ACTIVE | provider=10.0.10.250 |

+--------------------------------------+-------------------+--------+----------------------+

YEAHHH!!!