This commit is contained in:
forgejo-actions 2026-10-26 22:29:20 +00:00
commit 567a7d6dc9
38 changed files with 1165 additions and 34 deletions

View file

@ -669,6 +669,7 @@ window.runMermaid = runMermaid;</script>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>
@ -354,6 +355,7 @@
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#bascule-d-un-backend-a-l-autre">Bascule d’un backend à l’autre</a></li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#relais-dns-et-ntp">Relais DNS et NTP</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#watchdog">Watchdog</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#journalisation">Journalisation</a></li>
</ul>
@ -633,6 +635,29 @@ dernière qui conditionne le provisionnement cloud-init.</p></li>
l’autre.</p>
</section>
</section>
<section id="relais-dns-et-ntp">
<h2>Relais DNS et NTP<a class="headerlink" href="#relais-dns-et-ntp" title="Lien vers cette rubrique">#</a></h2>
<div class="highlight-yaml notranslate"><div class="highlight"><pre><span></span><span class="nt">hostsvc</span><span class="p">:</span>
<span class="w"> </span><span class="nt">dns_upstream</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span>
<span class="w"> </span><span class="nt">ntp_upstream</span><span class="p">:</span><span class="w"> </span><span class="p p-Indicator">[]</span>
<span class="w"> </span><span class="nt">rate_limit_per_vpc</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">100</span>
</pre></div>
</div>
<p>Lue par <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code> (voir <a class="reference internal" href="../concepts/dns-ntp.html"><span class="doc">DNS et NTP des VM</span></a>), au démarrage du service.</p>
<dl class="simple">
<dt><code class="docutils literal notranslate"><span class="pre">dns_upstream</span></code></dt><dd><p>résolveurs interrogés en premier, sous la forme <code class="docutils literal notranslate"><span class="pre">ip</span></code> ou <code class="docutils literal notranslate"><span class="pre">ip:port</span></code> (port 53 par défaut).
Ceux de <code class="docutils literal notranslate"><span class="pre">/etc/resolv.conf</span></code> de l’hôte viennent ensuite ; liste vide : l’hôte seul.</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">ntp_upstream</span></code></dt><dd><p>serveurs NTP relayés en premier, <code class="docutils literal notranslate"><span class="pre">ip</span></code> ou <code class="docutils literal notranslate"><span class="pre">ip:port</span></code> (port 123 par défaut). Sans serveur ou
sans réponse, l’horloge de l’hôte répond.</p>
</dd>
<dt><code class="docutils literal notranslate"><span class="pre">rate_limit_per_vpc</span></code></dt><dd><p>requêtes par seconde, DNS et NTP confondus, pour chaque VPC.</p>
</dd>
</dl>
<p>Un nom d’hôte, un port hors de 1–65535 ou une limite nulle ou négative font échouer le
démarrage de l’agent comme de <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code>, qui lisent le même fichier. Une modification prend
effet au redémarrage de <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code>.</p>
</section>
<section id="watchdog">
<h2>Watchdog<a class="headerlink" href="#watchdog" title="Lien vers cette rubrique">#</a></h2>
<div class="highlight-yaml notranslate"><div class="highlight"><pre><span></span><span class="nt">watchdog</span><span class="p">:</span>
@ -711,6 +736,7 @@ l’autre.</p>
<li class="toc-h3 nav-item toc-entry"><a class="reference internal nav-link" href="#bascule-d-un-backend-a-l-autre">Bascule d’un backend à l’autre</a></li>
</ul>
</li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#relais-dns-et-ntp">Relais DNS et NTP</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#watchdog">Watchdog</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#journalisation">Journalisation</a></li>
</ul>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>
@ -349,6 +350,7 @@
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#une-vm-n-arrive-pas-a-emettre-certaines-trames">Une VM n’arrive pas à émettre certaines trames</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-a-une-adresse-mais-cloud-init-n-applique-rien">La VM a une adresse mais cloud-init n’applique rien</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-user-data-est-servi-vide">Le user-data est servi vide</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-resout-pas-les-noms-ou-n-a-pas-l-heure">La VM ne résout pas les noms ou n’a pas l’heure</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-demarre-pas-uefi">La VM ne démarre pas (UEFI)</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-delete-renvoie-409">Le <code class="docutils literal notranslate"><span class="pre">DELETE</span></code> renvoie 409</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-base-et-le-systeme-ont-diverge">La base et le système ont divergé</a></li>
@ -497,6 +499,38 @@ réellement écrit :</p>
</div>
<p>Un base64 invalide, lui, aurait été rejeté en 400 à la création.</p>
</section>
<section id="la-vm-ne-resout-pas-les-noms-ou-n-a-pas-l-heure">
<h2>La VM ne résout pas les noms ou n’a pas l’heure<a class="headerlink" href="#la-vm-ne-resout-pas-les-noms-ou-n-a-pas-l-heure" title="Lien vers cette rubrique">#</a></h2>
<p>La VM interroge sa gateway (<code class="docutils literal notranslate"><span class="pre">interface_ip</span></code>), que le DHCP annonce en DNS et en NTP ; la requête
est redirigée vers <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code> dans le netns du VPC (voir <a class="reference internal" href="../concepts/dns-ntp.html"><span class="doc">DNS et NTP des VM</span></a>).</p>
<div class="highlight-bash notranslate"><div class="highlight"><pre><span></span><span class="c1"># Dans la VM : DNS et NTP annoncés par le bail (systemd-networkd)</span>
sudo<span class="w"> </span>cat<span class="w"> </span>/run/systemd/netif/leases/<span class="k">$(</span>cat<span class="w"> </span>/sys/class/net/ens3/ifindex<span class="k">)</span><span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span>-E<span class="w"> </span><span class="s1">'^(DNS|NTP)='</span>
<span class="c1"># Sur l'hyperviseur</span>
systemctl<span class="w"> </span>status<span class="w"> </span>two-hostsvc
cat<span class="w"> </span>/run/two/hostsvc/hostsvc.state<span class="w"> </span><span class="c1"># le VPC doit y figurer</span>
ip<span class="w"> </span>-n<span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>-4<span class="w"> </span>addr<span class="w"> </span>show<span class="w"> </span>dev<span class="w"> </span>hostsvc<span class="w"> </span><span class="c1"># 169.254.169.253/32</span>
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>iptables<span class="w"> </span>-t<span class="w"> </span>nat<span class="w"> </span>-S<span class="w"> </span>TWO-HOSTSVC<span class="w"> </span><span class="c1"># 2 RETURN puis 3 DNAT</span>
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>iptables<span class="w"> </span>-t<span class="w"> </span>nat<span class="w"> </span>-L<span class="w"> </span>TWO-HOSTSVC<span class="w"> </span>-v<span class="w"> </span>-n<span class="w"> </span><span class="c1"># compteurs des redirections</span>
ip<span class="w"> </span>netns<span class="w"> </span><span class="nb">exec</span><span class="w"> </span>&lt;vpc&gt;<span class="w"> </span>ss<span class="w"> </span>-lntu<span class="w"> </span><span class="p">|</span><span class="w"> </span>grep<span class="w"> </span><span class="m">169</span>.254.169.253<span class="w"> </span><span class="c1"># 53/udp, 53/tcp, 123/udp</span>
journalctl<span class="w"> </span>-u<span class="w"> </span>two-hostsvc<span class="w"> </span>-n<span class="w"> </span><span class="m">50</span>
</pre></div>
</div>
<p>Causes rencontrées :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code> arrêté : plus de DNS ni de NTP pour aucun VPC de l’hyperviseur, et un VPC créé
pendant ce temps part en <code class="docutils literal notranslate"><span class="pre">error</span></code> ;</p></li>
<li><p>adresse <code class="docutils literal notranslate"><span class="pre">169.254.169.253</span></code> ou règle de la chaîne retirée à la main : la requête n’arrive plus
au relais ; le watchdog le signale ;</p></li>
<li><p>VPC créé par une version antérieure à la 0.3.0 : ni <code class="docutils literal notranslate"><span class="pre">dummy</span></code> ni chaîne ni socket. Le recréer ;</p></li>
<li><p><code class="docutils literal notranslate"><span class="pre">open</span></code> refusé par <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code> avec <code class="docutils literal notranslate"><span class="pre">permission</span> <span class="pre">denied</span></code> ou <code class="docutils literal notranslate"><span class="pre">invalid</span> <span class="pre">argument</span></code> sur
<code class="docutils literal notranslate"><span class="pre">/var/run/netns/&lt;vpc&gt;</span></code> : l’unit n’a pas <code class="docutils literal notranslate"><span class="pre">CAP_DAC_READ_SEARCH</span></code>, ou le netns, créé après le
démarrage du service, ne lui est pas visible parce que <code class="docutils literal notranslate"><span class="pre">/</span></code> n’est pas en propagation
<code class="docutils literal notranslate"><span class="pre">shared</span></code> (<code class="docutils literal notranslate"><span class="pre">findmnt</span> <span class="pre">-no</span> <span class="pre">PROPAGATION</span> <span class="pre">/</span></code>). Rencontré en conteneur, pas sur un hyperviseur.</p></li>
</ul>
<p>Sans serveur <code class="docutils literal notranslate"><span class="pre">ntp_upstream</span></code> qui réponde, l’heure vient de l’horloge de l’hyperviseur : si
celle-ci n’est pas synchronisée, la réponse porte l’indicateur d’alarme et la VM l’ignore.</p>
</section>
<section id="la-vm-ne-demarre-pas-uefi">
<h2>La VM ne démarre pas (UEFI)<a class="headerlink" href="#la-vm-ne-demarre-pas-uefi" title="Lien vers cette rubrique">#</a></h2>
<p><code class="docutils literal notranslate"><span class="pre">uefi:</span> <span class="pre">true</span></code> exige les fichiers OVMF déclarés dans la configuration :</p>
@ -585,6 +619,7 @@ l’agent n’est plus piloté par lui.</p>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#une-vm-n-arrive-pas-a-emettre-certaines-trames">Une VM n’arrive pas à émettre certaines trames</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-a-une-adresse-mais-cloud-init-n-applique-rien">La VM a une adresse mais cloud-init n’applique rien</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-user-data-est-servi-vide">Le user-data est servi vide</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-resout-pas-les-noms-ou-n-a-pas-l-heure">La VM ne résout pas les noms ou n’a pas l’heure</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-vm-ne-demarre-pas-uefi">La VM ne démarre pas (UEFI)</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#le-delete-renvoie-409">Le <code class="docutils literal notranslate"><span class="pre">DELETE</span></code> renvoie 409</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#la-base-et-le-systeme-ont-diverge">La base et le système ont divergé</a></li>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>
@ -405,6 +406,16 @@ de VM et la réponse des units systemd associées, ainsi que le <strong>segment
public (<code class="docutils literal notranslate"><span class="pre">interfaces.internet</span></code>) doit exister, être actif et porter un port VXLAN
(<code class="docutils literal notranslate"><span class="pre">vxlan-public</span></code>), sinon les VPC de l’hôte n’ont pas de segment public. Il ne vérifie pas le
numéro du VNI.</p>
<p>Dès qu’un VPC est <code class="docutils literal notranslate"><span class="pre">running</span></code> sur l’hyperviseur, il contrôle aussi le relais DNS et NTP (voir
<a class="reference internal" href="../concepts/dns-ntp.html"><span class="doc">DNS et NTP des VM</span></a>) :</p>
<ul class="simple">
<li><p><code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code> injoignable sur sa socket de contrôle : une notification, aucun VPC de
l’hyperviseur n’a plus de DNS ni de NTP ;</p></li>
<li><p>pour chaque VPC <code class="docutils literal notranslate"><span class="pre">running</span></code> : VPC absent de la liste servie par <code class="docutils literal notranslate"><span class="pre">two-hostsvc</span></code>,
<code class="docutils literal notranslate"><span class="pre">169.254.169.253</span></code> absente de la <code class="docutils literal notranslate"><span class="pre">dummy</span></code> <code class="docutils literal notranslate"><span class="pre">hostsvc</span></code>, ou chaîne <code class="docutils literal notranslate"><span class="pre">TWO-HOSTSVC</span></code> absente ou
incomplète dans son netns. Un VPC créé par une version antérieure à la 0.3.0 n’a rien de tout
cela : il est signalé à chaque tick jusqu’à sa recréation.</p></li>
</ul>
<p>Avec une section <code class="docutils literal notranslate"><span class="pre">bgp</span></code> dans la configuration, il contrôle aussi le plan de contrôle :</p>
<ul class="simple">
<li><p><strong>Sessions BGP</strong> : une notification par route reflector dont la session n’est pas

