search

ptoma98 / skytap-cloud-plugin

Repository for Release 2 of the Skytap Plugin
0 stars 0 forks source link

question re: create published service #4

Open ptoma98 opened 10 years ago

ptoma98 commented 10 years ago

In the spec I can see the input parameters for create published service include 'network name'. The API request to create the service requires an interface id.. for example:

https://cloud.skytap.com/configurations/1453536/vms/2554726/interfaces/nic-1002768-2433448-0

I can get the interface id ("nic-1002768-2433448-0" in this case) using the network name .. my question is, can a network have more than 1 interface? In that case the user would be better of just specifying the interface id.

If not I will retrieve it using the network name.

ptoma98 commented 10 years ago

Never mind.. I already have a method that does this easily. I am wondering though if it is possible for a network to have more than one interface id..

tjmilligan commented 10 years ago

I'll check and see

Tom Milligan

On Jan 25, 2014, at 3:22 PM, "Patrick Toma" notifications@github.com<mailto:notifications@github.com> wrote:

Never mind.. I already have a method that does this easily. I am wondering though if it is possible for a network to have more than one interface id..

Reply to this email directly or view it on GitHubhttps://github.com/ptoma98/skytap-cloud-plugin/issues/4#issuecomment-33301012.

tjmilligan commented 10 years ago

It is possible for a VM to have more than one network interface with both assigned to the same network.

Rather than making this extraordinarily complex at this point, we can just document what will happen if this is the case and the "create published service" action is attempted. E.g "The first interface defined in the VM definition returned is used" or "If the VM has more than one network interface, the create published service action will return an error."

I don't see how we can do much more than this since the interface ID is unique to each configuration and there is no way to know the ID of a config created from a template as part of a build. Our approach, then, is the only possible way to implement this and requires that a published service be created for a network with one and only one interface. I will make sure this is noted in the documentation.