Zuul d6c2422bc3 Merge "Use diskimage username in AWS and Azure drivers"

2023-08-23 00:57:54 +00:00

24 KiB

Raw Blame History

zuul

Azure Compute Driver

Before using the Azure driver, make sure you have created a service principal and saved the credential information in a JSON file. Follow the instructions at Azure CLI and use the --sdk-auth flag:

az ad sp create-for-rbac --name nodepool --sdk-auth

You must also have created a network for Nodepool to use. Be sure to enable IPv6 on the network if you plan to use it.

The Azure driver now uses "Standard" SKU for all public IP addresses. Standard IP addresses block all incoming traffic by default, therefore the use of a Network Security Group is required in order to allow incoming traffic. You will need to create one, add any required rules, and attach it to the subnet created above.

You may also need to register the Microsoft.Compute resource provider with your subscription.

Selecting the azure driver adds the following options to the providers section of the configuration.

providers.[azure]

An Azure provider's resources are partitioned into groups called pool, and within a pool, the node types which are to be made available are listed

Note

For documentation purposes the option names are prefixed providers.[azure] to disambiguate from other drivers, but [azure] is not required in the configuration (e.g. below providers.[azure].pools refers to the pools key in the providers section when the azure driver is selected).

Example:

providers:
  - name: azure-central-us
    driver: azure
    location: centralus
    resource-group: nodepool
    resource-group-location: centralus
    auth-path: /path/to/nodepoolCreds.json
    network: nodepool
    cloud-images:
      - name: bionic
        username: zuul
        key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAA...
        image-reference:
          sku: 18.04-LTS
          publisher: Canonical
          version: latest
          offer: UbuntuServer
    pools:
      - name: main
        max-servers: 10
        labels:
          - name: bionic
            cloud-image: bionic
            hardware-profile:
              vm-size: Standard_D1_v2

name

A unique name for this provider configuration.

location

Name of the Azure region to interact with.

resource-group

Name of the Resource Group in which to place the Nodepool nodes.

resource-group-location

Name of the Azure region where the home Resource Group is or should be created.

auth-path

Path to the JSON file containing the service principal credentials. Create with the Azure CLI and the --sdk-auth flag

network

Network upon which to create VMs. This can either be a string, in which case it must be the name of a network in the provider's resource group and Nodepool will use the subnet named default, or it can be a dictionary with these keys:

resource-group

The resource group containing the network.

network

The name of the network.

subnet

The name of the subnet within the network.

ipv4

Whether to enable IPv4 networking. Defaults to true unless ipv6 is enabled. Enabling this will attach a private IP address.

ipv6

Whether to enable IPv6 networking. Enabling this will attach a private IP address.

public-ipv4

Whether to attach a public IPv4 address to instances. Defaults to true, but will change to false in a future release. Implies ipv4.

public-ipv6

Whether to attach a public IPv4 address to instances. Defaults to true, but will change to false in a future release. Implies ipv6.

use-internal-ip

If a public IP is attached but Nodepool should prefer the private IP, set this to true.

host-key-checking

Whether to validate SSH host keys. When true, this helps ensure that nodes are ready to receive SSH connections before they are supplied to the requestor. When set to false, nodepool-launcher will not attempt to ssh-keyscan nodes after they are booted. Disable this if nodepool-launcher and the nodes it launches are on different networks, where the launcher is unable to reach the nodes directly, or when using Nodepool with non-SSH node platforms. The default value is true.

rate

The number of operations per second to perform against the provider.

boot-timeout

Once an instance is active, how long to try connecting to the image via SSH. If the timeout is exceeded, the node launch is aborted and the instance deleted.

launch-timeout

The time to wait from issuing the command to create a new instance until that instance is reported as "active". If the timeout is exceeded, the node launch is aborted and the instance deleted.

launch-retries

The number of times to retry launching a server before considering the request failed.

post-upload-hook

Filename of an optional script that can be called after an image has been uploaded to a provider but before it is taken into use. This is useful to perform last minute validation tests before an image is really used for build nodes. The script will be called as follows:

<SCRIPT> <PROVIDER> <EXTERNAL_IMAGE_ID> <LOCAL_IMAGE_FILENAME>

If the script returns with result code 0 it is treated as successful otherwise it is treated as failed and the image gets deleted.

cloud-images

Each entry in this section must refer to an entry in the labels section.

cloud-images:
  - name: bionic
    username: zuul
    image-reference:
      sku: 18.04-LTS
      publisher: Canonical
      version: latest
      offer: UbuntuServer
  - name: windows-server-2016
    username: zuul
    image-reference:
       sku: 2016-Datacenter
       publisher: MicrosoftWindowsServer
       version: latest
       offer: WindowsServer

Each entry is a dictionary with the following keys

name

Identifier to refer this cloud-image from labels section. Since this name appears elsewhere in the nodepool configuration file, you may want to use your own descriptive name here.

username

The username that should be used when connecting to the node.

password

If booting a Windows image, an administrative password is required. Either supply it here, or set providers.[azure].cloud-images.generate-password. Nodepool does not provide the password to requesting clients; to be used it must be provided in some other manner.

generate-password

If booting a Windows image, an administrative password is required. If the password is not actually used (e.g., the image has key-based authentication enabled), a random password can be provided by enabling this option. The password is not stored anywhere and is not retrievable.

key

The SSH public key that should be installed on the node.

connection-type

The connection type that a consumer should use when connecting to the node. For most diskimages this is not necessary. However when creating Windows images this could be winrm to enable access via ansible.

connection-port

The port that a consumer should use when connecting to the node. For most diskimages this is not necessary. This defaults to 22 for ssh and 5986 for winrm.

python-path

The path of the default python interpreter. Used by Zuul to set ansible_python_interpreter. The special value auto will direct Zuul to use inbuilt Ansible logic to select the interpreter on Ansible >=2.8, and default to /usr/bin/python2 for earlier versions.

shell-type

The shell type of the node's default shell executable. Used by Zuul to set ansible_shell_type. This setting should only be used

For a windows image with the experimental connection-type ssh in which case cmd or powershell should be set and reflect the node's DefaultShell configuration.
If the default shell is not Bourne compatible (sh), but instead e.g. csh or fish, and the user is aware that there is a long-standing issue with ansible_shell_type in combination with become

image-filter

Specifies a private image to use via filters. Either this field, providers.[azure].cloud-images.shared-gallery-image, providers.[azure].cloud-images.community-gallery-image, providers.[azure].cloud-images.image-reference, or providers.[azure].cloud-images.image-id must be provided.

If a filter is provided, Nodepool will list all of the images in the provider's resource group and reduce the list using the supplied filter. All items specified in the filter must match in order for an image to match. If more than one image matches, the images are sorted by name and the last one matches.

Example:

cloud-images:
  - name: image-by-name
    image-filter:
      name: test-image
  - name: image-by-tag
    image-filter:
      tags:
        foo: bar

The following filters are available:

name

The name of the image.

location

The location of the image.

24 KiB Raw Blame History

Azure Compute Driver

24 KiB

Raw Blame History