EnterpriseMysqlClusterProject < CF

CF Web>InternalProjects>EnterpriseMysqlClusterProject (2016-04-11, DanielAllen) (raw view)

---+ Enterprise Mysql Cluster Project

---++ Table of Contents
%TOC%

---++ Project Objective: Purpose

The purpose is to set up a Highly Available clustered mysql database to support general computing. This is a term goal for Winter 2016, with a firm deadline of April 13th (meeting between Ken and CSCF Managers). 

---++ Project Scope/Deliverables
The high-level outcomes and results of this project are as follows:
   * we're agreed on a project plan and timeline %Y%
   * new 3-node cluster with proper master/slave replication %Y%
   * mysql.cs databases [[EnterpriseMyseqlClusterProjectDBList][(list here)]] are moved to new cluster %Y%
   * Marmoset is left behind on current mysql.cs %Y%
   * appropriate resource, latency, and health monitoring of the database services %Y%
   * wrapup includes: 
      * [[MySQLHAOperationsManual][maintenance documentation]] %Y%
      * [[EnterpriseMysqlClusterProjectWrapup][plans for potential upcoming work]] %Y%

---++ Scope Includes/Excludes

---+++ Includes
   * high-speed dedicated storage network
   * asynchronous replication (master/slave, same process as set up by Clayton for yubikey)
   * failover process with acceptable downtime
   * tested failover and recovery, with (test instances of?) real applications and with no data loss (requires application experts - eg., Daniel for inventory)
   * necessary documentation
   * cluster deployment
      * PXE booting cluster
      * create salt pillar to build and deploy 3 mysql nodes on hardware cluster (Anthony and Clayton)
      * saltifying: mysql cluster backup (Anthony with Fraser)
      * benchmarking and testing mysql cluster performance (Fraser, Lori, Steve Weber)
   * migrate data from mysql.cs to cluster (Fraser)  

---+++ Excludes
   * synchronous data replication (unless Clayton's instructions say it's trivial)
   * investigating additional mysql cluster setups
   * creating automated containers

---++ Constraints
   * many current databases [[EnterpriseMyseqlClusterProjectDBList][(list here)]] are critical; downtime must be pre-planned and minimized (no unscheduled downtime)
   * no user-level changes: two weeks before exams until last CS exam
   * end of term is April (23 - end of classes; 29 - last business day before new term)

---++ Assumptions and Risks
   * marmoset can stay where it is on the non-clustered database, for this phase.

---++ Project Members
drallen (project manager), dlgawley a2brenna fhgunn gxshen arpepper ldpaniak

---++ Project Stakeholders
lfolland omnafees (, ISG ...)

---++ Project Sponsor
Ken Salem

---++ ST
   * [[https://cs.uwaterloo.ca/cscf/internal/request/UpdateRequest?85594][ST#85594]]

---++ Implementation Plan
   * [[Enterprise Mysql Cluster Project Implementation]] including Work Breakdown Structure and timeline

---++ Meeting notes
   * EnterpriseMysqlClusterProject20160120
   * EnterpriseMysqlClusterProject20160127
   * EnterpriseMysqlClusterProject20160203
   * EnterpriseMysqlClusterProject20160211
   * EnterpriseMysqlClusterProject20160217
   * EnterpriseMysqlClusterProject20160225
   * EnterpriseMysqlClusterProject20160303
   * EnterpriseMysqlClusterProject20160309
   * EnterpriseMysqlClusterProject20160317
   * EnterpriseMysqlClusterProject20160324
   * EnterpriseMysqlClusterProject20160331
   * EnterpriseMysqlClusterProject20160411

-- Main.DanielAllen - 2016-01-19

Topic revision: r19 - 2016-04-11 - DanielAllen

Information in this area is meant for use by CSCF staff and is not official documentation, but anybody who is interested is welcome to use it if they find it useful.

Other Webs

My links
- People
- CERAS
- WatForm
- Tetherless lab
- Ubuntu Main.HowTo
- eDocs
- RGG NE notes
- RGG
- CS infrastructure
- Grad images

Edit