yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #55379
[Bug 1615371] Re: Restrict user private network cidr input
Already documented in original patch, this is just an incorrect use of
DocImpact.
** Changed in: horizon
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1615371
Title:
Restrict user private network cidr input
Status in OpenStack Dashboard (Horizon):
Invalid
Bug description:
https://review.openstack.org/135877
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/horizon" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.
commit 134210195578bb568ec48228246fc7e399e80ba2
Author: LIU-Yulong <liuyulong@xxxxxxxx>
Date: Thu Nov 20 14:53:48 2014 +0800
Restrict user private network cidr input
If the user's private network has the same CIDR as the public
network, there will be an error. The router is unable to set
the gateway properly when the private and public CIDR overlap.
This patch add setting 'ALLOWED_PRIVATE_SUBNET_CIDR' to decide
whether to restrict user private network cidr input. And admin
dashboard network panel was not restricted.
Example:
ALLOWED_PRIVATE_SUBNET_CIDR = {'ipv4': ['192.168.0.0/16',
'10.0.0.0/8'],
'ipv6': ['fc00::/7',]}
By default, leave the 'ipv4' and 'ipv6' with empty lists,
then user subnet cidr input will not be restricted.
DocImpact
Implements blueprint: restrict-private-network-input
Change-Id: I6b2ee58447d517c1c40344b8f4dd95968638da5b
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1615371/+subscriptions
References