Neurocloud concepts

Prev Next

Available in VPC

This document describes the network configuration of Neurocloud.

Note

Configurations of Neurocloud's network and management network may differ by client because they are determined through separate consultations with the clients.

Configuring network

There must be a logical network configuration between the Neurocloud and on-premise networks. The following are examples of configurations of a development VPC and a service VPC with diagrams.

neurocloud-info_networkconfig_ko

  • Physical connection through the BL (boarder leaf) switch at the very top of the Neurocloud network and the customer device (backbone switch) of the on-premise network.
  • Connected to the subnets of the on-premise network through communication routes where there is one on-premise gateway per Neurocloud VPC.
  • Neurocloud's public subnets are connected to the on-premise network through the internet gateway and access the internet through the external network access route provided by the client's data center.
  • Neurocloud's private subnets are connected to the on-premise network through the NAT gateway and access the internet through the external network access route provided by the client's data center.
  • Multiple logically isolated VPCs can be created in the Neurocloud network, and subnets can be subcategorized by their use.

The following are the network services available in this Neurocloud:

Component Icon Detailed description
VPC Service that provides the client with a dedicated private network that is in complete logical separation from the public cloud environment
  • Provides an IP network space of up to /16 (IP band: RFC 1918)
Subnet Feature that allows you to sub-divide the network space of VPC according to the purpose
  • Addresses /16 - /28 can be allocated
  • Public subnets are connected to the internet through the internet gateway
  • Private subnets are created if there is no connection to the internet gateway
NAT Gateway Gateway used by private subnets for external communication. IP address exposure is minimized
Router Feature to set the network route
ACG Controls inbound and outbound traffic of the server. Operation is Stateful-based
NACL Controls inbound and outbound traffic of the subnet. Operation is Stateful-based
On Premise Gateway Logical interface for communication between the client's on-premise network and the Neurocloud VPC
VPC Peering Endpoint guaranteeing private connection between VPCs
Note

For more information on how to use the components, see VPC use guide.

Configuring Neurocloud's management network

Neurocloud is managed on Neurocloud's dedicated platform management system included in the client's site installation tools. To receive remote management by NAVER Cloud Platform's expert, you need to connect a dedicated cable for the management network. Through the management network, you can apply updates and patches to manage the Neurocloud platform and maintain the platform S/W to the latest version. The following is an example of the Neurocloud management network shown in a diagram.

neurocloud-info_mgmtnetconfig_ko

Note
  • You cannot access the client's data center network through the management network.
  • Even when the dedicated cable for the management network is disconnected, Neurocloud's infrastructure operates normally.