Re: [DISCUSS] Changing events to include UUIDs, could it break your integration

2017-12-28 Thread Michael J McCafferty
Hi Rohit, This will break billing for us. We use Ubersmith. If this change is made, please make it optional (global setting for old and new way) or allow for different API versions either by option or path that is called. Thanks! Mike

RE: Upgrading to XenServer 7.x

2017-12-28 Thread Sebastian Gomez
Thank you for the explanation. Is good to know that there really were an incompatibility problem, and not a mistake during config. Thank you again for your work and time. Regards. El 28/12/2017 9:55, "Paul Angus" escribió: > Sebastian, > > XenServer 7.1 and 7.2 aren't

Re: [DISCUSS] Changing events to include UUIDs, could it break your integration

2017-12-28 Thread Nux!
+1 for this change as far as I am concerned, seems a good one. -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro - Original Message - > From: "Rohit Yadav" > To: "dev" , "users" >

Re: [DISCUSS] Changing events to include UUIDs, could it break your integration

2017-12-28 Thread Khosrow Moossavi
+1 on API versioning and make it really RESTful (cherry on top). I'm willing to participate on this change if voted for. Khosrow Moossavi CloudOps On Thu, Dec 28, 2017 at 11:07 AM, Rene Moser wrote: > Hi > > On 12/28/2017 10:52 AM, Rohit Yadav wrote: > > All, > > > > > >

Re: [DISCUSS] Changing events to include UUIDs, could it break your integration

2017-12-28 Thread Rene Moser
Hi On 12/28/2017 10:52 AM, Rohit Yadav wrote: > All, > > > We've come across a pull request which changes the event description to > use/export UUIDs instead of the numeric internal ID of a resource. I'm not > sure if this could potentially break any external integration such as > billing,

[DISCUSS] Changing events to include UUIDs, could it break your integration

2017-12-28 Thread Rohit Yadav
All, We've come across a pull request which changes the event description to use/export UUIDs instead of the numeric internal ID of a resource. I'm not sure if this could potentially break any external integration such as billing, crms etc. so wanted to get your feedback on this. My

RE: Upgrading to XenServer 7.x

2017-12-28 Thread Paul Angus
Sebastian, XenServer 7.1 and 7.2 aren't supported in 4.9.x - the main fix is to add the guest OS mappings to the database. These have been added for 4.11, but there seems to be a slight change in behaviour in XS7.1 when adding a host to a cluster which is confusing CloudStack. Kind

Re: Upgrading to XenServer 7.x

2017-12-28 Thread Sebastian Gomez
Hi all. I had a similar problem, but usign XenServer 7.2. It was a fresh installation from scratch. The system vms where created, but them *could'nt get the local link IP*, so the cloudstack agent never went up. After that, I found the compatibility matrix, where its specified that the