I've discussed this a little with Ian off list, but relating to:
https://fedoraproject.org/wiki/Features/Condor_Cloud
Condor Cloud aims at setting up a bunch of Fedora nodes to act as a
mini-cloud managed via the Condor grid infrastructure. So the natural
question was... Why not use oVirt Node for this rather than a full
Fedora OS install?
Pulling condor-cloud and condor RPMs into the core oVirt Node will
significantly expand the size of the node and make it more specific
purpose, so we thought it made more sense to add this functionality to
oVirt Node as a 'plugin' added via edit-livecd to inject it into the ISO
offline.
So, the flow would look like this:
condor-cloud RPM has a script that is bundled with it that is a
edit-livecd kickstart, meant to be applied to the stock Fedora oVirt
Node that adds Condor and whatever else is needed.
So if someone wants to use Condor with oVirt Node they:
* install condor-cloud
* download ovirt-node ISO
* on a F16 host run a command like: edit-node condor-node-plugin.ks
* edit-node calls edit-livecd with condor-node-plugin.ks
* condor rpm is installed along with deps from fedora repos
* Firewall is changed, and whatever else is needed for Condor Node
* Condor Node is created as a derivative ISO
* User deploys Condor Node and uses Condor Cloud just like they would
with Fedora hosts
So what we need here to make this work are:
* Condor Node kickstart that can be used by the edit-livecd tool
* Finish up creating edit-node based on edit-livecd and make Condor
Node one of the first examples of an oVirt Node plugin
Both of those items are represented on the backlog:
https://fedorahosted.org/ovirt/wiki/Backlog
Cheers,
Perry
