Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 910633 Details for
Bug 1110069
Create Quick Start-Packstack article
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Dahms review
PackStack_QSG (text/plain), 4.36 KB, created by
Summer Long
on 2014-06-20 05:11:07 UTC
(
hide
)
Description:
Dahms review
Filename:
MIME Type:
Creator:
Summer Long
Created:
2014-06-20 05:11:07 UTC
Size:
4.36 KB
patch
obsolete
>Product: Red Hat Enterprise Linux OpenStack Platform 5 >Guide: Quick Deploy OpenStack using PackStack >Link: http://file.bne.redhat.com/~slong/docs/Red-Hat-Guides/QuickStart-Packstack/ > >Spelling: >N/A > >Links: >No issues with external links. > >Comments: >At the beginning of the document, would it be possible to include a short description of what PackStack is and approximately how long the procedures in the guide will take? Coming in as a person without much context, information such as this might prove a handy reference to have. What do you think? DONE > >Line Edit: > > >################################################## >1.1. Prerequisites >################################################## > > Dumb question: What is an all-in-one deployment, and why are we doing this instead of a component-based approach? ADDED to intro > > s/See for details:Single-node Deployment Requirements/See for details: Single-Node Deployment Requirements/ DONE > > >################################################## >1.2. Install OpenStack >################################################## > >Procedure 1. Enable OpenStack Repositories > >Step 1. > > s/requires your subscription user and password):/requires your subscription user name and password):/ > >Step 4. DONE > > Are the utility packages a must-have for the trial? If not, would it be simpler to leave them out here? > NEEDED (utils include yum-config-manager and believe plugin-priorities are for packstack) > >Step 5. > > I ran into some trouble with this step, which would result in the following output when run as is: > > [root@localhost yum.repos.d]# yum-config-manager --enable --enable=rhel-7-server-openstack-rpms \ > > --setopt="rhel-7-server-openstack-rpms.priority=1" > Loaded plugins: langpacks, priorities, product-id > Usage: "yum-config-manager [options] [section] > > Command line error: --enable option does not take a value > > Changing the syntax to the following completed without errors - > > s/# yum-config-manager --enable --enable=rhel-7-server-openstack-rpms \/# yum-config-manager --enable rhel-7-server-openstack-rpms \/ >DONE > >Procedure 2. Adjust Network Manager and Firewall > >Step 2. > > s/Open up ports for Dashboard access/Open up ports for Dashboard access:/ >DONE > >Procedure 3. Install and Run PackStack > >Step 2. > > Dumb question - What will running PackStack do and how long does it take? >ADDED to title (time needed placed in Abstract section. > s/Install the Packstack package:/Install the PackStack package:/ >DONE > >################################################## >â 2. Start up >################################################## > >2.1 Launch an Instance > > Dumb question for 2.1 - What is an instance? ADDED to header > Dumb question for 2.1 - What user should I log in as? Admin? ADDED 'Demo' (good catch, managed to delete that somehow.) >Step 1. > > s/In your browser, sign into/In your browser, sign in to/ DONE > s/Figure 1. Log In Screen/Figure 1. Login Screen/ DONE > >Step 2. > > My dashboard opened to the Admin tab - I had to figure out that the Compute > Access & Security option was in the Projects tab. Would it be beneficial to add a step to click on the Projects tab first? NOT NEEDED if you sign in as 'Demo' (Projects tab is the then the default). > >Step 3. > > Dumb question - what is a key pair, and do I need it for this evaluation? > > s/On the Keypairs tab, click the Create Keypair button. The Create Keypair dialog is displayed./On the Keypairs tab, click the Create Key Pair button. The Create Key Pair dialog is displayed./ > s/Figure 2. Create Keypair/Figure 2. Create Key Pair/ > s/Specify a name in the Keypair Name field, and click the Create Keypair button./Specify a name in the Keypair Name field, and click the Create Keypair button./ > s/ssh/SSH/ >REMOVED > >Step 4. > > s/Select the 'Boot from image option/Select the <guilabel>Boot from image</guilabel> option/ USED ' ' to delineate (not a label) > s/from the Instance Boot Source dropdown list/from the Instance Boot Source drop-down list/ DONE > s/Select the 'cirros (12.5 MB)' image from the dropdown list/Select the 'cirros (12.5 MB)' image from the drop-down list/ DONE > >Step 5. > > s/Click the Manage Compute > Volumes menu/Click the Compute > Volumes menu/ DONE > "and select Edit Attachments. " â 'select' is also bold, and should be in standard type. DONE > >2.2 Log into your New Instance > > s/Log into your/Log in to your/ > >Step 3. > > s/Log in using the CirrOS image's user and password,/Log in using the CirrOS image's user name and password,/ > > >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1110069
: 910633