Update - as of tonight's ugrades everything works regarding live
migration of containers -
Jake
On Mon, Jun 6, 2016 at 3:10 PM, jjs - mainphrame wrote:
> Greetings -
>
> Thanks Cyril, vzctl suspend/resume bug filed and fixed -
> suspend/resume now works on all CTs and the
spameden posts
>> Please understand me correctly, we don't want to support a variety of all
>> Linux zoo.
>> It requires much more time of development, testing and support.
>
> That's a shame. Another nail in the coffin of OpenVZ.. :(
>
Sergey as spameden aptly posts, unsupported GNU/Linux
On 06/06/2016 07:13 PM, Сергей Мамонов wrote:
> Yes, i know it's still possible to create an image which will be compacted
not that efficiently, but this becomes quite a rare case.
But in irl - get random prodaction node and first container with max delta
(data vs image size) -
> Please understand me correctly, we don't want to support a variety of all
Linux zoo.
> It requires much more time of development, testing and support.
That's a shame. Another nail in the coffin of OpenVZ.. :(
2016-06-06 19:43 GMT+03:00 jjs - mainphrame :
> Hi Sergey,
>
>
On 06/06/2016 06:13 PM, Konstantin Khorenko wrote:
On 06/06/2016 02:23 PM, Volker Janzen wrote:
Hi Sergey,
On 14:39 Sun 05 Jun , Volker Janzen wrote:
Unfortunately no. We don't support upgrade from pre-release version to the
final one.
When I use a CentOS 7 as base system and install VZ7
On 13:23 Mon 06 Jun , Volker Janzen wrote:
> Hi Sergey,
>
> > On 14:39 Sun 05 Jun , Volker Janzen wrote:
> >>>
> >>> Unfortunately no. We don't support upgrade from pre-release version to
> >>> the final one.
> >>
> >> When I use a CentOS 7 as base system and install VZ7 afterward it's not
>
Hi Sergey,
> As you know Virtuozzo 7 based on VzLinux distribution.
I forgot another question: is there a hardware requirement / compatibility list
for VzLinux? As of it's not the same as CentOS, the requirements may be
different. Is there software raid support in bare metall installer? Or is
Hi Sergey,
I suppose one could still migrate CTs from an OVZ7 pre-release to a
newly installed OVZ7, is that a reasonable assumption? Is live
migration likely to work in this scenario?
Jake
On Sun, Jun 5, 2016 at 3:55 AM, Sergey Bronnikov wrote:
> Hello, Volker
>
> On 22:06
Hi Sergey,
>> On 13:23 Mon 06 Jun , Volker Janzen wrote:
>> Hi Sergey,
>>
>>> On 14:39 Sun 05 Jun , Volker Janzen wrote:
>
> Unfortunately no. We don't support upgrade from pre-release version to
> the final one.
When I use a CentOS 7 as base system and install VZ7
No war here too.
I only was collecting disperse data, and I'm not against correcting
LVM/ZFS mentions if necessary.
My effort was focused on having a better comparison page to be
referenced for anyone.
El 06/06/16 a les 15:19, Narcis Garcia ha escrit:
> I've "debugged" and enhanced the main
> Yes, i know it's still possible to create an image which will be
compacted not that efficiently, but this becomes quite a rare case.
But in irl - get random prodaction node and first container with max delta
(data vs image size) -
ploop-balloon discard
Sergey, do you mean that supported distribution for OpenVZ/Virtuozzo
will be (or is) VzLinux OS?
Could you document this GNU/Linux distribution with a Wikipedia article?
Thanks.
El 06/06/16 a les 15:33, Sergey Bronnikov ha escrit:
> On 13:23 Mon 06 Jun , Volker Janzen wrote:
>> Hi Sergey,
>>
On 06.06.2016 13:51, Sergey Bronnikov wrote:
Why do you prefer simfs instead of ploop?
simfs allow usage OpenVZ containers with native ZFS storage.
Did you see comparison simfs vs ploop?
https://openvz.org/CT_storage_backends
Did you see comparison simfs vs ploop?
Hi Sergey,
> On 14:39 Sun 05 Jun , Volker Janzen wrote:
>>>
>>> Unfortunately no. We don't support upgrade from pre-release version to the
>>> final one.
>>
>> When I use a CentOS 7 as base system and install VZ7 afterward it's not
>> possible to upgrade, too?
>
> There is only one supported
I've "debugged" and enhanced the main Wiki comparison table:
https://openvz.org/CT_storage_backends
I've taken into account openvz_storage_backends.md
But somebody else could "migrate" ploop_issues.md too.
El 06/06/16 a les 13:41, Gena Makhomed ha escrit:
> On 06.06.2016 13:51, Sergey Bronnikov
Color coding on this page is also strange. Even advantages of simfs are marked
red and disadvantages of ploop - green :-)
-Original Message-
From: users-boun...@openvz.org [mailto:users-boun...@openvz.org] On Behalf Of
Narcis Garcia
Sent: Monday, June 6, 2016 14:43
To: users@openvz.org
Why the CT_storage_backends page is not showing any "No" in the ploop
column, and all "No"s in simfs columns are red (eg.compaction)
The "qcow format" row is redundant, as it could be "can use same host
filesystem".
The "No problems" row seems to be written to put a "Yes" in the "good"
column.
On 06/06/2016 01:51 PM, Sergey Bronnikov wrote:
Hi, Volker
On 14:39 Sun 05 Jun , Volker Janzen wrote:
Unfortunately no. We don't support upgrade from pre-release version to the
final one.
When I use a CentOS 7 as base system and install VZ7 afterward it's not
possible to upgrade, too?
Hi, Volker
On 14:39 Sun 05 Jun , Volker Janzen wrote:
> >
> > Unfortunately no. We don't support upgrade from pre-release version to the
> > final one.
>
> When I use a CentOS 7 as base system and install VZ7 afterward it's not
> possible to upgrade, too?
There is only one supported
19 matches
Mail list logo