add a staging environment profile
change how oracle java is handled... something changed upstream, and the install has been failing.
git added the new meta file
fix to asgard context path
change to the JETTY_BASE before launching, should resolve relative path issues in things like log4j configs
some fixes to Asgard for #17
add export to the *_HOME vars being set
note with the concept for the new virtual base
base is now base_buri, and a new "virtual" base role assembles a base from it, options like java, and possibly future local hooks (although it may need to be pushed to the top level play from initial tests). Is the better solution #40 was looking for, cleaner, and more extensible.
if a folder "roles_local" exists in the BURI_BASE, buri will tell ansible to add it as a roles folder, allowing additional roles to be merged into the plays
add new roles_local folder to gitignore
buri detects a base_local if there is a roles_local, and does the signalling needed for doing #39 final goal. nothing activates on it yet
default asgard to 1.5
not going to try to make local_base hide in the base... will be explicitly a 4-layer process to use a local foundation->base_buri->base_local->role, so taking out some of the signals
give virtual base a defaults file, resnap demands it for now.
dont do the image build exclude inside virtual base, that will happen higher up if needed. was throwing off resnaps
initial work on #32, to support flat disk images (no partitions)
small tweaks/cleanups, only funcitonal difference is setting root devicename to sda1 for device mappings for pvm/ebs (seems right, may have to unwind)
get the rootfs label right, dont "fix" grub on flat images
attempt to use extlinux to get though the hvm boot issue on flat image