View file

@ -233,6 +233,7 @@
<li class="toctree-l2"><a class="reference internal" href="../concepts/modes-reseau.html">Modes réseau</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/cycle-de-vie.html">Cycle de vie des ressources</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/metadata-cloud-init.html">Metadata et cloud-init</a></li>
<li class="toctree-l2"><a class="reference internal" href="../concepts/dns-ntp.html">DNS et NTP des VM</a></li>
</ul>
</details></li>
<li class="toctree-l1 has-children"><a class="reference internal" href="../architecture/index.html">Architecture</a><details><summary><span class="toctree-toggle" role="presentation"><i class="fa-solid fa-chevron-down"></i></span></summary><ul>
@ -345,6 +346,7 @@
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#dnsmasq">dnsmasq</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#serveur-dhcp-integre">Serveur DHCP intégré</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#relais-dns-et-ntp">Relais DNS et NTP</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#qemu-n-est-pas-une-unit">QEMU n’est pas une unit</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#sockets-par-vm">Sockets par VM</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#arret-de-l-agent">Arrêt de l’agent</a></li>
@ -362,7 +364,7 @@
<section id="services-systemd">
<h1>Services systemd<a class="headerlink" href="#services-systemd" title="Lien vers cette rubrique">#</a></h1>
<p>Quatre units, installées dans <code class="docutils literal notranslate"><span class="pre">/etc/systemd/system</span></code> par <code class="docutils literal notranslate"><span class="pre">deploy.sh</span></code> ; les binaires et scripts
<p>Cinq units, installées dans <code class="docutils literal notranslate"><span class="pre">/etc/systemd/system</span></code> par <code class="docutils literal notranslate"><span class="pre">deploy.sh</span></code> ; les binaires et scripts
qu’elles lancent sont sous <code class="docutils literal notranslate"><span class="pre">/opt/two/bin</span></code>. Les deux units DHCP
s’excluent : celle qui tourne dépend de <code class="docutils literal notranslate"><span class="pre">dhcp.backend</span></code> (voir <a class="reference internal" href="configuration.html"><span class="doc">Configuration</span></a>).</p>
<div class="pst-scrollable-table-container"><table class="table">
@ -394,6 +396,11 @@ s’excluent : celle qui tourne dépend de <code class="docutils literal notrans
<td><p><code class="docutils literal notranslate"><span class="pre">&lt;nom</span> <span class="pre">de</span> <span class="pre">la</span> <span class="pre">VM&gt;</span></code></p></td>
<td><p>serveur de metadata cloud-init, un par VM</p></td>
</tr>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">two-hostsvc.service</span></code></p></td>
<td><p>—</p></td>
<td><p>relais DNS et NTP des VM, un par hyperviseur, démarré avant l’agent (voir
<a class="reference internal" href="../concepts/dns-ntp.html"><span class="doc">DNS et NTP des VM</span></a>)</p></td>
</tr>
</tbody>
</table>
</div>
@ -403,6 +410,7 @@ n’y a pas à les démarrer à la main en fonctionnement normal.</p>
systemctl<span class="w"> </span>status<span class="w"> </span><span class="s1">'dnsmasq@vp-admin_br-000001'</span><span class="w"> </span><span class="c1"># backend dnsmasq</span>
systemctl<span class="w"> </span>status<span class="w"> </span><span class="s1">'dhcp@vp-admin_br-000001'</span><span class="w"> </span><span class="c1"># backend two</span>
systemctl<span class="w"> </span>status<span class="w"> </span><span class="s1">'metadata@i-web'</span>
systemctl<span class="w"> </span>status<span class="w"> </span>two-hostsvc
</pre></div>
</div>
<section id="dnsmasq">
@ -475,6 +483,33 @@ socket UDP. À la suppression du subnet, l’agent retire aussi la socket, pour
processus serait mort sans nettoyer (<code class="docutils literal notranslate"><span class="pre">SIGKILL</span></code>, plantage).</p>
<p>Diagnostic : voir <a class="reference internal" href="diagnostic.html"><span class="doc">Diagnostic</span></a>, qui montre comment interroger la socket.</p>
</section>
<section id="relais-dns-et-ntp">
<h2>Relais DNS et NTP<a class="headerlink" href="#relais-dns-et-ntp" title="Lien vers cette rubrique">#</a></h2>
<p><code class="docutils literal notranslate"><span class="pre">two-hostsvc.service</span></code> lance <code class="docutils literal notranslate"><span class="pre">/opt/two/bin/two-hostsvc</span></code>, un seul processus par hyperviseur,
qui sert DNS et NTP aux VM de tous les VPC (voir <a class="reference internal" href="../concepts/dns-ntp.html"><span class="doc">DNS et NTP des VM</span></a>). Il lit la section
<code class="docutils literal notranslate"><span class="pre">hostsvc</span></code> de <code class="docutils literal notranslate"><span class="pre">/etc/two/agent.yml</span></code> (voir <a class="reference internal" href="configuration.html"><span class="doc">Configuration</span></a>).</p>
<div class="pst-scrollable-table-container"><table class="table">
<colgroup>
<col style="width: 40.0%" />
<col style="width: 60.0%" />
</colgroup>
<tbody>
<tr class="row-odd"><td><p>Socket de contrôle</p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">/run/two/hostsvc/hostsvc.sock</span></code></p></td>
</tr>
<tr class="row-even"><td><p>État</p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">/run/two/hostsvc/hostsvc.state</span></code> (VPC servis)</p></td>
</tr>
<tr class="row-odd"><td><p>Journal</p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">journalctl</span> <span class="pre">-u</span> <span class="pre">two-hostsvc</span></code></p></td>
</tr>
</tbody>
</table>
</div>
<p>L’unit démarre avant <code class="docutils literal notranslate"><span class="pre">agent.service</span></code> et se relance en cas d’échec. Son répertoire
<code class="docutils literal notranslate"><span class="pre">/run/two/hostsvc</span></code> survit à un redémarrage du service : le processus y relit la liste des VPC
servis et rouvre leurs sockets. Un VPC ne peut pas être créé tant que le service ne répond pas.</p>
</section>
<section id="qemu-n-est-pas-une-unit">
<h2>QEMU n’est pas une unit<a class="headerlink" href="#qemu-n-est-pas-une-unit" title="Lien vers cette rubrique">#</a></h2>
<p>Les processus QEMU sont lancés par <code class="docutils literal notranslate"><span class="pre">systemd-run</span> <span class="pre">--scope</span></code>, <strong>jamais</strong> en unit transitoire. Un
@ -563,6 +598,7 @@ les services à la main avant de lancer le script fait perdre cette liste.</p>
<ul class="visible nav section-nav flex-column">
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#dnsmasq">dnsmasq</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#serveur-dhcp-integre">Serveur DHCP intégré</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#relais-dns-et-ntp">Relais DNS et NTP</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#qemu-n-est-pas-une-unit">QEMU n’est pas une unit</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#sockets-par-vm">Sockets par VM</a></li>
<li class="toc-h2 nav-item toc-entry"><a class="reference internal nav-link" href="#arret-de-l-agent">Arrêt de l’agent</a></li>