This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003825.html
Change-Id: Ic8d24b79e09e75a2b2a2397012a1e2218a8c49b6
The logic in the Gemfile was relying on Zuulv2 variables to find out
whether the spec helper gem was already available on disk, and since
Zuulv3 has changed things it was failing to find it and downloading the
master version instead. This patch ensures the Gemfile looks for the gem
in the right place when running in CI.
Change-Id: I930aa7160e76e2cfdaa1eabd477f5d3f6ad9970a
Instead of keeping a local copy of spec_helper_acceptance.rb and
requiring updates to all modules for any change, we can move it into the
common helper gem and require it from there. This will make it easier to
create and review changes that affect all puppet modules. Also change
the Gemfile to look for the gem in the local workspace if running in a
zuul environment.
Change-Id: Ieb3cc87333ca243fa3d74e8afa573895dfaf604b
Because of the way glean works, we don't actually need to have a DNS
server setup to boot our images. In this case, it is actually
problematic for centos-7, because glean overwrites our
/etc/resolv.conf file.
Change-Id: Ie81bc593ac3257021e0636b6c111c37e8b87b747
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This patch adds a xenial nodeset and updates the spec helper to install
puppet 3 from the Ubuntu repos instead of from puppetlabs. However, it
ultimately disables the tests on xenial because neither the Ubuntu Cloud
Archive[1] nor the Puppet-OpenStack modules support mitaka on xenial. We
will need to plan our xenial upgrade and OpenStack upgrade at the same
time and reenable xenial testing when we are ready for the OpenStack
upgrade.
[1] http://ubuntu-cloud.archive.canonical.com/ubuntu/dists/xenial-updates/
Change-Id: I3b7c2c83d6a20907de4b69fe6fcd4c59a5052d23
Bindep is a tool for checking the presence of binary packages needed
to use an application / library. It started life as a way to make it
easier to set up a development environment for OpenStack projects.
Change-Id: I0763d217b5f429675cc7133475355c02c391ceab
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
Default for ubuntu-minimal has been set to xenial,
and it's causing dhcp-all-interfaces to fail. A bug has been
opened in bifrost for it:
https://bugs.launchpad.net/bifrost/+bug/1641668
Change-Id: I52b9f984e4dd77916c38e8ce8d2aa41c247a66c8
If that is not set, it is not picking the max_connection
updates until next restart, causing manifest to fail at
first run.
Change-Id: Ia6ff2700b564801e647b88d68d6a4ecb579b96c1
Depending on the cores and memory of the server, this needs
to be parameterized properly or is causing issues on
neutron and nova.
Change-Id: Id5a0e5af031175cc0a9d8b5a3bb97ae4adfbdf1e
The external gateway is passed with the parameter
gateway_ip, this ipv4_gateway was the old one, and
hardcoded on the manifest.
Change-Id: I0eb532bf423e45ac683fc6bf23d80699d074bd17
bifrost is composing network ids with ipv4+mac, while
sys_interfaces is just a dict with mac:nic values.
Get rid of that ipv4 prefix when searching for the right
interface to create the bridge.
We will be trying first to retrieve the original id,
then get rid of ipv4- as a fallback.
Change-Id: I78ac1e6b735cbc2cc120c92f6c9bf1492924f5e4
Our dhcp is just used for pxe boots, and shall not
be adding a default route. Send the right option for bifrost
to disable it.
Change-Id: Id5d1cd02544c8c4c5ce869114299e6681db81b19
Naming with dashes is causing issues on CentOS,
because glean is called with interface br/xxx instead
of br-xxx due some naming translation.
Also interface name and vlans can differ on environments,
causing all puppet modules to change their naming. Instead of
depending on vlan or nic to configure bridge name, add the
ability to pass that name as a parameter, and likely set
to br_infracloud on our deployments.
At the moment, leaving the default naming to do not break
existing cloud deployment.
Change-Id: I0790bab2fd63f525e8b9c8d47ee79ea63a72750a
We upload our images today as qcow2 format, however compute nodes will
force them to raw format. To improve performance when first booting a
node, do bother converting the image to raw format.
Change-Id: I82e16825a90a1a8995b6dd3c8769954e3976a15f
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This doesn't have to be hardcoded in the module, but
parameterized, and ideally shall be configured using
hiera. As an initial step, add the parameters with
default values, to pass tests until the corresponding
change for system-config lands.
Change-Id: Ic1f0368a1cb6c94405a4cb52dec1b83131164035
We do not rely anymore on infra-cloud-networking element,
replaced by infra-cloud-bridge. So removing not needed
templates, and files from the manifest.
Also remove global vars for hpuswest, as this is not
used anymore.
Change-Id: Ie05d4c1e5bf5801cf0a3d2dd5cf5203c480ed53e
Current ansible install fails when does not find gcc
or openssl-dev. Add this before calling the ansible class.
Also remove uuid dependency from RHEL as package does
not exist.
Change-Id: I1c9002d669ec8df30ef09b3086f9f5297e032da1
Since vanilla and chocolate are on the same VLAN, we don't have
two different bifrost machines, just one to handle both.
Therefore, the per-region split logic is not needed anymore and makes
it impossible to have on the current baremetal machine in prod
having both inventories at the same time.
Note: I'm leaving the 'region' parameter on purpose, otherwise
the apply tests fail.
Will remove it in a subsequent patch.
Change-Id: I433cdb8675c3acd2e699272aaf6a0e67eb9200b0
We cannot use naming with br-xxx because it is translated
to br/xxx when passed to glean, causing it to fail.
As a temporary workaround until https://review.openstack.org/368692
lands, use br_xxx naming for not debian/ubuntu (to avoid
crashing current deploys of infracloud)
Change-Id: I6a511bef0b262e40981abfc46bb5c60865fde566
According to documentation, the proper way to start a service
after the network comes up, is add After and Wants on the
default file.
Change-Id: Ibf252426210fcb1716dae918266d988a36ccbbb6
Per documentation on RHEL side, the proper way
to activate the bridge, is full restarting the
network service.
Change-Id: I61564b3c39b169f9de13dd2297210a2348f448e2
It is causing troubles on rabbit and linuxbridge, crashing
because permission denied errors. Initially disable it to
have a working cloud, and add the right settings on future
patches to re-enable it.
Change-Id: Ibc3303966e7bc450f9d9dbaa4fce7104fcb90635
Monty Taylor