Re: Deploying CloudFoundry on AWS - Too many machines are being created
Sabha
As the blog post explained, its possible at higher cost (due to bigger vms),
as well as scalability for different components...
If you want to collocate some jobs to shrink the # of vms, you would need to
modify the vm sizes (cpu/ram/disk) as well as lots of job related references
(like nats or loggregator or others to avoid port/property conflicts). Its
manual and error-prone process.
What version of cf-release/manifest you are using/testing?
-Sabha
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Deploying-CloudFoundry-on-AWS-Too-many-machines-are-being-created-tp467p472.html
Sent from the CF Dev mailing list archive at Nabble.com.
as well as scalability for different components...
If you want to collocate some jobs to shrink the # of vms, you would need to
modify the vm sizes (cpu/ram/disk) as well as lots of job related references
(like nats or loggregator or others to avoid port/property conflicts). Its
manual and error-prone process.
What version of cf-release/manifest you are using/testing?
-Sabha
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-Deploying-CloudFoundry-on-AWS-Too-many-machines-are-being-created-tp467p472.html
Sent from the CF Dev mailing list archive at Nabble.com.