Hi Paul,
the OVSInterfaceDriver creates interfaces with type internal so agents like
DHCP/L3 etc can put IP addresses on them. But I don't think type internal will
work for instances. You could try subclassing and overriding so it does not do
this:
On Mar 29, 2014, at 2:02 PM, Gary Duan
garyd...@gmail.commailto:garyd...@gmail.com wrote:
I guess you need bind the port you just create.
PCM: Can you elaborate on what is needed for the binding?
In the call to create the port in Neutron, the script passes in an additional
dict item for
it helps,
Irena
From: Paul Michali (pcm) [mailto:p...@cisco.com]
Sent: Saturday, March 29, 2014 1:17 AM
To: openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] Problem plugging I/F into Neutron...
Hi,
I have a VM that I start up outside
Hi Darragh,
Can you elaborate on what the “set interface” arguments do in OVS? Just trying
to understand why it is not desired, when plugging into this interface (note I
have a management interface on the br-int and it works fine…this one, which is
also on br-int, but needs to tie to the
Hi Paul,
tbh I'm not exactly sure what you are trying to do overall. But from your
script it seems to me that you are trying to create an OVS port so a libvirt
instance outside of Nova control can use it. And you don't need the linux
bridge for security group iptables.
AFAIK the tap must be
Hi Darragh,
Yes (I should included more background), I have a VM started in KVM, and it has
I/Fs associated with scripts for I/F up and down:
IFNAME_ETH0=$NAME__mgmt
IFNAME_ETH1=$NAME__public
IFNAME_ETH2=$NAME__private
kvm -m 8192 -name $NAME \
-smp 4 \
-serial
I tinkered with the Nova create call and things are (sort of) working)…
I changed the plugging to do this:
port_id = port['port']['id']
instance = {'uuid': vm_uuid}
network = {'bridge': 'br-int'}
class VeryDangerousHack(network_model.VIF):
def __init__(self, port_id, mac_addr, network):
ok, good to hear you are making progress. From the variable names in the script
- ifname=$IFNAME_ETH2,vlan=2 - it sounds like this is a Neutron provider
network. If so, then it should be possible to bridge the VM to the link with
with a simple Linux bridge, without the need for a Neutron port
) [mailto:p...@cisco.com]
Sent: Saturday, March 29, 2014 1:17 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] Problem plugging I/F into Neutron...
Hi,
I have a VM that I start up outside of OpenStack (as a short term solution,
until we get it working inside a Nova VM), using KVM
I guess you need bind the port you just create. Also, the port need to be
plugged into the VM, right? I don't see that in the code. Maybe you are
doing it outside of OpenStack.
Thanks,
Gary
On Fri, Mar 28, 2014 at 3:15 PM, Paul Michali (pcm) p...@cisco.com wrote:
Hi,
I have a VM that I
Hi,
I have a VM that I start up outside of OpenStack (as a short term solution,
until we get it working inside a Nova VM), using KVM. It has scrips associated
with the three interfaces that are created, to hook this VM into Neutron. One
I/F is on br-ex (connected to the “public network for
11 matches
Mail list logo
