Initial code developed with raspbian jessie lite. Should also work with full desktop image, probably turn off desktop by default.

Notice: /Stage[main]/Maverick-baremetal::Raspberry/Exec[raspberry-devicetree]/returns: executed successfully
Notice: /Stage[main]/Maverick-baremetal::Raspberry/Exec[raspberry-serial]/returns: executed successfully
Notice: /Stage[main]/Maverick-baremetal::Raspberry/Exec[raspberry-disableconfig]/returns: executed successfully
Notice: /Stage[main]/Maverick-baremetal::Raspberry/Exec[raspberry-i2c]/returns: executed successfully
Notice: /Stage[main]/Maverick-baremetal::Raspberry/Exec[raspberry-spi]/returns: executed successfully

These should only run once, logic for exec unless/onlyif should be better

Ensure base system setup works, deal with hardware setup separately.

Reboot needed at end of bootstrap run, add a message as a reminder/clarity.

rume.sh should check for arguments and print usage if none, or on --help

Project will be easier to manage if self contained. /srv/maverick is as good a place as any.

Add logic to runme.sh to install puppet package if it doesn't already exist.

http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD
https://gist.github.com/treeherder/34830497fa90c1b5eaea

Should this be for dev environment only? Perhaps if set it can't hurt to configure for all environments.

These use huge amounts of memory and don't need to run continuously

Currently mav user is allowed passwordless sudo access to root. This is convenient, but insecure, so we should at least have a parameter that disables this.

Warning: Firewall100 allow cloud9 access from : Unable to persist firewall rules: Execution of '/usr/sbin/service iptables-persistent save' returned 1: iptables-persistent: unrecognized service

Add a camera config parameter and logic to raspberry class, for automated setup.

raspi-config not installed by default on all raspberry OS (ubuntu mate).

Firewall rules are sprinkled throughout the code which is correct, but they should only activate if the maverick-security class, more specifically maverick-security::firewall class is included, which it isn't by default.

There is already a defaults.json, this is better called something like 'config.json' or 'local.json'.

At least on original BBB with only 2Gb eMMC storage there isn't enough space for dev stack, so we should fail the run if /srv/maverick isn't mounted on SD storage.

Currently raspberry config will turn on various config actions but not turn off. Must do both.

If maverick already run in non-bootstrap mode, extract environment and use as default instead of having to specify --env each time.

If interfaces set to static dhcp should not interfere, also with interfaces such as can0/can1 on beagle.

Firewall rules loaded on first puppet run, should be run on boot instead

Rewrite /etc/issue with a more friendly message. On beagle debian for example it shows default username/password:

Debian GNU/Linux 8

BeagleBoard.org Debian Image 2016-01-24

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

default username:password is [debian:temppwd]

While it is possible to run puppet as non-root user, there are so many things that need root that we might as well have root as requirement, for now.

hostname/fqdn declared in node manifests or determined in hostname fact not being set permanently.

Add basic AP wifi configuration for wlan0, start with SSID and passphrase in defaults.json (or possibly another hiera file that is .gitignored)

So classes can be automatically included/excluded based on hardware platform

In bootstrap mode, don't set production as the environment, only do base actions. Move other classes into production defaults.json.

Add parameter and logic to raspberry hardware setup to configure GL

Add an environment that just deals with basic system setup rather than full software/fc setup. This is so that basic hardware like sd card expansion has a chance to happen and a reboot occur before full setup happens (that would otherwise fail due to lack of space etc).

Ssl stuff currently being written to maverick-puppet/conf/ssl, nothing should get written to maverick-puppet, it should go to $vardir which is /var/lib/puppet by default.

Clone into /srv/maverick/software

Currently unuseable on Model a+

Really irritating at 1hr

Check for puppet environment, if not set then bail out. Also probably add a confirm parameter as this script has the potential to do all sorts of badness to those who aren't familiar with it. Use getopts.

Disabling / removing connman destroys networking state. Need to find a workaround.

These chinese LCD screens come with complete (outdated) customised images to support the screens and are hard to configure outside of the images. Puppetise the steps.

init file self deletes, need a more permanent marker