- Feb 25, 2019
-
-
Christian Berendt authored
Change-Id: Id8276448c6e779b2b4a0aafee45d953c4f009fc1
-
Zuul authored
-
Zuul authored
-
- Feb 22, 2019
- Feb 21, 2019
-
-
Michal Nasiadka authored
Change-Id: Iebd98acf03418817d3707c4a117771b73da80166
-
Mark Goddard authored
backport: rocky Not including this means that SoftwareDeployments do not have a configured region (it's set to 'null'), and can therefore not communicate back to the heat API. In particular, this breaks Magnum with the following error in the journal on the deployed servers: publicURL endpoint for orchestration service in null region not found Change-Id: Ia2c18ef10727391812368c958262a92385374ace Co-Authored-By:
John Garbutt <john@stackhpc.com> Closes-Bug: #1817051
-
- Feb 20, 2019
-
-
Mariusz authored
Use "{{ node_config_directory }}/murano-api/" for `murano-api` and "{{ node_config_directory }}/murano-engine/" for `murano-engine`, so correct `config.json` are mounted in containers. Change-Id: I824ff00f6b86aac3eab5dc6fd01728653b4661d1 Closes-Bug: 1811716
-
- Feb 19, 2019
-
-
Doug Szumski authored
By parsing the creation_time timestamp in Logstash, Elasticsearch can parse it correctly. This closes a bug where the creation_time timestamp was shown as a date shortly after the epoch (1970) when viewed in Kibana. Closes-Bug: #1816585 Change-Id: I00decfe94607845ef0eae9bec631a0e729aac3fa
-
Doug Szumski authored
This commit enables two settings which are useful when restarting a Kafka node as part of a cluster. The first supports moving partitions for which a node being restarting is the leader to another broker, and the second supports automatically rebalancing partitions when the node rejoins the cluster. See the documentation for more details: https://kafka.apache.org/10/documentation.html#basic_ops_restarting Change-Id: I0718fca08ea116db926b348e3e6e3bc2373db1fb
-
Kien Nguyen authored
Vitrage supports new Prometheus configuration now [1]. Kolla should allow user to configure this configuration file. [1] https://review.openstack.org/#/c/630514/ Change-Id: I84072d90b0342c6d460ee733ba646a5fb787faa9
-
ZhongShengping authored
This is a mechanically generated patch to add a unit test job running under Python 3.7. See ML discussion here [1] for context. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-October/135626.html Change-Id: Ice5e11c244b48812e786ef188b4110e6d57b5445 Story: #2004073 Task: #27423
-
- Feb 18, 2019
-
-
Maciej Kucia authored
'in' expresion matches substrings, therefore it is possible that following expression will fail: inventory_hostname in groups['groupname'][0] for example when: inventory_hostname = 'my-host-a' groups['groupname'][0] = 'my-host-a1' The result is running task on multiple hosts rather than single one. Such action might result in playbook failure Change-Id: Ibe2d5ca2f9502a8140a895ab3ac7abc5076ce2ff Signed-off-by:
Maciej Kucia <m.kucia@partner.samsung.com>
-
Zuul authored
-
Zuul authored
-
Zuul authored
-
- Feb 15, 2019
-
-
Zuul authored
-
Michal Nasiadka authored
Those issues intermittently show up in various branches, in all cases it's wrong path used to resolveip binary. Similar to the recent kolla-ansible-ubuntu-source job failures. Change-Id: I8cce42b60897e4ceb8d3b0bd5181fda88b10c2b8
-
- Feb 14, 2019
-
-
Doug Szumski authored
Until the Monasca Kafka client fork is removed it is currently required to run Kafka in compatibility mode. It is also necessary to disable an optimisation in the Kafka brokers to clean up idle connections. This is because the optimisation was added after the Monasca Kafka client was forked, and the client hasn't been updated since. These settings are now applied automatically when Monasca is enabled. Change-Id: I6935f1fb29f4f731cf3c9a70a0adf4d5812ca55e
-
Mohamed El Gindi authored
Karbor provider configs can be injected/managed from 'node_custom_config' var openstack-infra.conf will still be created if no custom providers present Closes-Bug #1814464 Change-Id: I500daae80596cb7b7342fd8d4affa8f901b24a13
-
Zuul authored
-
Pedro Alvarez authored
Change-Id: I3defe0c38f41d7335e1cbafb75523c3cd44323ee
-
wu.chunyang authored
when ceph_mon and ceph_osd start failed, add debug option will print more info. now when ceph_mon and ceph_osd containers start failed, docker logs ceph_mon print none log Closes-Bug: #1815707 Change-Id: I3c5086019808a9738714f5279ec74cbb9b7a8587
-
wu.chunyang authored
when customize policy.json,disable cinder-backup caused deploy failed Change-Id: I50bf72e52bff27dc4abc7b13436b2115f6a9e955 Closes-Bug: #1802221
-
Michal Nasiadka authored
- py35/py36 jobs are failing python 3.6 pycache also includes links - so those also need to be removed by tox testenv - kolla-ansible-ubuntu-source job is failing Without basedir set in galera.cnf - mysql_install_db looks for resolveip in /usr/sbin, instead of /usr/bin, thus complains about cannot resolving neither $HOSTNAME, nor localhost. Change-Id: I40514c0a7c43ae01c7680aac81123942be1cdef9
-
- Feb 12, 2019
-
-
Zuul authored
-
- Feb 08, 2019
-
-
Jim Rollenhagen authored
This allows nova service endpoints to use custom hostnames, and adds the following variables: * nova_internal_fqdn * nova_external_fqdn * placement_internal_fqdn * placement_external_fqdn * nova_novncproxy_fqdn * nova_spicehtml5proxy_fqdn * nova_serialproxy_fqdn These default to the old values of kolla_internal_fqdn or kolla_external_fqdn. This also adds the following variables: * nova_api_listen_port * nova_metadata_listen_port * nova_novncproxy_listen_port * nova_spicehtml5proxy_listen_port * nova_serialproxy_listen_port * placement_api_listen_port These default to <service>_port, e.g. nova_api_port, for backward compatibility. These options allow the user to differentiate between the port the service listens on, and the port the service is reachable on. This is useful for external load balancers which live on the same host as the service itself. Change-Id: I7bcce56a2138eeadcabac79dd07c8dba1c5af644 Implements: blueprint service-hostnames
-
Zuul authored
-
- Feb 07, 2019
-
-
Maciej Kucia authored
This change allows usage of IPv6 as public address Change-Id: Ie82ec5fb0ac9106b39948c67d34d5ef611a8fa21 Signed-off-by:
Maciej Kucia <m.kucia@partner.samsung.com>
-
caowei authored
Use option "enabled_filters" from group "filter_scheduler". Change-Id: I042f0b011c060f9dbc645dbdbb60068cb41c0cc8
-
- Feb 05, 2019
-
-
confi-surya authored
We can see some contribution directory is missing which exist parallel to other directories. Adding this information to README is helpful for new contributors to understand high level directory structure. Change-Id: I4ed50b49aac1e9ab21957f4ec3da1b33883ad9b1
-
Zuul authored
-
- Feb 04, 2019
-
-
Zuul authored
-
confi-surya authored
Older hacking version depends on pep8, but pep8 module is replaced by pycodestyle. This is already resolved by updating hacking version in https://review.openstack.org/#/c/627149/ pep8 is dropped, so no longer require in lower-constraints.txt. Change-Id: I585e94098de20e0f541d4182367e904fc13d2ae6
-
Mark Goddard authored
The ironic TFTP server should be accessed via the internal API network. For ironic inspector, dnsmasq.conf advertises this correctly: dhcp-option=option:tftp-server,'api_interface_address' dhcp-option=option:server-ip-address,'api_interface_address' However, ironic conductor does not set the [pxe] tftp_server variable. This means the TFTP server advertised gets the default value of $my_ip, which is set by https://docs.openstack.org/oslo.utils/latest/reference/netutils.html#oslo_utils.netutils.get_my_ipv4, typically the source IP for the default route. This change sets [pxe] tftp_server to 'api_interface_address'. Change-Id: Ic3e688b3f2b92ad9515322f49cd5f4f29d763e49 Closes-Bug: #1808347
-
confi-surya authored
README is always a first point of interaction for users/operators. So adding zookeeper info to it will help to understand its support in Kolla. Change-Id: I4829847b95575b6e83b3001e0d377ad1dd71ecfb
-
- Feb 01, 2019
-
-
Scott Solkhon authored
Change-Id: I12af64725c0beec2ece0367c3773230c57908254
-