[
https://issues.apache.org/jira/browse/VCL-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14155072#comment-14155072
]
Andy Kurth commented on VCL-525:
--------------------------------
+1 (untag, lack of time)
Thanks for the clarification. I'd like to revisit the
connectmethodmap.autoprovisioned flag and how different connect methods show up
as (1) being a valid method a user sees on the Connect page and (2) to image
administrators as being an option to enable for an image. It may be best to
use separate columns or a separate mapping table for each use.
> explain how to install non autoprovisioned connect methods
> ----------------------------------------------------------
>
> Key: VCL-525
> URL: https://issues.apache.org/jira/browse/VCL-525
> Project: VCL
> Issue Type: Improvement
> Components: database, web gui (frontend)
> Reporter: Josh Thompson
> Fix For: 2.4
>
>
> Provide a way to explain to users how to install connect methods that cannot
> be autoprovisioned by the backend.
> Connect methods can be flagged as autoprovisioned" or not. If
> autoprovisioned, it is assumed either all images using some OS will have the
> connect method available (i.e. RDP on Windows), or vcld will be able to
> provision the method if it is not already there. If not autoprovisioned, it
> is the responsibility of the image creator to install the connect method. It
> would be useful for connect methods that are not autoprovisioned to have some
> text somewhere associated with the connect method that explains to an image
> creator how to install that connect method (i.e. To install xRDP, you need to
> install x, y, z packages and modify j, k, l configuration files).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
