You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/06 19:27:20 UTC

[jira] [Commented] (JCLOUDS-106) Modernize CloudStack instance credentials and security group code

    [ https://issues.apache.org/jira/browse/JCLOUDS-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677263#comment-13677263 ] 

ASF subversion and git services commented on JCLOUDS-106:
---------------------------------------------------------

Commit fbe637c8bfb951532a48b6f70eff0dc739654ee9 in branch refs/heads/master from [~abayer]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-jclouds.git;h=fbe637c ]

JCLOUDS-106. Add proper support for generation/detection of keypair/security groups to CloudStack.

                
> Modernize CloudStack instance credentials and security group code
> -----------------------------------------------------------------
>
>                 Key: JCLOUDS-106
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-106
>             Project: jclouds
>          Issue Type: Improvement
>    Affects Versions: 1.6.0
>            Reporter: Andrew Bayer
>            Assignee: Andrew Bayer
>             Fix For: 1.7.0
>
>
> See JCLOUDS-105 for a symptom caused by this - the CloudStack login code is rather archaic. It still expects the largely deprecated credentials store to be populated and the like. It should really get modernized to be like, say, openstack-nova. Same thing with security groups - we assume they already exist or we muck around with the default security group, and that's not optimal by a long shot.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira