848929 - set up chief for input -stage environment

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: WebOps: Other, task, P1)

Description

[Will Kahn-Greene [:willkg] ET needinfo? me]

The plan was to have chief set up for input -stage and -prod environments so we Input developers could deploy in a more continuous deployment fashion and save IT folks a ton of time.

We already do this for SUMO--it's been working really well there.

This bug is for setting up chief for the new Input -stage environment.

Comment 1

[Will Kahn-Greene [:willkg] ET needinfo? me]

This blocks going to production.

Comment 2

[Brandon Burton [:solarce]]

Marking as P1 which is webops goal impacting, but removing ability to page.

Comment 3

[Chris Turra [:cturra]]

i just spoke to :jakem about this and we want to prioritize getting input into prod over cheif since there will be some keyboard time required to get the python update script [1] worked out and cheif setup in the environment. it might be better to tackle this post production deployment since it shouldn't block our q1 goal.

[1] https://github.com/mozilla/fjord/blob/master/bin/update_site.py

Comment 4

[James Socol [:jsocol, :james]]

*not* setting up chief is going to add a ton of delay to us getting from stage-ready to production-ready.

Comment 5

[Will Kahn-Greene [:willkg] ET needinfo? me]

First off, I thought this was part of building the stage environment so I'm really bummed it's not.

In the sprint to get things working on -stage and -prod I'm expecting to do a lot of deployments. If you are ok with that, then we can push this off until next quarter.

Comment 6

[Brandon Burton [:solarce]]

(In reply to Will Kahn-Greene [:willkg] from comment #5)
> First off, I thought this was part of building the stage environment so I'm
> really bummed it's not.
> 
> In the sprint to get things working on -stage and -prod I'm expecting to do
> a lot of deployments. If you are ok with that, then we can push this off
> until next quarter.

I am pausing some other Chief rollouts to get this setup, I've done most of the legwork and should have an update script in a PR and be ready to test in the morning

Comment 7

[Will Kahn-Greene [:willkg] ET needinfo? me]

I really appreciate it. If there's anything I can do to lighten your load, feel free to let me know.

Comment 8

[Brandon Burton [:solarce]]

Just an update, this is nearly done, though it's taking a detour to redo some of the puppet work for chief, but it should be done Monday, Tuesday at the latest

Comment 9

[Brandon Burton [:solarce]]

This is ready for dev testing, we just need the flow from bug 852749

The URL is http://inputadm.private.phx1.mozilla.com/chief/input.stage/ and I'll communicate the password to you privately

While waiting on the flow I'll finish up the setup for prod and dev

Comment 10

[Will Kahn-Greene [:willkg] ET needinfo? me]

For documentation purposes:

The url is actually http://inputadm.private.phx1.mozilla.com/chief/input.stage with no trailing slash.

I got the password from solarce. Testing now.

Comment 11

[Will Kahn-Greene [:willkg] ET needinfo? me]

I tested it out and it seems to work great.

In testing it, I screwed up and deployed a pre-chief commit. Doing that hoses chief, so we shouldn't do that any more. Oops.

Comment 12

[Will Kahn-Greene [:willkg] ET needinfo? me]

I think this is all set. Marking it FIXED.

solarce: If there are outstanding things, we can reopen it.