-
Notifications
You must be signed in to change notification settings - Fork 1
/
README
37 lines (25 loc) · 1.17 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
Before running the app, first create $HOME/.cooling-tower/config.yml
Its contents should look something like this:
access_key: YOUR_EC2_ACCESS_KEY
secret_access_key: YOUR_SECRET_EC2_ACCESS_KEY
management_image_id: ami-2741ad4e
backend_image_id: ami-5949a530
frontend_image_id: ami-2749a54e
# Optional, only required if starting a mgmt server from ctjr
bucket: SOME-S3-BUCKET
# Optional, defaults to 'default'
key_pair_name: YOUR_KEY_PAIR_NAME
# Optional, as long as you have working ~/.ssh/config
ssh_private_key_file: /Users/YOU/.ssh/YOUR_PRIVATE_KEY.pem
ssh_username: root
# Optional, unless you're using latest EAP instances
deploy_dir: /opt/jboss-eap-5.0.1/jboss-as/server/cluster-ec2/farm/
# Optional, one of deltacloud or ec2 (default)
cloud: deltacloud
# Optional, only required if using Deltacloud
deltacloud_url: http://localhost:3001/api
If, upon starting the app, you see errors regarding an "already
activated net-ssh", try updating your gem:
$ sudo gem update net-ssh
Make sure you're running at least version 0.0.2 of deltacloud-core
(the server to which ctjr connects)