federatedai / fate-community Goto Github PK

Gennlife (Beijing) Technology Co.,Ltd.

Gennlife has passed the preliminary review and completed the assessment. TSC board members are requested to vote based on the assessment result, either "agree" or "disagree."
If more than half of the votes are favored, Gennlife will officially become a FATE community organization member.

I created a PR against the DOC-CHN 25 days ago. I found the oldest opened PR was created on Aug 24, 2020. And the last active PR was on Sep 20.

在fate-1.7.1和fate-1.7.2版本中：
1、guest方和host方的属性列名称不相同时，执行特定列的分箱操作失败，特征择选操作被卡住，且持续运行，如选择X0、X1列；
2、guest方和host方的属性列名称相同时，分箱操作选择特定列，如X0、X1列，则分箱操作和特征择选操作能顺利执行；

Describe the solution you'd like
Currently, we have deployment approaches like KubeFATE, and Ansible for the FATE cluster on one site. But we lack the federation level provision and management solution. The goal is to orchestrate the provisioning of multiple sites to form a globally secure and well-governed a federation.

Furthermore, current deployment solutions (including KubeFATE and Ansible) are CLI-based, which is still an overstretched requirement for personnel with only infrastructure knowledge. An easy-to-use GUI deployment solution is needed.

Describe alternatives you've considered
A Federated Lifecycle Manager (federation level lifecycle management system) is needed. The system should be easy to use for large-scale FATE cluster provisioning and management.

We can create a new repo for the Federated Lifecycle Manager (FedLCM) for the development of this feature.

Regarding the vote on the addition of 3 new organization members, the following 3 organization members have passed the preliminary review and completed the assessment. TSC board members are requested to vote based on the assessment results. Please vote "agree" or "disagree". If the number of "agree" votes exceeds half, they will officially become FATE community organization members.

The voting format is as follows (in no particular order):
China Reinsurance（Group）Corporation（**再保险）: agree or disagree.
SPD Bank（浦发银行）： agree or disagree.
Seceum Tech（神谱科技）： agree or disagree.

To host the documents and specifications of SIG InterOp, we plan to create a new repo for this purpose. The implementation code is still saved in the FATE main repo.

ByteDance has passed the preliminary review and completed the assessment. TSC board members are requested to vote based on the assessment result, either "agree" or "disagree."
If more than half of the votes are favored, ByteDance will officially become a FATE community organization member.

Regarding the vote on the addition of 6 new organization members, the following 6 organization members have passed the preliminary review and completed the assessment. TSC board members are requested to vote based on the assessment results. Please vote "agree" or "disagree". If the number of "agree" votes exceeds half, they will officially become FATE community organization members.

The voting format is as follows (in no particular order):
Shandong University: agree or disagree.
Shenzhen Weiyan Technology Co., Ltd.: agree or disagree
Hi-Think Technology, Corp: agree or disagree
Ma Shang Consumer Finance Co., Ltd.: agree or disagree
FinVolution Group: agree or disagree
GRG Information Security Technology Co., Ltd.: agree or disagree

Could you please name some operators to be implemented in the library?

What is FATE-Builder?

1. FATE has many release packages, such as Standalone, AllinOne, AnsibleFATE, etc. Before FATE 1.8, these packages were built manually. It requires the maintainer to use multiple scripts to build each package.
2. On FATE 1.8, all release packages were built automatically by FATE-Builder with just one command. And it is CI friendly, it can be integrated into GitHub CI for automatic releasing.

Why use a separate repository?

1. FATE-Builder includes some templates for generating packages, e.g. AnsibleFATE. Normal users does not need these templates.
2. FATE-Builder does not require a specific FATE version. Currently, it supports FATE 1.7+ and has been fully tested on FATE 1.8.
3. FATE-Builder does not use any script from FATE repository. It can clone, pull, build FATE and all submodules (eggroll, fateflow and fateboard), so it can run independently.

We can create a new repo for FATE-Bulder for the development of this feature.