Ask Your Question

Kishore Devkate's profile - activity

2016-07-02 12:24:59 -0500 received badge  Student (source)
2015-11-17 16:12:34 -0500 received badge  Famous Question (source)
2015-10-29 04:19:36 -0500 received badge  Notable Question (source)
2015-10-14 08:38:29 -0500 received badge  Popular Question (source)
2015-10-01 07:09:53 -0500 answered a question cinder service is not working

@soumitrakarmakar .... I copied from putty only and above it is showing. I ran below commands on "controller and cinder" nodes.

[root@controller ~]# cinder-manage service list

[root@cinder1 ~]# cinder-manage service list

also see below output. you might get more clearity.

[root@cinder1 cinder]# cinder service-list

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

| Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |

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

| cinder-scheduler | controller | nova | enabled | up | 2015-10-01T17:25:18.000000 | - |

| cinder-volume | cinder1@lvm | nova | enabled | down | 2015-10-01T16:57:07.000000 | - |

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

2015-10-01 06:24:56 -0500 asked a question cinder service is not working

Hi Friends,

I am facing issue since long time while doing practice on my lappy. I checked the services running on from cinder node as below

[root@cinder1 ~]# cinder-manage service list

/usr/lib/python2.7/site-packages/cinder/openstack/common/service.py:38: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_config instead. from oslo.config import cfg No handlers could be found for logger "oslo_config.cfg"

Binary Host Zone Status State Updated At

cinder-volume cinder1@lvm nova enabled :-) 2015-10-01 15:56:44

cinder-scheduler controller nova enabled XXX 2015-10-01 16:24:58

===================================

And from controller node i tried as below

[root@controller ~]# cinder-manage service list

/usr/lib/python2.7/site-packages/cinder/openstack/common/service.py:38: DeprecationWarning: The oslo namespace package is deprecated. Please use oslo_config instead. from oslo.config import cfg No handlers could be found for logger "oslo_config.cfg"

Binary Host Zone Status State Updated At

cinder-volume cinder1@lvm nova enabled XXX 2015-10-01 16:01:16

cinder-scheduler controller nova enabled :-) 2015-10-01 16:29:28

Somone please help me in it.

2015-09-15 02:08:27 -0500 answered a question Neutron: Failed to notify nova on events

have you created private network ?

2015-07-22 05:28:47 -0500 received badge  Famous Question (source)
2015-07-22 05:11:48 -0500 commented answer unable to access public (external) network in openstack

@dbaxps ... sent you the friend request and message also in linkedin

2015-07-22 04:25:26 -0500 commented answer unable to access public (external) network in openstack

@dbaxps .... do not know what exactly need to do in it, could you please take access and check it what you want to check ?

2015-07-22 02:53:21 -0500 commented answer unable to access public (external) network in openstack

@dbaxps ....i will check it again if not works then could you please take access to my lappy and have a look on it if possible

2015-07-22 02:13:17 -0500 commented answer unable to access public (external) network in openstack

@dbaxps .... i am totally newer for it...now what action needs to do from my side ?

2015-07-22 01:35:49 -0500 commented answer unable to access public (external) network in openstack

@dbaxps .... how to give you the output as there is no more than 280 characters accepting...please suggest me

2015-07-22 01:34:14 -0500 answered a question unable to access public (external) network in openstack

@dbaxps ... below is the requested output

**[root@network ~]# ovs-vsctl show**
17412c00-3337-4db6-911b-534e24387c87
    Bridge br-tun
        Port br-tun
            Interface br-tun
                type: internal
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "gre-0a00011f"
            Interface "gre-0a00011f"
                type: gre
                options: {df_default="true", in_key=flow, local_ip="10.0.1.21", out_key=flow, remote_ip="10.0.1.31"}
    Bridge br-int
        fail_mode: secure
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port "qr-82f4bbfd-d9"
            tag: 2
            Interface "qr-82f4bbfd-d9"
                type: internal
        Port br-int
            Interface br-int
                type: internal
        Port int-br-ex
            Interface int-br-ex
                type: patch
                options: {peer=phy-br-ex}
    Bridge br-ex
        Port br-ex
            Interface br-ex
                type: internal
        Port "qg-ec605f0c-db"
            Interface "qg-ec605f0c-db"
                type: internal
        Port "eno50332208"
            Interface "eno50332208"
        Port phy-br-ex
            Interface phy-br-ex
                type: patch
                options: {peer=int-br-ex}
    ovs_version: "2.3.1"

**[root@network ~]# ip a**
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno16777736: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:41:41:6a brd ff:ff:ff:ff:ff:ff
    inet 10.0.0.21/24 brd 10.0.0.255 scope global eno16777736
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe41:416a/64 scope link
       valid_lft forever preferred_lft forever
3: eno33554984: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:0c:29:41:41:74 brd ff:ff:ff:ff:ff:ff
    inet 10.0.1.21/24 brd 10.0.1.255 scope global eno33554984
       valid_lft forever preferred_lft forever
    inet6 fe80::20c:29ff:fe41:4174/64 scope link
       valid_lft forever preferred_lft forever
4: eno50332208: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master ovs-system state UP qlen 1000
    link/ether 00:0c:29:41:41:7e brd ff:ff:ff:ff:ff:ff
    inet6 fe80::20c:29ff:fe41:417e/64 scope link
       valid_lft forever preferred_lft forever
5: ovs-system: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether 56:63:8f:41:df:2a brd ff:ff:ff:ff:ff:ff
6: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN
    link/ether 00:0c:29:41:41:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.139.200/24 brd 192.168.139.255 scope global dynamic br-ex
       valid_lft 1392sec preferred_lft 1392sec
    inet6 fe80::20c:29ff:fe41:417e/64 scope link
       valid_lft forever preferred_lft forever
7: br-int: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether b6:1f:0b:57:b6:4f brd ff:ff:ff:ff:ff:ff
10: br-tun: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
    link/ether fe:f9:ba:27:e0:47 brd ff:ff:ff:ff:ff:ff
2015-07-22 00:25:36 -0500 commented answer Instances can't reach external network and Internet

@Zaino I am also having the same issue could you please help me to resolve the issue which i am facing since long time i am trying it but not working for me....i am using centos 7 in vmware workstation nad created 3 nodes for openstack environment

2015-07-20 13:12:23 -0500 received badge  Notable Question (source)
2015-07-20 06:31:58 -0500 received badge  Popular Question (source)
2015-07-20 05:41:09 -0500 received badge  Commentator
2015-07-20 05:41:09 -0500 commented answer Role of "br-int" in neutron GRE networking

Hi Deepa, Can you please help me in networking things...I have configured everything such as controller, compute and network node without any error...but i am unable to communicate external (public) network but able to communicate internal (private) network within openstack.

2015-07-20 05:34:32 -0500 commented answer unable to access public (external) network in openstack

I am thinking...i am missing something to configure...do not know what exactly i am missing....if you want logs i can share it

2015-07-20 05:33:07 -0500 commented answer unable to access public (external) network in openstack

@dbaxps .... i followed the doc given above but no luck internal networking working but external is not working

2015-07-20 05:32:40 -0500 answered a question unable to access public (external) network in openstack

@dbaxps .... i followed the doc given above but no luck internal networking working but external is not working

2015-07-20 03:07:55 -0500 asked a question unable to access public (external) network in openstack

Hi All,

I have installed centos 7 on my vmware in my lappy and configured openstack as below

1) controller node 2) compute node 3) network node

everything is working fine, when i am trying to access public network (external network) for internet and outside of openstack..it is unable to access...can someone please help me i googled it but not getting solution for it.

BR, Kishore

