NGST Server Deployment

NGST Server Deployment

Functional Requirements Specification

Revision 0.1

5/8/2007

Prepared By:

Confidential Material

1

SIP R2 ESS Application Deployment Software Functional Specification Rev. 03

Signature Page for Approvals

Distribution List & Approvals:

TABLE of CONTENTS

1.Revision History......

2.Document Overview......

2.1Purpose and Scope......

3.References......

4.Definitions & Acronym List......

4.1Definitions......

4.2Acronyms......

5.COP and CSP-based Deployment Strategies......

5.1Overview......

5.1.1COP......

5.1.2Platform Layer......

5.1.3Infrastructure Layer......

5.1.4Application Layer......

6.Deployment......

6.1Deploy a New NGST Server......

6.1.1Prerequisite......

6.1.2Installation......

6.1.3Configuration......

6.1.4Validation......

6.2Reconfigure an Existing NGST Server......

6.2.1Overview......

6.2.2Prerequisite......

6.2.3Installation......

6.2.4Configuration......

6.2.5Validation......

6.3Upgrade an Existing NGST Server......

6.3.1Overview......

6.3.2Deployment Prerequisites......

6.3.3Installation......

6.3.4Configuration......

6.3.5Validation......

6.4Patch an Existing NGST Server......

6.5Upgrade Soft Turret Telephony Daemon......

6.5.1Overview......

6.5.2Deployment Prerequisites......

6.5.3Installation......

6.5.4Configuration......

6.5.5Validation......

7.Disaster Recovery......

7.1Overview......

7.2Data Loss Recovery......

7.2.1Overview......

7.2.2Data Backup......

7.2.3Data Restore......

7.2.4Data Loss Recovery Process......

7.2.5Validation......

7.3Replace a Failed NGST Server......

7.3.1Overview......

7.3.2Permanent Server Failure Recovery Process......

7.3.3Validation......

7.4Replace a Failed Server Component......

7.4.1Overview......

7.4.2Replace the failed component process......

7.4.3Validation......

8.Alarming......

8.1Overview......

8.2AFM Integration......

8.3System Center Integration......

9.Multi-Server NGST Deployment......

10.Remote Access......

11.Maintenance......

12.Troubleshooting......

13.Additional Information......

13.1Interfaces, Ports and Protocols......

Company ConfidentialPrint Date:10/10/2018

Page 1 of 8

SIP R2 ESS Application Deployment Software Functional Specification Rev. 03

1.Revision History

2.Document Overview

2.1Purpose and Scope

The deployment of NGST system is the first IPC application, which will be based on the new COP/CSP architecture. Therefore a new deployment process must be defined.

Company ConfidentialPrint Date:10/10/2018

Page 1 of 8

SIP R2 ESS Application Deployment Software Functional Specification Rev. 03

3.References

• Marketing Requirements Definitions

\\ffdctdoc01\projectdocs\SoftTurret\MRD\2007-03 MRD - Next Generation Soft Turret V1.61.doc

• Engineering Requirements Definition
  \\ffdctdoc01\projectdocs\SoftTurret\ERD\NGSTERD_Rev2.doc
  
• Operational Requirements
  

4.Definitions & Acronym List

4.1Definitions

Build - Compiled software that is ready to be installed.

Software Component – Third party software that is not necessarily distributed in RPM format.

Software Package – A RedHat Enterprise Linux RPM package.

Installation – Installation copies one or more software packages to a server and creates basic settings that allow basic functionality.
Installation assumes a build has been executed.

Installer – The person who performs the installation and configuration of NGST server.

4.2Acronyms

5.COP and CSP-based Deployment Strategies

5.1Overview

The components of COP-based deployment for NGST are conceptually divided into three layers – Platform, Infrastructure and Application.

5.1.1COP

The non-HA common server platform must meet the following minimum hardware requirements:

• Intel Pentium 4, 3.00 GHZ (dual-core or single-core?)
• 2 GB DDR II SDRAM
• Two 80 GB hot swappable hard disks configured in RAID 1
• Dual gigabit Ethernet Network Interfaces
• Redundant power supplies
• Centralized hardware alarming capacity monitoring and reporting statuses of critical hardware components (i.e. power supply, hard disk, and etc).

5.1.2Platform Layer

Operating system:

• Red Hat Enterprise Linux ES 5.0 (Update, Kernel version?)

• System directories:
• /var: 15Gb
• /backup: 10Gb
• /opt: 10gb

System-level backup and restore:

• Backup partition
• In addition to the Linux system directories, a dedicated system partition must be created to store images of Linux partitions for system/application data for backup purpose.
• Backup/restore solution
• A drive/partition imaging solution must be provided to support the backup/restore of system/application data partitions[y1].

Essential components:

In addition to the operating system, the following components must be installed in and distributed with the platform layer.

Proposed essential components:

• Apache Tomcat (version[y2]?)
• BIND v 9.2.3
• OpenSSH v 3.9

•OpenSSL v .9.7

• PHP (version?)
• Libcurl 2.x

•NTP v 4.2.0

•RealVNC Enterprise Edition (version?)

All unlisted software packages shall be removed from the platform layer.

Security:

The platform layer should be hardened for security according to TBD[y3].

The platform layer should have latest patches installed for both OS and essential components.

Company ConfidentialPrint Date:10/10/2018

Page 1 of 8

[y1]What other system-level backup solutions are required (for example, DVD)?

[y2]Should tomcat be part of infrastructure layer?

[y3]Does this also include the OS user roles and default accounts?