[
https://issues.apache.org/jira/browse/CLOUDSTACK-8433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14521693#comment-14521693
]
ASF GitHub Bot commented on CLOUDSTACK-8433:
--------------------------------------------
GitHub user bhaisaab opened a pull request:
https://github.com/apache/cloudstack/pull/216
CLOUDSTACK-8433: Remove awsapi
Following actions from discussions on dev ML regarding removing awsapi and
preferring ec2stack. Reference from last PR:
https://github.com/apache/cloudstack/pull/44 Opening a new one as master has
changed since then and rebasing caused several conflicts so this PR consists of
3 patches (to make rebasing easier).
- Removes awsapi and awsapi-setup
- 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
- Removes awsapi db properties usage across codebase
- Removes references from spring xmls, test cases and TransactionLegacy
- Adds sql command to drop database cloudbridge in
schema-451to460-cleanup.sql
CentOS 7, CentOS 6.3, Debian repository:
http://packages.bhaisaab.org/cloudstack/nukeawsapi
TravisCI: https://travis-ci.org/apache/cloudstack/builds/60704658
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/cloudstack nuke-awsapi
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/216.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #216
----
commit e8d4ebf022a1838b079f7017b587ed8c1de37e32
Author: Rohit Yadav <[email protected]>
Date: 2015-04-30T14:05:39Z
CLOUDSTACK-8433: remove awsapi and awsapi-setup
Following actions from discussions on dev ML regarding removing awsapi and
prefering ec2stack. Reference from last PR:
https://github.com/apache/cloudstack/pull/44
Signed-off-by: Rohit Yadav <[email protected]>
commit e0eea01b4c718582e6c34d04e5f22b5d4a446d56
Author: Rohit Yadav <[email protected]>
Date: 2015-04-30T14:11:05Z
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 <[email protected]>
commit 72831ecfecdf5cd437f28c600341dc9ade00b4b7
Author: Rohit Yadav <[email protected]>
Date: 2015-04-30T14:15:39Z
CLOUDSTACK-8433: remove awsapi db usage and add upgrade cleanup path
- Removes awsapi db properties usage across codebase
- Removes references from spring xmls, test cases and TransactionLegacy
- Adds sql command to drop database cloudbridge in
schema-451to460-cleanup.sql
Signed-off-by: Rohit Yadav <[email protected]>
commit 4435ede72a437ec3adfedf46d429193f3ef039f5
Author: Rohit Yadav <[email protected]>
Date: 2015-04-30T15:43:51Z
CLOUDSTACK-8433: Fix rpm builds, avoid using commons-logging
- Removes commons-logging.properties file introduced with awsapi
- Fixed utils to use log4j instead of commons logging
Signed-off-by: Rohit Yadav <[email protected]>
----
> 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)
