Thanks for that Jason.  I'll have a read and see if it might work for us.

On 12 October 2016 at 15:01, 'Jason B. Nance' via Foreman users <
foreman-users@googlegroups.com> wrote:

> JC,
>
> My suggestion for you would be to use pulp-puppet-module-builder to create
> a local "forge" with only the modules you are interested in that Katello
> can sync.  You can find some info about it here:
>
> https://access.redhat.com/documentation/en-US/Red_Hat_
> Satellite/6.1/html/Puppet_Guide/sect-Red_Hat_Satellite-
> Puppet_Guide-Adding_Puppet_Modules_to_Red_Hat_Satellite_
> 6-Adding_Puppet_Modules_from_a_Git_Repository.html
>
> Regards,
>
> j
>
>
> ------------------------------
> *From: *"JC" <mr.jamie.caldw...@gmail.com>
> *To: *"Foreman users" <foreman-users@googlegroups.com>
> *Sent: *Wednesday, October 12, 2016 8:15:13 AM
> *Subject: *[foreman-users] [Katello 3.1]: getting puppet modules in an
> air-gapped environment?
>
> Hi folks,
> I'm running Katello 3.1 in an air-gapped environment.  I have a Katello
> 2.4 server connected to the internet which collects the repos needed by the
> 3.1 server.  I 'export' the content from the 2.4 server manually, then
> present it to the 3.1 server via http.  This is fine for the yum repos, but
> now I want to sync the puppet modules from the forge also.
> I've siphoned off the /var/lib/pulp/content/puppet_modules tar.gz files
> and collected https://forge.puppet.com/modules.json.  All of which are
> presented to the 3.1 server via http.  However, looking at the 3.1
> webserver logs, Katello can't find the tar.gz files when I start a sync --
> it appears to be looking, for example, for 
> /puppet_module*/system/releases/{first
> letter of package}/{package owner}/{package}.tar.gz .  It does know which
> files it wants and how many though.
>
> *puppet_module is where the modules.json file and the tar.gz files are
> stored.
>
> Any suggestions?  I've seen some other methods for getting and presenting
> the content from forge, but I'd really like Katello to own them
> internally.  Cheers.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Foreman users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/foreman-users/nTQ0vPE6JkM/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to