Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compilation VM number is too small for timely CF deployment #50

Closed
supertopher opened this issue Jul 30, 2016 · 3 comments
Closed

Compilation VM number is too small for timely CF deployment #50

supertopher opened this issue Jul 30, 2016 · 3 comments

Comments

@supertopher
Copy link

At cloud ops we favor a pretty robust compilation VM size and number. If you do a deployment during the work day, programmer time costs alot more than VM time.

3 VM takes a long time to deploy CF. We set our cloud config to a more liberal 6.

@cf-gitbot
Copy link

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/127404947

The labels on this github issue will be updated when the story is started.

@Amit-PivotalLabs
Copy link

Agreed, 6 would be nicer. Prioritizing.

@jchester
Copy link

The flipside is that this happens to people who set up brand-new accounts to fix #45:

Error 100: Unknown CPI error 'Unknown' with message 'You have requested more instances (6) than your current instance limit of 5 allows for the specified instance type. Please visit http://aws.amazon.com/contact-us/ec2-request to request an adjustment to this limit.'

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants