date:20210519

[Pulp-dev] Pulp Certguard 1.3.0 is Generally Available

2021-05-19 Thread Grant Gainey

pulp-certguard 1.3.0 has been released. It is compatible with pulpcore
versions 3.10 through future version 3.13.

This is only a compatibility release.

PyPi: https://pypi.org/project/pulp-certguard/1.3.0/
Docs: https://docs.pulpproject.org/pulp_certguard/
Python bindings: https://pypi.org/project/pulp-certguard-client/1.3.0/
Ruby: https://rubygems.org/gems/pulp_certguard_client/versions/1.3.0/

Enjoy!

G
-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Katello/Pulp3 Integration meeting

2021-05-19 Thread Grant Gainey

May 19, 2021

Overview

   -

   Katello Schedule
   -

  4.1 branching ~May 2021
  -

 pulpcore 3.11 (or newer)
 -

  4.2 branching ~August 2021
  -

 Pulpcore 3.13
 -

  4.3 branching ~Nov 2021

Pulp

   -

   Pulpcore
   -

  3.13 now scheduled for 25-May
  -

 Dalley is release-nanny
 -

  3.11.2 in-progress
  -

 4 requested backports
 -

 Requires django-2.2.23, pins click to 7.1.2
 -

 Is there work needed RE cleaning up media-dirs? Let bmbouter know!
 -

  Logging suggestion/concern
  -

 https://listman.redhat.com/archives/pulp-dev/2021-May/msg00052.html
 -

 Already an existing issue RE correlation-id-log-chattiness
 -

  Feedback needed https://pulp.plan.io/issues/8459 reclaim disk space
  story
  -

   RPM
   -

  3.11 is released
  -

 Adds support for modularity changes (static_context)
 -

 Last Y release compatible with pulpcore < 3.12
 -

 Consider upgrading pulp_rpm in Katello 3.18.z
 -

  3.12 should be out this week
  -

 Auto-publish support
 -

 ULN (Oracle) support
 -

  Repodata mirroring is close to completion, will be released in
  core-3.13
  -

   Migration
   -

   Ansible
   -

  0.8.0 will be released for pulpcore 3.13 compatibility
  -

 Add dependency syncing flag on CollectionRemote sync_dependencies
 -

 Now has label support
 -

   Pulp Container
   -

  Upcoming 2.5.3 and compatibility release 2.6.0 with core-3.13
  -

   Pulp CLI
   -

  0.9.0 released
  
  -

  Pins click to 7.1.2
  -

  Adds --dry-run flag
  -

   Pulp-certguard
   -

  Requests from Eric RE chained-CAs
  -

 we’re using the wrong CA into certguard
 -

 Would be nice to pass a bundle to certguard and have it Do The
 Right Thing
 -

 Issue filed - https://pulp.plan.io/issues/8783
 -

  Compatibility-release coming out #soon
  -

   Release-automation-improvements happening
   -

   Tasking-system-regression in Pulp2
   -

  solved
  -

   Discussion around odd Pulp3-tasking-weirdness
   -

  if/when encountered locally, hop into #pulp-dev and let us know!
  -

   Should Pulp2 discussions/issues come here?
   -

  When wider comms needed, probably a good place for it


Katello

   -

   Working on upgrading to pulp-rpm 3.11
   -

  Nightly to start
  -

  If All Goes Well, will look at release-cadence for 3.18/4.0
  -

   Ryan our intern started, will be working on ‘Generic content’ and python
   content support
   -

   Katello-4.2 will prob be compatible with core-3.13


QE

   -

   latest-z-release migration & bz testing is done
   -

   Start looking at next y-release features and test pre-snap


G
-- 
Grant Gainey
Principal Software Engineer, Red Hat System Management Engineering
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Pulp Installers team meeting minutes 2021-05-19

2021-05-19 Thread Mike DePaulo

## May 19 Agenda
* https://pulp.plan.io/issues/8679
* Mike to create a "triaged but unassigned" query, rather than just
listing this in the meeting outline
* vagrant-sshfs 1.3.6 (rpm in fedora testing) enables CentoS 8.3 / 8-stream
"powertools" but not 8.2 "PowerTools"
* Updates images?
* regular:
* 8.3 available:
https://cloud.centos.org/centos/8/x86_64/images/
* or switch to vagrant's "generic" project images
* FIPS: We'll rebuild https://github.com/mikedep333/fips-box-builder
* Stream is working anyway, so maybe this PR isn't necessary?
* Probably isn't breaking anything, since the old version works with
CentOS Stream
* Agreed: Mike to update images at his leisure, but do not worry about
breakage

-- 

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

Re: [Pulp-dev] Docs day revamp

2021-05-19 Thread Robin Chan

