- Openstack-zh - lists.openstack.org

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

09 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 叶勇 31 Jul '17

31 Jul '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 30 Jul '17

30 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 18 May '17

18 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 朱高校 17 Jan '17

17 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