- Openstack-zh - lists.openstack.org

OpenStack compatible list
by steven.wang＠gigacomputing.com 11 Dec '23

11 Dec '23

Hi, 請問大家, 要如何得知自己所使用的系統主機, 能相容於Open Stack的某個版本? 例如, 我的系統已經可以安裝RHEL 9.0也已通過RHEL hardware vertification, 是否可以說Wallaby, h Xena, Yoga, Zed, Antelope 等都可支援? 有參考的依據嗎? 謝謝. For OpenStack compatible check, how should we know the connection with base OS? Example; If the machine support RHEL9 and OpenStack Wallaby, can we say it is compatible to the newest OpenStack than Wallaby? So it should be no problem with Xena, Yoga, Zed, Antelope and Bobcat? Or please kindly let me know where can find the similar document? Thanks. Steven

1 0

“help”
by 许伟祥 15 Nov '23

15 Nov '23

carry out iaas-pre-host.sh report an error Downloading packages: warning: /var/cache/yum/x86_64/7/iaas/packages/python-fixtures-3.0.0-2.el7.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID 764429e6: NOKEY Public key for python-fixtures-3.0.0-2.el7.noarch.rpm is not installed Please Reboot or Reconnect the terminal How to fix it 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 0

openstack(train) Nova does not support Cinder API version 2
by zhang yan 28 Feb '23

28 Feb '23

大家好我参照文档--the Minimal deployment for Train( https://docs.openstack.org/install-guide/openstack-services.html) 搭建了一个学习环境。当我完成Block Storage service 安装后，成功创建了一个卷，然后将改卷关联至测试实例。计算节点的nova-compute 日志提示： 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server [req-24fde26d-3665-492c-8ce6-067bd793b864 bf6dc19622da48e59a272fc3daa292e5 b99ceef1d97c4aac89d15c732a5e1b0a - default default] Exception during message handling: UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server Traceback (most recent call last): 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/server.py", line 165, in _process_incoming 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = self.dispatcher.dispatch(message) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 274, in dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._do_dispatch(endpoint, method, ctxt, args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/dispatcher.py", line 194, in _do_dispatch 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server result = func(ctxt, **new_args) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 79, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server function_name, call_dict, binary, tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/exception_wrapper.py", line 69, in wrapped 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(self, context, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/utils.py", line 1372, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 219, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server kwargs['instance'], e, sys.exc_info()) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 207, in decorated_function 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return function(self, context, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6126, in attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server do_attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_concurrency/lockutils.py", line 328, in inner 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return f(*args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6124, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server bdm.destroy() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 220, in __exit__ 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server self.force_reraise() 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/oslo_utils/excutils.py", line 196, in force_reraise 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.type_, self.value, self.tb) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6121, in do_attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return self._attach_volume(context, instance, driver_bdm) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 6156, in _attach_volume 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, bdm['attachment_id']) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 399, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 450, in wrapper 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server res = method(self, ctx, attachment_id, *args, **kwargs) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 68, in wrapped_f 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return Retrying(*dargs, **dkw).call(f, *args, **kw) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 223, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server return attempt.get(self._wrap_exception) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 261, in get 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server six.reraise(self.value[0], self.value[1], self.value[2]) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/retrying.py", line 217, in call 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server attempt = Attempt(fn(*args, **kwargs), attempt_number, False) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 892, in attachment_delete 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server context, '3.44', skip_version_check=True).attachments.delete( 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server File "/usr/lib/python2.7/site-packages/nova/volume/cinder.py", line 260, in cinderclient 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server raise exception.UnsupportedCinderAPIVersion(version=version) 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server UnsupportedCinderAPIVersion: Nova does not support Cinder API version 2 2023-02-28 14:34:13.322 6913 ERROR oslo_messaging.rpc.server 这个错误要如何处理呢？我的测试环境的操作系统为Centos7.7 。

1 0

openstack windows虚拟机格式化卷（>40G）死循环
by 胡建斌 13 Jan '22

13 Jan '22

各位好！我是openstack新手，最近用 kolla-ansible 安装了一个openstack实验环境xena版本。但当我在windows虚拟机上 attach 创建的块存储设备做为D盘的时候，如果卷<10G，可以格式化。但当卷>40G，在windows的磁盘管理中格式化就死循环！！！不知如何配置，请教各位大神！！谢谢！！thanks!

1 0

OpenStack Third-Party CI ― puppet-openstackci 0.0.1.dev179 documentation
by 彭松宏杉科技 25 Apr '21

25 Apr '21

Hi，Everyone，my company's old Third-Party CI is destroy. But when we install a new one accoding to this page : https://docs.openstack.org/infra/openstackci/third_party_ci.html . and meet some trouble. some dependency can't download . So please tell me How about your environment is installed and give me some advices . Thanks a lot. pengsong 杭州宏杉科技股份有限公司深圳研发部邮箱：pengsong(a)macrosan-email.com 地址：深圳市南山区科技园科发路2号朗峰大厦4楼网址：http://www.macrosan.com ―――――――――――――――――――――――――――― 本邮件及其附件含有杭州宏杉科技股份有限公司的保密或特有信息，仅限于发送给发件人指定的个人或群组。禁止任何其他人以任何形式传播或使用（包括但不限于全部或部分地泄露、复制、或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并将原始邮件、附件及其所有复本从系统中删除！ The information (including any attachments) transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. sed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer.

1 0

[help] [cinder] How to correlate my openstack fundation accout with my ubuntuone account
by 蔡启龙 15 Sep '20

15 Sep '20

3 2

openstack CN domain and keyword
by Thomas Liu<thomas＠chinaregistry.org.cn> 04 Dec '17

04 Dec '17

(It's very urgent, please transfer this email to your CEO. Thanks) This is a formal email. We are the Domain Registration Service company in China. Here I have something to confirm with you. On Dec 4, 2017, we received an application from Jiahong Ltd requested "openstack" as their internet keyword and China (CN) domain names (openstack.cn, openstack.com.cn, openstack.net.cn, openstack.org.cn). But after checking it, we find this name conflict with your company name or trademark. In order to deal with this matter better, it's necessary to send email to you and confirm whether this company is your business partner in China? Best Regards, Thomas Liu | Service & Operations Manager China Registry (Head Office) | 6012, Xingdi Building, No. 1698 Yishan Road, Shanghai 201103, China Tel: +86-02164193517 | Fax: +86-02161918697 | Mob: +86-13816428671 Email: thomas(a)chinaregistry.org.cn Web: www.chinaregistry.org.cn This email contains privileged and confidential information intended for the addressee only. If you are not the intended recipient, please destroy this email and inform the sender immediately. We appreciate you respecting the confidentiality of this information by not disclosing or using the information in this email.

1 0

ovs-vswitchd.log netlink_socket- Too many open files
by 全新全译 17 Oct '17

17 Oct '17

1 0

关于让user 加入project的API
by xiangsun4＠iflytek.com 30 Sep '17

30 Sep '17

您好：我最近在做Keystone的相关调研，有一个地方不太明白，想请教您。我想要让一个user 加入到 project中，但是在官网没有找到相关API，是我对这两个名称理解有误吗？后来，我找到这个API :Assign role to user on project. 这个API有将user加入到project的作用吗？我尝试使用了上面这个API ,并使用下面这个API:List projects for user 去检查是否把用户加入了Project。过程中使用的TOKEN 是这么获取的： curl -i -X POST\ -H "Content-Type: application/json" \ -d ' { "auth": { "identity": { "methods": ["password"], "password": { "user": { "name": "admin", "domain": { "id": "default" }, "password": "0407" } } }, "scope": { "project": { "domain": { "name": "Default" }, "name": "admin" } } } }' \ "http://localhost:5000/v3/auth/tokens" ; 这个是用户： { "user": { "name": "xiangsun4", "links": { "self": "http://localhost:5000/v3/users/95df8c5d80ff4f43bd239500048973b3" }, "domain_id": "default", "enabled": true, "options": {}, "default_project_id": "a44c2e1e6eb247e086e62d81a0573c7b", "id": "95df8c5d80ff4f43bd239500048973b3", "password_expires_at": null } } 这个是project： { "project": { "is_domain": false, "description": "My first project", "links": { "self": "http://localhost:5000/v3/projects/dae552c5d08f4657a2af34bcb39bafd3" }, "enabled": true, "id": "dae552c5d08f4657a2af34bcb39bafd3", "parent_id": "default", "domain_id": "default", "name": "project4" } } **这个是role，role中定义了domain_id { "role": { "domain_id": "default", "id": "aa07402e8bc041e89db3fc4c0fbe98a0", "links": { "self": "http://localhost:5000/v3/roles/aa07402e8bc041e89db3fc4c0fbe98a0" }, "name": "noDomainRole2" } } 然后我调用了下面的 API尝试把三者捆绑。 curl -i -X PUT \ -H "X-Auth-Token: $OS_TOKEN" \ "http://localhost:5000/v3/projects/dae552c5d08f4657a2af34bcb39bafd3/users/95…" 接着我调用了下面的API，查看这个user是否有project： curl -i -X GET -H "X-Auth-Token: $OS_TOKEN" "http://localhost:5000/v3/users/95df8c5d80ff4f43bd239500048973b3/projects" 返回的结果是： {"links": {"self": "http://localhost:5000/v3/users/95df8c5d80ff4f43bd239500048973b3/projects", "previous": null, "next": null}, "projects": []} 由返回看出projects 是空数组。但我使用了另外一个role，这个role和上面role的区别就在于没有domain_id： { "role": { "domain_id": null, "id": "1cf7d2e43c814dc8bd7d66e380f6b339", "links": { "self": "http://localhost:5000/v3/roles/1cf7d2e43c814dc8bd7d66e380f6b339" }, "name": "noDomainRole1" } } 然后再捆绑同一个project-user，再用同样的方式检查，他的project数组是有值的这个是为什么呢？？我进一步测试我修改了第一个role数据库中的domain_id，由default修改成了<<null>>,再调用相同的方式检查，他返回的project数组有值，我再由<<null>>修改成了default，返回的project数组又是空的。这又是为什么呢？捆绑三者的域都是default,为什么会和default_id有关呢？麻烦您了，请您帮我解答一下，万分感谢！！！孙翔

1 0

關於taskflow的remote worker問題
by lampahome 18 Sep '17

18 Sep '17

現在再研究taskflow是否能夠用於結合遠端的程序能夠結合的話便可以跨伺服器變成管線的運作但是都找不到有類似的教學多半都只有local的像是: https://wiki.openstack.org/wiki/TaskFlow/Worker-based_Engine 並沒有client-server這樣配合的教學請問有更詳細的remote worker相關資料嗎

1 0

A Questionnaire about the Impact of Company's Domination on FLOSS Community
by YuxiaZ 10 Aug '17

10 Aug '17

Dear OpenStacker,  I am a researcher from Peking University. My colleague (Minghui Zhou, Zhi Jin, Xin Tan) and I are investigating the impacts that company’s domination may have on OSS community. The domination indicates the extent of contribution from the company which contributed the largest fraction of commits or manpower among all companies. Since so many companies step in open source today, we expect this could help people better understand the practices and build better ecosystems. We understood you have contributed a lot to OpenStack ecosystems. So we think your experiences will greatly help this study and we truly hope you will be kindly enough to reply this questionnaire. The questionnaire is opening on this website and links are as follows：https://sojump.com/jq/15822929.aspx. In order to avoid the website can not be opened, we have all the questions in this mail as following. Please note all the answers will be kept anonymous and only for research purpose. We define two metrics to characterize the company’s domination in an OSS project. One emphasizes on the degree of the dominating company's contribution, the value is obtained by dividing the company's commits (or manpower) by all commits (or manpower) contributed in the project per version. The other measures the balance of the intensity of all companies’ contribution (‘Shannon entropy’). The metrics we defined cover two aspects that directly influence the software development process: code and manpower. With this set of metrics, we investigated the history of four core projects of OpenStack, Nova, Swift, Neutron and Glance and obtained some rules. 1. What kind of contributor are you? (Single Choice) A. Volunteer B. Hired by company 2. We found a correlation between the extent of contribution from the most invested company (which contributed the largest fraction of commits or manpower among all companies) and the company turnover (joining and leaving of companies). For example, when the commits or manpower, contributed by the most invested company, is increasing, the number of companies who stayed in this project will decrease. i. Does it match your perception of what happened in OpenStack? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely ii. Does it match your perception of what you observed in FLOSS projects in general? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely iii. Do you think what might have caused that? iv. As a contributor, what are the factors that might prompt you to leave an open source project? (Multiple Choice) A. My company’s decision or business needs B. Lack of leisure time C. Have no interests any more D. ______ (other) v. As a contributor, what are the factors that might prompt you to continue to stay on an open source project? (Multiple Choice) A. My company’s decision B. Project’s high popularity C. Have great interests D. ______ (other) 3. We found a positive correlation between the extent of contribution from the most invested company (which contributed the largest fraction of commits or manpower among all companies) and contributors’ average efficiency. For example, when the commits or manpower, contributed by the most invested company, is increasing, the average number of contributors’ commits per version will increase. i. Does it match your perception of what happened in OpenStack? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely ii. Does it match your perception of what you observed in FLOSS projects in general? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely iii. Do you think which factors below might cause the increasing of contributors’ average efficiency? (Multiple Choice) A. Dominated company may provide a team for review B. Have common milestone leading by dominated company C. Personal experience and skills D. ______ (other) iv. Do you think which factors below might cause the decreasing of contributors’ average efficiency? A. Code used to implement different features may lead to conflicts B. Communication problems C. Personal experience and skills D. ______ (other) 4. We found a positive correlation between the extent of contribution from the most invested company (which contributed the largest fraction of commits or manpower among all companies) and the quality of issue reports. i. Does it match your perception of what happened in OpenStack? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely ii. Does it match your perception of what you observed in FLOSS projects in general? (Single Choice) A. highly unlikely B. unlikely C. hard to tell D. likely E. very likely iii. Do you think what might have caused that? iv. When you participate in a new project, which kind of tasks would you prefer to do firstly? (Multiple Choice) A. Report issues B. Fix bugs C. Write documentations D. Implement features E. ______ (other) 5. Do you have any comments about how things go due to company’s domination in OSS projects? Thanks a lot if you could offer any insights! Sorry if this bothers you. Yuxia Zhang, Xin Tan, Minghui Zhou, and Zhi Jin Key Laboratory of High Con dence Software Technologies, Peking University, Beijing, China 100871

1 0

kolla-ansible deploy 出现镜像找不到的情况
by 叶勇 01 Aug '17

01 Aug '17

kolla-ansible deploy 部署（allinone方式），出现centos-binary-fluentd:4.0.2 not found，我进入本地参数，找到centos-binary-fluentd，在tag里发现只有4.0.3和5.0.0，然后修改/etc/kolla/global.yml文件openstack_realease,分别为4.0.3和5.0.0后，还是出现centos-binary-fluentd:4.0.3和centos-binary-fluentd:5.0.0not found // 错误信息 for localhost TASK [common : Starting fluentd container] ************************************************************************************************************************************************************* fatal: [localhost]: FAILED! => {"changed": true, "failed": true, "msg": "'Traceback (most recent call last):\\n File \"/tmp/ansible_0gYptk/ansible_module_kolla_docker.py\", line 781, in main\\n result = bool(getattr(dw, module.params.get(\\'action\\'))())\\n File \"/tmp/ansible_0gYptk/ansible_module_kolla_docker.py\", line 595, in start_container\\n self.pull_image()\\n File \"/tmp/ansible_0gYptk/ansible_module_kolla_docker.py\", line 445, in pull_image\\n repository=image, tag=tag, stream=True\\n File \"/usr/lib/python2.7/site-packages/docker/api/image.py\", line 180, in pull\\n self._raise_for_status(response)\\n File \"/usr/lib/python2.7/site-packages/docker/client.py\", line 173, in _raise_for_status\\n raise errors.NotFound(e, response, explanation=explanation)\\nNotFound: 404 Client Error: Not Found (\"{\"message\":\"manifest for 192.168.1.104:4000/lokolla/centos-binary-fluentd:4.0.3 not found\"}\")\\n'"} to retry, use: --limit @/usr/share/kolla-ansible/ansible/site.retry PLAY RECAP ********************************************************************************************************************************************************************************************* localhost : ok=21 changed=0 unreachable=0 failed=1 Command failed ansible-playbook -i /usr/share/kolla-ansible/ansible/inventory/all-in-one -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=deploy /usr/share/kolla-ansible/ansible/site.yml Deploying Playbooks : ansible-playbook -i /usr/share/kolla-ansible/ansible/inventory/all-in-one -e @/etc/kolla/globals.yml -e @/etc/kolla/passwords.yml -e CONFIG_DIR=/etc/kolla -e action=deploy /usr/share/kolla-ansible/ansible/site.yml

2 1

ironic hypervisor_type QEMU
by mingxingma 31 Jul '17

31 Jul '17

Hi everyone 我在ubuntu14.04上部署mitaka openstack （一个controller，一个compute）在compute节点上安装ironic，按照官方文档安装完成之后，运行nova hypervisor-list 只有计算节点显示出来运行nova hypervisor-show 1 显示的结果hypervisor_type 是QEMU，正常结果不应该是ironic吗？有没有人碰到过相似的问题？谢谢解答！ -- Best Regards, Mingxing Ma (马明星)

1 0

请教关于cinder driver首次提交社区的问题
by 沈敏江 07 Jul '17

07 Jul '17

Hi All, 1. 我用temptest测试自己的driver代码，tox -e all -- volume | tee -a console.log.out，结果中有七八个失败的，因为失败的都是可选的功能，我们目前还不能实现，但是如果用CI环境测试的话，只要有一个失败，最后的结果就是测试失败，那么怎么才能让测试通过呢？ 2. 说明文档里说提交代码的时候要提供测试结果，我用git review提交的话，怎么附上测试结果呢？谢谢！

1 0

Excuse me, I need some help about nova-compute or amqp, tks!
by 杨可 04 Jul '17

04 Jul '17

在centos7环境下，按照官方文档搭建了好几次，发现依旧无法创建实例，报错如下： 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager [req-9dc58b73-719d-44ee-998f-32b7ec57dd95 ef162c8bdf8846ed9b441d4bb9acf5fd f0b31ad6a39d4b2995ad392cd08c54c3 - - -] Instance failed network setup after 1 attempt(s) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager Traceback (most recent call last): 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1570, in _allocate_network_async 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager bind_host_id=bind_host_id) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 49, in wrapped 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager return func(self, context, *args, **kwargs) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/base_api.py", line 77, in wrapper 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager res = f(self, context, *args, **kwargs) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 283, in allocate_for_instance 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager nw_info = self.network_rpcapi.allocate_for_instance(context, **args) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 163, in allocate_for_instance 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager macs=jsonutils.to_primitive(macs)) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 158, in call 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager retry=self.retry) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 90, in _send 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager timeout=timeout, retry=retry) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 470, in send 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager retry=retry) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 459, in _send 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager result = self._waiter.wait(msg_id, timeout) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 342, in wait 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager message = self.waiters.get(msg_id, timeout=timeout) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 244, in get 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager 'to message ID %s' % msg_id) 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager MessagingTimeout: Timed out waiting for a reply to message ID f9cc10b8b0364ec0994f82448df0202a 2017-07-04 15:14:01.663 20239 ERROR nova.compute.manager 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [req-9dc58b73-719d-44ee-998f-32b7ec57dd95 ef162c8bdf8846ed9b441d4bb9acf5fd f0b31ad6a39d4b2995ad392cd08c54c3 - - -] [instance: 876d5671-cb35-4d48-9b47-53645953c00f] Instance failed to spawn 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] Traceback (most recent call last): 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2218, in _build_resources 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] yield resources 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 2064, in _build_and_run_instance 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] block_device_info=block_device_info) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 2776, in spawn 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] write_to_disk=True) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/virt/libvirt/driver.py", line 4715, in _get_guest_xml 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] network_info_str = str(network_info) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/model.py", line 521, in __str__ 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return self._sync_wrapper(fn, *args, **kwargs) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/model.py", line 504, in _sync_wrapper 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] self.wait() 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/model.py", line 536, in wait 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] self[:] = self._gt.wait() 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 175, in wait 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return self._exit_event.wait() 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/eventlet/event.py", line 121, in wait 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return hubs.get_hub().switch() 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/eventlet/hubs/hub.py", line 294, in switch 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return self.greenlet.switch() 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/eventlet/greenthread.py", line 214, in main 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] result = function(*args, **kwargs) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/utils.py", line 1159, in context_wrapper 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return func(*args, **kwargs) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1587, in _allocate_network_async 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] six.reraise(*exc_info) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/compute/manager.py", line 1570, in _allocate_network_async 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] bind_host_id=bind_host_id) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 49, in wrapped 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] return func(self, context, *args, **kwargs) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/base_api.py", line 77, in wrapper 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] res = f(self, context, *args, **kwargs) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/api.py", line 283, in allocate_for_instance 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] nw_info = self.network_rpcapi.allocate_for_instance(context, **args) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/nova/network/rpcapi.py", line 163, in allocate_for_instance 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] macs=jsonutils.to_primitive(macs)) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/rpc/client.py", line 158, in call 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] retry=self.retry) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/transport.py", line 90, in _send 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] timeout=timeout, retry=retry) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 470, in send 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] retry=retry) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 459, in _send 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] result = self._waiter.wait(msg_id, timeout) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 342, in wait 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] message = self.waiters.get(msg_id, timeout=timeout) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] File "/usr/lib/python2.7/site-packages/oslo_messaging/_drivers/amqpdriver.py", line 244, in get 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] 'to message ID %s' % msg_id) 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] MessagingTimeout: Timed out waiting for a reply to message ID f9cc10b8b0364ec0994f82448df0202a 2017-07-04 15:14:01.666 20239 ERROR nova.compute.manager [instance: 876d5671-cb35-4d48-9b47-53645953c00f] 有解决过同样问题的朋友吗？可否告知一下问题所在？本人初步猜测是rabbit和neutron之间哪里少个配置什么的？感觉neutron到rabbit的队列得不到返回值。

