Ask Your Question

mlathe's profile - activity

2015-07-01 23:05:37 -0500 received badge  Popular Question (source)
2015-07-01 23:05:37 -0500 received badge  Notable Question (source)
2015-06-26 16:56:21 -0500 asked a question VM Console access from Dom0 CLI to test Neutron ML2 Driver

I'd like to setup some test scripts to verify that a Neutron ML2 Driver works through a series of test cases.

While the actual setup of a test case is quite easy (ie via the nova and neutron CLI commands), actually testing that a VM can connect to another VM has proved very difficult.

So far my only success was either by manually plugging into my Neutron segment (ie vlan) from my controller Dom0, or by setting up an external network and giving the VM a floating IP address. Neither of these is very good because they both depend on my neutron config to work 100% before I can assert anything.

One idea i had was to try to "VNC into the VM" from the CLI (ie not via the browser like the "nova get-vnc-console" command) kind of like you use a console port on a physical system. Then possibly using expect or something (holding my breath)

Another idea was that perhaps I need to work with the specific hypervisor I'm using and use a back door they have, but isn't advertised through the more generic OpenStack?


2015-05-20 01:21:26 -0500 received badge  Nice Question (source)
2015-01-17 05:31:49 -0500 received badge  Famous Question (source)
2014-12-29 05:07:37 -0500 received badge  Notable Question (source)
2014-12-27 04:57:28 -0500 received badge  Popular Question (source)
2014-12-24 15:14:41 -0500 asked a question Etymology of OpenStack Components

Hi, I've been trying to figure out exactly what the origin of the component naming is.

I think that the Release Naming scheme makes sense, and is somewhat well understood.

Anyone know the history?

Here are my guesses based on the list from

  1. Compute (Nova): because it came originally from NASA Ames?
  2. Object Storage (Swift): ???
  3. Image Service (Glance): ???
  4. Identity (Keystone): because identity is the "keystone" to security?
  5. Dashboard (Horizon): ???
  6. Networking (Neutron): Was quantum but change because of a trademark issue. But why neutron?
  7. Block Storage (Cinder): because of "cinder block"
  8. Telemetry (Ceilometer): ceilometers measure things
  9. Orchestration (Heat): ???
  10. Database Service (Trove): ???
  11. Data processing (Sahara): ???
  12. Bare metal (Ironic): A "ironic" play on the word "iron"?
  13. Queue service (Zaqar): ???
  14. Key management (Barbican): Barbican is a fortified gateway to a castle
  15. DNS Services (Designate): ???
  16. Common Libraries (Oslo): ???
2014-12-22 23:28:58 -0500 received badge  Famous Question (source)
2014-12-22 23:28:58 -0500 received badge  Notable Question (source)
2014-12-22 23:28:58 -0500 received badge  Popular Question (source)
2014-12-12 17:53:57 -0500 received badge  Student (source)
2014-12-11 22:02:31 -0500 asked a question Add new ML2 Driver without needing to release all of neutron

I'm trying to figure out how to add an new ML2 Driver as an entry point for the neutron-service, without needing to release all of neutron.

There seem to be a few threads, like this:

  • (
  • (
  • (

These all seem to imply that you need to change the setup.cfg file which will update the entry_point.txt file in: /usr/lib/python2.6/site-packages/neutron-2014.1-py2.6.egg-info/entry_points.txt

My question is, how do you do this without changing something in neutron? Ie if I do this, then don't I need to release neutron too? I suppose i can force my settings into the entry_point.txt file during my install (ie use the openstack-config command to write my properties into that file), but that seems ugly.

Are there any known examples of ML2 Plugins that do this without being known in the main neutron codebase?