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

"uncontained" nodes clutter container view #1129

Closed
rade opened this issue Mar 5, 2016 · 7 comments
Closed

"uncontained" nodes clutter container view #1129

rade opened this issue Mar 5, 2016 · 7 comments
Assignees
Labels
dogfood Important for the developer's own use of the project
Milestone

Comments

@rade
Copy link
Member

rade commented Mar 5, 2016

screenshot from 2016-03-05 10 07 32

If I was to draw the structure of that service on the whiteboard, I certainly would not be including any of the "uncontained" nodes. I might include the Internet, if my service was accessible from / talking to that. And I might include some uncontained processes if they are interacting with my service.

Possible fix: add a show/hide for Uncontained.

@2opremio
Copy link
Contributor

2opremio commented Mar 5, 2016

Related: #552

@2opremio
Copy link
Contributor

2opremio commented Mar 5, 2016

@rade Is it fair to phrase it as: As a user, I only want to see Uncontained nodes (probably expanded as processes) when they constitute a service component or are communicating with my service components?

If that's the case, we need a way to identify your service components.

Possible fix: add a show/hide for Uncontained.

Do you want to hide them even if they are talking to your service or are part of your service (this will happen in hybrid services)?

EDIT: slightly modified the formulation to include hybrid environments.

@2opremio 2opremio added the dogfood Important for the developer's own use of the project label Mar 5, 2016
@rade
Copy link
Member Author

rade commented Mar 5, 2016

Is it fair to phrase it as: As a user, I only want to see Uncontained nodes (probably expanded as processes) when they are communicating with my service components?

Yes.

If that's the case, we need a way to identify your service components.

"all containers in the current view" is a good approximation.

Do you want to hide them even if they are talking to your service or are part of your service.

For the show/hide, yes. But I really only proposed that as a quick fix. Doing the showing/hiding automatically along the lines you suggest would probably work better.

@2opremio
Copy link
Contributor

2opremio commented Mar 5, 2016

"all containers in the current view" is a good approximation.

This assumes that services are fully containerized, which may not be the case.

@rade
Copy link
Member Author

rade commented Mar 5, 2016

The hybrid view of #552 might well be the solution to this, effectively eliminating the notion of "Uncontained" from the UI altogether.

@pidster
Copy link
Contributor

pidster commented Mar 7, 2016

I think the hybrid view should be the default one and the other views be straightforward filters.

@pidster
Copy link
Contributor

pidster commented Jun 9, 2016

We're seeing this in the reference application too.

reference-app-noise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dogfood Important for the developer's own use of the project
Projects
None yet
Development

No branches or pull requests

4 participants