[OASIS Issue Tracker] Updated: (TOSCA-92) Use Case: Enabling admin access to endpoints

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/TOSCA-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthew Rutkowski  updated TOSCA-92:
------------------------------------


The following document lists additional "admin" access considerations:
https://www.oasis-open.org/apps/org/workgroup/tosca-interop/download.php/48514/ConsiderationsFor2TierWebApplications.docx

these include:
For HTTP apps. Setting the HTTP listen port to something other than 80. Disabling 80 and using 443. Only using SSL. Configuring SSL keys. Are there any other ports which need to be configured such as locking down off admin ports which may be externally accessible.

The SC agreed to move these comments/considerations into this use case for development.

> Use Case: Enabling admin access to endpoints
> --------------------------------------------
>
>                 Key: TOSCA-92
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-92
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Interop
>         Environment: Use case for development against TOSCA-v1.0-cs01.
>            Reporter: Matthew Rutkowski 
>            Assignee: Derek Palma
>
> TBD. This is the second agreed upon use case for the examples listed below which is to focus on "admin access" to endpoints.
> Examples:
> a) OS admin access -  Cloud may provide key pair. For clouds that don't provide SSH key pairs, install SSH keys (or accept password security).
> b) MySQL admin - Create optional separate SSH account or use OS SSH, Configure DB admin password
> c) Application via SSL -  Install specific SSL certs on WebServer Tier or Load Balancer
> d) Application clear and SSL - May need to configure VirtualHosts (or like concept)
> Notes:
> Matt: There seems to be multiple scenarios for this page of the presentation.  Do any need a separate issue? Can all or some be represented using a single use case? It seems there are pre-deploy (provide keys), during deploy (access to keys) and post deploy considerations (keys, IPs, access information).
> Derek: would break it down into endpoint config (exposing, creating).  Should be a pattern that can be used over and over. Other case is admin access. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira