Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
| public:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere [2026/09/12 17:42] – ↷ Page moved from private:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere to public:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere nick_dido | public:99_annexes:annex-b-terms-and-definitions:v:vmware_vsphere [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== VMware vSphere ====== | ====== VMware vSphere ====== | ||
| - | [[private: | + | [[public: |
| ===== Discussion ===== | ===== Discussion ===== | ||
| Line 9: | Line 9: | ||
| VMware vSphere includes a virtualization layer provided by ESX or ESXi and centralized management capabilities provided by vCenter. | VMware vSphere includes a virtualization layer provided by ESX or ESXi and centralized management capabilities provided by vCenter. | ||
| - | Within Crucible, VMware vSphere can serve as a [[private: | + | Within Crucible, VMware vSphere can serve as a [[public: |
| VMware vSphere provides platform-specific interfaces, resource models, configuration formats, image formats, and operational mechanisms. A Crucible Provider Implementation can isolate those platform-specific dependencies from provider-independent Crucible Descriptions and Infrastructure Baselines. | VMware vSphere provides platform-specific interfaces, resource models, configuration formats, image formats, and operational mechanisms. A Crucible Provider Implementation can isolate those platform-specific dependencies from provider-independent Crucible Descriptions and Infrastructure Baselines. | ||