New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 773431 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner:
Closed: Jul 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

Puppet staging branch

Project Member Reported by dgarr...@chromium.org, Oct 10 2017

Issue description

The idea is to create a staging branch for puppet which runs on the staging lab servers, then move to the current prod branch after staging verification.

One Problem:

We control DHCP and other config files via puppet and need to make changes to them in near real times. Move them to a different repo?

Also, we would want to automatically validate behavior on the staging servers (?via the current push test?), and need to create a push process for updating the rest of the lab.

 
Passing to Aviv to consider as a long term OKR.
Cc: pprabhu@chromium.org shuqianz@chromium.org jkop@chromium.org
Labels: -Type-Bug -Pri-3 Pri-2 Type-Feature
Owner: ----
Status: Available (was: Untriaged)
one of a few possible ideas for testing puppet changes before production
Hi, this bug has not been updated recently. Please acknowledge the bug and provide status within two weeks (6/22/2018), or the bug will be archived. Thank you.
Owner: ayatane@chromium.org
Status: Assigned (was: Available)
Mergedinto: 806034
Status: Duplicate (was: Assigned)

Sign in to add a comment