Hello!
Pulp 2.4 is now available in nightlies.
The easiest way to move to pulp 2.4 is to deploy a new --devel version
of katello-deploy (https://github.com/Katello/katello-deploy/)
To attempt to upgrade your dev workstations, follow these instructions.
If your workstation was deployed somewhat recently (in the past 4 months
or so), it should be fairly painless. For older dev workstations the
ssl certificate locations may have changed, so be very careful with step #7.
-
git pull master
-
rpm -e python-pulp-rpm-extension pulp-rpm-admin-extensions
(If installed)
- You can re-install pulp-rpm-admin-extensions afterwards if desired
-
Assuming you have the nightly katello-repos installed
- yum update pulp pulp-katello-plugins
-
cp /etc/qpidd.conf.rpmsave /etc/qpid/qpidd.conf
-
Edit /etc/qpid/qpidd.conf:
-
Comment out: cluster-mechanism=ANONYMOUS with a '#'
-
-
mv /etc/pulp/server.conf /etc/pulp/server.conf.back
-
wget http://jlsherrill.fedorapeople.org/server.conf -O
/etc/pulp/server.conf
-
Edit the file and replace FQDN instances with your fqdn
-
katello/config/katello.ymlEdit the oauth information based on the values specified in
-
from your server.conf.bak to the new server.confIf using an older install compare the certificate locations
-
-
service qpidd restart
-
sudo -u apache pulp-manage-db
- Check the ENTIRE output for failed messages. If any step failed
(may not be the last line), check /var/log/messages)
- Check the ENTIRE output for failed messages. If any step failed
-
service httpd restart
-
service pulp_celerybeat start
-
service pulp_workers start
-
service pulp_resource_manager restart
If you have any trouble feel free to hit me up on IRC. If push comes to
shove you should always be able to fall back to a new deployment using
vagrant
(https://github.com/Katello/katello-deploy/#development-deployment) or
on a system you've spun up yourself
(https://github.com/Katello/katello-deploy/#deployment) until we can
work through any issues.
Thanks to the Pulp team and help from David, Eric, and Brad!
-Justin