Re: [Pulp-dev] Removing pulp-smash from PyPI

2021-03-29 Thread Ina Panova
+1 Thank you!

On Mon, 29 Mar 2021, 18:24 David Davis,  wrote:

> I've heard back from most stakeholders that no one's using pulp-smash
> outside of the Pulp team. And I am not seeing any objections to removing it
> from PyPI.
>
> I plan to remove it from PyPI after April 5th unless anyone objects.
>
> Here are PRs to update projects:
>   - https://github.com/pulp/pulpcore/pull/1210
>   - https://github.com/pulp/pulp_file/pull/486
>   - https://github.com/pulp/pulp_container/pull/275
>   - https://github.com/pulp/pulp_deb/pull/257
>   - https://github.com/pulp/pulp_ansible/pull/549
>   - https://github.com/pulp/plugin_template/pull/359
>
> David
>
>
> On Fri, Mar 26, 2021 at 12:16 PM Pavel Picka  wrote:
>
>> I agree to remove it from PyPI and use only "source" if needed.
>>
>> On Fri, Mar 26, 2021 at 4:52 PM Brian Bouterse 
>> wrote:
>>
>>> I'm +1 to this plan and the removal of pulp-smash from PyPI.
>>>
>>> On Fri, Mar 26, 2021 at 11:26 AM David Davis 
>>> wrote:
>>>
 Yes, that's the plan. Sorry I didn't mention that in my email.

 David


 On Fri, Mar 26, 2021 at 11:23 AM Mike DePaulo 
 wrote:

> It's declared in many plugins' test dependencies without the git path,
> such as pulp_file/functest_requirements.txt
>
> I often install those as part of my installer development, and support
> for other teams.
>
> So I agree with this approach, but update the plugins too.
>
> -Mike
>
> On Fri, Mar 26, 2021 at 11:16 AM David Davis 
> wrote:
>
>> It recently came up that the pulp-smash release PyPI is badly out of
>> date. It's an extra burden to release it and it doesn't seem to have any
>> benefit. So instead we're considering using the git repo directly (see 
>> [0])
>> but I wanted to first check if that's a problem for anyone?
>>
>> [0] https://github.com/pulp/pulpcore/pull/1210
>>
>> David
>> ___
>> Pulp-dev mailing list
>> Pulp-dev@redhat.com
>> https://listman.redhat.com/mailman/listinfo/pulp-dev
>>
>
>
> --
>
> Mike DePaulo
>
> He / Him / His
>
> Service Reliability Engineer, Pulp
>
> Red Hat 
>
> IM: mikedep333
>
> GPG: 51745404
> 
>
 ___
 Pulp-dev mailing list
 Pulp-dev@redhat.com
 https://listman.redhat.com/mailman/listinfo/pulp-dev

>>> ___
>>> Pulp-dev mailing list
>>> Pulp-dev@redhat.com
>>> https://listman.redhat.com/mailman/listinfo/pulp-dev
>>>
>>
>>
>> --
>> Pavel Picka
>> Red Hat
>>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://listman.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev


Re: [Pulp-dev] How docker type repositories are getting synced in pulp3 w.r.t concurrency ?

2021-03-29 Thread Sayan Das
Hello Everyone,

I am not sure if my previous email was successfully delivered or not and
hence I am re-sending it.

I hope someone will be able to help me with some clarification there.


Thanks & Regards,

Sayan das

*T*echnical *S*upport *E*ngineer, RHCE

Red Hat India


Red Hat India Pvt. Ltd, Level-5, Tower-10, Cyber City

Magarpatta City Hadapsar, Pune-411013, Maharashtra, India.

say...@redhat.comM: +91-7890892756 IRC: Sayan



On Sat, Mar 27, 2021 at 12:17 AM Sayan Das  wrote:

> Hello All,
>
> I hope this email finds you all well.
>
> My name is Sayan and I work as a support engineer for the Red Hat
> Satellite 6 product. During a recent interaction with my colleague Ian
> Ballou, we came across a pulp2-vs-pulp3 question that we are looking for
> clarification on and It was suggested that this pulp-dev will be a really
> great place to get that clarification.
>
> Please allow me to explain the pulp 2 behavior.
>
> Some parameters to consider:
>
> Repo Type: Docker or Openshift repo [ Assuming it has 200 units to get
> downloaded ]
> Download Dir: /var/cache/pulp
> Data Dir: /var/lib/pulp/content/units/
> Download concurrency: 5
>
> Now,
>* Sync Started for the repo.
>* pulp downloaded 5 units in the "Download Dir" but never moved them in
> "Data Dir"
>* Once those first 5 units were downloaded, Pulp downloads the next 5
> units and the same cycle keeps on repeating untill all 200 units have been
> downloaded.
>* When all 200 units are downloaded, then the entire content will be
> moved from "Download Dir" to the respective location inside "Data Dir"
>
>
> For pulp 3,
>
> Download Dir: /var/lib/pulp/tmp
> Data Dir: /var/lib/pulp/media
> Download concurrency: 5 [ I heard it's 10 but let's assume it's 5 for now ]
>
>
> So the question is, Will pulp 3 behave the same as pulp 2, i.e. download
> the entire repository inside "Download Dir" by the batches of 5 units and
> then move the entire repository to "Data Dir" or the behavior is different
> i.e. after download 5 units in "Download Dir" the content will be moved to
> "Data Dir" and then the next 5 units will be downloaded?
>
> Please note, I have specifically mentioned that the repo is a
> Docker\Openshift type repo as we are concerned about only Docker\ISO\File
> type repos at this moment.
>
> Any clarification that can be provided on this will be really appreciated.
>
>
>
>
> Thanks & Regards,
>
> Sayan das
>
> *T*echnical *S*upport *E*ngineer, RHCE
>
> Red Hat India
> 
>
> Red Hat India Pvt. Ltd, Level-5, Tower-10, Cyber City
>
> Magarpatta City Hadapsar, Pune-411013, Maharashtra, India.
>
> say...@redhat.comM: +91-7890892756 IRC: Sayan
> 
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev