[
https://issues.apache.org/jira/browse/WHIRR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051531#comment-13051531
]
Tibor Kiss commented on WHIRR-88:
---------------------------------
@Andrei:
Regarding tarball URL to be local or remote...
We have not just tarballs, but packages which has to be installed with yum or
apt-get.
I am reasoning to the idea that having our own well tested and persisted image
would mean everything preinstalled, but not yet activated to start
automatically. With this idea the biggest problem is how to handle such a
second step install phase targeted to only one instance where he will install
the differences calculated from roles enumerated in instance-templates. For
example, in case of Hadoop if the targeted instance is the masternode,
searching by roles, it can be calculated that is still missing the
hadoop-datanode and hadoop-tasktracker.
The entire image creation for me it is an additional feature which is more
administrative than any other command currently we have. Being administrative,
it is something which you may use it less frequent. Such as administrative
process of image creation is more related to quality assurance. Some SLA impose
such a restriction to a production environment so that the well tested cluster
to be started from a persisted instance. Therefore that persistence step I
would split in two or three sub-steps in between you can review things
manually. These would be that 3 steps:
1. install the difference calculated from rules of the instance-templates into
the target instance
2. cleanup the instance to be ready to persist into image
3. create the image itself.
The step 3. is the least important to be coordinated by whirr API, allowing
more free access to fulfill the SLA requirements.
> 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
