| Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
Remove config setup in nova-conductor.
Change-Id: I0740e6a69601ab4a39c20a3287792013355a9262
|
|
|
|
|
|
|
|
Instead of multiple install commands, add multiple packages
into a single install.
Change-Id: Id27cb53da76df50bf2500eb2d6de18c7401e5c6c
|
|
Instead, nova-conductor will setup the database.
Change-Id: I91a46aa9bc3fc99fe58053b239929c8121864283
|
|
Configurations will exist in nova.conf. They will be read in and
set by the start script. The mysql configuration will be
made by nova-conductor.
Change-Id: I1709ff6620b19ef5dbcf5efe8b72c329acf96123
|
|
- batch yum operations to the build goes faster
- yum clean after install to remove yum cache and make
final image smaller
Change-Id: I62246a6329a6b2ab6ab4fee6f72652a805f1e72e
|
|
- use correct namespace for base image
- mariadb and openstack-utils are installed by fedora-rdo-base
Change-Id: I9c8bccab10f8b9dc66340fb94d45c90d1a39fea9
|
|
modify glance and keystone images to log to stdout/stderr, so that logs
can be recovered using "docker logs".
Change-Id: I18470c13142ceaf2f10c32e10f5e835ddaf58550
|
|
Use kubernetes volumes for data storage rather than placing data
directly on the container filesystem. That provides a starting point
for thinking about persistent data -- one could replace the emptyDir
source with an explicit path via hostDir, and then you would have
storage that would persist over a container delete/re-create.
Change-Id: Ifade1cb2ba546e5e0207c3d8c84965dc2195716b
|
|
Change-Id: I0dcbe6fd4c1d3ac9b79fc205df2013f62ff5a546
|
|
add /check.sh to keystone and glance-api images that can be used to
verify proper functionality of the container.
Change-Id: I0a878678fb8e9427d8e99af4896cbc679d3490a4
|
|
if we want to be able to run multiple keystone container instances, the
password cannot be generated as part of the container boot process; it
must be passed it as part of the pod template.
Change-Id: Idd1b50b6bdb3788eec316bf22fb954f5ecbaa4be
|
|
glance keystone password cannot be generated during container boot
because we need the same value in both the -api and -registry
containers.
Change-Id: I4099ca19bd7433ff2a75ffba3a1597eff0be2ce4
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cause glance start.sh scripts to exit on any errors (allowing kubernetes
to reschedule the pod).
Change-Id: Ibebbf47758a1dfc241cb04cdb12e44af77f92b55
|
|
Cause keystone start script to exit on any errors (permitting kubernetes
to reschedule the pod).
Closes-bug: 1379057
Change-Id: Ide2eac6495250c8cba91cf9b7409dcb313f6f74b
|
|
cause rabbitmq start script to exit on any errors
Change-Id: I08b12e25061048e1fda8e74ce8a62d16b6ddf6db
|
|
This adds a /opt/kolla/kolla-common.sh to the base image as a place to
put commonly used functions. The goal is to avoid code duplication
across all the images created from this base image.
Change-Id: Ib670fe369bb8048aa69979b74a984fa4ddaae7d9
|
|
make sure that DB_ROOT_PASSWORD is in quotes to prevent errors from
shell metacharacters in the password.
Change-Id: I586ba7bb1d518d4ebfef257f92d315684843dd9b
|
|
these tools are required by almost all of our images.
Change-Id: I217b766a0c573e530da03aa81a7caf4548b0d2b3
|
|
our Dockerfile was missing "yum clean all", causing a large yum cache to
get baked into the image.
Change-Id: Ib9942a12b8a14c7e04cf8ae3184cdefcdc5a4652
|
|
this simply makes the source file match the installed name of the
script.
Change-Id: I5e7296780a34f36e28419b49e185be689e4745ad
|
|
nova-libvirt doesn't make sense as a name since nova is not the
upstream of libvirt
Change-Id: I3e396b5a0897649312f3552a791c82429013f5ae
|
|
- use new yaml config files
- provide separate service- and pod- start/stop scripts
Change-Id: Iaff2a5b4d5a33467a9d10b10e9bd5c922eeed3aa
|
|
Change-Id: I7edbd3a59007d9e2f7f5ab5e4c020eeb58d03dd3
|
|
|
|
|
|
|
|
|