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
>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
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
> 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
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
>
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
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
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