Skip to main content

Cloud resources

Besides servers, Arianet Cloud has other resources, each with its own page in the cloud menu. This page explains, step by step, how to create, attach, edit and delete each of them. For creating and managing the server itself, see Arianet Cloud.

What every resource has in common​

  • Create: on each resource's list page, click the "… new" button («… جدید»), or use the Create («ساخت») button in the top bar. The create page has numbered sections, and the Summary («خلاصه») box at the side shows your choices and the cost. The create button is at the bottom of that box.
  • Name: English letters, digits, dots and dashes only; up to 63 characters, starting and ending with a letter or digit.
  • Labels: key/value pairs such as env=prod for grouping and searching.
  • Project: every resource is created in a project. Later, move it from its page with Move to another project («انتقال به پروژهٔ دیگر»). Only that resource moves, and its cost is attributed to the new project from that moment.
  • Delete protection: while it is on, the resource cannot be deleted from the panel or the API.
  • Delete: the delete button takes you to the delete page, which shows a summary of the resource and what deleting it does. Type the resource's name and click Delete forever («حذف برای همیشه»). If something blocks the delete (for example delete protection or being attached to a server), the page says so.
  • Activity: every resource has an Activity («فعالیت‌ها») tab or section listing all its operations.
tip

Costs are deducted hourly from your wallet, and the monthly amount is based on 730 hours. The exact price of each resource in the chosen data center is shown on its create page.

Load balancer​

A load balancer gives you one fixed address and spreads users' requests across several servers. It detects failed servers with health checks and sends them no traffic until they are healthy again, so your site stays up when one server goes down.

When to use it: when a site or service runs on several servers, when you want to replace or update servers without downtime, or to spread an internal service (for example a database) across servers on a private network.

Creating a load balancer​

Open Networking → Load balancers («شبکه ← لود بالانسرها») and click New load balancer («لود بالانسر جدید»).

  1. Data center («دیتاسنتر»): the load balancer connects only to servers and networks in this data center.
  2. Load balancer type («نوع لود بالانسر»): each type's card shows its limits (up to … services, up to … targets, … concurrent connections per service) and its monthly and hourly price. A type not offered in that data center is disabled with "not offered in this data center" («در این دیتاسنتر عرضه نمی‌شود»).
  3. Name («نام»): to recognize it in the list.
  4. Project («پروژه»)
  5. Load balancing algorithm («الگوریتم توزیع بار»):
    • Round Robin («چرخشی (Round Robin)»): requests go to all healthy targets in turn; for targets of equal capacity.
    • Least Connections («کمترین اتصال (Least Connections)»): each new connection goes to the target with the fewest open connections; better for long or uneven requests.
  6. Network («شبکه»):
    • Public interface («رابط عمومی (آدرس IPv4/IPv6 اینترنتی)»): on means users connect from the internet to the load balancer's public address. Off means it only gets an address inside a private network and is not reachable from the internet.
    • Private network («شبکهٔ خصوصی»): optional with a public interface, required without one. With a network, the load balancer reaches servers on their private addresses and internal traffic never crosses the internet.
  7. Services («سرویس‌ها»): click Add service («افزودن سرویس»); see Services and health checks. Without a service the load balancer passes no traffic.
  8. Targets (optional) («اهداف»):
    • Cloud servers («سرورهای ابری»): servers of this account in this data center.
    • Reach servers on their private address («رسیدن به سرورها با آدرس خصوصی»): the servers must be on the chosen private network.
    • Public IP addresses («آدرس‌های IP عمومی», public interface only): for servers outside this data center; type each address and press Enter.
  9. Labels (optional) («برچسب‌ها»)

The Order summary («خلاصهٔ سفارش») box shows the data center, type, access, number of services and targets, and the monthly and hourly cost. Click Create load balancer («ساخت لود بالانسر»). Creation takes a few minutes, and you can close the page meanwhile.

caution

The public interface cannot be changed after creation. A load balancer created without one always stays internal.

Services and health checks​

Each service is a port on the load balancer that is forwarded to a port on the target servers. The Add service window has three parts.

Protocol and ports («پروتکل و پورت‌ها»)

