From af626f68200ff6cf4b7b6e97a140a711c918aca4 Mon Sep 17 00:00:00 2001 From: Andreas Jaeger Date: Mon, 10 Mar 2014 20:19:23 +0100 Subject: [PATCH] Remove sudo usage from Image Guide Remove sudo usage and adjust prompts as needed. Add openSUSE information. Change-Id: I7d41819877e3bf17f5e8d8a64697bab7f308bdb8 --- doc/image-guide/ch_openstack_images.xml | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/doc/image-guide/ch_openstack_images.xml b/doc/image-guide/ch_openstack_images.xml index ac23385618..77ccdb9619 100644 --- a/doc/image-guide/ch_openstack_images.xml +++ b/doc/image-guide/ch_openstack_images.xml @@ -11,13 +11,12 @@ For a Linux-based image to have full functionality in an OpenStack Compute cloud, there are a few requirements. For - some of these, the requirement can be fulfilled by installing + some of these, you can fulfill the requirement by installing the cloud-init package. Read this section before you create your own image to be sure that - the image supports the OpenStack features that you plan on - using. + the image supports the OpenStack features that you plan to use. Disk partitions and resize root partition on boot @@ -227,7 +226,8 @@ You do not need a /boot partition unless your image is an older Linux distribution that requires that - /boot is not managed by LVM. + /boot is not managed by + LVM.
@@ -419,12 +419,12 @@ done variable: GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" Next, update the grub configuration. On Debian-based - operating-systems such as Ubuntu, - do:$ sudo update-grub - On Fedora-based systems such as RHEL and CentOS, - do:$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg + operating-systems such as Ubuntu, run this command: + # update-grub + On Fedora-based systems, such as RHEL and CentOS, and on + openSUSE, run this command: + # grub2-mkconfig -o /boot/grub2/grub.cfg
-
Paravirtualized Xen support in the kernel (Xen hypervisor only) @@ -514,9 +514,9 @@ done To see how the settings affect the deletion of a running instance, check the directory where the images are stored: - $ sudo ls -lash /var/lib/nova/instances/_base/ - Then look for the identifier in - /var/log/compute/compute.log: + # ls -lash /var/lib/nova/instances/_base/ + In the /var/log/compute/compute.log + file, look for the identifier: 2012-02-18 04:24:17 41389 WARNING nova.virt.libvirt.imagecache [-] Unknown base file: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810 a0d1d5d3_20 2012-02-18 04:24:17 41389 INFO nova.virt.libvirt.imagecache [-] Removable base files: /var/lib/nova/instances/_base/06a057b9c7b0b27e3b496f53d1e88810