Re: [Pulp-list] Pulp 3.20 content server

Hi Bin, I don't have an answer for you, but I'd like to invite you to start posting questions to https://discourse.pulpproject.org/. There is a "support" category there which would be a good fit for these types of questions. Would that work for you? This mailing list will likely be put into read

Re: [Pulp-list] Can't build PEX out of pulp-cli because of missing dependency

I don't work with the CLI, but I have seen projects declare a dependency on setuptools. That would make sense to me. On Wed, Dec 15, 2021 at 6:12 AM Konstantin M. Khankin < khankin.konstan...@gmail.com> wrote: > Hello Matthias! > > This workaround is sufficient for me. However, I feel like the

Re: [Pulp-list] redis on a passive backup server

Pulp wasn't in use. If that were the case cache invalidations not reaching it would be fine because the cache would be empty at failover time. As always though, there could be more needed to handle some specific use cases. > On Mon, Sep 20, 2021 at 10:31 PM Brian Bouterse > wrote: > >

Re: [Pulp-list] redis on a passive backup server

I believe with 3.14+ and new style workers, you can have an independant redis on the backup server. With the new-style tasking system (the default in 3.14) you no longer need Redis for tasking. It's only purpose then is to help speedup the content app which caches info about requests to make

[Pulp-list] pulpcore 3.14.0 is Generally Available

This release contains a lot of exciting features. See the blog announcement for a great recap of the major highlights, or or the github discussion announcement for info on upgrading and changelog links. https://pulpproject.org/2021/07/01/pulpcore-3.14-release-announcement/

Re: [Pulp-list] Content server Performance

On Tue, Jun 22, 2021 at 11:56 AM Danny Sauer wrote: > You can certainly run multiple instances of the content server. It just > needs a connection to the database and access to the storage. > Agreed, you could deploy additional content servers and have your nginx/apache load balance them. >

Re: [Pulp-list] pulpcore 3.13.0 is Generally Available

Yes it's here: https://github.com/fao89/pdc On Thu, Jun 3, 2021 at 12:11 PM Daniel Alley wrote: > I think that the resolver will have a hard time detecting package >> inconsistencies prior to upgrade when the installer calls pip for all the >> pulp modules individually. >> > > Yup, you're

Re: [Pulp-list] pulp mongodb upgrade

any other pulp logs . Thank you ! > > > > Sincerely, > Ramana Bora > > > > - Original message - > From: Brian Bouterse > To: Venkataramana Bora > Cc: pulp-list , Donal Keane > Subject: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgrade > Date: Wed,

Re: [Pulp-list] pulp3 remote mirrorlist

Yes I believe so. I also see some entries about it in the changelog https://pulp-rpm.readthedocs.io/en/latest/changes.html#id94 On Thu, Jun 3, 2021 at 1:58 PM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net> wrote: > Does the pulp support a mirrorlist as the remote url? If not, will this >

Re: [Pulp-list] [Pulp-dev] Github Discussions

I did this also for the pulpcore meeting: https://github.com/pulp/community/discussions/8 My format was a little different, but the same idea. On Thu, Jun 3, 2021 at 10:13 AM Grant Gainey wrote: > On Thu, Jun 3, 2021 at 9:40 AM David Davis wrote: > >> Based on feedback, I've moved discussions

Re: [Pulp-list] pulp mongodb upgrade

na can you post relevant log info when you get a chance tomorrow? > > Thanks, > > Donal > > > - Original message - > From: Brian Bouterse > To: Venkataramana Bora > Cc: pulp-list , Donal Keane > Subject: [EXTERNAL] Re: [Pulp-list] pulp mongodb upgrade &

Re: [Pulp-list] pulp mongodb upgrade

I don't have ready advice, but it might be helpful to post a snippet of the logs. Without that, all we know is there is a 500 server error, not what the cause could be. Have you considered migrating to Pulp3? Pulp2 is in maintenance mode, and likely has had its terminal release. Pulp3 is at 3.13

[Pulp-list] Pulpcore 3.11.2 Released

Since Pulp is trying GitHub Discussions, the actual announcement is here: https://github.com/pulp/pulpcore/discussions/1369 ___ Pulp-list mailing list Pulp-list@redhat.com https://listman.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Django v2.2.21 breaking changes

tl;dr You should temporarily downgrade Django for now back to 2.2.20. See #workaround below. # The issue It's unfortunate but Django's 2.2.21 breaks Pulp which given that Django 2.2.z is the Django LTS is extremely surprising to us. It actually broke a lot of projects. I've been investigating

Re: [Pulp-list] using ansible to install azure backend

I agree with @daviddavis. I think the installer would benefit from docs on how to configure django-storages for S3 and Azure as basic examples. I think the process is roughly: 1) Make sure the pulpcore[azure] pip extras is installed in the virtualenv:

Re: [Pulp-list] pulp 3.7.3 sync with checksum error

kages/s3transfer/tasks.py\", >>> line 126, in __call__\n return self._execute_main(kwargs)\n File >>> \"/opt/utils/venv/pulp/3.7.3/lib64/python3.7/site-packages/s3transfer/tasks.py\", >>> line 150, in _execute_main\n return_value = self._main(**kwargs)\n File >>

Re: [Pulp-list] PulpCon 2021

On Mon, Mar 15, 2021 at 11:12 AM David Davis wrote: > The topic of PulpCon came up today as spring is usually the time we begin > to plan PulpCon. The main question I think is whether we should hold > PulpCon again virtually this year or not. > > Optimally, we'd like to meet in person but given

Re: [Pulp-list] pulp 3.7.3 sync with checksum error

Did this happen inside a task? Did you see a traceback for it also? On Fri, Mar 5, 2021 at 12:00 PM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net> wrote: > The sync process gave an error "A file failed validation due to checksum". > Is this error caused by remote repo? Is there a way to

[Pulp-list] Removing MD5 and SHA-1 as default available checksums in 3.11

tl;dr With pulpcore 3.11, the plan is to remove MD5 and SHA-1 from the list of default available checksums. RPM and Migration plugin users will need to add this back in at 3.11 upgrade time for your systems to continue working. Please give on-list feedback on this change. ## Background Pulp has

Re: [Pulp-list] Possible to disable all client certificate checking?

Hi Don, Pulp by default doesn't use client certificate checking, so it's very possible. Really though if you're using Pulp through Katello, this is highly dependant on how Katello is a) configuring the webservers and b) if they would allow that configuration to occur. Unfortunately I don't know

Re: [Pulp-list] Apache 502 proxy errors when performing Pulp 3 to Pulp 3 syncs

Hi Adam, Thanks for sharing all of that and for opening that issue. Would you be willing to do one or two more things to help move it forward? Could you post the diff of the Apache config changes you made on the issue? Also if you'd be willing to open a PR I think it would go against this file.

Re: [Pulp-list] Content plugin for Conan packages

Hi Marcin, There isn't currently; the current list of plugins is here: https://pulpproject.org/content-plugins/#pulp-3-content-plugins-information Our goal is to make plugin writing as easy as possible, and to support them through their development. If you know someone who is interested in

Re: [Pulp-list] Database migration from 3.3 to 3.7

Maybe it's selinux labeling related. What step is it stuck on in the installer's output? What OS are you using? On Sat, Dec 5, 2020 at 9:48 AM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net> wrote: > We are upgrading pulp from 3.3 to 3.7. Ansible stuck on database migration > for more that

Re: [Pulp-list] pulp2 migration: AccessPolicy matching query does not exist

I've filed this issue tracking the improvement which would allow users to run `flush` and not experience this problem. https://pulp.plan.io/issues/7710 On Wed, Oct 14, 2020 at 12:14 PM Tatiana Tereshchenko wrote: > Adam, > I agree we lack documentation on resetting the environment and the >

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI PoC Feedback

I'm excited to use this. I went to try it, but the CLI's requests wouldn't trust the server which uses self-signed certificates. When running `pulp status` I get this error: requests.exceptions.SSLError: HTTPSConnectionPool(host='localhost', port=443): Max retries exceeded with url:

[Pulp-list] pulp-certguard 1.0.3 is Generally Available

pulp-certguard 1.0.3 has been released. It is compatible with pulpcore 3.3 through 3.8. This is a strict compatibility release and has no meaningful changes except declaring compatibility with pulpcore through 3.8. PyPI: https://pypi.org/project/pulp-certguard/1.0.3/ Changelog:

[Pulp-list] pulp_ansible 0.4.0 is Generally Available

