Ask Your Question

wangrich's profile - activity

2017-03-07 19:16:05 -0500 received badge  Nice Answer (source)
2015-10-30 03:00:53 -0500 asked a question cpu_allocation_ratio doesn't work

I have 8 cores on my compute node and I want over-provision. According to config document, I set cpu_allocation_ratio to 16.0 and restart openstack-nova-compute service. However neither nova host-describe compute will report more vcpu available, nor I can deploy m1.xlarge instance(8 vcpu required, while compute has other instances deployed) on it.

Do I need to modify other configurations?

I'm using OpenStack Juno and most of the configuration was followed the official tutorial.

2015-10-28 23:48:48 -0500 commented question Instances are not able to access internet although there is inter-VM connectivity

If you can ping 8.8.8.8 after del-port ethX from br-ex, the problem should be on br-ex. Recently I met a case that I added ifcfg-br-ex file in /etc/sysconfig/network-scripts and it caused problem in ip link set br-ex up. I deleted it and all work well. Could you check the status of br-ex?

2015-10-28 04:46:14 -0500 commented question Instances are not able to access internet although there is inter-VM connectivity

Suppose you use br-ex or eth0 outside the router namespace to connect to the Internet, can you ping them inside router namespace? The packets will go through these interfaces if the connection is ok.

2015-10-28 04:38:53 -0500 commented question Router namespace is not able to ping 8.8.8.8

Could you please show your ip route result outside the router namespace? Does it have an entry like 192.168.0.0/16 dev br-ex but not through other devices like eth3?

2015-10-28 04:38:53 -0500 received badge  Commentator
2015-10-28 02:48:31 -0500 commented question Instances are not able to access internet although there is inter-VM connectivity

Can you ping 8.8.8.8 in network host's public network namespace?

2015-10-28 02:40:21 -0500 commented question how to bring NOVA folder after deleting from var/log??

Re-create is possible as the answers said. You can also select a new place and change the corresponding item in /etc/nova/nova.conf. All creation operations should be done manually.

2015-10-28 02:37:33 -0500 commented question Router namespace is not able to ping 8.8.8.8

Can you ping 8.8.8.8 in network node's public network namespace? If so can you ping 192.168.12.2(br-ex) and 192.168.0.3(external network gateway) inside router namespace?

2015-10-28 02:10:25 -0500 received badge  Famous Question (source)
2015-10-24 03:07:39 -0500 answered a question How to remove a Compute Node from Juno release

If you want the service records to be removed from the controller after you have done the migration, you can use nova service-delete <id> on the controller host, where <id> can be found from nova service-list.

2015-10-24 03:00:58 -0500 commented question How to remove compute node from havana

In my Juno deployment I have successfully used nova service-delete <id> to delete the dead nodes, where <id> can be found from nova service-list. However it will mark the corresponding records as deleted but not completely remove them.

2015-06-17 11:01:09 -0500 received badge  Notable Question (source)
2015-06-17 11:01:09 -0500 received badge  Popular Question (source)
2015-04-28 10:06:45 -0500 received badge  Famous Question (source)
2014-11-06 08:24:30 -0500 received badge  Popular Question (source)
2014-11-02 04:42:36 -0500 received badge  Notable Question (source)
2014-10-31 13:06:46 -0500 received badge  Famous Question (source)
2014-10-15 03:25:38 -0500 received badge  Popular Question (source)
2014-10-09 03:44:54 -0500 received badge  Famous Question (source)
2014-10-01 01:27:23 -0500 received badge  Notable Question (source)
2014-09-29 09:33:40 -0500 received badge  Self-Learner (source)
2014-09-29 09:33:40 -0500 received badge  Teacher (source)
2014-09-29 08:55:17 -0500 answered a question authentication required when creating port on demo-net

Well, I've solved the problem after nearly a month...

I lost one line in /etc/neutron/neutron.conf on client side:

admin_tenant_name = service

which made nova-compute.log show the token-getting request with

{"tenantName": null, "passwordCredentials": {"username": "neutron", "password": "REDACTED"}}

while the right form should be

{"tenantName": "service", "passwordCredentials": {"username": "neutron", "password": "REDACTED"}}
2014-09-29 08:48:21 -0500 commented answer How to clear token in Neutron client?

I checked the log and found the token cache was still there. The log did not show the client requested for token before port-creating request - it just used the cached one.

2014-09-29 08:47:05 -0500 commented answer How to clear token in Neutron client?

It might be useful in removing the files from server side. But what I need is delete token cache from client side. And in my deployment the server and client are on different hosts.

2014-09-29 08:25:21 -0500 received badge  Popular Question (source)
2014-09-28 22:39:26 -0500 asked a question How to clear token in Neutron client?

Neutron client will need a token to request for creating a port on tenant-network to Neutron server. The token-requesting process has succeed before, so the token might be cached.

Now I want to clear all the cached tokens. Is that possible? Or how can I force the Keystone server to reset all the tokens?

Thank you!


Updated:

In my deployment, the Neutron client and server are on different hosts. So it might not helpful to remove the token files from server side. What I want is removing the cached tokens from the client side, which might keep the token unchanged but force the client request for it before sending port-creating request.

2014-09-27 03:12:43 -0500 received badge  Notable Question (source)
2014-09-24 20:09:31 -0500 commented answer Terminology: Tenant or Project?

probably...sorry for the collision

2014-09-24 06:18:02 -0500 answered a question Terminology: Tenant or Project?

I'm sure that I've found 'tenant is called project in previous version Openstacks' somewhere. But sorry that I forgot where it is.

2014-09-24 00:14:42 -0500 asked a question deploy Openstack on Debian without debconf

Hello! I'm trying to deploy Openstack on Debian 7.6. I'm not familiar with debconf and want to step aside it. Can I directly update the configuration files in Openstack (for example /etc/neutron/neutron.conf)?

Thank you!

2014-09-19 22:07:25 -0500 received badge  Notable Question (source)
2014-09-19 09:24:46 -0500 received badge  Popular Question (source)
2014-09-18 20:28:42 -0500 received badge  Enthusiast
2014-09-17 20:43:17 -0500 asked a question Neutron client didn't use 'demo' token to create port on 'demo' network

Hello! I'm following the OpenStack installing guide on Ubuntu 14.04.

When I'm trying to boot a CirrOS instance using 'nova boot', I see that it uses python-neutronclient to send HTTP request to Neutron server for creating a new port on tenant subnetwork. The tenant is 'demo'. But ahead of creating the port, the neutron client connects to Keystone server with username: neutron, password: REDACTED which is surely not the credential of user demo. After the token is returned back, the neutron client attaches that token to the creating-port request to Neutron server. Finally, Neutron server responses with HTTP 401. And the booting process fails.

I'm wondering whether the neutron fetches the token using the right credential. I mean should it use username: demo, password: demopass, tenant:demo instead of username: neutron, password: neutronpass? As the booting finally fails, I hope to find the reason.

Thank you!

2014-09-16 17:48:32 -0500 marked best answer v2.0 in authentication or not?

Hello! I'm following http://docs.openstack.org/icehouse/install-guide/install/apt/content/neutron-ml2-compute-node.html (http://docs.openstack.org/icehouse/in...) to set up OpenStack on some QEMU instances.

I'm confused by the auth_url format: some like 'http://controller:xxxx/v2.0' and some just like 'http://controller:xxx' and without v2.0. I found in Havana the 'v2.0' may be a bug in authenticating process. So I want to know what should I do?

I followed the intructions on that page exactly and I met with 'Unauthorized: Authentication required' error when Neutron tried to create port on my 'demo-net'. So the problem is critical to me.

Great thanks!

2014-09-16 01:26:12 -0500 received badge  Popular Question (source)
2014-09-16 00:22:34 -0500 commented answer authentication required when creating port on demo-net

I've updated the question and pasted some logs on it. Before that I wrote a summary about the authenticating process. I've puzzled by this issue for nearly a week.....

2014-09-16 00:17:14 -0500 marked best answer authentication required when creating port on demo-net

Hi,all! I'm following the intructions on OpenStack Icehouse Installation Manual for Ubuntu 14.04 Server. After I installed Glance, Neutron, Keystone and Nova, I tried to launch Cirros instance as the manual suggested. However, the vm failed to start.

I checked nova-compute.log on contorller node. It says:

2014-09-15 20:48:50.939 1754 DEBUG neutronclient.client [-] 
REQ: curl -i h ttp://controller:9696/v2.0/ports.json -X POST -H "X-Auth-Token: (omitted)" -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-neutronclient" -d '{"port": {"binding:host_id": "compute", "admin_state_up": true, "network_id": "065eea33-798c-490c-ae45-65cb323b0383", "tenant_id": "a8c813f2bd9b4d41b895f933bac32c3d", "device_owner": "compute:None", "security_groups": ["335f1122-a119-42ab-8c6b-4c1dc07935cb"], "device_id": "65f8c769-d260-4fef-ae8e-db9edaf91140"}}'
 http_log_req /usr/lib/python2.7/dist-packages/neutronclient/common/utils.py:173


2014-09-15 20:48:50.958 1754 DEBUG neutronclient.client [-] RESP:{'status': '401', 'content-length': '23', 'x-openstack-request-id': 'req-471db8f6-9e67-4215-9ebf-3471164a8298', 'date': 'Mon, 15 Sep 2014 12:48:50 GMT', 'content-type': 'text/plain', 'www-authenticate': "Keystone uri='h ttp://controller:5000'"} **Authentication required**
 http_log_resp /usr/lib/python2.7/dist-packages/neutronclient/common/utils.py:179

2014-09-15 20:48:50.959 1754 ERROR nova.network.neutronv2.api [-] [instance: 65f8c769-d260-4fef-ae8e-db9edaf91140] Neutron error creating port on network 065eea33-798c-490c-ae45-65cb323b0383

I'm sure that the tenant name and password are right. Why is there the authenticating process in creating ports? And what should I do to pass the authenticating?

Thank you!


UPDATED at 04:46pm GMT

As @larsks suggested, I checked Neutron and Keystone server log on controller node, and found something wired and incomprehensible(to me). I've a summary about what might happen according to the logs: (some previous interactions omitted)

  1. the Neutron client on compute node asked for a token to the Keystone server on controller node(controller:35357), and got HTTP 200 response.
  2. after got the token, the Neutron client on compute node sent a request to Neutron server on controller node(controller:9696) to create a port on demo-net(a tenant network)
  3. The Neutron server got the request. It started a connection to Keystone to 'revoke' the token. And got HTTP 200.
  4. The Neutron server invalidated the user token, and responsed HTTP 401 to the Neutron client on compute node. That is wired!

NOTE: in step 2, the client put demo's tenant id and token got by (neutron:neutron_password) in the HTTP header. Then it asked the server to create a port on demo's network(the tenant id of demo-net [demo_tenant's id]). Is that inconsistent?

Could you bother to look into my logs and find out why Neutron server got the reponse from Keystone and decided the user token was invalid?

Some related logs pasted below:

I must confess that the logs are too long... as it is about two processes on three nodes.

nova-compute.log on compute node:

2014-09-16 10:11:05.512 1654 DEBUG neutronclient.client [-] 
REQ: curl -i h-ttp://controller:35357/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-neutronclient" -d '{"auth": {"tenantName": null, "passwordCredentials": {"username": "neutron", "password": "REDACTED"}}}'
 http_log_req /usr/lib/python2.7/dist-packages/neutronclient/common/utils.py ...
(more)