Jira (PUP-7618) PSON -> JSON Testing

3 views
Skip to first unread message

Stan Duffy (JIRA)

unread,
Jun 2, 2017, 6:03:03 PM6/2/17
to puppe...@googlegroups.com
Stan Duffy created an issue
 
Puppet / Task PUP-7618
PSON -> JSON Testing
Issue Type: Task Task
Assignee: Stan Duffy
Created: 2017/06/02 3:02 PM
Environment:

Puppet Agent 5

Priority: Normal Normal
Reporter: Stan Duffy

In Puppet 5 we will be switching from using PSON by default to JSON. This requires that various interactions are validated to work as we expect them to. Here are the rough notes put together but John Duarte and myself based on a meeting we had with Josh Cooper

Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                     (covered in CI)
B: fallback to pson catalog only (with binary data)         (needs beaker testing)
C: --preferred serialization format=pson on Agent           (needs beaker testing)
F: cahched cat -> Always send json with escaped characters  (needs beaker testing)
------------------------------------
 v3/4               v5                     v5
D: pson                                                     (leavrage PR upgrade testing?)
F: cahched cat -> Always send json with escaped characters  Manual
------------------------------------
v5                 v4                      v4
E: pson                                                     (expected graceful failure early)     
F: cahched cat -> Always send json with escaped characters  (ka-boom!! Acceptable?)

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Atlassian logo

Josh Cooper (JIRA)

unread,
Jun 2, 2017, 7:57:02 PM6/2/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}

Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                     (covered in CI)
B: fallback to pson catalog only (with binary data)         (needs beaker testing)
C: --preferred serialization format=pson on Agent           (needs beaker testing)
F:  cahched  cached  cat -> Always send json with escaped characters  (needs beaker testing)
------------------------------------
 v3/4               v5                     v5
D: pson                                                     (
leavrage PR covered in PE  upgrade testing ? )
F:
 cahched  cached  cat -> Always send json with escaped characters  Manual

------------------------------------
v5                 v4                      v4
E: pson                                                     (expected graceful failure early)     
F:  cahched  cached  cat -> Always send json with escaped characters  (ka-boom!! Acceptable?)
{code}

Josh Cooper (JIRA)

unread,
Jun 5, 2017, 2:41:03 AM6/5/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}
Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                     (covered in CI)
B: fallback to pson catalog only (with binary data)         (needs beaker testing)
C: --preferred serialization format=pson on Agent           (needs beaker testing)
F: cached cat -> Always send json with escaped characters  (needs beaker testing)
------------------------------------
 v3/4               v5                     v5
D: pson                                                     (covered in PE upgrade testing)
F: cached cat -> Always send json with escaped characters
  Manual   (manual)
------------------------------------
v5                 v4                      v4
E: pson                                                     (expected graceful failure early)     
F: cached cat -> Always send json with escaped characters  ( ka-boom!! Acceptable? expected graceful failure )
{code}

Kenn Hussey (JIRA)

unread,
Jun 14, 2017, 1:58:03 PM6/14/17
to puppe...@googlegroups.com
Kenn Hussey updated an issue
Change By: Kenn Hussey
Fix Version/s: PUP 5.0.0

Geoff Nichols (JIRA)

unread,
Jun 14, 2017, 1:58:12 PM6/14/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Agent 2017-06-28

Geoff Nichols (JIRA)

unread,
Jun 14, 2017, 1:58:16 PM6/14/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Story Points: 3

Josh Cooper (JIRA)

unread,
Jun 14, 2017, 5:53:02 PM6/14/17
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}
Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                    (covered in CI)
B: fallback to pson catalog only (with binary data)        (needs beaker testing)
C: --preferred serialization format=pson on Agent          (needs beaker testing)
F: cached cat -> Always send json with escaped characters  (needs beaker testing)
------------------------------------
 v3/4               v5                     v5
D: pson                                                    (covered in PE upgrade testing)
F: cached cat -> Always send  json  pson  with escaped characters  (manual)
------------------------------------
v5                 v4                      v4
E: pson                                                    (expected
 graceful failure early  downgrade to pson )     
F: cached cat -> Always send json with escaped characters  (expected graceful failure)
{code}

Josh Cooper (JIRA)

unread,
Jun 14, 2017, 5:56:02 PM6/14/17
to puppe...@googlegroups.com
Josh Cooper commented on Task PUP-7618
 
Re: PSON -> JSON Testing

Made two edits:

v3/4 agents will always send reports in pson (with cached catalog or not), since that's all they know how to do
v5 agents talking to v4 masters (in the non-cached catalog case) should downgrade to pson. But as this isn't a supported combo, the main thing is to not explode.

John Duarte (JIRA)

unread,
Jun 14, 2017, 6:06:03 PM6/14/17
to puppe...@googlegroups.com
John Duarte updated an issue
Change By: John Duarte
QA Risk Assessment: Needs Assessment Automate

Geoff Nichols (JIRA)

unread,
Jun 15, 2017, 10:53:03 PM6/15/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Release Notes: Not Needed

Stan Duffy (JIRA)

unread,
Jun 23, 2017, 7:09:02 PM6/23/17
to puppe...@googlegroups.com
Stan Duffy updated an issue
Change By: Stan Duffy
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}
Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                    (covered in CI)
B: fallback to pson catalog only (with binary data)        (needs beaker testing)
C: --preferred serialization format=pson on Agent          (needs beaker testing)  (John)
F: cached cat -> Always send json with escaped characters  (needs beaker testing)
 (John)
------------------------------------
 v3/4               v5                     v5
D: pson                                                    (covered in PE upgrade testing)
F: cached cat -> Always send pson with escaped characters  (manual)  (Stan)
------------------------------------
v5                 v4                      v4
E: pson                                                    (expected downgrade to pson)
     
  (Stan)
F: cached cat -> Always send json with escaped characters  (expected graceful failure)  (manual) (Stan)
{code}

John Duarte (JIRA)

unread,
Jun 23, 2017, 7:10:02 PM6/23/17
to puppe...@googlegroups.com
John Duarte updated an issue
Change By: John Duarte
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}
Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                    (covered in CI)
B: fallback to pson catalog only (with binary data)        (needs beaker testing)  (John) (PUP-7681)
C: --preferred serialization format=pson on Agent          (needs beaker testing) (John)
F: cached cat -> Always send json with escaped characters  (needs beaker testing) (John)
------------------------------------
 v3/4               v5                     v5
D: pson                                                    (covered in PE upgrade testing)
F: cached cat -> Always send pson with escaped characters  (manual) (Stan)
------------------------------------
v5                 v4                      v4
E: pson                                                    (expected downgrade to pson)  (Stan)
F: cached cat -> Always send json with escaped characters  (expected graceful failure) (manual) (Stan)
{code}

John Duarte (JIRA)

unread,
Jun 26, 2017, 1:03:03 PM6/26/17
to puppe...@googlegroups.com

John Duarte (JIRA)

unread,
Jun 26, 2017, 1:03:04 PM6/26/17
to puppe...@googlegroups.com
John Duarte updated an issue
In Puppet 5 we will be switching from using PSON by default to JSON.  This requires that various interactions are validated to work as we expect them to.  Here are the rough notes put together but [~john.duarte] and myself based on a meeting we had with [~josh]

{code}
Agent     <-       Server      <-      Database
      node info             
      catalog               
      file meta data        
      
Agent     ->       Server       ->      Database        
      facts                 facts
      reports               catalog
                            reports
                            
------------------------------------
 v5                 v5                     v5
A: json                                                    (covered in CI)
B: fallback to pson catalog only (with binary data)        (needs beaker testing) (John) (PUP-7681)
C: --preferred serialization format=pson on Agent          (needs beaker testing) (John)
 
 (PUP-7729)
F: cached cat -> Always send json with escaped characters  (needs beaker testing) (John)  (PUP-7730)
------------------------------------
 v3/4               v5                     v5
D: pson                                                    (covered in PE upgrade testing)
F: cached cat -> Always send pson with escaped characters  (manual) (Stan)
------------------------------------
v5                 v4                      v4
E: pson                                                    (expected downgrade to pson)  (Stan)
F: cached cat -> Always send json with escaped characters  (expected graceful failure) (manual) (Stan)
{code}

