Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-6225

Can't start a fabric at boot time using systemd

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Won't Do
    • Major
    • None
    • jboss-fuse-6.2.1, jboss-fuse-6.3
    • Fabric8 v1
    • None
    • % %

    Description

      There is no documented, supported way to start a bunch of fabric containers at boot time, on a Linux system that only supports systemd for service management.

      A typical situation is that a particular Linux server hosts a couple of top-level containers and a bunch of child containers. We want the whole lot to start at boot time, and the whole lot to shut down cleanly when the system shuts down.

      We have been able to get around this problem until now, to some extent, by using ugly scripting methods tied to SysV-style init scripts. The good thing about init scripts is that they are "hands off" for the operating system – once the script has been launched it is up to the sysadmin to make everything work. But systemd does not provide this kind of hands-off management – it expects the processes it launches to keep running, and to behave in predictable ways that match its own service model. It is almost impossible to make a fabric installation fit that model.

      SysV init scripts have been regarded as legacy features since RHEL 7.0, and as of 7.1 are no longer supported.

      Attachments

        Issue Links

          Activity

            People

              hchirino Hiram Chirino
              rhn-support-kboone Kevin Boone
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: