Skip to content

Infrastructures and Profiles

Infrastructures are your organization's own cloud platforms that you provide and register within the system. It represents the physical or virtual resources where managed services will be deployed. Once you register an Infrastructure, you can create Profiles that define specific configurations for deploying managed services on that Infrastructure. This allows you to leverage the platform's management capabilities while maintaining control over your underlying infrastructure.

How it works

To use the platform's managed services, you must:

  1. Register your infrastructure: Bring your own private cloud environment and connect it to the platform.
  2. Create Profiles: Once registered, create one or more Profiles for that Infrastructure. Each Profile contains specific configurations that define how managed services will run, such as available flavors, storage options, and other infrastructure-specific settings
  3. Deploy managed services: When deploying a managed service (such as VMs or Kubernetes clusters), select which Profile to use. The platform connects to your infrastructure and deploys the service according to the Profile's configuration

This approach provides the flexibility to use the platform's service management capabilities while maintaining full control and ownership of the underlying infrastructure.

Supported Infrastructures

Currently, the platform supports OpenStack-based private clouds as the primary infrastructure type. This means not only your private OpenStack clouds but also public OpenStack-based cloud providers can be registered as Infrastructures. Support for additional infrastructure types (such as AWS, Azure, GCP, VMware, etc.) is planned for future releases.

Best Practices

  • Start with a single infrastructure: If you're new to the platform, start by registering one infrastructure to get familiar with how it works. This allows you to learn the ropes without overwhelming yourself with multiple environments.
  • Principle of least privilege: When registering an infrastructure, use credentials with the least privileges necessary for the platform to manage resources.
  • Use Profiles for governance: Profiles are a powerful tool for organization admins to define and enforce resource usage policies. Rather than giving teams access to all available infrastructure configurations, create curated Profiles with only the subset of flavors and resources you want teams to use. For example, you might create a "Development" Profile with smaller VM flavors for dev/test work, and a "Production" Profile with larger flavors and stricter settings for production workloads. This ensures teams stay within approved limits while maintaining operational flexibility.