New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
SolusVM 1.20.0 released
AnthonySmith
Member, Patron Provider
in General
Detailed release notes for a major version update:
1.20.0 Released: 7 Mar 2017 Type Note Feature Added support for OpenVZ on Virtuozzo Linux 7
Thanked by 1rivermigue
Comments
Before anyone gets too excited - this isn't the 'big release.' This just adds OpenVZ 7.
That's pretty big as well, if it's working properly.
Just curious, does open VZ 7 support 4.x kernel?Found: 3.10
You put more details in your LET Forum reply than in the official release notes, can you even begin to imagine the questions that have gone unanswered here haha?
The WHMCS module has not been updated, not sure if that is an issue if you are only supporting the bare minimum I guess.
I will throw up a node later on.
$7
If that's a real change log, they lack serious project management and communication skills.
Or at least I would have...
Updated today but no OpenVZ 7 option available, so no... its not supported yet.
https://documentation.solusvm.com/display/DOCS/v1.20
gasps
I used to feel bad for Terry whenever Anthony raged at him.
Now I just feel sad seeing how pathetic Solus is.
Everyone seems to think I am always furious haha, I'm really not, I don't have anything against Terry personally, we had a good conversation on the phone about 5 - 6 days ago, but ultimately I am a customer and if things are not right... I am not going to pull my punches.
Dude, people stopped being excited about Solus years ago.
Oh, the "rebrand VirtKick as Solus 2.0" release...hoo, yeah, the internet is all abuzz in anticipation of that.
@AnthonySmith @OnApp_Terry
Maybe I expected to much, please hold the napalm, I just expected the conversion to go through as part of the installer, doing that now and will try again, back in 2014 xen days I guess.
@AnthonySmith has seen SolusVM 2. He's given good feedback, and more importantly, in this case can confirm it is not VirtKick.
Well I gave feed back that was good rather than 'good feedback' Its not virtkick no.
I think we need an official LowEndTalk Solus 2 Release Date pool.
Let's start with some broad outlines: would anyone take a day in 2017?
Some of us have an unfair advantage with information... but yeah sure lets do it.
@OnApp_Terry
Added support for OpenVZ on Virtuozzo Linux 7
Only paid version? or also OpenVZ 7 ?
What about backups? because the backup module is only included in Virtuozzo (paid version).
Are you going to develop your own backup method?
It covers OpenVZ free version.
Seems I jumped the gun I apologize, you have to run the virtuozzo conversion before the solusvm installer.
I'll get the official info on this and update to the release docs.
when adding a new slave
ssh port - confirmed
id+key - confirmed
node ip - confirmed
firewalld - stopped
iptables - off
Problem found..
For some reason solusvm are putting the svmstack-fpm in to sysV so obviously it wont start and they did not think to start it after install.
Same issue I reported with new KVM installs on CentOS 7 about 4 months ago.. still unresolved.
simple fix:
]# service svmstack-fpm restart
Gracefully shutting down php-fpm warning, no pid file found - php-fpm is not running ?
Starting php-fpm done
I tell you what @OnApp_Terry your internal QA team are absolutely shite! its impossible not to run in to this issue if they even attempted to do a fresh install, so they obviously just green lighted everything anyway without testing it at all.
Next issue, VZ6 templates are not compatible with virtuozzo 7 and certainly not backwards compatible, solusvm does not have any way to handle this it seems and naming conventions are identical and there is only 1 set of templates for uses to pick from and no way to distinguish between them.
@OnApp_Terry this seems like a huge oversight?
That's it for my patience.. towel thrown in someone else take over.
November 31st.
This is a bit like when they fixed SMTP on "stable" after the PHPMailer update even though it was still broken (1.18.06):
https://documentation.solusvm.com/display/DOCS/v1.18
Doesn't anyone ever quality check before releasing?
I picture @AnthonySmith chainsmoking and muttering under his breath while wondering why he doesn't just take a couple months off, and build it himself.
I'll take April 1st