Bug 1039027

Summary: Request POWER architecture support in DTS
Product: Red Hat Developer Toolset Reporter: Michael Pagan <mpagan>
Component: RFEsAssignee: Brian Gollaher <nobody+bgollahe>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: unspecified    
Version: DTS 2.1 RHEL 6CC: bgollahe, drieden, mbenitez, mnewsome
Target Milestone: ---   
Target Release: 6.0   
Hardware: ppc64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-26 16:06:56 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Pagan 2013-12-06 12:06:37 UTC
Description of problem:

Bloomberg starting major development on RHEL 6 running on IBM Power architecture. Need DTS supported in Power to make DTS usable.

Version-Release number of selected component (if applicable):

DTS 2.1 and later, RHEL 6

How reproducible:

Not applicable

Steps to Reproduce:
1. Not applicable

Actual results:

Not applicable

Expected results:

Not applicable

Additional info:

Request support of IBM Power architecture for DTS moving forward.

Comment 3 Brian Gollaher 2014-01-14 16:19:30 UTC
DTS 2.1 is locked down and currently in alpha.  We will consider this request for a later DTS release.

Comment 9 Matt Newsome 2016-10-26 16:06:56 UTC
Red Hat recently released Developer Toolset 6 Beta with support on Red Hat Enterprise Linux for Power.

Please see the press release here:

https://www.redhat.com/en/about/blog/red-hat-software-collections-23-beta-red-hat-developer-toolset-6-beta-now-available

release notes here:

https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/6-Beta/html/6.0_Release_Notes/index.html

and user guide here:

https://access.redhat.com/documentation/en-US/Red_Hat_Developer_Toolset/6-Beta/html/User_Guide/index.html

In view of this availability we are closing this bug, however please raise further bugs if there are specific issues you encounter in evaluating the Beta release.