openstack team mailing list archive

[Hao Wang <hao.1.wang@xxxxxxxxx>]

Hi guys,

I went through rejoin-stack.sh which may not be what I want to get services
back from the original down status. It would be a script used to monitor
the logs of running services.

Good news is a procedure has been developped to implement the goal
mentioned by the mail subject after doing some research on
the script stack.sh. As Tong's mail has mentioned, there is something wrong
with the volume daemon. Please patch it with Tong's script if the volume
service is needed.

'''This is just for starting cloud without initializing mysql databases
   Please ensure run stack.sh successfully before executing the following
steps'''

1. Restart MySQL:

service mysql restart

2. Start keystone:

/opt/stack/keystone/bin/keystone-all --config-file
/etc/keystone/keystone.conf --log-config /etc/keystone/logging.conf -d
--debug

3. Restart APACHE:

service apache2 restart

4. Restart libvirt-bin:

service libvirt-bin restart

5. Start glance:

/opt/stack/glance/bin/glance-registry --config-file
/etc/glance/glance-registry.conf &
/opt/stack/glance/bin/glance-api --config-file /etc/glance/glance-api.conf &

Verify glance is working:
wget -q -O- http://127.0.0.1:9292

6. Start nova-api:

/opt/stack/nova/bin/nova-api &
 Verify novap-api is working:
wget -q -O- http://127.0.0.1:8774

7. Start nova:

/opt/stack/nova/bin/nova-cert &
/opt/stack/nova/bin/nova-network &
/opt/stack/nova/bin/nova-scheduler &
/opt/stack/noVNC/utils/nova-novncproxy --config-file /etc/nova/nova.conf &
/opt/stack/nova/bin/nova-xvpvncproxy --config-file /etc/nova/nova.conf &
/opt/stack/nova/bin/nova-consoleauth &

8. Start cinder:

/opt/stack/cinder/bin/cinder-api --config-file /etc/cinder/cinder.conf &
/opt/stack/cinder/bin/cinder-volume --config-file /etc/cinder/cinder.conf &
/opt/stack/cinder/bin/cinder-scheduler --config-file
/etc/cinder/cinder.conf &

If you've got any point, please let me know.

Regards,
Howard

On Fri, Oct 26, 2012 at 12:30 AM, Tong Li <litong01@xxxxxxxxxx> wrote:

> As I indicated, you can dress the volume stuff. Here is the
> rejoin-stack.sh I have, I just added a few lines to deal with the volume
> problem, if you use the script attached, everything will work fine. if you
> have swift enabled, change the data file to fit your configuration
>
> *(See attached file: rejoin-stack.sh)*
>
>
> Tong Li
> Emerging Technologies & Standards
>
> [image: Inactive hide details for Dean Troyer ---10/25/2012 11:34:57
> AM---On Thu, Oct 25, 2012 at 10:03 AM, Tong Li <litong01@xxxxxxxxx]Dean
> Troyer ---10/25/2012 11:34:57 AM---On Thu, Oct 25, 2012 at 10:03 AM, Tong
> Li <litong01@xxxxxxxxxx> wrote: > you can run rejoin-stack.sh
>
> From: Dean Troyer <dtroyer@xxxxxxxxx>
> To: Tong Li/Raleigh/IBM@IBMUS,
> Cc: Hao Wang <hao.1.wang@xxxxxxxxx>, openstack@xxxxxxxxxxxxxxxxxxx
> Date: 10/25/2012 11:34 AM
> Subject: Re: [Openstack] Could I restart devstack with old configuration?
> ------------------------------
>
>
>
> On Thu, Oct 25, 2012 at 10:03 AM, Tong Li <*litong01@xxxxxxxxxx*<litong01@xxxxxxxxxx>>
> wrote:
>
>    you can run rejoin-stack.sh from devstack directory to restart the
>    whole thing. However, there are some problems dealing with volume. But
>    other services should be OK.
>
>
>
> rejoin-stack.sh only addresses restarting the processes running under
> screen.  If you've used unstack.sh or rebooted it will probably not bring
> everything back.  We do need restack.sh to undo unstack.sh.  ;)
>
> As an alternative, if/when you do want to start with a fresh install but
> have additional things to add you can create local.sh to do that work at
> the end of stack.sh.  There is an example in samples/local.sh.
>
> dt
>
> --
>
> Dean Troyer*
> **dtroyer@xxxxxxxxx* <dtroyer@xxxxxxxxx>
>
>