diff --git a/doc/source/activeengine.rst b/doc/source/activeengine.rst index 3b4129e..d44e3b0 100644 --- a/doc/source/activeengine.rst +++ b/doc/source/activeengine.rst @@ -13,7 +13,7 @@ Installation and Configuration of zvmguestconfigure Cloudlib4zvm supports initiating changes to a Linux on z Systems virtual machine while Linux is shut down or the virtual machine is logged off. The changes to Linux are implemented using an activation engine (AE) that is run when Linux is booted the next time. The 1st active engine, zvmguestconfigure, must be installed -in the Linux on z Systems virtual server so it can process change request files transmitted by the cloudlib4sdk +in the Linux on z Systems virtual server so it can process change request files transmitted by the cloudlib4zvm service to the reader of the virtual machine as a class X file. zvmguestconfigure script should be installed in a machine that can be managed while it is logged off. This diff --git a/doc/source/imageguide.rst b/doc/source/imageguide.rst index c59647e..4e0e4bb 100644 --- a/doc/source/imageguide.rst +++ b/doc/source/imageguide.rst @@ -25,25 +25,15 @@ Image Requirements updated zvmguestconfigure installed * An image deployed on a compute node must match the disk type supported by that compute node, as - configured by the zvm_diskpool_type property in the nova.conf configuration file. A compute node + configured by the zvm_diskpool_type property in the zvmsdk.conf configuration file. A compute node supports deployment on either an ECKD or FBA image, but not both at the same time. If you wish to switch image types, you need to change the zvm_diskpool_type and zvm_diskpool properties in the - nova.conf file, accordingly. Then restart the nova-compute service to make the changes take effect. - + zvmsdk.conf file, accordingly. Then restart the nova-compute service to make the changes take effect. + * If you deploy an instance with an ephemeral disk, both the root disk and the ephemeral disk will be - created with the disk type that was specified by zvm_diskpool_type property in the nova.conf file. That + created with the disk type that was specified by zvm_diskpool_type property in the zvmsdk.conf file. That property can specify either ECKD or FBA. -* When resizing, remember that you can only resize an instance to the same type of disk. For example, if - an instance is built on an FBA type disk, you can resize it to a larger FBA disk, but not to an ECKD - disk. - -* For glance image-create, it is strongly suggested that you capture an instance with a root disk size no - greater than 5GB. - -* For nova boot, resize, it is recommended that you deploy an instance with a root disk size no greater than - 5GB. - * The network interfaces must be IPv4 interfaces. * Image names should be restricted to the UTF-8 subset, which corresponds to the ASCII character set. In @@ -54,7 +44,7 @@ Image Requirements * The virtual server/Linux instance used as the source of the new image should meet the following criteria: 1. The root filesystem must not be on a logical volume. - 2. The minidisk on which the root filesystem resides should be a minidisk of the same type as + 2. The minidisk on which the root filesystem resides should be a minidisk of the same type as desired for a subsequent deploy (for example, an ECKD disk image should be captured for a subsequent deploy to an ECKD disk). @@ -63,9 +53,7 @@ Image Requirements 4. The root disk should have a single partition. - 5. The image being captured should support SSH access using keys instead of specifying a password. - - 6. The image being captured should not have any network interface cards (NICs) defined below virtual + 5. The image being captured should not have any network interface cards (NICs) defined below virtual address 1100. In addition to the specified criteria, the following recommendations allow for efficient use of the image: diff --git a/doc/source/index.rst b/doc/source/index.rst index 7750a18..9c5ea59 100644 --- a/doc/source/index.rst +++ b/doc/source/index.rst @@ -19,17 +19,17 @@ Welcome to nova-zvm's documentation! Welcome to nova-zvm driver's documentation! -System z is a family name used by IBM for all of its mainframe computers. -IBM System z are the direct descendants of System/360, announced in 1964, -and the System/370 from 1970s, and now includes the IBM System z9, -the IBM System z10 and the newer IBM zEnterprise. System z is famous for +IBM Z is a family name used by IBM for all of its mainframe computers. +IBM Z are the direct descendants of System/360, announced in 1964, +and the System/370 from 1970s, and now includes the IBM System z13, +the IBM System z14 and the newer IBM zEnterprise. IBM Z is famous for its high availability and used in government, financial services, retail, manufacturing, and just about every other industry. -z/VM is a hypervisor for the IBM System z platform that provides a highly +z/VM is a hypervisor for the IBM Z platform that provides a highly flexible test and production environment. z/VM offers a base for customers who want to exploit IBM virtualization technology on one of the industry's -best-of- breed server environments, the IBM System z family. +best-of-breed server environments, the IBM Z family. zVM drivers, consist of a set of drivers/plugins for different OpenStack components, enables OpenStack to communicate with z/VM hypervisor to manage z/VM system and diff --git a/doc/source/planning.rst b/doc/source/planning.rst index f65cc38..eba69cd 100644 --- a/doc/source/planning.rst +++ b/doc/source/planning.rst @@ -11,12 +11,7 @@ z/VM System Requirements * A supported version of z/VM 6.4. -* In order to use live migration, the z/VM system must be configured in a Single System Image (SSI) - configuration, and must have been created using the IBM-provided installation instructions for SSI - configurations. - -* The appropriate APARs installed, the current list of which can be found at z/VM cloud connector Maintenance - (http://www.vm.ibm.com/sysman/xcmntlvl.html) and z/VM OpenStack Cloud Information +* The appropriate APARs installed, the current list of which can be found at z/VM OpenStack Cloud Information (http://www.vm.ibm.com/sysman/osmntlvl.html). .. note:: diff --git a/doc/source/topology.rst b/doc/source/topology.rst index be0d037..0db0fc8 100644 --- a/doc/source/topology.rst +++ b/doc/source/topology.rst @@ -66,8 +66,8 @@ zvm cloud connector. } } -Compare between vmware ----------------------- +Compare with vmware openstack driver +------------------------------------ Here's architecture comparsion between z/VM and vmware enablement for openstack.