Have something to say?
UI Support for Shared Networks and Subnets
Users can create ports via CLI on networks and subnets they have access to. However, the OSIE UI currently does not show which shared/authorized networks and subnets are available to the user/project. Please implement a UI view that shows all accessible networks and their corresponding subnets and makes them available for port creation.
Add configurability for the openstack workers
Nova api intermittently stops responding. From the logs this usually happens at :00, :15, :30 and :45 and a lot of the requests look to come from Osie. We can tune the number of workers on the Openstack side but I wondered if there are there any tuneables within Osie to define how the poller runs against Openstack? E.g limiting the max number of connections it will simultaneously make to Openstack or defining the polling interval? I’m just wondering if there’s a way to smooth out the number of requests.
Upgrade Keycloak to 26.8.2
we need keycloak upgraded along with osie-api upgrade as old keycloak images are very much vulnerable and those vulnerabilities are critical too. We need continous keycloak upgrades not just a one time bump as fixes are released almost weekly by keycloak.
Security Group is not displayed on the Port after saving
Security Group changes appear to be accepted without errors, but the assigned Security Group is not visible after saving. This prevents us from confirming whether the intended security policies are applied to the Port.
Implement Realm/Org selector on login screen
Hi Team, again, following up on our previous discussion :) Currently each login realm gets its own URL like https://osie.example.com/auth/realms/customer1/login In order to have an easier experience for customers, we implemented a subdomain redirect so customer1.osie.example.com goes to https://osie.example.com/auth/realms/customer1/login. This works fine but becomes difficult to manage for a large number of customers. Coming from another platform, we had an idea if it would be possible to implement a text box in the GUI that would allow customer to log into their Organization or Realm without changing the URL manually. Something like: I’m not sure however if this is even possible with the current backend design of the application that puts realms into different URLs and dedicated login screens that could be different from customer to customer based on auth methods they set up. Just wanted to throw the idea out there to consider :) Thank you.
Enable management of user identities in GUI
Hi Team, following up on our Slack discussion. Currently we have admin users that initially logged into a realm using local credentials and then using Keycloak OIDC. We want to disable local login for these users and keep only OIDC working + one local admin in the realm in case OIDC breaks. Currently there’s no way to diassociate user identity (like OIDC or local login) from particular user. Would it be possible to implement GUI similar to how Gitlab operates where user exists as one record but can be associated with multiple identities (like LDAP, OIDC, local login etc). If this existed, we would be able to “delete” the local identity from the user and keep only the OIDC identity if that makes sense. Thank you very much!
Organization-Specific Metadata During Server Creation
Customers should be able to define metadata at the organization level and select or enter it in the portal during server creation. The predefined metadata should be available across all projects within the respective organization and passed to OpenStack when creating a server.
sign-up link shows up when sign-up is disabled
sign-up disabled on all realms but still get the link to sing up. Trying to sign up will fail saying signup is disabled for this realm.
Floating IP port forwarding
https://docs.openstack.org/neutron/2026.1/admin/config-fip-port-forwardings.html with port ranges would be very helpful feature to implement for our customers but right now it only works in CLI. It uses port_forwarding neutron plugin. openstack extension list --network -c Alias | grep -i port-forward | expose-port-forwarding-in-fip | | floating-ip-port-forwarding-description | | floating-ip-port-forwarding-detail | | floating-ip-port-forwarding-port-ranges | | floating-ip-port-forwarding |
Selecting project removes realm selection
In client area when I have any realm selected and open user or org realm still stays selected in the dropdown menu but when clicking on project realm resets to “All realms"
Support for address-group extension
Having address-group and security-groups-remote-address-group would allow users to use address lists in security groups and firewall groups like so: openstack address group create \ --description "test address group" \ --address 10.10.10.5/32 \ --address 192.168.100.0/24 \ test-ag openstack security group create ag-test-sg openstack security group rule create \ --ingress --protocol tcp --dst-port 22 \ --remote-address-group test-ag \ ag-test-sg openstack security group rule list ag-test-sg --long +-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+ | created_at | 2026-11-04T22:38:21Z | | description | ag-test-sg | | id | ae8e7416-7f34-40ed-9244-b95da32e0715 | | is_shared | False | | name | ag-test-sg | | project_id | c151a4e809ad4b33a9b1434632454ad8 | | revision_number | 1 | | rules | created_at='2026-11-04T22:38:21Z', direction='egress', ethertype='IPv6', id='0d66a044-ccc4-4e24-a3e7-89e4ff212f13', standard_attr_id='31028', | | | updated_at='2026-11-04T22:38:21Z' | | | created_at='2026-11-04T22:38:21Z', direction='egress', ethertype='IPv4', id='d915023a-c31a-440a-8fe0-ae736424234e', standard_attr_id='31031', | | | updated_at='2026-11-04T22:38:21Z' | | stateful | True | | tags | [] | | updated_at | 2026-11-04T22:38:21Z | +-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
Renaming projects via OSIE portal
Our customer renamed a project via osie portal but the change was not reflected in openstack/keystone. So the project name now differs in osie portal and openstack/keystone.
Serve the admin console on its own domain
Operators want to open the admin console from a dedicated hostname, such as admin.cloud.example.com, without signing in to the client portal first and then typing /osie_admin/. Today the admin console works only under /osie_admin/ on the same domain as the API. If the Helm chart is given a separate admin hostname, the console fails to load, because the API refuses browser requests from any other domain. The client portal also has no link to the admin console, even for admins. What we'd like The Helm chart accepts an admin hostname and serves the admin console there, with / taking you to the console. The API accepts requests from the configured admin domain. Sign-in and sign-out on the admin domain land back on the admin console. Workaround until then An HTTPRoute that redirects the admin hostname to https:// /osie_admin/.
Display volume size in GiB
Would it be possible to select Gibibyte vs Gigabyte units when creating volume to match horizon/Openstack using Gibibyte?
IP restrictions - org admin
If i lock a project down to an IP which isn’t my own and then login - it lets me login and the project shows as locked (as expected) but the slight downfall is then that because i'm logged in as an org admin i can go to the organisation and update the IP allow list with My IP, which then unlocks the projects. I think updating the org settings should only be possible if the IP of the currently logged in user matches the allow list. If a user locks themselves out then it would require intervention from the provider to unlock it.
Customer Self-Service User Deletion
Customers should be able to fully delete their own users from OSIE, not only revoke permissions. The deletion should be possible without intervention from an OSIE Admin, while the internal realm remains protected.
WHMCS Payment Integration Issue
We have an issue regarding WHMCS payment gateway integration. The invoice was paid, but unable to add funds. For context, the invoice id is 348925 WHMCS = paid OSIE = error Gateway Message = An error occurred while adding the funds Thank you
quota per volume type
Project’s dashboard quota panel shows only total quota for volumes but our model is to share specific volume types with customers. Therefore it would be better to show them quota per each volume type shared with them or where it is set plus the total quota. Something like this:
RabbitMQ - migrate transient_nonexcl_queues to durable queues or exclusive transient queues
Rabbit 4.3+ dropped support for transient_nonexcl_queues, which is the type of queues OSIE is trying to create (the feature has been deprecated since 2021 - https://www.rabbitmq.com/release-information/deprecated-features-list, but up until 4.3 RabbitMQ only threw warnings into log, now it rejects them). This can be worked around by setting deprecated_features.permit.transient_nonexcl_queues = true in RabbitMQ cluster configuration, however it’s not a permanent fix since the the feature will be removed in future RabbitMQ versions. Documentation at https://www.rabbitmq.com/docs/queues#durability recommends switching to different type of queues: Transient (non-durable) non-exclusive classic queues are deprecated and cannot be declared by default starting with RabbitMQ 4.3.0. Please use one of the following: - durable queues - non-durable exclusive queues - durable queues with a queue TTL (a reasonably close equivalent to non-exclusive transient queues) To explicitly allow transient non-exclusive queues, add the following line to rabbitmq.conf: Enables deprecated non-durable (transient) non-exclusive queues (disabled by default as of RabbitMQ 4.3.0, will be removed in a later version) deprecated_features.permit.transient_nonexcl_queues = true Do you plan on implementing this in the future in order to not run into problems when upgrading to newer RabbitMQ version in the future? Thank you.