发起问题

tongda 的档案 - activity

2020-04-05 15:06:03 -0500 获得奖牌  受欢迎的问题 (source)
2020-04-05 15:06:03 -0500 获得奖牌  著名问题 (source)
2020-04-05 15:06:03 -0500 获得奖牌  热门的问题 (source)
2018-05-12 04:40:54 -0500 获得奖牌  热门的问题 (source)
2018-05-12 04:40:54 -0500 获得奖牌  受欢迎的问题 (source)
2018-05-12 04:40:54 -0500 获得奖牌  著名问题 (source)
2013-08-28 12:26:26 -0500 回答问题 Performance problem with keystone tokens.

Thanks Tiantian Gao, that solved my question.

2013-08-28 12:18:35 -0500 回答问题 How to Create or Modify Availability Zone Programmably

I found that using "nova create-aggregate" can assign an availability zone, if not exist, a new one will be created. So this may be a way to manipulate availability zones.

2013-08-28 12:04:39 -0500 问了问题 Performance problem with keystone tokens.

I built a testing environment with a controller(4 cores, 8GB RAM, installing kestone, glance, quantum-server, cinder, nova-api), a database server(4 cores, 8GB RAM, installing mysql), a network node(4 cores, 8GB RAM, installing quantum agents), and 5 compute nodes(4x2 cores, 96GB RAM). Databases of all modules are installed on the database server.

When openstack has been running for some days, the latency of dashboard response becomes longer and longer. After checking the softwares, I found that the bottleneck was the database. The I found that, every "SELECT ... FROM token" would take more than 7 seconds. The "SELECT count(*) from token;" returns more than 170,000 records. I think this is the key point of the performance problem.

I tried to delete the expired tokens and the latency shortened. But this is not the solution. So is this a bug or not? I think more than 1 million tokens is very normal in the practical environment, but the performance is unbearable.

What should I do to speed it up?

2013-07-09 15:44:29 -0500 问了问题 How to Create or Modify Availability Zone Programmably

I have known that to set an Availability Zone, I should set the node_availability_zone field in nova.conf. But I have two questions about the Availability Zone.

  1. How to create or modify Availability Zone by api? The nova command line tool only support availability-zone-list command, lacking creating and modifying command. If this is by design, why?

  2. When a host firstly register to controller node as nova zone, modifying the nova.conf to set node_availability_zone to "test_zone" cannot change metadata. The zone is still named as nova in "nova availability-zone-list" and the compute node still belong to nova zone in "nova-manage service list". Is there a way to change a host to another availability zone?

Thanks for your reading and sorry for my poor English.