From 93140c94537651413b511e1866c7d9dd8587a0ae Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Thu, 10 Oct 2013 09:20:09 +0200 Subject: [PATCH] Do not use os= in Config Reference The Config Reference does not profile for the os variable and thus all occurences of os=... are shown which leads to confusion. Add proper wording for all examples. Change-Id: I77c81b92e95d1b8737b507ea439a9622ebc3d6f1 Closes-Bug: #1232864 --- doc/common/section_dashboard_customizing.xml | 12 ++++-- doc/common/section_hyper-v.xml | 30 ++++++------- doc/common/section_kvm.xml | 44 ++++++++++++++------ doc/common/section_qemu.xml | 23 ++++++---- 4 files changed, 70 insertions(+), 39 deletions(-) diff --git a/doc/common/section_dashboard_customizing.xml b/doc/common/section_dashboard_customizing.xml index eaa0b59e21..d1f6639f93 100644 --- a/doc/common/section_dashboard_customizing.xml +++ b/doc/common/section_dashboard_customizing.xml @@ -125,9 +125,15 @@ text-decoration: none; Restart apache: - $ sudo service apache2 restart - $ sudo service httpd restart - $ sudo service apache2 restart + On Ubuntu: + $ sudo service apache2 restart + + On Fedora, RHEL, CentOS: + $ sudo service httpd restart + + On openSUSE: + $ sudo service apache2 restart + Reload the dashboard in your browser to view your diff --git a/doc/common/section_hyper-v.xml b/doc/common/section_hyper-v.xml index 82bbf582c3..db5b528d94 100644 --- a/doc/common/section_hyper-v.xml +++ b/doc/common/section_hyper-v.xml @@ -38,13 +38,13 @@ Network time services must be configured to ensure proper operation of the Hyper-V compute node. To set network time on your Hyper-V host you will need to run the following commands - + C:\net stop w32time - + C:\w32tm /config /manualpeerlist:pool.ntp.org,0x8 /syncfromflags:MANUAL - + C:\net start w32time @@ -56,10 +56,10 @@ To quickly enable an interface to be used as a Virtual Interface the following PowerShell may be used: - + PS C:\$if = Get-NetIPAddress –IPAddress 192* | Get-NetIPInterface - + PS C:\New-VMSwitch -NetAdapterName $if.ifAlias -Name yourbridgename –AllowManagementOS $false @@ -68,10 +68,10 @@ To prepare the Hyper-V node to be able to attach to volumes provided by cinder you must first make sure the Windows iSCSI initiator service is running and started automatically. - + C:\sc start MSiSCSI - + C:\sc config MSiSCSI start="auto" @@ -138,20 +138,20 @@ The openstack-compute service deployed with the setup must run with domain credentials. You can set the service credentials with: - + C:\sc config openstack-compute obj="DOMAIN\username" password="password" How to setup live migration on Hyper-V To enable shared nothing live migration run the 3 PowerShell instructions below on each Hyper-V host: - + PS C:\Enable-VMMigration - + PS C:\Set-VMMigrationNetwork IP_ADDRESS - + PS C:\Set-VMHost –VirtualMachineMigrationAuthenticationTypeKerberos @@ -227,7 +227,7 @@ The following python packages need to be installed via easy_install or pip. Run the following replacing PACKAGENAME with the packages below: - + C:\c:\Python27\Scripts\pip.exe install PACKAGE_NAME @@ -313,7 +313,7 @@ installer and follow the prompts in the installation wizard. The default should be acceptable for the needs of the document. Once installed you may run the following to clone the Nova code. - + C:\git.exe clone https://github.com/openstack/nova.git @@ -355,7 +355,7 @@ connection=mysql://nova:passwd@IP_ADDRESS/novahttp://technet.microsoft.com/en-us/library/cc772480.aspx Once you have successfully created a virtual machine, you can then upload the image to glance using the native glance-client: - + C:\glance image-create --name="VM_IMAGE_NAME" --is-public=true --container-format=bare --disk-format=vhd @@ -363,7 +363,7 @@ connection=mysql://nova:passwd@IP_ADDRESS/novaRunning Compute with Hyper-V To start the nova-compute service, run this command from a console in the Windows server: - + C:\C:\python27\python.exe c:\openstack\nova\bin\nova-compute.py diff --git a/doc/common/section_kvm.xml b/doc/common/section_kvm.xml index 71016d5ad8..3eb9bf92b0 100644 --- a/doc/common/section_kvm.xml +++ b/doc/common/section_kvm.xml @@ -81,20 +81,38 @@ libvirt_type=kvm (mainly Intel VT -x or AMD AMD-v technologies) to use KVM. In order to check if your processor has VT support (which has to be enabled in the - BIOS), issue as - root:# apt-get install cpu-checker + BIOS), follow on Ubuntu these steps: + + + Issue as root on Ubuntu: + # apt-get install cpu-checker # kvm-ok - $ egrep '(vmx|svm)' --color=always /proc/cpuinfo - - If KVM is supported, the output should look something like: -INFO: /dev/kvm exists + + + If KVM is supported, the output should look something like: +INFO: /dev/kvm exists KVM acceleration can be used - flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm arat dtherm tpr_shadow vnmi flexpriority ept vpid - - If KVM is not supported, the output should look something - like:INFO: Your CPU does not support KVM extensions -KVM acceleration can NOT be used - If KVM is not supported, you should get no output. + + + If KVM is supported, the output should look something like: +INFO: /dev/kvm exists +KVM acceleration can be used + + + On other distributions, follow these steps: + + + Run the following as user: + $ egrep '(vmx|svm)' --color=always /proc/cpuinfo + + + If KVM is supported, the output should look something like: + flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm pcid sse4_1 sse4_2 popcnt lahf_lm arat dtherm tpr_shadow vnmi flexpriority ept vpid + + + If KVM is not supported, you should get no output. + + Some systems require that you enable VT support in the system BIOS. If you believe your processor supports hardware acceleration but the above command produced no output, you may need to reboot your machine, enter the system BIOS, and enable the VT @@ -215,7 +233,7 @@ libvirt_cpu_model=Nehalem kernel module, as root: # modprobe vhost_net -
+
Troubleshooting Trying to launch a new virtual machine instance fails with the ERROR state, and the following diff --git a/doc/common/section_qemu.xml b/doc/common/section_qemu.xml index e51031fd51..ff6f021585 100644 --- a/doc/common/section_qemu.xml +++ b/doc/common/section_qemu.xml @@ -28,8 +28,15 @@ libvirt_type=qemu For some operations you may also have to install the guestmount utility: - $> sudo apt-get install guestmount - $> sudo yum install libguestfs-tools + On Ubuntu: + $> sudo apt-get install guestmount + + On RHEL, Fedora or CentOS: + $> sudo yum install libguestfs-tools + + On openSUSE: + $> sudo zypper install guestfs-tools + The QEMU hypervisor supports the following virtual machine image formats: @@ -42,24 +49,24 @@ libvirt_type=qemu VMWare virtual machine disk format (vmdk) -
Tips and fixes for QEMU on RHEL +
+ Tips and fixes for QEMU on RHEL If you are testing OpenStack in a virtual machine, you need to configure nova to use qemu without KVM and hardware virtualization. The second command relaxes SELinux rules to allow this mode of operation - (https://bugzilla.redhat.com/show_bug.cgi?id=753589). The + ( + https://bugzilla.redhat.com/show_bug.cgi?id=753589). The last two commands here work around a libvirt issue fixed in RHEL 6.4. Note nested virtualization will be the much slower TCG variety, and you should provide lots of memory to the top level guest, as the OpenStack-created guests default to 2GM RAM with no overcommit. - The second command, setsebool, may take a while. + The second command, setsebool, may take a while. + $> sudo openstack-config --set /etc/nova/nova.conf DEFAULT libvirt_type qemu $> sudo setsebool -P virt_use_execmem on $> sudo ln -s /usr/libexec/qemu-kvm /usr/bin/qemu-system-x86_64 $> sudo service libvirtd restart - -
-