[Airship-discuss] IPAM for Airship

Fri Sep 20 16:14:31 UTC 2019

I think we may intertwining two separate needs.

The first and most urgent need is to understand how we will declare the static IP assignments for each baremetal host up front, much like we do within Airship 1.0.  I disagree that MaaS behaves as an IPAM service – for the most part all it does is enforce the static assignments we declare within Drydock BaremetalNode documents as in here:
https://github.com/airshipit/treasuremap/blob/master/site/seaworthy/baremetal/nodes.yaml#L48-L86

I missed the latest bootstrap-sig call, however when we were initially discussing this one very simple way to get started with this is to represent the network configuration as cloud-init data in the BareMetalHost  (BMH) CRD.  There is support for that now without introducing any additional CRDs or fields.

The second need you are addressing, where files/CRs like “common-addresses” become more important and have definitions for all the various subnets--abstracted from specific machines, is supporting a more liberal IP assignment mechanism in Airship 2.0, where users need only define subnets, and we can support allocating addresses automatically.  This is where IPAM truly becomes a requirement but I think it is premature to look at this and feel this may be a subsequent step to delivering static functionality.

Alan Meadows

From: PACHECO, RODOLFO J
Sent: Friday, September 20, 2019 9:07 AM
To: Dmitry Ukov <dukov at mirantis.com>
Cc: airship-discuss at lists.airshipit.org
Subject: Re: [Airship-discuss] IPAM for Airship
Agree, we expect the document that defines this information to be generic.
Meaning it will be used by both ephemeral and target clusters.

Regards

Rodolfo Pacheco

Home/Office 732 5337671

From: Dmitry Ukov <dukov at mirantis.com<mailto:dukov at mirantis.com>>
Date: Friday, September 20, 2019 at 11:49 AM
To: "PACHECO, RODOLFO J" <rp2723 at att.com<mailto:rp2723 at att.com>>
Cc: "airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>" <airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>>
Subject: Re: [Airship-discuss] IPAM for Airship

Rodolfo,

Thanks for the links. This is what is needed for ephemeral node!
What is about target cluster nodes? We need to manage their network configuration some how (assign IPs, set up bonding etc). MAAS is used as IPAM service in Airship 1.0 but it will be replaced in favor of Metal3. So we may want to have the same mechanism of ip allocation for ephemeral cluster and for target cluster.

On Fri, Sep 20, 2019 at 7:47 PM PACHECO, RODOLFO J <rp2723 at att.com<mailto:rp2723 at att.com>> wrote:
Forgot to add, Jerome’s POC has an example that looks closer to a CR expectations https://github.com/keleustes/treasuremap/blob/kustomize/site/seaworthy/networks/common-addresses.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_keleustes_treasuremap_blob_kustomize_site_seaworthy_networks_common-2Daddresses.yaml&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Bjzj_RciGLj21LnNXoD5dw&m=eSPJlb86ECKHCgBeXNfbCrcBGq7doKl90sZz1JU-HJM&s=5hGWlv6RN10N-cPbl_8lnzrGFZRmONETR55X1GdKN7g&e=>

Regards

Rodolfo Pacheco

Home/Office 732 5337671

From: "PACHECO, RODOLFO J" <rp2723 at att.com<mailto:rp2723 at att.com>>
Date: Friday, September 20, 2019 at 11:40 AM
To: Dmitry Ukov <dukov at mirantis.com<mailto:dukov at mirantis.com>>, "airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>" <airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>>
Subject: Re: [Airship-discuss] IPAM for Airship

Dmitry

In Airship 1.0 we had such a document . I expect for 2.0 we need an equivalent CR for this type of information
Is what we have been calling Catalog or DB like Document’s

Here is an example from treasuremap

https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy/networks/common-addresses.yaml<https://urldefense.proofpoint.com/v2/url?u=https-3A__opendev.org_airship_treasuremap_src_branch_master_site_seaworthy_networks_common-2Daddresses.yaml&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Bjzj_RciGLj21LnNXoD5dw&m=eSPJlb86ECKHCgBeXNfbCrcBGq7doKl90sZz1JU-HJM&s=wvOJ_Dykh2xTn3clmits97RK3Pk5sSKbS6JAdw8eE1s&e=>

I think that is what you are thinking about.

Regards

Rodolfo Pacheco

Home/Office 732 5337671

From: Dmitry Ukov <dukov at mirantis.com<mailto:dukov at mirantis.com>>
Date: Friday, September 20, 2019 at 11:37 AM
To: "airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>" <airship-discuss at lists.airshipit.org<mailto:airship-discuss at lists.airshipit.org>>
Subject: [Airship-discuss] IPAM for Airship

Hello,
I'm working on cloud-init generator as a part of airshipctl bootstrap isogen command.
This cloud init will be used to deploy K8s on ephemeral node.
Following information is needed to set up ephemeral node:

  *   IP address
  *   Net mask
  *   Default Gateway
  *   DNS server address
There is no CRD/CR that actually has this information. For example BareMetalHost resource has IP and Netmask as a part of Status field (and determined dynamically by beremetal operator) and there is no info about Default GW and DNS.

This actually leads us to the situation where we need to have IPAM (ip address management) operator and appropriate CRs/CRDs.

Unfortunately there is not much IPAM services that can act as K8s operator (I've found only one actually https://github.com/inwinstack/ipam<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_inwinstack_ipam&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=Bjzj_RciGLj21LnNXoD5dw&m=c8c5DfwYKVyHfFy7VcpEn5JOI4G1u4qxCaCy9cDsgAI&s=d7costGUiy-0u1vBkTFbV8Gf4-BIyHE3PGYKZ49NK7k&e=> and it has limitations I guess).

As an alternative we have to implement IPAM as a part of Airship 2.0.

What do you think?

--
Kind regards
Dmitry Ukov
Principal Deployment Engineer
Mirantis, Inc.

--
Kind regards
Dmitry Ukov
Principal Deployment Engineer
Mirantis, Inc.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.airshipit.org/pipermail/airship-discuss/attachments/20190920/d7b52a1d/attachment-0001.html>