sowrdking's profile - activity

2015-05-11 07:20:44 -0600 received badge  Famous Question (source)
2015-05-04 05:32:49 -0600 received badge  Famous Question (source)
2015-03-19 03:31:39 -0600 received badge  Famous Question (source)
2015-03-10 07:17:56 -0600 received badge  Famous Question (source)
2014-12-25 02:29:17 -0600 received badge  Notable Question (source)
2014-12-19 05:52:53 -0600 received badge  Famous Question (source)
2014-12-16 20:17:35 -0600 received badge  Notable Question (source)
2014-12-16 20:17:35 -0600 received badge  Popular Question (source)
2014-12-10 22:37:36 -0600 marked best answer Messagingtimeout on CentOS 7 when initial network

Hi All,

I get a error message when initial network.

nova network-create demo-net --bridge-interface br100 --multi-host T --fixed-range-v4 10.134.12.154/22

Error:

ERROR: The server has either erred or is incapable of performing the requested operation. (HTTP 500) (Request-ID: req-3ec9e4d7-505e-446c-b4b4-046b30701ac2)

Log:

2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     return self.client.call(ctxt, 'create_networks', **kwargs)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/client.py", line 361, in call
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     return self.prepare().call(ctxt, method, **kwargs)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/rpc/client.py", line 150, in call
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     wait_for_reply=True, timeout=timeout)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/transport.py", line 90, in _send
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     timeout=timeout)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py", line 412, in send
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     return self._send(target, ctxt, message, wait_for_reply, timeout)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py", line 403, in _send
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     result = self._waiter.wait(msg_id, timeout)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py", line 267, in wait
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     reply, ending = self._poll_connection(msg_id, timeout)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack   File "/usr/lib/python2.7/site-packages/oslo/messaging/_drivers/amqpdriver.py", line 217, in _poll_connection
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack     % msg_id)
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack MessagingTimeout: Timed out waiting for a reply to message ID 44d4625e1dd647109c0671f7fb7dda83
2014-09-15 02:34:03.479 8860 TRACE nova.api.openstack

One problem is that I'm not sure I'm able to cute network like that. On the installation document, it said the network shares the same subnet on the compute node. So, does it means I need to use the same subnet as my psychical network to initial network?

2014-11-25 16:37:30 -0600 received badge  Notable Question (source)
2014-11-19 11:09:48 -0600 received badge  Famous Question (source)
2014-11-19 00:52:36 -0600 received badge  Notable Question (source)
2014-11-04 02:12:17 -0600 received badge  Popular Question (source)
2014-10-30 04:48:30 -0600 commented answer ceilometer won't show ironic data

Hello, I'll take a look at it. Thanks.

2014-10-30 04:32:03 -0600 commented answer ceilometer won't show ironic data

Hello, My project is based on Icehouse.

2014-10-30 04:05:17 -0600 received badge  Supporter (source)
2014-10-30 04:02:40 -0600 commented question ceilometer won't show ironic data

Hello, I have update my own question, please take a look at the settings. Thanks.

2014-10-30 03:26:18 -0600 asked a question ceilometer won't show ironic data

Hi All,

I'm trying to send IPMI data to ceilometer, ceilometer now only show glance and cinder data. And my ironic command works fine.

But when I use ironic-api on controller node, it will said

/usr/local/lib/python2.7/dist-packages/pecan/__init__.py:110: RuntimeWarning: `static_root` is only used when `debug` is True, ignoring
  RuntimeWarning
2014-10-30 16:21:59.862 14016 INFO keystoneclient.middleware.auth_token [-] Starting keystone auth_token middleware
2014-10-30 16:21:59.863 14016 INFO keystoneclient.middleware.auth_token [-] Using /tmp/keystone-signing-Z0FsdR as cache directory for signing certificate
2014-10-30 16:21:59.864 14016 CRITICAL ironic [-] [Errno 98] Address already in use

And when I use ironic-conductor, it will said

