diff options
| author |   blsaws <blsaws@hotmail.com> | 2015-10-29 12:12:49 +0900 |
|---|---|---|
| committer | blsaws <blsaws@hotmail.com> | 2015-10-29 12:12:49 +0900 |
| commit | 931850395b39d0f40d198d59cb58d0578965222f (patch) | |
| tree | 2c78dff053b59555458215c0778bad14ee18165a | |
| parent | 52a6e0e6056fd355ce363d78150993f00bd144b7 (diff) | |
Add DMZ deployment policy use case.
JIRA: COPPER-3
Change-Id: Iea9a0c15738f992870d118206b2740ba25df0021
Signed-off-by: blsaws <blsaws@hotmail.com>
| -rw-r--r-- | design_docs/usecases.rst | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/design_docs/usecases.rst b/design_docs/usecases.rst index 7d55c87..c4e6abd 100644 --- a/design_docs/usecases.rst +++ b/design_docs/usecases.rst @@ -79,6 +79,10 @@ As implemented by OpenStack Heat using scheduler hints: - network: {get_param: network} scheduler_hints: {different_host: {get_resource: serv1}} +DMZ Deployment +.............. +As a service provider, I need to ensure that applications which have not been designed for exposure in a DMZ zone, are not attached to DMZ networks. + Configuration Auditing ---------------------- |