[openstack-dev] [ironic][nova][horizon] Serial console support for ironic instances
Akira Yoshiyama
akirayoshiyama at gmail.com
Sat Apr 23 00:26:05 UTC 2016
Hi all,
Thank you Yuiko. I'll join the console session. See you at the venue.
(2)Add console drivers using ironic-console-server
https://review.openstack.org/#/c/302291/ (ironic-console-server)
https://review.openstack.org/#/c/306754/ (console logging spec)
https://review.openstack.org/#/c/306755/ (serial console spec)
* Pros:
- There is no influence to other components like nova and horizon.
Only adding 2 methods to nova.virt.ironic.driver.IronicDriver
- No additional nova/ironic service required but a tool
(ironic-console-server)
- No change required for pre-existing console drivers
- Output console log files; users can show them by 'nova console-log'
ex.
https://github.com/yosshy/wiki/wiki/image/ironic_console_on_horizon-22.png
* Cons:
- Need to bump API microversion/RPC for Ironic because it has no console
logging capability now.
Regards,
Akira
2016-04-13 17:47 GMT+09:00 Yuiko Takada <yuikotakada0313 at gmail.com>:
> Hi,
>
> I also want to discuss about it at summit session.
>
> 2016-04-13 0:41 GMT+09:00 Ruby Loo <rlooyahoo at gmail.com>:
>
>> 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.
>>
>
> I've summarized all of related proposals.
>
> (1)Add driver using Socat
> https://review.openstack.org/#/c/293827/
>
> * Pros:
> - There is no influence to other components
> - Don't need to change any other Ironic drivers(like
> IPMIShellinaboxConsole)
> - Don't need to bump API microversion/RPC
>
> * Cons:
> - Don't output log file
>
> (2)Add driver starting ironic-console-server
> https://review.openstack.org/#/c/302291/
> (There is no spec, yet)
>
> * Pros:
> - There is no influence to other components
> - Output log file
> - Don't need to change any other Ironic drivers(like
> IPMIShellinaboxConsole)
> - No adding any Ironic services required, only add tools
>
> * Cons:
> - Need to bump API microversion/RPC
>
> (3)Add a custom HTTP proxy to Nova
> https://review.openstack.org/#/c/300582/
>
> * Pros:
> - Don't need any change to Ironic API
>
> * Cons:
> - Need Nova API changes(bump microversion)
> - Need Horizon changes
> - Don't output log file
>
> (4)Add Ironic-ipmiproxy server
> https://review.openstack.org/#/c/296869/
>
> * Pros:
> - There is no influence to other components
> - Output log file
> - IPMIShellinaboxConsole will be also available via Horizon
>
> * Cons:
> - Need IPMIShellinaboxConsole changes?
> - Need to bump API microversion/RPC
>
> If there is any mistake, please give me comment.
>
>
> Best Regards,
> Yuiko Takada
>
> 2016-04-13 0:41 GMT+09:00 Ruby Loo <rlooyahoo at gmail.com>:
>
>> 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.
>>
>> --ruby
>>
>>
>> On 12 April 2016 at 09:17, Jim Rollenhagen <jim at jimrollenhagen.com>
>> wrote:
>>
>>> On Tue, Apr 12, 2016 at 02:02:44AM +0800, Zhenguo Niu wrote:
>>> > Maybe we can continue the discussion here, as there's no enough time
>>> in the
>>> > irc meeting :)
>>>
>>> Someone mentioned this would make a good summit session, as there's a
>>> few competing proposals that are all good options. I do welcome
>>> discussion here until then, but I'm going to put it on the schedule. :)
>>>
>>> // jim
>>>
>>> >
>>> > On Fri, Apr 8, 2016 at 1:06 AM, Zhenguo Niu <niu.zglinux at gmail.com>
>>> wrote:
>>> >
>>> > >
>>> > > Ironic is currently using shellinabox to provide a serial console,
>>> but
>>> > > it's not compatible
>>> > > with nova, so I would like to propose a new console type and a
>>> custom HTTP
>>> > > proxy [1]
>>> > > which validate token and connect to ironic console from nova.
>>> > >
>>> > > On Horizon side, we should add support for the new console type [2]
>>> as
>>> > > well, here are some screenshots from my local environment.
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > Additionally, shellinabox console ports management should be
>>> improved in
>>> > > ironic, instead of manually specified, we should introduce
>>> dynamically
>>> > > allocation/deallocation [3] mechanism.
>>> > >
>>> > > Functionality is being implemented in Nova, Horizon and Ironic:
>>> > > https://review.openstack.org/#/q/topic:bp/shellinabox-http-proxy
>>> > > https://review.openstack.org/#/q/topic:bp/ironic-shellinabox-console
>>> > > https://review.openstack.org/#/q/status:open+topic:bug/1526371
>>> > >
>>> > >
>>> > > PS: to achieve this goal, we can also add a new console driver in
>>> ironic
>>> > > [4], but I think it doesn't conflict with this, as shellinabox is
>>> capable
>>> > > to integrate with nova, and we should support all console drivers.
>>> > >
>>> > >
>>> > > [1]
>>> https://blueprints.launchpad.net/nova/+spec/shellinabox-http-proxy
>>> > > [2]
>>> > >
>>> https://blueprints.launchpad.net/horizon/+spec/ironic-shellinabox-console
>>> > > [3] https://bugs.launchpad.net/ironic/+bug/1526371
>>> > > [4] https://bugs.launchpad.net/ironic/+bug/1553083
>>> > >
>>> > > --
>>> > > Best Regards,
>>> > > Zhenguo Niu
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > Best Regards,
>>> > Zhenguo Niu
>>>
>>>
>>>
>>>
>>> >
>>> __________________________________________________________________________
>>> > OpenStack Development Mailing List (not for usage questions)
>>> > Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>>
>>> __________________________________________________________________________
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>>
>> __________________________________________________________________________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
--
吉山あきら <akirayoshiyama at gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160423/cee3ddc9/attachment.html>
More information about the OpenStack-dev
mailing list