Re: [Pulp-list] Error: Invalid properties: ['distributor_type_id']

, and it looks like it hasn't been updated in a while. If you are interested in getting it working with current pulp, your best bet is probably to contact the original author and see how you might be able to help out. Best of luck, Michael On Fri, Aug 21, 2015 at 2:35 PM, Mihai Ibanescu

Re: [Pulp-list] Error: Invalid properties: ['distributor_type_id']

. Something else needs to happen, but at this point I don't know which log files to check. On Thu, Aug 20, 2015 at 5:41 PM, Mihai Ibanescu mihai.ibane...@gmail.com wrote: Hi. I've been trying to make progress on installing pulp_win, and I am not sure if there's a problem with the plugin itself

Re: [Pulp-list] Error: Invalid properties: ['distributor_type_id']

... and following up again, this time the problem was client-side (i.e. admin extension side): it was passing distributor_type instead of distributor_type_id On Fri, Aug 21, 2015 at 12:58 PM, Mihai Ibanescu mihai.ibane...@gmail.com wrote: Following up on my own e-mail: Progress report: I

[Pulp-list] Error: Invalid properties: ['distributor_type_id']

Hi. I've been trying to make progress on installing pulp_win, and I am not sure if there's a problem with the plugin itself, or I forgot to restart something. After building the rpms (sources at https://github.com/lsjostro/pulp_win), I installed the server and the admin parts on separate

Re: [Pulp-list] Pulp_Docker Layers

Not having dealt with pulp-docker, but having implemented docker v1 and v2 image uploads: It will definitely break v1 It may break v2, not sure yet It may break any downstream layers that rely on the content in that layer. In other words it is most likely not a good idea. On September 2, 2015,

[Pulp-list] Customer stories

Hi, Can anyone on the list share their story around using pulp? I would really love to use that as part of the decision to use pulp in a project. The things that might be interesting are: high number of (distributed) clients, scaled-out deployment (mirrored pulp deployments), HA-style

Re: [Pulp-list] Colons vs equals in conf.files

Given that pulp is written in python, and it uses ConfigParser for its config files, either : or = will work just fine as separator. https://docs.python.org/2/library/configparser.html Mihai On Mon, Dec 7, 2015 at 12:00 PM, Kodiak Firesmith wrote: > Hey Pulp Folks, >

Re: [Pulp-list] Removing content from repo via API

Try association for filter, instead of unit. Just ran into this situation in the past week. ▶ Show quoted text On Dec 13, 2015 05:05, "Trey Dockendorf" wrote: > I'm attempting to cleanup some of my repositories via API, and am finding > I can successfully remove everything

[Pulp-list] Snapshotting support for a pulp repo

Hi, I am investigating how I can implement snapshotting support for Pulp repos (not with a plugin, at least not for now, but as a client). Essentially, I need to make a copy of the pulp repo after each "logical write" operation (a set of updates/copies from other repos, and before the publish

Re: [Pulp-list] 2.8 Tasks Stuck at Waiting

I have a similar problem on 2.7.1 with rabbitmq. Occasionally a task will get "lost": pulp-admin tasks details --task-id 622041ac-e9e4-4a15-bd7c-7c98a17782e0 +--+ Task Details

Re: [Pulp-list] Implementing Support for New Types - Directory Loading

Did you run pulp-manage-db? sudo -u apache pulp-manage-db On Fri, May 20, 2016 at 11:03 AM, Jay Medrano wrote: > Hello folks, > > > > I’m trying to add support for a new type >

Re: [Pulp-list] dropping el6 builds of Pulp

I would love for all the pulp components to be easily installable via pip install. That will probably require moving a lot of the data-manipulation that is happening in the rpm spec files into setup.py. Also, I am not sure how well pulp would handle the new paths for things like the json file

Re: [Pulp-list] Deprecating Pulp Nodes

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

Re: [Pulp-list] Changing working_directory and/or reducing disk utilization during sync

This may be unrelated to the sync problem - but do you have the export distributor configured on that repo? It doesn't affect syncing at all, but there is a publish operation at the end of the sync. The export distributor tries hard to burn all your CPU while running mkisofs (for my usecase we

Re: [Pulp-list] Can pulp sign repo metadata?

What we use internally for signing all sorts of things (including invoking the repository signature for Debian that Brian is referring to): https://github.com/sassoftware/relic It was released to the open-source community a few weeks ago. On Mon, Jul 17, 2017 at 4:32 PM, Brian Bouterse

Re: [Pulp-list] do you use global importer settings?

The Debian plugin uses that to configure repository metadata signing. It is handy to not have to define it on a per-repo basis. I can also see how it might be useful for the Docker plugin, which (I believe) allows you to redirect the actual downloading of the layers to a different system. Again,

Re: [Pulp-list] Old python2-debpkgr package causing debian / ubuntu not to synchronize successfully

Hi, I have made debpkgr 1.0.5 available in pypi. Mihai On Fri, Feb 9, 2018 at 7:19 AM, Patrick Creech wrote: > On Fri, 2018-02-09 at 10:30 +, Sebastian Sonne wrote: > > Hello everyone, > > > > ever since the stable release of 2.15, I’ve tried to synchronize debian, >

Re: [Pulp-list] Why isn't my distributor working?

James, Are you triggering the publish via the REST API, or via the pulp-admin cli? Because I think pulp-admin will only call one distributor, not all that are configured. Which brings me to the next question: Did you add the distributor to the repo you are trying to publish? I didn't have the

Re: [Pulp-list] Do you remove docker content from the repositories?

The expectations are fine. I was point out on #pulp-docker just today that the pulp2 implementation is excruciatingly slow (as in 40 seconds to remove a single manifest) for large enough repositories. So as long as the implementation is avoiding complicated database queries in favor of maybe

Re: [Pulp-list] Do you remove docker content from the repositories?

Replies inline. On Mon, Jul 22, 2019 at 6:54 AM Simon Baatz wrote: > On Fri, Jul 19, 2019 at 01:13:20PM +0200, Ina Panova wrote: > Btw. we have code in our automation to explicitly address this case, > i.e. we filter out manifest digests when the manifest digests are > referenced by manifest