2 1

Re: [Openstack-zh] Openstack-zh Digest, Vol 20, Issue 1
by JGX020 19 May '17

19 May '17

i use openstack ocata ---Original--- From: "openstack-zh-request"<openstack-zh-request(a)lists.openstack.org> Date: 2017/5/19 20:06:19 To: "openstack-zh"<openstack-zh(a)lists.openstack.org>; Subject: Openstack-zh Digest, Vol 20, Issue 1 Send Openstack-zh mailing list submissions to openstack-zh(a)lists.openstack.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-zh or, via email, send a message with subject or body 'help' to openstack-zh-request(a)lists.openstack.org You can reach the person managing the list at openstack-zh-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Openstack-zh digest..." Today's Topics: 1. Can Juno work well with RHEL 6.9 or 7.3? (Tang, Shibin) 2. Re: Can Juno work well with RHEL 6.9 or 7.3? (George Zhao) ---------------------------------------------------------------------- Message: 1 Date: Fri, 19 May 2017 02:53:00 +0000 From: "Tang, Shibin" <tangsb(a)cn.fujitsu.com> To: "openstack-zh(a)lists.openstack.org" <openstack-zh(a)lists.openstack.org> Subject: [Openstack-zh] Can Juno work well with RHEL 6.9 or 7.3? Message-ID: <0415A184A9F81647B6F1544A6701AB70A69FBE8E(a)G08CNEXMBPEKD03.g08.fujitsu.local> Content-Type: text/plain; charset="gb2312" Hi all, Customer built up their Cloud platform over Juno before, due to x86 server technologies upgrade were too frequent, now planned to add more new generation x86 servers which only support RHEL 6.9 or 7.3 to the cloud environment, here're two questions: 1. Can Juno work well with RHEL 6.9 or 7.3? if not, which openstack version at least needs to be upgraded? 2. Can Juno work well with multiple Linux versions, such as, RHEL 6.3, 6.9 and 7.3? Thanks and regards, Tang Shibin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-zh/attachments/20170519/e7d8…> ------------------------------ Message: 2 Date: Fri, 19 May 2017 17:22:34 +1200 From: George Zhao <george(a)hd.net.nz> To: openstack-zh(a)lists.openstack.org Subject: Re: [Openstack-zh] Can Juno work well with RHEL 6.9 or 7.3? Message-ID: <403875c4-f40b-b9e0-e9f8-c95e72ded2c8(a)hd.net.nz> Content-Type: text/plain; charset=gbk; format=flowed Why not using docker? On 05/19/2017 02:53 PM, Tang, Shibin wrote: > Hi all, > > Customer built up their Cloud platform over Juno before, due to x86 > server technologies upgrade were too frequent, now planned to add more > new generation x86 servers which only support RHEL 6.9 or 7.3 to the > cloud environment, here're two questions: > > 1. Can Juno work well with RHEL 6.9 or 7.3? if not, which openstack > version at least needs to be upgraded? > > 2. Can Juno work well with multiple Linux versions, such as, RHEL 6.3, > 6.9 and 7.3? > > Thanks and regards, > > Tang Shibin > > > > _______________________________________________ > Openstack-zh mailing list > Openstack-zh(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-zh > ------------------------------ Subject: Digest Footer _______________________________________________ Openstack-zh mailing list Openstack-zh(a)lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-zh ------------------------------ End of Openstack-zh Digest, Vol 20, Issue 1 *******************************************

1 0

Can Juno work well with RHEL 6.9 or 7.3?
by Tang, Shibin 19 May '17

19 May '17

Hi all, Customer built up their Cloud platform over Juno before, due to x86 server technologies upgrade were too frequent, now planned to add more new generation x86 servers which only support RHEL 6.9 or 7.3 to the cloud environment, here're two questions: 1. Can Juno work well with RHEL 6.9 or 7.3? if not, which openstack version at least needs to be upgraded? 2. Can Juno work well with multiple Linux versions, such as, RHEL 6.3, 6.9 and 7.3? Thanks and regards, Tang Shibin

2 1

Security group 681ca58f-2803-4de4-8266-e1e9e232b9c9 not found for project b2fd83925b0a433b82eaac7f40948b4c.
by xiaozumail 20 Feb '17

20 Feb '17

在dashboard上创建虚拟时时，出现 HTTP exception thrown: Security group 681ca58f-2803-4de4-8266-e1e9e232b9c9 not found for project b2fd83925b0a433b82eaac7f40948b4c. 虚拟机创建失败但是通过命令是可以查到安全组和项目信息的 [root@controller ~]# openstack security group list +--------------------------------------+---------+------------------------+----------------------------------+ | ID | Name | Description | Project | +--------------------------------------+---------+------------------------+----------------------------------+ | 681ca58f-2803-4de4-8266-e1e9e232b9c9 | default | Default security group | b2fd83925b0a433b82eaac7f40948b4c | +--------------------------------------+---------+------------------------+----------------------------------+ 通过命令行创建虚拟机，可以成功创建，没有报错信息服务器操作系统centos7，opentstack版本Mitaka，请大家帮忙解决，谢谢！

