Ask Your Question

jzwiep's profile - activity

2015-07-01 20:02:43 -0500 received badge  Famous Question (source)
2014-06-25 05:58:43 -0500 received badge  Notable Question (source)
2014-06-25 05:58:43 -0500 received badge  Popular Question (source)
2014-02-26 00:36:24 -0500 received badge  Famous Question (source)
2014-02-03 17:12:59 -0500 received badge  Popular Question (source)
2014-02-03 17:12:59 -0500 received badge  Notable Question (source)
2014-01-29 13:49:40 -0500 asked a question Unable to delete instances in 'ERROR' state

Every so often we'll be unable to delete 'ERROR'd instances on our OpenStack havana deployment. When trying to delete the instance in question, the following appears in /var/log/nova/nova-compute.log on the instance's host:

    2014-01-29 11:41:00.970 11857 AUDIT nova.compute.manager [req-36e7198e-006e-4462-9f02-d8dc8f88389f 650e1218f88341e882c24bb98aba5425 c9de2ba323d8459aae4106cb048f2743] [instance: 8c6c0227-1b55-4075-b2b5-3666bb7d4164] Terminating instance
    2014-01-29 11:41:01.204 11857 ERROR nova.virt.libvirt.driver [-] [instance: 8c6c0227-1b55-4075-b2b5-3666bb7d4164] During wait destroy, instance disappeared.
    2014-01-29 11:41:01.207 11857 INFO nova.virt.libvirt.firewall [req-36e7198e-006e-4462-9f02-d8dc8f88389f 650e1218f88341e882c24bb98aba5425 c9de2ba323d8459aae4106cb048f2743] [instance: 8c6c0227-1b55-4075-b2b5-3666bb7d4164] Attempted to unfilter instance which is not filtered
    2014-01-29 11:41:01.400 11857 INFO nova.virt.libvirt.driver [req-36e7198e-006e-4462-9f02-d8dc8f88389f 650e1218f88341e882c24bb98aba5425 c9de2ba323d8459aae4106cb048f2743] [instance: 8c6c0227-1b55-4075-b2b5-3666bb7d4164] Deletion of /var/lib/nova/instances/8c6c0227-1b55-4075-b2b5-3666bb7d4164 complete

Then after a short wait, we see an RPC timeout appear in the logs:

2014-01-29 11:42:01.511 11857 ERROR nova.compute.manager [req-36e7198e-006e-4462-9f02-d8dc8f88389f 650e1218f88341e882c24bb98aba5425 c9de2ba323d8459aae4106cb048f2743] [instance: 8c6c0227-1b55-4075-b2b5-3666bb7d4164] Failed to deallocate network for instance.
2014-01-29 11:42:02.170 11857 ERROR nova.openstack.common.rpc.amqp [req-36e7198e-006e-4462-9f02-d8dc8f88389f 650e1218f88341e882c24bb98aba5425 c9de2ba323d8459aae4106cb048f2743] Exception during message handling
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp Traceback (most recent call last):
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py", line 461, in _process_data
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     **args)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py", line 172, in dispatch
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     result = getattr(proxyobj, method)(ctxt, **kwargs)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 353, in decorated_function
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     return function(self, context, *args, **kwargs)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 90, in wrapped
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     payload)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/exception.py", line 73, in wrapped
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     return f(self, context, *args, **kw)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 243, in decorated_function
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     pass
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 229, in decorated_function
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp     return function(self, context, *args, **kwargs)
2014-01-29 11:42:02.170 11857 TRACE nova.openstack.common.rpc.amqp ...
(more)
2014-01-23 18:41:35 -0500 marked best answer Mounting Config Drive on a Windows 2008 Guest?

In our setup we can't use HTTP metadata, so config drive is really our only option for metadata. Unfortunately Windows seems to have only started supporting ISO9660 drive formats with Windows 2012.

Is there any way to mount this under Windows (third-pary or native)? Currently Windows can see the disk, but only shows it as unallocated.

2013-11-01 20:47:28 -0500 received badge  Nice Question (source)
2013-10-30 04:21:06 -0500 received badge  Famous Question (source)
2013-10-11 18:58:35 -0500 asked a question Multiple monitors attached to one OpenStack VM?