2014-10-30 16:22:13.852 14031 ERROR stevedore.extension [-] Could not load 'pxe_seamicro': PXEAndSeaMicroDriver
2014-10-30 16:22:13.852 14031 ERROR stevedore.extension [-] PXEAndSeaMicroDriver
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension Traceback (most recent call last):
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 162, in _load_plugins
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension     verify_requirements,
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/enabled.py", line 66, in _load_one_plugin
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension     verify_requirements,
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 179, in _load_one_plugin
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension     obj = plugin(*invoke_args, **invoke_kwds)
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/ironic/drivers/pxe.py", line 102, in __init__
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension     raise exception.DriverNotFound('PXEAndSeaMicroDriver')
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension DriverNotFound: PXEAndSeaMicroDriver
2014-10-30 16:22:13.852 14031 TRACE stevedore.extension
2014-10-30 16:22:13.853 14031 ERROR stevedore.extension [-] Could not load 'fake_seamicro': FakeSeaMicroDriver
2014-10-30 16:22:13.853 14031 ERROR stevedore.extension [-] FakeSeaMicroDriver
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension Traceback (most recent call last):
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 162, in _load_plugins
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension     verify_requirements,
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/enabled.py", line 66, in _load_one_plugin
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension     verify_requirements,
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/stevedore/extension.py", line 179, in _load_one_plugin
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension     obj = plugin(*invoke_args, **invoke_kwds)
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension   File "/usr/lib/python2.7/dist-packages/ironic/drivers/fake.py", line 87, in __init__
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension     raise exception.DriverNotFound('FakeSeaMicroDriver')
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension DriverNotFound: FakeSeaMicroDriver
2014-10-30 16:22:13.853 14031 TRACE stevedore.extension

It seems ... (更多)

2014-10-30 01:27:36 -0600 commented answer ceilometer meter-list is empty

Hello, I found entry_point.txt in /usr/lib/python2.7/dist-packages/ceilometer-2014.1.3.egg-info/ and I add notifier into it. But the result is still the same, it still a empty list.

After I change .messaging:NotifierPublisher to rpc:RPCPublisher, and it works. Thanks.

2014-10-29 22:26:31 -0600 commented answer ceilometer meter-list is empty

Hello, I only have /usr/local/lib/python2.7/dist-packages/ and there is no ceilometer folder. My python version is 2.7.6.

2014-10-29 04:49:27 -0600 answered a question ceilometer meter-list is empty

Hello,

My version is Icehouse, and below is my pipeline


sources: - name: meter_source interval: 600 meters: - "" sinks: - meter_sink - name: cpu_source interval: 600 meters: - "cpu" sinks: - cpu_sink - name: disk_source interval: 600 meters: - "disk.read.bytes" - "disk.read.requests" - "disk.write.bytes" - "disk.write.requests" sinks: - disk_sink - name: network_source interval: 600 meters: - "network.incoming.bytes" - "network.incoming.packets" - "network.outgoing.bytes" - "network.outgoing.packets" sinks: - network_sink sinks: - name: meter_sink transformers: publishers: - notifier:// - name: cpu_sink transformers: - name: "rate_of_change" parameters: target: name: "cpu_util" unit: "%" type: "gauge" scale: "100.0 / (10*9 * (resource_metadata.cpu_number or 1))" publishers: - notifier:// - name: disk_sink transformers: - name: "rate_of_change" parameters: source: map_from: name: "disk\.(read|write)\.(bytes|requests)" unit: "(B|request)" target: map_to: name: "disk.\1.\2.rate" unit: "\1/s" type: "gauge" publishers: - notifier:// - name: network_sink transformers: - name: "rate_of_change" parameters: source: map_from: name: "network\.(incoming|outgoing)\.(bytes|packets)" unit: "(B|packet)" target: map_to: name: "network.\1.\2.rate" unit: "\1/s" type: "gauge" publishers:

2014-10-24 04:27:04 -0600 asked a question ceilometer meter-list is empty

Hi All,

I installed ceilometer, and other installed are nova, keystone, glance, cinder. After I install it at controller and compute side, like the steps in openstack. I used "ceilometer meter-list", it always return empty and just the tables column.

After I used " ceilometer-agent-central", it will show

 2014-10-24 17:22:52.035 21907 TRACE ceilometer.pipeline   File "/usr/lib/python2.7/dist-paes/stevedore/driver.py", line 91, in _init_plugins
2014-10-24 17:22:52.035 21907 TRACE ceilometer.pipeline     (self.namespace, name))
2014-10-24 17:22:5ckag2.035 21907 TRACE ceilometer.pipeline RuntimeError: No 'ceilometer.publisher' driver found, looking for 'notifier'
2014-10-24 17:22:52.035 21907 TRACE ceilometer.pipeline

At the compute side I used "ceilometer-agent-compute", it will show

2014-10-24 17:13:32.078 6834 TRACE ceilometer.pipeline   File "/usr/lib/python2.7/dist-packages/stevedore/driver.py", line 91, in _init_plugins
2014-10-24 17:13:32.078 6834 TRACE ceilometer.pipeline     (self.namespace, name))
2014-10-24 17:13:32.078 6834 TRACE ceilometer.pipeline RuntimeError: No 'ceilometer.publisher' driver found, looking for 'notifier'
2014-10-24 17:13:32.078 6834 TRACE ceilometer.pipeline

Now, I search the issue about No ceilometer.publisher driver found, but no answer was be found. Do anyone have any idea about what's going on.

======================2014/10/29 update=======================================

Hello,

My version is Icehouse and below is my pipeline.yaml

---
sources:
    - name: meter_source
      interval: 600
      meters:
          - "*"
      sinks:
          - meter_sink
    - name: cpu_source
      interval: 600
      meters:
          - "cpu"
      sinks:
          - cpu_sink
    - name: disk_source
      interval: 600
      meters:
          - "disk.read.bytes"
          - "disk.read.requests"
          - "disk.write.bytes"
          - "disk.write.requests"
      sinks:
          - disk_sink
    - name: network_source
      interval: 600
      meters:
          - "network.incoming.bytes"
          - "network.incoming.packets"
          - "network.outgoing.bytes"
          - "network.outgoing.packets"
      sinks:
          - network_sink
sinks:
    - name: meter_sink
      transformers:
      publishers:
          - notifier://
    - name: cpu_sink
      transformers:
          - name: "rate_of_change"
            parameters:
                target:
                    name: "cpu_util"
                    unit: "%"
                    type: "gauge"
                    scale: "100.0 / (10**9 * (resource_metadata.cpu_number or 1))"
      publishers:
          - notifier://
    - name: disk_sink
      transformers:
          - name: "rate_of_change"
            parameters:
                source:
                    map_from:
                        name: "disk\\.(read|write)\\.(bytes|requests)"
                        unit: "(B|request)"
                target:
                    map_to:
                        name: "disk.\\1.\\2.rate"
                        unit: "\\1/s"
                    type: "gauge"
      publishers:
          - notifier://
    - name: network_sink
      transformers:
          - name: "rate_of_change"
            parameters:
                source:
                   map_from:
                       name: "network\\.(incoming|outgoing)\\.(bytes|packets)"
                       unit: "(B|packet)"
                target:
                    map_to:
                        name: "network.\\1.\\2.rate"
                        unit: "\\1/s"
                    type: "gauge"
      publishers:
          - notifier://

======================2014/10/30 add ceilometer.confi======================================

[DEFAULT]

#
# Options defined in ceilometer.middleware
#

# Exchanges name to listen for notifications. (multi valued)
http_control_exchanges=nova
http_control_exchanges=glance
http_control_exchanges=neutron
http_control_exchanges=cinder


#
# Options defined in ceilometer.pipeline
#

# Configuration file for pipeline definition. (string value)
#pipeline_cfg_file=pipeline.yaml


#
# Options defined in ceilometer.sample
auth_strategy=keystone
sqlite_db=ceilometer.sqlite
log_dir=/var/log/ceilometer
rpc_backend=ceilometer.openstack.common.rpc.impl_kombu
rabbit_host=x.x.x.x
rabbit_userid=guest
rabbit_password = guest

[api]

#
# Options defined in ceilometer.api
#

# The port for the ceilometer API server. (integer value)
# Deprecated group/name - [DEFAULT]/metering_api_port
port=8777

[database]

#
# Options defined in ceilometer.openstack.common.db.api
#

# The backend to use for db (string value)
# Deprecated group/name - [DEFAULT]/db_backend
backend=sqlalchemy

connection=mongodb://ceilometer:password@controller:27017/ceilometer

[notification]

#
# Options defined in ceilometer.notification
#

# Acknowledge message when ...
(更多)
2014-10-21 09:13:34 -0600 received badge  Popular Question (source)
2014-10-19 02:17:10 -0600 received badge  Notable Question (source)
2014-10-19 02:17:10 -0600 received badge  Popular Question (source)
2014-10-12 08:34:24 -0600 received badge  Notable Question (source)
2014-10-01 05:38:45 -0600 received badge  Popular Question (source)
2014-10-01 04:41:02 -0600 received badge  Scholar (source)
2014-10-01 04:40:39 -0600 answered a question cannot ping OpenStack launch instance

Un-comment public-interface=br100 and flat-network-bridge=br100. Problem solved. Thanks.

2014-09-30 03:26:22 -0600 asked a question cannot ping OpenStack launch instance

Hi All,

I have installed OpenStack on ubuntu 14.04 and follow the steps by Geek Everything is fine but the IP is wired. I cut my network 10.134.12.208/28, but when I launch a cirros I can't ping it. I have set All ICMP, SSH, HTTP into security rules, and I can use the VM by dashboard. 1. But the IP in dashboard shows 10.134.12.210, and in console is 10.134.12.201. 2. I can't ping both IP.

Here is the VM log

=== cirros: current=0.3.2 uptime=1.14 === === pinging gateway failed, debugging connection === ############ debug start ##############

/etc/init.d/sshd start Starting dropbear sshd: OK

ifconfig -a eth0 Link encap:Ethernet HWaddr

FA:16:3E:49:E6:58
inet addr:10.134.12.201 Bcast:10.134.15.255 Mask:255.255.252.0 inet6 addr: fe80::f816:3eff:fe49:e658/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:83 errors:0 dropped:2 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:11311 (11.0 KiB) TX bytes:980 (980.0 B)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2 errors:0 dropped:0 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:211 (211.0 B) TX bytes:211 (211.0 B)

