- Openstack-zh - lists.openstack.org

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

Re: [Openstack-zh] Openstack-zh Digest, Vol 14, Issue 3
by JGX020 22 Sep '16

22 Sep '16

the ubuntu password you can Crack to solve the method is simple.you can google ------------------ Original ------------------ From: "openstack-zh-request";<openstack-zh-request(a)lists.openstack.org>; Date: Thu, Sep 22, 2016 08:00 PM To: "openstack-zh"<openstack-zh(a)lists.openstack.org>; Subject: Openstack-zh Digest, Vol 14, Issue 3 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. [opendtack-zh][trove] (???) ---------------------------------------------------------------------- Message: 1 Date: Mon, 19 Sep 2016 14:29:52 +0800 From: ??? <liurqbupt(a)163.com> To: openstack-zh(a)lists.openstack.org Subject: [Openstack-zh] [opendtack-zh][trove] Message-ID: <79c08cb5-9caf-1570-b42c-8ea2533dbe25(a)163.com> Content-Type: text/plain; charset=gbk; format=flowed The background: I used fuel to deploy the openstack and installed trove according to the book "OpenStack Trove 1484212223". Then I download ubuntu-mysql image on the offical website http://tarballs.openstack.org/trove/images/ubuntu (http://tarballs.openstack.org/trove/i...) . But i cannot ssh the instance because it has password and i cannot find it. ??fuel9.0???openstack??????trove???????http://tarballs.openstack.org/trove/images/ubuntu/mysql.qcow2?????????ssh???? The problem: Whoever knows the password for the ubuntu-mysql image,or whom should i ask? ?????????????????? ------------------------------ _______________________________________________ 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 14, Issue 3 *******************************************

1 0

[opendtack-zh][trove]
by 刘芮青 19 Sep '16

19 Sep '16

The background: I used fuel to deploy the openstack and installed trove according to the book "OpenStack Trove 1484212223". Then I download ubuntu-mysql image on the offical website http://tarballs.openstack.org/trove/images/ubuntu (http://tarballs.openstack.org/trove/i...) . But i cannot ssh the instance because it has password and i cannot find it. 我用fuel9.0部署了openstack，并且安装了trove。但是官方镜像http://tarballs.openstack.org/trove/… The problem: Whoever knows the password for the ubuntu-mysql image,or whom should i ask? 谁知道这个镜像的密码，或者我该问谁？

1 0

答复: 有没有对OpenStack的文档管理比较熟悉的朋友
by 王智愚 11 Sep '16

11 Sep '16

Thanks a lot ~ 发送自 Windows 10 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>应用发件人: haifeng.yan<mailto:yanheven@qq.com> 发送时间: 2016年9月11日 18:32 收件人: 王智愚<mailto:darren_wang@outlook.com>; openstack-zh(a)lists.openstack.or<mailto:openstack-zh@lists.openstack.org> 主题: Re: [Openstack-zh] 有没有对OpenStack的文档管理比较熟悉的朋友 http://docs.openstack.org/contributor-guide/index.html specially this section Using documentation tools ------------------ Best Regards, Haifeng Yan ------------------ Original ------------------ From: "王智愚";<darren_wang(a)outlook.com>; Date: Sun, Sep 11, 2016 03:58 PM To: "openstack-zh(a)lists.openstack.org"<openstack-zh(a)lists.openstack.org>; Subject: [Openstack-zh] 有没有对OpenStack的文档管理比较熟悉的朋友 RT，我们团队现在在考察一些文档管理上的技术和工具，请问有没有对OpenStack的文档管理比较熟悉的，比如怎么编辑，怎么从文档代码生成网页等等，大家团队的文档都是怎么管理的，有其他的工具和手段也请希望多多指点。 <

1 0

邮件列表不太活跃，做了一个小社区，希望大家喜欢
by xxxmailk 11 Sep '16

11 Sep '16

鉴于大家都比较关注和喜欢openstack，但邮件列表可能不太符合大家的用户习惯，我特意搭建了一个小社区为大家提供方便，全中文交流，希望大家能够喜欢。社区非盈利性质，希望大家能够爱护和支持。社区地址：http://www.op99.cn 社区名称：op99开源技术社区社区成立时间：2016年7月17日。 2016-07-21 xxxmailk

7 8

Mitaka nova/cinder LVM的代码的分布 (nova-13.0.0 cinder-8.0.0)
by wk 22 Aug '16

22 Aug '16

hi：请教个cinder的问题。使用本地的lvm做cinder的物理存储。猜测lvm相关的代码在cinder-8.0.0\cinder\volume\drivers\lvm.py里面。但是没有调用lvm的lvcreate命令: def _create_volume(self, name, size, lvm_type, mirror_count, vg=None): vg_ref = self.vg if vg is not None: vg_ref = vg vg_ref.create_volume(name, size, lvm_type, mirror_count) lvcreate是在nova目录下： [root@opentest stack]# vi ./nova/nova/virt/libvirt/storage/lvm.py from oslo_concurrency import processutils from oslo_log import log as logging from oslo_utils import units import six import nova.conf from nova import exception from nova.i18n import _ from nova.i18n import _LW from nova.virt.libvirt import utils CONF = nova.conf.CONF LOG = logging.getLogger(__name__) def create_volume(vg, lv, size, sparse=False): """Create LVM image. Creates a LVM image with given size. :param vg: existing volume group which should hold this image :param lv: name for this image (logical volume) :size: size of image in bytes :sparse: create sparse logical volume """ if sparse: preallocated_space = 64 * units.Mi check_size(vg, lv, preallocated_space) if free_space < size: LOG.warning(_LW('Volume group %(vg)s will not be able' ' to hold sparse volume %(lv)s.' ' Virtual volume size is %(size)d bytes,' ' but free space on volume group is' ' only %(free_space)db.'), {'vg': vg, 'free_space': free_space, 'size': size, 'lv': lv}) cmd = ('lvcreate', '-L', '%db' % preallocated_space, '--virtualsize', '%db' % size, '-n', lv, vg) 以及cinder的cinder\brick\local_dev]\lvm.py, brick的代码为什么不放在cinder\volume\drivers\lvm.py里面? def create_volume(self, name, size_str, lv_type='default', mirror_count=0): """Creates a logical volume on the object's VG. :param name: Name to use when creating Logical Volume :param size_str: Size to use when creating Logical Volume :param lv_type: Type of Volume (default or thin) :param mirror_count: Use LVM mirroring with specified count """ if lv_type == 'thin': pool_path = '%s/%s' % (self.vg_name, self.vg_thin_pool) cmd = LVM.LVM_CMD_PREFIX + ['lvcreate', '-T', '-V', size_str, '-n', name, pool_path] else: cmd = LVM.LVM_CMD_PREFIX + ['lvcreate', '-n', name, self.vg_name, '-L', size_str]

1 0