JAXA Approach on Software Preservation

Satoko Horiyama MIURASatellite Applications and Operations CenterJAXA

Target SoftwareData Processing Software for EO Satellites

MOSJERS-1ADEOSADEOS-IITRMM/PRAqua/AMSR-EALOSGOSATGCOM-W1GPM/DPR

2

(From WGISS-39 ESA slides)Approaches

1. Preservation of hardware (techno-centric)

2. Emulation (data-centric)

3. Virtualization (data-centric)

4. Migration (functionality-centric)

5. Cultivation (process-centric)

6. Hibernation (knowledge-centric)

7. Deprecation (budget-centric)

8. Procrastination (I'll-get-round to it eventually -centric)

ESA UNCLASSIFIED – For Official Use

Current Possible Options in JAXANo. Approaches Possible? Notes1 Preservation of hardware 2 Emulation

3 Virtualization 4 Migration 5 Cultivation Maybe in the future

6 Hibernation

7 Deprecation Not yet, but…8 Procrastination

4

Issues on Software Preservation

5

No. Approaches Issues1 Preservation of hardware Support completion is certain to come.3 Virtualization Support completion is certain to come to “a

hypervisor”. 4 Migration High cost is required every few years.8 Procrastination Today OK, but tomorrow…

Preservation Flow

6

Contract(lease / service)

Completion

Extended support *1

available?

ContractExtension

System Replacement

Yes

No

No.1 Preservation of hardware (No.8 Procrastination)

No.3 VirtualizationNo.4 Migration

*1: Including H/W and S/W (OS, COTS, OSS, etc) support.

On-board mission is…

7

•Reliability > Cost

On-going

•Reliability ~= Cost

To be completed soon

•Reliability < Cost

Already completed

Emphasis

Example1: TRMM/PR, ALOS, GOSAT

These mission software was/will be migrated with its following mission;

TRMM/PR -> GPM/DPR (GPM/DPR processing software has a function to process TRMM/PR data).ALOS -> ALOS-2GOSAT -> GOSAT-2 (not launched yet)

8

SIMPLE!

Exapmle2 : MOS, JERS-1, ADEOS (1/3)Around 2000

Y2K ProblemNot “free and open” policy

9

Archive Data Processing System(ADPS)

MOS Processing

System

ADEOSProcessing

system

JERS-1 Processing

System

No virtualizationLimited capability (for limited user requests)

Exapmle2 : MOS, JERS-1, ADEOS (2/3)2013

Data Policy changeFree and Open

Support completion of the ADPS is approaching.System concept change

Request base processing -> Process and archive all the data (all SAR data and cloud-free optical data).

10

ADPSJERS-1/SARProcessing

system

Expanded ADPS

•New System•Virtualization used

•Existing System

Exapmle2 : MOS, JERS-1, ADEOS (3/3)2017

The ADPS will stop its operation in March.All the processed data will be available to any users.Additional processing may be required, but will be very rare.

11

Expanded ADPS

NewADPS

•New System•No Virtualization used•No network connection•Limited capability & reliability

Virtualization (1/2)A hypervisor S/W Study results in 2014

Purpose : to decrease migration/replacement frequencyTarget: VMware, KVM, Xen

12

VMware KVM Xen

Vendor Development VMware Inc. linux-kvm.org Xen ProjectSales VMware Inc. Redhat Inc. Citrix Inc.

Release Frequency 1 year 3 years 1 year

H/W Compatibility Based on “Hardware Compatibility List”

Guest OS Compatibility Based on “Compatibility List”

Technical Support 5 years 5 or 10 years 5 years

Virtualization (2/2)

13

Hypervisor S/W Ver. 1.0

H/W A

H/W B

H/W CHypervisor S/W

Ver. 2.0

NGOK

Guest OS Ver. 1.0

Guest OS Ver. 2.0

Guest OS Ver. 3.0

Every 1 or 3 years *

* In general, support (maintenance updates and upgrades, bug and security fixes) duration is about 5 years.