<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Personal Blog</title>
    <link>https://efkan-isazade.com/post/</link>
    <description>Recent content in Posts on Personal Blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Dec 2020 00:00:00 +0000</lastBuildDate><atom:link href="https://efkan-isazade.com/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automating Ubuntu-20.04 live-server template generation with packer vsphere-iso build.</title>
      <link>https://efkan-isazade.com/p/automating-ubuntu-20.04-live-server-template-generation-with-packer-vsphere-iso-build./</link>
      <pubDate>Wed, 23 Dec 2020 00:00:00 +0000</pubDate>
      
      <guid>https://efkan-isazade.com/p/automating-ubuntu-20.04-live-server-template-generation-with-packer-vsphere-iso-build./</guid>
      <description>Update: This setup is only for Ubuntu-20.04 live-server not legacy.
subiquity Subiquity is the Ubuntu server’s new automated installer, which was introduced in 18.04. The setup for autoinstallation is given by the cloud-init configuration. If set, values will be taken from the config file, otherwise default values will be used. There are different ways of delivering cloud-init configuration. User configuration is usually contained in user-data and cloud configuration in meta-data files.</description>
    </item>
    
    <item>
      <title>How to solve VMware ESXI /var partition ramdisk full issue ?</title>
      <link>https://efkan-isazade.com/p/how-to-solve-vmware-esxi-/var-partition-ramdisk-full-issue/</link>
      <pubDate>Mon, 30 Nov 2020 00:00:00 +0000</pubDate>
      
      <guid>https://efkan-isazade.com/p/how-to-solve-vmware-esxi-/var-partition-ramdisk-full-issue/</guid>
      <description>Fixing of the root cause of the runaway log file When the issue was presented, I wasn&amp;rsquo;t able to connect with any terminal app to hosts so, I had to use the host console. And after a while found that the /var/log/EMU/mili/mili2d.log was continually growing. In the vsphere syslog found this error:
1The ramdisk &amp;#39;var&amp;#39; is full. As a result, the file /var/log/EMU/mili/mili2d.log could not be written. Then I looked /var/log/EMU/mili/mili2d.</description>
    </item>
    
    <item>
      <title>Gitlab Container Registry with Minio custom S3 Bucket Part1</title>
      <link>https://efkan-isazade.com/p/gitlab-container-registry-with-minio-custom-s3-bucket-part1/</link>
      <pubDate>Fri, 31 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://efkan-isazade.com/p/gitlab-container-registry-with-minio-custom-s3-bucket-part1/</guid>
      <description>By default there is a setup may or may not enabled gitlab registry in Gitlab Omnibus. In this Post you will learn how to enable it and integrate with Minio S3 bucket. In this Part1 we will install and configure Minio server.
Pre-requisites For this setup we need:
 Gitlab Omnibus Server (ce, ee) Ubuntu 20.04 Server (minimum 4gb ram, 4 cpu, and 250 gb storage) Docker server to test Gitlab container registry Openssl or Letsencrypt for secure connection  Minio installation You can install the Minio server by compiling the source code or via a binary file.</description>
    </item>
    
    <item>
      <title>Gitlab Container Registry with Minio custom S3 Bucket Part2</title>
      <link>https://efkan-isazade.com/p/gitlab-container-registry-with-minio-custom-s3-bucket-part2/</link>
      <pubDate>Fri, 31 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://efkan-isazade.com/p/gitlab-container-registry-with-minio-custom-s3-bucket-part2/</guid>
      <description>In this part we will setup container registry inside self hosted gitlab with Openssl based self genrated ssl. If you wish you can read Part1. Lets get started. First we need generate SSL cert with Openssl in our gitlab server.
Certificate authority (CA) 1openssl req -x509 -nodes -new -sha256 -days 1024 -newkey rsa:2048 -keyout RootCA.key -out RootCA.pem -subj &amp;#34;/C=US/CN=Example-Root-CA&amp;#34; 2openssl x509 -outform pem -in RootCA.pem -out RootCA.crt Example-Root-CA is an example, you can customize the name.</description>
    </item>
    
    <item>
      <title>How to enable MongoDB authentication with docker-compose ?</title>
      <link>https://efkan-isazade.com/p/how-to-enable-mongodb-authentication-with-docker-compose/</link>
      <pubDate>Sat, 25 Jul 2020 00:00:00 +0000</pubDate>
      
      <guid>https://efkan-isazade.com/p/how-to-enable-mongodb-authentication-with-docker-compose/</guid>
      <description>By default there is no authentication in MongoDB. It means that it comes with empty authentication. So we should create users and roles manually. There are lots of ways to create MongoDB docker-compose with authentication. The most popular one of them is to write a bash script with user and roles then use it in docker-compose and another way is to create an init-mongodb.js file with users and roles and use it in docker-compose.</description>
    </item>
    
  </channel>
</rss>
