From Fedora Project Wiki

Line 92: Line 92:
     A.2. guestfish
     A.2. guestfish
     A.3. Other useful tools
     A.3. Other useful tools
<span style='color:orange'>--> kirsti is it an idea to add a few dos and do nots, as in what would make good use cases for virtualization, and what not?  </span>
B. Revision History
B. Revision History
=Changes to Content=
=Changes to Content=

Revision as of 12:43, 22 July 2015

Outline for Getting Started

Current TOC

This TOC should be changed -please indicate what needs changing in a different color or with an arrow. Please put your name in the line that has the change so we can track it. Thanks!


   1. Document Conventions
       1.1. Typographic Conventions
       1.2. Pull-quote Conventions
       1.3. Notes and Warnings
   2. We Need Feedback!

1. Introduction

   1.1. Who should read this guide?
   1.2. Virtualization in Fedora Linux
   1.3. Virtualization resources

2. What is virtualization and migration?

   2.1. What is virtualization? --> Lnovich ADD Here we need to add a section on "How a computer/server is virtualized - ie how it works? with a diagram. 

Add what a hypervisor is, what a host and guest are as this may be misunderstood.

   2.2. What is migration?  --> Lnovich - consider moving this elsewhere  --> kirsti when moving this elsewhere, consider changing title 2. as well 
       2.2.1. Benefits of migrating virtual machines

3. Advantages and misconceptions of virtualization

--> smccann consider rewriting as Why use virtualization --> kirsti or just Andvantages (misconceptions seems negative) --> grundblom How about considerations, features, or applications, Advantages give the idea that virtualization is best for everything, which is not the case

   3.1. Virtualization costs
   3.2. Virtualization learning curve --> kirsti suggestion to skip this 
   3.3. Performance
   3.4. Flexibility
   3.5. Disaster recovery
   3.6. Security
       3.6.1. Virtualization security features--> kirsti suggestion to make this 3.6 
   3.7. Virtualization for servers and individuals

4. Introduction to Fedora virtualization products

   4.1. KVM and virtualization in Fedora --> kirsti suggestion to just call it KVM? (since the fedora is mentioned in the main title  --> grundblom: I think we could use a chapter on how to make a vm in KVM like there is for boxes, and how to use libvirt tools.
   4.2. libvirt and libvirt tools
   4.3. Boxes
   4.4  Docker Containers --> grundblom: I have been using Docker containers as a virtualization tool, and while I dont think it is created for that purpose I would like to explore it here as an option since it works
   4.5. Storage
       4.5.1. Storage pools
       4.5.2. Storage volumes

5. Introduction to Boxes --> kirsti only a separate chapter for boxes, not for the other products? --> grundblom: I agree we should have sections for each product we mentioned in 4 I volunteer to write a section on how to make a vm in kvm.

   5.1. Features of Boxes
   5.2. How do I create a virtual machine in Boxes?
   5.3. How do I connect to other computers in Boxes?
   5.4. How do I change the settings of a machine in boxes?
   5.5. How do I move a Virtual Machine between computers?
   5.6. How do I delete a box?
   5.7. Boxes Tips and Tricks
   5.8. Advanced Commands in Boxes

6. Creating and Managing Guests with Virt-Manager --> smccann work toward common topic titles w/ Boxer chapter - should be covering same information

   6.1. System Requirements
   6.2. Installing Virtualization package groups
   6.3. Network Support
   6.4. Creating guests with virt-manager

A. Advanced Virtualization Concepts --> kirsti would this be a place to make a pointer to containers?

   A.1. Virtualized hardware devices
       A.1.1. Virtualized and emulated devices
       A.1.2. Para-virtualized devices
       A.1.3. Physical host devices
       A.1.4. CPU models
   A.2. guestfish
   A.3. Other useful tools
--> kirsti is it an idea to add a few dos and do nots, as in what would make good use cases for virtualization, and what not?  

B. Revision History

Changes to Content

Here you can list specific changes you would like to see made. In each instance please include some information that will help us find the location of the issue

Changes that are needed in the Getting Started Guide
Chapter/Section Link/URL Change Needed Who is requesting the Change Approved BZ Link
Ch 1 "The Fedora Virtualization Getting Started Guide introduces the basics of virtualization and assists with the navigation of other virtualization documentation and products that Fedora provides. This guide also explains the advantages of virtualization and dispels some common myths that exist regarding virtualization." leave out the second part (going with leaving out the misconceptions). First sentence could read "The Fedora Virtualization Getting Started Guide introduces the basics, and advantages of virtualization; and assists with the navigation of other virtualization documentation, and products that Fedora provides." (adding Oxford comma). Kirsti
ch2.1 Missing link in the note to Fedora Virtualization Deployment and Administration Guide Kirsti
ch2.2 under live migration is a reference to fedora 19."In Fedora 19, shared storage is not necessary for storing guest images to be migrated." Does this still apply to fed 22? Kirsti
ch 3 when we decide to go without the misconceptions, we need to rephrase the first two paragraphs, willing to make the attempt Kirsti
ch3.3 This chapter takes it from a misconception point of view. Searching the web I cannot come up easily with a good description, but is there a place in the admin manual where this subject is better explained? Could we work with something like: "While virtualization can speed processing up, it doesn't just magically make things better. Without the right architecture and tuning, virtualization will not deliver performance benefits." and then add a link to how to implement virtualization? Kirsti
ch3.4 Is this all we can say about flexibility? nothing about expanding or decreasing the number of machines in your network, easy test environment set-up without using up massive amounts of resources, easy to install when using images... Kirsti