You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Donal Lafferty <do...@citrix.com> on 2012/12/14 00:48:30 UTC
Adding .NET/C# client to project
Where do client libraries go in the source tree? Does it matter if they're not written in Java?
The background is that there's a .NET SDK that can be added to the project. Architecturally, its similar to AWS' .NET SDK. Now, not all API calls are covered, but the API calls supported provide a guide adding additional support.
Re: Adding .NET/C# client to project
Posted by Rohit Yadav <ro...@citrix.com>.
On 14-Dec-2012, at 8:54 AM, David Nalley <da...@gnsa.us> wrote:
> On Fri, Dec 14, 2012 at 6:52 AM, Donal Lafferty
> <do...@citrix.com> wrote:
>> The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
>>
>> The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
>>
>> However, I wanted to know in advance how the code was going to fit in with the existing code base.
>>
>
> So you should propose such a thing. I am not sure that it should
> belong in the same repo as the core codebase.
> If we decide as a group that we do want such libraries, it might make
> better sense to make them independent repos.
>
> The difficulty is that this was developed external from the ASF, so
> that code would need to go through IP Clearance.
>
> My personal feeling is that this should probably live on github;
> unless you or others are planning to work on building community around
> maintaining said libraries, and I imagine most of this can be
> maintained by walking the API going forward. Generally speaking
> flinging 'finished' products over the wall doesn't give folks a lot of
> area to get involved.
That would be great and I think people should host their tools and libraries as separate git repositories and these or anything that has no dependency during any of the maven build lifecycles should not be part of the codebase.
Even in the current codebase, we don't have any library (Marvin generates the pythonic cloudstackAPI but it's gitignored, Marvin is just a generator + test client). You can reuse marvin's codegenerator.py to generate boilerplate classes for all the api cmds and responses for any language (not just python).
Regards.
Re: Adding .NET/C# client to project
Posted by Chip Childers <ch...@sungard.com>.
On Thu, Jan 3, 2013 at 10:23 AM, Simon Waterhouse
<Si...@eu.citrix.com> wrote:
> There is now a design document for the .NET SDK at https://cwiki.apache.org/CLOUDSTACK/net-sdk-design-document.html
>
> Comments welcome. If it is to go into the CloudStack-Extras repo, could someone advise on the procedure to submit it there please?
>
> Thanks
> Simon
Why don't you start by publishing it to your own repo, and then we can
decide to transfer it into the cloudstack-extras account after we sort
out the question of "procedure" there.
I'll start a new thread about the governance questions around cloudstack-extras.
-chip
RE: Adding .NET/C# client to project
Posted by Simon Waterhouse <Si...@eu.citrix.com>.
There is now a design document for the .NET SDK at https://cwiki.apache.org/CLOUDSTACK/net-sdk-design-document.html
Comments welcome. If it is to go into the CloudStack-Extras repo, could someone advise on the procedure to submit it there please?
Thanks
Simon
-----Original Message-----
From: Chip Childers [mailto:chip.childers@sungard.com]
Sent: 14 December 2012 20:03
To: cloudstack-dev@incubator.apache.org
Subject: Re: Adding .NET/C# client to project
On Fri, Dec 14, 2012 at 11:54 AM, David Nalley <da...@gnsa.us> wrote:
> On Fri, Dec 14, 2012 at 6:52 AM, Donal Lafferty
> <do...@citrix.com> wrote:
>> The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
>>
>> The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
>>
>> However, I wanted to know in advance how the code was going to fit in with the existing code base.
>>
>
> So you should propose such a thing. I am not sure that it should
> belong in the same repo as the core codebase.
> If we decide as a group that we do want such libraries, it might make
> better sense to make them independent repos.
We should discuss how to provide language bindings. To date, others outside of Citrix and the Apache CloudStack community have provided Ruby, Python, etc... bindings. I would suggest that we don't want them in the repo, but perhaps in the CloudStack-Extras github location?
> The difficulty is that this was developed external from the ASF, so
> that code would need to go through IP Clearance.
+1 - Donal, I really appreciate your point about wanting to go through
the proposal, design, jira, etc... process. The reality is that if the code already exists, then those are steps that become more of a retrofit for informational purposes only. Any code developed outside of the project needs to be grated through a software grant agreement and / or IP clearance.
-chip
Re: Adding .NET/C# client to project
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Dec 14, 2012 at 11:54 AM, David Nalley <da...@gnsa.us> wrote:
> On Fri, Dec 14, 2012 at 6:52 AM, Donal Lafferty
> <do...@citrix.com> wrote:
>> The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
>>
>> The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
>>
>> However, I wanted to know in advance how the code was going to fit in with the existing code base.
>>
>
> So you should propose such a thing. I am not sure that it should
> belong in the same repo as the core codebase.
> If we decide as a group that we do want such libraries, it might make
> better sense to make them independent repos.
We should discuss how to provide language bindings. To date, others
outside of Citrix and the Apache CloudStack community have provided
Ruby, Python, etc... bindings. I would suggest that we don't want
them in the repo, but perhaps in the CloudStack-Extras github
location?
> The difficulty is that this was developed external from the ASF, so
> that code would need to go through IP Clearance.
+1 - Donal, I really appreciate your point about wanting to go through
the proposal, design, jira, etc... process. The reality is that if
the code already exists, then those are steps that become more of a
retrofit for informational purposes only. Any code developed outside
of the project needs to be grated through a software grant agreement
and / or IP clearance.
-chip
Re: Adding .NET/C# client to project
Posted by David Nalley <da...@gnsa.us>.
On Fri, Dec 14, 2012 at 6:52 AM, Donal Lafferty
<do...@citrix.com> wrote:
> The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
>
> The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
>
> However, I wanted to know in advance how the code was going to fit in with the existing code base.
>
So you should propose such a thing. I am not sure that it should
belong in the same repo as the core codebase.
If we decide as a group that we do want such libraries, it might make
better sense to make them independent repos.
The difficulty is that this was developed external from the ASF, so
that code would need to go through IP Clearance.
My personal feeling is that this should probably live on github;
unless you or others are planning to work on building community around
maintaining said libraries, and I imagine most of this can be
maintained by walking the API going forward. Generally speaking
flinging 'finished' products over the wall doesn't give folks a lot of
area to get involved.
RE: Adding .NET/C# client to project
Posted by Donal Lafferty <do...@citrix.com>.
Collocation with CLI seems intuitive.
AFAIK, you can build a cmdlet library on to of the SDK. This would have to be done in a follow up project.
DL
-----Original Message-----
From: Koushik Das [mailto:koushik.das@citrix.com]
Sent: 14 December 2012 4:07 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Adding .NET/C# client to project
Donal,
There is already a CLI tool that Rohit had written. The C# client can also go in there and have a similar hierarchy in the source tree.
BTW, have you considered making it Powershell cmdlets instead?
Thanks,
Koushik
-----Original Message-----
From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
Sent: Friday, December 14, 2012 5:23 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Adding .NET/C# client to project
The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
However, I wanted to know in advance how the code was going to fit in with the existing code base.
-----Original Message-----
From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
Sent: 14 December 2012 12:01 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Adding .NET/C# client to project
On Fri, Dec 14, 2012 at 05:18:30AM +0530, Donal Lafferty wrote:
> Where do client libraries go in the source tree? Does it matter if
> they're not written in Java?
>
> The background is that there's a .NET SDK that can be added to the
> project. Architecturally, its similar to AWS' .NET SDK. Now, not all
> API calls are covered, but the API calls supported provide a guide
> adding additional support.
>
What .NET library and what license? Is the plan to include the binary to the codebase?
--
Prasanna.,
RE: Adding .NET/C# client to project
Posted by Koushik Das <ko...@citrix.com>.
Donal,
There is already a CLI tool that Rohit had written. The C# client can also go in there and have a similar hierarchy in the source tree.
BTW, have you considered making it Powershell cmdlets instead?
Thanks,
Koushik
-----Original Message-----
From: Donal Lafferty [mailto:donal.lafferty@citrix.com]
Sent: Friday, December 14, 2012 5:23 PM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Adding .NET/C# client to project
The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
However, I wanted to know in advance how the code was going to fit in with the existing code base.
-----Original Message-----
From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
Sent: 14 December 2012 12:01 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Adding .NET/C# client to project
On Fri, Dec 14, 2012 at 05:18:30AM +0530, Donal Lafferty wrote:
> Where do client libraries go in the source tree? Does it matter if
> they're not written in Java?
>
> The background is that there's a .NET SDK that can be added to the
> project. Architecturally, its similar to AWS' .NET SDK. Now, not all
> API calls are covered, but the API calls supported provide a guide
> adding additional support.
>
What .NET library and what license? Is the plan to include the binary to the codebase?
--
Prasanna.,
RE: Adding .NET/C# client to project
Posted by Donal Lafferty <do...@citrix.com>.
The library was developed in Citrix to simplify accessing the CS API from C#. The intent is to release code under the ASLv2.0 license.
The addition would follow community processes, which includes posting a feature spec on wiki, announcing this to community, answering questions on design, proposing code for review, and providing docs.
However, I wanted to know in advance how the code was going to fit in with the existing code base.
-----Original Message-----
From: Prasanna Santhanam [mailto:prasanna.santhanam@citrix.com]
Sent: 14 December 2012 12:01 AM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Adding .NET/C# client to project
On Fri, Dec 14, 2012 at 05:18:30AM +0530, Donal Lafferty wrote:
> Where do client libraries go in the source tree? Does it matter if
> they're not written in Java?
>
> The background is that there's a .NET SDK that can be added to the
> project. Architecturally, its similar to AWS' .NET SDK. Now, not all
> API calls are covered, but the API calls supported provide a guide
> adding additional support.
>
What .NET library and what license? Is the plan to include the binary to the codebase?
--
Prasanna.,
Re: Adding .NET/C# client to project
Posted by Prasanna Santhanam <pr...@citrix.com>.
On Fri, Dec 14, 2012 at 05:18:30AM +0530, Donal Lafferty wrote:
> Where do client libraries go in the source tree? Does it matter if
> they're not written in Java?
>
> The background is that there's a .NET SDK that can be added to the
> project. Architecturally, its similar to AWS' .NET SDK. Now, not
> all API calls are covered, but the API calls supported provide a
> guide adding additional support.
>
What .NET library and what license? Is the plan to include the binary
to the codebase?
--
Prasanna.,