Feilong is a open source z/VM cloud connector project under the Open Mainframe Project umbrella that will accelerate the z/VM adoption, extending its ecosystem and its user experience. It provides a set of APIs to operate z/VM including guest, image, network, volume etc.
We once deployed Feilong z/VM without the IUCV authorizations by accident, and it was still comunicating fine with SMAPI, so I suspect it's the schema that is wrong, while the explanations in step 3 of 3.1.1 are correct.
How does Failong communicate with SMAPI by the way? I suspect with TCP/IP sockets?
https://cloudlib4zvm.readthedocs.io/en/latest/architecture.html#internal-architecture shows "IUCV" as the way the Feilong connector and SMAPI communicate.
According to "Update BYOL definition about IUCV" section on https://cloudlib4zvm.readthedocs.io/en/latest/quickstart.html#setup-for-z-vm-sdk-daemon, IUCV is rather used for the communication between Feilong and the deployed guests.
Which one is correct?
We once deployed Feilong z/VM without the IUCV authorizations by accident, and it was still comunicating fine with SMAPI, so I suspect it's the schema that is wrong, while the explanations in step 3 of 3.1.1 are correct.
How does Failong communicate with SMAPI by the way? I suspect with TCP/IP sockets?
Or is this an option that can be set somewhere?