Closed quantranhong1999 closed 2 years ago
I did not succeed deploy the TMail with AMQP synchronization change on preprod (have some issues with helm james).
Your mean is to create a new rabbitmq? if Yes, It is unnecessary, we can re-use a current rabbitmq (for tmail)
Let's say we let this be demoed when we plug the real contact app?
IMO, not need, we can use rabbitmq webadmin, and try to publish sample messages, then follow new contact has been indexed
Your mean is to create a new rabbitmq? if Yes, It is unnecessary, we can re-use a current rabbitmq (for tmail)
The problem as I said is about helm, not related to rabbitmq yet (I tried to point to the same rabbitmq anyway).
IMO, not need, we can use rabbitmq webadmin, and try to publish sample messages, then follow new contact has been indexed
Can you help with a demo locally?
Can you help with a demo locally?
Of course, let me record a video
Users is already:
Rabbitmq publisher (publishing AQMP messages to contact synchronization)
Add a new contact AQMP-message
{
"type": "addition",
"scope": "user",
"owner" : "bob@domain.tld",
"entry": {
"address": "alice@domain.tld",
"firstname": "Alice",
"surname": "Watson"
}
}
Remove a contact AQMP-message
{
"type": "removal",
"scope": "user",
"owner" : "bob@domain.tld",
"entry": {
"address": "alice@domain.tld",
"firstname": "Bob",
"surname": "Parker"
}
}
@quantranhong1999 why you didn't ask me then? You know I'm doing ok with Helm, I wrote the james chart one :P
Seeing your error my guess is it's like last time, Duc added some secrets manually with Lens quicky dirty, and it clashes with Helm now. I will take a look :)
After rewatching your demo @quantranhong1999 , don't we have a problem with the limit? we put a default limit to 256 but we return just 10 results max right? (as we don't want any scrolled search in es here).
Maybe we should change the default max limit to 10 then?
we put a default limit to 256 but we return just 10 results max right?
I think this solves your concern: https://github.com/linagora/tmail-backend/commit/5708874fa4e8266884c485abd96e3ee34fef3d00
(as we don't want any scrolled search in es here)
I checked again, we are doing scroll search for web admin listing routes, not related to auto-complete JMAP.
What we will demo:
Contact auto-completion feature with LDAP synchronization
Contact auto-completion feature with AMQP synchronization (optional)
Improved IMAP Performance
Improved IMAP Performance
Then
We can take TMail 0.5.0 IMAP performance as a comparison milestone (just relatively cause diff simulation and pods number).
Now
Our IMAP can handle up to 2000 req/s with a good response time.
We can say more about the performance/metric tools if people are interested.
Contact auto-completion feature with LDAP synchronization
Demo Script
parisnanterre.fr
domain contacts => return emptyVideo
https://user-images.githubusercontent.com/55171818/166896644-54cdc846-a6c0-4f43-abe1-876ffd365d69.mp4
Linshare
Contact auto-completion feature with AMQP synchronization
I did not succeed deploy the TMail with AMQP synchronization change on preprod (have some issues with helm james). @ducnm0711 is busy and will not be able to help solving this soon. Let's say we let this be demoed when we plug the real contact app? Otherwise another effort on this is welcome :')