Ask Your Question

Iván Sixto's profile - activity

2016-09-09 02:35:11 -0600 received badge  Famous Question (source)
2015-12-03 01:36:00 -0600 received badge  Popular Question (source)
2015-12-03 01:36:00 -0600 received badge  Notable Question (source)
2015-11-24 06:23:08 -0600 asked a question Some help with understanding Horizon design?

Hi!

I'm trying to get some info about internal design of Horizon, but I can't find some info...

It would be really interesting if someone knew some links with UML designs, architecture or even a little explanation for me to be able to get started with the sub-project.

I found it really interesting.

Thanks you very much guys! And I really sorry for my english, I know it sucks ;D

2014-09-25 08:34:49 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Ok, done... Everything is working... memcached has to be listening on 192.168.10.2 (management network).

Thank you very much.

Just for finish, I recommend to read the hole topic for those who has same issues.

Once again, thank you very much.

2014-09-25 08:25:02 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Just another doubt... memcache config IP, should be from storage network or management network?

2014-09-25 08:24:16 -0600 received badge  Famous Question (source)
2014-09-25 08:14:24 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Ok, I understand that actually it is a bad config...

The enpoint is pointing to ZEUS -> 192.168.10.2...

Then I have to change bind_ip on proxy-config to 192.168.10.2 instead 192.168.20.2.

I'll check it our in a sec.

2014-09-25 08:08:09 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

oh... Ehm,

zeus is pointed to management network 192.168.10.2

but proxy node is listening on 192.168.20.2 (storage network).. is that bad config?

2014-09-25 08:04:24 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

I've also noticed that there is no content on

/etc/swift/object-server /etc/swift/container-server /etc/swift/account-server

...

2014-09-25 07:41:37 -0600 commented answer [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

hi! thanks for replying.

I updated first post with all info.

;)

2014-09-25 04:02:04 -0600 received badge  Notable Question (source)
2014-09-24 16:25:04 -0600 commented question [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Ok, I have definitely no idea about what's going on.

If I look on keystone log I'm able to see how Swift user is authenticated. Please, have you got any idea?

2014-09-24 15:47:12 -0600 commented question [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Ok, fixed error on /var/log/messages by adding and changing bind_ip with storage network IP in proxy-server.conf (on controller) and container, account and object conf files on Storage nodes.

But, still same issue when swift stat (connecion refused).

2014-09-24 13:18:36 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

okey... Now I know why I couldn't ping an instance with floating IP to external network attached... I had forgotten to add a rule to the security group... (dont kill me =( )

nova secgroup-add-rule default icmp -1 -1 0.0.0.0/0

But, issue with metadata not reachable from VM still present...

2014-09-24 12:37:05 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

neutron-metadata-agent should be running on Controller too, right?

2014-09-24 12:12:30 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Sure,

Done, and: couldn't resolve host..

2014-09-24 12:01:53 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Okey, I think the proccess is install rabbitmq-server on Controller node... But i don't know where can I found doc about how to config rabbitmq and openstack services... :S is there any doc?

2014-09-24 11:48:45 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

So, are you saying rabbitMQ instead qpidd, right?

I'll try it.

2014-09-24 10:57:14 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Ok, set static IP too on Compute Node.

Now VMs get IP on tenant network, but... still same problem with external network...

But If I'm using qpidd... is there any problem?

2014-09-24 10:04:09 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Is it supposed to set a static Ip con the compute node?

AcTUAL COMPUTE CONF ETH0: DEVICE=eth0 BOOTPROTO="dhcp" ONBOOT=yes TYPE=Ethernet NAME="Externa eth0" DEFROUTE=yes

2014-09-24 09:20:12 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

dbaxps, first of all I'm using qpidd. Second, DHCPRequest... I'm not pretty sure about what the hell is going on... I haven't got DHCP enabled on external network... :S

And, since I changed to metadata config files that you provided, I cant ping to any device or IP... :S (show VM log on first post

2014-09-23 17:08:41 -0600 received badge  Popular Question (source)
2014-09-23 15:50:21 -0600 edited question VM doesn't get IP with Neutron (icehouse, centos 6.5)

Hi, I've got this network design on a fresh installation ( http://oi60.tinypic.com/2cglw2c.jpg ).

PROBLEM WHEN I LAUNCH AN INSTANCE (doesn't get IP on external network):

Starting acpid: OK
cirros-ds 'local' up at 1.00
no results found for mode=local. up 1.07. searched: nocloud configdrive ec2
Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cirros-ds 'net' up at 181.28
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 181.29. request failed
failed 2/20: up 183.44. request failed
failed 3/20: up 185.45. request failed
failed 4/20: up 187.46. request failed
failed 5/20: up 189.47. request failed
failed 6/20: up 191.48. request failed
failed 7/20: up 193.49. request failed
failed 8/20: up 195.50. request failed
failed 9/20: up 197.51. request failed
failed 10/20: up 199.52. request failed
failed 11/20: up 201.53. request failed
failed 12/20: up 203.54. request failed
failed 13/20: up 205.55. request failed
failed 14/20: up 207.56. request failed
failed 15/20: up 209.57. request failed
failed 16/20: up 211.58. request failed
failed 17/20: up 213.59. request failed
failed 18/20: up 215.60. request failed
failed 19/20: up 217.61. request failed
failed 20/20: up 219.61. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 221.62. searched: nocloud configdrive ec2
failed to get instance-id of datasource

CONTROLLER NODE:

eth0 (external)

DEVICE="eth0"
BOOTPROTO="static"
IPADDR=10.51.1.226
NETMASK=255.255.255.0
GATEWAY=10.51.1.1
ONBOOT="yes"
TYPE="Ethernet"
DEFROUTE=yes
NAME="System eth0"

eth1 (management)

DEVICE=eth1
TYPE=Ethernet
ONBOOT=yes
BOOTPROTO="static"
IPADDR=192.168.10.2
PREFIX=24
DEFROUTE=no
NAME="System eth1"
DNS1=10.51.1.1

NETWORK NODE:

eth0 (external)

DEVICE=eth0
ONBOOT="yes"
TYPE="OVSPort"
DEVICETYPE="ovs"
OVS_BRIDGE=br-ex
NM_CONTROLLED=no
IPV6INIT=no

eth1 (management)

DEVICE="eth1"
ONBOOT="yes"
IPADDR=192.168.10.3
PREFIX=24
NAME=Interna

eth1:0 (tunnel)

DEVICE="eth1:0"
ONBOOT="yes"
IPADDR=192.168.11.3
PREFIX=24
NAME=Tunel

br-ex

DEVICE="br-ex"
BOOTPROTO="static"
IPADDR="10.51.1.218"
NETMASK="255.255.255.0"
DNS1="8.8.8.8"
BROADCAST="10.51.1.255"
GATEWAY="10.51.1.1"
NM_CONTROLLED="no"
DEFROUTE="yes"
IPV4_FAILURE_FATAL="yes"
IPV6INIT=no
ONBOOT="yes"
TYPE="OVSBridge"
DEVICETYPE="ovs"

ovs-vsctl show

9bae8809-e0a1-4e64-b5dd-203e83945574
    Bridge br-int
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "qr-6e233dc7-40"
            tag: 1
            Interface "qr-6e233dc7-40"
                type: internal
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port "gre-c0a80b04"
            Interface "gre-c0a80b04"
                type: gre
                options: {in_key=flow, local_ip="192.168.11.3", out_key=flow, remote_ip="192.168.11.4"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
    Bridge br-ex
        Port "eth0 ...
(more)
2014-09-23 15:42:54 -0600 commented question [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

dbaxps, answared on that topic ;)

ebyenjoys, i uploaded rsyslog on first post. I'll check ports tomorrow (roaming data is getting over ;S)

2014-09-23 15:36:50 -0600 received badge  Famous Question (source)
2014-09-23 14:42:44 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Same result... :S

2014-09-23 13:42:39 -0600 asked a question [solved] Problem verifying installation of Swift. [Errno 111] Connection refused

Hi, I just installed Swift on a fresh installation of OpenStack.

I've got a problem when doing swift stat:

Account HEAD failed: http://zeus:8080/v1/AUTH_37d8b1fb62374ef9a5642f992f624eec 503 Internal Server Error

I think is about proxy server not being able to authenticate with Storage nodes, but I'm not pretty sure...

I've been reviewing my proxy-server.conf and I don't see any error...

Do you have any idea guys?

My proxy-server.conf: [DEFAULT] bind_port = 8080 user = swift

[pipeline:main]
pipeline = healthcheck cache authtoken keystoneauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true

[filter:keystoneauth]
use = egg:swift#keystoneauth
operator_roles = Member,admin,swiftoperator

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory
# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = true
# cache directory for signing certificate
#   signing_dir = /opt/swift/keystone-signing
# auth_* settings refer to the Keystone server
auth_protocol = http
auth_host = zeus
auth_port = 35357
# the service tenant and swift username and password created in Keystone
admin_tenant_name = service
admin_user = swift
admin_password = passswift


[filter:cache]
use = egg:swift#memcache

[filter:catch_errors]
use = egg:swift#catch_errors

[filter:healthcheck]
use = egg:swift#healthcheck

Just say that zeus is controller node (where keystone is installed).

Thanks

PD: All devices on Storage nodes are mounted.

EDITED:

From rsyslog: /var/log/messages

Sep 23 22:34:23 zeus proxy-server: Auth Token confirmed use of v2.0 apis
Sep 23 22:34:23 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:23 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:23 zeus proxy-server: Account GET returning 503 for [] (txn: tx8ff1e9e5b53a4824a84d9-005421d94f) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:24 zeus proxy-server: Account GET returning 503 for [] (txn: txc144fee25d804d499ab74-005421d950) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: ERROR with Account server 192.168.20.4:6002/sdb3 re: Trying to GET /v1/AUTH_37d8b1fb62374ef9a5642f992f624eec: Connection refused (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:26 zeus proxy-server: Account GET returning 503 for [] (txn: tx800f935d89ca434eba514-005421d952) (client_ip: 192.168.10.2)
Sep 23 22:34:30 zeus proxy-server: ERROR with Account server 192.168.20.3:6002/sdb2 re: Trying to GET ...
(more)
2014-09-23 10:46:26 -0600 commented answer VM doesn't get IP with Neutron (icehouse, centos 6.5)

Sorry, but for "Neutron Server" do you mean Network Node or Controller node (running neutron-server service)?

2014-09-23 10:42:05 -0600 received badge  Enthusiast
2014-09-22 19:33:48 -0600 received badge  Notable Question (source)
2014-09-22 15:02:38 -0600 commented question VM doesn't get IP with Neutron (icehouse, centos 6.5)

Do you mean at controller?

2014-09-22 14:55:13 -0600 commented question VM doesn't get IP with Neutron (icehouse, centos 6.5)

T u I, I'm not pretty sure... Should I include on my Controller nova.conf:

metadata_host = 192.168.10.4
metadata_listen = 0.0.0.0
metadata_listen_port = 8775 
(...)

And enabled_apis = metadata flag on Compute nova.conf ?