SmartOps tour
- In-house infrastructure management commodity in your company
- do not take steps in the wrong direction, we’ll show you a correct solution
- a solution built on the world-renowned Salt tool from the American company SaltStack
- training your team to use the salt
Why Intelligent Automation?
All the actions take a long time, because administrative commands are executed one by one and all is manual administration (installation, configuration etc.)
Mostly you have no history of server changes if you do not control them individually one by one.
A lot of work is done again and again which leads to monotony and increases your error-rate. One stops paying attention etc.
The documentation has to be written independently but in case of automation, the documentation is
the rule
for actions on all the servers, so the documentation is written from the very beginning.
And as we all know, writing a classical documentation is boring.
Any administrator should be paid for making sure the service is functional. Therefore, he should take care of the structure and the architecture of infrastructure instead of endless execution of the same administrative commands to install applications that can be automated.
Without automation, the administrator cannot has not enough time for self-education and pushing his own limits forward.
Automation is not here to replace the administrator, but to make the administrator´s work easier.
1. FULLY AUTOMATED PROVISION
By provisioning on your servers, you get a great control over what is running on them, when some changes are being done. All these actions are versioned and you can review them at any time.
If provisioning is applied through a CI/CD tool, as we recommend, you will get an opportunity to browse the history of logs and the details about what actions were made, by whom and on which machine.
This is a huge plus to troubleshoot problems/outages on your infrastructure.
And it can help you with the modification of the infrastructure in the future because multiple data sources are a big plus for successful diagnostics.
Moreover, with our solution, you get each node on each machine which is connected to the master server and you can perform the operations you need – from server monitoring to custom application state detections.
2. SERVER ORCHESTRATION
Orchestration gives us the ability to add more computing power (server power) easily and quickly.
It is important that the infrastructure is prepared for it, which we can provide with our solution.
We are able to orchestrate full virtualization directly (for example KVM/Qemu, WMware), and cloud services indirectly (such as OpenStack, Azure, AWS).
Other options are containers (Docker, LXC).
The advantage of our solution is that even this part of your infrastructure is set up and maintained as a code, and we make sure that both provisioning and orchestration is a whole ‘with the minimal use of technologies that differ significantly from one another.3. INFRASTRUCTURE AS A CODE
This is useful, for example, when you need to provide training to your new colleagues – administrators.
4. BEST PRACTICE
To do so, we defined our own best practices based on our past work experiences.
5. CI/CD TOOLS
What is supposed to happen with a given code depends on the context – in which branch the changes were made.
Then you can see the results in a web browser.
The results will be saved in colour form in the CI/CD tool and will not disappear in the console output.
6. INFRASTRUCTURE VERSIONING
This gives you an opportunity to change the functionality faster, get the history of changes as well as general overview of the application development.
In our case, this application code is the state of your infrastructure which brings you great documentation of what ever happened on the infrastructure, etc.
7. FEATURE BRANCHING
The infrastructure development can take place outside the production environment.
So the code can be tested, code-reviewed and then, as a whole, it can be combined with the production version.
This is the recommended development approach
8. PIPELINES
PRODUCTION PIPELINE when change is applied to production branches, we execute dry-run. If everything goes well, you will manually select a server or group of servers that will be deployed. Here the emphasis is on the stability.
DEVELOP PIPELINE if you develop in feature branch, you want to deploy on separated server, where you can do anything and you cannot break anything. And you want to make changes quickly.
We set it up so.
Sorry, these prices are valid only in the Czech Republic. Cloud solution is comming soon
Minimal
-
instalation of solution including all tools
-
automation of 5 VPS
-
automation training
ranging 5h for 3 people
Custom
Minimal variant
| instalation and configuration of SmartOps | |||
| automation (analysis+realization) 5xVPS | |||
Training of your team |
|||
| training, limited for 5 people (salt, salt-cloud, jenkins pipeline) |
|
||
|
|
|||
| Number of current VPS - analysis |
|
||
| Number of similar VPS - analysis |
|
||
| Number of current dedicated servers - analysis |
|
||
| Number of similar dedicated servers - analysis |
|
||
Kontakt
pište, volejte, sjednejte si s námi schůzku
+420 732 531 312 / +420 774 901 612
Ing. Antonín Rykalský
