jclouds-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrea Turli <notificati...@github.com>
Subject Re: [jclouds/jclouds-labs] JCLOUDS-1278: Allow to configure virtual machine NICs in Azure ARM (#386)
Date Wed, 26 Apr 2017 20:54:00 GMT
thanks @nacx I really like the kind of flexibility jclouds azurecompute-arm can gain with that!

couple of minor inital comments: 
1. don't we need to deprecate `subnetId` and `virtualNetworkName` before removing them, maybe?
2. with the second option `options.networks(subnetId2, subnetId2, ...);` how the nodes will
get a public IP?


as a broader discussion, I really think we are pushing jclouds compute to the limit: it's
original ability to manage nodes nowadays requires a lot of networking resource to be created
"around" the node before the provisioning can happen. I wonder if it's time for a `jclouds
network` abstraction where jclouds can manage concepts like vpc, subnets, security groups
so the `jclouds compute` abstraction can then consume those resources created in a portable
way. Of course this is well beyond the scope of this PR, but I'd like to know your thoughts
on that.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
View raw message