Re: 2.3 release status and proposed road map
Sorry I'm getting to this thread a little late. Our priorities for 2.4 would be NAT and OpenStack support. Everett Toews | Senior Developer http://twitter.com/#%21/cybera_everettCybera Inc. http://www.cybera.ca/ @everett_toews http://twitter.com/#!/everett_toews On Wed, May 23, 2012 at 3:30 PM, Shoji Kajita kaj...@nagoya-u.jp wrote: Hi Josh, I found that php requires gettext for multilingualization (or usually, internationalization or i18n). Is it possible to check gettext support by using testsetup.php? Shoji At Mon, 21 May 2012 15:53:40 -0400, Josh Thompson 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-
Re: 2.3 release status and proposed road map
I would commit to helping scripted installation into 2.4. I believe the focus should be on a basic, entry-level VCL that is automatic from bare metal to working system for those who are no so familiar with Linux. Larry Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris, We don't have any surveys or anything like that. Things really just happen through discussion on this list. Josh On Tuesday, May 22, 2012 1:13:01 PM Chris Jones wrote: It would be nice to see IPv6 included for sure. We at Clemson are definitely wanting that. Hopefully this wasn't mentioned before and I missed it, but is there a spot to vote on what features are important to the community? Like a survey or something for interested parties? Thanks for the great work, guys! -ChrisJ On Tue, May 22, 2012 at 11:56 AM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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
Re: 2.3 release status and proposed road map
Oops, Sorry - it's already listed. Aaron On Wed, May 23, 2012 at 10:46 AM, Aaron Peeler fapee...@ncsu.edu wrote: I agree. Definitely need to add the automated/scripted install to the published roadmap. Aaron On Wed, May 23, 2012 at 7:51 AM, Larry Burton larry_bur...@runningcedar.com wrote: I would commit to helping scripted installation into 2.4. I believe the focus should be on a basic, entry-level VCL that is automatic from bare metal to working system for those who are no so familiar with Linux. Larry Josh Thompson wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris, We don't have any surveys or anything like that. Things really just happen through discussion on this list. Josh On Tuesday, May 22, 2012 1:13:01 PM Chris Jones wrote: It would be nice to see IPv6 included for sure. We at Clemson are definitely wanting that. Hopefully this wasn't mentioned before and I missed it, but is there a spot to vote on what features are important to the community? Like a survey or something for interested parties? Thanks for the great work, guys! -ChrisJ On Tue, May 22, 2012 at 11:56 AM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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
Re: 2.3 release status and proposed road map
Hi Josh, I found that php requires gettext for multilingualization (or usually, internationalization or i18n). Is it possible to check gettext support by using testsetup.php? Shoji At Mon, 21 May 2012 15:53:40 -0400, Josh Thompson 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-
Re: 2.3 release status and proposed road map
-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-
Re: 2.3 release status and proposed road map
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.
Re: 2.3 release status and proposed road map
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 --
Re: 2.3 release status and proposed road map
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 NOTE - I changed access methods to connect methods in this thread since we ended up naming it connect methods previously. Mark, We can just add IPv6 in whatever release is next after you finish it. For NAPT, I was thinking to include that as part of Improve additional connect methods for 2.4. Other parts to that specific topic would be delivering download config files for things other than just RDP if other connect methods could use them and a place in the frontend for managing (adding, removing, setting defaults for OSes, etc) the connect methods. Josh On Tuesday, May 22, 2012 11:02:03 AM Mark Gardner 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 connect 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 connect 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
Re: 2.3 release status and proposed road map
Mark, Please start a discussion thread on the vcl-dev list regarding IPv6 support. Others may be interested in participating, the current status, problems encountered, etc. Thanks, Andy On Tue, May 22, 2012 at 11:21 AM, Josh Thompson josh_thomp...@ncsu.edu wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 NOTE - I changed access methods to connect methods in this thread since we ended up naming it connect methods previously. Mark, We can just add IPv6 in whatever release is next after you finish it. For NAPT, I was thinking to include that as part of Improve additional connect methods for 2.4. Other parts to that specific topic would be delivering download config files for things other than just RDP if other connect methods could use them and a place in the frontend for managing (adding, removing, setting defaults for OSes, etc) the connect methods. Josh On Tuesday, May 22, 2012 11:02:03 AM Mark Gardner 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 connect 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 connect 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
Re: 2.3 release status and proposed road map
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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
Re: 2.3 release status and proposed road map
It would be nice to see IPv6 included for sure. We at Clemson are definitely wanting that. Hopefully this wasn't mentioned before and I missed it, but is there a spot to vote on what features are important to the community? Like a survey or something for interested parties? Thanks for the great work, guys! -ChrisJ On Tue, May 22, 2012 at 11:56 AM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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 - -- - ---
Re: 2.3 release status and proposed road map
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris, We don't have any surveys or anything like that. Things really just happen through discussion on this list. Josh On Tuesday, May 22, 2012 1:13:01 PM Chris Jones wrote: It would be nice to see IPv6 included for sure. We at Clemson are definitely wanting that. Hopefully this wasn't mentioned before and I missed it, but is there a spot to vote on what features are important to the community? Like a survey or something for interested parties? Thanks for the great work, guys! -ChrisJ On Tue, May 22, 2012 at 11:56 AM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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
Re: 2.3 release status and proposed road map
Works for me. You can put Clemson down for wanting IPv6. :) -ChrisJ On Tue, May 22, 2012 at 2:01 PM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Chris, We don't have any surveys or anything like that. Things really just happen through discussion on this list. Josh On Tuesday, May 22, 2012 1:13:01 PM Chris Jones wrote: It would be nice to see IPv6 included for sure. We at Clemson are definitely wanting that. Hopefully this wasn't mentioned before and I missed it, but is there a spot to vote on what features are important to the community? Like a survey or something for interested parties? Thanks for the great work, guys! -ChrisJ On Tue, May 22, 2012 at 11:56 AM, Josh Thompson josh_thomp...@ncsu.eduwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I like the idea of prioritizing items that are preventing people from using VCL. I'll move power management and Libcloud to 2.5. I think Spice will be taken care of with the work needed for NAT. Having Spice makes us more competitive with commercial VDI solutions. Josh On Tuesday, May 22, 2012 11:19:31 AM Andy Kurth wrote: 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
Re: 2.3 release status and proposed road map
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- -- 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.
