| Age | Commit message (Collapse) | Author | Files | Lines |
|
Note: This should not result in any behavior changes in regular Kolla, just Kolla-Kubernetes and only when you've overridden stuff in globals.yml
Binds to the api_interface_address variable and uses the keystone and memcached facts we defined in earlier patches.
Co-authored-by: Ryan Hallisey <rhallise@redhat.com>
Change-Id: I8610f4adaa557a21fedd05601e10f5c308fd7ce3
Partially-implements: blueprint api-interface-bind-address-override
|
|
Change-Id: Ie98072ded6fee96b4e8c43cfe5124ead8e73e885
Implements: blueprint ansible-unit-tests
|
|
According to
http://docs.openstack.org/developer/designate/getting-started.html#initialize-start-the-central-service
designate database bootstrap to be done by designate-manage database sync.
Was also missing designate-manage pool_manager_cache sync.
designate-manage command is packaged with designate-central.
Boot strap commands moved to designate-central.
Added creation of log directories.
Added python2-oslo-reports and python2-suds for bootstrap to complete.
Change-Id: I3896064b0abb31c96307b16005a340fc193aac3c
Closes-Bug: 1610795
|
|
The --user-domain parameter is required when adding the role for
Heat. Without it, the command fails and the bootstrap
container exits early with the error message:
"No user with a name or ID of 'heat_domain_admin' exists."
Change-Id: I6f813edde3f437bca3ef521a43454146082bc5f5
Closes-bug: #1611768
Signed-off-by: Dave Walker (Daviey) <email@daviey.com>
|
|
Change-Id: Ie70db1b18a73528b1194e4fbcf53d09fed20f4a0
Implements: blueprint kolla-host
|
|
Initiator names are generated during image build and therefore are
not unique in multi-host environment. Instead the names should be
autogenerated during first start of iscsid containers.
Change-Id: Ia439b1563c9c9d6c26d8a314fe2817ba493dacb5
Closes-Bug: 1611775
|
|
enable_rabbitmq_cluster is now a "yes" by default but you can set it
to "no" if you want to disable clustering under any circumstances.
The agreement made at OpenStack in Austin was that Kolla-Kubernetes
would concentrate on RabbitMQ and MariaDB without clustering but
with persistent storage and workload migration, then examine how to
do proper distributed functionality as the project progresses, so I
am just following what we'd already agreed upon.
First, it helps us deal with issues of version upgrades without
dealing with clustered version upgrades and the synchronization
thereof.
Second, it provides an alternative model for durability when used in
Kubernetes. Understand that, if we disable RabbitMQ's clustering,
Kubernetes is still able to re-schedule the queue off of a failed node
in ways that Kolla-Ansible is not. There are known issues with
RabbitMQ clustering, especially with auto-heal turned on. For many
small-to-mid-sized clusters, it's going to provide for a better
operator experience to have the known potential for a 30 second blip
after RabbitMQ node failure than it is to have the known potential
for partition and data loss and/or manual operations after you've
turned off auto-heal.
Kolla-kubernetes has already turned off host networking for the
RabbitMQ pod; it's safe to set the interface address in the
Kubernetes context.
The question was asked why don't I just set the RabbitMQ cluster to be
a single instance. It's unlikely that Kubernetes RabbitMQ with a
PetSet will be clustered in the same declaritive fashion as the
rabbitmq-clusterer plugin. Easier to just disable it and worry about
how to configure the kube-friendly clustered RabbitMQ at a later point
in time. Furthermore, it's an entirely valid case for many OpenStack
control planes hosted atop Kolla-Kubernetes to accept the possibility
of a 30-60 second blip in lieu of the long and questionable history
of RabbitMQ clustering in production.
Co-authored-by: Ryan Hallisey <rhallise@redhat.com>
Change-Id: I7f0cb22d29a418fce4af8d69f63739859173d746
Partially-implements: blueprint api-interface-bind-address-override
|
|
This reverts commit 4e8bf3f90da2b1b36575528a30926a575bfc4095.
It seems removing /var/lib/apt/lists is having some unintended side
effects causing apt to not find packages [0]
[0] http://logs.openstack.org/87/350587/10/check/gate-kolla-dsvm-build-ubuntu-source/c0a22a3/console.html#_2016-08-09_13_41_14_477480
Change-Id: I89042e5883f19fddbae11d75b788f87ad5d871a1
|
|
|
|
|
|
|
|
The reason for introducing this script is to be able
to launch ovsdb-server and initialize it (create external bridge and plug
external interface) in one shot. It is applicable ONLY to Kubernetes environment
and it is required for Kubernetes DaemonSet usage. The behavior in classical
Kolla has not been changed.
TrivialFix
Change-Id: I54897cc2c0f2bcaaf0411822f3409bf96e92833d
|
|
|
|
Migrate to full variable syntax in with_ loop
instead of bare variables for:
- ceph
- ceilometer
- glance
- heat
- horizon
- keystone
- mariadb
- memcached
- neutron
- nova
- rabbitmq
Change-Id: Ib925b4ecea47ac758a77739c9c7e140f06933b08
Partial-Implements: blueprint ansible2
|
|
Change-Id: I3f0873f425f49514e6f086a6baa25dc3a3ee1dd5
Closes-bug: #1560049
|
|
The heat dev environment is not functional, remove it to avoid confusions.
Change-Id: I05ac25294516270328ca1fe88f15defeea570306
Partial-bug: #1562334
|
|
Cinder-backup containers require iscsid to mount iscsi volumes
to backup if the volumes are on different storage host.
Change-Id: Ifc0a30584a4f086b71278616d34bf87863d3e6e5
Closes-Bug: 1611330
|
|
* Remove the -y for every occurance of package install
* Replace `source` with `.`
according to
http://docs.openstack.org/contributor-guide/writing-style/code-conventions.html
Change-Id: I977c5dd58207be67a5bfc96d5ae1f9958b46089a
|
|
|
|
|
|
|
|
|
|
|
|
Leverage the browser cache and compress to speed up the file transfer.
In RHEL based image, the expire and deflate module are enabled in
default. In the Debian based image, only the deflate is enabled
* Enable expire module on the Debian based image
* Enable the expire for the assets resource
* Enable the deflate for the http response
Closes-Bug: #1605907
Change-Id: If25decc38a10a21929f72a89cdb350d4ac64a5a9
|
|
|
|
|
|
|
|
|
|
Kolla's default heka pipline may not satisfy user's requirements,
for example, sending openstack log to outer log analyze system.
So it is necessary to add heka custom configuration for define
user's encoders, outputs and other plugins.
Change-Id: I48bd8d7e0afbc2d023c49c83041f87a04970bbb6
Closes-Bug: #1611164
|
|
This patchset contains customization of Dockerfile of kibana
container
Change-Id: I0081cbcfeea7d0cd270116b61f009ea1a797c330
Partially-implements: blueprint third-party-plugin-support
|
|
Ansible's template action supports replacing horizon default config with
custom config, it should only add with_first_found param to
config.yml to support this.
Change-Id: I45b8eed5b8d6c4d42672d99e41bc4eff7023a26f
Closes-Bug: #1570677
|
|
TrivialFix
Change-Id: I74d6c763116adeda620b281fec87e595df82b796
|
|
The cleanup command in the external API is a misnomer and should
be called destroy.
Change-Id: I083e80699e09bb24266ce1bf549772a5de92a49e
Closes-Bug: 1610364
|
|
|
|
This patchset contains customization of Dockerfile of Ceph
containers
Change-Id: I20bc27f2c4c6025ea35c8b48c40aee9919553254
Partially-implements: blueprint third-party-plugin-support
Signed-off-by: Eduardo Gonzalez <dabarren@gmail.com>
|
|
Change-Id: Ia8e8bf86b8512cac7a3c0b200d690b5286012813
|
|
In the case of a single node environment without haproxy, the var
"kolla_internal_vip_adress" in global.yml should be the ip address
of the host. However, the prechecks will fail, because this ip
address is used by the host node and is pingable.
This commit fixes the prechecks of a vip address properly.
When the var "enable_haproxy" is "no", this fix will skip prechecks
for a vip address.
Change-Id: I0b752f179d20f82e3d6331047ee0bd802ab99a4b
Closes-Bug: #1570935
|
|
TrivialFix
Change-Id: I7ff752fffe47e9571ea15acdad3edd4835f9e612
|
|
The files inside /var/lib/apt/lists are not needed and should be removed when
cleaning up after a package installation.
TrivialFix
Change-Id: I80e2a11e05739f3dd5bcc3bb8564d8a73ec1ab17
|
|
* Use the nova microversion api for compute service
* Use the legacy nova api for compute_legacy service
* Update the nova service and endpoint during the upgrade stage
This is what the devstack used now[0]
[0]
https://github.com/openstack-dev/devstack/blob/e777bbce3b18ce50abe683a2d96394e96a3b70bc/lib/nova#L408,L422
TrivialFix
Change-Id: I0574a3116b1dd1702b4eccb2394538866675c4c1
|
|
Make the kolla_keystone_service can update the following fields
* service.name
* service.description
* endpoint.url
TrivialFix
Change-Id: If239a518b0217cfc105388ae5e298a8904ac2af5
|
|
|
|
|
|
Github is just a mirror of the OpenStack git-repo.
Changed from Github to OpenStack git url wherever possible.
Change-Id: I7941ef86967de4efe7f23ff9fb11ec86c793901e
|
|
Networking-SFC is a neutron big-tent project
Kolla does not have Networking-SFC agent support for now. This
is essential for Service Function Chaining use case. Build Networking-SFC
Container.
Change-Id: I67b4d6e061dbe31e2211cd3210726ab4c30cd087
Partially-Implements: blueprint enable-networking-sfc-support
|
|
|
|
This patchset contains customization of Dockerfile
of kolla-toolbox containers.
Change-Id: Idd141935012874e1184c1d88cd0e0fdc37e1b6c9
|
|
|
|
Only install English locales and do not install documentation.
http://wiki.ubuntu.com/ReducingDiskFootprint
Change-Id: I129cd7cc8777112acb751c600feb8900c0c2a461
|
|
|