Ask Your Question

DaveJ's profile - activity

2017-08-11 03:31:34 -0500 received badge  Famous Question (source)
2017-02-27 13:54:18 -0500 received badge  Popular Question (source)
2017-02-22 20:07:05 -0500 received badge  Famous Question (source)
2017-02-22 20:07:05 -0500 received badge  Notable Question (source)
2017-02-05 23:25:59 -0500 received badge  Notable Question (source)
2017-02-05 23:25:59 -0500 received badge  Popular Question (source)
2016-11-25 11:57:41 -0500 commented answer Why is ODL adding port eth1 to br-int by default

I'm using packstack, not devstack, so their is no local.conf here.

2016-11-24 11:41:57 -0500 commented question Why is ODL adding port eth1 to br-int by default

Hi, I'm using packstack to install Newton with ODL Boron-SR1 (but got the same behavior with Berylium). Does your system function correctly? When I create VMs sometimes they get IPs via DHCP and sometimes they don't. It's very flaky.

2016-11-23 13:05:08 -0500 asked a question Why is ODL adding port eth1 to br-int by default

On my ODL and Openstack setup, after I configure the OVS switch to be managed by ODL, two bridges are created:

br-int and br-ex.

For some reason ODL seems to add port eth1 to br-int by default

ovs-vsctl show
1fb6f2bf-3386-49d0-8a1c-16191307b82f
    Manager "tcp:192.168.120.254:6640"
    Bridge br-int
        Controller "tcp:192.168.120.254:6653"
        fail_mode: secure
        Port "eth1"
            Interface "eth1"
                error: "could not open network device eth1 (No such device)"
        Port br-int
            Interface br-int
                type: internal
    Bridge br-ex
        Controller "tcp:192.168.120.254:6653"
        fail_mode: secure
        Port br-ex
            Interface br-ex
                type: internal
    ovs_version: "2.5.0"

On my setup I don't have eth1, instead its

enp0s3 enp0s8 enp0s9

I haven't configured eth1 anywhere, so why does this get added by default?

2016-11-23 12:36:26 -0500 asked a question Opendaylight API not returning routers

Hi,

I'm working on a ODL integration with Openstack. After configuring openstack, I create a network and confirm that it is correctly created. Querying ODL It returns the network details:

  curl -u admin:admin http://192.168.120.254:8080/controller/nb/v2/neutron/networks
{
   "networks" : [ {
      "id" : "12112860-d04e-44e4-b5d1-727989a45e4a",
      "tenant_id" : "1ae7a1d4d54c40b5abcaaa8fc8389fe3",
      "name" : "private_network",
      "admin_state_up" : true,
      "shared" : false,
      "router:external" : false,
      "provider:network_type" : "vxlan",
      "provider:segmentation_id" : "92",
      "status" : "ACTIVE",
      "segments" : [ ]
   } ]
}

Next I create a router in Openstack and add an interface from the network. When I query ODL it doesn't return anything:

 curl -u admin:admin http://192.168.120.254:8080/controller/nb/v2/neutron/routers
{
   "routers" : [ ]
}

Is this expected behavior, or does it indicate a problem with the ODL / Openstack setup.

2016-11-23 05:42:10 -0500 commented answer Could not load 'opendaylight': No module named opendaylight.driver

N.B I repeated a fresh install with packstack. This time I installed networking_odl using yum, and there was no need to merge the entry_points txt file, so if using packstack install using rpms rather than pip.

2016-11-22 02:38:42 -0500 received badge  Popular Question (source)
2016-11-21 15:33:03 -0500 answered a question Could not load 'opendaylight': No module named opendaylight.driver

I eventually resolved this, by merging the contents of /usr/lib/python2.7/site-packages/networking_odl-2.0.1-py2.7.egg-info/entry_points.txt with /usr/lib/python2.7/site-packages/neutron-9.0.0-py2.7.egg-info/entry_points.txt

After restarting neutron-server it worked.

I'm not sure if there is a formal way to register a new entry_points file.

2016-11-21 11:12:50 -0500 asked a question Could not load 'opendaylight': No module named opendaylight.driver

Hi, I'm trying to integrate a Openstack install based on RDO Newton and Opendaylight Beryllium-SR4.

I have reconfigure neutron server to use opendaylight instead of openvswitch, but after starting neutron-server I see a 'Could not load opendaylight' error in the logs:

2016-11-21 16:57:44.349 22450 INFO neutron.plugins.ml2.managers [-] Configured mechanism driver names:['opendaylight'] 
2016-11-21 16:57:44.349 22450 ERROR stevedore.extension [-] Could not load 'opendaylight': No module named opendaylight.driver 
2016-11-21 16:57:44.350 22450 WARNING stevedore.named [-] Could not load opendaylight 
2016-11-21 16:57:44.350 22450 INFO neutron.plugins.ml2.managers [-] Loaded mechanism driver names: [] 
2016-11-21 16:57:44.350 22450 INFO neutron.plugins.ml2.managers [-] Registered mechanism drivers: []

I've installed networking_odl using pip, but this hasn't helped. Any ideas on how to resolve this?

The default ml2 plugins such as openvswitch are installed under: /usr/lib/python2.7/site-packages/neutron/plugins/ml2/drivers/openvswitch

But networking_odl gets installed under: /usr/lib/python2.7/site-packages/networking_odl/ml2

Could this be part of the problem?

2016-11-07 06:45:40 -0500 received badge  Famous Question (source)
2016-11-07 06:45:40 -0500 received badge  Notable Question (source)
2016-08-17 23:11:29 -0500 received badge  Great Question (source)
2016-08-10 10:40:03 -0500 received badge  Famous Question (source)
2016-07-10 21:20:51 -0500 received badge  Popular Question (source)
2016-06-14 09:33:56 -0500 asked a question Cant export volume snapshot as Image

I want to back up some vms externally. I used to do this by snapshotting and saving the image from glance. When I used volume backed instances this doesn't seem to work.

I have deployed Openstack with Cinder. When I boot an instance, I select boot from image (Creates new volume)

After making changes to the instance, I hit create snapshot. This creates a snapshot visible under the volumes page in horizon, and also creates an entry in the glance image list.

If I try to save/export that image from glance I get a file with 0 bytes i.e.

openstack image save 84b481fe-aeec-4d36-9ebd-8e2df286c82c --file /tmp/test.img ls -l /tmp/test

Is this a bug with cinder ? Or am I missing some vital command or flag?

2015-12-10 13:00:09 -0500 received badge  Famous Question (source)
2015-10-26 03:34:08 -0500 received badge  Famous Question (source)
2015-09-30 03:50:55 -0500 received badge  Taxonomist
2015-09-21 09:47:33 -0500 received badge  Famous Question (source)
2015-09-04 05:06:43 -0500 received badge  Famous Question (source)
2015-07-17 04:09:16 -0500 commented question How to implement openstack using 2/3 nodes

This should be perfectly possible. How many network interfaces do your laptops have? Two would be ideal. Also how will they connected? I assume using a fairly low end hub/switch. Can it carry VLAN tagged traffic?

2015-07-17 04:07:59 -0500 answered a question How to implement openstack using 2/3 nodes

Hi Yes it is.

Follow this quickstart guide to perform an all in one install: https://www.rdoproject.org/Quickstart Once your happy with that, you can then extend it to use multiple nodes.

Heres some detail:

Openstack typically consists of these logical components

  • controller (where the APIs run)
  • 1 or more compute nodes (usually a hypervisor)

You can place these on separate nodes, or combine them all in one. If you have never installed Openstack before, I would suggest you start with an 'AllInOne'. You can do this on a bare-metal machine or with VirtualBox.

With my Thinkpad laptop with an i5 CPU and 8GB RAM I have Fedora installed. Using VirtualBox I can create two VMs and install Openstack on top of that.
This is sufficient to boot the test image 'cirros' and demonstrate basic networking connectivity between VMs.

To get started with RDO, install Fedora 21/CentOS 7 on a baremetal or virtual machine, and run these commands (as root or with sudo permissions)

systemctl stop NetworkManager
systemctl disable NetworkManager
systemctl enable network

Change SELinux to run in permissive mode i.e. edit /etc/selinux/config so it looks like this:

SELINUX=permissive
SELINUXTYPE=targeted

Execute the following:

setenforce 0
yum update -y
yum install -y https://rdoproject.org/repos/rdo-release.rpm
yum install -y openstack-packstack
packstack --allinone

At the end of the install it shuold print the address where you can login to the installed Openstack system.

2015-07-03 08:21:15 -0500 received badge  Famous Question (source)
2015-06-26 07:21:04 -0500 received badge  Popular Question (source)
2015-06-26 07:21:04 -0500 received badge  Notable Question (source)
2015-06-17 05:45:53 -0500 received badge  Nice Answer (source)
2015-06-17 00:13:56 -0500 answered a question Linux Distros with Pre-Installed OpenStack

I'm not aware of other distros that provide this option. That said you can easily achieve what you want with a kickstart file (SuSE and Debian based distros have an equivalent).

The kickstart defines what should be installed and allows you to automate a OS install. You can execute any commands or scripts you like from that file, so you could call devstack or packstack all in one.

To bundle it in a ISO you just need to mount an existing install media, add the kickstart and modify the relevant grub entry to pass that kickstart file to the installer. You can then save that ISO.

Is an ISO essential or would pxe booting work for you ?

2015-06-14 15:52:04 -0500 received badge  Famous Question (source)
2015-06-11 09:09:39 -0500 received badge  Notable Question (source)
2015-06-10 20:04:49 -0500 received badge  Popular Question (source)
2015-06-10 05:14:01 -0500 received badge  Editor (source)
2015-06-10 05:13:22 -0500 asked a question which version of QEMU supports Per Node memory Binding (NUMA Pinning on Kilo)

Hi, I've been trying to enable cpu pinning on Kilo, with CentOS 7.

Unforutenaly I get an error when trying to launch the instance:

