zOS support

It would be great if Feilong supported zOS lifecycle, where zOS is 2nd level zVM guest:

1. IPL zOS,
2. Stop zOS
3. invoke MVS commands (D IPLINFO, ...) and capture their response

My understanding is that Feilong runs a zlinux under zVM, what it is resource consumption of this image (average CPU utilization, Memory, Disk). In my case I would ideally avoid extra VM with zlinux to reduce memory and CPU resources because I'm running zVM under zD&T (zPDT)

I already have a POC version implemented off the Feilong project here is an architecture diagram:

• In my case I can have many instances of zVM each representing a parallel sysplex, that could be provisioned by a developer, therefore I prefer to avoid zlinux on each zVM and instead have the majority of components off the zVM.
• Ideally, I would like to combine LXC and observer into a single VM to minimize overhead of infrastructure
• LXC is used to send commands such as: Q NAMES, CP SEND CP ZOS1 CP IPL ..., CP SEND CP ZOS1 VINPUT VMSG D IPLINFO, CP SET OBSERVER ...
• OBSERVER - IUCV2Socket - capture console messages sent from zOS vms and forward them via a network socket to a CLI that runs on linux, POC is based on
  • Managing z/OS guests on z/VM with IBM Operations Manager for z/VM interesting article describing how to interact with zOS master console using CP VINPUT VMSG xxx commands and how to capture responses using CP SET OBSERVER ...
  • Sample REXX program to listen on a TCPIP socket
  • Sample REXX program to trap IUCV messages using WAKEUP

No files, tests, or entry points are named; start by reviewing the linked POC architecture and the existing Feilong z/VM lifecycle implementation. Define the integration boundaries before changing code. Done means supporting z/OS IPL and stop operations, sending MVS commands, and capturing their responses without requiring a separate zLinux VM.