Fwd: Desktop as a Service solution

[Iheb Kahloul <ka...@gmail.com>]

Hello, i m working on a DaaS solution based on open source IaaS.
Do you advise me to base my work on CloudStack?
And if so, what are the VDI protocoles that it's using?

Ps: I have a realy short amount of time to provide a Beta version.
Thank you,
Iheb Kahloul

RE: Desktop as a Service solution

[Vijayendra Bhamidipati <vi...@citrix.com>]

Ah, didn't see the subject line earlier - I was thinking of Data as a service apart from Desktop as a Service when I saw DaaS and was wondering! You can ignore that first line unless you want to add more :)

Regards,
Vijay

-----Original Message-----
From: Vijayendra Bhamidipati [mailto:vijayendra.bhamidipati@citrix.com] 
Sent: Tuesday, April 16, 2013 3:57 PM
To: dev@cloudstack.apache.org
Subject: RE: Desktop as a Service solution

Iheb,

You  mentioned DaaS, so if possible, please provide us with more details on the DaaS solution you are trying to implement. Since you mentioned VDI protocols, I assume you are looking to build a VDI solution on top of a cloud platform, spawning off VDI host VMs on demand, and deploying a connection broker to route the VDI to user assignment. Please correct me if this isn't the case, but if so, cloudstack would be a great fit, especially considering that you have little time for the beta version. You can use cloudstack APIs to upload/remove VDI images, use them to spawn off VMs, retrieve the VM uuids, store it in your own layer to map their life cycle/assignments etc. You can dynamically add disks if required to the guest VMs, or follow a simpler storage allocation model. You can take snapshots, create templates of the guest VMs as well in case you would want to provide users with templates containing pre-installed software, according to your organization's license requirements. You can also use various network deployment models that cloudstack offers for traffic isolation between VMs.

Cloudstack supports integration with NFS on iSCSI and SAN (Fibre Channel) as well as the backend, so you will have wider options for deployment of the backend storage arrays that will need to store the VDI images.

Compared to other IaaS solutions, cloudstack is vastly easier to setup, so starting with it would be a good idea.

As for VDI protocols, as I see it, the IaaS wouldn't know about them - they would logically sit on top of the IaaS.

Please let us know if you have any questions or need help with cloudstack itself.

Regards,
Vijay

-----Original Message-----
From: Iheb Kahloul [mailto:kahloul.iheb@gmail.com] 
Sent: Tuesday, April 16, 2013 2:18 PM
To: dev@cloudstack.apache.org
Subject: Fwd: Desktop as a Service solution

Hello, i m working on a DaaS solution based on open source IaaS.
Do you advise me to base my work on CloudStack?
And if so, what are the VDI protocoles that it's using?

Ps: I have a realy short amount of time to provide a Beta version.
Thank you,
Iheb Kahloul

RE: Desktop as a Service solution

[Vijayendra Bhamidipati <vi...@citrix.com>]

Iheb,

You  mentioned DaaS, so if possible, please provide us with more details on the DaaS solution you are trying to implement. Since you mentioned VDI protocols, I assume you are looking to build a VDI solution on top of a cloud platform, spawning off VDI host VMs on demand, and deploying a connection broker to route the VDI to user assignment. Please correct me if this isn't the case, but if so, cloudstack would be a great fit, especially considering that you have little time for the beta version. You can use cloudstack APIs to upload/remove VDI images, use them to spawn off VMs, retrieve the VM uuids, store it in your own layer to map their life cycle/assignments etc. You can dynamically add disks if required to the guest VMs, or follow a simpler storage allocation model. You can take snapshots, create templates of the guest VMs as well in case you would want to provide users with templates containing pre-installed software, according to your organization's license requirements. You can also use various network deployment models that cloudstack offers for traffic isolation between VMs.

Cloudstack supports integration with NFS on iSCSI and SAN (Fibre Channel) as well as the backend, so you will have wider options for deployment of the backend storage arrays that will need to store the VDI images.

Compared to other IaaS solutions, cloudstack is vastly easier to setup, so starting with it would be a good idea.

As for VDI protocols, as I see it, the IaaS wouldn't know about them - they would logically sit on top of the IaaS.

Please let us know if you have any questions or need help with cloudstack itself.

Regards,
Vijay

-----Original Message-----
From: Iheb Kahloul [mailto:kahloul.iheb@gmail.com] 
Sent: Tuesday, April 16, 2013 2:18 PM
To: dev@cloudstack.apache.org
Subject: Fwd: Desktop as a Service solution

Hello, i m working on a DaaS solution based on open source IaaS.
Do you advise me to base my work on CloudStack?
And if so, what are the VDI protocoles that it's using?

Ps: I have a realy short amount of time to provide a Beta version.
Thank you,
Iheb Kahloul