From rob.decanha-knight at suse.com  Mon Mar  5 15:08:33 2018
From: rob.decanha-knight at suse.com (Rob de Canha-Knight)
Date: Mon, 5 Mar 2018 22:08:33 +0000
Subject: [caasp-beta] Use another interface after install
Message-ID: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2891 bytes
Desc: image001.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1588 bytes
Desc: image002.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1384 bytes
Desc: image003.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1369 bytes
Desc: image004.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1981 bytes
Desc: image005.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1549 bytes
Desc: image006.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/83a1d861/attachment-0005.png>

From Liam.McCafferty at smartodds.co.uk  Mon Mar  5 15:31:15 2018
From: Liam.McCafferty at smartodds.co.uk (Liam McCafferty)
Date: Mon, 5 Mar 2018 22:31:15 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
Message-ID: <a91d3444-bd17-4f99-8463-c19f164d111c@smartodds.co.uk>

Hi stephane,

We ran into this issue upon initial install on release day and we ended up creating a bond called eth0(messy i know) inside the autoyast.In the newer versions of  caas (you would have to update to latest version of the admin node before the bootstrap) saltstack actually looks at the grains I believe to set the interface name so you should be ok.

We have recently also updated from 1g to 10g networking in the cluster but as caas does not like us changing the interface name we simply changed the actually bond binding to 10g nics and updated dhcp with the reservation with the new mac. as far as caas is concerned we have not changed anything and this has been running fine in production for around a week now. I plan on doing the first update since this change later this week so lets see if it lives.

Although this upgrade is completely unsupported by suse it seems to work :D.


If you like I should be able to send over the section of autoyast dealing with bonding tomorrow?

This was sent from my phone so please excuse my complete lack of punctuation.

Cheers,

Liam

Sent from BlueMail

On 5 Mar 2018, 10:08 pm, at 10:08 pm, Rob de Canha-Knight <rob.decanha-knight at suse.com> wrote:
>Hi Stephane,
>
>
>
>In general, changing the network interface setup after install is not
>possible and I believe it is unsupported at this time.
>
>
>
>If you?ve got a mix of KVM and physical nodes the best thing to do is
>to download the autoyast generated by the admin node and modify it. You
>can then serve it up yourself from a normal SLES machine and Apache.
>
>That way you can have an autoyast suitable for KVM based VMs and a
>different autoyast file suitable for the physical hosts with network
>bonding.
>
>I strongly recommend setting up the bond inside of the autoyast file
>directly. I don?t however have any examples of how to do this.
>
>You can then reinstall the worker nodes or the cluster and they?ll get
>more appropriate installation settings to deal with network bonding.
>
>
>
>We also recently released some updates to CaaS Platform to remove the
>hardcoded eth0 references and instead use the default network interface
>inside all of the salt states/components. In your case this will be
>bond0 (but only if setup correctly or like that during install).
>
>So please make sure that your existing cluster is up to date both admin
>and worker nodes but also more importantly make sure you?re enabling
>updates during install for when you reinstall the cluster (this can be
>set in the autoyast file and is enabled by default in the autoyast I
>think as long as a registration code was provided to the admin node
>during installation.
>
>You?ll need all the <do_registration> and <reg_code> and
><install_updates> filled in correctly and enabled.
>
>Further information on updates to a cluster the process and how to
>recover from errors can be found at
>https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update
>
>
>
>
>We have a couple of customers that have achieved bonding network cards
>with CaaSP. I am adding in Liam to this thread as he was successful in
>achieving this and he may be able to share some examples or some
>insights into network bonding. Anything you?re able to share or input
>to the discussion is much appreciated Liam :)
>
>
>
>If I?ve said anything that?s incorrect then someone from Engineering
>will be able to comment (it?s been a while since I?ve looked into the
>issue of network bonding).
>
>
>
>Kind regards,
>
>Rob
>
>
>
>-----
>
>Rob de Canha-Knight
>
>EMEA Platform and Management Technical Strategist
>
>SUSE
>
>rob.decanha-knight at suse.com
>
>(P)  +44 (0) 1635 937689
>
>(M) +44 (0) 7869 113493
>
>(TW) rssfed23
>
>I work on GMT time zone
>
>----
>
>From: <caasp-beta-bounces at lists.suse.com> on behalf of "Le Bihan
>St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com>
>Date: Monday, 26 February 2018 at 10:53
>To: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>
>Subject: [caasp-beta] Use another interface after install
>
>
>
>Hello,
>
>
>
>My admin is installed in KVM, so he use eth0 for kubernetes.
>
>I want to add a physical node (baremetal) to kubernetes cluster. But on
>it, I want to use a bond with two card 10Go.
>
>
>
>But when I join host baremetal to cluster, deployement want to use
>eth0.
>
>
>
>How I can fix interface change just for this host ? I think it?s on
>Saltstack deployement, but I don?t want who I can change it ?
>
>
>
>Any idea ?
>
>
>
>Regards,
>
>
>
>
>
>St?phane Le Bihan
>
>SDE/DSI/IPR/SSD/UNX
>
>90, Boulevard Pasteur - 75015 Paris
>
>Web: www.amundi.com<http://www.amundi.com>
>
>Tel: +33 1 76 32 32 08
>
>Tel Unix Team: +33 1 76 32 02 30
>
>@: stephane.lebihan at amundi.com
>
>@: sits.unix at amundi.com
>
>
>
>Visit us on:
>
>
>
>
>
>
>
>
>______________________________________________________________________
>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) 7482 0077 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 540 Highgate Studios, 53-79 Highgate
>Road, London NW5 1TL

______________________________________________________________________
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) 7482 0077 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180305/046c4c15/attachment.htm>

From stephane.lebihan at amundi.com  Mon Mar  5 23:54:43 2018
From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=)
Date: Tue, 6 Mar 2018 06:54:43 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
Message-ID: <DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 2890 bytes
Desc: image007.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image018.png
Type: image/png
Size: 2891 bytes
Desc: image018.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image019.png
Type: image/png
Size: 1588 bytes
Desc: image019.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image020.png
Type: image/png
Size: 1384 bytes
Desc: image020.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image021.png
Type: image/png
Size: 1369 bytes
Desc: image021.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image022.png
Type: image/png
Size: 1981 bytes
Desc: image022.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image023.png
Type: image/png
Size: 1549 bytes
Desc: image023.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1587 bytes
Desc: image006.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1383 bytes
Desc: image009.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 1368 bytes
Desc: image011.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1980 bytes
Desc: image013.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 1548 bytes
Desc: image015.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180306/460aaa8c/attachment-0011.png>

From Rick.Ashford at suse.com  Tue Mar  6 15:06:38 2018
From: Rick.Ashford at suse.com (Rick Ashford)
Date: Tue, 6 Mar 2018 22:06:38 +0000
Subject: [caasp-beta] Troubleshooting initial deployment
Message-ID: <1520373997.15965.4.camel@suse.com>

I'm doing the initial deployment of a test cluster and I ran into an
error with the deployment (I forgot to add the update repos and patch
before deploying).

Now that I think I have the issue fixed, can I tell Velum to go try and
deploy again, or am I forced to rebuild everything?  If I can retry,
what do I need to do to make that happen?

-- 
Rick Ashford
Sales Engineering Manager - West
rick.ashford at suse.com
M:(512)731-3035

From abonilla at suse.com  Tue Mar  6 15:27:47 2018
From: abonilla at suse.com (Alejandro Bonilla)
Date: Tue, 6 Mar 2018 22:27:47 +0000
Subject: [caasp-beta] Troubleshooting initial deployment
In-Reply-To: <1520373997.15965.4.camel@suse.com>
References: <1520373997.15965.4.camel@suse.com>
Message-ID: <10535284-93EF-44B0-AD05-509AC4E88196@suse.com>



> On Mar 6, 2018, at 3:06 PM, Rick Ashford <Rick.Ashford at suse.com> wrote:
> 
> I'm doing the initial deployment of a test cluster and I ran into an
> error with the deployment (I forgot to add the update repos and patch
> before deploying).
> 
> Now that I think I have the issue fixed, can I tell Velum to go try and
> deploy again, or am I forced to rebuild everything?  If I can retry,
> what do I need to do to make that happen?

What is the status of the deployed cluster? What succeeded and what failed?

From rob.decanha-knight at suse.com  Wed Mar  7 04:41:12 2018
From: rob.decanha-knight at suse.com (Rob de Canha-Knight)
Date: Wed, 7 Mar 2018 11:41:12 +0000
Subject: [caasp-beta] Troubleshooting initial deployment
In-Reply-To: <10535284-93EF-44B0-AD05-509AC4E88196@suse.com>
References: <1520373997.15965.4.camel@suse.com>
	<10535284-93EF-44B0-AD05-509AC4E88196@suse.com>
Message-ID: <0D51F183-1AFD-42D6-98D0-168640A96594@suse.com>

Rick,

You can kick off the deployment manually by running
docker exec -it $(docker ps | grep salt-master | awk '{print $1}') salt-run -l debug state.orchestrate orch.kubernetes

Look for the first red error (all subsequent ones will be cascading failures as a result of the first one) and that'll be the root cause of your issue

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23 <https://twitter.com/rssfed23>
I work on GMT time zone
----

?On 06/03/2018, 22:28, "caasp-beta-bounces at lists.suse.com on behalf of Alejandro Bonilla" <caasp-beta-bounces at lists.suse.com on behalf of abonilla at suse.com> wrote:

    
    
    > On Mar 6, 2018, at 3:06 PM, Rick Ashford <Rick.Ashford at suse.com> wrote:
    > 
    > I'm doing the initial deployment of a test cluster and I ran into an
    > error with the deployment (I forgot to add the update repos and patch
    > before deploying).
    > 
    > Now that I think I have the issue fixed, can I tell Velum to go try and
    > deploy again, or am I forced to rebuild everything?  If I can retry,
    > what do I need to do to make that happen?
    
    What is the status of the deployed cluster? What succeeded and what failed?
    _______________________________________________
    caasp-beta mailing list
    caasp-beta at lists.suse.com
    http://lists.suse.com/mailman/listinfo/caasp-beta
    


From Rick.Ashford at suse.com  Wed Mar  7 10:03:43 2018
From: Rick.Ashford at suse.com (Rick Ashford)
Date: Wed, 7 Mar 2018 17:03:43 +0000
Subject: [caasp-beta] Troubleshooting initial deployment
In-Reply-To: <0D51F183-1AFD-42D6-98D0-168640A96594@suse.com>
References: <1520373997.15965.4.camel@suse.com>
	<10535284-93EF-44B0-AD05-509AC4E88196@suse.com>,
	<0D51F183-1AFD-42D6-98D0-168640A96594@suse.com>
Message-ID: <C8B5AF6D-2868-4C0B-B85D-B6A8F4E6311E@suse.com>

Thanks. Worked like a champ. 

Rick Ashford
Sales Engineering Manager - West
rick.ashford at suse.com
(512)731-3035

> On Mar 7, 2018, at 5:41 AM, Rob de Canha-Knight <rob.decanha-knight at suse.com> wrote:
> 
> Rick,
> 
> You can kick off the deployment manually by running
> docker exec -it $(docker ps | grep salt-master | awk '{print $1}') salt-run -l debug state.orchestrate orch.kubernetes
> 
> Look for the first red error (all subsequent ones will be cascading failures as a result of the first one) and that'll be the root cause of your issue
> 
> -----
> Rob de Canha-Knight
> EMEA Platform and Management Technical Strategist
> SUSE
> rob.decanha-knight at suse.com
> (P)  +44 (0) 1635 937689
> (M) +44 (0) 7869 113493
> (TW) rssfed23 <https://twitter.com/rssfed23>
> I work on GMT time zone
> ----
> 
> ?On 06/03/2018, 22:28, "caasp-beta-bounces at lists.suse.com on behalf of Alejandro Bonilla" <caasp-beta-bounces at lists.suse.com on behalf of abonilla at suse.com> wrote:
> 
> 
> 
>> On Mar 6, 2018, at 3:06 PM, Rick Ashford <Rick.Ashford at suse.com> wrote:
>> 
>> I'm doing the initial deployment of a test cluster and I ran into an
>> error with the deployment (I forgot to add the update repos and patch
>> before deploying).
>> 
>> Now that I think I have the issue fixed, can I tell Velum to go try and
>> deploy again, or am I forced to rebuild everything?  If I can retry,
>> what do I need to do to make that happen?
> 
>    What is the status of the deployed cluster? What succeeded and what failed?
>    _______________________________________________
>    caasp-beta mailing list
>    caasp-beta at lists.suse.com
>    http://lists.suse.com/mailman/listinfo/caasp-beta
> 
> 

From romninja at gmail.com  Wed Mar  7 20:12:24 2018
From: romninja at gmail.com (romninja)
Date: Thu, 8 Mar 2018 08:42:24 +0530
Subject: [caasp-beta] Multipath I/O on CAASP 2.0
Message-ID: <CALWTv7sgOF8X8Ei48=O-bm+km7vKiGVTQy9h_ox-=xDGUiNdkw@mail.gmail.com>

Hi All,

We are evaluating CAASP 2.0 for a project of ours. We need multipathing I/O
for our project, but we are unable to install multipath-tools on CAASP 2.0.

Is there any way we can install multipath-tools on CAASP 2.0?

Any help would be appreciated.

With Regards,
romninja
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180308/180b0a01/attachment.htm>

From special011 at gmail.com  Wed Mar  7 22:33:46 2018
From: special011 at gmail.com (Jerry Hwang)
Date: Wed, 7 Mar 2018 21:33:46 -0800
Subject: [caasp-beta] velum troubleshoot
In-Reply-To: <CANrne0S2sAc2ZS5Q7i86kkkhbTEpoShKm=Z3d-s8giDLjc627g@mail.gmail.com>
References: <CANrne0SZ4DR_bH1Wmwvy+=noacXoL-UbPGpb62voeeEABnLW7g@mail.gmail.com>
	<1515876628007.92646@smartodds.co.uk>
	<CANrne0QSG3ZVj1oQf50j4xEtK7=NwrOonrcHVGT5MsjoNQzGKg@mail.gmail.com>
	<1515877672987.7123@smartodds.co.uk>
	<CANrne0SQJDbMnziBmh+_Q8QYoCUqn9jkPrCPG27KPvp4R3K2fw@mail.gmail.com>
	<1515878635948.68938@smartodds.co.uk>
	<CANrne0SAkiboQ5zhmnEN1exJ1KKPCHoFJNtuappGSBREvqYshw@mail.gmail.com>
	<CANrne0S2sAc2ZS5Q7i86kkkhbTEpoShKm=Z3d-s8giDLjc627g@mail.gmail.com>
Message-ID: <CANrne0R_JbZN8e4cuS5GrL1MUu2a9zVDUx5xdAYL010NBTbpvw@mail.gmail.com>

Hello,

The velum dashboard is still unstable. Does it work well for everyone?
To SUSE team, do you have any kb or tips for troubleshooting velum?

I see this error in dashboard container:
Processing by DashboardController#index as HTML
Completed 500 Internal Server Error in 60111ms (ActiveRecord: 7.1ms)
Velum::SaltApi::SaltConnectionException (Net::ReadTimeout):

In the salt minion container, this repeats with no more clue.
[ERROR   ] Error while bringing up minion for multi-master. Is master at
localhost responding?

However, I don't see any error in salt master or api container.

That's pretty much I see in syslog as well.
It worked well in the beginning, but not so well after a while..
Where I should check further?

Jerry

On Sat, Jan 13, 2018 at 8:00 PM, Jerry Hwang <special011 at gmail.com> wrote:

> I confirmed the admin node reboot (even shutdown) doesn't cause to fail
> kubectl (I even confirmed while the admin node is down, kubectl still
> works, and I also checked kubectl conf points to k8s master node), so it
> must be something related to when the admin node is updated (& subsequently
> rebooted).
> I will check more detail next time the admin node is updated and confirm
> the situation. If you can try, you may also try kubectl soon after you
> initiated the admin node update (& subsequent auto reboot) in the dashboard
> during the process..
>
> Regarding the dashboard loading (taking too long), I see something
> potentially not clean with salt master connection, and I will check
> further..
> Velum::SaltApi::SaltConnectionException (Net::ReadTimeout):
>
> Thanks,
> Jerry
>
> On Sat, Jan 13, 2018 at 1:30 PM, Jerry Hwang <special011 at gmail.com> wrote:
>
>> Okay, what you described is also what I expected.
>> Thanks for the idea.
>>
>> Regards,
>> Jerry
>>
>> On Sat, Jan 13, 2018 at 1:23 PM, Liam McCafferty <
>> Liam.McCafferty at smartodds.co.uk> wrote:
>>
>>> I have never noticed this before so  I just rebooted my admin node and I
>>> can confirm I can still communicate via kubectl to the master node.
>>>
>>>
>>> I have also checked my kube config in ~/.kube/config and I can
>>> see that the cluster server is set to the master server. does
>>> your kubeconfig point to your master node?  Upon checking my admin node I
>>> see it also that it has the haproxy k8 containers which I believe deal
>>> with routing to the k8 api. so if your config is pointed to your admin node
>>> that would make sense that you cant reach the api server.
>>>
>>>
>>>
>>> Cheers,
>>>
>>>
>>> Liam
>>>
>>>
>>>
>>> ------------------------------
>>> *From:* Jerry Hwang <special011 at gmail.com>
>>> *Sent:* 13 January 2018 21:11
>>> *To:* Liam McCafferty
>>> *Cc:* caasp-beta at lists.suse.com
>>> *Subject:* Re: [caasp-beta] velum troubleshoot
>>>
>>> Right, that is also a good point. (I too much focused on the general
>>> idea  :))
>>>
>>> And it seems I can't get to k8s cluster via kubectl (from my local
>>> machine) during admin node upgrade & reboot, is it expected?
>>>
>>> Thanks,
>>> Jerry
>>>
>>> On Sat, Jan 13, 2018 at 1:07 PM, Liam McCafferty <
>>> Liam.McCafferty at smartodds.co.uk> wrote:
>>>
>>>> No Velum runs on standard docker on the caas admin node ( along with a
>>>> salt master and a mariadb and various other containers ) where as
>>>> kubernetes only runs on the master and worker nodes.
>>>>
>>>>
>>>> Hope this helps
>>>>
>>>>
>>>> Regards,
>>>>
>>>>
>>>> Liam
>>>> ------------------------------
>>>> *From:* Jerry Hwang <special011 at gmail.com>
>>>> *Sent:* 13 January 2018 21:02
>>>> *To:* Liam McCafferty
>>>> *Cc:* caasp-beta at lists.suse.com
>>>> *Subject:* Re: [caasp-beta] velum troubleshoot
>>>>
>>>> Ah right, all run in container on kubernetes.
>>>>
>>>> Thanks,
>>>> Jerry
>>>>
>>>> On Sat, Jan 13, 2018 at 12:50 PM, Liam McCafferty <
>>>> Liam.McCafferty at smartodds.co.uk> wrote:
>>>>
>>>>> Hi Jerry,
>>>>>
>>>>>
>>>>> I always put this down to the fact the node has just rebooted, However
>>>>> if you wish to view the velum logs it runs inside a container on the admin
>>>>> node  you can find this container via using a docker ps command then use a
>>>>> docker logs command to get the log output for the container.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>>
>>>>> Liam
>>>>> ------------------------------
>>>>> *From:* caasp-beta-bounces at lists.suse.com <
>>>>> caasp-beta-bounces at lists.suse.com> on behalf of Jerry Hwang <
>>>>> special011 at gmail.com>
>>>>> *Sent:* 13 January 2018 18:50
>>>>> *To:* caasp-beta at lists.suse.com
>>>>> *Subject:* [caasp-beta] velum troubleshoot
>>>>>
>>>>> Hello,
>>>>>
>>>>> Does anyone have a general guideline where or how to check velum?
>>>>>
>>>>> I always observe this message in the browser after admin node update
>>>>> (v2)
>>>>> > We're sorry, but something went wrong.
>>>>> > If you are the application owner check the logs for more information.
>>>>>
>>>>> Eventually I can get back to the admin node (velum), but sometimes it
>>>>> takes long, and I thought if I have a list to check or monitor, it'd useful.
>>>>>
>>>>> And I noticed I can't get to k8s cluster via kubectl (from my local
>>>>> machine) during admin node upgrade & reboot, is it expected?
>>>>>
>>>>> Jerry
>>>>>
>>>>> note: this is to look for some general idea or share, not a support
>>>>> request.
>>>>>
>>>>> ______________________________________________________________________
>>>>> 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)
>>>>> 7482 0077 <+44%2020%207482%200077> 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 540 Highgate Studios, 53-79
>>>>> Highgate Road, London NW5 1TL
>>>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>>>
>>>>> ______________________________________________________________________
>>>>> 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)
>>>>> 7482 0077 <+44%2020%207482%200077> 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
>>>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>>>
>>>>
>>>>
>>>> ______________________________________________________________________
>>>> 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) 7482
>>>> 0077 <+44%2020%207482%200077> 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 540 Highgate Studios, 53-79
>>>> Highgate Road, London NW5 1TL
>>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>>
>>>> ______________________________________________________________________
>>>> 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) 7482
>>>> 0077 <+44%2020%207482%200077> 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
>>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>>
>>>
>>>
>>> ______________________________________________________________________
>>> 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) 7482
>>> 0077 <+44%2020%207482%200077> 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 540 Highgate Studios, 53-79
>>> Highgate Road, London NW5 1TL
>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>
>>> ______________________________________________________________________
>>> 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) 7482
>>> 0077 <+44%2020%207482%200077> 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
>>> <https://maps.google.com/?q=53-79+Highgate+Road,+London+NW5+1TL&entry=gmail&source=g>
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180307/d52e7746/attachment.htm>

