[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] Function VM.set_VCPUs_number_live and license restriction error


  • To: xen-api@xxxxxxxxxxxxx
  • From: Narcís Escarpanter <nescarpanter@xxxxxxxxxxxxx>
  • Date: Tue, 5 Sep 2017 10:52:41 +0200
  • Delivery-date: Tue, 05 Sep 2017 08:52:57 +0000
  • List-id: User and development list for XCP and XAPI <xen-api.lists.xen.org>

Hi Olivier,

Thank you for your response.

It's so sad that a feature which was working from (as far as I can remember) XCP 1.6, now, magically, has been modified pushing users to pay a license for it. It's a step back in my opinion. Most users won't upgrade their platforms or maybe will switch to KVM (not for this feature, to avoid this kind of "surprises").
Still don't know why is not documented anywhere, it just appears that will be available from XenCenter (which seems correct to me). I can't understand a new version which removes features from older versions.

Anyway, nothing to do here.

Thank you (again).

Narcís Escarpanter Llandrich
CTO · SWHosting

T: +34 972 010 550
F: +34 972 010 555
www.swhosting.com

P Please consider the environment before printing this email.

On 09/04/2017 03:20 PM, Olivier Lambert wrote:
Hi Narcis,

Olivier from Xen Orchestra project here. We hit the same wall few
months ago, and we created an issue here:
https://bugs.xenserver.org/browse/XSO-722

Sadly, you need now XenServer Enterprise Edition to have this feature
working. The official reason is "that feature wasn't exposed in
XenCenter before", despite we used it in Xen Orchestra since ages.


Regards,


Olivier.

On Mon, Sep 4, 2017 at 10:22 AM, Narcís Escarpanter
<nescarpanter@xxxxxxxxxxxxx> wrote:
Hi Guys,

I was making some tests with new XenServer versions and I've seen that the
function VM.set_VCPUs_number_live was changed at ely (7.1)  release but it's
not been documented anywhere but GitHub repository
(http://xapi-project.github.io/xen-api/releases/ely.html)

It not appears at XenServer 7.1 release notes, either at 7.1 new licensed
features (just talks about XenCenter), etc.
I was wondering if someone else has been affected by this change, if there
is a reason and how to solve it (because it doesn't say which kind of
license is needed) or maybe is a XenAPI bug.

Maybe is not a question to ask to XenAPI mailing list but is the only place
that mentions the license restriction.

Thank you in advance.

Narcís Escarpanter Llandrich
CTO · SWHosting

T: +34 972 010 550
F: +34 972 010 555
www.swhosting.com

P Please consider the environment before printing this email.


_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
https://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
https://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
https://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.