Perfect answer ! As I have the Sync 1.1 Apache <-> Mod_wsgi <-> server-core <-> postgreSQL working, I'm doing a documentation then I'll work on 1.5 and dispatch of the services, then documentation again (!).
Thanks Ryan ! Robin Aleman Apprentice engineer - Software integration Customer Integration & Support EQUANT France - Sophia Antipolis +00 33 4 92 96 64 48 [email protected] -----Original Message----- From: Ryan Kelly [mailto:[email protected]] Sent: Friday, July 04, 2014 01:01 To: ALEMAN Robin SCE/ID ITS; [email protected] Subject: Re: sync architecture diagram On 3/07/2014 10:19 PM, [email protected] wrote: > FYI : discussion about the Sync Self hosted architecture. > > > @Ryan : > " What we call "server-code" is a low-level utility library with components > that are shared between reg, storage, etc." > > You lost me :p Ugh, typo: I mean "server-core" in the above, not "server-code"... > For me there is a main server, the "server-full", where every services, sync > needs, are included : Reg, Storage, ... I don't seen where I can "split" the > services between servers. > Maybe I've miss something in the documentation but for me, the compilation > /setup don't leave any choice : compile then setup then run the server. Right, the whole point of server-full is to package up all the different parts into a single server so that it's easy to install and run. We don't run server-full in production at mozilla. We run each of reg, storage, etc as a separate service. This is not included in the self-hosting documentation because almost no-one needs it - AFAICT you would be the first :-) You can checkout each of the servers individually: http://hg.mozilla.org/services/server-reg http://hg.mozilla.org/services/server-storage http://hg.mozilla.org/services/server-key-exchange Each should `make build` in much the same way as the server-full package, and should have a .ini configuration file to run it as a standalone component. Ryan > Robin Aleman > Apprentice engineer - Software integration Customer Integration & > Support EQUANT France - Sophia Antipolis > +00 33 4 92 96 64 48 > [email protected] > > -----Original Message----- > From: Ryan Kelly [mailto:[email protected]] > Sent: Thursday, July 03, 2014 06:38 > To: ALEMAN Robin SCE/ID ITS > Subject: Re: sync architecture diagram > > On 2/07/2014 6:14 PM, [email protected] wrote: >> Thanks for the comment. >> >> I'm working on 1.1 sync because of Fennec incompatibility (for now) with >> custom sync server 1.5. but if I can do the same for 1.5 it's always good >> for the next step when fennec will be ready. > > Hopefully this will be ready soon - I see you got some replies in the other > thread along these lines. > >> About to run each service on different server, I don't see anything about >> it in documentation. > > Indeed, it's not documented anywhere because it only really makes sense for > very large-scale deployments. > >> From my point of view, the Server-core has module compiled in and >> they all work within it. (my schema show this : Server core with >> module within it : storage, reg, easy setup) > > So I realized this is not quite right. > > Terminology-wise, what you have labelled "server-core" is more accurately > described as "server-full", which is a top-level python package containing > the various components. > > What we call "server-code" is a low-level utility library with components > that are shared between reg, storage, etc. > > Also, the self-hosting setup does not currently include an easy-setup server. > Unfortunately I don't think there is any documentation on how to do this. > You would have to: > > 1) Run your own instance of this server: > http://hg.mozilla.org/services/server-key-exchange > > 2) Use about:config in firefox to change the URL under > "https://setup.services.mozilla.com/"; > >> Maybe could you point me to the right direction ? > > You almost certainly don't need to do this unless you're running at a scale > similar to Mozilla's production deployment. I will follow up in the public > thread on sync-dev. > > > Cheers, > > Ryan > > ______________________________________________________________________ > ___________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc pas etre diffuses, > exploites ou copies sans autorisation. Si vous avez recu ce message > par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les > pieces jointes. Les messages electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or > privileged information that may be protected by law; they should not be > distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you. _______________________________________________ Sync-dev mailing list [email protected] https://mail.mozilla.org/listinfo/sync-dev
