A couple more things to consider that have come to my mind after reading the ComputeService implementation again:
* The `templateOptions.inboundPorts` should be considered to open those ports in the target virtual machine. Is this something that can be done per VM, or the "external" ports must be unique per Cloud Service/ whatever? (I'm still not familiar enough with some of the Azure concepts). * The template options also provides a way so users can specify a set of network IDs, and jclouds is supposed to assign to the node one IP address in each of those networks. Is this something that makes sense in Azure too? * Does azure support setting tags and metadata (key/value pairs) in each VM? If so, the compute service adapter should also take into account the tags and userMetadata template options. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/132#issuecomment-74574993
