> On Mon, Jul 23, 2012 at 11:50 AM, Julian Edwards
> <email address hidden> wrote:
> > To clarify, why would someone "very likely would want to query by the
> > mac address". What's the use case?
>
> If they are staring at a rack full of hardware, one of which has a
> fault light lit, the only data they have at hand is the MAC address of
> the ethernet card, which is (for servers) often printed on the card,
> for exactly this reason.
Right, and if there is a database of information about systems, then it
contains MAC addresses.
The other thing is that if maas is not in charge of the dhcp and they're
doing static-dhcp, then they clearly *do* have a MAC address to system
database somewhere already.
basically, MAC is a unique id for a system that people already have and
use, and as Robert said, is often actually on a sticker on the hardware.
(ignore the known fact that there duplicate macs exist).
On Mon, 23 Jul 2012, Robert Collins wrote:
> On Mon, Jul 23, 2012 at 11:50 AM, Julian Edwards
> <email address hidden> wrote:
> > To clarify, why would someone "very likely would want to query by the
> > mac address". What's the use case?
>
> If they are staring at a rack full of hardware, one of which has a
> fault light lit, the only data they have at hand is the MAC address of
> the ethernet card, which is (for servers) often printed on the card,
> for exactly this reason.
Right, and if there is a database of information about systems, then it
contains MAC addresses.
The other thing is that if maas is not in charge of the dhcp and they're
doing static-dhcp, then they clearly *do* have a MAC address to system
database somewhere already.
basically, MAC is a unique id for a system that people already have and
use, and as Robert said, is often actually on a sticker on the hardware.
(ignore the known fact that there duplicate macs exist).