Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


SolusVM 1.20.0 released - Page 2
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.

SolusVM 1.20.0 released

24

Comments

  • AnthonySmithAnthonySmith Member, Patron Provider

    WSS said: 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.

    haha, i'm just laughing tbh, going to take the dogs out for a walk and revisit this thread next week

    Thanked by 1Junkless
  • AnthonySmithAnthonySmith Member, Patron Provider

    raindog308 said: 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?

    I will take February 15th 2018

  • HxxxHxxx Member

    All this moaning. Time to code your own :)

  • AnthonySmithAnthonySmith Member, Patron Provider
    edited March 2017

    Hxxx said: All this moaning. Time to code your own :)

    Your one of those "I told you so" people that suffer in silence eh?

    Thanked by 1Hxxx
  • @AnthonySmith said:

    AnthonySmith said: I will throw up a node later on.

    Or at least I would have...

    >  o----------------------------------------------------------------o
    >  | :: SolusVM Installer                         v5.1 (2017/03/07) |
    >  o----------------------------------------------------------------o
    >  |                                                                |
    >  |   What SolusVM type would you like to install?                 |
    >  |                                                                |
    >  |                                                                |
    >  |   RHEL/CENTOS/SCI LINUX 7 HOST SERVER:                         |
    >  |   ----------------------------------------------------------   |
    >  |   | Opt | Type             | Virtualization                |   |
    >  |   ==========================================================   |
    >  |   | [1] | UI               | None                          |   |
    >  |   ----------------------------------------------------------   |
    >  |   | [2] | Hypervisor       | KVM                           |   |
    >  |   ----------------------------------------------------------   |
    >  |   | [3] | Hypervisor       | Xen                           |   |
    >  |   ----------------------------------------------------------   |
    >  |                                                                |
    >  o----------------------------------------------------------------o
    > 

    Updated today but no OpenVZ 7 option available, so no... its not supported yet.

    image

    For me it shows OpenVZ 7

      | :: SolusVM Installer                         v5.1 (2017/03/07) |
     o----------------------------------------------------------------o
     |                                                                |
     |   What SolusVM type would you like to install?                 |
     |                                                                |
     |                                                                |
     |   VIRTUOZZO 7 HOST SERVER:                                     |
     |   ----------------------------------------------------------   |
     |   | Opt | Type             | Virtualization                |   |
     |   ==========================================================   |
     |   | [1] | Hypervisor       | OpenVZ                        |   |
     |   ----------------------------------------------------------   |
     |   | [2] | Hypervisor       | OpenVZ with basic templates   |   |
     |   ----------------------------------------------------------   |
     |   | [3] | UI               | OpenVZ with basic templates   |   |
     |   ----------------------------------------------------------   |
     |   | [4] | UI               | OpenVZ                        |   |
     |   ----------------------------------------------------------   |
     |                                                                |
     o----------------------------------------------------------------o
    

    Choose an option :

  • ClouviderClouvider Member, Patron Provider
    edited March 2017

    Did you read all the posts above before posting this ?

  • jmginerjmginer Member, Patron Provider

    What is UI ?

  • ClouviderClouvider Member, Patron Provider

    @jmginer said:
    What is UI ?

    First assumption will be Solus UI.

    Thanked by 1Junkless
  • dedicadosdedicados Member
    edited March 2017

    AnthonySmith said: Problem found..

    For some reason solusvm...

    i found your problem in the end of the last line...

    ur welcome!

    Thanked by 2Hxxx AnthonySmith
  • SolusVMSolusVM Member, Host Rep

    @AnthonySmith said:
    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.

    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.

  • ClouviderClouvider Member, Patron Provider

    @SolusVM said:

    @AnthonySmith said:
    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.

    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)

  • jmginerjmginer Member, Patron Provider
    edited March 2017

    /var/log/vzctl.log

    6 lines writed every second, at this point, I will need a hard drive just to store logs :)

    2017-03-07T21:58:23+0100 prl_disp_service : Warning: NUMTCPSOCK parameter is deprecated
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: TCPSNDBUF parameter is deprecated
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: TCPRCVBUF parameter is deprecated
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: OTHERSOCKBUF parameter is deprecated
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: DGRAMRCVBUF parameter is deprecated
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: NUMOTHERSOCK parameter is deprecated
    
    Thanked by 1raindog308
  • AnthonySmithAnthonySmith Member, Patron Provider
    edited March 2017

    @SolusVM said:

    @AnthonySmith said:y
    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.

    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.

    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.

  • dedicadosdedicados Member
    edited March 2017

    jmginer said: I will need a hard drive just to store logs :)

    just put a SOLUSVM sticker on the little red cart...

  • WSSWSS Member

    What a complete clusterfuck this software is- and I don't even have to manage it!

    Thanked by 3FredQc quadhost JackH
  • raindog308raindog308 Administrator, Veteran
    2017-03-07T21:58:23+0100 prl_disp_service : Warning: SOLUS is deprecated
    
  • @OnApp_Terry said:
    Before anyone gets too excited - this isn't the 'big release.' This just adds OpenVZ 7.

    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...

  • AnthonySmithAnthonySmith Member, Patron Provider
    edited March 2017

    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.

  • WSSWSS Member

    @AnthonySmith said:
    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!?

  • AnthonySmithAnthonySmith Member, Patron Provider

    @WSS said:

    @AnthonySmith said:
    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

  • WSSWSS Member

    @AnthonySmith said:

    @WSS said:

    @AnthonySmith said:
    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.

  • Tr33nTr33n Member

    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.

  • AnthonySmith said: 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.

    May not have involved QA

  • AnthonySmithAnthonySmith Member, Patron Provider

    jcaleb said: 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

    Thanked by 1jcaleb
  • WSSWSS Member

    @AnthonySmith said:
    2) If they did they need to issue some P45's

    They'll soon be joining UB-40, eh?

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @AnthonySmith said:

    jcaleb said: 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

    So how terrified are you of SVM2?

    Francisco

  • AnthonySmithAnthonySmith Member, Patron Provider

    Francisco said: So how terrified are you of SVM2?

    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.

  • FranciscoFrancisco Top Host, Host Rep, Veteran

    @AnthonySmith said:

    Francisco said: So how terrified are you of SVM2?

    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

  • AnthonySmithAnthonySmith Member, Patron Provider

    Francisco said: Ah, so the 'before summer' estimates are a bit off then :P

    depends which one I suppose.

    Thanked by 1Francisco
Sign In or Register to comment.