Ask Your Question

Uzi's profile - activity

2017-05-29 06:09:35 -0500 received badge  Famous Question (source)
2017-05-29 06:09:35 -0500 received badge  Notable Question (source)
2017-05-24 02:49:37 -0500 received badge  Famous Question (source)
2016-07-10 13:17:54 -0500 received badge  Popular Question (source)
2016-06-30 14:37:39 -0500 asked a question working with external dhcp and enable metadata server

Hi All

i am working in a network that requires not openstack related network DHCP because the Organization DHCP add additional information to the Instance .

however i also need the cloud-init when instantiating the instance ,so i need its routing rule that enable access to metadata server at the controller in the first place

what can i do in-order to have both "worlds" ?, is there a way for open stack to intercept incoming DHCP packets and add the meta data routing rule to them ?

thanks for your help

2016-06-06 10:34:23 -0500 received badge  Notable Question (source)
2016-06-06 10:34:23 -0500 received badge  Popular Question (source)
2016-05-06 12:51:47 -0500 received badge  Notable Question (source)
2016-05-06 12:51:47 -0500 received badge  Famous Question (source)
2016-05-06 12:51:47 -0500 received badge  Popular Question (source)
2016-01-06 05:30:36 -0500 commented question Instance creation with Local network failed when using ML2 linuxbridge mechanism driver

we found the problem both ovs witch and linuxbridge agents were running and seem that local network was handles by both , when only one agent was running all was OK

i have read that ML2 plugin implement several mechanism drivers each one pointing , so this is only if local networks not involved ?

2016-01-04 11:34:26 -0500 asked a question Instance creation with Local network failed when using ML2 linuxbridge mechanism driver

Hi All

i am working with Juno (2014.2.3) both controller and compute

the compute neutron ml2 mechanism driver is set to linuxbridge

what happen is that it success to launch instance with local network

however the taps assoicated with qbr### type of bridge instead of brq### one and the brq### bridge created with no associated ports

so if i make two VMs with same local network i am expecting to get

tapX -- brq  -- tapY

instead i get

tapX -- qbrX 
tapY -- qbrY
brq### without any ports

btw, other networks of type vlan or flat are made only with brq### bridge , as expected

of course after that i get errors that are sympthom of this such as

device tap82788db3-56 is already enslave it to bridge brqb6a9480f-cd

when creating VMs

any way to avoid making the qbr bridges and just associating two taps to same bridge in order to chain VMs ?

thanks in advance


2015-11-03 07:02:19 -0500 asked a question How can change horizon to show mac-address in instances table

Hi All

today the horizon gives list of networks and IP-address associated to instance in the instances table view

in the IP-Address column we have :


so in order to check mac-addresses corresponding to each of instance network ports , i need to check the network section

i would like to give also mac-address to this table like this :


how can i do such ? where should i look for first ?


in advance


2015-09-09 04:35:21 -0500 received badge  Famous Question (source)
2015-06-23 10:33:11 -0500 received badge  Famous Question (source)
2015-06-17 03:10:04 -0500 commented answer how do i keep vm running after compute reboot without controller accessability

thanks ! , VM is at active state i encounter with yet another problem

the OVS bridges cleared from flows when controller accessible flows re populated with the correct flows derived from VMs attached networks

can i configure the ovs/neutron to keep last flows configuration after reboot ?

2015-06-17 03:00:31 -0500 received badge  Notable Question (source)
2015-06-17 00:51:03 -0500 received badge  Popular Question (source)
2015-06-16 10:35:41 -0500 asked a question how do i keep vm running after compute reboot without controller accessability

Hi All i am using openstack Juno with Ubuntu controller/compute

there use cases when controller wont be accessible to compute ,

how do i keep the current compute nova/neutron state when such happen after i reboot the compute even if controller not accessible ? (that is keep the VMs active , keep the current neutron/ml2/ovs flows as they been )

post reboot if controller is accessible resume the VMs to active is via this nova.conf attribute



2015-06-13 09:53:16 -0500 received badge  Notable Question (source)
2015-06-11 07:35:26 -0500 answered a question Juno Controller reboot result nova compute state down

seem sysctl -w command not persistent after reboot

 #sysctl  -w net.ipv4.tcp_keepalive_intvl=1  net.ipv4.tcp_keepalive_time=5  net.ipv4.tcp_keepalive_probes=5

i had to edit the file /etc/sysctl.conf and add there the lines in

2015-06-07 19:15:47 -0500 received badge  Popular Question (source)
2015-06-07 05:52:07 -0500 commented question deleted instance running on compute

