[Pulp-list] Ruby gems mirror

Tue Oct 14 04:34:56 UTC 2014

Dhaval Joshi
09879838392

Hello,

I am happy to work on this, if you can give me basic information on putting in new plugin and requirements.

Regards,
DJ
 ------------------------------

 Message: 4
 Date: Sun, 12 Oct 2014 20:25:47 -0400 (EDT)
 From: Michael Hrivnak <mhrivnak at redhat.com>
 To: "Jason Ashby (IMS)" <AshbyJ at imsweb.com>
 Cc: pulp-list at redhat.com
 Subject: Re: [Pulp-list] Ruby gems mirror
 Message-ID:
     <483093631.31532931.1413159946991.JavaMail.zimbra at redhat.com>
 Content-Type: text/plain; charset=utf-8

 Jason,

 Pulp cannot manage ruby gems directly yet, but that would be
 a nice plugin to have. If you or anyone else is interested
 in making that happen (writing code), the core pulp team
 would be happy to help guide that effort.

 Reading the blog post you linked to, my guess is that they
 packaged their gems as rpms and thus managed them as normal
 yum repos.

 Michael

 ----- Original Message -----
 From: "Jason Ashby (IMS)" <AshbyJ at imsweb.com>
 To: pulp-list at redhat.com
 Sent: Sunday, October 12, 2014 2:03:29 PM
 Subject: [Pulp-list] Ruby gems mirror

 Has anyone created a gems repo with pulp? I can?t seem to
 find info on what the actual mirror URL would be on
 rubygems.org. Any idea what url to sync from? 

 Rubygems want you to use their custom mirror setup tool, but
 I?d prefer to create all of my package mirrors with pulp
 whenever possible. 

 This blog post suggests it is possible: http://www.krisbuytaert.be/blog/ruby-gems-yum-repo 

 Thanks, 

 Jason 

 Information in this e-mail may be confidential. It is
 intended only for the addressee(s) identified above. If you
 are not the addressee(s), or an employee or agent of the
 addressee(s), please note that any dissemination,
 distribution, or copying of this communication is strictly
 prohibited. If you have received this e-mail in error,
 please notify the sender of the error. 

 _______________________________________________
 Pulp-list mailing list
 Pulp-list at redhat.com
 https://www.redhat.com/mailman/listinfo/pulp-list

 ------------------------------

 Message: 5
 Date: Mon, 13 Oct 2014 00:52:44 +0000
 From: "Ashby, Jason (IMS)" <AshbyJ at imsweb.com>
 To: Michael Hrivnak <mhrivnak at redhat.com>
 Cc: "pulp-list at redhat.com"
 <pulp-list at redhat.com>
 Subject: Re: [Pulp-list] Ruby gems mirror
 Message-ID: <36D29181-E545-46C4-A7D2-1204DD09EE43 at imsweb.com>
 Content-Type: text/plain; charset="Windows-1252"

 Thanks Michael, that answers a bunch of questions.  If
 I find the time in the near future, I'll get to work on gem
 support. Thanks to the pulp team for making some great
 software.

 On Oct 12, 2014, at 8:27 PM, Michael Hrivnak <mhrivnak at redhat.com>
 wrote:

 Jason,

 Pulp cannot manage ruby gems directly yet, but that would be
 a nice plugin to have. If you or anyone else is interested
 in making that happen (writing code), the core pulp team
 would be happy to help guide that effort.

 Reading the blog post you linked to, my guess is that they
 packaged their gems as rpms and thus managed them as normal
 yum repos.

 Michael

 ----- Original Message -----
 From: "Jason Ashby (IMS)" <AshbyJ at imsweb.com>
 To: pulp-list at redhat.com
 Sent: Sunday, October 12, 2014 2:03:29 PM
 Subject: [Pulp-list] Ruby gems mirror

 Has anyone created a gems repo with pulp? I can?t seem to
 find info on what the actual mirror URL would be on
 rubygems.org. Any idea what url to sync from?

 Rubygems want you to use their custom mirror setup tool, but
 I?d prefer to create all of my package mirrors with pulp
 whenever possible.

 This blog post suggests it is possible: http://www.krisbuytaert.be/blog/ruby-gems-yum-repo

 Thanks,

 Jason

 Information in this e-mail may be confidential. It is
 intended only for the addressee(s) identified above. If you
 are not the addressee(s), or an employee or agent of the
 addressee(s), please note that any dissemination,
 distribution, or copying of this communication is strictly
 prohibited. If you have received this e-mail in error,
 please notify the sender of the error.

 _______________________________________________
 Pulp-list mailing list
 Pulp-list at redhat.com
 https://www.redhat.com/mailman/listinfo/pulp-list

 ________________________________

 Information in this e-mail may be confidential. It is
 intended only for the addressee(s) identified above. If you
 are not the addressee(s), or an employee or agent of the
 addressee(s), please note that any dissemination,
 distribution, or copying of this communication is strictly
 prohibited. If you have received this e-mail in error,
 please notify the sender of the error.

 ------------------------------

 Message: 6
 Date: Mon, 13 Oct 2014 13:26:37 +0300
 From: Veiko Kukk <vkukk at xvidservices.com>
 To: pulp-list at redhat.com
 Subject: [Pulp-list] Individual repo authentication
 Message-ID: <543BA8DD.9080502 at xvidservices.com>
 Content-Type: text/plain; charset=utf-8; format=flowed

 Hi

 I'm trying to upgrade from pulp-1.1.11-1.el6.noarch to 
 pulp-server-2.3.1-1.el6.noarch. Both systems are Centos
 6.5.
 Repo creation, population etc works fine, but I ran into
 problems with 
 securing selectively some of the repos.

 Old syntax goes like this and runs/works fine:

 # pulp-admin -u admin -p password repo update --id reponame

 --consumer_ca=/etc/pulp/capulp.crt
 --consumer_cert=/etc/pulp/client.crt 
 --consumer_key=/etc/pulp/client.key
 Successfully updated repository [ reponame ]

 With new version, syntax has changed and I'm confused how to
 get this 
 working. Found no documentation except from command line:
 Consumer Authentication
    --host-ca   - full path to
 the CA certificate that signed the repository

    hosts's SSL certificate when serving over
 HTTPS
    --auth-ca   - full path to
 the CA certificate that should be used to 
 verify

    client authentication certificates;
 setting this turns 
 on client

    authentication for the repository
    --auth-cert - full path to the entitlement
 certificate that will be 
 given to

    bound consumers to grant access to this
 repository

 Would be very helpful if you can link me some up to date
 documentation 
 of Pulp 2.3 regarding this issue.

 Thanks in advance,
 Veiko

 ------------------------------

 Message: 7
 Date: Mon, 13 Oct 2014 16:31:38 +0300
 From: Veiko Kukk <vkukk at xvidservices.com>
 To: pulp-list at redhat.com
 Subject: Re: [Pulp-list] Individual repo authentication
 Message-ID: <543BD43A.9090903 at xvidservices.com>
 Content-Type: text/plain; charset=utf-8; format=flowed

 On 13/10/14 13:26, Veiko Kukk wrote:
 > I'm trying to upgrade from pulp-1.1.11-1.el6.noarch to
 > pulp-server-2.3.1-1.el6.noarch. Both systems are Centos
 6.5.
 > Repo creation, population etc works fine, but I ran
 into problems with
 > securing selectively some of the repos.
 >
 > Old syntax goes like this and runs/works fine:
 >
 > # pulp-admin -u admin -p password repo update --id
 reponame
 > --consumer_ca=/etc/pulp/capulp.crt
 --consumer_cert=/etc/pulp/client.crt
 > --consumer_key=/etc/pulp/client.key
 > Successfully updated repository [ reponame ]

 Looks very similar to this bug 
 https://bugzilla.redhat.com/show_bug.cgi?id=1119126
 When executing:
 # pulp-admin -u admin -p password rpm repo update --repo-id
 reponame 
 --host-ca=/etc/pki/pulp/ca.crt
 --auth-ca=/etc/pki/pulp/capulp.crt 
 --auth-cert=/etc/pki/pulp/client.crt

 The server indicated one or more values were incorrect. The
 server 
 provided the
 following error message:

     Configuration key 'https_ca' is not supported

 More information can be found in the client log file
 ~/.pulp/admin.log.

 And from the log:
 2014-10-13 13:24:36,961 - ERROR - Exception occurred:
          href:   
   /pulp/api/v2/repositories/reponame/
          method:   
 PUT
          status:   
 400
          error: 
    Configuration key 'https_ca' is not
 supported
          traceback: None
          data:   
   {u'args': [u"Configuration key 'https_ca' is not 
 supported"]}

 Veiko

 ------------------------------

 Message: 8
 Date: Mon, 13 Oct 2014 11:29:48 -0400
 From: Randy Barlow <rbarlow at redhat.com>
 To: "pulp-list at redhat.com"
 <pulp-list at redhat.com>
 Subject: [Pulp-list] [devel] Bug Counts
 Message-ID: <543BEFEC.1090408 at redhat.com>
 Content-Type: text/plain; charset="utf-8"

 I've begun tracking our overall bug counts on a daily basis.
 Attached is
 a graph of the first few days of data. There isn't much
 movement so far,
 but we hope to see this graph move down and to the right
 over time.
 This graph excludes bugs that are NEW and low priority, and
 it also
 excludes bugs that are VERIFIED (which means they aren't
 released, but
 have passed QE for an upcoming release.)
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: Screenshot from 2014-10-13 11:27:28.png
 Type: image/png
 Size: 25495 bytes
 Desc: not available
 URL: <https://www.redhat.com/archives/pulp-list/attachments/20141013/b9133094/attachment.png>
 -------------- next part --------------
 A non-text attachment was scrubbed...
 Name: signature.asc
 Type: application/pgp-signature
 Size: 819 bytes
 Desc: OpenPGP digital signature
 URL: <https://www.redhat.com/archives/pulp-list/attachments/20141013/b9133094/attachment.bin>

 ------------------------------

 _______________________________________________
 Pulp-list mailing list
 Pulp-list at redhat.com
 https://www.redhat.com/mailman/listinfo/pulp-list

 End of Pulp-list Digest, Vol 59, Issue 6
 ****************************************