从nova-volume迁移到cinder的一些提示

邮件列表上看到的，估计以后得用上，记录下，原文内容如下：

Hi Ahmed -

We don't have a specific Cinder install guide, but this wiki page
gives guidance:
http://wiki.openstack.org/<wbr>MigrateToCinder</wbr>

Specific to nova.conf:

set the correct volume api class in nova.conf
volume_api_class=nova.volume.

<wbr>cinder.API<br><br> disable the nova-volume-api in enabled apis in /etc/nova/nova.conf sed<br> -i "s/osapi_volume,// /etc/nova/nova.conf", if you do not have<br> enabled_apis set explicitly set it to<br> enabled_apis=ec2,osapi_<wbr>compute,metadata as osapi_volume is included by<br> default<br><br> Hope this helps.<br> Anne<br><div> <div class="im"> <br> On Mon, Nov 5, 2012 at 2:43 PM, Ahmed Al-Mehdi &lt;<a href="mailto:[e-mail]">[e-mail]</a>&gt; wrote:<br> &gt; Hello,<br> &gt;<br> &gt; I am following the steps outlined in "OpenStack Install and Deploy – Ubuntu"<br> &gt; to setup a two node configuration. I plan to use Cinder as the block<br> &gt; storage instead of nova-volume. I have a few question regarding sample<br> &gt; nova.conf file mentioned in the doc (<br> &gt; <a href="http://docs.openstack.org/trunk/openstack-compute/install/apt/content/compute-minimum-configuration-settings.html" target="_blank"> http://docs.openstack.org/<wbr>trunk/openstack-compute/<wbr>install/apt/content/compute-<wbr>minimum-configuration-<wbr>settings.html</wbr></wbr></wbr></wbr></a><br> &gt; ):<br> &gt;<br> &gt; - In the "VOLUME" section, are those same options applicable for Cinder?<br> &gt; Is there any documentation on installing Cinder (even a draft copy).<br> &gt;<br> &gt; - Does Cinder use the same iscsi application (iSCSI Target) and utility to<br> &gt; create/manage storage as nova-volume?<br> &gt;<br> &gt; - In the section "COMPUTE" section, "libvirt_type=qem". I am guessing<br> &gt; since the manual is written specific for kvm, the config parameter should be<br> &gt; "libvirt_type=kvm". Is that a typo in the doc?<br> &gt;<br> &gt; - In the section "COMPUTE/APIS",<br> &gt;<br> &gt; # COMPUTE/APIS: if you have separate configs for separate services<br> &gt; # this flag is required for both nova-api and nova-compute<br> &gt; allow_resize_to_same_host=True<br> &gt;<br> &gt; What exactly does "separate config" mean, separate config file, different<br> &gt; configuration? Did not find much info in the docs (<br> &gt; <a href="http://docs.openstack.org/essex/openstack-compute/admin/content/compute-options-reference.html" target="_blank"> http://docs.openstack.org/<wbr>essex/openstack-compute/admin/<wbr>content/compute-options-<wbr>reference.html</wbr></wbr></wbr></a><br> &gt; ). Should I just leave it to "true".<br> &gt;<br> &gt; - In the section "NETWORK", I am assuming the config "my_ip" is not used by<br> &gt; nova, but for internal consumption by the script?<br> &gt;<br> &gt;<br> &gt; Thank you very much for your help.<br> &gt;<br> &gt; Regards,<br> &gt; Ahmed.</div> </div> </wbr></wbr>