use NICDEF statements as replacement for vswitch grant and vlan tag

[coolkil]

In current implementation the use of the NICDEF directory statement appears limited.

NICDEF could also be used for connections to vswitches and to set the correct VLAN tag.

This would add the following additional paramaters to the POST /guests/{userid}/nic:
vswitch_name
vlan_id_list
porttype: TRUNK|ACCESS

But will make the following api calls redundant:

Grant user to vswitch
Set user VLANID to vswitch

[jichenjc (jichenjc)]

you are saying those 2 are not needed?

Grant user to vswitch
Set user VLANID to vswitch

sorry I am not fully understand this , can you provide some API call result and additional info here?

[coolkil (coolkil)]

When using the 7.4.15. Create Guest nic RESTAPI the result is an NICDEF definition in the dirmaint user direct

the exact result is like this
NICDEF 1000 TYPE QDIO DEVICES 3

However the NICDEF statements can also be used to replace the grant vswitch and couple commands see:
https://www.ibm.com/support/knowledgecenter/en/SSB27U_7.1.0/com.ibm.zvm.v710.hcpa5/dnicdef.htm

If the end result of the 7.4.15. Create Guest nic RESTAPI can be changed to something like the following:
NICDEF 1000 TYPE QDIO LAN SYSTEM VSW1 PORTTYPE ACCESS VLAN 100

This would have the result of coupling a virtual nic with vdev 1000 to the vsw1 vswitch and have an access port in vlan 100

For the same result in the current setup we need to do three API calls:
Create a Nic using 7.4.15. Create Guest nic
Grant the user to a vswitch using 7.7.4. Grant user to vswitch
And set a vlanID using 7.7.6. Set user VLANID to vswitch

I hope this clears it up a bit

[jichenjc (jichenjc)]

ok, now I understand this , so you want to combine those 3 calls you mentioned above to one call to avoid some effort? so it's API granularity question..

[coolkil (coolkil)]

basically but it reduces complexity and centralizes the virtual network interface definitions.

[jichenjc (jichenjc)]

let me see what I can do on this ...