Scribd
Upload
17 views5 pages

LM17

open stack

Uploaded by

Eugene Berna I
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
17 views5 pages

LM17

open stack

Uploaded by

Eugene Berna I
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

Launching an instance using the web interface

Now that we've booted an instance on the command line, let's take a look at doing the same
thing in the web interface:

1. Go ahead and log in to the web interface as the non-administrative user you
created in Chapter 3, Identity Management.
2. Under the Compute menu, select Instances and then click on the Launch
Instance button.
3. In the Launch Instance dialog, fill in a name for the instance, choose a flavor,
and select Boot from image as the boot source, as shown in the following
screenshot.
4. Select the image you uploaded in Chapter 4, Image Management.

5. Select the next tab, Access & Security. This view should already be filled in for
you. This is the view in which you can select a different SSH key pair and select
a combination of security groups for the instance. The following screenshot is a
view of the Access & Security tab:
6. Next, select the Networking tab. In this view, if you have only one tenant
network defined, it will be automatically added to the selected networks. If you
have more than one network, you will have to add one to the selected networks.
More than one network can be added to the selected networks. Each will be added
to your instance as a virtual network interface and each interface will DHCP to a
separate DHCP service to get its IP address. The following screenshot is a view of
the Networking tab:

7. Go ahead and launch the instance; the web interface will poll OpenStack to keep
you informed of the progress of the launching instance. You can watch the
instance's progress as it launches. The polling will update the web interface as the
state changes. This screenshot captures a still of the launching instance on the web
interface:
8. Click on the instance's name; there is a Log tab and a Console tab.
The Console tab will load the URL that was displayed by the get-vnc-
console command executed in Launching an Instance section. Here's a screenshot
of this page:

9. The next step is to associate a floating IP address with the instance. You can use
the button that is displayed before the instance is activated. Once the instance is
activated, you can find the associated floating IP option in the More menu on the
instance. Select Associate to associate the floating IP address with the instance:

10. Remember that a floating IP first needs to be allocated to a project before it can
be associated with an instance. Click on the + button next to the IP address
selection box. The following screenshot captures the instructions in this step:
11. Click on Allocate IP to allocate an IP to your project. Then, complete the
association with the running instance, as shown in the following screenshot:

12. Once the floating IP has been associated, it will show up in the IP address box
next to the instance. This is not an auto-update piece of information. You will
have your browser's refresh button to refresh the page to see the update. The
following screenshot captures this step:

13. The final step is to open up the security groups. Click on the Access &
Security menu, select the Security Groups tab, and click on the Manage
Rules button. In the top-right corner, click on the Add Rule button.
14. Fill out the form for ICMP, as shown in the following screenshot:
15. Repeat this for SSH and for any other port you need opened up

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy