Re: [Pulp-dev] Naming/Tagging-Schema for container images

2020-05-14 Thread Mike DePaulo 
On Thu, May 14, 2020 at 12:54 PM Matthias Dellweg 
wrote:

> We have recently started a new repository calles pulp-oci-images that
> should emit according to its name OCI compatible images with pulp
> installed.
> In the first go, this includes the single-container promoted though
> this blog post [0].
> Soon to be added is the base container image that shall speed up our CI
> [1].
> In the future, i envision a similar single-container solution based on
> centos instead of fedora,
> as well as ci base images based on centos having python3.6 installed.
> Does anyone think, we even need different ci-images for pulp release
> branches?
>

When you say "ci images", you mean images meant for user consumption? Or
images only used in CI testing?

>
> The big question now is: How are we going to name and tag those images?
>
> The one from [0] is called "pulp/pulp-fedora31:latest".
> We could go with that and add names like:
> - "pulp/pulp-centos8:3.2"
>   installation of core version 3.2 with all compatible plugins on centos8
> - "pulp/pulp-ci-fedora32:latest"
> - "pulp/pulp-ci-centos8:latest"
>

Remember that our current images like "
https://quay.io/repository/pulp/pulp-ci-f31; are only used for CI testing
of upgrades. The description states:
"Images of Pulp on Fedora 31, for CI testing of ansible-pulp performing
upgrades."
In fact, they are built via ansible molecule.

-Mike

>
> BTW, the ci-base images can be built by using the same Conteinerfile
> interrupted early.
> (with --target in a multistage build)
>
> What do you think?
>
> [0] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
> [1]
> https://github.com/pulp/pulpcore/blob/master/.travis/Containerfile.ci_base
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.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://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] RPM plugin meeting notes

2020-05-14 Thread Tatiana Tereshchenko 
Pulp 3:

   -

   https://pulp.plan.io/issues/6699
   -

  Core change
  -

  bmbouter to put a complete proposal
  -

   Release 3.3.1 is out, 3.3.2 is planned
   -

   Features
   -

  Estimate for mirroring metadata https://pulp.plan.io/issues/6353
  -

 Relative_path needs to be addressed to do this
 -

 Somewhere around 1-3 staff months/2 months.
 -

  Remaining features for Katello 4.0
  https://pulp.plan.io/projects/pulp_rpm/issues?query_id=155
  -

 File task to skip drpms during sync
 -

 Daniel email amatej w/r to the drpm library support
 -

   Tests
   -

  Coverage
  -

 Hook and markdown form in WIP https://pulp.plan.io/issues/6706
 - RHEL repos
  -

 Users reporting problems only seen when consuming RHEL-CDN repos
 -

 Add debug-cert to secrets, have a nightly test against RHEL
 -

 Needs a test-specific/pulp-bot-owned cert-ticket opened
 -

 ttereshc takes AI to write up issue
 -

 dkliban takes AI to write up cert-getting ticket
 -

  Upgrade tests
  -

 Pulp_rpm_prerequisites CI tests upgrade, but it not test database
 migration (as it does not have data)
 -

 https://hackmd.io/Bz6cLGRCSMmnCLDvhnBWtg?both
 -

 Have upgrade tests with data in the db
 -

 Potentially run in CI for https://github.com/pulp/pulp-oci-images/
 -

 AI to write a task
 -

  SSL cert test https://pulp.plan.io/issues/6735
  -

 Needs “RHEL repos” above, to really have tests
 -

   Docs
   -

  RPM copy API documentation PR:
  https://github.com/pulp/pulp_rpm/pull/1706
  -

  REST API docs are out of date, don’t forget to push fresh api.json if
  you make any changes affecting it
  -

 (dalley) I’m doing this in the copy docs PR
 -

 (david) I am never going to remember to do this. Can we add
 https://pulp.plan.io/issues/5541 to next sprint?
 -

Discuss at open floor
-

   Priorities


Open PRs:

   -

   https://github.com/pulp/pulp_rpm/pulls


