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, python packages, and any non-python dependencies, e.g. the webserver. A small number of aspects of the installer won't be relevant to containers. For example, containers don't need systemd-units installed because the user starts the container or something like openshift will start the container. That's the only aspect I can think of that is current planned in the redmine tickets. -Brian On Fri, Jun 8, 2018 at 10:21 AM, Bryan Kearney <[email protected]> wrote: > 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 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 you!) > > > > If you could benefit from a Pulp 3 installer, please have a look through > > the features and stories to make sure we cover your use cases. > > > > Comments, questions, feature requests, and uses cases are encouraged on > > the redmine issue: > > https://pulp.plan.io/issues/3716 > > > > > > _______________________________________________ > > Pulp-list mailing list > > [email protected] > > https://www.redhat.com/mailman/listinfo/pulp-list > > > > > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
