Hi Amit

We are able to combine following cloud foundry jobs into one VM and deploy. The global default setting is serial:true
Curious to confirm, In this scenario, what is the order of the template jobs being created? Will it serially create the template jobs one by one from the beginning?
Here I have arranged the templates reading your answer in the below link

https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/GQR3FGZGBPPZS56ZYALBYX6WGUVTY24Y/

Thanks for your detailed answer in this link.

Templates:
- name: etcd
release: cf
- name: etcd_metrics_server
release: cf
- name: nats
release: cf
- name: nats_stream_forwarder
release: cf
- name: collector
release: cf
- name: postgres
release: cf
- name: uaa
release: cf
- name: cloud_controller_clock
release: cf
- name: consul_agent
release: cf
- name: go-buildpack
release: cf
- name: binary-buildpack
release: cf
- name: nodejs-buildpack
release: cf
- name: ruby-buildpack
release: cf
- name: php-buildpack
release: cf
- name: python-buildpack
release: cf
- name: staticfile-buildpack
release: cf
- name: cloud_controller_ng
release: cf
- name: statsd-injector
release: cf
- name: blobstore
release: cf
- name: route_registrar
release: cf
- name: metron_agent
release: cf
update: {}


regards
Nithiyasri

If the question can be paraphrased as "when colocating multiple job (templates) on a single VM, will they start in parallel or instead in some sort of order?" then the jobs will generally come online in parallel unless one job has a monit-level dependency on another, in which case monit will start them in order of the dependencies.

Given you are colocating jobs which are usually on multiple VMs and hence the ordering would be handled by bosh jobs (bosh-level dependencies), these job templates will not have monit-level dependencies configured and so you will likely see most jobs starting together. This may or may not work; we haven't tried starting all jobs in parallel.

The serial: true configuration in the bosh manifest applies at the bosh-level to multiple VMs, but as you only have a single VM it has no effect.

Thanks,
Rob Dimsdale
CF Release Integration
Pivotal