Submitting Kimchi project as an oVirt incubator project (V2)

[Adam Litke]

On Tue, Sep 10, 2013 at 12:58:49PM -0400, Mike Burns wrote:
> On 09/10/2013 12:50 PM, Dave Neary wrote:
> >Hi,
> >
> >On 09/10/2013 05:23 PM, Adam Litke wrote:
> >>It has been some time since we last discussed incubating Kimchi into
> >>oVirt so I'd like to rekindle the discussion.  It seems like there has
> >>been general agreement that the two projects are complimentary.  What
> >>are the next steps?  Does the board require more information to make a
> >>decision?  Is there any work that needs to be done before the board can
> >>vote?
> >
> >I think Kimchi would be a great addition to the family, it fills out the
> >single host management need well. I'm all in favour.
> >
> >Regards,
> >Dave.
> >
> 
> +1 from me as well (though I'm not a board member).
> 
> We're already planning on it being incorporated with oVirt Node.
> It's a proposed feature for the 3.1 release of Node [1].
> 
> [1] http://www.ovirt.org/Node_3.1_release-management

Wow, you guys move fast :)  I played around with building a node that
contains the kimchi rpm.  Main initial issue is that we are not storing
dynamic state in a persisted location.  

Please let me know what else I can do to make kimchi a better ovirt-node
resident.  I read the plugins page and found that some work may be
needed in the spec file to make kimchi installable as a software
collection (/opt/kimchi).

-- 
Adam Litke <agl at us.ibm.com>
IBM Linux Technology Center