On Sun, Aug 20, 2017 at 04:11:13PM -0400, Christopher Duryee wrote:
On Sun, Aug 20, 2017 at 4:02 PM, Ewoud Kohl van Wijngaarden <
ew...@kohlvanwijngaarden.nl> wrote:
Hello all,
While working on splitting the Katello installation from its services I
ran into the pulp_export_destination setting. That made me look at the
Repository Export[1] which assumes the pulp server and application server
share the same filesystem.
That means I'm stuck in attempting to split services to different machines
where I don't want to assume a shared filesystem. Looking at the containers
it's not handled there either. I don't see a way to support this feature
without a major rewrite of the code but I'm not familiar with the Katello
code base.
Anyone has advice on how to deal with this?
I think if Pulp took a parameter to publish to a non-default location, we
would not need to do the extra copy step that ties Katello and Pulp closely
together. Currently it is needed because we need the export to land in
pulp_export_destination.
That would be nice. To me it looks like it already sends the
export_directory to pulp and has an absolute path. Is there a reason
this can't be set to Setting['pulp_export_destination'] directly?
[1]:
https://github.com/Katello/katello/blob/master/app/lib/actions/katello/repository/export.rb
--
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to foreman-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
