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

gluon-emitter #7

Open
ghost opened this issue Dec 18, 2015 · 13 comments
Open

gluon-emitter #7

ghost opened this issue Dec 18, 2015 · 13 comments

Comments

@ghost
Copy link

ghost commented Dec 18, 2015

The supernodes must be in the graph somehow.

@dereulenspiegel
Copy link
Collaborator

I would consider an alias file a "dirty hack". I would prefer an announced agent for supernodes. But I will see if an alias file could be an intermediate solution.

@ghost
Copy link
Author

ghost commented Dec 19, 2015

I already read your forum posts about that. I basically agree with you, but I need the aliases, because I don't have access to the supernodes of our domain and those who do don't have the time to care about such 'unneccecary' things as announced.

@dereulenspiegel
Copy link
Collaborator

As a middle ground I started to implement the gluon-emitter (https://github.com/ffdo/node-informant/tree/supernode). A small daemon which runs on the supernodes, can read in an alias file, but has also builtin support to dynamically collect different metrics. This WIP. Advantage of this approach is, that it is more suited to automated deployment scenarios like Ansible, Chef etc. and that I don't have to modify anything in the gluon-collector.

@ghost
Copy link
Author

ghost commented Dec 25, 2015

Great! I'll start testing it on my computer.

@dereulenspiegel
Copy link
Collaborator

Whoa, sorry wrong impression. I started to implement this, but it is far from finished. Currently I have trouble receiving in the multicast group. Once this is solved we can start testing.

@dereulenspiegel
Copy link
Collaborator

In the supernode branch should now be a first usable version of the gluon-emitter.

@ghost
Copy link
Author

ghost commented Dec 25, 2015

We should either rename this issue to "gluon-emitter" (is that possible?) or create a new one and close this one

@dereulenspiegel dereulenspiegel changed the title Aliases.json gluon-emitter Dec 25, 2015
@ghost
Copy link
Author

ghost commented Dec 26, 2015

root@gl1 /o/node-informant# bin/gluon-emitter -interface bat0 -alias alias.yaml 
INFO[0000] Loading alias file                           
FATA[0000] Can't load alias file                         error=Unknown file format .yaml path=alias.yaml

@dereulenspiegel
Copy link
Collaborator

Currently the extension of the alias file needs to be yml or json. A better handling of file types will come soon.

@ghost
Copy link
Author

ghost commented Dec 26, 2015

okay maybe that with 'yml instead of 'yaml' should be documented..
It has been running for 10 mins now, but the node is not showing up on the map.

@dereulenspiegel
Copy link
Collaborator

If you have enabled debug output you should see if gluon-emitter is receiving any requests at all and with how many bytes it es responding. Keep in mind that this far from being finished or stable.

@stebifan
Copy link

It would be nice if gluon-ermitter automaticly pushes the MAC Addresses of all Interfaces on the Server. Here we have different MACs for every interface. Its hard to put them all in a Aliases file because they are dynamic.

@dereulenspiegel
Copy link
Collaborator

@stebifan As you can see in the README automatic collection of facts/statistics is already on the ToDo list.

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

No branches or pull requests

2 participants