Stephan Kulow - 9:24 21.09.11 wrote:
Am Dienstag, 20. September 2011 schrieb Michal Hrusecky:
Vincent Untz - 15:34 11.09.11 wrote:
Hey,
Chatting with Klaas here about infrastructure issues, and I suggested
investigating OSUOSL: http://osuosl.org/ http://osuosl.org/services/hosting
Apparently, that's something we could discuss at the next team meeting.
Just few ideas before that meeting will happen. Whatever we will move there will be probably unable to use iChain setup for our services. So I Well, there is no moving away from ichain without moving away from provo datacenter. But if you host something somewhere else, you can still use login.opensuse.org to verify ichain passwords.
BTW: I find the reasons given for eliminating ichain strange - especially as we do not use ichain for connect, but login.opensuse.org
What is login.opensuse.org and how it works? Strange question, but is it documented somewhere? And isn't it just another iChain instance? AFAIK Connect is behind some proxy that provides authentication which is impossible (or at least hard) to do on servers hosted out of our internal network. So if we are going to move some services out of Provo, we need to move them away from iChain as well anyway. Also using some standard mean of authentication can be useful for people wanting to provide more services to members of openSUSE Community... Not speaking about possibility to use Connect login for example on sf.net ;-) -- Michal HRUSECKY SUSE LINUX, s.r.o openSUSE Boosters Team Lihovarska 1060/12 PGP 0xFED656F6 19000 Praha 9 mhrusecky[at]suse.cz Czech Republic http://michal.hrusecky.net http://www.suse.cz