Page Comparison

...

Status and Stucks
- Current POMBA Dublin Stories (Logging Project) -
  - Dublin Pomba Stories
- Current Code Inspections
  - https://gerrit.onap.org/r/#/q/status:open+pomba
- POMBA 6 hour healthcheck (full 200G CD deployment) - http://kibana.onap.info:5601/app/kibana#/dashboard/AWAtvpS63NTXK5mX2kuS
- General Status
  - Dublin
    - Stories in progress:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-958
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-957
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key SDNC-637
    - Stories to be formally verified before closure:
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-778
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-763
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key SDNC-475
        : For network resource only and should be split into Network Discovery and ND context builder.
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-779
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-404
    - Stories closed since last meeting:
    - 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
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-976995
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-975994
      Bugs in progress:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-852993
      - Jira Legacy
        server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-988
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-967987
      - Jira Legacy
        server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-966986
    - Bugs in progress:
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-916852
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-965
      Bugs to be verified:
      - Jira Legacy
        showSummary true975
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-807976
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-803
        (Verify in OOM fails, assigned back to design)
        967
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-808966
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-981
      Bugs closed off since last meeting:
      - 916
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-933965
    - Bugs to be verified:
      - Jira Legacy
        showSummary true
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-893807
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-881803
        (Verify in OOM fails, assigned back to design)
      - Jira Legacy
        server System Jira
        columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-917808
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-931981
    - Bugs closed off since last meeting:
Technical Discussion
- Consider demo schedules
  - J. Ram Balasubramanian will forecast demos as development progresses
    - ~~Data Dictionary & Network Discovery- Dec 20~~
      - ~~Done~~
    - L2 Network data (Today!)
      - See slides
    - Additional enhancement - March 21st
      - additional resources and rules
      - potentially other enhancements
- Note we have discovered a number of discrepancies between the model definition in the wiki and the code. We are now raising bugs on specific issues found and will resolve as appropriate.
- OOM submissions
  - Steps to ensure PODS are healthy
    - Before checkins should do a local Robot health check. If this is not clear, documentation needs to be updated.
      - action Yong
  - This was guidance from PTL and also good practice.
Making the PTL Happy
- Casablanca
  - Release notes being prepared.
    - Still seems to be open.
  - Data router version was upped. So, POMBA needed to update its version. This was integrated.
    - There was a bug and the A&AI team fixed it. Integration team tested the fix, but perhaps did not test POMBA
      - J. Ram will quickly test.
      - Michael O. did test already that the POD comes up and passes health check.
- Dublin
  - Should look at milestones and ensure we are in good shape.
    - Feature commitment Jan 17 → pushed one week. Jan 24th. (M1)
      - Prudence is supporting Michael for this activity.
      - https://wiki.onap.org/display/DW/Logging+Dublin+Deliverables+for+Planning+Milestone+Checklist+Template
      - https://wiki.onap.org/display/DW/Logging+Dublin+M1+Release+Planning
    - Functionality freeze Feb 21
      - Any new APIs are supposed have draft definition, but this doesn't really apply to us
      - Michael has filled in the templates for POMBA. Should be good to go.
    - API freeze is March 14th (or has this slipped?)
Demo
- Slides
- Dublin Test lab configuration
- POMBA audit is trigger
  - Currently via service instance id, model id and model invariant id
    - This enables some good validation
  - This information can be hard to find in cases. An audit trigger based on information a more typical user has should be considered
    - Both could be supported
    - Brian thinks he previously raised something on this. If not, Sharon will add something to the backlog to track.
      - Jira Legacy
        server System Jira
        serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
        key LOG-983
- The demo data is roughly based on vfw, but modified to ensure we have violations to show
- Integration team can create their own rules. The steps are defined
  - Validation Service
  - Action Yong to improve page or create a new one with better steps.
- Openstack keystone needs to be version 3, or shortly no one will be able to use it
  - Network Discovery is using v3, so we are ok
- Currently Openstack coordinates are part of the helm chart. There is a way the URL information can be discovered
  - Action Sharon to add something to the backlog for this
    - Jira Legacy
      server System Jira
      serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
      key SDNC-663
- Openstack passwords are obfuscated.
- Ideally, it would be good to network discover using meta-data
  - This information gets associated to the VM
  - Openstack does support filtering on field values. Depending on how the meta data is stored in openstack, this would be possible to implement.
    - Currently network discovery is triggered out resource type and id.
  - There is a heatstack to metdata association that is critical
  - More analysis of this is required.

Versions Compared

Old Version 1

New Version 2

Key