Hi,
I'd already setup nexenta in a independent server and nova-volume run on another server with nexenta driver configured in nova.conf to provide volume service to the openstack system. I can use command or dashboard to create volume well and nexenta also have create relative zol,but question is I always could not attach the volume to the instance,here is the environment and questions I met: 1. The output of "iscsiadm -m session" that compute node show(volume-00000001 is created by command and was in the list of nexenta ZVOL list) root@nc01:/home/romi# iscsiadm -m session tcp: [21] 192.168.1.42:3260,1 iqn.1986-03.com.sun:01:005008c802ff.4fb2f97dvolume-00000001 tcp: [5] 192.168.1.42:3260,2 iqn.1986-03.com.sun:01:005008c802ff.4fb2f97d 2. When I use command to attach the volume to the instance, nova-volume service gave the log error is: Command: sudo iscsiadm -m node -T "iqn.1986-03.com.sun:01:005008c802ff.4fb2f97d"volume-00000001 -p 192.168.1.42:3260 --rescan 2012-06-26 18:00:37 TRACE nova.rpc.amqp Stderr: 'iscsiadm: No portal found.\n' 3. I try to run "icsiadm -m node -T "iqn.1986-03.com.sun:01:005008c802ff.4fb2f97d"volume-00000001 -p 192.168.1.42:3260 -rescan" manually in compute node, the output is well: Rescanning session [sid: 21, target: iqn.1986-03.com.sun:01:005008c802ff.4fb2f97dvolume-00000001, portal: 192.168.1.42,3260] So, I could not know what is wrong or is there special setting needed in nexenta server? Appreciate if someone could help. Regards, Romi
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp