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

[Daniel Henrique Barboza]

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.

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. 

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