Ask Your Question

amit-g's profile - activity

2017-08-14 17:37:16 -0500 asked a question Client disconnected before sending all data to backend

Hello all,

I have been facing this issue while upload image that is of 1.1GB to S3 store. Is there a way to increase the timeout value for this.

2017-08-15 03:04:50.244 2519 INFO eventlet.wsgi.server [req-5566b2cf-11ee-49c2-9398-6f36a774febc 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:04:50] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.028111
2017-08-15 03:04:57.914 2516 INFO eventlet.wsgi.server [req-75f5ee5d-2cd8-47db-b21a-fdca413a3168 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:04:57] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.064382
2017-08-15 03:05:08.272 2514 INFO eventlet.wsgi.server [req-6a184ea4-d414-4af9-9dd3-7de5aea64fd0 

661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:08] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.266585
2017-08-15 03:05:08.665 2516 INFO eventlet.wsgi.server [req-fb4f692f-a8ef-49a2-98b6-8e141960b284 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:08] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.026095
2017-08-15 03:05:08.861 2516 INFO eventlet.wsgi.server [req-a8fb49a3-53c6-49ab-bc1e-ca53089f1811 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:08] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.026345
2017-08-15 03:05:12.335 2520 INFO eventlet.wsgi.server [req-e3facfd7-b9bc-4433-a3c6-bb4bb6b17a5c 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:12] "GET /v1/images/detail?sort_key=name&sort_dir=asc&limit=21 HTTP/1.1" 200 1194 0.095153
2017-08-15 03:05:12.826 2518 INFO eventlet.wsgi.server [req-94c9fc5c-08a4-44cf-9574-e0a14e7a0aab 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:12] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.103292
2017-08-15 03:05:15.463 2516 INFO eventlet.wsgi.server [req-25982bf9-c858-4293-b85a-66f321e26452 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:15] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.026239
2017-08-15 03:05:20.583 2520 INFO eventlet.wsgi.server [req-7e2699fe-c286-4572-9f7a-04a2e83ea83b 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:20] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.026116
2017-08-15 03:05:28.222 2519 INFO eventlet.wsgi.server [req-82a60ab2-fdfd-4ccf-90a4-5fdd174a8e8d 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:28] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.026891
2017-08-15 03:05:38.589 2519 INFO eventlet.wsgi.server [req-8ae8f489-95e3-423e-aba2-b40d181bf33e 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:38] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.264245
2017-08-15 03:05:50.898 2515 WARNING glance.api.v1.upload_utils [req-70109b7d-c18f-4aca-8d45-aca59784816d 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] Client disconnected before sending all data to backend
2017-08-15 03:05:51.217 2516 INFO eventlet.wsgi.server [req-b560eae3-c75f-4aee-86af-94306b6cc1df 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:51] "HEAD /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 200 718 0.027622
2017-08-15 03:05:55.549 2515 INFO eventlet.wsgi.server [req-70109b7d-c18f-4aca-8d45-aca59784816d 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] 10.209.105.116 - - [15/Aug/2017 03:05:55] "PUT /v1/images/364532e5-6389-4868-9452-bbdf954575af HTTP/1.1" 400 396 74.894388 ...
(more)
2017-08-14 14:38:25 -0500 commented answer (glance S3 client) plan to support multipart upload method

Hello ,

I am trying to use Glance S3 , and have issues where it does not show any PUT request. Any help

2017-08-14 07:51:22 -0500 asked a question Glance does not send PUT request to S3 Server

I have been trying to upload the images from Glance onto the S3 server. It looks like the Glance does contact the S3 server, but does not upload the images. Besides, Glance does not looks to be sending PUT request on the S3 Server. The S3 server is listening on port 3145 Following are the configuration of the api .

[glance_store]
stores = file,http,swift,s3
default_store = s3
s3_store_host = s3.ga34:3145
s3_store_access_key = MGE1M2JhOWxxxBkOTc
s3_store_secret_key = YTgxYThiMWFiOTliYjUzMmUwMWMwxxxyMjdiNmE
s3_store_bucket = glance
# The S3 calling format used to determine the bucket. Either subdomain
# or path can be used. (string value)
#s3_store_bucket_url_format =



subdomain
s3_store_bucket_url_format = path
# What size, in MB, should S3 start chunking image files and do a
# multipart upload in S3. (integer value)
#s3_store_large_object_size = 100
s3_store_large_object_size = 2000

# What multipart upload part size, in MB, should S3 use when uploading
# parts. The size must be greater than or equal to 5M. (integer value)
#s3_store_large_object_chunk_size = 10
s3_store_large_object_chunk_size = 10

Some API Logs ::

Aug/2017 01:25:51] "POST /v1/images HTTP/1.1" 201 763 0.120749
2017-08-14 01:25:51.735 18366 DEBUG glance.api.middleware.version_negotiation [req-d34c2b26-7b40-452c-8e00-c6eaefac7e30 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] Determining version of request: PUT /v1/images/8bf4e86d-f804-4013-a4d9-f8e9fa795509 Accept: */* process_request /usr/lib/python2.7/site-packages/glance/api/middleware/version_negotiation.py:46
2017-08-14 01:25:51.736 18366 DEBUG glance.api.middleware.version_negotiation [req-d34c2b26-7b40-452c-8e00-c6eaefac7e30 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] Using url versioning process_request /usr/lib/python2.7/site-packages/glance/api/middleware/version_negotiation.py:58
2017-08-14 01:25:51.737 18366 DEBUG glance.api.middleware.version_negotiation [req-d34c2b26-7b40-452c-8e00-c6eaefac7e30 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] Matched version: v1 process_request /usr/lib/python2.7/site-packages/glance/api/middleware/version_negotiation.py:70
2017-08-14 01:25:51.738 18366 DEBUG glance.api.middleware.version_negotiation [req-d34c2b26-7b40-452c-8e00-c6eaefac7e30 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] new path /v1/images/8bf4e86d-f804-4013-a4d9-f8e9fa795509 process_request /usr/lib/python2.7/site-packages/glance/api/middleware/version_negotiation.py:71
2017-08-14 01:25:51.742 18366 DEBUG glance.common.client [req-55b63428-bb0a-48ee-af77-338e5514af09 661b5e9aa053480a8b311deb5b9689bf b20fc169510748639a312f4389f058e6 - - -] Constructed URL: http://0.0.0.0:9191/images/8bf4e86d-f804-4013-a4d9-f8e9fa795509 _construct_url /usr/lib/python2.7/site-packages/glance/common/client.py:398
2017-08-14 01:25:51.756 18369 DEBUG eventlet.wsgi.server [-] (18369) accepted ('10.209.105.116', 60830) server /usr/lib/python2.7/site-packages/eventlet/wsgi.py:826
2017-08-14 01:25:51.758 18369 DEBUG glance.api.middleware.version_negotiation [-] Determining version of request: GET /v1/images/detail Accept: */* process_request /usr/lib/python2.7/site-packages/glance/api/middleware/version_negotiation.py:46

Any Clues on this.

2017-06-29 05:19:40 -0500 received badge  Notable Question (source)
2017-06-11 14:09:48 -0500 received badge  Popular Question (source)
2017-06-11 12:03:47 -0500 commented answer Installing Cinder on Two host Ocata RDO

Thanks for the reply. Is there a way to start cinder-volume process on the other node. I presently , have second node running as compute node. I can run the command cinder-list on the second node but cannot see /etc/cinder.conf on the second node.

2017-06-10 15:38:34 -0500 received badge  Editor (source)
2017-06-10 15:22:00 -0500 asked a question Installing Cinder on Two host Ocata RDO

Hello,

I am planning To install OpenStack With Two nodes. I have a question is there a way to install cinder services on two host in OpenStack Ocata or Is it possible. I needed this for my requirement. I shall be provisioning storage to OpenStack node using NFS , that will be hosted on external storage, by specifying backend in /etc/cinder/cinder.conf. Now, I want to have this NFS hosted on the two different nodes, with different IPs , that will be exported to two different storage. I am using Packstack to deploy openstack. is there a way to define cinder hosts in answerfile.

Feel free to request me details if needed.

Thanks.

2017-02-24 12:52:08 -0500 received badge  Popular Question (source)
2017-02-24 12:52:08 -0500 received badge  Famous Question (source)
2017-02-24 12:52:08 -0500 received badge  Notable Question (source)
2016-06-30 11:26:55 -0500 commented answer "url_helper.py" Need to disable these messages

Thanks for the reply. Presently, I just managed to get rid of these messages by removing packages with cloud-init.

2016-06-27 19:30:25 -0500 asked a question "url_helper.py" Need to disable these messages

Hello Team,

I am working on the network configuration, where I have configured and external network of the subnet 10.209.82.x and have attached an Instance (RHEL 6.0) directly to this network and have assigned it with floating IP. However, on booting the instance I keep getting following message "url_helper.py[WARNING]:Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failied " , which in turns delays the booting of machine. Is there a way to disable this message.

Thanks

2016-06-17 08:59:35 -0500 received badge  Famous Question (source)
2016-06-13 04:24:49 -0500 received badge  Notable Question (source)
2016-06-13 03:32:34 -0500 received badge  Popular Question (source)
2016-06-11 16:30:01 -0500 asked a question Importing Cinder Block Device On NFS To Other OpenStack node

Hello Team,

I have an Openstack Node , where I am provisioning block device to Instances via NFS share. So, on the NFS share it looks like a block device created by cinder is in the form of a file. Now, I have one more openstack node , where I am sharing the same NFS share via Cinder. What I am trying to find out is, if the same file on the NFS share, that is acting as block device to instance on one openstack node, can it imported as a block device on the other openstack node. Ofcourse, I shall be detaching it from instances on first openstack node. This is like an use to for DR, where I can spun up a new VM on the other node and import the file to get the data back.

                     Are any  other solution for this kind of use case.

Thanks in Advance.

2016-06-07 06:35:47 -0500 received badge  Famous Question (source)
2016-06-07 00:17:05 -0500 received badge  Enthusiast
2016-06-06 21:19:48 -0500 received badge  Famous Question (source)
2016-06-05 13:27:22 -0500 received badge  Notable Question (source)
2016-06-04 23:50:50 -0500 received badge  Popular Question (source)
2016-06-04 05:36:53 -0500 commented answer How to Configure Two Bridge Network In Neutron

Are there any documented procedures, specially what changes do we have to make in plugin.ini . As before creating a subnet, on the openstack host ( all in one node) , I would be able to ping the network of 192.168.2.x network. considering eth1 as br-ex1 and changing ifcfg-br-ex1 and ifcfg-eth2

2016-06-03 10:21:40 -0500 asked a question How to Configure Two Bridge Network In Neutron

Hello Team ,

I need some heads up or procedure in adding two network in OpenStack. I am using openstack Kilo .

Network A eth0 configured as 10.209.86.202 . ( has a default gw and is connect to internet) Some Instance would be connecting to or shall be assigned to floating ips in subnect 10.209.86.x

Network B

eth1 configured as 192.168.2.10 ( This is a network without internet). Some instance would be connecting to this network with floating ip.

All the instance has local ip in the subnect 10.0.0.x.

So , what files I need to edit in /etc/neutron as I may have to put both the interfaces as br-ex and br-ex1.

Thanks

To Make it More Simpler ::

On My Setup the other network that I need to get connected had an interface p1p2 with ip 192.168.10.115 , So I converted it into br-ex1

 br-ex1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.155  netmask 255.255.255.0  broadcast 192.168.10.255
        inet6 fe80::a236:9fff:fe68:938e  prefixlen 64  scopeid 0x20<link>
        ether a0:36:9f:68:93:8e  txqueuelen 0  (Ethernet)
        RX packets 1733  bytes 569040 (555.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2496  bytes 260041 (253.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
p1p2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::a236:9fff:fe68:938e  prefixlen 64  scopeid 0x20<link>
        ether a0:36:9f:68:93:8e  txqueuelen 1000  (Ethernet)
        RX packets 101908  bytes 6605748 (6.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 2495  bytes 260107 (254.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Now, from the host machine I can ping other machine , after changing this.

[root@b010 ~]# ping 192.168.10.48 PING 192.168.10.48 (192.168.10.48) 56(84) bytes of data. 64 bytes from 192.168.10.48: icmp_seq=1 ttl=64 time=0.167 ms 64 bytes from 192.168.10.48: icmp_seq=2 ttl=64 time=0.212 ms

Now , what I am working out is I want my instance , once it is assigned with floating IP (say 192.168.10.100) this instance would be able to ping other machine in the network or the machine with 192.168.10.48. My present instances are in the range of 10.0.0.x subnet. The 192.168.10.x does has any Gateway ,

[root@b010 ~]# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         10.182.197.41   0.0.0.0         UG    0      0        0 br-ex
10.182.192.0    0.0.0.0         255.255.248.0   U     0      0        0 br-ex
169.254.0.0     0.0.0.0         255.255.0.0     U     1002   0        0 em1
169.254.0.0 ...
(more)
2016-06-02 15:28:42 -0500 commented question openstack-cinder-api.service failed on rhel7

what's the status of Selinux cat /etc/selinux/conf ???

2016-06-02 14:03:12 -0500 asked a question Cinder Block Storage Tuning Parameters

HEllo Team ,

I have configured Cinder Block Storage , in Kilo Version of OpenStack. This is connected to an external Storage via NFS. I wanted to know , to have a improved throughput , on the block device connected to Instances , are there any tuning parameter in Cinder. I understand most of the thing depends on NFS and Storage Device connected, however just wanted to check if in OpenStack we can workout anything at Cinder's Configuration.

Thanks.

2016-05-23 06:08:26 -0500 received badge  Notable Question (source)
2016-05-19 16:59:00 -0500 received badge  Popular Question (source)
2016-05-19 05:32:16 -0500 asked a question OpenStack Installation Fails On RHEL 7 Using RDO

Hello,

I am trying to install OpenStack Kilo Version with RDO on RHEL 7.0 and it looks to be failing with Following ERROR ::

RROR : Error appeared during Puppet run: 10.182.197.39_provision_glance Error: Could not prefetch glance_image provider 'glance': Execution of '/usr/bin/glance --os-tenant-name services --os-username glance
--os-password 7c551c390f304bfa --os-region-name RegionOne --os-auth-url http://192.168.10.15:35357/ image-show edd2a9e5-eebd-4b13-9b37-59d38382a4c5' returned 1: id

Some More Logs ::

^[[mNotice: Compiled catalog for xyz.com in environment production in 0.24 seconds^[[0m
^[[1;31mError: Could not prefetch glance_image provider 'glance': Execution of '/usr/bin/glance --os-tenant-name services --os-username glance --os-password 7c551c390f304bfa --os-region-name RegionOne --os-auth-url http://192.168.10.15:35357/ image-show edd2a9e5-eebd-4b13-9b37-59d38382a4c5' returned 1: id^[[0m
^[[mNotice: /Stage[main]/Main/Glance_image[cirros]/ensure: created^[[0m
^[[mNotice: Finished catalog run in 12.59 seconds^[[0m