title | expires_at | tags | |
---|---|---|---|
Deployment Constraints |
never |
|
Before deploying the Diego cluster, ensure that the sql database it will connect to is already deployed and provisioned.
In your manifest, ensure that the following constraints on job update order and rate are met:
-
BBS servers should update before BBS clients. This can be achieved by placing
database_zN
instances at the beginning of the jobs list in your manifest. For example:jobs: - instances: 1 name: database_z1
-
database_zN
nodes update one at a time. This can be achieved by settingmax_in_flight
to1
andserial
totrue
fordatabase_zN
jobs.- instances: 1 name: database_z1 ... update: max_in_flight: 1 serial: true
-
brain_zN
jobs update separately from cells. This can be achieved by settingmax_in_flight
to1
andserial
totrue
forbrain_zN
jobs.- instances: 1 name: brain_z1 ... update: max_in_flight: 1 serial: true