Page Comparison

...

1. Policy logic loading Ramesh Murugan Iyer 
   1. Consider putting the policy_type_impl and policy_type_impl_ref fields in as metadata fields
   2. Please add the new API calls to the page
   3. Please analyse if and how much the size of policies will increase
   4. Please update the wiki page with your findings and if required, please  report back oat next week's meeting
2. Liam Fallon Clean up the documentation JIRAs
3. Liam Fallon Check the package-lock.json file in the policy/gui repo (Thanks Daniel Hanrahan , see JIRA 

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3806

   )
4. Liam Fallon Rename the High Availability JIRA JIRA 

   Jira Legacy
   server System 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 4733707d-2057-3a0f-ae5e-4fd8aff50176 key POLICY-3809

   to include a mention of database high availability (Done)
5. Welcome Isaac Adorno to the project
6. Ramesh Murugan Iyer is the point of contact for the PMSH use case for Jorge Hernandez 
7. Saul Gill will present the DB High Availability work at the next meeting
8. DCAE plan to discontinue deployments using Cloudify in this release and will use K8S deployment only. This has impacts on the Policy Framework. Liam Fallon to request a session with Vijay Kumar and the Policy Framework committers to discuss this.
9. The CLAMP GUI code is currently duplicated in policy/clamp and policy/gui, the aim is to remove the GUI code from the policy/clamp repo if we have time in this release.

...