Search results

das ist sogar sicher so. siehe oben CNC Maschine: ja, es hätte ein Update vom Hersteller gegeben, wobei die komplette Elektronik ausgetauscht wird. Das machen sie aber nicht selbst, sondern kaufen zu -> darum auch das hauseigene Problem mit den Leihmaschinen. Kostenpunkt > EUR 10.000,-- Und (ich...

ich durfte vor ein paar Jahren einmal eine CNC Maschine reparieren und musste mich daher mit IDE, dos, highmem und Co rumplagen :) Der Hersteller war begeistert und gab mir einen Auftrag, weil sie damit 20 Leihmaschinen wieder zum Leben erwecken konnten :)

we use proxmox and "abuse" it as a debian with zfs kernel....

das sieht sehr cool aus. freue mich schon, das mal auf einem testcluster zu testen....

yes its proxmox, no need to worry. pve needs the keys for cluster communication, migrations, shared pve-fs etc...

sorry thats not possible

https://docs.ansible.com/ansible/latest/index.html there is also puppet, chef, salt,...

we use ansible to provision machines. no templates, just fresh installs, provision, build, throw away (preferable containers)

btw: this is not that important to me. it's just a feeling because I was forced by "management" to upgrade a cluster in a timeframe I didnt want to and all because a web gui meant to "warn" me....

old stable normaly gets all security relevant Updates for at least a year or more. but thats not the main point. even if you are a very security affine sysop (and I am) there are reasons or circumstances where you cannot upgrade a virtualization stack in a timeframe given by a 3rd party eg...

I would like to suggest that on "old stable" (Bullseye, PVE7) there are not "YOU ARE EOL" messages shown on the GUI. I think it's unneccesary stress between IT and customer to force an update where it's not security relevant. imo stable and old-stable should be "warning free" just had an...

it is a good default to block cifs for home users. cifs is not meant to be a "remote" protocol

thomas-krenn.com bietet auf proxmox getestete Systeme an. Du kannst das "ausnutzen" und einfach einmal schauen, was sie verbauen. Und damit sie auch etwas davon haben: thomas-krenn ist wegen dieses services und auch sonst in allen belangen ein absolut empfehlenswerter Hardware Lieferant. wir...

and you see - no offense - that a backup would have made life so much easier :) even a small usb stick on a host and regularily cp /etc and config.db (or a scp, rsnyc, cp to nas etc...) is better than no backup cant say this often enough

imo decrease it a lot. upgrading a large hyperconverged production cluster is.... challenging :) and yes, i too think that scaling is much easier that way. depends on your situation, you need more hardware, more rackspace but we dont do hyperconverged clusters ever. we also have more than...

as we need cpu and ram for workloads anyway we dropped the concept of hyperconverged and seperate storage (ceph, nfs) from workload clusters. and we dont go further then 20 nodes/Cluster (the only disadvantage of pve imo, scalability)

wir hatten mehrmonatige Versuche mit Backups auf Hetzner Storage Boxen gemacht. System war nicht PBS aber auch ein Backup mit chunks und deplizierung. sehr viel io. bei uns kam es zu Datenverlust, vermutlich auch weil die Storages eher "unzuverlässig" sind, was connectivity betrifft. wir sind...

maybe your physical switches block vlan 1 as it is the default management vlan

I guess the "cluster" way to deal with it is * move vms from the missconfigured node * drop the node * setup new node (new name, new keys) * move vms back * goto 10

thanks. i knew. but at the moment the spam amount is overwhelming. my fingers forced me to post a "rant". thank you for your excellent work anyway!