Region/Zone/Group¶
Purpose of This Document¶
This document describes the definition of Region, Zone and Group, which are the resource accommodation units.
Note
Overview¶
Customers can configure up to three tiers of location information for each menu as follows:
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.
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¶
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.
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 Virtual Server Menu¶
Group in Storage Menu¶
Note
Wasabi object storage is not included in the group concept above.
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
Note : Tenant¶
Details¶
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 |
<Security> |
||||
Network-based Security |
N *1 |
Y | Y | Y |
<Platform Service> |
||||
Cloud Foundry | N *1 |
Y | N | N |
DNS | 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) | Y | N | N | |
WebRTC Platform SkyWay | Y | N | N | |
<Management> |
||||
Monitoring | N *1 |
Y | N | N |
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 |
|||||
JP7 | Zone 1 |
Tokyo No.11 Data Center |
Group A |
||
Group B |
|||||
Group C |
|||||
West Japan |
JP2 | Zone 1 |
Osaka No.5 Data Center |
Group A |
|
Group B |
|||||
Osaka No.1 Data Center |
Group C |
||||
Group D |
|||||
JP6 | Zone 1 |
Kinrakuji Data Center |
Group A |
||
Group B |
|||||
Others |
- | JP3 | Zone 1 |
JP3 region is available for the limited users. |
Group A |
Group B |
Note
For this service, the storage unit for creating various resources is region/zone/group.As mentioned previously, regions are units of the management system.By separating regions, you can distribute the impact of your management system, but because regions are only a unit of management system, different regions can have the same country or region.On the other hand, in order to supplement the geographical concept, the units of countries and regions to which each region belongs are classified as “Area” and are shown in the table above.By separating areas, customers can take disaster countermeasures and distribute them at the national and regional levels.
Note