2015-07-17 04:36:40 -0500 received badge  Famous Question (source)
2015-06-26 03:52:55 -0500 received badge  Famous Question (source)
2015-06-09 07:59:39 -0500 received badge  Notable Question (source)
2015-06-01 04:39:36 -0500 received badge  Notable Question (source)
2015-05-31 14:14:46 -0500 received badge  Popular Question (source)
2015-05-29 10:59:45 -0500 received badge  Popular Question (source)
2015-05-29 00:09:49 -0500 commented question Caught error: Volume driver not ready.

@jdexter ..... I removed all the nodes and everything now doing packstart practice as i was waited for someone who help me but no one were responded that is why thanks for the response if in furture i get any issue will post here again....as i already googled it but did not get the proper solution

2015-05-28 03:29:04 -0500 asked a question Caught error: Volume driver not ready.

Hi Friends,

i have created an instance and volume in cinder, but issue facing is that when i tried to attach the volume to the instance i am unable to attach it to instance. Below is the log of /var/log/cinder/api.log.

"2015-05-22 19:02:28.586 2763 ERROR cinder.api.middleware.fault [req-0721c714-cc3e-4b60-a91c-691f4c320d18 b48ac80d198347cd8d0f61eb0a5d7b3e 72d36b9ab4d74d57ae39095f4dbf6d80 - - -] Caught error: Volume driver not ready."

Could someone please help me in it.

BR, Kishore

2015-05-26 00:40:10 -0500 answered a question Caught error: Volume driver not ready.
[root@block1 ~]# cat /etc/cinder/cinder.conf
[DEFAULT]
rpc_backend = rabbit
rabbit_host = 10.0.0.11
rabbit_password = guest
auth_strategy = keystone
my_ip = 10.0.0.41
glance_host = 10.0.0.11
iscsi_helper = lioadm
verbose = True

#
# Options defined in oslo.messaging
#

# Use durable queues in AMQP. (boolean value)
# Deprecated group/name - [DEFAULT]/rabbit_durable_queues
#amqp_durable_queues=false

# Auto-delete queues in AMQP. (boolean value)
#amqp_auto_delete=false

# Size of RPC connection pool. (integer value)
#rpc_conn_pool_size=30

# Qpid broker hostname. (string value)
#qpid_hostname=localhost

# Qpid broker port. (integer value)
#qpid_port=5672

# Qpid HA cluster host:port pairs. (list value)
#qpid_hosts=$qpid_hostname:$qpid_port

# Username for Qpid connection. (string value)
#qpid_username=

# Password for Qpid connection. (string value)
#qpid_password=

# Space separated list of SASL mechanisms to use for auth.
# (string value)
#qpid_sasl_mechanisms=

# Seconds between connection keepalive heartbeats. (integer
# value)
#qpid_heartbeat=60

# Transport to use, either 'tcp' or 'ssl'. (string value)
#qpid_protocol=tcp

# Whether to disable the Nagle algorithm. (boolean value)
#qpid_tcp_nodelay=true

# The number of prefetched messages held by receiver. (integer
# value)
#qpid_receiver_capacity=1

# The qpid topology version to use.  Version 1 is what was
# originally used by impl_qpid.  Version 2 includes some
# backwards-incompatible changes that allow broker federation
# to work.  Users should update to version 2 when they are
# able to take everything down, as it requires a clean break.
# (integer value)
#qpid_topology_version=1

# SSL version to use (valid only if SSL enabled). valid values
# are TLSv1 and SSLv23. SSLv2 and SSLv3 may be available on
# some distributions. (string value)
#kombu_ssl_version=

# SSL key file (valid only if SSL enabled). (string value)
#kombu_ssl_keyfile=

# SSL cert file (valid only if SSL enabled). (string value)
#kombu_ssl_certfile=

# SSL certification authority file (valid only if SSL
# enabled). (string value)
#kombu_ssl_ca_certs=

# How long to wait before reconnecting in response to an AMQP
# consumer cancel notification. (floating point value)
#kombu_reconnect_delay=1.0

# The RabbitMQ broker address where a single node is used.
# (string value)
#rabbit_host=localhost

# The RabbitMQ broker port where a single node is used.
# (integer value)
#rabbit_port=5672

# RabbitMQ HA cluster host:port pairs. (list value)
#rabbit_hosts=$rabbit_host:$rabbit_port

# Connect over SSL for RabbitMQ. (boolean value)
#rabbit_use_ssl=false

# The RabbitMQ userid. (string value)
#rabbit_userid=guest

# The RabbitMQ password. (string value)
#rabbit_password=guest

# The RabbitMQ login method. (string value)
#rabbit_login_method=AMQPLAIN

# The RabbitMQ virtual host. (string value)
#rabbit_virtual_host=/

# How frequently to retry connecting with RabbitMQ. (integer
# value)
#rabbit_retry_interval=1

# How long to backoff for between retries when connecting to
# RabbitMQ. (integer value)
#rabbit_retry_backoff=2

# Maximum number of RabbitMQ connection retries. Default is 0
# (infinite retry count). (integer value)
#rabbit_max_retries=0

# Use HA queues in RabbitMQ (x-ha-policy: all). If you change
# this option, you must wipe the RabbitMQ database. (boolean
# value)
#rabbit_ha_queues=false

# Deprecated, use rpc_backend=kombu+memory or rpc_backend=fake
# (boolean value)
#fake_rabbit=false

# ZeroMQ bind address. Should be a wildcard (*), an ethernet
# interface, or IP. The "host" option should point or resolve
# to this address. (string value)
#rpc_zmq_bind_address=*

# MatchMaker driver. (string value)
#rpc_zmq_matchmaker=oslo.messaging._drivers.matchmaker.MatchMakerLocalhost

# ZeroMQ receiver listening port. (integer value)
#rpc_zmq_port=9501

# Number of ZeroMQ contexts, defaults to 1. (integer value ...
(more)
2015-05-22 06:04:08 -0500 asked a question Caught error: Volume driver not ready.

Hi Friends,

i have created an instance and volume in cinder, but issue facing is that when i tried to attach the volume to the instance i am unable to attach it to instance. Below is the log of /var/log/cinder/api.log.

"2015-05-22 19:02:28.586 2763 ERROR cinder.api.middleware.fault [req-0721c714-cc3e-4b60-a91c-691f4c320d18 b48ac80d198347cd8d0f61eb0a5d7b3e 72d36b9ab4d74d57ae39095f4dbf6d80 - - -] Caught error: Volume driver not ready."

Could someone please help me in it.

BR, Kishore

2015-05-11 11:54:35 -0500 received badge  Notable Question (source)
2015-01-31 14:30:22 -0500 received badge  Popular Question (source)
2014-12-10 00:02:58 -0500 received badge  Famous Question (source)
2014-11-28 04:27:20 -0500 commented question Internal Server Error

Now it resolved.

2014-11-28 03:07:15 -0500 asked a question Internal Server Error

Hi All,

When i tried to access my openstack dashboard using http://10.0.0.11/dashboad . Its throwing some error as below. Please help me to resolve it.

"Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log."

2014-11-28 01:12:17 -0500 received badge  Enthusiast
2014-11-27 20:50:32 -0500 received badge  Famous Question (source)
2014-11-27 09:26:03 -0500 commented answer AMQP server on 10.0.0.11:5672 is unreachable

@Ram.Meena,

yes it was giving trouble so I disabled it. now working fine. Thanks Ram Meena for the help.

BR, Kishore

2014-11-27 07:00:03 -0500 commented answer AMQP server on 10.0.0.11:5672 is unreachable

@dbaxps,

Yet i did not installed neutron service. I stucked at compute configuration on compute node.

BR, Kishore