roadmap

[dtaht]

I was looking for a way to collaborate directly on a roadmap document. This isn't it.

[rchac]

Curious what major features or changes we should tackle next. Anyone have recommendations? I was considering integrating a netlink library so we can better track existing queues and add queues without a full reload. It probably possible without using a net link library but I figure that's a generally better direction to go.

[interduo]

@rchac

My suggestion is:

1. Make some additional features/bug repair

• Adding/Reloading single subscriber service parameters #49

• Reloading All QoS rules - don't drop packets for customers when reloading #47
  This is the most important thing now, the network throughtput drops to 15% when we do full reloading for ~4sec. The first issue will remove the need to do this every circuits change (its easier to implement than remove purpose of this bug)

• Allow data collecting from LibreQoS into monitoring tools #75
  InfluxDB with UI is not so ussable like it looks. Zabbix eats it on first round ;-)

• Support for one-network-card card configuration, single card configuration, one NIC only #48
  This is important mainly for 2 reasons - small instances <20gbps could have one 40G instead of two
  (most med-shelf switches have only 4 ports 40G). This could seriously lower the money spend on ports for main / backup LibreQoS servers.

2. Review the code and make some "hardenings" like:

• don't busy CPU with graphs and other things #74
• Running LibreQoS.py from other place like it's dir gives an error - small improvment needed #54
• review,test,enhance API of LibreQoS - allow to use all functions of lqtools.py from API,
• Make some integrations with most popular CRMs,

All projects after few versions needs to say stop and do some bunch of testing, then review and redesign. After all needed features implemented this would be a good time to do this. This would be for example a good time for implementing net link library.

3. Make better default performance settings: (libreqos is mainly for grinding the network packets so we need make it fast as possible)

• Lower CPU usage a bit #30
• performance tuning - some improvements #96
• Using HTB more efficiently with cburst and burst #40
• testing, testing, more testing, and much more testing,

4. Afterwards:
   Mark version 2.0.
   Make new roadmap,
   Send information about LQoS to all ISPs all-over-the-world to use it,

[dtaht]

Is there a way to reach out to the userbase?

[dtaht]

I would enjoy a chance for us all to get together for a videoconference to discuss a roadmap. Thursdays are my big meeting day, but wednesdays are good too. To get NZ in the picture, somewhere between 12-2 PST (which is friday in NZ) is good. I generally use the galene videoconferencing server, and have them up all over the world. So I setup a new one here:

https://spacewrt.net:8443/group/libreqos/

It works best with chrome, any login you want, no password. Would anyone here be able to get together in these windows this week?

[thebracket]

As long as I have advanced notice (I'm hearing impaired, so I need to setup my assistive headphone kit), I can try and attend. I'm in US central time, and since I mostly do consulting and authoring my schedule is pretty flexible between 8am and 4:30pm central time (GMT-6); outside of those hours, I'm chasing a baby round in circles.

[dtaht]

oh, wow, I'm almost completely deaf in one ear and struggle a lot in social situations. Also blind in one eye. It makes for a different life, eh? One of my interests in videoconferencing tools is I REALLY want good speech to text support in them in case I lose the other ear.

1PM PST thursday?