From 8f2e82b7db54cfff9315e5647bd2ba3dd6aacaad Mon Sep 17 00:00:00 2001 From: wangfaxin Date: Fri, 13 Dec 2019 10:31:44 +0800 Subject: [PATCH] Update the community page. Change-Id: I5b06cf5b3f1409fdc1c68ee80492766b3a831e88 --- working_materials/scoring.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/working_materials/scoring.txt b/working_materials/scoring.txt index 09e6ff73..f7a5071f 100644 --- a/working_materials/scoring.txt +++ b/working_materials/scoring.txt @@ -109,7 +109,7 @@ Notes: Subnet pools were introduced in Kilo but had incomplete support in Horizon at the time. A Heat resource for subnet pools was added in Mitaka, and OpenStackClient added support late in the Mitaka cycle - as well (https://review.openstack.org/#/c/279918/). If we make subnet + as well (https://review.opendev.org/#/c/279918/). If we make subnet pools advisory now, they could become required in 2017.08--in which the earliest release in the Guideline will be Mitaka. Toolkits like jClouds, Fog, and libcloud do not yet support subnet pools that I see.