1
0
-1
Is only command-executor communicating with VNFs or also Blueprint Prosessor directly?
    CommentAdd your comment...

    1 answer

    1.  
      1
      0
      -1

      Samuli Silvius There are various ways the CBA Package within action can be model to communicate to the VNF depending on the capabilities of the VNF.


      Modeling Concepts#rest

      Another approach is  REST > ODL > Device


      1. Samuli Silvius

        Script Executor → From Blueprint Processor POD

        Remove Python Executor → From Command Executor POD

        Remote Ansible Executor → From some AWX POD or external AWX server somehow. Not described...

        Is this correct?

        And how about Netconf? I assume directly from Blueprint Processor POD? Is this the same as Script Executor?


      2. Alexis de Talhouët

        Script Executor → From Blueprint Processor POD

        Remove Python Executor → From Command Executor POD

        Remote Ansible Executor → From some AWX POD or external AWX server somehow. Not described...

        Is this correct?

        Yes, that's the idea. Python and Ansible already supports a bunch of libraries to communicate with Network Element.

        And how about Netconf? I assume directly from Blueprint Processor POD? Is this the same as Script Executor?

        They are many ways to achieve NetConf connection to NE:

        • through Script Executor (Jython or Kotlin, leveraging CDS's NetConf client)
        • through Remote Python Executor, using libraries such as ncclient, netmiko, etc...
        • through Ansible / Ansible Playbook, leveraging netconf_config module for instance.
      CommentAdd your comment...