Hello Ina,
Thank you for the explanation. That makes perfect sense but still remains a
concern for us if the same flow will be happening in pulp3 as well in case
of Docker or ISO type repos.
Customers are always concerned about disk space and this situation might
lead to a disk space unavailabili
Recently the release workflow was updated to use a manual trigger instead
of being triggered by a new tag[0]. This should allow us to rerun the
release workflow anytime there's a failure.
Once you pick up this change via plugin_template, you'll need to tweak your
release process. If your plugin ha
It looks like everyone on the team has voted. The week of September 13-17
seems to be the most popular week. Let's try to aim for some time that
week. September 20-25 can be a possible backup week if the week of
September 13 doesn't work out for some reason.
I'll try to get the ball rolling in the
# March 30, 2021
## Previous AIs
* [bmbouter] to close https://github.com/pulp/pulpcore/pull/1122 based on
the recent convo at pulp_ansible meeting
* [ttereshc] to review https://github.com/pulp/pulpcore/pull/1194
* Done, merged
## Topics
* another go/no-go meeting? thursday
* MasterModel dis
Regards,
Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Tue, Mar 30, 2021 at 10:12 AM Sayan Das wrote:
> Hello Matthias,
>
> Thanks for your response on this one.
>
> By this,
> ~~
When is the next meeting?
David
On Tue, Mar 23, 2021 at 11:22 AM Ina Panova wrote:
> Here's the tracker for the pulpcore 3.12.0 release
> https://pulp.plan.io/issues/8437
> The tentative GA date is April 6th.
>
> The first go/no-go meeting happened today and so far we are on track.
>
> --
We need to look into fixing this bug https://pulp.plan.io/issues/8295 to
match the behaviour you have described Matthias.
Regards,
Ina Panova
Senior Software Engineer| Pulp| Red Hat Inc.
"Do not go where the path may lead,
go instead where there is no path and leave a trail."
On Tue
On Tue, Mar 30, 2021 at 10:06 AM Sayan Das wrote:
> Hello Matthias,
>
> Thanks for your response on this one.
>
> By this,
> ~~
> Since those stages use python async and asyncio this means, there will be
> 5 parallel downloads (as long as enough requests flow by that stage). Once
> an artifact is
Hello Matthias,
Thanks for your response on this one.
By this,
~~
Since those stages use python async and asyncio this means, there will be 5
parallel downloads (as long as enough requests flow by that stage). Once an
artifact is downloaded, the next stage will transfer it to the final
storage lo
I am not quite sure, i understand the right notion of the question, but
i'll try to give my view of it.
Pulp 3 has a special asynchronous sync pipeline. That means on synching a
remote repository (regardless of it's type) there is a pipeline with so
called stages. The first stage is supposed to fet
10 matches
Mail list logo
