In 3.0 'service supervisor-database stop' dont stop all database services

contrail-database is now, not part of supervisor-database, hence cannot be controlled from it.
The external scripts need to issue 2 commands
service contrail-database restart
service supervisor-database restart

but in most cases probably
service contrail-database restart
is enough..

Thank you Raj for answer,

There is some kind of inconsistency then, are there any plans to separate contrail-database in contrail-status?

It looks like now:

== Contrail Database ==
contrail-database: active
supervisor-database: active
contrail-database-nodemgr active
kafka active

Which can be understood as supervisor stopping all services.

the database is still provisioned by contrail provision scripts — we would like to keep it’s status in contrail-status
May be we can make it as below..

== Contrail Database ==
contrail-database: active

== Contrail Database ==
supervisor-database: active
contrail-database-nodemgr active
kafka active

-Raj

> On Apr 11, 2016, at 6:29 AM, Katarzyna <email address hidden> wrote:
>
> Thank you Raj for answer,
>
> There is some kind of inconsistency then, are there any plans to
> separate contrail-database in contrail-status?
>
> It looks like now:
>
> == Contrail Database ==
> contrail-database: active
> supervisor-database: active
> contrail-database-nodemgr active
> kafka active
>
> Which can be understood as supervisor stopping all services.
>
> --
> You received this bug notification because you are a member of Contrail
> Systems engineering, which is subscribed to Juniper Openstack.
> https://bugs.launchpad.net/bugs/1568062
>
> Title:
> In 3.0 'service supervisor-database stop' dont stop all database
> services
>
> Status in Juniper Openstack:
> Won't Fix
>
> Bug description:
> For contrail database service, as below:
>
> == Contrail Database ==
> supervisor-database: active
> contrail-database active
> contrail-database-nodemgr active
> kafka active
>
> 'service supervisor-database stop' command was always stopping all
> dataase services. In Contrail 3.0, issuing this one don't stop
> contrail-database service and it should be stopped manually:
>
> == Contrail Database ==
> contrail-database: active
> supervisor-database: inactive
>
> Same when starting services.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juniperopenstack/+bug/1568062/+subscriptions

Loooks good, in my opinion that output will clarify how services should be stopped/started

Review in progress for https://review.opencontrail.org/19706
Submitter: Santosh Gupta (<email address hidden>)

Review in progress for https://review.opencontrail.org/19766
Submitter: Santosh Gupta (<email address hidden>)

Reviewed: https://review.opencontrail.org/19706
Committed: http://github.org/Juniper/contrail-controller/commit/c5c03562cf48db465befea4d152a9161d61a3613
Submitter: Zuul
Branch: master

commit c5c03562cf48db465befea4d152a9161d61a3613
Author: Santosh Gupta <email address hidden>
Date: Thu Apr 28 10:31:40 2016 -0700

Closes-Bug: #1568062
seperate contrail-database and contrail supervisor-database in contrail-status output

Change-Id: I4fae9542ee848d5c334c6f9e718704c1c1bda423

Reviewed: https://review.opencontrail.org/19766
Committed: http://github.org/Juniper/contrail-controller/commit/40378215509b42b630a3dc54d28bcc22a99f99ef
Submitter: Zuul
Branch: R3.0

commit 40378215509b42b630a3dc54d28bcc22a99f99ef
Author: Santosh Gupta <email address hidden>
Date: Fri Apr 29 16:12:06 2016 -0700

Closes-Bug: #1568062 seperate contrail-database and contrail supervisor-database in contrail-status output

Change-Id: I3d5669fb8cc48e9856fd8253346db2b54c829935