On Fri, Apr 17, 2009 at 3:08 AM, Randy Bias <span dir="ltr"><<a href="mailto:randyb@gogrid.com">randyb@gogrid.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We should start with it simpler, but eventually it will matter and network<br>
objects will be required.<br>
</blockquote><div><br>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).<br><br>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.<br>
<br>Sam<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 4/16/09 11:29 AM, "Richard Davies" <<a href="mailto:richard.davies@elastichosts.com">richard.davies@elastichosts.com</a>><br>
wrote:<br>
<div class="im"><br>
> Network configuration does not - essentially this is just configuration of a<br>
> network interface on a server. As such, it's much simpler to fold the<br>
> configuration into the server object itself, rather than splitting it out<br>
> into a separate "configuration object" and linking to it from the main<br>
> "server object".<br>
<br>
<br>
</div><div class="im">--<br>
Randy Bias, VP Technology Strategy, GoGrid<br>
<a href="mailto:randyb@gogrid.com">randyb@gogrid.com</a>, (415) 939-8507 [mobile]<br>
BLOG: <a href="http://neotactics.com/blog" target="_blank">http://neotactics.com/blog</a>, TWITTER: <a href="http://twitter.com/randybias" target="_blank">twitter.com/randybias</a><br>
<br>
</div><div><div></div><div class="h5">_______________________________________________<br>
occi-wg mailing list<br>
<a href="mailto:occi-wg@ogf.org">occi-wg@ogf.org</a><br>
<a href="http://www.ogf.org/mailman/listinfo/occi-wg" target="_blank">http://www.ogf.org/mailman/listinfo/occi-wg</a><br>
</div></div></blockquote></div><br>