Index: [Article Count Order] [Thread]

Date: Wed, 12 Nov 2008 13:50:18 +0800
From: "Rommel Laranjo" <rslaranjo@gmail.com>
Subject: [users:00991] Re: Collecting the problem information regarding VEL
To: users@tahi.org
Message-Id: <f051005f0811112150n2ecd43a6tf90c74084928f69b@mail.gmail.com>
In-Reply-To: <6E54B86AA7254B43B1B0217628D37B3702AFF9452285@EXMAIL02.jp.ykgw.net>
References: <C2231149-7874-40A8-B176-39B74DE91A1C@tahi.org>	 <200810221404.23510.cihlarov@suse.cz>	 <6E54B86AA7254B43B1B0217628D37B3702AFF9452238@EXMAIL02.jp.ykgw.net>	 <f051005f0811111940i7ff87022me7e33ae005b9098e@mail.gmail.com>	 <6E54B86AA7254B43B1B0217628D37B3702AFF9452285@EXMAIL02.jp.ykgw.net>
X-Mail-Count: 00991

Hiroki-san,

This is great! I'll be waiting for its release.

Thank you so much.

Rommel


2008/11/12  <Hiroki.Endou@jp.yokogawa.com>:
> Hi Rommel and all,
>
> The current version of VEL does not support Version 4.0.1 of the IPv6 Ready
> Interoperability Specification.
> To support it, we are now updating VEL's scenarios.
> We release the new version by the beginning of December.
>
> Best regards,
> --
> Hiroki ENDO, TAHI Project
>
>> -----Original Message-----
>> From: Rommel Laranjo [mailto:rslaranjo@gmail.com]
>> Sent: Wednesday, November 12, 2008 12:40 PM
>> To: users@tahi.org
>> Subject: [users:00988] Re: Collecting the problem information
>> regarding VEL
>>
>> Hello TAHI users,
>>
>> I am very much interested to use VEL in our Phase 2
>> Interoperability Testing.
>> But first, I would to ask if the current version of VEL
>> already support Version 4.0.1 of the IPv6 Ready
>> Interoperability Specification?
>>
>> I gladly appreciate your reply.
>>
>> Thanks,
>>
>> Rommel
>>
>>
>>
>> 2008/10/23  <Hiroki.Endou@jp.yokogawa.com>:
>> > Hi Klara,
>> >
>> > Thanks for your contribution!
>> > You have been a great help.
>> >
>> > I am interested in your testing environment. Would you tell OS name
>> > and its version which you use as target and reference nodes?
>> > When you notice additional problems, please give us your comments.
>> >
>> > Thanks again,
>> > --
>> > Hiroki ENDO
>> > TAHI Project
>> >
>> >> -----Original Message-----
>> >> From: Klara Cihlarova [mailto:cihlarov@suse.cz]
>> >> Sent: Wednesday, October 22, 2008 9:04 PM
>> >> To: Hiroshi MIYATA
>> >> Cc: users@tahi.org
>> >> Subject: [users:00948] Re: Collecting the problem information
>> >> regarding VEL
>> >>
>> >> Hi,
>> >> we are just using the vel. I am planning to prepare more detailed
>> >> info after testing but if you are here with the question,
>> there are
>> >> some problems ;-).
>> >>
>> >> There was a small problem to build it, so we made a change in
>> >> lib/Tg/TcSocket.h. Here is a diff:
>> >>
>> >> cihlarov@gnoll:/tmp/vel-1.0.4/lib> diff -u Tg/TcSocket.h
>> >>
>> /nfshome/cihlarov/Export/cert/ipv6/vel-1.0.4-patched/lib/Tg/TcSocket.h
>> >> --- Tg/TcSocket.h       2005-07-13 03:46:14.000000000 +0200
>> >> +++
>> >>
>> /nfshome/cihlarov/Export/cert/ipv6/vel-1.0.4-patched/lib/Tg/TcSocket
>> >> +++ .h
>> >> 2008-05-20 17:47:18.000000000 +0200
>> >> @@ -104,7 +104,7 @@
>> >>         void startTimer(time_t,uint32_t);
>> >>  virtual        void startTimer();
>> >>         STR buffer(int32_t);
>> >> -virtual        int TcSocket::receiveBuffer(STR s,int32_t len);
>> >> +virtual        int receiveBuffer(STR s,int32_t len);
>> >>         int connectIndication();
>> >>  virtual        int connectAction()=0;
>> >>  virtual        sockaddr* destSock()=0;
>> >>
>> >>
>> >> There is also a little problem to find waiting sync, so our other
>> >> small change
>> >> is:
>> >>
>> >> cihlarov@gnoll:/tmp/vel-1.0.4/lib> diff -u Tg/TgStatement.cc
>> >> /nfshome/cihlarov/Export/cert/ipv6/vel-1.0.4-patched/lib/Tg/Tg
>> > Statement.cc
>> >> --- Tg/TgStatement.cc   2005-07-13 03:46:14.000000000 +0200
>> >> +++
>> >>
>> /nfshome/cihlarov/Export/cert/ipv6/vel-1.0.4-patched/lib/Tg/TgStatem
>> >> +++ ent.cc
>> >> 2008-05-20 17:05:02.000000000 +0200
>> >> @@ -278,11 +278,14 @@
>> >>                 switch((int)step_) {
>> >>                         case 0:
>> >>                                 setTime(startTime_);
>> >> +                               if (logLevel > 0) {
>> >> +                                       managerLog("prepare: %s
>> >> (\"%s\")",host->name(),command_.string());
>> >> +                               }
>> >>
>> >>
>> result=agent->opCommand(thread_,this,id_req,command_.string(),waitf);
>> >>                                 break;
>> >>                         default:
>> >>                                 setTime(endTime_);
>> >> -                               managerLog("%s
>> >> (\"%s\")",host->name(),command_.string());
>> >> +                               managerLog("done: %s
>> >> (\"%s\")",host->name(),command_.string());
>> >>                                 abort=false; return  false;}
>> >>                 if(result==false) {abort=true; return false;}
>> >>                 if(waitf==true) break;} @@ -297,11 +300,14 @@
>> >>                 switch((int)step_) {
>> >>                         case 0:
>> >>                                 setTime(startTime_);
>> >> +                               if (logLevel > 0) {
>> >> +                                       managerLog("prepare: %d
>> >> (\"%s\")",step_,event_.string());
>> >> +                               }
>> >>
>> >> result=TgSyncEvent::syncEvent(thread_,this,id_req,event_,waitf);
>> >>                                 break;
>> >>                         default:
>> >>                                 setTime(endTime_);
>> >> -                               managerLog(
>> >> "(\"%s\")",event_.string());
>> >> +                               managerLog( "done: %d
>> >> (\"%s\")",step_,event_.string());
>> >>                                 abort=false; return  false;
>> >>                 }
>> >>                 if(result==false) {abort=true; return false;}
>> >> cihlarov@gnoll:/tmp/vel-1.0.4/lib>
>> >>
>> >> It is really a small change, because we have not time to implement
>> >> more :-(.
>> >> It would be great to have more debug options.
>> >>
>> >> Because we are using OpenBSD, we added config for it. The
>> ip command
>> >> has now a little different syntax in openSUSE, so we changed the
>> >> USAGI config. Both changes are in attachments. I am not sure, if
>> >> everything is OK, but hope, it helps you.
>> >>
>> >>
>> >> --
>> >> Best Regards / Mit freundlichen Gruessen / S pozdravem,
>> >>
>> >> KláÓa Cihlâúová
>> >>
>> >> QA Developer
>> >>
>> ---------------------------------------------------------------------
>> >> SUSE LINUX, s.r.o.                       e-mail: cihlarov@suse.cz
>> >> Lihovarská 1060/12                       tel: +420 284 028 958
>> >> 190 00 Praha 9                           fax: +420 284 028 951
>> >> Czech Republic                           http://www.suse.cz
>> >>
>> ---------------------------------------------------------------------
>> >>
>> >
>> >
>> >
>>
>>
>>
>
>
>