FieldDescription
Protocol («پروتکل»)TCP: any protocol over TCP (databases, SSH, mail…); the load balancer does not read the content. HTTP: unencrypted web, with cookie-based sticky sessions and HTTP health checks. HTTPS (TLS passthrough) («HTTPS (عبور TLS)»): encrypted traffic reaches the servers without being opened.
Listen port («پورت ورودی»)The port users connect to on the load balancer's address (1–65535). Two services cannot share a listen port.
Destination port («پورت مقصد»)The port your application listens on on the target servers.
PROXY protocol («پروتکل PROXY»)TCP and HTTPS only. Sends the user's real address at the start of the connection. Turn it on only if your application (for example nginx with proxy_protocol) understands it, otherwise connections break.

Sessions and redirect («نشست و تغییر مسیر», HTTP and HTTPS)

  • Sticky sessions («چسبندگی نشست (Sticky Sessions)»): each user returns to the server they first reached. With HTTP this uses a cookie; with HTTPS, since the content is encrypted, it uses the user's IP address.
  • Application cookie name (optional) («نام کوکی برنامه (اختیاری)», HTTP with sticky sessions only): if empty, the load balancer sets its own cookie; if you enter your application's session cookie name (for example PHPSESSID), stickiness follows that cookie. The cookie lifetime cannot be set.
  • Redirect HTTP to HTTPS («تغییر مسیر HTTP به HTTPS», HTTPS only): unencrypted requests on port 80 are sent to the HTTPS address with a 301. Enter the Site domain («دامنهٔ سایت», for example example.com). Port 80 is taken for this and counts as one service against the type's limit.
note

The load balancer does not terminate TLS (TLS passthrough). The certificate stays installed on the target servers; installing a certificate on the load balancer is not supported.

Health check («بررسی سلامت»)

FieldDefaultDescription
Check method («روش بررسی»)HTTP for an HTTP service, otherwise TCPTCP (port open) or HTTP (page response)
Check port («پورت بررسی»)destination portEmpty means the destination port.
Check interval, seconds («فاصلهٔ بررسی (ثانیه)»)153 to 300
Response timeout, seconds («مهلت پاسخ (ثانیه)»)10at least 1 and not more than the interval
Retries («تعداد تلاش»)31 to 10; failed answers in a row before a server counts as unhealthy

The HTTP method also has:

  • Path («مسیر»): starts with / and has no spaces; default /.
  • Domain (Host), optional («دامنه (Host) - اختیاری»): for example example.com.
  • Accepted status codes («کدهای وضعیت قابل قبول»): three digits such as 200 or a class such as 2??; default 2??, 3??. Combine classes only if consecutive (2?? and 3??), or use single codes only.
  • Check over HTTPS («بررسی روی HTTPS»): the check request is sent over TLS and the server's certificate is not verified.

Click Add service («افزودن سرویس»), or Save service («ذخیرهٔ سرویس») when editing.

caution

The target servers' firewall must allow the load balancer to connect to the destination port and the health check port; otherwise the target stays unhealthy and gets no traffic.

The load balancer page​

Click a load balancer in the list to open its page. The header shows the name (with a rename button), status, type, project, data center, IPv4, IPv6, private address and the number of services and targets.

SectionWhat it does
Overview («نمای کلی»)Addresses and ID, target health («سلامت اهداف»: healthy, unhealthy, unknown per service), attaching or detaching a private network, and configuration (type, algorithm, cost, delete protection, labels)
Services («سرویس‌ها»)Add, edit and delete services; change the algorithm with Apply algorithm («اعمال الگوریتم»)
Targets («اهداف»)Target table with address and per-port health; Add target («افزودن هدف»), remove a target and Check again («بررسی دوباره»)
Change type («تغییر نوع»)Compare limits and cost and switch to another type
Settings («تنظیمات»)Name, delete protection, labels and Delete load balancer («حذف لود بالانسر»)
Activity («فعالیت‌ها»)Every operation performed

To point a domain at it, create an A record to the load balancer's IPv4 (and optionally an AAAA record to its IPv6) in the domain's DNS.

Adding and removing targets​

