Revision history [back]

Hi,

Have found that when deploying a Cloudbase Windows Server 2012 R2 image with multiple NICs the order of the NICs can be inconsistent.

Would expect the Heat template below to result in int1="Ethernet", int2="Ethernet 2", int2 ="Ethernet 3" Sometimes this is the case, sometime int1 and int2 are transposed. Is there a way to have them fixed to the correct interface.

Server: type: OS::Nova::Server properties: name: Server flavor: { getparam: flavor } image: { getparam: image } availabilityzone: { getparam: availabilityzone } networks: - port: { getresource: int1 } - port: { getresource: int2 } - port: { getresource: int3 }

Hi,

Have found that when deploying a Cloudbase Windows Server 2012 R2 image with multiple NICs the order of the NICs can be inconsistent.

Would expect the Heat template below to result in int1="Ethernet", int2="Ethernet 2", int2 int3 ="Ethernet 3" Sometimes this is the case, sometime int1 and int2 sometimes interfaces are transposed. For example int1="Ethernet 2" and int2"=Ethernet". Is there a way to have them fixed to the correct interface.interface, we don't see this issue when RedHat images via HOT.

Server: type: OS::Nova::Server properties: name: Server flavor: { getparam: flavor } image: { getparam: image } availabilityzone: { getparam: availabilityzone } networks: - port: { getresource: int1 } - port: { getresource: int2 } - port: { getresource: int3 }

Hi,

Have found that when deploying a Cloudbase Windows Server 2012 R2 image with multiple NICs the order of the NICs can be inconsistent.

Would expect the Heat template below to result in int1="Ethernet", int2="Ethernet 2", int3 ="Ethernet 3" Sometimes this is the case, sometimes interfaces are transposed. For example int1="Ethernet 2" and int2"=Ethernet". Is there a way to have them fixed to the correct interface, we don't see this issue when RedHat images via HOT.

Server: type: OS::Nova::Server properties: name: Server flavor: { getparam: flavor } image: { getparam: image } availabilityzone: { getparam: availabilityzone } networks: - port: { getresource: int1 } - port: { getresource: int2 } - port: { getresource: int3 }

Hi,

Have found that when deploying a Cloudbase Windows Server 2012 R2 image with multiple NICs the order of the NICs can be inconsistent.

Would expect the Heat template below to result in int1="Ethernet", int2="Ethernet 2", int3 ="Ethernet 3" Sometimes this is the case, sometimes interfaces are transposed. For example int1="Ethernet 2" and int2"=Ethernet". Is there a way to have them fixed to the correct interface, we don't see this issue when RedHat images via HOT.

Server: type: OS::Nova::Server properties: name: Server flavor: { getparam: flavor } image: { getparam: image } availabilityzone: { getparam: availabilityzone } networks: - port: { getresource: int1 } - port: { getresource: int2 } - port: { getresource: int3 }