Open Stack

Hi Sumanth,

No! You certainly need restart the horizon service after making changes in /opt/stack/horizon in order for your changes to take effect, but as I was saying before – that is NOT the intention of stack.sh.

Unstack.sh will take down your entire devstack, so while that part is overkill it is still technically a way to take down horizon. Rejoin-stack.sh is what will bring your entire devstack back WITHOUT doing a reinstall and reconfigure. Running stack.sh WILL do a full reinstall and reconfigure, and any projects or users (for example) that have been added or changed in your previous install of devstack will be completely lost.

A simpler way to simply restart horizon would be to follow the advice in David’s original email.

Tim


From: Sumanth Sathyanarayana <sumanth.sathyanarayana at gmail.com<mailto:sumanth.sathyanarayana at gmail.com>>
Date: Thursday, September 3, 2015 at 11:19 AM
To: Timothy Symanczyk <timothy_symanczyk at symantec.com<mailto:timothy_symanczyk at symantec.com>>
Cc: OpenStack General <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: Re: [Openstack] Building DevStack

Thanks David and Timothy.
But as I make custom changes to Horizon frontend of devstack in /opt/stack/horizon,
I do have to run the stack.sh(after unstack.sh) script everytime I make the change right?

Best Regards
Sumanth

On Thu, Sep 3, 2015 at 10:41 AM, Timothy Symanczyk <Timothy_Symanczyk at symantec.com<mailto:Timothy_Symanczyk at symantec.com>> wrote:
Hi Sumanth,

In addition to David’s helpful links, please keep in mind that ./stack.sh is intended to INSTALL and CONFIGURE devstack. If it is your intention to START FRESH every time, then running unstack.sh and stack.sh would be correct. But if it is your intention to persist any changes you’ve previously made with your devstack (adding projects / users, etc), then running rejoin-stack.sh would be the way to bring it back up without losing that progress.

Tim

From: David Medberry <openstack at medberry.net<mailto:openstack at medberry.net>>
Date: Wednesday, September 2, 2015 at 5:58 PM
To: Sumanth Sathyanarayana <sumanth.sathyanarayana at gmail.com<mailto:sumanth.sathyanarayana at gmail.com>>
Cc: OpenStack General <openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>>
Subject: Re: [Openstack] Building DevStack

http://www.slideshare.net/SajuMadhavan/open-stack-devstack-screen-commands-and-key-bindings may be more current.

On Wed, Sep 2, 2015 at 6:57 PM, David Medberry <openstack at medberry.net<mailto:openstack at medberry.net>> wrote:
Be aware that there is a "screen" session running with each of the services. If you go to the appropriate screen in the screen session and then "Ctrl-C" therein and hit up arrow return, you'll basically be restarting just that service.

This may be out of date but give it a try:

http://www.rushiagr.com/blog/2013/06/05/linux-screens-in-devstack/

On Wed, Sep 2, 2015 at 6:39 PM, Sumanth Sathyanarayana <sumanth.sathyanarayana at gmail.com<mailto:sumanth.sathyanarayana at gmail.com>> wrote:
Hi,

I am relatively new to openstack and devstack and wanted to know if there is any easy way to build devstack, every time I change a class or a python file in /opt/stack/*
If I just compile that particular python file which has been changed (say in Horizon - /opt/stack/horizon/*), it doesn't get reflected until I run  unstack.sh and again run stack.sh.

Thanks & Best Regards
Sumanth

_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to     : openstack at lists.openstack.org<mailto:openstack at lists.openstack.org>
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20150903/0d783cad/attachment.html>