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.

Sign up for GitHub

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

Jump to bottom

clarify expectations for cost estimation #629

Merged
merged 1 commit into from
Apr 3, 2018
Merged

clarify expectations for cost estimation #629

merged 1 commit into from
Apr 3, 2018

Conversation

willingc
Copy link
Collaborator

@willingc willingc commented Apr 3, 2018

Closes #626

  • Moves cost projection section to an appendix of the administrator guide.
  • Adds a clarification section at the beginning
  • Reorder to have all factors precede the cost estimator

@yuvipanda
Copy link
Collaborator

I like it, @willingc!

@yuvipanda yuvipanda requested a review from choldgraf April 3, 2018 01:24
betatim
betatim reviewed Apr 3, 2018
View reviewed changes
doc/source/cost.rst
the resources you need to provide. In the future JupyterHub will have
auto-scaling functionality, but currently it does not. This means that you need
to provision resources for the *maximum* expected number of users at one time.


Examples
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we move this further to the top (or reference it from the beginning) when we have a few more examples. It probably provides the best examples/guidance on how to work out how much it might cost you. As the hard part is converting "N students in my semester long course" into "number of CPUs and RAM to have available". After that you "just " have to look up your cloud providers prices ;)

@betatim betatim merged commit b9e225b into jupyterhub:master Apr 3, 2018
@betatim
Copy link
Member

betatim commented Apr 3, 2018

Ah, I overlooked the review request. Chris if you want something changed let me know and we can make a new PR.

@willingc willingc deleted the costs-clarify branch April 3, 2018 10:48
@manics manics mentioned this pull request Aug 15, 2018
Closed
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@betatim betatim betatim left review comments

@choldgraf choldgraf Awaiting requested review from choldgraf

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@willingc @yuvipanda @betatim