diff options
| author |   weinstock, alan <aw2574@att.com> | 2019-04-29 20:53:16 +0000 |
|---|---|---|
| committer | weinstock, alan <aw2574@att.com> | 2019-04-29 20:53:16 +0000 |
| commit | aac693c68e535ef3716eec5cd5a9eb4ca7bc2f80 (patch) | |
| tree | e6052ea423e2ca90dba9ee9224b6358f98a8e54f | |
| parent | 006d74c72300eaa2312db2212a0419eaf7205bea (diff) | |
[VNFRQTS] Add Requirement to "Key Pairs" Section
Issue-ID: VNFRQTS-632
Change-Id: I68d03dc2c9481935df0133fc7bfe8903075c14ff
Signed-off-by: weinstock, alan <aw2574@att.com>
| -rw-r--r-- | docs/Chapter5/Heat/ONAP Heat Template Constructs.rst | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/docs/Chapter5/Heat/ONAP Heat Template Constructs.rst b/docs/Chapter5/Heat/ONAP Heat Template Constructs.rst index d4c8c01..ea87248 100644 --- a/docs/Chapter5/Heat/ONAP Heat Template Constructs.rst +++ b/docs/Chapter5/Heat/ONAP Heat Template Constructs.rst @@ -700,6 +700,20 @@ environment file (since it is public, it is not a secret key), or passed at run-time as instance-specific parameters. ONAP will never automatically assign a public/private key pair. +.. req:: + :id: R-100380 + :keyword: SHOULD + :introduced: dublin + :validation_mode: none + :target: VNF + + If a VNF requires the use of an SSH key created by OpenStack, the VNF + Heat Orchestration Template **SHOULD** create the ``OS::Nova::Keypair`` + in the base module, and expose the public key as an output value. + + This allows re-use of the key by ONAP when triggering scale out, recovery, + or other day 1 operations. + *Example (create keypair with an existing ssh public-key for {vm-type} of lb (for load balancer)):* |