Page 1 of 1

The use of $(id) in the target's name

Posted: Fri Aug 24, 2007 1:20 pm
by Han
Can somebody explain the use of $(id) in the target's name e.g.:
iqn.2003-06.rocketdivision.starwind.$(host).$(id)?
Whenever I try to use the $(id) macro the following is logged:

target name 'iqn.2003-06.rocketdivision.starwind.stor01.$(host).$(id)' is invalid according to RFC 3722!

Regards,
Han Valk.

Posted: Mon Aug 27, 2007 7:50 am
by Bohdan (staff)
Hi.
According to RFC 3722:
An iSCSI name is a string of UTF-8 [RFC3629] characters that includes a type designator, a naming authority based on domain names, and a unique part within the naming authority. The unique part may be generated based on anything the naming authority deems useful, and may include user input.

So, 'id' - is a unique part within the naming authority.
But this template (iqn.2003-06.rocketdivision.starwind.$(host).$(id)) is only used when target name is not specified during target sharing. If target name is specified then iqn = target name.

Posted: Mon Aug 27, 2007 7:57 am
by Han
From the configuration file:

<!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>-->

So the default target name is based on $(symid) not $(id). I would like to use iqn.2003-06.com.rocketdivision.starwind:$(host).$(id). But what ever combination I use I'm unable to use the $(id) macro.
Could this be a bug?
bohdan (staff) wrote:Hi.
According to RFC 3722:
An iSCSI name is a string of UTF-8 [RFC3629] characters that includes a type designator, a naming authority based on domain names, and a unique part within the naming authority. The unique part may be generated based on anything the naming authority deems useful, and may include user input.

So, 'id' - is a unique part within the naming authority.
But this template (iqn.2003-06.rocketdivision.starwind.$(host).$(id)) is only used when target name is not specified during target sharing. If target name is specified then iqn = target name.

Posted: Mon Aug 27, 2007 8:25 am
by Val (staff)
Han wrote:From the configuration file:

<!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>-->

So the default target name is based on $(symid) not $(id). I would like to use iqn.2003-06.com.rocketdivision.starwind:$(host).$(id). But what ever combination I use I'm unable to use the $(id) macro.
Could this be a bug?
Hi,

Only macros $(host) and $(symid) are supported by StarWind.
- $(host) is the name of the host
- $(symid) is the name of the target (like imagefile0, etc)

The use of $(id) in the target's name

Posted: Mon Aug 27, 2007 8:37 am
by Han
Thanks that explains the behaviour I see. It would probably be a good idea to remove $(id) macro the from the documentation (StarWind configuration.doc)

valery (staff) wrote:
Han wrote:From the configuration file:

<!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>-->

So the default target name is based on $(symid) not $(id). I would like to use iqn.2003-06.com.rocketdivision.starwind:$(host).$(id). But what ever combination I use I'm unable to use the $(id) macro.
Could this be a bug?
Hi,

Only macros $(host) and $(symid) are supported by StarWind.
- $(host) is the name of the host
- $(symid) is the name of the target (like imagefile0, etc)

Re: The use of $(id) in the target's name

Posted: Mon Aug 27, 2007 8:40 am
by Val (staff)
Han wrote:Thanks that explains the behaviour I see. It would probably be a good idea to remove $(id) macro the from the documentation (StarWind configuration.doc)

valery (staff) wrote:
Han wrote:From the configuration file:

<!--<DefTargetName value="iqn.2003-06.com.rocketdivision.starwind:$(host).$(symid)"/>-->

So the default target name is based on $(symid) not $(id). I would like to use iqn.2003-06.com.rocketdivision.starwind:$(host).$(id). But what ever combination I use I'm unable to use the $(id) macro.
Could this be a bug?
Hi,

Only macros $(host) and $(symid) are supported by StarWind.
- $(host) is the name of the host
- $(symid) is the name of the target (like imagefile0, etc)
Hi,

Thank you for pointing at the documentation issue.
We'll fix it in the next version.