-
Notifications
You must be signed in to change notification settings - Fork 8
0.7 TAP Maintenance
This page provides some guidelines for maintaining TAP 0.7.
Go here for CloudFoundry documentation
If the CLI responds with: No additional stagers available
, then existing runners are out of space. You need to add more runners to the platform, as follows:
-
SSH to jumpbox:
ssh -i key-to-jumpbox ubuntu@JumpboxIP
-
Authorize as a root:
sudo -i
-
Edit the file:
vim cf.yml
-
Find the lines shown below:
256 - name: runner_z1 257 instances: 2
-
Add more runners by changing the
instances
number, for example, from2
to4
. -
Save your changes and execute:
bosh deployment cf.yml
-
Run deployment with:
bosh deploy
-
Carefully review changes and accept them by entering
yes
Warning: Do not cancel this process. -
This task can take from 20 to 40 minutes to complete.
If you cannot create a service, check your Docker storage:
-
SSH to jumpbox:
ssh -i key-to-jumpbox ubuntu@JumpboxIP
-
Authorize as a root:
sudo -i
-
Select deployment:
bosh deployment docker-broker.yml
-
SSH to the instance executing:
bosh ssh
-
Check disk usage with
df -h
. If the store is full, or nearly full, you must resize the disk. Logout from the machine. -
Edit the file:
vim docker-broker.yml
-
Find the line:
persistent_disk: 65536
-
Provide a new value in MB and save your changes.
-
Select docker-broker deployment:
bosh deployment docker-broker.yml
-
Deploy changes:
bosh deploy
. -
Carefuly review changes and accept them by entering
yes
Warning: Do not cancel this process. -
This task can take from 45-60 minutes to complete, depending on the size of the volume.