vms | Compiler and a virtual machine test project in Python and C

There is a dedicated architecture reference and sample available on the Azure documentation on Immutable Infrastructure CI/CD using Jenkins and Terraform on Azure Virtual Architecture

And here is the template as well

Kafka clients don't need to expose any port mappings

Your assumption is correct, that given the proper VPC settings, then communicate should be fine.

That's working:

[answer based on the live debug] there is no issue on the DPDK side with either e1000e or vmxnet3 device. Based on the current debug it based on switch on vsphere

Debugging with kernel driver vmnext3, shows

1. VM-1 receives and transmit packets
2. VM-2 receives and transmit packets
3. there is a physical interface also connected which forwards packets.
4. set the IP address of VM-1 to '12.12.12.1' and IP address of VM-2 to '12.12.12.2'
5. Run iperf3 between VM-1 and VM-2, it fails.
6. debugging with tcpdump showcases that VM-1 is not receiving packets from the switch from VM-2. While packets from VM-1 are received.

The same is behaviour with DPDK l2fwd/testpmd/skeleton and even sample application. Hence DPDK 18.11.11 LTS with vmxnet3 has no issues in sending or receiving packets.

So no one else has to go through this pain.

The custom_data part works peachy keen. This is the script I needed to get it running:

Why do you need a state here? Can't you just do agreementInfos[index].agreement_scan_copy = res.data.data.url;?

Start/Stop VMs during off-hours

It starts or stops machines on user-defined schedules, provides insights through Azure Monitor logs, and sends optional emails by using action groups. The feature can be enabled on both Azure Resource Manager and classic VMs for most scenarios.

This feature uses Start-AzVm cmdlet to start VMs. It uses Stop-AzVM for stopping VMs.

Prerequisites

1. The runbooks for the Start/Stop VMs during off hours feature work with an Azure Run As account. The Run As account is the preferred authentication method because it uses certificate authentication instead of a password that might expire or change frequently.

2. An Azure Monitor Log Analytics workspace that stores the runbook job logs and job stream results in a workspace to query and analyze. The Automation account and Log Analytics workspace need to be in the same subscription and supported region. The workspace needs to already exist, you cannot create a new workspace during deployment of this feature.

Recommended: Use a separate Automation account for working with VMs enabled for the Start/Stop VMs during off-hours feature. Azure module versions are frequently upgraded, and their parameters might change. The feature isn't upgraded on the same cadence and it might not work with newer versions of the cmdlets that it uses. Before importing the updated modules into your production Automation account(s), we recommend you import them into a test Automation account to verify there aren't any compatibility issues.

Permissions

You must have certain permissions to enable VMs for the Start/Stop VMs during off-hours feature. The permissions are different depending on whether the feature uses a pre-created Automation account and Log Analytics workspace or creates a new account and workspace.

You don't need to configure permissions if you're a Contributor on the subscription and a Global Administrator in your Azure Active Directory (AD) tenant. If you don't have these rights or need to configure a custom role, make sure that you have the permissions described below.

Runbooks

The following link lists the runbooks that the feature deploys to your Automation account. Do NOT make changes to the runbook code. Instead, write your own runbook for new functionality.

Don't directly run any runbook with child appended to its name.

All parent runbooks include the WhatIf parameter. When set to True, the parameter supports detailing the exact behavior the runbook takes when run without the parameter and validates that the correct VMs are targeted. A runbook only performs its defined actions when the WhatIf parameter is set to False.

Main default runbooks:

1. ScheduledStartStop_Parent
2. SequencedStartStop_Parent

Variables (used by Runbooks)

The following table lists the variables created in your Automation account. Only modify variables prefixed with External. Modifying variables prefixed with Internal causes undesirable effects.

Main variables to use with your Runbooks:

1. External_Start_ResourceGroupNames: Comma-separated list of one or more resource groups that are targeted for start actions.
2. External_Stop_ResourceGroupNames: Comma-separated list of one or more resource groups that are targeted for stop actions.
3. External_ExcludeVMNames: Comma-separated list of VM names to exclude, limited to 140 VMs. If you add more than 140 VMs to the list, VMs specified for exclusion might be inadvertently started or stopped.

Schedules

Don't enable all schedules, because doing so might create overlapping schedule actions. It's best to determine which optimizations you want to do and modify them accordingly.

1. Scheduled_StopVM: Runs the ScheduledStopStart_Parent runbook with a parameter of Stop every day at the specified time. Automatically stops all VMs that meet the rules defined by variable assets. Enable the related schedule Scheduled-StartVM.
2. Scheduled_StartVM: Runs the ScheduledStopStart_Parent runbook with a parameter value of Start every day at the specified time. Automatically starts all VMs that meet the rules defined by variable assets. Enable the related schedule Scheduled-StopVM.
3. Sequenced-StopVM: Runs the Sequenced_StopStop_Parent runbook with a parameter value of Stop every Friday at the specified time. Sequentially (ascending) stops all VMs with a tag of SequenceStop defined by the appropriate variables. For more information on tag values and asset variables, see Runbooks. Enable the related schedule, Sequenced-StartVM.
4. Sequenced-StartVM: Runs the SequencedStopStart_Parent runbook with a parameter value of Start every Monday at the specified time. Sequentially (descending) starts all VMs with a tag of SequenceStart defined by the appropriate variables. For more information on tag values and variable assets, see Runbooks. Enable the related schedule, Sequenced-StopVM.

How to enable and configure Start/Stop VMs during Off-hours.

1. Search for and select Automation Accounts.
2. On the Automation Accounts page, select your Automation account from the list.
3. From the Automation account, select Start/Stop VM under Related Resources. From here, you can click Learn more about and enable the solution. If you already have the feature deployed, you can click Manage the solution and find it in the list.

1. On the Start/Stop VMs during off-hours page for the selected deployment, review the summary information and then click Create.

With the resource created, the Add Solution page appears. You're prompted to configure the feature before you can import it into your Automation account.

1. On the Add Solution page, select Workspace. Select an existing Log Analytics workspace from the list. If there isn't an Automation account in the same supported region as the workspace, you can create a new Automation account in the next step.

2. On the Add Solution page if there isn't an Automation account available in the supported region as the workspace, select Automation account. You can create a new Automation account to associate with it by selecting Create an Automation account, and on the Add Automation account page, provide the the name of the Automation account in the Name field.

All other options are automatically populated, based on the Log Analytics workspace selected. You can't modify these options. An Azure Run As account is the default authentication method for the runbooks included with the feature.

After you click OK, the configuration options are validated and the Automation account is created. You can track its progress under Notifications from the menu.

1. On the Add Solution page, select Configure parameters. The Parameters page appears.

1. Specify a value for the Target ResourceGroup Names field. The field defines group names that contain VMs for the feature to manage. You can enter more than one name and separate the names using commas (values are not case-sensitive). Using a wildcard is supported if you want to target VMs in all resource groups in the subscription. The values are stored in the External_Start_ResourceGroupNames and External_Stop_ResourceGroupNames variables.

The default value for Target ResourceGroup Names is a *. This setting targets all VMs in a subscription. If you don't want the feature to target all the VMs in your subscription, you must provide a list of resource group names before selecting a schedule.

• Specify a value for the VM Exclude List (string) field. This value is the name of one or more virtual machines from the target resource group. You can enter more than one name and separate the names using commas (values are not case-sensitive). Using a wildcard is supported. This value is stored in the External_ExcludeVMNames variable.

• Use the Schedule field to select a schedule for VM management by the feature. Select a start date and time for your schedule to create a recurring daily schedule starting at the chosen time. Selecting a different region is not available. To configure the schedule to your specific time zone after configuring the feature, see Modify the startup and shutdown schedules.

1. To receive email notifications from an action group, accept the default value of Yes in the Email notifications field, and provide a valid email address. If you select No but decide at a later date that you want to receive email notifications, you can update the action group that is created with valid email addresses separated by commas. The following alert rules are created in the subscription:

• AutoStop_VM_Child
• Scheduled_StartStop_Parent
• Sequenced_StartStop_Parent

1. After you have configured the initial settings required for the feature, click OK to close the Parameters page.

2. Click Create. After all settings are validated, the feature deploys to your subscription. This process can take several seconds to finish, and you can track its progress under Notifications from the menu.

