Websites/Captain Shove: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
m (name fixup)
 
(19 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{outdated}}
Captain Shove is the evolution of [https://github.com/mozilla/chief Chief]. It only evolves if you trade it to another trainer while it's holding a Deploy Stone.
Captain Shove is the evolution of [https://github.com/mozilla/chief Chief]. It only evolves if you trade it to another trainer while it's holding a Deploy Stone.


Line 10: Line 12:
== Overview ==
== Overview ==
* Code name: Captain Shove (capshove)
* Code name: Captain Shove (capshove)
* Prod URL:
* URL: https://captain.mozilla.org
* Dev URL:
* Code Repo: https://github.com/mozilla/captain
* Stage URL:  
* Code Repo:  
* Code: Python/Django
* Code: Python/Django
* Product Owner: Jake Maul
* Product Owner: Jake Maul
* Dev Team: Michael Kelly, Will Khan-Greene, Chris Lonnen
* Dev Team: Michael Kelly, Will Khan-Greene, Lonnen
* IRC Channel: [irc://irc.mozilla.org:6697/capshove #capshove on irc.mozilla.org]
* IRC Channel: [irc://irc.mozilla.org:6697/capshove #capshove on irc.mozilla.org]
== Justification ==
Why not simply ssh into the admin node and run the commands you want via fab, limiting power with sudo, taking admin burden off IT's plate by submitting Puppet patches?
* Sometimes, non-ssh-knowing people should be able to do things, like update l10n files.
* You don't need to know the VPN config or where the admin node is (which is usually a fairly hard-to-remember hostname).
* You get free, accessible logging of what's been done by whom when.
* You get (ideally) a code review to sanity-check the insane things you want to do.
* Ops doesn't have to manually add access for new users to existing sites.


= Team =
= Team =
The primary and secondary contacts for each role of this project:
The primary and secondary contacts for each role of this project:


* Product owner - Jake Maul
* Product owner - Jake Maul (jakem)
* Web Project Manager - Michael Kelly
* Web Project Manager - Michael Kelly (mkelly)
* Developers - Michael Kelly, Will Khan-Greene, Chris Lonnen
* Developers - Michael Kelly (mkelly), Will Kahn-Greene (willkg), Lonnen
* IT - Brandon Burton, Chris Turra
* IT - Brandon Burton (solarce), Chris Turra (cturra)
* QA -
* Security - Frederik Braun (freddyb), Guillaume Destuynder (kang)
* Security -


= Meetings =
= Meetings =
* [https://etherpad.mozilla.org/captain-shove-security-2013-07-24 Initial talk with Security]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-09-26 2013-09-26 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-09-19 2013-09-19 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-09-12 2013-09-12 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-09-05 2013-09-05 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-08-29 2013-08-29 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-08-22 2013-08-22 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-08-15 2013-08-15 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-08-08 2013-08-08 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-weekly-2013-08-01 2013-08-01 Weekly Meeting]
* [https://etherpad.mozilla.org/captain-shove-security-2013-07-24 2013-07-24 Initial talk with Security]
* [https://etherpad.mozilla.org/the-future-of-chief-2013-7-22 2013-07-22 The Future of Chief Brainstorm]
* [https://etherpad.mozilla.org/the-future-of-chief-2013-7-22 2013-07-22 The Future of Chief Brainstorm]
= Important Bugs =
* [https://bugzilla.mozilla.org/show_bug.cgi?id=903542 Bug 903542: Server Setup Request]
* [https://bugzilla.mozilla.org/show_bug.cgi?id=902725 Bug 902725: Security Review Request]

Latest revision as of 22:24, 5 May 2023

Ambox outdated.png THIS PAGE MAY BE OUTDATED
This article is in parts, or in its entirety, outdated. Hence, the information presented on this page may be incorrect, and should be treated with due caution until this flag has been lifted. Help by editing the article, or discuss its contents on the talk page.

Captain Shove is the evolution of Chief. It only evolves if you trade it to another trainer while it's holding a Deploy Stone.

Elevator Pitch

Captain Shove is web-based frontend that communicates with a small daemon process on our admin nodes and webheads that executes commands for things like deploying a site, updating translations, kicking memcached, etc. The frontend is centralized and gives more control of the deploy process to developers, making life easier for both developers and operations people.

Goals and Measurements

  • Replace Chief for deployment of our websites.
  • Make everyone happy.

Overview

Justification

Why not simply ssh into the admin node and run the commands you want via fab, limiting power with sudo, taking admin burden off IT's plate by submitting Puppet patches?

  • Sometimes, non-ssh-knowing people should be able to do things, like update l10n files.
  • You don't need to know the VPN config or where the admin node is (which is usually a fairly hard-to-remember hostname).
  • You get free, accessible logging of what's been done by whom when.
  • You get (ideally) a code review to sanity-check the insane things you want to do.
  • Ops doesn't have to manually add access for new users to existing sites.

Team

The primary and secondary contacts for each role of this project:

  • Product owner - Jake Maul (jakem)
  • Web Project Manager - Michael Kelly (mkelly)
  • Developers - Michael Kelly (mkelly), Will Kahn-Greene (willkg), Lonnen
  • IT - Brandon Burton (solarce), Chris Turra (cturra)
  • Security - Frederik Braun (freddyb), Guillaume Destuynder (kang)

Meetings

Important Bugs

Retrieved from "https://wiki.allizom.org/index.php?title=Websites/Captain_Shove&oldid=1246418"