cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-8433) Deprecate and remove CloudStack AWSAPI which is not actively maintained or widely used
Date Thu, 30 Apr 2015 16:29:08 GMT

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

ASF subversion and git services commented on CLOUDSTACK-8433:
-------------------------------------------------------------

Commit 3746e3d7f218ba743ea3304eebd7656ea468e7ab in cloudstack's branch refs/heads/nuke-awsapi
from [~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3746e3d ]

CLOUDSTACK-8433: remove awsapi rpm and debian packaging

- Removes awsapi packaging rules for debian, centos63, centos7, fedora 20/21
- Removes catalina port 7080 service configs
- Fixes build replace properties for AWSAPILOG
- Removes maven profile for building awsapi and deploying db in developer profile

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


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

Mime
View raw message