Bug 1376050 - [RFE] Support for SCVMM 2016 [NEEDINFO]
Summary: [RFE] Support for SCVMM 2016
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: cfme-future
Assignee: John Hardy
QA Contact: Jeff Teehan
URL:
Whiteboard: scvmm:provider
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-14 14:10 UTC by Loic Avenel
Modified: 2021-09-09 11:56 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 14:57:15 UTC
Category: Feature
Cloudforms Team: CFME Core
Target Upstream Version:
lavenel: needinfo? (jhardy)


Attachments (Terms of Use)

Description Loic Avenel 2016-09-14 14:10:03 UTC
Description of problem:

SCVMM 2106 is not currently supported

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Dave Johnson 2016-09-15 23:00:44 UTC
Jeff, haven't we already done a little bit investigation around this?  I believe I recall us setting up a vm or two but maybe I am wrong.  If there are specific issues, we probably should open them and link them to this RFE.

Comment 3 Jeff Teehan 2016-09-15 23:09:00 UTC
Yes, and we determined that we would need additional servers to support Windows Server 2016 which would be required to virtualize the hyper-v servers and provide enough power to handle the load.  It's not SCVMM that is the issue, it's the lack of hyper-v servers to attach to it.

Comment 5 Jeff Teehan 2017-02-23 01:01:38 UTC
Yeah, it works fine.  It's a small environment.  Honestly, I can't see any difference between 2012 R2 with global update 13.1 the latest versions.  Near as I can tell they are identical and they just renamed it.

We can go ahead and close this one.  I already add all the test cases to Polarion.


Note You need to log in before you can comment on or make changes to this bug.