I went ahead and saved it:
https://pulp.plan.io/issues?query_id=174
And should show up in the named queries on the right hand side
And I'm seeing 16 items now.

Robin Chan

She/Her/Hers

Satellite Software Engineering Manager - Pulp

Asian Network Co-Chair

Red Hat 

IRC: rchan

Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.
 [image:
https://source.redhat.com/communitiesatredhat/diversity_and_inclusion/asian_network]

May is Asian Pacific American Heritage Month.

We
recognize and celebrate the contributions of Asians and Pacific Islanders
to American society and culture.


On Wed, May 19, 2021 at 8:18 AM David Davis  wrote:

> Awesome, thanks for organizing this and putting together a query.
>
> David
>
>
> On Tue, May 18, 2021 at 11:54 AM Ina Panova  wrote:
>
>> The Pulpcore team met today and went a bit through the docs backlog.
>>
>> Here is the query with the list of  docs issues we are going to focus
>> tomorrow May 19 https://tinyurl.com/ymctcr32
>>
>> 
>> 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 Wed, May 5, 2021 at 2:05 PM Ina Panova  wrote:
>>
>>> I have marked May 19th in the outage calendar as Pulp Docs Day.
>>>
>>> 
>>> 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 Thu, Apr 29, 2021 at 12:54 PM David Davis 
>>> wrote:
>>>
 Sounds good to me. Thank you for organizing this.

 David


 On Thu, Apr 29, 2021 at 5:47 AM Ina Panova  wrote:

> Hi everyone,
>
> Historically we have had Docs Day before a release so we can get some
> more docs PRs in. But this did not work out well for us because of all the
> amount of work and commitments we had to fulfill just before the release
> date. Our focus was somewhere else which is understandable.
>
> There is a new suggestion to organize Docs Day that would not be
> aligned to any release date. Folks would feel less stressed and have more
> time to actually prioritize docs issues.
>
> Currently there are 73 doc issues spread across Pulp in the plan.io
> [0]
> And only 2 doc issues marked for the Q2 2021.
>
> I am suggesting each mini team, in preparation for the Docs Day to
> take an action item and go through the backlog and mark issues for the Q2
> 2021.
> Projects that are moved to github issues can apply an appropriate
> label.
>
> The proposed date for the next iteration of Docs Day would be May 19.
> By that time we should be over a pulpcore 3.13 release and the temperature
> should be relatively low.
>
> Suggestions are welcome.
>
> [0] https://tinyurl.com/r492c8s
> [1] https://tinyurl.com/ymctcr32
>
> 
> 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."
> ___
> 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
>>
> ___
> 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] Docs day revamp

2021-05-19 Thread David Davis

Awesome, thanks for organizing this and putting together a query.

David

On Tue, May 18, 2021 at 11:54 AM Ina Panova  wrote:

> The Pulpcore team met today and went a bit through the docs backlog.
>
> Here is the query with the list of  docs issues we are going to focus
> tomorrow May 19 https://tinyurl.com/ymctcr32
>
> 
> 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 Wed, May 5, 2021 at 2:05 PM Ina Panova  wrote:
>
>> I have marked May 19th in the outage calendar as Pulp Docs Day.
>>
>> 
>> 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 Thu, Apr 29, 2021 at 12:54 PM David Davis 
>> wrote:
>>
>>> Sounds good to me. Thank you for organizing this.
>>>
>>> David
>>>
>>>
>>> On Thu, Apr 29, 2021 at 5:47 AM Ina Panova  wrote:
>>>
 Hi everyone,

 Historically we have had Docs Day before a release so we can get some
 more docs PRs in. But this did not work out well for us because of all the
 amount of work and commitments we had to fulfill just before the release
 date. Our focus was somewhere else which is understandable.

 There is a new suggestion to organize Docs Day that would not be
 aligned to any release date. Folks would feel less stressed and have more
 time to actually prioritize docs issues.

 Currently there are 73 doc issues spread across Pulp in the plan.io [0]
 And only 2 doc issues marked for the Q2 2021.

 I am suggesting each mini team, in preparation for the Docs Day to take
 an action item and go through the backlog and mark issues for the Q2 2021.
 Projects that are moved to github issues can apply an appropriate label.

 The proposed date for the next iteration of Docs Day would be May 19.
 By that time we should be over a pulpcore 3.13 release and the temperature
 should be relatively low.

 Suggestions are welcome.

 [0] https://tinyurl.com/r492c8s
 [1] https://tinyurl.com/ymctcr32

 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."
 ___
 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
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://listman.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Feedback Wanted, Upcoming Changes in Pulp Python

2021-05-19 Thread Matthias Dellweg

