Eksporter (0) Skriv ut
Vis alt
EN
Dette innholdet er ikke tilgjengelig på ditt språk, men her er den engelske versjonen.

List Operating System Families

Updated: September 30, 2014

The List Operating System Families operation lists the guest operating system families available in Microsoft Azure, and also lists the operating system versions available for each family.

The List Operating System Families request may be specified as follows. Replace <subscription-id> with the subscription ID.

 

Method Request URI

GET

https://management.core.windows.net/<subscription-id>/operatingsystemfamilies

You must make sure that the request that is made to the management service is secure. For additional details, see Authenticating Service Management Requests.

The following table describes the request headers.

 

Request Header Description

x-ms-version

Required. Specifies the version of the operation to use for this request. The value of this header must be set to 2010-10-28 or higher. For more information about versioning headers, see Service Management Versioning.

The response includes an HTTP status code, a set of response headers, and a response body.

A successful operation returns status code 200 (OK). For information about status codes, see Service Management Status and Error Codes.

The response for this operation includes the following headers. The response may also include additional standard HTTP headers. All standard headers conform to the HTTP/1.1 protocol specification.

 

Response Header Description

x-ms-request-id

A value that uniquely identifies a request made against the management service.

The format of the response body is as follows:

<?xml version="1.0" encoding="utf-8"?>
<OperatingSystemFamilies xmlns="http://schemas.microsoft.com/windowsazure">
  <OperatingSystemFamily>
    <Name>osfamily-number</Name>
    <Label>base64-encoded-label</Label>
    <OperatingSystems>
      <OperatingSystem>
        <Version>operating-system-version</Version>
        <Label>base64-encoded-label</Label> 
        <IsDefault>true|false</IsDefault>
        <IsActive>true|false</IsActive>
      </OperatingSystem>
    </OperatingSystems>
  </OperatingSystemFamily>
</OperatingSystemFamilies>

The following example shows the format of the response body.

 

Element Name Description

Name

Specifies the operating system family this version belongs to. For information about supported Guest OS releases, see Azure Guest OS Releases and SDK Compatibility Matrix.

Label

Specifies the base-64 encoded label of the operating system family.

Version

Specifies the operating system version. This value corresponds to the configuration value for specifying that your service is to run on a particular version of the Azure guest operating system. See Azure Guest OS Update Settings for additional details.

Label

Specifies the base-64 encoded label of the operating system version.

IsDefault

Indicates whether this operating system version is the default version for a service that has not otherwise specified a particular version. The default operating system version is applied to services that are configured for auto-upgrade. An operating system family has exactly one default operating system version at any given time, for which the IsDefault element is set to true; for all other versions, IsDefault is set to false.

See Azure Guest OS Update Settings for additional details on configuring operating system versions for your service.

IsActive

Indicates whether this operating system version is currently active for running a service. If an operating system version is active, you can manually configure your service to run on that version.

An operating system version may be inactive for one of two reasons:

  • It is not yet active as it is in the process of being rolled out to Azure data centers. If your service is configured to use auto-upgrade, it will be upgraded to the new operating system version during the rollout. If you are manually configuring your operating system version, you can upgrade to the latest version once it becomes active.

  • It is no longer supported for running a service. In this case you will either need to manually configure your service to run on a newer version, or configure your service to use auto-upgrade to manage operating system upgrades.

Vis:
© 2014 Microsoft