Mercurial > ~samis > hgweb.cgi > blag

comparison posts/Propellor_and_Pi.md @ 7:7aaa5b28857f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add nice/useful links to post
author Samuel Hodgkins <samuel.hodgkins@sky.com>
date Fri, 01 Sep 2017 02:15:36 +0100
parents a2460c562582
children 212b64ea9488
comparison
equal deleted inserted replaced
6:a2460c562582 7:7aaa5b28857f
1 [[!meta title="Propellor and a Raspberry Pi 3" author="samis"]] 1 [[!meta title="Propellor and a Raspberry Pi 3" author="samis"]]
2 [[!tag tech linux]] 2 [[!tag tech linux]]
3 I've given a number of configuration management tools a whirl - Puppet, Chef, Salt, Ansible. 3 I've given a number of configuration management tools a whirl - Puppet, Chef, Salt, Ansible.
4 Chef and Puppet started nice, but seemed complex to use given my small needs. 4 Chef and Puppet started nice, but seemed complex to use given my small needs.
5 Salt and Ansible had potential and features unique to either, but I've never liked using YAML syntax, and this showed. 5 Salt and Ansible had potential and features unique to either, but I've never liked using YAML syntax, and this showed.
6 6
13 4. Unlike with Chef or Puppet, there was no fancy layered complexity of the tool itself. No fancy 'structures' like Librarian, R10K and Berkshelf for Chef. No large servers requiring gigabytes of RAM all the time. 13 4. Unlike with Chef or Puppet, there was no fancy layered complexity of the tool itself. No fancy 'structures' like Librarian, R10K and Berkshelf for Chef. No large servers requiring gigabytes of RAM all the time.
14 14
15 I got started, there were and remain some niggles and quirks on the road - for example my VPS needed special bootstrapping attention (interestingly the problem was fixed upstream the same day I worked around it) 15 I got started, there were and remain some niggles and quirks on the road - for example my VPS needed special bootstrapping attention (interestingly the problem was fixed upstream the same day I worked around it)
16 Soon enough two of three boxen of interest had a no-op configuration applied, indicating that the program was working correctly for future usage. But what happened to that third one? It's a long story. 16 Soon enough two of three boxen of interest had a no-op configuration applied, indicating that the program was working correctly for future usage. But what happened to that third one? It's a long story.
17 17
18 This third box was a Raspberry Pi 3 running [Arch Linux ARM](https://archlinuxarm.org/). 18 This third box was my [Raspberry Pi 3](https://cdn.shopify.com/s/files/1/0174/1800/products/Rainbow_1_of_3_47e94e82-ba3a-4804-a280-3140109cd304_1024x1024.jpg?v=1456669057) running [Arch Linux ARM](https://archlinuxarm.org/).
19 19
20 # My attempts 20 # My attempts
21 21
22 First I tried just installing GHC. Didn't work, linking errors (later I found there were missing static libraries) 22 First I tried just installing GHC. Didn't work, linking errors (later I found there were missing static libraries)
23 Then I tried to get a known-good compiler via Stack...before realizing it didn't have ARM binaries. It also didn't work well with the previously mentioned compiler. 23 Then I tried to get a known-good compiler via Stack...before realizing it didn't have ARM binaries. It also didn't work well with the previously mentioned compiler.