You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by "Andy Kurth (JIRA)" <ji...@apache.org> on 2014/10/01 18:32:34 UTC

[jira] [Updated] (VCL-525) explain how to install non autoprovisioned connect methods

     [ https://issues.apache.org/jira/browse/VCL-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Kurth updated VCL-525:
---------------------------
    Description: 
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).

  was:Provide a way to explain to users how to install connect methods that cannot be autoprovisioned by the backend.


> 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)