pulp_ansible 0.4.0 has been released. It is compatible with pulpcore 3.7 and pulpcore 3.8 (not yet released). It contains only bugfixes, but we don't want to change the pulpcore version a plugin uses in the z-stream. See the changelog for all changes (link below). PyPI:

[Pulp-list] pulpcore 3.7.0 and pulp_file 1.3.0 are Generally Available

Pulpcore 3.7.0[0] and pulp_file 1.3.0[1] have been released. Details of the most important changes are available in our blog[2]. For a full list of changes, please check the changelog for pulpcore[3] and pulp_file[4]. Starting with pulpcore 3.7 plugins can now be compatible with both 3.y and

Re: [Pulp-list] Simple use case of mirroring external repos in pulp3

@Jim Davis My takeaway from this is that we need a verbatim mirror feature for pulp_rpm. Thanks for sharing that use case. On Tue, Sep 22, 2020 at 11:28 AM Jim Davis wrote: > I do think it is important that it is possible to have a verbatim repo > replication happen in a true mirror fashion

[Pulp-list] pulpcore 3.6.4 is Generally Available

pulpcore 3.6.4 is available on PyPI[0]. This release fixes bindings issues caused by a dependency that released backwards incompatible changes[1]. # Installation and Upgrade Users should use the 3.6.4 release of pulp_installer[2] to install or upgrade their installations. This version of the

Re: [Pulp-list] Can't get CentOS 7 Updates repo published

I don't know much about it, but I believe the sqlite db is used by some client types in some cases when fetching packages from Pulp. IIRC, if the sqlite db is not present it falls back to a less-efficient form of package fetching from Pulp. On Tue, Sep 1, 2020 at 4:53 AM Konstantin M. Khankin <

Re: [Pulp-list] pulpcore 3.6.0 and pulp_file 1.2.0 are generally available

pulp-certguard 1.0.2 has been released. It is compatible with pulpcore 3.6. This is a strict compatibility release and has no meaningful changes except declaring compatibility with 3.6 PyPI: https://pypi.org/project/pulp-certguard/1.0.2/ Changelog:

Re: [Pulp-list] Pulp 3 distribution trees

If you have a use case you'd like to share that is valuable to you, please do! On Thu, Jul 23, 2020 at 11:04 AM Dennis Kliban wrote: > Distribution trees are currently considered a tech preview feature. There > are multiple bugs that are actively being fixed at this time[0,1,2]. There > is

[Pulp-list] pulp-certguard 1.0.1 is available

pulp-certguard 1.0.1 is available on PyPI. This release is the same as 1.0.0, but now compatible with pulpcore 3.5.0 Changelog: https://github.com/pulp/pulp-certguard/blob/master/CHANGES.rst#101-2020-07-20 PyPI: https://pypi.org/project/pulp-certguard/1.0.1/ Docs:

[Pulp-list] General Availability of pulp-certguard 1.0.0!

Certificate based client authorization is now generally available with pulp-certguard 1.0.0. The pypi release is here [0] and the docs are here [1]*. There are no changes since 0.1.0rc5 so there is no meaningful, new changelog to see. The 1.0.0 release is compatible with pulpcore 3.3.z and 3.4.z.

Re: [Pulp-list] Tuning Pulpcore Worker Count in Katello

ly. More questions are welcome; this topic is important and can be a bit complicated with our lack of docs. :/ > > On Mon, Jun 15, 2020 at 2:14 PM Brian Bouterse > wrote: > >> >> >> On Mon, Jun 15, 2020 at 1:09 PM William Clark wrote: >> >>> Hell

Re: [Pulp-list] Tuning Pulpcore Worker Count in Katello

On Mon, Jun 15, 2020 at 1:09 PM William Clark wrote: > Hello Pulp Community! > > I'm working on a feature to allow the foreman-installer to set the number > of Pulpcore workers deployed on Katello or Content Proxy, and I require > some assistance from the Pulp community in setting sane defaults

Re: [Pulp-list] Pulp Core Support on SUSE

It should work anywhere Python 3.6+ and the dependencies are available so I expect it would. We currently do not test the CI against SLES like we do other distros. See the Supported Platform docs for more details [0] [0]:

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

certd, disabled > subscription management, and combinations in between. > > On Wed, May 27, 2020 at 2:23 PM Brian Bouterse > wrote: > >> If the certs are short-lived, then there isn't much to do except ask the >> issuer to give you longer ones. You could inspect the cert

