Skip to content

Instantly share code, notes, and snippets.

Knut Alejandro Anderssen González teclator

Block or report user

Report or block teclator

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

My first Openstack Summit Event

I had the oportunity to attend to the OpenStack Summit in Barcelona (October 24-27), in particular I attended to the COA trainning by SuSE (Ron Terry & Ross Brunson) which gave me the oportunity to learn more in detail how it works and what is the main role of each component, in general, to be in touch with OpenStack.

whatsapp image 2016-10-27 at 17 06 27

It was also a good oportunity to share time with the Network Team, so I accepted the invitation of the Team Manager (Rosella Sblendido) to


The Problem

Currently in Yast Network Configuration, in case that we have some Netcard with NPAR or SR-IOV capabilities there is no way to know if we are creating a Bonding with two devices with the same physical port. It not makes sense or at least could not produce the expecpted results and the normal case is to combine two devices from different Ethernet ports.

Bonding, Teaming or Link Agregation is a way to combine multiple network connections to increase the throughput, bandwith and to provide redundancy.


NPAR (NIC Partitioning) provides the capability to create multiple native Ethernet interfaces that share a single physical port.


Description (trello PBI)

From the POV of a user, during installation, if the installer restart after a self-update it should continue from the same step as before the self-update/restart was applied. To get it, two requirements should be met:

  1. All the steps before the one wich do the restart should be skipped remembering them state [1]
  2. In case the user decides to go back from the current step, the dialogs should maintain the same state as if a self update wouldn't been applied.

Taking this in account, we encountered that the two requirements weren't met.

teclator /
Last active May 20, 2016
Installation Workflow (Networking) discussion


The goal of this document is to discuss or show how affect the network configuration to the installation workflow, and in particular how installation self-update is affected and how it could be improved.

Network Availability: Having at least one interface configured with an IP address.

Self update scenarios

In the last Sprint we added self-update to yast-installation, so now if network is available we will check for updates and in case there are some update for our system, it will automatically downloaded and installed.

You can’t perform that action at this time.