I hereby claim:
- I am tturnerdev on github.
- I am tturner (https://keybase.io/tturner) on keybase.
- I have a public key ASCQw8X3seDKfQmgzcpHOkc_Wwtv_g6lmaOzsPEl47jbfAo
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
Note this should only be done once you are sure you have reliable TB mesh network.
this is because proxmox UI seems fragile wrt to changing underlying network after configuration of ceph.
All installation done via command line due to gui not understanding the mesh network
This setup doesn't attempt to seperate the ceph public network and ceph cluster network (not same as proxmox clutser network), The goal is to get an easy working setup.
**2025.04.24 NOTE: some folks had to switch to IPv6 for ceph due to IPv4 unreliability issues, we think as of pve 8.4.1 and all the input the community has give to update this set of gsists - that IPv4 is now reliable even on MS-01. As such i advising everyone to use IPv4 for ceph as if you have IPv6 you will have issues with SDN at this time (if you don't use SDN this is not an issue).
this gist is part of this series
Put simply I am not sure what the design should be. I have the thunderbolt mesh network and the 2.5gbe NIC on each node. The ideal design guidelies cause my brain to have a race conditions because:
this gist is part of this series
This assumes you are running Proxmox 8.4 and that the line source /etc/network/interfaces.d/* is at the end of the interfaces file (this is automatically added to both new and upgraded installations of Proxmox 8.2).
This changes the previous file design thanks to @NRGNet and @tisayama to make the system much more reliable in general, more maintainable esp for folks using IPv4 on the private cluster network (i still recommend the use of the IPv6 FC00 network you will see in these docs)
aka what i did to get from nothing to done.
note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so). YMMV
| <!-- put this to IDEA keymaps config folder. For v13 it is <userdir>\.IntelliJIdea13\config\keymaps\ --> | |
| <?xml version="1.0" encoding="UTF-8"?> | |
| <keymap version="1" name="Mac OS X 10.5+ Windows Ctrl" parent="Mac OS X 10.5+"> | |
| <action id="$Copy"> | |
| <keyboard-shortcut first-keystroke="meta C" /> | |
| <keyboard-shortcut first-keystroke="meta INSERT" /> | |
| <keyboard-shortcut first-keystroke="control C" /> | |
| <keyboard-shortcut first-keystroke="control INSERT" /> | |
| </action> | |
| <action id="$Cut"> |
In terms of programming-in-the-large, at Google and elsewhere, I think that language choice is not as important as all the other choices: if you have the right overall architecture, the right team of programmers, the right development process that allows for rapid development with continuous improvement, then many languages will work for you; if you don't have those things you're in trouble regardless of your language choice. -- Peter Norvig
| REF: https://mirrors.edge.kernel.org/pub/software/scm/git/docs/howto/revert-a-faulty-merge.txt | |
| Archive: April 11, 2018 | |
| Date: Fri, 19 Dec 2008 00:45:19 -0800 | |
| From: Linus Torvalds <torvalds@linux-foundation.org>, Junio C Hamano <gitster@pobox.com> | |
| Subject: Re: Odd merge behaviour involving reverts | |
| Abstract: Sometimes a branch that was already merged to the mainline | |
| is later found to be faulty. Linus and Junio give guidance on | |
| recovering from such a premature merge and continuing development | |
| after the offending branch is fixed. |
| time | type | distance | disposition | |
|---|---|---|---|---|
| 10.767 | Suspect | 364.966253229622 | HANDLED BY OFFICER | |
| 9.383 | Theft | 655.532480744734 | REPORT | |
| 7.433 | NonViolent | 418.959396534806 | HANDLED BY OFFICER | |
| 7.083 | Suspect | 421.977374823697 | UNABLE TO LOCATE | |
| 6.933 | NonViolent | 462.310209812741 | REPORT | |
| 18.933 | Theft | 609.032939868237 | HANDLED BY OFFICER | |
| 16.717 | Suspect | 389.345420404078 | UNABLE TO LOCATE | |
| 13.017 | Theft | 291.593094160669 | OTHER | |
| 1.683 | Suspect | 1266.2267703109 | HANDLED BY OFFICER |