- Openstack-zh - lists.openstack.org

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

10 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 胡建斌 12 Jan '22

12 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 29 Sep '17

29 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 17 Sep '17

17 Sep '17

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

1 0