Answer: soon!
Here's the present TODO file, as stored in git:
- HIGH PRIORITY:
- Test interfaces in CLI and webapp thoroughly
- make authz_ownership work for all of the new commands (require admin
group?)
- verify duplicate hostname and ip code works
- yum SHA knowledge for F11/F12 from older OS (reposync/import)
- MODERATE PRIORITY:
- Look over old webapp and ensure tooltips in new version are good
enough or better
- Replicate improvements
- reinstate reports with formatted output options
I think the biggest challenge here is the ownership one, as that
requires some testing, and well, testing in general.
If you are interested in helping with testing/fixing, some of the code
that is in lesser used corners needs the most attention:
* manage_dhcp/manage_dns for both ISC/named and dnsmasq
* power management (?) which has had some cleanup lately
I still have yet to redo replicate, so no point in testing that just
yet. Most other things should be fair game.
If someone wants to go ahead and add the "-s sha" stuff to the
createrepo calls so working with Fedora 11/12 from EL-4/5 works
*without* installing python-hashlib, that would be an easy one. I'll
knock it out eventually if no one else does this week.
Getting the advanced formatting report commands to work would be nice,
but may take an overhaul, I don't think I was kind to the present
implementation when doing the XMLRPC based CLI. I think it would be
nice if these could also be generated in the web app (with URLs that
were easily formed to generate them) -- but no major item of
importance. Would also be nice if "cobbler status" worked via the
webapp, though PV and I were talking about potential overhaul some today
-- that might wait for 2.1
Anything else? Comments? Questions?
If you are currently working on something, plan on being finished up and
ready for testing in the next 2 weeks. Unfinished things are fine, but
this means we'll be putting them on a branch.
Since 2.0 was the big refactor/cleanup to make contributions easier for
everyone, I suspect future releases will be able to come out at greater
frequency, and will also be more focused around individual usable items
-- like the deployment features, or maybe network objects, depending on
interest.
(Sidenote -- Debian stuff seems to be ongoing on IRC but I've heard
little actual details. Please post and link to your repos with what
you are doing. Thanks! I would like to have this to be a major
theme of 2.1 (most likely) though it will be entirely fueled by your
contributions. By major theme I mean get it completely done. Koan
support, import, repo support, etc. Let's make it good, and do share
what you have so far. If it's not done by then, I don't want a
half-finished implementation in a stable codebase, and we need to look
at whether it belongs in there. So, good reason to knock it out of the
park once and for all.)
--Michael
Show replies by date