Region/Zone/Group

Purpose of This Document

This document describes the definition of Region, Zone and Group, which are the resource accommodation units.


Overview

Customers can configure up to three tiers of location information for each menu as follows:

概念図

Image of Region, Zone and Group


Region

Details

Region is the superordinate concept of Zone, and can have multiple Zones underneath one Region.

This means “1 Region = n Zones”. Zone does not cross over Regions.

Region is a unit of administrative system in this service and mentions collectible unit of countries or regions mainly(*1).


Note

*1: Please note the unit does not guarantee to separate to country or region.

Please refer to “Zone/Group in Each Region” which stated below for details information like location in each region.


リージョンのイメージ

Image of Region


What Customers Can Do

As mentioned previously, Region is a collectible unit of countries or regions.

Therefore, it becomes possible for Customers to cope with large-scale disaster at the levels of countries or region.

Furthermore, if the region differs, management system unit is also differ.

By dividing Regions, Customers can design independent systems on their own at the Region level.


Zone

Details

Zone is the subordinate concept of Region, and the superordinate concept of Group. There are multiple Zones within one Region, and one Zone can have multiple Groups underneath itself.
In other words, following equations logically make sense in essence, “1 Region = n Zones”, “1 Zone = n Groups”.
Zones never cross over their Regions. Moreover, Groups do not cross over their Zones.
Zone primarily is a unit of a group of building housing infrastructure.

Image of Zones

ゾーンのイメージ

What Customers Can Do

As mentioned, Zone means the group of buildings housing infrastructure. By dividing zone, Customers can distribute the buildings by themselves. This enables Customers to realize the countermeasure for the building-level of disasters.


Group

Details

Group is the subordinate concept of Zone. There are multiple Groups within one Zone. It means “1 Zone = N Groups”. Group means the set of infrastructures. Services which can select Group can select group of infrastructures. Group usually means set of goup of servers, switches or storages.

グループのイメージ

Image of Groups


What Customers Can Do

As mentioned, Group is the set of infrastructures, so Customers can distribute their accommodated servers and switches by dividing a Group, By doing so, they can activate to cope with the physical failures and errors of servers or switches.


Difference of Groups in among Baremetal Server Menu, Virtual Server Menu and Storage Menu

This Note complements the difference of concept of Groups in among Baremetal Server Menu, Virtual Server Menu and Storage Menu.

Group in Baremetal Server Menu

Group in Baremetal Server is the unit of infrastructure which consists of multiple switches.
Customers can select one Group out of multiple Groups.
By dividing Groups, Customers’ Baremetal Servers are always connected to physically different swithes.
(If Customers configure Baremetal Server into the same Group, then Baremetal Server can be connected to the same switch.)
As such, this enables Customers to provision their system with physically-redundant switches.
ベアメタルサーバーメニューにおけるグループ

Group in Baremetal Server Menu

Group in Virtual Server Menu

Group in Virtual Server is the unit of infrastructure which consists of multiple physical servers.
Customers can select one Group out of multiple Groups.
By dividing Groups, Customers’ Virtual Servers are always deployed within the different physical servers.
(If Customers create Virtual Server in the concurrent Group, then Virtual Server could be created in the con current Physical Server.)
As such, this enables Customers to provision their system with physically-redundant servers.
仮想サーバーメニューにおけるグループ

Group in Virtual Server Menu


Group in Storage Menu

Group in Storge is the unit of infrastructure which consists of multiple storages.
Customers can select one Group out of multiple Groups.
By dividing Groups, Customers’ Storage are always deployed within the different physical storages.
(If Customers create Storage in the concurrent Group, then Storgae could be created in the con current Physical Storage.)
As such, this enables Customers to provision their system with physically-redundant storages.
ストレージメニューにおけるグループ

Group in Storage Menu


Redundant configuration using multiple groups

  • In this service, two groups (Group A, Group B) are provided for one zone, and we recommend that you configure a group A and a group B when forming a redundant configuration within a zone.
    NOTE: Because redundant configuration within a single group may be accommodated in the same facility (switch, physical host, storage).
  • With this service, there is a possibility to provide Group C, D, E, F, G ... for reasons such as difficulties in reinforcing within Group A or Group B.
    In this case, we recommend grouping redundancy with “Group A, C, E ...” and “Group B, D, F ...”.
    NOTE: Redundant configuration in group A, C, E ... and “Group B, D, F ...”, Distributing accommodation facilities (switches, physical hosts, storage) if the group differs Although it is possible to do, there is a possibility that construction time concerning accommodation facilities will be the same.
    In this service, for periodic maintenance, construction will be carried out in the time zone defined by Maintenance Window We do,
    For the construction time to be carried out in the maintenance window (the time during which you actually work and may be affected)
    We plan to avoid duplication between “Group A, C, E ...” and “Group B, D, F ...”.
    For this reason, when a redundant configuration is formed with “Group A, C, E ...” and “Group B, D, F ...”, scheduled maintenance work time for accommodating facilities (switches, physical hosts, storages) can
複数グループで冗長構成を組む際の推奨構成

Recommended configuration for configuring redundant configuration with multiple groups


Note : Tenant

Details

When creating resource, Tenant is the highest concept Customers need to set, and is like a workspace.
It is not accommodation unit but the unit of User Permission Groups; i.e., this is conceptually different from the infrastructure accommodation unit of Region / Zone / Group.
Fundamentally, in order for Customers to utilize respective services, they are required to create Tenants. And underneath the Tenants comes Resource in creation (although there may be exceptional cases).
in case of creating Tenant, customers need to specify Region Tenant belongs to.
Cusotmer can create more than one tenant in one Region but Customer can not create a tenant across regions.
Bacause the scope of Tenant is as same as Region, Customer can create resources in one Tenant(=Region) evenif the resources is not located same Zones/Groups.
テナントのイメージ

Image of Tenants


Designable Unit for Respective Menu

Following is the list of units that is designable to Respective Menu:

Menu

Region

Tenant

Zone

Group

<Common function>

       

Tenant

Y N N

<Server>

       

Baremetal Server

N *1

Y Y Y

Virtual Server

N *1

Y Y Y

Image Storage

N *1

Y N N

<Storage>

       

Block Storage (I/O Performance)

N *1

Y Y Y

FileStorage(Premium)

N *1

Y Y Y

File Storage(Standard)

N *1

Y Y Y

<Network>

       

Logical Network

N *1

Y N N

Internet Connectivity

N *1

Y Y N

Firewall(vSRX)

N *1

Y Y Y

Firewall (Brocade 5600 vRouter)

N *1

Y Y Y

Load Balancer(NetScaler VPX)

N *1

Y Y Y

VPN Gateway

N *1

Y Y N
<SD-Exchange>        

CIC Inter-Connectivity

N *1

Y Y N

Enterprise Cloud 1.0 Interconnectivity(EIC)

N *1

Y Y N

Enterprise Cloud 2.0 Interconnectivity

N *1

Y N N

Amazon Web Services Interconnectivity

N *1

Y N N

Google Cloud Platform Inter-Connectivity

N *1

Y N N

Microsoft Azure Inter-connectivity

N *1

Y N N

Datacenter Inter-Connectivity

N *1

Y Y N

<Backup>

       

Backup (Location where stored Backup file)

N *1

Y N N

<Security>

       

Network-based Security

N *1

Y Y Y

<Platform Service>

       
Cloud Foundry

N *1

Y N N
DNS

N *1 *2

Y N N
Fast DNS

N *1

Y N N
Power Systems

N *1

Y N N
Hybrid Cloud with Microsoft Azure

N *1

Y N N
Hybrid Cloud with GCP

N *1

Y N N

Rancher(Docker Container Management)

N *1

Y N N
Global Server Load Balance(Global Traffic Management)

N *1 *2

Y N N
WebRTC Platform SkyWay

N *1 *2

Y N N

<Management>

       
Monitoring

N *1

Y N N
Monitoring Logs

N *1

Y N N
*1:Customers cannot assign a Region directly, but by assigning Tenants, they can specify the Region they would like to in essence.
*2: This service does not have the concept of Region, however, Customer need to select tenant because each service is required to belong to any Region.

Note

As for the menu that Customers can assign up to Group, suchu as Baremetal Server, Virtual Server and Block Storage (Provisioned I/O Performance), they can assign both Zone and Group by selecting hyphen-connected parameters in pairs such as “zoneX - groupX” when they select from the list of “Zone/Group”. For example, Zone and Group selected at “zone1-groupa” means the Customers will be accommodated at Group A in Zone 1 and “zone1-groupb” means the Customers will be accommodated at Group B in Zone 1.


Zone/Group in Each Region

Following is the information of Zone and Group in each Region:

Country

Area

Region Name

Zone Name

Datacenter

Group Name

Japan

East Japan

JP1*

Zone 1

Saitama No.1 Data Center

Group A

         

Group B

    JP4

Zone 1

Tokyo No.10 Data Center

Group A

         

Group B

    JP5

Zone 1

Tokyo No.2 Data Center

Group A

         

Group B

 

West Japan

JP2

Zone 1

Osaka No.5 Data Center

Group A

         

Group B

       

Osaka No.1 Data Center

Group C

         

Group D

U.S.

East Coast of U.S.

US1

Zone 1

Virginia Ashburn1 (VA1) Data Center

Group A

         

Group B

UK

UK

UK1

Zone 1

UK Hemel Hempstead2

Group A

       

UK Hemel Hempstead3

Group B

Germany

Germany

DE1

Zone 1

Germany Frankfurt 1 Data Center

Group A

         

Group B

         

Group C

         

Group D

France

France

FR1

Zone 1

France DATA4 Data Center

Group A

         

Group B

Singapore

Singapore

SG1

Zone 1

Singapore Serangoon Data Center

Group A

         

Group B

Hong Kong

Hong Kong

HK1

Zone 1

Hong Kong Financial Data Center

Group A

         

Group B

Australia

Australia

AU1

Zone 1

Australia Sydney 1 Datacenter

Group A

Others

JP3

Zone 1

JP3 region is available for the limited users.

Group A

         

Group B


Warning

*Creating new tenant in JP1 Region is stopped since 26th April 2018.
Please see News on Knowledge Center for details.

Note

Note: Area
In this service, the set of infrastructure when creating resources in Region/Zone/Group, and Region is the set of management system.
By dividing Regions, Customers can design independent systems on their own.
However, Region guarantees to separate not country or region but management system.
For complementing to information of geographical location, Area describes Region where country of region belongs to.
By dividing Area, Customers design separate their resource into multiple geographical location lilke countries or regions.