Use https instead of http to ensure the safety without containing our
account/password information
Change-Id: If14429d0beed57cace5a4929c56fa811920ca132
We don't maintain a long standing log file for the helper process, so
any log messages that we issue from inside it just vanish after router
cleanup.
This patch enforces syslog logging for the daemon, revealing any errors
and other messages that may be triggered by it.
Closes-Bug: #1635629
Change-Id: I8712f5f3a34fc9f403dfba06e7a64bd9eb408c4a
This will expose more details about what keepalived is doing (like
adding new VIPs, gARPs sent, config warnings and such).
Change-Id: I297f13f3debe0c80d1ad58f9031618fec3575ad0
tl;dr : without this Ocata and Pike have the same version causing
packaging issues.
https://docs.openstack.org/developer/pbr/#version
Because projects don't push a tag before milestone 1 (pike-1 here),
downstream packages are still building packages by using the version
from Ocata and it causes problems to distros because they can't test
the upgrades from Ocata to Pike.
Bumping the semver will allow us to test packages upgrades.
Note: When your version is X.Y.Z, api-break will bump X, and feature
will bump Y. In this patch, we bump X because this is the way you
bump tags over releases.
Change-Id: I7f3549852e984bb32cdaeb7d8a758c18db045b26
Sem-Ver: api-break
When run in an HA or DVR configured environment,
the test_show_router_attribute_with_timestamp API
test can fail with an 'updated_at' timestamp mismatch.
The test should check if the timestamp is >= since
post-creation code could update the object.
Closes-bug: #1679794
Change-Id: I3c58af022d1699ab05ca964b6d957dae39cf1ccc
This patch introduces support for requests where the user does
not know the segmentation details of a subport and by specifying
segmentation_type=inherit will let the trunk plugin infer these
details from the network to which the subport is connected to, thus
ignoring the segmentation_id in case it were to be specified.
This type of request is currently expected to have correct results
when the network segmentation type is 'vlan', and the network has
only one segment (provider-net extension use case).
DocImpact: Extend trunk documentation to include Ironic use case.
Closes-bug: #1648129
Depends-on: Ib510aade1716e6ca92940b85245eda7d0c84a070
Change-Id: I3be2638fddf3a9723dd852a3f9ea9f64eb1d0dd6
paginate_query was exploding when sort_keys had a
boolean column, since it was fixed in 4.18.0 of
oslo.db. This workaround is no longer needed.
Change-Id: Ie8df9c91c2828bb8886f9b175f06966fe9dd962c
The patch handles the case when a port is updated
with an IP from a new IPv6 auto-address subnet
See bug for details on how the issue can affect DHCP
functionality.
Closes-Bug: #1678104
Change-Id: If2473f2db3ca16b5f46d3280e79a49756d1c098a
Neutron-lib 1.1.0 is now out and contains the portbindings
API definition (as per commit [1]). This patch moves neutron
references over to the neutron-lib version.
NeutronLibImpact
- Consumers using the public constants within neutron's
portbindings API extension must now use the values
from neutron-lib.
[1] 87e42f993c07ae320159d5123662ee9f3bd4d903
Change-Id: I669af9b4c712877772d91a03857ab108714001d4
When neutron is deployed with hypervisor is XenServer, current
implementation will grab port's iface-id via xapi, but this isn't
the proper way:
Port's iface-id is already set when creating VM or hot plugging
VIFs in nova project, so there is no need to grab it via xapi
Change-Id: Ie07527cc89ac81ff1e3519db66925cee482f77a4
Closes-Bug: #1649747
When adding an egress rule to sg assigned remote CIDR, vms using
this sg will add a rule in iptables like -oxxxxxxxx-x -d CIDR.
But test cases for egress with prefix always using -s CIDR, which
is not correct.
Closes-Bug: #1523835
Change-Id: Ifabfe3278aa0516a222f71153e47149ff4562d5e