News
(Update)Baremetal/Dedicated Hypervisor(vSphere/Hyper-V) will shift to End of Marketing and new flavors will be provided
Current flavor being provided in Baremetal Server and Dedicated Hypervisor(vSphere/Hyper-V) menu will shift to inventory sales（End of Marketing） from December 15th, 2017(JST).
[04/01/2018 update]
Added that Name change of current flavors is reflected in the portal display
[12/13/2017 update]
Added Dedicated Hypervisor menu（vSphere/Hyper-V）
Added availability list of official Image template
Overview
Four flavors in Baremetal Server and Dedicated Hypervisor(vSphere/Hyper-V) menu will shift to End of Marketing status from December 15th, 2017(JST). And based on the inventory status for each region, we will provide new flavors. As a result End of Life (End of support) is set to December 31, 2022.
- End of Marketing：
General Purpose 1/ General Purpose 2/ General Purpose 3/Workload Optimized 1 in Baremetal Server and Dedicated Hypervisor(vSphere/Hyper-V) menu
*It is not the End of Sales of the menu
Name change of Current flavors and sales of new flavor
About name change of Current flavor
Following the start of the new flavor, current flavor name will be changed. So name current flavor as v1.
Name change of current flavors is reflected in the portal display sequentially from April 11th, 2018.
Name change of current flavor
| Current flavor | New name of current flavor |
| General Purpose 1
General Purpose 2 General Purpose 3 Workload Optimized 1 Workload Optimized 2 |
General Purpose 1 v1
General Purpose 2 v1 General Purpose 3 v1 Workload Optimized 1 v1 Workload Optimized 2 v1 |
Release of New Flavors
Based on the inventory status for each region, we will provide new flavors as v2 from first quarter of 2018 (Calendar year). Details schedule will be announced as soon as it is fixed. For inventory status of v1, please contact our sales representative. Part of the specification will be changed compared with v1.
Main specification comparison of v1 and v2
| Item | v1 | v2 | |
| Maker | HPE | Fujitsu | |
| Processor Number | GP1 | E5-2623v3 | E5-2620v4 |
| GP2 | E5-2670v3 | E5-2683v4 | |
| GP3 | E5-2699v3 | E5-2697v4 | |
| WO1 | E5-2623v3 | E5-2637v4 | |
| Processor Base Frequency(GHz) | GP1 | 3.0 | 2.1 |
| GP2 | 2.3 | 2.1 | |
| GP3 | 2.3 | Same as the v1 | |
| WO1 | 3.0 | 3.5 | |
| Number of Cores | GP1 | 4 | 8 |
| GP2 | 24 | 32 | |
| GP3 | 36 | Same as the v1 | |
| WO1 | 4 | 4 | |
| Disk | HDD
(600GB x 2) |
SSD
(480GB x 2) |
|
| Price in JP region
（without TAX） |
GP1 | 114,000 yen | Planning a price equal to v1 |
| GP2 | 230,000 yen | ||
| GP3 | 340,000 yen | ||
| WO1 | 297,000 yen | ||
| Supported OS/Hypervisor | Refer to SD | Partly unsupported* | |
Availability of Official Image Template
| Item | v1 | v2 | |
| Official Image Template | Red Hat Enterprise Linux server 7.1 | Y | – |
| Red Hat Enterprise Linux server 7.3 | Y | Y | |
| Red Hat Enterprise Linux server 7.1 for BYOL | Y | – | |
| Red Hat Enterprise Linux server 7.3 for BYOL | Y | Y | |
| Windows Server 2012R2 Standard | Y | Y | |
| Windows Server 2016 Standard | Y | Y | |
| Windows Server 2012R2 Standard for BYOL | Y | Y | |
| Windows Server 2016 Standard for BYOL | Y | Y | |
| Windows Server 2012R2 Datacenter | Y | Y | |
| Windows Server 2016 Datacenter | Y | Y | |
| Windows Server 2012R2 Datacenter for BYOL | Y | Y | |
| Windows Server 2016 Datacenter for BYOL | Y | Y | |
| VMware ESXi 5.5u3a | Y | – | |
| VMware ESXi 6.0u2 | Y | Y | |
| CentOS 7.1-1503 | Y | Y | |
| CentOS 7.3-1611 | Y | Y | |
| Ubuntu 14.04.1 | Y | Y | |
| Ubuntu 16.04.01 | Y | Y | |
| CoreOS 835.9.0 | Y | – | |
Please refer to the following link (PRIMERGY RX2530 M2 column in OS matrix) when bringing in your own license on v2.
https://sp.ts.fujitsu.com/dmsp/Publications/public/osrel-py.pdf
Mixed-use when using Dedicated Hypervisor menu
Clustering with v1 and v2 mixed is possible in Dedicated Hypervisor menu. For details, please refer to following link.
vSphere ESXi
Hyper-V
https://technet.microsoft.com/en-au/library/dn859550(v=ws.11).aspx
For customers currently using v1
- When changing to v2 or migrating the system for performance improvement, it is necessary for customers to implement migration work.
- Since v1 and v2 have different number of cores, please be careful when you use licenses that depend on the number of cores.