That is correct, both in substance and meaning. PVE need not be involved.
If you dont define one, you WILL have a default rule for single datacenter, triple replication with no device class. If you need to specify additional/different logic, yes...
Welcome to the world of having a boss.
Depending on your role, your job is to INFORM the decision makers or MAKE decisions. if you're in the former, voice your concern in writing and then do what is decided (and dont bitch! once the decision is...
yeah I hear that.
In truth, you already have PBS that could effectively serve the purpose anyway. and scripting it is trivial if the use case mandated it. Its not really a problem from my POV, more a curiousity.
I mean, sure- I like efficiency too; but multi back end support is part of the PVE featureset. technically, anything that can be rendered out as bitmap (raw) can be compressed and sent anywhere. seems like an arbitrary limitation. anyone from the...
Is it a matter of validation alone? it seems to me that the allocated size is available from vmid.conf, and on disk size is available using zfs get or blockdev... its trivial enough to pipe it manually using dd | ssh | rbd-import so I wonder why...
This is a question for your compliance and management team. There is no universal answer to your concern. Are you in Finance, Pharma, Defense, or is this a medium size SaaS business. There are many variables here.
Sometimes an agent based...
Again, PVE doesnt need to be involved. This is a matter of ceph configuration.
You ARE running into the limitation of using a centrally managed ceph.conf, which adds a technical wrinkle. You would need to decouple the nodes individual ceph.conf...
the point about the storage infrastructure is insidious.
IF your target cluster is able to attach the storage for the source cluster, it is possible to do this without any data movement; simple MOVE the vmid.conf files to the other cluster.
BUT...
This isnt a pve question. PVE doesnt do anything outside of what ceph can do.
As long as you build your crush rule to do what you want, the client will respect it too. Assuming you have the following hierarchy:
DC
Node
OSD
you just need to...
Ignorance. although I usually leave room for the possibility the ignorance is mine. there is no more certainty in being wrong then not allowing for a different perspective. believing you're right and being, err, forceful about it says more about...
I'm curious- what would be the use case for this? in my view containers exist to isolate an application from the underlying hardware. if a container has access it loses its purpose to exist.
I cant speak for the idiosyncracies of hdfs, but the approach is supportable in general and raw/qcow2 over nfs is a first class citizen with PVE. Depending on the IOPs capabilities of the back end it may or may not be suitable for virtualization...
If you're asking whether the claude provided steps are correct- they are, but I would make an adjustment to step 7- specify the destination drive by its uuid/blkid however relevent to how you defined your pool originally, not but drive letter.
I...