Farmers/Users Communication Channel #34

Closed
opened 2024-04-12 19:18:59 +00:00 by mik-tf · 2 comments
Owner

Situation

Farmers don't have ways to communicate with users, e.g. maintenance.

Proposition

Develop a communication channel between farmers and users. Can be done via the Dashboard or via email.

  1. Communication Channel: Farmers and Users Contact Info
    1. There must be efficient communication channels between farmers and users for maintenance and service reasons.
      1. Farmers should have users info (e.g. email) to be able to send maintenance notifications, etc.
      2. Users/TFGrid should be able to contact farmers (email and telephone)
  2. System for farmers to announce maintenance window without loss of reputation or the like
    1. A mechanism where farmers could go through an announcement procedure, that downtime is expected on a node/farm due to maintenance or upgrade, without loosing any reputation or rewards

Automated + Manual Modes

With some function automated, e.g. maintenance parameter for farmers that will automatically send alerts to users (e.g. email, or displayed on the dashboard of the user) when farmers set a maintenance window.

And also "manual" communication, we also have the option for farmers and users to communicate via email, as a simple communication channel

Examples with Farmers' Maintenance Schedule

  • Planned downtime
    • A maintenance button/setting on the Dashboard, where you can state a downtime for your node (scheduled).
    • The system behind it automatically notifies the user(s) via a dashboard message and/or an email with the maintenance period.
  • Unplanned downtime
    • Farmer can send a message with the expected downtime (e.g. one node's SSD failed and you need 2 days to get a replacement)

Benefit of communication channel

This would offer farmers

  1. the ability to maintain and communicate a regular maintenance schedule
  2. notify users of unexpected outage
  3. perform upgrades in coordination with the users to minimize disruption.

This would bring users

  1. the ability to communicate further needs for additional resources I.e. happy customer wants another node.
  2. request specific upgrades to a nodes/connection/ more ips then are currently available.
  3. report issues, unexpected shutdowns

Reference

This has been discussed in many different ways, especially this well-explained tf forum post and in the 3.14 forum post.

Thanks to all the community members who participated in this discussion and other related discussions.

Note

Can be moved to 3.15 or 4.0 project if too complex for a short period of time.

## Situation Farmers don't have ways to communicate with users, e.g. maintenance. ## Proposition Develop a communication channel between farmers and users. Can be done via the Dashboard or via email. 1. Communication Channel: Farmers and Users Contact Info 1. There must be efficient communication channels between farmers and users for maintenance and service reasons. 1. Farmers should have users info (e.g. email) to be able to send maintenance notifications, etc. 2. Users/TFGrid should be able to contact farmers (email and telephone) 1. System for farmers to announce maintenance window without loss of reputation or the like 1. A mechanism where farmers could go through an announcement procedure, that downtime is expected on a node/farm due to maintenance or upgrade, without loosing any reputation or rewards ## Automated + Manual Modes With some function automated, e.g. maintenance parameter for farmers that will automatically send alerts to users (e.g. email, or displayed on the dashboard of the user) when farmers set a maintenance window. And also "manual" communication, we also have the option for farmers and users to communicate via email, as a simple communication channel ### Examples with Farmers' Maintenance Schedule - Planned downtime - A maintenance button/setting on the Dashboard, where you can state a downtime for your node (scheduled). - The system behind it automatically notifies the user(s) via a dashboard message and/or an email with the maintenance period. - Unplanned downtime - Farmer can send a message with the expected downtime (e.g. one node's SSD failed and you need 2 days to get a replacement) ## Benefit of communication channel This would offer farmers 1. the ability to maintain and communicate a regular maintenance schedule 2. notify users of unexpected outage 3. perform upgrades in coordination with the users to minimize disruption. This would bring users 1. the ability to communicate further needs for additional resources I.e. happy customer wants another node. 2. request specific upgrades to a nodes/connection/ more ips then are currently available. 3. report issues, unexpected shutdowns ## Reference This has been discussed in many different ways, especially this well-explained [tf forum post](https://forum.threefold.io/t/feedback-on-our-tfgrid-3-14/4276/10) and in the [3.14 forum post](https://forum.threefold.io/t/feedback-on-our-tfgrid-3-14/4276/10). Thanks to all the community members who participated in this discussion and other related discussions. ## Note Can be moved to 3.15 or 4.0 project if too complex for a short period of time.
mik-tf added this to the (deleted) project 2024-04-12 19:18:59 +00:00
Owner
  • we need a feature in TFChain which allows user to set node in maintenance mode, so it will not be used for further deployment, specify a window, farming needs to look at it
- we need a feature in TFChain which allows user to set node in maintenance mode, so it will not be used for further deployment, specify a window, farming needs to look at it
despiegk modified the project from (deleted) to (deleted) 2024-04-23 11:44:42 +00:00
despiegk modified the project from (deleted) to tfgrid_3_14 2024-05-22 07:56:44 +00:00
despiegk removed this from the tfgrid_3_14 project 2024-05-22 07:57:23 +00:00
Author
Owner

Moved. See above.

Moved. See above.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: tfgrid/circle_engineering#34
No description provided.