Apps/ServerArchitecture: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
http://ziade.org/appsync.png
http://ziade.org/appsync.png


= appsync =
= Overview =
 
* The appsync server provides
** appsync APIs
** the static myapps website
** a MySQL database that mirrors all writes
* The sauropod server is a Node.js server
** keeps sessions in memory (DB tokens)
** proxies the calls to the HBAse server
* The HBase cluster manage the data
 
= appsync/myapps =


* Points of contact
* Points of contact
Line 7: Line 18:
** Devs: Tarek
** Devs: Tarek
* Servers
* Servers
** appsync-stage1.vm1.labs.sjc1.mozilla.com (alias?)
** appsync-stage1.vm1.labs.sjc1.mozilla.com (https://stage-myapps.mozillalabs.com/)
* stack
* stack
** CentOS6
** CentOS 6
** Python 2.6
** Python 2.6
** nginx
** nginx
Line 17: Line 28:
* CI / CD : http://hudson.build.mtv1.svc.mozilla.com/view/9.%32Apps
* CI / CD : http://hudson.build.mtv1.svc.mozilla.com/view/9.%32Apps


= Sauropod server stack =  
= memcached =  


* urls
* Points of contact
** sauropod.mozillalabs.com
** Ops: Gozer
** stage-sauropod.mozillalabs.com
** appsync-stage1.vm1.labs.sjc1.mozilla.com
** dev-sauropod.mozillalabs.com
* OS - ubuntu ?
* stack
* stack
** node.js ?
** CentOS 6
** hbase ?
** Python 2.6
** nginx
** gunicorn
** appsync server
* status - DEPLOYED
 
= Sauropod Node.JS server =
 
* Points of contact
** Ops: Gozer
** Devs: ?
* Servers
** sauropod-stage1.vm1.labs.sjc1.mozilla.com
* stack
** CentOS6
** node.js 0.6.3 from mozilla-services package repository
** direct checkout from github
* status - Hackishly deployed
* CI / CD - not yet
 
= Sauropod HBase stack =
 
* Points of contact
** Ops: Gozer
** Devs: rtilder
* Servers
** appsync-hbase-stage1.vm1.labs.sjc1.mozilla.com
*** "master": running the namenode
*** Zookeeper quorum node
*** Also running as an HDFS data node and HBase region server
** appsync-hbase-stage2.vm1.labs.sjc1.mozilla.com
*** "slave": running HDFS data node and HBase region server
*** Zookeeper quorum node
* stack
** CentOS6
** Sun JVM 1.6.0
** Cloudera HBase distro version CDH3U2
* status - DEPLOYED
* CI / CD - none
 
= open questions =
 
* how to load balance sauropod ? client-side ? Zeus ?
* backup on the sauropod nodes ?

Latest revision as of 10:04, 14 December 2011

appsync.png

Overview

  • The appsync server provides
    • appsync APIs
    • the static myapps website
    • a MySQL database that mirrors all writes
  • The sauropod server is a Node.js server
    • keeps sessions in memory (DB tokens)
    • proxies the calls to the HBAse server
  • The HBase cluster manage the data

appsync/myapps

memcached

  • Points of contact
    • Ops: Gozer
    • appsync-stage1.vm1.labs.sjc1.mozilla.com
  • stack
    • CentOS 6
    • Python 2.6
    • nginx
    • gunicorn
    • appsync server
  • status - DEPLOYED

Sauropod Node.JS server

  • Points of contact
    • Ops: Gozer
    • Devs: ?
  • Servers
    • sauropod-stage1.vm1.labs.sjc1.mozilla.com
  • stack
    • CentOS6
    • node.js 0.6.3 from mozilla-services package repository
    • direct checkout from github
  • status - Hackishly deployed
  • CI / CD - not yet

Sauropod HBase stack

  • Points of contact
    • Ops: Gozer
    • Devs: rtilder
  • Servers
    • appsync-hbase-stage1.vm1.labs.sjc1.mozilla.com
      • "master": running the namenode
      • Zookeeper quorum node
      • Also running as an HDFS data node and HBase region server
    • appsync-hbase-stage2.vm1.labs.sjc1.mozilla.com
      • "slave": running HDFS data node and HBase region server
      • Zookeeper quorum node
  • stack
    • CentOS6
    • Sun JVM 1.6.0
    • Cloudera HBase distro version CDH3U2
  • status - DEPLOYED
  • CI / CD - none

open questions

  • how to load balance sauropod ? client-side ? Zeus ?
  • backup on the sauropod nodes ?
Retrieved from "https://wiki.allizom.org/index.php?title=Apps/ServerArchitecture&oldid=378713"