You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bigtop.apache.org by "Bruno Mahé (JIRA)" <ji...@apache.org> on 2013/03/16 22:38:12 UTC

[jira] [Commented] (BIGTOP-871) Add a Boxgrinder wrapper to Bigtop

    [ https://issues.apache.org/jira/browse/BIGTOP-871?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13604428#comment-13604428 ] 

Bruno Mahé commented on BIGTOP-871:
-----------------------------------

That sounds awesome!
Unfortunately I recently learned that boxgrinder is now unmaintained. So if you already have the code handy or if it will not take long to implement, sure go ahead. If this is for a more long term effort, it may or may not be worth it.
I am about to open a discussion about it on the mailing list.
                
> 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
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira