Pulp 2.11.0 Release Candidate 2 is now available, and can be downloaded from
the 2.11 beta repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.11/
The new feature for pulp-manage-db has failed upgrade testing and has been
removed from this
release. This feature is outlined in th
On 12/08/2016 02:31 PM, Kodiak Firesmith wrote:
> Just speaking for myself here, but when Red Hat converged on Puppet
> (~2011?), we went all-in on that so we're a Puppet shop. We didn't expect
> Red Hat to go flipmode on us and buy Ansible 3 years later. So I'm only
> interested in Puppet right
Two things that come to mind:
* if nodes was indeed replicating the pulp user metadata (of which I am
unsure), then you will have to make it clear that going with repo syncs is
not quite equivalent
* sync runs are asynchronous calls. If a call runs for too long, there may
be more than one sync tas
Kodiak,
I think Katello is using sync schedules but they have some other solution
lined up for when we drop them in 3.0. I am not sure of the exact details.
The main reason for dropping sync schedules was to keep the 3.0 MVP as
small as possible and we felt like we could offload the functionality