[
https://issues.apache.org/jira/browse/CLOUDSTACK-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521739#comment-14521739
]
ASF GitHub Bot commented on CLOUDSTACK-8433:
--------------------------------------------
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/216#issuecomment-97861338
@runseb - Sure. I was testing 4.5 today and the awsapi service did not
work for me, after wasting almost 2 hours to make it work, I tried ec2stack
which worked out of the box. I thought it would be a good idea to get rid of it
and promote ec2stack :)
I’ve split the changes in 3 commits to make it easier to rebase/merge. I’ll
keep this open and hope to merge it next week but am interested in merge it now
to avoid rebasing efforts again. If ec2stack will get its own git repo like
docs repos or cloudmonkey - does it matter if we merge this now or next week
and will this block 4.6 release management?
> Deprecate and remove CloudStack AWSAPI which is not actively maintained or
> widely used
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8433
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8433
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.6.0
>
>
> Since the last discussion on dev ML, I've tested awsapi on ACS 4.5 and it
> does not work for me, possibly due to using older versions while newer
> clients such as awscli have moved now. I tried ec2stack which worked out of
> the box. It only makes sense to deprecate awsapi, remove it and add an
> upgrade path starting 4.6.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
