[Airship-discuss] IPAM for Airship

[PACHECO, RODOLFO J]

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

I think that is what you are thinking about.

Regards

Rodolfo Pacheco

Home/Office 732 5337671

From: Dmitry Ukov <dukov at mirantis.com>
Date: Friday, September 20, 2019 at 11:37 AM
To: "airship-discuss at lists.airshipit.org" <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.

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