From aj at suse.com  Thu Mar  8 08:52:30 2018
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 8 Mar 2018 16:52:30 +0100
Subject: [caasp-beta] Multipath I/O on CAASP 2.0
In-Reply-To: <CALWTv7sgOF8X8Ei48=O-bm+km7vKiGVTQy9h_ox-=xDGUiNdkw@mail.gmail.com>
References: <CALWTv7sgOF8X8Ei48=O-bm+km7vKiGVTQy9h_ox-=xDGUiNdkw@mail.gmail.com>
Message-ID: <a6d61668-754c-778b-97cb-411d5d2417f7@suse.com>

On 2018-03-08 04:12, romninja wrote:
> Hi All,
> 
> We are evaluating CAASP 2.0 for a project of ours. We need multipathing
> I/O for our project, but we are unable to install multipath-tools on
> CAASP 2.0.
> 
> Is there any way we can install multipath-tools on CAASP 2.0?
> 
> Any help would be appreciated.

What exactly are you installing?

I'm curious about your use case, can you tell me a bit more, please?

I'll upload some packages for you, will reply once they're out,

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From aj at suse.com  Thu Mar  8 09:05:45 2018
From: aj at suse.com (Andreas Jaeger)
Date: Thu, 8 Mar 2018 17:05:45 +0100
Subject: [caasp-beta] Multipath I/O on CAASP 2.0
In-Reply-To: <a6d61668-754c-778b-97cb-411d5d2417f7@suse.com>
References: <CALWTv7sgOF8X8Ei48=O-bm+km7vKiGVTQy9h_ox-=xDGUiNdkw@mail.gmail.com>
	<a6d61668-754c-778b-97cb-411d5d2417f7@suse.com>
Message-ID: <aa9b4b9f-3299-4102-5df7-ab216550b3d4@suse.com>

On 2018-03-08 16:52, Andreas Jaeger wrote:
> On 2018-03-08 04:12, romninja wrote:
>> Hi All,
>>
>> We are evaluating CAASP 2.0 for a project of ours. We need multipathing
>> I/O for our project, but we are unable to install multipath-tools on
>> CAASP 2.0.
>>
>> Is there any way we can install multipath-tools on CAASP 2.0?
>>
>> Any help would be appreciated.
> 
> What exactly are you installing?
> 
> I'm curious about your use case, can you tell me a bit more, please?
> 
> I'll upload some packages for you, will reply once they're out,

For multipath you need these 4 packages:
http://users.suse.com/~aj/multipath/

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
   GF: Felix Imend?rffer, Jane Smithard, Graham Norton,
       HRB 21284 (AG N?rnberg)
    GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


From stephane.lebihan at amundi.com  Wed Mar 14 11:42:39 2018
From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=)
Date: Wed, 14 Mar 2018 17:42:39 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
Message-ID: <DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>

Hi all,

We finish to deploy non-production plateform for test.

So I test to install with patching ok on future production server?. Yes it?s bad but I don?t have another plateform for test :D

So after many test.
I start install admin node. After install ok. I?m connect to it.
Configure proxy
Configure /etc/SUSEConnect and register on SCC.
Refresh repository.
Use : transactional-update up and reboot.

After I configure Admin Node by Velum and launch deployement.
But it?s not ok. But may be it?s not same problem.

I have this in /var/log/salt/minion on master :

2018-03-14 17:16:44,779 [salt.state       ][ERROR   ][3511] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-14 17:18:29,522 [salt.loaded.int.grains.core][WARNING ][1763] Unable to find IPv6 record for "3d6fef2c01eb416390f1e6ee6df97449.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

I joined supportconfig off all host.

Have you an idea of problem ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : mardi 6 mars 2018 07:55
? : Rob de Canha-Knight; Liam Mccafferty
Cc : Julien Niedergang; caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2890 bytes
Desc: image001.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.png
Type: image/png
Size: 1587 bytes
Desc: image017.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 1383 bytes
Desc: image024.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image025.png
Type: image/png
Size: 1368 bytes
Desc: image025.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image026.png
Type: image/png
Size: 1980 bytes
Desc: image026.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image027.png
Type: image/png
Size: 1548 bytes
Desc: image027.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028.png
Type: image/png
Size: 2891 bytes
Desc: image028.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image029.png
Type: image/png
Size: 1588 bytes
Desc: image029.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image030.png
Type: image/png
Size: 1384 bytes
Desc: image030.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image031.png
Type: image/png
Size: 1369 bytes
Desc: image031.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image032.png
Type: image/png
Size: 1981 bytes
Desc: image032.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image033.png
Type: image/png
Size: 1549 bytes
Desc: image033.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1587 bytes
Desc: image003.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1383 bytes
Desc: image005.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1368 bytes
Desc: image008.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1980 bytes
Desc: image012.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 1548 bytes
Desc: image016.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_clappcaasa01_180314_1729.tbz
Type: application/octet-stream
Size: 1275815 bytes
Desc: nts_clappcaasa01_180314_1729.tbz
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_clappcaasa01_180314_1729.tbz.md5
Type: application/octet-stream
Size: 33 bytes
Desc: nts_clappcaasa01_180314_1729.tbz.md5
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0001.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_clappcaasm01_180314_1722.tbz
Type: application/octet-stream
Size: 982393 bytes
Desc: nts_clappcaasm01_180314_1722.tbz
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0002.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_clappcaasm01_180314_1722.tbz.md5
Type: application/octet-stream
Size: 33 bytes
Desc: nts_clappcaasm01_180314_1722.tbz.md5
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0003.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_dl360s-101.unix.sits.credit-agricole.fr_180314_1729.tbz
Type: application/octet-stream
Size: 1097470 bytes
Desc: nts_dl360s-101.unix.sits.credit-agricole.fr_180314_1729.tbz
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0004.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_dl360s-101.unix.sits.credit-agricole.fr_180314_1729.tbz.md5
Type: application/octet-stream
Size: 33 bytes
Desc: nts_dl360s-101.unix.sits.credit-agricole.fr_180314_1729.tbz.md5
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0005.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_dl360s-103.unix.sits.credit-agricole.fr_180314_1729.tbz
Type: application/octet-stream
Size: 1100379 bytes
Desc: nts_dl360s-103.unix.sits.credit-agricole.fr_180314_1729.tbz
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0006.dll>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nts_dl360s-103.unix.sits.credit-agricole.fr_180314_1729.tbz.md5
Type: application/octet-stream
Size: 33 bytes
Desc: nts_dl360s-103.unix.sits.credit-agricole.fr_180314_1729.tbz.md5
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/67d6ae9e/attachment-0007.dll>

From rob.decanha-knight at suse.com  Wed Mar 14 14:32:01 2018
From: rob.decanha-knight at suse.com (Rob de Canha-Knight)
Date: Wed, 14 Mar 2018 20:32:01 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
	<DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>
Message-ID: <E73470F1-23F2-4738-9073-BAF809B30C63@suse.com>

Hi Stephane.

I?ve forwarded your mail onto our support and engineering teams for them to take a look as this is a bit beyond me.

I have a feeling it may be related to updating the cluster or network issues somewhere along the line.

The warning about the 10 second timeout is something you don?t need to worry about this is normal when not using ipv6 so please ignore that.

I?ll send an update as and when I?ve got one.

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com>
Date: Wednesday, 14 March 2018 at 17:45
To: Liam Mccafferty <liam.McCafferty at smartodds.co.uk>, Rob de Canha-Knight <rob.decanha-knight at suse.com>
Cc: "caasp-beta at lists.suse.com" <caasp-beta at lists.suse.com>, Julien Niedergang <Julien.Niedergang at suse.com>
Subject: RE: [caasp-beta] Use another interface after install

Hi all,

We finish to deploy non-production plateform for test.

So I test to install with patching ok on future production server?. Yes it?s bad but I don?t have another plateform for test :D

So after many test.
I start install admin node. After install ok. I?m connect to it.
Configure proxy
Configure /etc/SUSEConnect and register on SCC.
Refresh repository.
Use : transactional-update up and reboot.

After I configure Admin Node by Velum and launch deployement.
But it?s not ok. But may be it?s not same problem.

I have this in /var/log/salt/minion on master :

2018-03-14 17:16:44,779 [salt.state       ][ERROR   ][3511] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-14 17:18:29,522 [salt.loaded.int.grains.core][WARNING ][1763] Unable to find IPv6 record for "3d6fef2c01eb416390f1e6ee6df97449.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

I joined supportconfig off all host.

Have you an idea of problem ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : mardi 6 mars 2018 07:55
? : Rob de Canha-Knight; Liam Mccafferty
Cc : Julien Niedergang; caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2891 bytes
Desc: image001.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1588 bytes
Desc: image002.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1384 bytes
Desc: image003.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1369 bytes
Desc: image004.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1981 bytes
Desc: image005.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1549 bytes
Desc: image006.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 2892 bytes
Desc: image007.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1589 bytes
Desc: image008.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1385 bytes
Desc: image009.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1370 bytes
Desc: image010.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 1982 bytes
Desc: image011.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1550 bytes
Desc: image012.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180314/c42b0094/attachment-0011.png>

From stephane.lebihan at amundi.com  Thu Mar 15 00:32:25 2018
From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=)
Date: Thu, 15 Mar 2018 06:32:25 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <E73470F1-23F2-4738-9073-BAF809B30C63@suse.com>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
	<DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>
	<E73470F1-23F2-4738-9073-BAF809B30C63@suse.com>
Message-ID: <DD3BF21C77802042A0BC4AED019A4A7B88075048@SMBX003.ad-its.credit-agricole.fr>

Hi Rob,

Thanks for forward mail.

I test another install last night. Same problem but I noticed another information.
Because I have update I complete ?Enable registry mirror? on velum install. And I noticed docker daemon don?t restart on master node, because daemon.json file is bad.

So I launch a new install ths morning. I let ?Enable registry mirror? disable and I send result.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : mercredi 14 mars 2018 21:32
? : Le Bihan St?phane (AMUNDI-ITS)
Cc : caasp-beta at lists.suse.com; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane.

I?ve forwarded your mail onto our support and engineering teams for them to take a look as this is a bit beyond me.

I have a feeling it may be related to updating the cluster or network issues somewhere along the line.

The warning about the 10 second timeout is something you don?t need to worry about this is normal when not using ipv6 so please ignore that.

