I think 2.4 should include the highest-priority items which currently prevent some institutions/organizations from using VCL including: -IPv6 support -NAT support -Single network interface support
Adding these makes the list for 2.4 ridiculously long. I would suggest moving power management, Spice, and libcloud support to later releases. I think any feature can be worked on in the meantime if anyone is interested in doing so, but completion should not prevent 2.4 from being released. I would also like to plan a 2.3.1 bug fix release targeted for early to mid August, 2012. -Andy On Tue, May 22, 2012 at 11:02 AM, Mark Gardner <m...@vt.edu> wrote: > Aaron, > > At some point I would like to put IPv6 and NAPT on the list but I am > still working on the code. (I would prefer to follow in the footsteps > of the others and have something working to back it up so maybe we > don't want to put it on the schedule yet.) > > Mark > > On Tue, May 22, 2012 at 9:50 AM, Aaron Peeler <fapee...@ncsu.edu> wrote: >> Looks good to me. >> >> Anyone else? This is a community decision :) >> >> Aaron >> >> On Tue, May 22, 2012 at 9:30 AM, Josh Thompson <josh_thomp...@ncsu.edu> >> wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> That ends up making the list of feature for 2.4 pretty long. How about >>> splitting them up into two releases as follows: >>> >>> VCL 2.3 (this release) >>> * Service deployments >>> * Allow for additional access methods for environments (port, other >>> protocols, etc) >>> * Added framework support for libvirt and specifically for KVM >>> * Added support for OS X under ESX >>> * Added support for VMware VCenter >>> * Added multilingualization to frontend >>> >>> VCL 2.4 >>> * Power management >>> * Improve additional access methods >>> * Support for Spice remote display protocol >>> * Scripted installation >>> * Support for ESX OS for end users >>> * Initial support for EC2 API and OpenStack >>> * Initial support for Libcloud >>> >>> VCL 2.5 >>> * Improve cluster reservations >>> * Service deployment configuration management >>> >>> VCL 2.6 >>> * develop tools for managing both system and user storage >>> >>> The list for 2.4 is a little long, but several of the items have a >>> significant >>> amount of the work already completed (largely by newer people in the >>> community >>> - - yay!). >>> >>> Josh >>> >>> On Monday, May 21, 2012 4:02:11 PM Aaron Peeler wrote: >>>> Looks good. >>>> >>>> I would also like to see added to 2.4: >>>> * support for ESX OS for end users - the work that Dmitri has done >>>> * initial support for EC2 api, openstack, this could likely include >>>> the code that Cameron and Young have are working on >>>> * initial support for libcloud >>>> >>>> Aaron >>>> >>>> On Mon, May 21, 2012 at 3:53 PM, Josh Thompson <josh_thomp...@ncsu.edu> >>> wrote: >>>> > -----BEGIN PGP SIGNED MESSAGE----- >>>> > Hash: SHA1 >>>> > >>>> > Previously, I had stated that I'd like to get a release candidate cut by >>>> > Wednesday of last week. We've been doing lots of testing and finding >>>> > small >>>> > bugs here and there that have kept me from cutting the RC. As soon as we >>>> > stop finding bugs, I should be able to cut the RC. >>>> > >>>> > In each release, we include a road map of where we want to go with the >>>> > next >>>> > few releases. The following is a starting point of what to include. >>>> > Please let me know if there are any notable features that I left off of >>>> > 2.3. Also, let me know what you think of the future features. >>>> > >>>> > VCL 2.3 (this release) >>>> > * Service deployments >>>> > * Allow for additional access methods for environments (port, other >>>> > protocols, etc) >>>> > * Added framework support for libvirt and specifically for KVM >>>> > * Added support for OS X under ESX >>>> > * Added support for VMware VCenter >>>> > * Added multilingualization to frontend >>>> > >>>> > VCL 2.4 >>>> > * Power management >>>> > * Improve cluster reservations >>>> > * Service deployment configuration management >>>> > * Support for Spice remote display protocol >>>> > * Scripted installation >>>> > >>>> > VCL 2.5 >>>> > * develop tools for managing both system and user storage >>>> > >>>> > Josh >>>> > - -- >>>> > - ------------------------------- >>>> > Josh Thompson >>>> > VCL Developer >>>> > North Carolina State University >>>> > >>>> > my GPG/PGP key can be found at pgp.mit.edu >>>> > >>>> > 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. >>>> > -----BEGIN PGP SIGNATURE----- >>>> > Version: GnuPG v2.0.17 (GNU/Linux) >>>> > >>>> > iEYEARECAAYFAk+6nUgACgkQV/LQcNdtPQPexACfceYBzdJ5mqvmOTbK+PKckIig >>>> > IrQAnAzC3JQGSpc76uxH8eCvp6KHebo+ >>>> > =t8CA >>>> > -----END PGP SIGNATURE----- >>> - -- >>> - ------------------------------- >>> Josh Thompson >>> VCL Developer >>> North Carolina State University >>> >>> my GPG/PGP key can be found at pgp.mit.edu >>> >>> 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. >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v2.0.17 (GNU/Linux) >>> >>> iEYEARECAAYFAk+7lPcACgkQV/LQcNdtPQOz6gCfWvwf/ETFbxmwN6D1HdwYovDo >>> cZwAnjxVK8dR2q49ZNYc0oRQUQl5nQh4 >>> =yN0Q >>> -----END PGP SIGNATURE----- >>> >> >> >> >> -- >> 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. > > > > -- > Mark Gardner > --
