Re: [Openstack] multi_nic and mac addresses
@brian: the problem with a json field is that searching would be really expensive if we ever need to pull mac addresses from the db to ensure uniqueness. @Ilya: If I make a table, I plan on putting mac address, instance id, network id, and if zones are about ready, some sort of zone information in the table. -tr3buchet On Sat, Feb 26, 2011 at 8:11 AM, Ilya Alekseyev wrote: > I think that new table for NIC mac addresses is good idea, but we need in > table not only instance id, but network id for interface too. It will be > good for implementation multi-nic in libvirt for example. > Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] multi_nic and mac addresses
I think that new table for NIC mac addresses is good idea, but we need in table not only instance id, but network id for interface too. It will be good for implementation multi-nic in libvirt for example. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] multi_nic and mac addresses
Look at instance migration branch ComputeService table. How about json text field network-info. We want to do qdr infiniban ifs also. Sent from my iPhone On Feb 25, 2011, at 7:24 PM, Trey Morris wrote: > Tracking mac addresses is going to have to change for multi-nic. Instances > are going to have more than one mac address. It's been proposed that we don't > need to track the mac address(es) but I think it's necessary in order to > determine whether a mac is unique or not. Mac addresses don't need to be > unique across a whole implementation but they do need to be unique as far as > layer 2 networking is concerned. It will be quite a while before we run out > of mac addresses across the whole implementation so allowing duplicate macs > but preventing duplicates within a network layer two "zone" (not sure the > terminology at this point) can be handled later. I propose making a new table > for storing instance id mac address relationships. I'm also considering > randomly generating mac addresses using instance uuid as salt. > > Thoughts? > > -tr3buchet > Confidentiality Notice: This e-mail message (including any attached or > embedded documents) is intended for the exclusive and confidential use of the > individual or entity to which this message is addressed, and unless otherwise > expressly indicated, is confidential and privileged information of Rackspace. > Any dissemination, distribution or copying of the enclosed material is > prohibited. > If you receive this transmission in error, please notify us immediately by > e-mail > at ab...@rackspace.com, and delete the original message. > Your cooperation is appreciated. > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] multi_nic and mac addresses
Tracking mac addresses is going to have to change for multi-nic. Instances are going to have more than one mac address. It's been proposed that we don't need to track the mac address(es) but I think it's necessary in order to determine whether a mac is unique or not. Mac addresses don't need to be unique across a whole implementation but they do need to be unique as far as layer 2 networking is concerned. It will be quite a while before we run out of mac addresses across the whole implementation so allowing duplicate macs but preventing duplicates within a network layer two "zone" (not sure the terminology at this point) can be handled later. I propose making a new table for storing instance id mac address relationships. I'm also considering randomly generating mac addresses using instance uuid as salt. Thoughts? -tr3buchet Confidentiality Notice: This e-mail message (including any attached or embedded documents) is intended for the exclusive and confidential use of the individual or entity to which this message is addressed, and unless otherwise expressly indicated, is confidential and privileged information of Rackspace. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at ab...@rackspace.com, and delete the original message. Your cooperation is appreciated. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