Kenn Hussey (JIRA)

unread,
Jun 28, 2017, 10:07:03 AM6/28/17
to puppe...@googlegroups.com
Kenn Hussey commented on Task PUP-7618

Stan Duffy is this done now (seeing as the release has shipped)?

Geoff Nichols (JIRA)

unread,
Jun 28, 2017, 4:20:06 PM6/28/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Agent 2017-06-28 , Agent 2017-07-12

Geoff Nichols (JIRA)

unread,
Jun 28, 2017, 4:36:03 PM6/28/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Fix Version/s: PUP 5.0.0
Fix Version/s: PUP 5.0.z

Geoff Nichols (JIRA)

unread,
Jun 28, 2017, 4:36:03 PM6/28/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Agent  2017-06-28  N+1 , Agent 2017- 07 06 - 12 28

Geoff Nichols (JIRA)

unread,
Jul 19, 2017, 1:45:03 PM7/19/17
to puppe...@googlegroups.com
Geoff Nichols assigned an issue to Unassigned
Change By: Geoff Nichols
Assignee: Stan Duffy

Geoff Nichols (JIRA)

unread,
Jul 25, 2017, 7:46:03 AM7/25/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Agent  N+1, Agent  2017-06-28 , Platform Core 2017-08-22

Geoff Nichols (JIRA)

unread,
Jul 25, 2017, 7:46:03 AM7/25/17
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Team: Agent Platform Core

John Duarte (JIRA)

unread,
Jul 31, 2017, 6:43:03 PM7/31/17
to puppe...@googlegroups.com
John Duarte assigned an issue to John Duarte
Change By: John Duarte
Assignee: John Duarte

Karen Van der Veer (JIRA)

unread,
Aug 4, 2017, 2:37:05 PM8/4/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Sprint: Agent 2017-06-28, Platform Core  2017-08-22  Grooming

Karen Van der Veer (JIRA)

unread,
Aug 9, 2017, 1:30:04 PM8/9/17
to puppe...@googlegroups.com

Hey John Duarte, WDYT should happen with this one? Is it imminent that it will be worked on?

Karen Van der Veer (JIRA)

unread,
Aug 9, 2017, 1:30:05 PM8/9/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Fix Version/s: PUP 5.0.z

Karen Van der Veer (JIRA)

unread,
Aug 9, 2017, 1:30:06 PM8/9/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Fix Version/s: PUP 5.y

Karen Van der Veer (JIRA)

unread,
Aug 9, 2017, 1:38:02 PM8/9/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Sprint: Agent 2017-06-28 , Platform Core Grooming

John Duarte (JIRA)

unread,
Aug 10, 2017, 6:29:03 PM8/10/17
to puppe...@googlegroups.com
John Duarte updated an issue
Change By: John Duarte
Sprint: Agent 2017-06-28 , Platform Core 2017-08-22

John Duarte (JIRA)

unread,
Aug 18, 2017, 12:54:02 PM8/18/17
to puppe...@googlegroups.com
John Duarte commented on Task PUP-7618

Waiting on tests associated with subtasks to be merged.

Karen Van der Veer (JIRA)

unread,
Aug 24, 2017, 1:37:09 PM8/24/17
to puppe...@googlegroups.com
Karen Van der Veer updated an issue
Change By: Karen Van der Veer
Sprint: Platform Core 2017-09-05, Agent 2017-06-28, Platform Core 2017-08-22

Karen Van der Veer (JIRA)

unread,
Aug 25, 2017, 9:31:02 PM8/25/17
to puppe...@googlegroups.com

John Duarte There have been PR reviews, not sure if they can be merged now or not. Take a look.

John Duarte (JIRA)

unread,
Aug 28, 2017, 9:45:02 AM8/28/17
to puppe...@googlegroups.com
John Duarte commented on Task PUP-7618

Karen Van der Veer, the tests associated with subtasks have not yet been merged. This ticket is pending the merge and successful CI completion of PUP-7729 and PUP-7730.

Josh Cooper (JIRA)

unread,
Jul 15, 2019, 7:50:04 PM7/15/19
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Fix Version/s: PUP 5.y
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages