Bare metal discovery: auto-provision NICs?

Support
1

Hello

is there a way with Foreman and the autodiscovery plugin to preconfigure
NICs before provisioning the discovered bare metal server?
I want to provision directly with bonded interfaces and right now I've to
do it manually, and I cannot find a way to control this with the
autodiscovery plugin.
I'm using foreman 1.14.1

Thanks

2

I have found that the best way is to just write a script to do the bonding
as part of provisioning. Without the RFE that Lukas mentioned, setting up
bonds is painful at best.

··· -- Brandon Boles

On Tuesday, March 7, 2017 at 10:20:05 AM UTC-6, dav...@billymob.com wrote:

Hello

is there a way with Foreman and the autodiscovery plugin to preconfigure
NICs before provisioning the discovered bare metal server?
I want to provision directly with bonded interfaces and right now I’ve to
do it manually, and I cannot find a way to control this with the
autodiscovery plugin.
I’m using foreman 1.14.1

Thanks

3

No unfortunately, we are tracking this RFE as:

http://projects.theforeman.org/issues/13847

It has many votes already, upvote. It's one of the most demanded
features for Foreman. Patches welcomed :slight_smile:

LZ

··· On Tue, Mar 7, 2017 at 5:20 PM, wrote: > Hello > > is there a way with Foreman and the autodiscovery plugin to preconfigure > NICs before provisioning the discovered bare metal server? > I want to provision directly with bonded interfaces and right now I've to do > it manually, and I cannot find a way to control this with the autodiscovery > plugin. > I'm using foreman 1.14.1 > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Foreman users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-users+unsubscribe@googlegroups.com. > To post to this group, send email to foreman-users@googlegroups.com. > Visit this group at https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.

–
Later,
Lukas @lzap Zapletal

4

Brandon, that's a really good idea! Even if I will probably come up with
something tied to my infra, it's a good workaround.
Anyway, I'm going to upvote that RFE.

Thanks to both for you answers

··· On Wednesday, March 8, 2017 at 10:47:30 AM UTC+1, Brandon Boles wrote: > > I have found that the best way is to just write a script to do the bonding > as part of provisioning. Without the RFE that Lukas mentioned, setting up > bonds is painful at best. >
5

Hello Brandon,

Any chance you can share the script? I'd love to do something similar. We
are in an even worse situation (bonding + trunking) and that would be a
godsend.

Thanks.

··· On Wednesday, March 8, 2017 at 10:47:30 AM UTC+1, Brandon Boles wrote: > > I have found that the best way is to just write a script to do the bonding > as part of provisioning. Without the RFE that Lukas mentioned, setting up > bonds is painful at best. >
6

That script is pretty specific but may give you a starting point. Let me
know if you have any questions.

··· On Friday, March 10, 2017 at 2:50:40 AM UTC-6, Alexander Rilik wrote: > > On Wednesday, March 8, 2017 at 10:47:30 AM UTC+1, Brandon Boles wrote: >> >> I have found that the best way is to just write a script to do the >> bonding as part of provisioning. Without the RFE that Lukas mentioned, >> setting up bonds is painful at best. >> > > Hello Brandon, > > Any chance you can share the script? I'd love to do something similar. We > are in an even worse situation (bonding + trunking) and that would be a > godsend. > > Thanks. >

–
Brandon Boles

7

Brilliant, thanks!

··· On Tuesday, March 14, 2017 at 7:00:44 PM UTC+1, Brandon Boles wrote: > > > https://github.com/bboles/foreman-nic-provisioning > > That script is pretty specific but may give you a starting point. Let me > know if you have any questions. > >
8

Brandon, thanks for sharing. Anyway in the end I went another route: I
pre-created the hosts in Foreamn programmatically using hammer CLI, since I
already knew all the hosts being added.
I know that in a scenario "we are adding 200 machines at the same time" it
doesn't scale as well as autodiscovery, but in my case they were just 20.

··· On Tuesday, March 14, 2017 at 7:00:44 PM UTC+1, Brandon Boles wrote:

https://github.com/bboles/foreman-nic-provisioning

That script is pretty specific but may give you a starting point. Let me
know if you have any questions.

9

I also have been taking this strategy for our physical hosts when we get
them. Just grab their MAC addresses and use a script to loop through them
and create the hosts. The issues with discovery & bonded nics makes it
pretty hard to use discovery at all.

··· On Fri, Mar 17, 2017 at 6:03 AM wrote:

On Tuesday, March 14, 2017 at 7:00:44 PM UTC+1, Brandon Boles wrote:

https://github.com/bboles/foreman-nic-provisioning

That script is pretty specific but may give you a starting point. Let me
know if you have any questions.

Brandon, thanks for sharing. Anyway in the end I went another route: I
pre-created the hosts in Foreamn programmatically using hammer CLI, since I
already knew all the hosts being added.
I know that in a scenario “we are adding 200 machines at the same time” it
doesn’t scale as well as autodiscovery, but in my case they were just 20.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

–

KAYAK

Neil Hanlon

Devops Engineer

+1 978 451 0707