Change Details

- Make sure job queue processing switches over cleanly: T124673 - Likely won't rely on EventBus yet; DC fail-over for that is discussed in {T127718} - Check the status of metrics and log aggregation (graphite T127976, logstash T127977) - Figure out a way to switch the master Action API accessed from various services between DCs (not always local). - DNS might be too slow / unpredictable - Network layer feasibility unclear; LVS in current configuration requires all hosts to be on the same network. - Possibily, set up basic service discovery from various services / set watches on etcd to update the action API URL config variable in-memory. Question is if hundreds of watches are realistic. If we use polling instead, it seems unclear if the effort gains us much over DNS.

- Make sure job queue processing switches over cleanly: T124673 - Likely won't rely on EventBus yet; DC fail-over for that is discussed in {T127718} - Check the status of metrics and log aggregation (graphite T127976, logstash T127977) - Figure out a way to switch the master Action API accessed from various services between DCs (not always local): T125069 - DNS might be too slow / unpredictable - Network layer feasibility unclear; LVS in current configuration requires all hosts to be on the same network. - Possibily, set up basic service discovery from various services / set watches on etcd to update the action API URL config variable in-memory. Question is if hundreds of watches are realistic. If we use polling instead, it seems unclear if the effort gains us much over DNS.

- Make sure job queue processing switches over cleanly: T124673 - Likely won't rely on EventBus yet; DC fail-over for that is discussed in {T127718} - Check the status of metrics and log aggregation (graphite T127976, logstash T127977) - Figure out a way to switch the master Action API accessed from various services between DCs (not always local).: T125069 - DNS might be too slow / unpredictable - Network layer feasibility unclear; LVS in current configuration requires all hosts to be on the same network. - Possibily, set up basic service discovery from various services / set watches on etcd to update the action API URL config variable in-memory. Question is if hundreds of watches are realistic. If we use polling instead, it seems unclear if the effort gains us much over DNS.