<div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Thank you so much for the response!<br><br></div><div>I used the commercial version for more than a year, and it was a great experience.<br><br>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><br></div><div>My plan is to create a complete architecture (below), integrating and testing it first on OpenVZ and later on Virtuozzo (commercial version).<br><br></div><div>1. OpenVZ SDK in pure nodejs<br> - zero dependencies<br> - to manage every aspect of the host, OpenVZ containers (and later VMs)<br></div><div> - available as a NPM package<br></div><div><br></div><div>2. Back-end API that uses this new SDK:<br> - API with both HTTP and Socket (real-time) endpoints<br></div><div> - modular and easy to maintain; fast with async and reactive programming</div><div> - secure, with two-factor auth, brute-force analysis, and session tokens instead of JWT<br></div><div> - low RAM usage (expected ~60MB) and small, dependency-free, Linux binary (expected ~20 to ~40MB)<br><br></div><div>3. Front-end<br></div><div> - design: following the best practices in UI/UX<br></div><div> - small and fast: compiling the app to a pure, framework-less and performant javascript code (Svelte)<br></div><div> - easy to receive code contributions, using natural HTML+CSS+JS that everyone knows in each component (Svelte)<br></div><div> - responsive and mobile friendly</div><div><br><br></div><div>I have only one doubt:<br>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><br></div><div><div>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><br>-<br><br>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><br></div><div>Thanks again!<br><br><br></div><div>Paulo Coghi<br></div></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></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">khorenko@virtuozzo.com</a>> wrote:<br></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>
<br>
you are very welcome in the OpenVZ community and i bet many OpenVZ users will be grateful to you<br>
for the convenient UI developing.<br>
<br>
From our side we can show you the UI for Virtuozzo version so you can check what how it's done,<br>
take a look what functionality is implemented there, etc.<br>
It may be useful to verify the existing solution while designing the new one.<br>
<br>
<a href="https://docs.virtuozzo.com/virtuozzo_automator_7_administrators_guide/index.html" rel="noreferrer" target="_blank">https://docs.virtuozzo.com/virtuozzo_automator_7_administrators_guide/index.html</a><br>
This is a UI for administrator.<br>
<br>
<a href="https://docs.virtuozzo.com/virtuozzo_powerpanel_administrators_guide/index.html" rel="noreferrer" target="_blank">https://docs.virtuozzo.com/virtuozzo_powerpanel_administrators_guide/index.html</a><br>
This is for end-users (so, they can configure their own Containers and VMs only).<br>
<br>
AFAIK, above UI work on Virtuozzo installations only, so you will need to set up trial<br>
Virtuozzo nodes. If you have any difficulties with getting trial licenses for that, please let us know.<br>
<br>
i don't currently know your plan (design), but probably if you wish to minimize the effort of writing<br>
back-end, we can teach back-end of Virtuozzo Automator to be installed on OpenVZ nodes as well<br>
(currently it will detect OpenVZ and fail the installation) and provide the back-end API,<br>
so you can write only frond-end UI part.<br>
i'm currently not 100% committing to that plan but it seem to be logical and if you like it<br>
(after you check the internal Automator structure and the API), we can ask for permission to do that.<br>
<br>
Good luck!<br>
<br>
--<br>
Best regards,<br>
<br>
Konstantin Khorenko,<br>
Virtuozzo Linux Kernel Team<br>
</blockquote></div></div></div></div></div></div></div></div></div></div></div></div></div>