Re: Why CloudStack 5

I'm in the favour of keeping the 4.x going because no API compatibility is broken, and as long as we are following semver there is no need. Calling a 4.x a 5.x just for the sake of bumping versions may cause some perception issue. Removal of unsupported/poc/incomplete features, plugins including

Re: Why CloudStack 5

That sounds reasonable to me. From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 5:25 PM To: users Cc: d...@cloudstack.apache.org Subject: Re: Why CloudStack 5 NetApp Security WARNING: This is an external email. Do not click links or open attachments un

Re: Why CloudStack 5

I would say that it is indeed a solid version. However, version 4.12 by itself is not breaking anything. Therefore, according to the semantic versioning, we cannot increase the ‘X’ bit. It is also interesting to consider that 4.12 has over 188 PRs merged into it. When we finish, we will probably h

Re: Why CloudStack 5

Is 4.12 a decent candidate to be branded 5.0 or might we be waiting for some specific set of backwards-incompatible updates? From: Rafael Weingärtner Sent: Wednesday, January 23, 2019 4:58 PM To: dev Cc: users Subject: Re: Why CloudStack 5 NetApp Security WARNI

Re: Why CloudStack 5

Hello Ivan, Can you provide reasons why not move to a version 5? To help you, I will provide why I think we should move to 5.0.0 after 4.12. Therefore, I would expect this 5.0.0 to be an LTS version as well. 1. To begin with, technically, we should already be in version 5 if we had been fol

Possible bug fix - sanity check please

The following issue was seen using CS 4.11.2 in advanced mode with security group isolation. VM (internal name i-2-29-VM) - is created and works fine with default security group allowing inbound SSH and ICMP echo request. Migrate the VM to another of the compute nodes and the VM migrates and

Re: 答复: CloudStack 4.11.2 Snapshot Revert fail

Hi I have just reproduced your issue (7.1 though, no updates, and not relevant I guess...) I changed VM (edit VM, while stopped) after it was previously snapshoot-ed successfully OS types vs restore results below: Centos 6.6 x64 fails to restore, CentOS 6.7 x64 fails to restore CentOS 6.5 x64 CAN

答复: 答复: CloudStack 4.11.2 Snapshot Revert fail

I modified and recompiled cloudstack4.11.2, and then I can complete the xenserver vm snapshot recovery. plugins/hypervisors/xenserver/src/com/cloud/hypervisor/xenserver/resource/CitrixResourceBase.java public VM createWorkingVM(final Connection conn, final String vmName, final String guestOST

答复: 答复: CloudStack 4.11.2 Snapshot Revert fail

I tried, modified the VM to CENTOS6.5 (64-bit) and reported the same error. 发件人: Andrija Panic 发送时间: 2019年1月23日 16:38 收件人: dev 抄送: users@cloudstack.apache.org 主题: Re: 答复: CloudStack 4.11.2 Snap

Re: 答复: CloudStack 4.11.2 Snapshot Revert fail

Hi, Did you try with other OS types - message above suggests that your Xen is seen as 6.5 version and doesn't support CentOS 7 - can you try to edit the VM to CentOS 6 or CentOS 7.1/7.2 etc ? Does the revert works then ? On Wed, 23 Jan 2019 at 02:58, Haijiao <18602198...@163.com> wrote: > This i