Page History

•  Trevor Lovettupdate this to bi-weekly 

Open/In-Progress

• Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-843

  - Owner Trevor: 
  1. No Change - will address when we have a schema to publish

• Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-812

   - Owner Trevor: 
  1. Partially handled in VNFRQTS-813, but more work needed and it will be delivered under this ticket

• Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-892

   - Owner Damian
  1. Needs assignment
•  

  Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-885

  - Owner Damian
  1. Submitted for review
•  

  Jira
  server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VNFRQTS-842

   - Owner Damian
  1. Resolved only having 1 listener FQDN in VNFRQTS, 813, but no mention of 3GPP.  Is more needed here?  Damian will review and report back on next meeting.

Recently Closed

1. VNFRQTS-842- Resolve 3GPP Alignment of Listener IPs

   1. Closed - Merged w/ 108418

2. VNFRQTS-813 - Rationalize VES Event Listener Spec and VNF Monitoring Requirements

   1. Closed - Merged w/ 108418

3. VNFRQTS-887

   1. Closed - Merged w/ 108418

4. VNFRQTS-885
   1. Closed - Merged w/ 108418