Pulp 2.5.0-0.11 has been published to the beta repositories. Here is the
changelog:
1009429 - Don't verify FS permissions with httpd.
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
+1
- Original Message -
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
Pulp 2.5.0-0.14 has been published to the beta repositories. Here is the
changelog:
- 1153344 - verify_ssl default to true. (rbar...@redhat.com)
- 1153344 - Support Mongo SSL on the result backend. (rbar...@redhat.com)
The jenkins test infrastructure was failing . I was unable to test this
What we have now:
- Storage directory defined here [0]
- The above value is used to create a path for working directories here [1]
Proposed changes:
- Add a new config value in the 'server' section called 'working_directory'.
It's default value would be /var/lib/storage
- Change
- Original Message -
- Original Message -
From: Dennis Kliban dkli...@redhat.com
To: pulp-list pulp-list@redhat.com
Sent: Monday, December 15, 2014 2:37:35 PM
Subject: [Pulp-list] working directories proposal
What we have now:
- Storage directory defined here
Pulp 2.5.2-0.4.rc is now available in the beta repo. This release candidate
addresses the following bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1175818
https://bugzilla.redhat.com/show_bug.cgi?id=1179463
https://bugzilla.redhat.com/show_bug.cgi?id=1178920
- Original Message -
Hello,
I'm pretty new to Pulp and I created an rpm repo with a feed from RHN.
I created a schedule to have it download any new released updates, but it
seems like that doesn't work. Is there any logging where I can look at the
scheduled runs? Or do I need to
2.4.4-0.4.rc has been published to the beta repo. This release candidate
addresses the following bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1176261
https://bugzilla.redhat.com/show_bug.cgi?id=1171280
https://bugzilla.redhat.com/show_bug.cgi?id=1165355
Pulp 2.5.2-0.3.beta is now available in the beta repo. This beta addresses the
following bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1171278
https://bugzilla.redhat.com/show_bug.cgi?id=1159040
___
Pulp-list mailing list
Pulp-list@redhat.com
Pulp 2.5.2-0.2.beta is now available in the beta repo. This release addresses
the following issues:
https://bugzilla.redhat.com/show_bug.cgi?id=1179463
https://bugzilla.redhat.com/show_bug.cgi?id=1171278
https://bugzilla.redhat.com/show_bug.cgi?id=1159040
I was supposed to be on PTO, but my plans fell through. So back to Pulp I go!
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
This sounds like a good RFE to file. Though there might be already one there.
- Original Message -
Hi,
I have a repo group of rpm repos that I am exporting to ISOs. I am then
importing those ISOs into an iso repo. Is it possible to have the export
operation directly import into
Pulp 2.6.1 is available at the usual location [0].
The release notes can be found here [1]
[0] https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/
[1]
http://pulp.readthedocs.org/en/latest/user-guide/release-notes/2.6.x.html#pulp-2-6-1
Hello everyone. I hope someone could help me with this.
Since i dont want to rely on a single server (for resiliency reasons). I
triied to configure a child pulp node but i'm stuck with some Oauth
authentication failure that instst triing to use ssl:
I am not sure about your nodes problem,
Pulp 2.6.2 beta is available at the usual beta location[0]. Happy testing!
This release contains fixes for the following:
- Platform -
https://pulp.plan.io/projects/pulp/issues?utf8=%E2%9C%93set_filter=1f%5B%5D=cf_4op%5Bcf_4%5D=%3Dv%5Bcf_4%5D%5B%5D=2.6.2
- RPM Support -
Pulp 2.6.2 is now available. This release contains mostly bug fixes [0].
The rpm sync operation has been improved in this release. The sync process
checks the revision number in upstream metadata to determine if it has changed
since the previous sync. If not, most steps in the sync will be
Now that Fedora 22 is out, the maintenance period for Fedora 20 is coming to an
end [0]. I propose that Pulp project stops building packages for Fedora 20. At
the same time we should start building packages for Fedora 22. If no reasonable
objections are brought up, this change will start with
The 2.6.3 beta is now available at the usual location [0]. This release
contains some bug fixes [1].
[0] - https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.6/
[1] -
https://pulp.plan.io/projects/pulp/issues?utf8=✓set_filter=1f%5B%5D=cf_4op%5Bcf_4%5D=%3Dv%5Bcf_4%5D%5B%5D=2.6.3
The latest 2.7.0 beta is now available in the usual location [0]. This beta has
packages for Fedora 21, Fedora 22, EL5 (consumer), EL6, and EL7. Happy testing!
[0] https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.7/
___
Pulp-list mailing list
I am happy to announce that we have another 2.7.0 beta available in the regular
location [0]. This repository contains the following and their dependencies:
Pulp 2.7.0 beta
RPM plugin 2.7.0 beta
Puppet plugin 2.7.0 beta
OSTree plugin version 1.0.0 beta
Python plugin version 1.0.1
Docker plugin
I am very glad to announce that Pulp 2.6.5 beta is now available in it's usual
location [0]. This repository contains the following and their dependencies:
Pulp 2.6.5 beta
RPM plugin 2.6.5 beta
Puppet plugin 2.6.5 beta
Python plugin version 1.0.1
Docker plugin version 1.0.2
Crane version 1.1.0
I am happy to announce the availability of Pulp 2.7.0 release candidate in the
regular location [0]. This repository contains the following and their
dependencies:
Pulp 2.7.0 rc
RPM plugin 2.7.0 rc
Puppet plugin 2.7.0 rc
OSTree plugin version 1.0.0 rc
Python plugin version 1.0.1
Docker plugin
I am very glad to announce that Pulp 2.6.5 release candidate is now available
in it's usual location [0]. This repository contains the following and their
dependencies:
Pulp 2.6.5 rc
RPM plugin 2.6.5 rc
Puppet plugin 2.6.5 rc
Python plugin version 1.0.1
Docker plugin version 1.0.2
Crane version
Yesterday
- removed the testing branches from all the projects
- merged pulp-ostree testing branch into dev branch as part of ^
- packaged and published Pulp 2.7.0 RC
- realized that since I built pulp-ostree from the dev branch for the
previous beta, the release notes were not present
Pulp team is pleased to announce the release of Pulp 2.6.5. It is available in
the 2.6 repository[0]. This release contains several bug fixes [1-3].
Please note that qpid, a pulp dependency, is currently broken on EL6. We will
send a follow up email when an updated version will become
- Original Message -
> Hello,
>
> When trying to download modules from our local forge with puppet 3.8, the
> returned code from pulp is 401:
I believe you can only use the latest client with Pulp 2.7.0. Which version of
pulp-server and pulp-puppet do you have installed?
-Dennis
>
>
Could you please file an issue at
https://pulp.plan.io/projects/pulp_rpm/issues/new ?
Thanks,
Dennis
- Original Message -
> Actually i have to correct myself.. everything works just fine.
> The issue i had was due the fact that those rpm's was not available in the
> repositories
I'd like to thank everyone who provided feedback on the previous 2.7.0. We have
fixed the issues that were reported and published the new RPMs at their regular
location [0]. This repository contains the following and their dependencies:
Pulp 2.7.0 beta
RPM plugin 2.7.0 beta
Puppet plugin 2.7.0
- Original Message -
I just setup a Pulp server, and finally figured out how to setup the repo
sync. Documentation does not say were the downloaded rpm's will be put, or
how to size the appropriate file system. I initiated an repo sync of RHEL
6.x.
There are over 15,000 RPM's to
You can find the latest Pulp 2.6.3 Release Candidate in the usual location [0].
- Dennis
[0] https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.6/
___
Pulp-list mailing list
Pulp-list@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
The repository for Pulp 2.6.3 [0] published on Friday mistakenly contained a
previously released 1.0.0 version of python-crane. The repository has now been
updated with python-crane 1.1.0.
- Dennis
[0] https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.6/
This beta contains a few bug fixes in platform and RPM plugin. The list can be
found here [0-1]. The packages are available at their regular location [2].
Happy testing!
- Dennis
[0]
- Original Message -
> Hey folks,
> The Red Hat bugzilla lists a bunch of community projects, even "PulpDist"
> which I'd never heard of, but there is no heading for just "Pulp" - where
> can I file a minor bug I found in 2.7.0-1?
https://pulp.plan.io
> Thanks!
> - Kodiak
>
>
- Original Message -
> I'm walking through the latest docs for 2.7.0-1 and it's not clear if the
> Pulp server I'm setting up can be a pulp-consumer of itself.
This is how I test the consumer code on my development environment. Seems like
you should be able to do the same thing for your
- Original Message -
>
>
> Hello,
>
> Is there a way to add a password when the remote repo requires
> authentication? For example –
If you are talking about basic auth, then you can add to the feed URL.
--feed=http://privateuser1:passw...@private.testsite.com/private/testrepo
If
[0]
http://pulp-puppet.readthedocs.org/en/2.7-release/tech-reference/forge_api.html
>
> Thanks,
> Dennis
>
> [0] https://pulp.plan.io/issues/1378
>
> >
> >
> > On Mon, Nov 16, 2015 at 5:11 PM, Dennis Kliban <dkli...@redhat.com> wrote:
> >
> > &
- Original Message -
> I forgot to mention that we have upgraded to 2.7
I just got to trying this out myself. I filed this issue [0] to track the
problem.
Thanks,
Dennis
[0] https://pulp.plan.io/issues/1378
>
>
> On Mon, Nov 16, 2015 at 5:11 PM, Dennis Kliban <dkl
This is great! I am glad to see us releasing more often.
- Original Message -
> For bugfix releases (also known as "z" releases due to the incrementing
> of the number in the "x.y.z" version representation), we're changing the
> process slightly, as indicated in the subject of this mail.
The first 2.8.0 beta is now available at it's usual location[0]. This release
contains the following packages and their dependencies:
Pulp 2.8.0 beta
RPM plugin 2.8.0 beta
Puppet plugin 2.8.0 beta
OSTree plugin version 1.1.0 beta
Python plugin version 1.0.1
Docker plugin version 2.0.0 beta
RHEL 7. Seems not to be in EPEL...
You need to enable the 'extras' repo.
>
> -----Ursprüngliche Nachricht-
> Von: Dennis Kliban <dkli...@redhat.com>
> Gesendet: Do 28.01.2016 18:42
> Betreff: Re: [Pulp-list] Pulp 2.8.0 beta 3 is available
> An: pu
Pulp 2.8.0 beta 2 is now available in the usual location[0]. This release
contains the following packages and their dependencies:
Pulp 2.8.0 beta
RPM plugin 2.8.0 beta
Puppet plugin 2.8.0 beta
OSTree plugin version 1.1.0 beta
Python plugin version 1.1.0 beta
Docker plugin version 2.0.0 beta
- Original Message -
> Some of the known issues that are worth highlighting:
>
> * Pulp can only run with SELinux in permissive mode
> * Nodes syncing is not working
Please disregard the note about nodes not syncing. This functionality has been
fixed in this release.
>
>
>
Pulp 2.8.0 beta 2 is now available in the usual location[0]. This release
contains the following packages and their dependencies:
Pulp 2.8.0 beta
RPM plugin 2.8.0 beta
Puppet plugin 2.8.0 beta
OSTree plugin version 1.1.0 beta
Python plugin version 1.0.1
Docker plugin version 2.0.0 beta
Crane
Pulp 2.8.0 Release Candidate can be found in the usual beta location[0]. The
release notes can be found here[1-6].
Note:
EL6 users wishing to use Qpid can get the latest Qpid packages by following
instructions[7] sent out recently on this mailing list.
EL6 users will temporarily need to
- Original Message -
> When trying to install the pulp consumer for RHEL 6, it seems that
> python-quid is not available. Is there a work around for this?
On EL 6 you need to enable the Qpid Copr repo. More info can be found here[0]
[0] http://qpid.apache.org/packages.html#epel
>
>
Thanks for reminding me. I have updated the upgrade instructions.
-Dennis
- Original Message -
> Documentation is still proposing to remove pulp-server package. I suppose it
> should be fixed :)
>
> 2016-04-05 23:15 GMT+03:00 Jeff Ortel < jor...@redhat.com > :
>
>
> -BEGIN PGP
- Original Message -
> Hello,
>
> I'm not sure if this topic was already discussed here but I would really
> appreciate if Pulp would be possible to install with a different web server
> than Apache - for example Nginx.
>
> This would require to create extra packages containing only the
Is goferd running?
- Original Message -
> Hi - I am new to pulp. I have a working pulp repo and I am able to
> successfully bind consumers to the repo and bind to the repositories as long
> as the servers I'm binding are on the same vlan. However, I have a bunch of
> servers on different
This is our best 2.8.0 beta to date! You can find it in it's usual location[0].
Release notes can be found here [1-5].
EL6 users wishing to use Qpid can get the latest Qpid packages by following
instructions[6] sent out recently on this mailing list.
[0]
Pulp 2.8.0 beta 8 can be found in it's usual location[0]. The release notes can
be found here[1-6].
EL6 users wishing to use Qpid can get the latest Qpid packages by following
instructions[7] sent out recently on this mailing list.
[0] https://repos.fedorapeople.org/pulp/pulp/beta/2.8/
[1]
- Original Message -
> Hello Guys,
>
> Recently i planned to configure pulp on my rhel 6, but unable as there seems
> to be dependency problem while executing "yum groupinstall
> pulp-server-qpid". Did lotof search in google, but unlucky. My RHEL is
> registered through
As Pulp is being developed, the latest changes are packaged on a nightly basis.
When a build succeeds, the packages are published to
https://repos.fedorapeople.org/repos/pulp/pulp/testing/automation//stage/
After the packages are published, they are installed and automated tests are
run.
I have received some feedback on the proposed story grooming process. I have
made some changes based on that feedback and moved the content to a public
etherpad[0].
The main difference from the first version is the lack of the "groomed" state
for a story. Once the author thinks a story has all
> So something like:
>
> https://repos.fedorapeople.org/repos/pulp/pulp/nightly//
> 2016-04-22/
> https://repos.fedorapeople.org/repos/pulp/pulp/tested-nightly//
> 2016-04-22/
>
> And then there could be:
>
> https://repos.fedorapeople.org/repos/pulp/pulp/nightly//latest/
>
Yesterday
* set up build targets in koji to support 2.11.x builds
* realized that koji was in a broken state
* investigated and discovered that Fedora 23 in Koji got updated yesterday,
but somehow the repo metadata did not get updated
* kicked off mrepo to resync Fedora 23
* some more
Bryce,
You can perform a mongo dump on the 2.7 install and a mongo restore on the
2.12 install. Then you can connect to mongo using mongo shell and remove
everything except for the following collections:
'content_types'
'repos'
'repo_distributors'
'repo_importers'
'migration_trackers'
'users'
One solution is to use a shared filesystem for /var/lib/pulp. Mount that
filesystem on whatever host you want serving the content and then
configure httpd to serve it.
Another solution is to use the rsync distributor[0]. The rsync distributor
was added in 2.10. It allows Pulp to publish content
o some workarounds.
>
> When I choose the child-server concept, i can manage every child-server
> and consumer directly on the parent, right?
>
> Tuz
>
> 2017-02-15 19:11 GMT+01:00 Dennis Kliban <dkli...@redhat.com>:
>
>> One solution is to use a shared filesys
Dustin,
Thank you for reporting this issue. I was able to reproduce it by disabling
SELinux. We plan to include a fix for this problem in the next beta. You can
see the patch here[0]. The restorecon operation was not permitted when SELinux
was disabled.
-Dennis
[0]
What version of Pulp are you using? It sounds like you are experiencing a known
issues[0] that was fixed back in 2.6.3.
[0] https://pulp.plan.io/issues/998
-Dennis
- Original Message -
>
>
> When running a regenerate applicability task (for 8 repositories), I received
> the
The docs for applicability calculations can be found here[0].
[0]
http://docs.pulpproject.org/dev-guide/integration/rest-api/consumer/applicability.html
- Original Message -
> How do you list errata applicable to a consumer?
>
> https://www.fedorahosted.org/pulp/wiki/Errata
>
>
Thank you for such prompt response! That got me unstuck!
On Tue, Apr 18, 2017 at 4:27 PM, Jiri Tyr <jiri@gmail.com> wrote:
> Please follow these installation instructions:
>
> https://github.com/jtyr/ansible-config_encoder_filters#installation
>
> On Tue, Apr 18, 20
I am not sure why we decided to postpone this issue till Pulp 3, but it
seems like an annoying bug to deal with on the 2 line. Would changing this
behavior be a backwards incompatible change?
-Dennis
On Wed, Apr 12, 2017 at 11:13 AM, Jason B. Nance wrote:
> Hello all,
>
> I
I would like to use the ansible Pulp role published on ansible galaxy[0].
However, I am having some trouble. I ran the following commands on my
CentOS 7 box:
sudo yum install
http://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
sudo yum install ansible
sudo ansible-galaxy install
Jason, I've left a comment[0] with the next steps on the issue. Thanks for
bringing this back to our attention.
[0] https://pulp.plan.io/issues/2588#note-7
-Dennis
On Thu, Apr 13, 2017 at 7:34 AM, Dennis Kliban <dkli...@redhat.com> wrote:
> I am not sure why we decided to postpone t
Paul, I believe that the 2.14 beta has the feature[0] that solves this
problem. You should be able to provide extra arguments for preserving
permissions on files.
[0] https://pulp.plan.io/issues/2730
On Thu, Jul 27, 2017 at 11:56 AM, Paul Urwin wrote:
> Apologies, I
It looks like mongodb is not running. Pulp can't operate without the
database.
On Thu, Oct 12, 2017 at 3:08 PM, Donald Wolfe wrote:
> Hi all,
>
>
>
> Any help would be greatly appreciated.
>
>
>
> I had Pulp working fine with CentOS and RHEL 6 repositories, but ran into
>
We should start scheduling these calls again. I am interested in discussing
workflows and REST API for
- moving content between repositories
- purging orphaned content/artifacts and orphaned publications.
Other topic suggestions are welcome.
On Mon, Jul 24, 2017 at 5:38 PM, Brian Bouterse
The use case you are describing is not one that Pulp 2 currently supports.
However, I can picture this feature working in 2 different ways:
1) A publisher for a repository with an 'immediate' download policy on an
importer should make sure that all the content it is publishing is actually
On Mon, Dec 18, 2017 at 2:49 PM, Justin Sherrill <jsher...@redhat.com>
wrote:
>
>
> On 12/18/2017 02:31 PM, Dennis Kliban wrote:
>
> The use case you are describing is not one that Pulp 2 currently supports.
> However, I can picture this feature working in 2 different
You can stop pulp_resource_manager, pulp_workers, and qpidd. Then start
qpidd, pulp_resource_manager, and pulp_workers. The workers will mark the
tasks as canceled in the database when they start and qpid should drain the
queue when it is restarted.
On Fri, Nov 10, 2017 at 6:33 PM, Dustin McNabb
lready tried using “pulp-admin tasks
> purge”, right (ref: https://www.mankier.com/1/pulp-admin#Tasks-Purging)?
>
>
>
> *From:* pulp-list-boun...@redhat.com [mailto:pulp-list-boun...@redhat.com]
> *On Behalf Of *Dustin McNabb
> *Sent:* Monday, November 13, 2017 9:00 AM
> *To:
This is currently not possible to do using the rsync distributor. This
feature would make for a great contribution to the RPM plugin. The first
step is to file a story in our issue tracker[0]. I will provide guidance to
anyone that wants to implement this feature.
[0]
The tasking system in Pulp locks a repository during an import of a content
unit. If clients are uploading content to the same repository, the import
operation has to wait for any previous imports to the same repo to
complete. It's possible that you are not waiting long enough. Unfortunately
this
Please try out the POC and send all feedback about the implementation or
any additional use cases before July 2nd.
There are a lot of details on the issue[0] in pulp.plan.io.
[0] https://pulp.plan.io/issues/3756
On Mon, Jun 11, 2018 at 1:20 PM, Bihan Zhang wrote:
> After gathering some
On Wed, Jun 6, 2018 at 9:11 AM, Simon Baatz wrote:
> We looked into Pulp's Docker support recently and ran into surprising
> problems.
>
> Our setup is probably not the usual Pulp & Crane setup: We have
> detached content servers to which Pulp pushes yum and iso repositories
> using rsync
Pulp 2.16.2 Beta 1 is now available, and can be downloaded from the 2.16
beta repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.16/
This release includes bugfixes for: Pulp, Docker Support, RPM Support, and
Puppet Support
Upgrading
=
The Pulp 2.16 beta repository is
What version of MongoDB are you running? Mongo 2.4 requires using
mapporduce during this step[0] which is slow.
[0] https://github.com/pulp/pulp_rpm/commit/58cfa00876a831e4baacf66f07c401
8f7349bbb8
On Tue, Jun 5, 2018 at 12:45 PM, Austin Macdonald
wrote:
> Thanks for asking the list.
Pulp 2.16.2 is now available, and can be downloaded from the 2.16 stable
repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/stable/2.16/
This release includes bugfixes for: Pulp, Docker Support, RPM Support, and
Puppet Support
Upgrading
=
The Pulp 2.16 stable repository is
The solution was to execute the following in a python shell:
from pulp.server.db.connection import initialize; initialize()
from pulp.server.controllers.user import update_user
update_user('admin', {'password':'yournewpassword'})
On Thu, Jan 11, 2018 at 11:21 AM, Paul Urwin
It sounds like you may be experiencing issue https://pulp.plan.io/issues/
3135
>From our conversation on IRC, I learned that the hypervisor is acting up
and the VMs pause from time to time. So even though the system is not under
heavy load it still behaves as though it is. As a result the
I noticed that your consumer packages are from 2.11 and server packages are
from 2.15 release. The two versions need to match up. Here[0] is where the
EL6 consumer packages for 2.15 are located.
[0] https://repos.fedorapeople.org/pulp/pulp/stable/2.15/6Server/x86_64/
On Wed, Feb 14, 2018 at 3:49
Did this get resolved?
On Fri, Jul 6, 2018 at 7:16 AM, Kodiak Firesmith
wrote:
> Hi Tyrone,
> Unfortunately the problem is ongoing. I've just tried once more to be
> sure, it's still related to the rhel-server-6.10-x86_64-dvd.iso image
> sync. I'm wondering if the CDN team might be able to
Please file an issue at https://pulp.plan.io/issues/new
Please include any tracebacks you seen in the logs.
On Wed, Apr 11, 2018 at 1:54 PM, Jim Davis wrote:
> The epel repo sync completed successfully on v 2.15
>
>
>
> *From:* Jim Davis
> *Sent:* Wednesday, April 11,
Seems like a problem with whatever mirror you are hitting.
On Thu, Mar 22, 2018 at 12:37 PM, Ashish Humbe wrote:
> Hi,
>
> When we try to create and sync the mirrorlist URL on Sat6.3
> with pulp-server-2.13.4.6-1 it fails
>
> # pulp-admin -u admin -p XXX rpm repo create
The POC for Crane looks good to me.
Story 3761 seems to be all about making a new rsync distributor for Docker.
Do you still see that as necessary?
On Fri, Jun 15, 2018 at 11:59 AM, Simon Baatz wrote:
> On Mon, Jun 11, 2018 at 08:25:39AM -0400, Dennis Kliban wrote:
> >On Wed, Ju
Actually, let's move this discussion to the issue tracker[0].
[0] https://pulp.plan.io/issues/3761#note-2
On Thu, Jun 28, 2018 at 11:07 AM, Dennis Kliban wrote:
> The POC for Crane looks good to me.
>
> Story 3761 seems to be all about making a new rsync distributor for
> Docker.
We are going to meet from 18:00 to 20:00 EDT in the Tavern Room of Raleigh
Brewing Company[0] in Raleigh, NC.
[0] https://www.raleighbrewing.com/
On Wed, Oct 10, 2018 at 5:09 PM Dennis Kliban wrote:
> The first Pulp Community Meetup is going to take place on Tuesday, October
> 23
ker.
>
> Thanks!
>
> вт, 23 окт. 2018 г. в 23:58, Dennis Kliban :
>
>> Konstantin,
>>
>> Could you please file an issue in pulp.plan.io?
>>
>> Thanks,
>> Dennis
>>
>> On Sat, Oct 20, 2018 at 5:40 AM Konstantin M. Khankin <
>>
Konstantin,
Could you please file an issue in pulp.plan.io?
Thanks,
Dennis
On Sat, Oct 20, 2018 at 5:40 AM Konstantin M. Khankin <
khankin.konstan...@gmail.com> wrote:
> *Forgot to mention versions:*
>
> pulp-admin-client-2.17.1-1.el7.noarch
> pulp-agent-2.17.1-1.el7.noarch
>
Matthew,
Have you read through the scaling guide[0] ? It does not provide any apache
configs, but there is a section on load balancing[1].
[0] https://docs.pulpproject.org/user-guide/scaling.html
[1]
https://docs.pulpproject.org/user-guide/scaling.html#load-balancing-requirements
On Mon, Oct
Kodiak,
Thanks for the heads up. The 404 for the treeinfo file is expected for all
repos that are not used for provisioning (kickstart). Do you have any other
404 examples you could share?
Thanks,
Dennis
On Tue, Oct 30, 2018 at 9:38 AM Kodiak Firesmith
wrote:
> Good Morning Pulp Users!
> RHEL
Pulp 2.17.1 Beta 2 is now available, and can be downloaded from the 2.17
beta repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.17/
This release includes bugfixes for: Pulp, Docker Support, RPM Support,
OSTree and Debian Support
Upgrading
=
The Pulp 2.17 beta
A couple of issues[0,1] were discovered during the beta process. Beta 2
should be available tomorrow. The GA should now be available on October
11th. The updated release schedule is here[2].
[0] https://pulp.plan.io/issues/4055
[1] https://pulp.plan.io/issues/4050
[2]
The first Pulp Community Meetup is going to take place on Tuesday, October
23, 2018 in the Raleigh, NC area. The plan is to get together from 17:30 to
19:30 EDT. We don’t have a specific agenda. We want to use this as an
opportunity for Pulp users and developers to get together and discuss Pulp
Pulp 2.17.1 Beta 1 is now available, and can be downloaded from the 2.17
beta repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.17/
This release includes bugfixes for: Pulp, Docker Support, RPM Support,
OSTree and Debian Support
Upgrading
=
The Pulp 2.17 beta
On Thu, Dec 6, 2018 at 1:47 PM Matthew Madey wrote:
> Having some trouble with the search API.. I'd like to be able to query for
> a package to see if it exists in any repository on the server. Can someone
> share an example curl POST to find a particular RPM based on name? I've
> been trying
Pulp 2.18.0 Release Candidate 1 is now available, and can be downloaded
from the 2.18 beta repositories:
https://repos.fedorapeople.org/repos/pulp/pulp/beta/2.18/
This release includes new features for: Crane, Docker Support, Pulp, Puppet
Support, and RPM Support
Upgrading
=
The Pulp
The beta 1 release of pulp_docker for Pulp 3 is now available:
https://pypi.org/project/pulp-docker/4.0.0b1/
Checkout a demo of the features:
https://www.youtube.com/watch?v=IeY4lI8jG38=703s
___
Pulp-list mailing list
Pulp-list@redhat.com
I think you are onto something Tanya. The installer has pulp_content_host
settings[0] and it defaults to localhost:8080. You should set it to your
actual IP or hostname plus port. This config is used to create the systemd
file for pulp-content-app.
You can also manually modify the the systemd
1 - 100 of 260 matches
Mail list logo