[
https://issues.apache.org/jira/browse/OODT-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14031027#comment-14031027
]
Sheryl John commented on OODT-676:
----------------------------------
Hi, yes you're right.
I think I found out why it didn't automatically download. My vagrant version
was really old (1.2.2!). So just upgrading it on my machine, and believe it'll
work without changing the Vagrantfile to point to an existing box.
> Simplify OODT RADiX setup: provide pre-configured RADiX via Vagrant
> -------------------------------------------------------------------
>
> Key: OODT-676
> URL: https://issues.apache.org/jira/browse/OODT-676
> Project: OODT
> Issue Type: New Feature
> Components: radix
> Affects Versions: 0.6
> Environment: Platform-independent (Vagrant currently supports MacOSX,
> Windows, Debian, CentOS)
> Reporter: Rishi Verma
> Assignee: Rishi Verma
> Fix For: 0.7
>
> Attachments: OODT-676.rverma.06-12-2014.patch.txt, radix-vagrant.tar
>
>
> Hitting the ground running with OODT can be a challenge, that's one of the
> reasons RADiX was developed. However, we can make that process even simpler
> by providing users with a pre-configured RADiX deployment through the use of
> Vagrant virtual machine technology [1].
> The benefits:
> * Users only need to issue a single command ("vagrant up") to have a full
> OODT RADiX deployment running on their machine - no configuration,
> dependencies, or modifications required! Tools like JDK, Maven2, etc will be
> automatically installed on the Vagrant virtual machine.
> * Latest OODT snapshot features will be automatically provisioned for use by
> RADiX. In other words, if users want to use a RADiX version that has not yet
> been tagged to a released OODT version, they can use this proposed tool to
> automatically use a snapshot with no extra effort.
> * Reproducible and reusable RADiX development environment for all users. New
> projects, demo configurations, etc can all benefit by having a VM created
> automatically and consistently.
> Suggested approach:
> * New top-level OODT directory titled "vagrant", containing sub-folders with
> more specific development environment configurations
> * Start with a single Vagrant dev environment supporting the automated set up
> of the latest trunk version of RADiX. Add more as separate JIRA issues
> --
> [1] http://www.vagrantup.com/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
