ZAPI-781: Pass server NIC tag information to NAPI


Fixed: A fix for this issue is checked into the tree and tested.
(Resolution Date: 2017-06-02T18:34:57.000Z)

Fix Versions

2017-06-08 SUDAN SURPRISE (Release Date: 2017-06-08)

Related Issues

Related Links


RFD 43 is adding support for network pools that contain networks with different NIC tags. In order to help NAPI know which of the networks in a pool are safe to provision addresses from, NAPI will need to be informed of what NIC tags are present on the server that the NIC will be on. When NICs are created, VMAPI will pass along the list of tags via the nic_tags_available field. Additionally, VMAPI will need to pass along the full list of NIC tags that a network pool spans, versus just one of them. DAPI-340 is adding a new field, nic_tag_requirements, that VMAPI will be able to provide.


Comment by Cody Mello
Created at 2017-05-19T18:17:11.000Z
To test these changes, I stood up a COAL HN and a CN in vmware on my laptop, and installed an updated CNAPI, VMAPI, and NAPI. I then assigned the NIC tag external2 to the second CN, and created an external2 network for that NIC tag, plus an external network pool that contained both the external and external2 networks. I then attempted the following provisions:

Comment by Bot Bot [X]
Created at 2017-06-02T17:48:12.000Z

sdc-vmapi commit 65a88b2 (branch master, by Cody Peter Mello)

ZAPI-781 Pass server NIC tag information to NAPI
    Reviewed by: Marsell Kukuljevic <>
    Reviewed by: Josh Wilsdon <>
    Approved by: Josh Wilsdon <>