[Pulp-dev] possible to upload container image blobs?

I know I can upload a skopeo copy tar file but is it possible to upload individual blobs directly? Or upload the components of the tar file individually? I am on pulp-2.15.2. ___ Pulp-dev mailing list Pulp-dev@redhat.com

Re: [Pulp-dev] Migrating Sprint to Custom Field [happening tomorrow]

Thank you! My late but big +1. Tanya On Tue, Mar 6, 2018 at 11:04 PM, Brian Bouterse wrote: > Thanks for all the feedback! With many +1s and no -1s, I'm going to make > this change tomorrow. I'll send out links to the result when it is done. > > -Brian > > > On Mon, Mar 5,

Re: [Pulp-dev] possible to upload container image blobs?

Hello Tom, No it is not possible to upload individual blobs, the only way how to get image manifest schema1 or schema2 for now is to use skopeo copy and tar the output. For more info please checks the docs and recipes [0]. In addition it is not safe to upload the components of the tar file

Re: [Pulp-dev] possible to upload container image blobs?

resending since mobile email triggered approval... i have created an api endpoint in foreman for docker push and from there will be calling pulp. don’t worry about “safe” since there is no manual aspect. if pulp doesn’t support it, i will work around. if it us possible, please tell me how.

[Pulp-dev] Next Community Demo March 28

FYI, I scheduled the next demo for March 28. We're pushing it out a little bit so the core team can focus on core a bit more to hopefully wrap it up into a beta at some point. Feel free to record demos ahead of time as you do work. The demos are a great way to communicate to users how things

Re: [Pulp-dev] 2.15.3 dev freeze -- 22:00 UTC Tuesday, March 6th

On Tue, Mar 6, 2018 at 11:30 PM, Brian Bouterse wrote: > Per the release schedule, the code for 2.15.3 is now frozen. There are a > total of 8 issues spread across core, rpm, and docker. This is ready for > release engineering. The current beta date for 2.15.3 is March 13th.

Re: [Pulp-dev] 2.15.3 dev freeze -- 22:00 UTC Tuesday, March 6th

Yes they are docs only. In that case, I think it's ok to include them in the Z-stream. I switched them to issues since only issues can be in the z-stream. The 2.15.3 release now contains 10 issues. https://pulp.plan.io/issues?query_id=59 Thanks! Brian On Wed, Mar 7, 2018 at 4:43 AM, Milan

Re: [Pulp-dev] Plugin triage

I would like to hear from QE since I know they had some concerns here. Since the Pulp QE team is much smaller, having to manage attendance to multiple traige's per week is more of a strain on them to have the interruptions and their expertise may not be as clearly delineated as a larger team which

Re: [Pulp-dev] Plugin triage

On Wed, Mar 7, 2018 at 8:58 AM, Robin Chan wrote: > I would like to hear from QE since I know they had some concerns here. > Since the Pulp QE team is much smaller, having to manage attendance to > multiple traige's per week is more of a strain on them to have the >