A year or so ago I committed an RPM spec file for VCL. I'm sure it could use some work, but we use it to deploy the application.
Also we have configuration management coded in both Ansible and Chef (but not Puppet), if that's what is meant here by configuration management and/or scripted install. Thanks, Curtis. On Fri, Aug 23, 2013 at 8:19 AM, Aaron Peeler <[email protected]> wrote: > Hi Folks, > > For the next release, we need to start planing in order to get it out > in a reasonable time frame. > > Some key features that come to my mind are: > > * NAT support VCL-174 https://issues.apache.org/jira/browse/VCL-174 > * openstack support VCL-590 https://issues.apache.org/jira/browse/VCL-590 > * maybe the openNebula support (Dmitri ?) http://opennebula.org/ > * cluster provisioning improvements > * general enhancements/bugfixes > * Some form of the scripted install(could be a bash script for non-RH > OS's, rpm install, maybe a puppet config?) > > The previous roadmap features http://vcl.apache.org/dev/roadmap.html > such as the configuration management and the broker tool are still be > worked on or vetted and wouldn't be production ready before the > release. > > These are suggestions on what I think might be release ready. I would > like to see another release out this year. > > Please share your thoughts, comments, concerns on if these are feasible. > > Thanks, > Aaron > > > -- > Aaron Peeler > Program Manager > Virtual Computing Lab > NC State University > > All electronic mail messages in connection with State business which > are sent to or received by this account are subject to the NC Public > Records Law and may be disclosed to third parties. -- Twitter: @serverascode Blog: serverascode.com