Is there some way to attach more than one display device to a VM with openstack?

We're looking for some way to do this, preferably using KVM as our hypervisor, but Google hasn't returned much in the way of useful information.

2013-08-20 10:37:41 -0500 received badge  Notable Question (source)
2013-08-20 10:37:41 -0500 received badge  Popular Question (source)
2013-07-24 21:01:53 -0500 answered a question Creating a network without NAT in essex

These nova.conf network options, specifically the dmz_cidr solved the issue:

# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--libvirt_use_virtio_for_bridges=true
--flat_interface=eth0
--flat_network_bridge=br100
--flat_injected=False
--fixed_range=10.10.38.0/24
--dmz_cidr=10.10.32.0/21

https://answers.launchpad.net/nova/+question/185826

2013-07-24 21:00:19 -0500 received badge  Famous Question (source)
2013-07-24 20:59:05 -0500 answered a question Using OpenStack with existing LAN Network

Managed to fix it.

I corrected the fixed_range in nova.conf to match nova's network, and added this config option:

--dmz_cidr=10.10.32.0/21

This stops VM traffic from getting SNATTED (https://answers.launchpad.net/nova/+question/185826)

2013-07-24 20:47:41 -0500 answered a question VMs on Controller Node can't properly send/recieve broadcasts

Managed to fix it.

I corrected the fixed_range in nova.conf to match nova's network, and added this config option:

--dmz_cidr=10.10.32.0/21

This stops VM traffic from getting SNATTED (https://answers.launchpad.net/nova/+question/185826)

2013-07-22 14:23:12 -0500 asked a question VMs on Controller Node can't properly send/recieve broadcasts

On our private OpenStack essex cloud (single host, flatDHCP networking), VMs spawned on the controller can't properly send or receive broadcasts (looks like a NAT), while VMs spawned on the compute nodes don't experience any issues at all.

We have two independent networks:

Network 1: 10.10.32.0/21

Network 2: 10.10.20.0/23

and the VMs are all connected to 'network 1' and are given addresses in the subnet 10.10.38.0/24. When a broadcast is sent from a VM on the controller node, machines on 'network 1' see it as being sent from the controller's 'network 2' interface address. Simlararly, when a broadcast is sent from a machine on 'network 1' a VM on the controller node will see it as being sent from the controller's 'network 2' interface address.

This does not happen at all on the compute node guests.

Our config setup:

/etc/network/interfaces (eth0 is connected to 'network 1', eth1 to 'network 2')

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

auto lo
iface lo inet loopback

# eth0 is not defined here, because it is used in the bridge
auto eth1
iface eth1 inet dhcp

auto eth0
iface eth0 inet dhcp

auto br100
iface br100 inet dhcp
        bridge_ports eth0
        bridge_stp off
        bridge_maxwait 0
        bridge_fd 0

/etc/nova/nova.conf

--sql_connection=mysql://novadbadmin:novasecret@10.10.33.233/nova
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/run/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
--scheduler_available_filters=nova.scheduler.filters.standard_filters
--scheduler_default_filters=AvailabilityZoneFilter,RamFilter,ComputeFilter,CoreFilter
--cpu_allocation_ratio=1.0
--s3_host=10.10.33.233
--ec2_host=10.10.33.233
--cc_host=10.10.33.233
--nova_url=http://10.10.33.233:8774/v1.1/
--glance_api_servers=10.10.33.233:9292
--image_service=nova.image.glance.GlanceImageService
--ec2_url=http://10.10.33.233:8773/services/Cloud
--keystone_ec2_url=http://10.10.33.233:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--multi_host=true
--iscsi_helper=tgtadm
--root_helper=sudo nova-rootwrap
--verbose
--connection_type=libvirt
--libvirt_type=kvm
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--rpc_response_timeout=3600

# vnc specific configuration
--novnc_enabled=true
--novncproxy_base_url=http://10.10.33.233:6080/vnc_auto.html
--vncserver_proxyclient_address=10.10.33.233
--vncserver_listen=10.10.33.233

# network specific settings
--network_manager=nova.network.manager.FlatDHCPManager
--libvirt_use_virtio_for_bridges=true
--fixed_range=10.10.32.0/21
--flat_interface=eth0
--flat_network_bridge=br100
--flat_injected=False

# RabbitMQ settings
--rabbit_host=10.10.33.233

# Metadata settings
--metadatahost=10.10.33.233

iptables for instance on controller

Chain nova-compute-inst-229 (1 references)
target     prot opt source               destination
DROP       all  --  anywhere             anywhere             state INVALID
ACCEPT     all  --  anywhere             anywhere             state RELATED,ESTABLISHED
nova-compute-provider  all  --  anywhere             anywhere
ACCEPT     udp  --  10.10.38.1           anywhere             udp spt:bootps dpt:bootpc
ACCEPT     all  --  10.10.38.0/24        anywhere
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:3389
ACCEPT     icmp --  anywhere             anywhere
ACCEPT     tcp  --  anywhere             anywhere             multiport dports 50080:50110
ACCEPT     udp ...
(more)
2013-07-06 20:31:57 -0500 received badge  Nice Question (source)
2013-05-27 02:24:31 -0500 received badge  Famous Question (source)
2013-05-22 08:14:57 -0500 received badge  Famous Question (source)
2013-05-20 02:42:09 -0500 received badge  Notable Question (source)
2013-05-18 12:50:18 -0500 commented answer Using OpenStack with existing LAN Network

I actually did find and follow that exactly while trying our initial configuration. It caused almost everything to work correctly except for VMs being able to ping outside of their subnet. Do you think that switching to Folsom or Grizzly would fix that?

2013-05-18 02:59:07 -0500 received badge  Popular Question (source)
2013-05-17 19:59:55 -0500 commented answer Creating a network without NAT in essex

Hmm, yeah. I'm not sure this fixes our problem. Thanks though.

2013-05-17 19:56:52 -0500 commented question Using OpenStack with existing LAN Network

Essex is just what the current system happens to be running. Upgrading is definitely possible though. What kind of changes made in Folsom/Grizzly make this setup easier?

2013-05-17 08:06:48 -0500 received badge  Notable Question (source)
2013-05-16 19:59:02 -0500 asked a question Using OpenStack with existing LAN Network

We'd like to have OpenStack integrated with our existing LAN network. We want to assign a subnet not managed by our network's DHCP to nova-network. Right now, VMs spawn and aquire their addresses fine, but they can't ping any addresses outside of their subnet.

So we can ping other VMs, we can ping the compute/controller hosts, we can ping other machines that are assigned an address in the VM Subnet, machines can ping VMs, but we just can't get the VMs to be able to ping addresses outside of both their subnet and the OpenStack setup.

Any help would be greatly appreciated!

Our current setup:

OpenStack Essex

Network: 10.10.32.0/21

VM Subnet: 10.10.38.0/24

nova.conf

--sql_connection=mysql://novadbadmin:novasecret@10.10.33.52/nova
--dhcpbridge_flagfile=/etc/nova/nova.conf
--dhcpbridge=/usr/bin/nova-dhcpbridge
--logdir=/var/log/nova
--state_path=/var/lib/nova
--lock_path=/run/lock/nova
--allow_admin_api=true
--use_deprecated_auth=false
--auth_strategy=keystone
--scheduler_driver=nova.scheduler.filter_scheduler.FilterScheduler
--scheduler_available_filters=nova.scheduler.filters.standard_filters
--ram_allocation_ratio=0.85
--s3_host=10.10.33.52
--ec2_host=10.10.33.52
--cc_host=10.10.33.52
--nova_url=http://10.10.33.52:8774/v1.1/
--glance_api_servers=10.10.33.52:9292
--image_service=nova.image.glance.GlanceImageService
--ec2_url=http://10.10.33.52:8773/services/Cloud
--keystone_ec2_url=http://10.10.33.52:5000/v2.0/ec2tokens
--api_paste_config=/etc/nova/api-paste.ini
--iscsi_helper=tgtadm
--root_helper=sudo nova-rootwrap
--verbose
--connection_type=libvirt
--libvirt_type=kvm
--start_guests_on_host_boot=true
--resume_guests_state_on_host_boot=true
--rpc_response_timeout=3600

# vnc specific configuration
--novnc_enabled=true
--novncproxy_base_url=http://10.10.33.52:6080/vnc_auto.html
--vncserver_proxyclient_address=10.10.33.52
--vncserver_listen=10.10.33.52

# network specific settings
--network_manager=nova.network.manager.FlatManager
--libvirt_use_virtio_for_bridges=true
--flat_network_bridge=br100
--flat_interface=eth0
--flat_injected=False
--fixed_range=10.10.38.0/24

# RabbitMQ settings
--rabbit_host=10.10.33.52

interfaces

auto lo
iface lo inet loopback

auto eth1
iface eth1 inet dhcp

auto eth0
iface eth0 inet dhcp

auto br100
iface br100 inet dhcp
        bridge_stp off
        bridge_fd 0

Network

sudo nova-manage network create camera_network --fixed_range_v4=10.10.38.0/24 --bridge_interface=br100 --num_networks=1 --network_size=256

ifconfig

br100     Link encap:Ethernet  HWaddr 3a:7c:6e:51:bf:1f
          inet addr:10.10.38.1  Bcast:10.10.38.255  Mask:255.255.255.0
          inet6 addr: fe80::387c:6eff:fe51:bf1f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:1328 (1.3 KB)

eth0      Link encap:Ethernet  HWaddr d4:ae:52:bb:9f:2c
          inet addr:10.10.33.52  Bcast:10.10.39.255  Mask:255.255.248.0
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:3845153 errors:0 dropped:237 overruns:0 frame:0
          TX packets:446 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3487867583 ...
(more)
2013-05-12 07:55:23 -0500 received badge  Popular Question (source)
2013-05-10 18:50:43 -0500 received badge  Taxonomist
2013-04-30 06:37:43 -0500 received badge  Notable Question (source)
2013-04-29 13:10:40 -0500 received badge  Organizer (source)
2013-04-29 13:04:25 -0500 asked a question Creating a network without NAT in essex

We're looking for a way to configure OpenStack so that it assigns ip addresses from a given subnet of our internal network without any NAT rules in place.

Currently we use a similar setup as outlined here:

http://dijks.wordpress.com/2012/07/06/32/

It essentially disables nova-network, and allows an external DHCP server to assign ip addresses to the instances. This works, but it breaks major functionality within OpenStack (like parts of the api, and metadata) and it makes using the system a pain.

Is a NAT free network possible under essex?

2013-04-29 12:49:01 -0500 answered a question Trying to integrate VMs to existing LAN

Heres a solution that worked for us in Essex (not sure about Folsom):

http://dijks.wordpress.com/2012/07/06/32/

Basically, it involves essentially disabling nova-network via editing the libvirt.xml.template file. The major downside to this 'fix' is that OpenStack's api will no longer be aware of each instances ip address, and so things like HTTP metadata break.

2013-04-22 11:43:40 -0500 received badge  Famous Question (source)
2013-04-18 12:01:18 -0500 received badge  Scholar (source)
2013-04-18 12:01:17 -0500 received badge  Supporter (source)
2013-04-16 03:37:44 -0500 received badge  Notable Question (source)
2013-04-12 10:21:11 -0500 received badge  Popular Question (source)
2013-04-10 18:42:28 -0500 received badge  Editor (source)
2013-04-10 18:40:55 -0500 asked a question Is there a way to configure OpenStack network without a NAT in Grizzly?

I'm looking for some way to config OpenStack's networking without a NAT using Grizzly. Each VM needs to be fully integrated into our current network, and should preferably use our own DHCP server.

Currently I achieved this in Essex by 'disabling' nova-network: modified libvirt.xml.template, and defined a bridge to our network on each compute node interface. (http://dijks.wordpress.com/2012/07/06/32/)

I'd like to have similar capabilities with Grizzly, though ideally with a much 'cleaner' method.

Has anyone done something similar?