I?ll send an update as and when I?ve got one.

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Wednesday, 14 March 2018 at 17:45
To: Liam Mccafferty <liam.McCafferty at smartodds.co.uk<mailto:liam.McCafferty at smartodds.co.uk>>, Rob de Canha-Knight <rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>>
Cc: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>, Julien Niedergang <Julien.Niedergang at suse.com<mailto:Julien.Niedergang at suse.com>>
Subject: RE: [caasp-beta] Use another interface after install

Hi all,

We finish to deploy non-production plateform for test.

So I test to install with patching ok on future production server?. Yes it?s bad but I don?t have another plateform for test :D

So after many test.
I start install admin node. After install ok. I?m connect to it.
Configure proxy
Configure /etc/SUSEConnect and register on SCC.
Refresh repository.
Use : transactional-update up and reboot.

After I configure Admin Node by Velum and launch deployement.
But it?s not ok. But may be it?s not same problem.

I have this in /var/log/salt/minion on master :

2018-03-14 17:16:44,779 [salt.state       ][ERROR   ][3511] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-14 17:18:29,522 [salt.loaded.int.grains.core][WARNING ][1763] Unable to find IPv6 record for "3d6fef2c01eb416390f1e6ee6df97449.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

I joined supportconfig off all host.

Have you an idea of problem ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com> [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : mardi 6 mars 2018 07:55
? : Rob de Canha-Knight; Liam Mccafferty
Cc : Julien Niedergang; caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 2890 bytes
Desc: image013.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 2891 bytes
Desc: image024.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image025.png
Type: image/png
Size: 1588 bytes
Desc: image025.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image026.png
Type: image/png
Size: 1384 bytes
Desc: image026.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image027.png
Type: image/png
Size: 1369 bytes
Desc: image027.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028.png
Type: image/png
Size: 1981 bytes
Desc: image028.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image029.png
Type: image/png
Size: 1549 bytes
Desc: image029.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image030.png
Type: image/png
Size: 2892 bytes
Desc: image030.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image031.png
Type: image/png
Size: 1589 bytes
Desc: image031.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image032.png
Type: image/png
Size: 1385 bytes
Desc: image032.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image033.png
Type: image/png
Size: 1370 bytes
Desc: image033.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image034.png
Type: image/png
Size: 1982 bytes
Desc: image034.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image035.png
Type: image/png
Size: 1550 bytes
Desc: image035.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1587 bytes
Desc: image001.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1383 bytes
Desc: image002.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1368 bytes
Desc: image003.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1980 bytes
Desc: image004.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1548 bytes
Desc: image005.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/9caba360/attachment-0017.png>

From stephane.lebihan at amundi.com  Thu Mar 15 00:43:22 2018
From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=)
Date: Thu, 15 Mar 2018 06:43:22 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DD3BF21C77802042A0BC4AED019A4A7B88075048@SMBX003.ad-its.credit-agricole.fr>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
	<DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>
	<E73470F1-23F2-4738-9073-BAF809B30C63@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B88075048@SMBX003.ad-its.credit-agricole.fr>
Message-ID: <DD3BF21C77802042A0BC4AED019A4A7B8807510B@SMBX003.ad-its.credit-agricole.fr>

Shit same problem on master node :

master:~ # tail -15 /var/log/salt/minion
2018-03-15 06:31:30,315 [salt.utils.http  ][ERROR   ][4190] The client-side certificate path that was passed is not valid: ['/etc/pki/minion.crt', '/etc/pki/minion.key']
2018-03-15 06:31:30,336 [salt.utils.http  ][ERROR   ][4190] The client-side certificate path that was passed is not valid: ['/etc/pki/minion.crt', '/etc/pki/minion.key']
2018-03-15 06:31:30,357 [salt.utils.http  ][ERROR   ][4190] The client-side certificate path that was passed is not valid: ['/etc/pki/minion.crt', '/etc/pki/minion.key']
2018-03-15 06:31:30,378 [salt.utils.http  ][ERROR   ][4190] The client-side certificate path that was passed is not valid: ['/etc/pki/minion.crt', '/etc/pki/minion.key']
2018-03-15 06:32:16,852 [salt.utils.http  ][ERROR   ][5495] The client-side certificate path that was passed is not valid: ['/etc/pki/minion.crt', '/etc/pki/minion.key']
2018-03-15 06:37:29,305 [salt.state       ][ERROR   ][5495] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-15 06:40:23,426 [salt.loaded.int.grains.core][WARNING ][1748] Unable to find IPv6 record for "clappcaasm01.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

But docker.service is started on master.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : jeudi 15 mars 2018 07:32
? : Rob de Canha-Knight
Cc : Julien Niedergang; caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob,

Thanks for forward mail.

I test another install last night. Same problem but I noticed another information.
Because I have update I complete ?Enable registry mirror? on velum install. And I noticed docker daemon don?t restart on master node, because daemon.json file is bad.

So I launch a new install ths morning. I let ?Enable registry mirror? disable and I send result.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : mercredi 14 mars 2018 21:32
? : Le Bihan St?phane (AMUNDI-ITS)
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane.

I?ve forwarded your mail onto our support and engineering teams for them to take a look as this is a bit beyond me.

I have a feeling it may be related to updating the cluster or network issues somewhere along the line.

The warning about the 10 second timeout is something you don?t need to worry about this is normal when not using ipv6 so please ignore that.

I?ll send an update as and when I?ve got one.

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Wednesday, 14 March 2018 at 17:45
To: Liam Mccafferty <liam.McCafferty at smartodds.co.uk<mailto:liam.McCafferty at smartodds.co.uk>>, Rob de Canha-Knight <rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>>
Cc: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>, Julien Niedergang <Julien.Niedergang at suse.com<mailto:Julien.Niedergang at suse.com>>
Subject: RE: [caasp-beta] Use another interface after install

Hi all,

We finish to deploy non-production plateform for test.

So I test to install with patching ok on future production server?. Yes it?s bad but I don?t have another plateform for test :D

So after many test.
I start install admin node. After install ok. I?m connect to it.
Configure proxy
Configure /etc/SUSEConnect and register on SCC.
Refresh repository.
Use : transactional-update up and reboot.

After I configure Admin Node by Velum and launch deployement.
But it?s not ok. But may be it?s not same problem.

I have this in /var/log/salt/minion on master :

2018-03-14 17:16:44,779 [salt.state       ][ERROR   ][3511] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-14 17:18:29,522 [salt.loaded.int.grains.core][WARNING ][1763] Unable to find IPv6 record for "3d6fef2c01eb416390f1e6ee6df97449.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

