[
https://issues.apache.org/jira/browse/WHIRR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13050910#comment-13050910
]
Paul Baclace commented on WHIRR-88:
-----------------------------------
Until there is a convenient way to make and save OS images to be used later by
Whirr, what is the workaround? That is, what does Whirr require of an image
and how can a custom image be invoked?
Presumably, I should be able to ssh to a master created by Whirr and then
follow a cloud provider specific method for saving the current image. The
trick is to save the image when it is still in a "stem cell" phase that allows
it to become a master or slave, and can be modified for specific cluster
details. (I've done this before with by modifying the old bash scripts, but
Whirr+jclouds is coming along nicely.)
> Support image creation
> ----------------------
>
> Key: WHIRR-88
> URL: https://issues.apache.org/jira/browse/WHIRR-88
> Project: Whirr
> Issue Type: New Feature
> Components: core
> Reporter: Tom White
>
> Much of the time taken to start a cluster is in installing the software on
> the instances. By allowing users to build their own images it would make
> cluster launches faster. The way this could work is by having a create image
> step that brings up an instance and runs the install scripts on it before
> creating an image from it. The resulting image would then be used in
> subsequent launches.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
