How does MechanismDriver api reflects on the topology?

asked 2014-09-03 13:21:35 -0500

ettorezugliani gravatar image

updated 2014-09-08 15:49:00 -0500

I'm trying to make a mechanism driver, but I wasn't able to find how exactly each api (create network, create port...) would reflect on the actual topology (switches), or how they should be connected and so on. Is there a pattern about how this apis should reflect on the hardwares? How they should be connected to form a topology? Or does OpenStack somehow detects the connections?

edited added to make te question more readable.

These are the main documentations that we are using in order to learn on how to create the driver: http://docs.openstack.org/api/openstack-network/2.0/content/ (http://docs.openstack.org/api/opensta...) https://wiki.openstack.org/wiki/NeutronDevelopment (https://wiki.openstack.org/wiki/Neutr...)

Here is an example of what we don't know: once we receive a "Create Network" API call we don't know how exactly it reflects on ANY switch configuration. Suppose we receive a create_network with the tenant_id = tid and we use the TypeDriver VLAN, should we create a VLAN on the swtich with vid = tid? On a create_port API call should we add a specifc port -manually- to this vlan? Another thing that comes to mind is if there is a default port or do we get the correct port fron Neutron context?

Those kind of questions leads us to this main question: is there any kind of documentation that explains on how the topology may be affected by the API calls?

Thanks in advance!

edit retag flag offensive close merge delete

Comments

Do you have a guide you are following about this, or maybe elaborate about what you are trying to do?

mpetason gravatar imagempetason ( 2014-09-03 13:29:54 -0500 )edit

We divied the answer in a lot of comments due to charecters limitation

These are the main documentations that we are using in order to learn on how to create the driver: http://docs.openstack.org/api/openstack-network/2.0/content/ (http://docs.openstack.org/api/opensta...) https://wiki.openstack.org/wiki/NeutronDevelopment (https://wiki.openstack.org/wiki/Neutr...)

ettorezugliani gravatar imageettorezugliani ( 2014-09-03 14:14:46 -0500 )edit

Ok, here is an example of what we don't know: once we receive a "Create Network" API call we don't know how exactly it reflects on ANY switch configuration.

ettorezugliani gravatar imageettorezugliani ( 2014-09-03 14:15:12 -0500 )edit

Continnuing, suppose we receive a create_network with the tenant_id = tid and we use the TypeDriver VLAN, should we create a VLAN on the swtich with vid = tid?

ettorezugliani gravatar imageettorezugliani ( 2014-09-03 14:15:21 -0500 )edit

On a create_port API call should we add a specifc port -manually- to this vlan? Another thing that comes to mind is if there is a default port or do we get the correct port fron Neutron context?

ettorezugliani gravatar imageettorezugliani ( 2014-09-03 14:15:27 -0500 )edit