Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Thanks, but I still don't undestand the questions that I asked. I have already read those posts, and many others. My question is simply to understand the flow of who against whom and where. So I will phrase it as questions:

Let's say I set up a simple openstack with 1 controller and 2 computes. I understand that the neutron server is running on the controller. Now, say I add a simple tenant network, with some subnet. Some program notifies Neutron server that I would like to create such network, and Neutron talks to ML2 plugin. 1. Does ML2 talk directly to the mechanism driver? 2. Does that mean that the mechanism driver code has to be present only on the controller node? 3. Where is the neutron agent code running? on each compute? on the controller? on both? 4. Who calls the neutron agent? 5. To whom does the neutron agent call?

I essentially am just trying to understand the exact flow of things, in creation of networks, and when launching VMs.

Thanks, but I still don't undestand the answers to the questions that I asked. I have already read those posts, and many others. My question is simply to understand the flow of who against whom and where. So I will phrase it as questions:

Let's say I set up a simple openstack with 1 controller and 2 computes. I understand that the neutron server is running on the controller. Now, say I add a simple tenant network, with some subnet. Some program notifies Neutron server that I would like to create such network, and Neutron talks to ML2 plugin. 1. Does ML2 talk directly to the mechanism driver? 2. Does that mean that the mechanism driver code has to be present only on the controller node? 3. Where is the neutron agent code running? on each compute? on the controller? on both? 4. Who calls the neutron agent? 5. To whom does the neutron agent call?

I essentially am just trying to understand the exact flow of things, in creation of networks, and when launching VMs.

Thanks, but I still don't undestand the answers to the questions that I asked. I have already read those posts, and many others. My question is simply to understand the flow of who against whom and where. So I will phrase it as questions:

Let's say I set up a simple openstack with 1 controller network node and 2 computes. I understand that the neutron server service (API) is running on the controller. network node. Now, say I add a simple tenant network, with some subnet. Some program notifies Neutron server Neutron service (API) is notified that I would like to create such network, and Neutron talks to ML2 plugin. 1. Does ML2 talk directly to the mechanism driver? 2. Does that mean that the mechanism driver code has to be present is only on the controller relevant for the network node? 3. Where is Who calls the neutron agent code running? on each compute? on the controller? on both? on the network node and on the compute node? Neutron service? Neutron ML2 plugin? Neutron ML2 mechanism driver? 4. Who calls the neutron agent? Is the whole purpose of the agent to set rules in the vSwitch and set up ports locally? 5. To whom does Does the neutron agent call?ever initiate something, or only does as it is told? 6. Does it always act locally (i.e. changes things only on the server it's running on)?

I essentially am just trying to understand the exact flow of things, in creation of networks, and when launching VMs.