[Openstack] Use of MAC addresses in Openstack VMs

Shake Chen shake.chen at gmail.com
Tue Oct 23 00:43:23 UTC 2012


On Mon, Oct 22, 2012 at 8:08 PM, Gary Kotton <gkotton at redhat.com> wrote:

>  On 10/20/2012 07:23 PM, Tim Bell wrote:
>
>  ** **
>
> If we purchase an OUI, is there a mechanism within Quantum to only
> allocate Mac addresses with that prefix ?
>
>
> At the moment Quantum enables the user to define a base MAC address. That
> is the user can update the configuration file. The user selects a base MAC
> and the MAC's are allocated in that range. I think that this gives us a lot
> of flexibility.
>
> Please see below for the configuration options.
>
> # Base MAC address. The first 3 octets will remain unchanged. If the
> # 4h octet is not 00, it will also used. The others will be
> # randomly generated.
> # 3 octet
> # base_mac = fa:16:3e:00:00:00
> # 4 octet
> # base_mac = fa:16:3e:4f:00:00
>

as my know, the  fa:16:3e would on behalf of a company.

>
> If I recall correctly this is hard coded in nova networking.
>
> Thanks
> Gary
>
>
>  ****
>
> ** **
>
> Tim****
>
> ** **
>
> *From:* openstack-bounces+tim.bell=cern.ch at lists.launchpad.net [
> mailto:openstack-bounces+tim.bell=cern.ch at lists.launchpad.net<openstack-bounces+tim.bell=cern.ch at lists.launchpad.net>]
> *On Behalf Of *Salvatore Orlando
> *Sent:* 20 October 2012 10:20
> *To:* Vinay Bannai
> *Cc:* openstack at lists.launchpad.net
> *Subject:* Re: [Openstack] Use of MAC addresses in Openstack VMs****
>
> ** **
>
> Hi Vinay,****
>
> ** **
>
> I understand your concerns about conflicts with already assigned OUIs.****
>
> It is however my opinion that it is not up to the Openstack Foundation,
> but to entities deploying Openstack, to buy MAC OUIs.****
>
> As regards Quantum, we should ensure the default MAC range we use is
> locally assigned; unfortunately I do not know enough about nova-network.**
> **
>
> Also, it is my opinion that a locally-assigned OUI would be sufficient for
> many use cases, without the need for a globally assigned one.****
>
> ** **
>
> Regards,****
>
> Salvatore****
>
> ** **
>
> On 20 October 2012 04:05, Vinay Bannai <vbannai at gmail.com> wrote:****
>
> I was talking to Nachi and Gary during the Quantum design session about
> the need to have a proper MAC OUI allocation scheme for Openstack
> development folks. They suggested that I send it out for wider discussion
> on the mailing list. ****
>
> ** **
>
> It turns out that it would be useful for the Openstack foundation to apply
> for a MAC OUI from IEEE that can be used for development purposes and
> testing. This way we don't unwittingly use someone else MAC allocation.
> Here are the details ****
>
> ** **
>
> http://standards.ieee.org/develop/regauth/oui/index.html****
>
> ** **
>
> The cost to get a OUI allocation is around $2000 dollars. Remember if we
> use random MAC OUI,  the actual owners can assert their legal claim on the
> MAC address in the event of a conflict now that we have support for more
> sophisticated tunnels that allow connections from public and private
> clouds. ****
>
> ** **
>
> Comments welcome. ****
>
> ** **
>
> Vinay****
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp****
>
> ** **
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
Shake Chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20121023/e1e2614b/attachment.html>


More information about the Openstack mailing list