Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

View file
namepnc-init-payload-1-r9.json
height250
View file
namepnc-init-payload-2-r9.json
height250

Image Added


Q&A:

  1. What is the difference between ACTN simulator docker image v1.0.5 and vlatest? Why v1.0.5 was recommended on R8 ACTN Simulator Wiki? Is ACTN simulator backward compatible, and still support transport slicing usecase?                                                  Ans：A little background here, our team started the ACTN simulator project for "transport slice" usecase in ONAP R8/Guilin release. the ACTN simulator was designed to simulate the underlay physical network controller (L1) and serves the ONAP SDNC controller through IETF-ACTN-defined northbound interface. Later on, we added support to "cloud-lease-line" usecase as well. So, functionality-wise, it will keep supporting both "transport-slicing" and "cloud-lease-line" use cases as it advances. But, there is a problem. ACTN simulator is by nature a IETF ACTN standard advocator, and its API strictly follows the standard. In other words. whenever IETF ACTN updates the YANG model, ACTN simulator updates its own API to reflect these changes in due time. Unfortunately, this conflicts with ONAP development paradigm. Therefore, we recommend you stick with v1.0.5 and R8/Guilin ONAP if you want to test "transport-slicing", and using vlatest and R9/Istanbul for "cloud-lease-line". For those who're interested in testing "transport slicing" using latest ACTN simulator and latest ONAP. I suggest you look into SDNC DGs and update SDNC DG's RESTful calling, or contact our ONAP-SDNC expert hesam.rahimi@huawei.com.