Hi Matt, Thanks a lot for the reply. I got some idea about updating process. However I would like to ask you about the files that needs to be updated if I wanted to update the versions of Kubernetes and its components, UCP components, OSH Components. Thanking you in advance. Best Regards, Santosh -----Original Message----- From: MCEUEN, MATT <MM9745@att.com> Sent: Saturday, January 05, 2019 3:45 AM To: santosh.thapamager <santosh.thapamager@as.ntt-at.co.jp>; airship-discuss@lists.airshipit.org Subject: RE: [Airship-discuss] Airship-in-a-bottle_Dev_Minimal_Bedhind Proxy：How to Update Site? Sorry for the delay, Santosh -- I'm catching up post-holiday. To supply updated documents to Shipyard, 1) First, update the documents in your git repository (e.g. something like https://github.com/openstack/airship-treasuremap/tree/master/site/airship-se...). Your repo serves as the declarative definition of what your site looks like, both for an initial deployment, and later, for an update. 2) The steps to update a site via Shipyard are very similar to the initial deployment, but with fewer steps! Lint and collect your updated documents, per: https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deploymen... Update the site using Shipyard*: https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deploymen... * Note: should use the Shipyard`update_site.sh` script instead of `deploy_site.sh` in the above step. I think we should add another section to the end of that site authoring guide to describe the update process -- today the guide is geared toward new deployments. Let me know if you have any other questions! Thanks, Matt -----Original Message----- From: santosh.thapamager <santosh.thapamager@as.ntt-at.co.jp> Sent: Thursday, December 20, 2018 5:59 PM To: MCEUEN, MATT <MM9745@att.com>; airship-discuss@lists.airshipit.org Subject: RE: [Airship-discuss] Airship-in-a-bottle_Dev_Minimal_Bedhind Proxy：How to Update Site? Hi Matt, Thanks for the instruction. I have been following airship-treasuremap document. As you mentioned that we need to update the deployment manifest and supply to Shipyard and call Shipyard update_site API. *************** 1) supplying updated deployment manifests to Shipyard, including the change 2) calling Shipyard's update_site API *************** However I could not find instruction for 1) as you mentioned. I would be greatly thankful to you if I can get some instruction for updating the deployment manifests and how to supply updated manifests to Shipyard. Best Regards, Santosh Thapa Magar -----Original Message----- From: MCEUEN, MATT <MM9745@att.com> Sent: Thursday, December 20, 2018 4:37 AM To: santosh.thapamager <santosh.thapamager@as.ntt-at.co.jp>; airship-discuss@lists.airshipit.org Subject: RE: [Airship-discuss] Airship-in-a-bottle_Dev_Minimal_Bedhind Proxy：How to Update Site? Hi Santosh - in general, the right way to update an airship site is by: 1) supplying updated deployment manifests to Shipyard, including the change 2) calling Shipyard's update_site API We don't have that as part of Aiship-in-a-Bottle, because AiaB is not intended to be used for "real life" sites -- it's a demo environment. I suggest taking a look at the Treasuremap documentation [1] and example manifests [2] as a way to stand up a fully lifecycled-site. Update_site (along with the rest of the Shipyard interface) is documented here [3] for the CLI and here [4] for the API. 1: https://urldefense.proofpoint.com/v2/url?u=https-3A__airship-2Dtreasuremap.readthedocs.io_en_latest_authoring-5Fand-5Fdeployment.html&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=GzUJawD1-C5_L5DGSKHFUYIHRm6qQLIa31I93xmqs5Q&s=OUmBq4L34nRJCxeMURicQJuQTXp7dTZGkrSZO8DTw6s&e= 2: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_openstack_airship-2Dtreasuremap&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=GzUJawD1-C5_L5DGSKHFUYIHRm6qQLIa31I93xmqs5Q&s=m5RHAnvcPXkc2rESb2Awl7FBDiEojHQWs5h-9UKiwow&e= 3: https://urldefense.proofpoint.com/v2/url?u=https-3A__airship-2Dshipyard.readthedocs.io_en_latest_CLI.html&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=GzUJawD1-C5_L5DGSKHFUYIHRm6qQLIa31I93xmqs5Q&s=qLoy0_3Np0PQyXcpSXmkxC5z8_Gsbt43Q1vbE0_si5M&e= 4: https://urldefense.proofpoint.com/v2/url?u=https-3A__airship-2Dshipyard.readthedocs.io_en_latest_API.html&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=GzUJawD1-C5_L5DGSKHFUYIHRm6qQLIa31I93xmqs5Q&s=2ckZS-p-G_eVrOfGGk9-CBvQiq6FgW8GYabJBi1yidA&e= The latest version of Promenade provisions a Kubernetes cluster that patches for the CVE you mention. Hope that helps - let me know if you have any other questions! Matt -----Original Message----- From: santosh.thapamager <santosh.thapamager@as.ntt-at.co.jp> Sent: Wednesday, December 12, 2018 10:03 PM To: airship-discuss@lists.airshipit.org Subject: [Airship-discuss] Airship-in-a-bottle_Dev_Minimal_Bedhind Proxy：How to Update Site? Hi all, I was able to install dev_minimal and deploy site behind proxy. Because of Kubernetes apiserver vulnerability (CVE-2018-1002105)I wanted to update Kubernetes version in my currently deployed site. However I could not find any documentations regarding updating deployed site. I would be thankful to all of you, if I could get any support. Best Regards, Santosh Thapa Magar _______________________________________________ Airship-discuss mailing list Airship-discuss@lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=Kp_9DVZcWk0qumyITPRn31pyOnpfXyno0HbJJJul7Xw&s=j6f8UNYzAnQn2PEYvDhC0N3F4i2vFF8qXyVC7Arx3hQ&e=