[Airship-discuss] [airship-discuss] Error when changing simple parameters for AIAB?
ks3019 at att.com
Fri Oct 4 16:07:01 UTC 2019
I think you may need to look into the AIAB scripts to see more if changing the region name may impact the changes in actual deployment scripts/assumptions of AIAB. It is definitely the right idea but then on the other hand AIAB are sort of demo/development case with various assumptions/simplifications to make it possible to do a single touch deployment in a single VM - without any user input.
I would suggest to poke around and initially try some config changes that may have lesser impact on the system as a whole. The particular variable, region_name is definitely possible to change, for example see Seaworthy deployment https://github.com/airshipit/treasuremap/blob/master/site/seaworthy/software/config/common-software-config.yaml#L15 .
I think simple visible things could be updating pod replicas or logging levels of OpenStack components to start with.
For example Heat
You may add replica part to the site manifests (borrowed from type)
For all the available variables you can change for Heat or any component will be in values.yaml in openstack-helm project, including OpenStack image that can be changed and overridden for chart deployment (in case you have a custom build)
There is also another way to update site deployments with config changes, without full re-deploy, that is when site is running (day 2 operations)
From: Nick Chase [nchase at mirantis.com]
Sent: Thursday, October 03, 2019 10:35 PM
To: airship-discuss at lists.airshipit.org
Subject: [Airship-discuss] [airship-discuss] Error when changing simple parameters for AIAB?
So i was able to deploy Airship in a Bottle, albeit on a much larger machine (but that's a separate issue). I wanted to demonstrate how the manifests control things, so I started up a fresh VM and edited /root/deploy/treasuremap/site/aiab/software/config/common-software-config.yaml to change the region name:
I then went ahead and ran the script as usual, but it was unable to deploy/find Horizon. To make sure that the change was the issue, I then went and created a THIRD fresh VM and ran it without the change, and it deployed successfully.
Is this expected?
mkdir -p /root/deploy && cd "$_"
git clone https://opendev.org/airship/treasuremap/<https://urldefense.proofpoint.com/v2/url?u=http-3A__opendev.org_airship_treasuremap_&d=DwMFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=L2WcX1Ge33cpIHXX6krAgw&m=i7XiFhmUk7_iab0NprdyhgeYbBuzyviytv6_co_GVYs&s=wE686gobeMCRbv5J_45OiKOp9F1UR9O0UiPofZlHnZY&e=>
If someone can recommend a value that I could successfully change as a demonstration, I would really appreciate it.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Airship-discuss