Deploy the federation based on bloxes

The config sample: https://snippet.vraiment.top/?fe680454ba789b44#HTziiZNPvTFCMx5XxmYSbae38HmeugA2hMTf5U1GVbG1

Need to:

1. write the new config for all blocks
2. replace standalone instances with a server:// for all federation:// endpoints
3. implement the global federation mecanism
4. keep skills pointing to the community URL but change it for a federation including community for the others
5. update all existing configuration

added feature label

mentioned in issue management/startinblox-feature-requests#268 (closed)

mentioned in issue #209

changed the description

@jbpasquier Adapting the default configuration of all bloxes I see that resources and polls haven't changed much: https://git.startinblox.com/applications/hubl/tree/feature/3b-improvements#resources

I found that particularly strange for circles and upload endpoints...

Forgot to change them, I'll update asap.

Still, parameters looks good.

For the moment I updated them on my side wihtout federation endpoints. I'll change it later.

marked the checklist item write the new config for all blocks as completed

@jbpasquier When deploying standalone apps I disable communities directory as said in the doc, right ?

No need to override the federation endpoints ?

I did the changes on test3 it gives a more complicated config: 4ddf7e79

It seems to work. I'll wait validation before moving it to all standalone...

I did the changes on test3 it gives a more complicated config: 4ddf7e79

Looks good

When deploying standalone apps I disable communities directory as said in the doc, right ? No need to override the federation endpoints ?

There should be nothing more, yes.

marked the checklist item replace standalone instances with a server:// for all federation:// endpoints as completed

changed the description

mentioned in issue #225 (closed)

marked the checklist item implement the global federation mecanism as completed

marked the checklist item keep skills pointing to the community URL but change it for a federation including community for the others as completed

marked the checklist item keep skills pointing to the community URL but change it for a federation including community for the others as incomplete

@jbpasquier I prepared all the staging instances with the new config. Their all standalone. It took me forever to port the new config.

We should be ok to deploy stagings everywhere. I also updated the secoiadeal-stg platform with those last changes and it works.

@jbpasquier On the skillset topic. I'm testing it on happy dev staging instance and it's not clear what I should do.

I tried to federate the bloxes using skills with stg1 and it works. But I don't want to federate directory or job-offer with hubl. I just want to benefit from the hubl skillset in those bloxes with the ability to add my owns. And skills endpoint doesn't support federation.

I prepared the deployment of all Happy Dev instances. For example: https://git.startinblox.com/infra/platform/blob/feature/blox_by_blox/inventory/prd/hdparis.yml

I noticed the direct messages are not working on the staging instances deployed with this feature (HD and Secoiadeal).

- type: directory
  parameters:
    - rangeSkills: server://sources/skills/

And ensure to have https://api.community.hubl.world/skills/ and your federation on LDP Sources with the key skills on DjangoLDP. Notice that the old federate command will do it for you.

marked the checklist item keep skills pointing to the community URL but change it for a federation including community for the others as completed

marked the checklist item update all existing configuration as completed

marked the checklist item update all existing configuration as incomplete

closed