> +import org.jclouds.compute.domain.Hardware;
> +import org.jclouds.compute.domain.Image;
> +import org.jclouds.compute.domain.NodeMetadata;
> +import org.jclouds.compute.domain.Volume;
> +import org.jclouds.domain.Location;
> +import org.jclouds.functions.IdentityFunction;
> +import org.jclouds.lifecycle.Closer;
> +import org.jclouds.location.suppliers.ImplicitLocationSupplier;
> +import org.jclouds.location.suppliers.implicit.OnlyLocationOrFirstZone;
> +import static org.jclouds.util.Predicates2.retry;
> +
> +public class ProfitBricksComputeServiceContextModule extends
> +        ComputeServiceAdapterContextModule<ServerInDataCenter, Hardware, 
> Provisionable, DataCenter> {
> +
> +    @Override
> +    protected void configure() {

Now that jclouds supports arbitrary CPU, RAM and Storage, configure the 
template builder here too! See [blog 
post](https://jclouds.apache.org/blog/2016/08/22/arbitrary-cpu-ram/) for 
details.

-- 
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/292/files/1533bf29a80f2c87834f501abd91ea399debd688#r78122825

Reply via email to