Virtualization of EPOCH IPS

Transcription

Virtualization of EPOCH IPS
April, 2016
Tatsuya Watanabe / Assistant Manager
System Engineering Team
SKY Perfect JSAT Corporation (SJC)
0
Agenda
1. Overview of SJC and YSCC
2. Current status of virtualization in SJC
3. Function of VMware and how SJC uses it
4. Points of concern about virtualization
Copyright © 2016 Sky Perfect JSAT Corporation. All Rights Reserved
1
Overview of SJC and YSCC
2
Satellite Fleet
* Horizons-1 & 2 are Jointly owned by
JSAT and Intelsat.
JCSAT-4A
(82E)
JCSAT-85**
（Intelsat-15）
(85E)
** JSAT owns 5 Ku-band
transponders on IS-15
Horizons-1*
(127W)
GEO
36,000km
3rd Party
Customer
Satellite
Horizons-2*
(84.8E)
N-SAT-110
(Backup)
JCSAT-1B
(150E)
JCSAT-RA
(Backup)
JCSAT-5A
(132E)
*** JCSAT-110R is Jointly owned by
JSAT and B-SAT.
Superbird-B3
Superbird-C2
(144E)
Superbird-B2
(162E)
Superbird-A3
（158E）
JCSAT-2A
(154E)
JCSAT-110R***
(110E)
JCSAT-15
JCSAT-14
JCSAT-16
JCSAT-4B
(124E)
JCSAT-3A
(128E)
N-STAR c
(136E) 3rd Party Customer
Satellite(143E)
3
Satellite Operations Experience
As of 2014/12
’89
J C S A T -1
’90
’91
’92
’93
’94
’95
’96
’97
’98
’99
’00
’01
’02
’03
’04
’05
’06
SSL
SSL
J C S A T -3
’12
’13
’14
D e - o rb it
D e - o rb it
B o e in g
S u p e rb ird -A 3
B o e in g
B o e in g
J C S A T -1 B
J C S A T -4 A
B o e in g
B o e in g
S u p e rb ird -B 2
NTT
N -S T A R a
N -S T A R b
NTT
SSL
D e - o rb it
D e - o rb it
SSL
LockheedL Martin
社製
M
N -S A T -1 1 0
Boeing
社製
B o e in
g
J C S A T -2 A
N -S T A R c
Orbital社製
O r b ita l
NTT
Boeing
社製
B o e in
g
H o riz o n s-1
D e - o rb it
Space System
S S LLoral 社製
3 rd P a rty S a t- A
J C S A T -5 A
Lockheed
社製
L Martin
M
Lockheed
社製
L Martin
M
J C S A T -3 A
J C S A T -1 1 0 R
’11
D e - o rb it
B o e in g
J C S A T -R
J C S A T -8 5
’10
D e - o rb it
S u p e rb ird -A
J C S A T -R A
’09
D e - o rb it
B o e in g
S u p e rb ird -B
S u p e rb ird -C 2
’08
D e - o rb it
B o e in g
J C S A T -2
H o riz o n s-2
’07
Orbital
社製
O r b ita
l
Boeing 社製
Lockheed Martin 社製
Space Systems Loral 社製
Orbital 社製
三菱電機
社製
Melco
NEC 社製
NEC
三菱電機製
M e l co
LM
O r b ita l
LM
LM
J C S A T -4 B
3 rd P a rty S a t- B
N EC
4
SJC Ground Stations
Gunma Satellite Control Station （GSCS）
Sub Ground Station
Yamaguchi Network Control Center（SPW）
Sub Ground Station
Ibaraki Network Control Center （SPE）
Backup Satellite Control Center and Teleport
Yokohama Satellite Control Center （YSCC）
Primary Satellite Control Center and Teleport Facilities
5
YSCC Organization
Satellite Planning &
Operations Group
Satellite Operations
Division
Service Operations
Division
Noriko Masuda
Hideo Hayashi
Satellite Control
Team
Yoji Sato
System Engineering
Team
Hiroaki Nagai
Satellite Engineering
Team
Azuma Miyata
Network Operations
Team
Satelite Facilities
Management &
Administration Div.
Tetsuya Segawa
Team-1
Ground Systems Procurement &
Maintenance
Teleport Operations
Team-1
Teleport Operations
Team-2
Team-2
General affairs & administrations in
YSCC
Team-3
Orbital Dynamics
Team
General affairs & administrations
in SPE
Hideshi Chazono
6
Current status of virtualization
in SJC
7
Reasons to use virtualization

