<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">
Hi, Paulo,
<div class=""><br class="">
</div>
<div class="">prlctl uses Virtuozzo SDK inside.</div>
<div class=""><br class="">
</div>
<div class="">If you plan to use nodejs, I would recommend to wrap existing Virtuozzo SDK into native code, e.g. like it is done here:</div>
<div class=""><a href="https://github.com/matortheeternal/s2js" class="">https://github.com/matortheeternal/s2js</a></div>
<div class="">Such approach is much faster (comparing to cmdline execution) and provides better flexibility.<br class="">
<div><br class="">
</div>
<div><br class="">
<blockquote type="cite" class="">
<div class="">14 мая 2019 г., в 19:45, Paulo Coghi - Coghi IT <<a href="mailto:paulocoghi@gmail.com" class="">paulocoghi@gmail.com</a>> написал(а):</div>
<br class="Apple-interchange-newline">
<div class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div dir="ltr" class="">
<div class="">Thank you so much for the response!<br class="">
<br class="">
</div>
<div class="">I used the commercial version for more than a year, and it was a great experience.<br class="">
<br class="">
There are many good aspects to be inspired from it, but I will strive to deliver improvements as well (always talking to you first).<br class="">
<br class="">
</div>
<div class="">My plan is to create a complete architecture (below), integrating and testing it first on OpenVZ and later on Virtuozzo (commercial version).<br class="">
<br class="">
</div>
<div class="">1. OpenVZ SDK in pure nodejs<br class="">
- zero dependencies<br class="">
- to manage every aspect of the host, OpenVZ containers (and later VMs)<br class="">
</div>
<div class=""> - available as a NPM package<br class="">
</div>
<div class=""><br class="">
</div>
<div class="">2. Back-end API that uses this new SDK:<br class="">
- API with both HTTP and Socket (real-time) endpoints<br class="">
</div>
<div class=""> - modular and easy to maintain; fast with async and reactive programming</div>
<div class=""> - secure, with two-factor auth, brute-force analysis, and session tokens instead of JWT<br class="">
</div>
<div class=""> - low RAM usage (expected ~60MB) and small, dependency-free, Linux binary (expected ~20 to ~40MB)<br class="">
<br class="">
</div>
<div class="">3. Front-end<br class="">
</div>
<div class=""> - design: following the best practices in UI/UX<br class="">
</div>
<div class=""> - small and fast: compiling the app to a pure, framework-less and performant javascript code (Svelte)<br class="">
</div>
<div class=""> - easy to receive code contributions, using natural HTML+CSS+JS that everyone knows in each component (Svelte)<br class="">
</div>
<div class=""> - responsive and mobile friendly</div>
<div class=""><br class="">
<br class="">
</div>
<div class="">I have only one doubt:<br class="">
What is the method used by the existing Virtuozzo SDKs to comunicate directly with OpenVZ? Call `prlctl` commands on behind, or access a specific OpenVZ interface to control it?<br class="">
<br class="">
</div>
<div class="">
<div class="">If such an interface exists, I would prefer to make the new SDK in Node to use it, instead of call `prlctl` commands on behind.<br class="">
<br class="">
-<br class="">
<br class="">
I'm commited to help making OpenVZ better, better known, make it even easier than it already is (with the new UI) and give support for the community. In this way, I hope to bring more users not only to the open source version of OpenVZ, but more paying customers
to Virtuozzo as well.<br class="">
<br class="">
</div>
<div class="">Thanks again!<br class="">
<br class="">
<br class="">
</div>
<div class="">Paulo Coghi<br class="">
</div>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Tue, May 14, 2019 at 11:52 AM Konstantin Khorenko <<a href="mailto:khorenko@virtuozzo.com" class="">khorenko@virtuozzo.com</a>> wrote:<br class="">
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Hi Paulo,<br class="">
<br class="">
you are very welcome in the OpenVZ community and i bet many OpenVZ users will be grateful to you<br class="">
for the convenient UI developing.<br class="">
<br class="">
From our side we can show you the UI for Virtuozzo version so you can check what how it's done,<br class="">
take a look what functionality is implemented there, etc.<br class="">
It may be useful to verify the existing solution while designing the new one.<br class="">
<br class="">
<a href="https://docs.virtuozzo.com/virtuozzo_automator_7_administrators_guide/index.html" rel="noreferrer" target="_blank" class="">https://docs.virtuozzo.com/virtuozzo_automator_7_administrators_guide/index.html</a><br class="">
This is a UI for administrator.<br class="">
<br class="">
<a href="https://docs.virtuozzo.com/virtuozzo_powerpanel_administrators_guide/index.html" rel="noreferrer" target="_blank" class="">https://docs.virtuozzo.com/virtuozzo_powerpanel_administrators_guide/index.html</a><br class="">
This is for end-users (so, they can configure their own Containers and VMs only).<br class="">
<br class="">
AFAIK, above UI work on Virtuozzo installations only, so you will need to set up trial<br class="">
Virtuozzo nodes. If you have any difficulties with getting trial licenses for that, please let us know.<br class="">
<br class="">
i don't currently know your plan (design), but probably if you wish to minimize the effort of writing<br class="">
back-end, we can teach back-end of Virtuozzo Automator to be installed on OpenVZ nodes as well<br class="">
(currently it will detect OpenVZ and fail the installation) and provide the back-end API,<br class="">
so you can write only frond-end UI part.<br class="">
i'm currently not 100% committing to that plan but it seem to be logical and if you like it<br class="">
(after you check the internal Automator structure and the API), we can ask for permission to do that.<br class="">
<br class="">
Good luck!<br class="">
<br class="">
--<br class="">
Best regards,<br class="">
<br class="">
Konstantin Khorenko,<br class="">
Virtuozzo Linux Kernel Team<br class="">
</blockquote>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br class="">
</div>
</body>
</html>