<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi <br>
<br>
there is VPN mechanism in neutron we could consider for future how
to get around these networking obstacles if we would like to use
direct SSH.<br>
<br>
1) every private created by murano would create VPN gateway on
public interface of the router [1]<br>
<br>
<font color="#3333ff">neutron vpn-service-create --name myvpn
--description "My vpn service" router1 mysubnet</font><br>
<br>
2) any service like mistral which needs directly access VM via SSH
(or other protocols) would connect to that VPN and then it could
directly access VM on its fixed IP<br>
<br>
This mechanism would probably resolve network obstacles. But it
requires more effort to analyse it.<br>
<br>
[1] <a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Neutron/VPNaaS/HowToInstall">https://wiki.openstack.org/wiki/Neutron/VPNaaS/HowToInstall</a><br>
<br>
Filip<br>
<br>
On 05/08/2015 10:22 AM, Renat Akhmerov wrote:<br>
</div>
<blockquote
cite="mid:84F6C050-57EE-4AD7-96F8-60F436FDA5D9@mirantis.com"
type="cite">
<pre wrap="">Generally yes, std.ssh action works as long as network infrastructure allows access to a host using specified IP, it doesn’t provide anything on top of that.
</pre>
<blockquote type="cite">
<pre wrap="">On 06 May 2015, at 22:26, Fox, Kevin M <a class="moz-txt-link-rfc2396E" href="mailto:kevin.fox@pnnl.gov"><kevin.fox@pnnl.gov></a> wrote:
This would also probably be a good use case for Zaqar I think. Have a generic "run shell commands from Zaqar queue" agent, that pulls commands from a Zaqar queue, and executes it.
The vm's don't have to be directly reachable from the network then. You just have to push messages into Zaqar.
</pre>
</blockquote>
<pre wrap="">
Yes, in Mistral it would be another action that puts a command into Zaqar queue. This type of action doesn’t exist yet but it can be plugged in easily.
</pre>
<blockquote type="cite">
<pre wrap="">Should Mistral abstract away how to execute the action, leaving it up to Mistral how to get the action to the vm?
</pre>
</blockquote>
<pre wrap="">
Like I mentioned previously it should be just a different type of action: “zaqar.something” instead of “std.ssh”. Mistral engine itself works with all actions equally, they are just basically functions that we can plug in and use in Mistral workflow language. >From this standpoint Mistral is already abstract enough.
</pre>
<blockquote type="cite">
<pre wrap="">If that's the case, then ssh vs queue/agent is just a Mistral implementation detail?
</pre>
</blockquote>
<pre wrap="">
More precisely: implementation detail of Mistral action which may not be even hardcoded part of Mistral, we can rather plug them in (using stevedore underneath).
Renat Akhmerov
@ Mirantis Inc.
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: <a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>