I propose that we leave the 2.4 release locked in at Celery 3.1.9. I don't
think that Celery bug will be on any code paths, and we can upgrade and test
the latest with the 2.4.1 release. What do you think about that?
-Brian
- Original Message -
From: Randy Barlow rbar...@redhat.com
Hi John,
It seems that the connection to the qpid broker is not being made to allow
Celery tasks to be dispatched. The first thing I usually try it to run qpidd
in the foreground with --auth=no as a command line option. That way I know
it's running, and that it knows that auth should be
Is it difficult to add more space to koji.katello.org? I'm trying to determine
if its a matter of cost, or if there is technical complexity.
-Brian
- Original Message -
From: Lukas Zapletal l...@redhat.com
To: foreman-...@googlegroups.com, candle...@lists.fedorahosted.org,
Hi Mark,
This exception is caused by an authentication error with Qpid. I believe you're
missing a package that provides the Cyrus SASL authentication type. This
results in the SASL(-4): no mechanism available: No worthy mechs found
message. I recommend installing cyrus-sasl-plain package, and
Hi Henri. I'm not 100% on the root cause of your problem, but it looks like the
AMQP message that tells the client to bind is being received but rejected.
Could it be that this is an upgrade from a previous version to pulp 2.4? If so,
then it sounds like you need to run pulp-consumer update
I have RTD access, but it only has projects for pulp user guide, pulp dev
guide, pulp rpm user guide, etc for pulp, pulp_rpm, and pulp_puppet. I'm adding
the Pulp Docker User Guide now, and configure the master builder. I'll send out
the URL when I'm done.
There is another guide in the
I only enabled the master builder. Here it is:
http://pulp-docker-user-guide.readthedocs.org/en/master/
-Brian
- Original Message -
From: Brian Bouterse bbout...@redhat.com
To: Randy Barlow rbar...@redhat.com
Cc: pulp-list@redhat.com
Sent: Wednesday, September 17, 2014 9:30:52 AM
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
The new python-kombu-3.0.15-13.pulp is available in Koji [0]. A future Pulp
release (2.5.1) will include this newer version of python-kombu which allows
Pulp to use anonymous authentication with Qpid out of the box without any
adjustments to qpidd.conf. This should make it easier for new Pulp
/enter_bug.cgi?product=Pulp
-Brian
- Original Message -
From: joshi dhaval d_josh...@yahoo.com
To: Brian Bouterse bbout...@redhat.com
Cc: pulp-list@redhat.com
Sent: Tuesday, October 21, 2014 12:13:37 PM
Subject: Re: [Pulp-list] how does this agent commnication works ?
Hello,
if i can use
Are you familiar with the nodes [0] setup of Pulp? If you are trying to manage
content between sites, I would recommend reading it to see if it will meet your
needs. With nodes you could transfer content using a sync of TK repository
content from UK repository content which should perform
I have credentials and can help with this. How about I build out the new
builders first thing in the morning?
+1 to the names you suggest.
Others might not be aware, but we need new builders because we need to leave
the old ones round because we're not backporting this doc merge into the 2.5
With the recent increase in pulp-list traffic that is related to the
development of pulp, I propose that a pulp-...@redhat.com mailing list be
created. This would be configured roughly the same as pulp-list@redhat.com. If
others have thoughts (or just some +1's) let me know.
-Brian
'master' docs for pulp, pulp_rpm, pulp_puppet, pulp_docker, pulp_ostree are
available at the URLs below. These contain the consolidated user and dev guides
as one set of documentation that rbarlow put together recently.
http://pulp.readthedocs.org/en/latest/
Hi Jason,
I've successfully used Qpid over SSL with Pulp 2.4 with port 5671. I see that
you've configured the Qpid side of the SSL connection, but is server.conf for
pulp configured? Refer to the docs [0] for how to configure the Pulp side of
this.
The login portions of Pulp are unrelated to
- Original Message -
From: Jason Ashby (IMS) ash...@imsweb.com
To: Brian Bouterse bbout...@redhat.com
Cc: pulp-list@redhat.com
Sent: Friday, October 24, 2014 11:11:50 AM
Subject: RE: [Pulp-list] Qpid SSL on Pulp 2.4
Hi Brian,
Thanks for the reply. For now, I'll ditch
Two things jumped out at me that I wanted to comment on:
snip
Is there anything obvious now outstanding I have diabled selinux in the
meantime.
I think this is a good idea.
Also Even If I want to skip SSL, I still have grief:
vim /etc/pulp/admin/admin.conf
verify_ssl = False
This
Are you interested in the upcoming Pulp versions that are being developed? Do
you want to know if its safe to upgrade to these new versions without your Pulp
installation breaking? Read more about these topics at the blog post [0]. Also
developers who have forks or local checkouts should read
-
From: Steven Roberts strob...@strobe.net
To: Brian Bouterse bbout...@redhat.com
Cc: Mark Keller mdkel...@gmail.com, pulp-list@redhat.com
Sent: Tuesday, November 25, 2014 12:29:56 AM
Subject: Re: [Pulp-list] Pulp upgrade from 2.3 to 2.4 issues
On Mon, Nov 24, 2014 at 05:18:08PM -0500
Hi Paul,
Mongo does have a 16MB document limit [0], and this repo must have metadata
that is a little larger than that. I was able to reproduce this bug, and I
documented it here [1]. I did find some old BSON related Pulp bugs [2] [3], but
those all seemed to be resolved so [1] is the only
A couple of thoughts:
I'm glad you brought this up. This is something we need to do! I think
reorganizing these docs is important to do as part of 2.6.0 because in 2.6.0 we
switched from using two sphinx [0][1] projects to one [2]. That change caused
the left side to look completely different
Hi Ben,
Here are some thoughts that may help you identify the problem. Migration 0009
tries to connect to the broker, so its likely that Pulp cannot successfully
connect to Qpid.
- I typically don't set anything in /etc/sasl2/qpidd.conf. Perhaps that feature
is not working as expected. The
Hi Gregory,
I don't believe Pulp can apply permissions [0] to a specific repo. It can limit
a user to specific actions for a general type of thing (ie: a repo), but it
can't limit repo A versus repo B. I hope this will be expanded in the future.
I'm not sure if there is a specific RFE for this
To my knowledge, there isn't a great way to do this in Pulp currently, but I
believe there is a workaround. If you set the user_cert_expiration parameter in
the [security] session to a large number and restart all of your pulp related
processes then the next time you use pulp-admin to acquire a
The robots.txt rule was planned but never got put into place, so the v1 docs
are still publicly indexed and searched. The BZ [0] is still in the assigned
state.
[0]: https://bugzilla.redhat.com/show_bug.cgi?id=1155271
-Brian
- Original Message -
From: Randy Barlow rbar...@redhat.com
Hi Alex,
Usually the 'no mechanisms agreed' is due to Pulp not being able to communicate
with the Qpid broker using SASL. This is typically caused by either a package
being missing on the Qpid broker machine or the SASL database and/or Qpid's use
of SASL is misconfigured. This Pulp docs
Message -
From: R P Herrold herr...@owlriver.com
To: Pulp mailing list pulp-list@redhat.com, Brian Bouterse
bbout...@redhat.com
Sent: Wednesday, February 18, 2015 2:45:57 PM
Subject: Migration from Bugzilla to Redmine
On Wed, 18 Feb 2015, Brian Bouterse wrote:
The Pulp community
Hi Alan,
The PR history is a little misleading associated with BZ 1141336. The bug
target release is 2.6.0 which is correct, the rabbitMQ fix is only in 2.6.0. It
was merged to 2.5-dev in preparation to be included with 2.5.1. We had features
that also were committed to 2.5-dev which required
,
I'll respond directly to you with details about your account.
[0]: https://pulp.plan.io/account/register
-Brian
- Original Message -
From: Cristian Falcas cristi.fal...@gmail.com
To: Brian Bouterse bbout...@redhat.com
Cc: pulp-list@redhat.com
Sent: Sunday, March 1, 2015 11:39:31 AM
- Original Message -
From: Brian Bouterse bbout...@redhat.com
To: pulp-list@redhat.com
Sent: Thursday, February 26, 2015 5:57:37 PM
Subject: [Pulp-list] Pulp Migration to Redmine Moved to Saturday 2/28 at
20:00 UTC (3pm EST)
The Pulp migration to Redmine has been moved to Saturday 2
All non-CLOSED bugs and feature requests will be migrated from Bugzilla to
Pulp's Redmine instance [0] starting at Tuesday 2/24 @ 6pm EST. The migration
is expected to last a small number of hours, which should allow for enough time
to address any unexpected data quality issues that may come up
The issues that postponed the Pulp migration from Bugzilla to Redmine have been
resolved. The migration of all non-closed Pulp bugs and RFEs is planned for
Thursday 2/26 @ 23:00 UTC (6pm EST). The Bugzilla Pulp tracker [0] will not
allow new bugs to be filed starting on Friday 2/27 at 14:00 UTC
The Pulp migration to Redmine has been delayed due to several data quality
issues with the production data that did not show up in test migrations. These
errors prevent us from starting the migration until these are resolved. It will
be rescheduled for a planned time in the near future. Please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It looks like the machine you are running pulp-admin on is not
authenticated with the server. As such pulp is denying the request
saying that your user doesn't have enough permissions. Try logging in
explicitly with pulp-admin and then retry your repo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently, a lot of Pulp developer discussion happens in places other
than pulp-list. We are thinking of re-directing those conversations to
pulp-list, but it can get pretty technical. It would increase the
amount of traffic to pulp-list, and those
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Using a shared AMQP instance should be safe as long as a dedicated
exchange is used.
- -Brian
On 04/27/2015 07:26 AM, Tomas Tomecek wrote:
Quoting Chris Duryee (2015-04-24 19:31:53)
On 04/24/2015 08:51 AM, Michael Hrivnak wrote:
Tomas,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ben,
Regarding the tasks getting stuck, what version of Pulp are you running?
- -Brian
On 05/04/2015 02:03 AM, ben.stan...@exemail.com.au wrote:
As I have created a script to create my repos, and it seems to
cause pulp a lot of trouble, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Frédéric,
I recommend manually cancelling tasks that are stuck at the waiting
state. Also you can read more about that and other techniques to get
tasks unstuck in this recent pulp-list e-mail [0].
[0]:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thanks for the bug report. I turned it into this issue which will be
included in the upcoming 2.6.1 release.
[0]: https://pulp.plan.io/issues/935
- -Brian
On 05/01/2015 04:26 AM, ben.stan...@exemail.com.au wrote:
I installed my pulp system
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ben,
Pulp uses many processes which can cause concurrent writes to the log,
but it doesn't use very much multithreading. One thing you can do is
work with your syslog daemon to include the process ids with your log
files. This will help identify
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Ben,
The tasking system was significantly improved with 2.6.x versus 2.5.x,
but here are some recommendations that you can use on 2.5.x.
use pulp-admin to list tasks: `pulp-admin tasks list`. The list is
long and the ordering isn't as you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I don't use that command much myself, but all admin-client should
provide usage information with --help.
- -Brian
On 05/10/2015 11:38 PM, ben.stan...@exemail.com.au wrote:
Hi,
I need to configure a second pulp server that is disconnected from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Frédéric,
A couple of things to check. Make sure that pulp_workers,
pulp_resource_manager, and pulp_celerybeat are running, and ensure
that the logs don't show errors when they start. Potentially
restarting these services would be good.
After
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I generally think Mongo is going to be using significantly more memory
than pulp processes.
IIRC, the celery log files you referenced only log for a brief moment
in time before all logs redirect to syslog. See [0] for Pulp's logging
docs.
FYI there
. Should I expect maybe 3-4 workers at any one time? I've
got 2 now, but that is at an idle state.
On Mon, Jun 22, 2015 at 9:24 AM, Brian Bouterse
bbout...@redhat.com mailto:bbout...@redhat.com wrote:
Hi Sean,
I'm not really sure what you mean by the term 'children'. Maybe
you mean
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I merged a commit [0] to 2.7-testing (2.7.0) which updates pymongo to
2.7.2 and mongoengine to 0.9.0. When you are developing on Pulp 2.7.0
or later your developer environment needs to be using at least these
versions.
These rpms will be available
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've written up a tracker task [0] outlining a new feature to allow
Pulp to sync content lazily. That tracker task has ~20
subtasks/stories that outline the implementation work. Please comment
on any of these with questions or suggestions for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Daryl,
I better understand what you are asking now. To have more control over
the format of the e-mail you receive, I'll recommend the following
approach:
0. Configure Pulp to use the AMQP notifier [0].
1. Write a small program that listens for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've compiled a few bugs/stories/refactors to outline short-term
improvements to Pulp's usage of MongoDB. These are all subtasks of a
tracker task [0]. If you are interested in this topic, please read the
stories to ask questions or leave comments
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The Pulp project's branching strategy is being simplified [0], and the
x.y-testing branches are no longer needed. All x.y-testing branches
will be deleted on Friday Oct 23rd from all pulp repos [1].
Currently, there are no open pull requests
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This doc is really good! Thanks for writing it up. I put several
comments [0] on it just now for some more clarity/ideas. Please read
all comments before responding since I had some ideas later that may
obsolete some of my earlier comments.
We can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
FYI, I've put in a proposal to redo the upload API in a way that would
allow an upload once, associate many use case.
The main design story: https://pulp.plan.io/issues/892
Two related stories:
https://pulp.plan.io/issues/894
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I personally haven't used Pulp with /var/lib/pulp hosted on glusterfs,
but it should work. I've heard from others that they've specifically
done it, and that it worked for them.
The clustering guide [0] outlines Pulp's storage system requirements
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A change [0] has been merged to master which may require updates from
plugin authors. Specifically, if you've written a plugin unit which
subclasses the mongoengine based ContentUnit, two fields are changing
names.
The field named 'source_location'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
+1 to this idea. +1 to drawing the upgrade line at 2.5.X.
Is there some way we can halt the user's upgrade using the spec file
so that they know they need to upgrade to 2.5.0 first? Maybe in one of
the pre stages?
Would we do this for all the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Alan,
I may not fully understand your question with regards to the term
metadata, but this sounds related to the consumer groups API [0]. That
API provides the ability to group consumers together, bind them to
repositories, and install content
Jason and Jeffrey,
Thanks for reporting this. I've written up a bug [0] and I am
investigating the root cause.
On the bug are you able to leave some answers to these questions?
- Can you confirm that it affects both RabbitMQ and Qpid usage?
- Can you confirm that the workers "go missing" and
This issue has been resolved through the creation of a new Qpid repo for
EL6 bits [0]. This new repo contains a newer version than the 0.26 Qpid
bits Pulp has distributed for EL6 in the past. All Qpid users who
received their Qpid bits through the pulp repo are recommended to
upgrade at their
Hi Radu,
>From the traceback I can see your server.conf is still configured to use
Qpid. Revisit your server.conf settings to configure Pulp to work with
RabbitMQ.
-Brian
On 12/22/2015 12:37 PM, Radu Coroi wrote:
> I'm trying to setup Pulp 2.7.1 with RabbitMQ and I was able to create a
> new
-server
> - Every 60 seconds for me as well. /var/log/messages loos as below.
>
> -Jeffrey
>
>
>
>
>
> -----Original Message-
> From: pulp-list-boun...@redhat.com
> <mailto:pulp-list-boun...@redhat.com>
t;
> Can these be merged?
>
> On Wed, Nov 18, 2015 at 9:05 AM, Brian Bouterse <bbout...@redhat.com
> <mailto:bbout...@redhat.com>> wrote:
>
> Jason and Jeffrey,
>
> Thanks for reporting this. I've written up a bug [0] and I am
> investigating
In converting to mongoengine, we have not yet thought through this
problem. I agree with your two approaches and assessment.
Using the UTCDateTimeField is a good short term solution because it will
be simple to implement. By doing the timezone conversion in to_python()
we can avoid littering the
Hi Radu,
I haven't tested this myself, but I suspect the value you are using for
build_time does not match up with how the database thinks of time. When
I look at an RPM in my pulp development database I see this snippet:
"build_time" : 1331831373,
I suspect that your criteria request is not
Yes these records are purged. There are some docs about it here[0]. It
is configurable and you can use these settings[1] in your server.conf.
[0]:
http://pulp.readthedocs.io/en/latest/user-guide/admin-client/tasks.html#listing
[1]:
The Pulp development team does 3 week sprints and intends to demo new
features and notable bugfixes after each one. These demos are recorded
and will be shared via pulp-list.
Here are two demos in one e-mail: (1) the one from 3 weeks ago and (2)
the demo that occurred today. Both demos focus
The Pulp team is happy to announce the availability of a new
documentation site for Pulp and its plugins.
Latest (2.8.4 currently): https://docs.pulpproject.org/
All versions: https://docs.pulpproject.org/en/
== Improvements ==
* Finding the documentation you need is easier with
+1 to this idea.
Also, there is an task to create a "contrib" area for Pulp [0]. It would
be great to see some of these things (especially scripts) move into an
install-able package.
@jcline, would you be able to comment on [0] with a recommendation for
which repo it should be kept in and
We want to make getting code into Pulp as efficient as possible.
Shortening the code review time is one area we can improve.
To that end, jortel had an idea to have a bot auto assign PRs to a
reviewer once they are opened. I've summarized here [0] what I've heard
from several people regarding
see inline
On 01/27/2016 01:21 PM, Lesley Kimmel wrote:
> All;
>
> I am attempting to secure Satellite/Katello per DoD security guidance.
> The first few items I need to do is to limit incoming connections and to
> enable access control. Along those lines can anyone answer:
>
> a) How many
I wasn't sure of the answer, so I asked someone via IRC who I thought
would know. They told me:
"There is no easy way to get the feeds. if you have the product certs in
hand you can use `rct cat-cert ` to list the contents
including the directories. If you have a system subscribed to an
Generally upgrades should be that easy. We write the release notes for
each release, based on the specific changes reading those thoroughly
will give you the best result.
Some releases will come with disk migrations, but most won't so I don't
expect any ballooning of disk space. Trying a test
A few months back, the Qpid team started publishing Qpid bits in a
dedicated repo for EL6. We recommended Pulp users who want to use Qpid
on EL6 receive their Qpid bits from that repo.
We still recommend that, but since then, they have modified the URL
where it is published. To continue receiving
In late 2015, a deadlocking issue was found in one of Pulp's
dependencies, python-qpid, which would cause Pulp tasks to become
"stuck". That issue is believed to be fixed, if you are running the
right [0] versions of python-qpid.
We want to make sure this has been fully fixed. To that end, we
You know what's great? Knowing how code changes affect performance of a
software project over time. To use an example from a completely separate
project, here are performance benchmarks published by the Lucene
project[0]. Click on the links in the "Results" section of that page to
see the graphs.
A symlink issue was introduced with 2.8.0, but it's symptom is
observable when serving content and not with sync/publish issues[0].
This looks like a separate issue. Can you file an issue against Pulp and
include the specific AVC denials you are encountering? Also showing the
symlink link and
There is a known issue [0] introduced in 2.8.0 which will cause your
tasks to become stuck at waiting. This occurs after Pulp runs normally
for hours or days.
A fix is completed but won't be released until Pulp 2.8.3 is released.
The good news is, you can resolve that issue now by upgrading
an.io/issues/1832
-Brian
On 04/08/2016 03:15 PM, Matthew Madey wrote:
> When I checked on the state, the status was "not started". I think
> that's why it remained stuck after reboots and bouncing the services.
>
> On Fri, Apr 8, 2016 at 1:27 PM, Brian Bouterse <bbout.
> tool wasn't used, but I can try it (if it's valuable for you).
>
> On Wed, Mar 23, 2016 at 3:23 PM, Brian Bouterse <bbout...@redhat.com
> <mailto:bbout...@redhat.com>> wrote:
>
> Hi Vaclav,
>
> The bug #1749 was fixed in the 2.8.0 Pulp release. What v
Oleg, As I understand it rpm repositories don't support versioning, and
generally RHEL repos are constant being updated with new/better content.
Given that, unless there is a feed available for specifically RHEL 6.6 I
don't know of a way to do this today with Pulp.
One option is to sync a repo
Hi Vaclav,
The bug #1749 was fixed in the 2.8.0 Pulp release. What version of Pulp
are you running? Also we don't support upgrading from one beta to
another. Did you upgrade your system directly from a GA release to
another GA release?
Did you run the pre-upgrade data validation tool[0]? What
For those in Raleigh, I'm going to see Michael DeHaan give a talk[0] at
NCSU in a few weeks. If you want to come with me, let me know.
[0]: https://csc.ncsu.edu/news/1856
___
Pulp-list mailing list
Pulp-list@redhat.com
I've recently talked with two Pulp users in #pulp who have tried to use
pulp_deb with pulp-server 2.8.0. From those conversations I know that
pulp_deb is incompatible with pulp-server 2.8+ due to changes to the
Pulp internals between 2.7-> 2.8 related to mongoengine.
Several of us have fixed
> <http://srpadinf0244.mgt.insim.biz:5672//>
>
> May 04 05:11:07 mysrv pulp[4776]: kombu.transport.qpid:INFO:
> Connected to qpid with SASL mechanism ANONYMOUS
>
> Hint: Some lines were ellipsized, use -l to show in full.
>
> __ __
>
> __ __
>
> # systemctl status p
I've updated the language on [0] to incorporate recent discussion of
story review and marking them "groomed".
-Brian
On 05/03/2016 10:20 PM, Dennis Kliban wrote:
> I have received some feedback on the proposed story grooming process. I have
> made some changes based on that feedback and moved
>
> May 04 05:11:22 mysrv celery[4798]: - ** -- .> results:
> disabled
>
> May 04 05:11:22 mysrv celery[4798]: - *** --- * --- .> concurrency: 1
> (prefork)
>
> May 04 05:11:22 mysrv celery[4798]: -- ***
>
> May 04 05:11:22 mysrv celery[4798
Kodiak is right that the second task stuck at "Waiting to Begin" is
likely waiting behind another operation on that same repo. Canceling the
one prior will likely allow the later one to start.
How many workers are running and how many do you expect? You can see
what Pulp thinks with: `pulp-admin
t only found it in /var/log/httpd/ssl_access_log
>> and /var/log/httpd/ssl_request_log (lines like:
>> /var/log/httpd/ssl_access_log:135.1.215.52 - - [12/Apr/2016:15:04:17
>> -0500] "GET /pulp/api/v2/tasks/f3a4a828-1a98-4d30-989f-a8f62acc29f9/
>> HTTP/1.1" 200 579
>>
>&g
Did this ever get resolved? If not, would you be willing to file a bug
with reproducer instructions in the bug tracker[0].
[0]: https://pulp.plan.io/
-Brian
On 04/02/2016 04:42 PM, Konstantin M. Khankin wrote:
> Hello!
>
> I have sync schedules set up for repos I host locally with pulp. For
>
The Pulp project is moving its weekly bug triage to an IRC meeting
format. This allows anyone to participate and discuss Pulp bugs being
triaged. The meeting will be in #pulp-dev on Freenode at 10:30 am ET and
will follow the documented format[0].
Join fellow Pulp users and developers as we
ut be sure that you're running the latest python-kombu rpm as
discussed here[2].
[0]: https://pulp.plan.io/issues/1363
[1]: https://pulp.plan.io/issues/1838
[2]: https://www.redhat.com/archives/pulp-list/2016-April/msg00020.html
-Brian
On 04/15/2016 03:26 PM, Brian Bouterse wrote:
> I'm ve
I generally recommend picking a recent x.y release and always staying
current on its z stream updates (i.e 2.8.6). I also recommend upgrading
y releases often because we are releasing smaller changes, more often
now and new features come with y releases along with updates. Also,
security
They generally should work together unless there are new features that
you are trying to use in the 2.9.0 client which the 2.8.6 server cannot
honor.
The release notes [0] should call out these new features or you can look
in the tracker with a query like this one [1] for 2.9.0 "stories" (aka
I'm familiar with this limitation. You can manually delete them [0], but
there is nothing in Pulp which cleans these up automatically as far as I
know.
Pulp does have a monthly maintenance [1] codepath which could also
delete unimported content. It could look for files older than some
tps://docs.pulpproject.org/en/X.Y/testing/
Nightly docs for X.Y: https://docs.pulpproject.org/en/X.Y/nightly/
2.7 docs are here: https://docs.pulpproject.org/en/2.7/
2.6 docs are here: https://docs.pulpproject.org/en/2.6/
Pre 2.6 docs are available via source.
-Brian
On 06/21/2016 10:28 AM, Brian Boute
For those interested in what's likely coming with Pulp 2.10, here is the
Sprint 4 demo video.
http://www.pulpproject.org/2016/07/07/sprint-demo-4-july-7-2016/
-Brian
___
Pulp-list mailing list
Pulp-list@redhat.com
I've put together a new pulpproject.org site. I'm planning to put it
into production sometime near July 20th, but I wanted to share a preview
now so I could get some feedback before it launches.
You can preview the site here [0]. You can see a demo of the site here
[1] at minute 7:53.
==
For those interested in what's likely coming with Pulp 2.10, here is the
Sprint 5 demo video.
http://www.pulpproject.org/2016/07/28/sprint-demo-5-july-28-2016/
-Brian
___
Pulp-list mailing list
Pulp-list@redhat.com
+1 to using contrib in favor of pulp_contrib, and similar for other new
repos.
My reasoning is based on optimizing the common case. It's very common
for people to work with Pulp repos everyday so having a cleaner name is
nice. The uncommon case is when it's forked AND a user doesn't know
I'm trying to understand if the pain point is related to downtime or
total runtime.
For instance, what if these migration could be run as a pre-migration
step, ahead of time while Pulp was still online? The upgrade would still
take just as long but you could use your (in this case) 2.6
, the tough part is having to distribute that
backwards. Pulp would have to distribute it back to 2.6, and Katello
would have to push out patches to our 2.4 release channel.
Eric
On Fri, Jul 1, 2016 at 11:14 AM, Brian Bouterse <bbout...@redhat.com
<mailto:bbout...@redhat.com>> wrote:
1 - 100 of 301 matches
Mail list logo
