[Pulp-list] Pulp v3 Installation and testing
Hi All, I am not able to find a proper installation document for pulp v3. Using the current documentation at - https://docs.pulpproject.org/installation/instructions.html#ansible-installation-recommended I am not able to use REST APIs. My use case for using Pulp is: 1. Handle security patches for CentOS 2. Handle CentOS updates (7.3 --> 7.4) Can anybody point me to a proper documentation? Also I am not sure if 'pulp-admin' and 'pulp-consumer' exists in Pulp v3. Please clarify. My understanding is that all operations like: 1. Registering consumer 2. Creating repo 3. Syncing repo 4. Installing RPM package on a consumer 5. Updating a consumer Is all via REST API. Please confirm. Regards. Pradeep. S ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] Pulp 2.21.1 Beta 1 is available
Pulp 2.21.1 Beta 1 is now available, and can be downloaded from the 2.21 beta repositories: https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.21/ This release includes bugfixes for: Debian Support, Docker Support, Pulp, and RPM Support Upgrading = The Pulp 2.21 beta repository is included in the pulp repo files: https://repos.fedorapeople.org/repos/pulp/pulp/fedora-pulp.repo for Fedora https://repos.fedorapeople.org/repos/pulp/pulp/rhel-pulp.repo for RHEL 7 After enabling the pulp-beta repository, you'll want to follow the standard upgrade path with migrations: $ sudo systemctl stop httpd pulp_workers pulp_resource_manager pulp_celerybeat pulp_streamer goferd $ sudo yum upgrade $ sudo -u apache pulp-manage-db $ sudo systemctl start httpd pulp_workers pulp_resource_manager pulp_celerybeat pulp_streamer goferd The pulp_streamer and goferd services should be omitted if those services are not installed. Issues Addressed Debian Support 4345 Review behaviour when publishing empty repositories. 5170 As a user, I can specify --force-full on sync and it verifies existing content on disc Docker Support 4095 Can't import containers created with Buildah Pulp 2220 Copying units between repositories hits DocumentTooLarge: BSON document too large, if source repo contains > 345,000 units of same type 5512 Can't connect to remote mongodb when FIPS-enabled 5573 Publish won't create multiple checkecksummed copies of primary.xml, fileliststs.xml etc even when in fast-forward mode 5742 Pulp 3 can't sync when installed along side Pulp 2 RPM Support 5658 Copying modulemd_defaults over an uploaded unit fails: Not a directory 5578 rsync should use --skip-existing when creating remote directory 5659 Regression: publishing an empty ISO repo no longer publishes PULP_MANIFEST 5942 centos 8 appstream non-modular rpms are marked as modular 5951 yum_distributor wrongly skips publish after update of multi-repo errata 6096 After using the /associate endpoint, publish of the new repository fails 6151 associate-with-filter sometimes ends up with filtered-rpms in the destination Regards, Ina Panova Senior Software Engineer| Pulp| Red Hat Inc. "Do not go where the path may lead, go instead where there is no path and leave a trail." ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
[Pulp-list] pulpcore 3.2.0 and pulp_file 0.2.0 releases
pulpcore 3.2.0[0] and pulp_file 0.2.0[1] have been released. For a list of all changes, please check the changelogs for pulpcore[2] and pulp_file[3]. # Installation and Upgrade Users should use the 3.2.0 release of ansible-pulp installer[4] to install or upgrade their installations. This version of the installer will check compatibility of all installed plugins with pulpcore 3.2. The installer will abort if any plugin is incompatible. # Plugin API Plugin writers can see the plugin API changelog here ( https://docs.pulpproject.org/en/3.2.0/changes.html#plugin-api ). There was only one backwards incompatible change[5], and in keeping with the recommended strategy to pin plugins to a 3.y version of pulpcore, plugins should release compatibility releases with 3.2 as soon as they can. We recommend using "pulpcore>=3.0,<3.3". The installer also has a backwards incompatible change in 3.2.0 where it no longer attempts to handle custom URLs for plugins automatically. If your plugin uses URLs outside of /pulp/api/v3/ or /pulp/content/ you will need to add a snippet. See these docs[6] for more. [0]: https://pypi.org/project/pulpcore/3.2.0/ [1]: https://pypi.org/project/pulp-file/0.2.0/ [2]: https://docs.pulpproject.org/changes.html#id1 [3]: https://pulp-file.readthedocs.io/en/0.2.0/changes.html#id1 [4]: https://github.com/pulp/ansible-pulp/releases/tag/3.2.0 [5]: https://github.com/pulp/pulpcore/pull/555 [6]: https://pulp.plan.io/issues/6057 David ___ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
