An idea behind AVCN is to introduce an use-case in PNF-Simulator (overall NF-Simulator), which supports ORAN defined O1 interface (reporting of NF events to Service Management Orchestrators).
Within the use-case, it is expected, that an NF configuration change, happening due to multiple reasons (network mechanism triggered change - e.g. discovery of neighbours) is reported to the network management system, using ONAP`s VES REST events.
The simulator is expected to cover planned NF behaviour - receive the config change via a NetConf protocol, and report that change (and potentially other related changes) to the network management system using ONAP`s VES event.

COS:

• introduce AVCN part
• adopt onap/org.onap.integration.simulators.netopeer and onap/org.onap.integration.simulators.netconfsimulator to newest netopeer images https://github.com/CESNET/Netopeer2/
• rename repo pnf-simulator to nf-simulator: /repos/integration/simulators/pnf-simulator to /repos/integration/simulators/nf-simulator
• due to fact that there are issues during Jenkins builds and new component is introduced, split repo to:
  • integration/simulators/nf-simulator/netconf-server
  • integration/simulators/nf-simulator/pm-https-server
  • integration/simulators/nf-simulator/bes-client
  • integration/simulators/nf-simulator/avcn-manger
• Update integration docs/confluence about availability of such set of simulators that can be uses in day N use cases
• Prepare example helm charts and blueprint using which those simulators can be orchestrated as CNF-s