How to plan an IT infrastructure budget in Oktawave cloud platform
Posted by on 27.02.2014 18:28
Sometimes during conversations with our clients we hear some concerns about the fact that companies are not able to accurately estimate the monthly cost of Oktawave infrastructure. These concerns are partly justified and come out as a result of the very concept of flexibility - in which we assume that at the beginning we do not know precisely how much infrastructure the customer actually will consume within a month, and we want him to pay only for those resources actually used.
Here we have signs of old habits, in which customers agree to overpay for infrastructure, as long as they have a fixed monthly price. Cloud computing is changing the status quo - the state, which by definition we consider to be detrimental to users and we want them to see the advantages of flexibility. Therefore, we have prepared this document. It aims to help customers in better controlling the monthly budget for expenses in Oktawave and precise understanding of how billing works in Oktawave.
Please note that the prices used in this material are illustrative and may have changed recently. Please check out this site for current prices of our services and adjust them according to the scheme presented here for calculations.
OCI cloud server valuation
Oktawave Cloud Instances (OCI) is a service that allows you to easily utilize the resources of cloud computing (virtual servers, which are called instances) for the creation and development of scalable websites and web applications, dedicated systems or online games.
Thanks to accounting only for the resources used, you can limit your costs spent on IT, while maintaining the ability for rapid adaptation of infrastructure to the changing needs of your customers and the market.
To make the valuation of the OCI, you must take into account four OCI environment parameters and the three OVS (Oktawave Volume Storage, which is the equivalent of the disk) parameters.
OCI is a logical unit functioning in the virtualized Oktawave data center resources, defined by the amount of RAM (defined in GB, gigabytes) and the number of CPUs (vCPUs) of a certain computing power (expressed in GHz, gigahertz), which allows running the operating system. OCI is therefore equivalent to a logical server.
Oktawave offers predefined RAM and vCPUs configurations environments - they begin with 0.5 GB RAM, 1 vCPUs x 2.5 Ghz (32 or 64 bit). Up to date configurations can be found in our price list page.
The customer must also take decisions, whether constructed infrastructure will be operated under Windows or Linux operating system - the first one cost a bit more.
Another parameter is the outgoing transfer of the instance to the Internet in a month. It is worth remembering that in Oktawave transfer between instances is free of charge.
In Oktawave for the use of the infrastructure customers pay hourly and thus to estimate monthly cost, the amount received from the above points should be multiplied by 732 (the average number of hours per month).
In summary, these four parameters needed for the valuation of OCI are:
OVS disk valuation
The next step is to choose the OVS disk (Oktawave Volume Storage). OVS provides a permanent data record for the instances so that you can manage disk volumes, regardless of which instances are using them and assign one volume to many instances at the same time, building clusters such as SQL or High Performance Computing solutions (HPC).
Server instances in Oktawave require disk space. It is Oktawave Volume Storage that complies this role. One of the basic parameters of the service is of course the capacity (defined in GB, gigabytes).
Another parameter is the number of IOPS (Input and Output Operations per Second, the number of read and write operations on the disk). The maximum number of IOPS depends on the hard disk. Oktawave offers five types of disks, so-called tiers:
In addition to how fast you can write and read data from the disk - in Oktawave we count how many such operations have been performed during the month. Total IOPS number during one month depends on the maximum speed of the disk and its average load, for example expressed as a percentage.
In summary, the parameters that affect the OVS price are:
* If 300 GB is not enough, use the additional volume and using - for example, logical volume manager - integrate all into one disc.
Example 1: a basic server instance
There are many examples of Oktawave infrastructure usage, but in the beginning we will focus on the simple but illustrative example - it will be the DNS server.
The requirements of such environments are small, just 0.5 GB RAM, 1 vCPUs x 2.5 Ghz - the v1.standard-1.05 variant with the Linux operating system.
This is the amount 0,02 USD per hour, which is multiplied by the number of hours a month, which gives us the amount of 14.64 USD without tax (we assume that a month in the year scale has an average of 732 hours).
For DNS we just need 1 GB of outgoing data transfer per month, so to the amount of 14.64 USD we must add 0.0045 USD (a month for 1 GB).
Because DNS servers do not require a large disk, we just add to this 15 GB of disk space. 1 GB is the cost of 0.0001 for one hour, so multiply it by 24 and then by 30.5 (average number of days in a month) and in the end multiply it by 15 (the selected volume size), it will give us a total of 1.09 USD per month for 15 GB.
We chose the drive with tier 1, which allows for 1000 operations per second, the number of transactions per month is 1000 * 3600 (number of seconds in an hour) = 3 600 000, multiply it by 732 (hours a month), which gives 2 635 200 000 IOPS . This is the maximum, but we assume that we will use only 5%, hence we have a specific number of IOPS: 131 760 000.
The number of operations (in our example 131 millions) we multiply by 0.0120 USD, which gives us the amount of 1.57 USD, which after adding the data space costs gives an amount of 2.66 USD.
The total cost of the environment (in this example the DNS) is 2.66 USD (disk) + 14.64 USD (instance + transfer) = 17.30 USD (without tax).
Example 2: backup
Optionally, you can create backups of your server using Oktawave Cloud Storage - but note that this is a separate type of magazine. Oktawave Cloud Storage (OCS) is a reliable and secure way to exchange files between various systems and applications on the Internet. It has been designed to facilitate the development of scalable environments, regardless of the technologies used. In other words, if OVS is a highly efficient disk block system, the OCS is object storage (photos, videos, backups, etc.).
Monthly cost of such backups is calculated by determining the space for such backups multiplied by the hourly cost per gigabyte of OCS and the number of hours a month. For our example, the DNS server, this cost is (50 GB for backup): 50 * 0.0001 * 732 = 3.66 USD.
In the case of backups performed using the functionality available in the Oktawave administration panel, transfer to the OCS is not counted within a region of availability.
Example 3: file storage
To estimate the cost of storing files in the OCS, we must take into account the amount of stored data and the amount of monthly transfer to and from the OCS service.
For example, we assume 100 GB space: 100 * 0.0001 * 732 = 7.32 USD for space per month.
Incoming transfer in the amount of 50 GB and outgoing in the amount of 40 GB will cost: 50 * 0.0045 + 40 * 0.0045 = 0.40 USD for transfer in a month.
So it will give us: 7.32 USD + 0.40 USD = 7,72 USD per month.
It happens that customers start with a safe buffer of disc storage - it is worth knowing that storage at any time can be increased and there is no point to raise costs in this way.