Hi,
my 2 cents:
For me, vdi are more spice solution.
Something like you have a customer portal, user click on create a new vdi,
It's spawing a new vm (linked clone from a template).
Spice is launching (maybe better with a spice html5 implementation)
and when user close the session, the vm
> You guys could integrate Apache Guacamole to Proxmox VE, perhaps.
You can install an run that inside any VM. So I don't really understand what
we should integrate?
___
pve-devel mailing list
pve-devel@pve.proxmox.com
Hi there
How can I add a shortcut to an external link, into web interface?
Someone can point me the direction to do that??
Thanks a lot
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
___
You guys could integrate Apache Guacamole to Proxmox VE, perhaps.
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
2018-04-19 9:33 GMT-03:00 Gilberto Nunes :
> Hi there...
>
> Is there any plan to add some
___
pve-devel mailing list
pve-devel@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
this implements those parts of draft-ietf-acme-acme-09 which are needed
to use Let's Encrypt's v2 API.
(based on an internal implement for the Let's Encrypt v1 API)
Co-Authored-By: Wolfgang Bumiller
Signed-off-by: Fabian Grünbichler
---
for registering, updating, refreshing and deactiving a PVE-managed ACME
account, as well as for retrieving the (optional, but required if
available) terms of service of the ACME API provider / CA.
Signed-off-by: Fabian Grünbichler
---
PVE/API2/Makefile | 1 +
Hi there...
Is there any plan to add some VDI solution, like Ulteo OVD, VMWare
Horizons, something like that.
I thing this would bring a big differential to Proxmox.
Thanks
---
Gilberto Nunes Ferreira
(47) 3025-5907
(47) 99676-7530 - Whatsapp / Telegram
Skype: gilberto.nunes36
to allow retrieval of certificate information, and uploading or removing
of custom certificate files.
Signed-off-by: Fabian Grünbichler
---
PVE/API2/Makefile| 1 +
PVE/API2/Certificates.pm | 205 +++
to lock an ACME account config file
Signed-off-by: Fabian Grünbichler
---
data/PVE/Cluster.pm | 8
1 file changed, 8 insertions(+)
diff --git a/data/PVE/Cluster.pm b/data/PVE/Cluster.pm
index ef7a541..d12c244 100644
--- a/data/PVE/Cluster.pm
+++
general purpose certificate related helper functions
Signed-off-by: Fabian Grünbichler
---
src/Makefile | 1 +
src/PVE/Certificate.pm | 396 +
2 files changed, 397 insertions(+)
create mode 100644
this patch series is implementing the following features:
- certificate utility module (pve-common)
- ACME v9 / Let's Encrypt v2 API client library (pve-common)
- PVE specific Certificate helper utility (pve-manager)
- new per-node configuration file in /etc/pve/nodes/FOO/config and API for
for creating/ordering a new certificate and renewing respectively
revoking an existing one.
Signed-off-by: Fabian Grünbichler
---
PVE/API2/Makefile | 1 +
PVE/API2/ACME.pm | 325 ++
2 files changed, 326
Signed-off-by: Fabian Grünbichler
---
src/PVE/ACME/Challenge.pm | 22 ++
src/PVE/ACME/StandAlone.pm | 74 ++
2 files changed, 96 insertions(+)
create mode 100644 src/PVE/ACME/Challenge.pm
create mode 100644
PVE-specific certificate helper functions
Signed-off-by: Fabian Grünbichler
---
PVE/Makefile | 1 +
PVE/CertHelpers.pm | 107 +
2 files changed, 108 insertions(+)
create mode 100644 PVE/CertHelpers.pm
diff
Also fixes a minor spelling error in changelog.Debian and extends the
.gitignore to ignore build files.
Signed-off-by: René Jochum
---
.gitignore | 7 +++
Makefile | 29 ++--
changelog.Debian =>
On Thu, Apr 19, 2018 at 11:31:08AM +0200, Rene Jochum wrote:
> Thanks again, comments inline.
>
> On 2018-04-19 10:16, Fabian Grünbichler wrote:
> >> @@ -52,23 +54,27 @@ install: PVE/RADOS.pm RADOS.so
> >> .PHONY: deb ${DEB}
> >> deb: ${DEB}
> >> ${DEB}:
> >> - rm -rf debian
> >> - mkdir
On Thu, Apr 19, 2018 at 11:02:44AM +0200, Rene Jochum wrote:
> On 2018-04-19 10:16, Fabian Grünbichler wrote:
> > some comments inline (your patch also only applies when ignoring
> > whitespace changes!)
>
>
> Hi Fabian,
>
> thank you for looking into it! Can you give me a tip on making patches
Thanks again, comments inline.
On 2018-04-19 10:16, Fabian Grünbichler wrote:
>> @@ -52,23 +54,27 @@ install: PVE/RADOS.pm RADOS.so
>> .PHONY: deb ${DEB}
>> deb: ${DEB}
>> ${DEB}:
>> -rm -rf debian
>> -mkdir debian
>> -make DESTDIR=${CURDIR}/debian install
>> -install -d -m
On 2018-04-19 10:16, Fabian Grünbichler wrote:
> some comments inline (your patch also only applies when ignoring
> whitespace changes!)
Hi Fabian,
thank you for looking into it! Can you give me a tip on making patches
that apply without ignoring white space changes?
Will implement all the
this prevented creating/editing an iscsi storage
Signed-off-by: Dominik Csapak
---
www/manager6/storage/IScsiEdit.js | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www/manager6/storage/IScsiEdit.js
b/www/manager6/storage/IScsiEdit.js
index
thanks for this! one of the leftover packages which we haven't converted
so far (for lack of recent changes). now that Alwin did some changes and
is planning to do some more, it's probably a good idea to convert it.
some comments inline (your patch also only applies when ignoring
whitespace
A ZFS storage under heavy load can take more time.
---
PVE/Storage/ZFSPoolPlugin.pm | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
[Patch V2]
make timout depending on whether it is in a worker or not.
diff --git a/PVE/Storage/ZFSPoolPlugin.pm b/PVE/Storage/ZFSPoolPlugin.pm
index
It should use an asynchronous API call to create an image,
because some storages may need longer to alloc an image.
If a storage needs more than 30 sec
the proxy will timeout and we have an orphan image.
Also, it is possible to increase the timeout for some
storages if an asynchronous call is
Use the async API call 'update_vm' to create a HD.
This will encourage a worker and we can increase the time-out for ZFS at high
load.
Patch V1 -> V2
[storage]
Rebased 32c0a1d59bfea6a21212cb5386a9d06e27089f10 ->
bce13b7f505ea63bc92a12d3beabe0ebb9a802fe
make timout depending on whether it is in
`zfs create` add the creation job in a worker queue,
which should normally execute instantly. But there are circumstances
where the job will take a while to get processed.
If this is the case udev settle will see no dev in the queue and the program
will continue without an allocated dev.
The busy
26 matches
Mail list logo