Hello Ahmed,<br><br>it seems like we are facing the same problems!<br><br>I was able to install cinder and you can find the instructions here <a href="http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html">http://docs.openstack.org/trunk/openstack-compute/install/apt/content/osfolubuntu-cinder.html</a>.<br>
<br>The instructions still have some errors and/or miss some info you can find reading these bugs that are still open:<br><br>- <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1078057">https://bugs.launchpad.net/openstack-manuals/+bug/1078057</a><br>
- <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1078353">https://bugs.launchpad.net/openstack-manuals/+bug/1078353</a><br><br>This installation uses tgt and I experimented only that one.<br><br>To my knowledge, there's no cinder command for listing or showing the volume group cinder is currently using. In my opinion, this makes sense: the volume group is something that makes sense only in the case you are using tgt as virtualization technology for supporting virtual volumes but this is incidental.<br>
In case, in the future, you use a different technology, maybe the volume group concept disappears.<br>I mean, tgt (the enabling technology) needs a volume group for working but the purpose of cinder is to provide volumes to users independently on how they are implemented.<br>
<br>Anyway, if you what a complete list of cinder commands, just type<br><br><b>$ cinder help</b><br><br>In case you want to know more on a single command (the line above gives the whole list), type:<br><br><b>$ cinder help <command></b><br>
<br>For example<br><br><b>$ cinder help show</b><br><br>gives information on the syntax and the semantics of command "cinder show".<br><br>BTW: this instructions are also valid for other CLIs like nova, keystone and quantum.<br>
<br>Adding a new volume group in addition to cinder-volumes?<br><br>To be honest I don't know. It depends on how tgt works (<a href="http://stgt.sourceforge.net/">http://stgt.sourceforge.net/</a>).<br><br>On the other hand, I think that if your goal is to add storage to an already in place infrastructure, then you probably need to add physical volumes to cinder-volumes volume group.<br>
I'm not an expert on this field, but I think you've got to investigate vg (volume group) commands like vgscan, vgextend (I presume this is the one you need to use for adding storage to an existing volume group), etc...<br>
<br>Caveat: read very carefully this bug report <a href="https://bugs.launchpad.net/openstack-manuals/+bug/1078353">https://bugs.launchpad.net/openstack-manuals/+bug/1078353</a>.<br><br>Regards,<br>Marco.<br><br><br><br><br>
<br><br><br><br><br> <br><br><br><div class="gmail_quote">On Wed, Dec 5, 2012 at 12:02 AM, Ahmed Al-Mehdi <span dir="ltr"><<a href="mailto:ahmedalmehdi@gmail.com" target="_blank">ahmedalmehdi@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br><br>In my setup, cinder.conf is set as follows:<br><br>root@novato:/etc/cinder# cat cinder.conf<br>[DEFAULT]<br>
rootwrap_config=/etc/cinder/rootwrap.conf<br>sql_connection = mysql://<a href="http://cinderUser:cinderPass@10.176.20.102/cinder" target="_blank">cinderUser:cinderPass@10.176.20.102/cinder</a><br>
api_paste_confg = /etc/cinder/api-paste.ini<br>iscsi_helper=ietadm<br>volume_name_template = volume-%s<br>volume_group = cinder-volumes<br>verbose = True<br>auth_strategy = keystone<br>#osapi_volume_listen_port=5900<br><br>
root@novato:/etc/cinder# grep -nsir cinder /etc/iet/*<br>root@novato:/etc/cinder# grep -nsir cinder /etc/tgt/*<br>/etc/tgt/conf.d/cinder_tgt.conf:1:include /var/lib/cinder/volumes/*<br><br><br>I have a few cinder related questions:<br>
- Which iSCSI target is officially supported / tested in Folsom release - IET (<a href="http://sourceforge.net/projects/iscsitarget/files/" target="_blank">http://sourceforge.net/projects/iscsitarget/files/</a>) or tgt (<a href="http://sourceforge.net/projects/iscsitarget/files/" target="_blank">http://sourceforge.net/projects/iscsitarget/files/</a>). If both are supported, what is the appropriate value for "volume_driver" and "iscsi_helper" in cinder.conf for either of them. Any docs explaining this?<br>
<br>- Will Cinder create an internal ID (representation) for volume_group - "cinder-volumes"?<br><br>- What cinder cli command can I issue to get info on the volume_group - "cinder-volumes"?<br><br>- Is there a way I can add an additional volume-group, e.g "cinder-volumes2"?<br>
<br>I read through the doc at <a href="http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_volumes.html" target="_blank">http://docs.openstack.org/folsom/openstack-compute/admin/content/ch_volumes.html</a>, but did not find answers to the above.<br>
<br>Thank you very much in advance.<br><br>Regards,<br>Ahmed.<br><br>
<br>_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br></blockquote></div><br>