In Targets, click Add target («افزودن هدف») and choose one of three kinds:

  • Cloud server («سرور ابری»): one of this account's servers in this data center.
  • Label selector («انتخابگر برچسب»): every server in this data center whose labels match the selector becomes a target, and new servers with matching labels are added automatically. Format: env=prod,tier!=db,web,!legacy.
  • IP address («آدرس IP», public interface only): a public IPv4 or IPv6, for example a server outside this data center. Private and reserved addresses are refused.

For a server or a label selector, turn on Use private address («استفاده از آدرس خصوصی») so traffic reaches the server over the load balancer's private network; the server must be on that network. If the load balancer has no network yet, first attach one in Overview. A load balancer without a public interface reaches servers only over the private network.

To remove a target, click the delete button on its row and confirm. The target server is not deleted; it just stops receiving traffic.

Changing the type​

In Change type, pick the new type. The Comparison («مقایسه») table shows both types' limits on services, targets, concurrent connections and monthly cost, and the cost increase or decrease. Click Change to … («تغییر به …»). The addresses stay the same and the new cost applies from the next hour.

caution

Open connections may drop for a few seconds while the type change is applied. If the current services or targets don't fit in a smaller type, remove some first.

Deleting a load balancer​

In Settings, click Delete load balancer, type the name and click Delete forever. If delete protection is on, turn it off first.

danger

Deleting releases the load balancer's addresses and no more traffic reaches the targets. The target servers are not deleted. Billing stops from the next hour.

Cost and limits​

The cost depends on the load balancer's type, is hourly, and starts when the load balancer is ready; if creation fails, nothing is charged. The type sets the limits on services, targets and concurrent connections; Redirect HTTP to HTTPS also counts as one service.

API and CLI​

/load-balancers, POST /load-balancers/{id}/actions/{op} (services, targets, type, algorithm, network), GET /load-balancers/{id}/health and GET /load-balancer-types; on the CLI, arianet cloud load-balancers. See the Cloud API, the interactive reference and the CLI.

Firewalls​

A firewall controls inbound and outbound traffic of cloud servers. Inbound traffic that matches no rule is blocked; outbound traffic is free as long as you have no outbound rules. A firewall applies to the servers' public network interface, and a server can have several firewalls.

When to use it: for every public server. Keep only the ports and networks you need open.

Creating a firewall​

Open Security → Firewalls («امنیت ← فایروال‌ها») and click New firewall («فایروال جدید»).

  1. Name («نام»): Firewall name («نام فایروال»).
  2. Initial rules («قوانین اولیه»): pick a template: Empty («خالی», everything blocked), Web (80, 443, SSH) («وب (۸۰، ۴۴۳، SSH)»), SSH only («فقط SSH»), SSH and Ping («SSH و Ping») or Database (SSH, MySQL, PostgreSQL) («پایگاه داده (SSH، MySQL، PostgreSQL)»). Template rules are open to all addresses and can be changed later on the firewall's page.
  3. Servers («سرورها», optional): the servers the firewall applies to.
  4. Labels («برچسب‌ها», optional)

Click Create firewall («ساخت فایروال»). Firewalls are free.

Rules​

On the firewall's page, the Rules («قوانین») tab has Inbound («ورودی») and Outbound («خروجی») sections. Add an empty row with Add rule («افزودن قانون»), or a common rule with Preset rule («قانون آماده»: SSH, HTTP, HTTPS, Ping, DNS, RDP, MySQL, PostgreSQL, all TCP or UDP ports). Each rule has:

FieldDescription
Protocol («پروتکل»)TCP, UDP, ICMP, ESP or GRE
Port («پورت»)TCP and UDP only; one port (443) or a range (1000-2000)
Source networks / Destination networks («شبکه‌های مبدأ» / «شبکه‌های مقصد»)Addresses in CIDR form; type each one and press Enter. Write a single address as /32 (IPv4) or /128 (IPv6). All IPv4 («همه IPv4») and All IPv6 («همه IPv6») add 0.0.0.0/0 and ::/0.
Description («توضیح»)Optional

Click Save and apply rules («ذخیره و اعمال قوانین»); Discard changes («لغو تغییرات») goes back to the saved rules. A firewall has at most 50 rules.

caution

If the Inbound section is empty, no inbound traffic is allowed, not even SSH. Make sure your own access port is open before saving.

Applying to servers​

In the Servers («سرورها») tab, pick servers from the list or remove them with the button next to each, and click Save servers («ذخیرهٔ سرورها»). You can also do this from a server's Firewall tab.

Editing and deleting​

Rename with the button next to the title. The Labels and protection («برچسب‌ها و محافظت») tab holds delete protection and labels. To delete, click Delete firewall («حذف فایروال»).

danger

A deleted firewall is removed from all its servers. Servers that have no other firewall then accept all inbound traffic.

API and CLI​

/firewalls (PUT /firewalls/{id} replaces all rules), PUT /firewalls/{id}/servers, POST /firewalls/{id}/actions/{op}; on the CLI, arianet cloud firewalls. See the Cloud API, the interactive reference and the CLI.

Private networks​

A private network connects the servers of one data center over internal addresses. Its traffic never crosses the internet and is free.

When to use it: for an application server talking to its database, servers behind a load balancer, or servers that should have no public IP at all (they reach the internet through a router).

Creating a network​

Open Networking → Private networks («شبکه ← شبکه‌های خصوصی») and click New network («شبکهٔ جدید»).

  1. Data center («دیتاسنتر»): only servers in this data center can join the network.
  2. IP range («محدودهٔ آی‌پی»): IP range (CIDR) («محدودهٔ آی‌پی (CIDR)»), a private range from /16 to /28; presets are 10.0.0.0/16, 172.16.0.0/16 and 192.168.0.0/24. With First subnet covers only part of the range («زیرشبکهٔ اول فقط بخشی از محدوده باشد») you make the first subnet smaller (for example 10.0.1.0/24). Below the field you see how many servers it fits.
  3. Name, labels and project («نام، برچسب و پروژه»)

Click Create network («ساخت شبکه»).

caution

The IP range cannot be changed later, so leave room to grow. The first address of each subnet is reserved for the router.

Attaching a server​

  • Choose the network in the networking section while creating a server.
  • Or, on the network's page, Servers tab, click Attach server («اتصال سرور»). In the Attach to private network («اتصال به شبکهٔ خصوصی») window choose the server, the Subnet («زیرشبکه», default Automatic (first subnet) «خودکار (اولین زیرشبکه)») and the Address («آدرس»: Automatic «خودکار» or Specific address «آدرس مشخص»), then click Attach («اتصال»).

To detach, click Detach («جدا کردن») in the same table. A server that has no public IP and lives only on this network (marked Primary network «شبکهٔ اصلی») cannot be detached.

Subnets, routes and router​

The network page has these tabs: Overview and subnets («نمای کلی و زیرشبکه‌ها»), Servers («سرورها»), Routes («مسیرها»), Settings («تنظیمات») and Activity («فعالیت‌ها»).

  • Subnets: type the new subnet and click Add subnet («افزودن زیرشبکه»). It must be inside the network's range, not overlap another subnet, and be between /16 and /29. A subnet that has servers, or the only subnet, cannot be deleted.
  • Static routes («مسیرهای ایستا»): routes are pushed to every server on the network over DHCP; traffic for a destination (for example 192.168.100.0/24) is sent to a gateway inside the network (for example a VPN server at 10.0.0.5). Add up to 32 routes with Add route («افزودن مسیر») and save.
  • Router and internet access («روتر و دسترسی به اینترنت»): if the network has no router, its servers without a public IP have no internet access. Click Add router («افزودن روتر»).

Deleting a network​

In Settings, click Delete network («حذف شبکه»). Before deleting, detach all servers and delete the network's router; a load balancer attached to the network must also be detached or deleted. Deleting removes the network with all its subnets and routes.

API and CLI​

/networks, POST /networks/{id}/subnets, DELETE /networks/{id}/subnets/{subnet}, PUT /networks/{id}/routes, and POST /servers/{id}/actions/attach_to_network to attach a server; on the CLI, arianet cloud networks. See the Cloud API, the interactive reference and the CLI.

Routers​

A router (NAT gateway) takes one public IP and carries the outbound traffic of a private network's servers to the internet. Servers without a public IP reach the internet only this way, and only with a router can they get an elastic IP.

When to use it: when servers sit on a private network without a public IP but still need to install packages or reach outside services.

Creating a router​

Open Networking → Routers («شبکه ← روترها») and click New router («روتر جدید»), or Add router on a network's page.

  1. Network («شبکه»): each network has only one router; networks that already have one cannot be chosen. Below the field you see the router's address in each subnet (its gateway).
  2. Name, labels and project («نام، برچسب و پروژه»): the name is optional.

Click Create router («ساخت روتر»). A router is billed hourly; the price is shown in the summary box.

The router page​

The Overview tab shows the router's details and public IP, Connected subnets («زیرشبکه‌های متصل») and Servers that depend on this router («سرورهای وابسته به این روتر»). Outbound traffic of all servers on the network leaves through the router's IP; to bring inbound traffic to a private server, give it an elastic IP. Settings holds labels, delete protection and Delete router («حذف روتر»).

danger

Release the elastic IPs of this network's servers before deleting the router. Deleting it cuts internet access for servers on the network that have no public IP, and releases the router's public IP.

API and CLI​

/nat-gateways and /nat-gateways/{id}. See the Cloud API and the interactive reference.

Volumes​

A volume is extra storage that lives separately from the server and can be attached to any server in the same data center whenever you want. When a server is deleted, its separate volumes remain.

When to use it: for data that should stay independent of a server (databases, uploads, backups) or when the plan's disk is too small.

Creating a volume​

Open Storage → Volumes («ذخیره‌سازی ← دیسک‌ها») and click New volume («دیسک جدید»).

  1. Data center («دیتاسنتر»): the volume can only be attached to servers in this data center.
  2. Size («اندازه»): 10 to 10,240 GB in steps of 10. Use the preset buttons (10, 50, 100, 250, 500 and 1000 GB), the slider or the number box. The monthly and hourly cost is shown there.
  3. Attachment and filesystem («اتصال و فایل‌سیستم»): Server («سرور») is optional (default No attachment «بدون اتصال»). Filesystem («فایل‌سیستم»): ext4 (default on most distributions), xfs (large files and databases) or I'll format it myself («خودم فرمت می‌کنم»).
  4. Name, labels and project («نام، برچسب و پروژه»): Volume name («نام دیسک»).

Click Create volume («ساخت دیسک»).

note

The volume is delivered raw and is not formatted or mounted automatically. The filesystem choice only decides the ready-made commands. After attaching, the format and mount commands appear with a copy button on the volume's page (Using the volume inside the server «استفاده از دیسک داخل سرور») and on the server's Volumes tab.

Attaching and detaching​

  • On the volume's page, in Attach to server («اتصال به سرور»), choose the server and click Attach («اتصال»). Once attached, the Device path in the server («مسیر دیسک در سرور») and Disk ID in the server («شناسهٔ دیسک در سرور») are shown.
  • Each row's menu in the volume list also has Attach to server («اتصال به سرور») and Detach from server («جدا کردن از سرور»).
  • To detach, click Detach from server and confirm. The volume's data is kept.
caution

Unmount the volume inside the server before detaching (for example sudo umount /mnt/data) so no data is left half-written.

Increasing the size​

In Increase size («افزایش حجم»), set the new size with the +10, +50 and +100 GB buttons, the slider or the number box. The new monthly cost and the increase are shown. Click Increase size.

caution

A volume can only grow, never shrink. After growing it, also grow the filesystem inside the server (the Guide «راهنما» button shows the commands).

Editing and deleting​

Rename with the rename button. Labels and protection («برچسب‌ها و محافظت») holds delete protection and labels. To delete, first detach the volume from its server and turn off delete protection, then click Delete volume («حذف دیسک»).

danger

Deleting a volume destroys all its data permanently.

Cost​

Per GB of size, hourly, whether or not it is attached to a server. The total size and monthly cost of all volumes is shown above the list.

API and CLI​

/volumes and POST /volumes/{id}/actions/{op} (attach, detach, resize), GET /volume-prices; on the CLI, arianet cloud volumes. See the Cloud API, the interactive reference and the CLI.

Floating IP​

A floating IP is an extra fixed public address that moves from one server to another in the same data center within seconds.

