> + System.out.println(str);
> + }
> + return Iterables.filter(listNodes(), new Predicate<VMDeployment>() {
> + @Override
> + public boolean apply(final VMDeployment input) {
> + return Iterables.contains(ids, input.deployment.name());
> + }
> + });
> + }
> +
> + private String getGroupId() {
> + String group = System.getProperty("test.azurecompute-arm.groupname");
> + if (group == null)
> + group = "jCloudsGroup";
> + return group;
> + }
This method must be removed.
How is this supposed to work? Will users have to configure a resource group
when creating the context and that one is going to be the only one considered
by the compute service? Or should instead the compute service be available to
list nodes in all resource groups?
Would it make sense to use the jclouds "group" to create a resource group?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs/pull/267/files/bae5d6dfcdb26e31057db4551c5996836666a31b#r63966048
