From 3ee40f3e9369e336fee7fe74dfb6404eab041f1a Mon Sep 17 00:00:00 2001 From: Emilien Macchi Date: Mon, 13 Feb 2017 11:47:35 -0500 Subject: [PATCH] Add release note for services endpoint change Add reno for: - I1213a83ef8693c1cca1d20de974f7949a801d9f1 - Ib1103c00ddb7d6d624f4911147197d8355a3a6dd Change-Id: Iecbbab5aeeade46b5cc238bc5542396e78db751c --- .../notes/keystone_internal-53cc7b24ebdd9df4.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 releasenotes/notes/keystone_internal-53cc7b24ebdd9df4.yaml diff --git a/releasenotes/notes/keystone_internal-53cc7b24ebdd9df4.yaml b/releasenotes/notes/keystone_internal-53cc7b24ebdd9df4.yaml new file mode 100644 index 0000000000..1f41073bca --- /dev/null +++ b/releasenotes/notes/keystone_internal-53cc7b24ebdd9df4.yaml @@ -0,0 +1,9 @@ +--- +other: + - | + Use Keystone internal endpoint instead of admin for services. + The admin endpoint is listening on the ctlplane network by default; + services should ideally be using the internal api network for this kind + of traffic, as the ctlplane network is mostly for provisioning. On the + other hand, the admin endpoint shouldn't be as relevant with services + switching to keystone v3.