[Airship-discuss] Divestiture

MCEUEN, MATT MM9745 at att.com
Mon Aug 12 16:13:35 UTC 2019

Hi Aaron,

Yes, you’re most welcome to join open design discussions!  We also have a new airship-bootstrap SIG[1] that has an overlapping focus with bare metal provisioning.

For Airship 2.0, we’re moving away from using Drydock as the declarative API for driving host provisioning, and moving to the Kubernetes Cluster API, which is getting wide participation in the community.  In particular, we’re planning to leverage / contribute to the Metal3 project, which aims to provide a bare metal implementation of the Cluster API.  The Metal3->Ironic interface doesn’t use Bifrost today, but that’s certainly something that we could talk through in the design call – feel free to add it to the agenda.

For the current Airship 1.x implementation configured in Treasuremap:  If you’d like to explore a sort of “bring your own bare metal” approach, where Bifrost performs bare metal provisioning instead of Airship, you can take a look at Airskiff[2] configuration.  However, Airskiff also assumes a “bring your own Kubernetes”, so you’d need to provision e.g. a KubeADM or Kubespray cluster on your nodes prior to deploying software (OpenStack etc) via Airship in this configuration.  Let me know if you have any questions on this.


[1]: https://wiki.openstack.org/wiki/Airship#AIRSHIP_SIG_-_Special_Interest_Meetings
[2]: https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html

From: Aaron Blair <airshipcloud at gmail.com>
Sent: Saturday, August 10, 2019 12:24 AM
To: kbaegis at gmail.com; MCEUEN, MATT <MM9745 at att.com>
Cc: airship-discuss at lists.airshipit.org
Subject: Re: Divestiture

I'm trying to follow the latest progress/discussion of Airship 2.0 and the drydock ironic integration; is it best to join the open design discussions (https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions<https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_Airship-5FOpenDesignDiscussions&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=wb_dJdy8HPNbBYvvkEItu9wbdqF3dGzl3YQuU016bXA&s=SafuSx-pl8wTPQEMxYDWQ-PNtYdrUJ38BjuxmVR-SNs&e=>) or another method?

Based on some of the comments from the drydock and standalone ironic integration (https://review.opendev.org/#/c/613358/4/specs/approved/drydock_ironic_integration.rst<https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_613358_4_specs_approved_drydock-5Fironic-5Fintegration.rst&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=wb_dJdy8HPNbBYvvkEItu9wbdqF3dGzl3YQuU016bXA&s=itoM7lFq_ZvaW6jNiZQIiNmCpTMQsWkHNj-9XQeThN8&e=>), it seems at least some folks are partially aware of Bifrost; when using Kolla-Ansible for Bifrost (https://docs.openstack.org/kolla-ansible/latest/reference/deployment-and-bootstrapping/bifrost.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.openstack.org_kolla-2Dansible_latest_reference_deployment-2Dand-2Dbootstrapping_bifrost.html&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=wb_dJdy8HPNbBYvvkEItu9wbdqF3dGzl3YQuU016bXA&s=DfPPdakPZNmRQSqb9kUo2eGZZO1mheEcVne4Tsp178k&e=>), you have options for an automated deployment of a single docker container with:
- standalone ironic (conductor and inspector)
- keystone
- dnsmasq for dhcp/tftp which supports pxe/ipxe deployments and uefi/bios boot modes
- Nginx which masquerades as an unauthenticated 'Swift' object storage service for Inspector and hosts images for ipxe over http

I currently have containerized Biforst deployed in this manner with an inventory of 8 baremetal nodes with which I would like to deploy treasuremap/seaworthy.

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

More information about the Airship-discuss mailing list