libvirtError: internal error: process exited while connecting to monitor: 2015-06-10T09:02:21.558766Z qemu-kvm: -object memory-backend-ram,size=8192M,id=ram-node0,host-nodes=0,policy=bind: **NUMA node binding are not supported by this QEMU**

I've tried a few versions of libvirt now including 1.2.8, 1.2.9 and 1.2.11.

Does anyone know of pre built packages that will provide these features on CentOS 7.

N.B currently using the packages from here:

https://repos.fedorapeople.org/repos/...

2015-06-10 02:22:01 -0500 received badge  Notable Question (source)
2015-06-10 02:19:00 -0500 received badge  Notable Question (source)
2015-06-10 02:19:00 -0500 received badge  Popular Question (source)
2015-06-09 10:21:02 -0500 received badge  Popular Question (source)
2015-06-09 03:28:54 -0500 asked a question where to get libvirt 1.2.9 for CentOS 7

Hi, I've been trying to use the NUMA pinning features available in Kilo running on CentOS 7.1, but unfortunately I get the following error:

libvirtError: unsupported configuration: Per-node memory binding is not supported with this QEMU

I can't find supported packages for libvirt 1.2.9 on CentOS. Does anyone have an offical repo or build?

2015-06-09 03:08:09 -0500 commented answer libvirt issue on CentOS 7 with Kilo

Hi, Where did you get libvirt 1.2.9 from? The stock version for CentOS seems to be 1.2.8. I actually need 1.2.9 myself, so I was wondering what repos you are using?

2015-06-08 16:04:29 -0500 received badge  Notable Question (source)
2015-06-04 08:50:11 -0500 answered a question sriov vif binds to wrong device

I'm not sure if the issue is related to this: https://bugs.launchpad.net/nova/+bug/...

I was able to work around it by changing my whitelist configuration to specify the device name:

pci_passthrough_whitelist = {"devname":"ens2f0","physical_network":"physnet1"}

Where devname = port 0 of my card.

Interestingly now the port seems to get attached to a PCI address | binding:profile | {"pci_slot": "0000:07:11.6", "physical_network": "physnet1", "pci_vendor_info": "8086:10ed"} |

When I do ip link show I can see it attached to the last vf of port 0

ip link show ens2f0
5: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode     DEFAULT qlen 1000
link/ether 90:e2:ba:40:8c:ec brd ff:ff:ff:ff:ff:ff
vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
...
...
vf 7 MAC fa:16:3e:25:29:eb, vlan 522, spoof checking on, link-state auto
2015-06-04 07:40:10 -0500 asked a question sriov vif binds to wrong device

Hi,

When I launch a VM with an SR-IOV port, the vif binds to the wrong PCI device (it seems to ignore the whitelist rules)

I'm using RDO (Kilo) and have enabled SR-IOV as per https://wiki.openstack.org/wiki/SR-IO.... The hardware is HP DL360G8 with Intel 82599 10G cards.

Specifically I did the following:

Controller

edited /etc/neutron/plugins/ml2/ml2_conf.ini and set the following

  • type_drivers =local,flat,vlan,gre,vxlan
  • tenant_network_types = flat,vlan,gre,vxlan
  • mechanism_drivers =openvswitch,sriovnicswitch

edited /etc/neutron/plugins/ml2/ml2_conf_sriov.ini: - supported_pci_vendor_devs = 8086:10fb, 8086:10ed

Compute

edited /etc/nova/nova.conf and set the pci white list - pci_passthrough_whitelist = {"address":":07:10.","physical_network":"physnet1"}

N.B I got the address from lspci. My cards has two ports, and only one is connected (the first). when I execute lspci -nn | grep 82599 I see the following

lspci -nn | grep 82599
  07:00.0 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
  07:00.1 Ethernet controller [0200]: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection [8086:10fb] (rev 01)
  07:10.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
  07:10.1 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
  07:10.2 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
  ..... 
  07:11.0 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
  07:11.1 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)
  ....
  07:11.7 Ethernet controller [0200]: Intel Corporation 82599 Ethernet Controller Virtual Function [8086:10ed] (rev 01)

So when I create a direct port, I would expect it to bind to a PCI device that has the address 07:10.* and not the 07:11.* When I use neutron port show the binding profile looks correct:

neutron port-show 030575a1-b3f8-461e-ac06-18371de87cca

| binding:profile | {"pci_slot": "0000:07:10.7", "physical_network": "physnet1", "pci_vendor_info": "8086:10ed"} | | binding:vif_details | {"port_filter": false, "vlan": "522"} | | binding:vif_type | hw_veb | | binding:vnic_type | direct |

Based on this, I believed it would bind to pci_slot": "0000:07:10.7",

On the compute node, when I do ip link show, it shows that it is actually connecting to a different device. N.B my device has two porrts ens2f0 (connected) and ens2f1 (not connected)

ip link show ens2f0
6: ens2f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master ovs-system state UP mode DEFAULT qlen 1000
link/ether 90:e2:ba:49:b2:28 brd ff:ff:ff:ff:ff:ff
  vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
  vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
  vf 2 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
  vf 3 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
  vf 4 MAC 00:00:00:00 ...
(more)