?Thanks!

One thing I forgot to mention is that we would like to use LDAP for 
authentication, but if Pulp uses Django authentication, it should be possible 
to use django-auth-ldap.


I'll let you know if I run into any issues. Thanks again!


Joey Dumont

Technical Advisor, Knowledge, Information, and Technology Services
National Research Council Canada / Governement of Canada
[email protected]<mailto:[email protected]> / Tel: 
613-990-8152 / Cell: 438-340-7436

Conseiller technique, Services du savoir, de l'information et de la technologie
Conseil national de recherches Canada / Gouvernement du Canada
[email protected]<mailto:[email protected]> / Tél.: 
613-990-8152 / Tél. cell.: 438-340-7436
________________________________
From: Brian Bouterse <[email protected]>
Sent: 12 September 2019 12:49
To: Kodiak Firesmith
Cc: Dumont, Joey; [email protected]
Subject: 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 and we can try to get you on the right 
track.

Thanks for asking!
-Brian

On Thu, Sep 12, 2019 at 10:43 AM Kodiak Firesmith 
<[email protected]<mailto:[email protected]>> wrote:
Hi Joey,
My point of view comes from being a long term end user of Pulp 2x only (not a 
developer, much less a Pulp dev, FWIW):

Despite Pulp 2x being great, starting fresh on a tech evaluation, I'd 100% pick 
Pulp 3.  Because:
1.  Pulp 3x/PulpCore is the next long term support code base, so it's the 
branch with a long lifespan out in front of if within Satellite 6.
2.  Pulp 2x was (AFAICT) the branch where the vast majority of lessons were 
learned throughout the course of the project, so it might carry an amount of 
technical debt common with such ongoing lessons learned.
3.  Pulp 3x is more than an evolution of Pulp 2x, it's a completely new 
codebase that uses Django rather than homebrew.  Adopting 3x from the outset 
will save you a potentially difficult migration in the future.

Hope this helps, and I'm sure the core devs can hop in and correct me on any 
mistakes in my reasoning.

 - Kodiak, a very happy Pulp 2x user

On Thu, Sep 12, 2019 at 10:20 AM Dumont, Joey 
<[email protected]<mailto:[email protected]>> wrote:

?Hi,


My group woud like to assess Pulp to see if it fits our needs. Would you 
recommend installing v3 over v2?


We need to mirror python packages, RPM repos, and spin up a private Docker 
registry.


Thanks!


Joey Dumont

Technical Advisor, Knowledge, Information, and Technology Services
National Research Council Canada / Governement of Canada
[email protected]<mailto:[email protected]> / Tel: 
613-990-8152 / Cell: 438-340-7436

Conseiller technique, Services du savoir, de l'information et de la technologie
Conseil national de recherches Canada / Gouvernement du Canada
[email protected]<mailto:[email protected]> / Tél.: 
613-990-8152 / Tél. cell.: 438-340-7436
_______________________________________________
Pulp-list mailing list
[email protected]<mailto:[email protected]>
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected]<mailto:[email protected]>
https://www.redhat.com/mailman/listinfo/pulp-list
_______________________________________________
Pulp-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/pulp-list

Reply via email to