csc/Hanlon

Next-generation automation software for bare-metal and virtual server provisioning.

tjmcs

@tjmcs

'To see'...not 'to so'...sorry

That's what you did...it's been a long morning already

gmoy

@gmoy

I screwed something up now I did a gem update and then rebooted the server Now I am getting the following message trying to run a hanlon command

<-uninitialized constant BSON::OrderedHash

gmoy

@gmoy

I need to step away for a few hours. I created an image before I got started this morning so I think I will install it and run through the final configuration again

tjmcs

@tjmcs

k, I think there's an issue with the MK image we created a few days ago

could try to pull the 3.0.0 image from cscdock and see if that works or not

may have to release a 3.0.2 image soon...testing the 3.0.1 image locally

guess it's not an issue with that image; here's what I got using the 3.0.1 Microkernel image from cscdock:

$ $ docker pull cscdock/hanlon-microkernel:3.0.1
3.0.1: Pulling from cscdock/hanlon-microkernel
6ea79f377ee3: Pull complete
896fd5026af0: Pull complete
ad5ce9abe4f9: Pull complete
9bd88c7ac976: Pull complete
5de0195fc354: Pull complete
Digest: sha256:952b319fb953752ab53e2a80c0559f481e1e5b4ed7ed1cdccb573d79a6bd06a0
Status: Downloaded newer image for cscdock/hanlon-microkernel:3.0.1
$ docker save cscdock/hanlon-microkernel:3.0.1 > /tmp/hanlon-microkernel-v3.0.1.tar
$ bzip2 /tmp/hanlon-microkernel-v3.0.1.tar
$ hanlon image add -t mk -p /tmp/rancheros-v0.4.1.iso -d /tmp/hanlon-microkernel-v3.0.1.tar.bz2 -k ~/.ssh/id_rsa.pub
Attempting to add, please wait...
Image Added:
 UUID =>  29bfsqlvBTXxdb2G8iVt6e
 Type =>  MicroKernel Image
 Name/Filename =>  rancheros-v0.4.1.iso
 Status =>  Valid
 Version =>  3.0.1
 Built Time =>  2016-02-23 09:14:00 -0800

$  hanlon node
Discovered Nodes
         UUID           Last Checkin  Status                                         Tags
4QO9zcE5b9ZxoeC0AXKu0m  12 sec        A       [small_disk,000C29AECE0B,cpus_1,IntelCorporation,memsize_1987MiB,nics_1,vmware_vm]
$

tjmcs

@tjmcs

(the hanlon node command was run after starting up a VM and waiting for it to boot into the Microkernel)

the first couple of tags in that list were created by a pair of tags I defined locally, but the rest (starting with cpus_1 and continuing to the end) are system defined tags

gmoy

@gmoy

I emailed you what I have done so far to build the ubuntu server , install hanlon, and configure hanlon

The server I am trying to image is at a login prompt for rancheros and the hanlon node output is

Discovered Nodes
UUID Last Checkin Status Tags
2wOEift4AJHrzyWxH1LkEC 12 sec A [n/a]

And the hanlon image output is

Image:
UUID => 6P5Rrz2HHE6px1N40Hjksy
Type => MicroKernel Image
Name/Filename => rancheros-v0.4.1.iso
Status => Valid
Version => 3.0.1
Built Time => 2016-02-23 14:47:33 -0500

gmoy

@gmoy

Also the server that I am trying to image is a HP BL460cG8 blade with 10Gb Flex Fabric nic interfaces. Just wondering if this maybe a driver issue

gmoy

@gmoy

It is a driver issue with the FLEX 10 Fabric nics. I booted an older server and I see tags now for the node.

gmoy

@gmoy

The blade servers are what we need a deployment server for so I guess hanlon won't work until the lan drivers on the MK can be upgraded

Please let me know when this can be done otherwise I will need to look at other options.

tjmcs

@tjmcs

The best solution is probably to modify the cloud-config that is fed to the RancherOS instance when it boots up so that it'll feed in (and install) the appropriate drivers as it

As it boots up

Would be an extension to Hanlon to support the installation of additional drivers (if they are specified) into the RancherOS instance as it boots

Joseph Callen

@jcpowermac

@gmoy thanks for your document that you sent. When I get a chance I will put it up in the wiki and give you credit. Last night @tjmcs and I went through the troubleshooting steps so that we can get more information.
https://gist.github.com/jcpowermac/3ed70022ba218ad29ce6

Hippie Hacker

@hh

Put up https://github.com/csc/Hanlon/wiki/How-is-it-all-connected for fun, documenting some of the more obscure portions of the process with a walk through of all the packets w/ screenshots and links to code

tjmcs

@tjmcs

Wow! Thanks @hh for the detailed documentation of the entire process :)

Hippie Hacker

@hh

its definately needs to be broken down further into DHCP, TFTP, Microkernel, and common active_model fsm logic

These vendor specific options used to be processed by https://github.com/csc/Hanlon-Microkernel/commit/05b87262967ee33b3a50ea3d412e7812d8dcac9f#diff-0ba7ab68423f2fe93e585cf854323583

#dnsmasq options:
dhcp-option-force=224,1.1.1.6
dhcp-option-force=225,8026
dhcp-option-force=226,http://1.1.1.6:8026/

Has there been a replacement for these?

Hippie Hacker

@hh

Looks like we moved away from the ZenHub issue board? (last used in December): https://github.com/csc/Hanlon/issues#boards?repos=17629871

tjmcs

@tjmcs

I was maintaining that view of the project, @hh, but found that the constraint that only those with commit access (contributors) could update the status of items on the Kanban board limited the usefulness of that tool

If the ZenHub folks add some sort of RBAC (based on GitHub roles) to that tool it'd be a lot more useful

Hippie Hacker

@hh

@tjmcs on raspi / chip (armv7) 7zip and fuseiso may be overkill... is there a reason we went that route? I remember conversations, but it's been a long time

tjmcs

@tjmcs

we needed a set of utilities that could consistently unpack the ISOs that were being loaded into Hanlon, @hh, and the set of tools used seemed to be the best combination for the ISOs that were out there at the time (in fact, if you look at the code you'll see that it uses a number of different combinations to try to find one that works locally, depending on the toolset available to you and the ISO that it's unpacking)

Hippie Hacker

@hh

Weren't there issues with mount on some?

tjmcs

@tjmcs

apologies for the delayed response, @hh, but have been in transit...we used a mount command to unpack the ISO when we wrote the original Razor project, but there was concern on the part of the PuppetLabs folks that it would require either sudo'ers access to allow for the mount command or that Razor would have to be run as root; that led us to use fuseiso and 7zip instead (which could be run in user space and didn't require root-level access)

the logic in Hanlon got a bit more complicated when we wrote the code to unpack Windows images as well, since the fuseiso command won't work with a Windows image...so the choices are mount, fuseiso, and 7zip, and Hanlon will try to find the one that works and use it

you can find the logic for how it uses those commands in the Hanlon project in the base.rb and windows_install.rb files under the core/image_service directory

Hippie Hacker

@hh

csc/Hanlon#445 where did the Halon wiki go?

tjmcs

@tjmcs

https://github.com/csc/Hanlon/wiki

Or were you really looking for the Halon wiki?

Hippie Hacker

@hh

it was down

csc/Hanlon#445

chris8205

@chris8205

hi, what is the current release-state of hanlon ?

i ask because it seems there are no updates since 2015-2016

Hippie Hacker

@hh

I think @tjmcs has moved on, I used it a bit to create a raspi/chip based k8s deployer: http://blog.ii.coop/bring-the-cloud-to-your-neighborhood/ but haven't done much since

@chris8205 I don't believe it's in active development at the moment

tjmcs

@tjmcs

Unfortunately, I moved on from CSC (who "own" the project) and shortly after I moved on the members of the Hanlon team that I had left at CSC also left for other jobs at other employers

tjmcs

@tjmcs

I've offered to take over the project twice now and the owners (formerly CSC, now DXC) have told me that they are bringing people onboard to support it

one of these days, I just might fork it (or maybe someone else should?)

Where communities thrive

People

Repo info

Activity