As part of the breaking up of Access and Security, move the Key Pairs tab to a new panel under Compute. Separate patches will address Floating IPs, Security Groups, and API Access. Fixes include: - Should be significantly faster to access Key Pairs, as we are no longer running multiple API calls for the other Access & Security tabs at the same time. Hooray for speed! - Should be easier for new users to find where Key Pairs are located. - Reduce reuse of identical translatable strings - Use common templates instead of duplication - Updated policy rules and added missing rules to table get_data - Small cleanup of the Key Pair download page, which was previously using modal classes despite not being a modal. Change-Id: I66f1f65a2cb49bd10e0364b12efba4346f373ed3 Implements: blueprint reorganise-access-and-security
13 lines
853 B
HTML
13 lines
853 B
HTML
{% extends "horizon/common/_modal_form.html" %}
|
|
{% load i18n %}
|
|
|
|
{% block modal-body-right %}
|
|
<p>{% trans "Key Pairs are how you login to your instance after it is launched." %}</p>
|
|
<p>{% trans "Choose a key pair name you will recognise and paste your SSH public key into the space provided." %}</p>
|
|
<p>{% trans "SSH key pairs can be generated with the ssh-keygen command:" %}</p>
|
|
<p><pre>ssh-keygen -t rsa -f cloud.key</pre></p>
|
|
<p>{% trans "This generates a pair of keys: a key you keep private (cloud.key) and a public key (cloud.key.pub). Paste the contents of the public key file here." %}</p>
|
|
<p>{% trans "After launching an instance, you login using the private key (the username might be different depending on the image you launched):" %}</p>
|
|
<p><pre>ssh -i cloud.key <username>@<instance_ip></pre></p>
|
|
{% endblock %}
|