KVM storage adaptors (the agent-side code for a storage plugin) should be detected at runtime, rather than relying on source code modifications to add new adaptors.
A new annotation "StorageAdaptorInfo" will allow the storage developer to identify a new StorageAdaptor implementation. Then the jar can just be placed in the classpath and
we can find it via reflection. The StorageAdaptorInfo annotation can house the properties required for the adaptor:
@StorageAdaptorInfo( storagePoolType=StoragePoolType.XYZ )
public class MyStorageAdaptor implements StorageAdaptor {
}
public class
discussion of alternatives amongst design ideas, their resources/time tradeoffs and limitations. Explain why a certain design idea is chosen over others
list changes to existing web services APIs and new APIs introduced with signatures and throughout documentation
Are there any entities being created that require usage reporting for billing purposes?
Does this change any existing entities for which usage is being tracked already?
Appendix A:
Appendix B: