PTL: Seshu Kumar Mudiganti 

J release highlights/accomplishments ():

• First version of Topology & Inventory (TEIV) registry & exposure service contributed and released
  • Wiki – Topology & Inventory (TEIV)
  • O-RAN SC SMO TEIV Technical Coordinator – John Keeney 
  • Gerrit Repository – https://gerrit.o-ran-sc.org/r/admin/repos/smo/teiv
  • Documentation – https://docs.o-ran-sc.org/projects/o-ran-sc-smo-teiv
  • Nexus: https://nexus.o-ran-sc.org/#nexus-search;quick~smo-teiv
  • Sonar: https://sonarcloud.io/project/overview?id=smo-teiv
  • JIRA 

    • Jira
      server ORAN Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-146

    • Jira
      server ORAN Jira serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-144

    • Jira
      server ORAN Jira serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-145

J release source code, container images and deployment instructions (and status)

J release source code for SMO can be found in the following repositories

• TEIV repository
• O1 repository
• O1/VES repository
• O2 repository
  • For the O2 Interface OpenStack Tacker project (External repository)
    • Source code: https://opendev.org/openstack/tacker
    • Code coverage: Coverage report (Latest OpenStack verification results)
    • Functional test log for Fault Management: Zuul-logs

The container images for SMO can be found on the Nexus server, where applicable.
The container images for OpenStack Tacker can be found in OpenStack Kolla repository.

• https://quay.io/repository/openstack.kolla/tacker-server
• https://quay.io/repository/openstack.kolla/tacker-conductor

The OpenStack Tacker container can be started with the steps in the following documentation.

• https://docs.openstack.org/tacker/latest/install/kolla.html
• https://docs.openstack.org/kolla-ansible/latest/user/quickstart.html

The installation instructions for SMO can be found in the documentation page here.

Status

The status of the SMO project is tracked using JIRA epic items. For the latest status refer to the items below.

• Jira
  server ORAN Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-146

• Jira
  server ORAN Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-145

• Jira
  server ORAN Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-144

• Jira
  server ORAN Jira columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 5ec52304-b77c-3ce7-af6a-112cb13e6008 key SMO-135