Identity/DevOps: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
In Q1 2013 the Identity DevOps team will be moving services out of the physical datacenter SCL2 and into Amazon Web Services.
In Q1 2013 the Identity DevOps team will be moving services out of the physical datacenter SCL2 and into Amazon Web Services.


3/19 : VPC outbound internet access via NAT instance
* 3/19 : VPC outbound internet access via NAT instance
3/21 : Webhead AMI
* 3/21 : Webhead AMI
3/22 : Zeus routing logic converted to nginx
* 3/22 : Zeus routing logic converted to nginx
3/26 : keysigner AMI
* 3/26 : keysigner AMI
3/27 : dbwriter AMI
* 3/27 : dbwriter AMI
3/29 : Cross DC VPN for DBs
* 3/29 : Cross DC VPN for DBs
4/2 : db AMI
* 4/2 : db AMI
4/3 : Handoff environment to QA
* 4/3 : Handoff environment to QA
4/5 : Nagios monitoring
* 4/5 : Nagios monitoring
4/9 : Create region 2
* 4/9 : Create region 2
4/10 : QA approval of region 1
* 4/10 : QA approval of region 1
 
* 4/30 : Final day to turn down servers at SCL2
4/30 : Final day to turn down servers at SCL2


5/13
5/13

Revision as of 17:55, 18 March 2013

Roadmap

Q1/Q2 2013 roadmap

In Q1 2013 the Identity DevOps team will be moving services out of the physical datacenter SCL2 and into Amazon Web Services.

  • 3/19 : VPC outbound internet access via NAT instance
  • 3/21 : Webhead AMI
  • 3/22 : Zeus routing logic converted to nginx
  • 3/26 : keysigner AMI
  • 3/27 : dbwriter AMI
  • 3/29 : Cross DC VPN for DBs
  • 4/2 : db AMI
  • 4/3 : Handoff environment to QA
  • 4/5 : Nagios monitoring
  • 4/9 : Create region 2
  • 4/10 : QA approval of region 1
  • 4/30 : Final day to turn down servers at SCL2

5/13

  • Modify DB architecture to remove single point of failure (single write master)
    • This is not re-evaluating our choice of persistence. It's just making our existing architecture truly fault-tolerant and highly available.
  • Add more performance monitoring to enable later platform improvements
    • There are many ways we could further scale. To make intelligent choices, we need to gather information about the performance and behavior of our servers.

Beyond

Additional Operational Improvements