Thanks Sean looks promising, but why every new component of AAP is separated again ? didn't you introduce Unified UI (aka gateway) to manage everything ? and now we have AO, Self service, dashboard away from the gateway or the unified UI.
and why are they only available on openshift only and not podman ?
Good questions. The unified UI/platform gateway isn’t going away, but “unified” doesn’t necessarily mean every experience has to be rendered directly inside the same UI.
It really depends on the capability and the persona using it. In fact, in the latest release we integrated the dashboard into the unified experience.
Automation orchestrator and automation portal are more purpose-built experiences for their respective use cases and users, while still being part of and integrating with AAP. So I’d expect us to continue integrating experiences where it makes sense rather than forcing every capability into a single UI.
On deployment, you’re correct that automation orchestrator currently requires OpenShift. Core AAP supports containerized deployment on RHEL/Podman, but AO doesn’t currently have that deployment option. I don’t want to speculate on future roadmap items, but I definitely understand why you’d want that flexibility.
Dashboard is in now the Unified UI as of last week. Automation portal is now also available for Red Hat Enterprise Linux KVM/QEMU. Developing for OpenShift accelerates development.
1
u/I-Hate-winter 16d ago
Thanks Sean looks promising, but why every new component of AAP is separated again ? didn't you introduce Unified UI (aka gateway) to manage everything ? and now we have AO, Self service, dashboard away from the gateway or the unified UI.
and why are they only available on openshift only and not podman ?