Closed
Bug 1332609
Opened 8 years ago
Closed 6 years ago
Upgrade puppet version on our puppet masters
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Infrastructure & Operations
RelOps: Puppet
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: aselagea, Unassigned)
Details
We discussed with Kim and Coop about this during our recent meetings and there are a few questions that we'd like to address here:
1. which is the current state?
2. are there any concerns about the upgrade (e.g. moving some machines to another DC)?
3. how can buildduty help with this?
Reporter | ||
Updated•8 years ago
|
Flags: needinfo?(arich)
Updated•8 years ago
|
Assignee: infra → relops
Component: Infrastructure: Puppet → RelOps: Puppet
QA Contact: cshields → mcornmesser
Comment 1•8 years ago
|
||
I definitely have concerns about trying to do a puppet upgrade while we're trying to do security patching, stand up a new platform, and move to multiple datacenters, yes. I think the first step here would be to evaluate how long the transition would be, what the work involved is (I presume we need to upgrade the binaries and libraries on ALL the platforms as well as change the puppet code itself), and if we can get it done before we start trying to do all the prep work for the dc move. If so, and buildduty wants to own and drive this, then sure, let's do it. Otherwise, I suspect this is something that will be put on hold until after we've finished the move.
Flags: needinfo?(arich)
Comment 2•6 years ago
|
||
We're abandoning the old puppet master model, moving to masterless puppet and upgrading along the way.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•