[Pulp-list] dropping el6 builds of Pulp

Brian Bouterse bbouters at redhat.com
Tue Nov 29 19:58:24 UTC 2016

Here are some links to stories/tasks that have been written/updated
recently based on this conversation.

- Getting Ansible to entirely install and/or configure Pulp [0].
- Ensuring all Pulp packages have setup.py files with requirements [1].
- Publishing Pulp via PyPI [2].

In addition to the issue tracker, the pulp-dev mailing list [3] may be a
good venue to collaborate on converging/developing Ansible playbooks for
Pulp also.

[0]: https://pulp.plan.io/issues/2443
[1]: https://pulp.plan.io/issues/278
[2]: https://pulp.plan.io/issues/2444
[3]: https://www.redhat.com/mailman/listinfo/pulp-dev

On Tue, Nov 29, 2016 at 11:54 AM, Jeremy Audet <jaudet at redhat.com> wrote:

> > In theory, you can pip install pulp now right from the git repositories
> if you just check out the desired release tags.
> Is this true? Some of the Pulp-related git repositories (perhaps all of
> them?) lack a setup.py file, which is the first thing I look for when
> trying to install Python software. Additionally, it's unclear which git
> tags should be checked out. For example, pulp_python has a tag named
> '1.0-release'. Which Pulp releases does that tag work with? And pulp_rpm
> has a tag named '2.9-release' - does this tag correspond to 2.9, 2.9.1,
> 2.9.2, etc?
> > The challenge of course is that today the RPMs provide much more than
> just the code; apache configs, /etc/pulp, /var/lib/pulp, selinux stuff,
> startup scripts, etc. It would be great to move a lot of that work to a
> config management system and treat that as an installer, which is probably
> the biggest chunk of work currently necessary to make "pip install" a
> viable deployment technique. This would be wonderful to have. Another great
> benefit to this general effort is that it would open up the possibility of
> installing Pulp on Debian-based systems.
> Can we completely separate the installation and configuration steps? Could
> we let the user install Pulp via whatever method they prefer, such as via
> pip, dnf/yum, apt*, pacman, emerge, ansible, etc, and then let the user
> also configure Pulp via either Ansible or manually?
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20161129/47523d94/attachment.htm>

More information about the Pulp-list mailing list