Craig McClanahan
|
Posted: September 16, 2009 13:57 by Craig McClanahan
|
|
In the initial incarnation of the Sun Cloud API, it was assumed that a typical scenario for setting up a new VM would be the following sequence of operations: * Create the VM * Attach each desired PublicAddress or VNet to the VM * Deploy the fully configured VM Now that we have removed the "deploy" step, it would be useful to allow the client to specify all the desired network connections when the VM is initially created, rather than having to add them later. Also, for some service implementations, it might not even feasible to have a created VM that has no network connections, because it would not be accessible. The proposal to make this possible is as follows: * On the Create VM operation, allow the "interfaces" array to optionally be included. * If one or more Interface objects are included, only the "vnet", "public_address", and "nic" fields would be recognized. Either the "vnet" or "public_address" would be required. If the "nic" value was not included, the service implementation would assign a default name to the virtual nic that was created. * The corresponding network connections would be established on the initial creation of the new VM. * The "attach" and "detach" operations would remain available for modifying the network configuration after initial creation, but they would typically require a reboot to become effective (in the interim, the "updated" flag would be set to indicate pending changes are present). As a side note, we should also allow the "attach" command to optionally specify a "nic" option to set a non-default name for the newly created nic. Thoughts? Craig |
Proposal: Specifying Network Connections on VM Creation
2 posts
Replies: 1 - Last Post: September 18, 2009 19:13
by: Tim Bray
by: Tim Bray
showing 1 - 2 of 2
Tim Bray
|
Posted: September 18, 2009 19:13 by Tim Bray
|
|
This seems like a no-brainer, since it's hard to imagine wanting to create a VM that isn't hooked up to anything, and furthermore I suppose it would enable some optimizations on the server side. I'm nervous about the "nic" field, since there is probably going to be little standardization from cloud-to-cloud in this area, and I'm not sure it's reasonable to require implementations to allow clients to specify this. |
Replies: 1 - Last Post: September 18, 2009 19:13
by: Tim Bray
by: Tim Bray
