Ok fair enough. I am not sure cobbler is keeping up with linux tbh. For example those kernel options need to be used with ubuntu 16.04. Maybe there is a future roadmap for cobbler? Or maybe the future is cloud where you dont need to do os installs?
-- Alastair Munro -----Original Message----- From: Matt Luettgen <mattluett...@gmail.com> To: alast...@alastair-munro.com Cc: cobbler mailing list <email@example.com> Sent: Fri, 14 Oct 2016 18:14 Subject: Re: [cobbler] Re: teamd support in cobbler teamd has better speeds, options, etc... http://rhelblog.redhat.com/2014/06/23/team-driver On Oct 14, 2016 12:00 PM, <alast...@alastair-munro.com> wrote: > Meant to add, this just sounds like bonding mode 5? Is there are reason > why you don't want to use this? Cobbler supports bonding. > > A quick google finds this (saves me trying to explain it): > > http://www.unixarena.com/2013/06/how-to-configure-bondingteaming-on.html > > I tend to force the old device naming on el7 (like eth0), as its a bit > more predictable for cobbler. Use these as kernel options. > > net.ifnames=0 biosdevname=0 > > > On 2016-10-14 17:50, alast...@alastair-munro.com wrote: > >> Network Manager is managing networking via a service.Originally it was >> designed for GUI logins where you would login as a user as part of the >> login, network manager would be run to setup the network (typically >> using dhcp). Now it seems Network Manager is much more expanded. >> Refering to the link below, section 1.9 refers back to the static >> network config, which cobbler implements: 1.9. NETWORK CONFIGURATION >> USING SYSCONFIG FILES. >> >> Note this section: >> >> 1.3. INTRODUCTION TO NETWORKMANAGER >> >> In Red Hat Enterprise Linux 7, the default networking service is >> provided by NetworkManager, which is a dynamic network control and >> configuration daemon that attempts to keep network devices and >> connections up and active when they are available. The traditional >> ifcfg type configuration files are still supported. See Section 1.8, >> “NetworkManager and the Network Scripts” for more information. >> >> So I think cobbler uses the older/static way of configuring >> networking, using the /etc/sysconfig/network-scripts config dir. >> >> I am not sure what is planned for future versions of cobbler? >> >> I suspect you may need to include post kickstart snippet for using >> network manager, or figure how to do the teaming using the older >> method? >> >> Alastair >> >> On 2016-10-14 16:01, Matt Luettgen wrote: >> >>> https://access.redhat.com/documentation/en-US/Red_Hat_Enterp >>> rise_Linux/7/html/Networking_Guide/sec-Configure_a_Network_ >>> Team_Using-the_Command_Line.html >>> >>> On Oct 14, 2016 9:39 AM, "Orion Poplawski" <or...@cora.nwra.com> >>> wrote: >>> >>> On 10/14/2016 01:31 AM, johanwint...@gmail.com wrote: >>>> >>>> Will there be teamd support in cobbler? or how can i deploy rhel7 >>>>> machines with teamd config on cobbler. >>>>> >>>> >>>> I know nothing about teamd. What needs to get configured on a >>>> target machine? >>>> >>>> -- >>>> Orion Poplawski >>>> Technical Manager 303-415-9701 x222  >>>> NWRA/CoRA Division FAX: 303-415-9702  >>>> 3380 Mitchell Lane or...@cora.nwra.com >>>> Boulder, CO 80301 http://www.cora.nwra.com >>>> _______________________________________________ >>>> cobbler mailing list -- firstname.lastname@example.org >>>> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org >>>> >>> >>> >>> Links: >>> ------ >>>  tel:303-415-9701%20x222 >>>  tel:303-415-9702 >>> _______________________________________________ >>> cobbler mailing list -- email@example.com >>> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org >>> >> _______________________________________________ >> cobbler mailing list -- firstname.lastname@example.org >> To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org >> >
_______________________________________________ cobbler mailing list -- email@example.com To unsubscribe send an email to cobbler-le...@lists.fedorahosted.org