Dear NUT developers and contributors,<br><br>time has come to shed more light on 2.8.0 roadmap!<br><br>Ubuntu Developer Summit attendance has helped to clarify things.<br>several of 2.8.0 tasks are detailed here: <a href="https://wiki.ubuntu.com/ServerOneiricInfraPower" target="_blank">https://wiki.ubuntu.com/ServerOneiricInfraPower</a><br>
<br>I'm conscious that our development infrastructure (Alioth) is not that suitable to track roadmaps, "Agile" specs and developments, as we do in NUT.<br>Charles and I are still investigating possible improvements.<br>
<br><br>as for the 2.8.0 roadmap itself, here is the overall plan:<br><br>1) NUT schedule is mapped on the next Ubuntu release (11.10, aka Oneiric Ocelot), to be available in it:<br><a href="https://wiki.ubuntu.com/OneiricReleaseSchedule" target="_blank">https://wiki.ubuntu.com/OneiricReleaseSchedule</a><br>
<br>this means that:<br>- once released, NUT packages have to be updated in Debian, and then sync'ed in Ubuntu. which needs a bit more time,<br>- the above has to happen between August 25th (Beta freeze) and September 29th (Final freeze)<br>
<br>but this doesn't mean that other distro / OS, or users needs in general, won't be considered!<br>it's simply a main target.<br><br>2) the targeted features list is:<br><br>priority 1)<br> * Mozilla NSS support:<br>
I've got to go again through this, but code is done, tested (including regression) and should be ready for merge (congrats again to Emilien Kia and thanks to Eaton)<br> I hope Charles will be able to handle the merge ;)<br>
<br> * nut-scanner:<br> Fred Bohe is currently working on this, and has already made good progress.<br> a first version will probably be merged in the trunk next week ; from there, improvements will happen on the trunk<br>
the task should be completed by the end of June (another thanks to Eaton)<br><br> * configuration: I'm not yet sure about the exact content of this task!<br> pyNutConfig class + CLI pynut-config (or simply nut-config), with an augeas wrapper first and maybe simple fallback with no deps<br>
optionally integrate in NUT-Monitor with a GUI<br> David Goncalves will maybe help on this one<br><br> * nut-ipmi driver step 1<br> only include power supply unit (PSU) support<br> I'm still doing some investigation, but already have few things (m4 macro and very initial driver)<br>
I should be able to commit something within the next couple of weeks<br><br> * jNUT Java binding<br> the exact content of this task is still to be defined, but this should include native client access and NSS support,<br>
the following will be considered with a lower priority:<br> - device discovery (JNI using libnut-scanner),<br> - configuration (using Augeas)<br> - mDNS discovery<br> I'm currently checking resources staffing with Eaton<br>
<br> * PowerChain step 1<br> as described in the above ServerOneiricInfraPower link, the idea is to be able to link powerflow, and consider the whole. power chain, and not anymore the UPS only. the nut-ipmi driver is a dependency of the task<br>
step 1 adds:<br> - device.parent in nut-names,<br> - support in drivers (parameters in main.c->storeval())<br> - support upsc for "-P PowerChain"<br> I've already started a few things, and will get back soon for the RFC<br>
<br> * NUT generalization, step 1<br> - more generic nut names (ie move from ups.* to device.* in nut-names.txt)<br>
- move existing ups.{model,mfr,...} to device.* in drivers<br>
- move ups.status to device.status<br>
- with compat mapping counterparts (device.* also to ups.* if (device.type == ups))<br><br> * standard flow of bug-fixes and stagging improvements...<br><br>priority 2 (best effort)<br> * powerchain step 2: support in upsmon<br>
* Windows port integration: if possible, need step refactoring / enhancement / more testing<br> * better Mac OS X integration (including StartupItem initscript, .pmdoc packaging script and ?)<br><br><br>I realize that this is ambitious, as Arjen noted, but not impossible and the progress is already good.<br>
we also have priority 2 which are best effort. so we can still postponed these a bit more, if needed.<br>we're finally gaining more support from Eaton, hopefully in a stable way, which will be determinant.<br><br>I will get back to you soon with RFCs and progress update on the above.<br>
Feedback, comments, help and testing are welcome, as always.<br><br>cheers,<br>Arnaud<br>-- <br>Linux / Unix Expert R&D - Eaton - <a href="http://powerquality.eaton.com" target="_blank">http://powerquality.eaton.com</a><br>
Network UPS Tools (NUT) Project Leader - <a href="http://www.networkupstools.org/" target="_blank">http://www.networkupstools.org/</a><br>Debian Developer - <a href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>
Free Software Developer - <a href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br><br>