Add internal and external storage wizard for cephfs
Signed-off-by: Alwin Antreich
---
www/manager6/Makefile | 1 +
www/manager6/Utils.js | 10 ++
www/manager6/storage/CephFSEdit.js | 71 ++
3 files changed, 82 insertions(+)
cre
This patch series is an update and adds the Cephfs to our list of storages.
You can mount the storage through the kernel or fuse client. The plugin for
now allows all content formats, but this needs further testing.
Config and keyfile locations are the same as in the RBD plugin.
Example entry:
ce
- ability to mount through kernel and fuse client
- allow mount options
- get MONs from ceph config if not in storage.cfg
- allow the use of ceph config with fuse client
Signed-off-by: Alwin Antreich
---
PVE/API2/Storage/Config.pm | 2 +-
PVE/API2/Storage/Status.pm | 2 +-
PVE/Storage.
On Wed, May 16, 2018 at 12:01:40PM +0200, Alexandre Derumier wrote:
> ---
> Makefile | 42 +
> debian/changelog | 174
> +
> debian/compat | 1 +
> debian/co
applied
On Wed, May 16, 2018 at 03:30:59PM +0200, Thomas Lamprecht wrote:
> We show and can remove serial devices but couldn't add new ones
> through the WebUI.
> Add a simple component to allow adding serial ports backed by a
> socket, which can be especially useful now with xterm.js
>
> Passing
Hi Wolfgang,
Thanks for review !
>>I'd like to have more info on patch 0007-add-dummy-..., probably best
>>to just write a more descriptive commit message there.
yes, indeed. It's to avoid to launch ifupdown proxmox
scripts(bridgevlanport,mtu), without remove them, as they are still provide b
- ability to mount through kernel and fuse client
- allow mount options
- get MONs from ceph config if not in storage.cfg
- allow the use of ceph config with fuse client
Signed-off-by: Alwin Antreich
---
PVE/API2/Storage/Config.pm | 2 +-
PVE/Storage.pm | 2 +
PVE/Storage/C
---
.gitmodules | 3 +++
ifupdown2 | 1 +
2 files changed, 4 insertions(+)
create mode 100644 .gitmodules
create mode 16 ifupdown2
diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 000..a9d2457
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,3 @@
+[submodule "ifupdown2"]
+
Changelog v2:
- use submodule for ifupdown2 src
- split proxmox/extra patches
- add description in 0004-add-dummy-mtu-bridgevlanport-modules.patch
- add a note in this cover letter about systemd-networkd and ipv6 madness
Hi,
Theses last months, I'm working on vxlan implementation. (I'll send
---
debian/changelog | 174 +
debian/compat | 1 +
debian/control | 31
debian/copyright | 28
...0001-start-networking-add
some general remarks from a quick run-through:
- backup does not seem to work, probably requires
qemu-server/pve-container changes? [1]
- parts of this could be merged with RBDPlugin code, either by extending
it, or by refactoring to use a common helper module
- ceph-fuse and the kernel have a
minimally fixes #1764, by introducing ebtables_enable as option in cluster.fw
Signed-off-by: Stoiko Ivanov
---
Note: A better option would be to just not overwrite any output of
ebtables-save, not containing pve-specific interface names or PVE, however
this patch should at least fix the problem
Hey Guys,
when I disable an iSCSI Storage it gets disabled in /etc/pve/storage.cfg
by adding a "disabled"-line. The GUI shows it correct, but you can't
reactivate it because when you edit it, it thinks it is enabled.
When you enable it by removing the line in storage.cfg everything is
fine again.
Hi,
I had a strange behaviour today,
with a vm running + qga enabled, but qga service down in the vm
after theses attempts,
May 17 21:54:01 kvm14 pvedaemon[20088]: VM 745 qmp command failed - VM 745 qmp
command 'guest-fsfreeze-thaw' failed - unable to connect to VM 745 qga socket -
timeout aft
in qmpclient : open_connection
for (;;) {
$count++;
$fh = IO::Socket::UNIX->new(Peer => $sname, Blocking => 0, Timeout =>
1);
last if $fh;
if ($! != EINTR && $! != EAGAIN) {
die "unable to connect to VM $vmid $sotype socket - $!\n";
}
Seem to be introduced a long time ago in 2012
https://git.proxmox.com/?p=qemu-server.git;a=blobdiff;f=PVE/QMPClient.pm;h=9829986ae77e82d340974e4d4128741ef85b4a0e;hp=d026f4d4c3012203d96660a311b1890e84e6aa18;hb=6d04217600f2145ee80d5d62231b8ade34f2e5ff;hpb=037a97463447b06ebf79a7f1d40c596d9955acee
pr
> we use $elapsed >= $timeout.
>
> Isn't this timeout for command execution time and not connect time ?
>
> I'm seeing at the end:
> $self->{mux}->set_timeout($fh, $timeout);
>
> seem to be the command execution time in the muxer
>
I guess both should be shorter than $timeout?
___
If you simply skip commands like 'guest-fsfreeze-thaw'
your VM will get totally unusable (frozen). So I am not
sure what you want to suggest?
A correct fix would be to implement an async command queue inside qemu...
> On May 18, 2018 at 7:13 AM Alexandre DERUMIER wrote:
>
>
> Seem to be intro
>>If you simply skip commands like 'guest-fsfreeze-thaw'
>>your VM will get totally unusable (frozen). So I am not
>>sure what you want to suggest?
I'm not sure, but don't we have 2 timeout here ?
1 for connect , and 1 for command execution ?
I would like to be able to fast timeout on connec
Hi Bastian,
On 5/17/18 9:29 PM, Bastian Sebode wrote:
> Hey Guys,
>
> when I disable an iSCSI Storage it gets disabled in /etc/pve/storage.cfg
> by adding a "disabled"-line. The GUI shows it correct, but you can't
> reactivate it because when you edit it, it thinks it is enabled.
>
> When you en
The dc/storage refactoring done in
commit 8f60ee4ccacc14f1bbe025874522c151cc375f83
introduced a regression where an once deactivated iSCSI storage could
not be activated again through UI, as we did not called the parent
setValue function correctly, thus the Enable checkbox was always set
to true. A
21 matches
Mail list logo
