Filtering of Services and Control-Planes with Organization Origins

tobru commented

2025-04-07 14:50:02 +00:00

Owner

Stories

As a portal admin, I want to configure organization origins to filter available services.

Implementation Notes

As a follow-up to #37 we need to implement a filtering system based on organization origins and information we retrieved from the OSB API.

If nothing is configured (default): everything visible (no filtering).

Cloud Provider Access

In the organization origin setting, allow configuring which cloud providers the organization has access to. When this is configured, only allow seeing and provisioning instances on the selected cloud providers

Service availability

In the OSB provisioning step, the parameter service_id is used to enable access to a certain service. For that, we need to store the service_id in the service offering and use this to filter which services are available to the organization. We also have to store the service IDs received via OSB in the organization to be able to know which services an organization has access to.

In the services list, we show the activated services as usual and other available services but non-activated in a "disabled" state so that the user knows what else would be available. For these disabled services, we need to show a help text that explains that these services have to be enabled on Exoscale first before they become available in the Servala portal.

See attached file how Glasskube is doing it

## Stories _As a portal admin, I want to configure organization origins to filter available services._ ## Implementation Notes As a follow-up to #37 we need to implement a filtering system based on organization origins and information we retrieved from the OSB API. If nothing is configured (default): everything visible (no filtering). ### Cloud Provider Access In the organization origin setting, allow configuring which cloud providers the organization has access to. When this is configured, only allow seeing and provisioning instances on the selected cloud providers ### Service availability In the OSB provisioning step, the parameter `service_id` is used to enable access to a certain service. For that, we need to store the `service_id` in the service offering and use this to filter which services are available to the organization. We also have to store the service IDs received via OSB in the organization to be able to know which services an organization has access to. In the services list, we show the activated services as usual and other available services but non-activated in a "disabled" state so that the user knows what else would be available. For these disabled services, we need to show a help text that explains that these services have to be enabled on Exoscale first before they become available in the Servala portal. See attached file how Glasskube is doing it

glasskube-console2.png

61 KiB

tobru added this to the Exoscale Integration milestone 2025-04-07 14:50:02 +00:00

tobru added the

enhancement

label 2025-04-07 14:50:03 +00:00

tobru added this to the Development Planning project 2025-07-04 08:36:10 +00:00

tobru referenced this issue

2025-09-26 06:29:07 +00:00

Open Service Broker for Exoscale - Onboarding #37

tobru referenced this issue

2025-09-29 07:21:32 +00:00

Implement Exoscale onboarding API endpoint #199

tobru referenced this issue

2025-09-29 14:46:23 +00:00

Implement Exoscale onboarding API endpoint #199

rixx referenced this issue

2025-10-17 03:57:21 +00:00

October feature list #226

tobru commented

2025-10-17 08:55:17 +00:00

Author

Owner

The "Limit to these Cloud providers" setting must be available in the organization origin setting and inherit from there into the organization. In the organization, when this setting is set on the organization origin, don't allow changing it (like the billing entity). When this setting is changed on the organization origin, it must be reflected on all organizations (unlike the billing entity)
When "Limit to these Cloud providers" is set, hide the "Cloud provider" filter option on the services list view
The "No services found" card is too wide and not aligned in sizing with the filter bar on the services list view

* The "Limit to these Cloud providers" setting must be available in the organization origin setting and inherit from there into the organization. In the organization, when this setting is set on the organization origin, don't allow changing it (like the billing entity). When this setting is changed on the organization origin, it must be reflected on all organizations (unlike the billing entity) * When "Limit to these Cloud providers" is set, hide the "Cloud provider" filter option on the services list view * The "No services found" card is too wide and not aligned in sizing with the filter bar on the services list view

rixx commented

2025-10-21 16:14:42 +00:00

Member

The "Limit to these Cloud providers" setting must be available in the organization origin setting and inherit from there into the organization. In the organization, when this setting is set on the organization origin, don't allow changing it (like the billing entity).

Right, not sure how I overlooked this – follow-up question: Do we need this setting only per origin or also per organization?

> The "Limit to these Cloud providers" setting must be available in the organization origin setting and inherit from there into the organization. In the organization, when this setting is set on the organization origin, don't allow changing it (like the billing entity). Right, not sure how I overlooked this – follow-up question: Do we need this setting only per origin or also per organization?

tobru commented

2025-10-22 05:47:46 +00:00

Author

Owner

For now we only need it in the organization origin. It could pop-up as a feature request to also have this setting per organization in the future, but not now.

rixx referenced this issue from a commit

2025-10-22 09:39:57 +00:00

Limit cloud providers per organization origin

tobru commented

2025-10-22 13:30:46 +00:00

Author

Owner

One last thing: Billing entity in organization origin shouldn't be mandatory.

rixx referenced this issue from a commit

2025-10-22 13:40:49 +00:00

Make sure origin billing entity is not mandatory

tobru closed this issue