Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 240675

Re: Check my understanding of composer bits/architecture

$
0
0

TedH256 wrote:

 

Regarding #1 above, I guess what I was trying to get at is this:

 

I have a vm that I've used as gold master, then I create a snapshot, then a replica is created based on that. Now - I want to create a new pool - can I take another snapshot of that same "gold master" and then use the second snapshot as the basis for my new pool? Or is that entirely silly and if I want a new pool I need to create a new gold master, and then a snapshot of that?

 


You can do either depending on what you feel is easier to manage.   The new pool can even go as far as to be pointed at the exisiting snapshot if that is applicable.

 

 

TedH256 wrote:

 

And some clarifying attempts here on another point:

 

if I need to "update the image" (let's say new patches applied, etc) then what is the process? I imagine something like:

 

update the gold master, then take a new snapshot, then somehow use the recompose process to point at the updated snapshot? Do I need to commit the first snapshot before I create the new one? And - do I have to take the pool off-line before I do any of this?

 

Thank you for you patience! Clearly I'm a newby at this, and I can read documentation till I fall asleep, but somehow it never seems to "just say" what needs to be done, so an exchange like this is very very helpful to me!

You have the right idea.   Update your parent image, shutdown the parent image, create a new snapshot, and then recompose the pool based on that snapshot.   There is no need to commit the first snapshot and most people will leave it around in case the new snapshot has some type of configuration issue.   Also you don't take the pool offline but individual desktops will be offline as they are recomposed.


Viewing all articles
Browse latest Browse all 240675

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>