Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-23 Thread Joshua Harlow
Doug Hellmann wrote: Excerpts from Kanagaraj Manickam's message of 2016-05-18 19:48:13 +0530: DIms, Use case could be anything, which would needed by either operator/community, who wants to perform an required task before and after service is started. This requirement is very generic by

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-23 Thread Kanagaraj Manickam
>Excerpts from Kanagaraj Manickam's message of 2016-05-18 19:48:13 +0530: >> > DIms, >> >> >> >> Use case could be anything, which would needed by either >> >> operator/community, who wants to perform an required task before and >> after >> >> service is started. This requirement is very generic

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-18 Thread Doug Hellmann
Excerpts from Kanagaraj Manickam's message of 2016-05-18 19:48:13 +0530: > > DIms, > >> > >> Use case could be anything, which would needed by either > >> operator/community, who wants to perform an required task before and > after > >> service is started. This requirement is very generic by

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-18 Thread Kanagaraj Manickam
> DIms, >> >> Use case could be anything, which would needed by either >> operator/community, who wants to perform an required task before and after >> service is started. This requirement is very generic by nature, and I >> believe it will be very useful. >> >> Would like to give the sample use

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-13 Thread Doug Hellmann
Excerpts from Kanagaraj Manickam's message of 2016-05-13 14:46:06 +0530: > DIms, > > Use case could be anything, which would needed by either > operator/community, who wants to perform an required task before and after > service is started. This requirement is very generic by nature, and I >

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-13 Thread Kanagaraj Manickam
DIms, Use case could be anything, which would needed by either operator/community, who wants to perform an required task before and after service is started. This requirement is very generic by nature, and I believe it will be very useful. Would like to give the sample use cases from from

Re: [openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-11 Thread Davanum Srinivas
Kanagaraj, Who is the first consumer? for what specific purpose? Thanks, Dims On Wed, May 11, 2016 at 9:27 AM, Kanagaraj Manickam wrote: > Hi, > > When OpenStack service components are started/stooped, > operators or OpenStack Services want to execute some actives > before

[openstack-dev] [oslo.service] Lifecycle Hooks

2016-05-11 Thread Kanagaraj Manickam
Hi, When OpenStack service components are started/stooped, operators or OpenStack Services want to execute some actives before and/or after component is started/stopped. Most of the time, operator needs to depends on the start-up scripts to do it, which is an installer dependent, while OpenStack