On Wed, Oct 1, 2014 at 4:01 PM, Josh Thompson <[email protected]> wrote: > > > > > > > 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? >
It wouldn't be too much work. The code would be similar to the mechanism already in 'vcld -setup' to configure Windows KMS and MAC activation. I did not think of editing connecttext. We don't currently have any multi-line editing functionality. This would require a little bit of work. A quick way to do this may be: -Read the text field from the database, or begin with a stock template if adding a new connect method -Create a temp file populated with the text -Call system() to launch vi or the default editor and open the temp file -User edits text and saves the temp file -Read the updated text file -Validate the data -Update the database > > > > > 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. > I have corresponded with Karuna directly. She is aware of this discussion. I have asked her to respond to this thread. Regards, Andy
