image::images/pve-software-stack.svg["Proxmox Software Stack",align="center"]
+[[intro_central_management]]
Central Management
------------------
Proxmox Cluster File System (pmxcfs)::
-Proxmox VE uses the unique Proxmox Cluster file system (pmxcfs), a
+{pve} uses the unique Proxmox Cluster file system (pmxcfs), a
database-driven file system for storing configuration files. This
enables you to store the configuration of thousands of virtual
machines. By using corosync, these files are replicated in real time
on all cluster nodes. The file system stores all data inside a
persistent database on disk, nonetheless, a copy of the data resides
-in RAM which provides a maximum storage size is 30MB - more than
+in RAM which provides a maximum storage size of 30MB - more than
enough for thousands of VMs.
+
-Proxmox VE is the only virtualization platform using this unique
+{pve} is the only virtualization platform using this unique
cluster file system.
Web-based Management Interface::
-Proxmox VE is simple to use. Management tasks can be done via the
+{pve} is simple to use. Management tasks can be done via the
included web based management interface - there is no need to install a
separate management tool or any additional management node with huge
databases. The multi-master tool allows you to manage your whole
Command Line::
For advanced users who are used to the comfort of the Unix shell or
-Windows Powershell, Proxmox VE provides a command line interface to
-manage all the components of your virtual environment. This command
-line interface has intelligent tab completion and full documentation
+Windows Powershell, {pve} provides a command-line interface to
+manage all the components of your virtual environment. This command-line
+interface has intelligent tab completion and full documentation
in the form of UNIX man pages.
REST API::
-Proxmox VE uses a RESTful API. We choose JSON as primary data format,
+{pve} uses a RESTful API. We choose JSON as primary data format,
and the whole API is formally defined using JSON Schema. This enables
fast and easy integration for third party management tools like custom
hosting environments.
Authentication Realms::
-Proxmox VE supports multiple authentication sources like Microsoft
+{pve} supports multiple authentication sources like Microsoft
Active Directory, LDAP, Linux PAM standard authentication or the
-built-in Proxmox VE authentication server.
+built-in {pve} authentication server.
Flexible Storage
----------------
-The Proxmox VE storage model is very flexible. Virtual machine images
+The {pve} storage model is very flexible. Virtual machine images
can either be stored on one or several local storages or on shared
storage like NFS and on SAN. There are no limits, you may configure as
many storage definitions as you like. You can use all storage
* LVM Group (network backing with iSCSI targets)
* iSCSI target
* NFS Share
+* CIFS Share
* Ceph RBD
* Directly use iSCSI LUNs
* GlusterFS
the VM or CT data which includes the VM/CT configuration files.
KVM live backup works for all storage types including VM images on
-NFS, iSCSI LUN, Ceph RBD or Sheepdog. The new backup format is
-optimized for storing VM backups fast and effective (sparse files, out
-of order data, minimized I/O).
+NFS, CIFS, iSCSI LUN, Ceph RBD. The new backup format is optimized for storing
+VM backups fast and effective (sparse files, out of order data, minimized I/O).
High Availability Cluster
-------------------------
-A multi-node Proxmox VE HA Cluster enables the definition of highly
-available virtual servers. The Proxmox VE HA Cluster is based on
+A multi-node {pve} HA Cluster enables the definition of highly
+available virtual servers. The {pve} HA Cluster is based on
proven Linux HA technologies, providing stable and reliable HA
services.
Flexible Networking
-------------------
-Proxmox VE uses a bridged networking model. All VMs can share one
+{pve} uses a bridged networking model. All VMs can share one
bridge as if virtual network cables from each guest were all plugged
into the same switch. For connecting VMs to the outside world, bridges
-are attached to physical network cards assigned a TCP/IP
+are attached to physical network cards and assigned a TCP/IP
configuration.
For further flexibility, VLANs (IEEE 802.1q) and network
bonding/aggregation are possible. In this way it is possible to build
-complex, flexible virtual networks for the Proxmox VE hosts,
+complex, flexible virtual networks for the {pve} hosts,
leveraging the full power of the Linux network stack.
any VM or Container interface. Common sets of firewall rules can
be grouped into ``security groups''.
+include::hyper-converged-infrastructure.adoc[]
+
Why Open Source
---------------
-Proxmox VE uses a Linux kernel and is based on the Debian GNU/Linux
-Distribution. The source code of Proxmox VE is released under the
-http://www.gnu.org/licenses/agpl-3.0.html[GNU Affero General Public
+{pve} uses a Linux kernel and is based on the Debian GNU/Linux
+Distribution. The source code of {pve} is released under the
+https://www.gnu.org/licenses/agpl-3.0.html[GNU Affero General Public
License, version 3]. This means that you are free to inspect the
source code at any time or contribute to the project yourself.
core infrastructure independent from a single vendor.
-Your benefit with {pve}
------------------------
+Your benefits with {pve}
+------------------------
* Open source software
* No vendor lock-in
include::getting-help.adoc[]
+[[intro_project_history]]
Project History
---------------
was simple (server generated web page).
But we quickly developed new features using the
-http://corosync.github.io/corosync/[Corosync] cluster stack, and the
+https://corosync.github.io/corosync/[Corosync] cluster stack, and the
introduction of the new Proxmox cluster file system (pmxcfs) was a big
step forward, because it completely hides the cluster complexity from
the user. Managing a cluster of 16 nodes is as simple as managing a
The support for various storage types is another big task. Notably,
{pve} was the first distribution to ship ZFS on Linux by default in
2014. Another milestone was the ability to run and manage
-http://ceph.com/[Ceph] storage on the hypervisor nodes. Such setups
+https://ceph.com/[Ceph] storage on the hypervisor nodes. Such setups
are extremely cost effective.
When we started we were among the first companies providing
https://linuxcontainers.org/[LXC]. Containers are now deeply
integrated, and they can use the same storage and network features
as virtual machines.
+
+include::howto-improve-pve-docs.adoc[]
+include::translation.adoc[]
+
projects / pve-docs.git / blobdiff