The current CloudStack packaging has only cloud-utils, cloud-api, cloud-core, cloud-server, cloud-agent, cloud-ovm, cloud-vmware, and a few others. Now we are expecting more developers to join the ranks of committers, I'm proposing the following structure to further refine the modules and to enforce code separation so it can be easily tested.
Module |
Description |
---|---|
cloud-utils |
common utilities |
cloud-service-api |
api for orchestration services |
cloud-framework |
frameworks for the server |
cloud-plugin-api |
plugin apis needed by the orchestration engine |
cloud-resource-api |
api for resource |
cloud-api-server |
api server portion |
cloud-orchestration |
orchestration engine |
cloud-plugin-ovs |
ovs implementation |
cloud-plugin-srx |
srx implementation |
cloud-plugin-netscaler |
netscaler implementation |
cloud-plugin-f5 |
f5 implmenetation |
cloud-plugin-dp-user-concentrating |
user concentrating deployment planner |
cloud-plugin-dp-user-dispersing |
user dispersing deployment planner |
cloud-plugin-baremetal |
baremetal implementation |
cloud-plugin-xenserver |
xenserver implementation |
cloud-plugin-vmware |
vmware implementation |
cloud-plugin--kvm |
kvm implementation |
cloud-plugin--ovm |
ovm implementation |
cloud-plugin-simulator |
simulator |
|
|
|
|