Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Instance pool usages #5894

Merged
merged 13 commits into from
Jun 17, 2019
Merged

Instance pool usages #5894

merged 13 commits into from
Jun 17, 2019

Conversation

johnpaulkee
Copy link
Contributor

@johnpaulkee johnpaulkee commented May 8, 2019

Latest improvements:

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Contribution checklist:

  • I have reviewed the documentation for the workflow.
  • Validation tools were run on swagger spec(s) and have all been fixed in this PR.
  • The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

  • Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
  • adding/removing APIs.
  • adding/removing properties.
  • adding/removing API-version.
  • adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

  • If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
    Please follow the link to find more details on API review process.

@AutorestCI
Copy link

AutorestCI commented May 8, 2019

Automation for azure-sdk-for-ruby

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-ruby#2635

@AutorestCI
Copy link

AutorestCI commented May 8, 2019

Automation for azure-sdk-for-python

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-python#5771

@AutorestCI
Copy link

AutorestCI commented May 8, 2019

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@AutorestCI
Copy link

AutorestCI commented May 8, 2019

Automation for azure-sdk-for-js

A PR has been created for you based on this PR content.

Once this PR will be merged, content will be added to your service PR:
Azure/azure-sdk-for-js#3877

@johnpaulkee
Copy link
Contributor Author

I plan to add instancePoolUsages.json and instancePools.json (not in this review) in a separate PR, so merging with just these files after validation and review is ok.

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@AutorestCI
Copy link

AutorestCI commented May 8, 2019

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@sergey-shandar sergey-shandar added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 10, 2019
@ravbhatnagar
Copy link
Contributor

@johnpaulkee - The API signature and the response schema does not comply with ARM /usages contract. Please take a look - https://armwiki.azurewebsites.net/api_contracts/UsagesAPIContract.html

@ravbhatnagar ravbhatnagar added the ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review label May 13, 2019
@ravbhatnagar
Copy link
Contributor

ravbhatnagar commented May 19, 2019

We(ARM) will need to update the usages contract to cater to such scenarios. I Will have a proposal early next week. That way we can have consistency across Azure w.r.t getting usage data.

@sanjaiganesh
Copy link
Contributor

PR still needs to be updated per new usages spec (ARM). Gaurav is following up offline with the team.


In reply to: 493736164 [](ancestors = 493736164)

@johnpaulkee
Copy link
Contributor Author

johnpaulkee commented May 31, 2019

Acked on updated usages contract

@johnpaulkee johnpaulkee requested a review from jaredmoo as a code owner June 7, 2019 20:34
@openapi-sdkautomation
Copy link

openapi-sdkautomation bot commented Jun 7, 2019

SDK Automation [Logs] (Generated from 73f5d68)

Pending Python: Azure/azure-sdk-for-python
  • Package generation pending.
Pending Java: Azure/azure-sdk-for-java
  • Package generation pending.
Pending Go: Azure/azure-sdk-for-go
  • Package generation pending.
Pending JavaScript: Azure/azure-sdk-for-js
  • Package generation pending.
Pending Ruby: Azure/azure-sdk-for-ruby
  • Package generation pending.

@johnpaulkee
Copy link
Contributor Author

johnpaulkee commented Jun 7, 2019

PR still needs to be updated per new usages spec (ARM). Gaurav is following up offline with the team.

In reply to: 493736164 [](ancestors = 493736164)

I've updated swagger based on updated usages contract.
There is ongoing thread with ARM team to help us with this:

-	Provide exact standardized swagger, in particular:
o	prescribed operation id’s (e.g. “InstancePools_ListUsages”? “Usages_ListByInstancePool”),
o	schema names
o	parameter names 
o	descriptions,
-	Work with Samer’s team to come up with validators for these?

@ravbhatnagar please validate when possible :) thank you.

@sergey-shandar
Copy link
Contributor

@ravbhatnagar @sanjaiganesh any update on ARM review?

@johnpaulkee
Copy link
Contributor Author

Ping @ravbhatnagar for review.

{
"swagger": "2.0",
"info": {
"version": "2.0",
Copy link
Contributor

Choose a reason for hiding this comment

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

this should be the api-version

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed. thanks @ravbhatnagar 👍

@ravbhatnagar
Copy link
Contributor

@johnpaulkee - looks good. just the api-version needs to be fixed. Signing off considering the api-version value will be fixed.

@ravbhatnagar ravbhatnagar added ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review and removed ARMChangesRequested <valid label in PR review process>add this label when require changes after ARM review WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required labels Jun 14, 2019
@johnpaulkee
Copy link
Contributor Author

Thanks @ravbhatnagar , I've updated api-version.
@sergey-shandar should be good for review now.

@johnpaulkee
Copy link
Contributor Author

ping @sergey-shandar for review.
I've updated the instancePoolUsages.json to usages.json FYI.

@johnpaulkee
Copy link
Contributor Author

Thanks @sergey-shandar !

@johnpaulkee johnpaulkee deleted the instancePoolUsages branch June 17, 2019 22:37
mccleanp pushed a commit that referenced this pull request Mar 23, 2022
…5894)

* AzureSphere: Fix of response of generateDefaultDeviceGroups action.
Work item:
https://dev.azure.com/msazuresphere/4x4/_workitems/edit/127676

* Azure Sphere fix typo on example
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants