Open Stack

Hi Brad

> To me, a global range that everyone is using that's provided by OpenStack is seems much worse than just calculating an arbitrary private range by flipping bit b2 to 1 as shown in the wiki article below.  As long as you set this, you're guaranteed not to collide with any registered mac OUIs from other vendors (assuming you generate a fairly random range with the remaining bits) and offer a reasonable guarantee of uniqueness if you end up integrating at L2 with other clouds.  If, however, many OpenStack clouds end up using the same OUI because the foundation globally registers one, your risk of collision during L2VPN between OpenStack clouds would be higher.
>
> http://en.wikipedia.org/wiki/MAC_address

IMO, this is not matter of OUI by Openstack foundation. Because users
who has not use there own OUI may use default configuration value of
OUI bit which is not
owned by us. May be it could be another vendor's OUI.

My proposal is the default OUI value should be owned by OpenStack
foundation if $2000 isn't concern for OpenStack foundation.

Thanks
Nachi


> Just my two cents.. personally even if the foundation had a range I'd feel safer on a private scope than one that I KNOW a bunch of other clouds are using.
>
> Thanks!
>
> Brad McConnell
> Rackspace network guy
>
> ________________________________________
> From: openstack-bounces+bmcconne=rackspace.com at lists.launchpad.net [openstack-bounces+bmcconne=rackspace.com at lists.launchpad.net] on behalf of Eric Windisch [eric at cloudscaling.com]
> Sent: Saturday, October 20, 2012 2:54 PM
> To: Salvatore Orlando
> Cc: Vinay Bannai; openstack at lists.launchpad.net
> Subject: Re: [Openstack] Use of MAC addresses in Openstack VMs
>
> Sent from my iPad
>
> On Oct 20, 2012, at 10:19, Salvatore Orlando <sorlando at nicira.com> wrote:
>
>> 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.
>
> For comparison and reference, Xen has its own OUI which is used by default for its VMs.  Users of Xen do not need to apply for their own OUIs and I don't believe they should.
>
> It isn't necessary for VMs to have globally unique MACs, but they shouldn't overlap with devices from other vendors.
>
> I believe OpenStack should have its own OUI.
>
> Regards,
> Eric Windisch
> _______________________________________________
> 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