Additional entries for the .gitignore to clean up status results.
cover and MagicMock directories are transient and results of our
coverage measurement and testing procedures.
.devcontainer and .vscode are created as part of VScode workflow.
Neither should be included in codebase and as such only add noise
to the 'git status' report.
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I6c22770d19f465a5fe54a43d99886a048ab1fde9
Add the ability to install an undercloud minion which is connected to an
original undercloud. This minion can have either heat-engine or
ironic-conductor deployed on it.
Adds two new openstack commands for the minion install and a new
minion.conf can be used to configure them.
openstack undercloud minion install
openstack undercloud minion upgrade
Depends-On: https://review.opendev.org/#/c/656984
Change-Id: I61832f5088be172eaf31b36a9cca8dc289580bb2
Related-Blueprint: undercloud-minion
According to Openstack summit session [1],
stestr is maintained project to which all Openstack projects should migrate.
Let's switch to stestr as other projects have already moved to it.
[1] https://etherpad.openstack.org/p/YVR-python-pti
Change-Id: I11f742b525d8d7328a9d46f0bd46da112e27ad82
In line with [1] removing references to developer tools in
.gitignore.
[1] https://review.openstack.org/#/c/592520/
Change-Id: I313350e3ac1d472749126a86bc462ec2fe5461a5
Undercloud deployment starts logging into its log file
too late, omitting log records from undercloud_config,
preflight checks. This is a problem as we want to log
at least the commands used for undercloud install/upgrade.
Ideally, messages in stdout/stderr should not miss the
log file.
Fix this via the added custom undercloud_log_file config
(use --log-file for standalone CLI). Use those to
configure logging to a file.
Fix missing formatting, like timestamps and source, for
undercloud config and preflight checks.
Write preflight/install/upgrade logs into the same
logfile.
Move the load oslo config method into shared utilities.
Add the configure logging shared utility for the classless
modules (w/o oslo_log supported). Such modules can
mimic oslo_log behavior defined for the main deployment
modules derived from openstack client classes, which
support logging to files natively and are not affected
by the subject issue. With an exception made for those
classless modules allowing them to log INFO+ be default.
So operators will have the pre-flight check
notes logged, for example.
Change-Id: I340be11bc9471df22f038629679634c3542d34d6
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
This is the start of a standalone.conf for use with the all in one
installer.
Change-Id: I656f4c1f7094b9a5981c1f15ff1c119693cd17c8
Related-Blueprint: all-in-one
Add ReNo support to manage release notes.
http://docs.openstack.org/developer/reno/
We'll start using it during Ocata.
Change-Id: Ie8945b6da8c37d5d4e7bc5a09f0d6f75ede9f58f
Jiri Podivin