<html>#2574: alias patterns for BlueWaters and frontera conflict
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2021_05</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>If you could change aliaspattern to:</p>
<div class="codehilite"><pre><span></span><span>aliaspattern = login[1234]\.frontera\.tacc\.utexas\.edu$</span>
</pre></div>
<p>ie remove the <code>(...)?</code> optional marker, then check if <code>./simfactory/bin/sim whoami</code> still reports frontera then we can update the machine definition file to avoid the confusion due to identical login node hostnames in different cluster domains.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2574/alias-patterns-for-bluewaters-and-frontera'>https://bitbucket.org/einsteintoolkit/tickets/issues/2574/alias-patterns-for-bluewaters-and-frontera</a></p>
</html>