<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">Hi Stan<br>
      <br>
      we wanted interact with murano applications from mistral.
      Currently there is no support in mistral how to execute scripts on
      VM via murano agent (maybe I miss something). We noticed std.ssh
      mistral action so we consider SSH as one of the options. I think
      that it is not good idea due to networking obstacles I just wanted
      to confirm that. Thanks for pointing out Zaquar I didn't know
      about it.<br>
      <br>
      Filip<br>
      <br>
      <br>
      On 05/10/2015 04:21 AM, Stan Lagun wrote:<br>
    </div>
    <blockquote
cite="mid:CAOCoZiY=ia4z6nPKyQSN87pC3pTWRKOGs2N81a=_0KXQwx3jhg@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <div dir="ltr">Filip,
        <div><br>
        </div>
        <div>If I got you right the plan is to have Murano application
          execute Mistral workflow that SSH to VM and executes
          particular command? And alternative is
          Murano->Mistral->Zaquar->Zaquar agent?</div>
        <div>Why can't you just send this command directly from Murano
          (to Murano agent on VM)? This is the most common use case that
          is found in nearly all Murano applications and it is
          battle-proven. If you need SSH you can contribute SSH plugin
          to Murano (Mistral will require similar plugin anyway). The
          more moving parts you involve the more chances you have for
          everything to fail </div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="gmail_signature">
            <div dir="ltr"><span
                style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times
                New
Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span
                  style="font-family:arial;font-size:small">Sincerely
                  yours,<br>
                  Stan Lagun<br>
                  Principal Software Engineer @ Mirantis</span></span><br>
              <span
                style="border-collapse:separate;color:rgb(0,0,0);font-family:'Times
                New
Roman';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><span
                  style="font-family:arial;font-size:small"><br>
                </span></span></div>
          </div>
        </div>
        <br>
        <div class="gmail_quote">On Fri, May 8, 2015 at 11:22 AM, Renat
          Akhmerov <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:rakhmerov@mirantis.com" target="_blank">rakhmerov@mirantis.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
            <span class=""><br>
              <br>
              > On 06 May 2015, at 22:26, Fox, Kevin M <<a
                moz-do-not-send="true" href="mailto:kevin.fox@pnnl.gov">kevin.fox@pnnl.gov</a>>
              wrote:<br>
              ><br>
              > 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.<br>
              > The vm's don't have to be directly reachable from the
              network then. You just have to push messages into Zaqar.<br>
              <br>
            </span>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.<br>
            <span class=""><br>
              > Should Mistral abstract away how to execute the
              action, leaving it up to Mistral how to get the action to
              the vm?<br>
              <br>
            </span>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.<br>
            <span class=""><br>
              > If that's the case, then ssh vs queue/agent is just a
              Mistral implementation detail?<br>
              <br>
            </span>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).<br>
            <span class="HOEnZb"><font color="#888888"><br>
                <br>
                Renat Akhmerov<br>
                @ Mirantis Inc.<br>
              </font></span>
            <div class="HOEnZb">
              <div class="h5"><br>
                <br>
__________________________________________________________________________<br>
                OpenStack Development Mailing List (not for usage
                questions)<br>
                Unsubscribe: <a moz-do-not-send="true"
href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe"
                  target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
                <a moz-do-not-send="true"
                  href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev"
                  target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
              </div>
            </div>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">__________________________________________________________________________
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>