Hi all,

 YAM SIG brought to notice old Airship 1.0 terminology for defining BareMetal Requirements & NodeDef

This is to describe Site / Type / Composite / Function Naming convention in Treasuremap v2.

https://etherpad.openstack.org/p/Airship_Yaml (refer Oct 12 Discussions)

Here is the new Jira Story added by Rodolfo Pacheco.

https://airship.atlassian.net/browse/AIR-185

 

I will assume following and have started the documentation in google docs added to YAML SIG etherpad as well

1.      Strawman Proposal for Identifying Site Type and associated MVP BareMetal Descriptor.

2.      Create a Draft Proposal for What a Site should look like for Airship v2?

3.      Outline your thoughts/ideas on your initial judgement/ideas to improve Airship v2 based on three configurations available in Airship 1.0:

4.      Get feedback from YAML SIG

5.      Update Draft till Final and Summarize the Conclusion.

 

• airshipctl cluster  https://docs.google.com/document/d/15zRU5c5cCJLdFzE1P9UArdu19u-nRVrYk8p_JKTmhK0/edit?usp=sharing

 

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Airship MVP Beta (V2) - YAML SIG Google Doc sharing for

Treasuremap Strawman Proposal

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

·        Refer to above link,  Matt & Jared, if you can add your tables T1 (Seaworthy) & T2 (Airsloop)

 

·         Let me know your suggestions of  Airship 2.0 terminology and the Topology to clarify hierarchy (Region, Zone(AZ), Cluster, Site, Node) data elements, labels, annotations, and terms we will use different from Airship 1.0 and interpretations we appear to have now. Of-course code is king, and k8s is default, still we need to rationalize this for v2(Beta) branch now for design and deployment of BareMetal Node and Cluster using Metal-3/Cluster APIs, OSH Operator, Ironic plus all Plugins we plan to use modules like Kustomize etc.

Thanks

Prakash