from #992:

The code in generate_manifest in the mirage tool should check that device names are unique and alphanumeric

from Solo5/solo5#372

NAME must be composed of alphanumeric characters only, and within 1..67 characters in length

Hi all,

Sorry if my questions look too simple but there still things I do not understand:

GPG keys:
Is there any GPG keys compatibility list? Is the Nitrokey U2F compatible with heads?
Is specificaly this key: https://docs.puri.sm/PureBoot/Heads.html compatible?
Is there any limitation or keys that are know not working with heads?

OTP apps:
Is there only google code app how

the primary instance conversion procedure in the evacuating node admin docs is ambiguous. it seems to say that, to evacuate a node, you first need to switch all the primary instances to their secondaries:

There are two steps of moving i

It becomes very complicated start to use and contribute to this project, because it lacks documentation, apparently referring to unit testing, as if it were an appropriate way to start, but they are not.

Maybe for beginners like me it is complicated, but the idea is that everyone can contribute, or at least try.

We will have to understand how radare2 debugger internals works to figure out how we should implement some specific features of r2vmi

I am brand new to xen server, terraform and go but eventually got it working. Here are my notes for getting this working with ubuntu 16.04, xen server 7.3 and terraform 0.11.3

a) Install the version of go that terraform depends on. As of 0.11.3, terraform depends on go 1.10, ubuntu includes an older version. Updating ubuntu to the correct version requires several steps described here: https:

The help for xen-create-image states that multiple space separated nameservers are allowed. However the checkOption sub, called by parseCommandLineArguments, validates the value as a single ipv4.

# xen-create-image --verbose \
>   --hostname=crow \
>   --mac=00:16:3e:00:00:25 \
>   --ip=192.168.18.202 \
>   --netmask=255.255.255.0 \
>   --gateway=192.168.18.255 \
>   --nameserver="1

A good testing regime could include the following:

• Perform an initial backup
• Verify volume
• Perform an incremental backup
• Verify volume
• Prune first backup
• Verify volume
• Diff volume (cross-check with source vol data)

Changing program_name in the code could allow the test data set to be created under a different base folder name without interfering with real-life back

Would be nice to have an option to specify disk description in the terraform script.
Something like:

resource "xenorchestra_vm" "vm1" {
...
 disk {
    sr_id      = "111111111-22222-333-444-555555555"
    name_label = var.vm_name
    name_description = "MY DISK DESCRIPTION"
    size = 21474836480
  }
}

Thank you.