« Virtualization of Enterprise Systems - Primer | Main | Some Definitions Cloudpeople, Clouds and Private Cloud »



Feed You can follow this conversation by subscribing to the comment feed for this post.

Douq Millar

If vApps are essentially a template to stamp more instances of virtual configurations, how then does update occur? One of the many potential advantages of vApps is that configurations are standardized, all with fresh updates and patches, so that support is easier (every customer doing same thing, hitting same issues, nothing occurs due to unique configurations).

Does updating the vApp update the derived instances or does each instance have to be maintained separately?

I'd think a structure where software image is shared between all instances, but data is unique would do the trick - oh yeah, isn't that multi-tenant?

Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment

Comments are moderated, and will not appear until the author has approved them.

Your Information

(Name is required. Email address will not be displayed with the comment.)

Cloud Computing Journal
Top 100 Cloud Computing Bloggers