Open Stack

Johnson,

I am not sure what you mean by 'attach volume manually'.  Do you mean
when you do a 'nova volume-attach'?  If so, then, yes, the process will
use the appropriate iscsi_helper and iscsi_ip_address to configure the
attachment.

Does that answer your question?

Jay

On Mon, 2014-07-21 at 12:23 +0000, Johnson Cheng wrote:
> Dear Thomas,
> 
> Thanks for your reply.
> So when I attach volume manually, will iSCSI LUN be automatically setup via cinder.conf (iscsi_helper and iscsi_ip_address)?
> 
> 
> Regards,
> Johnson
> 
> -----Original Message-----
> From: Duncan Thomas [mailto:duncan.thomas at gmail.com] 
> Sent: Monday, July 21, 2014 6:16 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target Question
> 
> The iSCSI lun won't be set up until you try to attach the volume
> 
> On 17 July 2014 12:44, Johnson Cheng <Johnson.Cheng at qsantechnology.com> wrote:
> > Dear All,
> >
> >
> >
> > I installed iSCSI target at my controller node (IP: 192.168.106.20),
> >
> > #>iscsitarget open-iscsi iscsitarget-dkms
> >
> >
> >
> > then modify my cinder.conf at controller node as below,
> >
> > [DEFAULT]
> >
> > rootwrap_config = /etc/cinder/rootwrap.conf
> >
> > api_paste_confg = /etc/cinder/api-paste.ini
> >
> > #iscsi_helper = tgtadm
> >
> > iscsi_helper = ietadm
> >
> > volume_name_template = volume-%s
> >
> > volume_group = cinder-volumes
> >
> > verbose = True
> >
> > auth_strategy = keystone
> >
> > #state_path = /var/lib/cinder
> >
> > #lock_path = /var/lock/cinder
> >
> > #volumes_dir = /var/lib/cinder/volumes
> >
> > iscsi_ip_address=192.168.106.20
> >
> >
> >
> > rpc_backend = cinder.openstack.common.rpc.impl_kombu
> >
> > rabbit_host = controller
> >
> > rabbit_port = 5672
> >
> > rabbit_userid = guest
> >
> > rabbit_password = demo
> >
> >
> >
> > glance_host = controller
> >
> >
> >
> > enabled_backends=lvmdriver-1,lvmdriver-2
> >
> > [lvmdriver-1]
> >
> > volume_group=cinder-volumes-1
> >
> > volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
> >
> > volume_backend_name=LVM_iSCSI
> >
> > [lvmdriver-2]
> >
> > volume_group=cinder-volumes-2
> >
> > volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver
> >
> > volume_backend_name=LVM_iSCSI_b
> >
> > [database]
> >
> > connection = mysql://cinder:demo@controller/cinder
> >
> >
> >
> > [keystone_authtoken]
> >
> > auth_uri = http://controller:5000
> >
> > auth_host = controller
> >
> > auth_port = 35357
> >
> > auth_protocol = http
> >
> > admin_tenant_name = service
> >
> > admin_user = cinder
> >
> > admin_password = demo
> >
> >
> >
> > Now I use the following command to create a cinder volume, and it can 
> > be created successfully.
> >
> > #> cinder create --volume-type lvm_controller --display-name vol 1
> >
> >
> >
> > Unfortunately it seems not attach to a iSCSI LUN automatically because 
> > I can not discover it from iSCSI initiator,
> >
> > #> iscsiadm -m discovery -t st -p 192.168.106.20
> >
> >
> >
> > Do I miss something?
> >
> >
> >
> >
> >
> > Regards,
> >
> > Johnson
> >
> >
> >
> >
> >
> > From: Manickam, Kanagaraj [mailto:kanagaraj.manickam at hp.com]
> > Sent: Thursday, July 17, 2014 1:19 PM
> >
> >
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: Re: [openstack-dev] [Cinder] Integrated with iSCSI target 
> > Question
> >
> >
> >
> > I think, It should be on the cinder node which is usually deployed on 
> > the controller node
> >
> >
> >
> > From: Johnson Cheng [mailto:Johnson.Cheng at QsanTechnology.com]
> > Sent: Thursday, July 17, 2014 10:38 AM
> > To: OpenStack Development Mailing List (not for usage questions)
> > Subject: [openstack-dev] [Cinder] Integrated with iSCSI target 
> > Question
> >
> >
> >
> > Dear All,
> >
> >
> >
> > I have three nodes, a controller node and two compute nodes(volume node).
> >
> > The default value for iscsi_helper in cinder.conf is “tgtadm”, I will 
> > change to “ietadm” to integrate with iSCSI target.
> >
> > Unfortunately I am not sure that iscsitarget should be installed at 
> > controller node or compute node?
> >
> > Have any reference?
> >
> >
> >
> >
> >
> > Regards,
> >
> > Johnson
> >
> >
> >
> >
> > _______________________________________________
> > OpenStack-dev mailing list
> > OpenStack-dev at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> >
> 
> 
> 
> --
> Duncan Thomas
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev