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

optionally display STOPPING and STOPPED hosts #356

Merged
merged 3 commits into from
Mar 17, 2017

Conversation

nathantypanski
Copy link
Contributor

Previously, the environment overview page only showed hosts in the deploy
status that were not STOPPING or STOPPED. The only way to look at them is to
look in "Total" hosts.

First of all, it doesn't make sense to me to to have an agent state that shows
up in the TOTAL but isn't available in the board.

This adds an extra configuration parameter to display STOPPING and STOPPED
hosts. It is disabled by default, in case you have some reason you do not
display those states.

Related: #354

Current behavior:

screen shot 2017-03-15 at 9 24 35 pm

Notice the TOTAL for the Previous(a2f66f1) build is 1, even though none of the state columns actually display 1 host!

With os.environ.setdefault("DISPLAY_STOPPING_HOSTS", "true") in manage.py, we can see even the stopped hosts:

screen shot 2017-03-15 at 9 24 59 pm

Previously, the environment overview page only showed hosts in the deploy
status that were not STOPPING or STOPPED. The only way to look at them is to
look in "Total" hosts.

First of all, it doesn't make sense to me to to have an agent state that shows
up in the TOTAL but isn't available in the board.

This adds an extra configuration parameter to display STOPPING and STOPPED
hosts. It is disabled by default, in case you have some reason you do not
display those states.

Related: pinterest#354
@lilida
Copy link
Contributor

lilida commented Mar 16, 2017

+@sbaogang for comment on STOPPING and STOPPED.

@sbaogang
Copy link
Contributor

sbaogang commented Mar 16, 2017

I am all for it - STOPPING/STOPPED was added as a new feature to gracefully shutdown apps sometimes ago, apparently the UI part was not updated.

@nathantypanski
Copy link
Contributor Author

Perhaps we should default it to enabled, then? Is there a reason to hide this?

@lilida
Copy link
Contributor

lilida commented Mar 16, 2017

I think it should be enabled by default, Nathan, can you make it be enabled? Also, I'd like to have your agreement on distributing the code in Apache 2.0 license for me to merge it. You can reply your agreement just here.

@nathantypanski
Copy link
Contributor Author

I agree to have my code released under the Apache 2.0 license.

I missed this earlier in d5e5efa -
changed it in manage.py but not in settings.py.
@lilida lilida merged commit e12e4ff into pinterest:master Mar 17, 2017
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

Successfully merging this pull request may close these issues.

3 participants