TAS components - what feeds what, after running CF push

What feeds what after a developer runs cf push

.

1. 1. What is the first component?

(in the image on the left)

.

(Additional context) This component of TAS is the first component involved or the first to take action after a developer runs the “cf push” command. It forwards the developer's request to the 2nd component which then tells the 3rd component to stage the app the developer is requesting

• Diego Brain

• Go Router

• Droplet

• CAPI

 2. What is the 2nd component, that then tells the 3rd component to "stage the app" the developer is requesting

• NATS

• Droplet

• CAPI

• Diego Brain

3. 3. What is the 3rd component, that then finds out how to run the app the developer is requesting  

• 3. Diego brains

• Doppler

• Diego Cell

• blobstore

4. Whats the 4th component, which has the buildpacks and source code downloaded on to it so it can create/build a droplet,  so the app can be run 

• Diego Brain

• Blobstore

• Diego cell

• NATS

5. 5. Where does Diego cell then put/store that droplet after its built 

• GoRouter

• Blobstore 

• Diego Brain

• Doppler

Which file would you look at to see what resources an app is requesting (such Ram, buildpacks, etc)?

• main.go

• manifest.yml

• go.mod

• .gitignore

what command would use to see quota details via cli?

• bosh quotas

• cf quota

• cfdot quotas

• cf quotas

where would you go to scale up Diego Cells to increase their cpu, ram and disk?

• AppsMan

• OpsMan > TAS tile > resource config

• OpsMan > MySQL

• OpsMan > TAS tile > Advanced features

Who's responsible for scaling diego cells?

• support

• platform engineers

• developer

what command below would be the correct command to check vm vitals?

(to check for bleeding/issues )

• bosh  -d cf-d11d1ea2bd990762c103 is --v -p

• bosh -d cf-d11d1ea2bd990762c103 vms --vitals  

  
  

• bosh vm -p