Hi!
THX for describing it, it would have been very helpful when I was writing
my DRBD8 plugin.
On 01/16/2017 09:46 PM, Dmitry Petuhov wrote:
+# public
+# returns $path to image/directory to be passed to qemu/lxc.
sub path {
my ($class, $scfg, $volname, $storeid, $snapname) = @_;
Hi!
> I'll try work on this next week.
May I ask you to consider a new API for merging between Storage and Plugin.
It might be very useful for a plugin to know a migration is starting and
is finished, so that a plugin can do additional commands to the particular
storage driver. And a plugin
Hi!
When you add a HardDisk to a not running VM, it gets simply written to the
*.conf file. But when you EDIT a HardDisk, someone executes the storage plugin
function "activate_volume", even if the VM is deactivated.
Is this a bug or a feature?
At least the state of the volume is different after
Hi!
>> > First, we call deactivate if you migrate a VM to another node.
>> OK, I haven't seen this. I will test once my plugin is ready.
The plugin is ready now and I could test this today.
-> It works like you said.
> I simply do not understand why you think the current approach is wrong. It
> No, you need to set that yourself if you want to test that.
If there is no command to force it, is there an action to trigger it somehow?
If not, why does it exist?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
# pvesm list
THX, I could now debug most of the function, but "vollist" is always undefined.
I used the parameters "-content images" and "-vmid 101". There are no more
options to the list command.
Is there another command to force "vollist" beeing defined?
Hi!
It is really hard to develop a storage plugin, if there is no API description
available. At least I haven't found it.
I could discover all functions, except "list_images". It has some variants to
be executed and I really can't discover what the main goal of this function
is.
1) I think it
> IMHO DRBD8 is old and replaced by DRBD9. Linbit will provide a DRBD9 driver
> in future
Yes they will, but as stated in http://pve.proxmox.com/wiki/DRBD9
"DRBD9 integration is introduced in Proxmox VE 4.x as technology preview."
and Linbit says
> Why? There is no real need to deactivate a volume, unless you move the VM
> to another node.
I already told you why:
For a DRBD8 plugin, which I want to write, it is essential to switch the
volume back to secondary after using it. Otherwise it can't be used on the
other machine and you
Hi!
>> It seems the storage plugin function "deactivate_volume" will be not
>> executed, when the VM stops by issuing a "poweroff" command.
> That is by design ...
So there is NO interface between the code who already detects this
(eg.: "pvedaemon[6695]: client closed connection") to the storage
Hi!
It seems the storage plugin function "deactivate_volume" will be not executed,
when the VM stops by issuing a "poweroff" command.
Hint: It is executed, when you klick the Shutdown button from the GUI.
I have seen
pvedaemon[21622]: client closed connection
in the log, but no further
Hi!
I am just analysing the Storage class and plugins and discovered that
activate_storage in Storage.pm and also activate_storage in the plugins is
executed cyclically.
The reason is, that "cache" is always a new hash and therefore
"if $cache->{activated}->{$storeid};" in
now :(
Is there a possibility / concept to dynamically rewrite parts of the GUI which
may be reused here ?
BR,
Jasmin
**
On 12/10/2016 07:04 PM, Jasmin J. wrote:
Hi!
I started today playing with storage plugins.
I installed this plugin on
Hi!
I started today playing with storage plugins.
I installed this plugin on my machine to see how it works, but I couldn't see
it in the Add dialog on the WEB interface.
I restarted only "pveproxy", which should enough, I guess.
I even tried to execute it directly from Storage.pm, without
Hi!
Wouldn't this cause issues with multiple systems attempting to control the
same device simultaneously?
Whenever you use software, you need to think. The same applies here.
It is possible to clone the VM manually by copying the conf file and the
referenced virtual disks. The advantage of
Hello Dietmar!
So where do you make a copy of the device data?
I do the same like for CDROMs. This line will copy the configuration entry in
the conf file. The device data is on the device and remains there (like it does
for CDROMs).
BR,
Jasmin
*
On 2014-10-26 11:27, Michael Rasmussen wrote:
On Sun, 26 Oct 2014 11:04:40 +0100 Jasmin J. jas...@anw.at wrote:
I intended to use cloning a VM with a device to make a copy of the
current state just before I do changes in the VM (e.g: update, install
new software). And yes, it might
This is not a 'clone', and nothing I want to add.
And virtual disks are copied to new disks as expected for a clone. Only the
disk device content isn't copied.
Imagine there is a device with 4TB mapped to a guest. There is no possibility
to copy this huge amount of data. When people do disk
18 matches
Mail list logo
