--001a114e8aa28a3694054dfc3e45
Content-Type: text/plain; charset=UTF-8

Hello,
I am using debian stretch and I am trying to have openvswitch to work right after rebooting the machine.

So far, I manually configure the card with znetconf and then start
openvswitch and then manually bring up the interfaces.

To visualize my approach, I list the commands (bridge and port had already
been added to ovs beforehand):
# znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary
# systemctl start openvswitch-switch
# ip l s [ccwdev0] up
# ip l s br0 up

Everything works out fine, I can now live migrate vm's via virsh.

What options do I have to add to /etc/sysconfig/hardware/config-ccw-0.0.[ccwdev0] to set the bridge_role
when the interface is brought up?

Best,
Benjamin.

--001a114e8aa28a3694054dfc3e45
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hello,<br></div>I am using debian stretch and I am trying to have openvswitch to work right after rebooting the machine.<br><br></div>So far, I manually configure the card with znetconf and
then start openvswitch and then manually bring up the interfaces.<br><br></div>To visualize my approach, I list the commands (bridge and port had already been added to ovs beforehand):<br></div># znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary<

</div><div># systemctl start openvswitch-switch<br></div># ip l s [ccwdev0] up<br></div># ip l s br0 up<br><br></div>Everything works out fine, I can now live migrate vm&#39;s via virsh.<br><br></div>What options do I have to add to /etc/sysconfig/

hardware/config-ccw-0.0.[ccwdev0] to set the bridge_role when the interface is brought up?<br><br></div>Best,<br></div>Benjamin.<br></div>

--001a114e8aa28a3694054dfc3e45--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 25.04.2017 13:44, Benjamin Jakob Zimmermann wrote:

Hello,
I am using debian stretch and I am trying to have openvswitch to work right after rebooting the machine.

So far, I manually configure the card with znetconf and then start openvswitch and then manually bring up the interfaces.

To visualize my approach, I list the commands (bridge and port had already been added to ovs beforehand):
# znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary
# systemctl start openvswitch-switch
# ip l s [ccwdev0] up
# ip l s br0 up

Everything works out fine, I can now live migrate vm's via virsh.

What options do I have to add to /etc/sysconfig/hardware/config-ccw-0.0.[ccwdev0] to set the bridge_role
when the interface is brought up?

Best,
Benjamin.

Hi,

I fear there's no out-of-the box support for the bridge_role property in sysconfig-hardware. As a temporary circumvention you could apply the
following change in /etc/sysconfig/scripts/hardware/hwup-ccw-group:

1. locate the line containing
write_setting "portno" "$QETH_PORTNO'
2. insert the following line
write_setting "bridge_role" "$QETH_BRIDGE_ROLE'

Then you can add
QETH_BRIDGE_ROLE=primary
to the config file.

Needless to say that this will not survive a package update. You might
be better served by setting the property in a post-up command for the interface.

I am not really sure whether it makes sense to add more properties to
the sysconfig handling because in the long run persistent CCW device configurations should be done using chzdev, see https://www.ibm.com/developerworks/linux/linux390/s390-tools-1.33.0.html#newtools
On the other hand, this will probably not happen for stretch :-(.

--

Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martina Köderitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 26.04.2017 08:15, Benjamin Jakob Zimmermann wrote:

Ok,
thank you for pointing me into the right direction.

The working solution is the following entry in /etc/network/interfaces:
[...]
allow-ovs br0
iface br0 inet manual

allow-ovs [ccwdev0-encif]
iface [ccwdev0-encif]
pre-up znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary [...]

This way both interfaces come up as soon as I am starting open vswitch ('systemctl start openvswitch-switch').

I did not manage to set bridge_role in the post-up, since it is already online at that point of time.
I had also no success with changes in /etc/sysconfig/scripts/ hardware/hwup-ccw-group.

Do you know if 'chzdev' will be in future s390-tools in stretch?

[...]
Well, it's contained in the upstream source package, so it would just be
a matter of including the binaries lszdev and chzdev (plus the man pages).
The other thing is that one has to get rid of the old-style config
files, e.g. by not installing them in the first place, which what Ubuntu
did.
It might be nice if the Ubuntu changes to s390-tools and
d-i/sysconfig-writer could be backported to Debian (Dimitri?).

--

Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martina Köderitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

--001a114d71a801bb44054e0bc360
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Ok,
thank you for pointing me into the right direction.

The working solution is the following entry in /etc/network/interfaces:
[...]
allow-ovs br0
iface br0 inet manual

allow-ovs [ccwdev0-encif]
iface [ccwdev0-encif]
pre-up znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary
[...]

This way both interfaces come up as soon as I am starting open vswitch ('systemctl start openvswitch-switch').

I did not manage to set bridge_role in the post-up, since it is already
online at that point of time.
I had also no success with changes in /etc/sysconfig/scripts/ hardware/hwup-ccw-group.

Do you know if 'chzdev' will be in future s390-tools in stretch?

2017-04-25 15:10 GMT+02:00 Viktor Mihajlovski <[email protected]>:

On 25.04.2017 13:44, Benjamin Jakob Zimmermann wrote:

Hello,
I am using debian stretch and I am trying to have openvswitch to work

right

after rebooting the machine.

So far, I manually configure the card with znetconf and then start openvswitch and then manually bring up the interfaces.

To visualize my approach, I list the commands (bridge and port had

already

been added to ovs beforehand):
# znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary
# systemctl start openvswitch-switch
# ip l s [ccwdev0] up
# ip l s br0 up

Everything works out fine, I can now live migrate vm's via virsh.

What options do I have to add to /etc/sysconfig/hardware/config-ccw-0.0.[ccwdev0] to set the bridge_role when the interface is brought up?

Best,
Benjamin.

Hi,

I fear there's no out-of-the box support for the bridge_role property in sysconfig-hardware. As a temporary circumvention you could apply the following change in /etc/sysconfig/scripts/hardware/hwup-ccw-group:

1. locate the line containing
write_setting "portno" "$QETH_PORTNO'
2. insert the following line
write_setting "bridge_role" "$QETH_BRIDGE_ROLE'

Then you can add
QETH_BRIDGE_ROLE=primary
to the config file.

Needless to say that this will not survive a package update. You might
be better served by setting the property in a post-up command for the interface.

I am not really sure whether it makes sense to add more properties to
the sysconfig handling because in the long run persistent CCW device configurations should be done using chzdev, see https://www.ibm.com/developerworks/linux/linux390/s390-tools-1.33.0.html# newtools
On the other hand, this will probably not happen for stretch :-(.

--

Mit freundlichen Grüßen/Kind Regards
Viktor Mihajlovski

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martina Köderitz
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

--001a114d71a801bb44054e0bc360
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir="ltr"><div><div><div>Ok,<br></div>thank you for pointing me into the right direction.<br><br></div>The working solution is the following entry in /etc/network/interfaces:<br>[...]<br></div><div>allow-ovs br0<br></div><div>iface br0 inet manual<

<br></div><div>allow-ovs [ccwdev0-encif]<br></div><div>iface [ccwdev0-encif]<br></div><div>         pre-up znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary<br>[...]<br><br></div><div>This way both interfaces come up as soon as I am

starting open vswitch (&#39;systemctl start openvswitch-switch&#39;).<br><br></div><div>I did not manage to set bridge_role in the post-up, since it is already online at that point of time.<br></div><div>I had also no success with changes in /etc/
sysconfig/scripts/<wbr>hardware/hwup-ccw-group.<br><br></div><div>Do you know if &#39;chzdev&#39; will be in future s390-tools in stretch?<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2017-04-25 15:10 GMT+02:00 Viktor Mihajlovski <
span dir="ltr">&lt;<a href="mailto:[email protected]" target="_blank">[email protected]</a>&gt;</span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div
class="h5">On <a href="tel:25.04.2017%2013" value="+12504201713">25.04.2017 13</a>:44, Benjamin Jakob Zimmermann wrote:<br>
&gt; Hello,<br>
&gt; I am using debian stretch and I am trying to have openvswitch to work right<br>
&gt; after rebooting the machine.<br>
&gt;<br>
&gt; So far, I manually configure the card with znetconf and then start<br> &gt; openvswitch and then manually bring up the interfaces.<br>
&gt;<br>
&gt; To visualize my approach, I list the commands (bridge and port had already<br>
&gt; been added to ovs beforehand):<br>
&gt; # znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary<br>
&gt; # systemctl start openvswitch-switch<br>
&gt; # ip l s [ccwdev0] up<br>
&gt; # ip l s br0 up<br>
&gt;<br>
&gt; Everything works out fine, I can now live migrate vm&#39;s via virsh.<br> &gt;<br>
&gt; What options do I have to add to<br>
&gt; /etc/sysconfig/hardware/<wbr>config-ccw-0.0.[ccwdev0] to set the bridge_role<br>
&gt; when the interface is brought up?<br>
&gt;<br>
&gt; Best,<br>
&gt; Benjamin.<br>
&gt;<br>
</div></div>Hi,<br>

I fear there&#39;s no out-of-the box support for the bridge_role property in<br>
sysconfig-hardware. As a temporary circumvention you could apply the<br> following change in /etc/sysconfig/scripts/<wbr>hardware/hwup-ccw-group:<br>

1. locate the line containing<br>
write_setting &quot;portno&quot; &quot;$QETH_PORTNO&#39;<br>
2. insert the following line<br>
write_setting &quot;bridge_role&quot; &quot;$QETH_BRIDGE_ROLE&#39;<br>

Then you can add<br>
 QETH_BRIDGE_ROLE=primary<br>
to the config file.<br>

Needless to say that this will not survive a package update. You might<br>
be better served by setting the property in a post-up command for the<br> interface.<br>

I am not really sure whether it makes sense to add more properties to<br>
the sysconfig handling because in the long run persistent CCW device<br> configurations should be done using chzdev, see<br>
<a href="https://www.ibm.com/developerworks/linux/linux390/s390-tools-1.33.0.html#newtools" rel="noreferrer" target="_blank">https://www.ibm.com/<wbr>developerworks/linux/linux390/<wbr>s390-tools-1.33.0.html#<wbr>newtools</a><br>
On the other hand, this will probably not happen for stretch :-(.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>

Mit freundlichen Grüßen/Kind Regards<br>
   Viktor Mihajlovski<br>

IBM Deutschland Research &amp; Development GmbH<br>
Vorsitzender des Aufsichtsrats: Martina Köderitz<br>
Geschäftsführung: Dirk Wittkopp<br>
Sitz der Gesellschaft: Böblingen<br>
Registergericht: Amtsgericht Stuttgart, HRB 243294<br>

</font></span></blockquote></div><br></div>

--001a114d71a801bb44054e0bc360--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 26 April 2017 at 12:17, Viktor Mihajlovski
<[email protected]> wrote:

On 26.04.2017 08:15, Benjamin Jakob Zimmermann wrote:

Ok,
thank you for pointing me into the right direction.

The working solution is the following entry in /etc/network/interfaces:
[...]
allow-ovs br0
iface br0 inet manual

allow-ovs [ccwdev0-encif]
iface [ccwdev0-encif]
pre-up znetconf -a [ccwdev0] -o layer2=1 -o bridge_role=primary
[...]

This way both interfaces come up as soon as I am starting open vswitch
('systemctl start openvswitch-switch').

I did not manage to set bridge_role in the post-up, since it is already
online at that point of time.
I had also no success with changes in /etc/sysconfig/scripts/
hardware/hwup-ccw-group.

Do you know if 'chzdev' will be in future s390-tools in stretch?

[...]
Well, it's contained in the upstream source package, so it would just be
a matter of including the binaries lszdev and chzdev (plus the man pages). The other thing is that one has to get rid of the old-style config
files, e.g. by not installing them in the first place, which what Ubuntu
did.
It might be nice if the Ubuntu changes to s390-tools and
d-i/sysconfig-writer could be backported to Debian (Dimitri?).

Yeah, in Ubuntu we kind of cheat. The installer is using sysconfig
stuff, but at the end of the install uses chzdev to take a dump of the
running configuration and store that on disk. This way all installed
systems only use chzdev/lszdev.

You can install and use ubuntu package, and chzdev/lszdev configs are
not conflicting with existing stuff as they simply generate udev rules
that one places in /etc/udev/rules.d/ dir.

I was late on many things for stretch =/

Ideally I was hoping to have full chzdev support in d-i, such that one
can preseed any devices, with any of the supported args (e.g. to be
able to install the system with e.g. bridge_role=primary et al)

--
Regards,

Dimitri.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

To: [email protected] (Debian S/390 Team)
Copy: [email protected] (Benjamin Jakob Zimmermann)

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --NVPqom1dW3WSLMvPxVmnCiObXAtUlSdat
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 04/26/2017 02:05 PM, Dimitri John Ledkov wrote:

Yeah, in Ubuntu we kind of cheat. The installer is using sysconfig
stuff, but at the end of the install uses chzdev to take a dump of the running configuration and store that on disk. This way all installed
systems only use chzdev/lszdev.

You can install and use ubuntu package, and chzdev/lszdev configs are
not conflicting with existing stuff as they simply generate udev rules
that one places in /etc/udev/rules.d/ dir.

I was late on many things for stretch =/

Ideally I was hoping to have full chzdev support in d-i, such that one
can preseed any devices, with any of the supported args (e.g. to be
able to install the system with e.g. bridge_role=primary et al)

FWIW, you don't need to hold back on git commits to d-i for chzdev
support even during freeze time. We can also negotiate uploads to
experimental for s390-tools if needed.

Now if something like Viktor's suggestion would've worked, I think we
could've fixed stretch using that as well. But then it's true that
chzdev should be the way forward. And there's too little man power to
just make it happen in Debian right now.[*]

Kind regards
Philipp Kern

[*] I hold that Ubuntu could've just made it happen within Debian
without much trouble. Even though I sort of understand the context why
that didn't happen.



--NVPqom1dW3WSLMvPxVmnCiObXAtUlSdat--

-----BEGIN PGP SIGNATURE-----

iQFFBAEBCAAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAlkBL7MRHHBoaWxAcGhp bGtlcm4uZGUACgkQRG4lRTXQVuzTxQgAy0iGASLSB5MSuIKZdZBZecPfVbMvUY/l B6ZWo6oczb3SKUE1Shtht079cxO6X1YPpgCYaVx8bikBQwunt0SxkGh/x5sWKgdF 8RS3greNR4YkhHiH5pB+am85DadAWaOZi+WFwf5r4S7kE58UvzmfMx5LoGuN7alP o0gVQVsM55DpMiB+HZ6iZYnOkn3Cwx5WlcxBuhqn0BwEkfZ5x5WJd/2viXdnidTe eE/pG3rYZFRhIOJHnAAZFjw/whyxRv3TFE1CvMG8yTxb6RvDo5G1vMHv9+9uVosB 27PtvEmxQv8EaXBuNyM1dI+MN8UkY6UmP29DxOTIrNbPBal0u7NDBg==
=3C5M
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Is there any progress on this please ? Debian too deserves the full set of S390-tools, especially lszdef and chzdef. How can we otherwise define and configure persistent new networking devices in s390x ?

Thanks,

Peter J. Jansen

Sent from Mail for Windows 10


<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/
html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
..MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}

</style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Is there any progress on this please ? Debian too deserves the full set of S390-tools, especially lszdef and

chzdef. How can we otherwise define and configure persistent new networking devices in s390x ?</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Thanks,</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Peter J. Jansen</p><p class=
MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi,

On 29 November 2017 at 20:00, Peter Jansen <[email protected]> wrote:

Is there any progress on this please ? Debian too deserves the full set of S390-tools, especially lszdef and chzdef. How can we otherwise define and configure persistent new networking devices in s390x ?

thank you for your email. You appear to be responding to some email,
but I am lacking the context for your reply.

Could you please elaborate where the discussion has started? E.g. link
to the start of the thread?

Thanks,

Peter J. Jansen

Sent from Mail for Windows 10

--
Regards,

Dimitri.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)