Home / user-429373

Sam's questions

Martin Hope
Sam
Asked: 2021-04-17 02:55:54 +0800 CST
  • -1

My Friday brain is really struggling to convert an Ansible command line into the format my Packer .json wants. The Ansible:

ansible-playbook playbook.yml -e @env/users/user01.yml --ask-vault --ask-become

My attempted Packer block:

  "provisioners": [
    {
      "ansible_env_vars": ["ANSIBLE_HOST_KEY_CHECKING=False"],
      "playbook_file": "{{ template_dir }}/../path/playbook.yml",
      "type": "ansible",
      "user": "{{ user `ssh_username` }}",
      "extra_arguments": ["--extra-vars", "@env", "../path/env/users/user01.yml", "desktop=false", "--vault-password-file", "../vaultpass"]
    }
  ],

I've tried various combinations of key=value (like the docs say) instead of separate "thing", blocks but then it looks like Ansible is trying to read everything as one big argument for --extra-vars (whereas at least --vault-password-file should be separate I think?).

ansible ansible-playbook packer
Martin Hope
Sam
Asked: 2020-06-30 01:03:02 +0800 CST
  • 0

I'm currently backing up Azure VMs via Azure CLI:

create resource group:

az group create -n backup-resource-group -l uksouth

create recovery services vault:

az backup vault create --resource-group backup-resource-group --name backup --location uksouth

loop VMs to create backup jobs:

az backup protection enable-for-vm --resource-group backup-resource-group --vault-name backup --vm $(az vm show -g servers-resource-group -n {{ loopedoutvm }} --query id | tr -d '"') --policy-name DefaultPolicy

This works fine, but only backs up VMs in the same Azure region. I'd like to adjust this to store the backups in a different region (in addition to the same region the VMs run in). If I run this again with a new resource group and vault created in a different region, Azure returns a message that recovery service vaults can only contain VMs from that location.

Which is strange, because in the Azure portal, it seems I can replicate VM backups to other regions (either via: some VM > disaster recovery > advanced, or via: some recovery services vault > replicate). But I don't know how to achieve this (or something similar) via Azure CLI in order to automate it. There doesn't seem to be anything in Microsoft's documentation for doing this with CLI.

If anyone could point me in the right direction it would be hugely appreciated.

backup disaster-recovery azure azure-backup recovery-services
Martin Hope
Sam
Asked: 2019-10-02 01:05:50 +0800 CST
  • 2

I used Prometheus and node exporter a while ago and had access to node_filesystem_* metrics to monitor disk usage but I've recently fired it up on some other servers (Ubuntu Linux) and those metrics seem to be missing.

According to this https://github.com/prometheus/node_exporter those metrics should be enabled by default and available from Linux hosts. What might be causing them to not appear?

To clarify, I can get metrics for CPU, memory etc so it's not that node exporter just isn't working.

monitoring
Martin Hope
Sam
Asked: 2018-07-20 05:28:39 +0800 CST
  • 1

I have an HP Microserver running ESXi 6.5 from a USB stick. A series of power outages seems to have caused some corruption, preventing ESXi from booting (pink screen, unable to load kernel modules).

The VMs reside on a mirrored pair of HDDs so should hopefully still be intact and healthy.

I've done a fresh install of ESXi on a new stick and was wondering if it's possible to point ESXi to the VMs sitting on the drive array so it can manage them again?

vmware-esxi
Martin Hope
Sam
Asked: 2018-07-19 23:40:58 +0800 CST
  • 1

I have an HP Microserver running ESXi 6.5 from a USB stick. A series of power outages seems to have caused some corruption, preventing ESXi from booting (pink screen, unable to load kernel modules).

I'd like to plug the USB stick into my Linux PC and extract the config to import into a fresh install of ESXi on a new USB stick, but I'm not seeing any promising candidates for configuration files.

I was under the impression that a working ESXi install will keep the necessary configuration stored in /etc but I'm not seeing a traditional Linux-looking file system on any of the three partitions that mount when I plug in the stick.

Gparted shows two 'unknown filesystem' partitions - might those contain /etc or whatever it is I need? Would additional drivers be required to see those partitions (assuming they do contain what I need)?

backup