<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 2013年12月01日 21:39, Christopher Yeoh
      wrote:<br>
    </div>
    <blockquote
cite="mid:CANCY3ecik=jfNa+SETad19QitgZBqyOqiRes0HbWHyhCk01m5g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>
                    <div>
                      <div>
                        <div>Hi,<br>
                          <br>
                          At the summit we agreed to split out
                          lock/unlock, pause/unpause, suspend/unsuspend<br>
                        </div>
                        functionality out of the V3 version of admin
                        actions into separate extensions to make it
                        easier for deployers to only have loaded the
                        functionality that they want.<br>
                        <br>
                        Remaining in admin_actions we have:<br>
                        <br>
                      </div>
                      migrate<br>
                      live_migrate<br>
                    </div>
                    reset_network<br>
                  </div>
                  inject_network_info<br>
                </div>
                create_backup<br>
              </div>
              reset_state<br>
              <br>
            </div>
            I think it makes sense to separate out migrate and
            live_migrate into a migrate plugin as well. <br>
            <br>
            What do people think about the others? There is no real
            overhead of having them in separate<br>
            plugins and totally remove admin_actions. Does anyone have
            any objections from this being done?<br>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    I have question for reset_network and inject_network_info. Is it
    useful for v3 api? The network info(ip address, gateway...) should
    be pushed<br>
    by DHCP service that provided by Neutron. And we don't like any
    inject.<br>
    <br>
    <blockquote
cite="mid:CANCY3ecik=jfNa+SETad19QitgZBqyOqiRes0HbWHyhCk01m5g@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div><br>
          </div>
          Also in terms of grouping I don't think any of the others
          remaining above really belong together, but welcome any
          suggestions.<br>
          <br>
        </div>
        Chris<br>
        <div><br>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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>