Ask Your Question
0

Understanding iSCSI in Openstack

asked 2011-05-10 18:14:02 -0600

mahahn gravatar image

Hey, we got Nova, Glance, and Swift setup. Everything seems to be working with starting instances. Now we are trying to setup iSCSI so that we can present extra storage to the instances. I am trying to understand how Openstack handles iSCSI. However, the documentation seems kind of vague. I have a couple of questions.

First, how do the iSCSI LUNs get presented to the instances? Does the compute node present the iSCSI LUN to the instance via KVM? Or does the instance talk to the nova-volume service directly via iSCSI to get the volume?

Second, I am not understanding the –iscsi_ip_prefix argument in nova.conf. What exactly is this flag used for? What network should we specify here?

Thanks, Matt

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2011-05-10 19:02:33 -0600

vishvananda gravatar image

On May 10, 2011, at 11:15 AM, Matthew Hahn wrote:

New question #156930 on OpenStack Compute (nova): https://answers.launchpad.net/nova/+q...

Hey, we got Nova, Glance, and Swift setup. Everything seems to be working with starting instances. Now we are trying to setup iSCSI so that we can present extra storage to the instances. I am trying to understand how Openstack handles iSCSI. However, the documentation seems kind of vague. I have a couple of questions.

First, how do the iSCSI LUNs get presented to the instances? Does the compute node present the iSCSI LUN to the instance via KVM? Or does the instance talk to the nova-volume service directly via iSCSI to get the volume?

In KVM, the compute host attaches to the iscsi target and presents the disk to the guest as a local block device

Second, I am not understanding the –iscsi_ip_prefix argument in nova.conf. What exactly is this flag used for? What network should we specify here?

During the discovery process, iscsiadm reports all of the ips that the target is exposed on. The prefix is matched against the possible IPs so that it knows which IP to connect to. It just uses simple string matching, so if all of your hosts are on the 192.168.1.0/24 network you could use --iscsi_ip_prefix=192.168.1

This code is a bit hacky, and it will probably be converted to actually store the ip in the database so the discovery doesn't have to happen.

Thanks, Matt


You received this question notification because you are a member of Nova Core, which is an answer contact for OpenStack Compute (nova).

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2011-05-10 18:14:02 -0600

Seen: 148 times

Last updated: May 10 '11