You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@crail.apache.org by "Jonas Pfefferle (JIRA)" <ji...@apache.org> on 2019/03/04 10:34:00 UTC
[jira] [Commented] (CRAIL-93) Using Crail with NVMf, the Default
NQN also attaches the port number to the name.
[ https://issues.apache.org/jira/browse/CRAIL-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16783217#comment-16783217 ]
Jonas Pfefferle commented on CRAIL-93:
--------------------------------------
1) You are correct. The NQN currently appends the port number. This is a hack to allow connecting to multiple targets on the same host, as currently the nqn is not stored on the namenode. However, this should not have made it into the upstream version. I will remove it until we figure out a solution for the problem. So once fixed you should be able to use the subsystem NQN as expected.
2) The host NQN is generated from a random UUID (according to spec):
nqn.2014-08.org.nvmexpress:uuid:<128bit_random_uuid>
since I found no easy way to generate a unique host NQN. For now I can introduce a new configuration parameter in the config file to set the host NQN. Note that this requires to have a separate configuration file for each client that should have a different host NQN (which we generally try to avoid). Although not recommended I can try to generate a unique host NQN from the MAC address.
> Using Crail with NVMf, the Default NQN also attaches the port number to the name.
> ---------------------------------------------------------------------------------
>
> Key: CRAIL-93
> URL: https://issues.apache.org/jira/browse/CRAIL-93
> Project: Apache Crail
> Issue Type: Bug
> Affects Versions: 1.2
> Environment: I'm running crail nodes with docker containers, on a Ubuntu 18.04 base.
> Reporter: David Crespi
> Assignee: Jonas Pfefferle
> Priority: Critical
>
> This is the version I'm actually using: v1.1-2-gf0afadc
> I'm set up to use spdk on the backend to crail. When attempting to attach, it appears that crail needs two subsystems to achieve the connection. Instead of allowing the default name, I have the system variable set: -e NVMF_NQN="nqn.2017-06.io.crail:cnode"
> 1) subsystem NQN: nqn.2017-06.io.crail:cnode
> 2) subsystem NQN: nqn.2017-06.io.crail:cnode4420
> 19/03/01 17:46:45 INFO crail: CrailHadoopFileSystem fs initialization done..
> 19/03/01 17:46:45 INFO crail: Connecting to NVMf target at Transport address = /192.168.2.104:4420, subsystem NQN = nqn.2017-06.io.crail:cnode4420
> It appears that the initial connect/discovery of the subsystem uses #1, but using the
> crail commands (crail fs -mkdir /test) uses #2.
> Both have to have a valid namespace attached as well.
>
> It also appears that when using my own subsystem NQN (NVMF_NQN) name, crail wants to generate its own Host NQN. A new one every time. First, how do you learn of that
> NQN, and 2nd, it would be great to disable it if spdk has "allow any hosts" set. It refuses
> to connect to spdk.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)