* h1. What *
The custom resource managed services broker is will be responsible for creating instances :
- exposing sliced plans to the catalog
- Allowing the provision of custom resources slice plans
- Allowing deprovision of slice plans
- Allow binding of slices
- Allow deleting of slice bindings.
h1. How
h2. Exposing Slice Plans to the Catalog
When the catalog makes a request to the catalog end-point of this broker. When this end-point is called, the broker will scan all sharedservices and for operators any that are status ready, it will look for a matching SharedServicePlan resource and parse that resource into a set of service classes to act on return to the service catalog .
h2. Allowing Provision of Slice Plans
When a provision of a shared service slice is requested, the broker will create a SharedServiceSlice resource for the requested sharedservice type.
It allows us will also enable the catalog to leverage retrieve the UI flow last_operation for the provision of a slice.
h2. Allow Deprovision of Slice Plans
When a user requests the catalog deprovision of a SharedServiceSlice, the broker will delete the SharedServiceSlice object, and also expose a last_operation to the ability catalog for the catalog progress of the deletion of the slice.
h2. Allow Binding of Slices
When the user requests a binding to manage secrets the running Slice, the binding params in the service class will show input for the required user 's namespaces parameters (e . g. binding type for keycloak).
Once
The broker will then take these parameters and convert them into a SharedServiceAction which contains the UI piece around operators becomes clearer it may turn out we don't need this for servicename and the moment though it gives us user parameters.
h2. Allow Unbinding of Slices
When the user deletes a useful bridge binding, the broker will delete the SharedServiceAction resource .
|
|
