search

esseph / groundcontrol

A basic html5/php/mysql interface for monitoring, graphing and controlling wireless and other devices (ubiquiti, mikrotik, cambium, etc.)
GNU General Public License v2.0
15 stars 3 forks source link

roadmap to release v1.0 #1

Open esseph opened 9 years ago

esseph commented 9 years ago

UBNT

rkerr commented 9 years ago

I don't know what level of thought you've put into how you would achieve these things, but I would encourage you not to re-invent the wheel where possible. There are tools already in existence for network config archiving and diffing (eg RANCID, punc) and for discovery (netdot, netdisco, SNMP::Info). You can potentially save a lot of work by using some of those in the backend and focusing more on the frontend at least for an initial release.

syadnom commented 9 years ago

rkerr, Josh did say the plan was to use existing scrapers. Some things might require a bit more (pushing configs to radios for example), but I think everyone is on the same page about reusing existing tools.

jabreity-zz commented 9 years ago

I'm sold. The reason I suggest python is it really works well to wrap around command line tools. There's already existing libraries to be called upon for much of this - for SNMP, syslog monitoring, etc.

Jason

On Fri, Dec 5, 2014 at 11:11 AM, syadnom notifications@github.com wrote:

rkerr, Josh did say the plan was to use existing scrapers. Some things might require a bit more (pushing configs to radios for example), but I think everyone is on the same page about reusing existing tools.

— Reply to this email directly or view it on GitHub https://github.com/esseph/groundcontrol/issues/1#issuecomment-65811602.

tetherow commented 9 years ago

Device discovery: I've been able to reverse engineer all but 2 bytes of the UBNT discovery packet.

What are you envisioning when you say device provisioning? Being able to automatically push a one off config file for a radio?

On 12/04/2014 06:47 AM, Josh Reynolds wrote:

UBNT

  • device discovery
  • device provisioning
  • config archives
  • config "diff"
  • mass config changes
  • firmware storage
  • mass firmware upgrades

— Reply to this email directly or view it on GitHub https://github.com/esseph/groundcontrol/issues/1.

esseph commented 9 years ago

Just basic config changesvia the groundcontrol UI.

I really like the way that aircontrol 1 was laid out. AC1 would scan an entire config file and then let you see which boxes you wanted to look at in the UI(on the monitoring side)-- basically it would look at every variable and their value. If it knew the "proper" value for variable values (like airmax priority), it would use the word equivalent.

I see no reason why you couldn't do that for configuration as well. This would allow us to support new devices as soon as they were released.

On 12/05/2014 08:31 AM, tetherow wrote:

Device discovery: I've been able to reverse engineer all but 2 bytes of the UBNT discovery packet.

What are you envisioning when you say device provisioning? Being able to automatically push a one off config file for a radio?

On 12/04/2014 06:47 AM, Josh Reynolds wrote:

UBNT

  • device discovery
  • device provisioning
  • config archives
  • config "diff"
  • mass config changes
  • firmware storage
  • mass firmware upgrades

— Reply to this email directly or view it on GitHub https://github.com/esseph/groundcontrol/issues/1.

— Reply to this email directly or view it on GitHub https://github.com/esseph/groundcontrol/issues/1#issuecomment-65824550.

rkerr commented 9 years ago

All sounds good - I'd like to help out where possible.

juantellezi commented 9 years ago

See that this never takeoff, if you need help please tell me, i have my own programed system , it do almost everything what you say.

jaapjolman commented 9 years ago

I would also like to help, juantellezi what system did you build?