The two modules use complete different syntax to achieve the same result, to create a LPAR of a certain type.
I would suggest that variable names match and the method of assigning adapters aligns with the VIO strategy, making it way more portable by not requiring unique identifiers, but instead basing it on slot ID's.
Some examples.
In ibm.power_hmc.vios:
profile_name: default
min_procs: 1
desired_procs: 4
max_procs: 8
io_slots: "21010019/none/0"
In ibm.power_hmc.powervm_lpar_instance:
prof_name: default
min_proc: 1 (proc singular instead of procs)
proc: 4
max_proc: 8 (proc singular instead of procs)
physical_io:
- UABCD.001.ABC123-P1-C1
The two modules use complete different syntax to achieve the same result, to create a LPAR of a certain type.
I would suggest that variable names match and the method of assigning adapters aligns with the VIO strategy, making it way more portable by not requiring unique identifiers, but instead basing it on slot ID's.
Some examples.
In ibm.power_hmc.vios:
In ibm.power_hmc.powervm_lpar_instance: