Hey John-Paul,
I can clarify the installation process for you:
When you want to set up an admin node on a virtual machine, you can put the ISO
in the DVD drive of the VM and boot directly from the ISO. This results in the
OS being installed on the admin node VM. The next step is to:
sudo /tftpboot/ubuntu_dvd/extra/install <dnsName>
I use this method all the time when developing.
When installing an admin node on actual hardware though, the above method won't
work. Instead, you install vmWare Player on a laptop, add the Crowbar
installer VM image into vmWare Player, them put the ISO into the DVD drive of
the Crowbar installer VM. Next connect a network cable from the laptop to the
box that you want to turn into an admin node (note the cable will probably need
to be a crossover cable), turn on the box, and make it network boot. The
Crowbar installer VM is a little PXE boot server, and its sole purpose is to
serve up the ISO to the network booting box.
Once the OS has been installed on the hardware, ssh into it, and sudo
/tftpboot/ubuntu_dvd/extra/install <dnsName> as above to complete the
installation.
Using this method will allow you to bootstrap a hardware admin node.
Hope this helps!
Chris
Dell
-----Original Message-----
From: crowbar-bounces On Behalf Of John-Paul Robinson
Sent: Tuesday, August 27, 2013 11:08 AM
To: crowbar
Subject: Re: [Crowbar] crowbar 1.6 mesa iso in virtualbox
Thanks for the feedback.
It appears there were two problems that instigated my post:
1. confusion on how the crowbar admin node gets installed 2. a bug during the
admin node install that causes the reboot to fail
On item 1, the wiki instructions suggested that the admin node gets installed
by attaching a laptop-hosted VM to the admin node and PXE
booting the physical admin node off this VM. I was attempting to use
the crowbar iso image to create that laptop-hosted installer VM.
It appears, however, that the admin node is directly created by booting from
the crowbar iso image. So, I actually had an imaged Crowbar admin node in my
VM after booting from this iso.
On item 2, the problem with the console coming up after the ISO install
completes and the VM reboots appears to be a bug during the install of the ISO.
The apparmor package looks like it's not installing successfully during the iso
boot+install which results in a missing /lib/apparmor/functions file. When the
admin node reboots after the install, the missing file aborts the boot process
and leaves the admin node inaccessible (blank console and no SSH access).
I've documented a work around, where I attach the installed image to a CentOS
live image, chroot to the mounted subsystem, and reinstall apparmor manually
https://dev.uabgrid.uab.edu/ticket/227#comment:2
This is workaround is fine for me, at least during dev.
I am a little confused on item one about the difference of the documented
install process. If the booting of the ISO now causes the admin node to get
installed, that suggests I'll need an external boot device (cdrom or usb)
attached to my physical admin node instead of the documented laptop-hosted VM
from which the admin node PXE boots.
Is this interpretation of a new approach to the admin node install correct?
Any thoughts on why I'm hitting an apparmor install problem during the iso
install?
Thanks,
~jpr
On 08/26/2013 01:32 PM, wayne_al...@dell.com wrote:
> John-Paul,
>
> This is common in a virtual box install. I'm don't know why the
> console is unavailable. I ssh to the node and run the install script
> remotely (/opt/dell/bin/install-crowbar admin.whatever.org)
>
> I configure my vm admin node to have 8 Gig of mem, two processors, and 24 Gig
> storage.
>
> Hope this helps...
>
> Wayne
>
>
> -----Original Message-----
> From: crowbar-bounces On Behalf Of John-Paul Robinson
> Sent: Wednesday, August 21, 2013 9:41 AM
> To: crowbar
> Subject: [Crowbar] crowbar 1.6 mesa iso in virtualbox
>
> Hello
>
> In preparation for upgrading our physical servers from Essex to
> Grizzly, I'm trying to test the crowbar 1.6 iso
> (crowbar-mesa-1.6_openstack-os-build.3508.dev.iso) in a VirtualBox
> environment to build an admin node and test a simple compute/storage node
> config.
>
> I've created a 1GB VM (called crowbar-iso) attached to an internal network
> and seem to be able to successfully boot the ISO. It goes through an
> automatic install process that appears to image the VM ending with a somewhat
> length "preseed" install step. That's the last thing I can observe the VM
> doing.
>
> After this step the VM console turns to black and I expect the login prompt
> from step 11 of
> http://crowbar.github.io/docs/getting-started/install-admin-node.html to show
> up. The console stays dark though.
>
> I've attempted to restart the VM and it seems to boot from the disk, without
> the crowbar iso attached. At least, there is no error about not finding an
> OS. From what I can tell, this is a CentOS image but I can't seem to
> "access" it any way like alt consoles or such.
>
> Should I expect this iso to be functional? Is there some system requirement
> that would prevent the login prompt from appearing, like a min ram?
>
> My goal is to get the crowbar-iso VM operational and the attach my
> crowbar-admin VM to the same internal network and bootstrap the system this
> way.
>
> Any suggestions?
>
> ~jpr
>
> _______________________________________________
> Crowbar mailing list
> Crowbar@dell.com
> https://lists.us.dell.com/mailman/listinfo/crowbar
> For more information: http://crowbar.github.com/
>
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
_______________________________________________
Crowbar mailing list
Crowbar@dell.com
https://lists.us.dell.com/mailman/listinfo/crowbar
For more information: http://crowbar.github.com/
