Comment 3 for bug 1568062

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