Puppet required?
by Avram Lubkin
I was looking over the project and it looks interesting, much improved over
Spacewalk. I particularly like how different projects are used instead of
one monolithic project. There's just one thing that concerns me. It looks
like if I want to do provisioning I have to use Foreman and if I use
Foreman I have to use Puppet. Since Puppet requires ruby installed on all
clients I can't deploy it. This is due to a security requirement. I can't
add interpreters to a system unless I have a good justification. I can do
what puppet does without adding another interpreter, so I can't justify it.
I know there are lots of organizations that use puppet and probably install
Ruby to support it, but I've never worked with a group that would allow
that. Any plans to support CFengine or something similar that wouldn't
require another interpreter on the clients? Python is Okay too, since any
RHEL or RHEL-like system already has it.
Please reply all, not on the list.
Thanks,
Avram
10 years, 10 months
Package path migration needed with next version
by Mike McCune
Pulp, the underlying package storage mechanism changed how it stores the
packages on disk which will require a migration if you don't want to
have duplicate packages on disk. Please read below for how to migrate
your /var/lib/pulp/ directory to the new structure.
I just pushed the pulp-1.0.0-6 version of packages to our pulp repos here:
http://repos.fedorapeople.org/repos/katello/pulp/
Mike
-------- Original Message --------
Subject: [Pulp-list] Package path enhancements in pulp
Date: Mon, 19 Mar 2012 22:48:50 -0400
From: Pradeep Kilambi <pkilambi(a)redhat.com>
To: pulp-list(a)redhat.com <pulp-list(a)redhat.com>
Hey All:
We recently ran into an issue where in some situations package paths in
pulp could collide. The relevant bug is here #798656. Due to this we
decided to change the package path location to include the whole package
checksum instead of first three characters. Though the change sounds
simple, the path for migration is involved. The following wiki page
illustrates the changes in detailed
https://fedorahosted.org/pulp/wiki/PackagePathUpdate .
The changed pushed to master and v1 will require you to do the
following in this order:
For Development Setup:
=======================
* Update pulp and grinder to newest
* rerun setup.py and pulp-dev.py
* take pulp-server offline
* follow the migration steps in
https://fedorahosted.org/pulp/wiki/PackagePathUpdate#Howtorunmigration
* start pulp-server
For a Pulp/Katello server upgrade:
=================================
Effected versions:
grinder: 0.141 or newer
pulp v1: 1.0.0-6 or newer
pulp dev: 0.277 or newer
* update pulp and grinder rpms
* take pulp-server offline
* follow the migration steps in
https://fedorahosted.org/pulp/wiki/PackagePathUpdate#Howtorunmigration
* start pulp-server
For a fresh pulp install, no need to run migration.
In both cases, taking pulp server offline is critical to avoid other
running tasks such as syncs, clones or uploads corrupting the existing data.
If you have any questions or run into any issues, please ping me on #pulp.
--
-- Pradeep Kilambi | irc: prad
Red Hat Systems Management
Phone: +1 919 754 4285
RHCE/RHCDS # 805008680430554
_______________________________________________
Pulp-list mailing list
Pulp-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list
12 years