Jump to: navigation, search

Difference between revisions of "IscsiChapSupport"

 
Line 18: Line 18:
 
== Rationale ==
 
== Rationale ==
 
== User stories ==
 
== User stories ==
−
== Assumptions ==
+
User sets iSCSI san Flags in nova.conf, and starts/restarts nova-volume service.
−
Glance ''stores'' the server template and metadata map; Nova must ''implement'' the server template.
+
 
 +
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.
  
−
== Design ==
+
volume-create:
−
This is just one possible design for this feature (keep that in mind). At its simplest, a server template consists of a core image and a ''metadata map''. The metadata map defines metadata that must be collected during server creation and a list of files (on the server) that must be modified using the defined metadata.
 
  
−
Here is a simple example: let's assume that the server template has a Linux server with Apache HTTP installed. Apache needs to know the IP address of the server and the directory on the server that contains the HTML files.
+
* [[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
  
−
The metadata map would look something like this:
+
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.
  
−
<pre><nowiki>
+
volume-delete:
−
  metadata {
 
−
  IP_ADDRESS;
 
−
  HTML_ROOT : string(1,255) : "/var/www/";
 
−
  }
 
−
  map {
 
−
  /etc/httpd/includes/server.inc
 
−
  }
 
−
</nowiki></pre>
 
  
−
In this case, the <code><nowiki>metadata</nowiki></code> section defines the metadata components required; the <code><nowiki>map</nowiki></code> section defines the files that must be parsed and have the metadata configured. Within the <code><nowiki>metadata</nowiki></code> section, there are two defined items. <code><nowiki>IP_ADDRESS</nowiki></code> is a predefined (built-in) value, and <code><nowiki>HTML_ROOT</nowiki></code> is the root directory of the web server.
+
* 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.
  
−
For <code><nowiki>HTML_ROOT</nowiki></code>, there are three sub-fields: the name, the data type, and (in this case) the default value. The token <code><nowiki>required</nowiki></code> could be used for items that must be supplied by the user.
+
On volume_create()
  
−
When the server is created, a (as-yet-undefined) process would look at the files in the <code><nowiki>map</nowiki></code> section and replace metadata tokens with the defined values. For example, the file might contain:
+
* 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
  
−
<pre><nowiki>
+
== Assumptions ==
−
<VirtualHost {{IP_ADDRESS}}:*>
+
== Design ==
−
  DocumentRoot "{{HTML_ROOT}}";
 
−
</VirtualHost>
 
−
</nowiki></pre>
 
  
 
== Implementation ==
 
== Implementation ==
Line 78: Line 77:
  
 
----
 
----
−
 
 
[[Category:Spec]]
 
[[Category:Spec]]

Revision as of 11:48, 14 August 2012

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

Summary

A server template consists of a base image plus the definitions of configuration metadata. For example, a server template might include an Apache HTTP server; the metadata would include the server name, location of the HTML root directory, and tuning parameters. Glance stores the template in its registry; Nova, when creating a new server from the template, would validate the required metadata and configure the internal applications directly.

The metadata could also be used to drive automatically-generated web interfaces to solicit the configuration metadata.

Server templates could greatly increase the flexibility and usability of compute clouds; rather than creating a "bare" server and configuring it manually, this could allow users to prepopulate applications in a server image and configure them automatically.

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.

Rationale

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

Assumptions

Design

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

This need not be added or completed until the specification is nearing beta.

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.

Retrieved from "https://wiki.openstack.org/w/index.php?title=IscsiChapSupport&oldid=989"