2738 rfd

From UG

(Difference between revisions)
Jump to: navigation, search
(CT2 EA Demo)
(Current NY based Linux servers and applications)
Line 84: Line 84:
** BKK:?
** BKK:?
-
=== Current NY based Linux servers and applications ===
+
=== Servers ===
 +
 
 +
This is overview of Current NY based Linux servers and applications.
These servers are part of NY office network. All of them run some kind of Linux.
These servers are part of NY office network. All of them run some kind of Linux.
Line 103: Line 105:
2) '''Sugar CRM / EA Demo server'''  
2) '''Sugar CRM / EA Demo server'''  
-
* (old) Sugar CRM app - This has been migrated to *.74 CT2 server in a cloud  
+
* (old) [[#Sugar CRM]] app - This has been migrated to *.74 CT2 server in a cloud  
** could be discontinued now
** could be discontinued now
-
* EA Demo Apps - instances of internal and Client CT2 Apps for Sales
+
* [[#CT2 EA Demo]] - instances of internal and Client CT2 Apps for Sales
** has to be migrated  
** has to be migrated  
Line 111: Line 113:
3) '''Dev'''  
3) '''Dev'''  
-
* "Demo/QA" dev environment for QA and UAT (CT2 internal and client apps)
+
* [[#CT2 Demo]] 
** in active use
** in active use
-
* "Staging" dev environment for pere-release QA (CT2 internal and client apps)
+
* [[#CT2 Staging]] 
** in active use
** in active use
Line 124: Line 126:
5) '''Mantis'''
5) '''Mantis'''
-
* Mantis App (old version)
+
* [[#Mantis]]  (old version)
** not used, to be discontinued now
** not used, to be discontinued now
-
* Wiki App (old version)
+
* [[#Wiki]] (old version)
** not used, to be discontinued now
** not used, to be discontinued now
-
* SVN
+
* [[#SVN]]
** in active use
** in active use

Revision as of 22:58, 21 February 2011


Contents

Info

0002738: (Servers and Apps) Discontinue all Linux servers in Valley S and migrate applications

Requirements and Solutions

Intro

Number of factors related to the elimination or scaling down server farm:

  • President's strategic direction of "moving all NY servers into cloud" due to:
    • possibility of flood
    • lack of IT resources in house to support servers
  • TBD

Disadvantages of elimination of servers:

  • hire cost of hosting (if we need extra servers at hosting provider)

Potential compromise would be to leave one server in NY with some services/applications that:

  • could be easily recovered on non NY server in case of flood or lack of support
  • require no support from NY staff

Another option would be to have one Linux server that would run applications related to both CT2 development / production and to NY office internal IT needs (Squid, what else?)

Applications

Squid

  • What: web filter
  • Users: most NY office users (8-8 EST)
  • Usage pattern: constant, all users will be down if app is down; most users have browser pointing to it for internet access

Door card DB

  • What: users info about NY office main door access (not sure what is there)
  • Users: michael.k@jaguarfreight.com (he is responsible for managing cards)
  • Usage pattern: approx once a week

Sugar CRM

  • What: CRM for Sales Dept (global)
  • Users: All Jaguar Sales - sales@jaguarfreight.com
Chikei Ho; Harry Morgan; Janine Hines; Percy Kaye; Simon Kaye; Sylvia Jenkins; Vikesh Vithlani
  • Usage pattern: global, unknown, low between 19-20 EST

CT2

Main Jaguar App. There are several versions - see below. Always have 2 parts (wars/urls): internal and client.

CT2 EA Demo

  • What: Demo version of CT2 for Sales Dept to demonstrate to prospective Clients CT2 functionality
  • Users: All Jaguar Sales - sales@jaguarfreight.com and any client users during the scheduled demo and possibly after if salesman left them login info
  • Usage pattern: unknown

CT2 Demo

  • What: Demo version of CT2 for QA and UAT. RE-deployed almost daily.
  • Users: CT2 Team plus MOs occasionally
  • Usage pattern: 24x7 with heavy during:
    • NY: (8-20 EST)
    • Kiev: (2-19 EST)

CT2 Staging

  • What: Staging version of CT2 for QA before release and bug investigation
  • Users: CT2 Team plus MOs occasionally
  • Usage pattern: most heavy before release or emergency release, could be used for bug investigation any day

SVN

  • What: CT2 source code repository
  • Users: CT2 Team, mostly Development Team
  • Usage pattern: unknown

Mantis

  • What: task and bug tracking system for CT2 and IT
  • Users: CT2 Team, list could grow in the future
  • Usage pattern: 24x7 with heavy during:
    • NY: (8-20 EST)
    • Kiev: (2-19 EST)
    • SF: ?
    • BKK:?

Wiki

  • What: info repository for CT2 and IT (specs, etc)
  • Users: CT2 Team plus MOs occasionally
  • Usage pattern: 24x7 with heavy during:
    • NY: (8-20 EST)
    • Kiev: (2-19 EST)
    • SF: ?
    • BKK:?

Servers

This is overview of Current NY based Linux servers and applications.

These servers are part of NY office network. All of them run some kind of Linux.

See Jaguar Network diagram below:

File:Network diagramm.JPG

Linux servers in NY office and list of apps/services running on them (as far as we know):

1) Squid proxy - this is the only server that is required for NY office network

  • #Squid
    • could be discontinued in the future
  • #Door card DB
    • could be migrated into simple xls (for Michael to manage)

Box: old PC

2) Sugar CRM / EA Demo server

  • (old) #Sugar CRM app - This has been migrated to *.74 CT2 server in a cloud
    • could be discontinued now
  • #CT2 EA Demo - instances of internal and Client CT2 Apps for Sales
    • has to be migrated

Box: new Optiplex 330

3) Dev

Box: new Optiplex 330

4) Dev Firewall

  • firewall for Dev server

Box: old PC

5) Mantis

  • #Mantis (old version)
    • not used, to be discontinued now
  • #Wiki (old version)
    • not used, to be discontinued now
  • #SVN
    • in active use

Box: new Precision 390

6) Ext

  • backups for Dev server apps (anything else?)
    • used, not clear what exactly is there

Box: new Optiplex 330

7) Specs - video tutorial Dev Server

  • not used, can be discontinued

Box: old PC

8) Test/Dev for Sugar CRM

  • not used, can be discontinued

Box: old PC

Future solution

4 newer PCs as identified in previous section has to be re-used as user Desktops.

Servers and applications will be located / distributed as follows:

TBD

Architect Review

Implementation Notes

QA Plan

History

Personal tools