Crane

As an administrator, I can copy the redirect files from one deployment to another (for example, internal and external), and have Crane redirect to different pulp HTTP frontend machines without the need to re-publish or to hand-edit the redirect files.

Details¶

In our current setup, we have a purely internal pulp deployment, that publishes to an NFS share.

HTTP frontend machines handle the cert-based authn/authz and serve the content from the NFS share.

We have an internal set of HTTP frontend machines, and an internal customer has access to published content for all development stages (dev/test/prod).

We also have an external set of HTTP frontend machines, that handle external customer requests, and only serve the prod stage. Content from the internal NFS share is selectively rsynced into the external disk share.

This all works great for rpm and such.

I believe there is a problem with docker. We would have one internal and one external crane deployment, as expected. Content would be rsynced, as usual. However, because the redirect URL is "baked" into the redirect json files, the external Crane would redirect to the internal system, which is not helpful.

We would prefer not to republish / recreate the redirect files in our transition from internal to external content.

One way to handle this would be a Crane configuration option that directs crane to rewrite the redirect URL. In that case, internal and external crane systems would be configured differently.