<div dir="ltr">Thanks Yuiko for doing this, but I'm sorry that I can't go to Austin, so I would like to add more details about my proposal here, hope someone can bring it to the session.<div><br></div><div><span style="font-size:12.8px">Add a custom HTTP proxy for web based consoles to Nova</span><div style="font-size:12.8px"><a href="https://review.openstack.org/#/c/300582/" target="_blank">https://review.openstack.org/#/c/300582/</a></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">* Pros:</div><div style="font-size:12.8px">- for Ironic </div><div style="font-size:12.8px"> - Don't need any change to Ironic API</div><div style="font-size:12.8px"> - We can continue use the web interface from Ironic, don't rely on Nova's websocketproxy to provide a ws/wss URL</div><div style="font-size:12.8px">- for Nova and Horizon</div><div style="font-size:12.8px"> - Support one more console type for hypervisors which provide web based consoles not only for Ironic, here's another one which also needs it</div><div style="font-size:12.8px"> <a href="https://blueprints.launchpad.net/nova/+spec/spice-http-proxy">https://blueprints.launchpad.net/nova/+spec/spice-http-proxy</a></div><div style="font-size:12.8px"><br></div><div style="font-size:12.8px">* Cons: </div><div style="font-size:12.8px">- Don't output log file</div><div> but I think session logging capability is a great extension for shellinabox, will explore this more.</div><div><br></div></div><div><br></div><div>And Ironic will support different console drivers, I don't think only one proposal will be accepted here.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Apr 14, 2016 at 10:11 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Apr 13, 2016 at 05:47:15PM +0900, Yuiko Takada wrote:<br>
> Hi,<br>
><br>
> I also want to discuss about it at summit session.<br>
><br>
> 2016-04-13 0:41 GMT+09:00 Ruby Loo <<a href="mailto:rlooyahoo@gmail.com">rlooyahoo@gmail.com</a>>:<br>
><br>
> > Yes, I think it would be good to have a summit session on that. However,<br>
> > before the session, it would really be helpful if the folks with proposals<br>
> > got together and/or reviewed each other's proposals, and summarized their<br>
> > findings.<br>
> ><br>
><br>
> I've summarized all of related proposals.<br>
><br>
> (1)Add driver using Socat<br>
> <a href="https://review.openstack.org/#/c/293827/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/293827/</a><br>
><br>
> * Pros:<br>
> - There is no influence to other components<br>
> - Don't need to change any other Ironic drivers(like IPMIShellinaboxConsole)<br>
> - Don't need to bump API microversion/RPC<br>
><br>
> * Cons:<br>
> - Don't output log file<br>
><br>
> (2)Add driver starting ironic-console-server<br>
> <a href="https://review.openstack.org/#/c/302291/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/302291/</a><br>
> (There is no spec, yet)<br>
><br>
> * Pros:<br>
> - There is no influence to other components<br>
> - Output log file<br>
> - Don't need to change any other Ironic drivers(like IPMIShellinaboxConsole)<br>
> - No adding any Ironic services required, only add tools<br>
><br>
> * Cons:<br>
> - Need to bump API microversion/RPC<br>
><br>
> (3)Add a custom HTTP proxy to Nova<br>
> <a href="https://review.openstack.org/#/c/300582/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/300582/</a><br>
><br>
> * Pros:<br>
> - Don't need any change to Ironic API<br>
><br>
> * Cons:<br>
> - Need Nova API changes(bump microversion)<br>
> - Need Horizon changes<br>
> - Don't output log file<br>
><br>
> (4)Add Ironic-ipmiproxy server<br>
> <a href="https://review.openstack.org/#/c/296869/" rel="noreferrer" target="_blank">https://review.openstack.org/#/c/296869/</a><br>
><br>
> * Pros:<br>
> - There is no influence to other components<br>
> - Output log file<br>
> - IPMIShellinaboxConsole will be also available via Horizon<br>
><br>
> * Cons:<br>
> - Need IPMIShellinaboxConsole changes?<br>
> - Need to bump API microversion/RPC<br>
><br>
> If there is any mistake, please give me comment.<br>
<br>
</div></div>Thanks for doing this Yuiko, this will be helpful for everyone preparing<br>
for this session. Looking forward to chatting about it. :)<br>
<span class="HOEnZb"><font color="#888888"><br>
// jim<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
><br>
> Best Regards,<br>
> Yuiko Takada<br>
><br>
> 2016-04-13 0:41 GMT+09:00 Ruby Loo <<a href="mailto:rlooyahoo@gmail.com">rlooyahoo@gmail.com</a>>:<br>
><br>
> > Yes, I think it would be good to have a summit session on that. However,<br>
> > before the session, it would really be helpful if the folks with proposals<br>
> > got together and/or reviewed each other's proposals, and summarized their<br>
> > findings. You may find after reviewing the proposals, that eg only 2 are<br>
> > really different. Or they several have merit because they are addressing<br>
> > slightly different issues. That would make it easier to<br>
> > present/discuss/decide at the session.<br>
> ><br>
> > --ruby<br>
> ><br>
> ><br>
> > On 12 April 2016 at 09:17, Jim Rollenhagen <<a href="mailto:jim@jimrollenhagen.com">jim@jimrollenhagen.com</a>> wrote:<br>
> ><br>
> >> 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<br>
> >> the<br>
> >> > irc meeting :)<br>
> >><br>
> >> 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>
> >><br>
> >> ><br>
> >> > On Fri, Apr 8, 2016 at 1:06 AM, Zhenguo Niu <<a href="mailto:niu.zglinux@gmail.com">niu.zglinux@gmail.com</a>><br>
> >> 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<br>
> >> 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>
> >> > > Additionally, shellinabox console ports management should be improved<br>
> >> 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<br>
> >> ironic<br>
> >> > > [4], but I think it doesn't conflict with this, as shellinabox is<br>
> >> capable<br>
> >> > > to integrate with nova, and we should support all console drivers.<br>
> >> > ><br>
> >> > ><br>
> >> > > [1]<br>
> >> <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>
> >> > ><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>
> >> ><br>
> >> __________________________________________________________________________<br>
> >> > OpenStack Development Mailing List (not for usage questions)<br>
> >> > Unsubscribe:<br>
> >> <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:<br>
> >> <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>
> > __________________________________________________________________________<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>
> __________________________________________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>Best Regards,<br></div>Zhenguo Niu<br></div></div>
</div>