> > It's expected that containers will be created and destroyed at a much > faster rate than typically experienced with just VMs. With that in > mind, seeing Neutron REST API calls in this flow may make people worry > about the increased setup time. It seems to me that logical ports could > optionally be reused to avoid this cost at the creation of every > container. Can you think of a reason that would be problematic? I don't see a reason for it to be problematic. I think it is a valid use case.
> > If that sounds OK, how about this as some additional text here: > > * The Neutron API call here to create a logical port for the container > could add a relatively significant amount of time to container creation. > However, an optimization is possible here. Logical ports could be > created in advance and reused by the container system doing container > orchestration. Additional Neutron API calls would only be needed if the > port needs to be attached to a different logical I will add this as part of v2. Thank you for the text! > >> +* When a container is eventually deleted, the network plugin in that VM >> +will make a call to Neutron to delete that port. Neutron in turn will >> +delete the entry in the Logical_Port table of the OVN Northbound Database. > > If the above text is added, I would change "will make a call" to "may > make a call". > > -- > Russell Bryant _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
