Hi Andrea,

Though both interfaces come up, only one will response to the ping from the 
neutron router.
When I disable it, then the second one will response to ping.
So it looks like only one interface is useful at a time.

My question is is there any useful case for this, I.e. Why would you do this?

Thanks,
Danny


Date: Tue, 2 Dec 2014 10:44:57 +0000
From: Andrea Frittoli 
<andrea.fritt...@gmail.com<mailto:andrea.fritt...@gmail.com>>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [qa] Should it be allowed to attach 2
interfaces from the same subnet to a VM?
Message-ID:
<cab7wygv4+ji-tj5jkvg98kw0hxot8zlnuk+nzvjywfdijio...@mail.gmail.com<mailto:cab7wygv4+ji-tj5jkvg98kw0hxot8zlnuk+nzvjywfdijio...@mail.gmail.com>>
Content-Type: text/plain; charset=UTF-8

Hello Danny,

I think so. Any special concern with a VM using more than one port on a subnet?

andrea

On 2 December 2014 at 02:04, Danny Choi (dannchoi) 
<dannc...@cisco.com<mailto:dannc...@cisco.com>> wrote:
Hi,

When I attach 2 interfaces from the same subnet to a VM, there is no error
returned and
both interfaces come up.

lab@tme211:/opt/stack/logs$ nova interface-attach --net-id
e38dba4a-74ed-4312-ba21-2a04b5c5a5b5 cirros-1

lab@tme211:/opt/stack/logs$ nova list

+--------------------------------------+----------+--------+------------+-------------+-------------------+

| ID                                   | Name     | Status | Task State |
Power State | Networks          |

+--------------------------------------+----------+--------+------------+-------------+-------------------+

| 9d88d0b5-2453-4657-8058-987980ec7744 | cirros-1 | ACTIVE | -          |
Running     | private=10.0.0.10 |

+--------------------------------------+----------+--------+------------+-------------+-------------------+

lab@tme211:/opt/stack/logs$ nova interface-attach --net-id
e38dba4a-74ed-4312-ba21-2a04b5c5a5b5 cirros-1

lab@tme211:/opt/stack/logs$ nova list

+--------------------------------------+----------+--------+------------+-------------+------------------------------+

| ID                                   | Name     | Status | Task State |
Power State | Networks                     |

+--------------------------------------+----------+--------+------------+-------------+------------------------------+

| 9d88d0b5-2453-4657-8058-987980ec7744 | cirros-1 | ACTIVE | -          |
Running     | private=10.0.0.10, 10.0.0.11 |

+--------------------------------------+----------+--------+------------+-------------+------------------------------+


$ ifconfig

eth0      Link encap:Ethernet  HWaddr FA:16:3E:92:2D:2B

           inet addr:10.0.0.10  Bcast:10.0.0.255  Mask:255.255.255.0

           inet6 addr: fe80::f816:3eff:fe92:2d2b/64 Scope:Link

           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

           RX packets:514 errors:0 dropped:0 overruns:0 frame:0

           TX packets:307 errors:0 dropped:0 overruns:0 carrier:0

           collisions:0 txqueuelen:1000

           RX bytes:48342 (47.2 KiB)  TX bytes:41750 (40.7 KiB)


eth1      Link encap:Ethernet  HWaddr FA:16:3E:EF:55:BC

           inet addr:10.0.0.11  Bcast:10.0.0.255  Mask:255.255.255.0

           inet6 addr: fe80::f816:3eff:feef:55bc/64 Scope:Link

           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

           RX packets:49 errors:0 dropped:0 overruns:0 frame:0

           TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

           collisions:0 txqueuelen:1000

           RX bytes:3556 (3.4 KiB)  TX bytes:1120 (1.0 KiB)



Should this operation be allowed?


Thanks,

Danny


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org<mailto: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

Reply via email to