New Compute Profile Available

[marstr]

As seen in Azure/azure-sdk-for-go#525 authored by @moritzheiber:

Working with Virtual Machine Scale Sets with Ubuntu using this SDK isn't very easy since it neither allows for Scale Sets to carry extensions, nor, since the compute API is using an outdated version, modification of customData passed to each instance.
However, customData is the only way of passing data to Scale Set instances using the go SDK. This means modifying the customData property will only work if you take down the Scale Set prior to modification.
API version 2016-08-30 does support modification of the customData property and I'ld vouch for a bump in API versions in the compute client, if possible.
//cc @pellepelster @fbernitt

A new Swagger profile needs to be defined to accommodate new functionality in the Azure service.

[colemickens]

(Hopefully one of these new Compute swaggers will include the MSI-related fields. I have an internal thread about this, but I thought it was worth mentioning here as well)

[moritzheiber]

Solving this issue would be really helpful because without the newer API specs using Scale Sets is pretty much impossible to get right through the dependent SDKs

[amarzavery]

@huangpf Please take a look. Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Moritz Heiber <notifications@github.com> Sent: Wednesday, February 1, 2017 12:22:36 AM To: Azure/azure-rest-api-specs Cc: Subscribed Subject: Re: [Azure/azure-rest-api-specs] New Compute Profile Available (#895) Solving this issue would be really helpful because without the newer API specs using Scale Sets is pretty much impossible to get right through the dependent SDKs — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-rest-api-specs%2Fissues%2F895%23issuecomment-276598808&data=02%7C01%7Camzavery%40microsoft.com%7C32646addbb61457e201e08d44a7b7b8e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636215341591056229&sdata=NYhmXscmRbldeyHSfJJ5gcWs%2BFm0AXu9tt%2F%2BYwYuMwg%3D&reserved=0>, or mute the thread<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAET9B3yX19EdDN4-x5EMlW05DF7by3dHks5rYEDMgaJpZM4LzO83&data=02%7C01%7Camzavery%40microsoft.com%7C32646addbb61457e201e08d44a7b7b8e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636215341591056229&sdata=zcNyYNEteJHngX4FBUHLAPKAyutXhEkkR%2BWnn695%2BP8%3D&reserved=0>.

[huangpf]

2016-08-30 doesn't seem to be an official API version. Is it for a special or preview release or internal customers?

[moritzheiber]

I was referencing this support thread in my issue submitted for the Golang SDK.

[huangpf]

From the Compute spec, you can see there is no such official API version:
https://github.com/Azure/azure-rest-api-specs/tree/master/arm-compute

But I believe AutoRest generated API in any language supports overriding the request being sent, please refer to how this C# handler is defined:
https://github.com/Azure/azure-sdk-for-net/blob/AutoRest/src/ResourceManagement/Compute/Compute.Tests/Helpers/RecordedDelegatingHandler.cs

I don't think we have a plan to add a spec with that API version, but I would like to add @singhkays to help confirm.

[moritzheiber]

So you're saying there is an API version, but it's unofficial, thus there will be no support inside the official SDKs?

[huangpf]

This needs service team's confirmation, awaiting @singhkays.

[singhkays]

Sorry @huangpf, I don't own this. From the linked support thread looks like @gbowerman might have some knowledge of this re:VMSS. Also adding @stephbaron for Compute spec question.

[moritzheiber]

To provide some context: Asking the AzureCloud API itself about the providers available and their respective API versions returns the following snippet for virtualMachineScaleSets:

{
  "aliases": null,
  "apiVersions": [
    "2016-08-30",
    "2016-03-30",
    "2015-06-15",
    "2015-05-01-preview"
  ],
  "locations": [
    "East US",
    "East US 2",
    "West US",
    "Central US",
    "North Central US",
    "South Central US",
    "North Europe",
    "West Europe",
    "East Asia",
    "Southeast Asia",
    "Japan East",
    "Japan West",
    "Australia East",
    "Australia Southeast",
    "Brazil South",
    "Canada Central",
    "Canada East",
    "West US 2",
    "West Central US",
    "UK South",
    "UK West"
  ],
  "properties": null,
  "resourceType": "virtualMachineScaleSets"
}

That's why I was expecting these specs to support the API version I mentioned.

[gbowerman]

The currently valid Compute API versions are: 2016-03-30 and 2016-04-30-preview.
Despite the preview moniker the latter will be one we recommend to use in production starting next week (2/8). A little while after that it will be 2017-03-30. Therefore the AzureCloud API should return these values (and possibly the 2016-06-15 one as well though I hope no-one uses it since it was before scale set GA).

[moritzheiber]

@gbowerman Okay, I understand. Three questions though:

1. Why is the API returning the (supposedly unsupported) version 2016-08-30 as "available" then?
2. Why do you recommend using version 2016-08-30 in the linked support thread?
3. Shouldn't the SDK not be a representation of what's available, and not what's recommended? I mean, it's not like your target audience are toddlers .. ?

I'm not trying to be obnoxious here, but the feature I'm after is only supported by the newer API version, and, according to the Azure API, it seems like it's supposed to be supported, thus I was looking for support in the official SDK as well.

Am I missing something? Just trying to make sense of it.

[gbowerman]

@moritzheiber as I understand it, 1, 2, 3 above are bugs we need to fix. Your questions are not obnoxious. They are a useful elucidation of the problem. I've started a thread with the Compute API owners - various Compute resources have the same and apparently invalid dates.

[hassanbabaie]

@gbowerman Hi Guy, it doesn't look like Microsoft's API documentation has changed, do you know if the move to 2016-04-30-preview is delayed?

[gbowerman]

@hassanbabaie 2016-04-30-preview is GA today. Hopefully you'll see the API updated shortly.

[hassanbabaie]

@gbowerman yes spotted it now, thanks!

[kirthik]

@gbowerman , @stephbaron : Please close this if the issue is resolved.

[moritzheiber]

Err, how's 2016-04-30-preview going GA solving this issue? I will still be unable to use Scale Sets properly ..

[cberner]

It looks like 2017-03-30 has been released, could that be added? We're still blocked on using Scale Sets because the custom_data field can't be modified under the 2016-04-30-preview API version.

> az provider list
...
"apiVersions": [
          "2017-03-30",
          "2016-08-30",
          "2016-04-30-preview",
          "2016-03-30",
          "2015-06-15",
          "2015-05-01-preview"
        ],

[salameer]

Closing due to inactivity