Re: Committee to Sort through CCC Presentation Submissions

Hi everyone, This note is a follow-up to this discussion thread. Around the middle of April, the CloudStack PMC received an e-mail indicating (to our surprise) that we needed to provide the people organizing Montreal’s upcoming ApacheCon (which includes the CloudStack Collab Conf) with a

Re: [DISCUSS] CloudStack graceful shutdown

Thanks for the feedback Ilya. Then, we would only need to adapt this new feature introduced by you and ShapeBlue. On Sat, Apr 21, 2018 at 4:03 PM, ilya musayev wrote: > Rafael > > What you are suggesting - was already implemented. We've created Load > Balancing

Re: Default API response type: XML -> JSON

This can possibly fail some environments, but it depends on feedback from users. One option is to introduce global settings, (but we've got many of those) such that it's set to XML set in ConfigKey, but when a new env is installed (as part of server xml/sql) we set it to JSON. Another option

Re: [DISCUSS] 4.11.1.0 release

Thanks Wido (and Gabriel)! Update - I'll spend next 2.5 weeks to triage issues, work with everyone to reviews, fix, test PRs. The rough timeline is to work on that and try an get RC1 voting started by the end of next month, maybe as early as mid-May (14-15 May). If RC1 voting is not started

Re: Default API response type: XML -> JSON

I am +1 but with a versioned API (v2) because this would break most likely many API implementations. René On 04/23/2018 03:34 PM, Marc-Aurèle Brothier wrote: > Hi everyone, > > I thought it would be good to move from XML to JSON by default in the > response of the API if no response type is

Re: Default API response type: XML -> JSON

The time would be better spent on fixing the docs. It is time to turn Cloudstack into a production quality product with documentation that actually reflects the quality of the design and functionality. At the moment you have 2 people willing to work on the docs waiting for a committer to

Re: Default API response type: XML -> JSON

No problem Marc, but I still do not think that having a parameter is an overkill. My view is that if there is a decision to be made (regarding the default response type for requests), if we (as developers) take this decision (hardcode it), why not externalize it? I do not see as overkill, it is a

Re: Default API response type: XML -> JSON

@rafael - I think it's overkill to have this as a configuration option. We should have one default response type, or maybe not have a default one and enforce the use of the response type the client is willing to receive. On Mon, Apr 23, 2018 at 3:39 PM, Rafael Weingärtner <