Re: [Pulp-dev] Work on creating a Kubernetes Operator for Pulp 3

le > system. For example, multiple pulp-content instances is 1 large advantage I > intend to implement soon, but autoscaling of pulp-content and pulp-worker > (later in development) would make for a much better demo. > > -Mike > > On Mon, May 13, 2019 at 5:03 PM Tom McKay wrote: &

Re: [Pulp-dev] Work on creating a Kubernetes Operator for Pulp 3

This is great! Glad to see the investment continuing. Is there a recorded demo of the operator in action on OCP/OKD? On Thu, May 9, 2019 at 6:12 PM Mike DePaulo wrote: > Hi everyone, > > Eric Helms & I have been working on creating Pulp 3 Kubernetes / container > packaging, including a

[Pulp-dev] How to retrieve file via pulp API?

I'd like to retrieve a file that is associated referenced in pulp, is there an API for that? I have info in foreman for a docker manifest (pulp id, storage path, etc) but am unsure how to retrieve it via pulp's API. ___ Pulp-dev mailing list

Re: [Pulp-dev] Call for Presenters: Community Demo, Wednesday August 1st

I'm not sure I have time to prepare for tomorrow's demo, but would it be alright to demo foreman with features directly attributable to pulp work? Specifically there are three pulp-2.17 features (two being demoed by @bizhang tomorrow!) that I could show at the next community demo. On Wed, Jul

Re: [Pulp-dev] foreman community demo w/ pulp container image repos

On Thu, May 31, 2018 at 1:03 PM, Tom McKay wrote: > Foreman[1] uses pulp as a service for managing content. I gave a demo[2] > today on two features that rely on pulp: Mirroring docker registries and > maintaining the image names, and uploading skopeo saves to disk for > disconnect

Re: [Pulp-dev] Pulp 2 plugin release plan

Just curious, but I assume that for an async plugin release that would imply zero changes to the exposed APIs and only fixes to the underlying code? As a consumer of pulp, we install pulp-server not individual plugins. If a plugin changes it's exposed interface (ie. API) then I'd expect a bump on

[Pulp-dev] foreman community demo w/ pulp container image repos

Foreman[1] uses pulp as a service for managing content. I gave a demo[2] today on two features that rely on pulp: Mirroring docker registries and maintaining the image names, and uploading skopeo saves to disk for disconnected and other cases. A big thanks to all the pulp devs that have put up

Re: [Pulp-dev] Lazy for Pulp3

r naming ideas and use cases > are welcome. > > Thanks, > Brian > > On Wed, May 30, 2018 at 10:50 AM, Brian Bouterse > wrote: > >> >> >> On Wed, May 30, 2018 at 8:57 AM, Tom McKay >> wrote: >> >>> I think there is a usecase for "proxy only&

Re: [Pulp-dev] Lazy for Pulp3

I think there is a usecase for "proxy only" like is being described here. Several years ago there was a project called thumbslug[1] that was used in a version of katello instead of pulp. It's job was to check entitlements and then proxy content from a cdn. The same functionality could be

Re: [Pulp-dev] Pulp api seemingly incompatible with generated bindings

If I'm deploying pulp in openshift, my "hostname" can vary greatly since comms go through a router. Would you want to save docker-registry.192.168.100.1.nip.io in the database? apiVersion: v1 kind: Route metadata: name: registry-access spec: host: docker-registry.`minishift ip`.nip.io to:

[Pulp-dev] Two docker repos with the same registry image name?

I forget the field in pulp db, the one that crane exposes as the image name. Can I have two repos with the same image name? For example, could I have repo 1 with name "rhel7/rhel" with tags 1 and 2, as well as repo 2 with name "rhel7/rhel" with tags 3 and 4?

[Pulp-dev] pulp-3 mock API for use with foreman prep

Is there collaboration already between pulp and foreman devs in preparation for pulp-3 changes? I would feel more comfortable if as the pulp-3 api is developed a working mock api that foreman devs could code against. This would expose gaps in data, models, patterns, etc. I know foreman has a

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

> Regards, > > Ina Panova > 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, Mar 7, 2018 at 10:06 PM, Tom McKay <thomasmc...@redhat.com> wrote: >>

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

; ide/recipes.rst#upload-v2-schema-2-and-schema-1-images-to-pulp >> >> >> >> >> Regards, >> >> Ina Panova >> Software Engineer| Pulp| Red Hat Inc. >> >> "Do not go where the path may lead, >> go instead where th

[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

[Pulp-dev] docker repo RFEs

A couple foreman RFEs continue to pop up around managing docker tags in repos when syncing. The case for them centers around cleaning up storage and preventing stale manifests and tags from being accessible. The first is a request to be able to create tag filters for sync. This would let the user

[Pulp-dev] example json to upload a tag?

Can someone paste me an example json of creating a tag through API import_upload? I'm struggling to figure out how to tag an uploaded skopeo tar. https://docs.pulpproject.org/en/2.15/dev-guide/integration/rest-api/content/upload.html?highlight=import_upload#import-into-a-repository

Re: [Pulp-dev] Proposal and feedback request: un-nest urls

I don't know how this works, but in github I see "Latest commit 898584a 3 days ago" and clicking through gives me the full "898584a7d241618b2d9206d21eaf2fbd0a75ecd7". As a user, I like the the convenience of the shorter id for use in command line interactions and displayed in UI. On Fri, Nov 17,

Re: [Pulp-dev] Docker Manifest list support in Pulp

Would you mind providing links to docs, tech and user level, for what a manifest list is and is used for? On Mon, Jun 12, 2017 at 10:36 AM, Ina Panova wrote: > There have been ongoing planning effort on how to add the support for > Manifest lists into Pulp.[0][1] > > Please

Re: [Pulp-dev] Setting up solr with crane for docker search

Figured out: I had not defined my schema so the fields were defaulted to multi-valued. I'll write up example and make suggestions to that section of the docs. On Sat, Jan 28, 2017 at 7:21 AM, Tom McKay <thomasmc...@redhat.com> wrote: > I can find nothing about solr that would

Re: [Pulp-dev] Setting up solr with crane for docker search

I can find nothing about solr that would indicate the results I'm seeing versus the expected. http://yonik.com/solr-json-request-api/ On Sat, Jan 28, 2017 at 6:42 AM, Tom McKay <thomasmc...@redhat.com> wrote: > BTW, I figured it out with some help. > > The fields necessary in s

Re: [Pulp-dev] Setting up solr with crane for docker search

t > about each one. That's not nearly enough to help you decide if you want to > use a particular repository, unless you just need to be reminded of the > name of a repository you previously researched and decided to use. > > Michael > > On Fri, Jan 27, 2017 at 2:28 PM, Tom McKay &

[Pulp-dev] Setting up solr with crane for docker search

Does anyone have instructions for setting up solr for search? I am running a simple solr container[1] and have crane configured[2] to query it. However, I am missing the "data import handler" piece in solr, I think. I can see that a "docker search" successfully hits solr but has zero results.