#theforeman

you could then search by mac to get hosts

thats fancy and i will use it. I love consoles but terrible with the foreman console for some reason ;)

given another 5 min i could probably do a 2-d array

its k

but you get the idea :P

indeed. tyvm

gwmngilfen: now that I have you... is there documentation for the console?

only in so far as it's a normal Rails console. we don't really do anything foreman-specific

gotcha

so, as per usual, you have access to all the Models, etc

tbh, what i gave you is overly complicated - you could just do Nic::Base.all.map(&:mac).compact.sort

thanks again. i rarely use the console but it seems to be very helpful when needed to do odd tasks

definitely

does it matter if i install foreman, or puppetserver first?

a default run of foreman-installer will include a puppetserver anyway, so I'd go for that

is there a way to specify a predefined key pair to use with AWS instance provisioning?

one question: I added the bmc module to the foreman proxy, and I see in the infrastructure-smart-proxies, that it's enabled

bbut on the host list, I do not get an option to reboot discovered hosts

even though the discovered hosts all have been identified with correct ip address for ipmi

tmilam: no, foreman uses your api key to add it's own key. you can always add more keys to auth_keys in the finish script though

einjen_: i'm not sure about the interaction of bmc and discovery ^ lzap?

einjen_: for normal hosts you'd have to add a BMC nic in Foreman to show the power controls

gwmngilfen: this is a katello install, if it matters

i don't think it does

I tried regular foreman a few months ao, and then the bmc module worked

thanks gwmngilfen

or, I configured it correctly then, and not now.

ipmitool from cli works as expected

einjen_: check it works for ordinary hosts - my guess is that the discovery plugin isn't bmc-aware, but I don't know for sure

failing that, hit up the mailing list as i think most of the discovery ppl are afk just now

i do think it is, because it recogize all four nics + ipmi interface

thats just facts from puppet, iirc

it even detect the ipmi ip address

i have no bmc hardware to test on though :)

so, yeah, i'd either try back later or hit up the mailing list for a more async conversation on it

gwmngilfen: do you think it's more robust to install puppetserver, and install foreman through a maintained puppet module?

ok

thanks

is https://docs.puppet.com/puppet/4.0/reference/in... enterprise, or the free version?

jeffreylevesque: the foreman-installer is a set of puppet modules - you can run the installer and then import the installer modules to maintain it. thats what i do

ok

gwmngilfen: so, https://github.com/theforeman/puppet-foreman?

thats one of the installer modules, yes. for the whole thing, i'd use https://theforeman.org/manuals/1.12/quickstart_...

regarding puppet: When I'm provisioning my hosts, they do not have puppet installed when they are finished installing. I'm using centos. Is there some additional repos I need to have enabled?

epel?

iirc puppet is in epel, yes

ah

but enable-epel defaults to true in the default kickstart - https://github.com/theforeman/community-templat...

reboot and retry, then

is it attempting to install puppet and failing to find it, or not even trying that?

you can check the rendered template for the host to see if puppet/epel are listed

(Host > Templates > Review Provision Template)

not sure, but the nodes does not have access to epel because they are on closed subnet. I have only enabled centos Base repo on foreman server

well, obviously to install puppet they'll have to be able to get an rpm from somewhere :)

i am working on that very same thing right now and have an interesting issue I have yet to figure out. The script returns the Fedora epel repo for ALL linux hosts, even when the OS is not Fedora

also using centos einjen_

i'm testing foreman in vagrant local vm. since it's a local test environment, should i change /etc/hosts - https://bpaste.net/show/bd399d9d907f?

Singularity42: there is no other epel - epel is a set of packages for rhel-like OSs based on Fedora's packages

jeffreylevesque: yep, you absolutely need a proper fqdn, even for a sandbox env. ofc, you can just make one up (foreman.sandbox.local?)

gwmngilfen: sorry. I mean difference between Fedora and Cento Repo for downloading puppet

fedora vs. el

gwmngilfen: thanks.... I see in the provisioning template that there is an option to give repository (url). May I add available repositories? how?

Singularity42: still no idea what you mean then. the default kickstart uses both http://yum.puppetlabs.com/fedora/... and http://yum.puppetlabs.com/el/... depending on an OS variable, or gets it from the existing repos if enable-puppetlabs-repo is false

einjen_: where are you looking? just so i know which thing you're altering :)

host --> templates --> provisioning template

einjen_: so the templates are entirely free fo your to edit to your requirements, the ones shipped are just what work for the majority. head over to Provisioning Templates and edit as you like (or clone and edit the new one)

s/fo your/for you

i see in the config for provisioning templates, there is two puppet templates. puppet.conf and puppet_setup

I should probably look into these

indeed, those are what we call snippets - reusable template chunks that can be included in other templates

helps to reduce duplication across templates

sorry. I'm VERY new to all this. both puppet and foreman :/

trying to replace rocks Cluster software :)

einjen_: no need to be sorry, we all had to start somewhere

the thing to keep in mind is the Review button (or the Preview while editing a template) which allows you to see the Kickstart exactly as it will be sent to the host in question

that'll help you check that the kickstart looks right before spending 20mins waiting for an install to fail ;)

is this bad - https://bpaste.net/show/0c6a641aecd1?

maybe, it looks like yum didn't 100% like the puppetserver package.

that said, if it's installed and working, it's probably fine

you can re-run the installer again to make sure

is that production safe?

i guess i can blow this away

and redo

its written in puppet, so it's automatically idempotent

tbh, it's your call. it's probably fine, but beeing 100% sure doesn't hurt if you have the time

(assuming it is *actually* fine and the puppetserver is actually installed an running)

i've not seen that particular error about deltarpm before, tbh

but i would expect further errors if it had completely failed to install