how l2 agent binds the ip to the vm?
I was going through the following link to understand the vm instantiation flow with respect to neutron: https://github.com/cloudandbigdatalab... I have the doubt at step 9. and step 9 says "Step9: A similar RPC notification is also provided to the L2 Agent residing on the same compute node the VM was created. From now onwards this L2 agent will take over."
As per the above statement, L2 agent will get notify from neutron server about new port and L2 agent will bind this port to the newly created instance.
But in another blog I found the following diagram, which says L2 agent continuously scans about newly created instances, and when it found new instance, it will get the details from neutron.
Could some one please clarify, L2 agent involvement in Vm instantiation.
I researched that a few months ago (Mitaka) and believe that the diagram is correct for ML2: The agent on the compute node discovers the plugged VIF, then contacts the neutron server via RPC for info, which it uses to configure the OVS or Linux bridge or whatever other structure it oversees.
Now, do other core plugins or other ML2 mechanism drivers use the same approach? I don't know.