| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Unify the shell to bash in all Kolla scripts.
Change-Id: Ib9591b2f8f344eb88455c5e9b7ecf2164fb5960a
Implements: blueprint use-bash-shell
|
|
Previously, check_required_vars was requiring log file variables
to be set in openstack.env. This would cause an error when
starting nova/neutron containers that used default (blank) log
file settings. Since the log files are not required
for the services to start, the default log files are left blank
(without a value in the K/V pair). This patch removes the
log_file variable for check_required_vars in each nova/neutron
script.
Change-Id: I169baab28f63a0e0ae06c8aef21b5e8d3155bdda
|
|
Previously, logging was hard coded into the nova and neutron
containers. This patch creates two common params for logging:
DEBUG_LOGGING
VERBOSE_LOGGING
and sets default values of verbose=true and debug=false. This patch
implements logging for Nova and Neutron. Add'l OS service config
scripts and images will need to be updated to use the logging
params.
Change-Id: I03d48005d5b4789aa3c519879a20d963ef1cbaa3
|
|
In order for the `check_for_*` functions to be consumed by `wait_for`,
they should notify of their success but not exit.
As a consequence, the previous behavior is restored by the fail_unless_*
companion functions.
With this change, it is now possible to do:
wait_for 30 1 check_for_os_service_running keystone
Change-Id: I16ddf8913027030c3ccb5487713d172904508fd6
|
|
When nova-api start and the nova database hasn't yet been created, it
would create it itself, preventing the migration in nova-conductor to
run and making it unable to start. This commit ensures that nova-api
container will not try to steal nova-conductor's job of creating the
nova database.
Nova-scheduler reacts differently to the missing database and simply
exits with a backtrace. This commit also prevents nova-scheduler to
start when the nova database cannot be found.
Change-Id: Ib6f7521151815faa7a26ec1d170df5a1cdb7fd63
Related-Bug: #1335804
|
|
This allows Kubernetes to reschedule containers in case a required
variable is missing, for example when the Kubernetes pod is started
before the service.
The checks were cleaned using the following method:
* remove duplicates
* remove check for variables that get a default value in the same file
* check for all variables used in the file
* check for required services when it is obvious.
Change-Id: Ib7e0530c410c61f828d36efe8925a20dc9781eab
|
|
Change-Id: Ia0b9057887bf34423546ca36346d9253ef4c90b9
|
|
The endpoints for Nova services needed to be properly created for ports
8773 (ec2/ec2) and 8774(nova/compute) and 8774(novav3/computev3).
Change-Id: I5e1931d2e7ea35f741ab73b070e24926a3763054
|
|
start.sh was trying to run nova-config.sh which has been renamed
nova-controller-config.sh
Change-Id: I546ce046c0789144cb48668500ea4b206d07487d
|
|
Without +x, docker will not run the shell scripts and the containers
exit immediately.
Change-Id: I03ca231d6e46131a58c01fae0f9b65e0a3722d36
|
|
Change-Id: I90fcd6ed43ce6c2b224eb43492586c8f4231ceda
|
|
Instead, nova-conductor will setup the database.
Change-Id: I91a46aa9bc3fc99fe58053b239929c8121864283
|
|
Partial-blueprint: kube-nova-container
Change-Id: Ib48e6318ae458bf03510725a220332d1920cbeae
|
