This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.
The following shows the packages and their purpose. If you're adding code to CloudStack, please read this over to decide where the code should be placed.
Utility methods that can be used in any project
REST API, Agent API, and Java API definitions
Remember that each ServerResource should be deployable in both a management server and in a remote agent container.
Core is also being converted to be one project per ServerResource, as how OVM is done today.
ServerResource for Oracle VM
The future of ServerResource packaging
Simulated ServerResource for scale and regression test
ServerResource for VMware
CloudStack build dependencies reflect the design principal of CloudStack and, therefore, should not be changed. The packages core, ovm, agent-simulator, and vmware-base are all ServerResource implementations and are only based off of the cloud-api package. By doing this, these packages are designed to not access the database. The package cloud-agent is based off of cloud-api because the serialization and deserialization code are in that package; however, ideally, cloud-agent is only a container and should be based off of cloud-util.
CloudStack will move toward the following package and build dependencies.
In this architecture, the CloudStack API package is further refined into three packages. Each defines a separate area of integration.
OAM&P and End User API
API for adding capabilities to CloudStack
API for communicating with ServerResource