On 15-Jan-2013, at 6:29 PM, Rajesh Battala <[email protected]> wrote:
> Hi,
> When referring to the API's example (CreateLBStickinessPolicyCmd), this cmd
> is available in both the folder Cloud-api and Cloudstack/api. Why it is
> present in both the projects? For creating the new api command, we should
> write in which project?
> Is one of the project deprecated ?
Which other project are you referring to? git clean -f to clean any non-tracked
file.
There is only one:
./api/src/org/apache/cloudstack/api/command/user/loadbalancer/CreateLBStickinessPolicyCmd.java
If you referring to package names, you should follow
org.apache.cloudstack.api.{user,admin}.loadbalancer for any lb related apis.
If you're writing apis which will be part of a plugin, you're free to choose
any, but if the code gets contributed to asf, it has to be in
org.apache.cloudstack for uniformity. Watchout any cmd/response class on hints
on how to write cmd/response classes as per new/fixed annotations.
Next, if a feature does not need to be part of core cloudstack or is not
generic, it should be developed as a plugin or implement/fix layer such that
general stuff can be exposed so a plugin can be written.
Regards.
>
> Thanks
> Rajesh Battala
