I see the instructions for upgrading from 3.x to 4.0. What about from 4.0 Beta2 to 4.0 stable? Just change the repos from pvetest to stable?
Proxmox VE 4.0 released!
- Thread starter martin
- Start date
With OpenVZ, i was used to do batch of things on all containers with a thing like this:
With LXC, it somehow does not pass the whole command inside.
Any idea?
Code:
vzctl exec $ID "apt-get update somepackage -y"With LXC, it somehow does not pass the whole command inside.
Code:
pct exec 100 apt-get install mc -y
Unknown option: y
400 unable to parse option
pct exec <vmid> [<extra-args>]
pct exec 100 "apt-get install mc -y"
lxc-attach: attach.c: lxc_attach_run_command: 1195 No such file or directory - failed to exec 'apt-get install mc -y'Any idea?
With OpenVZ, i was used to do batch of things on all containers with a thing like this:Code:vzctl exec $ID "apt-get update somepackage -y"
With LXC, it somehow does not pass the whole command inside.
Code:pct exec 100 apt-get install mc -y Unknown option: y 400 unable to parse option pct exec <vmid> [<extra-args>] pct exec 100 "apt-get install mc -y" lxc-attach: attach.c: lxc_attach_run_command: 1195 No such file or directory - failed to exec 'apt-get install mc -y'
Any idea?
just run:
> pct exec 100 apt-get install mc
Yeah, sure, i do But then i need to answer things. This is not cool when running something on 200+ containers. Ok, it doesnt matter that much as Puppet etc. take care of almost all things, but sometimes (when everybody needs a package the day before) this is kind of handy.
But then i need to answer things. This is not cool when running something on 200+ containers. Ok, it doesnt matter that much as Puppet etc. take care of almost all things, but sometimes (when everybody needs a package the day before) this is kind of handy.Jip, please have a look, this was my first try
Code:
pct exec 100 apt-get install mc -y
Unknown option: y
400 unable to parse option
pct exec <vmid> [<extra-args>]Pleas use '--' to pass additional parameter, for example:
# pct exec 100 apt-get -- install mc -y
# pct exec 100 apt-get -- install mc -y
Nice, works like charm. Would have been the next thing to play around with...but this way it's documented for other people having similiar problems as well.
Thank you!
Thank you!
First of all thank you for the amazing work! This update is huge, but the ones before this are not a tiny bit inferior!
I would like to clarify my planned upgrade method from 3.4 to 4.0 with you, if you don't mind. I am running a 5 node cluster, running all KVM based VMs with Ceph backend. (Ceph is installed separately, outside of Proxmox.) My concern is that I have to stop all VMs and recreate the cluster during the upgrade. I don't have spare bare metal so I came up with the following idea. I migrate away all VMs from a node, upgrade it to 4.0, create a new cluster on it, then stop some VMs on the old cluster and restart them on the new node and start the process over until all of the nodes are upgraded. Of course on the second and so on upgraded nodes I don't create a new cluster but join the new one. What do you think, will it work?
Kinds regards,
Mate
I would like to clarify my planned upgrade method from 3.4 to 4.0 with you, if you don't mind. I am running a 5 node cluster, running all KVM based VMs with Ceph backend. (Ceph is installed separately, outside of Proxmox.) My concern is that I have to stop all VMs and recreate the cluster during the upgrade. I don't have spare bare metal so I came up with the following idea. I migrate away all VMs from a node, upgrade it to 4.0, create a new cluster on it, then stop some VMs on the old cluster and restart them on the new node and start the process over until all of the nodes are upgraded. Of course on the second and so on upgraded nodes I don't create a new cluster but join the new one. What do you think, will it work?
Kinds regards,
Mate
First of all thank you for the amazing, ork! This update is huge, but the ones before this are not a tiny bit inferior!
I would like to clarify my planned upgrade method from 3.4 to 4.0 with you, if you don't mind. I am running a 5 node cluster, running all KVM based VMs with Ceph backend. (Ceph is installed separately, outside of Proxmox.) My concern is that I have to stop all VMs and recreate the cluster during the upgrade. I don't have spare bare metal so I came up with the following idea. I migrate away all VMs from a node, upgrade it to 4.0, create a new cluster on it, then stop some VMs on the old cluster and restart them on the new node and start the process over until all of the nodes are upgraded. Of course on the second and so on upgraded nodes I don't create a new cluster but join the new one. What do you think, will it work?
Kinds regards,
Mate
Hi,
I have done it online without vm interruption
The tricky part is to upgrade to jessie and proxmox 4 online , sxtich to cororync2 on all nodes at the same time
Then you ll be able to do live migration and reboot empty hosts
Im on holiday this week but i ll try to post an howto next week
Thank you very much for making this reply on your holiday! I would be very interested in that howto if you would have time to make it sometime. Enjoy your holiday!
Thanks and congrats for the 4.0 release. I'm a new user and I've enjoyed using it so far.
I just wanted to report a small omission in the wiki.
If you navigate to the "Update a running Proxmox Virtual Environment 4.x to latest 4.0" paragraph of the Downloads wiki page (sorry I'm not authorized to post links on the forum yet), a "deb" is missing:
I just wanted to report a small omission in the wiki.
If you navigate to the "Update a running Proxmox Virtual Environment 4.x to latest 4.0" paragraph of the Downloads wiki page (sorry I'm not authorized to post links on the forum yet), a "deb" is missing:
Code:
deb <link> jessie main contrib
# security updates
[B][COLOR=#ff0000]deb [/COLOR][/B]<link> jessie/updates main contribHi, we have following error on apt-get update:
What can we do here? I mean, you have no pve entry in your source-list on http://download.proxmox.com/debian/dists/jessie/Release only pvetest and no-subscription...
sourcelist.conf:
Best regards
Code:
W: Fehlschlag beim Holen von http://download.proxmox.com/debian/dists/jessie/Release Erwarteter Eintrag »pve/binary-amd64/Packages« konnte in Release-Datei nicht gefunden werden (falscher Eintrag in sources.list oder missgebildete Datei).What can we do here? I mean, you have no pve entry in your source-list on http://download.proxmox.com/debian/dists/jessie/Release only pvetest and no-subscription...
sourcelist.conf:
Code:
deb http://ftp.de.debian.org/debian jessie main contrib non-free
deb-src http://ftp.de.debian.org/debian jessie main contrib non-free
deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb-src http://ftp.debian.org/debian/ jessie-updates main contrib non-free
deb http://security.debian.org/ jessie/updates main contrib non-free
deb-src http://security.debian.org/ jessie/updates main contrib non-free
# PVE packages provided by proxmox.com
deb http://download.proxmox.com/debian jessie pve
# PVE pve-no-subscription repository provided by proxmox.com, NOT recommended for production use
deb http://download.proxmox.com/debian jessie pve-no-subscriptionBest regards
Last edited: