<?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>Alberto Racca</title>
    <link>https://www.slashopt.it/</link>
    <description>Recent content on Alberto Racca</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 06 Nov 2025 10:24:00 +0100</lastBuildDate>
    <atom:link href="https://www.slashopt.it/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Principal Propagation in cloud foundry</title>
      <link>https://www.slashopt.it/posts/principal-propagation/</link>
      <pubDate>Thu, 06 Nov 2025 10:24:00 +0100</pubDate>
      <guid>https://www.slashopt.it/posts/principal-propagation/</guid>
      <description>&lt;p&gt;In &lt;em&gt;Cloud Foundry&lt;/em&gt;, how to make a request from an application running on a subaccount, to an endpoint handled by another application running on a different subaccount and protected with &lt;em&gt;Roles&lt;/em&gt;&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;official documentation at &lt;a href=&#34;https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/user-propagation-between-cloud-foundry-applications&#34;&gt;https://help.sap.com/docs/connectivity/sap-btp-connectivity-cf/user-propagation-between-cloud-foundry-applications&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;We first need to establish a &lt;em&gt;SAML&lt;/em&gt; trust between account 2 and account 1, and then configure a destination that can propagate the user login from account 1 to account 2
&lt;img loading=&#34;lazy&#34; src=&#34;https://www.slashopt.it/20250702232157.png&#34;&gt;&lt;/p&gt;
&lt;h2 id=&#34;prepare-the-idp-metadata--for-establishing-trust&#34;&gt;Prepare the IdP Metadata  for establishing trust&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;Download the certificate of subaccount 1 by clicking &lt;em&gt;Export&lt;/em&gt; in &lt;em&gt;Connectivity&lt;/em&gt; -&amp;gt; &lt;em&gt;Destination Trust&lt;/em&gt; &lt;img loading=&#34;lazy&#34; src=&#34;https://www.slashopt.it/20250702183626.png&#34;&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;blockquote&gt;
&lt;p&gt;it could be required to generate the trust first &lt;img loading=&#34;lazy&#34; src=&#34;https://www.slashopt.it/20250709101753.png&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>My New Post</title>
      <link>https://www.slashopt.it/posts/test/</link>
      <pubDate>Wed, 30 Jul 2025 12:00:00 +0000</pubDate>
      <guid>https://www.slashopt.it/posts/test/</guid>
      <description>&lt;p&gt;This is my new post using the Hugo PaperMod theme.&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>https://www.slashopt.it/posts/dataflow-write-to-opensql-table/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.slashopt.it/posts/dataflow-write-to-opensql-table/</guid>
      <description>&lt;p&gt;In #SAP #Datasphere, you have the need to write to a table created in the &lt;em&gt;OPENSQL&lt;/em&gt; schema equivalent of the space
By default, datasphere operations like Data flow have &lt;em&gt;Read&lt;/em&gt; only access to the table defined in the &lt;em&gt;OPENSQL&lt;/em&gt; schema&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;see &lt;a href=&#34;https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/7eaa370fe4624dea9f182ee9c9ab645f.html?locale=en-US&#34;&gt;https://help.sap.com/docs/SAP_DATASPHERE/be5967d099974c69b77f4549425ca4c0/7eaa370fe4624dea9f182ee9c9ab645f.html?locale=en-US&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;In order to GRANT &lt;em&gt;Write&lt;/em&gt; access, a procedure &lt;em&gt;GRANT_PRIVILEGE_TO_SPACE&lt;/em&gt; must be run by the &lt;em&gt;OPENSQL&lt;/em&gt;  user&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;running it with the Console user does not return an error, but it does nothing&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>https://www.slashopt.it/posts/kubernetes-install/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.slashopt.it/posts/kubernetes-install/</guid>
      <description>&lt;h1 id=&#34;kubernetes-on-ubuntu2204&#34;&gt;Kubernetes on Ubuntu22.04&lt;/h1&gt;
&lt;p&gt;&lt;a href=&#34;https://www.learnlinux.tv/how-to-build-an-awesome-kubernetes-cluster-using-proxmox-virtual-environment/&#34;&gt;https://www.learnlinux.tv/how-to-build-an-awesome-kubernetes-cluster-using-proxmox-virtual-environment/&lt;/a&gt;&lt;/p&gt;
&lt;h2 id=&#34;system-configuration&#34;&gt;System configuration&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Using #Ubuntu sever 22.04&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code class=&#34;language-sudo&#34; data-lang=&#34;sudo&#34;&gt;&lt;/code&gt;&lt;/pre&gt;&lt;ul&gt;
&lt;li&gt;Create the initial configuration:&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;sudo mkdir /etc/containerd
containerd config default | sudo tee /etc/containerd/config.toml
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;For this #kubernetes cluster to work properly, we’ll need to enable SystemdCgroup within the configuration. To do that, we’ll need to edit the config we’ve just created:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;sudo nano /etc/containerd/config.toml
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Within that file, find the following line of text:&lt;/p&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;[plugins.&amp;#34;io.containerd.grpc.v1.cri&amp;#34;.containerd.runtimes.runc.options]
SystemdCgroup = true
&lt;/code&gt;&lt;/pre&gt;&lt;ul&gt;
&lt;li&gt;Disable swap&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;sudo swapoff -a
&lt;/code&gt;&lt;/pre&gt;&lt;ul&gt;
&lt;li&gt;Enable bridging&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To enable bridging, we only need to edit one config file:&lt;/p&gt;</description>
    </item>
    <item>
      <title></title>
      <link>https://www.slashopt.it/posts/oee/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://www.slashopt.it/posts/oee/</guid>
      <description>&lt;h1 id=&#34;oee&#34;&gt;OEE&lt;/h1&gt;
&lt;h2 id=&#34;calcolo-kpi-riferiti-ad-una-risorsa&#34;&gt;Calcolo KPI riferiti ad una risorsa&lt;/h2&gt;
&lt;p&gt;Qui di seguito le formule per calcolare gli indicatori &lt;strong&gt;Availability&lt;/strong&gt;, &lt;strong&gt;Perfomance&lt;/strong&gt; e &lt;strong&gt;Qualità&lt;/strong&gt; in un turno per una determinata risorsa. Le formule sono comunque generalizzabili per intervalli di tempo diversi ( ad esempio l&amp;rsquo;ora ). E&amp;rsquo; solito usare il turno come campione per analisi storiche, mentre unità più piccole solo per analisi puntali come il turno in corso.&lt;/p&gt;
&lt;h3 id=&#34;availability&#34;&gt;Availability&lt;/h3&gt;
&lt;p&gt;L&amp;rsquo;indicatore &lt;strong&gt;Availability&lt;/strong&gt; è determinato dal rapporto della disponibilità &lt;em&gt;effettiva&lt;/em&gt; di una risorsa a produrre rispetto al tempo &lt;em&gt;previsto&lt;/em&gt;
Abbiamo quindi a numeratore la durata del turno ridotta di tutti i fermi ( ossia tutto il tempo in cui la macchina era disponibile ), mentre a denominatore la durata del turno ridotta dei fermi pianificati&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
