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 OSPO landscape using landscape2, you can check it out at https://ospo.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
• Stop background automated processes that write to this repository (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 update the 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 😉

[anajsana]

Thanks for the heads up @tegioz ! I'll work on the DNS entries

[tegioz]

Awesome, thanks @anajsana!

Please let us know the hostnames you'd like to use (i.e. landscape.todogroup.org) so that we can prepare our end to listen on them before the DNS switch.

[anajsana]

hello @tegioz I'm working on the issue right now. The hostname would remain the same as it is now ➡️ landscape.todogroup.org.

FYI: landscape.todogroup.org DNS is managed through Netlify DNS (adding @AndreyKozlov1984 for Awareness)

[tegioz]

Ok, cool. Let us prepare the certificate for that domain. I'll get back to you with a CNAME entry that we'd need you to add for the verification.

[tegioz]

Could you add the following CNAME entries for the certificate validation @anajsana?

_3092379d4b4f7ad1d1e139a4f87e71e3.landscape.todogroup.org. -> _d9cd02efae823ecd2e9e31601ab83f66.mhbtsbpdnt.acm-validations.aws.
_805bf4746f975aaec3ed4878413164ec.l.todogroup.org. -> _26e33b3154f85ca82be915c632bd1cc9.mhbtsbpdnt.acm-validations.aws.

[tegioz]

Hi @anajsana 👋

This is just a friendly ping to check how the addition of the CNAME entries was going 🙂

[anajsana]

Hello @tegioz sorry for the late response. I've just added the CNAME entries in TODO's Netlify DNS records 👍

[tegioz]

Awesome! Our end is now ready to serve the landscape on landscape.todogroup.org.

You can update the DNS record whenever you are ready 🙂

CNAME `landscape.todogroup.org` -> `d29xupvrdvym8m.cloudfront.net`

It'd be great if you could also update the embed views from the previous landscape (i.e. like this one). It works slightly different now, but it should be easy to migrate using the embed configurator (before the DNS switch available at: https://ospo.landscape2.io/embed-setup, after at https://landscape.todogroup.org/embed-setup).

Please ping me if you have any question!

[anajsana]

sorry for the slow reply on this @tegioz I've added the new CNAME record provided in the DNS record.

Should the new landscape view appear soon once these additions are applied or is there anything else I should take care? 🙂

[tegioz]

No worries, thanks for taking care of this @anajsana!

That should be it. I can see the new one already (it may take a few minutes to be available everywhere as there could still be some DNS entries cached).

We'll help you with the rest of the tasks in this issue soon! 🙂

[anajsana]

Thank you! I can see changes are live in the OSPO landscape url now 🙌

[tegioz]

Hi @anajsana!

Quick summary of the pending tasks:

• Stop background automated processes that write to this repository (CNCF bot)

Could you please stop any background processes related to v1 for this landscape @AndreyKozlov1984? Thanks!

• Unlink this repository from Netlify

This landscape doesn't seem to be in the Netlify account I've access to. Could you or @AndreyKozlov1984 unlink the landscape from this repository on Netlify?

• Update README file and clean up some files no longer needed in this repository

Partially done in #201. All files that are no longer needed have been removed.

The README file still needs to be updated as some information on it does no longer apply. We can do this for you starting off the new version in the CNCF landscape repository (or you can update it yourself if you prefer, up to you).

• Setup the landscape2-validate-action to validate the landscape.yml file on PRs (optional)

Done in #201.

You'll notice that as part of #201 I've removed the guide.md. This is not a mistake 😇 The guide file for this repository lives at the moment at the landscape2-sites repository. Eventually we'll move it to this repo, but if you need to make any changes in the meantime, feel free to submit a PR on that repository.

I think this is it! You can continue adding entries to the landscape as usual by updating the landscape.yaml file 🙂

[tegioz]

I've just noticed that l.todogroup.org isn't redirecting to landscape.todogroup.org. You can either setup that redirection or update the l.todogroup.org to point to the same destination I provided for landscape.todogroup.org @anajsana.

I've just created a PR to update the README file and remove the parts that are no longer relevant in v2. As soon as it's merged and the redirection done I think we can consider the migration complete and close this issue 🙂