Ok folks,
So I'm working on adding virtualized image deployment support for koan.
What does this mean?
In cobbler, you will be able to track a library of images for kicking
off fullvirt installations from Media (read: Windows) as well as
tracking a library of virtual disk images for purposes of re-clonining
them.
At this point, I'd like to take the time to simplify koan where
possible. As 1.0 was the "major" release for cobbler, this is the time
to clean up koan a good bit.
This should all be goodness, though a bit confusing. There will be Wiki
docs on how to use all of this /if/ you need it. The primary driver of
this right now is the ovirt project, who needs it for a provisioning
library, though I think it will be nice to have a contained Windows
deployment solution for when the two must mix.
Meanwhile, there are a few things that I'd like to pull.
I'm looking at removing --no-cobbler support for doing --replace-self
without a cobbler server. Koan is robin to Cobbler's batman, and I
want to limit scope. If you aren't using cobbler, and you are using
koan, you should be using cobbler too. That should be fair enough.
If you liked that feature, it's easily replaceable with a few calls to
"grubby".
I also believe "buildiso" has successfully made the Cobbler livecd much
easier to use, so I'm looking at removing that as well. There should
be no objections to this because buildiso is so much easier to build on
all platforms and supports a much wider pool of hardware.
Comments welcome.
--Michael
Show replies by date