| View Revisions: Issue #8208 |
[ All Revisions ] [ Back to Issue ] |
| Summary |
0008208: [4.4.1] [Clause 5.5.3.24] McioInfo makes "vduId" mandatory; however, not all MCIOs may be mappable to a VNFC |
|
| Revision |
07-06-2023 10:33 by Yinan Liu |
|
| Additional Information |
By the way, if VNFM is unable to respond with a (or more) discovered MCIOs (because there was no associated vduId found), this would be a loss of information to the API consumer (NFVO, EM, etc.) because the former will never be aware of the existence of such an _unmapped_ MCIO. |
|
| Revision |
22-05-2023 15:10 by Sujeet Banerjee |
|
| Additional Information |
By the way, if VNFM is unable to respond with a (or more) discovered MCIOs (because there was no associated vduId found), this would be a loss of information to the API consumer (NFVO, EM, etc.) because the former will never be aware of the existence of such an _unmapped_ MCIO. |
