Re: [MTT devel] MTToGDS

[Jeff Squyres (jsquyres)]

Ok. I'll try to look at this as well - but no promises about when I can do 
so... 

-jms 
Sent from my PDA. No type good.



From: Igor Ivanov  
To: Igor Ivanov  
Cc: b...@argus-cv.com ; Igor Ivanov 
; Development list for the MPI Testing Tool 
; mtt-devel-boun...@open-mpi.org 
; Mike Dubman ; Jeff 
Squyres (jsquyres) 
Sent: Thu Mar 04 01:31:16 2010
Subject: Re: [MTT devel] MTToGDS 




Igor Ivanov wrote: 

I considered possibility to use cookie when issue was found out. But 
looking google documentation I could not understand if it solved this issue. So 
it require additional investigation that I do not have now. I will look in this 
way closer but current quick solutions were suggested in mail.
Now we have information about issue and know ways to workaround them.

Igor

Jeff Squyres wrote: 

Yoinks.

Alternatively, doesn't a Google login return a cookie of some 
flavor that is valid for a long period of time (somewhere between 1 day and 2 
weeks)?  Can't we keep/cache that cookie down in the MTT client and use it for 
subsequent data submissions until the cookie expires and we have to login again?


On Feb 27, 2010, at 8:30 AM, Igor Ivanov wrote:

  

Description:
Issue arises during submitting data frequently. We can 
get failure during data submitting with authentication error.

Reason:
Google allows a failure response on The ClientLogin 
authorization process with a CAPTCHA challenge means that Google has decided, 
for whatever reason, that additional security measures should be taken. This 
response is accompanied by a CAPTCHA image URL and a token representing the 
specific CAPTCHA challenge.
I do not see way to organize customer input in this 
case.

Detail information can be found at:

http://code.google.com/intl/en-EN/apis/accounts/docs/AuthForInstalledApps.html

Possible solutions:
1. catch error condition on server side and return 
status 503: 'Service Unavailable';
In this case client can organize processing of this 
failure (it is possible that sleeping for some time could help)
2. catch error condition on server side and accept 
authentication by correct username only w/o real verification;
3. rollback to previous scheme;


Igor

Igor Ivanov wrote:


Hi Jeff,

I am sending patch that enable google account 
approach to submit data to MTT GDS.
It also has the fix to a bug in displaying 
table as respond to bquery.pl --view (It has not been committed yet to MTT 
trunk).

As for question relating "how does one develop 
..." that source information can be found at following location as: 
http://svn.open-mpi.org/svn/mtt/trunk/docs/gds/VBench_GDS_Setup.doc.
In case you make a resolve to accept patch I am 
sending next steps should be done:

1. update application on server side using 
instruction in VBench_GDS_Setup.doc (topic 4 "Installation")
example: appcfg.py update /
2. change version on 
https://appengine.google.com/deployment?_id=open-mpi-mtt_id=1.337140739868725607
 from 1 to 2 (make default)
note: after this operation all users that 
attempt to submit data using previous scheme of authentication will get failure 
respond.
3. go to open-mpi-mtt and add new users with 
google account


Regards,
Igor

Jeff Squyres wrote:
  

Great -- many thanks!

On Feb 12, 2010, at 12:32 PM, Igor 
Ivanov wrote:

Re: [MTT devel] MTToGDS

[Jeff Squyres (jsquyres)]

Fair enough (the appspot is quit limited to admin). 

But the next time we edit it, if we could add some kind of printf about "you 
are signed in with a google account that does not have access to this portion 
of the app spot; please re-login as an authorized user" or something simple 
like that, that would be great. 

That's all I was asking about - not developing more capabilities of the admin 
side of the appspot. 

-jms 
Sent from my PDA. No type good.



From: Igor Ivanov  
To: Igor Ivanov  
Cc: b...@argus-cv.com ; Igor Ivanov 
; Development list for the MPI Testing Tool 
; yift...@voltaire.com ; Mike 
Dubman ; Jeff Squyres (jsquyres) 
Sent: Thu Mar 04 01:30:56 2010
Subject: Re: [MTT devel] MTToGDS 




Igor Ivanov wrote: 

Hi Jeff,

Look  at my comments below.

Note: be aware that my mail has been changed to itseez.com domain.

Igor

Jeff Squyres wrote: 

On Feb 16, 2010, at 10:19 AM, Igor Ivanov wrote:

  

I am sending patch that enable google account approach 
to submit data to MTT GDS.
It also has the fix to a bug in displaying table as 
respond to bquery.pl --view (It has not been committed yet to MTT trunk).



Thanks guys!  And sorry for my long lack of response - I was 
working in a window of availability for MTT stuff before, and then that window 
closed and I got sucked into other high priority things.  I have another small 
window of availability for MTT now...

It looks like Mike D. committed this stuff to SVN already, 
right?  If so, great!

  

As for question relating "how does one develop ..." 
that source information can be found at following location as: 
http://svn.open-mpi.org/svn/mtt/trunk/docs/gds/VBench_GDS_Setup.doc.



Ok, I'll dig into that.

One thing that is quite confusing is the sign in to 
http://open-mpi-mtt.appspot.com/.  When you go there, you get a "Sign in or 
register" link.  You click that and get to a Google Accounts login.  I used 
openmpi.ci...@gmail.com and its associated password, but then I'm bounced back 
to the "Sign in or register" link.

Only when I login as open...@gmail.com do I actually get beyond 
the "Sign in or register" link.

Does this mean that openmpi.ci...@gmail.com does not have login 
privlidges on the open-mpi-mtt appspot?  If so, can we add a better error 
message than this?  It's very confusing -- because you *are* apparently signing 
in to a google account properly, but then you just get the "Sign in or 
register" link again.
  

[ii] As I mentioned in previous mails current form of web-site suits 
administrating purpose mostly (to fit full multiuser access it should be 
provided additional
operations). So I knowingly limited admission for administrator only as 
"openmpi" to avoid additional questions in multiuser usage. 
  

  

In case you make a resolve to accept patch I am sending 
next steps should be done:

1. update application on server side using instruction 
in VBench_GDS_Setup.doc (topic 4 "Installation")
example: appcfg.py update /
2. change version on 
https://appengine.google.com/deployment?_id=open-mpi-mtt_id=1.337140739868725607
 from 1 to 2 (make default)
note: after this operation all users that attempt to 
submit data using previous scheme of authentication will get failure respond.
3. go to open-mpi-mtt and add new users with google 
account



It looks like this was all done already -- probably because I 
took so long to reply.

Thanks!

  



__ Information from ESET NOD32 Antivirus, version of virus 
signature database 4913 (20100303) __

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru


__ Information from ESET NOD32 Antivirus, version of virus 
signature database 4913 (20100303) __

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru




__ Information from ESET NOD32 Antivirus, version of virus signature 
database 4913 (20100303)