Skip to content

Conversation

@JackQuincy
Copy link
Contributor

@JackQuincy JackQuincy commented Apr 10, 2019


This checklist is used to make sure that common guidelines for a pull request are followed.

  • The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

  • I adhere to the Command Guidelines.

JackQuincy and others added 4 commits March 27, 2019 15:42
* adding cluster admin option to osa create

* adding direcctory read permissions to the aad app

* making active directory app always require directory permissions

* infra node to 3
* adding cluster admin option to osa create

* adding direcctory read permissions to the aad app

* making app always require directory permissions

* clean + infra node to 3

* fixing typo

* using new version of acs python sdk
@tjprescott tjprescott requested a review from mboersma April 11, 2019 17:14
Copy link
Member

@mboersma mboersma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good Jack, I had a couple minor comments.

short-summary: The CIDR used on the Subnet into which to deploy the cluster.
- name: --customer-admin-group-id
type: string
short-summary: The ID of an Azure Active Directory Group that memberships will get synced into the OpenShift group "osa-customer-admins". If not specified no cluster admin access will be granted
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you change the second sentence here to have a comma and end with a period?
If not specified, no cluster admin access will be granted.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks like this was already updated

agent_infra_pool_profile = OpenShiftManagedClusterAgentPoolProfile(
name='infra', # Must be 12 chars or less before ACS RP adds to it
count=int(2),
count=int(3),
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this change the default node pool count from 2 to 3? That seems like a significant change (not related to this PR). Maybe it should be mentioned separately in the release notes.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, we agreed on this to switch from 2 to 3

Copy link
Contributor

@yugangw-msft yugangw-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A few minor comments. Please address and I will merge


2.3.20
++++++
* adding customer-admin-group-id flag to az osa create
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please move to the top

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, moved to top as 2.3.22 and bumped version

short-summary: The CIDR used on the Subnet into which to deploy the cluster.
- name: --customer-admin-group-id
type: string
short-summary: The ID of an Azure Active Directory Group that memberships will get synced into the OpenShift group "osa-customer-admins". If not specified, no cluster admin access will be granted.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i believe it should be the object id of the AAD group? If yes, please make it clear

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated description

- name: Create an OpenShift cluster and auto create an AAD Client
text: az openshift create -g MyResourceGroup -n MyManagedCluster --fqdn {FQDN}
- name: Create an OpenShift cluster and auto create an AAD Client and setup cluster admin group
text: az openshift create -g MyResourceGroup -n MyManagedCluster --fqdn {FQDN} --customer-admin-group-id {GROUP_ID}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is going to be incompatible with PR #9083 which removes FQDN.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tjprescott FQDN is not being removed. Its being made optional. PR #9083 will be done on top of this PR.

additional_properties=None, type="Scope")
required_osa_aad_access = RequiredResourceAccess(resource_access=[resource_access],
# Read directory permissions on Windows Azure Active Directory API
directory_access = ResourceAccess(id="5778995a-e1bf-45b8-affa-663a9f3f4d04",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this hard-coded ID?

Copy link

@amanohar amanohar Apr 18, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is this hard-coded ID?

@tjprescott these are scope GUIDs for programmatic use and represent various permissions: https://docs.microsoft.com/en-us/graph/permissions-reference. Currently there isn't a straightforward documentation from AAD for this and this is obtained by looking at currently configured apps in AAD.

@tjprescott tjprescott modified the milestone: Sprint 59 Apr 18, 2019
# Conflicts:
#	src/command_modules/azure-cli-acs/HISTORY.rst
#	src/command_modules/azure-cli-acs/setup.py
@amanohar
Copy link

@yugangw-msft @mboersma comments addressed by @sozercan. PTAL

@tjprescott
Copy link
Member

@amanohar @sozercan need to get the CI green

@mboersma
Copy link
Member

mboersma commented Apr 19, 2019

From the CI failures, maybe we just need to re-record the test_aks_create_service_no_wait test?

Edit: or all of them. AZURE_CLI_TEST_MODULES=acs azdev test

@sozercan
Copy link
Member

sozercan commented Apr 24, 2019

@tjprescott any ideas why PURPOSE='Load extension commands' test fails? https://travis-ci.org/Azure/azure-cli/jobs/523726845

Verifying extension: dev-spaces
The checksum of the extension does not match the expected value. Use --debug for more information.
The command "./scripts/ci/test_extensions.sh" exited with 1.

@sozercan
Copy link
Member

@tjprescott @yugangw-msft tests are green now

@tjprescott tjprescott merged commit 70099c5 into Azure:dev Apr 24, 2019
@sozercan sozercan deleted the osa-cluster-admin branch April 24, 2019 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants