Ask Your Question

holo's profile - activity

2019-04-13 23:41:37 -0500 received badge  Famous Question (source)
2018-12-29 00:26:49 -0500 received badge  Famous Question (source)
2018-09-04 09:37:49 -0500 received badge  Famous Question (source)
2018-09-04 09:37:49 -0500 received badge  Notable Question (source)
2018-03-15 11:23:20 -0500 received badge  Notable Question (source)
2018-02-06 23:25:28 -0500 received badge  Popular Question (source)
2018-01-30 20:22:02 -0500 asked a question Can not assigne floating IP to instance with DVR router

Hello,

EDIT: i recreated everything just like was in documentation (without vlans) , chaged centos to ubuntu and still that same. My newest configs at bottom

Assigning floating ip is not working for me, am i doing something wrong? Below listing from operation:

[root@controller00 kolla-ansible]# openstack -vvv server add floating ip ad6a5662-9f53-4537-9844-1be01081a75d 192.168.11.62 
START with options: [u'-vvv', u'server', u'add', u'floating', u'ip', u'ad6a5662-9f53-4537-9844-1be01081a75d', u'192.168.11.62']
options: Namespace(access_token='***', access_token_endpoint='', access_token_type='', application_credential_id='', application_credential_name='', application_credential_secret='***', auth_type='', auth_url='http://192.168.30.254:35357/v3', cacert=None, cert='', client_id='', client_secret='***', cloud='', code='', debug=False, default_domain='default', default_domain_id='', default_domain_name='', deferred_help=False, discovery_endpoint='', domain_id='', domain_name='', endpoint='', identity_provider='', insecure=None, interface='internal', key='', log_file=None, openid_scope='', os_beta_command=False, os_compute_api_version='', os_identity_api_version='3', os_image_api_version='', os_key_manager_api_version='1', os_network_api_version='', os_object_api_version='', os_orchestration_api_version='1', os_project_id=None, os_project_name=None, os_volume_api_version='', passcode='', password='***', project_domain_id='', project_domain_name='Default', project_id='', project_name='admin', protocol='', redirect_uri='', region_name='RegionOne', remote_project_domain_id='', remote_project_domain_name='', remote_project_id='', remote_project_name='', service_provider='', system_scope='', timing=False, token='***', trust_id='', url='', user_domain_id='', user_domain_name='Default', user_id='', username='admin', verbose_level=4, verify=None)
Auth plugin password selected
auth_config_hook(): {'auth_type': 'password', 'beta_command': False, u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0', u'metering_api_version': u'2', 'auth_url': 'http://192.168.30.254:35357/v3', u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2', 'networks': [], u'image_api_version': u'2', 'verify': True, u'dns_api_version': u'2', u'object_store_api_version': u'1', 'username': 'admin', u'container_infra_api_version': u'1', 'verbose_level': 4, 'region_name': 'RegionOne', 'api_timeout': None, u'baremetal_api_version': u'1', 'auth': {'user_domain_name': 'Default', 'project_name': 'admin', 'project_domain_name': 'Default'}, 'default_domain': 'default', u'image_api_use_tasks': False, u'floating_ip_source': u'neutron', u'orchestration_api_version': '1', 'timing': False, 'password': '***', u'application_catalog_api_version': u'1', 'cacert': None, u'key_manager_api_version': '1', u'workflow_api_version': u'2', 'deferred_help': False, u'identity_api_version': '3', u'volume_api_version': u'2', 'cert': None, u'secgroup_source': u'neutron', u'status': u'active', u'container_api_version': u'1', u'interface': 'internal', u'disable_vendor_agent': {}}
defaults: {u'auth_type': 'password', u'status': u'active', u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0', 'api_timeout': None, u'baremetal_api_version': u'1', u'image_api_version': u'2', u'container_infra_api_version': u'1', u'metering_api_version': u'2', u'image_api_use_tasks': False, u'floating_ip_source': u'neutron', u'orchestration_api_version': u'1', 'cacert': None, u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2', u'application_catalog_api_version': u'1', u'key_manager_api_version': u'v1', u'workflow_api_version': u'2', 'verify': True, u'identity_api_version': u'2.0', u'volume_api_version': u'2', 'cert': None, u'secgroup_source': u'neutron', u'container_api_version': u'1', u'dns_api_version': u'2', u'object_store_api_version': u'1', u'interface': None, u'disable_vendor_agent': {}}
cloud cfg: {'auth_type': 'password', 'beta_command': False, u'compute_api_version': u'2', 'key': None, u'database_api_version': u'1.0', u'metering_api_version': u'2', 'auth_url': 'http://192.168.30.254:35357/v3', u'network_api_version': u'2', u'message': u'', u'image_format': u'qcow2', 'networks': [], u'image_api_version': u'2', 'verify': True, u'dns_api_version': u'2', u'object_store_api_version': u'1', 'username': 'admin', u'container_infra_api_version': u'1', 'verbose_level': 4, 'region_name': 'RegionOne', 'api_timeout': None, u'baremetal_api_version': u'1', 'auth': {'user_domain_name': 'Default', 'project_name': 'admin', 'project_domain_name': 'Default'}, 'default_domain': 'default', u'image_api_use_tasks': False, u'floating_ip_source ...
(more)
2018-01-30 20:03:50 -0500 answered a question Interfaces created by kolla in DOWN/UNKNOWN state

After one week of fighting with it i finally find out "issue".

By default Kolla configuration is using only private networking and is not creating external bridge "br-ex" on compute instances so there is no posibility to bind port to public network. I solved it by enabling DVR in global file:

enable_neutron_dvr: "yes"

2018-01-24 05:18:31 -0500 received badge  Popular Question (source)
2018-01-24 03:16:59 -0500 commented question Interfaces created by kolla in DOWN/UNKNOWN state

Here are is my global file: https://pastebin.com/ew66SaG2

Errors from controller server https://pastebin.com/Z7cPQYYT

Errors from compute server: https://pastebin.com/WUam0z29

What i mention, when i start instance with internal interface it is starting normaly.

2018-01-23 16:13:41 -0500 asked a question Interfaces created by kolla in DOWN/UNKNOWN state

Hello

All interfaces created by Kolla after installation are in DOWN state. When i try manually set them up they are changing to UNKNOWN. Can it be that im using systemd-networkd for seeting up my main interfaces? If not, how can i fix it? What can i check?

EDIT:

When i try to start normal instance instead of router im getting such error in neutron and nova:

2018-01-24 01:17:24.589 28 ERROR neutron.plugins.ml2.managers [req-8751f883-f9dd-43d1-ab5c-ea9d85813df3 6e758d916f514fe6978304c1558bcfe7 367730891853403bb40d8f00dfc57d6b - default default] Failed to bind port 5195df11-9719-4387-8a21-e7333bcde630 on host compute00 for vnic_type normal using segments [{'network_id': '8302585c-7543-4414-b01c-0437878cf8f5', 'segmentation_id': None, 'physical_network': u'physnet1', 'id': '19da16de-701c-4d2d-b7e1-7d97b1a9279a', 'network_type': u'flat'}]
2018-01-24 01:17:24.590 28 INFO neutron.plugins.ml2.plugin [req-8751f883-f9dd-43d1-ab5c-ea9d85813df3 6e758d916f514fe6978304c1558bcfe7 367730891853403bb40d8f00dfc57d6b - default default] Attempt 2 to bind port 5195df11-9719-4387-8a21-e7333bcde630
2018-01-24 01:17:24.617 28 ERROR neutron.plugins.ml2.managers [req-8751f883-f9dd-43d1-ab5c-ea9d85813df3 6e758d916f514fe6978304c1558bcfe7 367730891853403bb40d8f00dfc57d6b - default default] Failed to bind port 5195df11-9719-4387-8a21-e7333bcde630 on host compute00 for vnic_type normal using segments [{'network_id': '8302585c-7543-4414-b01c-0437878cf8f5', 'segmentation_id': None, 'physical_network': u'physnet1', 'id': '19da16de-701c-4d2d-b7e1-7d97b1a9279a', 'network_type': u'flat'}]

/EDIT

root@controller00 network]# ip l
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eno1: <BROADCAST,MULTICAST,SLAVE,UP,LOWER_UP> mtu 1500 qdisc mq master bond0 state UP mode DEFAULT qlen 1000
    link/ether 00:1e:4f:2f:b1:57 brd ff:ff:ff:ff:ff:ff
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,SLAVE,UP> mtu 1500 qdisc mq master bond0 state DOWN mode DEFAULT qlen 1000
    link/ether 00:1e:4f:2f:b1:57 brd ff:ff:ff:ff:ff:ff
4: bond0: <BROADCAST,MULTICAST,MASTER,UP,LOWER_UP> mtu 1500 qdisc noqueue master ovs-system state UP mode DEFAULT qlen 1000
    link/ether 00:1e:4f:2f:b1:57 brd ff:ff:ff:ff:ff:ff
5: vlan60@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether 2e:7d:7c:81:83:1b brd ff:ff:ff:ff:ff:ff
6: vlan70@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether be:7f:83:4f:21:69 brd ff:ff:ff:ff:ff:ff
7: vlan20@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether ea:8e:c4:e9:71:9d brd ff:ff:ff:ff:ff:ff
8: vlan10@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether 02:c1:b0:3c:c8:13 brd ff:ff:ff:ff:ff:ff
9: vlan50@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether 26:5a:c4:d3:46:21 brd ff:ff:ff:ff:ff:ff
10: vlan40@bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT qlen 1000
    link/ether fe:2b:9a:62:ad:c7 brd ff:ff:ff:ff:ff ...
(more)
2017-06-20 15:52:17 -0500 received badge  Famous Question (source)
2017-03-09 02:47:00 -0500 received badge  Notable Question (source)
2017-03-05 12:46:18 -0500 received badge  Popular Question (source)
2017-03-04 07:25:03 -0500 received badge  Editor (source)
2017-03-04 06:48:52 -0500 answered a question HTTPInternalServerError (HTTP 500) - glance on separate server

There was not python-memcached module installed on glance server. I missed that information actually appear in glance log. Now glance service is working. Thank you for your time and sorry - my fault.

PS It could be good to add python-memcached as dependency for glance and other services too, not only for keystone in case of installation on separate instances.

2017-03-04 06:37:58 -0500 commented question HTTPInternalServerError (HTTP 500) - glance on separate server

Here it is: http://pasted.co/999f47de

Database was create manually and then i used command from docs to create tables:

su -s /bin/sh -c "glance-manage db_sync" glance
2017-03-04 05:13:02 -0500 commented question HTTPInternalServerError (HTTP 500) - glance on separate server

In glance log is onlly info about service start nothing more. During installation i needed to sync DB and tables are created so glance have connection to database.During operation i see only new logs in keystone log and nothing more (no errors).

2017-03-04 04:58:00 -0500 received badge  Enthusiast
2017-03-03 12:57:44 -0500 asked a question HTTPInternalServerError (HTTP 500) - glance on separate server

Hello

I'm configuring openstack according to: https://docs.openstack.org/ocata/inst...

I installed keystone on one instance and want to install glance on separate server, when im trying to verify my configuration im getting:

[root@manage01 ~]# openstack image create "cirros"   --file cirros-0.3.4-x86_64-disk.img   --disk-format qcow2 --container-format bare   --public
HTTPInternalServerError (HTTP 500)
[root@manage01 ~]# openstack -v image create "cirros"   --file cirros-0.3.4-x86_64-disk.img   --disk-format qcow2 --container-format bare   --public
START with options: [u'-v', u'image', u'create', u'cirros', u'--file', u'cirros-0.3.4-x86_64-disk.img', u'--disk-format', u'qcow2', u'--container-format', u'bare', u'--public']
command: image create -> openstackclient.image.v2.image.CreateImage
Using auth plugin: password
HTTPInternalServerError (HTTP 500)
END return value: 1

My present endpoints configuration:

[root@manage01 ~]# openstack endpoint list
+----------------------------------+-----------+--------------+--------------+---------+-----------+---------------------------+
| ID                               | Region    | Service Name | Service Type | Enabled | Interface | URL                       |
+----------------------------------+-----------+--------------+--------------+---------+-----------+---------------------------+
| 94f2b772504042d380fb6b2779d7b513 | RegionOne | glance       | image        | True    | internal  | http://image:9292         |
| 97e549d381604224ad742b718b833d02 | RegionOne | glance       | image        | True    | public    | http://image:9292         |
| 9f3ee12b68bd449f84150c2a8a4a2340 | RegionOne | keystone     | identity     | True    | public    | http://identity:5000/v3/  |
| a1ccaa525b6a48549a79017388354204 | RegionOne | glance       | image        | True    | admin     | http://image:9292         |
| bf47ca0119a94a07b6f5acece8a5b699 | RegionOne | keystone     | identity     | True    | admin     | http://identity:35357/v3/ |
| c62838c2471e4624a3e7f5c3bc5fdf38 | RegionOne | keystone     | identity     | True    | internal  | http://identity:5000/v3/  |
+----------------------------------+-----------+--------------+--------------+---------+-----------+---------------------------+

What am i missed? If i do everything exectly same way but on same server where i have keystone configured glance is working. Should i change some other configuration too which is not mentioned in standard installation?

Connection betwenn instances is working (separate VLAN for mgmt network).

Regards holo

2017-01-27 07:37:58 -0500 received badge  Famous Question (source)
2016-08-29 06:42:14 -0500 received badge  Notable Question (source)
2016-08-16 05:29:33 -0500 received badge  Popular Question (source)
2016-08-15 07:26:47 -0500 asked a question Public endpoints

I have noob question. If im configuring public cloud, should all services be configured with public endpoints exposed to public network or is it enough to do this only for keyston api and rest services will be "talking" internally?

Thanks

2016-08-14 15:36:49 -0500 received badge  Notable Question (source)
2016-08-13 01:08:01 -0500 received badge  Popular Question (source)
2016-08-12 12:48:48 -0500 received badge  Student (source)
2016-08-12 12:14:54 -0500 commented answer openstack client can't create virtual machine

Yes, that was it. Thank You for your time.

2016-08-12 12:13:50 -0500 received badge  Supporter (source)
2016-08-12 11:50:43 -0500 asked a question openstack client can't create virtual machine

I configured openstack according to insallation guide but when im trying to start instance i have such error:

[root@controller ~]# openstack server create --flavor m1.tiny --image cirros --nic 2bf61961-c8dd-495a-9053-95468652773c --security-group default --key-name mykey testinstance2
dictionary update sequence element #0 has length 1; 2 is required
[root@controller ~]#

i find out error in my glance log:

2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client [req-02b4b560-0f41-48d1-87e8-9ab3e037afa7 eb753a607305461f92b01d5a759f4a68 4228d3befa1c43fd9b25367df08bbb7c - - -] Registry client request GET /images/cirros raised NotFound
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client Traceback (most recent call last):
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client   File "/usr/lib/python2.7/site-packages/glance/registry/client/v1/client.py", line 123, in do_request
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client     **kwargs)
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client   File "/usr/lib/python2.7/site-packages/glance/common/client.py", line 70, in wrapped
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client     return func(self, *args, **kwargs)
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client   File "/usr/lib/python2.7/site-packages/glance/common/client.py", line 373, in do_request
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client     headers=copy.deepcopy(headers))
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client   File "/usr/lib/python2.7/site-packages/glance/common/client.py", line 87, in wrapped
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client     return func(self, method, url, body, headers)
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client   File "/usr/lib/python2.7/site-packages/glance/common/client.py", line 528, in _do_request
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client     raise exception.NotFound(read_body(res))
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client NotFound: 404 Not Found
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client 
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client The resource could not be found.
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client 
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client    
2016-08-12 16:54:00.553 18079 ERROR glance.registry.client.v1.client 
2016-08-12 16:54:00.555 18079 INFO eventlet.wsgi.server [req-02b4b560-0f41-48d1-87e8-9ab3e037afa7 eb753a607305461f92b01d5a759f4a68 4228d3befa1c43fd9b25367df08bbb7c - - -] 10.0.0.13 - - [12/Aug/2016 16:54:00] "HEAD /v1/images/cirros HTTP/1.1" 404 213 0.255239
2016-08-12 16:54:00.824 18079 INFO eventlet.wsgi.server [req-a06be10c-d176-4986-8e5e-f443bdbd82b0 eb753a607305461f92b01d5a759f4a68 4228d3befa1c43fd9b25367df08bbb7c - - -] 10.0.0.13 - - [12/Aug/2016 16:54:00] "GET /v1/images/detail?is_public=none&limit=20 HTTP/1.1" 200 709 0.261196

What is strange when i use "nova" client to boot new instance everything is working. Is it something with my setup?