Hi, yes, I have create a PS for airship-in-a-bottle to align the schemas

https://review.openstack.org/#/c/632610/

/Kaspars

From: Georg Kunz [mailto:georg.kunz@ericsson.com]
Sent: Tuesday, January 22, 2019 11:10 AM
To: SKELS, KASPARS <ks3019@att.com>
Cc: airship-discuss@lists.airshipit.org
Subject: RE: How to enable hugepages

Hi Kaspars,

Thank you for the pointers. In the meantime I also noticed that the HardwareProfile schema in AIAB [1] does not contain the hugepages attributes (yet) in contrast to the
schema in treasuremap [2]. This likely answers my questions i) and ii) from below.

I’ll take a look at the files you mentioned and extend the HardwareProfile schema in AIAB for testing purposes.

[1] https://github.com/openstack/airship-in-a-bottle/blob/master/deployment_files/global/v1.0demo/schemas/drydock/HardwareProfile/v1.yaml

[2] https://github.com/openstack/airship-treasuremap/blob/master/global/schemas/drydock/HardwareProfile/v1.yaml

Best regards

Georg

From: SKELS, KASPARS <ks3019@att.com>
Sent: Tuesday, January 22, 2019 5:59 PM
To: Georg Kunz <georg.kunz@ericsson.com>
Cc: airship-discuss@lists.airshipit.org
Subject: RE: How to enable hugepages

Hi Georg,

our main deployment reference treasuremap (https://github.com/openstack/airship-treasuremap) doesn’t have right now good samples for huge pages but you can find a few in the test section of Drydock..

- For hardware profile

https://github.com/openstack/airship-drydock/blob/master/python/tests/yaml_samples/deckhand_fullsite.yaml#L427

- And there are also kernel related parameters available to set

https://github.com/openstack/airship-drydock/blob/master/python/tests/yaml_samples/deckhand_fullsite.yaml#L366

Kindly, Kaspars

From: Georg Kunz [mailto:georg.kunz@ericsson.com]
Sent: Tuesday, January 22, 2019 8:04 AM
To: airship-discuss@lists.airshipit.org
Subject: [Airship-discuss] How to enable hugepages

Hi Airship community,

I have been trying to use hugepages in my Airship deployment, but failed to get it to work in my particular development environment. Some advice would be greatly appreciated.

My development environment is a multi-node Airship-in-a-bottle gate [1] to which Matt pointed me some time ago. This environment defines a “GenericVM” hardware profile [2]. According to the Drydock documentation, I can enable hugepages in a hardware profile by adding a “hugepages” attribute [3][4]. However, when doing this in the multi-gate environment as shown here [5], the deployment (using .”/gate.sh multimode_deploy”) fails with an error stating “Additional properties are not allowed ('hugepages' was unexpected)” [6]

When checking the HardwareProfile defined in /tmp/<something>/site_yaml/deployment_files.yaml, it is missing the hugepages attribute. This could explain why Shipyard is complaining.

My questions:

i) Why is Shipyard complaining about the additional “hugepages” attribute? The HardwareProfile schema in treasuremap does list the “hugepages” attribute.

ii) Why is hugepages missing from the overall deployment_files.yaml?

iii) How do I enable hugepages the right way?

[1] https://github.com/openstack/airship-in-a-bottle/tree/master/tools/multi_nodes_gate

[2] https://github.com/openstack/airship-in-a-bottle/blob/master/deployment_files/site/gate-multinode/profile/hardware/generic_vm.yaml

[3] https://airshipit.readthedocs.io/projects/drydock/en/latest/topology.html#hardware-profile

[4] https://github.com/openstack/airship-treasuremap/blob/master/global/schemas/drydock/HardwareProfile/v1.yaml

[5] https://hastebin.com/paboxagori.cs

[6] https://hastebin.com/uzepikenol.py

Thanks a lot!

Best regards

Georg