Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncm-metaconfig: add ability to do service reload #280

Closed
alahiff opened this issue Aug 19, 2014 · 3 comments
Closed

ncm-metaconfig: add ability to do service reload #280

alahiff opened this issue Aug 19, 2014 · 3 comments
Assignees
Milestone

Comments

@alahiff
Copy link

alahiff commented Aug 19, 2014

It seems that ncm-metaconfig can only restart a specified service when the configuration is changed. This is a blocking issue that prevents us from being able to use metaconfig for some services, e.g. HTCondor. Would it be possible to add the ability to do a service reload?

@piojo-zz
Copy link
Member

piojo-zz commented Oct 2, 2014

As agreed during the workshop, we'll modify the schema slightly so that each file contains an nlist of daemons and actions:

"/.../metaconfig/services/{/path/to/fie}/daemons" = nlist(
    "daemona", "action_for_daemona",
    ...
);

If two files require different actions on the same daemon, we'll execute them all at the beginning. In the future, depending on the need, we may de-duplicate actions.

@stdweird
Copy link
Member

we need feedback how to treat the use of the legacy daemon field: do we throw a warning (maybe even in the schema validation) and thus treating it as real legacy code? if so, we should also schedule a traget release by which this becomes an error (and not allowed in schema).

@jrha
Copy link
Member

jrha commented Nov 3, 2014

Fixed by #328.

@jrha jrha closed this as completed Nov 3, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants