Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_provider [2026/09/12 17:42] – removed - external edit (Unknown date) 127.0.0.1 | public:99_annexes:annex-b-terms-and-definitions:i:infrastructure_provider [2026/09/12 17:43] (current) – ↷ Links adapted because of a move operation nick_dido | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== Infrastructure Provider ====== | ||
| + | [[public: | ||
| + | |||
| + | ===== Discussion ===== | ||
| + | |||
| + | An Infrastructure Provider is a [[public: | ||
| + | |||
| + | The Infrastructure Provider may expose physical resources, virtual resources, cloud services, managed infrastructure, | ||
| + | |||
| + | An Infrastructure Provider may also provide identity, monitoring, security, lifecycle management, support, and service-level capabilities associated with the supplied infrastructure. | ||
| + | |||
| + | A [[public: | ||
| + | |||
| + | ===== Definition ===== | ||
| + | |||
| + | // | ||
| + | |||
| + | ===== Source ===== | ||
| + | |||
| + | Generalized from infrastructure management, cloud computing, data-center operations, outsourcing, | ||
| + | |||
| + | ===== Note ===== | ||
| + | |||
| + | An Infrastructure Provider may be internal or external to the organization using the infrastructure. | ||
| + | |||
| + | The Infrastructure Provider role does not by itself identify ownership of the workload, application, | ||
| + | |||
| + | ===== Example ===== | ||
| + | |||
| + | An enterprise infrastructure team operates private compute clusters, storage systems, networks, and virtualization services for internal product teams. The enterprise infrastructure team acts as the Infrastructure Provider. | ||
| + | |||
| + | ---- | ||
| + | |||
| + | <WRAP centeralign> | ||
| + | © 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc. | ||
| + | </ | ||