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.
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.
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 |
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 | +-----------------+----------------------------------------------------------------------------------------------------------------------------------------------------------+
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.
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:
Storware Workflow timestamps
Display timestamps for workflows, especially when they were started and completed.
SMTP Test Functionality
Please add an SMTP test functionality to the OSIE WebUI. Administrators should be able to trigger a test email directly from the SMTP configuration page to verify that the configured SMTP server, authentication, and email delivery are working correctly.
FWaas v2
add support for neutron firewall https://docs.openstack.org/ocata/networking-guide/fwaas-v2-scenario.html
Kubernetes Operator & GitOps
Build a Kubernetes Operator to deploy and manage OSIE in a GitOps way, including: version upgrades configuration reconciliation such as: platform configuration openstack connections pricing configurations flavor and image categories
Email event log or bcc
I’d like, at minumum, to have the option to bcc on every email the Osie system sends. Ideally it should have an email logs similar to the audit log, that administrators can use to see the full contents of emails being sent.
Session Timeout
Please add support for configurable session timeouts to improve security and compliance. Administrators should be able to define inactivity and session lifetime limits, with automatic logout after the configured timeout period. This helps reduce the risk of unauthorized access through unattended sessions.