Re: [Netstack] Quantum agents

Thanks. On 05/01/2012 03:52 AM, Dan Wendlandt wrote: Hi Gary, On Sat, Apr 28, 2012 at 10:39 PM, Gary Kotton > wrote: In general, there is also a thought that the VIF driver should be really thin, and to the extent possible Quantum plugin-specific detail

Re: [Netstack] Quantum and oVirt

On 05/01/2012 12:12 AM, Kyle Mestery (kmestery) wrote: This is great Gary, thanks for sharing! I'm going through this in detail now. Is the goal to try and create blueprints to address some of these issues in Quantum, with similar work on the oVirt side? Originally we wanted to understand the g

Re: [Netstack] Quantum and oVirt

Agreed, this is very cool stuff! Dan On Mon, Apr 30, 2012 at 2:12 PM, Kyle Mestery (kmestery) wrote: > This is great Gary, thanks for sharing! I'm going through this in detail > now. Is the goal to try and create blueprints to address some of these > issues in Quantum, with similar work on the

Re: [Netstack] Quantum agents

Hi Gary, On Sat, Apr 28, 2012 at 10:39 PM, Gary Kotton wrote: > > In general, there is also a thought that the VIF driver should be really > thin, and to the extent possible Quantum plugin-specific details should be > pulled out it. > > I definitely agree with Sumit's comment. > > > I un

Re: [Netstack] Common Database Interface

Hi Gary, Great that you're working on this. Looks like some of this is stuff you're already tackling in in the DB-HA branch on gerrit, which is great. A couple other things to note: - we already have a basic shared database python API and shared sqlalchemy models in the quantum/db directory. Th

Re: [Netstack] Common Database Interface

Hi Gary, The blueprint looks like a good start for standardizing how plugins and agents communicate with a database. It may also be helpful to think about how and why the database is used as a means for both storing and propagating state. An abstraction resulting from such consideration woul

Re: [Netstack] Quantum and oVirt

This is great Gary, thanks for sharing! I'm going through this in detail now. Is the goal to try and create blueprints to address some of these issues in Quantum, with similar work on the oVirt side? Or until the core gaps and limitations are fixed, oVirt integration will only be a POC? Thanks,