[Kimchi-devel] [RFC] The new ginger-basic plugin

Tue Aug 11 17:36:11 UTC 2015

On 08/11/2015 02:17 PM, Aline Manera wrote:
>
>
> On 11/08/2015 13:27, Kevin Zander wrote:
>> On Tue, 2015-08-11 at 11:47 -0300, Aline Manera wrote:
>>> Hi all,
>>>
>>> As we have agreed on moving the Kimchi Host tab to Ginger community 
>>> and creating a new plugin (ginger-basic), I want to list 
>>> step-by-step what we need to do *on Kimchi side*.
>>>
>>> 1) Will we call this new plugin as ginger-basic? Any other suggestion?
>>
>> I think keeping it as ginger is better. ginger-basic sounds like 
>> there's ginger-advanced (or similar), when there really isn't 
>> anything like that. What we have is just additional functionality 
>> based on your OS flavor. So keeping ginger as the plugin name, to me, 
>> is the easiest. Then all it takes is looking up your flavor: 
>> ginger-[ppc|z|pickled]
>
> The final goal of ginger-basic is to handle only host basic 
> information, host statistics and debug reports.
> Those features were identified as common between Kimchi and Ginger so 
> the need of a new plugin (ginger-basic).
> You can check the other thread where we decided to do that in: 
> http://lists.ovirt.org/pipermail/kimchi-devel/2015-August/011173.html
>
> The idea of this email in only clarify what we need to do as we've 
> already had an agreement in the concept.
>
> About the plugin name, you can suggest other one which may be better 
> understood than ginger-basic - as you said it sounds to there is a 
> ginger-advanced.

'ginger-basic' is just a name. We can rename it to ginger-hostinfo, 
ginger-basicinfo and the plug-in that will add the current Ginger 
features can be named 'ginger-adm', 'ginger-advanced' ....

We can discuss how each plug-in will be named (a discussion which 
belongs to ginger-dev-list at nongnu.org ) but, in my opinion, agreeing 
with the design is more important ATM.

>
>>
>>>
>>> 2) Create the new plugin structure into wok branch, ie, create a 
>>> directory named ginger-basic (?) and all it is needed to launch it 
>>> as a wok plugin, including building and packaging details.
>>>     In this first moment, the entire Host tab will be part of the 
>>> ginger-basic - just to move the discussion as soon as possible to 
>>> Ginger community.
>>>
>>> 3) Add ginger-basic plugin as a Kimchi dependency.
>>>
>>> Once we have those items done, I will create a new repository for 
>>> ginger-basic under kimchi-project organization in Github.
>>> After that, the discussion *will be moved to Ginger community*, ie, 
>>> all patches and discussion must be sent to the Ginger mailing list 
>>> (https://lists.nongnu.org/mailman/listinfo/ginger-dev-list)
>>>
>>> I have sent to Ginger community the next steps to be done there. 
>>> Please, check: "[Ginger-dev-list] [RFC] Inheriting Kimchi's Host tab"
>>>
>>> Let me know what you think about that.
>>>
>>> Regards,
>>> Aline Manera
>>>
>>>
>>> _______________________________________________
>>> Kimchi-devel mailing list
>>> Kimchi-devel at ovirt.org  <mailto:Kimchi-devel at ovirt.org>
>>> http://lists.ovirt.org/mailman/listinfo/kimchi-devel
>
>
>
> _______________________________________________
> Kimchi-devel mailing list
> Kimchi-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/kimchi-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/kimchi-devel/attachments/20150811/875d359a/attachment.html>