When to use it: for failover, moving to a new server without changing DNS, or several sites on one server.

Creating one​

Open Networking → Floating IPs («شبکه ← آی‌پی‌های شناور») and click New floating IP («آی‌پی شناور جدید»).

  1. Data center («دیتاسنتر»): the IP can only be assigned to servers in this data center.
  2. Address type («نوع آدرس»): IPv4 or IPv6 (if the data center offers IPv6).
  3. Assign to server («اختصاص به سرور»): optional; only servers with a public IP in this data center. Default No assignment («بدون اختصاص»).
  4. Name, labels and project («نام، برچسب و پروژه»): Name («نام», optional; empty means an automatic name), Description («توضیحات», optional), labels and project.

Click Create floating IP («ساخت آی‌پی شناور»).

Assigning, moving and releasing​

On the IP's page, in Assignment («اختصاص»), click Assign to server («اختصاص به سرور», or Move «انتقال» if it is already assigned), choose the server and click Assign («اختصاص»). Release («آزاد کردن») detaches it from the server. Each row's menu in the list has the same options.

caution

A floating IP must also be added inside the server's operating system. After assigning, Configure this address in the server's operating system («تنظیم این آدرس در سیستم‌عامل سرور») shows persistent commands for that server's OS.

Reverse DNS​

In Reverse DNS (PTR) («DNS معکوس (PTR)»), click Edit («ویرایش»), enter the Domain name («نام دامنه») and click Save («ذخیره»). First create an A record (AAAA for IPv6) in the domain's DNS pointing this name at the address. Restore default («بازگردانی پیش‌فرض») brings back the data center's default name. See also Networking and reverse DNS.

Editing and deleting​

The Settings tab holds the description, labels, delete protection and delete. Deleting returns the address to the data center's pool for good, and its reverse DNS is cleared.

note

A floating IP that is not assigned to a server is still billed. The cost is hourly, with separate prices for IPv4 and IPv6.

API and CLI​

/floating-ips and POST /floating-ips/{id}/actions/{op} (assign, unassign, change_dns_ptr); on the CLI, arianet cloud floating-ips. See the Cloud API, the interactive reference and the CLI.

Elastic IP​

An elastic IP is a public IPv4 translated one-to-one (NAT) to a server without a public IP. The server stays behind the private network, and only this address reaches it from the internet.

When to use it: when a private server must be reachable from the internet (for example for one specific service) without having a direct public IP.

caution

The server's network must have a router.

Creating and assigning​

Open Networking → Elastic IPs («شبکه ← آی‌پی‌های الاستیک») and click New elastic IP («آی‌پی الاستیک جدید»).

  1. Data center («دیتاسنتر»)
  2. Assign to server («اختصاص به سرور»): optional; only servers in this data center without a public IP whose network has a router. At most one elastic IP per server.
  3. Name, labels and project («نام، برچسب و پروژه»)

Click Create elastic IP («ساخت آی‌پی الاستیک»). Assigning, moving, releasing, delete protection and deleting work as for a floating IP. Elastic IPs have no reverse DNS. Deleting returns the address to the data center's pool, and the attached server is no longer reachable from the internet.

The cost is hourly and shown in the summary box on the create page.

API​

/elastic-ips and POST /elastic-ips/{id}/actions/{op} (assign, unassign). See the Cloud API and the interactive reference.

Primary IPs​

A primary IP is the server's own public address: every cloud server gets a public IPv4 at creation and, if the data center supports it, a public IPv6. These addresses are created with the server and released when it is deleted. Servers without a public IP work behind the private network's router and have no primary IP.

When to use it: to see all your servers' public addresses in one place, set their reverse DNS, or change a server's IPv4.

Creating one​

Primary IPs have no create page. They are created by turning on Public IPv4 («آی‌پی عمومی IPv4») and IPv6 in the networking section while creating a server.

The primary IP list​

Open Primary IPs («آی‌پی‌های اصلی») in the cloud menu. The table has the columns IP («آی‌پی»), Type («نوع», IPv4 or IPv6), Server («سرور»), Reverse DNS («DNS معکوس»), Data center («دیتاسنتر») and Labels («برچسب‌ها»). Filter by search (IP, name, reverse DNS, server or label), data center and type. The server name links to that server's networking tab.

