[caasp-beta] Micro OS NIC bonding

[David Mace]

Hi Thorsten

Having some issues;

I provisioned a physical server using the autoyast.xml from the CaaS
admin server and I also put those network bonding changes I detailed in
the previous email.

The CaaS worker node completed the installation OK and I was able to SSH
from the admin server.

I could see that the network bonding worked. The devices "em1" and "em2"
were bonded to "bond0" I could ping the server from any host on the network


The CaaS worker node appeared in the Velum UI and I was able to accept
the host.

However when I then tried to add it to the Kubernetes cluster this
failed and showed the worker with a red cross in the Velum UI.


I put the log "/var/log/messages" for the CaaS worker node in a gist here:

https://gist.github.com/megamaced/4adaaeb42f4ca4f5bd937851b8d9ad5b


I noticed this error in the log:

salt-minion[2785]: [ERROR   ] Interface eth0 not found.


This suggests to me maybe eth0 is hard-coded somewhere in a Salt state?
Obviously eth0 is very likely to be valid for a virtual machine, but in
my experience physical machine network devices are more varied like
"em1" or "p6p1" or in my case "bond0"

Cheers

David



On 27/10/17 06:25, Thorsten Kukuk wrote:
> Hi,
>
> On Thu, Oct 26, David Mace wrote:
>
>> Hi,
>>
>> Is it supported to edit the autoyast.xml provided by the CaaSP admin
>> node with NIC bonding settings. For example;
> Editing the autoyast.xml profile is allowed. If we support that depends
> on what the problem is, like with SLES. If an autoyast bug itself, we
> will support. If a problem with the customers autoyast profile, we will
> not support this.
> Bonding of NICs: if all needed tools are there, it is fine with us.
> If not, then this needs a feature request.
>
>> And does the MicroOS support Autoyast pre-scripts? For example, we
>> replace the "nic1" and "nic2" values above with a pre-script which
>> detects the first two valid devices
> We use already script sections in the default autoyast profile.
> If it is a first stage functionality, the script should be executed
> correctly. If not and it is a autoyast bug, we will fix it. If it
> is a problem with the script itself, we can of course not support that.
> If you choose an autoyast option, which exist or is executed only in
> the second stage of autoyast: since we don't have this, this is not
> supported.
>
>   Thorsten
>

-- 
David Mace
Senior Systems Architect
Smartodds Limited.

Unit 531 Highgate Studios
53-79 Highgate Road
London NW5 1TL

email: david.mace at smartodds.co.uk
+44 (0)20 7482 9300          (tel)
+44 (0)20 7482 3682          (fax)
+44 (0)77 4339 7664          (mobile)


______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

This e-mail and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 74820223 and delete the material from your systems. Smartodds is a business carried on by Smartodds Limited, a company registered with the Registrar of Companies for England and Wales with number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road, London NW5 1TL