Re: Api docs

[Ahmed Awlaqi]

Hi, I already made PR to fix it here:
https://github.com/apache/cloudstack-www/pull/215 and here:
https://github.com/apache/cloudstack/pull/9226

On Wed, 12 Jun 2024 at 10:31, Rohit Yadav  wrote:

> Hi Ahmed,
>
> What issue have you found? You may share here or report it as an issue
> https://github.com/apache/cloudstack-www/issues
>
> Thanks and Regards.
>
>
>
> 
> From: Wei ZHOU 
> Sent: Tuesday, June 11, 2024 18:00
> To: ahmed.awl...@sue.nl.invalid 
> Cc: dev@cloudstack.apache.org 
> Subject: Re: Api docs
>
> Hi,
>
> You can find the code at https://github.com/apache/cloudstack-www
>
>
> -Wei
>
> On Tue, Jun 11, 2024 at 2:29 PM Ahmed Awlaqi
>  wrote:
> >
> > Hi, I wanna know where can I find the code for this website
> > https://cloudstack.apache.org/api/ I found a mistake and would like to
> fix
> > it.
> >
> > --
> >  <https://www.multistax.com>
> >
> > --
> > The information in this message is confidential, and only intended for
> the
> > addressee(s). If you are not the person to whom this message is
> addressed,
> > you are hereby notified that any disclosure, reproduction, distribution
> or
> > use of this message is strictly prohibited. If you received this in
> error,
> > please inform the sender and delete the message without copying or
> opening
> > it.
>

-- 
 <https://www.multistax.com>

-- 
The information in this message is confidential, and only intended for the 
addressee(s). If you are not the person to whom this message is addressed, 
you are hereby notified that any disclosure, reproduction, distribution or 
use of this message is strictly prohibited. If you received this in error, 
please inform the sender and delete the message without copying or opening 
it.

Re: Api docs

[Rohit Yadav]

Hi Ahmed,

What issue have you found? You may share here or report it as an issue 
https://github.com/apache/cloudstack-www/issues

Thanks and Regards.
 



From: Wei ZHOU 
Sent: Tuesday, June 11, 2024 18:00
To: ahmed.awl...@sue.nl.invalid 
Cc: dev@cloudstack.apache.org 
Subject: Re: Api docs

Hi,

You can find the code at https://github.com/apache/cloudstack-www


-Wei

On Tue, Jun 11, 2024 at 2:29 PM Ahmed Awlaqi
 wrote:
>
> Hi, I wanna know where can I find the code for this website
> https://cloudstack.apache.org/api/ I found a mistake and would like to fix
> it.
>
> --
>  <https://www.multistax.com>
>
> --
> The information in this message is confidential, and only intended for the
> addressee(s). If you are not the person to whom this message is addressed,
> you are hereby notified that any disclosure, reproduction, distribution or
> use of this message is strictly prohibited. If you received this in error,
> please inform the sender and delete the message without copying or opening
> it.

Re: Api docs

[Wei ZHOU]

Hi,

You can find the code at https://github.com/apache/cloudstack-www


-Wei

On Tue, Jun 11, 2024 at 2:29 PM Ahmed Awlaqi
 wrote:
>
> Hi, I wanna know where can I find the code for this website
> https://cloudstack.apache.org/api/ I found a mistake and would like to fix
> it.
>
> --
>  
>
> --
> The information in this message is confidential, and only intended for the
> addressee(s). If you are not the person to whom this message is addressed,
> you are hereby notified that any disclosure, reproduction, distribution or
> use of this message is strictly prohibited. If you received this in error,
> please inform the sender and delete the message without copying or opening
> it.

Api docs

[Ahmed Awlaqi]

Hi, I wanna know where can I find the code for this website
https://cloudstack.apache.org/api/ I found a mistake and would like to fix
it.

-- 
 

-- 
The information in this message is confidential, and only intended for the 
addressee(s). If you are not the person to whom this message is addressed, 
you are hereby notified that any disclosure, reproduction, distribution or 
use of this message is strictly prohibited. If you received this in error, 
please inform the sender and delete the message without copying or opening 
it.

[GitHub] [cloudstack-go] rohityadavcloud merged pull request #65: Link to most current API docs 4.18

[via GitHub]

rohityadavcloud merged PR #65:
URL: https://github.com/apache/cloudstack-go/pull/65


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-go] jbampton opened a new pull request, #65: Link to most current API docs 4.18

[via GitHub]

jbampton opened a new pull request, #65:
URL: https://github.com/apache/cloudstack-go/pull/65

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: 4.9 api docs went missing

[Özhan Rüzgar Karaman]

its working again, thanks Rohit

On Fri, Jan 6, 2017 at 9:58 AM, Rohit Yadav <rohit.ya...@shapeblue.com>
wrote:

> I've fixed it now, please recheck.
>
>
> Regards.
>
> 
> From: ?zhan R?zgar Karaman <oruzgarkara...@gmail.com>
> Sent: 04 January 2017 17:59:10
> To: dev@cloudstack.apache.org
> Subject: Re: 4.9 api docs went missing
>
> Hi;
> I think they are setting up the api page for new CloudStack release, its
> not accessible till this Monday.
>
> Thanks
> ?zhan
>
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> @shapeblue
>
>
>
> On Wed, Jan 4, 2017 at 12:42 PM, Linas ?ilinskas <li...@host1plus.com
> <mailto:li...@host1plus.com>> wrote:
>
> Hello.
>
> Not sure if intentional, but 4.9 api docs at
> https://cloudstack.apache.org/api.html are missing now.
>
> It seems the page got reverted to a previous version.
>
> Linas ?ilinskas
> Head of Development
> [cid:part1.9B217719.D668B006@host1plus.com]
> website<http://www.host1plus.com/> facebook<https://www.facebook.
> com/Host1Plus> twitter<https://twitter.com/Host1Plus> linkedin<
> https://www.linkedin.com/company/digital-energy-technologies-ltd.>
>
> Host1Plus is a division of Digital Energy Technologies Ltd.
>
> 26 York Street, London W1U 6PZ, United Kingdom
>
>
>
>

Re: 4.9 api docs went missing

[Rohit Yadav]

I've fixed it now, please recheck.


Regards.


From: ?zhan R?zgar Karaman <oruzgarkara...@gmail.com>
Sent: 04 January 2017 17:59:10
To: dev@cloudstack.apache.org
Subject: Re: 4.9 api docs went missing

Hi;
I think they are setting up the api page for new CloudStack release, its not 
accessible till this Monday.

Thanks
?zhan


rohit.ya...@shapeblue.com 
www.shapeblue.com
53 Chandos Place, Covent Garden, London  WC2N 4HSUK
@shapeblue
  
 

On Wed, Jan 4, 2017 at 12:42 PM, Linas ?ilinskas 
<li...@host1plus.com<mailto:li...@host1plus.com>> wrote:

Hello.

Not sure if intentional, but 4.9 api docs at 
https://cloudstack.apache.org/api.html are missing now.

It seems the page got reverted to a previous version.

Linas ?ilinskas
Head of Development
[cid:part1.9B217719.D668B006@host1plus.com]
website<http://www.host1plus.com/> facebook<https://www.facebook.com/Host1Plus> 
twitter<https://twitter.com/Host1Plus> 
linkedin<https://www.linkedin.com/company/digital-energy-technologies-ltd.>

Host1Plus is a division of Digital Energy Technologies Ltd.

26 York Street, London W1U 6PZ, United Kingdom

Re: 4.9 api docs went missing

[Özhan Rüzgar Karaman]

Hi;
I think they are setting up the api page for new CloudStack release, its
not accessible till this Monday.

Thanks
Özhan

On Wed, Jan 4, 2017 at 12:42 PM, Linas Žilinskas <li...@host1plus.com>
wrote:

> Hello.
>
> Not sure if intentional, but 4.9 api docs at
> https://cloudstack.apache.org/api.html are missing now.
>
> It seems the page got reverted to a previous version.
>
> Linas Žilinskas
> Head of Development
> website <http://www.host1plus.com/> facebook
> <https://www.facebook.com/Host1Plus> twitter
> <https://twitter.com/Host1Plus> linkedin
> <https://www.linkedin.com/company/digital-energy-technologies-ltd.>
>
> Host1Plus is a division of Digital Energy Technologies Ltd.
>
> 26 York Street, London W1U 6PZ, United Kingdom
>
>
>

Build failed in Jenkins: build-4.6-api-docs #3

[jenkins]

See <http://jenkins.buildacloud.org/job/build-4.6-api-docs/3/>

--
[...truncated 28 lines...]
[INFO] Apache CloudStack Utils
[INFO] Apache CloudStack Framework
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Framework - Configuration
[INFO] Apache CloudStack API
[INFO] Apache CloudStack Framework - REST
[INFO] Apache CloudStack Framework - IPC
[INFO] Apache CloudStack Cloud Engine
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Framework - Security
[INFO] Apache CloudStack Core
[INFO] Apache CloudStack Agents
[INFO] Apache CloudStack Framework - Clustering
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Cloud Engine Schema Component
[INFO] Apache CloudStack Framework - Jobs
[INFO] Apache CloudStack Cloud Engine Internal Components API
[INFO] Apache CloudStack Server
[INFO] Apache CloudStack Usage Server
[INFO] Apache CloudStack Cloud Engine Orchestration Component
[INFO] Apache CloudStack Cloud Services
[INFO] Apache CloudStack Secondary Storage
[INFO] Apache CloudStack Secondary Storage Service
[INFO] Apache CloudStack Engine Storage Component
[INFO] Apache CloudStack Engine Storage Volume Component
[INFO] Apache CloudStack Engine Storage Image Component
[INFO] Apache CloudStack Engine Storage Data Motion Component
[INFO] Apache CloudStack Engine Storage Cache Component
[INFO] Apache CloudStack Engine Storage Snapshot Component
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Cloud Engine Service
[INFO] Apache CloudStack Plugin POM
[INFO] Apache CloudStack Plugin - API Rate Limit
[INFO] Apache CloudStack Plugin - Storage Volume default provider
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider
[INFO] Apache CloudStack Plugin - API SolidFire
[INFO] Apache CloudStack Plugin - API Discovery
[INFO] Apache CloudStack Plugin - ACL Static Role Based
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor
[INFO] Apache CloudStack Plugin - Explicit Dedication Processor
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
[INFO] Apache CloudStack Plugin - Implicit Dedication Planner
[INFO] Apache CloudStack Plugin - Skip Heurestics Planner
[INFO] Apache CloudStack Plugin - Host Allocator Random
[INFO] Apache CloudStack Plugin - Dedicated Resources
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM
[INFO] Apache CloudStack Plugin - Open vSwitch
[INFO] Apache CloudStack Plugin - Hypervisor XenServer
[INFO] Apache CloudStack Plugin - Hypervisor KVM
[INFO] Apache CloudStack Plugin - RabbitMQ Event Bus
[INFO] Apache CloudStack Plugin - In Memory Event Bus
[INFO] Apache CloudStack Plugin - Kafka Event Bus
[INFO] Apache CloudStack Plugin - Hypervisor Baremetal
[INFO] Apache CloudStack Plugin - Hypervisor UCS
[INFO] Apache CloudStack Plugin - Hypervisor Hyper-V
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM3
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer
[INFO] Apache CloudStack Plugin - Network Internal Load Balancer
[INFO] Apache CloudStack Framework - Spring Life Cycle
[INFO] Apache CloudStack Plugin - Network Juniper Contrail
[INFO] Apache CloudStack Plugin - Palo Alto
[INFO] Apache CloudStack Plugin - Network Netscaler
[INFO] Apache CloudStack Plugin - Network Nicira NVP
[INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment
[INFO] Apache CloudStack Plugin - Network Brocade VCS
[INFO] Apache CloudStack Plugin - Midokura Midonet
[INFO] Apache CloudStack Plugin - Stratosphere SSP
[INFO] Apache CloudStack Plugin - Network Opendaylight
[INFO] Apache CloudStack Plugin - Storage Allocator Random
[INFO] Apache CloudStack Plugin - User Authenticator LDAP
[INFO] Apache CloudStack Plugin - User Authenticator MD5
[INFO] Apache CloudStack Plugin - User Authenticator PBKDF2-SHA-256
[INFO] Apache CloudStack Plugin - User Authenticator Plain Text
[INFO] Apache CloudStack Plugin - User Authenticator SAML2
[INFO] Apache CloudStack Plugin - User Authenticator SHA256 Salted
[INFO] Apache CloudStack Plugin - Dns Notifier Example
[INFO] Apache CloudStack Plugin - Storage Image S3
[INFO] Apache CloudStack Plugin - Storage Image Swift provider
[INFO] Apache CloudStack Plugin - Storage Image default provider
[INFO] Apache CloudStack Plugin - Storage Image sample provider
[INFO] Apache CloudStack Plugin - Storage Volume Nexenta Provider
[INFO] Apache CloudStack Plugin - Storage Volume CloudByte Provider
[INFO] Apache CloudStack Plugin - Storage Volume sample provider
[INFO] Apache CloudStack Plugin - SNMP Alerts
[INFO] Apache CloudStack Plugin - Syslog Alerts
[INFO] Apache CloudStack Plugin - Network VXLAN
[INFO] Apache CloudStack Plugin - GloboDNS
[INFO] Apache CloudStack Plugin - NetApp File System
[INFO] Apache CloudStack Plugin - F5
[INFO] Apache CloudStack Plugin - Juniper SRX
[INFO] Apache CloudStack Plugin - Nuage VSP
[INFO] 

Build failed in Jenkins: build-4.6-api-docs #1

[jenkins]

See <http://jenkins.buildacloud.org/job/build-4.6-api-docs/1/>

--
[...truncated 34 lines...]
[INFO] Apache CloudStack Utils
[INFO] Apache CloudStack Framework
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Framework - Configuration
[INFO] Apache CloudStack API
[INFO] Apache CloudStack Framework - REST
[INFO] Apache CloudStack Framework - IPC
[INFO] Apache CloudStack Cloud Engine
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Framework - Security
[INFO] Apache CloudStack Core
[INFO] Apache CloudStack Agents
[INFO] Apache CloudStack Framework - Clustering
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Cloud Engine Schema Component
[INFO] Apache CloudStack Framework - Jobs
[INFO] Apache CloudStack Cloud Engine Internal Components API
[INFO] Apache CloudStack Server
[INFO] Apache CloudStack Usage Server
[INFO] Apache CloudStack Cloud Engine Orchestration Component
[INFO] Apache CloudStack Cloud Services
[INFO] Apache CloudStack Secondary Storage
[INFO] Apache CloudStack Secondary Storage Service
[INFO] Apache CloudStack Engine Storage Component
[INFO] Apache CloudStack Engine Storage Volume Component
[INFO] Apache CloudStack Engine Storage Image Component
[INFO] Apache CloudStack Engine Storage Data Motion Component
[INFO] Apache CloudStack Engine Storage Cache Component
[INFO] Apache CloudStack Engine Storage Snapshot Component
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Cloud Engine Service
[INFO] Apache CloudStack Plugin POM
[INFO] Apache CloudStack Plugin - API Rate Limit
[INFO] Apache CloudStack Plugin - Storage Volume default provider
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider
[INFO] Apache CloudStack Plugin - API SolidFire
[INFO] Apache CloudStack Plugin - API Discovery
[INFO] Apache CloudStack Plugin - ACL Static Role Based
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor
[INFO] Apache CloudStack Plugin - Explicit Dedication Processor
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
[INFO] Apache CloudStack Plugin - Implicit Dedication Planner
[INFO] Apache CloudStack Plugin - Skip Heurestics Planner
[INFO] Apache CloudStack Plugin - Host Allocator Random
[INFO] Apache CloudStack Plugin - Dedicated Resources
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM
[INFO] Apache CloudStack Plugin - Open vSwitch
[INFO] Apache CloudStack Plugin - Hypervisor XenServer
[INFO] Apache CloudStack Plugin - Hypervisor KVM
[INFO] Apache CloudStack Plugin - RabbitMQ Event Bus
[INFO] Apache CloudStack Plugin - In Memory Event Bus
[INFO] Apache CloudStack Plugin - Kafka Event Bus
[INFO] Apache CloudStack Plugin - Hypervisor Baremetal
[INFO] Apache CloudStack Plugin - Hypervisor UCS
[INFO] Apache CloudStack Plugin - Hypervisor Hyper-V
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM3
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer
[INFO] Apache CloudStack Plugin - Network Internal Load Balancer
[INFO] Apache CloudStack Framework - Spring Life Cycle
[INFO] Apache CloudStack Plugin - Network Juniper Contrail
[INFO] Apache CloudStack Plugin - Palo Alto
[INFO] Apache CloudStack Plugin - Network Netscaler
[INFO] Apache CloudStack Plugin - Network Nicira NVP
[INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment
[INFO] Apache CloudStack Plugin - Network Brocade VCS
[INFO] Apache CloudStack Plugin - Midokura Midonet
[INFO] Apache CloudStack Plugin - Stratosphere SSP
[INFO] Apache CloudStack Plugin - Network Opendaylight
[INFO] Apache CloudStack Plugin - Storage Allocator Random
[INFO] Apache CloudStack Plugin - User Authenticator LDAP
[INFO] Apache CloudStack Plugin - User Authenticator MD5
[INFO] Apache CloudStack Plugin - User Authenticator PBKDF2-SHA-256
[INFO] Apache CloudStack Plugin - User Authenticator Plain Text
[INFO] Apache CloudStack Plugin - User Authenticator SAML2
[INFO] Apache CloudStack Plugin - User Authenticator SHA256 Salted
[INFO] Apache CloudStack Plugin - Dns Notifier Example
[INFO] Apache CloudStack Plugin - Storage Image S3
[INFO] Apache CloudStack Plugin - Storage Image Swift provider
[INFO] Apache CloudStack Plugin - Storage Image default provider
[INFO] Apache CloudStack Plugin - Storage Image sample provider
[INFO] Apache CloudStack Plugin - Storage Volume Nexenta Provider
[INFO] Apache CloudStack Plugin - Storage Volume CloudByte Provider
[INFO] Apache CloudStack Plugin - Storage Volume sample provider
[INFO] Apache CloudStack Plugin - SNMP Alerts
[INFO] Apache CloudStack Plugin - Syslog Alerts
[INFO] Apache CloudStack Plugin - Network VXLAN
[INFO] Apache CloudStack Plugin - GloboDNS
[INFO] Apache CloudStack Plugin - NetApp File System
[INFO] Apache CloudStack Plugin - F5
[INFO] Apache CloudStack Plugin - Juniper SRX
[INFO] Apache CloudStack Plugin - Nuage VSP
[INFO] 

Build failed in Jenkins: build-4.6-api-docs #2

[jenkins]

See <http://jenkins.buildacloud.org/job/build-4.6-api-docs/2/>

--
[...truncated 29 lines...]
[INFO] Apache CloudStack Utils
[INFO] Apache CloudStack Framework
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Framework - Configuration
[INFO] Apache CloudStack API
[INFO] Apache CloudStack Framework - REST
[INFO] Apache CloudStack Framework - IPC
[INFO] Apache CloudStack Cloud Engine
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Framework - Security
[INFO] Apache CloudStack Core
[INFO] Apache CloudStack Agents
[INFO] Apache CloudStack Framework - Clustering
[INFO] Apache CloudStack Framework - Event Notification
[INFO] Apache CloudStack Cloud Engine Schema Component
[INFO] Apache CloudStack Framework - Jobs
[INFO] Apache CloudStack Cloud Engine Internal Components API
[INFO] Apache CloudStack Server
[INFO] Apache CloudStack Usage Server
[INFO] Apache CloudStack Cloud Engine Orchestration Component
[INFO] Apache CloudStack Cloud Services
[INFO] Apache CloudStack Secondary Storage
[INFO] Apache CloudStack Secondary Storage Service
[INFO] Apache CloudStack Engine Storage Component
[INFO] Apache CloudStack Engine Storage Volume Component
[INFO] Apache CloudStack Engine Storage Image Component
[INFO] Apache CloudStack Engine Storage Data Motion Component
[INFO] Apache CloudStack Engine Storage Cache Component
[INFO] Apache CloudStack Engine Storage Snapshot Component
[INFO] Apache CloudStack Cloud Engine API
[INFO] Apache CloudStack Cloud Engine Service
[INFO] Apache CloudStack Plugin POM
[INFO] Apache CloudStack Plugin - API Rate Limit
[INFO] Apache CloudStack Plugin - Storage Volume default provider
[INFO] Apache CloudStack Plugin - Storage Volume SolidFire Provider
[INFO] Apache CloudStack Plugin - API SolidFire
[INFO] Apache CloudStack Plugin - API Discovery
[INFO] Apache CloudStack Plugin - ACL Static Role Based
[INFO] Apache CloudStack Plugin - Host Anti-Affinity Processor
[INFO] Apache CloudStack Plugin - Explicit Dedication Processor
[INFO] Apache CloudStack Plugin - User Concentrated Pod Deployment Planner
[INFO] Apache CloudStack Plugin - User Dispersing Deployment Planner
[INFO] Apache CloudStack Plugin - Implicit Dedication Planner
[INFO] Apache CloudStack Plugin - Skip Heurestics Planner
[INFO] Apache CloudStack Plugin - Host Allocator Random
[INFO] Apache CloudStack Plugin - Dedicated Resources
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM
[INFO] Apache CloudStack Plugin - Open vSwitch
[INFO] Apache CloudStack Plugin - Hypervisor XenServer
[INFO] Apache CloudStack Plugin - Hypervisor KVM
[INFO] Apache CloudStack Plugin - RabbitMQ Event Bus
[INFO] Apache CloudStack Plugin - In Memory Event Bus
[INFO] Apache CloudStack Plugin - Kafka Event Bus
[INFO] Apache CloudStack Plugin - Hypervisor Baremetal
[INFO] Apache CloudStack Plugin - Hypervisor UCS
[INFO] Apache CloudStack Plugin - Hypervisor Hyper-V
[INFO] Apache CloudStack Plugin - Hypervisor OracleVM3
[INFO] Apache CloudStack Plugin - Network Elastic Load Balancer
[INFO] Apache CloudStack Plugin - Network Internal Load Balancer
[INFO] Apache CloudStack Framework - Spring Life Cycle
[INFO] Apache CloudStack Plugin - Network Juniper Contrail
[INFO] Apache CloudStack Plugin - Palo Alto
[INFO] Apache CloudStack Plugin - Network Netscaler
[INFO] Apache CloudStack Plugin - Network Nicira NVP
[INFO] Apache CloudStack Plugin - BigSwitch Virtual Network Segment
[INFO] Apache CloudStack Plugin - Network Brocade VCS
[INFO] Apache CloudStack Plugin - Midokura Midonet
[INFO] Apache CloudStack Plugin - Stratosphere SSP
[INFO] Apache CloudStack Plugin - Network Opendaylight
[INFO] Apache CloudStack Plugin - Storage Allocator Random
[INFO] Apache CloudStack Plugin - User Authenticator LDAP
[INFO] Apache CloudStack Plugin - User Authenticator MD5
[INFO] Apache CloudStack Plugin - User Authenticator PBKDF2-SHA-256
[INFO] Apache CloudStack Plugin - User Authenticator Plain Text
[INFO] Apache CloudStack Plugin - User Authenticator SAML2
[INFO] Apache CloudStack Plugin - User Authenticator SHA256 Salted
[INFO] Apache CloudStack Plugin - Dns Notifier Example
[INFO] Apache CloudStack Plugin - Storage Image S3
[INFO] Apache CloudStack Plugin - Storage Image Swift provider
[INFO] Apache CloudStack Plugin - Storage Image default provider
[INFO] Apache CloudStack Plugin - Storage Image sample provider
[INFO] Apache CloudStack Plugin - Storage Volume Nexenta Provider
[INFO] Apache CloudStack Plugin - Storage Volume CloudByte Provider
[INFO] Apache CloudStack Plugin - Storage Volume sample provider
[INFO] Apache CloudStack Plugin - SNMP Alerts
[INFO] Apache CloudStack Plugin - Syslog Alerts
[INFO] Apache CloudStack Plugin - Network VXLAN
[INFO] Apache CloudStack Plugin - GloboDNS
[INFO] Apache CloudStack Plugin - NetApp File System
[INFO] Apache CloudStack Plugin - F5
[INFO] Apache CloudStack Plugin - Juniper SRX
[INFO] Apache CloudStack Plugin - Nuage VSP
[INFO] 

API Docs

[Ian Duffy]

Folks,

With the amount of emails I seen about API docs not being found etc. I put
in a quick fix.

I just did a symbolic link between docs/api and api/. I created an
index.html within api/ that will redirect to api.html accordingly.

No idea if we can modify content folder directly with this
middleman/new-setup, if anyone is unhappy with the change please revert
it... I didn't want to see any more users been given 404 pages.

Thanks,
Ian

Re: Cloudstack API docs down?

[Ian Duffy]

Put in a quick fix for this, should fix all the linking issues.

On 14 May 2015 at 01:09, Marcus shadow...@gmail.com wrote:

 Maybe it's just a search thing. If I google 'cloudstack api doc', most of
 the links are broken. If I navigate to cloudstack.apache.org everything
 seems to work, but things have been rearranged so bookmarks or external
 links will need to be updated.


 On Wed, May 13, 2015 at 2:51 PM, Sebastien Goasguen run...@gmail.com
 wrote:

 
 
   On 13 May 2015, at 23:35, Marcus shadow...@gmail.com wrote:
  
   Looks like we're still missing some chunks of the website.
 
 
  Which ones ?
 
  
   On Mon, May 11, 2015 at 10:06 PM, Sebastien Goasguen run...@gmail.com
 
   wrote:
  
   Yes i know what that is. I am on it after breakfast
  
   -Sebastien
  
   On 12 May 2015, at 05:03, Abhinandan Prateek 
   abhinandan.prat...@shapeblue.com wrote:
  
   https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html
  
   On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com
   wrote:
  
   I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
   anyone else have the same problem or is it just me?
  
   Find out more about ShapeBlue and our range of CloudStack related
   services
  
   IaaS Cloud Design  Build
   http://shapeblue.com/iaas-cloud-design-and-build//
   CSForge – rapid IaaS deployment framework
  http://shapeblue.com/csforge/
   CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
   CloudStack Software Engineering
   http://shapeblue.com/cloudstack-software-engineering/
   CloudStack Infrastructure Support
   http://shapeblue.com/cloudstack-infrastructure-support/
   CloudStack Bootcamp Training Courses
   http://shapeblue.com/cloudstack-training/
  
   This email and any attachments to it may be confidential and are
   intended solely for the use of the individual to whom it is addressed.
  Any
   views or opinions expressed are solely those of the author and do not
   necessarily represent those of Shape Blue Ltd or related companies. If
  you
   are not the intended recipient of this email, you must neither take
 any
   action based upon its contents, nor copy or show it to anyone. Please
   contact the sender if you believe you have received this email in
 error.
   Shape Blue Ltd is a company incorporated in England  Wales. ShapeBlue
   Services India LLP is a company incorporated in India and is operated
  under
   license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
   company incorporated in Brasil and is operated under license from
 Shape
   Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic
  of
   South Africa and is traded under license from Shape Blue Ltd.
 ShapeBlue
  is
   a registered trademark.
  
 

Re: API Docs

[Abhinandan Prateek]

 On 14-May-2015, at 12:20 pm, Ian Duffy i...@ianduffy.ie wrote:

 Folks,

 With the amount of emails I seen about API docs not being found etc. I put
 in a quick fix.

 I just did a symbolic link between docs/api and api/. I created an
 index.html within api/ that will redirect to api.html accordingly.


 Thanks it works !

 No idea if we can modify content folder directly with this
 middleman/new-setup, if anyone is unhappy with the change please revert
 it... I didn't want to see any more users been given 404 pages.

 Thanks,
 Ian

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
CloudStack Software 
Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
CloudStack Infrastructure 
Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England  Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Cloudstack API docs down?

[Marcus]

Looks like we're still missing some chunks of the website.

On Mon, May 11, 2015 at 10:06 PM, Sebastien Goasguen run...@gmail.com
wrote:

 Yes i know what that is. I am on it after breakfast

 -Sebastien

  On 12 May 2015, at 05:03, Abhinandan Prateek 
 abhinandan.prat...@shapeblue.com wrote:
 
  https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html
 
  On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com
 wrote:
 
  I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
  anyone else have the same problem or is it just me?
 
  Find out more about ShapeBlue and our range of CloudStack related
 services
 
  IaaS Cloud Design  Build
 http://shapeblue.com/iaas-cloud-design-and-build//
  CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
  CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
  CloudStack Software Engineering
 http://shapeblue.com/cloudstack-software-engineering/
  CloudStack Infrastructure Support
 http://shapeblue.com/cloudstack-infrastructure-support/
  CloudStack Bootcamp Training Courses
 http://shapeblue.com/cloudstack-training/
 
  This email and any attachments to it may be confidential and are
 intended solely for the use of the individual to whom it is addressed. Any
 views or opinions expressed are solely those of the author and do not
 necessarily represent those of Shape Blue Ltd or related companies. If you
 are not the intended recipient of this email, you must neither take any
 action based upon its contents, nor copy or show it to anyone. Please
 contact the sender if you believe you have received this email in error.
 Shape Blue Ltd is a company incorporated in England  Wales. ShapeBlue
 Services India LLP is a company incorporated in India and is operated under
 license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
 company incorporated in Brasil and is operated under license from Shape
 Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
 South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is
 a registered trademark.

Re: Cloudstack API docs down?

[Marcus]

Maybe it's just a search thing. If I google 'cloudstack api doc', most of
the links are broken. If I navigate to cloudstack.apache.org everything
seems to work, but things have been rearranged so bookmarks or external
links will need to be updated.


On Wed, May 13, 2015 at 2:51 PM, Sebastien Goasguen run...@gmail.com
wrote:



  On 13 May 2015, at 23:35, Marcus shadow...@gmail.com wrote:
 
  Looks like we're still missing some chunks of the website.


 Which ones ?

 
  On Mon, May 11, 2015 at 10:06 PM, Sebastien Goasguen run...@gmail.com
  wrote:
 
  Yes i know what that is. I am on it after breakfast
 
  -Sebastien
 
  On 12 May 2015, at 05:03, Abhinandan Prateek 
  abhinandan.prat...@shapeblue.com wrote:
 
  https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html
 
  On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com
  wrote:
 
  I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
  anyone else have the same problem or is it just me?
 
  Find out more about ShapeBlue and our range of CloudStack related
  services
 
  IaaS Cloud Design  Build
  http://shapeblue.com/iaas-cloud-design-and-build//
  CSForge – rapid IaaS deployment framework
 http://shapeblue.com/csforge/
  CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
  CloudStack Software Engineering
  http://shapeblue.com/cloudstack-software-engineering/
  CloudStack Infrastructure Support
  http://shapeblue.com/cloudstack-infrastructure-support/
  CloudStack Bootcamp Training Courses
  http://shapeblue.com/cloudstack-training/
 
  This email and any attachments to it may be confidential and are
  intended solely for the use of the individual to whom it is addressed.
 Any
  views or opinions expressed are solely those of the author and do not
  necessarily represent those of Shape Blue Ltd or related companies. If
 you
  are not the intended recipient of this email, you must neither take any
  action based upon its contents, nor copy or show it to anyone. Please
  contact the sender if you believe you have received this email in error.
  Shape Blue Ltd is a company incorporated in England  Wales. ShapeBlue
  Services India LLP is a company incorporated in India and is operated
 under
  license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
  company incorporated in Brasil and is operated under license from Shape
  Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic
 of
  South Africa and is traded under license from Shape Blue Ltd. ShapeBlue
 is
  a registered trademark.
 

Re: Cloudstack API docs down?

[Sebastien Goasguen]

 On 13 May 2015, at 23:35, Marcus shadow...@gmail.com wrote:
 
 Looks like we're still missing some chunks of the website.


Which ones ?

 
 On Mon, May 11, 2015 at 10:06 PM, Sebastien Goasguen run...@gmail.com
 wrote:
 
 Yes i know what that is. I am on it after breakfast
 
 -Sebastien
 
 On 12 May 2015, at 05:03, Abhinandan Prateek 
 abhinandan.prat...@shapeblue.com wrote:
 
 https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html
 
 On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com
 wrote:
 
 I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
 anyone else have the same problem or is it just me?
 
 Find out more about ShapeBlue and our range of CloudStack related
 services
 
 IaaS Cloud Design  Build
 http://shapeblue.com/iaas-cloud-design-and-build//
 CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
 CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
 CloudStack Software Engineering
 http://shapeblue.com/cloudstack-software-engineering/
 CloudStack Infrastructure Support
 http://shapeblue.com/cloudstack-infrastructure-support/
 CloudStack Bootcamp Training Courses
 http://shapeblue.com/cloudstack-training/
 
 This email and any attachments to it may be confidential and are
 intended solely for the use of the individual to whom it is addressed. Any
 views or opinions expressed are solely those of the author and do not
 necessarily represent those of Shape Blue Ltd or related companies. If you
 are not the intended recipient of this email, you must neither take any
 action based upon its contents, nor copy or show it to anyone. Please
 contact the sender if you believe you have received this email in error.
 Shape Blue Ltd is a company incorporated in England  Wales. ShapeBlue
 Services India LLP is a company incorporated in India and is operated under
 license from Shape Blue Ltd. Shape Blue Brasil Consultoria Ltda is a
 company incorporated in Brasil and is operated under license from Shape
 Blue Ltd. ShapeBlue SA Pty Ltd is a company registered by The Republic of
 South Africa and is traded under license from Shape Blue Ltd. ShapeBlue is
 a registered trademark.
 

Cloudstack API docs down?

[Syed Mushtaq]

I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
anyone else have the same problem or is it just me?

Re: Cloudstack API docs down?

[Sebastien Goasguen]

Yes i know what that is. I am on it after breakfast

-Sebastien

 On 12 May 2015, at 05:03, Abhinandan Prateek 
 abhinandan.prat...@shapeblue.com wrote:
 
 https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html
 
 On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com wrote:
 
 I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
 anyone else have the same problem or is it just me?
 
 Find out more about ShapeBlue and our range of CloudStack related services
 
 IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
 CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
 CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
 CloudStack Software 
 Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
 CloudStack Infrastructure 
 Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
 CloudStack Bootcamp Training 
 Courseshttp://shapeblue.com/cloudstack-training/
 
 This email and any attachments to it may be confidential and are intended 
 solely for the use of the individual to whom it is addressed. Any views or 
 opinions expressed are solely those of the author and do not necessarily 
 represent those of Shape Blue Ltd or related companies. If you are not the 
 intended recipient of this email, you must neither take any action based upon 
 its contents, nor copy or show it to anyone. Please contact the sender if you 
 believe you have received this email in error. Shape Blue Ltd is a company 
 incorporated in England  Wales. ShapeBlue Services India LLP is a company 
 incorporated in India and is operated under license from Shape Blue Ltd. 
 Shape Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
 operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
 registered by The Republic of South Africa and is traded under license from 
 Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Cloudstack API docs down?

[Abhinandan Prateek]

https://cloudstack.apache.org/docs/api/apidocs-4.5/TOC_User.html

 On 12-May-2015, at 6:23 am, Syed Mushtaq syed1.mush...@gmail.com wrote:

 I'm getting a 404 for http://cloudstack.apache.org/docs/api/  Does
 anyone else have the same problem or is it just me?

Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design  Buildhttp://shapeblue.com/iaas-cloud-design-and-build//
CSForge – rapid IaaS deployment frameworkhttp://shapeblue.com/csforge/
CloudStack Consultinghttp://shapeblue.com/cloudstack-consultancy/
CloudStack Software 
Engineeringhttp://shapeblue.com/cloudstack-software-engineering/
CloudStack Infrastructure 
Supporthttp://shapeblue.com/cloudstack-infrastructure-support/
CloudStack Bootcamp Training Courseshttp://shapeblue.com/cloudstack-training/

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England  Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Review Request 24300: listIsos call does not return isdynamicallyscalable in the response attributes as mentioned in API docs

[Damodar Reddy Talakanti]

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/24300/
---

Review request for cloudstack and Kishan Kavala.


Bugs: https://issues.apache.org/jira/browse/CLOUDSTACK-7245

https://issues.apache.org/jira/browse/https://issues.apache.org/jira/browse/CLOUDSTACK-7245


Repository: cloudstack-git


Description
---

listIsos call does not return isdynamicallyscalable in the response attributes 
as mentioned in API docs


Diffs
-

  server/src/com/cloud/api/query/dao/TemplateJoinDaoImpl.java 4c8ada1 

Diff: https://reviews.apache.org/r/24300/diff/


Testing
---

Tested by calling listIsos as admin and normal user on master branch


Thanks,

Damodar Reddy Talakanti

Re: [DOCS] Problem generating 4.4 API docs

[sebgoa]

On Jun 2, 2014, at 9:16 PM, Will Stevens wstev...@cloudops.com wrote:

 I started playing with the 'javasphinx' project to see if it would work for 
 generating the API docs.
 
 So here is the basic idea of what it produces.
 
 I created docs for the following cloudstack directory: 
 'api/src/org/apache/cloudstack/api/'
 
 I then took the RST files and generated the html docs from it.  I got a lot 
 of errors like the following when trying to build the html docs with 
 'sphinx-build':
 
 ERROR: Unknown directive type java:package
 ERROR: Unknown directive type java:import
 ERROR: Unknown directive type java:type
 ERROR: Unknown directive type java:constructor
 ERROR: Unknown directive type java:method
 etc...
 
 I am not sure if this is a long term issue, but we will probably have to 
 solve other bigger problems first.
 
 For example, here is the RST output for the CreateNetwork command for an 
 Admin:
 
 .. java:import:: org.apache.log4j Logger
 
 .. java:import:: org.apache.cloudstack.api APICommand
 
 .. java:import:: org.apache.cloudstack.api ApiConstants
 
 .. java:import:: org.apache.cloudstack.api ApiErrorCode
 
 .. java:import:: org.apache.cloudstack.api Parameter
 
 .. java:import:: org.apache.cloudstack.api ResponseObject.ResponseView
 
 .. java:import:: org.apache.cloudstack.api ServerApiException
 
 .. java:import:: org.apache.cloudstack.api.command.user.network 
 CreateNetworkCmd
 
 .. java:import:: org.apache.cloudstack.api.response NetworkResponse
 
 .. java:import:: com.cloud.exception ConcurrentOperationException
 
 .. java:import:: com.cloud.exception InsufficientCapacityException
 
 .. java:import:: com.cloud.exception ResourceAllocationException
 
 .. java:import:: com.cloud.network Network
 
 CreateNetworkCmdByAdmin
 ===
 
 .. java:package:: org.apache.cloudstack.api.command.admin.network
:noindex:
 
 .. java:type:: @APICommand public class CreateNetworkCmdByAdmin extends 
 CreateNetworkCmd
 
 Fields
 --
 s_logger
 
 
 .. java:field:: public static final Logger s_logger
:outertype: CreateNetworkCmdByAdmin
 
 Methods
 ---
 execute
 ^^^
 
 .. java:method:: @Override public void execute() throws 
 InsufficientCapacityException, ConcurrentOperationException, 
 ResourceAllocationException
:outertype: CreateNetworkCmdByAdmin
 
 getVlan
 ^^^
 
 .. java:method:: public String getVlan()
:outertype: CreateNetworkCmdByAdmin
 
 
 I have also attached the themed output for this doc...
 
 Obviously, this is not enough detail for us to use for actual API 
 documentation.
 
 If we wanted to go with this sort of documentation, we would need to really 
 look at how the details are being discovered...
 
 Do any of you have ideas or suggestions on this front?
 

I got to the same stage as you,

Might not be worth pursuing. I will try to contact some of the 
javasphinx-developer and see what they say.

-sebastien

 Cheers,
 
 Will
 
 
 
 On Fri, May 30, 2014 at 4:33 PM, Sebastien Goasguen run...@gmail.com wrote:
 
 On May 30, 2014, at 4:25 PM, Will Stevens wstev...@cloudops.com wrote:
 
  By clean install you mean starting from scratch, not 'mvn clean install'
  right?  I have been doing mvn clean installs…
 
 
 Will, quickly stated I think that piece of code is a nightmare + folks have 
 complained about our apidocs.
 
 Since you are familiar with sphinx now, maybe you can give a try with:
 http://bronto.github.io/javasphinx/
 
 Create some brand new api docs …that we can build automatically like the 
 regular docs.
 
 2 cts
 
  Will
 
 
  On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org wrote:
 
  Hi Will,
 
  Based on my last memories of the apidocs tool and maven poms, I think it
  used to scan built jar artifacts and reference them against something like
  a properties file (commands.properties?) and internally scans bunch of
  annotations in available class files to find apis and create apidocs. The
  ApiDiscovery plugin uses the same approach to discover available apis but
  during load time instead of build time.
 
  I would also recommend a clean install in case there are any caching
  issues. See if this helps.
 
  Regards.
 
 
  On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
  wrote:
 
  Hey All,
  Paul Angus and I have both tested this and this is what we are seeing.
 
  When we compile the the 'master' branch, the docs in
  'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
  Yes, we know that the versions that appear in the output is hardcoded in
  the XSL files, but that is not what we are using as our reference.
 
  So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
  have
  also confirmed that when a build is done, the
  'tools/apidoc/log/@AGENTLOG@
  '
  shows that the
  'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
  directory is being referenced.
 
  However, when I check the 'tools/apidoc/target/commands.xml', it does not
  include

Re: [DOCS] Problem generating 4.4 API docs

[Will Stevens]

I started playing with the 'javasphinx' project to see if it would work for
generating the API docs.

So here is the basic idea of what it produces.

I created docs for the following cloudstack directory:
'api/src/org/apache/cloudstack/api/'

I then took the RST files and generated the html docs from it.  I got a lot
of errors like the following when trying to build the html docs with
'sphinx-build':

ERROR: Unknown directive type java:package
ERROR: Unknown directive type java:import
ERROR: Unknown directive type java:type
ERROR: Unknown directive type java:constructor
ERROR: Unknown directive type java:method
etc...

I am not sure if this is a long term issue, but we will probably have to
solve other bigger problems first.

For example, here is the RST output for the CreateNetwork command for an
Admin:

.. java:import:: org.apache.log4j Logger

.. java:import:: org.apache.cloudstack.api APICommand

.. java:import:: org.apache.cloudstack.api ApiConstants

.. java:import:: org.apache.cloudstack.api ApiErrorCode

.. java:import:: org.apache.cloudstack.api Parameter

.. java:import:: org.apache.cloudstack.api ResponseObject.ResponseView

.. java:import:: org.apache.cloudstack.api ServerApiException

.. java:import:: org.apache.cloudstack.api.command.user.network
CreateNetworkCmd

.. java:import:: org.apache.cloudstack.api.response NetworkResponse

.. java:import:: com.cloud.exception ConcurrentOperationException

.. java:import:: com.cloud.exception InsufficientCapacityException

.. java:import:: com.cloud.exception ResourceAllocationException

.. java:import:: com.cloud.network Network

CreateNetworkCmdByAdmin
===

.. java:package:: org.apache.cloudstack.api.command.admin.network
   :noindex:

.. java:type:: @APICommand public class CreateNetworkCmdByAdmin extends
CreateNetworkCmd

Fields
--
s_logger


.. java:field:: public static final Logger s_logger
   :outertype: CreateNetworkCmdByAdmin

Methods
---
execute
^^^

.. java:method:: @Override public void execute() throws
InsufficientCapacityException, ConcurrentOperationException,
ResourceAllocationException
   :outertype: CreateNetworkCmdByAdmin

getVlan
^^^

.. java:method:: public String getVlan()
   :outertype: CreateNetworkCmdByAdmin


I have also attached the themed output for this doc...

Obviously, this is not enough detail for us to use for actual API
documentation.

If we wanted to go with this sort of documentation, we would need to really
look at how the details are being discovered...

Do any of you have ideas or suggestions on this front?

Cheers,

Will



On Fri, May 30, 2014 at 4:33 PM, Sebastien Goasguen run...@gmail.com
wrote:


 On May 30, 2014, at 4:25 PM, Will Stevens wstev...@cloudops.com wrote:

  By clean install you mean starting from scratch, not 'mvn clean install'
  right?  I have been doing mvn clean installs…
 

 Will, quickly stated I think that piece of code is a nightmare + folks
 have complained about our apidocs.

 Since you are familiar with sphinx now, maybe you can give a try with:
 http://bronto.github.io/javasphinx/

 Create some brand new api docs …that we can build automatically like the
 regular docs.

 2 cts

  Will
 
 
  On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org
 wrote:
 
  Hi Will,
 
  Based on my last memories of the apidocs tool and maven poms, I think it
  used to scan built jar artifacts and reference them against something
 like
  a properties file (commands.properties?) and internally scans bunch of
  annotations in available class files to find apis and create apidocs.
 The
  ApiDiscovery plugin uses the same approach to discover available apis
 but
  during load time instead of build time.
 
  I would also recommend a clean install in case there are any caching
  issues. See if this helps.
 
  Regards.
 
 
  On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
  wrote:
 
  Hey All,
  Paul Angus and I have both tested this and this is what we are seeing.
 
  When we compile the the 'master' branch, the docs in
  'tools/apidoc/target/xmldoc/html', but they appear to be the wrong
 docs.
  Yes, we know that the versions that appear in the output is hardcoded
 in
  the XSL files, but that is not what we are using as our reference.
 
  So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
  have
  also confirmed that when a build is done, the
  'tools/apidoc/log/@AGENTLOG@
  '
  shows that the
  'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
  directory is being referenced.
 
  However, when I check the 'tools/apidoc/target/commands.xml', it does
 not
  include API calls which were added in 4.3 (I can verify with the
  published
  4.3 API docs).  Also, the docs that are generated in the
  'tools/apidoc/target/xmldoc/html' directory also does not have the API
  calls that were added in 4.3.
 
  I am stumped as to how this is happening.  It is almost like the
  4.4.0-SNAPSHOT is actually the 4.2.0

[DOCS] Problem generating 4.4 API docs

[Will Stevens]

Hey All,
Paul Angus and I have both tested this and this is what we are seeing.

When we compile the the 'master' branch, the docs in
'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
 Yes, we know that the versions that appear in the output is hardcoded in
the XSL files, but that is not what we are using as our reference.

So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I have
also confirmed that when a build is done, the 'tools/apidoc/log/@AGENTLOG@'
shows that the 'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
directory is being referenced.

However, when I check the 'tools/apidoc/target/commands.xml', it does not
include API calls which were added in 4.3 (I can verify with the published
4.3 API docs).  Also, the docs that are generated in the
'tools/apidoc/target/xmldoc/html' directory also does not have the API
calls that were added in 4.3.

I am stumped as to how this is happening.  It is almost like the
4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how that
would be possible.

If someone who understands this piece of the software can have a look and
verify what we are seeing, we would appreciate the insight...

Thanks,

Will

Re: [DOCS] Problem generating 4.4 API docs

[Rohit Yadav]

Hi Will,

Based on my last memories of the apidocs tool and maven poms, I think it
used to scan built jar artifacts and reference them against something like
a properties file (commands.properties?) and internally scans bunch of
annotations in available class files to find apis and create apidocs. The
ApiDiscovery plugin uses the same approach to discover available apis but
during load time instead of build time.

I would also recommend a clean install in case there are any caching
issues. See if this helps.

Regards.


On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com wrote:

 Hey All,
 Paul Angus and I have both tested this and this is what we are seeing.

 When we compile the the 'master' branch, the docs in
 'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
  Yes, we know that the versions that appear in the output is hardcoded in
 the XSL files, but that is not what we are using as our reference.

 So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I have
 also confirmed that when a build is done, the 'tools/apidoc/log/@AGENTLOG@
 '
 shows that the 'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
 directory is being referenced.

 However, when I check the 'tools/apidoc/target/commands.xml', it does not
 include API calls which were added in 4.3 (I can verify with the published
 4.3 API docs).  Also, the docs that are generated in the
 'tools/apidoc/target/xmldoc/html' directory also does not have the API
 calls that were added in 4.3.

 I am stumped as to how this is happening.  It is almost like the
 4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how that
 would be possible.

 If someone who understands this piece of the software can have a look and
 verify what we are seeing, we would appreciate the insight...

 Thanks,

 Will

Re: [DOCS] Problem generating 4.4 API docs

[Will Stevens]

By clean install you mean starting from scratch, not 'mvn clean install'
right?  I have been doing mvn clean installs...

Will


On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org wrote:

 Hi Will,

 Based on my last memories of the apidocs tool and maven poms, I think it
 used to scan built jar artifacts and reference them against something like
 a properties file (commands.properties?) and internally scans bunch of
 annotations in available class files to find apis and create apidocs. The
 ApiDiscovery plugin uses the same approach to discover available apis but
 during load time instead of build time.

 I would also recommend a clean install in case there are any caching
 issues. See if this helps.

 Regards.


 On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
 wrote:

  Hey All,
  Paul Angus and I have both tested this and this is what we are seeing.
 
  When we compile the the 'master' branch, the docs in
  'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
   Yes, we know that the versions that appear in the output is hardcoded in
  the XSL files, but that is not what we are using as our reference.
 
  So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
 have
  also confirmed that when a build is done, the
 'tools/apidoc/log/@AGENTLOG@
  '
  shows that the
 'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
  directory is being referenced.
 
  However, when I check the 'tools/apidoc/target/commands.xml', it does not
  include API calls which were added in 4.3 (I can verify with the
 published
  4.3 API docs).  Also, the docs that are generated in the
  'tools/apidoc/target/xmldoc/html' directory also does not have the API
  calls that were added in 4.3.
 
  I am stumped as to how this is happening.  It is almost like the
  4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how that
  would be possible.
 
  If someone who understands this piece of the software can have a look and
  verify what we are seeing, we would appreciate the insight...
 
  Thanks,
 
  Will
 

Re: [DOCS] Problem generating 4.4 API docs

[Sebastien Goasguen]

On May 30, 2014, at 4:25 PM, Will Stevens wstev...@cloudops.com wrote:

 By clean install you mean starting from scratch, not 'mvn clean install'
 right?  I have been doing mvn clean installs…
 

Will, quickly stated I think that piece of code is a nightmare + folks have 
complained about our apidocs.

Since you are familiar with sphinx now, maybe you can give a try with:
http://bronto.github.io/javasphinx/

Create some brand new api docs …that we can build automatically like the 
regular docs.

2 cts

 Will
 
 
 On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org wrote:
 
 Hi Will,
 
 Based on my last memories of the apidocs tool and maven poms, I think it
 used to scan built jar artifacts and reference them against something like
 a properties file (commands.properties?) and internally scans bunch of
 annotations in available class files to find apis and create apidocs. The
 ApiDiscovery plugin uses the same approach to discover available apis but
 during load time instead of build time.
 
 I would also recommend a clean install in case there are any caching
 issues. See if this helps.
 
 Regards.
 
 
 On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
 wrote:
 
 Hey All,
 Paul Angus and I have both tested this and this is what we are seeing.
 
 When we compile the the 'master' branch, the docs in
 'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
 Yes, we know that the versions that appear in the output is hardcoded in
 the XSL files, but that is not what we are using as our reference.
 
 So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
 have
 also confirmed that when a build is done, the
 'tools/apidoc/log/@AGENTLOG@
 '
 shows that the
 'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
 directory is being referenced.
 
 However, when I check the 'tools/apidoc/target/commands.xml', it does not
 include API calls which were added in 4.3 (I can verify with the
 published
 4.3 API docs).  Also, the docs that are generated in the
 'tools/apidoc/target/xmldoc/html' directory also does not have the API
 calls that were added in 4.3.
 
 I am stumped as to how this is happening.  It is almost like the
 4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how that
 would be possible.
 
 If someone who understands this piece of the software can have a look and
 verify what we are seeing, we would appreciate the insight...
 
 Thanks,
 
 Will
 
 

Re: [DOCS] Problem generating 4.4 API docs

[Rohit Yadav]

Check if git branch or source code in question is correct, git clean -df
(note: this will remove files not tracked by git), check that
the commands.properties has the API you were searching in apidocs, remove
~/.m2 and do mvn clean install, if that does not work check if the
API/plugin in question implements a valid CloudStack API (annotations
etc.). Lastly, if nothing worked probably apidocs needs fixing.

Regards.


On Sat, May 31, 2014 at 1:55 AM, Will Stevens wstev...@cloudops.com wrote:

 By clean install you mean starting from scratch, not 'mvn clean install'
 right?  I have been doing mvn clean installs...

 Will


 On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org wrote:

  Hi Will,
 
  Based on my last memories of the apidocs tool and maven poms, I think it
  used to scan built jar artifacts and reference them against something
 like
  a properties file (commands.properties?) and internally scans bunch of
  annotations in available class files to find apis and create apidocs. The
  ApiDiscovery plugin uses the same approach to discover available apis but
  during load time instead of build time.
 
  I would also recommend a clean install in case there are any caching
  issues. See if this helps.
 
  Regards.
 
 
  On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
  wrote:
 
   Hey All,
   Paul Angus and I have both tested this and this is what we are seeing.
  
   When we compile the the 'master' branch, the docs in
   'tools/apidoc/target/xmldoc/html', but they appear to be the wrong
 docs.
Yes, we know that the versions that appear in the output is hardcoded
 in
   the XSL files, but that is not what we are using as our reference.
  
   So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
  have
   also confirmed that when a build is done, the
  'tools/apidoc/log/@AGENTLOG@
   '
   shows that the
  'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
   directory is being referenced.
  
   However, when I check the 'tools/apidoc/target/commands.xml', it does
 not
   include API calls which were added in 4.3 (I can verify with the
  published
   4.3 API docs).  Also, the docs that are generated in the
   'tools/apidoc/target/xmldoc/html' directory also does not have the API
   calls that were added in 4.3.
  
   I am stumped as to how this is happening.  It is almost like the
   4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how
 that
   would be possible.
  
   If someone who understands this piece of the software can have a look
 and
   verify what we are seeing, we would appreciate the insight...
  
   Thanks,
  
   Will
  
 

Re: [DOCS] Problem generating 4.4 API docs

[Will Stevens]

Thanks Rohit, I will do all those steps.

I know the git branch is correct, but I will do a clean anyway.

Removing the maven repositories is a good idea.

Thx,

Will


On Fri, May 30, 2014 at 4:35 PM, Rohit Yadav bhais...@apache.org wrote:

 Check if git branch or source code in question is correct, git clean -df
 (note: this will remove files not tracked by git), check that
 the commands.properties has the API you were searching in apidocs, remove
 ~/.m2 and do mvn clean install, if that does not work check if the
 API/plugin in question implements a valid CloudStack API (annotations
 etc.). Lastly, if nothing worked probably apidocs needs fixing.

 Regards.


 On Sat, May 31, 2014 at 1:55 AM, Will Stevens wstev...@cloudops.com
 wrote:

  By clean install you mean starting from scratch, not 'mvn clean install'
  right?  I have been doing mvn clean installs...
 
  Will
 
 
  On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org
 wrote:
 
   Hi Will,
  
   Based on my last memories of the apidocs tool and maven poms, I think
 it
   used to scan built jar artifacts and reference them against something
  like
   a properties file (commands.properties?) and internally scans bunch of
   annotations in available class files to find apis and create apidocs.
 The
   ApiDiscovery plugin uses the same approach to discover available apis
 but
   during load time instead of build time.
  
   I would also recommend a clean install in case there are any caching
   issues. See if this helps.
  
   Regards.
  
  
   On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
   wrote:
  
Hey All,
Paul Angus and I have both tested this and this is what we are
 seeing.
   
When we compile the the 'master' branch, the docs in
'tools/apidoc/target/xmldoc/html', but they appear to be the wrong
  docs.
 Yes, we know that the versions that appear in the output is
 hardcoded
  in
the XSL files, but that is not what we are using as our reference.
   
So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I
   have
also confirmed that when a build is done, the
   'tools/apidoc/log/@AGENTLOG@
'
shows that the
   'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'
directory is being referenced.
   
However, when I check the 'tools/apidoc/target/commands.xml', it does
  not
include API calls which were added in 4.3 (I can verify with the
   published
4.3 API docs).  Also, the docs that are generated in the
'tools/apidoc/target/xmldoc/html' directory also does not have the
 API
calls that were added in 4.3.
   
I am stumped as to how this is happening.  It is almost like the
4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how
  that
would be possible.
   
If someone who understands this piece of the software can have a look
  and
verify what we are seeing, we would appreciate the insight...
   
Thanks,
   
Will
   
  
 

Re: [DOCS] Problem generating 4.4 API docs

[Ove Ewerlid]

On 05/30/2014 10:40 PM, Will Stevens wrote:

Thanks Rohit, I will do all those steps.

I know the git branch is correct, but I will do a clean anyway.

Removing the maven repositories is a good idea.


NB; for this issue, e.g., fear of old cloudstack stuff being used rather 
then newly built bits, removing by;

 rm -rf ~/.m2/repository/org/apache/cloudstack
is a good idea.
Removing all of ~/.m2 will cause the entire cache, including non 
cloudstack artifacts, to need to be re-downloaded. That takes time, and 
the same artifact dependencies will be downloaded again hence a time 
consuming noop.


To mitigate ~/.m2 artifact cache download time during build from 
scratch, and the purpose is not to repopulate ~/.m2 cache from scratch, 
this directory minus cloudstack artifacts, can be saved and preloaded 
prior to the build start. If there are new artifact updates, maven will 
detect this and only download the new stuff.


/Ove


Thx,

Will


On Fri, May 30, 2014 at 4:35 PM, Rohit Yadav bhais...@apache.org wrote:


Check if git branch or source code in question is correct, git clean -df
(note: this will remove files not tracked by git), check that
the commands.properties has the API you were searching in apidocs, remove
~/.m2 and do mvn clean install, if that does not work check if the
API/plugin in question implements a valid CloudStack API (annotations
etc.). Lastly, if nothing worked probably apidocs needs fixing.

Regards.


On Sat, May 31, 2014 at 1:55 AM, Will Stevens wstev...@cloudops.com
wrote:


By clean install you mean starting from scratch, not 'mvn clean install'
right?  I have been doing mvn clean installs...

Will


On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org

wrote:



Hi Will,

Based on my last memories of the apidocs tool and maven poms, I think

it

used to scan built jar artifacts and reference them against something

like

a properties file (commands.properties?) and internally scans bunch of
annotations in available class files to find apis and create apidocs.

The

ApiDiscovery plugin uses the same approach to discover available apis

but

during load time instead of build time.

I would also recommend a clean install in case there are any caching
issues. See if this helps.

Regards.


On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
wrote:


Hey All,
Paul Angus and I have both tested this and this is what we are

seeing.


When we compile the the 'master' branch, the docs in
'tools/apidoc/target/xmldoc/html', but they appear to be the wrong

docs.

  Yes, we know that the versions that appear in the output is

hardcoded

in

the XSL files, but that is not what we are using as our reference.

So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I

have

also confirmed that when a build is done, the

'tools/apidoc/log/@AGENTLOG@

'
shows that the

'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'

directory is being referenced.

However, when I check the 'tools/apidoc/target/commands.xml', it does

not

include API calls which were added in 4.3 (I can verify with the

published

4.3 API docs).  Also, the docs that are generated in the
'tools/apidoc/target/xmldoc/html' directory also does not have the

API

calls that were added in 4.3.

I am stumped as to how this is happening.  It is almost like the
4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how

that

would be possible.

If someone who understands this piece of the software can have a look

and

verify what we are seeing, we would appreciate the insight...

Thanks,

Will












--
Ove Everlid
System Administrator / Architect / SDN-  Automation-  Linux-hacker
Mobile: +46706668199 (dedicated work mobile)
Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)

Re: [DOCS] Problem generating 4.4 API docs

[Will Stevens]

I have completely started from scratch with a new clone of the CloudStack
repo.

Master is now pointing to 4.5, so I checked out the 4.4 branch.

I put all the deps in place as well as the vhd-util file.

I completely removed my ~/.m2 directory so I am starting from completely
clean.

I checked the directory structure for 'commands.*' before building and the
only one was the following:

client/tomcatconf/commands.properties.in

It does not have all of the API calls in it (the UCS section for example is
not up to date).

I built the project successfully and then did the same check to see what
'commands.*' files were available.

Now I have:

client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/classes/commands.properties
client/target/conf/commands.properties
client/target/generated-webapp/WEB-INF/classes/commands.properties
client/tomcatconf/commands.properties.in
tools/apidoc/target/commands.xml

I checked the 'client/target/conf/commands.properties' and verified it does
not have the updated UCS api calls.

I checked the generated docs and they are still pre-4.3.

How do we go about getting commands.properties updated?  Why is the
commands.properties two releases behind?  Its not even up to date for 4.3.

Cheers,

Will


On Fri, May 30, 2014 at 4:59 PM, Ove Ewerlid ove.ewer...@oracle.com wrote:

 On 05/30/2014 10:40 PM, Will Stevens wrote:

 Thanks Rohit, I will do all those steps.

 I know the git branch is correct, but I will do a clean anyway.

 Removing the maven repositories is a good idea.


 NB; for this issue, e.g., fear of old cloudstack stuff being used rather
 then newly built bits, removing by;
  rm -rf ~/.m2/repository/org/apache/cloudstack
 is a good idea.
 Removing all of ~/.m2 will cause the entire cache, including non
 cloudstack artifacts, to need to be re-downloaded. That takes time, and the
 same artifact dependencies will be downloaded again hence a time consuming
 noop.

 To mitigate ~/.m2 artifact cache download time during build from scratch,
 and the purpose is not to repopulate ~/.m2 cache from scratch, this
 directory minus cloudstack artifacts, can be saved and preloaded prior to
 the build start. If there are new artifact updates, maven will detect this
 and only download the new stuff.

 /Ove


  Thx,

 Will


 On Fri, May 30, 2014 at 4:35 PM, Rohit Yadav bhais...@apache.org wrote:

  Check if git branch or source code in question is correct, git clean -df
 (note: this will remove files not tracked by git), check that
 the commands.properties has the API you were searching in apidocs, remove
 ~/.m2 and do mvn clean install, if that does not work check if the
 API/plugin in question implements a valid CloudStack API (annotations
 etc.). Lastly, if nothing worked probably apidocs needs fixing.

 Regards.


 On Sat, May 31, 2014 at 1:55 AM, Will Stevens wstev...@cloudops.com
 wrote:

  By clean install you mean starting from scratch, not 'mvn clean install'
 right?  I have been doing mvn clean installs...

 Will


 On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav bhais...@apache.org

 wrote:


  Hi Will,

 Based on my last memories of the apidocs tool and maven poms, I think

 it

 used to scan built jar artifacts and reference them against something

 like

 a properties file (commands.properties?) and internally scans bunch of
 annotations in available class files to find apis and create apidocs.

 The

 ApiDiscovery plugin uses the same approach to discover available apis

 but

 during load time instead of build time.

 I would also recommend a clean install in case there are any caching
 issues. See if this helps.

 Regards.


 On Sat, May 31, 2014 at 1:14 AM, Will Stevens wstev...@cloudops.com
 wrote:

  Hey All,
 Paul Angus and I have both tested this and this is what we are

 seeing.


 When we compile the the 'master' branch, the docs in
 'tools/apidoc/target/xmldoc/html', but they appear to be the wrong

 docs.

   Yes, we know that the versions that appear in the output is

 hardcoded

 in

 the XSL files, but that is not what we are using as our reference.

 So in the 'tools/apidoc/pom.xml' the 4.4.0-SNAPSHOT is referenced.  I

 have

 also confirmed that when a build is done, the

 'tools/apidoc/log/@AGENTLOG@

 '
 shows that the

 'client/target/cloud-client-ui-4.4.0-SNAPSHOT/WEB-INF/lib/'

 directory is being referenced.

 However, when I check the 'tools/apidoc/target/commands.xml', it does

 not

 include API calls which were added in 4.3 (I can verify with the

 published

 4.3 API docs).  Also, the docs that are generated in the
 'tools/apidoc/target/xmldoc/html' directory also does not have the

 API

 calls that were added in 4.3.

 I am stumped as to how this is happening.  It is almost like the
 4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how

 that

 would be possible.

 If someone who understands this piece of the software can have a look

 and

 verify what we are seeing, we would appreciate the insight...

 Thanks

Re: [DOCS] Problem generating 4.4 API docs

[Rohit Yadav]

/'
 
  directory is being referenced.
 
  However, when I check the 'tools/apidoc/target/commands.xml', it
 does
 
  not
 
  include API calls which were added in 4.3 (I can verify with the
 
  published
 
  4.3 API docs).  Also, the docs that are generated in the
  'tools/apidoc/target/xmldoc/html' directory also does not have the
 
  API
 
  calls that were added in 4.3.
 
  I am stumped as to how this is happening.  It is almost like the
  4.4.0-SNAPSHOT is actually the 4.2.0-SNAPSHOT, but I am not sure how
 
  that
 
  would be possible.
 
  If someone who understands this piece of the software can have a
 look
 
  and
 
  verify what we are seeing, we would appreciate the insight...
 
  Thanks,
 
  Will
 
 
 
 
 
 
 
  --
  Ove Everlid
  System Administrator / Architect / SDN-  Automation-  Linux-hacker
  Mobile: +46706668199 (dedicated work mobile)
  Country: Sweden, timezone; Middle Europan Time (MET or GMT+1)
 

Re: Incomplete API docs?

[David Nalley]

Yes - it's really a bug in ApiXmlDocWriter. Please file it.

--David

On Thu, Oct 17, 2013 at 4:39 PM, Demetrius Tsitrelis
demetrius.tsitre...@citrix.com wrote:
 Do you still think there needs to be a bug filed for the missing APIs?

 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Thursday, October 17, 2013 1:21 PM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?


 +1

 Radhika on the 4.3 release page I have solicited volunteers for different 
 release activities. Looks like the high level tasks could use a better 
 breakdown, do you want to take a stab at breaking doc into sub tasks and 
 folks interested can fill in their name.

 Animesh

 -Original Message-
 From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
 Sent: Wednesday, October 16, 2013 3:24 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?

 Hi All,

 Our API documentation requires a serious refurbishment.

 How about creating a doc sprint for enhancing API documentation ?

 I am in the process of setting up a Wiki page at
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+S
 pr
 int+for+Enhancing+API+Documentation to track this activity. Feel free
 int+for+Enhancing+API+to
 add/ edit/ remove the page content.

 I request all of you to volunteer so that we will have a comprehensive
 API doc set by next release.

 Appreciate your feedback.

 Regards
 -Radhika



 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Wednesday, October 16, 2013 7:36 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?

 Demetrius do you mind creating an issue in JIRA?

  -Original Message-
  From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
  Sent: Tuesday, October 15, 2013 5:15 PM
  To: dev@cloudstack.apache.org
  Subject: Re: Incomplete API docs?
 
  The commands.xml generated as a result of mvn build (mvn clean
  install
  - P developer,systemvm -DskipTests), doesn't include the commands
  mentioned by Demetrius. Looks like some regression bug in
  ApiXmlDocWriter - it used to include all the commands in 3.0.x
  version of the code.
 
  -Alena.
 
  From: Demetrius Tsitrelis
  dtsitre...@live.commailto:dtsitre...@live.com
  Reply-To:
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Date: Tuesday, October 15, 2013 4:33 PM
  To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Subject: Incomplete API docs?
 
 
 
  I grep'ed the source code and came up with a list of the APIs which
  the UI uses.  That list is at the end of this message.
  You can see that many of them (addNetscalerLoadBalancer,
  addVmwareDc,
  etc.) are not in the generated API documentation which appears at
  http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.htm
  l
 
 
  Is this something wrong with the input files or is a tool at fault?
 
 
  Here's the list of APIs used by the UI:
 
  activateProject
 
  addAccountToProject
 
  addBaremetalDhcp
 
  addBaremetalPxeKickStartServer
 
  addCluster
 
  addHost
 
  addImageStore
 
  addIpToNic
 
  addLdapConfiguration
 
  addNetscalerLoadBalancer
 
  addNetworkServiceProvider
 
  addNicToVirtualMachine
 
  addRegion
 
  addTrafficType
 
  addUcsManager
 
  addVmwareDc
 
  addVpnUser
 
  archiveAlerts
 
  archiveEvents
 
  assignToGlobalLoadBalancerRule
 
  assignToLoadBalancerRule
 
  assignVirtualMachine
 
  associateIpAddress
 
  associateUcsProfileToBlade
 
  attachIso
 
  attachVolume
 
  authorizeSecurityGroupEgress
 
  authorizeSecurityGroupIngress
 
  cancelHostMaintenance
 
  cancelStorageMaintenance
 
  configureInternalLoadBalancerElement
 
  configureVirtualRouterElement
 
  copyIso
 
  copyTemplate
 
  createAccount
 
  createAffinityGroup
 
  createAutoScalePolicy
 
  createAutoScaleVmGroup
 
  createAutoScaleVmProfile
 
  createCondition
 
  createDiskOffering
 
  createDomain
 
  createEgressFirewallRule
 
  createFirewallRule
 
  createGlobalLoadBalancerRule
 
  createIpForwardingRule
 
  createLBHealthCheckPolicy
 
  createLBStickinessPolicy
 
  createLoadBalancer
 
  createLoadBalancerRule
 
  createNetwork
 
  createNetworkACL
 
  createNetworkACLList
 
  createNetworkOffering
 
  createPhysicalNetwork
 
  createPod
 
  createPortableIpRange
 
  createPortForwardingRule
 
  createPrivateGateway
 
  createProject
 
  createRemoteAccessVpn
 
  createSecondaryStagingStore
 
  createSecurityGroup
 
  createServiceOffering
 
  createSnapshot
 
  createSnapshotPolicy
 
  createStaticRoute
 
  createStorageNetworkIpRange
 
  createStoragePool
 
  createTags
 
  createTemplate
 
  createUser
 
  createVlanIpRange
 
  createVMSnapshot
 
  createVolume
 
  createVPC
 
  createVpnConnection
 
  createVpnCustomerGateway
 
  createVpnGateway
 
  createZone
 
  dedicateCluster

Re: Incomplete API docs?

[David Nalley]

On Wed, Oct 16, 2013 at 6:24 AM, Radhika Puthiyetath
radhika.puthiyet...@citrix.com wrote:
 Hi All,

 Our API documentation requires a serious refurbishment.



Hi Radhika:

What do you see as lacking in our current API docs (aside from them
not working ;) )



 How about creating a doc sprint for enhancing API documentation ?

 I am in the process of setting up a Wiki page at 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+Sprint+for+Enhancing+API+Documentation
  to track this activity. Feel free to add/ edit/ remove the page content.

 I request all of you to volunteer so that we will have a comprehensive API 
 doc set by next release.

 Appreciate your feedback.

Re: Incomplete API docs?

[David Nalley]

That's actually a great point. One of my favorites is:
http://cloudstack.apache.org/docs/api/apidocs-4.2/root_admin/changeServiceForSystemVm.html

Is ID really UUID? or the human readable ID?

--David.

On Mon, Oct 21, 2013 at 5:32 AM, Radhika Puthiyetath
radhika.puthiyet...@citrix.com wrote:
 Hi David,

 They are simple one liners that do not convey  anything about the API.

 -Original Message-
 From: David Nalley [mailto:da...@gnsa.us]
 Sent: Monday, October 21, 2013 2:54 PM
 To: dev@cloudstack.apache.org
 Subject: Re: Incomplete API docs?

 On Wed, Oct 16, 2013 at 6:24 AM, Radhika Puthiyetath 
 radhika.puthiyet...@citrix.com wrote:
 Hi All,

 Our API documentation requires a serious refurbishment.



 Hi Radhika:

 What do you see as lacking in our current API docs (aside from them not 
 working ;) )



 How about creating a doc sprint for enhancing API documentation ?

 I am in the process of setting up a Wiki page at 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+Sprint+for+Enhancing+API+Documentation
  to track this activity. Feel free to add/ edit/ remove the page content.

 I request all of you to volunteer so that we will have a comprehensive API 
 doc set by next release.

 Appreciate your feedback.

RE: Incomplete API docs?

[Demetrius Tsitrelis]

Filed as CLOUDSTACK-4912.

-Original Message-
From: David Nalley [mailto:da...@gnsa.us] 
Sent: Monday, October 21, 2013 2:22 AM
To: dev@cloudstack.apache.org
Subject: Re: Incomplete API docs?

Yes - it's really a bug in ApiXmlDocWriter. Please file it.

--David

On Thu, Oct 17, 2013 at 4:39 PM, Demetrius Tsitrelis 
demetrius.tsitre...@citrix.com wrote:
 Do you still think there needs to be a bug filed for the missing APIs?

 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Thursday, October 17, 2013 1:21 PM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?


 +1

 Radhika on the 4.3 release page I have solicited volunteers for different 
 release activities. Looks like the high level tasks could use a better 
 breakdown, do you want to take a stab at breaking doc into sub tasks and 
 folks interested can fill in their name.

 Animesh

 -Original Message-
 From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
 Sent: Wednesday, October 16, 2013 3:24 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?

 Hi All,

 Our API documentation requires a serious refurbishment.

 How about creating a doc sprint for enhancing API documentation ?

 I am in the process of setting up a Wiki page at 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+
 S
 pr
 int+for+Enhancing+API+Documentation to track this activity. Feel free 
 int+for+Enhancing+API+to
 add/ edit/ remove the page content.

 I request all of you to volunteer so that we will have a 
 comprehensive API doc set by next release.

 Appreciate your feedback.

 Regards
 -Radhika



 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Wednesday, October 16, 2013 7:36 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?

 Demetrius do you mind creating an issue in JIRA?

  -Original Message-
  From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
  Sent: Tuesday, October 15, 2013 5:15 PM
  To: dev@cloudstack.apache.org
  Subject: Re: Incomplete API docs?
 
  The commands.xml generated as a result of mvn build (mvn clean 
  install
  - P developer,systemvm -DskipTests), doesn't include the commands 
  mentioned by Demetrius. Looks like some regression bug in 
  ApiXmlDocWriter - it used to include all the commands in 3.0.x 
  version of the code.
 
  -Alena.
 
  From: Demetrius Tsitrelis
  dtsitre...@live.commailto:dtsitre...@live.com
  Reply-To:
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Date: Tuesday, October 15, 2013 4:33 PM
  To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Subject: Incomplete API docs?
 
 
 
  I grep'ed the source code and came up with a list of the APIs which 
  the UI uses.  That list is at the end of this message.
  You can see that many of them (addNetscalerLoadBalancer, 
  addVmwareDc,
  etc.) are not in the generated API documentation which appears at 
  http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.ht
  m
  l
 
 
  Is this something wrong with the input files or is a tool at fault?
 
 
  Here's the list of APIs used by the UI:
 
  activateProject
 
  addAccountToProject
 
  addBaremetalDhcp
 
  addBaremetalPxeKickStartServer
 
  addCluster
 
  addHost
 
  addImageStore
 
  addIpToNic
 
  addLdapConfiguration
 
  addNetscalerLoadBalancer
 
  addNetworkServiceProvider
 
  addNicToVirtualMachine
 
  addRegion
 
  addTrafficType
 
  addUcsManager
 
  addVmwareDc
 
  addVpnUser
 
  archiveAlerts
 
  archiveEvents
 
  assignToGlobalLoadBalancerRule
 
  assignToLoadBalancerRule
 
  assignVirtualMachine
 
  associateIpAddress
 
  associateUcsProfileToBlade
 
  attachIso
 
  attachVolume
 
  authorizeSecurityGroupEgress
 
  authorizeSecurityGroupIngress
 
  cancelHostMaintenance
 
  cancelStorageMaintenance
 
  configureInternalLoadBalancerElement
 
  configureVirtualRouterElement
 
  copyIso
 
  copyTemplate
 
  createAccount
 
  createAffinityGroup
 
  createAutoScalePolicy
 
  createAutoScaleVmGroup
 
  createAutoScaleVmProfile
 
  createCondition
 
  createDiskOffering
 
  createDomain
 
  createEgressFirewallRule
 
  createFirewallRule
 
  createGlobalLoadBalancerRule
 
  createIpForwardingRule
 
  createLBHealthCheckPolicy
 
  createLBStickinessPolicy
 
  createLoadBalancer
 
  createLoadBalancerRule
 
  createNetwork
 
  createNetworkACL
 
  createNetworkACLList
 
  createNetworkOffering
 
  createPhysicalNetwork
 
  createPod
 
  createPortableIpRange
 
  createPortForwardingRule
 
  createPrivateGateway
 
  createProject
 
  createRemoteAccessVpn
 
  createSecondaryStagingStore
 
  createSecurityGroup
 
  createServiceOffering
 
  createSnapshot
 
  createSnapshotPolicy
 
  createStaticRoute
 
  createStorageNetworkIpRange
 
  createStoragePool
 
  createTags

