5.1.8. Enterprise Cloud 2.0 Inter-Connectivity(Network Shared type)¶
5.1.8.1. Overall¶
Enterprise Cloud 2.0 Inter-connectivity is a menu that provides a function to connect any tenant.
For the network-shared type, a logical network is shared by multiple tenants within the same region, and a function is provided that makes connections from other tenants' virtual server, bare metal server, and firewall (vSRX).
Terms used in this tutorial are defined as below.
Source tenant
Tenant that possesses a virtual server, bare metal server, and firewall (vSRX) from which Enterprise Cloud 2.0 Inter-connectivity are made
Destination tenant
A tenant existing a logical network to which the Enterprise Cloud 2.0 Inter-connectivity is connected.
Shared Network
Logical network on the destination tenant to be connected for Enterprise Cloud 2.0 Inter-connectivity.
Enterprise Cloud 2.0 Inter-connectivity(Shared network privilege)
Authority to connect / disconnect to shared network. Apply for and acquire from the source tenant to the destination tenant.
Tenant connectivity
Resource that represents device connection status between tenants.
5.1.8.2. Enterprise Cloud 2.0 Inter-connectivity application¶
At the time of application, click SD-Exchange" category → "Cloud/Server Between Tenants Connect" on the Control panel of the Customer portal of the source tenant."
Click on {Application for Between Tenants Connect}, and you will directed to the page as seen in the figure below.
By using this menu, all communication between different tenants becomes possible. Please check the notes and click next" if there is no problem."
Next, enter basic information on this Enterprise Cloud 2.0 connection and click Next"."
Finally, enter the tenant information of the connection destination and click the Application for Between Tenants Connect" button to apply."
The following is a list of the required information that you must enter.
Category |
Parameter |
Details |
|---|---|---|
Basic Information |
Name |
Set name. |
Description |
Set description. |
|
Tags |
Set tag information. |
|
Connection Destination Information |
Tenant ID of destination tenant. |
Set the ID of the tenant you want to connect. Both the same contract and different contracts can be specified. |
Logical network ID |
Set the Logical Network ID to apply for shared network rights. |
When the application is completed, the resource is displayed with status registered”."
5.1.8.3. Approval of Enterprise Cloud 2.0 Inter-connectivity¶
After {Application for Between Tenants Connect} is complete, the number of approval requests received is displayed in the {Approval Requests Inbox} of the Connection Destination's dashboard.
Click "List" to check the list of received permission requests.
Click on the appropriate {Request ID} in order to check the details of the receieved request information, then click {Approval} once confirmed.
A confirmation pop-up screen will appear regarding the approval of the approval request, click {OK} once confirmed.
5.1.8.4. Inter-tenant connection setting¶
To add an attached device to the Logical Network that acquired the shared network usage permission, click SD-Exchange" category → "Between Tenants Connect” on the control panel of the customer portal of the source tenant."
Click on the target Between Tenants Connect” → "Create tenant-to-tenant connection", the creation screen of the tenant inter-connectivity will be displayed."
First, enter the basic information on the tenant-to-tenant connection and click Next"."
Next, when you enter the connection source device information and click Create tenant inter-connectivity", connection between tenants will be carried out."
Be careful that the items to be entered differ depending on whether the connection source device type is a bare metal server, virtual server, or firewall (vSRX).
For Baremetal server
For Virtual server
For firewall (Juniper vSRX)
The following is a list of the required information that you must enter.
Category |
Parameter |
Details |
|---|---|---|
Basic Information |
Name |
Input name |
Description |
Input description |
|
Tags |
Input tag information |
|
Device type |
Selecting from among virtual server, bare metal server, and vSRX |
|
Device information |
Device ID |
Input the device id to be connected |
Auto IP address acquisition |
With checked, the fixed IP address of connection interface is automatically assigned. With unchecked, an arbitrary IP address is to be specified for the fixed IP address item. |
|
Static IP address |
Input static IP address assigned to connected interface |
|
Device interface ID |
Enter a connection device interface ID (bare metal server and firewall (vSRX) only). |
|
Segment ID |
(Only for baremetal server) Input connected segment ID |
|
Segment Types |
(Only for baremetal server) Select from flat and vlan |
Note
For details about a virtual server, refer to Service manual Virtual server .
It is recommended to add interface, with the instance halted.
If the instance is started or switched off then on (also restart by the HA function) with interface addition/deletion or volume attachment/detachment performed, the data volume may turn to off-line or the device name of the interface may be changed.
Once the instance is switched off then on(*1), this phenomenon does not occur again unless interface addition/deletion or volume attachment/detachment are newly performed. Therefore, if the phenomenon occurs, switch the interface off then on, and check that the interface and volume status do not change. (In the case where interface addition/deletion or volume attachment/detachment are performed with the instance halted, the instance does not need to be switched off then on after it is restarted.)
*1 After executing shutdown on the OS and checking that the instance has been placed into halt status, restart the instance through the portal or API. (Note that restart on the OS does not result in job execution.)
5.1.8.5. Refer information¶
The status of Enterprise Cloud 2.0 Inter-connectivity be checked in following way.
Enterprise Cloud 2.0 connection list (own tenant = source tenant)
You can check the list of Enterprise Cloud 2.0 Inter-connectivity you applied from your own tenant.
Enterprise Cloud 2.0 connection list (own tenant = destination tenant)
You can see a list of Enterprise Cloud 2.0 Inter-connectivity that accepted network sharing requests from other tenants.
The connection status of tenant connection can be checked below.
To view the list of devices in connection, select the target "Between Tenants Connect " tab.
5.1.8.6. Inter-tenant connection deletion¶
When deleting, click SD-Exchange" category → "Between Tenants Connect" on the control panel of the customer portal of the source tenant and destination tenant."
To view the list of devices in connection, select the target "Between Tenants Connect " tab.
To disconnect the device, click the target Delete tenant connection" and a pop-up confirmation of deletion will appear. If there is no problem, click "Delete tenant connection”."
5.1.8.7. Delete Enterprise Cloud 2.0 Inter-connectivity¶
To delete the Between Tenants Connect, click Delete Enterprise Cloud 2.0 Inter-connectivity.
If there is no problem, click Delete tenant connection” on pop-up window."
5.1.8.8. Supplement: Status description of resources¶
Possible kinds of status of resources created or deleted through Enterprise Cloud 2.0 Inter-connectivity services are described below:
Enterprise Cloud 2.0 Inter-connectivity (tenant_connection_request)¶
For Enterprise Cloud 2.0 connection resources (wording on API: "tenant_connection_request" resource), the possible kinds of status are as follows:
As for the status of an Enterprise Cloud 2.0 Inter-connectivity resource, the status of the following has been reflected: Allowed function .
Only when the Enterprise Cloud 2.0 Inter-connectivity resource has been approved, an inter-tenant connection resource can be created. As long as related inter-tenant connection resources exist, an Enterprise Cloud 2.0 Inter-connectivity resource cannot be deleted. To delete an Enterprise Cloud 2.0 Inter-connectivity resource, delete all related inter-tenant connection resources beforehand.
Status wording (Wording on API) |
Resource status |
|---|---|
Registered |
Status immediately after a connection source tenant sends an application to a connection destination tenant |
Approved |
Status with the application approved by a connection destination tenant
An inter-tenant connection resource can be created.
|
Denied |
Status with the application declined by a connection destination tenant or with the response due passed without approval |
Cancelled |
Status with the application canceled by a connection source tenant |
Unavailable |
Status with an applied logical network deleted |
Inter-tenant connections (tenant_connection)¶
For inter-tenant connection resources (wording on API: "tenant_connection" resource), the possible kinds of status are as follows:
As for the status of an inter-tenant connection resource, the status of the following has been reflected: "Port of Logical network .
Status wording (Wording on API) |
Resource status |
|---|---|
Active |
The port is in active status. |
Down |
The port is in down status. |
Monitoring_unavailable |
The port status failed to be checked. |
Error |
The port is in error status. |
Creating |
An inter-tenant connection resource is being created.
The port status may be creation in process (PENDING_CREATE).
|
Updating |
An inter-tenant connection resource is being updated or the port status is update in process (PENDING_UPDATE). |
Deleting |
An inter-tenant connection resource is being deleted.
The port status may be deletion in process (PENDING_DELETE).
|
Disconnected |
Status with inter-tenant connections disconnected
The port may have been deleted or disconnected.
|
Inconsistent |
Inconsistency has occurred at the time of inter-tenant connections.
The port may have been connected with a device which differs from the connection source device specified at the time of inter-tenant connection setting.
|