Functionality Levels
This section outlines the methods required for each supported functionality level of the Custom Provider Framework (CPF). The framework is designed to be implemented incrementally, allowing you to start with a minimal set of capabilities and expand functionality over time as needed.
Not all methods need to be implemented from the outset. At a minimum, only the methods required for the selected functionality level must be supported. Additional methods can be introduced later to enable more advanced features such as template-based deployments, linked clones, or template versioning.
This approach provides flexibility for different use cases:
Basic implementations can focus on simple VM enumeration and control.
Intermediate levels introduce task tracking and template-based provisioning.
Advanced implementations add snapshot management and version control capabilities.
By following this model, developers can deliver a working integration quickly and progressively enhance it without needing to redesign the provider architecture.
Basic: No templates, only good for creating standalone host pools.
Full clones: Basic support for template host pools by creating copies of the template VM.
Link clones: Can create link clones from a single snapshot of the template VM.
Template versions: Can create full or link clones from different snapshots and can revert the template VM to a specific snapshot (when entering maintenance mode).
Basic
✅
✅
✅
✅
Tasks
❌
✅
✅
✅
Template
❌
✅
✅
✅
Snapshots
❌
❌
✅
✅
Last updated