Ask Your Question

dgalvao's profile - activity

2015-07-24 09:00:02 -0500 received badge  Famous Question (source)
2015-03-31 00:47:22 -0500 received badge  Nice Answer (source)
2015-02-18 03:24:56 -0500 received badge  Famous Question (source)
2014-12-27 08:11:47 -0500 received badge  Notable Question (source)
2014-12-27 08:11:47 -0500 received badge  Popular Question (source)
2014-12-22 11:01:45 -0500 answered a question How to connect plain Hard drive to compute node?

If you have cinder installed in that node, you need to create a pv in that disk, then add it to the existing cinder-volumes volume group with vgextend (see http://docs.openstack.org/juno/instal... and http://rgheck.blogspot.com/2012/07/ho... ).

That works if you want to add additional volumes to your virtual machines.

If you are asking about the primary disk for virtual machines, they typically go in /var/lib/nova/instances. Likewise you can simply add that disk to whatever volume group contains /var/lib/nova/instances and then use lvextend, and resize2fs. Or you could format a new filesystem and mount /var/lib/nova/instances in the new disk.

2014-12-02 11:08:05 -0500 answered a question trying to create a volume in cinder

Looks like your block1 host cannot reach the messaging server (rabbit).

Check /etc/cinder/cinder.conf for the rabbit settings (IP address, and password), and ensure the rabbit host is allowing connections from the block1 host (make sure there isn't a firewall blocking that connection).

2014-12-01 12:10:14 -0500 answered a question Where can I find documentation for OpenStack on Xen hypervisor?
2014-11-26 12:02:23 -0500 commented answer vm can't access external network with vlan on physical interface

You need to ensure the interfaces are in promiscuous mode. All instances and neutron routers will have mac addresses different than the mac addresses in the physical interfaces. If promiscuous mode is disabled the interfaces will drop all those frames.

2014-11-26 09:22:46 -0500 answered a question vm can't access external network with vlan on physical interface

I have a similar setup and it's working. Did you enable promiscuous mode, in the interface configs?

$ ls ifcfg-eth2*
ifcfg-eth2  ifcfg-eth2.38  ifcfg-eth2.40
$ ls ifcfg-eth2* | while read line; do cat $line; echo "--------"; done
DEVICE=eth2
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
PROMISC=yes
--------
DEVICE=eth2.38
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
VLAN=yes
PROMISC=yes
--------
DEVICE=eth2.40
TYPE=Ethernet
BOOTPROTO=none
ONBOOT=yes
VLAN=yes
PROMISC=yes
--------
2014-11-25 16:09:10 -0500 received badge  Notable Question (source)
2014-11-21 13:28:32 -0500 answered a question Instance in error status after failed migrate

Fixed this issue by changing the nova user shell from /sbin/nologin to /bin/bash

2014-11-21 11:50:40 -0500 asked a question Instance in error status after failed migrate

I have a Juno environment with four nodes: controller node (in a VM) and neutron, nova-compute-1 and nova-compute-2 on real servers.

I'm able to live migrate instances from compute-1 to compute-2 and vice-versa, but when I choose the "migrate" option in dashboard (instead of "live migrate"), the migrate fails and the instance goes into an error status that I can't find a way to recover from.

For example, starting with an instance running on node compute-2:

This is the error:

"Error:  Failed to launch instance "test-c97c5b3d-fb91-4e7f-8981-61d1743a0edb": Please try again later [Error: Unexpected error while running command. Command: ssh <ip of compute-1> mkdir -p /var/lib/nova/instances/c97c5b3d-fb91-4e7f-8981-61d1743a0edb Exit code: 1 Stdout: u'This account is currently not available.\n' Stderr: u'******************************************]."   <-- this seems to be because the default shell for nova is /sbin/nologin

I tried nova reset-state and that won't recover the status. I can still ssh and see the console, so the VM is up, but because the instance is now in error state, the dashboard options are limited.

nova show c97c5b3d-fb91-4e7f-8981-61d1743a0edb

+--------------------------------------+--------------------------------------------------------------------------------------------------------+
| Property                             | Value                                                                                                  |
+--------------------------------------+--------------------------------------------------------------------------------------------------------+
| OS-DCF:diskConfig                    | AUTO                                                                                                   |
| OS-EXT-AZ:availability_zone          | nova                                                                                                   |
| OS-EXT-STS:power_state               | 1                                                                                                      |
| OS-EXT-STS:task_state                | -                                                                                                      |
| OS-EXT-STS:vm_state                  | error                                                                                                  |
| OS-SRV-USG:launched_at               | 2014-11-21T17:41:04.000000                                                                             |
| OS-SRV-USG:terminated_at             | -                                                                                                      |
| accessIPv4                           |                                                                                                        |
| accessIPv6                           |                                                                                                        |
| config_drive                         |                                                                                                        |
| created                              | 2014-11-21T17:40:46Z                                                                                   |
| dev-internal network                 | 192.168.1.12, 10.x.x.x                                                                             |
| fault                                | {"message": "Unexpected error while running command.                                                   |
|                                      | Command: ssh 10.x.x.x mkdir -p /var/lib/nova/instances/c97c5b3d-fb91-4e7f-8981-61d1743a0edb        |
|                                      | Exit code: 1                                                                                           |
|                                      | Stdout: u'This account is currently not available.\                                                    |
|                                      | '                                                                                                      |
|                                      | Stderr: u'******************************************", "code": 500, "created": "2014-11-21T17:42:54Z"} |
| flavor                               | m1.tiny (1)                                                                                            |
| hostId                               | 3d65aa27b9b5b98e90d25ac3cd3ffa5abeb826e7500f8e4f3696c13c                                               |
| id                                   | c97c5b3d-fb91-4e7f-8981-61d1743a0edb                                                                   |
| image                                | cirros-0.3.3-x86_64 (f577a8fc-6cfe-4a3e-9cb1-f78d6880dde1)                                             |
| key_name                             | -                                                                                                      |
| metadata                             | {}                                                                                                     |
| name                                 | test-c97c5b3d-fb91-4e7f-8981-61d1743a0edb                                                              |
| os-extended-volumes:volumes_attached | []                                                                                                     |
| security_groups                      | default                                                                                                |
| status                               | ERROR                                                                                                  |
| tenant_id                            | d125de30bb1a42ec8586615b5eb27ab7                                                                       |
| updated                              | 2014-11-21T17:42:54Z                                                                                   |
| user_id                              | 68c51e8e08f84bb1b84101dcf45396c8                                                                       |
+--------------------------------------+--------------------------------------------------------------------------------------------------------+

Has anyone seen this migrate issue before? Or, how can I recover the instance from the error status?

Thanks!

2014-11-20 18:57:29 -0500 answered a question add a compute node in juno

I liked the RDO instructions for a proof of concept and for getting something up and running quickly with packstack, but I now much prefer the Openstack foundation instructions: http://docs.openstack.org/juno/instal...

I think the openstack foundation instructions take longer to follow but give you a better understanding of how all the different components work together. I've been setting up an environment and just today I deployed a second computing node, and it was very easy.

2014-11-20 13:33:08 -0500 received badge  Popular Question (source)
2014-11-20 09:44:35 -0500 received badge  Scholar (source)
2014-11-20 09:44:24 -0500 commented answer No instance console when using dashboard with SSL

Thanks! That worked. I had to change that in the compute node as well, and also added a few more settings, like:

ssl_only=true cert=/path/to/certfile key=/path/to/keyfile

2014-11-19 15:34:06 -0500 asked a question No instance console when using dashboard with SSL

Hi there,

I have OpenStack Juno up and running on a few CentOS 7 nodes. I installed the dashboard on the controller node and all works well. However, when I access the dashboard via SSL I'm no longer able to access the instance console. Just shows a white area where the console would be.

Any ideas?

Thanks!

2014-11-18 02:57:09 -0500 received badge  Student (source)
2014-11-17 14:25:34 -0500 received badge  Supporter (source)
2014-11-17 11:08:06 -0500 answered a question Improving neutron openvswitch performance

From http://docs.openstack.org/juno/instal... :

" Tunneling protocols such as GRE include additional packet headers that increase overhead and decrease space available for the payload or user data. Without knowledge of the virtual network infrastructure, instances attempt to send packets using the default Ethernet maximum transmission unit (MTU) of 1500 bytes. Internet protocol (IP) networks contain the path MTU discovery (PMTUD) mechanism to detect end-to-end MTU and adjust packet size accordingly. However, some operating systems and networks block or otherwise lack support for PMTUD causing performance degradation or connectivity failure.

Ideally, you can prevent these problems by enabling jumbo frames on the physical network that contains your tenant virtual networks. Jumbo frames support MTUs up to approximately 9000 bytes which negates the impact of GRE overhead on virtual networks. However, many network devices lack support for jumbo frames and OpenStack administrators often lack control over network infrastructure. Given the latter complications, you can also prevent MTU problems by reducing the instance MTU to account for GRE overhead. Determining the proper MTU value often takes experimentation, but 1454 bytes works in most environments. You can configure the DHCP server that assigns IP addresses to your instances to also adjust the MTU."

2014-11-16 08:34:06 -0500 received badge  Enthusiast
2014-11-16 01:59:10 -0500 received badge  Self-Learner (source)
2014-11-16 01:59:10 -0500 received badge  Teacher (source)
2014-11-14 13:37:55 -0500 commented answer rdo juno openstack glance operations fail

If you see that error message, rabbit will not accept messages until there's more space in that filesystem. By default it's in /var. Once space is available, the alarm will clear and rabbitmq will accept messages again.

2014-11-13 15:14:21 -0500 answered a question rdo juno openstack glance operations fail

I had an issue with nova-compute hanging as well, with no helpful log messages even with debug enabled. It was a rabbitmq issue. Check rabbitmq logs for entries like this:

=INFO REPORT==== 12-Nov-2014::15:14:32 === Disk free space insufficient. Free bytes:696029184 Limit:1000000000

=WARNING REPORT==== 12-Nov-2014::15:14:32 === disk resource limit alarm set on node 'rabbit@xxxxxxx'.


* Publishers will be blocked until this alarm clears *


2014-11-13 03:03:50 -0500 received badge  Famous Question (source)
2014-11-12 14:58:44 -0500 received badge  Editor (source)
2014-11-12 14:55:49 -0500 answered a question nova-compute does not start

Issue solved. This was caused because the /var filesystem in the controller node dropped below 1GB and rabbitmq blocked publishers:

from the rabbitmq logs:

=INFO REPORT==== 12-Nov-2014::15:14:32 ===
Disk free space insufficient. Free bytes:696029184 Limit:1000000000

=WARNING REPORT==== 12-Nov-2014::15:14:32 ===
disk resource limit alarm set on node 'rabbit@cha-ops-xen-v04'.

**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************

After I increased space in that partition and re-started services I now see the nova-compute service listed in the controller.

2014-11-12 09:10:19 -0500 received badge  Notable Question (source)
2014-11-12 09:02:44 -0500 commented answer nova-compute does not start

And when I run it manually, it connects to rabbit-mq, but I expected it to show when I do nova service-list, as described in the documentation.

2014-11-12 09:02:43 -0500 commented answer nova-compute does not start

With systemctl I get:

[root@cha-bl465-06:(cha-bl465-06) ~]# systemctl start openstack-nova-compute.service Job for openstack-nova-compute.service failed. See 'systemctl status openstack-nova-compute.service' and 'journalctl -xn' for details. [root@cha-bl465-06:(cha-bl465-06) ~]#

2014-11-12 09:02:42 -0500 commented question nova-compute does not start

I expected to see it listed when I run nova service-list in the controller, but I only see the 4 services running in the controller (nova-consoleauth, nova-cert, nova-scheduler, nova-conductor)

2014-11-12 08:33:21 -0500 received badge  Popular Question (source)
2014-11-11 20:46:02 -0500 answered a question nova-compute won't start anymore

Update: maybe this helps you.

The issue I was seeing was caused by the /var filesystem dropping below 1GB and rabbitmq blocking publishers. From the rabbitmq logs:

=INFO REPORT==== 12-Nov-2014::15:14:32 ===
Disk free space insufficient. Free bytes:696029184 Limit:1000000000

=WARNING REPORT==== 12-Nov-2014::15:14:32 ===
disk resource limit alarm set on node 'rabbit@cha-ops-xen-v04'.

**********************************************************
*** Publishers will be blocked until this alarm clears ***
**********************************************************

I'm having a similar issue. I'm following that guide too and got the controller node running on a VM with keystone, glance and nova (minus compute) and all worked fine. However, on the compute node (running on a real server) I can't get the nova-compute service to start at all. It just hangs there with few helpful log messages even with the debug option on.

If you just run it as a service you will notice that it will timeout at about 90 seconds and try to start again and will just stay in that loop. For troubleshooting, I'm trying to start it manually: /usr/bin/nova-compute --debug --config-file /etc/nova/nova.conf --log-file /var/log/nova/nova-compute.log

You say "it won't start anymore". Did you ever get it to start successfully?

I've asked the same question a couple of hours ago, but it's waiting moderation. Hopefully we will have an answer soon.

2014-11-11 20:45:37 -0500 asked a question nova-compute does not start

Hello there,

I'm installing a new openstack environment on Centos 7, following the instructions from this guide: http://docs.openstack.org/juno/install-guide/install/yum/content/ (http://docs.openstack.org/juno/instal...)

I installed the controller node services (mariadb, rabbitmq, keystone, glance and nova, except nova-compute) on a VM and had no issues. Everything is working as described by the install guide.

But I'm having problems with the nova-compute service starting on the compute node, which runs on a real server also with Centos 7. I followed the instructions in the guide (here: http://docs.openstack.org/juno/install-guide/install/yum/content/ch_nova.html#nova-compute-install (http://docs.openstack.org/juno/instal...) ) but the service fails to start. I enabled debug mode but I don't see any obvious errors in the log either.

I've tried running manually, and this is what I get:

[root@cha-bl465-06:(cha-bl465-06) ~]# /usr/bin/nova-compute --debug --config-file /etc/nova/nova.conf --log-file /var/log/nova/nova-compute.log
2014-11-11 16:17:24.882 4224 DEBUG nova.servicegroup.api [-] ServiceGroup driver defined as an instance of db __new__ /usr/lib/python2.7/site-packages/nova/servicegroup/api.py:65
2014-11-11 16:17:25.056 4224 INFO nova.virt.driver [-] Loading compute driver 'libvirt.LibvirtDriver'
2014-11-11 16:17:25.062 4224 INFO nova.openstack.common.periodic_task [-] Skipping periodic task _periodic_update_dns because its interval is negative
2014-11-11 16:17:25.109 4224 INFO oslo.messaging._drivers.impl_rabbit [req-ae205550-f345-4951-aa05-f3425333336b ] Connecting to AMQP server on cha-ops-xen-v04:5672
2014-11-11 16:17:25.132 4224 INFO oslo.messaging._drivers.impl_rabbit [req-ae205550-f345-4951-aa05-f3425333336b ] Connected to AMQP server on cha-ops-xen-v04:5672
2014-11-11 16:17:25.140 4224 INFO oslo.messaging._drivers.impl_rabbit [req-ae205550-f345-4951-aa05-f3425333336b ] Connecting to AMQP server on cha-ops-xen-v04:5672
2014-11-11 16:17:25.165 4224 INFO oslo.messaging._drivers.impl_rabbit [req-ae205550-f345-4951-aa05-f3425333336b ] Connected to AMQP server on cha-ops-xen-v04:5672

It seems to connect fine to the rabbitmq service in the controller but then it just hangs there...

Any help will be much appreciated.

Daniel