CloudTran Guide - Rackspace Deployment

/deployments. The name of this sub-directory will be the name of the Deployment Option. For example if the Deployment Option is called 'Rackspace' in the MultiTenancy example.

Then the directory structure for the deployment will be as follows.

As you can see there are a number of files, including properties files, build files and shell scripts. All of these files are generated, based on the deployment defined in model. For instance the RackspaceTest_BusinessOrganisation.properties is the derived config properties for the Business Organisation Processing Unit. The shell scripts start and deploy the application on the Rackspace servers. The build.xml is an ant file that controls the deployment process. This makes use of Whirr and JClouds as well as classes in CloudTran.jar to perform the deployment.

For the Rackspace deployment to work some additional properties are needed. These currently are the 'whirr.identity' and 'whirr.credential'. They should be placed in the 'Rackspace.properties'. The 'whirr.identity' is your Rackspace login name and the 'whirr.credential' is your Rackspace API key. The Rackspace API key can be found by logging into your Rackspace account and This file has two parts - the first half is regenerated and the values are determined from the deployment option values. The second part of the file is not regenerated (all the values here are maintained) and this is where the 'whirr.identity' and 'whirr.credential' value should go. Any additional propertiest hat you wish to maintain for your deployment should be set in this section.
7.9.2 Configuration Properties
## ### This section is generated. Any changes made ### here will be overwritten in a rebuild ## whirr.cluster-name=SaaSHR whirr.provider=cloudservers whirr.image-id=9506164 whirr.hardware-id=4 whirr.instance-templates=2 dn whirr.private-key-file=C:/jeewiz/external/ssh/CloudTranRackspaceImageKey whirr.public-key-file=C:/jeewiz/external/ssh/CloudTranRackspaceImageKey.pub ## ### Non whirr properties ## run-script=runScript_rackspace.sh deploy-script=deployScript_rackspace.sh absolutePath=C:/jeewiz/examples/CloudTran/MultiTenancy/workspace/MultiTenancy/deployment/RackspaceTest/ ## ### ### Anything below this line will not be overwritten ### ## ### The identity and credential need to be provided. ### The identity is the your Rackspace username ### The credential is the api key which can be obtained from your Rackspace account ### - Your Account -> API key ### ## whirr.identity=xxxxxxxxxxxxxx whirr.credential=xxxxxxxxxxxxxx

7.9.3 Deploying

One of the generated artefacts of the deployment is an ant build.xml file. This ant script contains a number of targets. The main ones are

startGrid            Starts the grid on the servers           
deployApplication    Deploys the application by copying and running the appropriate shell scripts to the running servers
stopApplication      Stops the running application on the servers.
allocateServers      Starts a new cluster of servers based on the deployment configuration
deallocateServers    Destroys the running servers, even if the application is still running.
listServers          Lists the existing machines used in the cluster.

To run a particular target open a command box at the location of the ant script and type

ant <target>