Skip to content

Latest commit

 

History

History
46 lines (27 loc) · 1.41 KB

cinderella-notes.md

File metadata and controls

46 lines (27 loc) · 1.41 KB

Update jclouds timeout properties

Provisioning vms via Cinderella currently takes longer than the default timeout period in jclouds. To work around this issue, we have to set a couple of properties in the JcloudsUtil class to increase the timeout period.

Add the following to the JcloudsUtil.buildComputeService() method and make the updated brooklyn-core jar available:

properties.setProperty(Constants.PROPERTY_SO_TIMEOUT, "0");
properties.setProperty(Constants.PROPERTY_TIMEOUTS_PREFIX + "InstanceClient.runInstancesInRegion", "4800000");

Configuration

Add the following to ~/.brooklyn/brooklyn.properties:

# mapr-cinderella

brooklyn.location.named.cinderella-ec2=jclouds:ec2:http://localhost:8080/api/
brooklyn.location.named.cinderella-ec2.identity=YOUR_CINDERELLA_ACCESS_KEY
brooklyn.location.named.cinderella-ec2.credential=YOUR_CINDERELLA_SECRET_KEY
brooklyn.location.named.cinderella-ec2.imageId=Cluster01-Cloudsoft/ami-28f613b28f64497c93c4a78c4f2a4c29
brooklyn.location.named.cinderella-ec2.user=root

brooklyn.jclouds.ec2.identity=YOUR_CINDERELLA_ACCESS_KEY
brooklyn.jclouds.ec2.credential=YOUR_CINDERELLA_SECRET_KEY

Build

From brooklyn-mapr, run mvn clean install

Run

  1. Start Cinderella instance

  2. From cmd line: brooklyn launch -a io.cloudsoft.mapr.MyM3App -l named:cinderella-ec2

    or

    From your IDE: run/debug the main method in io.cloudsoft.mapr.MyM3App