Open Stack

For example, I have SR-IOV PF with four ports (P_i), two of them are
connected to one switch (SW_1) and other two to another (SW_2). I
would like to get VFs from distinct ports connected to distinct
switches (more details can be found in spec [1]), how it can be
modeled with nested resource providers?

Several possible solutions I see:

1)
                          --- compute node -----
                     ----/     /          \     \------
               -----/         /            \            \-------
              /              /              \                   \
         SR-IOV PF         SR-IOV PF         SR-IOV PF         SR-IOV PF
       (traits:P1,SW1)  (traits:P2,SW1)   (traits:P3,SW2)    (traits:P4,SW2)
            :                 :                 :                 :
           / \               / \               / \               / \
          /   \             /   \             /   \             /   \
       VF1    VF2        VF3    VF4        VF5    VF6        VF7    VF8


2)
                        compute node
                      /              \
                    /                  \
           SR-IOV PF                   SR-IOV PF
          (traits:SW1)                (traits:SW2)
            /      \                    /      \
           /        \                  /        \
      SR-IOV PF     SR-IOV PF     SR-IOV PF     SR-IOV PF
     (traits:P1)   (traits:P2)   (traits:P3)   (traits:P4)
         :             :             :             :
        / \           / \           / \           / \
       /   \         /   \         /   \         /   \
    VF1    VF2    VF3    VF4    VF5    VF6    VF7    VF8


3) Use tags for inventories, so the problem can be solved without complex
structures.

Are the described options applicable or there are other to solve the issue?

[1] https://review.openstack.org/#/c/182242/


-- 
Thanks,

Andrey Volkov,
Software Engineer, Mirantis, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170905/ad51aa0c/attachment.html>