From f6c785fad06eb628f88c62bf0ba568e9fd2b14c4 Mon Sep 17 00:00:00 2001 From: j Date: Sat, 17 Jun 2023 03:13:16 +0200 Subject: [PATCH] Update page '6-16-2023 Cohort 1 Sync Notes' --- 6-16-2023 Cohort 1 Sync Notes.md | 65 ++++++++++++++++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 6-16-2023 Cohort 1 Sync Notes.md diff --git a/6-16-2023 Cohort 1 Sync Notes.md b/6-16-2023 Cohort 1 Sync Notes.md new file mode 100644 index 0000000..a5951d3 --- /dev/null +++ b/6-16-2023 Cohort 1 Sync Notes.md @@ -0,0 +1,65 @@ +1400h: Started + +Sloetjes is reporting that there's still problems accessing her container + +Karen got chromium installed via the playbook, and the script can attempt to execute, but can't run due to other failures. + +1427h: mentioned that `ansible-playbook basic_checks.yml --start-at-task "Start pricer container with systemd"` can be used to skip directly to a given play in a playbook. + +The playbook still won't reliably run the container if you run the playbook after it creates the container, so to troubleshoot I did + +``` +$ docker run -it dev /lib/systemd/systemd +Failed to mount tmpfs at /run: Operation not permitted +Failed to mount tmpfs at /run/lock: Operation not permitted +[!!!!!!] Failed to mount API filesystems. +Exiting PID 1... +``` + +There's a reference to the tmpfs mount permissions here: + +https://docs.ansible.com/ansible/latest/collections/community/docker/docker_container_module.html#parameter-mounts/tmpfs_mode + +We should probably consolidate all the ansible logs somewhere, so the most expeditious option seems to be Slack... + +We had a long discussion about the nature of feedback and emotions in the workplace + +Two concepts: + +1. Senior people do not complain, do not 怨, they get assignments and do the work. Emotion has no place in business. + +2. You cannot force emotions on other people, you can only give them an environment and idea which encourage certain emotions. Creating positive emotions is good for your reputation and ability to obtain resources. + +Sloetjes says that confident and competence and education help you understand people, their needs, and how to do work to obtain their respect. + +We discussed the idea of indirectly influencing others' behavior, and the importance of professionally providing an environment which encourages positive emotions. + +Examples of how either of these rules were broken were discussed, and the negative consequences: unreliability, inconsistency. + +Respect and money are both important for life, and + +* Do not tell people how they feel, because they feel how they feel. +* The best answer to a question you don't know is to say you don't know, and to promise a certain time that you'll come back with answer. +* Don't take emotion into your working environment, because it will indirectly influence others, and it's not what we want. +* We don't want that because someone will be influenced by it, and it may cause some consequences, like losing your job. +* If you lose your job, it may cause unemployment for your family, and it will cause problems for you to stay alive. +* + +* Telling other people that they're not doing something they probably should be doing is a perfectly reasonable thing to do in Western companies. +* +https://en.wikipedia.org/wiki/If_Japan_Can..._Why_Can%27t_We%3F + +https://www.youtube.com/watch?v=vcG_Pmt_Ny4 + +* Fixing things twice: TPS, + +* Sloetjes points out that the core statement of that news report, "the problem of productivity", had two parts: workers saying that they want work security and pay, and secondly that experts are saying that you need active participation for people who are really doing the job. + +* "Properly rewarding workers when they produce added amount of production." + +* We need to find the root cause initially, for further troubleshooting for the same issue. +* Back to the scriptmaking, if we make some errors or warnings, we need first to find what the [] state, and then to pick out the background or the causes for that warning, and change tools (for example, to try to find the reason why it's caused and try to fix it). + +@j TODO bring up a messaging bus + +* modify ansible.cfg to use a callback plugin that spits output to that bus