Have something to say?
Impersonate user when using IDP
When we go to impersonate a user from the client area it provides the URL however attempting to use it takes us to the sign-in page. The sign in page only offers the option to redirect to the IDP therefore doesn’t work as the impersonation is done by Osie and our IDP isn’t aware.
Moving a project keeps existing permissions
Moving a project from one organisation to another does not look to update the user permissions. I’d expect when a project moved to another organisation that it would: Update user permissions to match those at the organisation level Update the billing profile to start billing from that point forward to the billing profile linked to the organisation
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
AZ settings relying on volumev3 endpoint
OSIE Version 26.6.1, Openstack 2026.1 service provider availability zone configuration only picks up cinder when volumev3 endpoints are recreated. Under customer portal it shows no volumes in the menu or when creating a new server with the new endpoint again only recreating volumev3 fixes it.
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
Trove create DB missing network
When creating a DB with trove in OSIE as a customer, it shows no dropdown or selection for which network the service should be on, where does that get configured?
Kubernetes PVC claims not adhering to AZ choice
(This could very well be my problem and not an issue with OSIE) I created a kubernetes cluster with magnum and its up and good. When I create an application on it with persistant volume claims, it tries to use my FSD1 availability zone. Within the OSIE Admin portal, I do NOT have Availability zones set for cinderv3 or anything at all. Is osie not adhering to that AZ setting when setting up the clusters with Magnum, or is this an openstack problem? I am not sure if this is something that needs to be corrected when creating the cluster so it knows the AZ (‘nova’) to put its volumes, or if I just need to work with customers to have them specify the az as nova manually for every application with a PVC that they deploy.
Magnum/Kubernetes node status incorrect
I’m provisioning a cluster right now and the cluster status is UNHEALTHY because the worker nodes are still provisioning. Within OSIE it shows those nodes as green, but they are not From the Kubernetes status, it shows 0 workers available, but you can’t tell that in OSIE. I’m not sure how much is available to you with just the magnum API calls..not sure if this deeper info is exposed to you.. but it would be great to have this be more factual, and show these systems red, so its obvious why the thing is UNHEALTHY
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.
Network Topology View
For customers, it would be a great feature to have a view of the network topology similar to the one in Horizon. (e.g. external Networks, internal Networks and routers)
Account Settings
The account section cannot be managed; clicking on the username—“Account”—in the upper-right corner only takes you to the organizations and projects, but not to an account page. There needs to be a way to manage your account (e.g., reset password and MFA).
Unimport Project
Please consider to enable unimport project function of existing project without cloud resources deleteion. Thank you.
Globally available custom roles across orgs
Allow creating custom roles at a global level so they can be applied to any organization, rather than requiring roles to be defined per org. The specific use case is a billing / read-only role reusable across orgs. No option for this appears to exist in osie_admin.
Password Policy
Could you please add support for configurable password policies in OSIE user authentication? Examples: Minimum password length Special character requirements Password history Prevent use of username or email address in passwords This would help customers meet their security and compliance requirements.
BGP Dynamic Routing in Neutron
Add support for https://docs.openstack.org/neutron/latest/admin/config-bgp-dynamic-routing.html
Metadata for Organizations and Users
I’d like simple metadata capabilities on Organizations and Users so I can cross-relate to my external CRM by ID. I would need to be able to set the meta data by API as well as part of a new customer onboarding.
Delete project by API call
the functionality exists in GUI nut not in admin API. Would be nice to add: DELETE /api-v1/admin/project/{id}?cascade=true (schedule deletion) DELETE /api-v1/admin/project/{id}/now (delete immediately) My end goal here is to create a demo project I could completely delete and recreate each night
API create user endpoint with invalid date
Users created with the admin_api/v1/users POST endpoint have an invalid create date. curl -X POST 'https://osie.domain.com/admin_api/v1/users' \ -H 'Authorization: Bearer eyJhb...Ig' \ -H 'Content-Type: application/json' \ -H 'Accept: application/json' \ -d '{ "email": "ficticious@abc.com", "sub": "ficticious@abc.com" }' Also, feature request for first_name and last_name to be available at user creation. The endpoint doesn’t support those fields currently but GET does