On 04/21/2013 11:13 AM, Mike Kolesnik wrote:
Each network can be provided either by oVirt or by the external provider.
>
>did we look at our code to understand what it would mean to refactor the
>ovirt network code as an external provider as well (doesn't have to be
>out of process, just generalize/modularize our code and not have private
>cases) - there is work for doing something similar for the pluggable
>scheduler, first refactoring the existing scheduling code out as well.
Currently there hasn't been much work in that direction, however we need to
consider the fact that Quantum (and many other external providers) will be
providing us with VM network capability only, so perhaps only this part
can be done as a "provider".
However, we should take note that current oVirt implementation for VM
networks is more flexible than that of Quantum, so having it as "provider"
could limit that flexibility.
worth thinking about this a bit - mapping the gaps will probably lead to
a better picture of how this should look like, expecting external
providers to actually have more features than ovirt currently has.
_______________________________________________
Arch mailing list
[email protected]
http://lists.ovirt.org/mailman/listinfo/arch
