openSUSE Project Management Tool: Issueshttps://progress.opensuse.org/https://progress.opensuse.org/themes/openSUSE/favicon/favicon.ico?15829177842024-01-16T19:46:19ZopenSUSE Project Management Tool
Redmine QA - action #153703 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - voyagerhttps://progress.opensuse.org/issues/1537032024-01-16T19:46:19Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> voyager is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3742" class="external">https://jira.suse.com/browse/ENGINFRA-3742</a></li>
<li>Ensure machine can be reached</li>
<li>Ensure machine is used as in before migration</li>
<li>look into <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: Prepare DHCP/DNS for machines coming to qe.prg2.suse.org based on former qam.suse.de entries size:M (Resolved)" href="https://progress.opensuse.org/issues/153799#note-12">#153799-12</a> and ensure that each VM has valid DHCP/DNS entries</li>
</ul>
QA - action #153700 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - arm4https://progress.opensuse.org/issues/1537002024-01-16T19:45:30Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> arm4 is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3741" class="external">https://jira.suse.com/browse/ENGINFRA-3741</a></li>
<li>Ensure machine can be reached</li>
<li>Ensure machine is used as in before migration</li>
</ul>
QA - action #153697 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - sauronhttps://progress.opensuse.org/issues/1536972024-01-16T19:44:36Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> sauron is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3733" class="external">https://jira.suse.com/browse/ENGINFRA-3733</a></li>
<li>Ensure machine can be reached</li>
<li>Ensure machine is used as in before migration</li>
</ul>
QA - action #153694 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - fibonaccihttps://progress.opensuse.org/issues/1536942024-01-16T19:43:46Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> fibonacci is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3740" class="external">https://jira.suse.com/browse/ENGINFRA-3740</a></li>
<li>Ensure machine can be reached</li>
<li>Ensure machine is used as in before migration</li>
</ul>
QA - action #153691 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - openqaw5-xenhttps://progress.opensuse.org/issues/1536912024-01-16T19:42:12Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> openqaw5-xen is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3739" class="external">https://jira.suse.com/browse/ENGINFRA-3739</a></li>
<li>Update openQA salt pillars</li>
<li>Ensure machine can be reached</li>
<li>Ensure openQA tests using the machine are successful</li>
</ul>
QA - action #153688 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - openqaw9-hypervhttps://progress.opensuse.org/issues/1536882024-01-16T19:40:46Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> openqaw9-hyperv is usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3738" class="external">https://jira.suse.com/browse/ENGINFRA-3738</a></li>
<li>Update openQA salt pillars</li>
<li>Ensure machine can be reached</li>
<li>Ensure openQA tests using the machine are successful</li>
</ul>
QA - action #153682 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - quinn size:Mhttps://progress.opensuse.org/issues/1536822024-01-16T19:29:20Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> quinn is usable from PRG2e, i.e. as bare-metal test machine in OSD</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li><em>DONE</em> Follow <a href="https://jira.suse.com/browse/ENGINFRA-3737" class="external">https://jira.suse.com/browse/ENGINFRA-3737</a></li>
<li>Follow what has been done in <a class="issue tracker-4 status-3 priority-4 priority-default closed child" title="action: Move of selected LSG QE machines NUE1 to PRG2e - fozzie size:M (Resolved)" href="https://progress.opensuse.org/issues/153670">#153670</a></li>
<li>Ensure PXE boot works, possibly same as #155521, simply add next_server config in OPS-Service/salt</li>
<li>Update openQA salt pillars</li>
<li>Ensure machine can be reached</li>
<li>Ensure openQA bare-metal tests using the machine are successful</li>
</ul>
QA - action #153679 (Blocked): Move of selected LSG QE machines NUE1 to PRG2e - andromedahttps://progress.opensuse.org/issues/1536792024-01-16T19:25:11Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> andromeda usable from PRG2</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3736" class="external">https://jira.suse.com/browse/ENGINFRA-3736</a></li>
<li>Ensure machine can be reached from o3</li>
<li>Coordinate with QAC to make use of andromeda</li>
</ul>
QA - action #153673 (Blocked): Move of selected LSG QE machines NUE1 to PRG2e - orionhttps://progress.opensuse.org/issues/1536732024-01-16T19:24:07Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> orion usable from PRG2</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Follow <a href="https://jira.suse.com/browse/ENGINFRA-3735" class="external">https://jira.suse.com/browse/ENGINFRA-3735</a></li>
<li>Ensure machine can be reached from o3</li>
<li>Coordinate with QAC to make use of orion</li>
</ul>
QA - action #153670 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e - fozzie size:Mhttps://progress.opensuse.org/issues/1536702024-01-16T19:21:24Zokurzokurz@suse.com
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> fozzie is usable from PRG2e, i.e. as bare-metal test machine in OSD</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li><em>DONE</em> Follow <a href="https://jira.suse.com/browse/ENGINFRA-3734" class="external">https://jira.suse.com/browse/ENGINFRA-3734</a></li>
<li>Ensure PXE boot works, possibly same as #155521, simply add next_server config in OPS-Service/salt</li>
<li>Update openQA salt pillars</li>
<li>Ensure machine can be reached</li>
<li>Ensure openQA bare-metal tests using the machine are successful</li>
</ul>
QA - action #132623 (Resolved): Decommissioning of selected selected LSQ QE machines from NUE1-SRV2https://progress.opensuse.org/issues/1326232023-07-12T15:08:37Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>NUE1 needs to be emptied. For some machines we opted to dcommission them as soon as replacement services are in place from other datacenters. Assuming nobody does the job for us we need to unrack and organize the decommissioning with Facilities and/or SUSE-IT.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> All machines from <a href="https://netbox.suse.de/dcim/devices/?tag=qe-lsg&tag=to-be-decommissioned" class="external">https://netbox.suse.de/dcim/devices/?tag=qe-lsg&tag=to-be-decommissioned</a> are physically gone</li>
<li><strong>AC2:</strong> inventory management is up-to-date</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Ask hreinecke and SUSE-IT and wengel and others how this decommissioning is organized</li>
<li>Wait for all other services relying on those machines to be served from elsewhere, e.g. no production machine still needing qanet</li>
<li>As necessary: Go to NUE1 Maxtorhof place beforehand and prepare the decommissioning, e.g. nothing connected anymore, put on pallet, labeled, packed into boxes, etc.</li>
<li>Inform users about the pending decommissioning</li>
<li>Follow <a href="https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs#How_to_decommission_and_dispose_old_hardware" class="external">https://wiki.suse.net/index.php/SUSE-Quality_Assurance/Labs#How_to_decommission_and_dispose_old_hardware</a></li>
<li>Ensure documentation is up-to-date</li>
</ul>
QA - action #132617 (Resolved): Move of selected LSG QE machines NUE1 to PRG2e size:Mhttps://progress.opensuse.org/issues/1326172023-07-12T15:00:01Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>NUE1 needs to be emptied. For some machines we opted to have them moved to "PRG2e" aka. "PRG2 Colo Extension" or similar. Assuming nobody does the job for us we need to unrack and organize the move with Facilities and SUSE-IT.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> All machines from <a href="https://netbox.suse.de/dcim/devices/?tag=qe-lsg&tag=move-to-prague-colo2" class="external">https://netbox.suse.de/dcim/devices/?tag=qe-lsg&tag=move-to-prague-colo2</a> are usable from PRG2e</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Ask hreinecke and SUSE-IT and wengel and others how this move is organized</li>
<li>As necessary organize transport of equipment: Create ticket over <a href="https://sd.suse.com" class="external">https://sd.suse.com</a> to component "Facilities" asking them how and where to prepare machines for move and ask them to move the equipment to FC Basement</li>
<li>As necessary: Go to NUE1 Maxtorhof place beforehand and prepare the move, e.g. nothing connected anymore, put on pallet, labeled, packed into boxes, etc.</li>
<li>Inform users about the pending move</li>
<li>Ensure machines are usable from PRG2e</li>
<li>Ensure documentation is up-to-date</li>
<li>Inform users after everything is done</li>
</ul>
<a name="Rollback-steps"></a>
<h2 >Rollback steps<a href="#Rollback-steps" class="wiki-anchor">¶</a></h2>
<p>Remove alert silence from <a href="https://monitor.qa.suse.de/alerting/silences" class="external">https://monitor.qa.suse.de/alerting/silences</a> with <code>alertname=openqaw5-xen: host up alert</code></p>
QA - coordination #130955 (Resolved): [epic] Migration out of SUSE NUE1 - QE setup in NUE3https://progress.opensuse.org/issues/1309552023-06-15T11:47:31Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>SUSE is deprecating NUE1 (Maxtorhof) and setting up replacement data centers. Primary location for production services will be PRG2 "Prg CoLo", see <a class="issue tracker-6 status-15 priority-5 priority-high3 parent behind-schedule" title="coordination: [saga][epic] Migration to QE setup in PRG2+NUE3 while ensuring availability (Blocked)" href="https://progress.opensuse.org/issues/121720">#121720</a>. Additionally a new datacenter is planned as fail-over location</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> NUE1 (Maxtorhof) is not relied upon by SUSE QE Tools anymore</li>
<li><strong>AC2:</strong> Relevant SUSE QE Tools services are provided out of NUE3</li>
</ul>
<a name="Further-details"></a>
<h2 >Further details<a href="#Further-details" class="wiki-anchor">¶</a></h2>
<p>Coordination chat room <a href="https://suse.slack.com/archives/C04MDKHQE20" class="external">#dct-migration</a></p>
openQA Infrastructure - action #123226 (New): Temperature monitoring in SUSE QE lab size:Mhttps://progress.opensuse.org/issues/1232262023-01-17T10:20:58Zokurzokurz@suse.com
<a name="Motivation"></a>
<h2 >Motivation<a href="#Motivation" class="wiki-anchor">¶</a></h2>
<p>We moved into Nbg Maxtorhof 2.2.14 assuming there would be proper temperature monitoring already but apparently that was not the case as shown by <a class="issue tracker-4 status-3 priority-5 priority-high3 closed" title="action: A/C broken in TAM lab size:M (Resolved)" href="https://progress.opensuse.org/issues/123028">#123028</a> when an A/C issue showed up and nobody realized the high room temperatures. So we should implement a simple temperature monitoring and alerting, e.g. based on the old QA room setup.</p>
<a name="Acceptance-criteria"></a>
<h2 >Acceptance criteria<a href="#Acceptance-criteria" class="wiki-anchor">¶</a></h2>
<ul>
<li><strong>AC1:</strong> The SUSE QE tools team is alerted about abnormal temperatures in Nbg Maxtorhof 2.2.14</li>
<li><strong>AC2:</strong> A graph showing temperature over time is available to multiple people</li>
</ul>
<a name="Suggestions"></a>
<h2 >Suggestions<a href="#Suggestions" class="wiki-anchor">¶</a></h2>
<ul>
<li>Try to use the temperature monitoring equipment we already had for the old QA lab and repurpose in Nbg Maxtorhof 2.2.14</li>
<li>Alternatively just buy and expense new monitoring devices</li>
<li>Check where the data should end up</li>
<li>Ensure that there is alerting, e.g. to <a href="mailto:osd-admins@suse.de">osd-admins@suse.de</a> or <a href="mailto:qa-team@suse.de">qa-team@suse.de</a> or grafana or a chat channel</li>
<li>Optional: Integrate in <a href="https://monitor.qa.suse.de" class="external">https://monitor.qa.suse.de</a></li>
</ul>
QA - coordination #37910 (Resolved): [tools][epic] Migration of or away from qanet.qa.suse.dehttps://progress.opensuse.org/issues/379102018-06-27T10:05:28Znicksingernsinger@suse.com
<p>qanet is an SLES11SP0 and needs a newer replacement to be safe for the future.</p>
<hr>
<a name="Replacement-hardware"></a>
<h1 >Replacement hardware<a href="#Replacement-hardware" class="wiki-anchor">¶</a></h1>
<a name="1-Physical-machine"></a>
<h2 >1. Physical machine<a href="#1-Physical-machine" class="wiki-anchor">¶</a></h2>
<a name="General-advantages"></a>
<h3 >General advantages:<a href="#General-advantages" class="wiki-anchor">¶</a></h3>
<ul>
<li>Potentially less problems then a virtualized machine (less layers -> less problems (especially in the network world))</li>
</ul>
<a name="General-disadvantages"></a>
<h3 >General disadvantages:<a href="#General-disadvantages" class="wiki-anchor">¶</a></h3>
<ul>
<li>Less flexible then a virtual machine</li>
</ul>
<a name="11-Use-the-same-machine-as-qanet-runs-on"></a>
<h3 >1.1. Use the same machine as qanet runs on<a href="#11-Use-the-same-machine-as-qanet-runs-on" class="wiki-anchor">¶</a></h3>
<a name="Advantages"></a>
<h4 >Advantages:<a href="#Advantages" class="wiki-anchor">¶</a></h4>
<ul>
<li>No new hardware needed</li>
<li>qanet is a quad core with 6GB of RAM -> More then sufficient for a network management server</li>
</ul>
<a name="Disadvantages"></a>
<h4 >Disadvantages:<a href="#Disadvantages" class="wiki-anchor">¶</a></h4>
<ul>
<li>Downtime for the whole network while migrating</li>
<li>In-place upgrade from SLE11 up to SLE15 might render the system unusable and then requires a re-installation</li>
<li>No (fast) way back in case of major issues after upgrading</li>
<li>Hardware of the server is long out-of-service</li>
</ul>
<a name="12-Buy-new-hardware"></a>
<h3 >1.2. Buy new hardware<a href="#12-Buy-new-hardware" class="wiki-anchor">¶</a></h3>
<a name="Advantages-2"></a>
<h4 >Advantages:<a href="#Advantages-2" class="wiki-anchor">¶</a></h4>
<ul>
<li>Parallel setup with already running qanet possible</li>
<li>After initial setup and migration, a fail-over setup is possible</li>
<li>Fallback in case of major issues after migration should be easily possible (unplug new, plugin old)</li>
<li>Hardware service for at least 2-3 years</li>
</ul>
<a name="Disadvantages-2"></a>
<h4 >Disadvantages:<a href="#Disadvantages-2" class="wiki-anchor">¶</a></h4>
<ul>
<li>Investment needed</li>
</ul>
<a name="2-Virtual-machine"></a>
<h2 >2. Virtual machine<a href="#2-Virtual-machine" class="wiki-anchor">¶</a></h2>
<a name="General-advantages-2"></a>
<h2 >General advantages<a href="#General-advantages-2" class="wiki-anchor">¶</a></h2>
<ul>
<li>More flexible in the future (VMs can be moved to other hosts, easy backup, failover easily possible)</li>
</ul>
<a name="General-disadvantages-2"></a>
<h2 >General disadvantages<a href="#General-disadvantages-2" class="wiki-anchor">¶</a></h2>
<ul>
<li>Setup of hypervisor can influence the functionality of network server</li>
</ul>
<a name="User-qamasterqasusede-as-VM-host"></a>
<h3 >User qamaster.qa.suse.de as VM host<a href="#User-qamasterqasusede-as-VM-host" class="wiki-anchor">¶</a></h3>
<a name="Advantages-3"></a>
<h4 >Advantages:<a href="#Advantages-3" class="wiki-anchor">¶</a></h4>
<ul>
<li>Already exists</li>
</ul>
<a name="Disadvantages-3"></a>
<h4 >Disadvantages:<a href="#Disadvantages-3" class="wiki-anchor">¶</a></h4>
<ul>
<li>Already close to it's capacity limit (renegotiation with users (of qamaster) needed)</li>
<li>Also the hypervisor OS needs an upgrade (SLES12)</li>
<li></li>
</ul>
<hr>