<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 11/07/2017 03:11 PM, John Meinel
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHE3fn6Cs0Z6h_++2PuyY4PbgBxG3Rkd5kbn2-af+4dcM1qOgg@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>...</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">
> Perhaps just:<br>
><br>
> juju deploy --map-machines A=B,C=D<br>
><br>
> ... or some variant of that?<br>
><br>
> Let's use the betas to refine and condense and
clarify.<br>
<br>
</span>+1 to that. I'm wondering if use-existing-machines
is ever appropriate<br>
on its own, as the machine numbers in a model are
ephemeral but<br>
machine numbers in a bundle are static.<br>
<br>
</blockquote>
<div><br>
</div>
<div>Feedback from Admins that one of their big use case
really is for bundle-a to lay down a definition/base charm
across everything, and bundle-b to be meant as an exact
overlay, and all of the machine-ids are exact matches. And
having to specify 0=0,...50=50 is a lot of ugly
boilerplate.</div>
</div>
</div>
</div>
</blockquote>
<br>
I would expect that --map-machines means that machine numbers
correspond UNLESS remapped. So your ugly boilerplate is not needed.<br>
<br>
Mark<br>
</body>
</html>