RE: Incomplete API docs?

[Animesh Chaturvedi]

+1

Radhika on the 4.3 release page I have solicited volunteers for different 
release activities. Looks like the high level tasks could use a better 
breakdown, do you want to take a stab at breaking doc into sub tasks and folks 
interested can fill in their name.

Animesh

 -Original Message-
 From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
 Sent: Wednesday, October 16, 2013 3:24 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?
 
 Hi All,
 
 Our API documentation requires a serious refurbishment.
 
 How about creating a doc sprint for enhancing API documentation ?
 
 I am in the process of setting up a Wiki page at
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+Spr
 int+for+Enhancing+API+Documentation to track this activity. Feel free to
 add/ edit/ remove the page content.
 
 I request all of you to volunteer so that we will have a comprehensive
 API doc set by next release.
 
 Appreciate your feedback.
 
 Regards
 -Radhika
 
 
 
 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Wednesday, October 16, 2013 7:36 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?
 
 Demetrius do you mind creating an issue in JIRA?
 
  -Original Message-
  From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
  Sent: Tuesday, October 15, 2013 5:15 PM
  To: dev@cloudstack.apache.org
  Subject: Re: Incomplete API docs?
 
  The commands.xml generated as a result of mvn build (mvn clean install
  - P developer,systemvm -DskipTests), doesn't include the commands
  mentioned by Demetrius. Looks like some regression bug in
  ApiXmlDocWriter - it used to include all the commands in 3.0.x version
  of the code.
 
  -Alena.
 
  From: Demetrius Tsitrelis
  dtsitre...@live.commailto:dtsitre...@live.com
  Reply-To:
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Date: Tuesday, October 15, 2013 4:33 PM
  To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Subject: Incomplete API docs?
 
 
 
  I grep'ed the source code and came up with a list of the APIs which
  the UI uses.  That list is at the end of this message.
  You can see that many of them (addNetscalerLoadBalancer, addVmwareDc,
  etc.) are not in the generated API documentation which appears at
  http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html
 
 
  Is this something wrong with the input files or is a tool at fault?
 
 
  Here's the list of APIs used by the UI:
 
  activateProject
 
  addAccountToProject
 
  addBaremetalDhcp
 
  addBaremetalPxeKickStartServer
 
  addCluster
 
  addHost
 
  addImageStore
 
  addIpToNic
 
  addLdapConfiguration
 
  addNetscalerLoadBalancer
 
  addNetworkServiceProvider
 
  addNicToVirtualMachine
 
  addRegion
 
  addTrafficType
 
  addUcsManager
 
  addVmwareDc
 
  addVpnUser
 
  archiveAlerts
 
  archiveEvents
 
  assignToGlobalLoadBalancerRule
 
  assignToLoadBalancerRule
 
  assignVirtualMachine
 
  associateIpAddress
 
  associateUcsProfileToBlade
 
  attachIso
 
  attachVolume
 
  authorizeSecurityGroupEgress
 
  authorizeSecurityGroupIngress
 
  cancelHostMaintenance
 
  cancelStorageMaintenance
 
  configureInternalLoadBalancerElement
 
  configureVirtualRouterElement
 
  copyIso
 
  copyTemplate
 
  createAccount
 
  createAffinityGroup
 
  createAutoScalePolicy
 
  createAutoScaleVmGroup
 
  createAutoScaleVmProfile
 
  createCondition
 
  createDiskOffering
 
  createDomain
 
  createEgressFirewallRule
 
  createFirewallRule
 
  createGlobalLoadBalancerRule
 
  createIpForwardingRule
 
  createLBHealthCheckPolicy
 
  createLBStickinessPolicy
 
  createLoadBalancer
 
  createLoadBalancerRule
 
  createNetwork
 
  createNetworkACL
 
  createNetworkACLList
 
  createNetworkOffering
 
  createPhysicalNetwork
 
  createPod
 
  createPortableIpRange
 
  createPortForwardingRule
 
  createPrivateGateway
 
  createProject
 
  createRemoteAccessVpn
 
  createSecondaryStagingStore
 
  createSecurityGroup
 
  createServiceOffering
 
  createSnapshot
 
  createSnapshotPolicy
 
  createStaticRoute
 
  createStorageNetworkIpRange
 
  createStoragePool
 
  createTags
 
  createTemplate
 
  createUser
 
  createVlanIpRange
 
  createVMSnapshot
 
  createVolume
 
  createVPC
 
  createVpnConnection
 
  createVpnCustomerGateway
 
  createVpnGateway
 
  createZone
 
  dedicateCluster
 
  dedicateGuestVlanRange
 
  dedicateHost
 
  dedicatePod
 
  dedicatePublicIpRange
 
  dedicateZone
 
  deleteAccount
 
  deleteAccountFromProject
 
  deleteAffinityGroup
 
  deleteAlerts
 
  deleteBigSwitchVnsDevice
 
  deleteCiscoNexusVSM
 
  deleteCluster
 
  deleteCondition
 
  deleteDiskOffering
 
  deleteDomain
 
  deleteEgressFirewallRule
 
  deleteEvents
 
  deleteF5LoadBalancer
 
  deleteFirewallRule
 
  deleteGlobalLoadBalancerRule
 
  deleteHost

RE: Incomplete API docs?

[Demetrius Tsitrelis]

Do you still think there needs to be a bug filed for the missing APIs?

-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Thursday, October 17, 2013 1:21 PM
To: dev@cloudstack.apache.org
Subject: RE: Incomplete API docs?


+1

Radhika on the 4.3 release page I have solicited volunteers for different 
release activities. Looks like the high level tasks could use a better 
breakdown, do you want to take a stab at breaking doc into sub tasks and folks 
interested can fill in their name.

Animesh

 -Original Message-
 From: Radhika Puthiyetath [mailto:radhika.puthiyet...@citrix.com]
 Sent: Wednesday, October 16, 2013 3:24 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?
 
 Hi All,
 
 Our API documentation requires a serious refurbishment.
 
 How about creating a doc sprint for enhancing API documentation ?
 
 I am in the process of setting up a Wiki page at 
 https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+S
 pr
 int+for+Enhancing+API+Documentation to track this activity. Feel free 
 int+for+Enhancing+API+to
 add/ edit/ remove the page content.
 
 I request all of you to volunteer so that we will have a comprehensive 
 API doc set by next release.
 
 Appreciate your feedback.
 
 Regards
 -Radhika
 
 
 
 -Original Message-
 From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
 Sent: Wednesday, October 16, 2013 7:36 AM
 To: dev@cloudstack.apache.org
 Subject: RE: Incomplete API docs?
 
 Demetrius do you mind creating an issue in JIRA?
 
  -Original Message-
  From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
  Sent: Tuesday, October 15, 2013 5:15 PM
  To: dev@cloudstack.apache.org
  Subject: Re: Incomplete API docs?
 
  The commands.xml generated as a result of mvn build (mvn clean 
  install
  - P developer,systemvm -DskipTests), doesn't include the commands 
  mentioned by Demetrius. Looks like some regression bug in 
  ApiXmlDocWriter - it used to include all the commands in 3.0.x 
  version of the code.
 
  -Alena.
 
  From: Demetrius Tsitrelis
  dtsitre...@live.commailto:dtsitre...@live.com
  Reply-To:
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Date: Tuesday, October 15, 2013 4:33 PM
  To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
  Subject: Incomplete API docs?
 
 
 
  I grep'ed the source code and came up with a list of the APIs which 
  the UI uses.  That list is at the end of this message.
  You can see that many of them (addNetscalerLoadBalancer, 
  addVmwareDc,
  etc.) are not in the generated API documentation which appears at 
  http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.htm
  l
 
 
  Is this something wrong with the input files or is a tool at fault?
 
 
  Here's the list of APIs used by the UI:
 
  activateProject
 
  addAccountToProject
 
  addBaremetalDhcp
 
  addBaremetalPxeKickStartServer
 
  addCluster
 
  addHost
 
  addImageStore
 
  addIpToNic
 
  addLdapConfiguration
 
  addNetscalerLoadBalancer
 
  addNetworkServiceProvider
 
  addNicToVirtualMachine
 
  addRegion
 
  addTrafficType
 
  addUcsManager
 
  addVmwareDc
 
  addVpnUser
 
  archiveAlerts
 
  archiveEvents
 
  assignToGlobalLoadBalancerRule
 
  assignToLoadBalancerRule
 
  assignVirtualMachine
 
  associateIpAddress
 
  associateUcsProfileToBlade
 
  attachIso
 
  attachVolume
 
  authorizeSecurityGroupEgress
 
  authorizeSecurityGroupIngress
 
  cancelHostMaintenance
 
  cancelStorageMaintenance
 
  configureInternalLoadBalancerElement
 
  configureVirtualRouterElement
 
  copyIso
 
  copyTemplate
 
  createAccount
 
  createAffinityGroup
 
  createAutoScalePolicy
 
  createAutoScaleVmGroup
 
  createAutoScaleVmProfile
 
  createCondition
 
  createDiskOffering
 
  createDomain
 
  createEgressFirewallRule
 
  createFirewallRule
 
  createGlobalLoadBalancerRule
 
  createIpForwardingRule
 
  createLBHealthCheckPolicy
 
  createLBStickinessPolicy
 
  createLoadBalancer
 
  createLoadBalancerRule
 
  createNetwork
 
  createNetworkACL
 
  createNetworkACLList
 
  createNetworkOffering
 
  createPhysicalNetwork
 
  createPod
 
  createPortableIpRange
 
  createPortForwardingRule
 
  createPrivateGateway
 
  createProject
 
  createRemoteAccessVpn
 
  createSecondaryStagingStore
 
  createSecurityGroup
 
  createServiceOffering
 
  createSnapshot
 
  createSnapshotPolicy
 
  createStaticRoute
 
  createStorageNetworkIpRange
 
  createStoragePool
 
  createTags
 
  createTemplate
 
  createUser
 
  createVlanIpRange
 
  createVMSnapshot
 
  createVolume
 
  createVPC
 
  createVpnConnection
 
  createVpnCustomerGateway
 
  createVpnGateway
 
  createZone
 
  dedicateCluster
 
  dedicateGuestVlanRange
 
  dedicateHost
 
  dedicatePod
 
  dedicatePublicIpRange
 
  dedicateZone
 
  deleteAccount
 
  deleteAccountFromProject

RE: Incomplete API docs?

[Radhika Puthiyetath]

Hi All,

Our API documentation requires a serious refurbishment.

How about creating a doc sprint for enhancing API documentation ?

I am in the process of setting up a Wiki page at 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Documentation+Sprint+for+Enhancing+API+Documentation
 to track this activity. Feel free to add/ edit/ remove the page content.

I request all of you to volunteer so that we will have a comprehensive API doc 
set by next release.

Appreciate your feedback.

Regards
-Radhika