Just one thought:
I assume $PULP_BASE_ADDR is the part without "pulp/api/v3/". So why should
you include the "pulp_python" segment? You could just host it as e.g. "
http://localhost/pypi/foo/simple;. The interfaces provided there should not
be in any way specific to pulp_anything.

On Tue, May 18, 2021 at 11:44 PM Gerrod Ubben  wrote:

> Hey everyone,
>
> I am currently working on the long-awaited Twine upload support [0] for
> pulp_python. To add this functionality a new upload endpoint is needed.
> Since this new endpoint will need to be able to accept POST requests I plan
> to make the Python endpoints apart of the Pulp API.
>
> Proposed change: Have Python endpoints available at
> "/pulp_python/pypi/{base_path}/"
> API Current Location New Location Description
> simple $PULP_CONTENT_ADDR/pulp/content/{base_path}/simple/
> $PULP_BASE_ADDR/pulp_python/pypi/{base_path}/simple/ Used for installing
> packages
> pypi $PULP_CONTENT_ADDR/pulp/content/{base_path}/pypi/
> $PULP_BASE_ADDR/pulp_python/pypi/{base_path}/pypi/ Used for syncing
> repositories
> upload
> $PULP_BASE_ADDR/pulp_python/pypi/{base_path}/legacy/
> **$PULP_BASE_ADDR/pulp_python/pypi/{base_path}/simple/* Used for
> uploading packages
>
> The current Python endpoints will still be available at their present
> locations (and will be used as the backbone for the new locations) and the
> new upload endpoint will be available at '/legacy/' since the default PyPI
> endpoint Twine uses is 'https://upload.pypi.org/legacy/'. Pip stores its
> index URLs in a 'pip.conf' file [1]  and Twine stores its index URLs in the
> '.pypirc' file [2], so to have an easy setup across all Python tools I am
> thinking of also having the upload functionality available at the simple
> URL. This way one URL can be used for the Pulp Python index across all the
> Python tooling.
>
> An example workflow with these new changes:
>
>> pulp python repository create --name foo
>> pulp python distribution create --name foo --base-path foo --repository
>> foo
>> export PULP_PYTHON_INDEX=$PULP_BASE_ADDR/pulp_python/pypi/foo/simple/
>> twine upload --repository-url $PULP_PYTHON_INDEX dist/* --skip-existing
>> pip install -i $PULP_PYTHON_INDEX pulpcore
>>
>
> Do these changes concern anyone? Would a different name for the upload
> endpoint be preferred? Should the simple endpoint also support uploading
> packages? I plan on having this feature fully complete and ready for review
> by the end of the week, May 21st. Any feedback before then would be
> appreciated.
>
> [0] https://github.com/pulp/pulp_python/pull/367
> [1] https://pip.pypa.io/en/stable/user_guide/#configuration
> [2] https://packaging.python.org/specifications/pypirc/
>
> Thanks,
> Gerrod
> ___
> 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] Making pulp logging more configurable

2021-05-19 Thread Matthias Dellweg

Hi,
my thoughts:
Using syslog facilities maybe with [0] should integrate nicely with systemd
logging, however i do not know how well they integrate with s6
(oci-images). So the easiest way might be to get the systemd-unit of all
services to redirect stdout and stderr to syslog.
Otherwise we probably need an option whether to log to syslog (for sys V /
systemd installations) or stdout (for foreground / container operations).
  Matthias

[0] https://docs.python.org/3/library/logging.handlers.html#sysloghandler

On Tue, May 18, 2021 at 5:56 PM Tanya Tereshchenko 
wrote:

> Hi,
>
> I'd like to bring to your attention a suggestion [0] (based on a BZ [1])
> to categorize Pulp logs differently and have an ability to write them to a
> different place.
> Different users might want to do it differently, so I read it as an ask to
> make logging more configurable.
>
> It might also be a good opportunity to take a look at how friendly our
> docs and configuration are with regards to logging in general.
> FWIW, I found only this note [2] in the docs which mentions django logging
> and defers to the django docs.
>
> Please share any thoughts, concerns or ideas directly on the issue [0].
>
> Thank you,
> Tanya
>
> [0] https://pulp.plan.io/issues/8773
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1961508
> [2] https://docs.pulpproject.org/pulpcore/settings.html#logging
> ___
> 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

[Pulp-dev] Pulp Certguard 1.3.0 is Generally Available

[Pulp-dev] Katello/Pulp3 Integration meeting

[Pulp-dev] Pulp Installers team meeting minutes 2021-05-19

Re: [Pulp-dev] Docs day revamp

Re: [Pulp-dev] Docs day revamp

Re: [Pulp-dev] Feedback Wanted, Upcoming Changes in Pulp Python

Re: [Pulp-dev] Making pulp logging more configurable

7 matches

Site Navigation

Mail list logo

Footer information