<div dir="ltr">Hi Steven, thank you for letting us know about your use case,<div><br></div><div>The problem is caused because since 6.1 release we run</div><div>part of network verification tasks before deployment [1], from</div><div>the code it can be seen, that this check is hardcoded [2], before</div><div>we send any deployment tasks, so we should figure out a way</div><div>to fix it.</div><div><br></div><div>Possible options:</div><div><br></div><div>1. run network verification us a part of deployment, somewhere</div><div> in pre_deployment stage, between pre_deployment/4999 and</div><div> pre_deployment/6000 [3], but it doesn't cover the case when user</div><div> wants to just run network verification on Network tab</div><div><br></div><div>2. introduce new stage pre_network_verification which will be</div><div> run before we start network verification, so you will be able</div><div> to configure switches</div><div><br></div><div>Also I would like to notice, that role as a plugin feature which</div><div>will allow to change deployment graph of the core, will not help</div><div>here [4]. Because network verification is not a part of the graph.</div><div><br></div><div>Thanks,</div><div><br></div><div>[1] <a href="https://bugs.launchpad.net/fuel/+bug/1439686">https://bugs.launchpad.net/fuel/+bug/1439686</a></div><div>[2] <a href="https://github.com/stackforge/fuel-web/commit/c4594fc2461f1cf66e580a07d32a869c3f25678d">https://github.com/stackforge/fuel-web/commit/c4594fc2461f1cf66e580a07d32a869c3f25678d</a><br></div><div>[3] <a href="https://wiki.openstack.org/wiki/Fuel/Plugins#stage_parameter">https://wiki.openstack.org/wiki/Fuel/Plugins#stage_parameter</a></div><div>[4] <a href="https://github.com/stackforge/fuel-specs/blob/master/specs/7.0/role-as-a-plugin.rst">https://github.com/stackforge/fuel-specs/blob/master/specs/7.0/role-as-a-plugin.rst</a></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jul 21, 2015 at 12:49 AM, Steven Kath <span dir="ltr"><<a href="mailto:kath@linux.com" target="_blank">kath@linux.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
I'm hoping to design a FUEL plugin which can provision a switch or set<br>
of switches according to the Network Settings specified when first<br>
configuring an environment in FUEL.<br>
<br>
We have puppet manifests which allow us to configure every aspect<br>
of our switches, including the plumbing of VLANs. It would be possible<br>
for us to configure the VLANs as specified in the environment's<br>
Network Settings prior to, or as part of, the "Verify Networks" stage.<br>
<br>
As far as I can tell, there aren't any FUEL plugin hooks this early in<br>
the provisioning process. I can't find where to initiate any<br>
configuration of a remote device before validating the network<br>
settings. I've looked at a number of the networking plugins for FUEL<br>
and they all seem to be focused on adding overlays, pre-supposing a<br>
static underlay network configuration which the plugins never<br>
manipulate.<br>
<br>
Can anyone confirm whether the current FUEL capabilities, or planned<br>
FUEL 7.0 functionality, would allow for this sort of pre-deployment<br>
network configuration?<br>
<br>
Are there any relevant documentation sections or plugin examples<br>
which I might have overlooked?<br>
<br>
Thanks!<br>
- Steven<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote></div><br></div>