SJC will launch 4 satellites within 2 years.
 work on reducing the operational load in several ways
 One of the way is virtualization of EPOCH IPS

Virtualization refers to the creation of a virtual machine that acts like a
real computer with an operating system(#).
Traditional Architecture
Virtual Architecture
(#)Wikipedia: https://en.wikipedia.org/wiki/Virtualization
8
Reasons to use virtualization
SJC decided
to use VMware as a virtualization software for EPOCH IPS.
VMware
has a lot of merits as follows:
Cost effective
Resource Optimization, Saving Rack space, Consumed Power
Functions to Reduce Operational Load
vMotion, Snapshot, cloning, HA, Backup, Converter, and so on.
Last year,
SJC verified following points:
Essential functions of VMware work as expected
EPOCH IPS on Virtual Server is working just like on a Physical Server
9
The relation between virtualization and increase of EPOCH IPS


EPOCH IPS constitutes an increasingly large portion of the SJC.
The more the percentage of EPOCH IPS is increasing, the more we’ll see
the effect of virtualization of EPOCH IPS go up.
Bus Type / Operations Software
Bus
Type
Operations
software
Boeing
601
A2100
(5 satellites)
Coming Soon
StarBus2
DS2000
SMACS
(1 satellites)
(1 satellites)
(1 satellites)
(5 satellites)
TCR/STA
New
Satellites
(4 satellites)
EPOCH v4 EPOCH v4
OASYS
OASYS
BirdStar
ORAMS
SMACS
EPOCH v4
OASYS
Consider the way to change to EPOCH IPS
Plan to change to EPOCH v4 & OASYS
without extra cost (because these are old
so it’s difficult to secure a budget
Copyright for
© 2016 now)
Sky Perfect JSAT Corporation. All Rights Reserved
10
Current situation and virtualization plan in the future


SJC has virtualized only part of EPOCH IPS servers.
SJC will continue to virtualize other servers and to investigate the
appropriate method to virtualize workstation.
Percentage of EPOCH IPS servers and workstations in each site
Already virtualized
Servers for existing satellites in YSCC
Servers for upcoming satellites in YSCC
Servers in Sub-site
Workstations in YSCC
Virtualization of workstation is
under investigation.
Workstations in Sub-site
11
Functions of VMware and
how SJC uses it
12
Physical Configuration Overview
VMware
is Installed on both of 2 dell servers
Virtual Machines (VM) are saved to a Shared Disk.
One of 2 VMware ESXis loads and executes VM onto its memory
Virtual Machines (VM)
EPOCH SV
Compass
REDHAT
Win Server
VMware ESXi
VMware ESXi
Dell Server
Dell L2SW
NAS for backup VMs
EPOCH SV
Compass
REDHAT
Win Server
Dell Shared Storage
for saving VMs
13
Saving Rack Space of Physical Configuration


Lots of VM are consolidated and working on these machines.
Hardware failure has a significant impact on VM, so it’s necessary to
make each Machine as a redundant configuration.
2 Dell servers
1
equipped with 2 (6 core,HT)
CPUs and 192GB Memory each
2
3
4
2 Dell Layer-2 Switches (back)
5
6
NAS
7
8
equipped with 4 7,200 RPM
SATA HDDs
9
Dell Shared Storage
10
equipped with 24 15,000 RPM
SAS HDDs
14
Basic License Type of VMware

So far, SJC is using Essentials Plus License of VMware that is reasonable
but has many functional restrictions.

This License enables us to:
 Use basic functions such as vMotion, Snapshot, clone, HA, and VDP

This License doesn’t enable us to:
 Scale-out more than 3 servers
 Use advanced functions such as FT, DRS, Storage vMotion, App-HA,
and so on
VMware
ESXi
VMware
ESXi
VMware
ESXi
VMware
ESXi
15
vMotion

vMotion enables running VM to move into another server with zero
downtime

SJC confirmed that EPOCH server can finish its vMotion process without
disconnecting from DSS.
DSS
Telemetry
①Stop
EPOCH SV
REDHAT
EPOCH SV
REDHAT
VMware ESXi
①Activate
VMware ESXi
16
Snapshot

Snapshot preserves the state of the VM at a specific point in time.

When you revert to a snapshot, you discard all changes made to the VM
since you took the snapshot.
①Take a snapshot
⑤return to Stable state
Stable state
②Apply Patch
③become Unstable state
④Back to the previous state
17
Clone

Clone is a copy of an existing virtual machine.

If you want to make a copy of a virtual machine for separate use, create
a clone.
Clone
EPOCH SV
REDHAT
①Cloning
EPOCH SV
REDHAT
VMware ESXi

If you want to save the current state of the virtual machine, so you can
revert to that state in case you make a mistake, take a snapshot.
18
VMware HA

Failover function when Physical or Virtual Machine fails.
1. Virtual Machine Failover
②Reboot VM on the same host
①failure
VM
monitor
VMware ESXi #1
VMware ESXi #2
2. Host Machine Failover
②Stop all powered-on VMs
VM
①failure
③VMs start
VM
VM
VM
monitor
VMware ESXi #1
VMware ESXi #2
19
VMware Data Protection (VDP)

VDP is an agent-less, image-level VM backup tool

Saving a lot of backups causes unstable state of VDP, so SJC set up
backup schedule of VDP as following
 Once
a day for 7 days, Once a week for 4 weeks, Once a month for 12 months
VDP
VMware ESXi
VMware ESXi
Dell Server
Dell L2SW
Backup
EPOCH SV
REDHAT
Dell Shared Storage
20
vCenter Converter




It’s hard to rebuilt already running EPOCH IPS servers as a VM.
vCenter Converter enables us to convert EPOCH IPS into VM easily.
SJC conducted load tests of the converted EPOCH server on VM, and
confirmed it works fine.
SJC has already been operating the converted EPOCH Server as a VM.
vCenter Converter
Control
Control
EPOCH SV
EPOCH SV
EPOCH CL
REDHAT
REDHAT
Windows7
Copy
EPOCH CL
Target Physical Servers
VMware ESXi 5.5
Windows7
Destination
21
Other features of VMs

VM is just a file, so it’s easy to move VM between a production
environment and a test environment.
Test environment
EPOCH SV
EPOCH SV
REDHAT
REDHAT
VMware Player
copy
EPOCH SV
REDHAT
Cloning
VMware Player
copy
EPOCH SV
EPOCH SV
REDHAT
REDHAT
VMware ESXi (Production environment)
22
Points of concern
about virtualization
23
Points of resource allocation

It’s necessary to decide resource allocation size of each VM.
 Resources are such as number of CPU cores, Memory size, and HDD size

If the resource allocation size is too much, and the total of all the VM’s
actual resource consumption exceeds physical server’s resource size, all
unprotected VMs become unstable.

On the other hand, if the resource allocation size is too little, it affects the
performance.

To prevent these situations, it’s necessary for important VMs such as
EPOCH server to investigate and to reserve (a function to assure allocated
resource) the minimum requirement of resource size.
24
Resource allocation size of each EPOCH IPS server in SJC

SJC conducted load tests and observed the resource utilization of each
EPOCH IPS server.
Specific resource allocation size of each EPOCH IPS server in SJC (#)
EPOCH server
Task
for 1 telemetry Initiator
Compass
Server
CPU core 2～
2～
2～
Memory
8GB～
4GB～
4GB～
HDD
100GB～
30GB～
30GB～

These specs are smaller than on Physical servers, yet they’re working fine.

The appropriate size depends on the use case scenario.
(#) The memory and HDD sizes will greatly differ according to whether or not we use the memory over commit and the thin provisioning functions
(SJC tries not to use these functions)
25
Failure detecting and resource monitoring

Hardware failure and resource shortage on the Physical Machine have a
significant impact on all virtual machines.

SJC built an NMS server to detect Hardware, VMware Hypervisor,
vCenter process failure and to monitor resource utilization.
vCenter
NMS
OS
Network Management System
VMware ESXi
iDrac
SNMP Polling & VMware API
Dell Server
Dell L2SW
SNMP Polling & SNMP Trap
Dell Shared Storage
SNMP Trap
26
Conclusion
27
Advantages and Disadvantages of VMware


There was a lot of hard work involved in our first introduction of
virtualization of EPOCH IPS as follows

to consider hardware specs, redundancy design, and migration plan

to prepare the way of failure detecting and resource monitoring (#)
However, VMware functions provide the benefit of increasing the
efficiency of the system operation.
(#) Preparing fault isolation methods is indispensable. If something happened to a VM, He that is unfamiliar with virtualization may doubt VMware.
28
Thank you.
Please feel free to contact me;
[email protected]
29
Appendix
30
Total optimization in the next stage

SJC is working on virtualizes only servers in main site for now, however
it’s necessary to consider multi-site design. For example,
 SJC needs sufficient number of client only in case of emergency in
other site.
 There is some possibility to make unused licenses that can be used
for a purpose of replace TCR/STA to EPOCH IPS.
Other Site (Sub-site)
Main Site
Server
Server
REDHAT
REDHAT
Client
Windows
Copy VM by using
VMware or Storage
replication
Client
Most part of the clients are
deactivate in normal time
and activate in case of
emergency
Windows
31
Ideal design of HA configuration

It may be possible to monitor the EPOCH server on the VM with higher
class license and custom settings of VMware.

This way is smart because it’s not necessary to prepare EPOCH Server on
the each VMware ESXi, but we have to consider the failover downtime,
reconnection with client / baseband, and get over some hurdles as
mentioned above.
①failure
EPOCH Server
Processes
monitor
②reboot Application
Redhat
monitor
VMware ESXi #1
monitor
VMware ESXi #2
32
VMware HA in SJC

If the application's process finishes, we want VMware to reboot the
application to recover. However, due to the licensing constraints and
other problems, this is not realized for now.

SJC prepares EPOCH server on the each VMware ESXi for redundancy.
BB
Telemetry
EPOCH Server
Process
Not monitor
EPOCH Server
Process
Redhat
monitor
VMware ESXi #1
Not monitor
monitor
Redhat
monitor
VMware ESXi #2
33
Problem that we have to solve

SJC needs the way to confirm whether or not EPOCH IPS server process is
alive without monitoring GUI. As one of the methods, we can use “ps aux
| grep epoch”, but it’s an uncertain way.

Does anyone know any monitoring functions of the EPOCH server like the
“statusEpoch” command?
NMS
monitor
EPOCH Server
Process
Not monitor
EPOCH Server
Process
Redhat
monitor
VMware ESXi #1
Not monitor
monitor
Redhat
monitor
VMware ESXi #2
34

Virtualization of EPOCH IPS

Transcription

Similar documents

10th - 12th July 2014

Asigra Virtual Disaster Recovery

I`m helping to end MS by participating in the 2016 Jayman BUILT MS

The Board of Directors of Qatar Fuel (WOQOD) is pleased to invite

5 `S` Training Program at ABV-IIITM, Gwalior on 21.07.2016

How to Install and Use SSS\Progman with Carsoft or INPA interface

Porky Expo Flyer

The NeuLion Report