I joined supportconfig off all host.

Have you an idea of problem ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com> [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : mardi 6 mars 2018 07:55
? : Rob de Canha-Knight; Liam Mccafferty
Cc : Julien Niedergang; caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2890 bytes
Desc: image006.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 1587 bytes
Desc: image007.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1383 bytes
Desc: image008.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1368 bytes
Desc: image009.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1980 bytes
Desc: image010.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 1548 bytes
Desc: image011.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1587 bytes
Desc: image012.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1383 bytes
Desc: image013.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1368 bytes
Desc: image014.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 1980 bytes
Desc: image015.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 1548 bytes
Desc: image016.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.png
Type: image/png
Size: 2891 bytes
Desc: image017.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image018.png
Type: image/png
Size: 1588 bytes
Desc: image018.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image019.png
Type: image/png
Size: 1384 bytes
Desc: image019.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image020.png
Type: image/png
Size: 1369 bytes
Desc: image020.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image021.png
Type: image/png
Size: 1981 bytes
Desc: image021.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image022.png
Type: image/png
Size: 1549 bytes
Desc: image022.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image023.png
Type: image/png
Size: 2892 bytes
Desc: image023.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 1589 bytes
Desc: image024.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image025.png
Type: image/png
Size: 1385 bytes
Desc: image025.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image026.png
Type: image/png
Size: 1370 bytes
Desc: image026.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image027.png
Type: image/png
Size: 1982 bytes
Desc: image027.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028.png
Type: image/png
Size: 1550 bytes
Desc: image028.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/43a62ad7/attachment-0022.png>

From stephane.lebihan at amundi.com  Thu Mar 15 04:12:11 2018
From: stephane.lebihan at amundi.com (=?utf-8?B?TGUgQmloYW4gU3TDqXBoYW5lIChBTVVOREktSVRTKQ==?=)
Date: Thu, 15 Mar 2018 10:12:11 +0000
Subject: [caasp-beta] Use another interface after install
In-Reply-To: <DD3BF21C77802042A0BC4AED019A4A7B88075048@SMBX003.ad-its.credit-agricole.fr>
References: <DAEB72C1-D1DB-4320-82E2-FEBD0DE4F06A@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B8804FE02@SMBX003.ad-its.credit-agricole.fr>
	<DD3BF21C77802042A0BC4AED019A4A7B88071DB8@SMBX003.ad-its.credit-agricole.fr>
	<E73470F1-23F2-4738-9073-BAF809B30C63@suse.com>
	<DD3BF21C77802042A0BC4AED019A4A7B88075048@SMBX003.ad-its.credit-agricole.fr>
Message-ID: <DD3BF21C77802042A0BC4AED019A4A7B8807564D@SMBX003.ad-its.credit-agricole.fr>

OK.

My Suse CAAS Plateform is up with bond etc?.

So step:

Install admin
Register admin
Update admin
Configure caasp in VElum
Prepare autoyast
Install master and worker
Register master and worker
Update master and worker
Deploy kubernetes with velum

So upate resolv problem of fix eth0 in salt.
But don?t miss to update all server before deploy.

Regards,


[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : jeudi 15 mars 2018 07:32
? : Rob de Canha-Knight
Cc : Julien Niedergang; caasp-beta at lists.suse.com
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob,

Thanks for forward mail.

I test another install last night. Same problem but I noticed another information.
Because I have update I complete ?Enable registry mirror? on velum install. And I noticed docker daemon don?t restart on master node, because daemon.json file is bad.

So I launch a new install ths morning. I let ?Enable registry mirror? disable and I send result.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : mercredi 14 mars 2018 21:32
? : Le Bihan St?phane (AMUNDI-ITS)
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane.

I?ve forwarded your mail onto our support and engineering teams for them to take a look as this is a bit beyond me.

I have a feeling it may be related to updating the cluster or network issues somewhere along the line.

The warning about the 10 second timeout is something you don?t need to worry about this is normal when not using ipv6 so please ignore that.

I?ll send an update as and when I?ve got one.

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Wednesday, 14 March 2018 at 17:45
To: Liam Mccafferty <liam.McCafferty at smartodds.co.uk<mailto:liam.McCafferty at smartodds.co.uk>>, Rob de Canha-Knight <rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>>
Cc: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>, Julien Niedergang <Julien.Niedergang at suse.com<mailto:Julien.Niedergang at suse.com>>
Subject: RE: [caasp-beta] Use another interface after install

Hi all,

We finish to deploy non-production plateform for test.

So I test to install with patching ok on future production server?. Yes it?s bad but I don?t have another plateform for test :D

So after many test.
I start install admin node. After install ok. I?m connect to it.
Configure proxy
Configure /etc/SUSEConnect and register on SCC.
Refresh repository.
Use : transactional-update up and reboot.

After I configure Admin Node by Velum and launch deployement.
But it?s not ok. But may be it?s not same problem.

I have this in /var/log/salt/minion on master :

2018-03-14 17:16:44,779 [salt.state       ][ERROR   ][3511] An exception occurred in this state: Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/salt/state.py", line 1746, in call
    **cdata['kwargs'])
  File "/usr/lib/python2.7/site-packages/salt/loader.py", line 1704, in wrapper
    return f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/salt/states/http.py", line 148, in wait_for_successful_query
    raise caught_exception  # pylint: disable=E0702
error: [Errno 111] Connection refused

2018-03-14 17:18:29,522 [salt.loaded.int.grains.core][WARNING ][1763] Unable to find IPv6 record for "3d6fef2c01eb416390f1e6ee6df97449.infra.caasp.local" causing a 10 second timeout when rendering grains. Set the dns or /etc/hosts for IPv6 to clear this.

I joined supportconfig off all host.

Have you an idea of problem ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com> [mailto:caasp-beta-bounces at lists.suse.com] De la part de Le Bihan St?phane (AMUNDI-ITS)
Envoy? : mardi 6 mars 2018 07:55
? : Rob de Canha-Knight; Liam Mccafferty
Cc : Julien Niedergang; caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>
Objet : Re: [caasp-beta] Use another interface after install

Hi Rob and Liam,

That confirm my idea.

When I install admin node, I have no update. I think it?s my proxy configuration or other don?t work. So he use eth0 hardcoded in Salt because this version is on DVD.

For the moment I deploy cluster kubernetes on non-production on eth0 (1Gb card).  I warned user we have to destroy all and launch new install for change it.

For autoyast, I modify it with no problem. But I didn?t have idea to name bond eth0 :D
And we have many autoyast (for KVM, or Baremetal server)

For information, when you set network on netsetup (No DHCP here), and not in autoyast it?s work. OS has good configuration and install works correctly.
I change just partitioning in autoyast for workers baremetal and master KVM ,for use dedicated devices for docker registry local.
So my autoyast is more generic, for install.

My problem is just because update is not ok? I think.

I finish to create access for developer and admin kubernetes on non-production server for validate CAASP solution, after I want to test another install on future production server with good proxy configuration.

Another info, (I take this opportunity) we have decide to use a dedicated partition for registry local, so I modify autoyast for include option in /etc/sysconfig/docker at install. But it?s not work.
I think it?s can be a good idea to permit modify this at install.
And after not overwrite option on deployment but just add option you want to fix.
But maybe it?s ok on update version?. ?

At the end I have :
DOCKER_OPTS="-g /docker --storage-driver btrfs --iptables=false --log-level=warn"

Thanks for you feedback and you response.

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

De : Rob de Canha-Knight [mailto:rob.decanha-knight at suse.com]
Envoy? : lundi 5 mars 2018 23:09
? : Le Bihan St?phane (AMUNDI-ITS); Liam Mccafferty
Cc : caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>; Julien Niedergang
Objet : Re: [caasp-beta] Use another interface after install

Hi Stephane,

In general, changing the network interface setup after install is not possible and I believe it is unsupported at this time.

If you?ve got a mix of KVM and physical nodes the best thing to do is to download the autoyast generated by the admin node and modify it. You can then serve it up yourself from a normal SLES machine and Apache.
That way you can have an autoyast suitable for KVM based VMs and a different autoyast file suitable for the physical hosts with network bonding.
I strongly recommend setting up the bond inside of the autoyast file directly. I don?t however have any examples of how to do this.
You can then reinstall the worker nodes or the cluster and they?ll get more appropriate installation settings to deal with network bonding.

We also recently released some updates to CaaS Platform to remove the hardcoded eth0 references and instead use the default network interface inside all of the salt states/components. In your case this will be bond0 (but only if setup correctly or like that during install).
So please make sure that your existing cluster is up to date both admin and worker nodes but also more importantly make sure you?re enabling updates during install for when you reinstall the cluster (this can be set in the autoyast file and is enabled by default in the autoyast I think as long as a registration code was provided to the admin node during installation.
You?ll need all the <do_registration> and <reg_code> and <install_updates> filled in correctly and enabled.
Further information on updates to a cluster the process and how to recover from errors can be found at https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update

We have a couple of customers that have achieved bonding network cards with CaaSP. I am adding in Liam to this thread as he was successful in achieving this and he may be able to share some examples or some insights into network bonding. Anything you?re able to share or input to the discussion is much appreciated Liam :)

If I?ve said anything that?s incorrect then someone from Engineering will be able to comment (it?s been a while since I?ve looked into the issue of network bonding).

Kind regards,
Rob

-----
Rob de Canha-Knight
EMEA Platform and Management Technical Strategist
SUSE
rob.decanha-knight at suse.com<mailto:rob.decanha-knight at suse.com>
(P)  +44 (0) 1635 937689
(M) +44 (0) 7869 113493
(TW) rssfed23<https://twitter.com/rssfed23>
I work on GMT time zone
----
From: <caasp-beta-bounces at lists.suse.com<mailto:caasp-beta-bounces at lists.suse.com>> on behalf of "Le Bihan St?phane (AMUNDI-ITS)" <stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>>
Date: Monday, 26 February 2018 at 10:53
To: "caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>" <caasp-beta at lists.suse.com<mailto:caasp-beta at lists.suse.com>>
Subject: [caasp-beta] Use another interface after install

Hello,

My admin is installed in KVM, so he use eth0 for kubernetes.
I want to add a physical node (baremetal) to kubernetes cluster. But on it, I want to use a bond with two card 10Go.

But when I join host baremetal to cluster, deployement want to use eth0.

How I can fix interface change just for this host ? I think it?s on Saltstack deployement, but I don?t want who I can change it ?

Any idea ?

Regards,

[cid:89B49E07-4580-47BA-A59D-B0A59F32E6C5]

St?phane Le Bihan
SDE/DSI/IPR/SSD/UNX
90, Boulevard Pasteur - 75015 Paris
Web: www.amundi.com<http://www.amundi.com>
Tel: +33 1 76 32 32 08
Tel Unix Team: +33 1 76 32 02 30
@: stephane.lebihan at amundi.com<mailto:stephane.lebihan at amundi.com>
@: sits.unix at amundi.com<mailto:sits.unix at amundi.com>

Visit us on:

[twitter]<https://twitter.com/Amundi_ENG>  [linkedin] <https://www.linkedin.com/company/amundi->   [facebook] <https://www.facebook.com/AmundiOfficial/>   [Sans titre-1] <https://www.instagram.com/myamundi/>   [youtube] <https://www.youtube.com/user/AmundiGroup>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2890 bytes
Desc: image006.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 1587 bytes
Desc: image007.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 1383 bytes
Desc: image008.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 1368 bytes
Desc: image009.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 1980 bytes
Desc: image010.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image011.png
Type: image/png
Size: 1548 bytes
Desc: image011.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 1587 bytes
Desc: image012.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image013.png
Type: image/png
Size: 1383 bytes
Desc: image013.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image014.png
Type: image/png
Size: 1368 bytes
Desc: image014.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image015.png
Type: image/png
Size: 1980 bytes
Desc: image015.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 1548 bytes
Desc: image016.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.png
Type: image/png
Size: 2891 bytes
Desc: image017.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0011.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image018.png
Type: image/png
Size: 1588 bytes
Desc: image018.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0012.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image019.png
Type: image/png
Size: 1384 bytes
Desc: image019.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0013.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image020.png
Type: image/png
Size: 1369 bytes
Desc: image020.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0014.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image021.png
Type: image/png
Size: 1981 bytes
Desc: image021.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image022.png
Type: image/png
Size: 1549 bytes
Desc: image022.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image023.png
Type: image/png
Size: 2892 bytes
Desc: image023.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 1589 bytes
Desc: image024.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image025.png
Type: image/png
Size: 1385 bytes
Desc: image025.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0019.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image026.png
Type: image/png
Size: 1370 bytes
Desc: image026.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image027.png
Type: image/png
Size: 1982 bytes
Desc: image027.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image028.png
Type: image/png
Size: 1550 bytes
Desc: image028.png
URL: <http://lists.suse.com/pipermail/caasp-beta/attachments/20180315/e5ebd9dc/attachment-0022.png>