[Pulp-dev] CI/CD meeting notes

February 18, 2020 - https://pulp.plan.io/issues/5687 - Has been on the current sprint since November - Prevents users from installing with S3 - Can someone from the installer team pick this up? - Dkliban will send note to list about switchi

Re: [Pulp-dev] Using nested virtualization for SELinux/FIPS CI testing on Travis & GHA

excellent report, thanks for working on this Mike! Best regards, Fabricio Aguiar Software Engineer, Pulp Project Red Hat Brazil - Latam +55 11 999652368 On Tue, Feb 18, 2020 at 5:51 PM Mike DePaulo wrote: > Nested hardware virtualization with KVM works on Travis, but

Re: [Pulp-dev] Using nested virtualization for SELinux/FIPS CI testing on Travis & GHA

Nested hardware virtualization with KVM works on Travis, but not on GitHub actions. I highly recommend we use it, even if it means maintaining some CI tests on travis rather than GHA. I evaluated 2 other possible solutions on GitHub Actions: VirtualBox software virtualization, and qemu emulation.

[Pulp-dev] Content.serializer class attribute for validation?

tl;dr should content subclasses define a serializer to be used for validation as a class attribute? For example FileContent would get: class FileContent(Content): serializer = FileContentSerializer Then the Stages API when creating content would use that Serializer when validating the data.

Re: [Pulp-dev] S3 support for development/testing

Thanks! This story sounds great; please let me know how I can help. On Tue, Feb 18, 2020 at 2:28 PM David Davis wrote: > Yea, good catch. I meant having plugin_template test against minio and not > s3. > > David > > > On Tue, Feb 18, 2020 at 2:22 PM Brian Bouterse > wrote: > >> This testing is

Re: [Pulp-dev] S3 support for development/testing

Yea, good catch. I meant having plugin_template test against minio and not s3. David On Tue, Feb 18, 2020 at 2:22 PM Brian Bouterse wrote: > This testing is much needed, so I'm glad to hear it's progressing. Thank > you for organizing. I put some questions inline. +1 to prioritizing it > until

Re: [Pulp-dev] S3 support for development/testing

This testing is much needed, so I'm glad to hear it's progressing. Thank you for organizing. I put some questions inline. +1 to prioritizing it until it's in place. On Mon, Feb 17, 2020 at 3:47 PM David Davis wrote: > Recently we discovered that S3 support was broken in Pulp 3.1[0]. Since we > h

Re: [Pulp-dev] Moving pulp_gem

I'm glad we moved pulp_gem. My personal perspective is that the Pulp organization on Github is useful to consolidate activity of the Pulp community. It's more visible to various other communities and users which is a good thing. Projects and plugins are free to host anywhere, but any project that w

Re: [Pulp-dev] [CI] [Installer] We should not test ansible-pulp against multiple versions of Python on the mgmt node

This all sounds good to me. Thanks @mikedep333! On Fri, Feb 14, 2020 at 10:47 AM Mike DePaulo wrote: > Hi CI & Installer teams, > > I talked with James Tanner (who works on Ansible Core), and his advice was > that we should not bother to test our ansible-pulp (a collection of roles) > against mu

[Pulp-dev] Pulp 2.21.1 dev freeze reminder

Any Pulp2 core or plugin bugfixes that you want included in the 2.21.1 release must be merged by 17:00 UTC, Wednesday Feb 19th. 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."