Hi all, In Rackspace's quark plugin (github.com/rackerlabs/quark), we’ve developed an extension for MAC address ranges (MARs) as a top-level resource. Thus, the Neutron service manages the MAC address allocation from a pool of ranges (as opposed to randomly generating a MAC address). However, we haven’t made a relationship between MARs and subnets/networks.
Amir On Feb 18, 2014, at 11:24 AM, Tim Bell <tim.b...@cern.ch> wrote: > > Jay, > > We've got a similar requirement at CERN where we would like to have pools of > ip/mac combinations for each subnet and have it so that the user is just > allocated one (and for the same subnet that the hypervisor is on). > > We've not found a good solution so far. > > Tim > >> -----Original Message----- >> From: Dong Liu [mailto:willowd...@gmail.com] >> Sent: 18 February 2014 18:12 >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [Network] Allocate MAC and IP address for a VM >> instance >> >> Hi Jay, >> >> In neutron API, you could create port with specified mac_address and fix_ip, >> and then create vm with this port. >> But the mapping of them need to manage by yourself. >> >> >> 在 2014年2月18日，22:41，Jay Lau <jay.lau....@gmail.com> 写道： >> >>> Greetings, >>> >>> Not sure if it is suitable to ask this question in openstack-dev list. Here >>> come a question related to network and want to get some >> input or comments from you experts. >>> >>> My case is as this: For some security issue, I want to put both MAC and >>> internal IP address to a pool and when create VM, I can get >> MAC and its mapped IP address and assign the MAC and IP address to the VM. >>> >>> For example, suppose I have following MAC and IP pool: >>> 1) 78:2b:cb:af:78:b0, 192.168.0.10 >>> 2) 78:2b:cb:af:78:b1, 192.168.0.11 >>> 3) 78:2b:cb:af:78:b2, 192.168.0.12 >>> 4) 78:2b:cb:af:78:b3, 192.168.0.13 >>> >>> Then I can create four VMs using above MAC and IP address, each row in >>> above can be mapped to a VM. >>> >>> Does any of you have any idea for the solution of this? >>> >>> -- >>> Thanks, >>> >>> Jay >>> _______________________________________________ >>> OpenStack-dev mailing list >>> OpenStack-dev@lists.openstack.org >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> >> _______________________________________________ >> OpenStack-dev mailing list >> OpenStack-dev@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
