Perhaps a silly question, but coming from the Satellite 5 world I'm just wanting to be sure - is upgrading from one major version to the next really as easy as 3 commands to upgrade and 3 service restarts? Every major release upgrade was a massive headache that I shared with many other sysadmins each time judging from the search hits I'd get about each problem I'd encounter going from 5.4 -> 5.5, 5.5 -> 5.6 and so on.
Are there common problems people encounter during the upgrades? Are there any particular preflight tasks one should be aware of beyond getting good conf file and Mongo backups? Are there disk paths that will have occupancy temporarily balloon during the upgrade process as was common Satellite? Sorry to sound skeptical, but thrice bitten forever shy on the upgrade front it seems.. Thanks! - Kodiak On Fri, Feb 19, 2016 at 6:32 PM, Dennis Kliban <dkli...@redhat.com> wrote: > A new Pulp 2.8.0 beta is now available in it's usual location[0]. Release > notes can be found here [1-5]. > > > > > [0] https://repos.fedorapeople.org/pulp/pulp/beta/2.8/ > [1] > https://github.com/pulp/pulp/blob/master/docs/user-guide/release-notes/master.rst > [2] > https://github.com/pulp/pulp_rpm/blob/master/docs/user-guide/release-notes/2.8.x.rst > [3] > https://github.com/pulp/pulp_puppet/blob/master/docs/user-guide/release-notes/2.8.x.rst > [4] > https://github.com/pulp/pulp_docker/blob/master/docs/user-guide/release-notes/1.2.x.rst > [5] > https://github.com/pulp/pulp_ostree/blob/master/docs/user-guide/release-notes/1.1.x.rst > > _______________________________________________ > Pulp-list mailing list > Pulp-list@redhat.com > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list
