Hello All,
I have started integrating the noVNC console to cloudstack. As my
mentor Syed suggested, it will be available along side the existing console
and can be accessed by passing a new parameter ( webscoket = true ) to the
existing console access url.
I have created a new context "/
Are you thinking of using OpenAPI(Swagger) to do the documentation?
Ron
On 05/06/2017 10:14 AM, Rafael Weingärtner wrote:
This might be a good excuse for an ACS 5.0! Maybe with some other additions
such as the support for OASIS CAMP or TOSCA?
It would be interesting to have a ROADMAP with thes
Please do not make any more roadmaps!
There are more than enough already and many include old promises about
updates that will be done on the page.
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Roadmap
https://cwiki.apache.org/confluence/display/CLOUDSTACK/2015+Plan
https://cwiki.apach
The wiki page exists for changes to be introduced at 5.0. It has been there for
more than a year so it needs tlc.
As for the API I sugest to start with a v2Beta api that we then migrate to v2
once we feel it can be maintained for a while without breaking backwards
compatibility. (and move to ACS
+1 for the API versioning. If you could create a wiki page Rene, we can
start documenting the changes.
Thanks,
-Syed
On Mon, Jun 5, 2017 at 10:14 AM, Rafael Weingärtner <
rafaelweingart...@gmail.com> wrote:
> This might be a good excuse for an ACS 5.0! Maybe with some other additions
> such as t
This might be a good excuse for an ACS 5.0! Maybe with some other additions
such as the support for OASIS CAMP or TOSCA?
It would be interesting to have a ROADMAP with these desires/wishes.
On Mon, Jun 5, 2017 at 8:52 AM, Simon Weller
wrote:
>
> +1. Echoing what Rohit pointed out, we have a lot
+1. Echoing what Rohit pointed out, we have a lot of cleanup to do :-) It
certainly makes it a lot easier though when you're not breaking compatibility
with existing code.
From: Rohit Yadav
Sent: Monday, June 5, 2017 4:04 AM
To: dev@cloudstack.apache.org
Subjec
+1 Good idea, though bear in mind there are 500+ APIs with no
modern-RESTful-standardization, a lot of work.
Regards.
From: Nitin Kumar Maharana
Sent: 05 June 2017 12:37:24
To: dev@cloudstack.apache.org
Subject: Re: [DISCUSS] API versioning
This looks good. +1
This looks good. +1
> On 04-Jun-2017, at 2:34 PM, Rene Moser wrote:
>
> Hi
>
> I recently developed ansible modules for the ACL API and ... found this
> has a really inconsistent API naming. E.g.
>
> createNetworkACL <<-- this creates an ACL rule
> createNetworkACLList <<-- this create the ACL
>
>
+1
boris.stoya...@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
> On Jun 4, 2017, at 7:15 PM, Tutkowski, Mike wrote:
>
> This sounds like a good idea to me.
>
>> On Jun 4, 2017, at 8:24 AM, Will Stevens wrote:
>>
>> +1. I like it.
>>
10 matches
Mail list logo