Scenario 1: Start/Stop VMs on a schedule

This scenario is the default configuration when you first deploy Start/Stop VMs during off-hours. For example, you can configure the feature to stop all VMs across a subscription when you leave work in the evening, and start them in the morning when you are back in the office. When you configure the schedules Scheduled-StartVM and Scheduled-StopVM during deployment, they start and stop targeted VMs.

Configuring the feature to just stop VMs is supported. See Modify the startup and shutdown schedules to learn how to configure a custom schedule.

The time zone used by the feature is your current time zone when you configure the schedule time parameter. However, Azure Automation stores it in UTC format in Azure Automation. You don't have to do any time zone conversion, as this is handled during machine deployment.

To control the VMs that are in scope, configure the variables: External_Start_ResourceGroupNames, External_Stop_ResourceGroupNames, and External_ExcludeVMNames.

You can enable either targeting the action against a subscription and resource group, or targeting a specific list of VMs, but not both.

Target the start and stop action by VM list

1. Run the ScheduledStartStop_Parent runbook with ACTION set to start.

2. Add a comma-separated list of VMs (without spaces) in the VMList parameter field. An example list is vm1,vm2,vm3.

3. Set the WHATIF parameter field to True to preview your changes.

4. Configure the External_ExcludeVMNames variable with a comma-separated list of VMs (VM1,VM2,VM3), without spaces between comma-separated values.

This scenario does not honor the External_Start_ResourceGroupNames and External_Stop_ResourceGroupnames variables. For this scenario, you need to create your own Automation schedule. For details, see Schedule a runbook in Azure Automation.

Scenario 2: Start/Stop VMs in sequence by using tags

Target the start and stop actions against a subscription and resource group

1. Add a sequencestart and a sequencestop tag with positive integer values to VMs that are targeted in External_Start_ResourceGroupNames and External_Stop_ResourceGroupNames variables. The start and stop actions are performed in ascending order. To learn how to tag a VM, see Tag a Windows virtual machine in Azure and Tag a Linux virtual machine in Azure.

2. Modify the schedules Sequenced-StartVM and Sequenced-StopVM to the date and time that meet your requirements and enable the schedule.

3. Run the SequencedStartStop_Parent runbook with ACTION set to start and WHATIF set to True to preview your changes.

4. Preview the action and make any necessary changes before implementing against production VMs. When ready, manually execute the runbook with the parameter set to False, or let the Automation schedules Sequenced-StartVM and Sequenced-StopVM run automatically following your prescribed schedule.

Scenario 3: Start or stop automatically based on CPU utilization

Start/Stop VMs during off-hours can help manage the cost of running Azure Resource Manager and classic VMs in your subscription by evaluating machines that aren't used during non-peak periods, such as after hours, and automatically shutting them down if processor utilization is less than a specified percentage.

By default, the feature is pre-configured to evaluate the percentage CPU metric to see if average utilization is 5 percent or less. This scenario is controlled by the following variables and can be modified if the default values don't meet your requirements:

• External_AutoStop_MetricName
• External_AutoStop_Threshold
• External_AutoStop_TimeAggregationOperator
• External_AutoStop_TimeWindow
• External_AutoStop_Frequency
• External_AutoStop_Severity

You can enable and target the action against a subscription and resource group, or target a specific list of VMs.

When you run the AutoStop_CreateAlert_Parent runbook, it verifies that the targeted subscription, resource group(s), and VMs exist. If the VMs exist, the runbook calls the AutoStop_CreateAlert_Child runbook for each VM verified by the parent runbook. This child runbook:

• Creates a metric alert rule for each verified VM.
• Triggers the AutoStop_VM_Child runbook for a particular VM if the CPU drops below the configured threshold for the specified time interval.
• Attempts to stop the VM.

Target the autostop action against all VMs in a subscription

1. Ensure that the External_Stop_ResourceGroupNames variable is empty or set to * (wildcard).

2. [Optional] If you want to exclude some VMs from the autostop action, you can add a comma-separated list of VM names to the External_ExcludeVMNames variable.

3. Enable the Schedule_AutoStop_CreateAlert_Parent schedule to run to create the required Stop VM metric alert rules for all of the VMs in your subscription. Running this type of schedule lets you create new metric alert rules as new VMs are added to the subscription.

Target the autostop action against all VMs in a resource group or multiple resource groups

1. Add a comma-separated list of resource group names to the External_Stop_ResourceGroupNames variable.

2. If you want to exclude some of the VMs from the autostop, you can add a comma-separated list of VM names to the External_ExcludeVMNames variable.

3. Enable the Schedule_AutoStop_CreateAlert_Parent schedule to run to create the required Stop VM metric alert rules for all of the VMs in your resource groups. Running this operation on a schedule allows you to create new metric alert rules as new VMs are added to the resource group(s).

Target the autostop action to a list of VMs

1. Create a new schedule and link it to the AutoStop_CreateAlert_Parent runbook, adding a comma-separated list of VM names to the VMList parameter.

2. Optionally, if you want to exclude some VMs from the autostop action, you can add a comma-separated list of VM names (without spaces) to the External_ExcludeVMNames variable.

Configure email notifications

1. In the Azure portal, click on Alerts under Monitoring, then Manage actions. On the Manage actions page, make sure you're on the Action groups tab. Select the action group called StartStop_VM_Notification.

1. On the StartStop_VM_Notification page, the Basics section will be filled in for you and can't be edited, except for the Display name field. Edit the name, or accept the suggested name. In the Notifications section, click the pencil icon to edit the action details. This opens the Email/SMS message/Push/Voice pane. Update the email address and click OK to save your changes.

Add a VM

There are two ways to ensure that a VM is included when the feature runs:

1. Each of the parent runbooks of the feature has a VMList parameter. You can pass a comma-separated list of VM names (without spaces) to this parameter when scheduling the appropriate parent runbook for your situation, and these VMs will be included when the feature runs.

2. To select multiple VMs, set External_Start_ResourceGroupNames and External_Stop_ResourceGroupNames with the resource group names that contain the VMs you want to start or stop. You can also set the variables to a value of * to have the feature run against all resource groups in the subscription.

Exclude a VM

To exclude a VM from Stop/start VMs during off-hours, you can add its name to the External_ExcludeVMNames variable. This variable is a comma-separated list of specific VMs (without spaces) to exclude from the feature. This list is limited to 140 VMs. If you add more than 140 VMs to this list, VMs that are set to be excluded might be inadvertently started or stopped.

Modify the startup and shutdown schedules

Managing the startup and shutdown schedules in this feature follows the same steps as outlined in Schedule a runbook in Azure Automation. Separate schedules are required to start and stop VMs.

Configuring the feature to just stop VMs at a certain time is supported. In this scenario you just create a stop schedule and no corresponding start schedule.

1. Ensure that you've added the resource groups for the VMs to shut down in the External_Stop_ResourceGroupNames variable.

2. Create your own schedule for the time when you want to shut down the VMs.

3. Navigate to the ScheduledStartStop_Parent runbook and click Schedule. This allows you to select the schedule you created in the preceding step.

4. Select Parameters and run settings and set the ACTION field to Stop.

5. Select OK to save your changes.

Here a possibile solution:

First of all without the agent installed, you will not be able to collect any logs from within that machine. It's definitely possible to install the Log Analytics Agent (Will be replaced by the Azure Monitor Agent, that's currently in preview) on Scale Sets. You can get your dev team to do it but we've encountered a lot of issues with that.

We build images via pipelines and not all our images are rebuilt frequently and we noticed we started facing issues with the MMA certificate getting expired for some reason. We barely had time to investigate as Policies were already being rolled out.

The best practice to deploy MMA to Scale Sets is to use an Azure Policy - it also ensures compliance. Any machine built automatically gets it and you can be confident it will be installed. It will DeployIfNotExists. The two links below will redirect you to the Azure Policy in your own Azure Portal.

1. Windows VMSS Policy for Log Analytics Agent
2. Linux VMSS Policy for Log Analytics Agent

One thing you should be aware is that if the upgrade mode on your Scale Set is Manual instead of Rolling/Automatic then you'll need to manually upgrade them for the agent installation to take effect.