With OpenStack there are quite a large number of daemons per host, each
of which has their own .service unit file.
Currently our OpenStack instructions have such fun commands as:
# for svc in api registry; do sudo systemctl start openstack-glance-$svc.service; done
# for svc in api objectstore compute network volume scheduler cert; do sudo systemctl start openstack-nova-$svc.service; done
What I'd like to be able todo is setup some kind of grouping, so that
you can just start/stop/check status of everything in simple commands
# sudo systemctl start openstack-nova.target
# sudo systemctl status openstack-nova.target
# sudo systemctl stop openstack-nova.target
My naive attempt to make this work was todo
- Create a openstack-nova.target containining
- Edit each of openstack-nova-XXX.service to change
WantedBy=multi-user.target to WantedBy=openstack-nova.target
But after doing this, stopping/starting the target has no effect on the
running state of units I associated with it. Also I'd like starting/stopping
XXX.target to take account of the enablement state of the individual
XXX-YYY.service files. eg so I can disable say, openstack-nova-network.service
on a host, but still use openstack-nova.target to bulk stop/start all the
other services that are enabled.
Either I'm missing some config change, or what I'm attempting is just not
the kind of functionality that .target files are intended to offer ?
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
>From Fedora 18 on, Fedora will no longer include the freedom to for a
user to create a fork or respin which is the technological equal of
the Project's output. Instead, this freedom will be available
exclusively from Microsoft for $99 under unspecified conditions.
I wish this were a joke.
Jaroslav Reznik wrote:
> Other possibility is to go directly to 1 GiB but we are not sure
> there's advantage (at least not now).
You would probably want to make the target 1 GB (SI units), not 1 GiB. The
capacity of thumb drives is measured in SI units, so a "1 GB" thumb drive really
is 1000^3 bytes, not 1024^3. (They start out with the binary capacity, but some
fraction of that is used for overhead, leaving some amount between the SI and
binary size. Hence the advertising refers to the SI size.)
> So we'd like to hear from rel-engs, QA etc. what's theirs position
AFAIK the only QA issue would be getting notified as to what the new target is,
so the size tests can be modified. You probably also want to create a page
https://fedoraproject.org/wiki/Releases/18/Spins with the new size. The
corresponding page currently exists for 16, but not 17 or 18.
I've just packaged tntnet - A web application server for web applications.
tntnet is needed for vdr-live - An interactive web interface for VDR
can someone review this package ?
I'm going to build the unstable PackageKit 0.8.1 into rawhide
tomorrow. The packagekit-glib and packagekit-qt break ABI, but I'll
take care of anything that needs patching / rebuilding.