-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We need testers!
We're really close to having 2.4 ready for release. I've created a VM with VCL trunk installed in to for people to use for testing the latest code. It is based on KVM and CentOS 7 and requires a host that supports nesting hypervisors. It is using the new NAT code. So, you only need a host with a single network adapter. After downloading the VM from https://drive.google.com/file/d/0B8eeP8Y-9a1VZmJfbjlocm9NMHc/view?usp=sharing you need to create a VM on your host with a single NIC that has a MAC address of 0e:00:00:38:fe:db and is bridged to a network from which it can get a public IP address via DHCP. Once you boot the VM, you can log in at the console to find out what IP address it received. Log in as root. The password is 'testVCL@trunk14'. Open a web browser and enter the IP. You should be redirected to the VCL page for selecting an authentication method. Log in with local account 'admin'. The password is the same as for the root user listed above. There is one CentOS 7 image available for testing and two VMs. There is a third VM that is running all of the VCL code. You can get to it from the parent VM by running 'ssh mn'. There is a script named update.sh in /root on the management node VM that will run 'svn update' for all the VCL parts. It does download updates for the database .sql files, but it does not import the update-vcl.sql file to actually change the schema. If you see that update-vcl.sql gets updated when running the update.sh script, you may want to manually update the schema. Make sure to do a backup first! Please test and report any problems you find or if you find that everything works without problems! Merry Christmas, 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 iEYEARECAAYFAlSZ2GUACgkQV/LQcNdtPQP4yACcCIJQEyAS2oYXUFXBYpE2S9Dt 7WIAnjI46UfYxjsjkv80Ol9U3fNl295Q =VT1A -----END PGP SIGNATURE-----
