On Tue, 02.12.14 10:30, Flavio Leitner (f...@redhat.com) wrote:
Sort of. This special restart is only need on few cases when
hot-upgrading, otherwise users expect full restart which is already
accomplished by the current service unit.
It seems to me that the solution is a mix of making two
On 11/25/2014 02:09 AM, Flavio Leitner wrote:
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which start/stop/reload the
service (both daemons) just fine.
However, we need to support
On Tue, 25.11.14 00:09, Flavio Leitner (f...@redhat.com) wrote:
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which start/stop/reload the
service (both daemons) just fine.
In general
On Tue, Nov 25, 2014 at 12:09:07AM -0200, Flavio Leitner wrote:
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which start/stop/reload the
service (both daemons) just fine.
However, we
On Tue, Nov 25, 2014 at 10:42:12AM +, Richard Maw wrote:
On Tue, Nov 25, 2014 at 12:09:07AM -0200, Flavio Leitner wrote:
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which
Hello,
The Open vSwitch is comprised by two daemons. One is a database and
another is the switch itself.
Currently we have the openvswitch.service which start/stop/reload the
service (both daemons) just fine.
However, we need to support hot-upgrade which means to stop the
vswitch daemon first,
