Hi Alan,
Pulp supports creating package groups directly or uploading them. See
https://pulp-rpm.readthedocs.org/en/latest/user-guide/recipes.html#package-groups.
Regards,
-Barnaby
- Original Message -
From: Alan Evangelista ala...@linux.vnet.ibm.com
To: pulp-list@redhat.com
Sent:
there is something
going on with the filesystem. Regards,
-Barnaby
- Original Message -
From: ben stanley ben.stan...@exemail.com.au
To: Ben Stanley ben.stan...@exemail.com.au
Cc: Barnaby Court bco...@redhat.com, pulp-list@redhat.com
Sent: Wednesday, June 24, 2015 1:37:31 AM
Subject: Re: [Pulp
Hi Sean,
Nodes is designed to help with replicating data between data centers. If you
are working to scale up the load that you can handle within a single datacenter
you would be better off adding some combination of more workers and apache
processes on a separate system and use NFS to share
Hi,
I'm surprised to see pulp_resource_manager using that much memory. The memory
required for the workers varies greatly depending on the job currently being
executed. For a system that is only running workers I would expect that 4 GB of
memory should be sufficient. Mongo is going to use all
Hi, What version of Pulp are you running? 'rpm -qa | grep pulp' should answer
the qeustion in detail. Regards,
-Barnaby
- Original Message -
From: Jason Ashby (IMS) ash...@imsweb.com
To: pulp-list pulp-list@redhat.com
Sent: Friday, June 12, 2015 8:12:50 AM
Subject: [Pulp-list]
Hi, I could maybe see that if Pulp and Crane were both configured on the same
port. Sadly the Docker API requires control of the context root on the server.
It looks like after crane was set up it is blocking the pulp server from
running. If you specify a different port in the Crane apache conf
If you run 'rpm-qa | grep pulp' what do you get for output? You should see
pulp-rpm-plugins in that list.
-Barnaby
- Original Message -
From: Trevor Vaughan tvaug...@onyxpoint.com
To: pulp-list@redhat.com
Sent: Wednesday, June 10, 2015 4:15:09 PM
Subject: [Pulp-list] Issue creating new
Hi Mike,
When you say it's a full day effort right now, what is it that is causing it to
be a full day effort? Is it personal involvement or the amount of time that
Pulp is spending on processing? If it is personal involvement I would highly
recommend repo groups so that you can configure all
Repository groups can be useful to trigger a publish on a group of repositories
or to export a group of repositories. The export case is designed to make it
simpler to support systems that are disconnected from the network. A repository
group can be exported to an ISO and then burned to a dvd
Hi Patrick,
Pulp requires a valid Yum repository for syncing. This means that a repomd.xml
and all the associated files must be present for Pulp to sync. For your
immediate issue I would recommend either 1) rsyncing the individual RPM files
locally and creating a repo using createrepo then
Hi Paul,
I don't know of a good way to copy only the latest version of a given RPM. For
you second question, if the RPMs have the same versions checksum then
duplicates will not be created. If either the version or the checksum is
different then a new RPM unit will be created in the repo. If
Hi,
If you are using only the command line, multiple repos is the way to do this.
Randy's suggestion about feeds is a good one. If you are using the rest api
you could create multiple yum_distributor instances, one for each relative
url. Each publish for the repo would run in sequence but
Hi,
Austin had it exactly right about using the rest api directly. If you are
working on a puppet provider, have you considered an extension to the puppet
module that we maintain for installing pulp. See
https://github.com/pulp/puppet_deployment. We would love to get a pull request
or patch
Hi Paul, What version of Pulp are you running? rpm -qa | grep pulp should
give all the pertinent information. Thanks!
-Barnaby
- Original Message -
From: Paul Jochum paul.joc...@alcatel-lucent.com
To: pulp-list@redhat.com
Sent: Monday, March 23, 2015 8:50:48 AM
Subject: [Pulp-list]
The first release candidate for Pulp 2.6.0 (pulp-2.6.0-0.9.rc) has been made
available in the beta repo. This release candidate addresses the following
bugs:
https://pulp.plan.io/issues/734
https://pulp.plan.io/issues/668
Regards,
Barnaby Court
Hi, The web published directory for ISO files is cleaned out every time a
publish occurs. If you specify a different directory using the '--export-dir'
flag on the command line the file will be added to the directory without
overwriting the contents. Adding the concept of aging or retention
That sounds a lot like https://bugzilla.redhat.com/show_bug.cgi?id=1176698
which will be fixed in the upcoming 2.6.0 release.
-Barnaby
- Original Message -
From: Vijayabalan Balakrishnan bvijay...@gmail.com
To: pulp-list@redhat.com
Sent: Wednesday, February 25, 2015 4:04:27 PM
Subject:
Hi, the details view of the repo is a good place to start. Just to clarify,
the copy action does not act on the filsystem. It is only a database update,
if it completes successfully then the items were copied. Where you can get
into trouble is that the target repository will not be
Hi,
Generally the directory structure that pulp uses for saving serving data is
not something that you should have to worry about. The Pulp server will manage
it's space and the links that are created during publishing. Generally, content
is stored in /var/lib/pulp/content and then when
Hi,
There is no downside other than losing the parts of Pulp that are tied to the
consumer (applicability, pushing out updates). If all you are looking for is
to mirror/promote content in repos this works great.
-Barnaby
- Original Message -
From: Mathew Crane
Fred,
Can you provide a sample of the two RPMs that are being uploaded? If the RPMs
have any differences in the Name, Epoch, Release, Version, Architecture, or
Checksum they should both appear in the published repository. If you uploaded
the same RPM twice but just changed the filename on
special instruction for upgrades of pulp_rpm from 2.5.0 to 2.5.1
to fix the yum rpm availability bug for existing repositories. Please see the
instructions in the release notes at
https://pulp-user-guide.readthedocs.org/en/2.5-release/release-notes/2.5.x.html
Regards!
Barnaby Court
Hi Sean, Are you referring to the directory where the content is stored long
term or the working directory that is used as scratch space as files are
downloaded? Generally the recommended means by which the long term storage is
recommended to be addressed is to change the mount point for
Hi, The issue here is that ctrl-c does not cancel the first import task that
appears to be hung. All it is doing is disconnecting the admin client from the
server. Check pulp-admin tasks list for any running tasks and then
pulp-admin tasks cancel --task-id id.
-Barnaby
- Original
Hi, This is by design. If files have not been removed from the repo we perform
an incremental publish which does not remove the old files. If an RPM is
removed from the repo we will perform a clean publish. The repomd.xml will
only reference the new files so yum should play nice.
-Barnaby
published files,
does yum work properly in that case? They should be ignored since they are not
referenced in the repomd.xml but I'm wondering if yum is doing something
strange.
-Barnaby
- Original Message -
From: Jon Shanks jon.sha...@gmail.com
To: Barnaby Court bco...@redhat.com
Cc
Hi,
Does the Pulp machine have access to both the internal and external network?
If so you can use a puppet repo to sync the modules from puppet forge and make
them available to the internal clients.
https://pulp-puppet-user-guide.readthedocs.org/en/latest/recipes.html#mirror-puppet-forge
the options we have today.
Thanks!
--
Barnaby Court
- Original Message -
From: Randy Barlow rbar...@redhat.com
To: pulp-list@redhat.com
Sent: Thursday, November 13, 2014 2:00:43 PM
Subject: [Pulp-list] [devel] git submodules
What if we used git submodules to put each Python package we have
Hi Sandro, I believe the directory has changed if you look in
server/6/6.5/x86_64/kickstart/ the kickstart files are there. Regards,
Barnaby
- Original Message -
From: Sandro Roth sandro.r...@zurich-airport.com
To: pulp-list@redhat.com pulp-list@redhat.com
Sent: Wednesday, November
-
From: Andreas Piesk a.pi...@gmx.net
To: Barnaby Court bco...@redhat.com
Cc: pulp-list@redhat.com
Sent: Wednesday, October 29, 2014 2:16:34 PM
Subject: Re: [Pulp-list] re-publishing repos?
Am 29.10.2014 um 17:26 schrieb Barnaby Court:
Hi, For the first item of the publish failing I am not aware
Paul, That should work, but the internals of the filesystem layout have
changed between 2.3 2.4. If you back up the database/restore the database
and copy the filesystem then when the migrations are run (via pulp-manage-db) I
think things will work ok. Two items I'd like to call out: 1)
Hi, For the first item of the publish failing I am not aware of any open
issues. Please open a bug with all the server logs as well as the contents of
the ~/.pulp/server_calls.log that should have the results of the rest call from
the server. For the item where changing the relative-url
Hi, I can't speak to 2.3.1 but I just verified that with Pulp 2.4.x the sync
for that repository was able to sync and publish the following bash rpm's:
bash-3.2-24.el5.src.rpm
bash-3.2-24.el5.x86_64.rpm
bash-3.2-32.el5_9.1.src.rpm
bash-3.2-32.el5_9.1.x86_64.rpm
bash-3.2-32.el5.src.rpm
Hi, Dropping i386 would be a problem for Pulp. We currently support i386 for
RHEL 5.
-Barnaby
- Original Message -
From: Lukas Zapletal l...@redhat.com
To: foreman-...@googlegroups.com, candle...@lists.fedorahosted.org,
pulp-list@redhat.com
Cc: Jan Blazek jbla...@redhat.com
Sent:
-list@redhat.com
Sent: Thursday, August 28, 2014 3:30:04 PM
Subject: Re: [Pulp-list] Dropping i386 arch from koji.katello.org
On 08/28/2014 11:50 AM, Barnaby Court wrote:
I believe the only platform Pulp is actively supporting i386 for is RHEL 5.
If we are maintaining i386 repositories
- Original Message -
From: Philipp Gassmann gassm...@puzzle.ch
To: Martin Collins martin.coll...@framestore.com, Christina Plummer
cplum...@gmail.com, Barnaby Court bco...@redhat.com
Cc: pulp-list@redhat.com
Sent: Tuesday, June 17, 2014 4:51:57 AM
Subject: Re: [Pulp-list] Repo configured to use SHA
To: Barnaby Court bco...@redhat.com
Cc: pulp-list@redhat.com
Sent: Thursday, June 5, 2014 5:20:43 PM
Subject: RE: [Pulp-list] unable to remove rpms
Hi Barnaby,
Thanks for the reply. These are custom rpms that I uploaded with the uploads
command:
pulp-admin rpm repo uploads rpm --repo-id=Dev-FOO
David,
That looks like a bug where the database object is being returned without being
properly formatted. Please open a bug if you have not done so already. Thanks!
-Barnaby
- Original Message -
From: David Gao d...@redhat.com
To: pulp-list@redhat.com
Sent: Wednesday, May 21, 2014
The RHEL6 repo didn't have any errors on the sync but still no
distribution - is showed 0/0 items for Tree Files.
Please let me know if I can provide more information that would be helpful.
Thanks,
Christina
On Wed, Dec 11, 2013 at 2:04 PM, Barnaby Court bco...@redhat.com
/6Server/x86_64/os
Preethi, Have you verified repos created from both of these CDN locations
include the distribution properly? Thanks,
Barnaby
- Original Message -
From: Christina Plummer cplum...@gmail.com
To: Barnaby Court bco...@redhat.com
Cc: pulp-list@redhat.com
Sent: Monday
This was a known bug with 2.1.3 and has been fixed in version 2.3.
-Barnaby
- Original Message -
From: Christina Plummer cplum...@gmail.com
To: Barnaby Court bco...@redhat.com
Cc: Tim Bielawa tbiel...@redhat.com, pulp-list@redhat.com
Sent: Monday, December 16, 2013 1:43:05 PM
Subject
...@redhat.com
To: Barnaby Court bco...@redhat.com, Christina Plummer
cplum...@gmail.com
Cc: pulp-list@redhat.com
Sent: Monday, December 16, 2013 4:06:13 PM
Subject: Re: [Pulp-list] Creating RHEL 5 compatible yum repositories
Barnaby,
OH SNAP -- Just set up a test pulp-server-2.3.0 server.
159
42 matches
Mail list logo
