There are still 51 jira issues tagged for the upcoming release. I suggest the following be either closed or pushed out to a later release. Please confirm if these should be pushed out:
VCL-579 provision ESXi as an end-user env VCL-572 Automatically install updates when an image is loaded VCL-416 Fix the default user profile when capturing an image VCL-465 Add support for computers with a single NIC VCL-678 Reduce unnecessary output written to vcld.log VCL-718 Add optional automatic execution of sdelete.exe to reduce vmdk size VCL-308 Computer load log does not account for images that have to be transferred to another management node Others? Also if ones that have been completed or are still in progress, please closed or updated. Aaron On Fri, Oct 31, 2014 at 9:24 AM, Mark Gardner <[email protected]> wrote: > On Fri, Oct 31, 2014 at 9:14 AM, Josh Thompson <[email protected]> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> I'd like to either close VCL-710 (Allow an admin to permanently delete an >> image) as Won't Fix, or bump it to a later release. The ability to delete >> VMware image files has been added to the setup part of vcld. I imagine >> adding >> other types of image files wouldn't be too difficult. There is currently >> no >> way for the frontend to trigger something like this on the backend. So, it >> would require enough design and development that I don't think it is a good >> idea to try to get it in 2.4. >> > > > +1 for postpone > . D > on't know about won't fix > as I have not had the need. > > > > Mark > -- > Mark Gardner > -- -- 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.
