---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 36
router_instances: 24
api_instances: 6
doppler_instances: 21
log_api_instances: 12
scheduler_instances: 4
cc_worker_instances: 4
cc_hourly_rate_limit: 60000
cc_staging_timeout_in_seconds: 2700
cc_maximum_health_check_timeout_in_seconds: 300
paas_region_name: ireland

prometheus_disk_size: 500GB
prometheus_retention_size: 475GB

---
uaa_instances: 3
nats_instances: 3
diego_api_instances: 3
cell_instances: 36
router_instances: 24
api_instances: 8
doppler_instances: 48
log_api_instances: 24
scheduler_instances: 6
cc_worker_instances: 6
cc_hourly_rate_limit: 60000
cc_staging_timeout_in_seconds: 2700
cc_maximum_health_check_timeout_in_seconds: 300
paas_region_name: ireland

prometheus_disk_size: 500GB
prometheus_retention_size: 475GB

Scale infra for cell increase in iso-segments
Scale infra for cell increase in iso-segments

The use of isolation segments bypasses some of our checks to ensure
scaling of infra components proportional to diego-cell counts.

We are adding a total of 36 cells (12+24) for Notify who intend to do
load testing and expect a general rise in requests. This will raise the
total cell count in Ireland to 94.

In order to ensure the platform is not bottlenecking Notify, we scale
infra to roughly map to ratios in prod-lon.
