| 1 |
Alec Ten Harmsel <alec@××××××××××××××.com> writes: |
| 2 |
|
| 3 |
> On Tue, Jan 19, 2016 at 01:46:45AM +0100, lee wrote: |
| 4 |
>> "J. Roeleveld" <joost@××××××××.org> writes: |
| 5 |
>> |
| 6 |
>> > On Monday, January 18, 2016 02:02:27 AM lee wrote: |
| 7 |
>> >> "J. Roeleveld" <joost@××××××××.org> writes: |
| 8 |
>> >> > On 17 January 2016 18:35:20 CET, Mick <michaelkintzios@×××××.com> wrote: |
| 9 |
>> >> > |
| 10 |
>> >> > [...] |
| 11 |
>> >> > |
| 12 |
>> >> >>I use the icaclient provided by Citrix to access my virtual desktop at |
| 13 |
>> >> >>work, |
| 14 |
>> >> >>but have never tried to set up something similar at home. What |
| 15 |
>> >> >>opensource |
| 16 |
>> >> >>software would I need for this? Is there a wiki somewhere to follow? |
| 17 |
>> >> >> |
| 18 |
>> >> > I'd love to do this myself as well. |
| 19 |
>> >> > |
| 20 |
>> >> > Citrix sells the full package as 'XenDesktop'. To do it yourself you need |
| 21 |
>> >> > a VMserver (Xen or similar) and a remote desktop tool that hooks into the |
| 22 |
>> >> > VM display. (Spice or VNC) |
| 23 |
>> >> > |
| 24 |
>> >> > Then you need some way of authenticating users and providing access to the |
| 25 |
>> >> > client software. [...] |
| 26 |
>> >> |
| 27 |
>> >> You would have a full VM for each user? |
| 28 |
>> > |
| 29 |
>> > Yes |
| 30 |
>> > |
| 31 |
>> >> That would be a huge waste of resources, |
| 32 |
>> > |
| 33 |
>> > Diskspace and CPU can easily be overcommitted. |
| 34 |
>> |
| 35 |
>> Overcommitting disk space sounds like a very bad idea. Overcommitting |
| 36 |
>> memory is not possible with xen. |
| 37 |
>> |
| 38 |
> |
| 39 |
> Depends on how the load is. Right now I have a 500GB HDD at work. I use |
| 40 |
> VirtualBox and vagrant for testing various software. Every VM in |
| 41 |
> VirtualBox gets a 50GB hard disk, and I generally have 7 or 8 at a time. |
| 42 |
> Add in all the other stuff on my system, which includes a 200GB dataset, |
| 43 |
> and the disk is overcommitted. Of course, none of the VirtualBox disks |
| 44 |
> use anywhere near 50GB. |
| 45 |
|
| 46 |
True, that's for testing when you do know that the disk space will not |
| 47 |
be used and have no trouble when it is. When you have the VMs in |
| 48 |
production and users (employees) using them, you don't know when they |
| 49 |
will run out of disk space and trouble ensues. |
| 50 |
|
| 51 |
> All Joost is saying is that most resources can be overcommitted, since |
| 52 |
> all the users will not be using all their resources at the same time. |
| 53 |
|
| 54 |
How do you overcommit disk space and then shrink the VMs automatically |
| 55 |
when disk usage gets lower again? |
Archives