IscsiChapSupport

• Launchpad Entry: CinderSpec:iscsi-chap
• Created: 13 Aug 2012
• Contributors: Vincent Hou

Summary

A server

CHAP(Challenge-Handshake Authentication Protocol) is an authentication scheme used by Point to Point Protocol (PPP) servers to validate the identity of remote clients. It can applied in iSCSI to authenticate the initiators or the targets. There are several types of CHAP, including one-way authentication, two-way authentication and reverse authentication. At the beginning of this blueprint, one-way CHAP authentication, via which the target authenticates the initiators, will be implemented first.

Release Note

This section should include a paragraph describing the end-user impact of this change. It is meant to be included in the release notes of the first release in which it is implemented. (Not all of these will actually be included in the release notes, at the release manager's discretion; but writing them is a useful exercise.)

It is mandatory.

User stories

User sets iSCSI san Flags in nova.conf, and starts/restarts nova-volume service.

Example nova.conf entries:

• --volume_manager=nova.volume.manager.VolumeManager --volume_driver=nova.volume.san.SolidFireSanISCSIDriver --iscsi_ip_prefix=192.168.69.211 --san_ip=192.168.69.210 --san_login=cluster_login --san_password=password --poolname=nova

The SolidFire appliance should now be available for use by OpenStack for additional block storage.

volume-create:

• SolidFire driver first builds a SolidFire user account based on a concatenation of the compute nodes hostname and the nov-volume objects project_id. For example if the compute nodes hostname is: 'mycomputenode' and the project_id is '1', then the SolidFire account will be 'mycomputenode-1'. This account is critical for using the SolidFire device, it determines ownership of the volumes on the system and is also used to store/configure all of the CHAP information. The next step is to querie the SolidFire system and see if the account exists, if it does we extract the information we pull the information we need from the system (CHAP and accountID info) and use it in volume creation. If the account does now exist, then we create it using a randomly generated 12 character string for CHAP passwords. Using the accountID the requested volume is created

volume-attach:

• Volume is attached using the current iSCSI/nova api methods. Model updates are done during creation as well as export to avoid re-scans.

volume-delete:

• The SolidFire driver verifies the volume_name from the database as well as the account and issues the SolidFire API call to delete the volume.

On volume_create()

• A user account name is built based on a concatenation of the compute nodes hostname and the project-id ie on compute node with hostname 'myhost' and a project_if of '1' the result would be:
  • 'myhost-1'

This has been tested with the current Diablo release using the nova api, as well as with the current Trunk release of Essex (devstack install

---