5.5. Enterprise Cloud 2.0 Inter-connectivity (Shared Network Type)¶
5.5.1. Service Menu Overview¶
5.5.1.1. Service Menu Overview¶
The Enterprise Cloud 2.0 Inter-Connectivity service menu allows connectivities between Tenants in the same region.
In the Shared Network Type, we share the logical network with multiple tenants in the same region and provide the function to connect from other tenant’s virtual server and bare metal server.
5.5.1.2. Service Menu Features¶
The Enterprise Cloud 2.0 Inter-Connectivity menu contains the following features and benefits.
Topology free
All tenants within the same region of Enterprise Cloud 2.0 can be freely connected. It is possible to connect between different tenants with different contracts.
Secure connection
Secure connection is realized by agreement of both “source tenant” and “destination tenant”.
Hi-speed connection
Virtual servers and bare metal servers are directly connected to other tenant’s logical networks, enabling high-speed connection equivalent to backbone connection.
On-demand provisioning
This menu provides self-management function that Customer can manage by Customer portal and API.
5.5.1.3. Definition of Terms¶
Source tenant
Tenant which owns virtual servers or bare metal servers as a connection source of Enterprise Cloud 2.0 inter-connectivity.
Destination tenant
Tenant which owns logical network as a connection destination of Enterprise Cloud 2.0 inter-connectivity.
shared network
Logical network which is shared among multiple tenants.
Enterprise Cloud 2.0 inter-connectivity (Shared network privilege)
Privilege to connect and disconnect the resource towards shared network. This privilege is requested from source tenant and approved by destination tenant.
tenant conenction
Resource that represents device connection status between tenants.
5.5.2. Available Functions¶
5.5.2.1. Overall Flow¶
Overall Flow |
Description |
|
|
5.5.2.2. List of Functions¶
Functions |
Function Overview |
|
|---|---|---|
| 1 | The function to apply Enterprise Cloud 2.0 inter-connectivity (Shared network privilege). |
The function to apply shared network privilege from source tenant to destination tenant. |
| 2 | The function to create and delete tenant connection |
The function to connect shared network from source tenant. This function is enabled after the approval of logical network privilege. |
| 3 | The function to delete Enterprise Cloud 2.0 inter-connectivity (Shared network privilege), |
The function to abolish shared network privilege. |
| 4 | Self-Management Function |
This menu provides self-management function that Customer can manage by Customer portal and API. |
5.5.2.3. Description of Functions¶
2. The function to create and delete tenant connection¶
After approving shared network privilege, connection over tenant from virtual server / baremetal server will be implemented.
For the logical network approved with shared network privilege, multiple virtual servers / baremetal servers can be connected without authorization.
Types |
Functions |
Source tenant |
Destination tenant |
|
|---|---|---|---|---|
| 1 | Create |
The function to connect to the shared network from bare metal servers and virtual servers. |
Possible |
Possible |
| 2 | Reference |
shared network |
Possible |
Possible |
Subnet which is associating with shared network |
Possible |
Possible |
||
Port which is created by source tenant. |
Possible |
Impossible |
||
Port which is NOT created by source tenant. |
Impossible |
Possible |
||
List of IP addresses and MAC addresses which are used in shared network. |
Possible |
Possible |
||
| 3 | Edit |
Port which is created by source tenant. |
Possible |
Impossible |
Port which is NOT created by source tenant. |
Impossible |
Possible |
||
| 4 | Delete |
Disconnection of virtual servers or bare metal servers from shared network. |
Possible |
Possible |
4. Self-Management Function¶
The following functions are available for managing Enterprise Cloud 2.0 Inter-Connectivity via the Customer Portal / API.
No. |
Operations |
Operable Actions |
|---|---|---|
| 1 | Apply for Enterprise Cloud 2.0 Inter-Connectivity |
Customer in source tenant can apply shared network privilege. |
| 2 | Edit Enterprise Cloud 2.0 inter-connectivity. |
Customer in source tenant can edit the information of Enterprise Cloud 2.0 inter-connectivity (shared network privilege). |
| 3 | Deletion of Enterprise Cloud 2.0 inter-connectivity. |
Customer in both source tenant and destination tenant can delete approved shared network privilege. |
| 4 | Apply for tenant connection. |
The customer can connect the virtual server and the bare metal server in source tenant to the approved shared network in destination tenant. |
| 5 | Edit tenant connection |
The customer can edit the information of tenant connection. |
| 6 | Deletion of tenant connection. |
The customer can delete connecting tenant connection. |
1. Apply for Enterprise Cloud 2.0 inter-connectivity
Customer in source tenant can apply shared network privilege.
Parameters that can be set are as follows.
Parameter |
Details |
|---|---|
Name |
Input name. |
Description |
Input description. |
Tags |
Input tag information. |
Connected tenant ID |
Input destination tenant ID. |
Logical Network ID |
Input shared network ID. |
2. Edit Enterprise Cloud 2.0 inter-connectivity.
Customer in source tenant can edit the information of Enterprise Cloud 2.0 inter-connectivity (shared network privilege).
Parameters that can be set are as follows.
Parameter |
Details |
|---|---|
Name |
Input name. |
Description |
Input description. |
Tags |
Input tag information. |
3. Deletion of Enterprise Cloud 2.0 inter-connectivity
Customer in both source tenant and destination tenant can delete approved shared network privilege.
4. Apply for tenant connection
The customer can connect the virtual server and the bare metal server in source tenant to the approved shared network in destination tenant.
Parameters that can be set are as follows.
Parameter |
Details |
|---|---|
Name |
Input name. |
Description |
Input description. |
Tags |
Input tag information. |
Device type |
Select from “Virtual Server” and “Bare metal Server” |
DeviceID |
Input DeviceID |
Fixed IP address |
Input interface IP address |
Device interface ID |
(Bare Metal only) Input device interface ID |
Segmentation ID |
(Bare metal only) Input Segmentation ID |
Segmentation Types |
(Bare metal only) Select from “flat” and “vlan”. |
5. Edit tenant connection
The customer can edit the information of tenant connection.
Parameters that can be set are as follows.
Parameter |
Details |
|---|---|
Name |
Input name. |
Description |
Input description. |
Tags |
Input tag information. |
6. Deletion of tenant connection
The customer can delete connecting tenant connection.
5.5.3. Service Menu¶
5.5.3.1. Service List¶
There will be no service plans available for Enterprise Cloud 2.0 Inter-Connectivity.
5.5.3.2. Order Types and Methods¶
The different Subscription Types are as follows.
Order Types |
Order Methods |
Offering Date |
|
|---|---|---|---|
| 1 | Apply for Enterprise Cloud 2.0 inter-connectivity (Shared network privilege) |
Customers’ operation via Customer Portal/API |
Instant delivery |
| 2 | Deletion of Enterprise Cloud 2.0 inter-connectivity (Shared network privilege) |
Customers’ operation via Customer Portal/API |
Instant delivery |
| 3 | Apply for tenant connection. |
Customers’ operation via Customer Portal/API |
Instant delivery |
| 4 | Deletion of tenant connection. |
Customers’ operation via Customer Portal/API |
Instant delivery |
5.5.3.3. Important Things to Note when Ordering¶
5.5.4. Terms And Conditions¶
5.5.4.1. Usage Conditions with Other Service Menus¶
This menu provide the connection from virtual servers and bare metal servers in source tenant and logical network in destination tenant.
5.5.5. Pricing¶
5.5.5.1. Initial Fee¶
There is no initial fee for this service.
5.5.5.2. Monthly Fees¶
There are no monthly fees for this service.
5.5.6. Quality of Service¶
5.5.6.1. Support Coverage¶
The Enterprise Cloud 2.0 support standards are within the coverage of support services.
5.5.6.2. Operations¶
The Quality of Operation for this Service Menu meets the Operation quality of the prescribed Enterprise Cloud 2.0 Standards.
5.5.6.3. SLA¶
This menu follows the standard SLA defined in this service. For details, refer to SLA service description.
5.5.7. Disclaimer¶
By using this menu, all communication between different tenants becomes possible.
At customer’s own risk, please do filtering by configuring firewall rule and routing etc. so that only minimum necessary communication is done.
We are not responsible for any damage to customers or third parties caused in connection with this menu.
5.5.8. Points to Note¶
Common
By using this menu, all communication between different tenants becomes possible. At customer’s own risk, please do filtering by configuring firewall rule and routing etc. so that only minimum necessary communication is done.
Deletion of tenant connection and Enterprise Cloud 2.0 inter-connectivity (Shared network privilege) can be done from both source tenant and destination tenant.
Since there is a menu where rebooting occurs when disconnecting from the logical network, if you want to avoid restarting by operation from other tenants, please design such as connecting with dedicated resource.
Please do not connect with Logical Networks (eg. “common_function_gw_access_ (unique ID)” or connectable NATs) that Enterprise Cloud 2.0 Inter-Connectivity is able to connect to through the Common Function Gateway. Once connected, the services (Backup, NPT etc.) that are available via the Common Function Gateway will become available to other Tenants.
Connection from multiple tenants to the same logical network
By using this menu, you will be connected to the same L2 segment. In addition to unicast communication, communication propagating to the same L2 segment (such as BUM) is also propagated, so please do not connect multiple tenants when it becomes a security problem.
The source tenant who acquired the shared network privilege can check the other tenant IDs connected to the logical network, port name, description, tag etc from the port information. Please do not connect multiple tenants when it becomes a security problem.
Operetion
We may inform the failure information of the connection partner (opposite tenant) for early identification of the fault location and recovery.
When trouble is detected in our tenant of the connection source tenant or the connection destination tenant, Service Provider will not notify failure information to the connection partner (opposite tenant).