instack-undercloud is no longer in use by the TripleO project. Removing
the code to avoid confusion. Stable branches will continue to be
maintained for their life however no new features should be added.
Change-Id: I63a813c7c1ffd30ca30017133d31a497b77a9a4d
Blueprint: remove-instack-undercloud
This was needed because puppet-certmonger didn't have the means to
request the appropriate EKU values manually (it relied on the defaults
per CA). This is no longer the case, so we can remove it.
Depends-On: Ie54d10fd4da45a73529a05e29aaa8eb19f986df3
Change-Id: I0eb466d7311e012d10fe03651c39dfd9a77bc517
Previously, certmonger tried to reload haproxy every time after a
certificate is requested. This is useful for certificate resubmits or
renewals. However, it turned out problematic on installation, when
haproxy is not yet active, as it would try many times and end up having
a race-condition with puppet.
This checks if haproxy is active and only then will it attempt to reload
it.
Closes-Bug: #1712377
Change-Id: I4edd42b888a0bbbb8eb0e71f5c17750bac46c2ce
This will allow tripleoclient to update instack-undercloud, call the
new pre_upgrade hook which will contain any new steps needed for
the coming release, and then call the regular upgrade script to
apply all the new configuration.
bp undercloud-upgrade
Change-Id: If7c2f5f5a904d570b2f2fbe4eea3f8fd7162afb9
We deprecated this script in ocata and can now remove it. The depends on
patch updates tripleo-docs to point to tripleo-quickstart directly for
creating virtual environments.
Change-Id: I920c73a1eb9b83644d7dd7dc4768ef1bd9949cdd
Add EKUS, or Extended Key Usage parameters, of id-kp-clientAuth and
id-kp-serverAuth to the certificate that certmonge generates, which is
used by haproxy to proxy public-facing hosts. This is necessary due to
the criteria by which Firefox and related browsers validate which
required extensions are acceptable when interpreting a certificate.
Change-Id: Ideec7d23769e68ae1b738c0118ec061b195e3bd7
Closes-Bug: 1668775
Let's go ahead and deprecate instack-virt-setup in Ocata. Then we can
see about removing it in a future release.
Change-Id: I22de582de69c15eb74d4de09c3a2d7299aee8f3f
Previously, the upgrade process for the undercloud has been to just
rerun the install process. The problem is that this does not include
anwyay to indicate that it's already been run if we need to trigger some
different actions on subsequent runs. As part of the Newton to Ocata
upgrade, we need to be able to run the cell v2 setup in a different
order than on a traditional install. We need a way for the puppet
scripts that ultimately get run to know if it's an upgrade or install
action. This change adds the creation of an undercloud_upgrade fact that
will be used when the upgrade process is run. Additionally a new script
called instack-upgrade-undercloud has been created to be used when
upgrade. The use of instack-install-undercloud will cause the install
flow to be execuated, while the instack-upgrade-undercloud will set the
fact to true to allow for the puppet scripts to use the upgrade flow.
Change-Id: Ie3cb21e30334fe8ffc0a9d6e707b42269b64c9ec
Related-Bug: #1649341
Related-Blueprint: undercloud-upgrade
Fix 1 warning and 1 error in bash syntax:
1) E043: Arithmetic compound has inconsistent return semantics.
Fix the bash syntax to be compliant.
2) ERROR: Split export and assignments in 2 files. Ignore the files.
Fix the bash syntax to be compliant.
Note: this test has been introducted by
https://review.openstack.org/#/c/400542/
Change-Id: I3c1134336033a8b5f2d56cd87fa190d9a354ecc0
This is now handled by tripleoclient, and has generated a bug
report. Let's get rid of it.
Change-Id: I3c51b5d920efe26fa47c3ae033f2b3199dbb2eeb
Closes-Bug: 1634052
Update instack-virt-setup to match the known minimum requirements for VM
memory (matches what tripleo-ci currently uses).
Change-Id: I435405d787134b1f0ea3e6bfef4b66faa9fde551
This will enable us to use a real CA to request the service certificates.
bp tls-via-certmonger
Depends-On: I32ded4e33abffd51f220fb8a7dc6263aace72acd
Change-Id: I5009273110154f0327ad542d75e83ff67bf72613
When deploying the overcloud with the default value of 4GB of RAM the overcloud fails throwing "Cannot allocate memory" errors.
By increasing the default memory to 5GB the error is solved in instack-undercloud
Change-Id: I29036edeebefc1959643a04c5396e72863fdca5f
Closes-Bug: #1563750
All these scripts are replaced by python-tripleoclient or manual docs
(in the tempest case). For better or worse, I don't think a deprecation
period is necessary here as I think we're way past that point with the
reality being that these scripts don't actually even work any longer.
Change-Id: I9d4f0e055a19bf662661f47ea328ec919e03ddda
No longer tie the default specs of undercloud VM to the overcloud VM
specs, make undercloud VM more powerful by default.
Change-Id: I53330bf7370f472edea7307883116197e3f66a63
instack-virt-setup runs
"tripleo get-vm-mac $UNDERCLOUD_VM_NAME" to get the
MAC address of the instack.
If multiple vm names contain $UNDERCLOUD_VM_NAME string,
several MACs are returned.
This fix returns mac from only one virtual server.
Depends-On: I3168c2c63c2d87aa243ab819b9977ec659721026
Change-Id: I55417bff0d6f0016d12cbc3abb8906b831a2077d
Since libvirt 1.2.11, libvirt doesn't ask for dnsmasq to fill a lease
file, thus instack-virt-setup fails to retrieve it at the end of the
installation. Simply using arp fixes that.
Change-Id: Ie6757a7b0c224d89ebab992ef147b6fc04f774cc
Closes-Bug: #1504179
Currently the virtual deployment creates a log file called virt-setup.log
This patch customizes this name file with the name of the instack server.
So by default the log file will change from virt-setup.log to virt-setup-instack.log
Change-Id: I64762fc9209fef93c3888752ab44d5bfc4d7b6f2
This will also be fixed in the unified CLI:
https://review.gerrithub.io/237539
I'm fixing it here as well just in case we have to fall back to this script for
any reason, and I don't want there to be a regression.
Change-Id: I9f1db761cf6ef5e02e79e6aed874a06d879b1e72
Related: rhbz#1233063
Bash was doing some weird things with the quoting of this variable,
so we need to wrap the whole call in an eval.
Change-Id: I596f1762e0f4685458933efdbc4d3ea26981fdd4
bz: https://bugzilla.redhat.com/show_bug.cgi?id=1228419
Upstream diskimage-builder has merged a version of the grub2 element,
so we don't need this one anymore and it conflicts with the upstream
version. Rename it to grub2-deprecated until we can switch to the
upstream element.
Change-Id: I264d2ecfceed730ccf396e1c7338d4c670a4466a
This isn't generally necessary right now, and there was actually
a typo in the $VM_LAST_NUMBER reference that made this fail anyway.
Change-Id: Icd468769d7adca511275090265ab098367e0ffec
* Move code after introspection, so that people don't report errors
against discoverd
* Increase retry timeout to 120 seconds for all Ironic operations
Change-Id: Ie6c6af223dd6a022fdbfafe7c44bf96b6e34ecd7
-Very incomplete testing right now
-Puts the password and stackrc files in the current user's home
directory during the install. Given that they now have secure
permissions and we recommend doing that anyway, I think it's fine,
but it is a non-trivial change in behavior.
This was done because it's awkward to read a root-owned file from
a Python process running as a regular user.
-Uses oslo.config instead of the bash-style answers file. A sample
conf file created by the oslo.config generator is included (for
now, although we may want to generate that dynamically at some
point). Backwards compatibility with existing answers files is
maintained for now, but is deprecated.
-Hard-codes the image path in instack-test-overcloud to . It's
difficult to extract the value from the conf file in bash (unless
they overrode the default, there's nothing for ConfigParser to read),
and since it's just a simple sanity test script I think that's okay,
at least for now.
Change-Id: I09270997dea7fdad2b40dfb303967ff425b55a9b