route -n Kernel IP routing table Destination Gateway

Genmask Flags Metric Ref
Use Iface 0.0.0.0 10.134.15.250 0.0.0.0 UG 0 0 0 eth0 10.134.12.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0

cat /etc/resolv.conf search supermicro.com.tw nameserver

10.128.8.1 nameserver 10.133.8.1

ping -c 5 10.134.15.250 PING 10.134.15.250 (10.134.15.250): 56 data bytes

--- 10.134.15.250 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss

pinging nameservers

ping -c 5 10.128.8.1 PING 10.128.8.1 (10.128.8.1): 56 data bytes

--- 10.128.8.1 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss

ping -c 5 10.133.8.1 PING 10.133.8.1 (10.133.8.1): 56 data bytes

Do anyone have idea about this?

2014-09-22 00:59:37 -0600 received badge  Enthusiast
2014-09-19 06:57:31 -0600 received badge  Popular Question (source)
2014-09-19 01:50:23 -0600 commented question nova boot keeps in spawning

If I bind br100 to my active interface eno1, br100 state is up. But then I cannot ping to controller or other website. So, is there steps missing when I create external interface "eth1"? I only add a copy of eno1 in /etc/sysconfig/network-scripts/ifcfg-eno1 to ifcfg-eth1 and modify the content.

2014-09-19 01:47:33 -0600 commented question nova boot keeps in spawning

Hello,

I found out that the reason is because nova-manage cannot find my device "eth1", which I use it as a external interface. I did the steps the guide shows, but the eth1 isn't recognize by the system. I also use "ip a | grep state" , eth1 state isn't up and br100 is not bind.

If I bind br100 to my active interface eno1, br100 state is up. But then I cannot ping to controller or other website. So, is there steps missing when I create external interface "eth1"? I only add a copy of eno1 in /etc/sysconfig/network-scripts/ifcfg-eno1 to ifcfg-eth1 and modify the content.

Update================= I try to boot another instance and here is the compute log I found may be the root cause.

2014-09-19 05:29:24.212 4972 DEBUG nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Tearing down appliance teardown /usr/lib/python2.7/site-packages/nova/virt/disk/vfs/guestfs.py:141 2014-09-19 05:29:24.214 4972 WARNING nova.virt.disk.vfs.guestfs [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Failed to close augeas aug_close: do_aug_close: you must call 'aug-init' first to initialize Augeas 2014-09-19 05:29:24.249 4972 DEBUG nova.virt.disk.api [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Unable to mount image /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with error Error mounting /var/lib/nova/instances/63ed8a3b-d11f-46ca-8a5d-cf8ad1a54c94/disk with libguestfs (mount_options: /dev/sda on / (options: ''): mount: /dev/sda is write-protected, mounting read-only mount: unknown filesystem type '(null)'). Cannot resize. is_image_partitionless /usr/lib/python2.7/site-packages/nova/virt/disk/api.py:211 2014-09-19 05:29:24.249 4972 DEBUG nova.openstack.common.lockutils [req-55fa24cf-163d-47b5-a90b-92264dab990c 160c9c6f2bb44e41836462d78d53ace0 587a337af7884dd69b2a7d77eb68e572] Released file lock "e56d642d025882a2734f5d19747f23205f5c0cc8" at /var/lib/nova/instances/locks/nova-e56d642d025882a2734f5d19747f23205f5c0cc8 lock /usr/lib/python2.7/site-packages/nova/openstack/common/lockutils.py:210

Any solution??

2014-09-18 20:49:41 -0600 asked a question nova boot keeps in spawning

Hi all,

My OS is CentOS7 and use nova network type. I can't boot my instance and the state keeps in spawning.

+--------------------------------------+----------------+--------+------------+-------------+----------+
| ID                                   | Name           | Status | Task State | Power State | Networks |
+--------------------------------------+----------------+--------+------------+-------------+----------+
| c801f8eb-c8a9-477f-9415-0012685e86e1 | admin-instance | BUILD  | spawning   | NOSTATE     |          |
+--------------------------------------+----------------+--------+------------+-------------+----------+

I check the log in controller and compute, there are no error message. The compute node have log in nova-compute.log like this, WARNING nova.compute.manager [-] Found 1 in the database and 0 on the hypervisor.

Do anyone have an idea about this situation? P.S Will IP conflict cause this issue?

2014-09-18 20:31:12 -0600 answered a question cannout boot instance

Thanks sushma.

I found out that my compute IP is conflict other system, so I changed the IP and it will not reply error state. It's task state stay on spawning and no error log, but this is another issue. I will find if there are same topic or open a new issue. Thanks.