You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Sean Mackrory (JIRA)" <ji...@apache.org> on 2014/12/31 01:13:14 UTC
[jira] [Resolved] (BIGTOP-871) Add a Boxgrinder wrapper to Bigtop
[ https://issues.apache.org/jira/browse/BIGTOP-871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Mackrory resolved BIGTOP-871.
----------------------------------
Resolution: Won't Fix
And done. I did indeed end up using Packer for all the stuff I needed to do. If there is a need for stand-alone VM images in the future I'd suggest we use Packer instead of trying to fill in the widening gaps in Boxgrinder, but let's create a new JIRA when that time comes...
> Add a Boxgrinder wrapper to Bigtop
> ----------------------------------
>
> Key: BIGTOP-871
> URL: https://issues.apache.org/jira/browse/BIGTOP-871
> Project: Bigtop
> Issue Type: Improvement
> Reporter: Sean Mackrory
> Assignee: Sean Mackrory
> Attachments: boxgrinder-bigtop.tar.gz
>
>
> There are certain improvements that I think can be made to the Bigtop VMs that are probably best accomplished by making a simple wrapper around Boxgrinder. Improvements include:
> - For including hypervisor-specific extensions, like VMWare Tools or Virtualbox Guest additions
> - More polishing of the resulting artifacts, like creating OVA appliances, tweak the VMX appliances
> - A good way to separate the boxgrinder configuration for each component
> I've done some tinkering in this direction and will post code for my ideas soon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)