-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Aaron - I think Dmitri meant actual VM images with those pieces already installed.
Dmitri - If that's the case, then no, we (ASF VCL) can't "officially" provide them since they would contain GPL things. We've (NCSU) discussed providing those to the community for anyone interested. They just couldn't be officially provided from ASF. Josh On Monday, August 26, 2013 2:49:04 PM Aaron Peeler wrote: > Hi Dmitri, > > Good point. Yes, one should be able to define which component to install. > > Aaron > > On Mon, Aug 26, 2013 at 2:34 PM, Dmitri Chebotarov <[email protected]> wrote: > > Hi, > > > > Is it an option to provide preconfigured VCL FE/BE/DB as vmware/vbox/qcow2 > > image? > > > > -- > > Thank you, > > > > Dmitri Chebotarov > > VCL Sys Eng, Engineering & Architectural Support, TSD - Ent Servers & > > Messaging > > 223 Aquia Building, Ffx, MSN: 1B5 > > Phone: (703) 993-6175 | Fax: (703) 993-3404 > > > > On 8/26/13 12:52 , "Josh Thompson" <[email protected]> wrote: > >>-----BEGIN PGP SIGNED MESSAGE----- > >>Hash: SHA1 > >> > >>Larry, > >> > >>That sounds like a great way to implement it. Thanks for the additional > >>info. > >> > >>Josh > >> > >>On Monday, August 26, 2013 11:52:25 AM Larry Burton wrote: > >>> Josh, > >>> Excellent point. I have created the installation process as a series of > >>> scripts, each of which adds a particular function function, for just > >>> this reason. A bare-metal install consists of a kickstart file and a "to > >>> do" list of scripts to run. Systems that already have an installation > >>> may run just a "to do" list to add additional functions. The script > >>> library is in a separate directory on the USB image, and may be copied > >>> to an existing installation. This seems to me to be extensible for those > >>> with a little more experience, and still allows a novice to get up and > >>> running without having to know a great deal about Linux. > >>> Larry > >>> > >>> On 08/26/2013 11:27 AM, Josh Thompson wrote: > >>> > -----BEGIN PGP SIGNED MESSAGE----- > >>> > Hash: SHA1 > >>> > > >>> > Larry, > >>> > > >>> > Would it be difficult to also provide an installer that could be run > >>> > >>>on a > >>> > >>> > system that already has a base install of Linux on it? I think there > >>> > >>>are > >>> > >>> > situations where this would be an easier starting point than putting > >>> > >>>an > >>> > >>> > image on a USB drive and booting from it. > >>> > > >>> > Thanks, > >>> > Josh > >>> > > >>> > On Friday, August 23, 2013 6:26:59 PM Larry Burton wrote: > >>> >> I have a scripted install working from bare metal to cloud, with > >>> > >>>custom > >>> > >>> >> profiling options -- except for a few remaining tweaks on xCAT. > >>> > >>>Perhaps > >>> > >>> >> we could include the package (everything is in a bootable USB image) > >>> > >>>as > >>> > >>> >> a helper for the next release, if there is interest. I'll try to > >>> > >>>finish > >>> > >>> >> a long overdue documentation update on the VCL website next week. > >>> >> Larry > >>> >> > >>> >> On 08/23/2013 10:19 AM, Aaron Peeler 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 > >>> > > >>> > - -- > >>> > - ------------------------------- > >>> > 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.19 (GNU/Linux) > >>> > > >>> > iEYEARECAAYFAlIbc+MACgkQV/LQcNdtPQNzOACfQDzr6gUrYhISGUvXKgCsIO9m > >>> > IOAAniAstqIp5lFOuwjhA7lqrkJkksDr > >>> > =LKMd > >>> > -----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.19 (GNU/Linux) > >> > >>iEYEARECAAYFAlIbh+8ACgkQV/LQcNdtPQNWTQCeLnDwUuQMYJx+Lsf3SsqDsb6m > >>2AgAn1R5khCa6XYLd9CA9LrGkzoBDMTH > >>=O5Z1 > >>-----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.19 (GNU/Linux) iEYEARECAAYFAlIbpEcACgkQV/LQcNdtPQM4lQCfWGAq5X5jcTncG4bTzBp6rW9Q 9ucAn1AwWYbbJimBzBrAzQzBqPhPpWkw =olRi -----END PGP SIGNATURE-----
