<link href="/user/plugins/datatables/assets/datatables.min.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/markdown-notices/assets/notices.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/form/assets/form-styles.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/simplesearch/css/simplesearch.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/highlight/css/default.css" type="text/css" rel="stylesheet"> <link href="/user/plugins/login/css/login.css" type="text/css" rel="stylesheet"> <link href="/user/themes/imagefactory/css/components.min.css" type="text/css" rel="stylesheet"> <link href="/user/themes/imagefactory/css/otc.css" type="text/css" rel="stylesheet"> <script src="/user/themes/imagefactory/js/jquery.min.js"></script> <script src="/user/plugins/datatables/assets/datatables.min.js"></script> <script src="/user/plugins/highlight/js/highlight.pack.js"></script> <script src="/user/themes/imagefactory/js/components.min.js"></script> <script src="/user/themes/imagefactory/js/totop.js"></script> <script> hljs.initHighlightingOnLoad(); </script>
Brand Claim Brand Claim
<h2>Linux</h2> <p>New Ubuntu image released</p> <ul> <li>Standard_Ubuntu_20.04_latest <ul> <li>support for BMS is planned</li> <li>default login user: ubuntu</li> <li>supported OTC flavors: https://imagefactory.otc.t-systems.com/flavor-list</li> </ul></li> </ul> <h2>GPG key extension of Cloud:OTC repositories on 10th of August 2020</h2> <p>The <strong>CLOUD:OTC</strong> GPG key will be expire in the near future. Some Linux based distributions (except RHEL and SUSE) are affected which are currently using the following GPG key:</p> <pre><code>05a6c49c-5b1ecbbd gpg(Cloud:OTC OBS Project &lt;Cloud:OTC@build.opensuse.org&gt;) pub 2048R/05A6C49C 2018-06-11 Cloud:OTC OBS Project &lt;Cloud:OTC@build.opensuse.org&gt; Key fingerprint = 3EA8 5041 32B7 F1E9 54A9 C0AD A4F6 B298 05A6 C49C</code></pre> <p>The above mentioned GPG key will be extended on the <strong>10th of August 2020</strong>! Afterwards it could happen that just a <strong>notification information</strong> or in certain cases an <strong>error message</strong> is returning by running an update of packages which have been signed with this GPG key.</p> <p>Please <strong>follow only instructions</strong> given down below in case of any <strong>error message</strong> returning to you!</p> <p>In this case Image Factory Team has introduced a package called: <strong>cloud-oty-keyring</strong><br /> It contains <strong>CLOUD:OTC</strong> GPG key and enroll it to our customers automatically.</p> <h3>SUSE - SLES | openSUSE</h3> <p>The GPG key extension and eventually mirroring might take some time for some of the repos and during that time zypper will complain about expiring GPG key. Below is a workaround for SUSE case.</p> <pre><code>zypper --no-gpg-checks &lt;rest of the arguments&gt;</code></pre> <h3>CentOS | EulerOS | OEL</h3> <p>It's necessary to configure two new repositories to being able to install <strong>cloud-otc-keyring</strong> package. </p> <h4>Configure repository URLs for CentOS-6 and OEL-6</h4> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/otc-tools.repo</strong> with the following contents:</p> <pre><code>[otc-tools] name=OTC-CLOUD-Tools-CentOS-6 baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_tools_centos6/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC</code></pre> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/otc-drivers.repo</strong> with the following contents:</p> <pre><code>[otc-drivers] name=OTC-CLOUD-Drivers-CentOS-6 baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_drivers_centos6/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC</code></pre> <h4>Configure repository URLs for CentOS-7, OEL-7 and EulerOS-2.5</h4> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/otc-tools.repo</strong> with the following contents:</p> <pre><code>[otc-tools] name=OTC-CLOUD-Tools-CentOS-7 baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_tools_centos7/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC</code></pre> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/otc-drivers.repo</strong> with the following contents:</p> <pre><code>[otc-drivers] name=OTC-CLOUD-Drivers-CentOS-7 baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_drivers_centos7/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC</code></pre> <h4>Configure repository URLs for CentOS-8 and OEL-8</h4> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/otc-tools.repo</strong> with the following contents:</p> <pre><code>[otc-tools] name=OTC-CLOUD-Tools-CentOS-8 baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_tools_centos8/ gpgcheck=1 enabled=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC</code></pre> <h4>Configure repository URLs for Fedora</h4> <p>To configure the repository on your system create the file <strong>/etc/yum.repos.d/OTC-Fedora.repo</strong> with the following contents:</p> <pre><code>[OTC-build] name=OTC-build baseurl=http://smt01-suse.otc-service.com/repo/RPMMD/otc_fedora30/ gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUD-OTC enabled=1 skip_if_unavailable=True</code></pre> <h4>Install and import new GPG key</h4> <p>If required for e.g. Fedora 30, <strong>yum</strong> command can also be replaced by <strong>dnf</strong> command!</p> <pre><code>$ yum clean all $ yum repolist all $ yum -y --nogpgcheck install cloud-otc-keyring</code></pre> <p>Any further updates or installations out of those two repositories will now work without any issues.</p> <h3>Debian | Ubuntu</h3> <h4>Cleanup home garloff</h4> <p>Older ECS installations may still have the home garloff repository configured.<br /> Since this repository is obsolete and replaced by Cloud OTC Tools, it is strongly recommended to remove any remains of this repository from <em>/etc/apt/sources.list</em> and <em>/etc/apt/sources.list.d/</em>.</p> <h4>Configure repository URL</h4> <p>Please have a look at <a href="http://download.opensuse.org/repositories/Cloud:/OTC:/Tools/">http://download.opensuse.org/repositories/Cloud:/OTC:/Tools/</a> or our local mirror <a href="http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/">http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/</a> to find the correct URL for your distribution and version.<br /> Hint: You can also use a command line browser like w3m to do this.</p> <p>For example the repository URL for Debian 10 is <a href="http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/Debian_10/">http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/Debian_10/</a>.</p> <p>To configure the repository on your system create the file <em>/etc/apt/sources.list.d/cloud-otc.list</em> with the following contents (this example demonstrates Debian 10):</p> <pre><code># otc-tools deb [arch=amd64] http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/Debian_10/ /</code></pre> <h4>Install the apt key</h4> <p>If you would run apt update now, you would get a error message like: "The repository 'http://debmirror.otc-service.com/repositories/Cloud:/OTC:/Tools/Debian_10 Release' is not signed."<br /> To fix this the apt key for the Cloud OTC Tools repository needs to be installed.</p> <p>For this the apt cache needs to be updated ignoring the missing key:</p> <pre><code>$ apt -o Acquire::AllowInsecureRepositories=true update</code></pre> <p>Remove locally added key:</p> <pre><code>$ apt-key --keyring /etc/apt/trusted.gpg del 3EA8504132B7F1E954A9C0ADA4F6B29805A6C49C</code></pre> <p>Then the cloud-otc-keyring package can be installed:</p> <pre><code>$ apt -o Acquire::AllowInsecureRepositories=true update $ apt install --allow-unauthenticated cloud-otc-keyring</code></pre> <p>Now you run apt update, again. It should not show any errors anymore. The repository is now ready and can be used to install and upgrade packages. </p> <p>If the the above steps fail, please run the following commands and rerun the steps above:</p> <pre><code>$ apt clean $ rm /var/lib/apt/lists/*OTC*</code></pre> <h2>Windows</h2> <h3>updated Microsoft Windws Server Images with current Microsoft Windows Server Patches of July 2020 (15th)</h3> <ul> <li> <p>Windows Server 2012 R2</p> <ul> <li>2020-07 Security Monthly Quality Rollup for Windows Server 2012 R2 for x64-based Systems (KB4565541)</li> <li>2020-07 Servicing Stack Update for Windows Server 2012 R2 for x64-based Systems (KB4566425)</li> <li>2020-07 Security Only Update for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 8.1 and Server 2012 R2 for x64 (KB4566468)</li> <li>2020-07 Security Only Quality Update for Windows Server 2012 R2 for x64-based Systems (KB4565540)</li> <li>2020-07 Cumulative Security Update for Internet Explorer 11 for Windows Server 2012 R2 for x64-based systems (KB4565479) </li> </ul> </li> <li> <p>Windows Server 2016</p> <ul> <li>2020-07 Cumulative Update for Windows Server 2016 for x64-based Systems (KB4565511)</li> <li>2020-07 Servicing Stack Update for Windows Server 2016 for x64-based Systems (KB4565912)</li> </ul> </li> <li> <p>Windows Server 2019</p> <ul> <li>2020-07 Servicing Stack Update for Windows Server 2019 for x64-based Systems (KB4558997)</li> <li>2020-07 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Server 2019 for x64 (KB4566516)</li> <li>2020-07 Cumulative Update for Windows Server 2019 for x64-based Systems (KB4558998)</li> </ul> </li> <li> <p>Driver and tools of all Windows Server types</p> <ul> <li>Cloudbase-Init: 0.9.12.dev86</li> <li>XEN GPL driver: 5.0.136.10</li> <li>KVM UVP Vmtools: 2.5.0.156</li> <li>Intel(R) Network Connections Software Version 25.0, January 2, 2020</li> <li>NVIDIA vGPU driver: 370.41 (fixes CVE 2019 5698)</li> <li>NVIDIA pGPU driver: 443.18 (solves CVE 2020 5962, CVE 2020 5963, CVE 2020 5964, CVE 2020 5965, CVE 2020 5966)</li> <li>NVIDIA V100 / T4 driver: 426.72 (fixes CVE 2020 5973)</li> </ul> </li> </ul>