Tag: Devel

A Basic Template This first section on this page doesn’t add new elements to the script code, but implements a more complex template. Since this is user-supplied data, this is more of template example than a code update.

Overview Same configuration and userdata files as before Improved ’look’ of the code (applied code formatter) Some minor improvements to messages (output) Most importantly, created the get_named_resource function for common tasks like checking for the existence of an image (or other resource) and returning the matching image object (a munch.

Setup the Packer Environment Prequisites The packer executable found in the download for your system at https://www.packer.io/ (Download button) needs to be in a directory that is in your PATH.

Setup the Packer Environment Prequisites The packer executable found in the download for your system at https://www.packer.io (Download button) needs to be in a directory that is in your PATH.

Implementation We now add an important piece: write_files support. In this implementation we: Take a colon separated list of local directory names For each directory we process every file in the directory (last directory wins in the case of duplicates) Processing each file means: We determine the target path the for the file by stripping the passed in directory name (so passed/in/dir/etc/aliases becomes /etc/aliases) We read the file If possible we ‘gzip’ (compress) it We base64 encode it (this avoids problems with characters in the file being interpreted by cloud-init as having meaning other than being just data; for example it avoids quoting and whitespace issues).

Preface You’ll notice that the basic-instance.ini config file has two sections with erroneous server_groups. This was done to provide a quite test of the new script’s error-handling.

Option 1: Use the Image Directly (not recommended) Upload packer image using virsh ls -al *.qcow2 virsh -c qemu+ssh://user@host/system vol-upload --pool default --vol preseeded-armhf-uefi-image-preseed-image-xxxx-xx-xx-xx-xx.qcow2 --file preseeded-armhf-uefi-image-preseed-image-xxxx-xx-xx-xx-xx.

Preface Our next phase was adding the configuration items we still needed, along with some enhancements on progress and error reporting. This is by no means a ‘product’, but it’s sufficient at this point (with the addition of userdata handling) for our small ‘cloud’ infrastructure.

About a month ago I made a change to the website layouts that broke the RSS (news) feeds. This is now fixed.

Hugo module for gathering metadata, and adding metadata and microformats to HTML (‘head’ and elsewhere)

Hugo module for creating minimal test cases to demonstrate Hugo issues

Hugo module for debugging theme and site issues (debug tables)

Convert from WordPress XML export to static site generator (Hugo)

Daniel has added a new page for a site metadata module and fixed site metadata

Developing for ARM-based hardware

It seems I’m doing more front-end web work than is ideal these days. I say that because I tend to prefer technical aspects of web development…

I will add more information later, but I have created a theme (Hugo Minimal Test Theme) which is designed to make it easy to add in minimal changes to create samples of problems that crop up, using a less complex theme than a full-blown one when developing with Hugo.

I’ve ended up doing some frontend web design after all, and have also enjoyed working with the Hugo static website generator.

Tools Used For this demonstration we show the use of Visual Studio Code We also use GitHub And Netlify Before Website screenshot of website before pushing commit

Overview Git is used extensively worldwide for many type of software and internet and other types of publishing projects (among others). This article provides an introduction to Git and probably the most popular central git repository (GitHub).

Preface This method of compiling for armel (e.g. ARMv5, earlier, and some ARMv6) which uses pbuilder in an ARM HardFloat VM is not recommended as it is extremely slow (because of running in a emulated VM, not because of using pbuilder).

Create an UEFI (newish) ARM Hard Float (32-bit) virtual machine for Libvirt/KVM using automated image build using Packer.

Preface Whether you want old school ARM (32-bit) or a shiny new UEFI ARM (32-bit) virtual machine in Libvirt/KVM, and automated or ‘manual’ creation, there is a way to get what you want.

NB These instructions are out of date since the release of Debian 11 (Bullseye). Some parts of these guide will need to be updated to the new Debian release.

Option 1: Use the Image Directly (not recommended) Upload kernel, initrd, and packer image using virsh ls -al vmlinuz* initrd.gz* *.qcow2 virsh -c qemu+ssh://user@host/system vol-create-as --pool default --name vmlinuz-x.

NB These instructions are out of date since the release of Debian 11 (Bullseye). Some parts of these guide will need to be updated to the new Debian release.

NB These instructions are out of date since the release of Debian 11 (Bullseye). Some parts of these guide will need to be updated to the new Debian release.

Preface Unless you have a new, high-powered, ARM system with which to build, the fastest and most practical way to build software for armel (early ARM CPU versions) is to cross-compile on an x86_64 machine (Debian and offshoots call this the amd64 architecture, even for non-AMD CPUs).

ARCHIVED This document is archived and may be out of date or inaccurate. NOTICE WARNING You could brick (render unusable and unrecoverable) your device while attempting to follow these instructions.

Overview The cross-compilation toolchains builtin to most modern Linux distributions do not support older versions of GCC. For old kernels (and other software) that require GCC4 or lower for building, this poses a challenge.

ARCHIVED This document is archived and may be out of date or inaccurate. Overview Around 2011 Android devices based on the WonderMedia 8xxx-series SoC (ARM v5) were being sold as netbooks.

Using a Hugo module starter and Netlify for Hugo module development

Hugo theme module for demo sites for hugo modules

ARCHIVED This collection of pages is archived and may contain out-of-date or no longer accurate information. Overview Learning experiments in using bespoke code & data under version control to consistently deploy virtual and bare metal hosts and the applications on them.

Preface Before finding the source of the issues with Terraform on OVH, a possible source of the dysfunction was thought to be with expired tokens. As such a couple of cross-platform token generation scripts using the Python bindings for the OVH API were tried.

Preface The OpenStack SDK is a OpenStack project aimed at providing a complete software development kit for the programs which make up the OpenStack community. It is a Python library with corresponding documentation, examples, and tools released under the Apache 2 license.

Preface Code The scripts described on this page are available in a Git repo @ https://github.com/danielfdickinson/ivc-in-the-wtg-experiments. First, Just a Template We start with a separate script that only generates userdata (no instance creation).

Preface Adding templating with the ability to add files to the instance and to run scripts during the instance deployment will get us most of the way to a complete solution for our needs, so that’s what this page is about.

Preface Some Thoughts At this point we should think about what is required to meet our Target Requirements. We’re going to put off a number of considerations as they depend on robust use of ‘userdata’ as we will be exploring the use of Jinja to template userdata later in the series.

Preface The Plan This page was intended to complete the OpenStack SDK with templated userdata portion of this Infrastructure Via Code set. This involves: Adding runcmd and bootcmd sections to userdata-default.

ARCHIVED: This page is archived and may contain information that is out-of-date or no longer accurate. Especially if you are older, have dirty or inadequate glasses, are just tired, or are using a small screen, you may have noticed that many sites use an excessively small font and that, worse, if you zoom the page, that the formatting of site ‘goes all to pieces’.

REMOVED Fork of Rpi-Distro/pi-gen WARNING: Due to https://bugs.launchpad.net/qemu/+bug/1805913 images built on non-arm hosts are broken! As I am, once again, late to the party and there are sufficient projects for most needs (and I have enough other things to work on) I am abandoning this fork.

REMOVED Project Plainfuse was a fork of Fuse.js (fuzzy search) by Kiro Risk due to concerns I had with difficulties auditing the minified Javascript (which at the time was the only output version available), combined with a desire for ES5 / IE11 support, which was not present at the time.

ARCHIVED This document is archived and may be out of date or inaccurate. Check the Debian Wiki first Before reading this page you should try looking at the DebianCustomCD Page on the Debian Wiki because it is updated more frequently, and by more contributors.