Re: [Pulp-list] Syncing Red hat Repos entitlement issue

If the certs are short-lived, then there isn't much to do except ask the issuer to give you longer ones. You could inspect the certs more closely I believe using the `rct cat-crt` command. Pulp-certguard has some docs showing an example with that tool

Re: [Pulp-list] Bug triage is moving to #pulp-meeting on Freenode

Thank you for bringing this up. Do we know what needs to be done to resolve this? I filed this task to fix the minutes not being recorded, and added it to the open floor agenda also. https://pulp.plan.io/issues/6791 On Tue, May 19, 2020 at 6:06 PM Fabricio Aguiar wrote: > I just noticed one

Re: [Pulp-list] [Pulp-dev] RFC: pulp command line interface

Thank you for sharing this! Can a basic README be added showing a few things a user could try after installing it from source? I also put a few comments inline also. On Mon, May 11, 2020 at 1:53 PM David Davis wrote: > Adding pulp-list to hopefully get user feedback on this. > > David > > > On

Re: [Pulp-list] [Pulp-dev] Pulp 3 CLI MVP

I think having the commands namespaced by the plugin name would be an organized way to see what capabilities a given plugin is shipping. I imagine for pulpcore's commands they could be namespaced under 'core' or 'pulpcore'. Also +1 to 'pulp' command name. On Mon, May 11, 2020 at 6:42 AM David

Re: [Pulp-list] 3.3.1 migration error

On Mon, May 11, 2020 at 5:04 AM Tatiana Tereshchenko wrote: > Dennis, > FWIW, I believe there are a couple of problems here but neither of them is > related to your advice to manually modify a migration. > Problem #1. `django-admin makemigrations` was run, so this 0009_auto_... > migration got

Re: [Pulp-list] upgrade to 3.3

Hi Bin, Another user reported a similar error to you, and I've filed this issue https://pulp.plan.io/issues/6623 The "pre-flight" check is designed to verify that the pulpcore version being installed/upgraded to is compatible with all plugins that will be installed prior to any bits installing

Re: [Pulp-list] Pulp-list Digest, Vol 125, Issue 19

Hi Bin, Related to this issue, I have some questions I'm interested in. I posted them here https://pulp.plan.io/issues/6463#note-1 If you're able to post any info you have that would be great. Thanks. Brian On Mon, Apr 20, 2020 at 7:12 PM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net>

Re: [Pulp-list] pulp 3 publication required

Also regarding the order of the creation of these things, I believe in all cases a Distribution (of any type) can be created before it's corresponding repository_version or in other cases a publication (depending on the content type's needs). The use case is that a user may want to design their

Re: [Pulp-list] pulp 3.2.1 duplicate key error

I heard another developer report a similar issue, but we couldn't reproduce it. Could you file this as an issue also please? On Tue, Apr 7, 2020 at 3:42 PM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net> wrote: > Noticed we have a few errors when running sync. > > "error": { >

Re: [Pulp-list] Pulp-list Digest, Vol 125, Issue 10

lp-list digest..." > > > Today's Topics: > > 1. Re: Pulp 3 waiting tasks (Daniel Alley) > > > ------ > > Message: 1 > Date: Mon, 6 Apr 2020 17:24:11 -0400 > From: Daniel Alley > To: Brian Bouterse > Cc: pulp-list , Bin Li > Subject: Re: [Pu

Re: [Pulp-list] Pulp 3 waiting tasks

Thank you. We will look into this bug you've filed. I believe you can recover your current installation by canceling the tasks stuck in the "waiting" state. To cancel use this API call https://docs.pulpproject.org/restapi.html#operation/tasks_cancel Let me know if this doesn't help get your

Re: [Pulp-list] Pulp 3 waiting tasks

So the problematic thing I see in this output is the "resource-manager | 0". This tells me that Pulp's record of the task is in postgresql (and was never run), but RQ has lost the task from the "resource-manager" queue in Redis. So the next question is how did that happen? Would you be willing to

Re: [Pulp-list] Pulp 3 waiting tasks

Since the task that is stalled has a "worker" unassigned it tells me it has not traveled through the resource-manager yet. All tests in Pulp3 (currently) go through the resource-manager. I can see from your ps output there is 1 resource-manager running (which is good), and the status API agrees

Re: [Pulp-list] Pulp 3 waiting tasks

