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.
Comments
haha, i'm just laughing tbh, going to take the dogs out for a walk and revisit this thread next week
I will take February 15th 2018
All this moaning. Time to code your own
Your one of those "I told you so" people that suffer in silence eh?
For me it shows OpenVZ 7
Choose an option :
Did you read all the posts above before posting this ?
What is UI ?
First assumption will be Solus UI.
@jmginer
https://www.lowendtalk.com/discussion/comment/2108088/#Comment_2108088
i found your problem in the end of the last line...
ur welcome!
If a pre-created template exists in the cache it will be automatically converted to a new template on first use. For example:
debian-7.0-x86_64-minimal.tar.gz will be generated as debian-7.0-x86_64-minimal.plain.ploopv2.tar.lz4
The legacy templates will then be cleaned up. The new EZ templates and apps will follow.
What if someone needs to run both legacy OpenVZ on some Hypervisors and OpenVZ 7 on some ? I heard the new tpls are not backwards compatible (though I haven't tested myself so this might not be 100% accurate)
/var/log/vzctl.log
6 lines writed every second, at this point, I will need a hard drive just to store logs
Well then they will not work on vz legacy /simfs based nodes will they?
And how on earth is that supposed to work with the template manager in solusvm?
example: debian-8.0-x86_64-minimal.tar.gz < this is the vz7 template shipped with the vz7 install, it wont work on VZ6, so I add it to the template manager in solusvm for users on the vz7 node.
Now I have to give it a different name from the current debian 8 template, so now current end users on vz6 nodes see 2 debian 8 templates, if they reinstall it becomes a coin toss depending on what they pick.
Maybe I am missing something, please correct me if I am?
These are all the really obvious things that really need to be handled in the documentation when you did the release instead of the 7 or 8 words you used.
just put a SOLUSVM sticker on the little red cart...
What a complete clusterfuck this software is- and I don't even have to manage it!
I'd be excited if I would have some type of support from cloud.net which was forwarded your way...
Sorry for the off topic...
well I just tried deploying a container through solusvm/virtuozzo 7 using a vz7 template, got a green light from solusvm, created successfully, even gave me the root password etc in the web UI, container never came online, further checking on the host node, it was never created to begin with, not even the config was created.
I am tired of being 'that guy' so I am just going to revisit it in a month when everyone else does the leg work.
What a disastrous release, you guys should be embarrassed, there is absolutely no way this has been tested before release, certainly not from start to finish or by anyone that can tie their own shoe laces.
Why bother paying for a team to QA when your customers can do it for free!?
That would be funny if they had not already confirmed they actually have a QA team
The piece-on-the-side won't sue as long as they get a paycheck.
I made tests with openvz 7 on the GA release and it had too many bugs. Switched back to openvz 6. Works far more stable.
Does somebody run it in production? Would say its safer to stay with openvz 6 until openvz 7 is mature.
May not have involved QA
There are 2 ways to respond to that.
1) There is no doubt they did not involve them, which is ridiculous.
2) If they did they need to issue some P45's
They'll soon be joining UB-40, eh?
So how terrified are you of SVM2?
Francisco
No point in getting scared until its even remotely close, by which time I seriously doubt I will be an OnApp customer any more anyway.
Ah, so the 'before summer' estimates are a bit off then :P
Francisco
depends which one I suppose.