-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Comments inline - I'll add the comments to the JIRA issues as well.
On Wednesday, October 01, 2014 12:59:11 PM Andy Kurth wrote: > Thanks for the feedback. One request when anyone untags an issue, please > add a comment with the corresponding discussion from this thread or a link > to this thread. This will make it easier to evaluate the issues later on. > > > > > VCL-178 - enable checkuser flag for per reservation instead of image > > only > > > > > > https://issues.apache.org/jira/browse/VCL-178 > > > > > > -1 (keep in 2.4) > > > This is one that was created in 2009 and got bumped all the way from > > > the 2.2 release. The backend code has supported this feature since > > > 2010. This would be pretty useful. How much time would it take to > > > implement this? > > > > The easy part is adding a checkbox for reservations that says not to do > > user > > login checks. The hard part is determining who sees the checkbox (i.e. > > permissions). How do we determine who gets to see this functionality? Is > > it > > a global permission? Is it something that is image specific? Is it image > > specific but also tied to a user permission? > > Though not ideal, what about doing something similar to the special > "Specify End Time" group? If we want to do something more elaborate in the > future such as adding a new privilege, it should be relatively easy to > transition by granting the single special group the new privilege. That would work and wouldn't be too difficult. > > > > VCL-526 - add section to site to manage connect methods > > > > https://issues.apache.org/jira/browse/VCL-526 > > > > > > -1 (or replace with a new issue) > > > How much time will this take? We added the connect methods feature in > > > 2.3 without a way to manage them other than directly modifying the > > > database. Not good. If adding a feature to the website takes too > > > much time we could add something to "vcld -setup" for 2.4. I'm not > > > voting +1 for the release without some way to manage this. > > > > Again, this is a permissions issue. Who gets to see and manage each > > connect > > method? It would also require creating a new section of the site for > > managing > > it. It may work to make them a new resource. > > So, add to "vcld -setup"? This wouldn't be too difficult and would only be > available to admins with access to a management node. I think this eventually needs to be in the frontend, but having it in the backend for 2.4 would allow things to be managed and would handle the permissions issue. However, it seems like a lot to add to "vcld -setup". Are you thinking to be able to add and remove connect methods, edit the connecttext and ports for them, and control their mappings? > > > VCL-577 - Cloud Broker tool for VCL > > > > > > > https://issues.apache.org/jira/browse/VCL-577 > > > > > > +? > > > This was submitted by Karuna Joshi. We need to reach out to her and > > > make sure she is involved in this discussion. If she is interested > > > and willing to assist, we should make an effort to include this in > > > 2.4. If she is interested but it is not feasible timewise to include > > > it in 2.4, it should be top priority after the release. We need to > > > encourage these contributions. > > > > This is more something that uses VCL instead of something that is part of > > VCL. > > So, I don't see a need for it being included in a release. However, if it > > were, Karuna would need to step up as a committer to maintain it, in which > > case, she should be contacted. > > I don't necessarily see it as needing to be included, but the issue > includes a patch file to the VCL code and there was a fair amount of > communication in the issue comments. The responsibility of testing it and > getting it into the release rests on her. We have been bitten in the past > by removing a module someone contributed who was not active in the > community at the time. Although this is not the same situation, we need to > be completely transparent and be sure to not surprise anyone. I'll send > her a direct message. If she doesn't respond or is not able to prepare it > for the release within our time constraints then we shelve it. Unless I missed something, the patch doesn't actually modify any of the existing code but just adds files that use the API and can reside anywhere on the webserver. She did add one table and a view to the database though. It is a good idea to reach out to her. I'm interested to see if she wants to continue to maintain this. 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.0.22 (GNU/Linux) iEYEARECAAYFAlQsXZsACgkQV/LQcNdtPQPUVQCfRWbunPVZPfultZzYqJoSrPPq lcwAn3+lg0h2qj5CauFiGxcpJOqnck7k =9O+Z -----END PGP SIGNATURE-----
