CDT
Robin CASSET Service R&D Bull SAS ________________________________________ From: [email protected] [[email protected]] on behalf of [email protected] [[email protected]] Sent: Wednesday, April 29, 2015 6:27 AM To: [email protected] Subject: cobbler Digest, Vol 82, Issue 11 Send cobbler mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://lists.fedorahosted.org/mailman/listinfo/cobbler or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of cobbler digest..." Today's Topics: 1. Re: Unamble to install nodes with Cobbler (Harry Hoffman) 2. Web doc issue (Orion Poplawski) 3. Re: Web doc issue (Alan Evangelista) 4. Provisioning 50 cluster nodes (Jagga Soorma) 5. Re: Provisioning 50 cluster nodes (Alan Evangelista) 6. Re: Provisioning 50 cluster nodes (Jagga Soorma) 7. Re: Provisioning 50 cluster nodes (Alan Evangelista) ---------------------------------------------------------------------- Message: 1 Date: Mon, 27 Apr 2015 08:13:55 -0400 From: Harry Hoffman <[email protected]> To: cobbler mailing list <[email protected]> Subject: Re: [cobbler] Unamble to install nodes with Cobbler Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 Hi Robin, Are you sure the tftp-server is listening and there's not a firewall (host or network based that's blocking communication to that tftp port)? Does the client system get a dhcp address from the server? Cheers, Harry On Apr 27, 2015 3:20 AM, Robin Casset <[email protected]> wrote: > > Hello, > > My name is Robin, I'm an apprentice engineer at Bull SAS. > I recently install cobbler on a server to make some few test of it. I have > been able to import an iso, create a repo and set up profiles. The pxe file > is generated and seems to be good but when the node boot on the network I > have a message "unable to find files" > > here are my node and image profiles : > > Name : dep12 > TFTP Boot Files : {} > Comment : > Enable gPXE? : False > Fetchable Files : {} > Gateway : 192.168.1.0 > Hostname : dep12 > Image : > IPv6 Autoconfiguration : False > IPv6 Default Device : > Kernel Options : {} > Kernel Options (Post Install) : {} > Kickstart : /var/lib/cobbler/kickstarts/dep12.ks > Kickstart Metadata : {} > LDAP Enabled : False > LDAP Management Type : authconfig > Management Classes : [] > Management Parameters : <<inherit>> > Monit Enabled : False > Name Servers : ['192.168.1.1'] > Name Servers Search Path : [] > Netboot Enabled : True > Owners : ['root'] > Power Management Address : 192.168.1.13 > Power Management ID : > Power Management Password : administrator- > Power Management Type : apc > Power Management Username : administrator > Profile : Centos7-x86_64 > Internal proxy : <<inherit>> > Red Hat Management Key : <<inherit>> > Red Hat Management Server : <<inherit>> > Repos Enabled : False > Server Override : <<inherit>> > Status : production > Template Files : {} > Virt Auto Boot : 0 > Virt CPUs : <<inherit>> > Virt Disk Driver Type : <<inherit>> > Virt File Size(GB) : <<inherit>> > Virt Path : <<inherit>> > Virt PXE Boot : 0 > Virt RAM (MB) : <<inherit>> > Virt Type : xenpv > Interface ===== : eth0 > Bonding Opts : > Bridge Opts : > CNAMES : [] > DHCP Tag : default > DNS Name : > Per-Interface Gateway : 192.168.1.0 > Master Interface : > Interface Type : > IP Address : 192.168.1.12 > IPv6 Address : > IPv6 Default Gateway : > IPv6 MTU : > IPv6 Prefix : > IPv6 Secondaries : [] > IPv6 Static Routes : [] > MAC Address : 00:30:48:7a:3c:bc > Management Interface : True > MTU : > Subnet Mask : 255.255.255.0 > Static : True > Static Routes : [] > Virt Bridge : xenbr0 > > profiles: > ========== > Name : Centos7-x86_64 > TFTP Boot Files : {} > Comment : > DHCP Tag : linux > Distribution : Centos7-x86_64 > Enable gPXE? : False > Enable PXE Menu? : True > Fetchable Files : {} > Kernel Options : {} > Kernel Options (Post Install) : {} > Kickstart : /var/lib/cobbler/kickstarts/dep12.ks > Kickstart Metadata : {} > Management Classes : [] > Management Parameters : <<inherit>> > Name Servers : [] > Name Servers Search Path : [] > Owners : ['root'] > Parent Profile : > Internal proxy : > Red Hat Management Key : <<inherit>> > Red Hat Management Server : <<inherit>> > Repos : ['Centos7'] > Server Override : <<inherit>> > Template Files : {} > Virt Auto Boot : 1 > Virt Bridge : xenbr0 > Virt CPUs : 1 > Virt Disk Driver Type : raw > Virt File Size(GB) : 5 > Virt Path : > Virt RAM (MB) : 512 > Virt Type : kvm > > And here the pxe file: > > default linux > prompt 0 > timeout 1 > label linux > kernel /images/Centos7-x86_64/vmlinuz > ipappend 2 > append initrd=/images/Centos7-x86_64/initrd.img ksdevice=bootif lang= > kssendmac text ks=http://192.168.1.1/cblr/svc/op/ks/system/dep12 > > I can't see where is the mistake and I tried many options... > > Thank's for you help! > > best regards > > > CDT > > Robin CASSET > Service R&D > Bull SAS > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler ------------------------------ Message: 2 Date: Mon, 27 Apr 2015 15:36:28 -0600 From: Orion Poplawski <[email protected]> To: cobbler mailing list <[email protected]> Subject: [cobbler] Web doc issue Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8 http://www.cobblerd.org/manuals/2.6.0/3/5_-_Kickstart_Templating.html mentions using a kickstart template in /opt, which is no longer allowed. -- Orion Poplawski Technical Manager 303-415-9701 x222 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane [email protected] Boulder, CO 80301 http://www.nwra.com ------------------------------ Message: 3 Date: Mon, 27 Apr 2015 18:48:52 -0300 From: Alan Evangelista <[email protected]> To: [email protected] Subject: Re: [cobbler] Web doc issue Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed On 04/27/2015 06:36 PM, Orion Poplawski wrote: > http://www.cobblerd.org/manuals/2.6.0/3/5_-_Kickstart_Templating.html > > mentions using a kickstart template in /opt, which is no longer allowed. Opened an issue in Cobbler issue tracker: https://github.com/cobbler/cobbler/issues/1455 Thanks for reporting. Regards, Alan Evangelista ------------------------------ Message: 4 Date: Tue, 28 Apr 2015 20:51:13 -0700 From: Jagga Soorma <[email protected]> To: cobbler mailing list <[email protected]> Subject: [cobbler] Provisioning 50 cluster nodes Message-ID: <CAKyjK50amjpr9cgMe3M9-JfDgEb=ax2rjz9oovekny_qrhp...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Hi Guys, I have been using cobbler for a few months now and it has worked very well for us. However, we have been only building a few servers at a time and my current process of having our SA's run a "cobbler system add" command for each server has worked just fine. I now have a requirement to build a cluster with 50+ nodes and was wondering how to automate this as much as possible. Has anyone out there already done something similar? If so, how did you approach this? I would hate to tell someone to run the cobbler system add command for 50 servers. Thanks in advance for your help with this! Regards. ------------------------------ Message: 5 Date: Wed, 29 Apr 2015 00:57:09 -0300 From: Alan Evangelista <[email protected]> To: [email protected] Subject: Re: [cobbler] Provisioning 50 cluster nodes Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed On 04/29/2015 12:51 AM, Jagga Soorma wrote: > I now have a > requirement to build a cluster with 50+ nodes and was wondering how to > automate this as much as possible. Has anyone out there already done > something similar? If so, how did you approach this? I would hate to > tell someone to run the cobbler system add command for 50 servers. I suppose you have a list of the MAC addresses and power management data (and maybe IP addresses) of the 50+ nodes. Simply create a Python script which creates the missing system data (eg name) automatically and uses Cobbler CLI / XML-RPC interface to add the systems to Cobbler. Regards, Alan Evangelista ------------------------------ Message: 6 Date: Tue, 28 Apr 2015 21:11:30 -0700 From: Jagga Soorma <[email protected]> To: cobbler mailing list <[email protected]> Subject: Re: [cobbler] Provisioning 50 cluster nodes Message-ID: <CAKyjK536x99ZQFFBUOgCvwq16T7iqNRAT0=hknufcodbgp0...@mail.gmail.com> Content-Type: text/plain; charset=UTF-8 Actually I don't have the mac addresses handy. Would have to login to the ilo/idrac of each server and grab the mac which is very time consuming. I do have all the hostnames and ip addresses defined in dns. Is there a way for me to get the bare metal hardware to tell the cobbler server its mac addresses and auto register somehow. From there maybe I can write a shell script to populate the other needed info. Thanks. On Tue, Apr 28, 2015 at 8:57 PM, Alan Evangelista <[email protected]> wrote: > On 04/29/2015 12:51 AM, Jagga Soorma wrote: >> >> I now have a >> requirement to build a cluster with 50+ nodes and was wondering how to >> automate this as much as possible. Has anyone out there already done >> something similar? If so, how did you approach this? I would hate to >> tell someone to run the cobbler system add command for 50 servers. > > > I suppose you have a list of the MAC addresses and power management data > (and maybe > IP addresses) of the 50+ nodes. Simply create a Python script which creates > the missing > system data (eg name) automatically and uses Cobbler CLI / XML-RPC interface > to add the > systems to Cobbler. > > > Regards, > Alan Evangelista > > _______________________________________________ > cobbler mailing list > [email protected] > https://lists.fedorahosted.org/mailman/listinfo/cobbler Hi! Yes, all dhcp/dns/tftp parameters were ok. I juste succed in depoyling nodes, the problem was the path of the repos... Thank's and sorry for asking your help for that >< best regards Robin ------------------------------ Message: 7 Date: Wed, 29 Apr 2015 01:27:45 -0300 From: Alan Evangelista <[email protected]> To: [email protected] Subject: Re: [cobbler] Provisioning 50 cluster nodes Message-ID: <[email protected]> Content-Type: text/plain; charset=utf-8; format=flowed On 04/29/2015 01:11 AM, Jagga Soorma wrote: > Actually I don't have the mac addresses handy. Would have to login to > the ilo/idrac of each server and grab the mac which is very time > consuming. Write a script to do that? expect/pexpect may be helpful. > I do have all the hostnames and ip addresses defined in > dns. Is there a way for me to get the bare metal hardware to tell the > cobbler server its mac addresses and auto register somehow. If your bare metal hardware is in the same LAN of the Cobbler server, you can use "arp -a" after pinging the bare metal hardware from Cobbler server to get its MAC address. If Cobbler server is not in the same LAN, you could split this in 2 steps: run a MAC address discovery script in a system which *is* in the same LAN of the bare metal hardware and then add the systems to Cobbler. Regards, Alan Evangelista ------------------------------ _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler End of cobbler Digest, Vol 82, Issue 11 *************************************** _______________________________________________ cobbler mailing list [email protected] https://lists.fedorahosted.org/mailman/listinfo/cobbler
