> + .imageNameMatches( "<ideally-unique-snapshot-name>" ) > + .options( new TemplateOptions() > + .overrideLoginUser( "root" ) // unless you > changed the user > + .overrideLoginPassword( "<changed-password>" )) > + // more options, as you need > + .build(); > + > +compute.createNodesInGroup( "cluster1", 1, template ); > +``` > +> If no `locationId` is specified in the template, jclouds will look for a > `DataCenter` that is of same scope as the `Image`. > + > + > +## Limitations > + > +1. There's no direct way of specifying arbitrary number of cores, RAM size, > and storage size via the compute interface, at least until after > [JCLOUDS-482](https://issues.apache.org/jira/browse/JCLOUDS-482) is resolved. > The adapter uses a predefined list hardware profiles instead. > +2. All provisioned nodes are connected at LAN 1 of a datacenter.
TBD in future PRs (not now). The template options allow to specify a set of "network ids". Perhaps that is the place to allow users to specify to which LANs the servers should be attached. The adapter should take into account that option. --- Reply to this email directly or view it on GitHub: https://github.com/jclouds/jclouds-labs/pull/145/files#r33444666
