I am sure there are many developers learning screen in order to work with devstack and I don't want to rob them off of their efforts.
However, there are developers (like me :) ) who use tmux everyday. I had used screen for some duration and moved to tmux as it provided some features that helped me debug and develop effectively. Every single day when I use devstack the thought of having tmux supported crosses my mind. While this is not the place to discuss pros and cons of tmux or screen, I would still like to provide links to get a glimpse what tmux has to offer. http://en.wikipedia.org/wiki/Tmux http://www.wikivs.com/wiki/Screen_vs_tmux http://dominik.honnef.co/posts/2010/10/why_you_should_try_tmux_instead_of_screen/ How it benifits devstack? ---- Developers using tmux can easily adopt it. devstack will bring all the advantanges that tmux brings. And I hope that the choice will even help devstackers unhappy with screen to try, IMHO, a newer and more elegant session manager. Why optional? ---- Both screen and tmux are under active development. devstack with tmux brings all the advantages that tmux brings and also the limitations that tmux brings. Apple-to-apple comparison is not going to help any of us. We spend time and learn and use tools of our choice so that we can work effectively. No choice of having variety of tools supported in any software only makes the adoption of that software more difficult. Code Complexity ---- I understand that the changes will introduce complexity, but I will try to abstract out this complexity so that we don't deal with it in everywhere in devstack but one. As Sean suggested I will go though all the screen calls in devstack and see if we have equivalent tmux calls and how we can abstract these things out and put in one place. I don't think there's going to be any functional differences, but I will investigate and point them out in the blueprint. Your feedback is valuable for me. Looking for more of it! On Thu, Jul 3, 2014 at 5:55 AM, Mathieu Gagné <mga...@iweb.com> wrote: > On 2014-07-02 2:10 PM, Yuriy Taraday wrote: > >> One problem that comes to mind is that screen tries to reopen your >> terminal when you attach to existing session or run a new one. >> So if you have one user you log in to a test server (ubuntu? root?) and >> another user that runs screen session (stack), you won't be able to >> attach to the session unless you do some dance with access rights (like >> "chmod a+rw `tty`" or smth). >> >> > I run this command to fix this issue instead of messing with chmod: > > script /dev/null > > -- > Mathieu > > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