the log shows that its using this attribute value

2015-06-04 17:51:08.488 2625 DEBUG nova.openstack.common.service [-] running_deleted_instance_action = reap
2015-06-04 11:21:40 -0500 received badge  Editor (source)
2015-06-04 11:19:47 -0500 asked a question deleted instance running on compute

Hi All

i am using openstack Juno controller/compute 2014.2.2 on ubuntu 14.04

recently i have deleted 2 instances using the Dashboard successfully, however the instances still running active on the compute

when searching the nova-compute.log i have seen that the process stop from logging few minutes before the deletion took place and also service nova-compute status was running

further on as i understand there is a periodic task '_cleanup_running_deleted_instances' that should find such instances and by default (reap) will delete those instances and that it is configure to run every 1800 sec by default.

however the instances remain as active in the compute

in the controller the nova-compute service were UP

further on after restart the instances were not deleted and instead they change to shutoff

from watching the log i noticed that it detected the discrepancy but again they been only shutdown and not deleted (udefine)

my question : what is needed to be configured in order to make sure deleted instances are confirmed as deleted during run-time and start of nova-compute ?

bellow log od the nova-compute.log only from the reboot time ,not before

2015-06-04 17:51:08.488 2625 DEBUG nova.openstack.common.service [-] running_deleted_instance_action = reap log_opt_values /usr/lib/python2.7/dist-packages/oslo/config/
2015-06-04 17:51:08.488 2625 DEBUG nova.openstack.common.service [-] running_deleted_instance_poll_interval = 1800 log_opt_values /usr/lib/python2.7/dist-packages/oslo/config/
2015-06-04 17:51:08.489 2625 DEBUG nova.openstack.common.service [-] running_deleted_instance_timeout = 0 log_opt_values /usr/lib/python2.7/dist-packages/oslo/config/

