Re: [Pulp-list] Accessing Puppet Module Repositories

2014-09-23 Thread Cristian Falcas
Hello Dan, I have the same erors. Did you manage to fix them? Best regards, Cristian Falcas On Mon, Sep 15, 2014 at 6:52 PM, Dan Hawker danhaw...@googlemail.com wrote: Hi, Have just started implementing Pulp as part of a PoC to see if we can use it to help streamline some of our

[Pulp-list] which pulp repository to use

2014-09-23 Thread joshi dhaval
Hello, can i deploy 2.4.1 available in 2.4 Beta repository for my production pulp deployment ? i think 2.4.1 has some bugs resolved.. which one i should use ? Regards, DJ ___ Pulp-list mailing list Pulp-list@redhat.com

Re: [Pulp-list] which pulp repository to use

2014-09-23 Thread Brian Bouterse
To me, it's a personal choice based on how comfortable you are with running code that is new and has not been fully tested. The term beta to the Pulp development team means that it is feature complete, testing has not finished yet. If you need to run code that has been fully tested then you

[Pulp-list] Is there any plan for audit activity ?

2014-09-23 Thread joshi dhaval
Hello, I am looking for audit activity on package Upload, deploy, remove by particular user, which should report which user did package installation or removed or uploaded to repository. i checked database, i did not find any activity information there as well. Regards, DJ

Re: [Pulp-list] [devel] pulp-2.4 has been deleted from the pulp_puppet repo

2014-09-23 Thread Randy Barlow
On 09/22/2014 04:38 PM, Randy Barlow wrote: I have deleted the scary pulp-2.4 branch from the pulp_puppet repo. You should delete your local copies of that branch too: (pulp_puppet)[rbarlow@notepad]~/devel/pulp_puppet% git branch -d pulp-2.4 Deleted branch pulp-2.4 (was dcc8ef9). We

[Pulp-list] 2.4.1-1 released!

2014-09-23 Thread Randy Barlow
The Pulp team is pleased to announce that we have release Pulp-2.4.1-1 to our stable repositories. This is a minor bugfix release. Please see the release notes[0][1][2] if you are interested in reading about the fixes that are included. Happy upgrading! [0]

Re: [Pulp-list] Is master going to be 2.6 or 3.0 (an API change question)?

2014-09-23 Thread Michael Hrivnak
You could have the web handler copy the attribute worker_name to queue, so the API returns both. Then mark queue as deprecated in the documentation. That would let us comfortably release this as part of a 2.6 or 3.0. Would that cover all public-API use cases? Or does that data get exposed

Re: [Pulp-list] Is master going to be 2.6 or 3.0 (an API change question)?

2014-09-23 Thread Randy Barlow
On 09/23/2014 03:00 PM, Michael Hrivnak wrote: You could have the web handler copy the attribute worker_name to queue, so the API returns both. Then mark queue as deprecated in the documentation. That would let us comfortably release this as part of a 2.6 or 3.0. This is a fantastic