AI usage disclaimer updates

Content/20240426135219-container.org

@@ -10,15 +10,17 @@ See [[id:af4d4e9f-3fd3-4718-ba73-e6af4f57c29c][Docker]],[[id:cda61bfd-86b7-481d-
 ** Prerequisites
  - isolated execution environments leveraging two key kernel features: [[id:a4ca9065-0613-44f8-8ca5-693dfc7704ae][cgroups]] and [[id:92f509f7-5b8f-4beb-a66c-7890e79c84a3][namespaces]].
  - cgroups (control groups) govern and isolate resource usage for processes.
-   - Processes are organized hierarchically into cgroups.
-   - Each cgroup enforces limits on resources like CPU time, memory, network bandwidth, and I/O.
+   - [[id:8afb9d29-252b-4f17-ad42-700444fe4464][Processes]] are organized hierarchically into cgroups.
+   - Each cgroup enforces limits on resources like CPU time, memory, [[id:a4e712e1-a233-4173-91fa-4e145bd68769][network]] bandwidth, and I/O.
  - Namespaces provide process isolation by creating virtual views of system resources.
 ** Collation
 Containers utilize both cgroups and namespaces to create isolated environments.
 1. Namespaces isolate: Processes, network resources, mount points, etc., creating the perception of a separate system.
 2. cgroups limit and manage:  Resource utilization within these isolated namespaces, ensuring predictable behavior.
 ** Caveats:
-- Container security relies heavily on the Linux kernel. Kernel vulnerabilities can impact container isolation.
-- While providing strong isolation, containers are not virtual machines. They share the host kernel, unlike [[id:9111c90b-6462-4ea4-93eb-9d6dd9b8e0ef][VMs]] which have their own kernel.
+- Container security relies heavily on the [[id:d43f2ef3-6eb4-4f8d-89ed-095fedd7d7f9][Linux]] kernel. Kernel vulnerabilities can impact container isolation.
+- While providing strong isolation, containers are not [[id:9111c90b-6462-4ea4-93eb-9d6dd9b8e0ef][virtual machines]]. They share the host kernel, unlike [[id:9111c90b-6462-4ea4-93eb-9d6dd9b8e0ef][VMs]] which have their own kernel.
+- managing multiple containers can be a task in itself, especially in a distributed context. checkout [[id:f822f8f6-89eb-4aa8-ac8f-fdcff3f06fb9][orchestration]].
+
 * Resources
  - https://container.training/intro-selfpaced.yml.html

Content/20240508163913-orchestration.org

@@ -6,9 +6,12 @@
 
 See [[id:d4627a77-fafc-4c76-91a2-59a84e42de71][Container]]
 * Abstract
+- provisioning automation for deployment, scaling and management of resources.
+- said resources may be defined by conceptual combinations of compute, storage and networking resources.
 * Instances
 ** [[id:27a4d68c-adef-42aa-a4b4-b44b3f10395d][Apache Mesos]]
 ** [[id:c2072565-787a-4cea-9894-60fad254f61d][Kubernetes]]
 * Resources
  - https://en.wikipedia.org/wiki/Orchestration_(computing)
 
+

Content/index.org

@@ -4,12 +4,37 @@
 #+title: Index
 
 * Global Disclaimer
+
 What I compile in these notes isn't meant to be a factual state of the art but how I currently perceive whatever I've partially captured in them.
 
 Expect [[id:be99b67e-e454-4f19-ade7-4c3faf10ce07][paradoxes]], inaccuracies, [[id:d3617afa-85ce-4ac8-bdc3-19fe587c1956][pseudoscience]] and some occasional epiphanies. It's mostly rambling but that is necessary for the rare insight that brings calm to the chaotic combination of concepts that are a prerequisite for a fertile [[id:fef55c48-87a6-4828-a298-4326264fc0e5][Mind]].
 
 I also consider deliberately intellectually [[id:f3347380-f482-4077-a89b-a3ff059b4af6][hallucinating]] so that I can churn up [[id:5a68c46a-85bf-49f1-a589-5a6116f839fb][reality]] a little to chance upon the silver linings that help one push abstract boundaries.
 
+** AI Usage Disclaimer (As of 0x2267)
+- most of what goes here is original thought and is typed by me.
+- I do use LLMs to accelerate my learning pursuits and do not directly inject those in these nodes.
+- that's mostly for any question I have that I wouldn't directly find in docs or for things that are somewhat irrelevant.
+- Henceforth, you'll find an AI SubNode at the end of larger root nodes where I paste uncurated responses from LLMs.
+- I'm mostly using gemini-1.5-pro-advanced with the following base prompt:
+  - You provide terse but complete responses with good coverage of the concept asked while also providing the caveats involved in what is being discussed. Freely use examples of existing tools and analogies to better explain the concept with links if they exist.
+- I'm using this via gptel (a simple LLM client for emacs) : https://github.com/karthink/gptel in doom gccEmacs
+
+
+- A sample of how that looks like would be:
+
+*** LLM: based on the above, greet my readers while summarize my intentions
+
+
+Welcome! This document reflects my own learnings augmented by LLMs, with raw LLM outputs appended as subnodes for transparency and further exploration. My aim is to provide concise yet comprehensive explanations on various topics.
+
+*** LLM
+- I may group my questions in a section at the end for easier access sometimes.
+**** mention the intentions of the author based on what occurs before this point.
+
+
+The author intends to utilize this document as a personal knowledge base, emphasizing clarity and conciseness in their explanations. They also plan to leverage LLMs as learning aids, appending raw LLM responses for transparency and further analysis. This hybrid approach aims to provide a comprehensive and insightful exploration of the covered topics.
+
 * Endpoints
 ** [[id:1729][Index]]
  - notes down some basic rules about the braindump's usage
@@ -27,6 +52,8 @@ I also consider deliberately intellectually [[id:f3347380-f482-4077-a89b-a3ff059
  - a cache for ideas that may never see the light of day again.
    - or they just might...
 * Stream
+** 0x2267
+ - will have an AI tag for nodes where I ask questions. Am using gemini-1.5-pro-advanceed.
 ** 0x2262
 - will be booting some frustrating habits over time that I've acquired unknowingly.
 - these should be generic patterns that don't pertain to anything specific but span several domains.