On Wed, Jul 14, 2010 at 01:17:26PM +0200, Andrew Beekhof wrote:
Not sure about this.
You don't think it will create confusion if half of the network
related API calls are in one place and the other half in another?
What's the motivation? Security domains perhaps?
I'm looking at it from a parent/child relationship. To create a new
logical network interface, such as a bridge, what is the most intuitive
way to go about the process? To me it seems that you would create it on
the host, and then configure it once the device "exists". So, from that
perspective, only the create API for network devices will exist at the
host level.
And, at that, I think we drop the list_network_devices API. With QMF I
think it's fairly trivial to ask the broker "give me all NetworkDevice
agents for this Host agent". So the host doesn't need to give an API for
retrieving them explicitly.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/