[Pulp-list] Syncing external repo GPG keys (dell OMSA)

[Trey Dockendorf]

Yep that works.  Thanks for suggestions.

- Trey

On Thu, Jan 29, 2015 at 1:30 AM, Roth, Sandro <
Sandro.Roth at zurich-airport.com> wrote:

>  Trey
>
>
>
> You could just remove the SSL requirement from apache config.
>
>
>
> In /etc/httpd/conf.d/pulp.conf it says
>
>
>
> <Location /pulp/static>
>
>     SSLRequireSSL
>
>     Options +Indexes
>
>     Order allow,deny
>
>     Allow from all
>
> </Location>
>
>
>
> Comment out the SSLRequireSSL option and you should be good to go!
>
>
>
> Sandro
>
>
>
> *From:* Trey Dockendorf [mailto:treydock at gmail.com]
> *Sent:* Mittwoch, 28. Januar 2015 17:14
> *To:* Roth, Sandro
> *Cc:* pulp-list at redhat.com
> *Subject:* Re: [Pulp-list] Syncing external repo GPG keys (dell OMSA)
>
>
>
> Sandro,
>
>
>
> That's exactly what I was looking for, thanks.  Is there a preferred
> method to make static content accessible over HTTP?  I have not yet
> configured HTTPS with a trusted CA cert so likely can't be used yet by
> clients.
>
>
>
> Thanks,
>
> - Trey
>
>
>
> On Wed, Jan 28, 2015 at 2:33 AM, Roth, Sandro <
> Sandro.Roth at zurich-airport.com> wrote:
>
> Hi Trey
>
>
>
> We manually put all the gpg keys in /var/lib/pulp/static/ which is then
> available at https://pulp-host/pulp/static/. (https only per default
> config I think)
>
> Puppet will rpm –import the keys before configuring the repos, which works
> really well.
>
>
>
>
>
> Cheers
>
> Sandro
>
>
>
> *From:* pulp-list-bounces at redhat.com [mailto:pulp-list-bounces at redhat.com]
> *On Behalf Of *Trey Dockendorf
> *Sent:* Dienstag, 27. Januar 2015 23:21
> *To:* pulp-list at redhat.com
> *Subject:* [Pulp-list] Syncing external repo GPG keys (dell OMSA)
>
>
>
> I've synced with Pulp the Dell OMSA repository for EL6 but am unsure how
> to handle the two GPG keys that are associated with the repo when the Dell
> provided bootstrap script is used.
>
>
>
> Below is the contents of what Dell's bootstrap script produces in
> /etc/yum.repos.d.  My goal is to mirror the "dell-omsa-indep" repo first
> and validate I can make that work with systems that have very restricted
> external connectivity to the internet.  Is there a way in Pulp to somehow
> grab those GPG keys and make them available via the repository paths
> generated when a repo is synced?
>
>
>
> Thanks,
>
> - Trey
>
>
>
> [dell-omsa-indep]
>
> name=Dell OMSA repository - Hardware independent
>
> type=rpm-md
>
> mirrorlist=
> http://linux.dell.com/repo/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&native=1&dellsysidpluginver=$dellsysidpluginver
>
> gpgcheck=1
>
> gpgkey=http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-dell
>
>     http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-libsmbios
>
> enabled=1
>
> failover=priority
>
> bootstrapurl=http://linux.dell.com/repo/hardware/latest/bootstrap.cgi
>
>
>
>
>
> [dell-omsa-specific]
>
> name=Dell OMSA repository - Hardware specific
>
> type=rpm-md
>
> mirrorlist=
> http://linux.dell.com/repo/hardware/latest/mirrors.cgi?osname=el$releasever&basearch=$basearch&native=1&sys_ven_id=$sys_ven_id&sys_dev_id=$sys_dev_id&dellsysidpluginver=$dellsysidpluginver
>
> gpgcheck=1
>
> gpgkey=http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-dell
>
>     http://linux.dell.com/repo/hardware/latest/RPM-GPG-KEY-libsmbios
>
> enabled=1
>
> failover=priority
>
> bootstrapurl=http://linux.dell.com/repo/hardware/latest/bootstrap.cgi
>
> This email message and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify us immediately and destroy the original transmittal. You are hereby notified that any review, copying or distribution of it is strictly prohibited. Thank you for your cooperation.
>
>
>
> Header information contained in E-mails to and from the company are monitored for operational reasons in accordance with swiss data protection act.
>
>
>
> This email message and any attachments are confidential and may be privileged. If you are not the intended recipient, please notify us immediately and destroy the original transmittal. You are hereby notified that any review, copying or distribution of it is strictly prohibited. Thank you for your cooperation.
>
> Header information contained in E-mails to and from the company are monitored for operational reasons in accordance with the Swiss data protection act.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-list/attachments/20150129/e12d159f/attachment.htm>