Reverse DNS​

Click the row's Reverse DNS («DNS معکوس») button, enter the Domain name («نام دامنه») and click Save («ذخیره»); Restore default («بازگردانی پیش‌فرض») brings back the data center's default name. First create an A record (AAAA for IPv6) in the domain's DNS pointing this name at the address. For some ranges the message "Setting reverse DNS for this IP range is not possible yet" («تنظیم reverse DNS برای این رنج آی‌پی فعلاً امکان‌پذیر نیست.») is shown and the button is disabled.

Changing the IP​

Next to each server's IPv4 there is a Change IP («تغییر IP») button (the same as on the server's networking tab). The Change IPv4 address («تغییر آی‌پی IPv4») window shows the current address and the cost: the change is either free (with the number of free changes left) or has a fee that is deducted from your wallet only after it succeeds; in that case type the confirmation phrase.

caution
  • The server gets a new IPv4 from the same data center and the current address is released.
  • A running server is soft-rebooted once to pick up the new address; a stopped server gets it on its next start.
  • The current address's reverse DNS is cleared. IPv6, floating IPs and firewalls are not changed.

Deleting and cost​

A primary IP cannot be deleted on its own; it is released when the server is deleted. IPv6 is free. The IPv4 cost (if the data center has a price for it) is shown in the server's create summary and on the server's Costs («هزینه‌ها») tab as Public IPv4 («آی‌پی عمومی IPv4»).

API​

GET /primary-ips, GET/PATCH /primary-ips/{id} (PATCH for name, labels and project) and POST /primary-ips/{id}/actions/change_dns_ptr. See the Cloud API and the interactive reference.

Snapshots​

A snapshot is a full copy of a server's disk at one moment and stays until you delete it, even after the server is deleted. You can create a new server from it or restore a server to it.

When to use it: before major changes (OS upgrade, installing software), or to create several identical servers.

Creating a snapshot​

Open Storage → Snapshots («ذخیره‌سازی ← اسنپ‌شات‌ها») and click New snapshot («اسنپ‌شات جدید»), or use the Snapshot tab on a server's page.

  1. Server («سرور»): servers being created, in rescue mode or locked cannot be chosen.
  2. Name and description («نام و توضیحات»): optional; an empty name becomes the server name and creation time.
  3. Cost («هزینه»): the Cost per GB («هزینهٔ هر گیگابایت») per month and per hour, and the maximum cost for the server's disk size.

Click Create snapshot («ساخت اسنپ‌شات»). Copying takes a few minutes depending on the disk size.

caution

If the server is running, the copy is taken as it is, and data being written at that moment (for example a database) may be incomplete. For a fully consistent copy, shut the server down first.

Using a snapshot​

  • Create a new server: click Create server from this snapshot («ساخت سرور از این اسنپ‌شات»). The new server is created in the same data center, and its plan needs at least the Minimum disk for a new server («حداقل دیسک برای سرور جدید»).
  • Restore a server: in the Use («استفاده») tab (or the row menu item Restore a server to this version «بازگرداندن یک سرور به این نسخه»), click Restore server («بازگرداندن سرور»), choose the Target server («سرور مقصد», only servers in the same data center with a large enough disk), type the server name to confirm and click Restore server.
danger

Restoring wipes all current data on the server's disk and replaces it with the snapshot. A running server is stopped immediately. The IP address does not change, and a new root password is generated and shown once.

Editing and deleting​

Change the name and description on the snapshot's page or with Rename and edit description («تغییر نام و توضیحات») in the row menu. Delete protection is in the Details («مشخصات») tab. To delete, click Delete snapshot («حذف اسنپ‌شات»); in the list you can select several snapshots and delete them at once (you type the count to confirm). A snapshot being created or protected is not deleted.

Cost​

Based on each copy's actual size, hourly. The total size and monthly cost is shown above the list. A snapshot whose creation failed is not billed.

API and CLI​

/snapshots and /snapshots/{id}, and GET /servers/{id}/snapshots. See the Cloud API and the interactive reference.

Backups​

Automatic backups are turned on per server: every day a full copy of the server's disk is taken and the last 7 copies are kept; when a new copy arrives, the oldest is deleted.

When to use it: for every server that holds important data.

Turning it on​

The Storage → Backups («ذخیره‌سازی ← پشتیبان‌گیری») page lists every server with its number of copies and backup state, with Servers with backups («سرورهای با پشتیبان‌گیری»), Copies available («نسخه‌های موجود»), Monthly backup cost («هزینهٔ ماهانهٔ پشتیبان‌گیری») and Servers without backups («سرورهای بدون پشتیبان») counted at the top. Filter by search, data center and All servers / With backups / Without backups («همهٔ سرورها / با پشتیبان‌گیری / بدون پشتیبان‌گیری»).

  1. Expand the server's row.
  2. Click Enable backups («فعال‌سازی پشتیبان‌گیری»).

You can also turn backups on while creating a server or in the Backups tab on a server's page. Back up now («پشتیبان‌گیری فوری») takes a copy immediately; manual and daily copies share the same 7 slots.

Restoring and keeping a copy​

The copies table shows each copy's name, origin, status and size:

  • Restore («بازگردانی»): the server's disk is replaced with the copy (same warnings as restoring a snapshot).
  • Create a new server from this backup («ساخت سرور جدید از این پشتیبان»)
  • Keep as a snapshot («نگه‌داشتن به‌صورت اسنپ‌شات»): the copy becomes a snapshot, leaves the rotation, and survives disabling backups or deleting the server; from then on it is billed separately by size.
  • Delete («حذف»): the copy is deleted before its rotation turn.

Turning it off​

Click Disable («غیرفعال کردن»), type the server name and click Disable and delete backups («غیرفعال کردن و حذف پشتیبان‌ها»).

danger

Disabling permanently deletes all of that server's existing backups. To keep one copy, convert it to a snapshot first.

Cost​

A percentage of the server plan's price (currently 20%), hourly. The percentage and the monthly and hourly amount for each server are shown on this page. Taking, keeping and restoring copies cost nothing extra.

API​

/backups, POST /backups/{id}/actions/convert, and POST /servers/{id}/actions/enable_backup, disable_backup, create_backup, restore_backup. See the Cloud API and the interactive reference.

Projects​

Projects group your cloud resources so you can see each group's cost separately. The wallet and invoices still cover the whole account. Every account has a Default («پیش‌فرض») project.

When to use it: to separate environments (for example test and production) or customers and see each one's cost.

Creating and selecting a project​

  1. Open Compute → Projects («محاسبات ← پروژه‌ها») and click New project («پروژهٔ جدید»).
  2. Enter the Project name («نام پروژه», up to 64 characters, unique in your account) and an optional Description («توضیحات»).
  3. Click Create project («ساخت پروژه»).

The Project («پروژه») switcher in the cloud menu narrows the lists to one project or All projects («همهٔ پروژه‌ها»), and links to Manage projects («مدیریت پروژه‌ها»). New resources are created in the project you choose on the create page.

Usage, resources and moving​

In the project list, each project shows its number of resources and the buttons Usage («مصرف»), Resources («منابع»), Rename («تغییر نام») and Delete («حذف»). The Usage page shows, for the chosen month, the Month total («جمع هزینهٔ ماه»), Daily cost («هزینهٔ روزانه»), By type («به تفکیک نوع») and By resource («به تفکیک منبع»).

To move a resource to another project, click Move to another project («انتقال به پروژهٔ دیگر») on its page, choose the Target project («پروژهٔ مقصد») and click Move («انتقال»). Dependent resources (for example volumes attached to a server) stay in their own project.

Deleting​

Only an empty project can be deleted; first delete its resources or move them to another project. The default project cannot be deleted. Projects cost nothing.

API​

API lists accept a project_id parameter, and PATCH on a resource changes its project. See Lists, labels and projects.

Limits​

Compute → Limits («محاسبات ← محدودیت‌ها») shows the maximum of each resource your account can have in each data center, with the amount used. Limits set specifically for your account are tagged Custom («اختصاصی»). When you reach a limit, that resource's create page tells you. To raise a limit, open a support ticket. API: GET /limits.