Re: [Pulp-dev] Pulp 3 for Fedora

[Neal Gompa]

On Mon, Feb 11, 2019 at 3:15 PM David Davis  wrote:
>
> Neal,
>
> I completely agree with the points you brought up and would love to see Pulp 
> 3 shipped in Fedora. The only thing I am hesitant about is the timing. Fedora 
> 30 is shipping in May, correct? We’re approaching an RC for Pulp’s core but 
> none of the plugins are really ready. I think releasing Pulp for Fedora 31 in 
> the fall might be more feasible but maybe we can re-evaluate in March.
>

If things are in a usable state, there's no reason not to start the
packaging work and go through the package review process[1]. That lets
us sort out issues early and get them addressed in time for
integration into the distribution. Failing that, there could be a
COPR[2] for it if it doesn't fully make it.

[1]: https://fedoraproject.org/wiki/Package_Review_Process
[2]: https://copr.fedorainfracloud.org/

> Also, I’d love to talk more about integrating Pulp into's Fedora 
> infrastructure. I joined the Pulp team a couple years ago and have been 
> constantly wondering why Fedora is not using Pulp to manage and distribute 
> its RPMs. Maybe at some point we can give you a demo of Pulp 3 and figure out 
> how we can help fill Fedora’s needs.
>

I know that previously Pulp was considered for at least hosting the
container images[3]. I'm not sure what happened there. It'd be a good
idea to introduce yourself to releng[4] and infrastructure[5] folks
and propose the idea.

[3]: https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service
[4]: 
https://lists.fedoraproject.org/archives/list/rel-...@lists.fedoraproject.org/
[5]: 
https://lists.fedoraproject.org/archives/list/infrastruct...@lists.fedoraproject.org/

--
真実はいつも一つ！/ Always, there's only one truth!

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

Re: [Pulp-dev] Pulplift responsibilities

[Dana Walker]

Thanks, Dennis!

I would also like to be part of this team.

--Dana

Dana Walker

Associate Software Engineer

Red Hat





On Mon, Feb 11, 2019 at 4:23 PM Dennis Kliban  wrote:

> A new mini-team should be responsible for pulplift. I would like to be
> part of that team. I welcome others to join the team or to just send
> contributions.
>
> On Tue, Feb 5, 2019 at 9:15 AM Dana Walker  wrote:
>
>> Eric Helms did a great job getting Pulplift off the ground and
>> transferred it to the Pulp organization.  Since then, several of us have
>> helped with PRs on it.  Now the question is--who all is interested in being
>> tasked with maintaining it moving forward?
>>
>> We have several miniteams for our plugins already--should it have its own
>> or be part of another?
>>
>> Thoughts?
>>
>> --Dana
>>
>> Dana Walker
>>
>> Associate Software Engineer
>>
>> Red Hat
>>
>> 
>> 
>> ___
>> 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

Re: [Pulp-dev] Pulp 3 for Fedora

[James Cassell]

On Mon, Feb 11, 2019, at 2:38 PM, Neal Gompa wrote:
> Hello all,
> 
> I wanted to ask about having Pulp 3 land in Fedora. We've had Pulp 2
> in the distribution for several releases now (it was dropped in Fedora
> 28~29). The new Pulp 3 stuff looks wicked cool and seems to be a vast
> improvement over Pulp 2. With MongoDB being dropped in Fedora 30[1],
> there's no longer an opportunity to run the current Pulp on Fedora.
> 
> Moreover, Fedora has been aggressively moving to drop Python 2
> components[2] and has done so for more than half of all Python
> components packaged in the distribution[3].
> 
> I had briefly discussed this with a few folks before, and they'd been
> under the impression that packaging for Fedora would be difficult. On
> the contrary, Python packaging in Fedora has never been easier! We now
> have the ability to auto-generate runtime dependencies[4] (which can
> also be activated on a per-spec basis in F28 and RHEL8) and an
> excellent tool for auto-generating the spec files for packaging Python
> software that is released to PyPI[5].
> 
> I would love to see Pulp reintroduced to Fedora now so that it could
> debut with the Fedora 30 release. It could also be interesting to see
> if we could leverage the new Pulp 3 in Fedora infrastructure for RPMs,
> OSTrees, and Docker containers in place of the hodgepodge of things we
> have now. I've heard good things about how Pulp 3 is developing, and
> I'd love to see it available on Fedora so I could use it there too. :)
> 
> What do you all think?
> 