-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com] 
Sent: Wednesday, October 16, 2013 7:36 AM
To: dev@cloudstack.apache.org
Subject: RE: Incomplete API docs?

Demetrius do you mind creating an issue in JIRA?

 -Original Message-
 From: Alena Prokharchyk [mailto:alena.prokharc...@citrix.com]
 Sent: Tuesday, October 15, 2013 5:15 PM
 To: dev@cloudstack.apache.org
 Subject: Re: Incomplete API docs?
 
 The commands.xml generated as a result of mvn build (mvn clean install 
 - P developer,systemvm -DskipTests), doesn't include the commands 
 mentioned by Demetrius. Looks like some regression bug in 
 ApiXmlDocWriter - it used to include all the commands in 3.0.x version 
 of the code.
 
 -Alena.
 
 From: Demetrius Tsitrelis
 dtsitre...@live.commailto:dtsitre...@live.com
 Reply-To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
 Date: Tuesday, October 15, 2013 4:33 PM
 To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
 dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
 Subject: Incomplete API docs?
 
 
 
 I grep'ed the source code and came up with a list of the APIs which 
 the UI uses.  That list is at the end of this message.
 You can see that many of them (addNetscalerLoadBalancer, addVmwareDc,
 etc.) are not in the generated API documentation which appears at 
 http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html
 
 
 Is this something wrong with the input files or is a tool at fault?
 
 
 Here's the list of APIs used by the UI:
 
 activateProject
 
 addAccountToProject
 
 addBaremetalDhcp
 
 addBaremetalPxeKickStartServer
 
 addCluster
 
 addHost
 
 addImageStore
 
 addIpToNic
 
 addLdapConfiguration
 
 addNetscalerLoadBalancer
 
 addNetworkServiceProvider
 
 addNicToVirtualMachine
 
 addRegion
 
 addTrafficType
 
 addUcsManager
 
 addVmwareDc
 
 addVpnUser
 
 archiveAlerts
 
 archiveEvents
 
 assignToGlobalLoadBalancerRule
 
 assignToLoadBalancerRule
 
 assignVirtualMachine
 
 associateIpAddress
 
 associateUcsProfileToBlade
 
 attachIso
 
 attachVolume
 
 authorizeSecurityGroupEgress
 
 authorizeSecurityGroupIngress
 
 cancelHostMaintenance
 
 cancelStorageMaintenance
 
 configureInternalLoadBalancerElement
 
 configureVirtualRouterElement
 
 copyIso
 
 copyTemplate
 
 createAccount
 
 createAffinityGroup
 
 createAutoScalePolicy
 
 createAutoScaleVmGroup
 
 createAutoScaleVmProfile
 
 createCondition
 
 createDiskOffering
 
 createDomain
 
 createEgressFirewallRule
 
 createFirewallRule
 
 createGlobalLoadBalancerRule
 
 createIpForwardingRule
 
 createLBHealthCheckPolicy
 
 createLBStickinessPolicy
 
 createLoadBalancer
 
 createLoadBalancerRule
 
 createNetwork
 
 createNetworkACL
 
 createNetworkACLList
 
 createNetworkOffering
 
 createPhysicalNetwork
 
 createPod
 
 createPortableIpRange
 
 createPortForwardingRule
 
 createPrivateGateway
 
 createProject
 
 createRemoteAccessVpn
 
 createSecondaryStagingStore
 
 createSecurityGroup
 
 createServiceOffering
 
 createSnapshot
 
 createSnapshotPolicy
 
 createStaticRoute
 
 createStorageNetworkIpRange
 
 createStoragePool
 
 createTags
 
 createTemplate
 
 createUser
 
 createVlanIpRange
 
 createVMSnapshot
 
 createVolume
 
 createVPC
 
 createVpnConnection
 
 createVpnCustomerGateway
 
 createVpnGateway
 
 createZone
 
 dedicateCluster
 
 dedicateGuestVlanRange
 
 dedicateHost
 
 dedicatePod
 
 dedicatePublicIpRange
 
 dedicateZone
 
 deleteAccount
 
 deleteAccountFromProject
 
 deleteAffinityGroup
 
 deleteAlerts
 
 deleteBigSwitchVnsDevice
 
 deleteCiscoNexusVSM
 
 deleteCluster
 
 deleteCondition
 
 deleteDiskOffering
 
 deleteDomain
 
 deleteEgressFirewallRule
 
 deleteEvents
 
 deleteF5LoadBalancer
 
 deleteFirewallRule
 
 deleteGlobalLoadBalancerRule
 
 deleteHost
 
 deleteImageStore
 
 deleteIpForwardingRule
 
 deleteIso
 
 deleteLBHealthCheckPolicy
 
 deleteLBStickinessPolicy
 
 deleteLdapConfiguration
 
 deleteLoadBalancer
 
 deleteLoadBalancerRule
 
 deleteNetscalerLoadBalancer
 
 deleteNetwork
 
 deleteNetworkACL
 
 deleteNetworkACLList
 
 deleteNetworkOffering
 
 deleteNetworkServiceProvider
 
 deleteNiciraNvpDevice
 
 deletePhysicalNetwork
 
 deletePod
 
 deletePortableIpRange
 
 deletePortForwardingRule
 
 deletePrivateGateway
 
 deleteProject
 
 deleteProjectInvitation
 
 deleteRemoteAccessVpn
 
 deleteSecondaryStagingStore
 
 deleteSecurityGroup
 
 deleteServiceOffering

Incomplete API docs?

[Demetrius Tsitrelis]

I grep’ed the source code and came up with a list of the
APIs which the UI uses.  That list is at the end of this message. 
You can see that many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are
not in the generated API documentation which appears at 
http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html

 

Is this something wrong with the input files or is a tool at
fault?

 

Here’s the list of APIs used by the UI:

activateProject

addAccountToProject

addBaremetalDhcp

addBaremetalPxeKickStartServer

addCluster

addHost

addImageStore

addIpToNic

addLdapConfiguration

addNetscalerLoadBalancer

addNetworkServiceProvider

addNicToVirtualMachine

addRegion

addTrafficType

addUcsManager

addVmwareDc

addVpnUser

archiveAlerts

archiveEvents

assignToGlobalLoadBalancerRule

assignToLoadBalancerRule

assignVirtualMachine

associateIpAddress

associateUcsProfileToBlade 

attachIso

attachVolume

authorizeSecurityGroupEgress

authorizeSecurityGroupIngress

cancelHostMaintenance

cancelStorageMaintenance

configureInternalLoadBalancerElement

configureVirtualRouterElement

copyIso

copyTemplate

createAccount

createAffinityGroup

createAutoScalePolicy

createAutoScaleVmGroup

createAutoScaleVmProfile

createCondition

createDiskOffering

createDomain

createEgressFirewallRule

createFirewallRule

createGlobalLoadBalancerRule

createIpForwardingRule

createLBHealthCheckPolicy

createLBStickinessPolicy

createLoadBalancer

createLoadBalancerRule

createNetwork

createNetworkACL

createNetworkACLList

createNetworkOffering

createPhysicalNetwork

createPod

createPortableIpRange

createPortForwardingRule

createPrivateGateway

createProject

createRemoteAccessVpn

createSecondaryStagingStore

createSecurityGroup

createServiceOffering

createSnapshot

createSnapshotPolicy

createStaticRoute

createStorageNetworkIpRange

createStoragePool

createTags

createTemplate

createUser

createVlanIpRange

createVMSnapshot

createVolume

createVPC

createVpnConnection

createVpnCustomerGateway

createVpnGateway

createZone

dedicateCluster

dedicateGuestVlanRange

dedicateHost

dedicatePod

dedicatePublicIpRange

dedicateZone

deleteAccount

deleteAccountFromProject

deleteAffinityGroup

deleteAlerts

deleteBigSwitchVnsDevice

deleteCiscoNexusVSM

deleteCluster

deleteCondition

deleteDiskOffering

deleteDomain

deleteEgressFirewallRule

deleteEvents

deleteF5LoadBalancer

deleteFirewallRule

deleteGlobalLoadBalancerRule

deleteHost

deleteImageStore

deleteIpForwardingRule

deleteIso

deleteLBHealthCheckPolicy

deleteLBStickinessPolicy

deleteLdapConfiguration

deleteLoadBalancer

deleteLoadBalancerRule

deleteNetscalerLoadBalancer

deleteNetwork

deleteNetworkACL

deleteNetworkACLList

deleteNetworkOffering

deleteNetworkServiceProvider

deleteNiciraNvpDevice

deletePhysicalNetwork

deletePod

deletePortableIpRange

deletePortForwardingRule

deletePrivateGateway

deleteProject

deleteProjectInvitation

deleteRemoteAccessVpn

deleteSecondaryStagingStore

deleteSecurityGroup

deleteServiceOffering

deleteSnapshot

deleteSnapshotPolicies

deleteSrxFirewall

deleteStaticRoute

deleteStorageNetworkIpRange

deleteStoragePool

deleteTags

deleteTemplate

deleteUcsManager

deleteUser

deleteVlanIpRange

deleteVMSnapshot

deleteVolume

deleteVPC

deleteVpnConnection

deleteVpnCustomerGateway

deleteVpnGateway

deleteZone

deployVirtualMachine

destroyRouter

destroySystemVm

destroyVirtualMachine

detachIso

detachVolume

disableAccount

disableAutoScaleVmGroup

disableCiscoNexusVSM

disableStaticNat

disableUser

disassociateIpAddress

disassociateUcsProfileFromBlade

enableAccount

enableAutoScaleVmGroup

enableCiscoNexusVSM

enableStaticNat

enableStorageMaintenance

enableUser

extractVolume

findHostsForMigration

findStoragePoolsForMigration

ldapCreateAccount

listAccounts

listAffinityGroups

listAffinityGroupTypes

listAlerts

listAutoScaleVmGroups

listAutoScaleVmProfiles

listBaremetalDhcp

listBaremetalPxeServers

listBigSwitchVnsDevices

listCapabilities

listCapacity

listCiscoNexusVSMs

listClusters

listConfigurations

listCounters

listDedicatedClusters

listDedicatedGuestVlanRanges

listDedicatedHosts

listDedicatedPods

listDedicatedZones

listDeploymentPlanners

listDiskOfferings

listDomainChildren

listDomains

listEgressFirewallRules

listEvents

listF5LoadBalancers

listFirewallRules

listGlobalLoadBalancerRules

listHosts

listHypervisorCapabilities

listHypervisors

listImageStores

listInternalLoadBalancerElements

listInternalLoadBalancerVMs

listIpForwardingRules

listIsos

listLBHealthCheckPolicies

listLBStickinessPolicies

listLdapConfigurations

listLdapUsers

listLoadBalancerRuleInstances

listLoadBalancerRules

listLoadBalancers

listNetscalerLoadBalancers

listNetworkACLLists

listNetworkACLs

listNetworkOfferings

listNetworks

listNetworkServiceProviders

listNiciraNvpDevices

listNics

listOsCategories

listOsTypes

listPhysicalNetworks

listPods

Re: Incomplete API docs?

[Alena Prokharchyk]

The commands.xml generated as a result of mvn build (mvn clean install -P 
developer,systemvm –DskipTests), doesn't include the commands  mentioned by 
Demetrius. Looks like some regression bug in ApiXmlDocWriter – it used to 
include all the commands in 3.0.x version of the code.

-Alena.

From: Demetrius Tsitrelis dtsitre...@live.commailto:dtsitre...@live.com
Reply-To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org 
dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
Date: Tuesday, October 15, 2013 4:33 PM
To: dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org 
dev@cloudstack.apache.orgmailto:dev@cloudstack.apache.org
Subject: Incomplete API docs?



I grep’ed the source code and came up with a list of the
APIs which the UI uses.  That list is at the end of this message.
You can see that many of them (addNetscalerLoadBalancer, addVmwareDc, etc.) are
not in the generated API documentation which appears at 
http://cloudstack.apache.org/docs/api/apidocs-4.2/TOC_Root_Admin.html


Is this something wrong with the input files or is a tool at
fault?


Here’s the list of APIs used by the UI:

activateProject

addAccountToProject

addBaremetalDhcp

addBaremetalPxeKickStartServer

addCluster

addHost

addImageStore

addIpToNic

addLdapConfiguration

addNetscalerLoadBalancer

addNetworkServiceProvider

addNicToVirtualMachine

addRegion

addTrafficType

addUcsManager

addVmwareDc

addVpnUser

archiveAlerts

archiveEvents

assignToGlobalLoadBalancerRule

assignToLoadBalancerRule

assignVirtualMachine

associateIpAddress

associateUcsProfileToBlade

attachIso

attachVolume

authorizeSecurityGroupEgress

authorizeSecurityGroupIngress

cancelHostMaintenance

cancelStorageMaintenance

configureInternalLoadBalancerElement

configureVirtualRouterElement

copyIso

copyTemplate

createAccount

createAffinityGroup

createAutoScalePolicy

createAutoScaleVmGroup

createAutoScaleVmProfile

createCondition

createDiskOffering

createDomain

createEgressFirewallRule

createFirewallRule

createGlobalLoadBalancerRule

createIpForwardingRule

createLBHealthCheckPolicy

createLBStickinessPolicy

createLoadBalancer

createLoadBalancerRule

createNetwork

createNetworkACL

createNetworkACLList

createNetworkOffering

createPhysicalNetwork

createPod

createPortableIpRange

createPortForwardingRule

createPrivateGateway

createProject

createRemoteAccessVpn

createSecondaryStagingStore

createSecurityGroup

createServiceOffering

createSnapshot

createSnapshotPolicy

createStaticRoute

createStorageNetworkIpRange

createStoragePool

createTags

createTemplate

createUser

createVlanIpRange

createVMSnapshot

createVolume

createVPC

createVpnConnection

createVpnCustomerGateway

createVpnGateway

createZone

dedicateCluster

dedicateGuestVlanRange

dedicateHost

dedicatePod

dedicatePublicIpRange

dedicateZone

deleteAccount

deleteAccountFromProject

deleteAffinityGroup

deleteAlerts

deleteBigSwitchVnsDevice

deleteCiscoNexusVSM

deleteCluster

deleteCondition

deleteDiskOffering

deleteDomain

deleteEgressFirewallRule

deleteEvents

deleteF5LoadBalancer

deleteFirewallRule

deleteGlobalLoadBalancerRule

deleteHost

deleteImageStore

deleteIpForwardingRule

deleteIso

deleteLBHealthCheckPolicy

deleteLBStickinessPolicy

deleteLdapConfiguration

deleteLoadBalancer

deleteLoadBalancerRule

deleteNetscalerLoadBalancer

deleteNetwork

deleteNetworkACL

deleteNetworkACLList

deleteNetworkOffering

deleteNetworkServiceProvider

deleteNiciraNvpDevice

deletePhysicalNetwork

