On Sunday, August 9, 2020 at 11:08:50 AM UTC-7, Amit Bawer wrote: > > ... > >> >>> The other option is to use one login-all call without parallelism, but >>> that would have other implications on our system to consider. >>> >> >> Such as? >> > As mentioned above, unless there is a way to specify a list of targets > and portals for a single login (all) command. > >> >>> Your answers would be helpful once again. >>> >>> Thanks, >>> - Amit >>> >>> >> You might be interested in a new feature I'm considering adding to >> iscsiadm to do asynchronous logins. In other words, the iscsiadm could, >> when asked to login to one or more targets, would send the login request to >> the targets, then return success immediately. It is then up to the end-user >> (you in this case) to poll for when the target actually shows up. >> > This sounds very interesting, but probably will be available to us only on > later RHEL releases, if chosen to be delivered downstream. > At present it seems we can only use the login-all way or logins in a > dedicated threads per target-portal. > >> >> ... >> > So you can only use RH-released packages? That's fine with me, but I'm asking you to test a new feature and see if it fixes your problems. If it helped, I would add up here in this repo, and redhat would get it by default when they updated, which they do regularly, as does my company (SUSE).
Just as a "side" point, I wouldn't attack your problem by manually listing nodes to login to. It does seem as if you assume you are the only iscsi user on the system. In that case, you have complete control of the node database. Assuming your targets do not change, you can set up your node database once and never have to discover iscsi targets again. Of course if targets change, you can update your node database, but only as needed, i.e. full discovery shouldn't be needed each time you start up, unless targets are really changing all the time in your environment. If you do discovery and have nodes in your node database you don't like, just remove them. Another point about your scheme: you are setting each node's 'startup' to 'manual', but manual is the default, and since you seem to own the open-iscsi code on this system, you can ensure the default is manual. Perhaps because this is a test? So, again, I ask you if you will test the async login code? It's really not much extra work -- just a "git clone" and a "make install" (mostly). If not, the async feature may make it into iscsiadm any way, some time soon, but I'd really prefer other testers for this feature before that. -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/open-iscsi/a86b42a0-bbc8-426e-9926-e87b6cb1a998o%40googlegroups.com.
