ginger-dev-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ginger-dev-list] Ginger-z for system z?


From: Chandra Shehkhar Reddy Potula
Subject: Re: [Ginger-dev-list] Ginger-z for system z?
Date: Wed, 2 Sep 2015 12:04:24 +0530
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0



On 08/26/2015 06:24 PM, Daniel Henrique Barboza wrote:
I am not sure if we had this discussion in the Kimchi ML, but Ginger-z is something that I consider 'inevitable' due to the amount of System Z exclusive features that would be hosted in multi-arch Ginger.

However I don't think this is time to worry about this separation. First we will officially move to WoK while fixing bugs, API docs and so on. Then we'll absorb some Kimchi features to create the ginger-base plug-in. Then we can think about splitting Ginger into platform specific parts.

For Sept 30 release I am totally agree with you on what you said above. But also if possible, my proposal is even to separate existing platform specific code from ginger to make it clean.
That doesn't mean that you can't contribute Z code now. You can. The separation will be a cleaner way for a user to get only the specific features, but Ginger can handle Z only features today. 
Slight deviation here from my side on this topic. Let us start with clean slate on platform specific feature we are planning for z by having the following benefits.
1. As you mentioned above, having clean way by not putting the platform specific code on platform where it does not make sense.
2. No additional efforts required again to separate them after a while.
3. Flexibility in patch updates ie end user can only pick up the plugin code updates which are required for his environment.

On 08/26/2015 07:36 AM, Harshal Patil wrote:
Hi,
 
Ginger being a host management plugin for the Wok framework is responsible for general host system management. What happens when you have some architecture specific things to handle when managing the system? 
 
For example, in System z there is a disk type called DASD. This type of device needs to be partitioned and formatted slightly differently and with different tools (not with fdisk). From high level it looks like the DASD partitioning could go in a ginger plugin specifically written for system Z, ginger-z if you will.  Similarly, when dealing with networking and storage we need to interact with something called Channel Sub System (CSS), again a good reason for the creation of ginger-z. 
 
What do you guys say?
 
Harshal




reply via email to

[Prev in Thread] Current Thread [Next in Thread]