…networking, I suggest you either use static IPs (and keep track of them in a sheet) or DHCP. I prefer static IPs though since that makes configuration (e.g. of an application to connect to the database) easier.
It also doesn't hurt to assign names, so you know which VM you're dealing with when GUI is enabled: db_config.vm.customize [ "modifyvm", :id, "--name", "DB", ]
Hardware
It doesn't hurt to have lots of CPU and RAM, …
…IP address the Raspberry Pi got (likely the first available address in your DHCP range), you can always check your router's DHCP table which should list all IP addresses it assigned, usually together with a host name.
While there, you could also assign a permanent IP address (still assigned via DHCP) by binding a MAC address to a reserved IP in your router's DHCP server setup. This makes it easier later on.
You could also assign a permanent DNS name (like pi.yourdomain.com) …
For many weekends (5?) over the past couple years I've spent hours trying to get my Zyxel NBG-419N to work in " Router Mode" instead of " Access Point Mode" when operating behind our (old) DSL modem, the Actiontec M1000. From juggling DHCP settings, to NAT-enabled settings, to Transparent Bridging, to attempting to configure PPPoE authentication and [...]
…as mentioned, connects to your Ethernet and grabs its IP address from DHCP. Any of the players you deploy just need to be paired with the press of a button, which is only a problem in really large mansions, as it has to happen on both devices within 2 minutes of each other.
At this point, you need to feed it some music, which basically means installing their Mac or Windows software on a machine with some sort of music on it, which, in my case, was the aforementioned studio Mac Pro …
…happened recently when we moved house and put our file server on a separate subnet that's not DHCP serviced.
I scratched my head for a little while on how to solve this. The obvious solution is to shorten the DHCP lease range and put the file server on the same subnet as the Boxee machine, but I'm cautious of what other CIFS bugs lurk beneath the surface, and it feels vastly more complicated than it should be.
The simplest solution I could find was to pass off handling CIFS…
…via the "needs creating" endpoint. As part of the PXE infrastructure, we ran DHCP with a configuration generated from the MAC to IP mappings maintained by the migration service. This allowed us to link requests from an IP to the to-be-configured VM.
When PXE booting, the VMs needed something to boot. Our legacy Xen hosts booted via PXE. For that, we modified this script . Further adapting it to suit our needs was easy. You can see the script we used here …
…into templating, and slowly built up the system with components covering file and printer sharing, DHCP + DNS in a DDNS setup, and LDAP replication and authentication.
One of the best outcomes of the exercise is that they now have a bunch of modular components for building servers and services outside the sphere of the original desktop + POS requirements. This is a tremendous boon for Kennards - by using Puppet they're making a long-term investment in the knowledge and implementation …
Dhcp was a breeze to set up with the ISC DHCP3 server. /etc/dhcp3/dhcpd.conf looks something like this: log-facility local7;
option domain-name-servers 10.0.0.9;
default-lease-time 3600; max-lease-time 7200;
subnet 10.0.0.0 netmask 255.255.255.0 { range 10.0.0.200 10.0.0.210; option routers 10.0.0.1; allow booting; allow bootp;
}
host macboot { filename "yaboot"; next-server 10.0.0.5; hardware ethernet DE:CA:FF:C0:FF:EE; fixed-address 10.0.0.201; …