The current deployment model for the *-status.appspot.com apps is to iterate through each hostname and do a separate deploy. This makes rolling back a pain. It's also wasteful to run so many different appengine projects that share the exact same code.
We should move all of these hostnames to be served by the same GAE app instance.
There are a few ways to do this:
- write one-time reverse proxy code, and push to each of the current separate gae apps. Proxie fwds to shared instances.
- pro: quick fix
- con: still have multiple gae projects to manage.
- write one-time 302 placeholder code, and push to each of the current separate gae apps. 302 redirects to shared instances.
- pro: quick fix.
- con: still have multiple gae projects to manage, some scripts may not handle 302s cleanly (low risk, but nonzero).
- figure out how to serve multiple hostnames from single gae project.
- pro: single gae app.
- con: still a mess to manage with different hostnames.
- migrate all clients to point to single gae hostname, preferably something under sheriff-o-matic.appspot.com/... so that all *-status 'apps' share the same release management and monitoring bits.
- pros: cleanest solution. can delete separate apps from src and cloud. centralized auth etc.
- cons: potentially lots of clean-up work for client code to update hostnames.
Comment 1 by seanmccullough@chromium.org
, Apr 4 2017Owner: zhangtiff@chromium.org
Status: Assigned (was: Available)