Jira (PDB-1450) Add deactivated node timestamp to wire format

[Ryan Senior (JIRA)]

Ryan Senior created an issue

PuppetDB / PDB-1450 Add deactivated node timestamp to wire format Issue Type: New Feature Assignee: Unassigned Created: 2015/04/23 10:33 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Ryan Senior Currently the deactivated node field is just a boolean. This doesn't work well in an HA/Replicated world. Instead if we include a timestamp (from the puppet master), so the date can be replicated. Add Comment

This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)

[Ryan Senior (JIRA)]

Ryan Senior updated an issue

PuppetDB / PDB-1450 Add deactivated node timestamp to wire format

Change By: Ryan Senior Sprint: PuppetDB 2015-05-06

Add Comment

[Wyatt Alt (JIRA)]

Wyatt Alt updated an issue

PuppetDB / PDB-1450 Add deactivated node timestamp to wire format

Change By: Wyatt Alt Story Points: 3

Add Comment

[Russell Mull (JIRA)]

Russell Mull commented on PDB-1450

Re: Add deactivated node timestamp to wire format A maybe good deactivation plan, from a discussion with Ryan Senior: We should think of three states: Decomissioning is done by the user, and has a producer_timestamp. It commutes with other commands. Deactivation is triggered internally. Deletion is also triggered internally. Decomissioning commands need to be replicated A good place for this may be in the /nodes endpoint Let the user optionally query for decommissioned nodes When pulling from a remote PDB, look at the producer_timestamp on each record. If, according the the producer_timestamp and your local clock and deactivation/deletion rules this record would be deleted, don't pull it over.

Add Comment

[Russell Mull (JIRA)]

Russell Mull commented on PDB-1450

Re: Add deactivated node timestamp to wire format

Further discussion: The deactivated status DOES need to be replicated. Consider this case: X and Y have the same active node. Partition the network Y receives an update Y's TTL expires, auto-deactivating a node Heal the partition Sync, but X's TTL hasn't yet expired In this case, X should get the updated state and keep the node active, locally.

Add Comment

[Russell Mull (JIRA)]

Russell Mull commented on PDB-1450

Re: Add deactivated node timestamp to wire format

Here's the plan: User-deactivated nodes (via the puppet deactivate command) will continue to be called 'deactivated', for consistency. Automatically deactivated nodes will be called 'expired'. add a boolean expired column to the certnames table update existing code that checks if a node is deactivated to also check if it's expired. When processing the 'deactivate node' command for a certname that doesn't exist, create a new entry instead of ignoring it When pulling data as part of sync include deactivated and expired records in each summary query only pull over records that would not be expired locally Allow users to include deactivated and expired records in query results at least for the factsets, catalogs, reports, and nodes endpoints ...but hopefully in a generic way for all endpoints Add the 'nodes' endpoint to the sync, for pulling over deactivation status Include the node's deactivation time in the summary query

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-1450

Make automatic deactivation work with sync Change By: Russell Mull Summary: Add deactivated node timestamp to wire format Make automatic deactivation work with sync

Add Comment

[Russell Mull (JIRA)]

Russell Mull assigned an issue to Russell Mull

PuppetDB / PDB-1450 Make automatic deactivation work with sync

Change By: Russell Mull Assignee: Russell Mull

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-1450

Make automatic expiration work with sync Change By: Russell Mull Summary: Make automatic  deactivation  expiration  work with sync

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Russell Mull

Currently the deactivated node field is just a boolean. This doesn't work well in an HA/Replicated world. Instead if we include a timestamp Automatic expiration  ( from the puppet master), so the date can be replicated. née

Add Comment

[Russell Mull (JIRA)]

Russell Mull updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Russell Mull

Automatic Our current node  expiration  system  (née  automatic deactivation) is problematic when synchronizing PDBs with each other, since it's based on clock comparison.

Add Comment

[Steve Barlow (JIRA)]

Steve Barlow updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync

Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20

Add Comment

[Russell Mull (JIRA)]

Russell Mull assigned an issue to Russell Mull

PuppetDB / PDB-1450 Make automatic expiration work with sync

Change By: Russell Mull Assignee: Russell Mull

Add Comment

[Russell Mull (JIRA)]

[John Duarte (JIRA)]

John Duarte updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync

Change By: John Duarte QA Risk Assessment: Medium

Add Comment

[John Duarte (JIRA)]

John Duarte updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync

Change By: John Duarte QA Status: Reviewed

Add Comment

[Claudia Petty (Jira)]

Claudia Petty updated an issue

PuppetDB / PDB-1450 Make automatic expiration work with sync

Change By: Claudia Petty Labels: new-feature

Add Comment

This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)