Experiment for large-scale operation of LibreOffice Online
•Télécharger en tant que ODP, PDF•
2 j'aime•234 vues
It is a slide released in the content of "Experiment for large-scale operation of LibreOffice Online". 日本語： アルバニア ティラナで開催された、LibreOffice Conferenceで "Experiment for large-scale operation of LibreOffice Online"のタイトルで発表した内容です。
Recommandé
Recommandé
Contenu connexe
Plus de iCRAFT Corp. (アイクラフト株式会社)
Plus de iCRAFT Corp. (アイクラフト株式会社) (20)
Dernier
Dernier (20)
Experiment for large-scale operation of LibreOffice Online
- 1. Experiment for large-scale operation of LibreOffice Online Masaki Murakami Shinji Enoki librepc@icraft.jp
- 2. Agenda • Who am I? • abstract • Uses in Many Users • Testing enviroment • Solution(?) • LOOL and nextcloud in Japan
- 3. Who am I? Masaki Murakami （村上正記） ● ICRAFT Corp.( アイクラフト株式会社 ) ● Tasks – Server administration and network administration – Marketing of “LibreBOX” ● Integrated server of nextcloud and LOOL – New business deveropment
- 4. abstract ● LibreOffice Online has improved performance, etc., than before, but there are still things you need to consider when linking with nextcloud, especially when you use it in an environment that many users use. ● This time we will announce the knowledge gained through experiments using the environment constructed so far.
- 5. 本題
- 6. Uses in Many Users Improve software performance Load balancing on multiple servers This session I focus on load balancing
- 7. Load balancing using a load balancer Testing enviroment LAN cloud Infrastructure Calling Service Responce nextcloud LOOL Servar1 LOOL Server2 LB
- 8. DEMO
- 9. Results ・ session is evenly distributed among two servers ・ Load balancing at round robin fails. ・ It is necessary to have a mechanism for load balancing so that one server corresponds to one file. ↓ ・ Should I have a mechanism to hold sessions for a specific server?
- 10. Solution(?) ・ Load balancer with TLS termination proxy and Cookie based load balancing ↓ ・ Fail ・ The reverse proxy used in LOOL may not be compatible with HTTPS communication.
- 11. Solution(?) ・ LOOL uses Websocket to manage sessions. ・ It is necessary to adopt a load balancer that supports Websocket ex:AWS Elastic Load Balancing ex:F5 Big-IP To be verified after construction of the environment
- 12. LOOL and nextcloud in Japan ・nextcloud and NEC tied up Ex:Japan to add millions of new nodes to federated Nextcloud network https://nextcloud.com/press/pr20180825-2/ - Since 1 Gbps broadband is connecting to many SOHO and medium offices in Japan, there is no performance problem at the present time for each household and small business to use. · By further distributing processing technology etc., performance will be improved if high load processing is load-balanced by these servers. · If LOOL is introduced to these servers, introduction of LibreOffice in Japan will accelerate.
- 13. Thanks!!
Notes de l'éditeur
- My name is Masaki Murakami,from Japan,Kobe. Today’s my presentation is “Experiment for large-scale operation of LibreOffice Online”. I am usually Japanese so I am unfamiliar with the presentation in English. I think that it is irritating, please keep in touch with the end.
- Today’s agenda is here.
- “Who am I” ということで、自己紹介をさせていただきます。It’s selfintroduce time.Because it is impeccable, I sometimes announce it while mixing Japanese.So,the content that I am speaking now is talking about the result translated by Google translation as it is. I am Masaki Murakami. I am working at iCRAFT in Kobe, Japan. Now, Kobe is very famous thanks for this person.My job is to manage servers and networks in a data center, which is mainly operated by iCRAFT. In addition, since we have released a product called "LibreBOX" of an appliance integrating nextcloud and LOOL, we are marketing that product and developing new business.
- iCRAFT has focused on LOOL since 2017 and has been conducting verification within iCRAFT. It is from this year that I participated in the business related to LOOL, but various improvements seem to be progressing even after I became involved. However, I think there are still many problems for LOOL to replace cloud services such as Google and Microsoft Office Online. Today, I will announce the results verified by iCRAFT to use LOOL in many people.
- I think that there are times when performance is not good as a problem to overcome in order to use LOOL in many people. This is as announced by CODE Website. I think there are two ways to reach the problem. One is to improve the performance of the software itself, and the other is to load balance by many servers. This time we will focus on load balancing, which is the approach iCRAFT has been working on. Why not talk about software performance is because I am not software deveroper and it’s too hard to read and improvement source code.
- This slide is setting an environment for this time. Prepare the nextcloud server in the iCRAFT company and build two LOOL virtual machines on the cloud service. The load balancer is provided by the cloud service and sorts sessions in a round robin fashion. The LOOL server follows Apache's official procedure when connecting Collabora's nextcloud and CODE and run Apache as a reverse proxy for each.
- I will try a demonstration at once.
- Sessions manipulating one file were evenly distributed among the two servers. I think that this is because the load balancer does not have the function of fixedly sorting a specific session to a specific server and evenly distributed it in round robin. By thinking differently, I thought that if you had a specific key for the session, by solving the server fixedly by that, it would solve it.
- First of all, I thought that if you have cookies in a session, you can distribute the load based on that. This is because many load balancers have the ability to maintain sessions on a cookie basis. However, in order to do that, it was necessary to decrypt TLS communication with a load balancer. Therefore, we placed a server certificate on the load balancer and verified that we can communicate. But this test failed. If you cancel the TLS communication with the load balancer, I think that it is because it can not be TLS communication again and it becomes HTTP communication again. In loolwsd.xml I thought that there was a setting that can be set to not use HTTPS communication, but it seems that the setting method and contents were different.
- So I thought that LOOL is using Websocket for maintaining sessions. That means that the load balancer side also needed a mechanism to correctly interpret the Websocket communication and distribute the load. Although the presentation ended up reaching here, as for the load balancer considering Wesocket, there is AWS Elastic Load Balancing etc. in the cloud service, etc. Also since there is F5 Big-IP even in the load balancer installed on-premises , I think that load balancing will be possible with this method. However, since these load balancers are expensive, I do not know if it is really a correct solution to use this.
- There is one background to do such a story this time. This is the move to enter nextcloud as a standard in a server incorporating broadband router function developed by NEC in collaboration with Japanese IT vendor NEC and nextcloud this year. A company in Japan who did this intermediation plans to make it possible to incorporate various server applications into this server / router and sell it to small business. As you know, in Japan, infrastructure capable of 1 Gbps optical broadband internet is also set up for SMEs and general households, so if LOOL is installed in this environment, it is possible to collaborate freely edit.You will be able to set up an environment where you can do it. I think that this will eventually become a catalyst for the spread of LibreOffice in Japan. I cannot support to editing code and I will contribute to infrastructures test and LOOL’s translating.
- Thank you Very mach !