Yes, reference is a problem. I see that we already have a resource
OS::Neutron::Port , but the problem is that we need to specify MAC & IP
manually for this resource and it is difficult to use this resource in a
autoscaling group.
https://github.com/openstack/heat-templates/blob/master/cfn/F17/Neu
On Tue, Jan 27, 2015 at 10:34:47AM +0800, Jay Lau wrote:
> 2015-01-27 10:28 GMT+08:00 Qiming Teng :
>
> > On Tue, Jan 27, 2015 at 10:13:59AM +0800, Jay Lau wrote:
> > > Greetings,
> > >
> > > I have a question related to MAC and IP binding, I know that we can
> > create
> > > a port to bind a priv
2015-01-27 10:28 GMT+08:00 Qiming Teng :
> On Tue, Jan 27, 2015 at 10:13:59AM +0800, Jay Lau wrote:
> > Greetings,
> >
> > I have a question related to MAC and IP binding, I know that we can
> create
> > a port to bind a private IP and MAC together then create VM using this
> > specified port to m
On Tue, Jan 27, 2015 at 10:13:59AM +0800, Jay Lau wrote:
> Greetings,
>
> I have a question related to MAC and IP binding, I know that we can create
> a port to bind a private IP and MAC together then create VM using this
> specified port to make sure the VM can use the the IP and MAC in this port
Greetings,
I have a question related to MAC and IP binding, I know that we can create
a port to bind a private IP and MAC together then create VM using this
specified port to make sure the VM can use the the IP and MAC in this port.
This can make sure one VM can have IP and MAC as customer require
