[Bug 1409639] Re: juju needs to support systemd for >= vivid

[Robie Basak]

** Description changed:

+ [Status]
+ 
+ The status of Juju and systemd need to be considered in three separate
+ scenarios:
+ 
+ A: A system administrator running the Juju client. For example, managing
+ a deployment somewhere else from your laptop.
+ 
+ B: Running within a deployment itself (the bootstrap node and all other
+ deployed nodes). This is the Juju that runs a production workload.
+ 
+ C: Developing charms using the local provider. This is really a special
+ case combining A and B.
+ 
+ The status of systemd and Juju in these scenarios is as follows:
+ 
+ A: Not affected. The client does not integrate with any init system, so
+ works fine under both upstart and systemd.
+ 
+ B: Affected (when deploying private Vivid charms). Juju will support
+ systemd from version 1.23 (yet to be released). Existing deployments are
+ not affected, since all existing Ubuntu releases run upstart. Deploying
+ onto Vivid is affected, since it will now run systemd, and will continue
+ to be affected after Vivid's release without further action. Workaround
+ for developers: arrange for deployed Vivid nodes to run upstart.
+ 
+ C: Affected (on Vivid only), until scenario B is fixed.
+ 
+ Schedule:
+ 
+ The first beta of 1.23 is expected 2015-03-18 and will provide full
+ systemd support. It will be available from a devel PPA. 1.23 is expected
+ to be released the week of 2015-03-30. It will be available from the
+ standard Juju stable PPA and will be uploaded to Vivid. In time, Trusty
+ will be updated too, although this has not yet been scheduled.
+ 
+ Archive status:
+ 
+ Currently no plans to upload 1.23 betas to Vivid. 1.23 will be uploaded
+ once it is released.
+ 
+ Until this time, dep8 tests are failing against juju-core as they test
+ scenario C, now in a systemd environment.
+ 
+ [Original Description]
+ 
  Ubuntu is currently working on switching its default init system from
  upstart to systemd; this has a direct impact on juju-core, which
  generates upstart configurations for the daemons that it runs across a
  deployment.
  
  The current target for switchover is the end of Jan/start of Feb, so it
  would be nice if we had a juju that supported this by then (at least in
  development).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1409639

Title:
  juju needs to support systemd for >= vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1409639/+subscriptions