Sounds great to me! (But I don't currently have time to do the work)

V/r,
James Cassell


> Best regards,
> Neal
> 
> [1]: https://fedoraproject.org/wiki/Changes/MongoDB_Removal
> [2]: https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
> [3]: https://fedora.portingdb.xyz/
> [4]: https://fedoraproject.org/wiki/Changes/EnablingPythonGeneratorsByDefault
> [5]: https://github.com/fedora-python/pyp2rpm
> 
> --
> 真実はいつも一つ！/ Always, there's only one truth!


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

Re: [Pulp-dev] Pulp 3 for Fedora

[David Davis]

Neal,

I completely agree with the points you brought up and would love to see
Pulp 3 shipped in Fedora. The only thing I am hesitant about is the timing.
Fedora 30 is shipping in May, correct? We’re approaching an RC for Pulp’s
core but none of the plugins are really ready. I think releasing Pulp for
Fedora 31 in the fall might be more feasible but maybe we can re-evaluate
in March.

Also, I’d love to talk more about integrating Pulp into's Fedora
infrastructure. I joined the Pulp team a couple years ago and have been
constantly wondering why Fedora is not using Pulp to manage and distribute
its RPMs. Maybe at some point we can give you a demo of Pulp 3 and figure
out how we can help fill Fedora’s needs.

Thanks for reaching out.

David


On Mon, Feb 11, 2019 at 2:39 PM Neal Gompa  wrote:

> Hello all,
>
> I wanted to ask about having Pulp 3 land in Fedora. We've had Pulp 2
> in the distribution for several releases now (it was dropped in Fedora
> 28~29). The new Pulp 3 stuff looks wicked cool and seems to be a vast
> improvement over Pulp 2. With MongoDB being dropped in Fedora 30[1],
> there's no longer an opportunity to run the current Pulp on Fedora.
>
> Moreover, Fedora has been aggressively moving to drop Python 2
> components[2] and has done so for more than half of all Python
> components packaged in the distribution[3].
>
> I had briefly discussed this with a few folks before, and they'd been
> under the impression that packaging for Fedora would be difficult. On
> the contrary, Python packaging in Fedora has never been easier! We now
> have the ability to auto-generate runtime dependencies[4] (which can
> also be activated on a per-spec basis in F28 and RHEL8) and an
> excellent tool for auto-generating the spec files for packaging Python
> software that is released to PyPI[5].
>
> I would love to see Pulp reintroduced to Fedora now so that it could
> debut with the Fedora 30 release. It could also be interesting to see
> if we could leverage the new Pulp 3 in Fedora infrastructure for RPMs,
> OSTrees, and Docker containers in place of the hodgepodge of things we
> have now. I've heard good things about how Pulp 3 is developing, and
> I'd love to see it available on Fedora so I could use it there too. :)
>
> What do you all think?
>
> Best regards,
> Neal
>
> [1]: https://fedoraproject.org/wiki/Changes/MongoDB_Removal
> [2]: https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
> [3]: https://fedora.portingdb.xyz/
> [4]:
> https://fedoraproject.org/wiki/Changes/EnablingPythonGeneratorsByDefault
> [5]: https://github.com/fedora-python/pyp2rpm
>
> --
> 真実はいつも一つ！/ Always, there's only one truth!
>
> ___
> 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] Pulp 3 for Fedora

[Neal Gompa]

Hello all,

I wanted to ask about having Pulp 3 land in Fedora. We've had Pulp 2
in the distribution for several releases now (it was dropped in Fedora
28~29). The new Pulp 3 stuff looks wicked cool and seems to be a vast
improvement over Pulp 2. With MongoDB being dropped in Fedora 30[1],
there's no longer an opportunity to run the current Pulp on Fedora.

Moreover, Fedora has been aggressively moving to drop Python 2
components[2] and has done so for more than half of all Python
components packaged in the distribution[3].

I had briefly discussed this with a few folks before, and they'd been
under the impression that packaging for Fedora would be difficult. On
the contrary, Python packaging in Fedora has never been easier! We now
have the ability to auto-generate runtime dependencies[4] (which can
also be activated on a per-spec basis in F28 and RHEL8) and an
excellent tool for auto-generating the spec files for packaging Python
software that is released to PyPI[5].

I would love to see Pulp reintroduced to Fedora now so that it could
debut with the Fedora 30 release. It could also be interesting to see
if we could leverage the new Pulp 3 in Fedora infrastructure for RPMs,
OSTrees, and Docker containers in place of the hodgepodge of things we
have now. I've heard good things about how Pulp 3 is developing, and
I'd love to see it available on Fedora so I could use it there too. :)

What do you all think?

Best regards,
Neal

[1]: https://fedoraproject.org/wiki/Changes/MongoDB_Removal
[2]: https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
[3]: https://fedora.portingdb.xyz/
[4]: https://fedoraproject.org/wiki/Changes/EnablingPythonGeneratorsByDefault
[5]: https://github.com/fedora-python/pyp2rpm

--
真実はいつも一つ！/ Always, there's only one truth!

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

[Pulp-dev] pulpcore-plugin 0.1.0b20

[Jeff Ortel]

The following packages are now available on PyPI:
   - pulpcore-plugin 0.1.0b20 [1] with its release notes here [2]

Note: The management of remote artifacts has been pulled out of the 
ContentSaver stage and is now provided by a /new/ RemoteArtifactSaver stage.

  Plugins creating custom pipelines should include this stage.

The beta documentation is available here[3].

[1]: https://pypi.org/project/pulpcore-plugin/0.1.0b20/ 

[2]: 
https://docs.pulpproject.org/en/pulpcore-plugin/nightly/release-notes/index.html#b20 


[3] https://docs.pulpproject.org/en/3.0/beta/
___
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev