<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Describe-Images on Kenno&#39;s Open Note</title>
    <link>https://blog.khmersite.net/tags/describe-images/</link>
    <description>Recent content in Describe-Images on Kenno&#39;s Open Note</description>
    <image>
      <title>Kenno&#39;s Open Note</title>
      <url>https://blog.khmersite.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://blog.khmersite.net/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.154.0</generator>
    <language>en</language>
    <lastBuildDate>Wed, 15 Nov 2023 23:06:42 +1100</lastBuildDate>
    <atom:link href="https://blog.khmersite.net/tags/describe-images/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>No support for RHEL with high availability in-place upgrade</title>
      <link>https://blog.khmersite.net/p/no-support-for-rhel-with-ha-in-place-upgrade/</link>
      <pubDate>Wed, 15 Nov 2023 23:06:42 +1100</pubDate>
      <guid>https://blog.khmersite.net/p/no-support-for-rhel-with-ha-in-place-upgrade/</guid>
      <description>&lt;p&gt;Well, if you know you know, otherwise, you could have wasted the whole evening trying to upgrade RHEL 7.9 with High Availability to RHEL 8.x, and failed!&lt;/p&gt;
&lt;p&gt;If you read this post, head to the link at [1] and you&amp;rsquo;d see that Red Hat does not support i-place upgrades or rolling-upgrades of cluster nodes from one major release of RHEL to another. Here is an extract from [1]:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Red Hat does not support in-place upgrades or rolling-upgrades of cluster nodes from one major release of RHEL to another. For example, there is no supported method for updating some nodes in a cluster from RHEL 6 to RHEL 7, introducing them into the cluster with existing RHEL 6 nodes to take over resources from them, and then updating the remaining RHEL 6 nodes. Upgrades in major releases of RHEL must be done by migrating services from a running cluster on the old release to another cluster running the new release.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Query Latest Debian 12 AMI Id Using AWS SSM Parameter Store</title>
      <link>https://blog.khmersite.net/p/query-latest-debian-ami-id-using-ssm-parameter-store/</link>
      <pubDate>Sat, 05 Aug 2023 00:24:53 +1000</pubDate>
      <guid>https://blog.khmersite.net/p/query-latest-debian-ami-id-using-ssm-parameter-store/</guid>
      <description>&lt;p&gt;Debian publishes their releases of Amazon Machine Image (AMI) for bookworm at &lt;a href=&#34;https://wiki.debian.org/Cloud/AmazonEC2Image/Bookworm&#34;&gt;Debian bookworm on Amazon EC2&lt;/a&gt; [1]. There, you can find the AMIs for various regions and two architecture &lt;code&gt;amd64&lt;/code&gt; and &lt;code&gt;arm64&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Another way to search for AMI for Debian 12 (bookworm) is to use AWS CLI with &lt;code&gt;describe-images&lt;/code&gt;. Here is an example on how to list the 3 most recent AMIs of Debian 12 (amd64 architecture), sorted by most recent to the oldest:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