deletePod

deletePortableIpRange

deletePortForwardingRule

deletePrivateGateway

deleteProject

deleteProjectInvitation

deleteRemoteAccessVpn

deleteSecondaryStagingStore

deleteSecurityGroup

deleteServiceOffering

deleteSnapshot

deleteSnapshotPolicies

deleteSrxFirewall

deleteStaticRoute

deleteStorageNetworkIpRange

deleteStoragePool

deleteTags

deleteTemplate

deleteUcsManager

deleteUser

deleteVlanIpRange

deleteVMSnapshot

deleteVolume

deleteVPC

deleteVpnConnection

deleteVpnCustomerGateway

deleteVpnGateway

deleteZone

deployVirtualMachine

destroyRouter

destroySystemVm

destroyVirtualMachine

detachIso

detachVolume

disableAccount

disableAutoScaleVmGroup

disableCiscoNexusVSM

disableStaticNat

disableUser

disassociateIpAddress

disassociateUcsProfileFromBlade

enableAccount

enableAutoScaleVmGroup

enableCiscoNexusVSM

enableStaticNat

enableStorageMaintenance

enableUser

extractVolume

findHostsForMigration

findStoragePoolsForMigration

ldapCreateAccount

listAccounts

listAffinityGroups

listAffinityGroupTypes

listAlerts

listAutoScaleVmGroups

listAutoScaleVmProfiles

listBaremetalDhcp

listBaremetalPxeServers

listBigSwitchVnsDevices

listCapabilities

listCapacity

listCiscoNexusVSMs

listClusters

listConfigurations

listCounters

listDedicatedClusters

listDedicatedGuestVlanRanges

listDedicatedHosts

listDedicatedPods

listDedicatedZones

listDeploymentPlanners

listDiskOfferings

listDomainChildren

listDomains

Master api-docs build

[Chiradeep Vittal]

Raising this again. Jenkins seems to not be cleaning up properly. The
dedicatePublicIpRange patch was reverted a few days ago and the build
should be successful.

On 4/11/13 3:05 PM, Apache Jenkins Server jenk...@builds.apache.org
wrote:

See https://builds.apache.org/job/cloudstack-apidocs-master/451/changes

Changes:

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - implement
create GSLB action.

[kelveny] Fix the systemvm packaging issue

[brian.federle] List view: Fix broken add row action

[brian.federle] VM NICs list view: Fix 'VM name' field for VMs without
name

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - create
GSLB - (1) pass gslbstickysessionmethodname parameter to
createGlobalLoadBalancerRule API. (2) Take async Job response.

[prachi] API changes for createAffinityGroup

[prachi] More API changes

[prachi] DeleteAffinityGroup API changes

[prachi] ListAffinityGroups API changes

[prachi] Changes to add AffinityGroupprocessor, deployVM changes

[prachi] Separated out host anti-affinity as a plugin.

[prachi] Added apache license header

[prachi] Schema changes to create affinity group tables

[prachi] DAO constructor should be lightweight to make Spring DI faster.

[prachi] Not using entity factory

[prachi] API to list planners and set the planner in Service offering

[prachi] API changes to expose the commands

[prachi] Changes to make affinity group types configurable.

[prachi] Fixes after functional tests

[prachi] Adding the missing header!

[prachi] Build failure fixes after rebase.

[prachi] Adding a unit test for the new affinity groups API

[prachi] Integration testcase and the config file needed,  that runs with
marvin.

[prachi] Correcting the rebase merge issues.

[prachi] Added cleanup of affinitygroups when a VM is expunging and when
the account is deleted.

[prachi] Changes to return affinity groups information during listVMsCmd

[prachi] Added AffinityGroup View in order to include VM details while
listing AffinityGroups.

[prachi] Fixes to de-couple the AffinityGroupResponse from
UserVmResponse, since ApiDiscoveryService breaks, if we nest two response
objects into each other.

[prachi] More log statements to debug

[prachi] affinity group tests moved into the test folder

[prachi] bvt: marvin test for the affinity groups feature

[prachi] marvin bvt: getting rid of unused keys in the test

[prachi] CLOUDSTACK-1968: affinity_groups: Column 'deployment planner'
cannot be null when creating a service offering

[prachi] affinitygroup bvt: changes to the bvt for affinity groups

[prachi] ACl on affinity group

[prachi] Adding pretty toString() to AffinityGroup

[prachi] Fixes for issues found while testing after the merge

[prachi] Fixes to unit-test dues to changes in master

[prachi] Fixing rat. Merge with master missed the header change

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - set
autocomplete off.

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - make
loginCmdText local.

[prachi]  Excluding this unit test for a while, since it fails because
ComponentContext.initComponentsLifeCycle(); is failing when DB is
unavailable

--
[...truncated 3749 lines...]

---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.12:test (default-test) @
cloud-client-ui ---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.3:war (default-war) @ cloud-client-ui ---
[INFO] Packaging webapp
[INFO] Assembling webapp [cloud-client-ui] in
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/cloud-client-ui-4.2.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/generated-webapp]
[INFO] Webapp assembled in [522 msecs]
[INFO] Building war:
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
cloud-client-ui-4.2.0-SNAPSHOT.war
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
cloud-client-ui ---
[INFO] Configured Artifact: org.jasypt:jasypt:1.9.0:jar
[INFO] [INFO] Configured Artifact: org.jasypt:jasypt:1.8:jar
[INFO] Copying jasypt-1.9.0.jar to
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
pythonlibs/jasypt-1.9.0.jar
[INFO] Copying jasypt-1.8.jar to
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
pythonlibs/jasypt-1.8.jar

[INFO] --- maven-dependency-plugin:2.5.1:copy (copy) @ cloud-client-ui ---
[INFO] [INFO] Installing
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
cloud-client-ui-4.2.0-SNAPSHOT.war to
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/cloudstack/clo
ud-client-ui/4.2.0-SNAPSHOT/cloud-client-ui-4.2.0-SNAPSHOT.war

[INFO] --- 

Re: Master api-docs build

[Prasanna Santhanam]

452 has actually passed the build.

--
Prasanna.,

- Original Message -
From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
Sent: Friday, April 12, 2013 09:41 AM
To: dev@cloudstack.apache.org dev@cloudstack.apache.org
Subject: Master api-docs build

Raising this again. Jenkins seems to not be cleaning up properly. The
dedicatePublicIpRange patch was reverted a few days ago and the build
should be successful.

On 4/11/13 3:05 PM, Apache Jenkins Server jenk...@builds.apache.org
wrote:

See https://builds.apache.org/job/cloudstack-apidocs-master/451/changes

Changes:

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - implement
create GSLB action.

[kelveny] Fix the systemvm packaging issue

[brian.federle] List view: Fix broken add row action

[brian.federle] VM NICs list view: Fix 'VM name' field for VMs without
name

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - create
GSLB - (1) pass gslbstickysessionmethodname parameter to
createGlobalLoadBalancerRule API. (2) Take async Job response.

[prachi] API changes for createAffinityGroup

[prachi] More API changes

[prachi] DeleteAffinityGroup API changes

[prachi] ListAffinityGroups API changes

[prachi] Changes to add AffinityGroupprocessor, deployVM changes

[prachi] Separated out host anti-affinity as a plugin.

[prachi] Added apache license header

[prachi] Schema changes to create affinity group tables

[prachi] DAO constructor should be lightweight to make Spring DI faster.

[prachi] Not using entity factory

[prachi] API to list planners and set the planner in Service offering

[prachi] API changes to expose the commands

[prachi] Changes to make affinity group types configurable.

[prachi] Fixes after functional tests

[prachi] Adding the missing header!

[prachi] Build failure fixes after rebase.

[prachi] Adding a unit test for the new affinity groups API

[prachi] Integration testcase and the config file needed,  that runs with
marvin.

[prachi] Correcting the rebase merge issues.

[prachi] Added cleanup of affinitygroups when a VM is expunging and when
the account is deleted.

[prachi] Changes to return affinity groups information during listVMsCmd

[prachi] Added AffinityGroup View in order to include VM details while
listing AffinityGroups.

[prachi] Fixes to de-couple the AffinityGroupResponse from
UserVmResponse, since ApiDiscoveryService breaks, if we nest two response
objects into each other.

[prachi] More log statements to debug

[prachi] affinity group tests moved into the test folder

[prachi] bvt: marvin test for the affinity groups feature

[prachi] marvin bvt: getting rid of unused keys in the test

[prachi] CLOUDSTACK-1968: affinity_groups: Column 'deployment planner'
cannot be null when creating a service offering

[prachi] affinitygroup bvt: changes to the bvt for affinity groups

[prachi] ACl on affinity group

[prachi] Adding pretty toString() to AffinityGroup

[prachi] Fixes for issues found while testing after the merge

[prachi] Fixes to unit-test dues to changes in master

[prachi] Fixing rat. Merge with master missed the header change

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - set
autocomplete off.

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - make
loginCmdText local.

[prachi]  Excluding this unit test for a while, since it fails because
ComponentContext.initComponentsLifeCycle(); is failing when DB is
unavailable

--
[...truncated 3749 lines...]

---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.12:test (default-test) @
cloud-client-ui ---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.3:war (default-war) @ cloud-client-ui ---
[INFO] Packaging webapp
[INFO] Assembling webapp [cloud-client-ui] in
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/cloud-client-ui-4.2.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/generated-webapp]
[INFO] Webapp assembled in [522 msecs]
[INFO] Building war:
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
cloud-client-ui-4.2.0-SNAPSHOT.war
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
cloud-client-ui ---
[INFO] Configured Artifact: org.jasypt:jasypt:1.9.0:jar
[INFO] [INFO] Configured Artifact: org.jasypt:jasypt:1.8:jar
[INFO] Copying jasypt-1.9.0.jar to
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
pythonlibs/jasypt-1.9.0.jar
[INFO] Copying jasypt-1.8.jar to
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
pythonlibs/jasypt-1.8.jar

[INFO] --- maven-dependency-plugin:2.5.1:copy (copy) @ cloud-client-ui ---
[INFO] [INFO] Installing
https

Re: Master api-docs build

[prasanna]

Oddly 453 failed again. They build on different nodes ubuntu4 and
ubuntu3 and ubuntu4 seems to fail the build.

On 12 April 2013 07:14, Prasanna Santhanam
prasanna.santha...@citrix.com wrote:
 452 has actually passed the build.

 --
 Prasanna.,

 - Original Message -
 From: Chiradeep Vittal [mailto:chiradeep.vit...@citrix.com]
 Sent: Friday, April 12, 2013 09:41 AM
 To: dev@cloudstack.apache.org dev@cloudstack.apache.org
 Subject: Master api-docs build

 Raising this again. Jenkins seems to not be cleaning up properly. The
 dedicatePublicIpRange patch was reverted a few days ago and the build
 should be successful.

 On 4/11/13 3:05 PM, Apache Jenkins Server jenk...@builds.apache.org
 wrote:

See https://builds.apache.org/job/cloudstack-apidocs-master/451/changes

Changes:

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - implement
create GSLB action.

[kelveny] Fix the systemvm packaging issue

[brian.federle] List view: Fix broken add row action

[brian.federle] VM NICs list view: Fix 'VM name' field for VMs without
name

[jessica.wang] CLOUDSTACK-1910: cloudstack UI - Regions menu - create
GSLB - (1) pass gslbstickysessionmethodname parameter to
createGlobalLoadBalancerRule API. (2) Take async Job response.

[prachi] API changes for createAffinityGroup

[prachi] More API changes

[prachi] DeleteAffinityGroup API changes

[prachi] ListAffinityGroups API changes

[prachi] Changes to add AffinityGroupprocessor, deployVM changes

[prachi] Separated out host anti-affinity as a plugin.

[prachi] Added apache license header

[prachi] Schema changes to create affinity group tables

[prachi] DAO constructor should be lightweight to make Spring DI faster.

[prachi] Not using entity factory

[prachi] API to list planners and set the planner in Service offering

[prachi] API changes to expose the commands

[prachi] Changes to make affinity group types configurable.

[prachi] Fixes after functional tests

[prachi] Adding the missing header!

[prachi] Build failure fixes after rebase.

[prachi] Adding a unit test for the new affinity groups API

[prachi] Integration testcase and the config file needed,  that runs with
marvin.

[prachi] Correcting the rebase merge issues.

[prachi] Added cleanup of affinitygroups when a VM is expunging and when
the account is deleted.

[prachi] Changes to return affinity groups information during listVMsCmd

[prachi] Added AffinityGroup View in order to include VM details while
listing AffinityGroups.

[prachi] Fixes to de-couple the AffinityGroupResponse from
UserVmResponse, since ApiDiscoveryService breaks, if we nest two response
objects into each other.

[prachi] More log statements to debug

[prachi] affinity group tests moved into the test folder

[prachi] bvt: marvin test for the affinity groups feature

[prachi] marvin bvt: getting rid of unused keys in the test

[prachi] CLOUDSTACK-1968: affinity_groups: Column 'deployment planner'
cannot be null when creating a service offering

[prachi] affinitygroup bvt: changes to the bvt for affinity groups

[prachi] ACl on affinity group

[prachi] Adding pretty toString() to AffinityGroup

[prachi] Fixes for issues found while testing after the merge

[prachi] Fixes to unit-test dues to changes in master

[prachi] Fixing rat. Merge with master missed the header change

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - set
autocomplete off.

[jessica.wang] CLOUDSTACK-1065: cloudstack UI - AWS Style Regions - make
loginCmdText local.

[prachi]  Excluding this unit test for a while, since it fails because
ComponentContext.initComponentsLifeCycle(); is failing when DB is
unavailable

--
[...truncated 3749 lines...]

---
 T E S T S
---

[INFO] --- maven-surefire-plugin:2.12:test (default-test) @
cloud-client-ui ---

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[JENKINS] Recording test results
[INFO]
[INFO] --- maven-war-plugin:2.3:war (default-war) @ cloud-client-ui ---
[INFO] Packaging webapp
[INFO] Assembling webapp [cloud-client-ui] in
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/cloud-client-ui-4.2.0-SNAPSHOT]
[INFO] Processing war project
[INFO] Copying webapp resources
[https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target
/generated-webapp]
[INFO] Webapp assembled in [522 msecs]
[INFO] Building war:
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
cloud-client-ui-4.2.0-SNAPSHOT.war
[INFO]
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @
cloud-client-ui ---
[INFO] Configured Artifact: org.jasypt:jasypt:1.9.0:jar
[INFO] [INFO] Configured Artifact: org.jasypt:jasypt:1.8:jar
[INFO] Copying jasypt-1.9.0.jar to
https://builds.apache.org/job/cloudstack-apidocs-master/ws/client/target/
pythonlibs/jasypt-1.9.0.jar
[INFO] Copying jasypt-1.8.jar