Use a little trick we deployed in devstack to install the latest
epel-release rpm; first setup a disabled "bootstrap" repo to epel and
then yum install the latest package.
This should avoid us having to touch anything when EPEL decides to
create a new release.
Change-Id: I9e43de3770b6dff03fd87edbf5decbae9780d8db
This reverts commit d935a86289.
The blockers for setuptools 8 compatibility should all be resolved
now.
Change-Id: I39b0103a999690ec63ab6963af4962c070ee8768
Latest release of setuptool 8.0 made several versions used in
requirements.txt of OpenStack projects invalid. Instances:
* SQLAlchemy>=0.8.4,<=0.8.99,>=0.9.7,<=0.9.99 in oslo.db 1.2.0
* python-neutronclient 2.3.9.40.g9ed73c0 in openstackclient
Cap '<8.0' is set as a temporary fix until a better solution
comes up.
Change-Id: I74530bd52cf21951d9b7c26133ed21f46c89c7d1
The 00-puppet.pref file is now a template that's generated based on
$pin_puppet set in your manifest.
Change-Id: I7548f3ddf02b8d0b5c0233f74407cf22038679e4
puppet looks for pip-python (rather than pip) when osfamily is
redhat. Somehow this wasn't causing a problem before (presumably
pip-python package was left behind but something has changed
upstream) and now we need to create a symlink for rhel6 as well.
Change-Id: I1f11aa7f6b33aa846e10715dd1653bb43e1c9d7e
As we discovered in the course of upgrading puppetboard the puppetdb
package is upgraded independently of the puppetdb-terminus package,
but in fact it will break if they don't match. We now pin them to
the same values for safety.
Change-Id: I628129997e084ec5e4cb18947fa7e2362c9b4ba5
This reverts commit 5be2e2f18a.
Yay! We've sucessfully upgraded to puppet3 and the sun is shining!
Start managing apt pins for puppet again, and also, set the default
to be 3.x everywhere.
Change-Id: I80db5b5e154a3849914aa348e1eabadd0a2ad936
* check to see if lsb_release exist or not, if not
install it. Updating logic to match other platforms.
Change-Id: Ic6e8625d90db9076a9ca08669fe11ca3cfe28b7b
This enables install_puppet.sh to run successfully on
trusty with PUPPET_VERSION=3 set.
Add a util directory and a puppetmaster bootstrap
shell script.
Puppetdb-terminus versions are the same in trusty and
precise but are different than the puppet version number.
Also puppetdb-terminus isn't present in the puppetlabs
repositories.
Along with this I have done sufficient testing to use
puppet version 3.6 with confidence.
Work has been done to enable directory environments as well.
Change-Id: I925fa6ac1ed9fc9c0b5e9e616fb071bf7a815436
The pip-python symbolic link creation is the last
step in the install_puppet.sh on Fedora.
If the symbolic link already exists,
the exit status of the script will be failed.
After this change the pip-python link will be created by force,
so it will not fail on second run, and it may correct an old incorrect
link.
Change-Id: I0b25b1d69ee5e851f15e44fd16f62c29676d2075
Install the right EPEL and puppet rpm's for RHEL7/Centos7.
I have tested this on one of the CentOS nightly builds and
run_puppet.sh, install_modules.sh and a puppet apply of
openstack_project::single_use_slave works as expected
Change-Id: I80024d1afdb4e40d5fe9793ab2ec443b887c5fa8
Installing setuptools with pip overtop of system setuptools
has evil and destructive results. Kill it with a hammer
before re-installing.
Change-Id: I556b2cec249ef46e09ffca3cd75521e0beeb7779
Add upgrading of setuptools to prepare-node.sh. We want this
to happen everywhere, and quite honestly I'm not sure I
fully trust trying to get puppet to do it.
This reverts commit 3bc3a11244.
Change-Id: Idf09be0e1e086e20f9e71ceb26602fea1fc62173
Instead of looking for an argument, change the install_puppet.sh script
to look for an environment variable to switch to installing puppet3.
Also export this environment variable in prepare_node.sh (albeit with a
default value that does not install puppet3).
Change-Id: I04bee2fa5bb70a4d763edb2f3d30f117cad5d65b
As part of move to add a puppet3 master the facter-2* exclusion on
centos6 was removed. We need this exclusion so add it back.
Change-Id: I085b242739a572cf2daeb514a46e93b36104d3ee
This change modifies install_puppet.sh to accept a --three option
setting it to install the latest puppet available. It also creates
a node definition for the puppetmaster.o.o node, the new 3 master,
and the master of the future. Changes were made to various classes
to allow the pinning to version 2.x to be turned off.
Change-Id: I805d6dc50b9de0d8a99cf818d22d06c2dea6090a
A small clean-up of the install_puppet.sh script to enhance
readability and to simplify adding support for extra distributions
- add distribution check functions
- move puppet installation for each distribution into its own
separate function
- move pip installation into a function
- add/expand several comments
Change-Id: I5d5f71fde607ace528b7372e2deadccbea58bd2f
I hit an issue with a system with curl *and* wget installed. The curl
download failed, leaving a corrupt get-pip.py and thus the wget
download started (which then saved to get-pip.py.1). The script then
tried to run the corrupt version. Although re-running is uncommon
unless you're manually deploying the scripts, best to also check for
the file first or these commands both re-download to get-pip.py.X
Change-Id: I6b70b4b7bb3d963ba70d71388c701951932e9adb
The pypa team has made a new static location for get-pip.py. Instead
of downloading from github, we should use this.
Change-Id: Ifb7f00447d4a19f20f6413fa7fece5913de092f8
There are few things that are different for our slaves on trusty. Of
note, we don't want to pin puppet, and we need to provide a version
for postgres.
Change-Id: Ibee78cd4fbeef2e6af43379d2bc3a0f0e9767a06
We nolonger need or want setuptools_git installed anywhere.
get-pip no longer needs ez_setup.py first. Also, github broke
redirection on Fedora, so change the URL.
Change-Id: I16d64695bf05e672fdc12236424b62e5cd5e5dc7
raw.github.com now redirects to raw.githubusercontent.com and various
curl commands are failing unless they include "-L".
Change-Id: I07d9c2f9caa2abc82ffd57435335875df5fbc96f
Puppetlabs have been updated and the pinned version of
puppet-common now requires a version of facter to be < 2.
As such facter is now pinned to 1.*.
Change-Id: Ief0030c7cb404322c131ac4cfe90e2c7b82b54a1
This allows hiera data to be split into two buckets: sensitive and
non-sensitive. Sensitive data is put where it always has been. Non-
sensitive data, such as users ssh keys and lists of packages can be
put into the data directory contained within the
openstack-infra/config git repository.
This also introduces a more complex hierarchy: data is now split on
osfamily and lsbdistcondename. Operatingsystem is left for
compatibility.
Change-Id: I3b3faeab837aa5732da01e96bbe0c19aa936a58d
In Fedora the pip command used by the packaged python-pip is
"pip-python" rather than "pip" due to a naming conflict. The
Puppet module tries to compensate, but we don't use the Fedora
package, so the command really is "pip" for us.
Adding symlink line to install_puppet.sh for Fedora to add the
pip-python command that Puppet is looking for.
Change-Id: I60a03fb6c27a18cd8a536080bcce1baaba965237
* install_puppet.sh: Different providers vary in what packages are
preinstalled, but usually they at least have one of curl or wget.
Have a falback here to make the script slightly more portable.
Change-Id: Id126e47f037cd3165a95241a066b48246661a168
packaged pip vs. upstream pip gets the systems very broken. Make launch-node
use get-pip to install pip as per:
http://www.pip-installer.org/en/latest/installing.html
Change-Id: Ice28b47d766c04b42462a7297911dc1a1abe5a77
There is a helpful script we can use that avoids the plumbing
discussion, and neither raring nor F19 can run a Puppet master, so we
should document that to avoid false starts.
Change-Id: I72f8767dc3fc7967207c37911e8e45a6d85c6001
Fedora 18 uses puppet2.7 natively so we use that and gem install hiera.
Also updates our openstack_project:base manifest so that we upgrade
hiera via the gem provider.
Change-Id: I2ad8c1a81f9955f6de7812f72075fae84f7f7d7f
NOTE: puppetlabs only provides puppet > 3 for Fedora 18 anyway.
Reviewed-on: https://review.openstack.org/32449
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
* install_jenkins_slave.sh: Perform a dist-upgrade on Ubuntu
servers, similar to install_puppet.sh.
* install_puppet.sh: Change from upgrade to dist-upgrade so kernels
will also be included in the initial package upgrade step.
Change-Id: Ia39c37f75cc411ce92b1deb5125fa0c5c6e6db35
Reviewed-on: https://review.openstack.org/30388
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
The install scripts now look for CentOS in release files. Also some
instances of facter's operatingsystem are switched to osfamily and
capitalization of RedHat is normalized to match what facter uses.
Change-Id: I3bbca5481d0d5e6de9e62bfd6e2b0a85264ed6ed
Reviewed-on: https://review.openstack.org/27398
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
Updates our install_puppet.sh script so that we pin the puppet
version on RHEL.
In doing this I dropped the explicit puppet version used on
the 'yum install' command since it is no longer required.
Here doc is quoted to avoid variable expansion.
Change-Id: I5e45182b67fe9533b92d1132fef6888fdd5d96b1
Reviewed-on: https://review.openstack.org/23574
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Jeremy Stanley <fungi@yuggoth.org>
Tested-by: Jenkins
This reverts commit 53ec5d4d1a.
Turns out redhat-lsb-core was fine after all, as of a week ago:
https://rhn.redhat.com/errata/RHBA-2013-0448.html
Change-Id: I8c258b084971bb090dc5d09645375939719a3259
Reviewed-on: https://review.openstack.org/23150
Reviewed-by: Khai Do <zaro0508@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
The redhat-lsb-core package won't apparently be split out until RHEL
6.4 at the earliest:
https://bugzilla.redhat.com/show_bug.cgi?id=835919
Change-Id: I4bc9bb542e68db26744b834a6de7d99b2249c568
Reviewed-on: https://review.openstack.org/23124
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: James E. Blair <corvus@inaugust.com>
Reviewed-by: James E. Blair <corvus@inaugust.com>
Tested-by: Jenkins
Updates the puppet install scripts so that we pre-install
lsb_release on RHEL distros. We *think* this fixes an
issue where lsbdistcodename wasn't getting set correctly
and was causing subsequent puppet failures like this:
lsbdistcodename fact not available: release parameter required at
/etc/puppet/modules/apt/manifests/ppa.pp
Change-Id: I1758ee8be9a599e17f1ccb98fc95b2b4f29916f7
Reviewed-on: https://review.openstack.org/23111
Reviewed-by: Jeremy Stanley <fungi@yuggoth.org>
Approved: Clark Boylan <clark.boylan@gmail.com>
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Tested-by: Jenkins
Follow on changes should invoke this script from
install_jenkins slave, and launch-node.py.
Change-Id: Id48c3967efe8ce4087d18975f3526564e09daecc
Reviewed-on: https://review.openstack.org/18977
Reviewed-by: Clark Boylan <clark.boylan@gmail.com>
Approved: Monty Taylor <mordred@inaugust.com>
Reviewed-by: Monty Taylor <mordred@inaugust.com>
Tested-by: Jenkins