Bug 1315947 - [RFE] When provisioning to Azure, Resource Group should be listed first under placement.
[RFE] When provisioning to Azure, Resource Group should be listed first under...
Status: CLOSED NOTABUG
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Provisioning (Show other bugs)
5.6.0
Unspecified Unspecified
unspecified Severity unspecified
: GA
: 5.6.0
Assigned To: Greg McCullough
Jeff Teehan
provision:ui:azure
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-09 00:29 EST by Jeff Teehan
Modified: 2016-05-06 12:29 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-06 12:29:00 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jeff Teehan 2016-03-09 00:29:37 EST
Description of problem:

In the Azure Provisioning: Environment Tab : Placement Options, Resource Group is the last choice, but the first three fields are sub-components of the Resource Group.  As Resource Group is the top most important selection, it doesn't make sense to select it last as it would void all the previous selections if they were not in that Resource Group.

Or, it should be automatically selected based on the Resource Group associated with the Storage Account which contains the Image.

Version-Release number of selected component (if applicable):
cfme-hyperv-5.6.0.0-nightly-20160308112121-1.x86_64.vhd

How reproducible:
Feature Request

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Bronagh Sorota 2016-03-09 10:54:40 EST
Hi Jeff,

A virtual machine can be provisioned to a different resource group than the one the selected network/subnet belongs to. The requirement is that the resource groups of each must belong to the same region. If you select a resource group and then change your mind and select a different one you will not see any change in the cloud network/subnet controls.

Also, it wouldn't be ideal to force the virtual machine to be placed in the same resource group that the source image (storage account) belongs to.
Comment 3 Jeff Teehan 2016-03-09 11:17:59 EST
Ok, let me try a few more complicated provision requests and if it handles them all I'll close this.  If we are going to allow any resource group to be used then we should also update the docs and require that the Active Directory App be assigned to the entire subscription rather than at the Resource Group level, unless you're already checking for that.

I'm just so used to having Resource Group being drilled into my head as just about every PowerShell cmdlet requires it as the first parameter.
Comment 4 Bronagh Sorota 2016-05-06 09:46:43 EDT
Jeff,
Did you try a few more complicated provisioning requests? Can this ticket be closed?

Thanks
Comment 5 Jeff Teehan 2016-05-06 12:29:00 EDT
Hi,

We can definitely do things using cross resource group objects that don't appear to be possible using the Azure GUI.  That said, it works and the VM runs without errors.

Closing as requested.

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