2015-06-04 17:51:08.966 2625 DEBUG nova.openstack.common.service [-] ******************************************************************************** log_opt_values /usr/lib/python2.7/dist-packages/oslo/config/
2015-06-04 17:51:08.970 2625 AUDIT nova.service [-] Starting compute node (version 2014.2.1)
2015-06-04 17:51:08.973 2625 DEBUG nova.virt.libvirt.driver [-] Connecting to libvirt: qemu:///system _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2015-06-04 17:51:10.974 2625 DEBUG nova.virt.libvirt.driver [-] Registering for lifecycle events <nova.virt.libvirt.driver.LibvirtDriver object at 0x7f091253a8d0> _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2015-06-04 17:51:10.976 2625 DEBUG nova.virt.libvirt.driver [-] Registering for connection events: <nova.virt.libvirt.driver.LibvirtDriver object at 0x7f091253a8d0> _get_new_connection /usr/lib/python2.7/dist-packages/nova/virt/libvirt/
2015-06-04 17:51:10.990 2625 DEBUG nova.virt.libvirt.config [-] Generated XML ('<cpu>\n  <arch>x86_64</arch>\n  <model>Haswell</model>\n  <vendor>Intel</vendor>\n  <topology sockets="1" cores="4" threads="2"/>\n  <feature name="abm"/>\n  <feature name="acpi"/>\n  <feature name="ds"/>\n  <feature name="ds_cpl"/>\n  <feature name="dtes64"/>\n  <feature name="est"/>\n  <feature name="f16c"/>\n  <feature name="ht"/>\n  <feature name="monitor"/>\n  <feature name="osxsave"/>\n  <feature name="pbe"/>\n  <feature name="pdcm"/>\n  <feature name="pdpe1gb"/>\n  <feature name="rdrand"/>\n  <feature name="smx"/>\n  <feature name="ss"/>\n  <feature name ...
2015-05-29 04:23:31 -0500 received badge  Famous Question (source)
2015-05-28 00:18:56 -0500 received badge  Notable Question (source)
2015-05-27 15:04:58 -0500 received badge  Popular Question (source)
2015-05-27 07:28:49 -0500 asked a question Juno Controller reboot result nova compute state down

Hi All

i am checking behavior of the controller/compute system behavior after reboots

Ubuntu 14.04 / Juno / 2014.2.2

after rebooting controller it takes long time (hours) for the nova compute service to change state to UP

i managed to fix the problem by changing the Linux TCP keepalive parameters answer #18

originally was

# cat /proc/sys/net/ipv4/tcp_keepalive_time
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
# cat /proc/sys/net/ipv4/tcp_keepalive_probes

change it to

# echo 60 > /proc/sys/net/ipv4/tcp_keepalive_time
# echo 16 > /proc/sys/net/ipv4/tcp_keepalive_intvl
# echo 6 > /proc/sys/net/ipv4/tcp_keepalive_probes

this solve the problem , after controller reboot the nova compute is up

my question : is there openstack parameters that do the same effect ?

i am not so happy to change OS default parameters

thanks in advance


2015-05-26 09:13:27 -0500 asked a question Flavor creation/deletion/update notification message via rabbit


i am trying to listen for flavor notification via rabbit exchanges

i don't see any (on create or delete flavor)

is there any notification config i should add somewhere ?



2015-05-19 13:19:53 -0500 received badge  Famous Question (source)
2015-05-18 04:35:19 -0500 commented answer Kilo Error launching Instance on compute with Qemu libvirt

OK thanks a lot , the patch disable the affinity and i was able to launch an instance

2015-05-18 04:33:55 -0500 received badge  Notable Question (source)
2015-05-18 00:19:41 -0500 received badge  Popular Question (source)
2015-05-17 14:26:37 -0500 commented question Kilo Error launching Instance on compute with Qemu libvirt

Ubuntu 14.04

2015-05-17 11:55:16 -0500 asked a question Kilo Error launching Instance on compute with Qemu libvirt

Hi All

i have installed Kilo today on Ubuntu , doing the the installation as requested.

i get error launching instance , when debugging the compute nova logs i see that the libvirt XML equipped with affinity that is not supported by Qemu

Note : i am running virtual compute node on Oracle VB , that's why i am using qemu and not kvm

compute-node.conf cat is :


what can i do to disable this feature and launch instance successfully on qemu based libvirt hypervisor

thanks in advance

the nova-compute.log is as follows :

2015-05-17 19:40:42.066 2379 ERROR nova.virt.libvirt.driver [req-9a8dc8e6-acef-4f3c-b3d7-1ef9438d6416 - - - - -] Error launching a defined domain with XML:
<domain type='qemu'>
    <nova:instance xmlns:nova="">
      <nova:package version="2015.1.0"/>
      <nova:creationTime>2015-05-17 16:40:39</nova:creationTime>
      <nova:flavor name="m1.tiny">
        <nova:user uuid="1f34d4efdfa842f29bff58f7180fcc4e">admin</nova:user>
        <nova:project uuid="4832d4ebf7424422816919e90344a18b">admin</nova:project>
      <nova:root type="image" uuid="6c1ead72-cb34-413e-9407-a0febfa7c0ae"/>
  <memory unit='KiB'>524288</memory>
  <currentMemory unit='KiB'>524288</currentMemory>
  <vcpu placement='static' cpuset='0'>1</vcpu>
  <sysinfo type='smbios'>
      <entry name='manufacturer'>OpenStack Foundation</entry>
      <entry name='product'>OpenStack Nova</entry>
      <entry name='version'>2015.1.0</entry>
      <entry name='serial'>3142848b-5b53-4059-a2fb-2c75303b6980</entry>
      <entry name='uuid'>6be60fd2-4af7-45c9-b9ec-0e201f6e89ce</entry>
    <type arch='i686' machine='pc-i440fx-utopic'>hvm</type>
    <boot dev='hd'/>
    <smbios mode='sysinfo'/>
  <cpu mode='host-model'>
    <model fallback='allow'/>
    <topology sockets='1' cores='1' threads='1'/>
  <clock offset='utc'/>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/nova/instances/6be60fd2-4af7-45c9-b9ec-0e201f6e89ce/disk'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    <controller type='pci' index='0' model='pci-root'/>
    <interface type='bridge'>
      <mac address='fa:16:3e:14:9d:0d'/>
      <source bridge='qbrf1716ada-a4'/>
      <target dev='tapf1716ada-a4'/>
      <model type='virtio'/>
      <driver name='qemu'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    <serial type='file'>
      <source path='/var/lib/nova/instances/6be60fd2-4af7-45c9-b9ec-0e201f6e89ce/console.log'/>
      <target port='0'/>
    <serial type='pty'>
      <target port='1'/>
    <console type='file'>
      <source path='/var/lib/nova/instances/6be60fd2-4af7-45c9-b9ec-0e201f6e89ce/console.log'/>
      <target type='serial' port='0'/>
    <input type='tablet' bus='usb'/>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' listen='' keymap='en-us'>
      <listen type='address' address=''/>
    </graphics ...
2015-02-17 14:58:14 -0500 received badge  Famous Question (source)
2015-02-10 11:15:29 -0500 received badge  Notable Question (source)