0.7 TAP Maintenance

Maintenance for TAP 0.7

This page provides some guidelines for maintaining TAP 0.7.

CloudFoundry

Go here for CloudFoundry documentation

Adding more runners to TAP instance

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:

1. SSH to jumpbox: ssh -i key-to-jumpbox ubuntu@JumpboxIP

2. Authorize as a root: sudo -i

3. Edit the file: vim cf.yml

4. Find the lines shown below:

   256 - name: runner_z1
   257   instances: 2
   

5. Add more runners by changing the instances number, for example, from 2 to 4.

6. Save your changes and execute: bosh deployment cf.yml

7. Run deployment with: bosh deploy

8. Carefully review changes and accept them by entering yes
   Warning: Do not cancel this process.

9. This task can take from 20 to 40 minutes to complete.

Resizing docker storage:

If you cannot create a service, check your Docker storage:

1. SSH to jumpbox: ssh -i key-to-jumpbox ubuntu@JumpboxIP

2. Authorize as a root: sudo -i

3. Select deployment: bosh deployment docker-broker.yml

4. SSH to the instance executing: bosh ssh

5. Check disk usage with df -h. If the store is full, or nearly full, you must resize the disk. Logout from the machine.

6. Edit the file: vim docker-broker.yml

7. Find the line: persistent_disk: 65536

8. Provide a new value in MB and save your changes.

9. Select docker-broker deployment: bosh deployment docker-broker.yml

10. Deploy changes: bosh deploy.

11. Carefuly review changes and accept them by entering yes
    Warning: Do not cancel this process.

12. This task can take from 45-60 minutes to complete, depending on the size of the volume.