<div dir="ltr"><div><div><div>Hi all, <br><br></div>Thank you Yuiko. I'll join the console session. See you at the venue.<br><div><br></div><div>(2)Add console drivers using <span class="">ironic</span>-<span class="">console</span>-server</div><div><a href="https://review.openstack.org/#/c/302291/" target="_blank">https://review.openstack.org/#/c/302291/</a> (ironic-console-server)<br></div><div><a href="https://review.openstack.org/#/c/306754/">https://review.openstack.org/#/c/306754/</a> (console logging spec)<br><a href="https://review.openstack.org/#/c/306755/">https://review.openstack.org/#/c/306755/</a> (serial console spec)<br><br></div><div>* Pros: </div><div>- There is no influence to other components like nova and horizon.<br></div><div>  Only adding 2 methods to nova.virt.ironic.driver.IronicDriver<br><div>- No additional nova/i<span class="">ronic</span> service required but a tool (ironic-console-server)<br></div></div><div>- No change required for pre-existing <span class="">console</span> drivers<br>- Output console log files; users can show them by 'nova console-log'<br></div>  ex. <a id="yui_3_10_3_1_1461370180738_1969" rel="nofollow" href="https://github.com/yosshy/wiki/wiki/image/ironic_console_on_horizon-22.png">https://github.com/yosshy/wiki/wiki/image/ironic_console_on_horizon-22.png</a><br><div><br>* Cons:</div><div>- Need to bump API microversion/RPC for Ironic because it has no console logging capability now.<br></div><br></div>Regards,<br>Akira<br></div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">2016-04-13 17:47 GMT+09:00 Yuiko Takada <span dir="ltr"><<a href="mailto:yuikotakada0313@gmail.com" target="_blank">yuikotakada0313@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi,</div><div><br></div><div>I also want to discuss about it at summit session.</div><span class=""><div><br></div><div>2016-04-13 0:41 GMT+09:00 Ruby Loo <span dir="ltr"><<a href="mailto:rlooyahoo@gmail.com" target="_blank">rlooyahoo@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Yes, I think it would be good to have a summit session on that. However, before the session, it would really be helpful if the folks with proposals got together and/or reviewed each other's proposals, and summarized their findings. </div></blockquote><div> </div></div></span><div>I've summarized all of related proposals.</div><div><br></div><div>(1)Add driver using Socat</div><div><a href="https://review.openstack.org/#/c/293827/" target="_blank">https://review.openstack.org/#/c/293827/</a></div><div><br></div><div>* Pros: </div><div>- There is no influence to other components</div><div>- Don't need to change any other Ironic drivers(like IPMIShellinaboxConsole)</div><div>- Don't need to bump API microversion/RPC</div><div><br></div><div>* Cons: </div><div>- Don't output log file</div><div><br></div><div>(2)Add driver starting ironic-console-server</div><div><a href="https://review.openstack.org/#/c/302291/" target="_blank">https://review.openstack.org/#/c/302291/</a></div><div>(There is no spec, yet)</div><div><br></div><div>* Pros: </div><div>- There is no influence to other components</div><div>- Output log file</div><div>- Don't need to change any other Ironic drivers(like IPMIShellinaboxConsole)</div><div>- No adding any Ironic services required, only add tools</div><div><br></div><div>* Cons:</div><div>- Need to bump API microversion/RPC</div><div><br></div><div>(3)Add a custom HTTP proxy to Nova</div><div><a href="https://review.openstack.org/#/c/300582/" target="_blank">https://review.openstack.org/#/c/300582/</a></div><div><br></div><div>* Pros: </div><div>- Don't need any change to Ironic API</div><div><br></div><div>* Cons: </div><div>- Need Nova API changes(bump microversion)</div><div>- Need Horizon changes</div><div>- Don't output log file</div><div><br></div><div>(4)Add Ironic-ipmiproxy server</div><div><a href="https://review.openstack.org/#/c/296869/" target="_blank">https://review.openstack.org/#/c/296869/</a></div><div><br></div><div>* Pros: </div><div>- There is no influence to other components</div><div>- Output log file</div><div>- IPMIShellinaboxConsole will be also available via Horizon</div><div><br></div><div>* Cons: </div><div>- Need IPMIShellinaboxConsole changes?</div><div>- Need to bump API microversion/RPC</div><div><br></div><div>If there is any mistake, please give me comment.</div><div><br></div><div><br></div><div>Best Regards,</div><div>Yuiko Takada</div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">2016-04-13 0:41 GMT+09:00 Ruby Loo <span dir="ltr"><<a href="mailto:rlooyahoo@gmail.com" target="_blank">rlooyahoo@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Yes, I think it would be good to have a summit session on that. However, before the session, it would really be helpful if the folks with proposals got together and/or reviewed each other's proposals, and summarized their findings. You may find after reviewing the proposals, that eg only 2 are really different. Or they several have merit because they are addressing slightly different issues. That would make it easier to present/discuss/decide at the session.<span><font color="#888888"><br><br>--ruby<br></font></span></div><div><div><br><div><div><div><div><div class="gmail_extra"><br><div class="gmail_quote">On 12 April 2016 at 09:17, Jim Rollenhagen <span dir="ltr"><<a href="mailto:jim@jimrollenhagen.com" target="_blank">jim@jimrollenhagen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>On Tue, Apr 12, 2016 at 02:02:44AM +0800, Zhenguo Niu wrote:<br>
> Maybe we can continue the discussion here, as there's no enough time in the<br>
> irc meeting :)<br>
<br>
</span>Someone mentioned this would make a good summit session, as there's a<br>
few competing proposals that are all good options. I do welcome<br>
discussion here until then, but I'm going to put it on the schedule. :)<br>
<br>
// jim<br>
<span><br>
><br>
> On Fri, Apr 8, 2016 at 1:06 AM, Zhenguo Niu <<a href="mailto:niu.zglinux@gmail.com" target="_blank">niu.zglinux@gmail.com</a>> wrote:<br>
><br>
> ><br>
> > Ironic is currently using shellinabox to provide a serial console, but<br>
> > it's not compatible<br>
> > with nova, so I would like to propose a new console type and a custom HTTP<br>
> > proxy [1]<br>
> > which validate token and connect to ironic console from nova.<br>
> ><br>
> > On Horizon side, we should add support for the new console type [2] as<br>
> > well, here are some screenshots from my local environment.<br>
> ><br>
> ><br>
> ><br>
> > ​<br>
> ><br>
</span><span>> > Additionally, shellinabox console ports management should be improved in<br>
> > ironic, instead of manually specified, we should introduce dynamically<br>
> > allocation/deallocation [3] mechanism.<br>
> ><br>
> > Functionality is being implemented in Nova, Horizon and Ironic:<br>
> > <a href="https://review.openstack.org/#/q/topic:bp/shellinabox-http-proxy" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/topic:bp/shellinabox-http-proxy</a><br>
> > <a href="https://review.openstack.org/#/q/topic:bp/ironic-shellinabox-console" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/topic:bp/ironic-shellinabox-console</a><br>
> > <a href="https://review.openstack.org/#/q/status:open+topic:bug/1526371" rel="noreferrer" target="_blank">https://review.openstack.org/#/q/status:open+topic:bug/1526371</a><br>
> ><br>
> ><br>
> > PS: to achieve this goal, we can also add a new console driver in ironic<br>
> > [4], but I think it doesn't conflict with this, as shellinabox is capable<br>
> > to integrate with nova, and we should support all console drivers.<br>
> ><br>
> ><br>
> > [1] <a href="https://blueprints.launchpad.net/nova/+spec/shellinabox-http-proxy" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/nova/+spec/shellinabox-http-proxy</a><br>
> > [2]<br>
> > <a href="https://blueprints.launchpad.net/horizon/+spec/ironic-shellinabox-console" rel="noreferrer" target="_blank">https://blueprints.launchpad.net/horizon/+spec/ironic-shellinabox-console</a><br>
> > [3] <a href="https://bugs.launchpad.net/ironic/+bug/1526371" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ironic/+bug/1526371</a><br>
> > [4] <a href="https://bugs.launchpad.net/ironic/+bug/1553083" rel="noreferrer" target="_blank">https://bugs.launchpad.net/ironic/+bug/1553083</a><br>
> ><br>
> > --<br>
> > Best Regards,<br>
> > Zhenguo Niu<br>
> ><br>
><br>
><br>
><br>
> --<br>
> Best Regards,<br>
> Zhenguo Niu<br>
<br>
<br>
<br>
<br>
</span>> __________________________________________________________________________<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>
<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></div></div></div></div></div></div></div>
<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>
<br></blockquote></div><br></div></div></div></div>
<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>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">吉山あきら <<a href="mailto:akirayoshiyama@gmail.com" target="_blank">akirayoshiyama@gmail.com</a>></div>
</div></div></div></div></div>