Keybase proof
I hereby claim:
- I am mildred on github.
- I am mildred (https://keybase.io/mildred) on keybase.
- I have a public key ASDQFes07Yd_g56-PPV853GxC2dKwU5YV7NzWmXJ8ddP_Qo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
CPU0 CPU1 CPU2 CPU3 | |
0: 10 0 0 0 IO-APIC 2-edge timer | |
8: 1 0 0 0 IO-APIC 8-edge rtc0 | |
9: 0 1613 0 0 IO-APIC 9-fasteoi acpi | |
29: 0 0 0 311 IO-APIC 29-fasteoi intel_sst_driver | |
32: 0 0 103 0 IO-APIC 32-fasteoi 808622C1:00 | |
33: 0 0 0 248 IO-APIC 33-fasteoi 808622C1:01 | |
37: 1709051 0 0 0 IO-APIC 37-fasteoi 808622C1:05 | |
41: 0 0 0 0 IO-APIC 41-fasteoi 8086228E:00 | |
42: 0 0 0 0 IO-APIC 42-fasteoi dw:dmac-1 |
Scenarios
2018/05/11 09:38:45 [INFO] Terraform version: 0.11.7 41e50bd32a8825a84535e353c3674af8ce799161 | |
2018/05/11 09:38:45 [INFO] Go runtime version: go1.10.1 | |
2018/05/11 09:38:45 [INFO] CLI args: []string{"/home/mildred/Work/SquareScale/squarescale-infrastructure/bin/terraform-0.11.7", "destroy", "-force"} | |
2018/05/11 09:38:45 [DEBUG] Attempting to open CLI config file: /home/mildred/.terraformrc | |
2018/05/11 09:38:45 [DEBUG] File doesn't exist, but doesn't need to. Ignoring. | |
2018/05/11 09:38:45 [INFO] CLI command args: []string{"destroy", "-force"} | |
2018/05/11 09:38:45 [INFO] command: empty terraform config, returning nil | |
2018/05/11 09:38:45 [DEBUG] command: no data state file found for backend config | |
2018/05/11 09:38:45 [DEBUG] New state was assigned lineage "596ea3fc-e5a8-78b7-c0cd-5ee21f559817" | |
2018/05/11 09:38:45 [INFO] command: backend initialized: <nil> |
Components:
Operation:
Rationale:
ostree-rpm
Put this in your PATH
. Requires git-hub
[m[4;2H+----------------------------------------------------------------------------+[5;2H|[5;79H|[6;2H|[6;79H|[7;2H|[7;79H|[8;2H|[8;79H|[9;2H|[9;79H|[10;2H|[10;79H|[11;2H|[11;79H|[12;2H|[12;79H|[13;2H|[13;79H|[14;2H|[14;79H|[15;2H|[15;79H|[16;2H|[16;79H|[17;2H+----------------------------------------------------------------------------+[m[18;2H[19;2H[m Use the ^ and v keys to select which entry is highlighted. | |
Press enter to boot the selected OS, `e' to edit the commands | |
before booting or `c' for a command-line. [5;80H [7m[5;3H*CoreOS default [m[5;78H[m[m[6;3H CoreOS USR-A [m[6;78H[m[m[7;3H CoreOS USR-B [m[7;78H[m[m[8;3H [m[8;78H[m[m[9;3H |
A namespace is a collection of nomad jobs in the same directory. Sub-directories are sub-namespaces. When instanciated, a namespace is allocated an identifier (8 character unique ID). Before being inserted in nomad, the jobs are modified to include this namespace identifier:
sub-namespaces are also inserted in the system when their parent namespace is inserted. Each sub-namespace is given an identifier the same way. The parent namespace is instanciated with:
TL;DR code linters may be beneficial but may also cause problems. Basically:
Code is complex when understanding what it does, reading it, becomes complex. Thus it depends on how people are reading the code. One thing that makes code complex is when you have to browse to different locations/files when reading the code. Another thing that makes reading difficult is when code is not well organized and you struggle to find a piece of code.