add auto fetch ssl certs
This commit is contained in:
@@ -13,7 +13,7 @@
|
||||
"articleSection" : "post",
|
||||
"name" : "[筆記] 測試 proxmox 存取由 synology HA cluster 分享的NFS 目錄 \/ Proxmox With Synology High Availability",
|
||||
"headline" : "[筆記] 測試 proxmox 存取由 synology HA cluster 分享的NFS 目錄 \/ Proxmox With Synology High Availability",
|
||||
"description" : "\x3cp\x3e前幾天修復了因為intel cpu bug 導致無法使用的 synology DS415\x2b\x3c\/p\x3e\n\n\x3cp\x3e詳情請看 \x3ca href=\x22https:\/\/h.cowbay.org\/post\/first-try-synology-ha\/\x22\x3ehttps:\/\/h.cowbay.org\/post\/first-try-synology-ha\/\x3c\/a\x3e\x3c\/p\x3e\n\n\x3cp\x3e今天趁尾牙前夕,手邊沒啥要緊事\x3c\/p\x3e\n\n\x3cp\x3e就來玩玩看promox 加上 synology high availability 再加上 NFS share 的環境\x3c\/p\x3e",
|
||||
"description" : "\x3cp\x3e前幾天修復了因為intel cpu bug 導致無法使用的 synology DS415\x2b\x3c\/p\x3e\n\x3cp\x3e詳情請看 \x3ca href=\x22https:\/\/h.cowbay.org\/post\/first-try-synology-ha\/\x22\x3ehttps:\/\/h.cowbay.org\/post\/first-try-synology-ha\/\x3c\/a\x3e\x3c\/p\x3e\n\x3cp\x3e今天趁尾牙前夕,手邊沒啥要緊事\x3c\/p\x3e\n\x3cp\x3e就來玩玩看promox 加上 synology high availability 再加上 NFS share 的環境\x3c\/p\x3e",
|
||||
"inLanguage" : "en",
|
||||
"author" : "Eric Chang",
|
||||
"creator" : "Eric Chang",
|
||||
@@ -45,9 +45,9 @@
|
||||
|
||||
<link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.3.1/css/all.css" integrity="sha384-mzrmE5qonljUremFsqc01SB46JvROS7bZs3IO2EmfFsd15uHvIt+Y8vEf7N7fWAU" crossorigin="anonymous">
|
||||
|
||||
<link href="https://h.cowbay.org/css/style.css?v=1626744134" rel="stylesheet" id="theme-stylesheet" type='text/css' media='all'>
|
||||
<link href="https://h.cowbay.org/css/style.css?v=1629951055" rel="stylesheet" id="theme-stylesheet" type='text/css' media='all'>
|
||||
|
||||
<link href="https://h.cowbay.org/css/custom.css?v=1626744134" rel="stylesheet" type='text/css' media='all'>
|
||||
<link href="https://h.cowbay.org/css/custom.css?v=1629951055" rel="stylesheet" type='text/css' media='all'>
|
||||
<link rel="shortcut icon" href="https://h.cowbay.org/img/favicon.ico" type="image/x-icon">
|
||||
<link rel="icon" href="https://h.cowbay.org/img/favicon.ico" type="image/x-icon">
|
||||
|
||||
@@ -81,10 +81,6 @@ if (!doNotTrack) {
|
||||
|
||||
<ul id="menu-secondary-items" class="menu-secondary-items">
|
||||
|
||||
<li class="menu-item menu-item-type-taxonomy menu-item-object-category">
|
||||
<a href="/categories/"></a>
|
||||
</li>
|
||||
|
||||
<li class="menu-item menu-item-type-taxonomy menu-item-object-category">
|
||||
<a href="/categories/ansible">ansible</a>
|
||||
</li>
|
||||
@@ -309,66 +305,35 @@ if (!doNotTrack) {
|
||||
<div class="entry-content">
|
||||
<article>
|
||||
<p>前幾天修復了因為intel cpu bug 導致無法使用的 synology DS415+</p>
|
||||
|
||||
<p>詳情請看 <a href="https://h.cowbay.org/post/first-try-synology-ha/">https://h.cowbay.org/post/first-try-synology-ha/</a></p>
|
||||
|
||||
<p>今天趁尾牙前夕,手邊沒啥要緊事</p>
|
||||
|
||||
<p>就來玩玩看promox 加上 synology high availability 再加上 NFS share 的環境</p>
|
||||
|
||||
<p>先上架構圖</p>
|
||||
|
||||
<p><img src="https://i.imgur.com/k7IDZ4Y.png" alt="" /></p>
|
||||
|
||||
<p><img src="https://i.imgur.com/k7IDZ4Y.png" alt=""></p>
|
||||
<p>架構很簡單,NAS設定一組NFS share, proxmox mount 進來,然後開一台VM在NFS 上</p>
|
||||
|
||||
<p>主要來談談proxmox 在碰到synology high availability 切換狀態、遇上腦裂(brain split)時候的狀況</p>
|
||||
|
||||
<p>觸發 brain split (說真的,我覺得腦裂很難聽 …)的情況,在上面連結那篇文章裡面有提到,就不多說了</p>
|
||||
|
||||
<p>來講講後續的狀況</p>
|
||||
|
||||
<p>發生 brain split 時,可以預期管理者會登入管理界面去修復</p>
|
||||
|
||||
<p>關於修復brain split 可以看看群暉的這篇文章</p>
|
||||
|
||||
<p><a href="https://www.synology.com/zh-tw/knowledgebase/DSM/help/HighAvailability/split_brain">https://www.synology.com/zh-tw/knowledgebase/DSM/help/HighAvailability/split_brain</a></p>
|
||||
|
||||
<p>而我選擇的是 [將兩台伺服器一同保留於叢集中]</p>
|
||||
|
||||
<p>在進行修復的過程中,會發現VM這邊會變成 read only</p>
|
||||
|
||||
<p>聽起來很合理,畢竟在修復時,所有服務幾乎都是停擺</p>
|
||||
|
||||
<p>但是呢,等到修復完成後,VM還是read only ,這就有點奇怪了</p>
|
||||
|
||||
<p>有跟群暉客服反應過這個狀況</p>
|
||||
|
||||
<p>所以在修復完成之後,在proxmox server 這邊直接對NFS 存取做測試</p>
|
||||
|
||||
<p>去下載一個template 是 OK 的,在console 裡面直接在NFS touch file 也是可以的</p>
|
||||
|
||||
<p>所以Synology high availability 是有正常發揮作用</p>
|
||||
|
||||
<p>而promox 這邊,在synology恢復之後,也可以正常存取NFS ,所以也沒有問題</p>
|
||||
|
||||
<p><del>那問題就是在VM裡面了,當發生了某些狀況,讓系統進入read only ,就必須透過reboot 才能解決</del></p>
|
||||
|
||||
<p><del>或者是看看這個指令用fsck去檢查filesystem 看看有沒有幫助</del></p>
|
||||
|
||||
<pre><code>sudo fsck -Af -M
|
||||
</code></pre>
|
||||
|
||||
<p>UPDATE:</p>
|
||||
|
||||
</code></pre><p>UPDATE:</p>
|
||||
<p>在proxmox 論壇上提出了這個問題,有回覆說要用 NFS Version 4.1</p>
|
||||
|
||||
<p>經過測試,在掛載NFS share folder 時,如果有指定 NFS Version 4.1</p>
|
||||
|
||||
<p>那在HA Cluster 恢復之後,VM也就跟著恢復正常</p>
|
||||
|
||||
<p>不必再重開機了!</p>
|
||||
|
||||
<p>所以這問題算是解決了!</p>
|
||||
</article>
|
||||
</div>
|
||||
@@ -648,7 +613,7 @@ title="pinterest icon"></i>
|
||||
|
||||
</ul> <div class="design-credit">
|
||||
|
||||
<p>© 2018 Göran Svensson</p>
|
||||
<p>© 2018 Göran Svensson</p>
|
||||
|
||||
<p>Nederburg Hugo Theme by <a href="https://appernetic.io">Appernetic</a>.</p>
|
||||
|
||||
@@ -660,7 +625,7 @@ title="pinterest icon"></i>
|
||||
</div>
|
||||
<script src="https://h.cowbay.org/js/jquery.min.js"></script>
|
||||
<script src="https://h.cowbay.org/js/jquerymigrate.js"></script>
|
||||
<script src="https://h.cowbay.org/js/production.min.js?v=1626744134"></script>
|
||||
<script src="https://h.cowbay.org/js/production.min.js?v=1629951055"></script>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
||||
Reference in New Issue
Block a user