What's the meaning of the "cluster_config" ?

[NKcqx]

          Now that we separate `ray.init` from `fed.init`,  there's no way to reach the cluster-level information, since each `fed.init` starts and only starts a job session.

Unless there's a global actor (or service job) that can break the job isolation and filter each job's tasks' invalid param type.

Originally posted by @NKcqx in #140 (comment)

[NKcqx]

          If we don't have the cluster config, why we not just use `config`? The question that we should answer before it getting finalized is whether we need the cluster config in the future at high level.

Originally posted by @jovany-wang in #140 (comment)

[NKcqx]

Firstly, the fact is that user can't configure the Ray cluster in a rayfed job, since the initialization of Ray cluster has separated from RayFed, i.e. fed.init.
I think the original semantic of "cluster_config" is "configure the cluster used in this job", in which case, it's a job-level config but containing all the non-business configurations.

[jovany-wang]

I think the original semantic of "cluster_config" is "configure the cluster used in this job", in which case, it's a job-level config but containing all the non-business configurations.

It sounds reasonable. Let's use the config key word as the job level configurations parameter name.

[jovany-wang]

What's the status of this PR?