Identity design for VCF Automation where tenants and provider each use separate identity providers; compare the Enterprise model, where everyone shares one.
Read more: Broadcom TechDocs
In the Ultra Transcenders books
Each book explains Service Provider model in context, with comparison tables and the common traps.
Terms in this definition
- IDENTITY
A column property, written IDENTITY(seed, increment), that gives each new row the next number in a rising sequence. SCOPE_IDENTITY reports the latest value created in the current scope, and a rolled-back transaction still uses up the numbers it took.
- VCF Automation
Self-service platform in VCF for provisioning VM, Kubernetes and AI workloads. Providers manage regions and tenants in one portal, while tenants handle projects and consumption in theirs.
- WHERE
Limits a SELECT, UPDATE or DELETE to just the rows meeting a condition. Omit it, and the statement hits every row.
- Provider
The organisation that shares data in OpenSharing. Recipients also see a provider as a Unity Catalog securable, from which shares can be mounted as catalogs.
- Enterprise model
Sign-in setup in VCF Automation where one IdP serves both provider and tenants. With the Service Provider model each side has its own.
- Shares
A relative weighting for dividing a contended resource such as memory, CPU, network bandwidth or disk I/O: double the shares earns double the entitlement. Reservations, by contrast, are guarantees and limits are ceilings.
Related terms
- Enterprise authentication model
In this VCF Automation model, one identity provider serves both the provider organization and its tenants (the service provider model, by contrast, uses separate ones). Tenants reach it directly via SAML or OIDC, whereas the provider goes through VCF Identity Broker and so also gets single sign-on to other VCF components.