https://blog.iphpo.com/tags/devops/Recent content in devops on 戲中話Hugozh-twherb09638@gmail.com (Herb)herb09638@gmail.com (Herb)Sun, 05 May 2019 01:00:29 +0800https://blog.iphpo.com/blog/2019/%E5%8D%87%E7%B4%9A%E7%B7%A8%E8%AD%AF-sshd-8.0-%E4%B8%A6%E7%A7%BB%E9%99%A4%E7%89%88%E6%9C%AC%E8%B3%87%E8%A8%8A/Sun, 05 May 2019 01:00:29 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2019/%E5%8D%87%E7%B4%9A%E7%B7%A8%E8%AD%AF-sshd-8.0-%E4%B8%A6%E7%A7%BB%E9%99%A4%E7%89%88%E6%9C%AC%E8%B3%87%E8%A8%8A/自己從source編譯的好處是可以隱藏版本資訊，並能即時更新到最新版本，修復各種新發現的漏洞https://blog.iphpo.com/blog/2018/01/kops-%E5%BB%BA%E7%AB%8B-cluster-%E6%99%82%E5%8A%A0%E5%85%A5-insecure-registry/Thu, 25 Jan 2018 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2018/01/kops-%E5%BB%BA%E7%AB%8B-cluster-%E6%99%82%E5%8A%A0%E5%85%A5-insecure-registry/<p>用 kops 可以輕易在 aws or gcp 上建立 kubernetes cluster</p> <p>但如果有自己的私人倉庫</p> <p>又沒有為這個倉庫買憑證的話</p> <p>就會遇到 pull 不了 image 的問題</p>https://blog.iphpo.com/blog/2018/01/kubernetes-%E4%BD%BF%E7%94%A8-%E7%A7%81%E6%9C%89-docker-%E5%80%89%E5%BA%AB%E4%B8%A6%E8%A7%A3%E6%B1%BAssl%E6%86%91%E8%AD%89%E5%95%8F%E9%A1%8C-kubernetes-private-registry-insecure/Sat, 20 Jan 2018 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2018/01/kubernetes-%E4%BD%BF%E7%94%A8-%E7%A7%81%E6%9C%89-docker-%E5%80%89%E5%BA%AB%E4%B8%A6%E8%A7%A3%E6%B1%BAssl%E6%86%91%E8%AD%89%E5%95%8F%E9%A1%8C-kubernetes-private-registry-insecure/<p>要在 Kubernetes 使用私有倉庫並不難</p> <p>只需要照著<a href="https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/">官方的教學</a>設定即可</p> <p>當我在用 <a href="https://github.com/kubernetes/minikube">minikube</a> 時卻一直無法成功 pull image</p> <p>我的 pod yaml 設定：</p>https://blog.iphpo.com/blog/2018/01/build-docker-image-%E6%99%82%E5%87%BA%E7%8F%BE-no-space-left-device/Tue, 02 Jan 2018 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2018/01/build-docker-image-%E6%99%82%E5%87%BA%E7%8F%BE-no-space-left-device/<p>我的 Macbook air 只有 128 GB 的硬碟空間(對這不叫內存!!!!!!)</p> <p>在某次build image的時候出現空間不足的錯誤</p>https://blog.iphpo.com/blog/2018/01/macos-x-%E4%B8%8B-docker-compose-%E9%80%9F%E5%BA%A6%E9%9D%9E%E5%B8%B8%E6%85%A2%E7%9A%84%E8%A7%A3%E6%B1%BA%E6%96%B9%E6%B3%95/Tue, 02 Jan 2018 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2018/01/macos-x-%E4%B8%8B-docker-compose-%E9%80%9F%E5%BA%A6%E9%9D%9E%E5%B8%B8%E6%85%A2%E7%9A%84%E8%A7%A3%E6%B1%BA%E6%96%B9%E6%B3%95/<p>每次執行 docker-compose up</p> <p>跟docker-compose down</p> <p>速度都超級慢</p> <p>正常來講</p> <p>幾秒鐘之內就可以關掉好幾個container</p> <p>但在我家電腦要花最少一分鐘以上</p> <p>這速度真是無法忍受</p> <p>搜尋後找到神奇的答案</p>https://blog.iphpo.com/blog/2017/11/logrotate-%E7%9A%84%E8%A8%AD%E5%AE%9A%E7%BF%BB%E8%AD%AF/Sat, 25 Nov 2017 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2017/11/logrotate-%E7%9A%84%E8%A8%AD%E5%AE%9A%E7%BF%BB%E8%AD%AF/<p>logrotate 是一個自動分割、打包檔案的工具</p> <p>log檔案會隨著時間日益增大</p> <p>不止不好查看</p> <p>大到一個程度寫入Log效能也會變差</p> <p>所以需要 logrotate 來幫忙分割打包壓縮處理</p> <p>有鑒於網路上都是分享自己的設定</p> <p>並沒有一個很全面的說明</p> <p>所以我就把 man logrotate 的設定翻譯一下</p>https://blog.iphpo.com/blog/2017/11/%E5%9C%A8command-line%E4%B8%8B%E7%A7%BB%E5%8B%95%E6%B8%B8%E6%A8%99-move-cursor-in-command/Sat, 25 Nov 2017 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2017/11/%E5%9C%A8command-line%E4%B8%8B%E7%A7%BB%E5%8B%95%E6%B8%B8%E6%A8%99-move-cursor-in-command/<p>對常使用command line的人來說</p> <p>移動游標一直是很不方便的事情</p> <p>尤其是打了一大串指令</p> <p>發現中間有錯字</p> <p>就會很崩潰的按著方向鍵等游標飄過去</p> <p>或是從網路上複製一大串指令</p> <p>發現中間要修改一個參數</p> <p>也是只能嘆口氣按下方向鍵等它飄過去</p> <p>其實不必這麼麻煩</p> <p>目前在 MacOSX 跟 Linux 上實測</p> <p>都有移動指標的快速鍵</p>https://blog.iphpo.com/blog/2017/11/ansible-%E8%88%87-vagrant-%E7%B5%90%E5%90%88%E7%B7%B4%E7%BF%92%E5%A4%9A%E7%92%B0%E5%A2%83%E7%8B%80%E6%B3%81/Mon, 06 Nov 2017 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2017/11/ansible-%E8%88%87-vagrant-%E7%B5%90%E5%90%88%E7%B7%B4%E7%BF%92%E5%A4%9A%E7%92%B0%E5%A2%83%E7%8B%80%E6%B3%81/<p>Vagrant <a href="https://www.vagrantup.com/">https://www.vagrantup.com/</a></p> <p>是一個輕量化簡單建置與管理VM的工具</p> <p>不同於VirtualBox，Vagrant沒有圖形介面</p> <p>一切都是文字（console）</p> <p>這也剛好可以用它來開多個不同vm</p> <p>來模擬多個環境下的Ansible play script</p> <p>為什麼不用docker呢？</p> <p>docker 跟實體的VM其實還有一段小小的差距</p> <p>像是我的playbook第一步驟是設定時區</p> <p>結果docker下的centos不能設定時區</p> <p>雖然可以跳過這一步驟</p> <p>但這就失去了測試的意義</p> <p>所以最後決定還是回到VM的懷抱</p>https://blog.iphpo.com/blog/2017/08/ansible-%E5%AE%89%E8%A3%9D%E5%A4%9A%E5%80%8B-package/Fri, 11 Aug 2017 00:00:00 +0800herb09638@gmail.com (Herb)https://blog.iphpo.com/blog/2017/08/ansible-%E5%AE%89%E8%A3%9D%E5%A4%9A%E5%80%8B-package/<p>安裝一個package</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-yaml" data-lang="yaml"><span class="line"><span class="cl">- <span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">install epel</span><span class="w"> </span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">yum</span><span class="p">:</span><span class="w"> </span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l">epel-release</span><span class="w"> </span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">state</span><span class="p">:</span><span class="w"> </span><span class="l">latest</span><span class="w"> </span></span></span><span class="line"><span class="cl"><span class="w"> </span><span class="nt">update_cache</span><span class="p">:</span><span class="w"> </span><span class="kc">yes</span><span class="w"> </span></span></span></code></pre></div><p>安裝多個package</p> <p>不能在name的部分用空格給多個package名稱</p> <p>該怎麼辦呢？</p>