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

Removing render.RenderableNode #1204

Merged
merged 6 commits into from
Mar 29, 2016
Merged

Removing render.RenderableNode #1204

merged 6 commits into from
Mar 29, 2016

Conversation

paulbellamy
Copy link
Contributor

Includes and supersedes #1169. Will need a rebase on master.

TODO:

  • Tests for detailed node rendering

@paulbellamy paulbellamy force-pushed the removing-renderablenode branch 2 times, most recently from 1eff227 to 8043001 Compare March 24, 2016 09:35
@paulbellamy
Copy link
Contributor Author

squashed and rebased up to 8c0fddc

@paulbellamy paulbellamy force-pushed the removing-renderablenode branch from 8043001 to a6eff1d Compare March 24, 2016 10:05
for _, k := range c.psMap.Keys() {
keys = append(keys, k)
func (c Counters) ForEach(f func(key string, val int)) {
if c.psMap != nil {

This comment was marked as abuse.

@@ -121,7 +121,7 @@ var (
// Node is arbitrary. We're free to put only precisely what we
// care to test into the fixture. Just be sure to include the bits
// that the mapping funcs extract :)
Client54001NodeID: report.MakeNode().WithLatests(map[string]string{
Client54001NodeID: report.MakeNode().WithID(Client54001NodeID).WithLatests(map[string]string{

This comment was marked as abuse.

This comment was marked as abuse.

@tomwilkie
Copy link
Contributor

Like this a lot. Some stuff in experimental needs fixing, and I think we need to add some testing for the final, fully rendered NodeSummaries.

Also I think we need to address #836 ASAP. And we can potentially experiment with not merging in existing metadata when we do a derived node.

@tomwilkie
Copy link
Contributor

Have run against example app, seems to do all the right things.

@tomwilkie
Copy link
Contributor

LGTM on this.

Squash of:
- use detailed.Summaries to render topology nodes
- ban merging nodes of different topologies (they should be mapped)
- need to prune parents when mapping node types
- render container images by id if they have no name
- remove separate render ids and prune parents in NewDerived*
- don't render metrics/metadata for groups of nodes
- fixing up tests
- removing pending unit tests (for mapping.go, for now)
- updating experimental dir for RenderableNode removal
Squash of:
- including children in topologies_test.go
- report.Node.Prune should prune children also
- rewrote ShortLivedInternetConnections test to express its intent
- adding tests for detail Summary rendering
@paulbellamy paulbellamy force-pushed the removing-renderablenode branch from 28f5957 to fe6203f Compare March 29, 2016 13:13
@paulbellamy
Copy link
Contributor Author

Rebased on 3744f47

@paulbellamy paulbellamy merged commit 0a9af6f into master Mar 29, 2016
@paulbellamy paulbellamy deleted the removing-renderablenode branch March 29, 2016 13:40
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.

2 participants