diff options
| author | Jasper Ras <jras@hostnet.nl> | 2025-01-19 21:14:51 +0100 |
|---|---|---|
| committer | Jasper Ras <jras@hostnet.nl> | 2025-01-19 21:14:51 +0100 |
| commit | 9642cd7ae24f0ba79ce5647c709b35ae8f06a285 (patch) | |
| tree | ae25c3b0db7ae4c23186b294c6d000073f085c2d /.trash | |
| parent | 969b96c2531fb986f6c7f21fd544391b439defd7 (diff) | |
vault backup: 2025-01-19 21:14:51
Diffstat (limited to '.trash')
46 files changed, 389 insertions, 0 deletions
diff --git a/.trash/10 Jan 2025 - Vrijdag.md b/.trash/10 Jan 2025 - Vrijdag.md new file mode 100644 index 0000000..7ce6f34 --- /dev/null +++ b/.trash/10 Jan 2025 - Vrijdag.md @@ -0,0 +1,19 @@ +#Inwerken #mohalm +Maakt aanname dat zijn changes mbt logstash werken; zonder dat ie uberhaupt iets heeft kunnen checken, zover waren we nog niet. We wachten nog op reactie van Martin betreffende de systems VPN. Pas daarna ga ik zijn hiera mergen op de testpod en laat ik hem inloggen op logstash om puppet te runnen en te zien of het werkt. + +Stelt weinig verdiepende vragen over de openstack deployment zelf. Wilt alleen een architectuur overview zien. + +Vandaag ook weer wat "kinderachtige" manier van communiceren; +``` +LOL, I just had the most fun plottwist you will ever hear off! +You know that when you boot to rescue mode, ephemeral storage devices are not mounted? +I didn't know about this tbh. +So, when I was in normal mode, I had 2 devices (vda, vdb). And when I try to unrescue, I still get 2 devices instead of 3 (vda, vdb). +And I was like: Why rescue mode is not working???? +LMAO.. +And spent an hour trying to figure it out.. +And then, by luck, I realized that when I rescue, the root fs size change to 2GBs instead of 20GBs. +HAHAHA +I then realized that other fs (other than the root fs) don't get mounted when entering rescue modes hahahah (edited) +Sheeeeesh bro +``` diff --git a/.trash/1736778030 Van Schie inloopspreekuur 2.md b/.trash/1736778030 Van Schie inloopspreekuur 2.md new file mode 100644 index 0000000..c40880d --- /dev/null +++ b/.trash/1736778030 Van Schie inloopspreekuur 2.md @@ -0,0 +1,2 @@ +8.30 - 9.00 +13.00 - 14.00
\ No newline at end of file diff --git a/.trash/1736805088 obsidian cli.md b/.trash/1736805088 obsidian cli.md new file mode 100644 index 0000000..3af45d3 --- /dev/null +++ b/.trash/1736805088 obsidian cli.md @@ -0,0 +1,4 @@ +Make cli for obsidian notes, add taskwarrior-like functionality. + +cz ref name +cz todo blaat
\ No newline at end of file diff --git a/.trash/1736805921 Feedback loops are crucial.md b/.trash/1736805921 Feedback loops are crucial.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/1736805921 Feedback loops are crucial.md diff --git a/.trash/1736842424.md b/.trash/1736842424.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/1736842424.md diff --git a/.trash/1736845385 Puppetrun script in PATH.md b/.trash/1736845385 Puppetrun script in PATH.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/1736845385 Puppetrun script in PATH.md diff --git a/.trash/1736846871 Openstack hostname scheme.md b/.trash/1736846871 Openstack hostname scheme.md new file mode 100644 index 0000000..2929d25 --- /dev/null +++ b/.trash/1736846871 Openstack hostname scheme.md @@ -0,0 +1,11 @@ +--- +tags: + - groupone + - "#vpsplatform" +--- +Testpod domain: `prv.vps1-testpod-cph3.one.com` + +testpod -> `n01.<service>.``[prv.vps1-testpod-cph3.one.com](http://prv.vps1-testpod-cph3.one.com/)` + +prod cph8/lej1 -> `<service>.env.<az>.``[one.com](http://one.com/)` -> az `vps1/2/3-<region>` +prod freenet -> `<service>.env.<az>.g1i.one` -> az `vps1-lej1/2/3`
\ No newline at end of file diff --git a/.trash/1736852174 Python dataclass.md b/.trash/1736852174 Python dataclass.md new file mode 100644 index 0000000..02bcd66 --- /dev/null +++ b/.trash/1736852174 Python dataclass.md @@ -0,0 +1,5 @@ +--- +tags: + - python +--- +There is no option for them to behave as dicts,
\ No newline at end of file diff --git a/.trash/1736852200.md b/.trash/1736852200.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/1736852200.md diff --git a/.trash/1736855110 push_to_prod.md b/.trash/1736855110 push_to_prod.md new file mode 100644 index 0000000..60bac81 --- /dev/null +++ b/.trash/1736855110 push_to_prod.md @@ -0,0 +1,7 @@ +--- +tags: + - puppet + - ci + - continuous-integration +--- +The `push_to_prod` script in `scripts/` handles the deployment of Puppet from the CI.
\ No newline at end of file diff --git a/.trash/1736860283 Gitlab predefined CI variables.md b/.trash/1736860283 Gitlab predefined CI variables.md new file mode 100644 index 0000000..d0bb91d --- /dev/null +++ b/.trash/1736860283 Gitlab predefined CI variables.md @@ -0,0 +1,8 @@ +--- +tags: + - gitlab + - continuous-integration +--- +We used a predefined variable to reference the branch name for [[Deploying Puppet test environments]]: `${CI_COMMIT_REF_NAME} + +This kind of variable can be found at: diff --git a/.trash/1736868887 Fixtures.md b/.trash/1736868887 Fixtures.md new file mode 100644 index 0000000..3835749 --- /dev/null +++ b/.trash/1736868887 Fixtures.md @@ -0,0 +1,6 @@ +--- +tags: + - pytest + - python + - testing +--- diff --git a/.trash/1736883778 prototype based programming.md b/.trash/1736883778 prototype based programming.md new file mode 100644 index 0000000..7a0da92 --- /dev/null +++ b/.trash/1736883778 prototype based programming.md @@ -0,0 +1 @@ +In a prototype language objects are created via either a special object creation function or via cloning an existing one. Thus the prototype of a given object is similar to the parent class in a class based language. This implies that this kind object is mutable because we should be able to change clones into "new types" by additional properties etc,
\ No newline at end of file diff --git a/.trash/1736930658.md b/.trash/1736930658.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/1736930658.md diff --git a/.trash/2 Jan 2025 - Donderdag.md b/.trash/2 Jan 2025 - Donderdag.md new file mode 100644 index 0000000..59dd45a --- /dev/null +++ b/.trash/2 Jan 2025 - Donderdag.md @@ -0,0 +1,7 @@ +#Inwerken #mohalm + +--- +Onboarding ging wat stroef; ==credentials onzichtbaar Firefox==. +Uiteindelijk gelukt en na de lunch kon ie aan de slag. +Puppet env laten opzetten en documentatie laten lezen. +Elke keer als ik aangaf lees de readme leek hij er heel ==hectisch doorheen te gaan en niet echt te lezen.== Haast?
\ No newline at end of file diff --git a/.trash/2 areas 2/Huisartspraktijk F.J. van Schie.md b/.trash/2 areas 2/Huisartspraktijk F.J. van Schie.md new file mode 100644 index 0000000..1608f1a --- /dev/null +++ b/.trash/2 areas 2/Huisartspraktijk F.J. van Schie.md @@ -0,0 +1,24 @@ +https://huisartspraktijkvanschie.uwartsonline.nl/bereikbaarheid/ + +Dorpsstraat 349 1531 HJ, Wormer +### Telefoon +075 642 12 06 +**Spoed** 075 642 01 05 +### Spreekuur +- Dagelijks 7.30- 9.00 uur en 13.00 – 14.00 uur inloopspreekuur. +- Woensdagmiddag alleen op afspraak. +### Aanvragen huisbezoeken +- voor 9.30 uur. +### Opvragen resultaten/ aanvragen herhaalrecepten +- 11.00 uur-12.00 uur, en 14.00 uur-16.00 uur (woensdagmiddag niet). + +--- +## Spoedgevallen + +- Overdag op werkdagen behalve woensdagmiddag als gewone lijn bezet is: +- Tel: 075 642 01 05 +### Avond/weekend +- Tel: 075 653 30 00 +### Weekenddienst +- Huisartsenpost Zaandam +- Tel: 075 653 30 00
\ No newline at end of file diff --git a/.trash/3 Jan 2025 - Vrijdag.md b/.trash/3 Jan 2025 - Vrijdag.md new file mode 100644 index 0000000..3db3651 --- /dev/null +++ b/.trash/3 Jan 2025 - Vrijdag.md @@ -0,0 +1,13 @@ +#Inwerken #mohalm + +--- +Ik ben heel erg moe en kan niet echt meedenken. Merk dat ik ook niet de basis van Puppet beheers. Gelukkig is Jerry er om hem te helpen, komt erachter dat de puppet refactor workshop te outdated is. +Jerry had voor zijn eigen nieuwe team member bedacht dat ie wel een profiel kon maken om LAMP stack op vagrant box te installeren. +Mo lijkt niet te weten wat dat is, maar ==na het voor hem te hebben gespeld gaat ie zelfstandig verder.== +Is vrij snel klaar met een node definitie maken die Apache, MariaDB etc include. +Gezegd dat ie daar mss een spec test voor kan maken. +Stelt wat vreemde vragen; zoals wat gebeurd er als we “spec_helper” renamen? + +Geeft soms wat hectische vibes, probeert te hard zichzelf te bewijzen? + +Ik heb vooralsnog m’n twijfels of hij wel geschikt is.
\ No newline at end of file diff --git a/.trash/6 Jan 2025 - Maandag.md b/.trash/6 Jan 2025 - Maandag.md new file mode 100644 index 0000000..bf1109d --- /dev/null +++ b/.trash/6 Jan 2025 - Maandag.md @@ -0,0 +1,13 @@ +#Inwerken #mohalm + +--- +In de ochtend internal IT gemaild voor group.ONE VPN, bleek dat hij systems VPN nodig had maar Martin is er niet. VPN van IIT was voldoende voor nu om bij gitlab e.d te komen. + +Hij keek ff mee met waar ik mee bezig was: issue libvirt socket closed. Toen opperde hij vanalles waardoor ik het idee kreeg dat hij niet echt snapt wat wat is. Hij ==wist ook niet wat libvirt was.== + +Heb 'm wat repo's laten zien, en hij had wat vragen over architectuur en over hoe mensen ons platform gebruiken. Uitleg gegeven over verschil MCS t.o.v Hostnet bijv. + +Was nog bezig met Ruby oefenen sinds dit weekend - tot een uur of 3 mee bezig geweest. +Ging daarna verder met Puppet workshop; jerry had ff gekeken wat hij had gedaan n.a.v vrijdag en hem opdracht gegeven de LAMP stack uit te breiden met Vhost waar die wordpress in moet installeren. + +==Wist niet wat Vhost was== dus moeten uitleggen. Gaat verder wel zelfstandig z'n gang en lijkt vooralsnog gewoon z'n ding te kunnen doen zonder al te veel vragen. diff --git a/.trash/7 Jan 2025 - Dinsdag.md b/.trash/7 Jan 2025 - Dinsdag.md new file mode 100644 index 0000000..3d6c07b --- /dev/null +++ b/.trash/7 Jan 2025 - Dinsdag.md @@ -0,0 +1,6 @@ +#Inwerken #mohalm + +--- +Gisteren verteld dat ie vhosts via hieradata moet gaan configureren. Vanmorgen ineens begonnen met het ticket waarvan ik zei dat is de volgende stap. +Oftwel, doet niet wat hem verteld wordt. +Uitgelegd wat ie precies moet doen en waarom: "easy peazy" zegt ie, "geef me 30 min"... onderschat je het mss?
\ No newline at end of file diff --git a/.trash/8 Jan 2025 - Woensdag.md b/.trash/8 Jan 2025 - Woensdag.md new file mode 100644 index 0000000..b8bbc64 --- /dev/null +++ b/.trash/8 Jan 2025 - Woensdag.md @@ -0,0 +1,14 @@ +#Inwerken #mohalm + +--- +### Communicatie +Reageren op vragen als "heb je hulp nodig?" met "Ez" komt niet altijd professioneel over. +### Eerste ticket +Heeft een nieuwe spec-test gemaakt voor profile::openstack::logstash, alleen het draaien van die test faalt: +``` +error during compilation: Evaluation Error: Error while evaluating a Resource Statement, Could not find declared class logstash (file: /home/jras/projects/group.one/vps/puppet/modules/profile/spec/fixtures/modules/profile/manifests/openstack/logstash.pp, line: 45, column: 6) on node work.home +``` + +**Could not find declared class logstash** is referring to the usage of the class logstash within the class profile::openstack::logstash. This means that a fixture has to be added so that the class logstash is available to our test. + +Fixtures zijn te defineren `.fixtures.yml` bijv in `modules/profiles/.fixtures.yml`.
\ No newline at end of file diff --git a/.trash/ARP.md b/.trash/ARP.md new file mode 100644 index 0000000..7b731f3 --- /dev/null +++ b/.trash/ARP.md @@ -0,0 +1 @@ +Address Resolution Procotol
\ No newline at end of file diff --git a/.trash/Atom detail.md b/.trash/Atom detail.md new file mode 100644 index 0000000..7ad5325 --- /dev/null +++ b/.trash/Atom detail.md @@ -0,0 +1,5 @@ +--- +tags: + - taskflow +--- +The atom detail serves as metadata for actual atoms so we can store information necessary for reconstructing the state of a flow for example
\ No newline at end of file diff --git a/.trash/Clippings/ChatGPT.md b/.trash/Clippings/ChatGPT.md new file mode 100644 index 0000000..4449c3b --- /dev/null +++ b/.trash/Clippings/ChatGPT.md @@ -0,0 +1,44 @@ +--- +title: ChatGPT +source: https://chatgpt.com/ +author: +published: +created: 2025-01-10 +description: ChatGPT helps you get answers, find inspiration and be more productive. It is free to use and easy to try. Just ask and ChatGPT can help with writing, learning, brainstorming and more. +tags: + - clippings +--- +A **broadcast storm** is a situation in a computer network where an excessive amount of broadcast traffic is generated, often causing network congestion, performance degradation, and potential network outages. This occurs when broadcast packets are continuously transmitted and forwarded across a network, leading to a loop or overload condition. + +### How a Broadcast Storm Happens: + +1. **Broadcast Traffic Propagation**: In a network, devices use broadcast messages (such as ARP requests) to communicate with all devices on the local network segment. Normally, switches forward these broadcast frames to all other ports except the port where the packet was received. +2. **Network Loops**: A broadcast storm often occurs when there are network loops. A **network loop** happens when a device or switch incorrectly forwards broadcast packets back into the network, causing the packets to continuously circulate. This can happen if there are redundant paths between network switches without the proper loop prevention mechanisms. +3. **Exponential Growth of Broadcast Traffic**: Once a loop is formed, broadcast frames get circulated around the loop, causing more and more copies of the same broadcast to be propagated through the network. As the broadcast packets continue to propagate, they consume network bandwidth and processing power of devices, leading to severe network congestion. +4. **Network Devices Overload**: If the storm is not controlled, network devices like routers and switches can become overwhelmed with the continuous broadcast traffic, and the network’s ability to process legitimate traffic diminishes. This can lead to high CPU utilization, dropped packets, or even complete network outages. + +### Causes of a Broadcast Storm: + +1. **Switch Loops**: When multiple network switches are connected in such a way that frames circulate endlessly through the network. This can happen if there is no proper loop detection or prevention mechanism like **Spanning Tree Protocol (STP)**. +2. **Faulty Configuration**: Incorrect network device configurations, such as improperly configured VLANs or missing loop prevention protocols, can lead to broadcast storms. +3. **Misbehaving Devices**: Devices that malfunction or incorrectly generate broadcast traffic, such as networked printers, routers, or computers, can also cause broadcast storms by continuously sending out broadcasts. +4. **Faulty Network Adapters or Software**: Malfunctions in network adapters or software (e.g., drivers that cause network interfaces to repeatedly send broadcast packets) can also contribute to broadcast storms. + +### Effects of a Broadcast Storm: + +- **Network Congestion**: The excessive broadcast traffic consumes a large portion of the available bandwidth, making it difficult or impossible for legitimate traffic to flow through the network. +- **Decreased Performance**: Devices that receive too many broadcast frames may struggle to process them, leading to slowdowns in network performance and increased latency. +- **Device Overload**: Switches, routers, and end devices may experience high CPU usage or become unresponsive due to the overload of processing broadcast frames. +- **Network Outages**: In severe cases, broadcast storms can bring down the entire network, as devices may be too busy handling the broadcast traffic to handle normal communication. + +### How to Prevent or Mitigate a Broadcast Storm: + +1. **Spanning Tree Protocol (STP)**: STP is a protocol used in Ethernet networks to prevent network loops by dynamically disabling certain paths, ensuring that broadcast traffic doesn't circulate endlessly. +2. **VLAN Segmentation**: By segmenting the network into multiple VLANs, you can limit the scope of broadcast traffic to a smaller area, preventing storms from affecting the entire network. +3. **Broadcast Storm Control**: Many modern switches include **broadcast storm control** features that allow administrators to limit the amount of broadcast traffic allowed on a port. This can help reduce the risk of a broadcast storm. +4. **Proper Network Design**: Ensuring that redundant paths are carefully managed, and network topologies are designed with loop prevention in mind, is essential to avoiding broadcast storms. +5. **Monitoring and Alerting**: Monitoring network traffic for signs of excessive broadcast traffic can help identify and resolve a potential broadcast storm before it becomes disruptive. + +### In Summary: + +A **broadcast storm** occurs when broadcast traffic is generated in such volume that it overwhelms a network, often due to network loops or misconfigurations. It can severely degrade network performance, cause devices to become unresponsive, and potentially lead to network outages. Effective use of network design, protocols like STP, and broadcast storm control mechanisms can help prevent or mitigate the impact of broadcast storms.
\ No newline at end of file diff --git a/.trash/Containment.md b/.trash/Containment.md new file mode 100644 index 0000000..6d3a638 --- /dev/null +++ b/.trash/Containment.md @@ -0,0 +1,8 @@ +--- +tags: + - puppet +--- +Controls order of execution. +Classes & defined type **contain** resources. + +Resources are automatically contained, classes only when declared with `contain` keyword.
\ No newline at end of file diff --git a/.trash/Contextlib closing.md b/.trash/Contextlib closing.md new file mode 100644 index 0000000..d4f50ab --- /dev/null +++ b/.trash/Contextlib closing.md @@ -0,0 +1,18 @@ +--- +tags: + - python +--- +Use `contextlib.closing` to automatically close something at the end of a block. +``` +with closing(blaat) as b: + b.do_something(b) +``` +is equal to +``` +try: + b.do_something() +finally: + b.close() +``` + +This is used for example with taskflow's [[Persistence]].
\ No newline at end of file diff --git a/.trash/Dagboek/do jan 09 2025.md b/.trash/Dagboek/do jan 09 2025.md new file mode 100644 index 0000000..081504d --- /dev/null +++ b/.trash/Dagboek/do jan 09 2025.md @@ -0,0 +1,10 @@ +Vanmorgen ontdekte ik dat je in Obsidian templates kan maken waarop je nieuwe notes kan baseren. Zo heb ik er nu een gemaakt voor de daily note. +Mohammed aan het werk gezet om **==VPN in orde te krijgen==**; na standup bleek dat hij ==**zelf ook een user moet maken via Chef**.== Ook moet hij nog een ==**user in openstack maken**==. + +Ik heb code gewijzigd voor ==VPS-806 en VPS-807 en begon dat te testen op de testpod==; ik kwam er toen achter dat er ==delete taken niet doorliepen== daar en heb die een voor een gereset zodat ze doorlopen. Om de een of andere reden als ik ze allemaal tegelijk reset dan falen ze omdat ze elkaar proberen te updaten ofzo. + +Rond het middaguur hebben we dat gemerged na goedkeuren van Esben. Er onstonden een ==aantal uid/gid conflicten==; keystone testpod; een mailpod en een tableau node. Ik kwam daar achter tijdens het uitrollen van zijn openstack user op de testpod. + +Mohammed Puppet laten aanpassen zodat de **==`rsync-fernet` user als system user==** gemaakt wordt. Ik heb daarna met de hand de user en files geupdatet. + +Mohammed z'n ==**OpenStack user werkt niet**==. Ik heb 'm toegevoegd aan het hostnet project maar dat helpt niet. Hij geeft aan dat ie vergeten was tijdens het encrypten de recipients op te geven dus denkt dat ie niet decrypted kan worden. ==**Tweede poging is wel gelukt.**==
\ No newline at end of file diff --git a/.trash/Deploying Puppet test environments.md b/.trash/Deploying Puppet test environments.md new file mode 100644 index 0000000..c0f3b7e --- /dev/null +++ b/.trash/Deploying Puppet test environments.md @@ -0,0 +1,8 @@ +--- +tags: + - puppet + - groupone +--- +We used to deploy puppet test environments from a fork but it requires the deploy key. The push_to_prod script explicitly only deploys master from the groupvps namespace. As we don't want to copy the deploy key to everyones fork, we'll update the workflow so that from the groupvps namespace projects/ branches are also deployed. + +Now we can push a branch prefixed with `projects/` to the main puppet repo and it will be deployed as an env on the testpod Puppet master(s). diff --git a/.trash/Documentation.md b/.trash/Documentation.md new file mode 100644 index 0000000..7afdf72 --- /dev/null +++ b/.trash/Documentation.md @@ -0,0 +1 @@ +The documentation for the Puppet that we use is found at https://www.puppet.com/docs/puppet/8/puppet_index.html.
\ No newline at end of file diff --git a/.trash/Drawing 2025-01-15 08.22.45.excalidraw.md b/.trash/Drawing 2025-01-15 08.22.45.excalidraw.md new file mode 100644 index 0000000..1509331 --- /dev/null +++ b/.trash/Drawing 2025-01-15 08.22.45.excalidraw.md @@ -0,0 +1,14 @@ +--- + +excalidraw-plugin: parsed +tags: [excalidraw] + +--- +==⚠ Switch to EXCALIDRAW VIEW in the MORE OPTIONS menu of this document. ⚠== You can decompress Drawing data with the command palette: 'Decompress current Excalidraw file'. For more info check in plugin settings under 'Saving' + + +## Drawing +```compressed-json +N4IgLgngDgpiBcIYA8DGBDANgSwCYCd0B3EAGhADcZ8BnbAewDsEAmcm+gV31TkQAswYKDXgB6MQHNsYfpwBGAOlT0AtmIBeNCtlQbs6RmPry6uA4wC0KDDgLFLUTJ2lH8MTDHQ0YNMWHRJMRZFAHZFAFYyJE9VGEYwGgQAbQBdcnQoKABlALA+UEl8PGzsDT5GTkxMch0YIgAhdFQAayKuRlwAYXpMenwEEABiADMx8ZAAX0mgA +``` +%%
\ No newline at end of file diff --git a/.trash/How to pass Sensitive data to template.md b/.trash/How to pass Sensitive data to template.md new file mode 100644 index 0000000..58de7e7 --- /dev/null +++ b/.trash/How to pass Sensitive data to template.md @@ -0,0 +1,4 @@ +--- +tags: + - puppet +--- diff --git a/.trash/Log context format.md b/.trash/Log context format.md new file mode 100644 index 0000000..099bfe8 --- /dev/null +++ b/.trash/Log context format.md @@ -0,0 +1,6 @@ +--- +tags: + - openstack + - log + - oslo +--- diff --git a/.trash/Migration/Antagonist Migration.md b/.trash/Migration/Antagonist Migration.md new file mode 100644 index 0000000..093dbd7 --- /dev/null +++ b/.trash/Migration/Antagonist Migration.md @@ -0,0 +1,31 @@ +#groupone #migration + + +--- +Migrate VMs + +Not managed by customers, only Antagonist managed +Most of it is backoffice, only few are front facing + +Ovirt (KVM) + + +Possible to change IPs? + +Difficulty: private networking between hosts + databases only ones in the private network + + Should be possible to switch IPs + + +Outsourced routers to DC provider, more difficult to integrate networks + +Most of the things can be redeployed, Rutger notes that maybe all they need is access + +We can use their left-over IP space + +Features +- requires internal network, so want to create networks/routers +- HA/automatic failover? -> Not yet +- Anti-affinity rules? Dont want all the LBs on the same (failing) node + diff --git a/.trash/OneIT Helpdesk.md b/.trash/OneIT Helpdesk.md new file mode 100644 index 0000000..970cfa6 --- /dev/null +++ b/.trash/OneIT Helpdesk.md @@ -0,0 +1,5 @@ +--- +tags: + - groupone + - support +--- diff --git a/.trash/Perpetual lists.md b/.trash/Perpetual lists.md new file mode 100644 index 0000000..9519dd5 --- /dev/null +++ b/.trash/Perpetual lists.md @@ -0,0 +1,7 @@ +#task #todo #bookmark + +--- +# Tasks +- +# Bookmarks +- [ ] https://obsidian.rocks/tracking-tasks-in-obsidian-the-beginners-guide/
\ No newline at end of file diff --git a/.trash/Persistence.md b/.trash/Persistence.md new file mode 100644 index 0000000..682b88e --- /dev/null +++ b/.trash/Persistence.md @@ -0,0 +1,40 @@ +--- +tags: + - taskflow +references: + - https://docs.openstack.org/taskflow/latest/user/persistence.html +--- +Main interface is called Backend. + +**prep** +Backend + (Logbook ->) Flow Detail -> Engine -> Storage + +**execution** +inspect existing atom details -> find unfinished -> inspect graph -> run atoms + +**post exec** +destroy logbook, clear backend +can be configured to keep those things around for any purpose + +> Logbook is the authoritive source of run-time state. Logbook written first, then persisted. + +Namespace: `taskflow.persistence`. +``` +from taskflow.persistence import backends + +... +persistence = backends.fetch(conf={ + "connection": "mysql", + "user": ..., + "password": ..., +}) + +logbookj +``` + +Types: +- memory (connection: memoery) +- files (connection: dir | file) + - https://docs.openstack.org/taskflow/latest/user/persistence.html#id5 +- sqlalchemy (connection: mysql | postgres | sqlite) +- zookeper (connection: zookeeper)
\ No newline at end of file diff --git a/.trash/Resumable.md b/.trash/Resumable.md new file mode 100644 index 0000000..1a36ef0 --- /dev/null +++ b/.trash/Resumable.md @@ -0,0 +1,13 @@ +--- +tags: + - taskflow +references: + - https://docs.openstack.org/taskflow/latest/user/resumption.html + - https://opendev.org/openstack/taskflow/src/branch/master//taskflow/examples/resume_from_backend.py +--- +[Example](https://opendev.org/openstack/taskflow/src/branch/master//taskflow/examples/resume_from_backend.py) + +A flow can be resumed by reconstructing the links between atoms. This is done by a factory function that has to be importable. Instead of passing a flow to the run function, we need to pass the factorkkky function to the load-from-factory function which will call the factory to create the flow and passes it to the engine. + +Atom names should be unique in a flow so that when resuming it the corresponding flow detail can be matched. + diff --git a/.trash/SystemRescueCD.md b/.trash/SystemRescueCD.md new file mode 100644 index 0000000..6e601a3 --- /dev/null +++ b/.trash/SystemRescueCD.md @@ -0,0 +1,6 @@ +--- +tags: + - linux +references: + - https://www.system-rescue.org/ +--- diff --git a/.trash/Taskflow.md b/.trash/Taskflow.md new file mode 100644 index 0000000..5df4766 --- /dev/null +++ b/.trash/Taskflow.md @@ -0,0 +1,8 @@ +--- +tags: + - python + - openstack +--- +Different kinds of flow types are called patterns and thus imported from `taskflow.patterns`. + +Flows can be [[Resumable]]
\ No newline at end of file diff --git a/.trash/Thursday, 16 Jan 2025.md b/.trash/Thursday, 16 Jan 2025.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/Thursday, 16 Jan 2025.md diff --git a/.trash/Untitled 1.canvas b/.trash/Untitled 1.canvas new file mode 100644 index 0000000..0175121 --- /dev/null +++ b/.trash/Untitled 1.canvas @@ -0,0 +1,6 @@ +{ + "nodes":[ + {"id":"30cedf91cb96488e","x":-125,"y":-30,"width":125,"height":50,"color":"6","type":"text","text":"Backend."} + ], + "edges":[] +}
\ No newline at end of file diff --git a/.trash/Untitled 3.canvas b/.trash/Untitled 3.canvas new file mode 100644 index 0000000..9e26dfe --- /dev/null +++ b/.trash/Untitled 3.canvas @@ -0,0 +1 @@ +{}
\ No newline at end of file diff --git a/.trash/Untitled 8.md b/.trash/Untitled 8.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/Untitled 8.md diff --git a/.trash/User management.md b/.trash/User management.md new file mode 100644 index 0000000..67ef7a0 --- /dev/null +++ b/.trash/User management.md @@ -0,0 +1,12 @@ +--- +tags: +references: + - https://www.puppet.com/docs/puppet/7/types/user.html + - https://www.puppet.com/docs/puppet/7/types/user.html#user-attribute-system +--- +System users can be defined as follows; +``` +user { + system => true|false +} +``` diff --git a/.trash/broadcast storm.md b/.trash/broadcast storm.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/broadcast storm.md diff --git a/.trash/wedding invitation.md b/.trash/wedding invitation.md new file mode 100644 index 0000000..e69de29 --- /dev/null +++ b/.trash/wedding invitation.md diff --git a/.trash/{{date}}.md b/.trash/{{date}}.md new file mode 100644 index 0000000..830b011 --- /dev/null +++ b/.trash/{{date}}.md @@ -0,0 +1 @@ +{{date}}
\ No newline at end of file |