Am 08.10.2014 um 09:34 schrieb Eneko Lacunza:
I think shared storage is the correct solution. If you want the feature,
you'll have to provide the shared storage which is not difficult to do,
otherwise current local storage works ok.
This would keep things as simple as possible, which is
Am 08.10.2014 um 09:34 schrieb Eneko Lacunza:
I think shared storage is the correct solution. If you want the
feature, you'll have to provide the shared storage which is not
difficult to do, otherwise current local storage works ok.
This would keep things as simple as possible, which is
I think shared storage is the correct solution. If you want the feature,
you'll have to provide the shared storage which is not difficult to do,
otherwise current local storage works ok.
This would keep things as simple as possible, which is quite good for
reliable logs.
On 06/10/14 10:43,
Am 04.10.2014 um 10:37 schrieb Dietmar Maurer:
I also like the rsync logs on migration. The only missing part is HA
migration
here.
Can i ignore this one?
So you would also need to sync the log on VM start. But from which node ??
Thought a bit more about that, and I think the only real
So the user can store the logs on NFS, GlusterFS, or CephFS ...
(or 'local' storage by default)
But this is not an easy task - also you need such a storage. Generally i think
something like a clustered leightweight database would be much better instead
of an FS for stuff like that.
IMHO
So i would like to implement something pretty simple f.e. rsync?
Note: as mentioned earlier, the rsync approach does not work for HA, because
you cannot sync the logs for a dead node.
___
pve-devel mailing list
pve-devel@pve.proxmox.com
I also like the rsync logs on migration. The only missing part is HA
migration
here.
Can i ignore this one?
So you would also need to sync the log on VM start. But from which node ??
Thought a bit more about that, and I think the only real solution is to but the
VM task logs on shared
Migrate the VM then migrate the logs for that VM.
Or use some sort of central logging system/distributed database.
A distributed NoSQL database seems like a good place to store the task
logs, each task can simply be a document.
Three ways to deal with task logs when a VM is deleted:
a) never
+1
On Oct 2, 2014 6:46 AM, Stefan Priebe - Profihost AG
s.pri...@profihost.ag wrote:
Hi,
i have asked this question already in the past but didn't had the time
to proceed.
I'm still missing that in case of a migration the task history migrates
too.
I really like to know the history of a
Any ideas how to archieve this.
Task logs and syslog are node local.
But I guess it would be possible to:
a.) rsync logs on migration.
b.) store logs on shared storage
other ideas?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
We *could* put them in /etc/pve someplace, so they automatically sync
throughout the cluster, but that would probably cause more issues than it
solves, especially as regards disk space and change frequency. The fact
that VMs themselves are sometimes node local, and sometimes on shared
storage,
Am 02.10.2014 19:31, schrieb Dietmar Maurer:
Any ideas how to archieve this.
Task logs and syslog are node local.
But I guess it would be possible to:
a.) rsync logs on migration.
b.) store logs on shared storage
other ideas?
I also like the rsync logs on migration. The only missing part
We *could* put them in /etc/pve someplace, so they automatically sync
throughout the cluster,
No, you cannot put large files there! (Everything is stored in RAM!)
___
pve-devel mailing list
pve-devel@pve.proxmox.com
I also like the rsync logs on migration. The only missing part is HA
migration here.
Can i ignore this one?
So you would also need to sync the log on VM start. But from which node ??
What do you think regarding deletion of VM?
no opinion
___
14 matches
Mail list logo
