Re: [Pulp-list] Synchronize Git Repositories: Crazy?

[Randy Barlow]

Scott McCarty wrote:
> Randy,
> I FINALLY had a chance to file this as a user story. Holy cow, you guys 
> have 200 open stories :-)  So, I thought I was busy, but I have no idea how 
> you guys would ever have time to implement this ;-)

Hahaha, yeah we have a lot to do for sure. Thanks for the RFE!

-- 
Randy Barlow
irc:   bowlofeggs



signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Question on purging stale rpms

[Partha Aji]

Here is the scenario. 
I synced a repo from some feed which has packages A1, B1. 
Now the feed got updated to packages A2, B1. 
Now when I resync I need my repo to have A2, B1 (exact mirror). The default 
behaviour in pulp seems to be not touch local repo and hence it ends up having 
packages A1, A2, and B1. I know there is a way to override this and was trying 
to figure out the config option.
Looking at 
https://github.com/pulp/pulp_rpm/blob/master/plugins/pulp_rpm/plugins/importers/yum/purge.py#L18
 I notice 2 options "remove-missing" and "retain-old-count". 
1) Do you guys know which option is it.
2) Can I use this option as a sync override, or specify it in an importer 
config per repo.

Partha

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Synchronize Git Repositories: Crazy?

[Scott McCarty]

Randy,
I FINALLY had a chance to file this as a user story. Holy cow, you guys 
have 200 open stories :-)  So, I thought I was busy, but I have no idea how you 
guys would ever have time to implement this ;-)

Nick,
I added your idea of the Builder Image too :-)

[1]: https://pulp.plan.io/issues/1526

Best Regards
Scott M

Scott McCarty, RHCA
Technical Product Marketing: Containers
Email: smcca...@redhat.com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com

Containerizing? Why does the user space matter? http://red.ht/1Kl0mpx

- Original Message -
> From: "Randy Barlow" 
> To: pulp-list@redhat.com
> Sent: Thursday, September 3, 2015 2:11:39 PM
> Subject: Re: [Pulp-list] Synchronize Git Repositories: Crazy?
> 
> Scott McCarty wrote:
> > - Absolutely, is there a guide somewhere on how to start this off?
> 
> I don't believe we have any formal process documented for writing a
> story, so I'll write some high level stuff here:
> 
> 0) Use Redmine to file a new issue:
> https://pulp.plan.io/projects/pulp/issues/new
> 
> 1) Choose "Story" as the type.
> 
> 2) Try to word the title of the story with "As a user, I can do such
> and
> such" so that the story is focused on what problem the user wants to
> solve, not necessarily on the technical details on how to solve it.
> 
> 3) Use the body to describe the use case in detail.
> 
> 4) The comments can then be used by people to discuss possible
> solutions, to ask questions, or for conversation that further defines
> the user story. The description can be updated as people go if
> desired.
> 
> 5) Once the story seems to be "ready to be worked on" (and has a set
> of
> clear deliverables), there is a checkbox called "sprint candidate".
> Once
> this is checked, the team will look at it and decide whether the
> description is well defined. If it is, it will get marked as
> "groomed".
> 
> 6) Alternatively, you can lead the development effort yourself and
> not
> worry too much about the "sprint candidate"/"groomed" workflow, so
> long
> as the story seems to be well vetted. We accept pull requests so long
> as
> they meet our quality standards (and we will help you get to the
> expected quality standards during code review).
> 
> Does that help? Thanks!
> 
> 
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] Question on purging stale rpms

[Michael Hrivnak]

It sounds like you want to use "remove-missing", which will remove local
packages that are now missing from the remote repo.

However, if the remote feed actually now has A1, A2, and B1, but you don't
care about A1 anymore, then set retain-old-count to 0. That will cause pulp
to keep zero old versions of each package; at the end of the sync, it would
remove A1 from the local repo, because A1 is older than A2.

You can specify these in the importer's json config file, save them in the
importer's config, or specify them in the override config with every sync
call you make. Pick your favorite!

Michael

On Wed, Jan 13, 2016 at 5:39 PM, Partha Aji  wrote:

>
> Here is the scenario.
> I synced a repo from some feed which has packages A1, B1.
> Now the feed got updated to packages A2, B1.
> Now when I resync I need my repo to have A2, B1 (exact mirror). The
> default behaviour in pulp seems to be not touch local repo and hence it
> ends up having packages A1, A2, and B1. I know there is a way to override
> this and was trying to figure out the config option.
> Looking at
> https://github.com/pulp/pulp_rpm/blob/master/plugins/pulp_rpm/plugins/importers/yum/purge.py#L18
> I notice 2 options "remove-missing" and "retain-old-count".
> 1) Do you guys know which option is it.
> 2) Can I use this option as a sync override, or specify it in an importer
> config per repo.
>
> Partha
>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

Re: [Pulp-list] How does "--retain-old-count" work?

[Michael Hrivnak]

Lynn,

Thanks for asking. You are correct that this setting only works during sync.

Pulp is designed right now so that once content is in the system, it can be
copied around very quickly and cheaply. As such, we've avoided doing much
of anything during copy besides add references in the DB. However, that
puts the burden on you as the user to carefully choose which content to
move where. It could be valuable if pulp offered more helpful options on
copy. Other users have expressed interest in copy operations limiting on
version, gpg signature, uniqueness of some combination of attributes, etc.
As we think about pulp 3.x, we will keep those use cases in mind.

Feedback is appreciated, so feel free to tell us more about your use cases.

Michael

On Tue, Jan 12, 2016 at 10:37 PM, Lin Yuan  wrote:

> Hi,
>
> I am a bit puzzled with the option "--retain-old-count" from "pulp-admin
> rpm repo create --repo-id demo --retain-old-count 2" command.
>
> After I uploaded foo-1.0.0-1.el6.noarch.rpm, foo-1.1.0-1.el6.noarch.rpm,
> foo-1.2.0-1.el6.noarch.rpm,  and foo-1.3.0-1.el6.noarch.rpm to the demo
> repository and publish it, I can still see all 4 rpms from browser.
>
> So I wonder if this option only work with feed sync? Does it work with
> manual upload or copy?
>
> I am using pulp 2.7.1.
>
>
> Best Regards
> Lynn
>
> ___
> Pulp-list mailing list
> Pulp-list@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list
>
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

[Pulp-list] Pulp 2.8.0 beta 1 is available

[Dennis Kliban]

The first 2.8.0 beta is now available at it's usual location[0]. This release 
contains the following packages and their dependencies:

Pulp 2.8.0 beta
RPM plugin 2.8.0 beta
Puppet plugin 2.8.0 beta
OSTree plugin version 1.1.0 beta
Python plugin version 1.0.1
Docker plugin version 2.0.0 beta 
Crane version 2.0.0 beta

Along with new features, this release contains a significant code rewrite. We 
are aware of quite a few unresolved issues in this beta release, but we still 
wanted to provide our community with a snapshot of what is in the works. We 
hope that as we work on fixing all the known issues, users will report any new 
issues they encounter while using this build.

Some of the known issues that are worth highlighting:

  * Pulp can only run with SELinux in permissive mode
  * Nodes syncing is not working

  
Release notes can be found here [1-5]  
  
[0] https://repos.fedorapeople.org/pulp/pulp/beta/2.8/
[1] 
https://github.com/pulp/pulp/blob/master/docs/user-guide/release-notes/master.rst
[2] 
https://github.com/pulp/pulp_rpm/blob/master/docs/user-guide/release-notes/2.8.x.rst
[3] 
https://github.com/pulp/pulp_puppet/blob/master/docs/user-guide/release-notes/2.8.x.rst
[4] 
https://github.com/pulp/pulp_docker/blob/master/docs/user-guide/release-notes/1.2.x.rst
[5] 
https://github.com/pulp/pulp_ostree/blob/master/docs/user-guide/release-notes/1.1.x.rst

___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list