Stud I/O Cloud Docs

Appearance

Networking ​

I/O Cloud Networking enables you to create rich network topologies to connect your instances to each other and to the internet. It is built on OpenStack Neutron, providing software-defined networking (SDN) capabilities.

Virtual Networks ​

Your cloud environment is isolated within your own Virtual Private Cloud (VPC).

  • Isolation: Tenant networks are fully isolated from one another using encapsulation protocols like VXLAN or Geneve. This ensures that your traffic remains private and secure, even within the shared infrastructure.
  • Subnets: You can define one or more subnets within your networks to manage IP addressing (IPv4 and IPv6) for your instances.

Routing and Connectivity ​

Alpha / Beta Notice

During the Stud I/O Cloud private alpha / beta, your primary router — the one with the default gateway to the public internet — is added to the project upon request, and a set of Floating IPs can be allocated to your project upon request.

Therefore, the primary router and Floating IPs described below are not yet available for self-service management.

A second, internal-only router is different: connecting to internal platform services (like Shared File Storage or the DNS resolver below) is fully self-service today. See Connect to Internal Platform Services.

  • Routers: Virtual routers connect your internal subnets to external networks. They act as gateways, allowing your instances to access the internet or other private networks.
  • Floating IPs: To make an instance accessible from the public internet, you associate a "Floating IP" with it. This is a public IP address that maps to the instance's private IP, allowing inbound traffic.

DNS ​

Once an instance is connected to internal platform services, it can resolve a DNS zone that you own and that stays in sync with your own instances' IP addresses, alongside normal internet DNS through the same resolver. See DNS for how this fits together, and Manage DNS for Your Instances to set it up.

Security ​

Security is a core component of the networking layer.

  • Security Groups: These act as a virtual stateful firewall for your instances. You define rules to allow specific types of ingress (incoming) and egress (outgoing) traffic (e.g., allow SSH on port 22 or HTTP on port 80).
  • Default Policy: By default, all inbound traffic is blocked, and all outbound traffic is allowed, until you explicitly add rules.