...
| Status | Choose One: DRAFT | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Submitter | Abdel Rabi (Vodafone) | ||||||||
| Contributors | Bryan Whittle (iconectiv) | ||||||||
| Proposed Release | Dublin Release | ||||||||
| JIRA Ticket(s) |
|
...
I think a third set of tags should also be provided providing some indication of what the VNF is. E.g. if the VNF is part of the mobile network then it should be identified as one (or more) 3GPP functional entities (PDN-GW, UPF, etc., etc.) this would enable the operator to automatically identify what it does and enable the first pass automatic test of the functionality. (so vendor pushes a new MME version to the operator portal, automation sees the new update, identifies the VNF, we know what it is from the tag and what we (as an operator want it to do – we do not necessarily want to use all of the 3GPP functionality), we can then create the correct test environment (what traffic sources and destinations, signalling etc. do we use) and then run through an automated test script covering all the acceptance tests (all the required signalling messages, logging output, traffic etc.) and only if this all passes is the operator alerted that an updated VNF is ready for rollout. Any failure results in a report to the operator and also to the vendor. This process should be fully automated – no personal involvement once it is set up.
References
Bryan Whittle (iconectiv)
Links to any additional resources referenced in or related to this proposal.
...