Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

[dns] Add weavedns status to weave status #237

Closed
bboreham opened this issue Nov 26, 2014 · 7 comments
Closed

[dns] Add weavedns status to weave status #237

bboreham opened this issue Nov 26, 2014 · 7 comments

Comments

@bboreham
Copy link
Contributor

The weave status command could at minimum state whether weavedns is running.
Perhaps give some other info like how many addresses are known to the local server.

@squaremo
Copy link
Contributor

$ curl http://<weavedns>:6785/status
Serving: weave.local.
Local names: 5

Anything else?

@squaremo
Copy link
Contributor

(For the synchronisation used in #200 we can use -X HEAD so it doesn't bother generating status info)

@rade
Copy link
Member

rade commented Jan 5, 2015

(For the synchronisation used in #200 we can use -X HEAD so it doesn't bother generating status info)

...which, unfortunately (and per the curl docs), doesn't work. One needs to use -I instead. Which breaks our abstraction in the weave script. grrr

@rade
Copy link
Member

rade commented Jan 10, 2015

@squaremo have you done any work on this or was the above comment just a mock-up?

The output should contain the version in the first line; just as happens for the router.

@squaremo
Copy link
Contributor

have you done any work on this or was the above comment just a mock-up?

It's a mock up, intended to stimulate discussion of what else could appear there.

@rade
Copy link
Member

rade commented Jan 12, 2015

We could display all (local, for now) records. After all, the router status shows all MACs in active use, which should be the same order of magnitude of information.

That would take care of #266.

@rade rade changed the title Add weavedns status to weave status [dns] Add weavedns status to weave status Jan 29, 2015
@inercia
Copy link
Contributor

inercia commented Mar 2, 2015

I would keep it simple and, for a GET /status, I would return just the version, and then I would return all names with a GET /name. I was planning to add a full RESTful interface for names anyway, with a GET method for listing all IPs for a name, and a POST method for adding more IPs...

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

No branches or pull requests

5 participants