You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Aaron Peeler <aa...@ncsu.edu> on 2010/10/05 18:47:50 UTC
Re: VCL 2.3 feature/improvement planning
I think this is a good path. Someone had mentioned libvirt previously
for controlling vm's. Would this make sense? Or should vcl interact
directly with kvm? http://libvirt.org/
Also I'd like to suggest us targeting a smaller release around the the
first of the year? Addressing any bug-fixes for 2.2 or maybe 1 or more
of the features scheduled for 2.3.
Anyone else?
Aaron
On 9/30/10 4:00 PM, Andy Kurth wrote:
> I'd like to begin planning the development of VCL 2.3. We need to
> work out a
> list of features/improvements to work on. The following is the
> current roadmap:
>
> VCL 2.3
> * Service deployments
> * power management
> * improve cluster reservations
>
> VCL 2.4
> * additional and improved hypervisor support
> * KVM and possibly others (virtual box and XEN)
> * Allow for additional access methods for environments (port, other
> protocols, etc)
>
> VCL 2.5
> * develop tools for managing both system and user storage
>
> (Note: This roadmap isn't set in stone and can be modified as the
> community sees
> fit. Please reply if you can think of additional features, think
> things should
> be prioritized differently, etc.)
>
> Going forward, the community needs development involvement from more
> people.
> One obvious/easy way to begin this will be to incorporate the code
> which has
> been submitted via this list/Jira but not yet been incorporated into
> VCL. I
> would like to target the following to be incorporated for 2.3:
>
> * VCL-203 Modify backend in order to be compatible with both MySQL and
> Apache
> Derby, submitted by Milen Paskov
> * VCL-339 Add the KVM support for VCL, submitted by Xianqing Yu
> * VCL-389 Duke ESX provisioning module, submitted by Sean Dilda
>
> (Please forgive me and speak up if I missed any other contributions)
>
> Another feature which came up recently on this list is Windows lab
> provisioning.
> I have created a Jira issue VCL-388 for this. I think this would be
> fairly
> straightforward to implement and might be a good task for someone to get
> involved with development. If you're interested, please start a
> thread, share
> some ideas, ask for collaboration, etc.
>
> The resulting VCL 2.3 roadmap:
> * Service deployments
> * power management
> * improve cluster reservations
> * Backend Derby support
> * KVM provisioning
> * Extend VMware provisioning options
> * Windows lab provisioning
>
> In addition, there are many Jira issues already tagged for 2.3 and
> other open
> issues which have not yet been scheduled for a particular version.
> Please take
> a look by clicking on the '2.3' and 'Unscheduled' links on this page:
> http://issues.apache.org/jira/browse/VCL
>
> Thoughts?
>
> Regards,
> Andy
>
--
Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_peeler@ncsu.edu
919-513-4571
Re: VCL 2.3 feature/improvement planning
Posted by James O'Dell <jo...@fullerton.edu>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I think libvirt is a great idea. Why write for vmware/kvm/xen if all
you need to do is write for libvirt? Very cool, vendor agnostic approach.
It should also be stable, as it's included in the latest version
of RedHat.
__Jim
On 10/5/2010 9:47 AM, Aaron Peeler wrote:
> I think this is a good path. Someone had mentioned libvirt previously
> for controlling vm's. Would this make sense? Or should vcl interact
> directly with kvm? http://libvirt.org/
>
> Also I'd like to suggest us targeting a smaller release around the the
> first of the year? Addressing any bug-fixes for 2.2 or maybe 1 or more
> of the features scheduled for 2.3.
>
> Anyone else?
>
> Aaron
>
> On 9/30/10 4:00 PM, Andy Kurth wrote:
>> I'd like to begin planning the development of VCL 2.3. We need to
>> work out a
>> list of features/improvements to work on. The following is the
>> current roadmap:
>>
>> VCL 2.3
>> * Service deployments
>> * power management
>> * improve cluster reservations
>>
>> VCL 2.4
>> * additional and improved hypervisor support
>> * KVM and possibly others (virtual box and XEN)
>> * Allow for additional access methods for environments (port, other
>> protocols, etc)
>>
>> VCL 2.5
>> * develop tools for managing both system and user storage
>>
>> (Note: This roadmap isn't set in stone and can be modified as the
>> community sees
>> fit. Please reply if you can think of additional features, think
>> things should
>> be prioritized differently, etc.)
>>
>> Going forward, the community needs development involvement from more
>> people.
>> One obvious/easy way to begin this will be to incorporate the code
>> which has
>> been submitted via this list/Jira but not yet been incorporated into
>> VCL. I
>> would like to target the following to be incorporated for 2.3:
>>
>> * VCL-203 Modify backend in order to be compatible with both MySQL and
>> Apache
>> Derby, submitted by Milen Paskov
>> * VCL-339 Add the KVM support for VCL, submitted by Xianqing Yu
>> * VCL-389 Duke ESX provisioning module, submitted by Sean Dilda
>>
>> (Please forgive me and speak up if I missed any other contributions)
>>
>> Another feature which came up recently on this list is Windows lab
>> provisioning.
>> I have created a Jira issue VCL-388 for this. I think this would be
>> fairly
>> straightforward to implement and might be a good task for someone to get
>> involved with development. If you're interested, please start a
>> thread, share
>> some ideas, ask for collaboration, etc.
>>
>> The resulting VCL 2.3 roadmap:
>> * Service deployments
>> * power management
>> * improve cluster reservations
>> * Backend Derby support
>> * KVM provisioning
>> * Extend VMware provisioning options
>> * Windows lab provisioning
>>
>> In addition, there are many Jira issues already tagged for 2.3 and
>> other open
>> issues which have not yet been scheduled for a particular version.
>> Please take
>> a look by clicking on the '2.3' and 'Unscheduled' links on this page:
>> http://issues.apache.org/jira/browse/VCL
>>
>> Thoughts?
>>
>> Regards,
>> Andy
>>
>
>
- --
Jim O'Dell
Network Analyst
California State University Fullerton
Email: jodell@fullerton.edu
Phone: (657) 278-2256
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkyredgACgkQREVHAOnXPYTMuACgntxSxCjPo2Pzgyhpuf1KvH6H
9rUAnjefi+n7ukWy9knUqD/Nu+6dWpTu
=cYgy
-----END PGP SIGNATURE-----