Update karlstaging Friday morning, make sure you know where the bodies are buried

[Paul Everitt]

Before we get into the weekend, I'd like to make sure you know how to drive anything done by the ChrisR->ChrisM->Shane work for karlstaging. Let's do an update ASAP and give ourselves time to recover if something is what you expected.

Also, timing wise, we're likely to need a final (code-only) update Sunday afternoon. If that isn't something you can do, let me know and we'll either adjust the schedule or see if someone else (e.g. Shane) can do it.

[Chris Rossi (chris-archimedeanco)]

I'm adding Shane as a subscriber to this ticket.

Shane,

Can you give me a rundown on what you've done with karlstaging so far and where any scripts that might have been produced are living?

Thanks,
Chris

[Paul Everitt (paul-agendaless)]

Putting out an APB on Shane.

[Chris Rossi (chris-archimedeanco)]

I am now up to speed with osideploy. Thanks. A couple of things:

1) We won't be using this to deploy to karldev. That uses Octomotron and the dev process, which is pretty different.

2) Our bluff is getting called on staging: there are two appservers set up. We still don't have a unified multiprocess logging solution. Maybe this should get bumped up in priority.