-
https://gist.github.com/jacobwagner/0d9a3ede8a3a3d5d0c1b
To recreate: install ha with quantum on precise, check for any process with rpcdaemon, also check the log, it will look like the above gist
T…
-
I think that it would be pertinant to refactor quantum-neutron into its own cookbook rather than keep it mixed up with nova-network. This would simplify the recipes dramatically and prepare for a futu…
-
It seems that the 'nova' network is only used in the following places:
default["keystone"]["services"]["admin-api"]["network"] = "nova"
default["nova"]["services"]["xvpvnc-proxy"]["network"] = "nova"…
-
Hi all,
I followed this how to: https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_MultiNode/OpenStack_Grizzly_Install_Guide.rst exaclty as it says.
However I can't ping the vm,…
-
Sorry I don't really now how to use github yet but I've spent alot of time getting both gre and vlan tag support working at the same time. I think it would be worth adding to your grizzly howtos as I'…
-
In quantum-common the network used for the ovs_local_ip is hard coded to the osops_network "nova". This should be parameterised like all other references to the osops_networks.
The offending line is:…
-
Floating IP networks are required by quantum in order to offer floating IPs. That network should be hidden though to en users when launching VMs. It should only be available when assigning floating IP…
-
When building a controller, single-network-node, single-compute cluster, you cannot add quantum networks without adding the following to /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini on the …
-
5e695499b97 assumes that the API result from OpenStack will have keys named "public" and "private" - which is not a valid assumption. I believe the keys are created, based on the name of the network, …
-
From Takayuki:
In summary, to create a single VM instance, quantum-server handled 16
requests taking 7.66 secs, meanwhile api handle 38 requests sent from
quantum-server taking 6.82 secs. That is, qu…