Migration to landscape2

[tegioz]

Hi! 👋

We've been working on a new version of the landscape generating software, landscape2. This new version relies on the same landscape.yml file as the main data source, so nothing changes regarding adding or updating entries in the landscape.

The CNCF landscape has already been successfully migrated to landscape2, and we'd like to start migrating more landscapes 🙂

We are already building the LF AI & DATA landscape using landscape2, you can check it out at https://lfai.landscape2.io/. It'd be great if you could give it a try when you have a chance and, whenever you are ready, we can proceed with the migration.

The process is very simple and would involve the following steps:

• [ ] Add/update some DNS entries [1]
• [ ] Stop background automated processes that write to this repository (i.e. CNCF bot)
• [ ] Unlink this repository from Netlify
• [ ] Update README file and clean up some files no longer needed in this repository
• [ ] Setup the landscape2-validate-action to validate the landscape.yml file on PRs (optional)

We can take care of the last 4 points, you'd only need to add/update some DNS entries.

Landscape2 supports embedding a view with items in a category/subcategory in another website, but it works slightly different than landscape1. If parts of this landscape are embedded using this mechanism on other websites, we'd appreciate if you could let them know about how it works now.

Please ping me if you have any question 😉

[1] We’d need to know the hostnames you'd like to use to prepare our end to listen on them before switching the DNS (i.e. landscape.lfai.foundation). Once we are ready we'll provide you with the destination for the DNS entries so that you can update them.

[tegioz]

Could you please create the following CNAME entries? We need them to prove that we are allowed to setup a certificate for those subdomains.

_6b19a9dfa414c9a7c8ceee3064f0d871.landscape.lfai.foundation. -> _fdc6548b91ac9d56aee1a1baf11889c3.mhbtsbpdnt.acm-validations.aws.
_ef6fbaebd04f81c3dc5b0fdee6a1b13d.l.lfai.foundation. -> _4cb360175e9ae7da1a1290fdc17e9fe7.mhbtsbpdnt.acm-validations.aws.

Once they are ready I'll update the list of hostnames and will share with you the new destination of the existing subdomains.

Thanks!

[ibrahimhaddad]

@tegioz Thanks Sergio, I submitted an internal ticket for the CNAME entries. I will drop you a note once this is done. Thx.

[ibrahimhaddad]

@tegioz the records have been added. Thanks.

[tegioz]

Thanks @ibrahimhaddad, but they don't seem to be ready yet:

% host -t cname _6b19a9dfa414c9a7c8ceee3064f0d871.landscape.lfai.foundation.
Host _6b19a9dfa414c9a7c8ceee3064f0d871.landscape.lfai.foundation. not found: 3(NXDOMAIN)
% host -t cname _ef6fbaebd04f81c3dc5b0fdee6a1b13d.l.lfai.foundation.
Host _ef6fbaebd04f81c3dc5b0fdee6a1b13d.l.lfai.foundation. not found: 3(NXDOMAIN)

[ibrahimhaddad]

Give it some more time? It's done. It may be caching or it needs some time to propagate. @tegioz

[tegioz]

Sure, no problem, but it's a bit weird (still not ready). It's a new entry so it shouldn't be cached.

[ibrahimhaddad]

@tegioz any update on this? Thanks.

[tegioz]

The DNS entries are not ready yet @ibrahimhaddad. You can check them yourself with the command I shared a few comments above. New entries are usually available pretty quick, so I suspect something went wrong when they were added.

Please let me know when they're ready and we'll continue with the process 🙂