How to contribute to wiki?

Spazmic

New Member
Sep 13, 2015
15
1
3
Before I start, good job at destroying documentation in your wiki (modified on october 22 2016). @wolfgang The 2 factor authentication "how to" was easy to follow with images, now you just destroyed it with irrevelant information.

Also, there are some things I would like to modify in the wiki because it's either outdated or false. How can I do so, i can't even propose changes.

EDIT: Look how wonderful OTP instructions were before it was destroyed on october 22nd. SO CLEAR WITH IMAGES! Is there an issue with clear information on this forum?
https://web.archive.org/web/20160329172523/http://pve.proxmox.com/wiki/Two-Factor_Authentication
 
Last edited:
Before I start, good job at destroying documentation in your wiki (modified on october 22 2016). @wolfgang The 2 factor authentication "how to" was easy to follow with images, now you just destroyed it with irrevelant information.

AFAIK nothing was destroyed. We just moved some parts into other locations. For example, we now
have a great article about using YubiKey here:

https://pve.proxmox.com/wiki/YubiKey

Also, there are some things I would like to modify in the wiki because it's either outdated or false. How can I do so, i can't even propose changes.

see https://pve.proxmox.com/wiki/Improving_the_Proxmox_VE_Documentation
 
AFAIK nothing was destroyed. We just moved some parts into other locations. For example, we now
have a great article about using YubiKey here:

Okay but what about CLEAR documentation about OTP? This documentation has disappeared since that merge.
 
I already sent a mail to Wolfgang - I guess we can improve that.
I am sorry about my shit attitude, but i am irritated because i trusted Proxmox 3.4. It was so simple, now proxmox 4 changed a lot and for the worst. There is not one aspect that I like of it except smart values for the disks lmao, and we are forced to migrate seeing 3.4 end of life incoming.
 
I am sorry about my shit attitude, but i am irritated because i trusted Proxmox 3.4. It was so simple, now proxmox 4 changed a lot and for the worst.

Not sure what you talk about exactly. We still have exactly the same architecture (excl. OpenVZ), the same command line interface, and all command line tools and even the REST API are almost 100% backward compatible.
 
Not sure what you talk about exactly. We still have exactly the same architecture (excl. OpenVZ), the same command line interface, and all command line tools and even the REST API are almost 100% backward compatible.

1- LXC is not ready for production, things like seeing the host's proc info is an handicap for anyone. Is there an advantage to this that I don't know?
2- Network on 4.3 is an horrowshow. On 3.4, you enter the ip and you click next; the VM is already deployed. Now we have to manually edit the network interfaces on each VMs.

I have to bang my head on each thing I want to accomplish with Proxmox 4+.
 
1- LXC is not ready for production, things like seeing the host's proc info is an handicap for anyone. Is there an advantage to this that I don't know?

LXC is extremely stable and production ready. We use lxcfs to virtualize relevant part of /proc/

2- Network on 4.3 is an horrowshow. On 3.4, you enter the ip and you click next; the VM is already deployed.

You can also enter the IP on 4.3 - everything if deployed automatically. Beside, it has much more features than the old network stack. So what exactly is a 'horrorshow'?
 
LXC is extremely stable and production ready. We use lxcfs to virtualize relevant part of /proc/

Well it doesn't seem like it's working lol, is it supposed to work now? Well it's not working for me and the persons of those threads:
https://forum.proxmox.com/threads/lxc-container-show-load-and-hardware-from-host.26051/
https://bugzilla.proxmox.com/show_bug.cgi?id=839


You can also enter the IP on 4.3 - everything if deployed automatically. Beside, it has much more features than the old network stack. So what exactly is a 'horrorshow'?

Then setting up the networking at OVH is an horrorshow. I understand this is due to OVH network configuration, but in 3.4, a vmac address wasn't needed for openvz containers.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!