[vdi][daas][ops] What are your solutions to VDI/DaaS on OpenStack?

Andy Botting andy at andybotting.com
Tue Jun 7 23:19:38 UTC 2022

Hi Radosław,

> First of all, wow, that looks very interesting and in fact very much
> what I'm looking for. As I mentioned in the original message, the
> things this solution lacks are not something blocking for me.
> Regarding the approach to Guacamole, I know that it's preferable to
> have guacamole extension (that provides the dynamic inventory)
> developed rather than meddle with the internal database but I guess it
> is a good start.

An even better approach would be something like the Guacozy project

They were able to use the Guacmole JavaScript libraries directly to
embed the HTML5 desktop within a React? app. I think this is a much
better approach, and I'd love to be able to do something similar in
the future. Would make the integration that much nicer.

> Any "quickstart setting up" would be awesome to have at this stage. As
> this is a Django app, I think I should be able to figure out the bits
> and bolts to get it up and running in some shape but obviously it will
> impede wider adoption.

Yeah I agree. I'm in the process of documenting it, so I'll aim to get
a quickstart guide together.

I have a private repo with code to set up a development environment
which uses Heat and Ansible - this might be the quickest way to get
started. I'm happy to share this with you privately if you like.

> On the note of adoption, if I find it usable, I can provide support
> for it in Kolla [1] and help grow the project's adoption this way.

Kolla could be useful. We're already using containers for this project
now, and I have a helm chart for deploying to k8s.

Also, an important part is making sure the images are set up correctly
with XRDP, etc. Our images are built using Packer, and the config for
them can be found at https://github.com/NeCTAR-RC/bumblebee-images

> Also, since this is OpenStack-centric, maybe you could consider
> migrating to OpenDev at some point to collaborate with interested
> parties using a common system?
> Just food for thought at the moment.

I think it would be more appropriate to start a new project. I think
our codebase has too many assumptions about the underlying cloud.

We inherited the code from another project too, so it's got twice the cruft.

> Writing to let you know I have also found the following related paper: [1]
> and reached out to its authors in the hope to enable further
> collaboration to happen.
> The paper is not open access so I have only obtained it for myself and
> am unsure if licensing permits me to share, thus I also asked the
> authors to share their copy (that they have copyrights to).
> I have obviously let them know of the existence of this thread. ;-)
> Let's stay tuned.
> [1] https://link.springer.com/chapter/10.1007/978-3-030-99191-3_12

This looks interesting. A collaboration would be good if there is
enough interest in the community.


More information about the openstack-discuss mailing list