Servers
A BareMetal server is a physical server connected to the network via two or more 1 Gbps, 10 Gbps, or 25 Gbps network interfaces. Its hardware and network resources are physically isolated and can be accessed only by their lessee.
The server can be provided to the user in one of the stock configurations, a custom configuration built as per the user's specification, or an on-request configuration with individual hardware properties.
Warning
BareMetal servers use optimal BIOS
At the hardware level, BareMetal servers are managed by a baseboard management controller (BMC) via the IPMI
Modifying BMC settings by the user will lead to the following:
- Server management via the KVM console will be unavailable.
- You will be unable to stop, start, or restart the server using the management console
, Yandex Cloud CLI, or API. - You will be unable to reinstall the server OS.
- You will be unable to view server hardware health metrics (processor temperature, fan speed, etc.)
Alert
If the user modifies BMC settings, Yandex BareMetal cannot guarantee the correct operation of the KVM console and other server management tools.
Renting servers
You can rent a stock configuration server for one day, one month, three months, six months, or one year. You can view rentable configurations in each pool when ordering a server in the management console
You can rent a custom-configured server for one month, six months, or one year.
The terms and conditions of renting an on-request configuration are determined on a case-by-case basis.
Server access
You can manage a server using the KVM console, which is available from the management console
Server pools
Pools are infrastructurally separate data center modules servers physically reside in. Pools are distributed across availability zones located in regions. Currently, Yandex BareMetal is only available in the Russia region.
| Region | Availability zone | Pools |
|---|---|---|
ru-central1 |
ru-central1-m |
ru-central1-m3ru-central1-m4 |
Redundant power supply for servers
When leasing a sever, you can select your configurations based on redundant power supply type:
- Servers with one power supply unit (
1 PSU). - Servers with two or more power supply units (
2+ PSU). - Open Compute Project (OCP)
servers. These servers share a redundant power bus between all servers in the same rack instead of using individual power supply units.
Server network interfaces
Any BareMetal server configuration includes at least two network interfaces
- Only to private subnets (
PRIVATE). - Only to public subnets (
PUBLIC). - Both to private and public subnets (
PUBLIC,PRIVATE).
In each BareMetal server:
- One of the network interfaces is always capable of connecting to public subnets.
- One of the network interfaces is always capable of connecting to private subnets.
If a server network interface supports connection both to private and public networks, you can switch between these network types for that interface. For more on changing network type for a network interface, see Switching the type of a network connected to a network interface.
Alert
When switching the type of a network attached to a network interface, the physical interface remains connected to the same Leaf-level switch it was previously connected to. This means that if you replace a public network with a private one on the interface, access to the private network via this interface will be routed through the same switch that handles the public network interfaces of other servers in the same data center rack.
Consequently, if this switch fails or a network attack targets any server in the rack, private network traffic passing through this modified interface may be disrupted or restricted.
This limitation does not apply to servers with MC-LAG network redundancy.
A server can have more than two network interfaces:
-
In configurations with 10 Gbps and 25 Gbp NICs, in addition to the primary (high-speed) network interfaces, server diagnostic tools may display two more (inactive) network interfaces.
These inactive interfaces belong to the integrated NICs of the server motherboard. They are not connected to any networks and do not require any configuration.
-
In configurations with the MC-LAG network connection redundancy, the server uses not one but two network interfaces at once to connect to each of the networks.
Network interfaces connected to the same network are combined into aggregation groups at the OS level, which increases the network connection speed and ensures fault tolerance.
You can attach several private subnets to the server's network interface (or MC-LAG aggregation group) connected to a private network at the same time. For more on adding additional private subnets, see Setting up a secondary private subnet with a tagged VLAN on a server.
Server statuses
A server can have one of the following statuses:
PROVISIONING: Server is being prepared to be issued to the user. You get your stock configuration server within anywhere from 30 seconds to several minutes. A custom-configured server takes up to four calendar days to be built and started.RUNNING: Rented server is fully available to the user. In this status, the server's power supply can be turned on or off.STARTING: Server is being powered up.STOPPING: Server is being powered down.RESTARTING: Server is rebooting.REINSTALLING: Server operating system is being reinstalled.UPDATING: Server or network settings are being updated.QUARANTINING: Server is being quarantined.QUARANTINED: Server is quarantined. Users cannot access quarantined servers over the network or through a KVM console.RETURNING_FROM_QUARANTINE: Server is returning from quarantine, with access being restored over the network and through a KVM console.DELETING: Server deletion is in progress. It may take several hours to completely delete the server and wipe all disks.ERROR: Error has occurred, the KVM console is unavailable. Contact support .
Quarantine
Quarantine: A transition state before server rent is fully terminated. In this state, the server is still listed in the user's directory. Users cannot access quarantined servers over the network or through a KVM console, but the server retains all user data and settings. The quarantine period is 72 hours. Following this period, the settings and data get completely deleted from the server, and the server itself gets removed from the user's directory.
At any time during the quarantine period, you can restore the server for further use. For more information, see support
Note
Servers with the QUARANTINING, QUARANTINED, RETURNING_FROM_QUARANTINE, or DELETING status are counted towards the total quota for the number of servers.
Servers with the QUARANTINING, QUARANTINED, RETURNING_FROM_QUARANTINE, or DELETING status are not billable.
If a server is restored for further use during the quarantine period, its quarantine time will be included into the paid rent period.