Bruno, thank you for pointing that out. I agree.
This introduces a new use case: to be able to install Python packages to
the system and not into a virtualenv. It also made us think about root as
being a requirement for running this playbook with its defaults. I've
updated the two tickets that
Just a note: As containers are already isolated from the hosting system I
think that a Virtualenv is an unnecessary layer inside a container, we can
just install the packages in the container's Python environment.
--
Bruno Rocha
Senior Quality Engineer
Red Hat
It's a legit question. A small amount of the installer work would be unused
but not much.
The installer (or something like it) will be needed to install+configure
the bits inside the containers themselves. Specifically, the installer
could be used to populate a container with the virtualenv,
Somewhat of a troll, somewhat not. If pulp3 was delivered only in
containers on top of kube... how much of the installer work "goes away"?
-- bk
On 06/07/2018 05:53 PM, Austin Macdonald wrote:
> The installer sub-group has collected use cases and drafted a high level
> design for a unified
The installer sub-group has collected use cases and drafted a high level
design for a unified Ansible installer for Pulp 3.
Our goal is that this installer will be useful for:
- end users
- QE
- developer installation
- plugin writers
- integrators
- other (please comment if this is
