You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2014/04/22 20:38:16 UTC

[jira] [Resolved] (AURORA-299) Improve vagrant setup

     [ https://issues.apache.org/jira/browse/AURORA-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Farner resolved AURORA-299.
--------------------------------

    Resolution: Fixed

Claiming success here, vagrant is much closer to a viable development aid.  We have some more work to figure out the story for iterating on code with the vagrant setup, but we can tackle that in a separate effort.

> Improve vagrant setup
> ---------------------
>
>                 Key: AURORA-299
>                 URL: https://issues.apache.org/jira/browse/AURORA-299
>             Project: Aurora
>          Issue Type: Story
>          Components: Build
>            Reporter: Bill Farner
>            Assignee: Bill Farner
>
> There are a handful of things i'd like to improve with the vagrant setup:
> - require less RAM.  running {{vagrant up}} is not really feasible on a machine with 4 GB of RAM
> - look into puppet or chef for provisioning
> - use a process manager like monit or supervisor



--
This message was sent by Atlassian JIRA
(v6.2#6252)