- Sep 12, 2019
-
-
Mark Goddard authored
Change-Id: I593b06c447d156c7a981d1c617f4f9baa82884de Closes-Bug: #1841175
-
- Sep 11, 2019
-
-
Zuul authored
-
Zuul authored
-
Mark Goddard authored
This is required for the dict2items filter. Change-Id: I60a04e839bf06506ff36c2631a286130d5fde972
-
Xing Zhang authored
According to [1]: IP address used in the IP options can be in either IPv4 or IPv6 format. DNS can be used for IPv4 only, IPv6 only and dual stack. Also should have FQDNs in subjectAltName per current[2]. [1] https://www.openssl.org/docs/man1.0.2/man5/x509v3_config.html [2] https://support.google.com/chrome/a/answer/7391219 Partially-Implements: blueprint ipv6-control-plane Change-Id: Ibad8f8c734984aeda8ddac1a5db39875bc242bbf
-
pangliye authored
From version 1.3, the web admin interface is no longer available in InfluxDB. https://docs.influxdata.com/influxdb/v1.3/administration/differences/#web-admin-ui-removal Change-Id: I1dce61a9c40a407882cfcd520ca491b4dee734ae
-
- Sep 10, 2019
-
-
Zuul authored
-
liyingjun authored
Change-Id: Idee76f6da357c600d52b4280d29b685ed443191a
-
Hongbin Lu authored
After the integration with placement [1], we need to configure how zun-compute is going to work with nova-compute. * If zun-compute and nova-compute run on the same compute node, we need to set 'host_shared_with_nova' as true so that Zun will use the resource provider (compute node) created by nova. In this mode, containers and VMs could claim allocations against the same resource provider. * If zun-compute runs on a node without nova-compute, no extra configuration is needed. By default, each zun-compute will create a resource provider in placement to represent the compute node it manages. [1] https://blueprints.launchpad.net/zun/+spec/use-placement-resource-management Change-Id: I2d85911c4504e541d2994ce3d48e2fbb1090b813
-
- Sep 09, 2019
- Sep 07, 2019
- Sep 06, 2019
-
-
Q.hongtao authored
Change-Id: I124cba4bfe85e76f732ae618619594004a5c911f
-
- Sep 05, 2019
-
-
Marcin Juszkiewicz authored
Instead of changing Docker daemon command line let's change config for Docker instead. In /etc/docker/daemon.json file as it should be. Custom Docker options can be set with 'docker_custom_config' variable. Old 'docker_custom_option' is still present but should be avoided. Co-Authored-By:
Radosław Piliszek <radoslaw.piliszek@gmail.com> Change-Id: I1215e04ec15b01c0b43bac8c0e81293f6724f278
-
- Sep 04, 2019
-
-
Zuul authored
-
Xing Zhang authored
add clear old environment set openstack client to use internalURL set manila client to use internalURL Change-Id: I263fa11ff5439b28d63a6a9ce7ba460cb56fb8e2
-
- Sep 03, 2019
-
-
Doug Szumski authored
The output from `nova-manage cell_v2 list_cells --verbose` contains an extra column, stating whether the cell is enabled or not. This means that the regex never matches, so existing_cells is always empty. This fix updates the regex by adding a match group for this field which may be used in a later change. Unfortuately the CLI doesn't output in JSON format, which would make this a lot less messy. Closes-Bug: #1842460 Change-Id: Ib6400b33785f3ef674bffc9329feb3e33bd3f9a3
-
Zuul authored
-
- Sep 02, 2019
-
-
Manuel Rodriguez authored
Allows enabling neutron port forwarding plugin and l3 extension to forward ports from floating IP to a fixed neutron port. Change-Id: Ic25c96a0ddcf4f69acbfb7a58acafec82c3b0aed Implements: blueprint enable-l3-port-forwarding
-
Zuul authored
-
Pierre Riteau authored
Commit d6864438 disabled these deprecated plugins more than three years ago. Change-Id: I2dd2a89a7aa2c4a54882a8b0aa8d23d874c0e4cc Closes-Bug: #1839172
-
- Sep 01, 2019
- Aug 30, 2019
-
-
Joseph M authored
nova.conf currently uses the [neutron] "url" parameter which has been deprecated since 17.0.0. In multi-region environments this can cause Nova to look up the Neutron endpoint for a different region. Remove this parameter and set region_name and valid_interfaces to allow the correct lookup to be performed. Change-Id: I1bbc73728439a460447bc8edd264f9f2d3c814e0 Closes-Bug: #1836952
-
Jan Horstmann authored
Upstream ironic went from $net_default_ip to $net_default_mac in ironic/drivers/modules/master_grub_cfg.txt with https://review.opendev.org/#/c/578959/ This commit makes the same change for ansible/roles/ironic/templates/ironic_pxe_uefi.default.j2 Using $net_default_ip breaks ironic standalone deployments with [dhcp]dhcp_provider = none Change-Id: I2ca9a66d2bdb0aab5cd9936c8be8206e6ade3bd5 Closes-Bug: 1842078
-
- Aug 29, 2019
-
-
Will Szumski authored
This resolves an issue where the web browser would complain that it was trying to connect to insecure websocket when using HTTPS with horizon. Change-Id: Ib75cc2bc1b3811bc31badd5fda3db3ed0c59b119 Closes-Bug: #1841914
-
Will Szumski authored
Change-Id: Ic80dbe1f4f7289fe2c2143125a381cec4586f7ef Closes-Bug: #1841908
-
- Aug 28, 2019
- Aug 27, 2019