Create an azure virtual machine as a node of rundeck - azure-devops

I want to use an azure virtual machine as a node of Rundeck, but I don't have any idea what does access key means in the following settings when I want to add a new node on Rundeck:
Can anyone explain what the access key is in the Azure virtual machine world?
Thanks!

Related

The agent request is not running because all potential agents are running other requests

We are running a pipeline that has run successfully for ages. It is failing as of yesterday. We are getting the error
The agent request is not running because all potential agents are running other requests.
The agent pool is offline
This stackoverflow solution says I need to run.cmd, but I am not running a self-hosting agent.
We also get this additional error
Failed to get scaleset from Azure with error: No service Endpoint found with Id: xxxx and Scope xxxx
How do I bring the agent back online and is that the solution to fix the error that is preventing the publish/deploy. If not, how do we fix this issue.
There are three kinds of icon of agent pool in Azure DevOps.
Microsoft-hosted agent:
Self-hosted agent:
VMSS(Azure Virtual Machine Scale Set):
So the type you are using is VMSS(Azure Virtual Machine Scale Set) pool. This type of agent pool will based on service connection of one of your project or subscription.
So if the machines are in the VMSS, you can try to edit your VMSS pool settings on Azure DevOps side, you can set up another service connection(please make sure the related register app on azure portal side has required permissions to the VMSS).
If no machine instances or the previous instances were been deleted, then the object on DevOps side will not be able to recovery. You can rec-config to a new VMSS or delete the old pool and create a new one.

Configure azure VM using terraform and ansible using azure cli and without ssh keys in azure pipelines

I'm using Azure Pipelines with terraform to create a dynamic infrastructure (unknown number of VMs, NIC..) in Azure.
I also tried to use Ansible in a separate stage to configure my VM, but I can't because the work is complicated because I had to create ssh keys and use them by Ansible, so I want to configure my Azure VM without using SSHAkey and use Azure CLI instead, I know that Ansible is agentless and use SSH to communicate with VM but I hope there is a module which allows us to configure VM using Azure CLI?
Alternatively, if anyone already has an existing project like this one and is well organised & less work, I would be grateful.

RunDeck can it be used in an Airgap environment

I have an Airgap environment and would like to know if it will work without internet access. The systems I have can't reach the outside of the enclave.
Rundeck doesn't need internet access, you can deploy a Rundeck instance in a server on your local network and dispatch commands and jobs to your "LAN" remote nodes.

Getting a VZVirtualMachine for a running virtualmachine

I would like to write a thin wrapper around the Virtualization framework that offers docker style commands to start and stop virtual machines. One hurdle I found is the inability to create VZVirtualMachineConfiguration and VZVirtualMachine that refers to an already running machine.
So, if I want to use my cli tool like this:
# creates VZVirtualMachineConfiguration, VZVirtualMachine, starts VM and detaches process
vm-cli run --assorted-vm-parameters
vm-cli stop
# recreate VZVirtualMachineConfiguration with same hardwareidentifier,
# macmachineidentifier and VZVirtualMachine now refer to new virtual machine that is stopped
Is there a way to control a virtual machine of antoher process without having to write a daemon that maintains a list of created virtual machines?

Provision new azure VM based on Image backup

I have created the Azure VM and taken successfully the backup of disk using powershell. Now i need to create another VM using that disk?
How to proceed with that. Also i wanted to do same using image also. My main goal is to take backup of vm using either disk or image and then able to create new VMs using those backups or update the existing vm using those backups
The process you need to follow is covered here:
http://blogs.msdn.com/b/amol/archive/2014/03/21/how-to-migrate-windows-azure-vm-from-one-region-to-another.aspx
Note that if you don't "sysprep" the source VM when you attempt to provision a new VM based on the VHD of the source VM it will provision but the Azure management portal will show Running (provisioning) for the host.