"How we build IaaS": materials about the work of 1cloud
We talk about how we launched and develop cloud 1cloud, we are talking about the evolution of its individual services and architecture as a whole. We also disassemble myths about IT infrastructure.
We compare our expectations before the launch of the platform with the first experience of providing services to customers. We start with a brief history of the appearance of 1cloud, then we talk about how we defined the circle of “our” clients. Next, we share the difficulties we encountered and the main conclusions based on the results of their resolution. We hope that this material will be useful for startups and teams starting to develop their projects.
This is a story about how we modified the platform based on the changing needs of customers: we implemented the possibility of creating private networks, updated ways to manage disk space and increased capacity. In addition, here we are talking about services for those who do not consider themselves system administrators and IT specialists - server templates, VDS hosting with a preinstalled control panel, and simplified license administration.
When we first launched our service, the platform was based on a classic three-component architecture: a web server, an application server, and a database server. However, over time, our infrastructure has grown geographically and many different client companies have appeared. The old three-tier model had certain limitations in terms of scaling, and we decided to try a modular approach to building architecture. How we approached this task, and what problems we encountered in the process of implementing the new architecture, read in this article.
The development cycle for new releases of our products has been somewhat erratic and has varied in length. The transition to DevOps allowed us to increase the efficiency of development and stabilize the time frame for the release of updates. From this material, you will learn some of the nuances of our implementation of the DevOps approach as part of the work on 1cloud.
We share our experience in organizing interaction with clients: from chat and telephone communication to mail and opportunities on the web. In addition, we have prepared recommendations to prepare calls to technical support that will help achieve the desired result.
First material of our cycle will debunk the myth that IaaS-provider technical support is filled with “girls” who do not understand anything. It also argues that it is not only IT professionals who can control and maintain a virtual environment.
Second article will dispel misconceptions about the insecurity of cloud solutions and the superiority of foreign providers over Russian ones. We will tell you why cloud security mechanisms are in no way inferior to traditional infrastructure protection systems, and why large corporations transfer business-critical applications to a virtual environment.
Third dedicated to the myths about iron. We will talk about the conditions under which large providers place hardware capacities - what requirements the data center must meet, and whether the equipment can operate in an accident-free mode. Also, we will explain what the availability of servers for clients depends on, and we will discuss the issue of “hype” around the cloud.
Here is an overview of the features available to 1cloud clients in the public public, private client, and public client subnets of our cloud. We tell you what affects the speed: from what data is transmitted to the equipment involved.
We find out whether the costs for on-prem and cloud servers will differ within five years of operation. We take into account the cost of equipment, rent, software installation, administration, maintenance and taxes. To complete the picture, we take two types of configurations as a basis - “powerful” and basic. Plus, here's a comparison table.
A photo report of the unpacking of new hardware, which will help us provide customers with VMs with 32-core processors and up to 400 GB of RAM. We will show what the “stuffing” looks like, talk about the technical characteristics and capabilities.
This article provides a checklist of 21 questions to ask a provider before signing a contract with them. There are basic points and not quite obvious things.