We should start with it simpler, but eventually it will matter and network
objects will be required.
In the most basic case we still need enumeration (short of reverse engineering the information by retrieving all objects and doing something like a 'select distinct' over them).
I'm thinking the network resources (and there shouldn't be many of them, or at least not many shared between all users) should start with little more than a name/description for UI purposes. Public cloud installations may just have a single shared "Internet" network resource and that might be something we want to allocate a well known UUID and/or alias to.
Sam
On 4/16/09 11:29 AM, "Richard Davies" <richard.davies@elastichosts.com>
wrote:
> Network configuration does not - essentially this is just configuration of a
> network interface on a server. As such, it's much simpler to fold the
> configuration into the server object itself, rather than splitting it out
> into a separate "configuration object" and linking to it from the main
> "server object".