pulp_installer will be able to upgrade to
pulpcore 3.22 (when it is available) using their existing Ansible Playbooks. However, no further releases of
pulp_installer will be made.
Users wishing to upgrade to
pulpcore 3.23+ will need to migrate their deployment to use containers. There are multiple options for running Pulp services as containers[0,1,2]. Upgrade instructions will be provided prior to the
pulpcore 3.23 release.
Two main motivators: 1) User Feedback and 2) Too costly to maintain relative to a container based option.
- If a user doesn’t already use Ansible, the installation of Pulp is seen as to large a barrier to entry.
- When the intaller has any problem/error because it’s so complex, even long-time Ansible users aren’t in a position to figure it out.
- The installer needs a lot of work for each OS version it supports. Containers need almost none.
- The CI test matrix for supporting all of OS versions is huge and takes a lot of human time just to keep it going. It breaks very often.
- Users need container based installs to run Pulp where they want, so having a container-based option is already a sunk cost
- Having one installation asset, i.e. used by all users will give better results for everyone