Ask Your Question

diegolopez's profile - activity

2017-04-20 21:37:20 -0500 received badge  Notable Question (source)
2017-04-20 21:37:20 -0500 received badge  Famous Question (source)
2015-10-27 10:25:11 -0500 received badge  Student (source)
2015-06-04 16:16:25 -0500 received badge  Taxonomist
2014-08-07 05:27:11 -0500 received badge  Popular Question (source)
2014-07-25 05:14:58 -0500 received badge  Famous Question (source)
2014-07-07 07:11:06 -0500 received badge  Famous Question (source)
2014-07-05 18:18:26 -0500 received badge  Notable Question (source)
2014-07-05 07:48:09 -0500 received badge  Popular Question (source)
2014-07-04 11:52:45 -0500 received badge  Famous Question (source)
2014-06-30 15:17:43 -0500 asked a question specify OVS path

How can I specify OpenVSwitch configuration path? and where?

Thanks!

2014-06-30 11:10:51 -0500 asked a question neutron queue and vpn: 404 not found

Hello,

When I run "neutron vpn-service-list" or "neutron queue-list", the result are:

404 Not Found

The resource could not be found.

I had the same problem with "neuton firewall-list", but it was solved adding in neutron.conf:

service_plugins = neutron.services.firewall.fwaas_plugin.FirewallPlugin,neutron.services.loadbalancer.plugin.LoadBalancerPlugin

Any idea?

Havana + Ubuntu 14.04 + GRE + OVS

2014-06-24 02:10:42 -0500 commented answer DHCP from instance is not reaching the DHCP Server

it's in the first comment. it's a link that points to /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini

2014-06-23 23:28:20 -0500 commented answer DHCP from instance is not reaching the DHCP Server

Ubuntu 14.04 . I changed this gateway by 192.168.122.1, but it still not work.

2014-06-23 23:26:32 -0500 received badge  Notable Question (source)
2014-06-23 16:11:03 -0500 answered a question DHCP from instance is not reaching the DHCP Server

not work, I set tunnel_types =gre, but it still doesn't work

I create this external-net:

neutron net-create ext-net --shared --router:external=True neutron subnet-create ext-net --allocation-pool start=192.168.122.100,end=192.168.122.150 --gateway=192.168.122.200 --enable_dhcp=True 192.168.122.0/24

When I see ext-net (neutron net-show ext-net) , the provider is local !!

provider:network_type local

If I try to change it, for example creating another like this, it throws an exception:

neutron net-create net2 --provider:network-type gre

400-{u'NeutronError': {u'message': u'Invalid input for operation: gre networks are not enabled.', u'type': u'InvalidInput', u'detail': u''}}

It seems like OVS don't get the config file. And when I restart OVS, in the openvswitch-agent.log:

2014-06-23 23:09:02.195 1958 ERROR neutron.plugins.openvswitch.agent.ovs_neutron_agent [-] Error while processing VIF ports 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent Traceback (most recent call last): 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py", line 1213, in rpc_loop 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent port_info = self.scan_ports(ports, updated_ports_copy) 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/plugins/openvswitch/agent/ovs_neutron_agent.py", line 816, in scan_ports 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent cur_ports = self.int_br.get_vif_port_set() 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ovs_lib.py", line 311, in get_vif_port_set 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent port_names = self.get_port_name_list() 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ovs_lib.py", line 267, in get_port_name_list 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent res = self.run_vsctl(["list-ports", self.br_name], check_error=True) 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ovs_lib.py", line 74, in run_vsctl 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent ctxt.reraise = False 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/openstack/common/excutils.py", line 82, in __exit__ 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent six.reraise(self.type_, self.value, self.tb) 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/ovs_lib.py", line 67, in run_vsctl 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent return utils.execute(full_args, root_helper=self.root_helper) 2014-06-23 23:09:02.195 1958 TRACE neutron.plugins.openvswitch.agent.ovs_neutron_agent File "/usr/lib/python2.7/dist-packages/neutron/agent/linux/utils.py", line 76, in execute ... (more)

2014-06-23 11:34:17 -0500 received badge  Enthusiast
2014-06-23 00:59:35 -0500 received badge  Popular Question (source)
2014-06-22 06:38:45 -0500 asked a question DHCP from instance is not reaching the DHCP Server

I'm trying to configure Neutron with OpenvSwitch and GRE tunneling, with 2 servers: One of them it's a controller and compute node, and the other it's only a compute node.

When OpenStack launch the instance into the controller, it's OK, the instance has IP, but when it's launched into the other, the instance is configured without IP, but I can see in Horizon that this instance has IP (for example I can see 10.0.0.100 but when I do "ifconfig" in the instance, it hasn't got IP and I can't ping on it).

I'm using KVM with Libvirth. My controller has 192.168.122.200, and the compute 192.168.122.201.

Controller: /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:
[OVS]
vxlan_udp_port=4789
network_vlan_ranges=physnet:1000:2000
local_ip=192.168.122.201
enable_tunneling=True
integration_bridge=br-int
tunnel_type=gre
tunnel_id_ranges=1:1000
tunnel_bridge=br-tun
tenant_network_type=gre

[AGENT]
polling_interval=2

[SECURITYGROUP]
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver

Compute: /etc/neutron/plugins/openvswitch/ovs_neutron_plugin.ini:
[OVS]
vxlan_udp_port=4789
network_vlan_ranges=physnet:1000:2000
local_ip=192.168.122.201
enable_tunneling=True
integration_bridge=br-int
tunnel_type=gre
tunnel_id_ranges=1:1000
tunnel_bridge=br-tun
tenant_network_type=gre

[AGENT]
polling_interval=2

[SECURITYGROUP]
firewall_driver=neutron.agent.linux.iptables_firewall.OVSHybridIptablesFirewallDriver


neutron agent-list:

+--------------------------------------+--------------------+------------+-------+----------------+

| id                                   | agent_type         | host       | alive | admin_state_up |

+--------------------------------------+--------------------+------------+-------+----------------+

...

| 2824eb92-eec8-4731-b432-b1960cd8c4e8 | Open vSwitch agent | comp1      | :-)   | True           |

| 730e40e2-f9db-4281-9418-caf3bebf990e | Open vSwitch agent | controller | :-)   | True           |

...

+--------------------------------------+--------------------+------------+-------+----------------+


Any ideas? Thanks!
2014-06-19 02:08:02 -0500 received badge  Notable Question (source)
2014-06-17 23:45:57 -0500 received badge  Popular Question (source)
2014-06-17 04:58:48 -0500 received badge  Editor (source)
2014-06-17 04:57:44 -0500 asked a question OpenStack Neutron agent-list not alive

I've got a problem with my network configuration. When I see neutron agents, I obtain this (not alives):

+--------------------------------------+--------------------+--------------------+-------+----------------+
| id     | agent_type         | host               | alive | admin_state_up |
+--------------------------------------+--------------------+--------------------+-------+----------------+
| 134c047a-8cb5-4120-97ce-ad73fe6c5631 | Metadata agent     | ubuntupruebas-comp | xxx   | True |
| 782cb953-5fbd-4c8b-8a8d-efbb1bdad0ff | Open vSwitch agent | ubuntupruebas-comp | xxx   | True  |
| 86e64314-c5a5-421e-864b-068c6fe2e69c | DHCP agent         | ubuntupruebas-comp | xxx   | True   |
| 9221940c-2df3-49a2-8f35-8d5bef3a5f3a | Metering agent     | ubuntupruebas-comp | xxx   | True  |
| bc34d84d-a6a9-4dd5-a7f5-34c56478feb0 | L3 agent           | ubuntupruebas-comp | xxx   | True   |
+--------------------------------------+--------------------+--------------------+-------+----------------+

but when I rerun the command, I obtain this:
$ neutron agent-list
+--------------------------------------+--------------------+--------------------+-------+----------------+
| id   | agent_type         | host               | alive | admin_state_up |
+--------------------------------------+--------------------+--------------------+-------+----------------+
| 134c047a-8cb5-4120-97ce-ad73fe6c5631 | Metadata agent     | ubuntupruebas-comp | xxx   | True    |
| 782cb953-5fbd-4c8b-8a8d-efbb1bdad0ff | Open vSwitch agent | ubuntupruebas-comp | :-)   | True   |
| 86e64314-c5a5-421e-864b-068c6fe2e69c | DHCP agent         | ubuntupruebas-comp | :-)   | True     |
| 9221940c-2df3-49a2-8f35-8d5bef3a5f3a | Metering agent     | ubuntupruebas-comp | xxx   | True     |
| bc34d84d-a6a9-4dd5-a7f5-34c56478feb0 | L3 agent           | ubuntupruebas-comp | :-)   | True   |
+--------------------------------------+--------------------+--------------------+-------+----------------+

And later, they die, and so on.

In horizon, the diagram of my network seems down. For example, I set to my br-ext IP 10.0.0.1, and the router that set gateway -> 10.0.0.5, and it's always down but I can do a "ping" to it.

I'm using Ubuntu14.04 with Open-vswitch

Any suggestions?
2014-06-05 08:05:18 -0500 received badge  Famous Question (source)
2014-05-12 05:03:16 -0500 received badge  Famous Question (source)
2014-04-17 23:27:39 -0500 received badge  Famous Question (source)
2014-04-13 23:12:21 -0500 received badge  Notable Question (source)
2014-04-13 23:12:21 -0500 received badge  Popular Question (source)
2014-04-09 10:50:36 -0500 received badge  Popular Question (source)
2014-04-09 10:50:36 -0500 received badge  Notable Question (source)
2014-03-19 13:40:35 -0500 received badge  Teacher (source)
2014-03-16 16:44:43 -0500 answered a question how to calculate physical servers needed for an openstack project

look at this:

http://www.mirantis.com/openstack-services/bom-calculator/ (http://www.mirantis.com/openstack-ser...)

http://docs.mirantis.com/fuel/fuel-4.0/pdf/Mirantis-OpenStack-4.0-Pre-InstallationGuide.pdf (http://docs.mirantis.com/fuel/fuel-4....)

Hope it helps

2014-03-16 16:37:17 -0500 asked a question heat: WikiDatabase: ImageId "" does not validate glance.image

I tried to launch a stack with heat, like this:

heat stack-create teststac -u https://raw.github.com/openstack/heat-templates/master/cfn/F17/WordPress_Single_Instance.template (https://raw.github.com/openstack/heat...) -P "DBUsername=wp;DBPassword=verybadpassword;KeyName=heat_key;LinuxDistribution=F17"

ERROR: Property error : WikiDatabase: ImageId "F17-x86_64-cfntools" does not validate glance.image

But when I saw the images, it seemed to be OK:

glance image-list +--------------------------------------+---------------------+-------------+------------------+-----------+----------------------------+ | ID | Name | Disk Format | Container Format | Size | Status | +--------------------------------------+---------------------+-------------+------------------+-----------+----------------------------+ | e8a3f8a7-1a5e-49b1-a5fa-3a7a7dd10894 | F17-x86_64-cfntools | qcow2 | bare | 476704768 | active | +--------------------------------------+---------------------+-------------+------------------+-----------+-----------------------------+

I tried to change F17-x86_64-cfntools for the ID e8a3f8a7-1a5e-49b1-a5fa-3a7a7dd10894 in the template, but the error persists.

I'm using Devstack, and I follow this doc: http://docs.openstack.org/developer/heat/getting_started/on_devstack.html#preparing-nova-for-running-stacks (http://docs.openstack.org/developer/h...)

Any idea?

2014-03-10 00:30:34 -0500 received badge  Notable Question (source)
2014-03-09 04:39:27 -0500 received badge  Popular Question (source)
2014-03-08 16:49:35 -0500 answered a question how can I launch an instance in a concrete server?

Solved, first I created an aggregate zone (and It created an availability zone). Then, you can add machines to this zone. The instance can be boot on this new availability zone.

For example:
nova boot example --image 778d0d68-4e98-40a5-ad01-97ab60ca9035 --flavor 1 --availability-zone new_zone

Here the instructions: http://russellbryantnet.wordpress.com/2013/05/21/availability-zones-and-host-aggregates-in-openstack-compute-nova/ (http://russellbryantnet.wordpress.com...)

2014-03-08 16:11:49 -0500 asked a question how can I launch an instance in a concrete server?

Hello,

I have got 2 compute nodes, and I'd like to choose in which one the instance will run. How can I do this? Maybe any parameter in "nova boot"?

Thanks!

2014-02-26 08:49:32 -0500 received badge  Supporter (source)
2014-02-21 09:32:54 -0500 asked a question Endpoint does not support RPC

I have this error when I launch "nova-all" in a compute node:

2014-02-21 16:20:38.611 ERROR nova.openstack.common.threadgroup [-] Remote error: UnsupportedVersion Endpoint does not support RPC version 1.63 [u'Traceback (most recent call last):\n', u' File "/opt/stack/oslo.messaging/oslo/messaging/_executors/base.py", line 36, in _dispatch\n
incoming.reply(self.callback(incoming.ctxt, incoming.message))\n', u' File "/opt/stack/oslo.messaging/oslo/messaging/rpc/dispatcher.py", line 143, in __call__\n raise UnsupportedVersion(version)\n', u'UnsupportedVersion: Endpoint does not support RPC version 1.63\n']. 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup Traceback (most recent call last): 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 117, in wait 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
x.wait() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/openstack/common/threadgroup.py", line 49, in wait 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
return self.thread.wait() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 168, in wait 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
return self._exit_event.wait() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/usr/local/lib/python2.7/dist-packages/eventlet/event.py", line 116, in wait 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
return hubs.get_hub().switch() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/usr/local/lib/python2.7/dist-packages/eventlet/hubs/hub.py", line 187, in switch 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
return self.greenlet.switch() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/usr/local/lib/python2.7/dist-packages/eventlet/greenthread.py", line 194, in main 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
result = function(args, *kwargs) 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/openstack/common/service.py", line 480, in run_service 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
service.start() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/service.py", line 193, in start 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
self.manager.pre_start_hook() 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/compute/manager.py", line 835, in pre_start_hook 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
self.update_available_resource(nova.context.get_admin_context()) 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/compute/manager.py", line 5119, in update_available_resource 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
rt.update_available_resource(context) 2014-02-21 16:20:38.611 TRACE nova.openstack.common.threadgroup
File "/opt/stack/nova/nova/openstack/common/lockutils.py", line 249, in inner ...





















(more)