Hi Alan, I'm glad you were able to work around it. Thanks so much for
letting us know about the issue!
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.co
config' in importer:
_write_pem_file(pki_path, importer['config'], key, filename)
If you are comfortable working in Python, you could try something like
that at line 25 in
/usr/lib/python2.6/site-packages/pulp/server/db/migrations/0023_importer_tls_storage.py
I apologize for the assumption an
On Wednesday, May 4, 2016 9:24:40 AM EDT Dennis Kliban wrote:
> I see value in keeping around older builds. That is the reason for having
a
> 'tested-nightly' directory that contains the last build that passed all
> pulp-smash tests. How many of the passing builds would we want to
keep
> around?
AIK it never was
"completed" enough to be functional. If you are interested in taking
this project on, hop over to #pulp on Freenode and chat with us. I'd
love to help you get started, and we have a pretty nice Vagrant
based development environment that makes it easier to work on Pulp.
On Friday, April 22, 2016 11:21:28 AM CDT Dennis Kliban wrote:
> The proposed locations are
>
> https://repos.fedorapeople.org/repos/pulp/pulp/nightly//
> https://repos.fedorapeople.org/repos/pulp/pulp/tested-nightly//
>
> What questions or comments do you have?
This sounds great! One
we find that it is too short (I doubt
we'll think it's too long ☺).
What do you think?
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/p
On Wednesday, March 16, 2016 12:23:48 AM EDT Matthew Madey
wrote:
> I think it's failing to remove the files when they are done. Currently
> there are 2G of RPM's in the cache directory, most of them are
0bytes. I'm
> syncing with the RHEL7 repository, and I'm seeing every package in
the
>
> Given this inconsistency, this looks like a bug(?)
Hello Simon! This is definitely a bug, would you mind reporting it in our
ticket tracker?
https://pulp.plan.io/projects/pulp/issues/new
Thanks for letting us know!
___
Pulp-list mailing list
On Fri, Mar 04, 2016 at 09:27:12PM +, Elizabeth Jones wrote:
> I did not have goferd running on the new server, I started it, cancelled the
> hung task and re-ran it but it still hangs.
Hello Elizabeth!
goferd should be running on the consumer - can you check that?
--
Randy Barl
On Wed, Mar 02, 2016 at 05:14:33PM -0500, Dennis Kliban wrote:
> Release notes can be found here [1-5].
Also, Crane 2.0.0's release notes are here:
https://github.com/pulp/crane/tree/2.0.0#200
Happy testing!
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signat
ld have been called Pulp 3.0 because it
makes several backwards incompatible changes. When you do upgrade
eventually, make sure you pay attention to the release notes for every
version but give special attention to the 2.4 release notes. There are
quite a few improvements in 2.7 so I'd say it's worth doi
se to use https:// if you don't want trust to happen.
TLS is for two things: trust and privacy, and you can't have privacy
without trust.
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@r
On Wed, Feb 03, 2016 at 05:32:58PM +0100, kamil kapturkiewicz wrote:
> Warning: group pulp-server-qpid does not exist.
Did you remember to add our yum repository?
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signature
___
P
On Wed, Feb 03, 2016 at 02:44:29PM -0500, Partha Aji wrote:
> Question is whether the default option be to skip verification and one has
> pass a separate flag to
> enable verification OR the other way round (I am ok either way.)
Defaulting to secure is a good policy.
--
Randy B
h them with a PULP_MANIFEST file and is also able to
sync them from Pulp to Pulp. You could use this to mirror png files,
flac files, or whatever you like!
Hope that helps!
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: PGP signature
___
Pul
sure. Thanks for the RFE!
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
you need to configure Pulp's broker. In
particular, pay attention to both the [messaging] and [tasks] sections.
Hope that helps!
--
Randy Barlow
irc: bowlofeggs
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@r
a link to the Katello Puppet module that serves
the same purpose:
https://github.com/pulp/puppet_deployment/pull/27
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list
On Tue, Dec 08, 2015 at 11:23:20AM -0500, Austin Macdonald wrote:
> -BEGIN PGP MESSAGE-
lololol
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.
On Tue, Dec 01, 2015 at 11:55:25AM -0500, Sean Myers wrote:
> On 11/30/2015 04:55 PM, Randy Barlow wrote:
> > 1) We could make the repository's README state that it is deprecated,
> > and provide a link to the Katello project.
>
> I prefer this, more details below.
>
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
port 443 and
that this is not configurable. In my opinion, it would be worth filing a
ticket to request that pulp-admin allow the port to be configurable.
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: PGP signature
___
, pulp_resource_manager, and pulp_celerybeat.
1) Try using RabbitMQ instead of qpidd.
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https
) upload lets you upload units, and it returns their unit ids in Pulp.
It does not associate with repositories.
1) associate allows you to associate units by ids with repositories.
The combination of the two I think would work well for your use case, as
well as all other use cases that I am familiar with.
Tha
w when that will be. Apologies for your frustration in the
meantime!
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: PGP signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
ovides the qpid message
adapter. There are also python-gofer-amqp and python-gofer-proton
messaging adapters for different message brokers if you happen to not be
using qpidd.
--
Randy Barlow
irc: bowlofeggs
phone: +1-919-890-8150
signature.asc
Description: OpenPGP digital sig
hange to me, and more like
one of the tasks was not able to find your pypi repository in the
database. Was there any more information in your syslog, perhaps a long
traceback or two? If so, can you share those? Is your repository
definitely named "pypi" (it is case sensitive)?
--
Randy Ba
On Thu, Oct 22, 2015 at 02:50:45PM +, Swartz, Patrick wrote:
> Is there a way to update the "--feed-cert=/etc/pki/entitlement/.pem" and
> "--feed-key=/etc/pki/entitlement/-key.pem" after a repo has been created?
There is! Have a look at the help text for pulp-admin rpm repo update.
Summary
===
The Pulp team has published Pulp 2.6.4 which contains a fix for
an important security vulnerability (CVE-2015-5263). Users who use the
pulp-consumer CLI to register consumers to the Pulp server should
upgrade to pulp-consumer-client>=2.6.4. All versions of
pulp-consumer-client from
Bradley Davis wrote:
> Do you think it would be worthwhile to add that note into the
> documentation? Or add a clarification to the general installation
> chapter as well as the nodes chapter? Numerous people on my team read it
> the same way, where resource manager and celerybeat were not to be
Bradley Davis wrote:
> It makes it seems that pulp_resource_manager and pulp_celerybeat should
> not be running on the child node server. When looking at the Nodes
> chapter, neither services are mentioned.
Hello Brad!
Apologies for the confusion. Each node is a complete Pulp installation
that
Dennis Kliban wrote:
> I am actually filing this bug. I was able to reproduce it on my box.
dkliban++!
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
Webb, Reece wrote:
> Sep 16 08:26:19 yummy pulp: celery.worker.job:ERROR: (1822-58784) Task
> pulp.server.managers.repo.publish.publish[e325dd8a-3541-4f10-a5f0-80f6a51f8a19]
> raised unexpected: TypeError("can't compare offset-naive and offset-aware
> datetimes",)
> Sep 16 08:26:19 yummy pulp:
Mihai Ibanescu wrote:
> I am trying to figure out how to lay out the repositories in pulp. I
> suspect the answer is 3 different repos, and creatively/carefully
> copying errata (with their packages) from 6.7 into the 6.5 repo.
This is exactly the way to do it, having separate repositories for
Scott McCarty wrote:
> - Absolutely, is there a guide somewhere on how to start this off?
I don't believe we have any formal process documented for writing a
story, so I'll write some high level stuff here:
0) Use Redmine to file a new issue:
https://pulp.plan.io/projects/pulp/issues/new
1)
Michael Hrivnak wrote:
This is conceptually the same with v1 and v2; they've mostly just
changed terminology.
To clarify a little, in pulp-docker-2.0.0 (not released or even alpha
built yet), we are going to have a new data type called a Manifest.
Rather than interacting with and promoting
of!
[0] https://github.com/pulp/pulp/pull/2005
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJV0lRHAAoJEIyFaKUJtmpiAeoP/RCxAXknOuFS5iFmRSRL88hZ
TI7Wh31x9/gh96wJv/aTenqhSuWe6joUfEOlS/oxiVGnQUcA06+sIYF+W07/S1jG
VXxHVar7f+8R2nXeRbed2+6++YC+VVEvEgKrjXaXu
or tomorrow if possible.
Thanks!
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJV0fL2AAoJEIyFaKUJtmpiWycP/R9fo2t/YmKZ68JiUb0o7nnx
MPI77opHRYRRC/+S4FqVSh5YgYU8IImKaidL1YSm1/EsUtA2Y6DDQqBkq7bkmHoF
T8COde8rzOFJqypIjYfZFMjFZCyU5Yuc93LdLEkUTR8+UW/Uus+nEXWKR8HGwX+E
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I just submitted a pull request that would be nice to get reviewed and
merged very quickly so I can continue on with the publish work. Would
someone mind doing that for me?
https://github.com/pulp/pulp_docker/pull/84
- --
Randy Barlow
-BEGIN
/pulp/pull/1997
[1] https://github.com/pulp/pulp/pull/1998
[2] http://fpaste.org/250707/
--
Randy Barlow
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp
though it announced that it would do it.
Unfortunately, I don't recall enough detail to tell you which exact
settings you will need but I suspect you will need to configure httpd
with SSL terms that the docker client is willing to use.
[0] https://github.com/golang/go/issues/5742
- --
Randy Barlow
… into!
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVkaTTAAoJEIyFaKUJtmpiCFEP/2mklUAVY6ZK2kDV+/hdlPnQ
kqbbjSd1K6LEg9hpeYLAT6oulP6glZrHp9wnnHSxNs2bYusxVNkO2wXzJ60qhbcb
UmdmXcU0NwdxMetN3gYEgsvk7fOWZlLSCi6FS7R81p9kc1hYyagqGv73eP+S54fV
Pj
packages for Fedora 22. If no reasonable objections are brought up,
this change will start with the 2.6.3 and 2.7.0 release streams.
+1
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVivVuAAoJEIyFaKUJtmpimVgP/1P/7PCujxmdYxwnEC7mCBj
) sudo yum/dnf install ansible
3) vagrant up
Let me know if you have any issues!
[0] https://github.com/pulp/pulp/pull/1897
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVea7nAAoJEIyFaKUJtmpiNzgP/i9cypegST0Ugy8ZklWQVsW6
mrLaOSCimjsA1xPO3YoC9
]
http://api.mongodb.org/python/current/api/pymongo/read_preferences.html#pymongo.read_preferences.ReadPreference
[1] https://github.com/pulp/pulp/pull/1864
--
Randy Barlow
write_concern_test.tar.bz2
Description: application/bzip
signature.asc
Description: OpenPGP digital signature
it working. Thanks for the note, and I hope you
enjoy the plugin otherwise!
[0] https://warehouse.python.org/
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVU0rsAAoJEIyFaKUJtmpiaUMP/1YfE0nNIum6EQSobZ0UPUDn
appreciate review soon because yesterday I had to rebase
three times due to commits that other people have been making. I'd
rather not have to solve a bunch more merge conflicts ☺
[0] https://github.com/pulp/pulp/pull/1844
[1] https://github.com/pulp/pulp_rpm/pull/682
- --
Randy Barlow
-BEGIN PGP
. I'm running the command as root.
This is correct, but you don't need to run pulp-admin as any
particular user (such as root) - pulp-admin uses the REST interface to
drive Pulp. Have you logged in with pulp-admin?
$ pulp-admin login
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG
/pulp/admin/admin.conf on or near line 26. Can you check the
syntax in that file? I'm not sure if it means literal line 26, or the
26th line that isn't a comment.
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVQAG6AAoJEIyFaKUJtmpiFyIP/R0iXkDrRd45KE2Q9ZdPWdt2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/28/2015 01:28 PM, Randy Barlow wrote:
fixing the defect it OK in a Y (or even Z) release.
s/defect it/defect is/
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVP8NWAAoJEIyFaKUJtmpipqAQAJuqRNJLKqE
on this broken
behavior anyway since it should not be documented that way.
Either way, it's important to call attention to this change in release
notes.
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVP8MqAAoJEIyFaKUJtmpiF5EP/2e4iNEiAjytcAd9+JhZQTri
c
another perspective on it for us to consider?
[0] https://pulp.plan.io/issues/918
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVPmajAAoJEIyFaKUJtmpi10EQAJ7trvL8sbm9D8rDjC6NTrxT
rvMY/BLctVioq6sGElLmanXuarYYXvBfvpCfpnCBTePOdMPkLMhVPsNYg7jTr9BJ
vf3wkA
for the inspiration, and in particular for writing
dev-setup.sh which got me thinking about this a lot. Also, I stole a
lot of code from dev-setup.sh ☺
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCgAGBQJVNWQpAAoJEIyFaKUJtmpiWVsP/00vQLu+tovxSuMS40u4lzSx
CnMpp9j
the Pulp web server and workers to keep
its RAM usage in a range that you prefer.
[0] https://en.wikipedia.org/wiki/Memory-mapped_file
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJVI+WzAAoJEIyFaKUJtmpiY+AQAJheYId25yXYzv0Z1h4RfiIK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello!
I will be at Pycon this week in Montréal. On Sunday, I will be
presenting Pulp at the poster session. If you are at the conference,
stop by and say hi!
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
need to have a talk where we discuss the two,
and figure out what we can do to combine them so we have only one the
suits everyone's needs. Unfortunately, we have no definite plans to do
this at the moment.
You might be best off to pick the one that meets your needs the best
for now.
- --
Randy
approach would be the only way to achieve
this. You might consider using copy commands to get the contents the
same instead of the sync. If you use sync, the risk is that the feed
changes between syncs, and one repo has slightly different content
than the other.
- --
Randy Barlow
-BEGIN PGP SIGNATURE
, and Pulp. This commit
works around that issue by fully stopping the workers instead of
issuing a restart to them.
https://pulp.plan.io/issues/686
closes #686
[0] https://pulp.plan.io/issues/686
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBCgAGBQJVC1
authority for Pulp to
use to trust the connection:
- --feed-ca-cert=/etc/rhsm/ca/redhat-uep.pem
You can see an example here:
http://pulp-rpm.readthedocs.org/en/latest/user-guide/recipes.html#sync-a-protected-repo
Hope this helps!
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
? For example, in pulp-admin for Yum
repositories, you can use the --feed-ca-cert flag to set the
certificate authority that should be trusted for the sync.
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJVCK3UAAoJEIyFaKUJtmpiXzcP/AuvYdtH+7gpF4i9D/U214H7
isn't a great
solution since they won't have it installed, but I find it works well
for protecting myself when I'm the only user of a service.
- --
Randy Barlow
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJVAxoJEIyFaKUJtmpickMP/RguJvDQrik+KNWQiyBFoA1B
/8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/25/2015 10:37 AM, Chris Duryee wrote:
There is a library that adds import order checking to flake8[1]. Is
this something we can enable for Pulp platform? This would let us
look at one less thing during PR review.
The linter ships with two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/13/2015 01:45 PM, Paul Jochum wrote:
Importer Type Id: iso_importer
I think this is the problem: the repo is not an RPM repo, it's an ISO
repo. It looked like you left off the rpm part of the create
command? Try again with this:
pulp-admin
On 02/11/2015 03:07 AM, Aaron Weitekamp wrote:
At DevConf this week I learned about a free, automated certificate authority
service called let's encrypt[1]. Given the number of pulp servers I've
deployed recently requiring ssl verify false I'm excited to see this. I
assume they'll be
On 02/11/2015 06:46 PM, Borkowski, Dan wrote:
Looks like there is an old RFE for this...
https://bugzilla.redhat.com/show_bug.cgi?id=976032
Hahaha, and I even commented on it. Memory is a funny thing.
signature.asc
Description: OpenPGP digital signature
. I believe it will do what you expect if you
add that flag. Hope that helps!
--
Randy Barlow
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
On 02/03/2015 12:56 AM, Gavin Jones wrote:
-- Processing Conflict: compat-qpid-cpp-client-0.24-19.el7.x86_64
conflicts qpid-cpp-client
-- Finished Dependency Resolution
Error: compat-qpid-cpp-client conflicts with
qpid-cpp-client-0.28-5.el7.x86_64
I experienced this same issue. I found a
On 01/29/2015 03:20 AM, Arnold Bechtoldt wrote:
Can I find the changelog for this upcoming release somewhere?
I'm not sure if this is complete or not, but this is what we have so far:
https://github.com/pulp/pulp_rpm/blob/2.5-testing/docs/user-guide/release-notes/2.5.x.rst
signature.asc
In the meantime, you can at least use https:// URLs to retrieve our
packages, which will help a lot with simple attacks. We look forward to
having full GPG support with our upcoming release!
signature.asc
Description: OpenPGP digital signature
___
On 01/27/2015 05:05 PM, Julien Pivotto wrote:
I have (re)created the logo of Pulp as SVG so we can have a better
resolution than the one on the website.
Please can find it attached to this mail. Credit for the logo does not
go to me, I just converted it to svg using inkscape.
This is great,
On 01/22/2015 11:07 AM, Trevor Vaughan wrote:
It would just be nice to be able to manage all Puppet modules and
Rubygems using the same interface since one begat the other.
Very much agreed, thanks for the note of interest!
signature.asc
Description: OpenPGP digital signature
On 01/19/2015 07:52 PM, Roman Revyakin wrote:
I’ll be looking into different arrangements of the Pulp servers in order
to achieve the redundancy until then.
It's also worth noting that Pulp's Nodes feature is not for redundancy.
It's intended more for distributing Pulp installations across the
On 12/23/2014 11:33 AM, Randy Barlow wrote:
If you are in the Raleigh-Durham, USA region on January 22nd, you might
be interested in attending a talk I will be giving at TriPython, the
local Python user group.
http://tripython.org/Members/cbc/jan-15-mtg
I will be presenting Pulp generally
On 01/12/2015 09:04 AM, Paul Jochum wrote:
Any suggestions on how to fix this?
Can you show us the server side tracebacks? The PulpExecutionException
is unfortunately not a useful one, and it will be the second of two. If
you can show us the traceback that precedes that one, it might be
helpful.
On 01/12/2015 04:50 PM, Paul Jochum wrote:
I also checked, and root was able to write to that filesystem.
Hmmm. Perhaps it would be valuable to ensure that the apache user can
write there? I briefly wondered if it could be an selinux issue since
you are using NFS, but I suspect you'd get a
On 01/07/2015 05:49 PM, ben.stan...@exemail.com.au wrote:
Here is info about where pulp logs things:
https://pulp-user-guide.readthedocs.org/en/latest/troubleshooting.html#logging
The documentation there regarding rsyslogd is incorrect (at least for RHEL7).
Hi Ben,
I filed a bug about this
On 12/23/2014 11:33 AM, Randy Barlow wrote:
If you are in the Raleigh-Durham, USA region on January 15th
Correction: the date is January 22. Thanks to mhrivnak for pointing this
out!
signature.asc
Description: OpenPGP digital signature
___
Pulp-list
On 12/22/2014 11:12 AM, Chris Duryee wrote:
Are there any objections to me removing it from the deps we carry for
Pulp 2.6?
+1 from me.
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
On 12/19/2014 04:19 PM, Michael Hrivnak wrote:
One problem with /var/tmp/ is that some distros, like RHEL, automatically run
tmpwatch to delete files in /var/tmp/ that are older than some amount of time
(I think 30 days is typical). If any pulp job needed to copy in old files
that retained
On 12/15/2014 02:54 PM, Michael Hrivnak wrote:
- Add a new config value in the 'server' section called
'working_directory'. It's default value would be /var/lib/storage
We should have pulp in the path. /var/cache/pulp would be a good choice and
works well with the FHS.
I'll suggest
On 12/17/2014 10:43 AM, Chris Duryee wrote:
done, at least for pulp, pulp_rpm and pulp_python. There are a lot of
repos nowadays:)
Nice!
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
I have published another beta for our upcoming 2.4.4 release. Happy testing!
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Hello!
I have just published the first alpha build (0.0.0-0.0.alpha!) of a new
set of plugins that will allow you to host your own PyPi server with
Pulp. So far it is possible to upload Python packages to a repo, publish
it, and use pip on a client machine to install the package hosted by
Pulp.
On 12/08/2014 02:04 PM, Davis, Daniel P wrote:
Is there a way to avoid using passwords for authentication on the pulp
server? Permanent certificate perhaps?
Yes! If you generated your own certificate signed by a CA that Apache is
configured to trust, you can store the cert+key in the
On 12/04/2014 10:22 PM, ben.stan...@exemail.com.au wrote:
In the source repository, the rpms are all sorted into sub-directories by
letter.
The repository index file references them that way as well.
When I publish the repository from pulp 2.5, it appears on my http server
in a single
Hello!
I have published a 2.4.4-0.1.beta build into our beta and testing
repositories. This build addresses this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1165355
Happy testing, and please let us know what you think!
signature.asc
Description: OpenPGP digital signature
Any other opinions on this?
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
On 11/21/2014 04:32 PM, Jeff Ortel wrote:
Although, I wonder if the 3.0 time frame would be more appropriate.
Thoughts?
I think we can reorganize the docs with any release if we want to. I
don't think that violates semantic versioning. I wouldn't want to do it
to the docs from an already
Our master branch currently has two top level sections in the docs: User
Guide and Developer Guide[0]. I propose that we reorganize the docs to
represent each type of person who might work with Pulp. I can think of
four offhand: administrators, users, integrators (API users), and
contributors
On 11/17/2014 10:18 AM, Michael Hrivnak wrote:
One of the big points of convenience with having the python packages under
one repo is the ability to make one pull request that touches multiple
packages. This is quite common, for example something as simple as adding a
constant to the common
continue having the meta-repo that we have now that brings
these submodules together for convenience.
What do you think?
--
Randy Barlow
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
Here is this week's bug count graph. They've been a bit on the rise over
the past week.
signature.asc
Description: OpenPGP digital signature
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
On 10/31/2014 02:39 AM, Gavin Jones wrote:
Hey Randy,
Thanks for your reply, yes you have some good points.
openssl x509 -in rootca.crt -noout -text | grep -i Version:
Version: 3 (0x2)
openssl x509 -in pulp01.rap.local.crt -noout -text | grep -i Version:
Version:
On 10/29/2014 07:18 PM, Gavin Jones wrote:
openssl req -new -key pulpca.key -out pulpca.csr
*# On the MS Root CA*
http://localrootca/certsrv/
Request a Certificate advanced certificate request
Paste the pulpca.csr Into the Saved Request Section
Certifcate Template: Web
On 10/30/2014 01:48 PM, Miroslav Suchý wrote:
Is it possible to run Pulp on different port than 80? (e.g. 81) And make
it available to localhost?
I want to run on 80 different web server, which is better for serving
static content.
I am afraid that I know the answer because of hardcoded
One note I'll add about intermediary CAs is that they need to be SSL v3
certificates, and they need to be set to the CA type. This is quite
different from root CAs, as most clients assume that a self-signed v1
certificate is a CA.
signature.asc
Description: OpenPGP digital signature
On 10/28/2014 12:32 AM, Gavin Jones wrote:
ConnectionException: (None, 'tlsv1 alert unknown ca', None)
Any more ideas?
This error means your server is signed by an untrusted CA (or is self
signed). You have two (possibly three) choices:
1) Sign the httpd process' SSL certificates with a
On 10/28/2014 09:04 AM, Ashby, Jason (IMS) wrote:
Add your root and intermediary CA's to system CA bundle (copy ca-bundle.crt
out to all consumers too):
openssl x509 -in /etc/pki/pulp_certs/rootca.crt -text
/etc/pki/tls/certs/ca-bundle.crt
openssl x509 -in /etc/pki/pulp_certs/pulpca.crt
On 10/28/2014 09:04 AM, Ashby, Jason (IMS) wrote:
ssl_ca_certificate: /etc/pki/pulp_certs/pulpca_chain.crt
This setting is used as a CA to add to consumer yum repo configs. If you
use a trusted CA certificate in httpd's ssl.conf (recommended), you
don't need this. Also, this does not need to be
On 10/26/2014 09:09 PM, Gavin Jones wrote:
--feed
https://cdn.redhat.com/content/dist/rhel/server/7/$releasever/$basearch/os \
This is the problem - you have to fill out these variables because Pulp
doesn't know which release or arch you want. For example, you could use
7Server and x86_64.
1 - 100 of 231 matches
Mail list logo
