@portrayal/juniper-mx304 0.0.0-stage → 4.0.2

package/mx304.base.right.elements.json

@@ -0,0 +1 @@
+{"components":{},"config":"base","configs":["base","dc","dual-re-ac","hvac-dc","one-re-3lmic-ac"],"device":"mx304","device-version":"4.0.2","elements":[{"box":{"h":88.9,"w":610.0,"x":0.0,"y":0.0},"class":"chassis","id":"chassis-faceplate","parent":null,"path":"chassis"}],"generator":{"tool":"portrayal-render","version":"0.2.0"},"source-sha256":"addb73373079848ba7b6516aca28d190c6aaaed64732666f304304c346bd534e","view":"right","viewBox":[0.0,0.0,610.0,88.9]}

package/mx304.base.right.svg

@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg xmlns="http://www.w3.org/2000/svg" width="610.0mm" height="88.9mm" viewBox="0 0 610.0 88.9" data-device="mx304" data-view="right" data-weight="32 kg fully loaded (two REs, two LMICs); 16 kg without FRUs (Table 22)" data-depth-with-brackets="782 mm over cable-management brackets, air filter and handles (Table 22)" data-throughput="4.8 Tbps system capacity; up to 12x400 Gbps or 48x100 Gbps ports (three LMICs)" data-power-typical-w="1033" data-power-max-w="1436" data-power-envelope="fully-configured" data-operating-temp="0 C to 40 C" data-storage-temp="-40 C to 70 C in shipping container" data-humidity="5-90 percent noncondensing" data-altitude="no performance degradation to 1800 m" data-asic="Juniper Trio 6 (one YT ASIC per LMIC)" data-macsec="inline MACsec on all ports at all speeds" data-timing="1PPS and 10 MHz SMB input and output, ToD and BITS RJ45, GM/PTP SFP (1-GbE/10-GbE); BITS and GM/PTP currently reserved for future use per the guide" data-redundancy="full hardware redundancy - Routing Engines, power supplies and fans" data-eol="none-announced">
+  <style>
+    [data-path] { cursor: pointer; }
+    .state-on    { --led-color: #22c55e; }
+    .state-up    { --led-color: #22c55e; }
+    /* link and up are the same fact on an Ethernet lamp; see docs/rj45-family-design.md */
+    .state-link  { --led-color: #22c55e; }
+    .state-activity { --led-color: #86efac; }
+    .state-ok    { --led-color: #22c55e; }
+    .state-fault { --led-color: #ef4444; }
+    .state-fail  { --led-color: #ef4444; }
+    .state-locate { --led-color: #3b82f6; }
+    .state-absent { opacity: 0.35; }
+    /* A SWITCHED OUTLET WITH NO LAMP is dimmed when it is off, as absent is but
+       less (docs/pdu-model-design.md section 3.2): every switched PDU in the
+       library has a lamp per outlet, and this is the fallback so the first one
+       without does not invent a lamp. An outlet a lamp is bound to by `for:`
+       carries data-lamped (mark_lamped) and is never dimmed: its lamp says it. */
+    [data-class='inlet'][data-states~='off'].state-off:not([data-lamped]) { opacity: 0.55; }
+    /* A state is a colour AND a behaviour. Solid and blinking of the same colour
+       are different facts on real hardware: on the S9510-28DC a solid green PWR
+       is "system power good" and a blinking green PWR is "power good but BMC
+       power fail". A blinking state that renders solid is the same failure as a
+       state class nothing paints - it looks modelled and is not.
+       blink animates opacity rather than fill, because each skin carries its own
+       unlit colour in the fill fallback and a keyframe cannot name it. alternate
+       animates fill, because two colours is the whole point, and takes its first
+       value from the element's own fill. */
+    @keyframes portrayal-blink {
+      0%, 49.9% { opacity: 1; }
+      50%, 100% { opacity: 0; }
+    }
+    @keyframes portrayal-alternate {
+      0%, 49.9% { fill: var(--led-color, #3a3f44); }
+      50%, 100% { fill: var(--led-color-alt, #3a3f44); }
+    }
+    .portrayal-highlight { filter: drop-shadow(0 0 1.2px #f59e0b) drop-shadow(0 0 0.5px #f59e0b); }
+    .portrayal-dim { opacity: 0.25; }
+    [data-class='region'].portrayal-highlight { stroke: #f59e0b; stroke-width: 0.7; filter: none; }
+    .state-fail[data-class='psu'], .state-fail[data-class='fan'] { filter: drop-shadow(0 0 1.4px #ef4444); }
+</style>
+  <metadata>{"device":"Juniper MX304","device-version":"4.0.2","generator":{"tool":"portrayal-render","version":"0.2.0"},"resolved-components":{},"source-sha256":"addb73373079848ba7b6516aca28d190c6aaaed64732666f304304c346bd534e","view":"right"}</metadata>
+  <rect id="chassis-faceplate" data-path="chassis" data-class="chassis" data-model="MX304" x="0" y="0" width="610" height="88.9" rx="1.2" fill="#8b8f94" stroke="#22262a" stroke-width="0.5" />
+  <g id="--decor" data-class="decor">
+    <rect id="plate-0" data-kind="plate" x="0" y="39" width="610" height="11" rx="0.6" fill="#7d8185" />
+  </g>
+</svg>

package/mx304.base.top.elements.json

@@ -0,0 +1 @@
+{"components":{},"config":"base","configs":["base","dc","dual-re-ac","hvac-dc","one-re-3lmic-ac"],"device":"mx304","device-version":"4.0.2","elements":[{"box":{"h":610.0,"w":440.8,"x":0.0,"y":0.0},"class":"chassis","id":"chassis-faceplate","parent":null,"path":"chassis"}],"generator":{"tool":"portrayal-render","version":"0.2.0"},"source-sha256":"addb73373079848ba7b6516aca28d190c6aaaed64732666f304304c346bd534e","view":"top","viewBox":[0.0,0.0,440.8,610.0]}

package/mx304.base.top.svg

@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<svg xmlns="http://www.w3.org/2000/svg" width="440.8mm" height="610.0mm" viewBox="0 0 440.8 610.0" data-device="mx304" data-view="top" data-weight="32 kg fully loaded (two REs, two LMICs); 16 kg without FRUs (Table 22)" data-depth-with-brackets="782 mm over cable-management brackets, air filter and handles (Table 22)" data-throughput="4.8 Tbps system capacity; up to 12x400 Gbps or 48x100 Gbps ports (three LMICs)" data-power-typical-w="1033" data-power-max-w="1436" data-power-envelope="fully-configured" data-operating-temp="0 C to 40 C" data-storage-temp="-40 C to 70 C in shipping container" data-humidity="5-90 percent noncondensing" data-altitude="no performance degradation to 1800 m" data-asic="Juniper Trio 6 (one YT ASIC per LMIC)" data-macsec="inline MACsec on all ports at all speeds" data-timing="1PPS and 10 MHz SMB input and output, ToD and BITS RJ45, GM/PTP SFP (1-GbE/10-GbE); BITS and GM/PTP currently reserved for future use per the guide" data-redundancy="full hardware redundancy - Routing Engines, power supplies and fans" data-eol="none-announced">
+  <style>
+    [data-path] { cursor: pointer; }
+    .state-on    { --led-color: #22c55e; }
+    .state-up    { --led-color: #22c55e; }
+    /* link and up are the same fact on an Ethernet lamp; see docs/rj45-family-design.md */
+    .state-link  { --led-color: #22c55e; }
+    .state-activity { --led-color: #86efac; }
+    .state-ok    { --led-color: #22c55e; }
+    .state-fault { --led-color: #ef4444; }
+    .state-fail  { --led-color: #ef4444; }
+    .state-locate { --led-color: #3b82f6; }
+    .state-absent { opacity: 0.35; }
+    /* A SWITCHED OUTLET WITH NO LAMP is dimmed when it is off, as absent is but
+       less (docs/pdu-model-design.md section 3.2): every switched PDU in the
+       library has a lamp per outlet, and this is the fallback so the first one
+       without does not invent a lamp. An outlet a lamp is bound to by `for:`
+       carries data-lamped (mark_lamped) and is never dimmed: its lamp says it. */
+    [data-class='inlet'][data-states~='off'].state-off:not([data-lamped]) { opacity: 0.55; }
+    /* A state is a colour AND a behaviour. Solid and blinking of the same colour
+       are different facts on real hardware: on the S9510-28DC a solid green PWR
+       is "system power good" and a blinking green PWR is "power good but BMC
+       power fail". A blinking state that renders solid is the same failure as a
+       state class nothing paints - it looks modelled and is not.
+       blink animates opacity rather than fill, because each skin carries its own
+       unlit colour in the fill fallback and a keyframe cannot name it. alternate
+       animates fill, because two colours is the whole point, and takes its first
+       value from the element's own fill. */
+    @keyframes portrayal-blink {
+      0%, 49.9% { opacity: 1; }
+      50%, 100% { opacity: 0; }
+    }
+    @keyframes portrayal-alternate {
+      0%, 49.9% { fill: var(--led-color, #3a3f44); }
+      50%, 100% { fill: var(--led-color-alt, #3a3f44); }
+    }
+    .portrayal-highlight { filter: drop-shadow(0 0 1.2px #f59e0b) drop-shadow(0 0 0.5px #f59e0b); }
+    .portrayal-dim { opacity: 0.25; }
+    [data-class='region'].portrayal-highlight { stroke: #f59e0b; stroke-width: 0.7; filter: none; }
+    .state-fail[data-class='psu'], .state-fail[data-class='fan'] { filter: drop-shadow(0 0 1.4px #ef4444); }
+</style>
+  <metadata>{"device":"Juniper MX304","device-version":"4.0.2","generator":{"tool":"portrayal-render","version":"0.2.0"},"resolved-components":{},"source-sha256":"addb73373079848ba7b6516aca28d190c6aaaed64732666f304304c346bd534e","view":"top"}</metadata>
+  <rect id="chassis-faceplate" data-path="chassis" data-class="chassis" data-model="MX304" x="0" y="0" width="440.8" height="610" rx="1.2" fill="#8b8f94" stroke="#22262a" stroke-width="0.5" />
+  <g id="--decor" data-class="decor">
+    <rect id="plate-0" data-kind="plate" x="0" y="0" width="6" height="610" rx="0.6" fill="#7d8185" />
+    <rect id="plate-1" data-kind="plate" x="434.8" y="0" width="6" height="610" rx="0.6" fill="#7d8185" />
+  </g>
+</svg>