Triage:

   -

   Un-triaged bugs https://pulp.plan.io/projects/pulp_rpm/issues?query_id=30
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Re: [Pulp-dev] Pulp Certguard Overview Next Week and @ggainey Joining certguard Mini Team

2020-05-14 Thread David Davis 
*cheers wildly*

David


On Thu, May 14, 2020 at 12:10 PM Brian Bouterse  wrote:

> tl;dr @ggainey is joining the pulp-certguard mini team, making him and I
> the mini team. Also, I'm hosting an open-and-recorded overview of
> pulp-certguard's features, code, test, and docs next week (details below).
>
> ## ggainey joining mini team
>
> Currently I'm the only person who is on the pulp-certguard mini team and
> that's a problem in terms of developer availability when I'm out of the
> office, and it's a bit stressful to be the only person on it.
>
> @ggainey has graciously accepted my invite to join the mini team. Thank
> you Grant!
>
> ## Pulp-certguard Tour: Wed, May 20th
>
> To onboard ggainey, and share info broadly, I've scheduled an overview of
> pulp-certguard's features, code, docs, and tests. With pulp-certguard
> nearing its feature completion state this week, this is a good time to do
> it. It will be recorded, posted to the YouTube channel, and a link sent
> back to this thread afterwards.
>
> Wed, May 20th 9:15 - 10am EDT
> Join with Google Meet:  meet.google.com/gse-zqnm-ptk
> Join by phone:  ‪+1 510-766-1775‬ PIN: ‪199 882 976‬#
>
> Thank you!
> Brian
>
> ___
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

[Pulp-dev] Naming/Tagging-Schema for container images

2020-05-14 Thread Matthias Dellweg 
We have recently started a new repository calles pulp-oci-images that
should emit according to its name OCI compatible images with pulp
installed.
In the first go, this includes the single-container promoted though
this blog post [0].
Soon to be added is the base container image that shall speed up our CI [1].
In the future, i envision a similar single-container solution based on
centos instead of fedora,
as well as ci base images based on centos having python3.6 installed.
Does anyone think, we even need different ci-images for pulp release branches?

The big question now is: How are we going to name and tag those images?

The one from [0] is called "pulp/pulp-fedora31:latest".
We could go with that and add names like:
- "pulp/pulp-centos8:3.2"
  installation of core version 3.2 with all compatible plugins on centos8
- "pulp/pulp-ci-fedora32:latest"
- "pulp/pulp-ci-centos8:latest"

BTW, the ci-base images can be built by using the same Conteinerfile
interrupted early.
(with --target in a multistage build)

What do you think?

[0] https://pulpproject.org/2020/03/15/pulp-fedora31-single-container/
[1] https://github.com/pulp/pulpcore/blob/master/.travis/Containerfile.ci_base

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

[Pulp-dev] Pulp Certguard Overview Next Week and @ggainey Joining certguard Mini Team

2020-05-14 Thread Brian Bouterse 
tl;dr @ggainey is joining the pulp-certguard mini team, making him and I
the mini team. Also, I'm hosting an open-and-recorded overview of
pulp-certguard's features, code, test, and docs next week (details below).

## ggainey joining mini team

Currently I'm the only person who is on the pulp-certguard mini team and
that's a problem in terms of developer availability when I'm out of the
office, and it's a bit stressful to be the only person on it.

@ggainey has graciously accepted my invite to join the mini team. Thank you
Grant!

## Pulp-certguard Tour: Wed, May 20th

To onboard ggainey, and share info broadly, I've scheduled an overview of
pulp-certguard's features, code, docs, and tests. With pulp-certguard
nearing its feature completion state this week, this is a good time to do
it. It will be recorded, posted to the YouTube channel, and a link sent
back to this thread afterwards.

Wed, May 20th 9:15 - 10am EDT
Join with Google Meet:  meet.google.com/gse-zqnm-ptk
Join by phone:  ‪+1 510-766-1775‬ PIN: ‪199 882 976‬#

Thank you!
Brian
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev