jxstanford
|
Posted: November 03, 2009 00:25 by jxstanford
|
|
I'm looking at this statement about PublicAddress: Most of the fields of a Public Address resource are automatically set in the course of its use; the only field specified at creation time is its logical name. And wondering if that is a qlayerism, or if there are some other operations in the spec that take care of assigning values. I'm guessing that this is qlayer specific, and wondering if the create PublicAddress call should have a more general approach to better accommodate other types of resource managers. One possibility would be to add a field for managed/unmanaged or to use a tag or param to define whether the back-end system manages the actual address details. I have a similar concern with VNets. They're great for qlayer which apparently manages a VNet type of resource, but what about the rest of the managers out there. Basically, I tend to think there should be a general facility for IPAddress that supports the PublicAddress and VNet resources. The IPAddress would have the following fields: address netmask gateway status {assigned, reserved, unassigned, ?} -- this supports allocations for Vnet attach, not so important for PublicAddress It would make sense to treat this similar to Interface (no uri and no direct operations). Thoughts? |
IPAddress resource?
1 post
Replies: 0 - Last Post: November 03, 2009 00:25
by: jxstanford
by: jxstanford
showing 1 - 1 of 1
Replies: 0 - Last Post: November 03, 2009 00:25
by: jxstanford
by: jxstanford
