Identity/DevOps: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
= Documentation =
All DevOps documentation can be found in our [https://github.com/mozilla/identity-ops/blob/master/docs/ idenetity-ops github repository documentation] section
= Source Code =
All DevOps tools and provisioning logic can be found in our [https://github.com/mozilla/identity-ops/ idenetity-ops github repository]
= Roadmap =
= Roadmap =
== Q1/Q2 2013 roadmap ==
== Q1/Q2 2013 roadmap ==
Line 15: Line 21:
* 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
* 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  ==
[https://github.com/mozilla/identity-ops/wiki/Operational-Improvements-List Additional Operational Improvements]

Latest revision as of 17:59, 20 June 2014

Documentation

All DevOps documentation can be found in our idenetity-ops github repository documentation section

Source Code

All DevOps tools and provisioning logic can be found in our idenetity-ops github repository

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