"There is a double spooking the world, the double of abstraction. The fortunes of states and armies, companies and communities depend on it. All contending classes - the landlords and farmers, the workers and capitalists - revere yet fear the relentless abstraction of the world on which their fortunes yet depend. All the classes but one. The hacker class." "The virtual is the true domain of the hacker. It is from the virtual that the hacker produces ever-new expressions of the actual. To the hacker, what is represented as being real is always partial, limited, perhaps even false. To the hacker there is always a surplus of possibility expressed in what is actual, the surplus of the virtual. This is the inexhaustible domain of what is real without being actual, what is not but which may be. To hack is to release the virtual into the actual, to express the difference of the real." | ||
| -- McKenzie Wark, A Hacker Manifesto | ||
Not so many years ago, it would've taken three computers to author this book efficiently on the go. Virtualization, however, has made it possible to write without the obscene hassle of dragging about so much baggage. Virtualization has reduced labor and energy expenditure and maximized productivity and discretionary time during the writing and production of this book.
Abstraction liberates us from material constraints, leaving in their place the privilege of nostalgia—tractor-fed edge strips, darkroom chemicals, printing presses and type-set trays, overflowing money bags with dollar signs, and of course, cramped server rooms.
Through server virtualization, the abstraction of computing resources from physical systems has overturned data centers and radically upset the traditional and repetitive routines of system engineers and administrators in favor of efficiency, conservation, lowered expenditure, secure systems, and the simple deployment of automation to complete repetitive tasks.
Proxmox VE has been a pioneering agent in this rapid revolution since the 2008 release of version 1.0—the first hypervisor to support both virtual machines and containers.
With version 4.2 in the works, and the industry's fascination finally fixed on the realization of a container revolution, Proxmox VE still provides an open source, enterprise virtualization solution with premium support that enjoys tremendous international popularity—even as competing brands have scrambled to roll out container solutions just in time.
This book is packed with introductory concepts and best practice techniques for experienced Linux users eager to take advantage of bleeding edge virtualization strategies and practices with Proxmox VE.
This book explores the benefits of two of these complementary virtualization technologies, containers and virtual machines, so you'll be forearmed to make informed and deliberated choices regarding the best paths for virtualizing your data center.
Chapter 1, Proxmox VE Fundamentals, outlines Proxmox VE's features and distinguishing characteristics and briefly compares and contrasts virtual machines and containers.
Chapter 2, Installing Proxmox VE, goes through the Proxmox VE installation process after covering Proxmox VE's hardware requirements and discussing minimal and optimal hardware specifications.
Chapter 3, Creating Containers, starts with a primer on containers and their uses before providing a walkthrough of the container creation processes, including choosing and downloading an OS or virtual appliance template.
Chapter 4, Creating Virtual Machines, first elaborates on the functional differences between virtual machines and suggests prospective use cases and the inherent benefits and drawbacks of full virtualization. It then walks through the process of creating and configuring virtual machines intended for Microsoft Windows Server and Fedora Server.
Chapter 5, Working with Virtual Disks, compares and contrasts virtual hard disk options, including disk image types, virtual bus/interfaces, and cache types.
Chapter 6, Networking with Proxmox VE, contrasts common virtual Ethernet adaptor options provided by Proxmox VE and works to articulate use cases for each.
Chapter 7, Securing Proxmox VE, enumerates strategies for mitigating security threats to virtualized datacenters in general, and Proxmox VE hosts and guests in particular.
Working with the illustrative examples in this book will require a 64-bit machine to host Proxmox 4.1 that meets at least the minimum recommended specs for evaluation:
- CPU: 64 bit (Intel EMT64 or AMD64)
- Intel VT/AMD-V capable CPU/Mainboard (for KVM Full Virtualization support)
- A minimum of 1 GB RAM
- Hard drive
- One NIC compatible with RedHat Enterprise Linux
This is not an ideal rig—more powerful specs can be found in Chapter 2, Installing Proxmox VE.
In addition to a machine to host Proxmox VE, broadband internet access is assumed, as is a remote workstation on the same LAN as the Proxmox VE host, a modern, JavaScript-enabled web browser, and installed ssh and sftp clients.
This book is intended for server and system administrators and engineers who are eager to take advantage of the potential of virtual machines and containers to manage servers more efficiently and make the best use of resources, from energy consumption to hardware utilization to physical real estate.
In this book, you will find a number of text styles that distinguish between different kinds of information. Here are some examples of these styles and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "We can use the qm create command to create a Proxmox VE virtual machine."
Any command-line input or output is written as follows:
-ostype win8 \ -sockets 1
New terms and important words are shown in bold. Words that you see on the screen, for example, in menus or dialog boxes, appear in the text like this: "Proceed with the installation by pressing i or navigating to Install Fedora 23."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or disliked. Reader feedback is important for us as it helps us develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <[email protected]>, and mention the book's title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide at www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for this book from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
You can download the code files by following these steps:
- Log in or register to our website using your e-mail address and password.
- Hover the mouse pointer on the SUPPORT tab at the top.
- Click on Code Downloads & Errata.
- Enter the name of the book in the Search box.
- Select the book for which you're looking to download the code files.
- Choose from the drop-down menu where you purchased this book from.
- Click on Code Download.
Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:
- WinRAR / 7-Zip for Windows
- Zipeg / iZip / UnRarX for Mac
- 7-Zip / PeaZip for Linux
We also provide you with a PDF file that has color images of the screenshots/diagrams used in this book. The color images will help you better understand the changes in the output. You can download this file from http://www.packtpub.com/sites/default/files/downloads/LearningProxmoxVE_ColorImages.pdf.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you could report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded to our website or added to any list of existing errata under the Errata section of that title.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors and our ability to bring you valuable content.
If you have a problem with any aspect of this book, you can contact us at <[email protected]>, and we will do our best to address the problem.