Simplify reference architecture and evolve scale docs

[spirosoik]

• Simplified architecture and splitting server from Monitoring + ES
• Update scale tables with Azure instances

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA cc11de6

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 273967b

[cwarnermm]

Great updates, @spirosoik! Thank you!

Small note: If we're changing /deploy/quick-start-evaluation.html to /deploy/try-mattermost.html, a page redirect will be needed via conf.py to ensure docs visitors with older links reach the correct destination.

[spirosoik]

Great updates, @spirosoik! Thank you!

Small note: If we're changing /deploy/quick-start-evaluation.html to /deploy/try-mattermost.html, a page redirect will be needed via conf.py to ensure docs visitors with older links reach the correct destination.

thanks @cwarnermm for pointing this out

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 353f09b

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA f3329fa

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 4a78cad

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 5e95e8a

[spirosoik]

@streamer45 @agnivade could you have a first look here, we did a couple of updates on reference architecture. What's not in scope for this PR and it's coming next:

• Elasticsearch architecture for enhanced and optimised search
• Monitoring etc.

@cwarnermm if everyone is ok we can merge this and I will continue with another PR for a few more improvements

[agnivade]

Will defer to @agarciamontoro

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 2b81562

[streamer45]

@spirosoik Are the Azure instance classes mapped on a best effort basis, or has your team conducted tests?

[spirosoik]

@spirosoik Are the Azure instance classes mapped on a best effort basis, or has your team conducted tests?

Correct @streamer45 it's best effort. me, @stafot and @angeloskyratzakos worked together on this.

[streamer45]

It looks good overall. I'll defer to Alejandro for a more fine-grained review. One question I have is about Azure Blob Storage: do we have native support for it and documentation on how to configure Mattermost with it?

[spirosoik]

It looks good overall. I'll defer to Alejandro for a more fine-grained review. One question I have is about Azure Blob Storage: do we have native support for it and documentation on how to configure Mattermost with it?

Not native. there's a work (PR here: mattermost/mattermost#30639) to start supporting this natively. Jesus plan to finalise tests/etc and have ready for review till Monday. Of course this needs extra testing/review etc.

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA 3d2cb24

[agarciamontoro]

Looks good! Thanks for updating the images, they now render perfectly :) I only have a couple of general suggestions:

• AWS data is backed by tests, but Azure is not. Should we add a disclaimer about that somewhere? Maybe something like "Every setup was tested to support the corresponding number of users in AWS exclusively. The specification of Azure instances in each architecture is extrapolated from the AWS data, and while it should generally work, it has not been proved".
• Non-blocking: if you don't know the Azure data is there, it's hard to find it: the way the tables are rendered, at least in my screen, make it seem that they only contain the AWS data. Unless one sees the horizontal scrollbar, the last column may be overlooked:
  

[spirosoik]

• AWS data is backed by tests, but Azure is not. Should we add a disclaimer about that somewhere? Maybe something like "Every setup was tested to support the corresponding number of users in AWS exclusively. The specification of Azure instances in each architecture is extrapolated from the AWS data, and while it should generally work, it has not been proved".

@cwarnermm I would like your input here.

Non-blocking: if you don't know the Azure data is there, it's hard to find it: the way the tables are rendered, at least in my screen, make it seem that they only contain the AWS data. Unless one sees the horizontal scrollbar, the last column may be overlooked:

There's an issue in multiple places with this.

[cwarnermm]

For the horizontal table scroll issue (and lack of Azure data visibility in said tables), I don't have an elegant fix, but I do recommend noting on the page that the user can scroll to see more information. example here

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA fd0b657

[spirosoik]

@cwarnermm fixed the scroll.

AWS data is backed by tests, but Azure is not. Should we add a disclaimer about that somewhere? Maybe something like "Every setup was tested to support the corresponding number of users in AWS exclusively. The specification of Azure instances in each architecture is extrapolated from the AWS data, and while it should generally work, it has not been proved".

@cwarnermm any good ideas how to incorporate this? I

[github-actions]

Newest code from mattermost has been published to preview environment for Git SHA e701e5a

[spirosoik]

@cwarnermm @agarciamontoro we can merge this to have the collateral and we can continue the improvements.

[agarciamontoro]

If this is very urgent, yes, we can merge. Otherwise, I'd appreciate discussing my proposal, I'm open to rewording what I suggested, it's in no way set in stone :)

[spirosoik]

we want to have the collateral public and we can add your proposal, as I have another multiple set of PRs and fixes.

[agarciamontoro]

Unblocking this, then :)

[cwarnermm]

Incorporated Azure testing feedback re: #7905