<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 10, 2015 at 5:08 PM, Brian Stansberry <span dir="ltr"><<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
</span>In a domain, yes. The migration of a subsystem in one profile does not<br>
mean the extension is unavailable for use in another profile.<br>
<br>
I don't have a strong opinion about this in standalone.<br>
</blockquote></div><br><br></div><div class="gmail_extra">Standalone shouldn't boot in non admin mode with legacy extensions, as they are only allowed to run in host controller and in admin mode.<br></div><div class="gmail_extra">At least that is the contract of AbstractLegacyExtension that all deprecated / legacy extensions extend(ed)<br></div><div class="gmail_extra"><br>Recently(as part of adding :migrate op) some of legacy extensions ware changed back to not use AbstractLegacyExtension, <br>but that was probably just because we haven't defined in what the lifecycle they should run given that they have migrate operation defined.<br></div><div class="gmail_extra"><br></div></div>