-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm working out any bugs in the rewrites I've already committed.
After that, I'll be working on anything needed on the frontend for VCL-174 (NAT). Then, I'll be going through the remaining JIRA issues for the frontend to start cleaning things up. If anyone else is interested in working on some of the issues for the frontend, don't hesitate to speak up. Any help is appreciated - testing is very needed as well. Josh On Monday, September 22, 2014 1:55:21 PM Andy Kurth wrote: > I'd like to start discussing and planning the VCL 2.4 release. This is a > good opportunity to review and improve several aspects of the project > including our testing and release procedures, documentation, and the > roadmap. I will be best to create separate threads for the various > topics. This thread is devoted to the progress of development work which > remains to be done. Separate threads will be created to discuss > documentation, etc. > > Please use this thread to detail everything you are working on or plan to > work on related to VCL 2.4. If the technical details of any particular > issue needs to be discussed further, start a dedicated thread. > > Here is a link to the open 2.4 issues: > https://issues.apache.org/jira/issues/?filter=12329339 > > And to all of the 2.4 issues: > https://issues.apache.org/jira/issues/?filter=12329344 > > Some of the open issues can be closed. I will be going through and > updating the ones I have worked on this week. > > I have added a "fix version" 2.4 tag to all of the issues which were only > tagged 2.3.3, and these are included in this filter. We should probably > delete 2.3.3 from Jira. I have also added a 2.5 version to Jira. There > will be a few issues we will decide to shelve for 2.4. These can be > untagged 2.4 and tagged 2.5. Please DO NOT untag any issues from 2.4 > without first asking the dev list! > > There are a few significant issues I plan to work on over the next few > weeks: > > * Database changes for VCL 2.4 ( > https://issues.apache.org/jira/browse/VCL-764) > I will be working on a Perl script which reads vcl.sql and either imports > the schema into a new database for new installs or compares the file to an > existing database's schema and executes 'alter' statements. This will > eliminate the need for the unwieldy update-vcl.sql file. > > * Allow dynamic private IP addresses, remove /etc/hosts requirement ( > https://issues.apache.org/jira/browse/VCL-767) > There is still some work to do to remove the reliance on /etc/hosts being > populated on each management node. The code is still using the hostname > for SSH commands. This needs to be changed. It is required in order to > properly test the Openstack module. For this issue, we need an upgrade > path since this is a significant change would could significantly break > things. When an upgrade to 2.4 is performed, each management node will > need to check every computer mapped to it and make sure the private IP > address the hostname resolves to matches the database. The database should > be updated if the private IP address is missing or incorrect. This > functionality may be included in the script to update the schema, making it > a more general install/upgrade script. > > * Improve user connection checking and how firewall is locked down ( > https://issues.apache.org/jira/browse/VCL-753) > This is also a significant change and needs a lot of testing. The code to > use the connectlog table is mostly complete but I have not committed it yet. > > * Add support for 64-bit cygwin ( > https://issues.apache.org/jira/browse/VCL-783) > This is a pretty easy one. The Windows module was designed to funnel > everything which would be affected by 32 vs 64-bit versions through > is_64_bit and get_system32_path so the changes will be minor. The > cygwin-sshd-config.sh and update_cygwin.cmd scripts also need an update. > > As always, your thoughts and comments are welcome. > > Thank You, > Andy - -- - ------------------------------- 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.22 (GNU/Linux) iEYEARECAAYFAlQi8zwACgkQV/LQcNdtPQPbCQCfc/xzDXKEh2PNV54vbt5EVX9Z dgoAnj/+vCXwwOj8s3xRz3dJUAxC+Qmg =ugrb -----END PGP SIGNATURE-----