1 0

trove 的ironic支持
by 朱高校 18 Jan '17

18 Jan '17

大家好，有人在进行trove组件的研究吗？是否有人尝试过trove的ironic支持？

1 0

OpenStack+KVM架构，不同物理机下创建的windows虚拟机无法相互远程桌面和传输大文件
by 张博 05 Jan '17

05 Jan '17

大家好：我司部署的OpenStack+KVM架构的资源池出现了如下问题：（下面的操作都是在同一个网段下进行的。）在不同物理机下的计算节点创建windos虚拟机（2008和2012都试过）A和B。（1）A ping B成功，且A telnet B的 3389端口成功。但是A无法与B远程桌面，且远程桌面的时输入账号密码后报错。（2）A 能向 B传输几KB的文件，但是几M的文件或者更大则传输失败，且报错。但是相同物理机下面创建的windows虚拟机A、B，它们之间既能远程桌面也能传输大文件。且不论是在相同的物理机还是在不同的物理机下面创建centos虚拟机A、B，它们之间也能完成远程登录和大文件的传输。请问社区各位学者有无遇到过类似的问题，该如何解决呢？十分感谢！

3 2

Mirantis Fuel 9.0单控制节点的一个重要配置问题
by 陈亚峰 24 Dec '16

24 Dec '16

我们在使用Fuel 9.0部署M版OpenStack时，系统在正常运行数天后，总会出现控制节点失效，不得不重启整个环境的问题。使用brctl show 发现正常情况下的虚拟网桥接口全部消失不见了，如下： root@node-5:/var/log# brctl show bridge namebridge idSTP enabledinterfaces br-ex8000.9457a5565678noeno1.104 p_ff798dba-0 br-fw-admin8000.9457a5565678noeno1 p_eeee51a2-0 br-mgmt8000.3215d3e4d700noeno1.101 mgmt-conntrd br-storage8000.9457a5565678noeno1.102 经过查看neturon、upstart、nova、rabbitmq等组件的日志，均未解决问题，最终在pacemaker日志中发现如下错误： ec 08 03:20:50 [7126] node-5.domain.tld lrmd: notice: operation_finished:p_rabbitmq-server_notify_0:79939:stderr [ Error: rabbit application is not running on node rabbit@messaging-node-5. ] Dec 08 03:20:50 [7126] node-5.domain.tld lrmd: notice: operation_finished:p_rabbitmq-server_notify_0:79939:stderr [ * Suggestion: start it with "rabbitmqctl start_app" and try again ] Dec 08 03:20:50 [7126] node-5.domain.tld lrmd: info: log_finished:finished - rsc:p_rabbitmq-server action:notify call_id:200 pid:79939 exit-code:0 exec-time:3738ms queue-time:0ms Dec 08 03:20:50 [7129] node-5.domain.tld crmd: info: match_graph_event:Action p_rabbitmq-server_notify_0 (116) confirmed on node-5.domain.tld (rc=0) Dec 08 03:20:50 [7129] node-5.domain.tld crmd: notice: process_lrm_event:Operation p_rabbitmq-server_notify_0: ok (node=node-5.domain.tld, call=200, rc=0, cib-update=0, confirmed=true) Dec 08 03:20:50 [7129] node-5.domain.tld crmd: notice: run_graph:Transition 53849 (Complete=18, Pending=0, Fired=0, Skipped=1, Incomplete=8, Source=/var/lib/pacemaker/pengine/pe-input-2696.bz2): Stopped Dec 08 03:20:50 [7129] node-5.domain.tld crmd: info: do_state_transition:State transition S_TRANSITION_ENGINE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL origin=notify_crmd ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: notice: unpack_config:On loss of CCM Quorum: Ignore Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: determine_online_status:Node node-5.domain.tld is online Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: determine_op_status:Operation monitor found resource p_vrouter:0 active on node-5.domain.tld Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: apply_system_health:Applying automated node health strategy: migrate-on-red Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: apply_system_health: Node node-5.domain.tld has an combined system health of -1000000 Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_vrouter [p_vrouter] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:vip__management(ocf::fuel:ns_IPaddr2):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:vip__vrouter_pub(ocf::fuel:ns_IPaddr2):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:vip__vrouter(ocf::fuel:ns_IPaddr2):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:vip__public(ocf::fuel:ns_IPaddr2):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_haproxy [p_haproxy] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_mysqld [p_mysqld] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Master/Slave Set: master_p_rabbitmq-server [p_rabbitmq-server] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Slaves: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:p_aodh-evaluator(ocf::fuel:aodh-evaluator):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:p_ceilometer-agent-central(ocf::fuel:ceilometer-agent-central):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_neutron-openvswitch-agent [neutron-openvswitch-agent] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_neutron-l3-agent [neutron-l3-agent] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_neutron-metadata-agent [neutron-metadata-agent] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_heat-engine [p_heat-engine] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_neutron-dhcp-agent [neutron-dhcp-agent] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_print:sysinfo_node-5.domain.tld(ocf::pacemaker:SysInfo):Stopped Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_dns [p_dns] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Master/Slave Set: master_p_conntrackd [p_conntrackd] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_p_ntp [p_ntp] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: clone_print: Clone Set: clone_ping_vip__public [ping_vip__public] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: short_print: Stopped: [ node-5.domain.tld ] Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:clone_p_vrouter: Rolling back scores from clone_p_dns Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:clone_p_vrouter: Rolling back scores from clone_p_ntp Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_vrouter:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:clone_p_haproxy: Rolling back scores from vip__management Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:clone_p_haproxy: Rolling back scores from vip__public Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_haproxy:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource vip__management cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:vip__vrouter_pub: Rolling back scores from master_p_conntrackd Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: rsc_merge_weights:vip__vrouter_pub: Rolling back scores from vip__vrouter Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource vip__vrouter_pub cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource vip__vrouter cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource vip__public cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_mysqld:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_rabbitmq-server:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: master_color:master_p_rabbitmq-server: Promoted 0 instances of a possible 1 to master Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_aodh-evaluator cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_ceilometer-agent-central cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource neutron-openvswitch-agent:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource neutron-l3-agent:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource neutron-metadata-agent:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource p_heat-engine:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource neutron-dhcp-agent:0 cannot run anywhere Dec 08 03:20:50 [7128] node-5.domain.tld pengine: info: native_color:Resource sysinfo_node-5.domain.tld cannot run anywhere 可以看出pacemaker某些情况下认为节点健康度为负无穷，认为节点不可用，所有的资源无法找到可运行的节点，就停止掉了。关键信息是： Applying automated node health strategy: migrate-on-red 证明可能与节点健康策略有关，通过google搜索pacemaker migrate-on-red，发现配置成该选项后操作系统等出现的问题会被设置为负无穷，导致节点不可用，但实际情况是服务器仍可用，可能是硬件健康检查有一些告警，单节点情况下无节点切换，就整个当机了。修正错误方法： 1、登入控制节点 2、输入crm 进入 pacemaker控制台 3、输入configure进入配置界面 4、输入edit编辑，将property中的node health strategy设为none，如下： property cib-bootstrap-options: \ have-watchdog=false \ dc-version=1.1.14-70404b0 \ cluster-infrastructure=corosync \ cluster-recheck-interval=190s \ no-quorum-policy=ignore \ stonith-enabled=false \ start-failure-is-fatal=false \ symmetric-cluster=false \ last-lrm-refresh=1477747972 \ node-health-strategy=none

1 0

华云数据: OpenStack职位推荐
by 黎绍秀 18 Nov '16

18 Nov '16

您好！上海华云数据目前正在寻找OpenStack方向的人才，职位包含研发总监、技术专家、开发工程师以及测试工程师等，职位参考JD如下。地址：上海市杨浦区伟成路70号瑞力创新中心1号楼9楼不知您是否有兴趣考虑呢？谢谢！ Openstack开发工程师岗位职责 1)参与公司基于OpenStack云平台产品的系统研究； 2)参与OpenStack及其管理平台的产品研发工作； 3)根据开发计划，负责公司基于OpenStack的Iaas云平台功能模块的详细设计、开发和单元测试工作； 4)解决部署实施过程遇到的技术问题。任职要求 1)熟悉OpenStack，CloudStack等虚拟化开源项目实现原理和系统架构，并对其中核心实现有一定深入研究，并以软件研发身份参与过虚拟化、云计算等项目，或OpenStack 核心项目的二次开发项目； 2)熟悉Python语言及Django、Eventlet等常用库； 3)知晓OpenStack核心功能组件的底层实现机制，及其在不同场景下的架构设计与主要配置； 4)2年以上Linux系统开发经验； 5)熟悉KVM、Xen等虚拟机技术； 6)英语阅读能力强，能独立查阅网络技术资料、社区文档，或与国内外贡献者沟通以解决开发、部署过程中遇到的问题； 7)有较好的团队合作意识，能熟练使用Git管理代码。加分点：有其它语言（Ruby、Go等）实际开发经验参与开源项目，或在OpenStack社区比较活跃有OpenStack CI/CD或自动化部署经验容器方面经验华云数据集团 www.chinac.com <http://www.chinac.com/> 华云数据集团，中国领先的云计算专家，目前在中国北京、上海、厦门、深圳、广州拥有分公司，在香港、纽约等地拥有运营中心。旗下拥有润迅通信、蓝芒、飞讯、爱办公等多个互联网服务品牌。华云数据以多样化的云化产品组合和领先的云化支撑运营能力，立志于成为亚洲最大的云计算独立服务提供商和平台合作伙伴的最佳选择。华云数据集团团队核心成员来自于惠普、微软、IBM、EMC、Ucloud、思科、华为、世纪互联、蓝芒等公司，加盟之前专注于网格计算、虚拟化、云计算相关的研究。华云数据是国内领先的综合性云计算服务提供商，以全线覆盖的云服务产品组合、领先的云化支撑运营能力和创新的云CDN等优秀技术致力于成为中国最大的独立云计算服务提供商和一站式云化合作平台。华云数据在国内拥有超过15个城市20个数据中心上万台物理服务器集群，网络覆盖中国电信、中国联通以及华云数据自有BGP网络，实现了从边缘到核心网络的全覆盖。华云数据不仅为用户提供IAAS、PAAS、云协同SAAS、云CDN等多类型服务，同时还提供私有云、电子商务云、金融云、游戏云、IDC转云等安全、方便、易用、节能、可靠、高效的解决方案。中国云应用平台依托华云数据强大的云计算基础设施，采用一站式运营模式，通过中国首创的云计算全程信息化服务及管理平台系统，提供销售结算、管理支持和安全合规等功能，为中国软件应用的SaaS云化提供了突破性的道路。传统软件应用可以借助封装部署、云化迁移等特有的领先技术，来实现快速上网云化。真正实现了广大企业用户、软件开发者和平台的三方共赢。华云数据建立开放共赢的云计算生态圈的理念，由此得到了投资界的高度认同。继2012 年底A轮获涌金集团投资之后，2014年2月又获由SIG领投，Intel投资跟投的总额为五千万美金的B轮融资。2015年5月再获由海通领投的壹亿美金C轮融资，并成立总规模10亿元人民币的华云数据云生态投资基金。客户群和合作伙伴卡酷、4399游戏、盛大游戏、艾瑞咨询集团、投中集团、易名中国、导航犬等国内主流网站和应用均放置在华云平台之上。客户群包括上海市税务局、无锡地铁、京东、领英、美图、畅游、链家网、龙图游戏、寺库、酷我音乐等，同时与各地政府就私有云、公有云以及混合云也已展开合作，业务成几何增长。华云和很多平台级运营者构建了合作伙伴关系，包括中国电信集团、中国银联、一些地方政府和地方运营商、中国数据、新网互联等等。通过资源共享和开放共赢的方式，初步形成了围绕华云的中国云化产业生态圈。华云PaaS平台项目在启动后短短的3个月时间，已经有包括微软、Oracle、金蝶、用友、等60多家，14个大类48个小类三百多个软件产品入驻。

1 0

(no subject)
by 任开朗 10 Nov '16

10 Nov '16

test

1 0

[opendtack-zh][diskimage-builder]
by 刘芮青 05 Oct '16

05 Oct '16

背景：我用fuel9.0部署了openstack，并且安装了最新的trove，能正常使用。但使用官方的diskimage-builder创建ubuntu-mysql镜像的时候总是会报错，显示如下： dib-run-parts Tue Oct 4 12:57:08 UTC 2016 99-tidy-logs completed dib-run-parts Tue Oct 4 12:57:08 UTC 2016 ----------------------- PROFILING ----------------------- dib-run-parts Tue Oct 4 12:57:08 UTC 2016 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 Target: cleanup.d dib-run-parts Tue Oct 4 12:57:08 UTC 2016 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 Script Seconds dib-run-parts Tue Oct 4 12:57:08 UTC 2016 --------------------------------------- ---------- dib-run-parts Tue Oct 4 12:57:08 UTC 2016 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 01-ccache 0.016 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 01-copy-manifests-dir 0.084 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 40-unblock-daemons 0.030 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 50-remove-img-build-proxy 0.011 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 51-bootloader 0.033 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 60-untrim-dpkg 0.075 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 99-tidy-logs 0.235 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 dib-run-parts Tue Oct 4 12:57:08 UTC 2016 --------------------- END PROFILING --------------------- rm: cannot remove '/tmp/dib_build.tBIihUi4': Device or resource busy 而且，我在程序中断后，试图自己sudo rm -rf /sudo rmdir都没有用。

1 0

水电费水电费
by 崔行兵 26 Sep '16

26 Sep '16

的范德萨发的个 2016-09-26 崔行兵

1 0