-
Notifications
You must be signed in to change notification settings - Fork 404
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[vote] rename IoT and yurt-device-controller: seeking suggestion for new names #1508
Comments
I have some confuse, i remember yurt-device-controller has device. deviceprofile and deviceservice CRDs, and this issue only talk about devce, what's about others? And i see the kind you provide it's all about management of iot, it has any other kind for iot? If it has, you can show us the details, so we can judge better. |
Below are the proposed names that come to my mind by now, just take them as a reference please: |
@JameKeal There may be some ambiguity here. yurt-device-controller is used for synchronizing three CRDs of device, deviceprofile, deviceservice. This issue actually involves two things, and I'll just add to that:
I hope my supplement can answer your questions. |
@Rui-Gan Because this crd will be used by controller to manage edge platform including the deployment, updates, and removal, etc. so i want to post a new name for CRD as following:
and the new name for yurt-device-controller, combing the comments from @JameKeal and @zzguang , I also want to post a new name as following:
|
Group: IoT, Kind: PlatformAdmin +1 |
Both polls are closed, the results are in, and the final plan is: refer: |
What would you like to be added:
The yurt-iot-manager project provides a CRD/controller for managing IoT devices. The IoT resource serves as an abstraction of a device management platform, enabling the deployment, updates, and removal of various device management platforms. However, the current naming convention for the resource's group and kind, "IoT" and "device" respectively, is ambiguous. This is because "device" is just one component of the broader IoT ecosystem. Therefore, it is recommended to rename the group and kind of this component to better reflect its purpose and scope.
The name of the yurt-device-controller component is also under review as it may cause confusion. The current name, "yurt-device-controller," includes "controller," which could be mistaken for the Kubernetes controller. However, it actually serves as a component that connects the cloud and edge management platforms. It can synchronize modifications of device properties in the cloud to the end devices, thereby affecting physical devices in the real world. Furthermore, the name "yurt-device-controller" is too generic and lacks specificity. Therefore, a new name is needed to better reflect its function and distinguish it from other components.
Several candidate names have been proposed for the IoT CRD group and kind, including:
Group: iot, Kind: IoTPlatform
Group: iot, Kind: Platform
Group: iot, Kind: LifecycleManager
Group: iot, Kind: IoTOpsManager
We invite suggestions for a new name for the yurt-device-controller. Please feel free to propose your favorite name or provide a suitable name in response to this issue.
The text was updated successfully, but these errors were encountered: