Versions Compared

Key

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

...

  • Status and Stucks
    • Current POMBA Dublin Stories (Logging Project) -

    • Current Code Inspections

    • POMBA hourly healthcheck (CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
    • General Status

      • Dublin
        • Tasks to be closed off (just a technicality):
        • Stories in progress: 
          • Attribute comparison rule: PNF

          • Attribute comparison rule: Network
          • SDNC-637 - network discovery + context builder work
          • May be missing ONAP stories for some current work
            • Action Sharon.
        • Stories to be formally verified before closure:
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-778
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-763
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keySDNC-475
            : For network resource only and should be split into Network Discovery and ND context builder.
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-779
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-404
        • Stories closed since last meeting:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-768
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-765
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-762
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-938
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-937
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-764
        • Bugs to enter:
          • Latest security scan results show ~9 medium issues that should be recorded (but aren't severe enough to merit immediate work).
        • Bugs entered in last week:
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-967
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-966
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-965
        • Bugs in progress:
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-852
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-916
        • Bugs to be verified:
          • Jira Legacy
            showSummarytrue
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-807
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-803
             (Verify in OOM fails, assigned back to design)
          • Jira Legacy
            serverSystem Jira
            columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-808
          • Jira Legacy
            serverSystem Jira
            serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
            keyLOG-917
        • Bugs closed off since last meeting:

  • Technical Discussion
    • Cross context builder dependencies, documented
    • Note we need to be careful about breaking POMBA when in the middle of incremental updates, where OOM isn't yet done.
      • Pulling OOM back into the project will fix this. This is currently not planned, and requires resources from OOM project to do this, so defer.
      • both master and any MR
      • Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyLOG-950
      • Sharon to create task for this for El Alto backlog.
      • Jira Legacy
        serverSystem Jira
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyLOG-971
    • Chesla has been adding content to the backlog.
      • Good to have a look. (Sharon to look)
      • Using the tag 'POMBA'?  Yes.
      • Note:  Architecture driven versus Use Case driven
        • Map the two?
    • Organizing Models and Swaggers between releases
      • Summary table
        • POMBA Releases
          • Note technically there was Swagger for the network discovery API in Casablanca, but it could not be used out of the box and has changed so much, we decided to remove it.
      • Basic navigation should take us to current. Need to verify this
        • Close for now
    • Consider demo schedules
      • J. Ram Balasubramanian will forecast demos as development progresses
        • Data Dictionary & Network Discovery-  Dec 20
          • Done
        • L2 Network data
          • Let's demo with some rules.
          • If we want validation run on new data, then Feb 21st makes more sense
        •  Additional enhancement - March 21st
    • Should ping the automation team on POMBA usage
      • Chesla to ping Brian.
        • Makes more sense when we can demo some additional openstack content (we can currently demo VM info)
        • Invite to next week's demo.
        • Can we run in integration lab to get some data?  Even if just saved and not live?
          • We did this at one point in Casablanca.
  • Making the PTL Happy