From: Dietmar Maurer Date: Sat, 8 Oct 2016 15:22:48 +0000 (+0200) Subject: mark toplevel docs X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=commitdiff_plain;h=5f09af76d7282a043be8fa5439349272f506cf02 mark toplevel docs --- diff --git a/datacenter.cfg.adoc b/datacenter.cfg.adoc index 1648b02..63bee57 100644 --- a/datacenter.cfg.adoc +++ b/datacenter.cfg.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ Datacenter Configuration include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The file `/etc/pve/datacenter.cfg` is a configuration file for {pve}. It contains cluster wide default values used by all nodes. diff --git a/getting-help.adoc b/getting-help.adoc index 6da0179..260a18e 100644 --- a/getting-help.adoc +++ b/getting-help.adoc @@ -2,6 +2,10 @@ Getting Help ------------ include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Proxmox VE Wiki ~~~~~~~~~~~~~~~ diff --git a/ha-manager.adoc b/ha-manager.adoc index a5ffe00..052eefc 100644 --- a/ha-manager.adoc +++ b/ha-manager.adoc @@ -4,6 +4,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -24,6 +26,9 @@ High Availability include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] Our modern society depends heavily on information provided by computers over the network. Mobile devices amplified that dependency, diff --git a/local-lvm.adoc b/local-lvm.adoc index c493501..ea6e751 100644 --- a/local-lvm.adoc +++ b/local-lvm.adoc @@ -2,6 +2,10 @@ Logical Volume Manager (LVM) ---------------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Most people install {pve} directly on a local disk. The {pve} installation CD offers several options for local disk management, and the current default setup uses LVM. The installer let you select a diff --git a/local-zfs.adoc b/local-zfs.adoc index 9b682b9..8ee8554 100644 --- a/local-zfs.adoc +++ b/local-zfs.adoc @@ -2,6 +2,10 @@ ZFS on Linux ------------ include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + ZFS is a combined file system and logical volume manager designed by Sun Microsystems. Starting with {pve} 3.4, the native Linux kernel port of the ZFS file system is introduced as optional diff --git a/pct.adoc b/pct.adoc index 48b12bc..da7db1c 100644 --- a/pct.adoc +++ b/pct.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -24,6 +26,9 @@ Proxmox Container Toolkit include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] Containers are a lightweight alternative to fully virtualized VMs. Instead of emulating a complete Operating System (OS), containers diff --git a/pct.conf.adoc b/pct.conf.adoc index 2f68d21..083628e 100644 --- a/pct.conf.adoc +++ b/pct.conf.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ Container Configuration include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The `/etc/pve/lxc/.conf` files stores container configuration, where `CTID` is the numeric ID of the given container. diff --git a/pmxcfs.adoc b/pmxcfs.adoc index 66555e8..0a07f39 100644 --- a/pmxcfs.adoc +++ b/pmxcfs.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -23,6 +25,10 @@ Proxmox Cluster File System (pmxcfs) include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The Proxmox Cluster file system (``pmxcfs'') is a database-driven file system for storing configuration files, replicated in real time to all cluster nodes using `corosync`. We use this to store all PVE related diff --git a/pve-admin-guide.adoc b/pve-admin-guide.adoc index 7118dd1..5514ea5 100644 --- a/pve-admin-guide.adoc +++ b/pve-admin-guide.adoc @@ -16,6 +16,7 @@ include::attributes.txt[] ifndef::wiki[] ifndef::manvolnum[] +:pve-toplevel: // Push titles down one level. :leveloffset: 1 diff --git a/pve-bibliography.adoc b/pve-bibliography.adoc index 2df8b3d..18998dd 100644 --- a/pve-bibliography.adoc +++ b/pve-bibliography.adoc @@ -3,6 +3,10 @@ Bibliography ============ include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + [bibliography] .Books about {pve} diff --git a/pve-disk-health-monitoring.adoc b/pve-disk-health-monitoring.adoc index 2bb740b..0b9b418 100644 --- a/pve-disk-health-monitoring.adoc +++ b/pve-disk-health-monitoring.adoc @@ -2,6 +2,10 @@ Disk Health Monitoring ---------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Altough a robust and redundant storage is recommended, it can be very helpful to monitor the health of your local disks. diff --git a/pve-faq.adoc b/pve-faq.adoc index 9489295..ec9f9a3 100644 --- a/pve-faq.adoc +++ b/pve-faq.adoc @@ -2,6 +2,10 @@ Frequently Asked Questions ========================== include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + NOTE: New FAQs are appended to the bottom of this section. ///////////////////////////////////////////////////////////////// diff --git a/pve-firewall.adoc b/pve-firewall.adoc index 37f982b..18ffbdc 100644 --- a/pve-firewall.adoc +++ b/pve-firewall.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ ifndef::manvolnum[] include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + {pve} Firewall provides an easy way to protect your IT infrastructure. You can setup firewall rules for all hosts inside a cluster, or define rules for virtual machines and diff --git a/pve-installation.adoc b/pve-installation.adoc index 7f5bcae..56b2b75 100644 --- a/pve-installation.adoc +++ b/pve-installation.adoc @@ -2,6 +2,10 @@ Installing Proxmox VE ===================== include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + {pve} ships as a set of Debian packages, so you can simply install it on top of a normal Debian installation, or download the installation CD-ROM and use that to install {pve} on your hardware. diff --git a/pve-network.adoc b/pve-network.adoc index 3c03615..de15989 100644 --- a/pve-network.adoc +++ b/pve-network.adoc @@ -2,6 +2,10 @@ Network Configuration --------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + {pve} uses a bridged networking model. Each host can have up to 4094 bridges. Bridges are like physical network switches implemented in software. All VMs can share a single bridge, as if diff --git a/pve-package-repos.adoc b/pve-package-repos.adoc index 84e2c1c..58d8699 100644 --- a/pve-package-repos.adoc +++ b/pve-package-repos.adoc @@ -2,6 +2,10 @@ Package Repositories -------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + All Debian based systems use http://en.wikipedia.org/wiki/Advanced_Packaging_Tool[APT] as package management tool. The list of repositories is defined in diff --git a/pve-storage-dir.adoc b/pve-storage-dir.adoc index 991b374..e3d15ed 100644 --- a/pve-storage-dir.adoc +++ b/pve-storage-dir.adoc @@ -2,6 +2,10 @@ Directory Backend ----------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `dir` {pve} can use local directories or locally mounted shares for diff --git a/pve-storage-glusterfs.adoc b/pve-storage-glusterfs.adoc index 131a7d2..5ac9a85 100644 --- a/pve-storage-glusterfs.adoc +++ b/pve-storage-glusterfs.adoc @@ -2,6 +2,10 @@ GlusterFS Backend ----------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `glusterfs` GlusterFS is a salable network file system. The system uses a modular diff --git a/pve-storage-iscsi.adoc b/pve-storage-iscsi.adoc index 4dbe4ac..e23f643 100644 --- a/pve-storage-iscsi.adoc +++ b/pve-storage-iscsi.adoc @@ -2,6 +2,10 @@ http://www.open-iscsi.org/[Open-iSCSI] initiator ------------------------------------------------ include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `iscsi` iSCSI is a widely employed technology used to connect to storage diff --git a/pve-storage-iscsidirect.adoc b/pve-storage-iscsidirect.adoc index 4dda04b..4681663 100644 --- a/pve-storage-iscsidirect.adoc +++ b/pve-storage-iscsidirect.adoc @@ -2,6 +2,10 @@ User Mode iSCSI Backend ----------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `iscsidirect` This backend provides basically the same functionality as the diff --git a/pve-storage-lvm.adoc b/pve-storage-lvm.adoc index 3f21644..be065bc 100644 --- a/pve-storage-lvm.adoc +++ b/pve-storage-lvm.adoc @@ -2,6 +2,10 @@ LVM Backend ----------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `lvm` LVM is a thin software layer on top of hard disks and partitions. It diff --git a/pve-storage-lvmthin.adoc b/pve-storage-lvmthin.adoc index be730cf..657f7bd 100644 --- a/pve-storage-lvmthin.adoc +++ b/pve-storage-lvmthin.adoc @@ -2,6 +2,10 @@ LVM thin Backend ---------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `lvmthin` LVM normally allocates blocks when you create a volume. LVM thin pools diff --git a/pve-storage-nfs.adoc b/pve-storage-nfs.adoc index d717c18..6165dc7 100644 --- a/pve-storage-nfs.adoc +++ b/pve-storage-nfs.adoc @@ -2,6 +2,10 @@ NFS Backend ----------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `nfs` The NFS backend is based on the directory backend, so it shares most diff --git a/pve-storage-rbd.adoc b/pve-storage-rbd.adoc index d7a6067..7361935 100644 --- a/pve-storage-rbd.adoc +++ b/pve-storage-rbd.adoc @@ -2,6 +2,10 @@ Ceph RADOS Block Devices (RBD) ------------------------------ include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `rbd` http://ceph.com[Ceph] is a distributed object store and file system diff --git a/pve-storage-zfspool.adoc b/pve-storage-zfspool.adoc index b67ddff..fe923cc 100644 --- a/pve-storage-zfspool.adoc +++ b/pve-storage-zfspool.adoc @@ -2,6 +2,10 @@ Local ZFS Pool Backend ---------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Storage pool type: `zfspool` This backend allows you to access local ZFS pools (or ZFS file systems diff --git a/pve-system-requirements.adoc b/pve-system-requirements.adoc index 19ddd2c..1eb4af9 100644 --- a/pve-system-requirements.adoc +++ b/pve-system-requirements.adoc @@ -2,6 +2,10 @@ System Requirements ------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + For production servers, high quality server equipment is needed. Keep in mind, if you run 10 Virtual Servers on one machine and you then experience a hardware failure, 10 services are lost. {pve} diff --git a/pve-usbstick.adoc b/pve-usbstick.adoc index cd263db..adf4ea8 100644 --- a/pve-usbstick.adoc +++ b/pve-usbstick.adoc @@ -2,6 +2,10 @@ Install from USB Stick ---------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The {pve} installation media is now a hybrid ISO image, working in two ways: diff --git a/pvecm.adoc b/pvecm.adoc index 9b45603..a1ba7d3 100644 --- a/pvecm.adoc +++ b/pvecm.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -23,6 +25,10 @@ Cluster Manager include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The {PVE} cluster manager `pvecm` is a tool to create a group of physical servers. Such a group is called a *cluster*. We use the http://www.corosync.org[Corosync Cluster Engine] for reliable group diff --git a/pvesm.adoc b/pvesm.adoc index 5ca5e3f..a93bbca 100644 --- a/pvesm.adoc +++ b/pvesm.adoc @@ -4,6 +4,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ ifndef::manvolnum[] include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + 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 or iSCSI (NAS, SAN). There are no limits, and you may diff --git a/pveum.adoc b/pveum.adoc index cca1ece..c83945e 100644 --- a/pveum.adoc +++ b/pveum.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ User Management include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + // Copied from pve wiki: Revision as of 16:10, 27 October 2015 Proxmox VE supports multiple authentication sources, e.g. Linux PAM, diff --git a/qm.adoc b/qm.adoc index f44314c..130e22a 100644 --- a/qm.adoc +++ b/qm.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -24,6 +26,10 @@ Qemu/KVM Virtual Machines include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + // deprecates // http://pve.proxmox.com/wiki/Container_and_Full_Virtualization // http://pve.proxmox.com/wiki/KVM diff --git a/qm.conf.adoc b/qm.conf.adoc index d392893..5dff0fc 100644 --- a/qm.conf.adoc +++ b/qm.conf.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ ifndef::manvolnum[] include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + The `/etc/pve/qemu-server/.conf` files stores VM configuration, where "VMID" is the numeric ID of the given VM. diff --git a/scan-adoc-refs b/scan-adoc-refs index fc6cdf4..c3ac08f 100755 --- a/scan-adoc-refs +++ b/scan-adoc-refs @@ -129,6 +129,19 @@ sub scan_adoc_file { chomp $env_last_line->{$e}; } + if ($line =~ m/^:(\S+?):\s*(.*\S)?\s*$/) { + my ($key, $value) = ($1, $2); + if ($key eq 'pve-toplevel') { + + foreach my $e (@{$env_stack->[-1]}) { + my $title = $fileinfo->{titles}->{$e}->{$filename}; + die "not title for toplevel file '$filename' (env=$e)\n" + if !defined($title); + $fileinfo->{toplevel}->{$e}->{$filename} = 1; + } + } + } + if ($line =~ m/^\[\[(.*)\]\]\s*$/) { my $blockid = $1; die "implement me" if $blockid =~m/,/; diff --git a/sysadmin.adoc b/sysadmin.adoc index c9e0ae6..c52c3fe 100644 --- a/sysadmin.adoc +++ b/sysadmin.adoc @@ -2,6 +2,10 @@ Host System Administration ========================== include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + {pve} is based on the famous https://www.debian.org/[Debian] Linux distribution. That means that you have access to the whole world of Debian packages, and the base system is well documented. The diff --git a/system-software-updates.adoc b/system-software-updates.adoc index 82281b4..76df217 100644 --- a/system-software-updates.adoc +++ b/system-software-updates.adoc @@ -2,6 +2,10 @@ System Software Updates ----------------------- include::attributes.txt[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + We provide regular package updates on all repositories. You can install those update using the GUI, or you can directly run the CLI command `apt-get`: diff --git a/vzdump.adoc b/vzdump.adoc index 97bdcf2..5ae6b3c 100644 --- a/vzdump.adoc +++ b/vzdump.adoc @@ -3,6 +3,8 @@ PVE({manvolnum}) ================ include::attributes.txt[] +:pve-toplevel: + NAME ---- @@ -25,6 +27,10 @@ Backup and Restore include::attributes.txt[] endif::manvolnum[] +ifdef::wiki[] +:pve-toplevel: +endif::wiki[] + Backups are a requirements for any sensible IT deployment, and {pve} provides a fully integrated solution, using the capabilities of each storage and each guest system type. This allows the system