Proxmox (some questions) - what, how?

Question

Debian

Host: debian 8.6, proxmox 4.4.
1) LVM is not configured according to the instructions. Instead of LVM, everything is in one directory. I do not see the point in LVM on the host system when the nodes are planned to be remote (located on another machine on which proxmox will be absent).
2) Postfix is ​​not installed, maybe a separate postfix virtual machine is planned, which will drive mail between all services.
1. How to treat?
> Warning during installation:
update failed - see /var/log/pveam.log for details
> Log:
Jan 14 00:43:42 start download https://releases.turnkeylinux.org/pve/aplinfo.dat.asc
Jan 14 00:43:42 download failed: 500 SSL_ca_file /etc/ssl/certs/ca-certificates.crt does not exist
Jan 14 00:43:42 update failed - no signature file '/var/lib/pve-manager/apl-info/pveam-releases.turnkeylinux.org.tmp.21775.asc'
> Exhaust with pveversion: pve-manager/ 4.4-5/c43015a5 (running kernel: 4.4.35-2-pve)
> Screenshot: polariton.ad-l.ink/8NHSqncHN/image.png
With the service as a whole it is clear, fixed with a reboot.
> How the installation was carried out (according to the instructions https://pve.proxmox.com/wiki/Install_Pr ... n_Jessie):
in hosts 192.168.1.2 TestDay pvelocalhost (ip, server name, something proxy - the domain was not specified during the installation of the system ).
echo "deb download.proxmox.com/debian jessie pve-no-subscription" > /etc/apt/sources.list.d/pve-install-repo.list
wget -O- "download.proxmox.com/debian/key.asc " | apt-key add -
apt-get update && apt-get -y dist-upgrade
apt-get -y install proxmox-ve ksm-control-daemon open-iscsi systemd- sysv
apt-get remove os-prober
reboot apt-get -y remove linux-image-amd64 linux-image -
3.16.0-4-amd64 linux-base
update-grub

2. Does the enterprise repository make sense?
while running apt-get update && apt-get -y dist-upgrade:
W: Failed to fetch https://enterprise.proxmox.com/debian/d … ry-amd6... HttpError401
E: Some index files failed to download.

Answer 1

well, if you need a support, of course you should buy it and use the enterprise repository, otherwise use a regular repo but subscript

Answer 2

3. What does hardware raid controller support provide?
Judging by the wiki - mdadm proxmox can't pve.proxmox.com/wiki/Raid_controller.
4. How to correctly add another node? What is required for this?
Fault tolerance and load balancing are not required. I only plan to add a node (which is located on the same network) and place virtual machines on it.
The documentation suggests adding a node to the cluster ( https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster) - hence the question: what are the prospects for the cluster?
5. How to set up the network correctly?
The network of the node is configured as follows: polariton.ad-l.ink/private/6WjvwqfL2/ed4037ca651bc...
By analogy, I plan to implement for virtual machines that I will natit on the switch.
ps The network settings in the VM look like this:
meson.ad-l.ink/7jMpJT77N/thumb.png
6. What is the Ballooling parameter?
meson.ad-l.ink/6sXjP69d9/thumb.png

Answer 3

1) LVM is not configured according to the instructions. Instead of LVM, everything is in one directory. I do not see the point in LVM on the host system when the nodes are planned to be remote (located on another machine on which proxmox will be absent).
2) Postfix is ​​not installed, maybe a separate postfix virtual machine is planned, which will drive mail between all services.

1) LVM is not critical, but proxmox relies heavily on it to make snapshots of virtual machines. But in general, in new versions it does this through ZFS. Therefore, without putting it, you break some logic of work.
2) postfix is ​​needed not only for external communications, but simply for sending notifications in the system. Proxmox sends you a notification about bad condition and weather ;) Yes, just local delivery in the system requires MTA.
3) Hardware Raid gives a certain guarantee that when one disk comes out, the second one will work and the rebuild will not load the system. Well, caching there, etc., etc.
On the other hand, with the introduction of ZFS, there is a hardware raid on the ZFS file system.
4) You create a cluster and add a node to it. Consider a cluster as your small data centers.
Need multicast support.
ballooning is dynamic memory allocation for virtual machines.

The traditional approach is to allocate a block of RAM of a given size, for example, 512 megabytes, to it immediately when starting a virtual machine (VM). Its drawback is that in those moments when there is unused space in the VM memory, it may not be enough in other VMs and the host system.
Memory ballooning is a mechanism to dynamically (a) allocate host RAM to a VM as needed and (b) return unused blocks as it becomes free. Thanks to it, it becomes possible to simultaneously run many VMs, the total amount of virtual RAM in which is greater than the amount of physical RAM in the host system, provided that they do not use the maximum allowed amount all at once. Due to this, the memory of the host system is distributed between the VMs in the same flexible way as between ordinary processes.
The creation of virtual resources that exceed physical ones in volume is denoted by the terms “overcommit” and “overselling”, beloved by many hosts.
Ballooning requires the coordinated operation of two software components:
MOM (memory overcommitment manager) in the host system, which changes the amount of RAM for the VM based on requests from it,
VMM (virtual memory manager) in the guest OS, which interacts with MOM through a virtual PCI controller .
MOM is enabled automatically in recent versions of KVM, older ones required enabling it with "kvm… -balloon virtio" on the command line.
The Windows hardware manager (devmgmt.msc) will see the guest device for communicating with the MOM as a "PCI standard RAM controller" of an unknown type. Unlike virt-stor and virt-net, the driver for it will not be prompted to install automatically. Instead, you should go to the properties of the device, on the tab "Driver" select the update and manually specify the path to balloon.inf on the VirtIO CD (proof). After that, the device will be renamed to "VirtIO Balloon Driver".

For other questions I will not answer, as the files have been deleted.