34a567089b
This fixes mainly screens, computeroutput/userinput and also marks some filenames. A lot of prompts have been added. Change-Id: I864dc5b051bb297b61c9b2ed5464f9a35306bd68 Partial-Bug: #1217503
33 lines
1.5 KiB
XML
33 lines
1.5 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<section xmlns="http://docbook.org/ns/docbook"
|
|
xmlns:xi="http://www.w3.org/2001/XInclude"
|
|
xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0"
|
|
xml:id="nova_cli_keygen"><title>Add keypair</title>
|
|
<para>Create at least one keypair for each project. If you have
|
|
generated a keypair with an external tool, you can import it into
|
|
OpenStack. The keypair can be used for multiple instances that
|
|
belong to a project.</para>
|
|
<procedure>
|
|
<title>To add a keypair</title>
|
|
<step>
|
|
<title>Create a key</title>
|
|
<para>To create a <literal>mykey</literal> key that you can
|
|
associate with instances, run the following command:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova keypair-add mykey > mykey.pem</userinput></screen>
|
|
<para>Save the <filename>mykey.pem</filename> file to a secure
|
|
location. It enables root access to any instances with which
|
|
the <literal>mykey</literal> key is associated.</para>
|
|
</step>
|
|
<step>
|
|
<title>Import a keypair</title>
|
|
<para>To import an existing public key,
|
|
<literal>mykey.pub</literal>, and associate it with the
|
|
<literal>mykey</literal> key, run the following
|
|
command:</para>
|
|
<screen><prompt>$</prompt> <userinput>nova keypair-add --pub-key mykey.pub mykey</userinput></screen>
|
|
<para>You must have the matching private key to access instances
|
|
that are associated with this key.</para>
|
|
</step>
|
|
</procedure>
|
|
</section>
|