improve the user scenarios in website

[haoqing0110]

We now have some user scenarios under https://open-cluster-management.io/scenarios/ , which may not be enough.

And we have below feedback from users, which can help improve the user scenarios

• I want to know how OCM is used in the real world.
• Can OCM dispatch jobs for multi-cluster env? not clear about what can it do and how.
• I need some detailed usage of the core functions (such as a blog for that).
• To deploy an application on multiple clusters, I would want an easy approach.
• How to integrate with the app or other middleware? e.g. kubeflow

Create this issue to further discuss this topic.
More ideas and suggestions are welcomed to comment on this issue.

---

Subtasks:

• A brief walk-through of how to write an addon based on addon-framework. #32
• Create a solution scenario on how is the placement used in OCM #33
  • How user can use placement to schedule their workload. #58
  • How user can extend placement scheduling. #59
  • How to use placement and other opensource tools to do workload or storage disaster recovery. #60
  • How to do cluster maintainence and its implementation on placement #61
• How do I run a multicluster service mesh with ocm #34
• How do I run argoCD with OCM #35
• Add Access managed cluster solution. #44

[haoqing0110]

/assign @elgnay @zhiweiyin318 @morvencao @haoqing0110

[haoqing0110]

/assign @xuezhaojun

[xuezhaojun]

Please add subtask: #44

[xuezhaojun]

@qiujian16 Should this #44 document in the repo https://github.com/open-cluster-management-io/OCM 's solutions part or in the repo https://github.com/open-cluster-management-io/open-cluster-management-io.github.io? or both?

[xuezhaojun]

@qiujian16 Should this #44 document in the repo https://github.com/open-cluster-management-io/OCM 's solutions part or in the repo https://github.com/open-cluster-management-io/open-cluster-management-io.github.io? or both?

It seems like this task is more suitable for OCM repo.

[github-actions]

This issue is stale because it has been open for 120 days with no activity. After 14 days of inactivity, it will be closed. Remove the stable label to prevent this issue from being closed.

[haoqing0110]

Close as all sub-tasks are done.