gateway and hostnames with multiple NICs

[Vreman, Peter]

I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.

My proposal is:
- Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network
- Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files
- Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX

Any toughts?

Regards,
Peter

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

[Jasper Capel]

Vreman, Peter - Acision wrote:
> I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.
>
> My proposal is:
> Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network
> Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files
> Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX
>
> Any toughts?
>
> Regards,
> Peter

FWIW: Sounds like a good idea to me. :)
(The ability to configure /etc/resolv.conf from cobbler is still on my 
list as well, unfortunately I don't have much time at the moment.)

Jasper

[Michael DeHaan]

Vreman, Peter - Acision wrote:
> I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.
>
> My proposal is:
> Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network

Understood. The underlying issue that resulted in the present 
implementation is that we need to be able to use Cobbler to provision a 
dual homed system, when we are using cobbler's manage_dns features. We 
may want to provide a different hostname to each interface. For 
instance, assume a DMZ setup. I also know of some folks using dual homed 
virtual machines as well.
> Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files

That's fair. If not set, we should be telling DNS management to use the 
hostname of the first defined NIC.

The cobbler code "from_datastruct" code would need to be smart enough to 
rename all of the fields in the interface from hostname->dnsname and 
populate the hostname field with the value from the first defined NIC. I 
am probably the one who best understands the underlying upgrade magic so 
I can give this a go.

I see Jasper already agreed below so I think we can make this happen if 
he'll volunteer to audit my changes to his snippets. We might as well 
get the networking features as right as we possibly can since we're 
making a lot of upgrades to them for this release.
> Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX

Sounds reasonable to me. Do you plan on adding the route feature?
> Any toughts?
>
> Regards,
> Peter
>
> This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
>
> cobbler mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/cobbler

[Vreman, Peter]

> -----Original Message-----
> From: [e-mail] [mailto:cobbler-
> [e-mail]] On Behalf Of Michael DeHaan
> Sent: woensdag 19 november 2008 16:59
> To: cobbler mailing list
> Subject: Re: gateway and hostnames with multiple NICs
>
> Vreman, Peter - Acision wrote:
> > I've systems with multiple NICs. This gives problems with the gateway
>
> and hostname that are configured per NIC.
> > My proposal is:
> > Make the Hostname and Gateway a system wide field instead of per NIC.
>
> This information can be used to generate the /etc/sysconfig/network
> >
>
> Understood. The underlying issue that resulted in the present
> implementation is that we need to be able to use Cobbler to provision a
> dual homed system, when we are using cobbler's manage_dns features. We
> may want to provide a different hostname to each interface. For
> instance, assume a DMZ setup. I also know of some folks using dual homed
> virtual machines as well.
> > Add an optional dnsname field to the NIC that can be used to provision
>
> the DNS or generate a hosts files
> >

All my systems have also an unique hostnames for each interface. The hostname is only the visible name to the user. In the configuration files for ip address names like hostname-oam or hostname-backup need to be used. That means that also for the first address I want to have the ability to add a secondary alias. With also having the dnsname per NIC this can be done.
> That's fair. If not set, we should be telling DNS management to use the
> hostname of the first defined NIC.
>
> The cobbler code "from_datastruct" code would need to be smart enough to
> rename all of the fields in the interface from hostname->dnsname and
> populate the hostname field with the value from the first defined NIC. I
> am probably the one who best understands the underlying upgrade magic so
> I can give this a go.

Ok
> I see Jasper already agreed below so I think we can make this happen if
> he'll volunteer to audit my changes to his snippets. We might as well
> get the networking features as right as we possibly can since we're
> making a lot of upgrades to them for this release.
> > Add a route field to the NICs there entries can be added in the format
>
> ipaddress:netmask:gateway. This is used to generate route-ethX
>
> Sounds reasonable to me. Do you plan on adding the route feature?

I can give it a try

Regards,
Peter

This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.

[Michael DeHaan]

Vreman, Peter - Acision wrote:
> > -----Original Message-----
> > From: [e-mail] [mailto:cobbler-
> > [e-mail]] On Behalf Of Michael DeHaan
> > Sent: woensdag 19 november 2008 16:59
> > To: cobbler mailing list
> > Subject: Re: gateway and hostnames with multiple NICs
> >
> > Vreman, Peter - Acision wrote:
> > > I've systems with multiple NICs. This gives problems with the gateway
> >
> > and hostname that are configured per NIC.
> > > My proposal is:
> > > Make the Hostname and Gateway a system wide field instead of per NIC.
> >
> > This information can be used to generate the /etc/sysconfig/network
> >
> > Understood. The underlying issue that resulted in the present
> > implementation is that we need to be able to use Cobbler to provision a
> > dual homed system, when we are using cobbler's manage_dns features. We
> > may want to provide a different hostname to each interface. For
> > instance, assume a DMZ setup. I also know of some folks using dual homed
> > virtual machines as well.
> > > Add an optional dnsname field to the NIC that can be used to provision
> >
> > the DNS or generate a hosts files
>
> All my systems have also an unique hostnames for each interface. The hostname is only the visible name to the user. In the configuration files for ip address names like hostname-oam or hostname-backup need to be used. That means that also for the first address I want to have the ability to add a secondary alias. With also having the dnsname per NIC this can be done.
> > That's fair. If not set, we should be telling DNS management to use the
> > hostname of the first defined NIC.
> >
> > The cobbler code "from_datastruct" code would need to be smart enough to
> > rename all of the fields in the interface from hostname->dnsname and
> > populate the hostname field with the value from the first defined NIC. I
> > am probably the one who best understands the underlying upgrade magic so
> > I can give this a go.
>
> Ok
> > I see Jasper already agreed below so I think we can make this happen if
> > he'll volunteer to audit my changes to his snippets. We might as well
> > get the networking features as right as we possibly can since we're
> > making a lot of upgrades to them for this release.
> > > Add a route field to the NICs there entries can be added in the format
> >
> > ipaddress:netmask:gateway. This is used to generate route-ethX
> >
> > Sounds reasonable to me. Do you plan on adding the route feature?
>
> I can give it a try
>
> Regards,
> Peter
>
> This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you.
>
> cobbler mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/cobbler

FWIW, I've already added the above, as I wanted to be certain of the 
migration codepath.

I'm working at adding this to the webapp now.

[Jasper Capel]

Vreman, Peter - Acision wrote:
> I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.
>
> My proposal is:
> Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network
> Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files
> Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX

I prefer we'd use the CIDR notation, as that's how it would end up in 
the route-ethX file. Is ipaddress/mask:gateway okay for everyone?

Jasper

[Michael DeHaan]

Jasper Capel wrote:
> Vreman, Peter - Acision wrote:
> > I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.
> >
> > My proposal is:
> > Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network
> > Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files
> > Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX
>
> I prefer we'd use the CIDR notation, as that's how it would end up in 
> the route-ethX file. Is ipaddress/mask:gateway okay for everyone?

+1 from me.
> Jasper
> _______________________________________________
> cobbler mailing list
> [e-mail]
> https://fedorahosted.org/mailman/listinfo/cobbler

[Jasper Capel]

Michael DeHaan wrote:
> Jasper Capel wrote:
> > Vreman, Peter - Acision wrote:
> > > I've systems with multiple NICs. This gives problems with the gateway and hostname that are configured per NIC.
> > >
> > > My proposal is:
> > > Make the Hostname and Gateway a system wide field instead of per NIC. This information can be used to generate the /etc/sysconfig/network
> > > Add an optional dnsname field to the NIC that can be used to provision the DNS or generate a hosts files
> > > Add a route field to the NICs there entries can be added in the format ipaddress:netmask:gateway. This is used to generate route-ethX
> >
> > I prefer we'd use the CIDR notation, as that's how it would end up in 
> > the route-ethX file. Is ipaddress/mask:gateway okay for everyone?
>
> +1 from me.

I've gone ahead and pushed this (static routes) to my networking branch.

Jasper