Same master image for pools of different memory size

[bjohn]

View 5.1.3.

How can I use the same master image to create:

1 pool with 4gb memory and another pool with 2gb memory.

Thanks

[nzorn]

You'll have to create 2 different snapshots (one with 4GB and one with 2GB of RAM), and you'll end up with 2 replicas.

[bjohn]

Wow, seems like a lot of work. Every time I update the master image, I would have to snapshot twice?

What if I create a pool with the 4gb master image and manually change the machines in the pool to 2GB. If I recompose, would they go back to 4GB?

[nzorn]

I would not recommend manually changing a composer created virtual machine.

[bjohn]

hmm, so there is no way to do this?

I want to use the same master image, so I don't have to update two master images.

One set of users need 2GB and another set of users require 4GB.

[nzorn]

As mentioned before you should be able to use the same master image, but 2 different snapshots.

[bjohn]

So when I updated my master image (monthly), the current master image is 2CPU/4GB. I should shutdown and take a snapshot. Then change to 1CPU/2GB and snapshot again. I don't think I have to reboot the VM, since it will be rebooted during recompose.

Is there a better way, anyone do anything similar?

Thanks

[vcpguy]

I would prefer to have 2 images with different Memory settings. During the life time of the Maste Image, there will be multiple snapshots, refresh and recompose. It will make things difficult for you to manage with different memory settings.

Basic design principal - keep things simple !!!

[bjohn]

I really cant believe there is no better way to do this.

I dread having to have two master images (or snapshots) just to have two different memory configurations.

The only thing different between these two pools is the memory.

Anyone out there do anything similar?

[bjohn]

Shameless bump to see if anyone has any other ideas, or if anyone does anything similar.