Until Pulp issue 9289 is resolved: Clone the https://github.com/pulp/pulp_file Git repo Change to the /pulp_file/pulp_manifest/ directory. $ cd /pulp_file/pulp_manifest/ Enter the following command: $ sudo python ./setup.py install

Of the pain points on this list: https://pulp.plan.io/issues/6658 [x] I expected some CLI as user interface, as I think that a big part of public for this tool is SysAdmin. Even API is a great interface, it's not comfortable for SysAdmin to manager repos (even more true we it needs to discover how it works) The lack of external doc, like tuto: How I mirror [ ] Centos [x] Debian with Pulp

Mel's suggestions based on nightly: https://pulp-installer.readthedocs.io/en/latest/quickstart/#storage Introduce this better: Where is the information about non S3 and Azure storage options? Can we first describe the "default" behavior? Add this section from Pulpcore documentation as an introduction.


Please put any ideas you might have here and +1 anything you would wear in public during the day in front of people who know you: Sports t-shirt/jersey Sports t-shirt sweat/moisture wicking: +1 https://www.sanmar.com/p/4532_HthrGrey https://www.sanmar.com/p/4134_HthrGrey Or maybe a polo style: +1 https://www.sanmar.com/p/4317_BlkWhite

In an on-premise environment, discovering and sharing Ansible content between different parts of your organization is a major problem. With the release of Ansible Galaxy_NG, you can take advantage of the following workflows on-premise: Enable multiple teams to produce Ansible collections within your organization Search for, discover, view, and use collections that already exist in your organization Mix-and-match your private collections with public collections from either galaxy.ansible.com or supported collections from cloud.redhat.com Add private Ansible collections to AWX The Ansible Galaxy_NG Workflow Using the Ansible Galaxy_NG web UI, you can upload collections to various namespaces. You can also identify collections that you want to synchronize from galaxy.ansible.com or cloud.redhat.com. All of these collections are browseable via the web UI. Once you select the collections you need, the web UI generates the command line copy-and-paste commands that clients can use to install on-premise hosted collections to various development machines.

Developing a user-focused Pulp community strategy What Pulp users in 2020 are saying about Pulp "Pulp is the only open source binary repo I see has a potential to beat every other paid binary repo out there. You have a long way to go but I am very happy to use Pulp." "So far the team has been doing a good job with the application I feel the workflow could be more intuitive for users" "When I told DevOps folks that I was working on installing Pulp, they reacted very negatively. It seems that Pulp 2 has a really bad reputation with those that were required to use Katello. They said that all issues with Katello were traced back to Pulp 2. Some kind of campaign might be required to change the perception of Pulp 3." What are the overall goals of a user-focused community strategy?

Last week, the Pulp 3 Debian plugin 2.6.1 was released. After eight beta versions, this is the first GA release! Let's take a look at the Debian plugin's main features: Ability to synchronize all or a subset of an upstream repository Support for the manual upload of files to a pulp_deb repository Add a public GPG key to verify upstream Release files Simple and structured publishing options Use a signing service to sign your simple and/or structured publications Verbatim publishing to recreate the synchronized subset of an upstream repository exactly

Over the coming months, the Pulp team will focus on the following areas. As with all plans, these are subject to change. Many of the items in this plan factor into Katello and Galaxy NG plans. Further updates will be announced on Pulp blog and mailing lists. If you have any questions or feedback, feel free to write to pulp-list@redhat.com Pulpcore Implementing Role Based Access Control (RBAC) Working towards making Pulp multi-user safe Working towards making Pulp FIPS-compliant Improving import/export functionality

The Pulp team is pleased to announce the release of the 0.3.0 version of the Pulp 2-to-3 Migration plugin. You can use this plugin to migrate content from Pulp 2 into Pulp 3. At the moment, the migration plugin covers the following scenarios: Pulp 2 ISO content can be migrated into Pulp 3 File. Pulp 2 Docker content can be migrated into Pulp 3 Container. Pulp 2 RPM content can be migrated into Pulp 3 RPM. This release is compatible with Pulpcore 3.6 and the following content plugins:

The Pulp team is pleased to announce the release of the Pulp Ansible 0.2.0 plugin. About the Pulp Ansible content plugin If you’re an Ansible user who does not want to host your private content on Ansible Galaxy, you can add the Pulp Ansible plugin to Pulp. You can then mirror the public Ansible content that you require and use Pulp as an on-premise platform to manage and distribute a scalable blend of public and private Ansible roles and collections across your organization. With the Pulp Ansible plugin, you can complete the following actions via the Pulp API. Ansible content includes both roles and collections: Mirror a subset of Ansible content on-premise Mirror all of Ansible Galaxy’s content on-premise Store private Ansible content on-premise