On 02/16/11 04:50 PM, Dave Miner wrote:
On 02/16/11 05:28 AM, Jan Damborsky wrote:
Hi John,
I have a questions not related to proposed fix itself, but related
to that CR, I believe.
There are two service discovery mechanisms currently used on AI client:
* mDNS
* fallback mechanism
Fallback mechanism is used if mDNS one fails. It obtains service
provider
from install_svc_address property.
Looking at bug report, it seems like AI didn't succeed to obtain
manifest at all,
so I assume that both mechanisms failed. Proposed fix seems to address
mDNS part of the problem.
I have taken a quick look at what might went wrong with fallback
mechanism
and it seems there is a discrepancy between what manifest-locator puts
into /tmp/service_list.$$ and what ai_get_manifest expects.
manifest-locator populates /tmp/service_list.$$ with 'IP:port'
(provided via install_svc_address) while ai_get_manifest now seems to
expect
'IP:port:service':
# echo "192.168.100.10:5555" > /tmp/svc
# ai_get_manifest -s /tmp/svc -o /tmp/m.xml
Traceback (most recent call last):
File "/usr/bin/ai_get_manifest", line 939, in <module>
RET_CODE = main()
File "/usr/bin/ai_get_manifest", line 932, in main
return(parse_cli(sys.argv))
File "/usr/bin/ai_get_manifest", line 858, in parse_cli
(ai_service, ai_port, ai_name) = service.split(':')
ValueError: need more than 2 values to unpack
# echo "192.168.100.10:5555:x-7012389-158" > /tmp/svc
# ai_get_manifest -s /tmp/svc -o /tmp/m.xml ; echo $?
0
#
I believe that should be fixed as well (assuming fallback mechanism
still matters).
It absolutely matters, since mDNS is typically not forwarded across
subnet boundaries.
You are right - now I recall :-)
Thanks for looking into why that didn't work, too.
You are welcome, Dave.
Jan
_______________________________________________
caiman-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
