> systemctl is part of systemd. If you have systemctl installed, then the
> system should be ready to use systemd service units just fine.
My point is that Centos and RHEL RPMS do not have the systemd files as
part of the rpms.
So if systemctl exists and the
usr_lib_systemd_system_openvswitch.serv
On Wed, Dec 04, 2013 at 01:06:35PM -0800, Gurucharan Shetty wrote:
> One more thing. There is no BRCOMPAT in master. So that will have to go.
Ok, I will remove it.
> On Wed, Dec 4, 2013 at 1:04 PM, Gurucharan Shetty wrote:
> > On Wed, Dec 4, 2013 at 12:12 PM, Flavio Leitner wrote:
> >> On Wed,
One more thing. There is no BRCOMPAT in master. So that will have to go.
On Wed, Dec 4, 2013 at 1:04 PM, Gurucharan Shetty wrote:
> On Wed, Dec 4, 2013 at 12:12 PM, Flavio Leitner wrote:
>> On Wed, Dec 04, 2013 at 10:27:10AM -0800, Gurucharan Shetty wrote:
>>> On Mon, Dec 2, 2013 at 5:13 PM, Fla
On Wed, Dec 4, 2013 at 12:12 PM, Flavio Leitner wrote:
> On Wed, Dec 04, 2013 at 10:27:10AM -0800, Gurucharan Shetty wrote:
>> On Mon, Dec 2, 2013 at 5:13 PM, Flavio Leitner wrote:
>> > There is a chicken and egg issue where common OVS
>> > configuration uses a controller which is only accessible
On Wed, Dec 04, 2013 at 10:27:10AM -0800, Gurucharan Shetty wrote:
> On Mon, Dec 2, 2013 at 5:13 PM, Flavio Leitner wrote:
> > There is a chicken and egg issue where common OVS
> > configuration uses a controller which is only accessible
> > via the network. So starting OVS before network.target
>
On Wed, Dec 04, 2013 at 10:27:10AM -0800, Gurucharan Shetty wrote:
> > --- a/rhel/etc_sysconfig_network-scripts_ifdown-ovs
> > +++ b/rhel/etc_sysconfig_network-scripts_ifdown-ovs
> > @@ -34,7 +34,15 @@ if [ ! -x ${OTHERSCRIPT} ]; then
> > OTHERSCRIPT="/etc/sysconfig/network-scripts/ifdown-eth"
On Mon, Dec 2, 2013 at 5:13 PM, Flavio Leitner wrote:
> There is a chicken and egg issue where common OVS
> configuration uses a controller which is only accessible
> via the network. So starting OVS before network.target
> would break those configurations.
>
> However, the network doesn't come up
There is a chicken and egg issue where common OVS
configuration uses a controller which is only accessible
via the network. So starting OVS before network.target
would break those configurations.
However, the network doesn't come up after boot because
OVS isn't started until after the network scri
