<div dir='auto'><div><br><div class="gmail_extra"><br><div class="gmail_quote">Den 8 jan. 2018 08:32 skrev Yedidyah Bar David <didi@redhat.com>:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><div><div class="elided-text">On Mon, Jan 8, 2018 at 1:36 AM, Sam McLeod <span dir="ltr"><<a href="mailto:mailinglists@smcleod.net">mailinglists@smcleod.net</a>></span> wrote:<br><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thank you for the information Dan, Dominik and Didi,<div><br></div><div>To avoid logging yet another bug for this issue, I've updated bug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1459229">https://bugzilla.redhat.com/show_bug.cgi?id=1459229</a> as you've mentioned with the brief of our conversation here.</div><div><br></div><div>By the way, it is very useful to name a bonded interface things other than bondXYZ, for example, you might have 6 bonds, each of a different network or native VLAN.</div><div>It helps with debugging, troubleshooting and logging if the interface is named after the (native) network, e.g. your iSCSI storage network might have a bond called 'storage', while your management or hypervisor network might have a bond named 'mgmt' then perhaps you have 'data' bond that might have several vlans off it such as 'db' (database), 'dmz', 'staff' etc... depending on how and where you chop your network up.</div></div></blockquote><div><br></div><div>When I was a sysadmin I used to call my bonds bondFUNCTION.<br><br></div><div>This way I both had a prefix 'bond' that readily showed it's<br></div><div>a bond, and a suffix showing its function.<br><br></div><div>IMO oVirt should allow any bond names. If we do decide to limit<br></div><div>them at all, I'd limit only in a negative way - what's not<br></div><div>allowed. E.g. it makes sense to me if we reject prefixes that<br></div><div>are common for non-bonds (eth, en, wl, br etc), but even that<br></div><div>I am not sure is so important.<br></div></div></div></div></div></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">I agree, while at the same time, I don't understand why you would want to "label" a bond. Even if it's untagged, since you can label the bridge that's ontop of it? So even if the bond is called "bond0", the bridge can be called "data", or whatever, to ease diagnozing etc.</div><div dir="auto"><br></div><div dir="auto">What if it's tagged? Would you want to label both bond, vlan and bridge? Like "foobond", "barvlan" and "bazbridge"?</div><div dir="auto"><br></div><div dir="auto">/K</div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div dir="ltr"><div><div class="elided-text"><div></div><div> </div><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div>
<div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div dir="auto" style="color:rgb( 0 , 0 , 0 );letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;word-wrap:break-word"><div dir="auto" style="word-wrap:break-word"><div style="color:rgb( 0 , 0 , 0 );font-family:'helvetica';font-size:12px;font-style:normal;font-weight:normal;letter-spacing:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br>--<br>Sam McLeod<br><a href="https://smcleod.net">https://smcleod.net</a><br><a href="https://twitter.com/s_mcleod">https://twitter.com/s_mcleod</a></div></div></div></div>
</div>
<div><div><div><br><blockquote><div>On 7 Jan 2018, at 6:08 pm, Yedidyah Bar David <<a href="mailto:didi@redhat.com">didi@redhat.com</a>> wrote:</div><br><div><div dir="ltr"><div><div class="elided-text">On Fri, Jan 5, 2018 at 7:44 AM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com">danken@redhat.com</a>></span> wrote:<br><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div><div>On Thu, Jan 4, 2018 at 5:50 AM, Sam McLeod <<a href="mailto:mailinglists@smcleod.net">mailinglists@smcleod.net</a>> wrote:<br>
> I'm having a problem where when setting up hosted engine deployment it fails<br>
> stating that the selected bond name is bad.<br>
><br>
> "code=25, message=bad bond name(s): mgmt)"<br>
><br>
> - Is there a problem similar to<br>
> <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1519807">https://bugzilla.redhat.com/show_bug.cgi?id=1519807</a> that's known?<br></div></div></blockquote><div><br></div><div>Please note that this is just but one bug in a series/tree of<br></div><div>related bugs, some of which are open. If you decide to follow<br></div><div>Dan's suggestion, perhaps reuse one of the others, or perhaps<br></div><div>even better - open a new one, and eventually one or more will<br></div><div>be closed as duplicate of one or more of the others. Sadly,<br></div><div>not all of them link properly to each other, and at least one<br></div><div>which was fixed caused another bug, so the fix was reverted.<br></div><div>See also e.g. all of the discussion in:<br><br><a href="https://bugzilla.redhat.com/show_bug.cgi?id=1459229">https://bugzilla.redhat.com/show_bug.cgi?id=1459229</a><br><br></div><div> </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb( 204 , 204 , 204 );padding-left:1ex"><div><div>
> - If it seems to be this bug, is it preferred that I simply update the<br>
> existing, closed issue as I have done, or open a new bug?<br>
><br>
> --<br>
> Sam McLeod<br>
> <a href="https://smcleod.net/">https://smcleod.net</a><br>
> <a href="https://twitter.com/s_mcleod">https://twitter.com/s_mcleod</a><br>
<br>
</div></div>I see that you are trying to use a bond interface named "mgmt".<br>
To avoid confusion while debugging a system, Vdsm has opted to allow<br>
only bond names starting with "bond" followed by one or more decimal<br>
digits. Anything else is considered "bad bond".<br>
<br>
I prefer keeping the "bond" prefix compulsory, but I'd like to hear<br>
why using different names is useful.<br>
<br>
You can reopen this bug, but please move it to vdsm and rename it: it<br>
should be something like "Allow any bondXYZ name for bonds" or "Allow<br>
any bond name" and explain there why it is a good idea.<br>
<br>
Dominik, is there an Engine-side limitation on bond names?<br>
<div><div>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@ovirt.org">Users@ovirt.org</a><br>
<a href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div>Didi<br></div>
</div></div>
</div></blockquote></div><br></div></div></div></div></blockquote></div><br><br clear="all"><br>-- <br><div>Didi<br></div>
</div></div>
_______________________________________________
<br>Users mailing list
<br>Users@ovirt.org
<br>http://lists.ovirt.org/mailman/listinfo/users
<br></div></blockquote></div><br></div></div></div>