Based on
http://lists.openstack.org/pipermail/openstack/2014-January/004667.html,
there is confusion in the openstack community on how auth_uri in
nova.conf is supposed to interact with the other auth_* settings.
I've modified our config to use both for now.
Change-Id: I1433305e23d872cd773599c85053ba8f9aeb6145
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
The nova-compute POD now starts and produces nearly correct output.
It may be that the libvirt container needs additional attention as it
is spitting out errors related to the firewall toolchain on the container.
Change-Id: I5bcd21c59f341494206a09e882631185ce66f336
Libvirt imports from fedora-rdo-base rather then nova-base, so no need
in generating an extra image.
Change-Id: I3ddd3aca54900686e3351de3dc11896347b14b6e
Previously Kolla did not support Neutron. This patch provides
initial Neutron support by implementing neutron-server
functionality. It also creates a neutron-base image that
provides common config and packages for all Neutron-based
services.
Partially Implements: Blueprint Kubernetes Neutron Container
Change-Id: I2399a1331992fae0f387f01e5b5c1c1d34f0637d
Nova imports python-cinderclinet, which is not present by just
installing python-nova-api. Hard yum-install it until upstream
fixes packaging.
Change-Id: I3187721d3eda7ce81da9540469fcc93b93560d3b
remove nova-controller image, which is not meant to be started directly.
add required NEUTRON_SHARED_SECRET environment variable.
Change-Id: Id671c5473db8e6e222b16ccdfd9eaedc872c60fa
- correct typos/syntax errors in configuration scripts
- make config script consistent with other images
- do not create keystone entries in base image script
Change-Id: I42986fe1b9c80c5b0735fd70294bce1a6223a3ca
nova-libvirt was not in the list of started services, so its port
was not available prior to this change.
Change-Id: I59cedb68ff87a9a54e93c85e60f748e5cc161a4c
replicaton controllers are now automatically started by the start
scripts and killed by the stop script
Change-Id: I15d15ff9b1b640bd0f8cace872a827ecfe476ca3
This patch adds a script for validating YAML files, and replaces the
existing JSON checks with one largely identical to the YAML check.
This also provides a script that can be installed as a pre-commit hook
that will perform this checks when you commit changes. You can install
the hook by running tools/pre-commit-hook --install.
Change-Id: Ib4742a9db062362cfa61d669c691151bc1ca376c
The nova-controller will be using ports 8773, 8774,
and 8775. Therefore, Docker needs to be made aware of this.
Change-Id: Ia53dd50bdce4b328c246bad5399ab7ff44750d58
AFAIK the service files are only for services with ports exposed. Since
nova-compute doesn't expose a port, kubecfg returns an error when attempting
to register it:
F1014 17:06:34.329482 32317 kubecfg.go:395] Got request error:
service "novacompute" is invalid: port: invalid value '0'
Change-Id: I4d9f8d50d538f42d520f3d9437ab32aa6a226d2b
Start all of the nova-controller services and pods with the start-all-pods
and start-all-services startup scripts
Change-Id: I47fe15d67ef177fbecf342357bff44cf2fdb5d9e
Prevoiusly the connection uri was using an undefined variable. Now
it will use NOVA_LIBVIRT_SERVICE.
Change-Id: Ia5ceb3428fa7aeb8dd1dd7b500c63119856977f2
- do not perform database or keystone initialization in nova-compute
image (these should happen in the controller images).
- fix incorrect nova.conf path
- configure keystone_authtoken correct
NB: This still won't result in a working image, because it does not
configure the RPC settings yet. That will be for a subsequent patch.
Change-Id: Icbd66104ef817d360c46003b29fff63f66ace8d2
Add kubernetes services so that the nova controller
can use the ports 8773, 8774, and 8775, which correspond with
nova-api, nova-ec2-api, and metadata-api.
Change-Id: Idb083e2e0745c6587f9fa4f01a068727a435c2c6
The previous values were just stand in values. The new
ports support nova-api, ec2 api, and metadata api.
Change-Id: I330575d9b53b69bcacc61061b271252e61e64d4b
The nova-controller is going to make all the configurations
so it needs a script to setup nova.conf. The config data is
stored locally in nova.conf and will be read in and executed by line.
Change-Id: Id501212671201ca68cd08018ce024db284dd8c54