While you are experiencing the issue, can you capture the status API output? Also can you paste an output of the workers on that system with `ps -awfux | grep pulp`. Also do you see any errors in the log? Could you share a copy of the log? On Fri, Apr 3, 2020 at 9:01 AM Bin Li (BLOOMBERG/ 120

[Pulp-list] Pulp 3.2 Scale Testing to 27K Repositories and 173K Repository Versions

I recently did some scale testing for Pulp3, and I posted the performance results and reproducer scripts to the Pulp blog today. https://pulpproject.org/2020/03/05/pulp-3-scale-testing/ Any feedback, or questions are welcome. Thanks! Brian ___

Re: [Pulp-list] pulp 3 django.request:WARNING

I think maybe this issue is related to https://pulp.plan.io/issues/6057 When a fix for 6057 is released maybe you can confirm if this is happening still or not. Thanks! Brian On Fri, Jan 31, 2020 at 9:31 AM Bin Li (BLOOMBERG/ 120 PARK) < bli...@bloomberg.net> wrote: > Hi All, > > Just noticed

[Pulp-list] pulpcore 3.1.1 is Generally Available

Pulpcore 3.1.1 is available and contains bugfixes for database connection loss errors, S3 integration, and more. See the release notes for all the details. https://docs.pulpproject.org/en/3.1.1/changes.html Pulpcore 3.1.1 contains only bugfixes

Re: [Pulp-list] pulp3 High availability and disaster recovery

ng list submissions to >>> pulp-list@redhat.com >>> >>> To subscribe or unsubscribe via the World Wide Web, visit >>> https://www.redhat.com/mailman/listinfo/pulp-list >>> or, via email, send a mes

Re: [Pulp-list] pulpcore 3.1 is Generally Available

r| Pulp| Red Hat Inc. > > "Do not go where the path may lead, > go instead where there is no path and leave a trail." > > > On Fri, Jan 31, 2020 at 1:12 PM Brian Bouterse > wrote: > >> Pulpcore 3.1.0 is the first feature release of Pulp 3 and contains some

[Pulp-list] pulpcore 3.1 is Generally Available

Pulpcore 3.1.0 is the first feature release of Pulp 3 and contains some significant features and fixes. See the release notes for all the details. https://docs.pulpproject.org/en/3.1.0/changes.html Here are some highlights: * Azure support * signing services for plugins to use * restriction of

Re: [Pulp-list] pulp 3 list packages

What do the logs say about why the gunicorn process serving pulp-api is dying? Would you want to file an issue https://pulp.plan.io/issues/new so we can do some testing? As an aside, I recommend using paging when pulling so many items from an API. You could decompose your large request to more,

[Pulp-list] pulpcore 3.0.1 is Generally Available

Pulpcore 3.0.1 is the first bugfix release and contains some significant fixes. See the release notes for all the details. https://docs.pulpproject.org/en/3.0.1/changes.html Pulpcore 3.0.1 contains only bugfixes and no breaking changes for either users or plugin developers. This means all

Re: [Pulp-list] pulp3 s3 migration path

It's a bit manual, but a second pulp system could be setup with the new type of storage and it could sync from the first system. On Tue, Jan 7, 2020 at 2:46 PM David Davis wrote: > No, there is not. You cannot change your storage once you have set up and > started to use pulp. > > I'm not sure

Re: [Pulp-list] pulp3 High availability and disaster recovery

Sorry for the late reply. Each component of Pulp itself can be deployed in HA configurations. Of the services Pulp's processes depend on, Redis is the one service that can't run as a full cluster because RQ doesn't support that yet, so the best you can do is a hot-spare Redis that auto-fails over.

[Pulp-list] RPM, Container, and File plugins for Pulp 3.0 are Generally Available

The Pulp developer community is excited to announce the general availability of the following: * pulp_rpm 3.0 to manage RPM content -- https://pulp-rpm.readthedocs.io/en/3.0/ * pulp_container 1.0 to manage Docker content -- https://pulp-container.readthedocs.io/en/1.0/ * pulp_file 0.1 to manage

[Pulp-list] Pulpcore RC9

The pulpcore 3.0.0rc9 and pulp_file 0.1.0rc2 packages are available on PyPI [0][1]. There are a lot of changes that have happened; see the release notes for all the details. There were a few user-facing breaking changes, please especially read that part. Note this is expected to be the final code

Re: [Pulp-list] Pulp 3.0.0 Release Date, December 12

title correction: Dec 12th On Tue, Nov 26, 2019 at 11:08 AM Brian Bouterse wrote: > We're planning one final release candidate 3.0.0rc9 for Dec 3rd, and a > generally available release with improved documentation on Dec 12th. This > will include pulp_rpm, pulp_container, and pulp_fil

[Pulp-list] Pulp 3.0.0 Release Date, December 13

We're planning one final release candidate 3.0.0rc9 for Dec 3rd, and a generally available release with improved documentation on Dec 12th. This will include pulp_rpm, pulp_container, and pulp_file as well. This is a delay from the initial GA release date of Dec 3rd. Read the blog post for more

Re: [Pulp-list] Role Based Access Control for Pulp 3.y -- Use Cases

on freenode Agenda: We'll discuss the use cases in this doc <https://docs.google.com/document/d/1byC3kXNqK0b4vA7iwkS9FDUdU60gfofixzxCMfLBt8E/edit?usp=sharing> On Tue, Nov 19, 2019 at 4:54 PM Brian Bouterse wrote: > The RBAC use case discussion is happening tomorrow! Details are below. >

Re: [Pulp-list] How to troubleshoot: Cannot sync EPEL

On Mon, Nov 11, 2019 at 7:38 AM Tatiana Tereshchenko wrote: > Unintentionally, this conversation went off-list on Friday. I'm sending > this note to let everyone know that the thread is closed. > > JFYI, the summary of the discussion: > - .treeinfo error is not an error, it's just a way of Pulp

Re: [Pulp-list] pulp3 publication

Hi Bin, Thank you for your question. We talked this over some during the "open floor" part of developer triage. There are a few use cases that motivate allowing multiple publications of a single RepositoryVersion. The main reason: Publishers could take various options which could make the two

[Pulp-list] Role Based Access Control for Pulp 3.y -- Use Cases

I'd like to host a chat meeting to gather use cases for Role Based Access Control needs in Pulp 3.y. The meeting details and agenda link are below. Both users and plugin developers are invited. Please join if you're interested! When: Wednesday, November 20⋅9:00 – 10:00am EST or in your time zone

[Pulp-list] Pulpcore RC7

The pulpcore 3.0.0rc7, pulpcore-plugin 0.1.0rc7, and pulp_file 0.1.0b4 packages are available on PyPI [0][1][2]. There are a lot of smaller changes that have happened; see the release notes for all the details. One noticeable change is the field names starting with an underscore were renamed.

Re: [Pulp-list] pulp3 sync epel repo

I agree a single mirror as the source URL is what is expected currently. Neither pulp_rpm for either Pulp2 or Pulp3 (not GA yet) implement metalink support currently. You can file a feature request against Pulp3 to request this feature here: https://pulp.plan.io/projects/pulp_rpm/issues/new

[Pulp-list] Pulp 3.0 GA Timeline

We are very excited to announce a timeline for the GA releases of Pulp3 RPM, Docker, ISO/File, and pulpcore. The target date is Dec 3rd, 2019. See the full details in the blog post: https://pulpproject.org/2019/09/30/pulp-3-GA-timeline/ Thanks, Brian

[Pulp-list] pulp_ansible 0.2 Beta 3 is released

The beta 3 release of pulp_ansible 0.2.0 for Pulp 3 is now available ( https://pypi.org/project/pulp-ansible/0.2.0b3/ ). Here's some of the big changes: * replacement of `mazer` with the new `ansible-galaxy collections` CLI in the Ansible 2.9 release * easier out-of-the-box installer experience *

Re: [Pulp-list] New install: v2 vs v3

+1 to @kodiak's assessment. Also in terms of the use cases you identified; I believe those are all functional so the published bits (still pre-GA) would work to meet your needs. Asking questions via this list if you run into problems is good, or you could report issues via the the issue tracker

[Pulp-list] pulp_ansible 0.2 Beta 2 is released

The beta 2 release of pulp_ansible 0.2.0 release for Pulp 3 is now available ( https://pypi.org/project/pulp-ansible/0.2.0b2/ ). Here's some of the big changes: * full mirroring support for Collection sync * full-text search of collection using the 'q' query param * significantly more attributes

Re: [Pulp-list] ISE when getting distribution task state

Hi Jan, You're encountering ( https://pulp.plan.io/issues/4945 ) which was an issue in pulpcore. If you upgrade pulpcore to the latest released bits, it includes a change in the setting's default which should fix this for you. If you still encounter the issue after upgrading pulpcore, can you

[Pulp-list] Pulpcore RC4 is Available

The pulpcore 3.0.0rc4 and pulpcore-plugin 0.1.0rc4 packages are available on PyPI [0][1]. This release was prompted to resolve an incompatibility with djangorestframework 3.10.0 that released on July 15th. RC4 includes a new chunked/parallel upload feature and various bugfixes. We encourage users

[Pulp-list] Pulpcore RC3 is Available

The pulpcore 3.0.0rc3 and pulpcore-plugin 0.1.0rc3 packages are available on PyPI [0][1]. It includes many bugfixes, important usability improvements, and a few backwards incompatible changes. We encourage users to try RC3, through an RC3 compatible plugin on a non-production system. # Release

Re: [Pulp-list] create remote to redhat on pulp 3

It says "Timeout on reading data from socket" so either this is a bug, or the remote server is not delivering you data over the socket connection, perhaps due to some rate limiting. The remote has a download_concurrency option [0] so perhaps reducing that will cause the server to give you all of

Re: [Pulp-list] [Pulp-dev] Pulp 2 to 3 Migration meeting on Wednesday June 19th

On Thu, Jun 20, 2019 at 7:54 AM Dennis Kliban wrote: > On Wed, Jun 19, 2019 at 2:10 PM Eric Helms wrote: > >> Thanks for these updates. >> >> On Wed, Jun 19, 2019, 1:59 PM Tatiana Tereshchenko >> wrote: >> >>> The logs from the meeting can be viewed here[0]. >>> >>> We covered: >>> - hard

[Pulp-list] pulp_rpm Python and Ruby bindings available

The pulp_rpm plugin for Pulp3 now has Python and Ruby bindings available. See the new section of the docs here: https://pulp-rpm.readthedocs.io/en/latest/bindings.html The bindings will publish nightly, and with each tagged release. Thanks to @dkliban for adding the binding publishing to

Re: [Pulp-list] rpm distribution not deleted when deleting a repo

Distributions can be reused (and updated with a PATCH call versus a POST which creates a new one). Note for rc2 specifically, because of the breaking changes with rc2, you'll need to make any Distributions and Publications new with rc2. Hopefully this is helpful and not confusing. More questions

Re: [Pulp-list] Pulpcore RC2 is Available

The beta 11 release of pulp_file 0.0.1 for Pulp 3 is now available: https://pypi.org/project/pulp-file/0.0.1b11/ This release is compatible with pulpcore 3.0.0rc2. On Mon, May 20, 2019 at 3:11 PM Brian Bouterse wrote: > The pulpcore 3.0.0rc2 and pulpcore-plugin 0.1.0rc2 packages are availa

Re: [Pulp-list] Pulpcore RC2 is Available

The rc5 release of pulp_ansible 0.1.0rc5 for Pulp3 is now available: https://pypi.org/project/pulp-ansible/ It supports pulpcore 3.0.0rc2. On Tue, May 21, 2019 at 1:02 AM Simon Baatz wrote: > The beta 3 release of pulp_cookbook 0.0.4 for Pulp 3 is now > available: > >

[Pulp-list] Pulpcore RC2 is Available

The pulpcore 3.0.0rc2 and pulpcore-plugin 0.1.0rc2 packages are available on PyPI [0][1]. It includes many bugfixes, important usability improvements, and a few backwards incompatible changes. We encourage users to try RC2, through an RC2 compatible plugin on a non-production system. # Release

Re: [Pulp-list] Create and remove repo with ansible

We don't have one for Pulp3 yet, but we do want to make one. I created a stub issue here to start tracking that effort. https://pulp.plan.io/issues/4658 On Tue, Apr 9, 2019 at 10:58 AM Juan Cabrera wrote: > Thanks. > > I suppose this does not work with pup 3.x , isn't it ? > On 9/04/19 16:00,

Re: [Pulp-list] Anyone have a configuration dump/load tool for Pulp 2.x?

I don't have any existing tooling, but this sounds related to a migration idea that came up recently... For migration from Pulp2 -> Pulp3 specifically, I think having a Pulp2 feature that outputs a config of all Pulp2 repositories for example. Then the user could edit this config file which would

Re: [Pulp-list] [Pulp-dev] Documentation Systemd clarification?

gt; sincerely > > Juan > > > On 5/04/19 00:12, Brian Bouterse wrote: > > See the updated docs here for the systemd templates: > https://docs.pulpproject.org/en/3.0/nightly/installation/instructions.html#systemd > > On Tue, Apr 2, 2019 at 5:33 PM Brian Bouterse wrote:

Re: [Pulp-list] [Pulp-dev] Documentation Systemd clarification?

See the updated docs here for the systemd templates: https://docs.pulpproject.org/en/3.0/nightly/installation/instructions.html#systemd On Tue, Apr 2, 2019 at 5:33 PM Brian Bouterse wrote: > I updated the path on the docs as you identified. Also, we are considering > linking to the ansibl

Re: [Pulp-list] [Pulp-dev] Documentation Systemd clarification?

. Let us know if you run into more issues. Thanks! On Tue, Apr 2, 2019 at 12:01 PM Brian Bouterse wrote: > I moved this convo to pulp-list since it's focused on user usage of Pulp3 > versus the development of Pulp itself (on pulp-...@redhat.com). See some > answers to Pulp3 usage

Re: [Pulp-list] [Pulp-dev] Documentation Systemd clarification?

ib/systemd/system/pulp-worker@.service > I'll look more into this, but I wanted to get what I had out to the list. > Sincerely > > Juan > > On 1/04/19 23:13, Brian Bouterse wrote: > > I made a docs issue [0] and a PR to adjust the systemd settings this [1]. > Since dyn

Re: [Pulp-list] [Pulp-dev] Pulp 3.0 RC release

A new pulp-certguard has been released and is compatible with pulpcore 3.0.0rc1. pulp-certguard is an X.509 Certificate Based Content protection for Pulp3. This ensures only clients with valid certificates receive content from Pulp. It's compatible with various types of content including RPM,

[Pulp-list] What Pulp2 RPM sync or publish features do you most use?

I'm trying to get some feedback to inform pulp3 RPM development. If you used the RPM plugin for Pulp 2.y, what sync or publish features did you use most? These are features like "force-full" syncing, retain X versions of an rpm, sync or publish only specific types, e.g. "errata". If you can

Re: [Pulp-list] Pulp Community Demo - Dec 5th

Due to technical issues, this is moving to Thursday at 16:00 UTC. Sorry for the last minute change. On Tue, Dec 4, 2018 at 12:22 PM Brian Bouterse wrote: > On Wednesday, the Pulp community demo will be broadcast live via YouTube. > The tentative agenda is: > > * Pulp3 Lazy Sync, b

[Pulp-list] Pulp Community Demo - Dec 5th

On Wednesday, the Pulp community demo will be broadcast live via YouTube. The tentative agenda is: * Pulp3 Lazy Sync, bmbouter, 3.0 * Pulp3 Docker Sync and Publish, dkliban, 3.0 When: Dec 5th at 3pm UTC [0] Where: https://www.youtube.com/watch?v=IeY4lI8jG38 Interact: Chat during the event on the

Re: [Pulp-list] Pulp Community Demo - Nov 7th

]: https://pulpproject.org/2018/11/07/community-demo/ On Tue, Nov 6, 2018 at 8:03 PM Brian Bouterse wrote: > On Wednesday, the Pulp community demo will be broadcast live via YouTube. > The tentative agenda is: > > * Human-friendly specified fields for serialization, (dalley), 3.0

[Pulp-list] Pulp Community Demo - Nov 7th

On Wednesday, the Pulp community demo will be broadcast live via YouTube. The tentative agenda is: * Human-friendly specified fields for serialization, (dalley), 3.0 * Unified Pulp 3 Ansible Installer, (asmacdo), 3.0 * Pulplift demo to easily run Pulp3, (bmbouter), 3.0 * Stages API Performance

Re: [Pulp-list] Pulp Community Demo - September 19th

/UCI43Ffs4VPDv7awXvvBJfRQ [1]: https://pulpproject.org/2018/09/19/community-demo/ On Tue, Sep 18, 2018 at 7:08 PM Brian Bouterse wrote: > On Wednesday, the Pulp community demo will be broadcast live via YouTube. > The tentative agenda is: > > * pulp_rpm sync + publish demo for Pulp3 (davidda

  1   2   3   4   >