The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #6599

The client should default to using its cached catalog

Added by Luke Kanies over 3 years ago. Updated over 2 years ago.

Status:AcceptedStart date:03/04/2011
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:agent
Target version:3.x
Affected Puppet version: Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

We currently default to the client upgrading its catalog every time, and there’s no straightforward mechanism to change this default. This means that all phased roll-out work must involve working directly on the clients to control catalog updates.

We should instead switch to a model where the client can ask the server if it should update its catalog, and by default uses its existing catalog.

This should probably be done by the client sending the server its catalog version and the server returning a boolean on whether it should be retrieving a new catalog.

Alternatively, it could do something like a ‘HEAD’ request on a new catalog and compare the versions on the client, and decide to upgrade based on that.

History

#1 Updated by Nigel Kersten about 3 years ago

  • Project changed from Product Roadmap to Puppet
  • Category deleted (Puppet)
  • Parent task deleted (#6598)

#2 Updated by Devon Peters over 2 years ago

  • Category set to agent
  • Target version set to 3.x

#3 Updated by Luke Kanies over 2 years ago

Note that I think it’s important that the decision about whether to download the catalog is made by the server, not by the client.

Also available in: Atom PDF