From hemant.sonawane at itera.io Thu Aug 1 09:26:31 2019 From: hemant.sonawane at itera.io (Hemant Sonawane) Date: Thu, 1 Aug 2019 11:26:31 +0200 Subject: [Airship-discuss] Failed to connect to remote host: FD Shutdown In-Reply-To: <5B9C5644A0B2414E90A7F40249CF6A955EEB973C@MOSTLS1MSGUSRFA.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A05AB2@MOSTLS1MSGUSRFF.ITServices.sbc.com> <5B9C5644A0B2414E90A7F40249CF6A955EEB973C@MOSTLS1MSGUSRFA.ITServices.sbc.com> Message-ID: Hello guys, Thank you so much for you emails. Hey Sean I tried your fix at first I exposed tiller svc as a NodePort and mounted the /etc/armada/armada.conf inside the container but still i am having some issue related to host port. Please find attached log file and armada.conf for your ready reference. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 377 bytes Desc: not available URL: -------------- next part -------------- 2019-08-01 09:13:27.694 140 ERROR armada.cli [-] Caught unexpected exception: TypeError: argument of type 'NoneType' is not iterable 2019-08-01 09:13:27.694 140 ERROR armada.cli Traceback (most recent call last): 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/handlers/k8s.py", line 44, in __init__ 2019-08-01 09:13:27.694 140 ERROR armada.cli config.load_incluster_config() 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/incluster_config.py", line 96, in load_incluster_config 2019-08-01 09:13:27.694 140 ERROR armada.cli cert_filename=SERVICE_CERT_FILENAME).load_and_set() 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/incluster_config.py", line 47, in load_and_set 2019-08-01 09:13:27.694 140 ERROR armada.cli self._load_config() 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/incluster_config.py", line 53, in _load_config 2019-08-01 09:13:27.694 140 ERROR armada.cli raise ConfigException("Service host/port is not set.") 2019-08-01 09:13:27.694 140 ERROR armada.cli kubernetes.config.config_exception.ConfigException: Service host/port is not set. 2019-08-01 09:13:27.694 140 ERROR armada.cli 2019-08-01 09:13:27.694 140 ERROR armada.cli During handling of the above exception, another exception occurred: 2019-08-01 09:13:27.694 140 ERROR armada.cli 2019-08-01 09:13:27.694 140 ERROR armada.cli Traceback (most recent call last): 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/cli/__init__.py", line 39, in safe_invoke 2019-08-01 09:13:27.694 140 ERROR armada.cli self.invoke() 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/cli/apply.py", line 207, in invoke 2019-08-01 09:13:27.694 140 ERROR armada.cli dry_run=self.dry_run) as tiller: 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/handlers/tiller.py", line 94, in __init__ 2019-08-01 09:13:27.694 140 ERROR armada.cli self.k8s = K8s(bearer_token=self.bearer_token) 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/handlers/k8s.py", line 46, in __init__ 2019-08-01 09:13:27.694 140 ERROR armada.cli config.load_kube_config() 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 645, in load_kube_config 2019-08-01 09:13:27.694 140 ERROR armada.cli persist_config=persist_config) 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 613, in _get_kube_config_loader_for_yaml_file 2019-08-01 09:13:27.694 140 ERROR armada.cli **kwargs) 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 153, in __init__ 2019-08-01 09:13:27.694 140 ERROR armada.cli self.set_active_context(active_context) 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 173, in set_active_context 2019-08-01 09:13:27.694 140 ERROR armada.cli context_name = self._config['current-context'] 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 495, in __getitem__ 2019-08-01 09:13:27.694 140 ERROR armada.cli v = self.safe_get(key) 2019-08-01 09:13:27.694 140 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/kubernetes/config/kube_config.py", line 491, in safe_get 2019-08-01 09:13:27.694 140 ERROR armada.cli key in self.value): 2019-08-01 09:13:27.694 140 ERROR armada.cli TypeError: argument of type 'NoneType' is not iterable 2019-08-01 09:13:27.694 140 ERROR armada.cli -------------- next part -------------- A non-text attachment was scrubbed... Name: armada.conf Type: application/octet-stream Size: 96 bytes Desc: not available URL: From hemant.sonawane at itera.io Thu Aug 1 12:28:58 2019 From: hemant.sonawane at itera.io (Hemant Sonawane) Date: Thu, 1 Aug 2019 14:28:58 +0200 Subject: [Airship-discuss] Failed to connect to remote host: FD Shutdown In-Reply-To: References: <7C64A75C21BB8D43BD75BB18635E4D8970A05AB2@MOSTLS1MSGUSRFF.ITServices.sbc.com> <5B9C5644A0B2414E90A7F40249CF6A955EEB973C@MOSTLS1MSGUSRFA.ITServices.sbc.com> Message-ID: Hello Guys, Thank you so much for your help finally it worked for me as I was missing KUBECONFIG parameter in the command line. Now it works perfectly fine. Thank you so much for you help. On Thu, 1 Aug 2019 at 11:26, Hemant Sonawane wrote: > Hello guys, > > Thank you so much for you emails. Hey Sean I tried your fix at first I > exposed tiller svc as a NodePort and mounted the /etc/armada/armada.conf > inside the container but still i am having some issue related to host port. > Please find attached log file and armada.conf for your ready reference. > > > -- Thanks and Regards, Hemant Sonawane -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Fri Aug 2 09:44:22 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Fri, 2 Aug 2019 11:44:22 +0200 Subject: [Airship-discuss] [sig][airship-bootstrap] Meeting time announcement In-Reply-To: <7B6F97D9A10BEC4A82949D15B7B34ECBD2B73174@deframbx01.intl.att.com> References: <7B6F97D9A10BEC4A82949D15B7B34ECBD2B73174@deframbx01.intl.att.com> Message-ID: When: Weekly from 2pm UTC to 3pm UTC (10 EST to 11 EST) on Wednesday from Wed Aug 7 to Tue Dec 31 Where: https://attcorp.webex.com/join/rg445d *~*~*~*~*~*~*~*~*~* This was the time with the most votes on the doodle meeting time poll. First sig-airship-bootstrap meeting will be next week. Etherpad: https://etherpad.openstack.org/p/Airship_bootstrap Notice that the subject line includes [sig][airship-bootstrap], please make sure you add this to any email to airship-discuss at lists.airshipit.org when the topic relates to the airship-bootstrap discussion. Best regards, -- Roman Gorshunov -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 4004 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 4088 bytes Desc: not available URL: From rv6848 at att.com Fri Aug 2 17:19:25 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Fri, 2 Aug 2019 17:19:25 +0000 Subject: [Airship-discuss] TC Meeting Scheduled Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA5587B067@MOSTLS1MSGUSREG.ITServices.sbc.com> Airship community. The Airship TC has determined the logistics for the monthly meeting. We will meet on the 1st Tuesday of every month at 9am CST, unless there is a conflict. The date/time and logistics for each meeting will be posted on the TC Wiki @ https://wiki.openstack.org/wiki/Airship/Airship-TC This is also where the meeting agenda/minutes will be posted. This is an open meeting, but Q&A from non-TC members will be limited to a defined time at the end of the meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848 at att.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Mon Aug 5 09:50:29 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Mon, 5 Aug 2019 11:50:29 +0200 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found Message-ID: Hello Airshipers, Back from holidays I try to launch a full rebuild of Airship in a bottle multinode and I get a strange error in the BGP_touter stage: the quagga image referenced doesn't exist anymore, and this is confirmed by browsing https://hub.docker.com/r/cumulusnetworks/quagga === Executing stage Create BGP router === Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally docker: Error response from daemon: pull access denied for cumulusnetworks/quagga, repository does not exist or may require 'docker login'. See 'docker run --help'. == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == Note that we use a tag from March (we added minor changes) and everything was running correctly upto the Overcloud. The Quagga 3.3.2 is still referenced in latest version on master. => any idea to fix this? BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From soujanya at atsgen.com Mon Aug 5 11:14:22 2019 From: soujanya at atsgen.com (Soujanya R M) Date: Mon, 05 Aug 2019 07:14:22 -0400 Subject: [Airship-discuss] =?utf-8?b?Pz09P3V0Zi04P3E/ID89PT91dGYtOD9xPyA/?= =?utf-8?q?=3D__Invalid_credentials_for_Openstack_dashboar?= In-Reply-To: <180bf-5d411b80-7b-53fb8680@166177242> Message-ID: <11b08-5d480f80-1d-53fb8680@235016935> Hi All, I have submitted a patch [0] addressing the password issue for Openstack dashboard. As we discussed, the password that is displayed after the deployment is not valid for accessing the dashboard. I have made changes that will make sure it picks the right password and displays correctly. Please try it out and review this change. Regards, Soujanya R M On Wednesday, July 31, 2019 00:39 EDT, "Soujanya R M" wrote:   Hi  Kaspars, Thanks for your response. I tried the default password as well but it still not working. Regards, Soujanya R M On Tuesday, July 30, 2019 10:30 EDT, "SKELS, KASPARS" wrote:   Soujanya, Have a look at secrets (keystone_admin) password.I think the default creds are password123, have a try! Kindly, Kaspars  ______________________________________________________________________________ From: Soujanya R M [soujanya at atsgen.com] Sent: Tuesday, July 30, 2019 3:35 AM To: airship-discuss at lists.airshipit.org Cc: Prabhjot Singh Sethi Subject: [Airship-discuss] Invalid credentials for Openstack dashboard   Hi All, I have deployed aiab using [0]. Deployment is successfully completed. I am unable to login to OpenStack dashboard due to Invalid credentials. Currently, I am using the same credentials that are displayed after the deployment. Credentials:   Domain: default   Username: admin   Password: password Can someone please help me with this? Thanks & Regards, Soujanya R M       -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Mon Aug 5 13:25:07 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Mon, 5 Aug 2019 15:25:07 +0200 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: References: Message-ID: minor typo & update: We use a commit from the beginning of July (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since 2017) seems to be obsolete and its docker image has been removed from the Docker Hub. Quagga doesn't seems to be used by the Airship-in-a-bottle version integrated in Treasumap/site. Is this Aiab version OK ? (latest on master of TreasureMap) BTW, I've just found that a new site has been added in the beginning of August: *seaworthy-virt *[1] => it seems to be what some other people and I were looking for (Cf. [2]) As someone tested it? [1] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt [2] http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html BR, Loïc Le lun. 5 août 2019 à 11:50, Loic Le Gal a écrit : > Hello Airshipers, > > Back from holidays I try to launch a full rebuild of Airship in a bottle > multinode and I get a strange error in the BGP_touter stage: the quagga > image referenced doesn't exist anymore, and this is confirmed by browsing > https://hub.docker.com/r/cumulusnetworks/quagga > > === Executing stage Create BGP router === > Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally > docker: Error response from daemon: pull access denied for > cumulusnetworks/quagga, repository does not exist or may require 'docker > login'. > See 'docker run --help'. > > == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == > > Note that we use a tag from March (we added minor changes) and everything > was running correctly upto the Overcloud. The Quagga 3.3.2 is still > referenced in latest version on master. > > => any idea to fix this? > > BR, > > Loïc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Mon Aug 5 14:17:37 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Mon, 5 Aug 2019 14:17:37 +0000 Subject: [Airship-discuss] =?utf-8?b?Pz0gID89PT91dGYtOD9xPyBJbnZhbGlkIGNy?= =?utf-8?q?edentials_for_Openstack_dashboar?= In-Reply-To: <11b08-5d480f80-1d-53fb8680@235016935> References: <180bf-5d411b80-7b-53fb8680@166177242> <11b08-5d480f80-1d-53fb8680@235016935> Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8087FB@MOKSCY3MSGUSRGI.ITServices.sbc.com> Good morning! Your patchset should be merged now. Thanks for the contribution!! Kindly, Kaspars From: Soujanya R M Sent: Monday, August 5, 2019 6:14 AM To: airship-discuss at lists.airshipit.org Cc: Prabhjot Singh Sethi Subject: Re: [Airship-discuss] ?==?utf-8?q? ?==?utf-8?q? ?= Invalid credentials for Openstack dashboar Hi All, I have submitted a patch [0] addressing the password issue for Openstack dashboard. As we discussed, the password that is displayed after the deployment is not valid for accessing the dashboard. I have made changes that will make sure it picks the right password and displays correctly. Please try it out and review this change. Regards, Soujanya R M On Wednesday, July 31, 2019 00:39 EDT, "Soujanya R M" > wrote: Hi Kaspars, Thanks for your response. I tried the default password as well but it still not working. Regards, Soujanya R M On Tuesday, July 30, 2019 10:30 EDT, "SKELS, KASPARS" > wrote: Soujanya, Have a look at secrets (keystone_admin) password. I think the default creds are password123, have a try! Kindly, Kaspars _____ From: Soujanya R M [soujanya at atsgen.com] Sent: Tuesday, July 30, 2019 3:35 AM To: airship-discuss at lists.airshipit.org Cc: Prabhjot Singh Sethi Subject: [Airship-discuss] Invalid credentials for Openstack dashboard Hi All, I have deployed aiab using [0]. Deployment is successfully completed. I am unable to login to OpenStack dashboard due to Invalid credentials. Currently, I am using the same credentials that are displayed after the deployment. Credentials: Domain: default Username: admin Password: password Can someone please help me with this? Thanks & Regards, Soujanya R M -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Mon Aug 5 14:19:31 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Mon, 5 Aug 2019 14:19:31 +0000 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: References: Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi, yes, we are slowly moving things from airship-in-a-bottle repo to treasuremap (to have common/single place for all the site reference manifests). From your pipelines/testing the AIAB in treasuremap is working very stable and we have started to recommend people to move to treasuremap. You may also use most recent tag v1.3 – but master should also be green right now. Kindly, Kaspars From: Loic Le Gal Sent: Monday, August 5, 2019 8:25 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found minor typo & update: We use a commit from the beginning of July (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since 2017) seems to be obsolete and its docker image has been removed from the Docker Hub. Quagga doesn't seems to be used by the Airship-in-a-bottle version integrated in Treasumap/site. Is this Aiab version OK ? (latest on master of TreasureMap) BTW, I've just found that a new site has been added in the beginning of August: seaworthy-virt [1] => it seems to be what some other people and I were looking for (Cf. [2]) As someone tested it? [1] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt [2] http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html BR, Loïc Le lun. 5 août 2019 à 11:50, Loic Le Gal > a écrit : Hello Airshipers, Back from holidays I try to launch a full rebuild of Airship in a bottle multinode and I get a strange error in the BGP_touter stage: the quagga image referenced doesn't exist anymore, and this is confirmed by browsing https://hub.docker.com/r/cumulusnetworks/quagga === Executing stage Create BGP router === Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally docker: Error response from daemon: pull access denied for cumulusnetworks/quagga, repository does not exist or may require 'docker login'. See 'docker run --help'. == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == Note that we use a tag from March (we added minor changes) and everything was running correctly upto the Overcloud. The Quagga 3.3.2 is still referenced in latest version on master. => any idea to fix this? BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Mon Aug 5 14:28:20 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Mon, 5 Aug 2019 16:28:20 +0200 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: Thanks a lot Kaspars for your quick answer, Here we go! Loïc Le lun. 5 août 2019 à 16:19, SKELS, KASPARS a écrit : > Hi, > > > > yes, we are slowly moving things from airship-in-a-bottle repo to > treasuremap (to have common/single place for all the site reference > manifests). > > From your pipelines/testing the AIAB in treasuremap is working very stable > and we have started to recommend people to move to treasuremap. > > > > You may also use most recent tag v1.3 – but master should also be green > right now. > > > > Kindly, Kaspars > > > > > > > > *From:* Loic Le Gal > *Sent:* Monday, August 5, 2019 8:25 AM > *To:* airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] [Aiab] Error building Gate multinode > site : Quagga 3.3.2 image not found > > > > minor typo & update: > > We use a commit from the beginning of July > (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. > > > > Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since > 2017) seems to be obsolete and its docker image has been removed from the > Docker Hub. > > Quagga doesn't seems to be used by the Airship-in-a-bottle version > integrated in Treasumap/site. > > Is this Aiab version OK ? (latest on master of TreasureMap) > > > > BTW, I've just found that a new site has been added in the beginning of > August: *seaworthy-virt *[1] > > => it seems to be what some other people and I were looking for (Cf. [2]) > > > > As someone tested it? > > > > [1] > https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt > > > [2] > http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html > > > > > http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html > > > > > BR, Loïc > > > > Le lun. 5 août 2019 à 11:50, Loic Le Gal a > écrit : > > Hello Airshipers, > > > > Back from holidays I try to launch a full rebuild of Airship in a bottle > multinode and I get a strange error in the BGP_touter stage: the quagga > image referenced doesn't exist anymore, and this is confirmed by browsing > https://hub.docker.com/r/cumulusnetworks/quagga > > > > > === Executing stage Create BGP router === > Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally > docker: Error response from daemon: pull access denied for > cumulusnetworks/quagga, repository does not exist or may require 'docker > login'. > See 'docker run --help'. > > == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == > > > > Note that we use a tag from March (we added minor changes) and everything > was running correctly upto the Overcloud. The Quagga 3.3.2 is still > referenced in latest version on master. > > > > => any idea to fix this? > > > > BR, > > > > Loïc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mb551n at att.com Mon Aug 5 14:30:20 2019 From: mb551n at att.com (BEAVER, MICHAEL A) Date: Mon, 5 Aug 2019 14:30:20 +0000 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: <09A8840B4970AE4F988B7B67087395CA0912EEE5@MOSTLS1MSGUSRFG.ITServices.sbc.com> Hi Loic, To add to what Kaspars has said: Thanks for the heads up! Yeah, we noticed the quagga image disappear late last week and have been investigating a suitable replacement for it. The aiab site under Treasuremap is designed to be a replacement for the traditional airship-in-a-bottle single node deployment, which is considerably different from the multimode environment you have been using, but is still very useful. You can read more about it here [0] As for the seaworthy-virt site, that is a new site we made in order to use the airship-in-a-bottle multinode environment with the Treasuremap manifests. The instructions to use this environment are here [1] however they are not quite done yet and are still under review. [0] https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab [1] https://review.opendev.org/#/c/655517/ From: SKELS, KASPARS Sent: Monday, August 5, 2019 9:20 AM To: Loic Le Gal ; airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi, yes, we are slowly moving things from airship-in-a-bottle repo to treasuremap (to have common/single place for all the site reference manifests). From your pipelines/testing the AIAB in treasuremap is working very stable and we have started to recommend people to move to treasuremap. You may also use most recent tag v1.3 – but master should also be green right now. Kindly, Kaspars From: Loic Le Gal > Sent: Monday, August 5, 2019 8:25 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found minor typo & update: We use a commit from the beginning of July (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since 2017) seems to be obsolete and its docker image has been removed from the Docker Hub. Quagga doesn't seems to be used by the Airship-in-a-bottle version integrated in Treasumap/site. Is this Aiab version OK ? (latest on master of TreasureMap) BTW, I've just found that a new site has been added in the beginning of August: seaworthy-virt [1] => it seems to be what some other people and I were looking for (Cf. [2]) As someone tested it? [1] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt [2] http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html BR, Loïc Le lun. 5 août 2019 à 11:50, Loic Le Gal > a écrit : Hello Airshipers, Back from holidays I try to launch a full rebuild of Airship in a bottle multinode and I get a strange error in the BGP_touter stage: the quagga image referenced doesn't exist anymore, and this is confirmed by browsing https://hub.docker.com/r/cumulusnetworks/quagga === Executing stage Create BGP router === Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally docker: Error response from daemon: pull access denied for cumulusnetworks/quagga, repository does not exist or may require 'docker login'. See 'docker run --help'. == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == Note that we use a tag from March (we added minor changes) and everything was running correctly upto the Overcloud. The Quagga 3.3.2 is still referenced in latest version on master. => any idea to fix this? BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Mon Aug 5 14:44:42 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Mon, 5 Aug 2019 16:44:42 +0200 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: <09A8840B4970AE4F988B7B67087395CA0912EEE5@MOSTLS1MSGUSRFG.ITServices.sbc.com> References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> <09A8840B4970AE4F988B7B67087395CA0912EEE5@MOSTLS1MSGUSRFG.ITServices.sbc.com> Message-ID: Hi Michael, Thanks for the details because our target is really multinodes. Except for the docs, is the light as green as Aiab for seaworthy-virt? Loïc Le lun. 5 août 2019 à 16:30, BEAVER, MICHAEL A a écrit : > Hi Loic, > > > > To add to what Kaspars has said: > > > > Thanks for the heads up! Yeah, we noticed the quagga image disappear late > last week and have been investigating a suitable replacement for it. > > > > The aiab site under Treasuremap is designed to be a replacement for the > traditional airship-in-a-bottle single node deployment, which is > considerably different from the multimode environment you have been using, > but is still very useful. You can read more about it here [0] > > > > As for the seaworthy-virt site, that is a new site we made in order to use > the airship-in-a-bottle multinode environment with the Treasuremap > manifests. The instructions to use this environment are here [1] however > they are not quite done yet and are still under review. > > > > [0] > https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab > > [1] https://review.opendev.org/#/c/655517/ > > > > > > *From:* SKELS, KASPARS > *Sent:* Monday, August 5, 2019 9:20 AM > *To:* Loic Le Gal ; > airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] [Aiab] Error building Gate multinode > site : Quagga 3.3.2 image not found > > > > ****Security Advisory:* This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > Hi, > > > > yes, we are slowly moving things from airship-in-a-bottle repo to > treasuremap (to have common/single place for all the site reference > manifests). > > From your pipelines/testing the AIAB in treasuremap is working very stable > and we have started to recommend people to move to treasuremap. > > > > You may also use most recent tag v1.3 – but master should also be green > right now. > > > > Kindly, Kaspars > > > > > > > > *From:* Loic Le Gal > *Sent:* Monday, August 5, 2019 8:25 AM > *To:* airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] [Aiab] Error building Gate multinode > site : Quagga 3.3.2 image not found > > > > minor typo & update: > > We use a commit from the beginning of July > (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. > > > > Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since > 2017) seems to be obsolete and its docker image has been removed from the > Docker Hub. > > Quagga doesn't seems to be used by the Airship-in-a-bottle version > integrated in Treasumap/site. > > Is this Aiab version OK ? (latest on master of TreasureMap) > > > > BTW, I've just found that a new site has been added in the beginning of > August: *seaworthy-virt *[1] > > => it seems to be what some other people and I were looking for (Cf. [2]) > > > > As someone tested it? > > > > [1] > https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt > > > [2] > http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html > > > > > http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html > > > > > BR, Loïc > > > > Le lun. 5 août 2019 à 11:50, Loic Le Gal a > écrit : > > Hello Airshipers, > > > > Back from holidays I try to launch a full rebuild of Airship in a bottle > multinode and I get a strange error in the BGP_touter stage: the quagga > image referenced doesn't exist anymore, and this is confirmed by browsing > https://hub.docker.com/r/cumulusnetworks/quagga > > > > > === Executing stage Create BGP router === > Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally > docker: Error response from daemon: pull access denied for > cumulusnetworks/quagga, repository does not exist or may require 'docker > login'. > See 'docker run --help'. > > == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == > > > > Note that we use a tag from March (we added minor changes) and everything > was running correctly upto the Overcloud. The Quagga 3.3.2 is still > referenced in latest version on master. > > > > => any idea to fix this? > > > > BR, > > > > Loïc > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Mon Aug 5 15:02:55 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Mon, 5 Aug 2019 15:02:55 +0000 Subject: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found In-Reply-To: References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808807@MOKSCY3MSGUSRGI.ITServices.sbc.com> <09A8840B4970AE4F988B7B67087395CA0912EEE5@MOSTLS1MSGUSRFG.ITServices.sbc.com> Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E80893E@MOKSCY3MSGUSRGI.ITServices.sbc.com> I would say it is work in progress.. but it should be soon 😊. Feel free to also check and ask questions more interactively on IRC #airshipit. /Kaspars From: Loic Le Gal Sent: Monday, August 5, 2019 9:45 AM To: BEAVER, MICHAEL A Cc: SKELS, KASPARS ; airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found Hi Michael, Thanks for the details because our target is really multinodes. Except for the docs, is the light as green as Aiab for seaworthy-virt? Loïc Le lun. 5 août 2019 à 16:30, BEAVER, MICHAEL A > a écrit : Hi Loic, To add to what Kaspars has said: Thanks for the heads up! Yeah, we noticed the quagga image disappear late last week and have been investigating a suitable replacement for it. The aiab site under Treasuremap is designed to be a replacement for the traditional airship-in-a-bottle single node deployment, which is considerably different from the multimode environment you have been using, but is still very useful. You can read more about it here [0] As for the seaworthy-virt site, that is a new site we made in order to use the airship-in-a-bottle multinode environment with the Treasuremap manifests. The instructions to use this environment are here [1] however they are not quite done yet and are still under review. [0] https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab [1] https://review.opendev.org/#/c/655517/ From: SKELS, KASPARS Sent: Monday, August 5, 2019 9:20 AM To: Loic Le Gal >; airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi, yes, we are slowly moving things from airship-in-a-bottle repo to treasuremap (to have common/single place for all the site reference manifests). From your pipelines/testing the AIAB in treasuremap is working very stable and we have started to recommend people to move to treasuremap. You may also use most recent tag v1.3 – but master should also be green right now. Kindly, Kaspars From: Loic Le Gal > Sent: Monday, August 5, 2019 8:25 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] [Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found minor typo & update: We use a commit from the beginning of July (2d7398fc21c3b2ccbaf5a67c7c96cbeeccc42afa) and not March. Investigation shows that cumulusnetworks/quagga (V3.3.2 not updated since 2017) seems to be obsolete and its docker image has been removed from the Docker Hub. Quagga doesn't seems to be used by the Airship-in-a-bottle version integrated in Treasumap/site. Is this Aiab version OK ? (latest on master of TreasureMap) BTW, I've just found that a new site has been added in the beginning of August: seaworthy-virt [1] => it seems to be what some other people and I were looking for (Cf. [2]) As someone tested it? [1] https://opendev.org/airship/treasuremap/src/branch/master/site/seaworthy-virt [2] http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000480.html http://lists.airshipit.org/pipermail/airship-discuss/2019-May/000478.html BR, Loïc Le lun. 5 août 2019 à 11:50, Loic Le Gal > a écrit : Hello Airshipers, Back from holidays I try to launch a full rebuild of Airship in a bottle multinode and I get a strange error in the BGP_touter stage: the quagga image referenced doesn't exist anymore, and this is confirmed by browsing https://hub.docker.com/r/cumulusnetworks/quagga === Executing stage Create BGP router === Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally docker: Error response from daemon: pull access denied for cumulusnetworks/quagga, repository does not exist or may require 'docker login'. See 'docker run --help'. == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == Note that we use a tag from March (we added minor changes) and everything was running correctly upto the Overcloud. The Quagga 3.3.2 is still referenced in latest version on master. => any idea to fix this? BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Mon Aug 5 15:56:00 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Mon, 5 Aug 2019 15:56:00 +0000 Subject: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment In-Reply-To: References: Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808AE8@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi Anirudh, The Airship Seaworthy is a bare-metal production reference implementation of Airship deployment, e.g. deployment that has 3 control servers (to carry HA and Ceph data replication), as well as ceph setup/replication for tenants data/VMs, redundant/bonded networks, and there are also things as DNS/TLS requirements to get this up and running. We also have Airsloop that is meant for 2 bare-metal servers (1 control node, and 1 compute). This from your description might fit better with your HW – and is also much simpler to install, here are some simplifications for it compared to full setup https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html I would def recommend to fist get familiar with Airsloop and get it up and running. The software/components are all the same but configured in non-redundant way. For virtual setups we have 2 options right now available * You can very simply get AIAB running – it’s a 1 VM setup and will give you a feel to what Airship is https://github.com/airshipit/treasuremap/tree/master/tools/deployment/aiab * There is also virtual multi-node environment that was available in the airship-in-a-bottle repo (https://github.com/airshipit/airship-in-a-bottle/tree/master/tools/multi_nodes_gate). This is now being moved to treasuremap and I would wait a bit since it’s slightly outdated on the old airship-in-a-bottle repo. Kind regards, Kaspars From: Anirudh Gupta Sent: Wednesday, May 29, 2019 2:31 AM To: airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes. But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment? We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment. In that case, what possible infrastructure do we require for setting up the complete setup. Looking forward for your response. Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001 DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Mon Aug 5 16:09:50 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Mon, 5 Aug 2019 16:09:50 +0000 Subject: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment In-Reply-To: References: Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E808B71@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi, this is great to hear!! Here are few additional tips on the direction you are going * It is actually possible to configure Drydock/MAAS to talk to libvirt, it’s a bit tricky to setup all the SSH keys – but it’s possible https://github.com/airshipit/treasuremap/blob/master/site/seaworthy-virt/profiles/host/gate-vm-cp.yaml#L27 * There is a framework called mutlinode-gate or seaworthy-virt that aims to create more of a testing/gating environment using KVM and single host (launching at this moment 4 VMs). Most of that code was in older airship-in-a-bottle repo but is now being moved to treasuremap (site/seaworthy-virt) site and docs/scripts will come later https://review.opendev.org/#/c/655517/. This uses very similar idea of automating launching KVM VMs and then fully automated deploying Airship on top. Have a look! * For the disk name – ‘bootdisk’ is alias based on a SCSI ID, you can look it up with ‘sudo lshw -c disk’ and then update the HW profile, using direct name as sda is also OK, as you found https://github.com/airshipit/treasuremap/blob/master/site/airsloop/profiles/hardware/dell_r720xd.yaml#L45 * Yes, LMA (logging, monitoring, alerting) is on the heavier side, and in fact I believe in our current virtual setups (AIAB and virtual seaworthy) we disable deployment of them as well. It’s needed in production, though. The Airsloop itself was more meant as bare-metal; you may use it to run proper VMs to test virtual workloads/VNFs in more real setting as compute is bare-metal, but it’s great you got it running!! Cheers, Kaspars From: Li, Cheng1 Sent: Sunday, June 9, 2019 12:59 AM To: Anirudh Gupta ; airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: Re: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Finally, I have been able to deploy airsloop on virtual env. I created two VMs(libvirt/kvm driven), one for genesis and the other for compute node. These two VMs were on the same host. As the compute node VM is supposed to be provisioned by maas via ipmi/pxe. So I used virtualbmc to simulate the ipmi. I authored the site by following these two guides[1][2]. It’s the mix of guide[1] and guide[2]. The commands I used are all these ones[3]. After fixing several issue, I have deployed the virtual airsloop env. I list here some issues I met: 1. Node identify failed. At the beginning of step ‘prepare_and_deploy_nodes’, the drydock power on the compute node VM via ipmi. Once the compute VM starts up via pxe boot, it runs script to detect local network interfaces and sends the info back to drycok. So the drydock can identify the node based on the received info. But the compute VM doesn’t have real ILO interface, so the drydock can’t identify it. What I did to workaround this was to manually fill the ipmi info on maas web page. 2. My host doesn’t have enough CPU cores, neither the VMs. So I had to increase --pods-per-core in kubelet.yaml. 3. The disk name in compute VM is vda, instead of sda. Drydock can’t map the alias device name to vda, so I had to used the fixed alias name ‘vda’ which is the same as it’s real device name.(it was ‘bootdisk’) 4. My host doesn’t have enough resource(CPU, memory), so I removed some resource consuming components(logging, monitoring). Besides, I disabled the neutron rally test. As it failed with timeout error because of the resource limits. I also paste my site changes[4] for reference. [1] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html [2] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html [3] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started [4] https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aaddec96b8cf2645e Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Thursday, May 30, 2019 7:29 PM To: Li, Cheng1 >; airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, I am trying to create Airship-Seaworthy from the link https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html It requires 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes to be configured, but there is no documentation of how to install and getting started with Airship-Seaworthy. Do we need to follow the “Getting Started” section mentioned in Airsloop or will there be any difference in case of Seaworthy. https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started Also what all configurations need to be run from the 3 controller nodes and what needs to be run from 3 computes? Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) From: Li, Cheng1 > Sent: 30 May 2019 08:29 To: Anirudh Gupta >; airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment I have the same question. I haven’t seen any docs which guides how to deploy airsloop/air-seaworthy in virtual env. I am trying to deploy airsloop on libvirt/kvm driven virtual env. Two VMs, one for genesis, the other for compute. Virtualbmc for ipmi simulation. The genesis.sh scripts has been run on genesis node without error. But deploy_site fails at prepare_and_deploy_nodes task(action ‘set_node_boot’ timeout). I am still investigating this issue. It will be great if we have official document for this scenario. Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Wednesday, May 29, 2019 3:31 PM To: airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes. But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment? We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment. In that case, what possible infrastructure do we require for setting up the complete setup. Looking forward for your response. Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001 DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Aug 5 18:44:51 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 5 Aug 2019 18:44:51 +0000 Subject: [Airship-discuss] AIB install issue In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e= From rv6848 at att.com Mon Aug 5 19:14:30 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Mon, 5 Aug 2019 19:14:30 +0000 Subject: [Airship-discuss] TC Meeting Scheduled In-Reply-To: <9B4615ED4FEDC74EA1FAF8B11F578BFA5587B067@MOSTLS1MSGUSREG.ITServices.sbc.com> References: <9B4615ED4FEDC74EA1FAF8B11F578BFA5587B067@MOSTLS1MSGUSREG.ITServices.sbc.com> Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA5588277C@MOSTLS1MSGUSREG.ITServices.sbc.com> The TC has rescheduled this meeting to avoid other conflicts. It will be held the 2nd Thursday of the month @ 8am CST. Hence this week Thursday will be the 1st meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering From: VAN WYK, RYAN L Sent: Friday, August 2, 2019 12:19 PM To: airship-discuss at lists.airshipit.org Subject: TC Meeting Scheduled Airship community. The Airship TC has determined the logistics for the monthly meeting. We will meet on the 1st Tuesday of every month at 9am CST, unless there is a conflict. The date/time and logistics for each meeting will be posted on the TC Wiki @ https://wiki.openstack.org/wiki/Airship/Airship-TC This is also where the meeting agenda/minutes will be posted. This is an open meeting, but Q&A from non-TC members will be limited to a defined time at the end of the meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848 at att.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From rv6848 at att.com Tue Aug 6 14:22:08 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Tue, 6 Aug 2019 14:22:08 +0000 Subject: [Airship-discuss] TC Meeting Scheduled In-Reply-To: <9B4615ED4FEDC74EA1FAF8B11F578BFA5588277C@MOSTLS1MSGUSREG.ITServices.sbc.com> References: <9B4615ED4FEDC74EA1FAF8B11F578BFA5587B067@MOSTLS1MSGUSREG.ITServices.sbc.com> <9B4615ED4FEDC74EA1FAF8B11F578BFA5588277C@MOSTLS1MSGUSREG.ITServices.sbc.com> Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA55883EBD@MOSTLS1MSGUSREG.ITServices.sbc.com> Correction, 9am CST. Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering From: VAN WYK, RYAN L Sent: Monday, August 5, 2019 2:15 PM To: airship-discuss at lists.airshipit.org Subject: RE: TC Meeting Scheduled The TC has rescheduled this meeting to avoid other conflicts. It will be held the 2nd Thursday of the month @ 8am CST. Hence this week Thursday will be the 1st meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering From: VAN WYK, RYAN L Sent: Friday, August 2, 2019 12:19 PM To: airship-discuss at lists.airshipit.org Subject: TC Meeting Scheduled Airship community. The Airship TC has determined the logistics for the monthly meeting. We will meet on the 1st Tuesday of every month at 9am CST, unless there is a conflict. The date/time and logistics for each meeting will be posted on the TC Wiki @ https://wiki.openstack.org/wiki/Airship/Airship-TC This is also where the meeting agenda/minutes will be posted. This is an open meeting, but Q&A from non-TC members will be limited to a defined time at the end of the meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848 at att.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Aug 7 01:01:16 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 06 Aug 2019 20:01:16 -0500 Subject: [Airship-discuss] Shanghai Summit Schedule is Live! Message-ID: <5D4A22DC.9090104@openstack.org> Hi everyone, The agenda for the Open Infrastructure Summit (formerly the OpenStack Summit) is now live! If you need a reason to join the Summit in Shanghai, November 4-6, here’s what you can expect: * Breakout sessions spanning 30+ open source projects from technical community leaders and organizations including ARM, WalmartLabs, China Mobile, China Railway, Shanghai Electric Power Company, China UnionPay, Haitong Securities Company, CERN, and more. * Project updates and onboarding from OSF projects: Airship, Kata Containers, OpenStack, StarlingX, and Zuul. * Join collaborative sessions at the Forum , where open infrastructure operators and upstream developers will gather to jointly chart the future of open source infrastructure, discussing topics ranging from upgrades to networking models and how to get started contributing. * Get hands on training around open source technologies directly from the developers and operators building the software. Now what? * Register before prices increase on August 14 at 11:59pm PT (August 15 at 2:59pm China Standard Time). * Recruiting new talent? Pitching a new product? Enhance the visibility of your organization by sponsoring the Summit ! Questions? Reach out to summit at openstack.org Cheers, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Wed Aug 7 12:39:04 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Wed, 7 Aug 2019 14:39:04 +0200 Subject: [Airship-discuss] Activating Prometheus (& other monitoring tools) for aiab Message-ID: Hi airshipers, I'd like to add Prometheus monitoring (+fluentbit, ...) to the new treasuremap/site/aiab; It seems that some charts already exist but I'm not sure the integration is finished because nothing usefull found in seaworthy site def. Server/client labels do not exist on the Genesis node so I've added them to site/aiab/profiles/genesis.yaml and launch again the whole genesis process from scratch but no new pods appear. (I also tried adding prometheus-global=true and prometheus-type=true labels) I've already searched in Armada read-the-docs. Even if the WIP in armada regarding automation of metrics collection is still a WIP [1), I just want to get prometheus pods (then add grafana, fluentbit, ...) Do you know where I can find information to add/activate the monitoring layer (osh-infra-monitoring) or just add a Prometheus pod ? [1] https://review.opendev.org/#/c/668980/ BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Wed Aug 7 15:06:58 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Wed, 7 Aug 2019 17:06:58 +0200 Subject: [Airship-discuss] Activating Prometheus (& other monitoring tools) for aiab In-Reply-To: References: Message-ID: Hi, Replying myself to close this thread. I finally succeed in creating prometheus-0 and alerter-0 pods by adding also -osh-infra-monitoring in the chart_groups: section of the file site/aiab/manifests/bootstrap.yaml. It seems to list the available charts, the deployment process looks in to match labels set on nodes. Le mer. 7 août 2019 à 14:39, Loic Le Gal a écrit : > Hi airshipers, > > I'd like to add Prometheus monitoring (+fluentbit, ...) to the new > treasuremap/site/aiab; > It seems that some charts already exist but I'm not sure the integration > is finished because nothing usefull found in seaworthy site def. > > Server/client labels do not exist on the Genesis node so I've added them > to site/aiab/profiles/genesis.yaml and launch again the whole genesis > process from scratch but no new pods appear. (I also tried adding > prometheus-global=true and prometheus-type=true labels) > > I've already searched in Armada read-the-docs. > Even if the WIP in armada regarding automation of metrics collection is > still a WIP [1), I just want to get prometheus pods (then add grafana, > fluentbit, ...) > > Do you know where I can find information to add/activate the monitoring > layer (osh-infra-monitoring) or just add a Prometheus pod ? > > [1] https://review.opendev.org/#/c/668980/ > > BR, Loïc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Wed Aug 7 15:27:38 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Wed, 7 Aug 2019 15:27:38 +0000 Subject: [Airship-discuss] Activating Prometheus (& other monitoring tools) for aiab In-Reply-To: References: , Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E80C0EA@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi, these charts are used in Airsloop/Seaworthy runs, so they should be tested, and especially since site/aiab uses sloop type, the resources are scaled down (less replicas, less storage requests), see https://github.com/airshipit/treasuremap/tree/master/type/sloop/charts/osh-infra. You should be able to deploy entire LMA (logging, monitoring, alerting) stack by adding this to full-site manifest - osh-infra-ingress-controller - osh-infra-ceph-config - osh-infra-radosgw - osh-infra-logging - osh-infra-monitoring - osh-infra-mariadb - osh-infra-dashboards This will add things like promethius, elasticsearch, kibana, etc. Part of the reasoning for not including these charts in the default AIAB site was to be able to limit resources to 20G of memory (so people can get it up and running in VMs on their laptops, and other resources constrained places). I wonder if you could investigate a way we could run AIAB (airship in a bottle) with an option (say something like --with-lma) or similar. We are having community IRC meetings every Tuesday 9AM CST and it would be a good topic to discuss. Kindly, Kaspars ________________________________ From: Loic Le Gal [l.legal.astellia at gmail.com] Sent: Wednesday, August 07, 2019 10:06 AM To: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Activating Prometheus (& other monitoring tools) for aiab Hi, Replying myself to close this thread. I finally succeed in creating prometheus-0 and alerter-0 pods by adding also -osh-infra-monitoring in the chart_groups: section of the file site/aiab/manifests/bootstrap.yaml. It seems to list the available charts, the deployment process looks in to match labels set on nodes. Le mer. 7 août 2019 à 14:39, Loic Le Gal > a écrit : Hi airshipers, I'd like to add Prometheus monitoring (+fluentbit, ...) to the new treasuremap/site/aiab; It seems that some charts already exist but I'm not sure the integration is finished because nothing usefull found in seaworthy site def. Server/client labels do not exist on the Genesis node so I've added them to site/aiab/profiles/genesis.yaml and launch again the whole genesis process from scratch but no new pods appear. (I also tried adding prometheus-global=true and prometheus-type=true labels) I've already searched in Armada read-the-docs. Even if the WIP in armada regarding automation of metrics collection is still a WIP [1), I just want to get prometheus pods (then add grafana, fluentbit, ...) Do you know where I can find information to add/activate the monitoring layer (osh-infra-monitoring) or just add a Prometheus pod ? [1] https://review.opendev.org/#/c/668980/ BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Aug 8 14:14:57 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 8 Aug 2019 16:14:57 +0200 Subject: [Airship-discuss] [sig][airship-bootstrap] airshipctl golang module vs. airshipctl interacting with a docker container Message-ID: Hello team, Hello Alan, Following up on an Airship-bootstrap call we have had yesterday, Alan described his alternative (lines 92-95 here https://etherpad.openstack.org/p/Airship_bootstrap, search for "isogen uses native go-lang library") which he was talking about close to the end of the call. I remember Alan has described this approach previously on one of design calls, I did not forget about it and I love this solution. What I was thinking about yesterday, was that creating a golang module for the airshipctl would be more complicated (at least for me) than to create a container image for a proof-of-concept stage. I'm all for not having containerd dependency in release version of airshipctl. I'd like to hear your feedback on this. Alan, What was the golang library you were talking about which could open and amend ISO image contents? And another question is what are the standard ISO images (esp. LiveCD) provided by vendors which have built-in cloud-init? Recording: https://attcorp.webex.com/attcorp/lsr.php?RCID=a05f4d1d798f40d79dfda57c9fa0e131 Recording password: HkYjdjq3 Recordings are stored on the server for 30 days only. Best regards, -- Roman Gorshunov From am240k at att.com Thu Aug 8 22:42:15 2019 From: am240k at att.com (MEADOWS, ALAN) Date: Thu, 8 Aug 2019 22:42:15 +0000 Subject: [Airship-discuss] [sig][airship-bootstrap] airshipctl golang module vs. airshipctl interacting with a docker container In-Reply-To: References: Message-ID: Roman, The go-lang library I had been looking at that supported reading and writing iso9660 (iso) images was diskfs: https://github.com/diskfs/go-diskfs The code samples on the README will walk you through filesystem manipulation. With regard to iso9660 filesystems, this does seem to have the ability to create iso9660 filesystems (https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) however I have not found or found the right examples that simply demonstrate manipulating an existing ISO (e.g. dropping in a file). Certain comments (like this one https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) have me wondering if there are some gaps or I have simply not spent enough time with it to understand the interfaces correctly. This presumed that operators would come to the table with (LiveCD) ISOs already generated and the responsibility of `airshipctl bootstral isogen` (or perhaps a better name) would be strictly to open up the path to the ISO, write cloud-init data in the right location, and write it back, preferably as a new image on the disk so the original remains untouched. To help operators generate custom LiveCDs though that have the packages they want pre-installed, I had envisioned we would be providing a separate toolkit to help build these images (whether this is containerized, bash, python, go-lang was entirely the choice of this toolkit. This would be an alternative to operators using out of the box LiveCDs from vendors. Anyways, this was the idea behind many of my comments on that call. As I mentioned on the etherpad, while having airshipctl call out to a runtime environment with an agreed upon interface to launch an operator provided container that would do this manipulation adds a dependency on airshipctl<->containers, it may make the operation of building that LiveCD more repeatable as the container image to use would be part of your declaration. In the above, it was a separate out of band process you would follow. Alan Meadows On 8/8/19, 7:17 AM, "Roman Gorshunov" wrote: Hello team, Hello Alan, Following up on an Airship-bootstrap call we have had yesterday, Alan described his alternative (lines 92-95 here https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_Airship-5Fbootstrap&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=EJ4k-ZQq9rUccFvreOF8yFdVt1QeKZURrJ71OdPNyAU&e=, search for "isogen uses native go-lang library") which he was talking about close to the end of the call. I remember Alan has described this approach previously on one of design calls, I did not forget about it and I love this solution. What I was thinking about yesterday, was that creating a golang module for the airshipctl would be more complicated (at least for me) than to create a container image for a proof-of-concept stage. I'm all for not having containerd dependency in release version of airshipctl. I'd like to hear your feedback on this. Alan, What was the golang library you were talking about which could open and amend ISO image contents? And another question is what are the standard ISO images (esp. LiveCD) provided by vendors which have built-in cloud-init? Recording: https://urldefense.proofpoint.com/v2/url?u=https-3A__attcorp.webex.com_attcorp_lsr.php-3FRCID-3Da05f4d1d798f40d79dfda57c9fa0e131&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=gOk3Ob1SfPyaSoEOgsC5DfYYDKur9gXSPJJVHEbR_VU&e= Recording password: HkYjdjq3 Recordings are stored on the server for 30 days only. Best regards, -- Roman Gorshunov _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=XEWJDL-YgGbN8ea1Y8Fvr4w9z8k6fynozH0GFPrBcKM&e= From paye600 at gmail.com Thu Aug 8 23:46:40 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Fri, 9 Aug 2019 01:46:40 +0200 Subject: [Airship-discuss] [sig][airship-bootstrap] airshipctl golang module vs. airshipctl interacting with a docker container In-Reply-To: References: Message-ID: <4A10798B-CC8F-48B5-B464-A285B92CF316@gmail.com> Alan, The go-diskfs doesn’t seem support manipulation of existing ISO’s. README says that “Any attempt to Mkdir() or OpenFile() in write/append/create modes or Write() to the file will result in an error.” [0]. Therefore, there would be a need to extract contents of existing iso, and rebuild it (go-diskfs supports El Torito cd-rom spec, which allows cd’s to be bootable). [0] https://github.com/diskfs/go-diskfs#read-only-filesystems Best regards, — Roman Gorshunov > On 9 Aug 2019, at 00:42, MEADOWS, ALAN wrote: > > Roman, > > The go-lang library I had been looking at that supported reading and writing iso9660 (iso) images was diskfs: > > https://github.com/diskfs/go-diskfs > > The code samples on the README will walk you through filesystem manipulation. With regard to iso9660 filesystems, this does seem to have the ability to create iso9660 filesystems (https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) however I have not found or found the right examples that simply demonstrate manipulating an existing ISO (e.g. dropping in a file). Certain comments (like this one https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) have me wondering if there are some gaps or I have simply not spent enough time with it to understand the interfaces correctly. > > This presumed that operators would come to the table with (LiveCD) ISOs already generated and the responsibility of `airshipctl bootstral isogen` (or perhaps a better name) would be strictly to open up the path to the ISO, write cloud-init data in the right location, and write it back, preferably as a new image on the disk so the original remains untouched. To help operators generate custom LiveCDs though that have the packages they want pre-installed, I had envisioned we would be providing a separate toolkit to help build these images (whether this is containerized, bash, python, go-lang was entirely the choice of this toolkit. This would be an alternative to operators using out of the box LiveCDs from vendors. > > Anyways, this was the idea behind many of my comments on that call. > > As I mentioned on the etherpad, while having airshipctl call out to a runtime environment with an agreed upon interface to launch an operator provided container that would do this manipulation adds a dependency on airshipctl<->containers, it may make the operation of building that LiveCD more repeatable as the container image to use would be part of your declaration. In the above, it was a separate out of band process you would follow. > > Alan Meadows > > On 8/8/19, 7:17 AM, "Roman Gorshunov" wrote: > > Hello team, > Hello Alan, > > Following up on an Airship-bootstrap call we have had yesterday, Alan > described his alternative (lines 92-95 here > https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_Airship-5Fbootstrap&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=EJ4k-ZQq9rUccFvreOF8yFdVt1QeKZURrJ71OdPNyAU&e=, search for "isogen > uses native go-lang library") which he was talking about close to the > end of the call. > > I remember Alan has described this approach previously on one of > design calls, I did not forget about it and I love this solution. What > I was thinking about yesterday, was that creating a golang module for > the airshipctl would be more complicated (at least for me) than to > create a container image for a proof-of-concept stage. I'm all for not > having containerd dependency in release version of airshipctl. > I'd like to hear your feedback on this. > > Alan, > What was the golang library you were talking about which could open > and amend ISO image contents? > > And another question is what are the standard ISO images (esp. LiveCD) > provided by vendors which have built-in cloud-init? > > Recording: https://urldefense.proofpoint.com/v2/url?u=https-3A__attcorp.webex.com_attcorp_lsr.php-3FRCID-3Da05f4d1d798f40d79dfda57c9fa0e131&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=gOk3Ob1SfPyaSoEOgsC5DfYYDKur9gXSPJJVHEbR_VU&e= > Recording password: HkYjdjq3 > Recordings are stored on the server for 30 days only. > > Best regards, > -- > Roman Gorshunov > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at 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=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=XEWJDL-YgGbN8ea1Y8Fvr4w9z8k6fynozH0GFPrBcKM&e= > From dukov at mirantis.com Fri Aug 9 05:50:24 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Fri, 9 Aug 2019 09:50:24 +0400 Subject: [Airship-discuss] [sig][airship-bootstrap] airshipctl golang module vs. airshipctl interacting with a docker container In-Reply-To: <4A10798B-CC8F-48B5-B464-A285B92CF316@gmail.com> References: <4A10798B-CC8F-48B5-B464-A285B92CF316@gmail.com> Message-ID: Roman, Alan As an alternative of using ISO we can switch to usb stick image: 1. It's supported by RedFish [1] 2. It should have RW capabilities 3. We probably can convert cloud image qcow2 to raw and just perform 'dd' to device (having nix based OS for airshipctl will be only requirement here) 4. Everyone are using usb sticks for OS deployment since it's hard to find CD-R to burn nowadays :) On Fri, Aug 9, 2019 at 3:51 AM Roman Gorshunov wrote: > Alan, > > The go-diskfs doesn’t seem support manipulation of existing ISO’s. README > says > that “Any attempt to Mkdir() or OpenFile() in write/append/create modes or > Write() > to the file will result in an error.” [0]. > > Therefore, there would be a need to extract contents of existing iso, and > rebuild it > (go-diskfs supports El Torito cd-rom spec, which allows cd’s to be > bootable). > > [0] https://github.com/diskfs/go-diskfs#read-only-filesystems > > Best regards, > — > Roman Gorshunov > > > On 9 Aug 2019, at 00:42, MEADOWS, ALAN wrote: > > > > Roman, > > > > The go-lang library I had been looking at that supported reading and > writing iso9660 (iso) images was diskfs: > > > > https://github.com/diskfs/go-diskfs > > > > The code samples on the README will walk you through filesystem > manipulation. With regard to iso9660 filesystems, this does seem to have > the ability to create iso9660 filesystems ( > https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) > however I have not found or found the right examples that simply > demonstrate manipulating an existing ISO (e.g. dropping in a file). > Certain comments (like this one > https://github.com/diskfs/go-diskfs/blob/master/filesystem/iso9660/iso9660.go#L49-L64) > have me wondering if there are some gaps or I have simply not spent enough > time with it to understand the interfaces correctly. > > > > This presumed that operators would come to the table with (LiveCD) ISOs > already generated and the responsibility of `airshipctl bootstral isogen` > (or perhaps a better name) would be strictly to open up the path to the > ISO, write cloud-init data in the right location, and write it back, > preferably as a new image on the disk so the original remains untouched. > To help operators generate custom LiveCDs though that have the packages > they want pre-installed, I had envisioned we would be providing a separate > toolkit to help build these images (whether this is containerized, bash, > python, go-lang was entirely the choice of this toolkit. This would be an > alternative to operators using out of the box LiveCDs from vendors. > > > > Anyways, this was the idea behind many of my comments on that call. > > > > As I mentioned on the etherpad, while having airshipctl call out to a > runtime environment with an agreed upon interface to launch an operator > provided container that would do this manipulation adds a dependency on > airshipctl<->containers, it may make the operation of building that LiveCD > more repeatable as the container image to use would be part of your > declaration. In the above, it was a separate out of band process you would > follow. > > > > Alan Meadows > > > > On 8/8/19, 7:17 AM, "Roman Gorshunov" wrote: > > > > Hello team, > > Hello Alan, > > > > Following up on an Airship-bootstrap call we have had yesterday, Alan > > described his alternative (lines 92-95 here > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_Airship-5Fbootstrap&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=EJ4k-ZQq9rUccFvreOF8yFdVt1QeKZURrJ71OdPNyAU&e=, > search for "isogen > > uses native go-lang library") which he was talking about close to the > > end of the call. > > > > I remember Alan has described this approach previously on one of > > design calls, I did not forget about it and I love this solution. What > > I was thinking about yesterday, was that creating a golang module for > > the airshipctl would be more complicated (at least for me) than to > > create a container image for a proof-of-concept stage. I'm all for not > > having containerd dependency in release version of airshipctl. > > I'd like to hear your feedback on this. > > > > Alan, > > What was the golang library you were talking about which could open > > and amend ISO image contents? > > > > And another question is what are the standard ISO images (esp. LiveCD) > > provided by vendors which have built-in cloud-init? > > > > Recording: > https://urldefense.proofpoint.com/v2/url?u=https-3A__attcorp.webex.com_attcorp_lsr.php-3FRCID-3Da05f4d1d798f40d79dfda57c9fa0e131&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=gOk3Ob1SfPyaSoEOgsC5DfYYDKur9gXSPJJVHEbR_VU&e= > > Recording password: HkYjdjq3 > > Recordings are stored on the server for 30 days only. > > > > Best regards, > > -- > > Roman Gorshunov > > > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at 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=OI-s0Rr_BtNj0OcKWGZyuA&m=39e3KOJnyQM7A29deZ-dZk7USCOUThcpuXal7e2-zVM&s=XEWJDL-YgGbN8ea1Y8Fvr4w9z8k6fynozH0GFPrBcKM&e= > > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From l.legal.astellia at gmail.com Fri Aug 9 13:13:56 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Fri, 9 Aug 2019 15:13:56 +0200 Subject: [Airship-discuss] Fwd: Activating Prometheus (& other monitoring tools) for aiab In-Reply-To: References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E80C0EA@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: Thanks again Kaspars, Adding all these charts seem too huge even for a 32 GB RAM VM (I'll try again, in case the failure came from a latency of our infra). Anyway, I succeed to add only Prometheus, AlertManager and Grafana by doing this: A - add these chartgroups in aiab bootstrap manifest - osh-infra-monitoring - osh-infra-ingress-controller - osh-infra-mariadb - osh-infra-dashboards B - Overload the osh-infra-dashboard chartgroup to include only grafana (using deckhand overloading mechanism instead of brute removal ) B1. add a label at the global layer to avoid Deckhand complains in B2 +++ b/global/software/charts/osh-infra/osh-infra-dashboards/chart-group.yaml @@ -6,6 +6,8 @@ metadata: layeringDefinition: abstract: false layer: global + labels: + name: osh-infra-dashboards-global storagePolicy: cleartext B2. create a new file at the type layer that only contains grafana: +++ b/type/sloop/charts/osh-infra/dashboards-chartgroup.yaml @@ -0,0 +1,20 @@ +--- +schema: armada/ChartGroup/v1 +metadata: + schema: metadata/Document/v1 + replacement: true + name: osh-infra-dashboards + layeringDefinition: + abstract: false + layer: type + parentSelector: + name: osh-infra-dashboards-global + actions: + - method: merge + path: . + storagePolicy: cleartext +data: + # disable kibana by changing the chartgroup content + chart_group: + - grafana +... C - Expose the services: kubectl expose pod/prometheus-0 -n osh-infra --type=NodePort --name=prometheus-dashboard kubectl expose pod/alertmanager-0 -n osh-infra --type=NodePort --name=alertmgr-dashboard kubectl expose service/grafana-dashboard -n osh-infra --type=NodePort --name=grafana-web Not every Grafana Dashboards are operational in aiab but those that are are really good ! BR, Loïc Le mer. 7 août 2019 à 17:27, SKELS, KASPARS a écrit : > Hi, > > these charts are used in Airsloop/Seaworthy runs, so they should be > tested, and especially since site/aiab uses sloop type, the resources are > scaled down (less replicas, less storage requests), see > https://github.com/airshipit/treasuremap/tree/master/type/sloop/charts/osh-infra. > You should be able to deploy entire LMA (logging, monitoring, alerting) > stack by adding this to full-site manifest > > - osh-infra-ingress-controller > - osh-infra-ceph-config > - osh-infra-radosgw > - osh-infra-logging > - osh-infra-monitoring > - osh-infra-mariadb > - osh-infra-dashboards > > This will add things like promethius, elasticsearch, kibana, etc. > > Part of the reasoning for not including these charts in the default AIAB > site was to be able to limit resources to 20G of memory (so people can get > it up and running in VMs on their laptops, and other resources constrained > places). > > I wonder if you could investigate a way we could run AIAB (airship in a > bottle) with an option (say something like --with-lma) or similar. > > We are having community IRC meetings every Tuesday 9AM CST and it would be > a good topic to discuss. > > Kindly, Kaspars > > > > > ------------------------------ > *From:* Loic Le Gal [l.legal.astellia at gmail.com] > *Sent:* Wednesday, August 07, 2019 10:06 AM > *To:* airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] Activating Prometheus (& other > monitoring tools) for aiab > > Hi, > > Replying myself to close this thread. > I finally succeed in creating prometheus-0 and alerter-0 pods by adding > also -osh-infra-monitoring in the chart_groups: section of the > file site/aiab/manifests/bootstrap.yaml. > It seems to list the available charts, the deployment process looks in to > match labels set on nodes. > > Le mer. 7 août 2019 à 14:39, Loic Le Gal a > écrit : > >> Hi airshipers, >> >> I'd like to add Prometheus monitoring (+fluentbit, ...) to the new >> treasuremap/site/aiab; >> It seems that some charts already exist but I'm not sure the integration >> is finished because nothing usefull found in seaworthy site def. >> >> Server/client labels do not exist on the Genesis node so I've added them >> to site/aiab/profiles/genesis.yaml and launch again the whole genesis >> process from scratch but no new pods appear. (I also tried adding >> prometheus-global=true and prometheus-type=true labels) >> >> I've already searched in Armada read-the-docs. >> Even if the WIP in armada regarding automation of metrics collection is >> still a WIP [1), I just want to get prometheus pods (then add grafana, >> fluentbit, ...) >> >> Do you know where I can find information to add/activate the monitoring >> layer (osh-infra-monitoring) or just add a Prometheus pod ? >> >> [1] https://review.opendev.org/#/c/668980/ >> >> >> BR, Loïc >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From airshipcloud at gmail.com Sat Aug 10 05:24:05 2019 From: airshipcloud at gmail.com (Aaron Blair) Date: Sat, 10 Aug 2019 01:24:05 -0400 Subject: [Airship-discuss] Divestiture Message-ID: 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) 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), 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), 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. Thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: From soujanya at atsgen.com Mon Aug 12 05:59:14 2019 From: soujanya at atsgen.com (Soujanya R M) Date: Mon, 12 Aug 2019 01:59:14 -0400 Subject: [Airship-discuss] =?utf-8?q?Issue_with_intalling_airship-in-a-bot?= =?utf-8?q?tle_on_dev=5Fsingle=5Fnode?= Message-ID: <1570a-5d510000-29-53fb8680@48757997> Hi, I am facing an issue while installing airship-in-a-bottle dev_single_node. This is the error that appears. Status: Downloaded newer image for quay.io/airshipit/promenade:master + PORT=9000 + UWSGI_TIMEOUT=300 + PROMENADE_THREADS=1 + PROMENADE_WORKERS=4 + '[' promenade = server ']' + exec promenade generate-certs -o /target deployment_files.yaml Traceback (most recent call last):   File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2168, in __getattr__     return self._get(name)   File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2602, in _get     value, loc = self._do_get(name, group, namespace)   File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2620, in _do_get     info = self._get_opt_info(name, group)   File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2796, in _get_opt_info     raise NoSuchOptError(opt_name, group) oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] During handling of the above exception, another exception occurred: Traceback (most recent call last):   File "/usr/local/bin/promenade", line 10, in     sys.exit(promenade())   File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__     return self.main(*args, **kwargs)   File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main     rv = self.invoke(ctx)   File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1063, in invoke     Command.invoke(self, ctx)   File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke     return ctx.invoke(self.callback, **ctx.params)   File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke     return callback(*args, **kwargs)   File "/opt/promenade/promenade/cli.py", line 16, in promenade     logging.setup(verbose=verbose)   File "/opt/promenade/promenade/logging.py", line 87, in setup     log_level = cfg.CONF.logging.log_level   File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2172, in __getattr__     raise NoSuchOptError(name) oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] + cp /root/deploy/genesis/certificates.yaml /root/deploy/airship-in-a-bottle/deployment_files/site/demo/secrets cp: cannot stat '/root/deploy/genesis/certificates.yaml': No such file or directory + error 'setting up certs with Promenade' + set +x Error when setting up certs with Promenade. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy. This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. A similar issue has been called out previously here: [0] could someone please help me out with this issue. Thanks & Regards, Soujanya R M -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Aug 12 14:06:51 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 12 Aug 2019 14:06:51 +0000 Subject: [Airship-discuss] AIB install issue In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A0C4F5@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN ; airship-discuss at lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e= From MM9745 at att.com Mon Aug 12 16:13:35 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 12 Aug 2019 16:13:35 +0000 Subject: [Airship-discuss] Divestiture In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A0C654@MOSTLS1MSGUSRFF.ITServices.sbc.com> 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. Thanks, Matt [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 Sent: Saturday, August 10, 2019 12:24 AM To: kbaegis at gmail.com; MCEUEN, MATT 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) 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), 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), 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. Thanks, Aaron -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Mon Aug 12 16:45:29 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Mon, 12 Aug 2019 18:45:29 +0200 Subject: [Airship-discuss] Issue with intalling airship-in-a-bottle on dev_single_node In-Reply-To: <1570a-5d510000-29-53fb8680@48757997> References: <1570a-5d510000-29-53fb8680@48757997> Message-ID: Hi Soyana, This bug should have been fixed in latest promenade image. Try to pull fresh code and re-run with promenade image tagged with `:cffca055fe78f53dfae029ee37d981507cb089fe` comit id. Sorry for confusion. We didn't have (actually still don't have) this problem covered by our CI tests. Best regards, -- Roman Gorshunov On Mon, Aug 12, 2019 at 7:59 AM Soujanya R M wrote: > > Hi, > > I am facing an issue while installing airship-in-a-bottle dev_single_node. This is the error that appears. > > Status: Downloaded newer image for quay.io/airshipit/promenade:master > + PORT=9000 > + UWSGI_TIMEOUT=300 > + PROMENADE_THREADS=1 > + PROMENADE_WORKERS=4 > + '[' promenade = server ']' > + exec promenade generate-certs -o /target deployment_files.yaml > Traceback (most recent call last): > File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2168, in __getattr__ > return self._get(name) > File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2602, in _get > value, loc = self._do_get(name, group, namespace) > File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2620, in _do_get > info = self._get_opt_info(name, group) > File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2796, in _get_opt_info > raise NoSuchOptError(opt_name, group) > oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] > > During handling of the above exception, another exception occurred: > Traceback (most recent call last): > File "/usr/local/bin/promenade", line 10, in > sys.exit(promenade()) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__ > return self.main(*args, **kwargs) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main > rv = self.invoke(ctx) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1063, in invoke > Command.invoke(self, ctx) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke > return ctx.invoke(self.callback, **ctx.params) > File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke > return callback(*args, **kwargs) > File "/opt/promenade/promenade/cli.py", line 16, in promenade > logging.setup(verbose=verbose) > File "/opt/promenade/promenade/logging.py", line 87, in setup > log_level = cfg.CONF.logging.log_level > File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2172, in __getattr__ > raise NoSuchOptError(name) > oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] > + cp /root/deploy/genesis/certificates.yaml /root/deploy/airship-in-a-bottle/deployment_files/site/demo/secrets > cp: cannot stat '/root/deploy/genesis/certificates.yaml': No such file or directory > + error 'setting up certs with Promenade' > + set +x > Error when setting up certs with Promenade. > + exit 1 > + clean > + set +x > To remove files generated during this script's execution, delete /root/deploy. > This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. > > A similar issue has been called out previously here: [0] > could someone please help me out with this issue. > > Thanks & Regards, > Soujanya R M _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From MM9745 at att.com Tue Aug 13 16:00:27 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 13 Aug 2019 16:00:27 +0000 Subject: [Airship-discuss] AIB install issue In-Reply-To: References: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970A0C4F5@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A0CD90@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hey Julien, Happy to hear of progress! Can you please clarify this one: "I let it upgrade during install instead of doing it after the install" -- do you mean that you did some of the steps here [1] in parallel? I learned yesterday that Hyon Park is getting the same error when running AIAB, consistently (just like you were), and I'm not sure what the common thread is yet. He was running in a VM on a public cloud on an Ubuntu 16.04 host. I'm not able to reproduce the issue, but I suspect there may be a common thread between your old environment and his current one. I'm also interested in your new issue. AIAB should be pretty turn-key, installing its own dependencies, etc! [1]: https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab -----Original Message----- From: BERTOZZI, JULIEN Sent: Tuesday, August 13, 2019 9:20 AM To: MCEUEN, MATT ; 'airship-discuss at lists.airshipit.org' Subject: RE: AIB install issue Hello Matt ! Well, as per recommendation on the aiab site, I always wipe between tries. I've had it a few times before posting to the ML. I retried now that I got your message (same image on the same usb key, same machine). Only difference that shouldn't affect anything is that I let it upgrade during install instead of doing it after the install Anyway, it seems to work, I got my k8s env 😊 Helm wasn't working properly though, it didn't created it's files. Doing a new `helm init` didn't fixed. Although it said the files were created, well, they were nowhere to be found Onto the next step Thanks for your time, J -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 12, 2019 4:07 PM To: Bertozzi, Julien ; 'airship-discuss at lists.airshipit.org' Subject: RE: AIB install issue Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN ; airship-discuss at lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e= From MM9745 at att.com Tue Aug 13 20:43:51 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 13 Aug 2019 20:43:51 +0000 Subject: [Airship-discuss] [airship-announce] Airship Working Committee Election Results Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A0CEEA@MOSTLS1MSGUSRFF.ITServices.sbc.com> Team, Voting for the Airship Working Committee has concluded, and detailed results can be found here [1]. The the following members of the Working Committee have been elected to a one-year term: - Drew Walters (AT&T) - Kaspars Skels (Ericsson) - Matt McEuen (AT&T) - Nishant Kumar (Ericsson) These results are subject to the eligibility requirements and two-per-employer cap as outlined in the Airship Governance. I'd like to sincerely thank all of the Airship community members who nominated to run for the WC. They reflect a strong, diverse team with a lot of ideas and energy to improve Airship, as a project and as a community. I encourage them to actively pursue these goals with support from the team, and to nominate for the WC in the future. Thanks, Matt [1]: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_2f5847e3165e9768 From MM9745 at att.com Mon Aug 19 13:50:05 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 19 Aug 2019 13:50:05 +0000 Subject: [Airship-discuss] [WC] Initial Working Committee meeting Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A1C710@MOSTLS1MSGUSRFF.ITServices.sbc.com> The initial Airship Working Committee meeting will be today, 2pm-3pm USA Central Time (19:00-20:00 UTC). Connectivity info can be found here[1]. The Airship community is welcome to join and listen in, and I plan to save time at the end for open floor discussion. Apologies for the late notice, meant to send this out on Friday. However, I do plan to record this for anyone who'd like to catch up. Thanks, Matt [1]: https://wiki.openstack.org/wiki/Airship/Airship-WC -------------- next part -------------- An HTML attachment was scrubbed... URL: From rv6848 at att.com Mon Aug 19 13:57:21 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Mon, 19 Aug 2019 13:57:21 +0000 Subject: [Airship-discuss] Airship in the news Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA558D3CA6@MOSTLS1MSGUSREG.ITServices.sbc.com> Press Release: https://about.att.com/story/2019/att_dell_opensource5g.html News: Bloomberg First Word [Newsletter] Dell, AT&T Collaborate on Open Source Edge Computing, 5G Infra | Giulia Camillo Aug. 15, 2019 Dell Technologies and AT&T are jointly exploring the development of open infrastructure technology areas to support new use cases and service opportunities in cloud-oriented 5G. * Goals include delivering open source automation capabilities across infrastructure stack, jointly enhancing additional open source efforts including Metal3-io and OpenStack Ironic, integrate Kubernetes Cluster API Channelnomics Dell, AT&T Partnering on the Network Edge | Channelnomics staff Aug. 15, 2019 CRN AT&T, Dell Team Up To Tackle Open-Source Edge Computing, 5G | Gina Narcisi Aug. 15, 2019 EnterpriseAI AT&T, Dell Partner to Advance 5G Cloud | George Leopold Aug. 15, 2019 FierceTelecom Led by AT&T, Dell takes flight to Airship open source project | Mike Robuck Aug. 15, 2019 Light Reading Dell Flying to 5G Cloud on AT&T-Led 'Airship' | Mitch Wagner Aug. 15, 2019 SDxCentral AT&T Brings Dell Technologies Into the Airship Project | Matt Kapko Aug. 15, 2019 Seeking Alpha Dell, AT&T partner on open source tech | Brandy Betz Aug. 15, 2019 siliconANGLE Dell and AT&T collaborate on open-source 5G network edge infrastructure | Mike Wheatley Aug. 15, 2019 telecompaper Dell Technologies, AT&T collaborate on open source edge computing, 5G software infrastructure Aug. 15, 2019 Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848 at att.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 11916 bytes Desc: not available URL: From MM9745 at att.com Mon Aug 19 20:34:50 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 19 Aug 2019 20:34:50 +0000 Subject: [Airship-discuss] [WC] 2019-08-19 Meeting Notes Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A1CAC6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Meeting notes from the 8/19 Airship Working Committee meeting: . Start an every-other week WC meeting cadence beginning on August 26th . The last fifteen minutes of every WC meeting will be an "open forum" for non-WC members  . Proposal:  hold a special election for the fifth WC seat, three months after the first election, with a duration of 9 months . The WC will create a feedback survey to gather input on Airship community pain points and opportunities . Nishant will host IRC meeting on the 20th, Kaspars on the 27th Full agenda and notes can be found here [1]. Thanks, Matt [1]: https://etherpad.openstack.org/p/airship-wc-meeting-2019-08-19 From MM9745 at att.com Mon Aug 19 22:28:28 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 19 Aug 2019 22:28:28 +0000 Subject: [Airship-discuss] [WC] 2019-08-19 Meeting Notes In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A1CAC6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A1CAC6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A1CB8A@MOSTLS1MSGUSRFF.ITServices.sbc.com> Also: the recording is available from the working committee Wiki. https://wiki.openstack.org/wiki/Airship/Airship-WC -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 19, 2019 3:35 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] [WC] 2019-08-19 Meeting Notes *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Meeting notes from the 8/19 Airship Working Committee meeting: . Start an every-other week WC meeting cadence beginning on August 26th . The last fifteen minutes of every WC meeting will be an "open forum" for non-WC members  . Proposal:  hold a special election for the fifth WC seat, three months after the first election, with a duration of 9 months . The WC will create a feedback survey to gather input on Airship community pain points and opportunities . Nishant will host IRC meeting on the 20th, Kaspars on the 27th Full agenda and notes can be found here [1]. Thanks, Matt [1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_airship-2Dwc-2Dmeeting-2D2019-2D08-2D19&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=fcOCENqZB3BkwHshiVtu5luV0p9xD8ecMhlucxaJYDs&s=9JkQuODSRdM0U946Uuy0p-Fm-1Su17dzxjmD5RtK_74&e= _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=fcOCENqZB3BkwHshiVtu5luV0p9xD8ecMhlucxaJYDs&s=l170SgRKGZTE38GSWfnB-_vSyxXXVcpiaCNbDoXdIVY&e= From rv6848 at att.com Tue Aug 20 12:52:14 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Tue, 20 Aug 2019 12:52:14 +0000 Subject: [Airship-discuss] [TC - August 8th TC Meeting Action Items Follow-up] Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA558D87D8@MOSTLS1MSGUSREG.ITServices.sbc.com> As a follow-up to a few TC Action Items: 1. This is the link to the feedback from the OSF on our progress towards confirmation for your consideration: https://etherpad.openstack.org/p/AirshipConfirmation * I am happy with this feedback, since it is capturing a point in time of an upward trajectory. I believe both concerns were fair, and we're moving in the right direction. * Although the SIGs are all run by AT&T folks, I would like to see SUSE work with Rodolfo to take point on the UI SIG in the near future. * I believe the "non-AT&T usage" argument will work itself out as Mirantis and SUSE are successful with their products, and given our efforts to talk with other operators and companies like Starbucks. 2. Bin Hu is taking ownership of creating the monthly "Airship Update" that will be sent to companies and individuals who have expressed interest in Airship. The goal is to keep them aware of the progress our community is making, and hopefully help them make the decision to join us. The structure of the email that will go out at the start of each month follows: * What's New: i. E.g. new additions to the community (e.g. Dell joining the team) ii. Other news/ milestones * The Airship Blog: i. Topic/ Link the blog releases for that month. * JIRA Status: i. Any metrics we can pull from JIRA/ visualize to show progress on the project since last month. * Get Involved: i. List next month's meetings/ links to page with logistics. * End the email with instructions of how to opt out/ or correct the point of contact (e.g. email rv6848 at att.com). Also ask if they have any news related to Airship (e.g. have started to use it) to share that back with rv6848 at att.com. 1. To support the above, and other outreach efforts I am creating a contact list. I will maintain this and share on a need to know basis. For those of you who have points of contact for folks that have expressed an interest in Airship, please share their name/ email with me. 2. A new section has been created by Bin Hu on the Airship Wiki. The goal of this section is to create a collection of presentations related to Airship as a one stop shop to make it easier for folks to come up to speed. Bin has populated it with the list we have, but if others have more to add, please do so. * Wiki section for Airship presentations: https://wiki.openstack.org/wiki/Airship/Airship-Presentations. i. Bin Captured I captured all 8 current presentations from https://www.airshipit.org/community/. ii. The wiki section can be navigated from https://wiki.openstack.org/wiki/Airship , then click "8 Airship Presentations", then follow the link of "Airship Presentations". 1. I have invited Chris Hoge/ OSF team to join the TC meetings monthly, and we will have a agenda item for them to speak to OSF feedback. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848 at att.com -------------- next part -------------- A non-text attachment was scrubbed... Name: winmail.dat Type: application/ms-tnef Size: 18916 bytes Desc: not available URL: From jimmy at openstack.org Wed Aug 21 19:18:18 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 21 Aug 2019 14:18:18 -0500 Subject: [Airship-discuss] Shanghai Forum Selection Committee Message-ID: <5D5D98FA.3080908@openstack.org> Hello Airship! The Forum in Shanghai is rapidly approaching. We would love 1 volunteer from Airship for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. For information on the Summit in Shanghai: https://www.openstack.org/summit/shanghai-2019/ For more information on the Forum, please see:https://wiki.openstack.org/wiki/Forum Please reach out to myself orknelson at openstack.org if you're interested. Volunteers should respond on or before September 2, 2019. Cheers, Jimmy From rp2723 at att.com Thu Aug 22 21:11:38 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 22 Aug 2019 21:11:38 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-yaml] Meetings Message-ID: <99088997CCAD0C4BA20008FD094344963C37853F@MISOUT7MSGUSRDI.ITServices.sbc.com> Canceling, This is a Holiday in the US · Etherpad : https://etherpad.openstack.org/p/Airship_Yaml Notice that the subject line includes [sig][airship-yaml] , please make sure you add this to any email to airship-discuss at lists.airshipit.org when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2195 bytes Desc: not available URL: From rp2723 at att.com Thu Aug 22 21:13:02 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 22 Aug 2019 21:13:02 +0000 Subject: [Airship-discuss] [sig][airship-yaml] Canceled: Meeting - Sept 2 , 2019 Message-ID: <11716BEF-7C8E-4278-8FE7-AAB5F29E571F@att.com> Cancelled, This is a Holiday in the US Etherpad : https://etherpad.openstack.org/p/Airship_Yaml Notice that the subject line includes [sig][airship-yaml] , please make sure you add this to any email to airship-discuss at lists.airshipit.org when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Thu Aug 22 21:17:11 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 22 Aug 2019 21:17:11 +0000 Subject: [Airship-discuss] Canceled: Airship - Open Design Call - Tuesday Aug 27, 2019 Message-ID: CANCELLED – TUESDAY, AUGUST 27, 2019 - AIRSHIP DESIGN CALL Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Aug 26 19:13:40 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 26 Aug 2019 19:13:40 +0000 Subject: [Airship-discuss] [WC] 2019-08-19 Meeting Notes In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A1CB8A@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A1CAC6@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970A1CB8A@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A27909@MOSTLS1MSGUSRFF.ITServices.sbc.com> Today's WC meeting is cancelled due to conflicts and out-of-office - we will pick up two weeks from today. -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 19, 2019 5:28 PM To: 'airship-discuss at lists.airshipit.org' Subject: RE: [Airship-discuss] [WC] 2019-08-19 Meeting Notes Also: the recording is available from the working committee Wiki. https://wiki.openstack.org/wiki/Airship/Airship-WC -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 19, 2019 3:35 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] [WC] 2019-08-19 Meeting Notes *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Meeting notes from the 8/19 Airship Working Committee meeting: . Start an every-other week WC meeting cadence beginning on August 26th . The last fifteen minutes of every WC meeting will be an "open forum" for non-WC members  . Proposal:  hold a special election for the fifth WC seat, three months after the first election, with a duration of 9 months . The WC will create a feedback survey to gather input on Airship community pain points and opportunities . Nishant will host IRC meeting on the 20th, Kaspars on the 27th Full agenda and notes can be found here [1]. Thanks, Matt [1]: https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_airship-2Dwc-2Dmeeting-2D2019-2D08-2D19&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=fcOCENqZB3BkwHshiVtu5luV0p9xD8ecMhlucxaJYDs&s=9JkQuODSRdM0U946Uuy0p-Fm-1Su17dzxjmD5RtK_74&e= _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=fcOCENqZB3BkwHshiVtu5luV0p9xD8ecMhlucxaJYDs&s=l170SgRKGZTE38GSWfnB-_vSyxXXVcpiaCNbDoXdIVY&e= From MM9745 at att.com Mon Aug 26 19:47:10 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 26 Aug 2019 19:47:10 +0000 Subject: [Airship-discuss] Let's name the Airship GUI Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://github.com/SUSE/stratos 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://github.com/mattmceuen/stratos We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://review.opendev.org/#/c/673900/ - Use the https://github.com/mattmceuen/stratos repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt From mm621n at att.com Mon Aug 26 19:56:54 2019 From: mm621n at att.com (MUEEN, MUZAMMIL) Date: Mon, 26 Aug 2019 19:56:54 +0000 Subject: [Airship-discuss] Let's name the Airship GUI In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <57EAC2FD9780DD4CA3D0C854CC86914E0E6C9537@CAFRFD1MSGUSRID.ITServices.sbc.com> My suggestion for the GUI name is 'admiral'. Its nautical, it exhibits the central 'command' of the whole fleet, and everyone knows what it means. I think admiral conveys the functionality of GUI quite appropriately. Regards, Muzammil -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 26, 2019 12:47 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] Let's name the Airship GUI *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_SUSE_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=svXcmUZNX10JWfyS0-sVcQ&m=GNG2FdZzF7Ev9XtX0DF7c75Ic6jBmlv9cMHvJvUjPWk&s=g2vM0e4DYlz_hP9q_NavXp7OC0IWoUthMILPUMLe-Lw&e= 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=svXcmUZNX10JWfyS0-sVcQ&m=GNG2FdZzF7Ev9XtX0DF7c75Ic6jBmlv9cMHvJvUjPWk&s=aKzf2uAlEvwbagHIdInFbYW8oCnNZneNqusu3sMnxuo&e= We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_673900_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=svXcmUZNX10JWfyS0-sVcQ&m=GNG2FdZzF7Ev9XtX0DF7c75Ic6jBmlv9cMHvJvUjPWk&s=IuoaSZOXAoygEDTUJS4LjlxrUPmRGlO01jBgb4BTuGw&e= - Use the https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=svXcmUZNX10JWfyS0-sVcQ&m=GNG2FdZzF7Ev9XtX0DF7c75Ic6jBmlv9cMHvJvUjPWk&s=aKzf2uAlEvwbagHIdInFbYW8oCnNZneNqusu3sMnxuo&e= repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=svXcmUZNX10JWfyS0-sVcQ&m=GNG2FdZzF7Ev9XtX0DF7c75Ic6jBmlv9cMHvJvUjPWk&s=mhybUTF7jceavUB4nD8IWAwyhP-sMHfS5V9rz1qizOk&e= From nchase at mirantis.com Mon Aug 26 20:40:13 2019 From: nchase at mirantis.com (Nick Chase) Date: Mon, 26 Aug 2019 16:40:13 -0400 Subject: [Airship-discuss] AIAB and default backend - 404 Message-ID: I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get default backend - 404 Except for the Horizon endpoint, where I get nothing at all. I'm assuming this is a K8s issue, but I'm not sure where to look further. Any ideas? ---- Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Aug 26 22:30:12 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 26 Aug 2019 22:30:12 +0000 Subject: [Airship-discuss] Canceled: Airship - Open Design Call - Tuesdays Aug 27, 2019 Message-ID: REMINDER –Airship Design Call – Cancelled tomorrow Aug 27, 2019 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 -------------- next part -------------- An HTML attachment was scrubbed... URL: From CB371J at att.com Mon Aug 26 22:37:00 2019 From: CB371J at att.com (BILLOVITS, CYNTHIA) Date: Mon, 26 Aug 2019 22:37:00 +0000 Subject: [Airship-discuss] Let's name the Airship GUI Message-ID: <717F342B06057944B02D7F82AB16790247A218EA@MISOUT7MSGUSRDF.ITServices.sbc.com> How about ship-to-shore or ship2shore? ----- Forwarded Message ----- Date: Mon, 26 Aug 2019 19:47:10 +0000 From: "MCEUEN, MATT" To: "'airship-discuss at lists.airshipit.org'" Subject: [Airship-discuss] Let's name the Airship GUI Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A27955 at MOSTLS1MSGUSRFF.ITServices.sbc.com> Content-Type: text/plain; charset="us-ascii" Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_SUSE_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2IlypPsc9zvDX1uFXPu0EA&m=eqO1rbPthLoAmTXGSEI57vZozxYbBkgeiQsEYCJV1p0&s=bn2BhpcSRoQyOiHop0F3vB4xrcmbqZVlo8PZ4vItDmM&e= 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2IlypPsc9zvDX1uFXPu0EA&m=eqO1rbPthLoAmTXGSEI57vZozxYbBkgeiQsEYCJV1p0&s=CBv4x2GNVg9KYB08RXTAsvHcEbLGHBJlgokfpc_5SRo&e= We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_673900_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2IlypPsc9zvDX1uFXPu0EA&m=eqO1rbPthLoAmTXGSEI57vZozxYbBkgeiQsEYCJV1p0&s=XrsjpuO4Lfpy0Mwe-PTfg7gNEcf7VT9DKYZCCCp11Cw&e= - Use the https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2IlypPsc9zvDX1uFXPu0EA&m=eqO1rbPthLoAmTXGSEI57vZozxYbBkgeiQsEYCJV1p0&s=CBv4x2GNVg9KYB08RXTAsvHcEbLGHBJlgokfpc_5SRo&e= repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt From paye600 at gmail.com Tue Aug 27 05:59:19 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Tue, 27 Aug 2019 07:59:19 +0200 Subject: [Airship-discuss] Let's name the Airship GUI In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hello all, My suggestion is to leave existing name Airship Copilot, as it has been discussed and agreed previously in Airship GUI spec here [0]. [0] https://airship-specs.readthedocs.io/en/latest/specs/approved/airship_copilot_gui.html Best regards, — Roman Gorshunov > On 26 Aug 2019, at 21:47, MCEUEN, MATT wrote: > > Airship team, > > I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... > 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI > 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://github.com/SUSE/stratos > 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://github.com/mattmceuen/stratos > > We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! > > If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. > If there's no clear winner already, we can discuss & vote in the IRC meeting. > Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. > > Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: > - https://review.opendev.org/#/c/673900/ > - Use the https://github.com/mattmceuen/stratos repo as the upstream in the projects.yaml > - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "" > - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide > > If you'd like to volunteer please reply to the ML. > > Thanks! > Matt > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From paye600 at gmail.com Tue Aug 27 06:03:13 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Tue, 27 Aug 2019 08:03:13 +0200 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: Message-ID: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Hi Nick, Which script did you run and from which repo? I would start with checking logs and config of running ingress. Best regards, — Roman Gorshunov > On 26 Aug 2019, at 22:40, Nick Chase wrote: > > I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get > > default backend - 404 > > Except for the Horizon endpoint, where I get nothing at all. > > I'm assuming this is a K8s issue, but I'm not sure where to look further. > > Any ideas? > > ---- Nick > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From nchase at mirantis.com Tue Aug 27 13:51:48 2019 From: nchase at mirantis.com (Nick Chase) Date: Tue, 27 Aug 2019 09:51:48 -0400 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: I ran the airship-in-a-bottle.sh script from https://opendev.org/airship/airship-in-a-bottle. Is there another preferred way? I can try the Vagrantfile. I'll check out the logs. ---- Nick On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov wrote: > Hi Nick, > > Which script did you run and from which repo? > I would start with checking logs and config of running ingress. > > Best regards, > — > Roman Gorshunov > > > > On 26 Aug 2019, at 22:40, Nick Chase wrote: > > > > I'm pleased to say that I've successfully run the script to install > Airship in a Bottle -- or at least I think I did. When I try to access > most of the endpoints, I get > > > > default backend - 404 > > > > Except for the Horizon endpoint, where I get nothing at all. > > > > I'm assuming this is a K8s issue, but I'm not sure where to look further. > > > > Any ideas? > > > > ---- Nick > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From nchase at mirantis.com Tue Aug 27 13:56:41 2019 From: nchase at mirantis.com (Nick Chase) Date: Tue, 27 Aug 2019 09:56:41 -0400 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: OK, I feel ridiculous saying this, but I can't find the Ingress. I get plenty of output from kubectl get --all-namespaces ing but "no resources" from kubectl get ing ---- Nick On Tue, Aug 27, 2019 at 9:51 AM Nick Chase wrote: > I ran the airship-in-a-bottle.sh script from > https://opendev.org/airship/airship-in-a-bottle. Is there another > preferred way? I can try the Vagrantfile. > > I'll check out the logs. > > ---- Nick > > On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov wrote: > >> Hi Nick, >> >> Which script did you run and from which repo? >> I would start with checking logs and config of running ingress. >> >> Best regards, >> — >> Roman Gorshunov >> >> >> > On 26 Aug 2019, at 22:40, Nick Chase wrote: >> > >> > I'm pleased to say that I've successfully run the script to install >> Airship in a Bottle -- or at least I think I did. When I try to access >> most of the endpoints, I get >> > >> > default backend - 404 >> > >> > Except for the Horizon endpoint, where I get nothing at all. >> > >> > I'm assuming this is a K8s issue, but I'm not sure where to look >> further. >> > >> > Any ideas? >> > >> > ---- Nick >> > _______________________________________________ >> > Airship-discuss mailing list >> > Airship-discuss at lists.airshipit.org >> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Aug 27 20:11:57 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 27 Aug 2019 20:11:57 +0000 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: For Promenade: Nishant Kumar For Shipyard: Michael Beaver, Matt Carter In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. With the expanding breadth of Airship, as well as a small amount of attrition, I think there's great opportunity to add additional Core Reviewers in the near term. I'd encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. I'd also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don't need to elaborate on how much of Airship's success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From eli at mirantis.com Tue Aug 27 20:29:31 2019 From: eli at mirantis.com (Evgeny L) Date: Tue, 27 Aug 2019 13:29:31 -0700 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: +1 On Tue, Aug 27, 2019 at 1:12 PM MCEUEN, MATT wrote: > Airship team, > > > > Based on their record of quality code review and substantial/meaningful > code contributions to specific Airship projects, as well as on needs of the > community, I would like to nominate the following individuals as Airship > Core Reviewers: > > > > For Promenade: Nishant Kumar > > For Shipyard: Michael Beaver, Matt Carter > > > > In my opinion all of these folks have demonstrated their ability to > enhance these projects as well as guide the enhancements of others, helping > to ensure a high-quality Airship. > > > > Current Core Reviewers over these projects are invited to reply with a > +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three > candidates, otherwise please spell out votes individually for the > candidates. > > > > With the expanding breadth of Airship, as well as a small amount of > attrition, I think there’s great opportunity to add additional Core > Reviewers in the near term. I’d encourage anyone who is interested in > these responsibilities to continue to contribute meaningful reviews and > enhancements for their repositories. > > > > I’d also like to share that two key members of the Airship team, Scott > Hussey and Bryan Strassner, have decided to bow out of Airship Core > Reviewer responsibilities. I don’t need to elaborate on how much of > Airship’s success is owed to the efforts of these two, the technical and > community foundations that they laid, and to their continued > contributions! Luckily for us they remain key members of the Airship > community and trusted team members. > > > > Thanks, > > Matt > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanvanwyk at gmail.com Tue Aug 27 20:49:07 2019 From: ryanvanwyk at gmail.com (Ryan van Wyk) Date: Tue, 27 Aug 2019 16:49:07 -0400 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <926688A3-63CB-41EB-A38B-DA13940CE90E@gmail.com> +1 Thanks, Ryan van Wyk 312-860-0966 > On Aug 27, 2019, at 4:11 PM, MCEUEN, MATT wrote: > > Airship team, > > Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: > > For Promenade: Nishant Kumar > For Shipyard: Michael Beaver, Matt Carter > > In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. > > Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. > > With the expanding breadth of Airship, as well as a small amount of attrition, I think there’s great opportunity to add additional Core Reviewers in the near term. I’d encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. > > I’d also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don’t need to elaborate on how much of Airship’s success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. > > Thanks, > Matt > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From petebirley at googlemail.com Tue Aug 27 21:09:03 2019 From: petebirley at googlemail.com (Pete Birley) Date: Tue, 27 Aug 2019 16:09:03 -0500 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: +1 On Tue, Aug 27, 2019, 15:13 MCEUEN, MATT wrote: > Airship team, > > > > Based on their record of quality code review and substantial/meaningful > code contributions to specific Airship projects, as well as on needs of the > community, I would like to nominate the following individuals as Airship > Core Reviewers: > > > > For Promenade: Nishant Kumar > > For Shipyard: Michael Beaver, Matt Carter > > > > In my opinion all of these folks have demonstrated their ability to > enhance these projects as well as guide the enhancements of others, helping > to ensure a high-quality Airship. > > > > Current Core Reviewers over these projects are invited to reply with a > +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three > candidates, otherwise please spell out votes individually for the > candidates. > > > > With the expanding breadth of Airship, as well as a small amount of > attrition, I think there’s great opportunity to add additional Core > Reviewers in the near term. I’d encourage anyone who is interested in > these responsibilities to continue to contribute meaningful reviews and > enhancements for their repositories. > > > > I’d also like to share that two key members of the Airship team, Scott > Hussey and Bryan Strassner, have decided to bow out of Airship Core > Reviewer responsibilities. I don’t need to elaborate on how much of > Airship’s success is owed to the efforts of these two, the technical and > community foundations that they laid, and to their continued > contributions! Luckily for us they remain key members of the Airship > community and trusted team members. > > > > Thanks, > > Matt > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Tue Aug 27 23:15:15 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Tue, 27 Aug 2019 23:15:15 +0000 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D0D4@MOKSCY3MSGUSRGI.ITServices.sbc.com> +1 From: MCEUEN, MATT Sent: Tuesday, August 27, 2019 3:12 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: For Promenade: Nishant Kumar For Shipyard: Michael Beaver, Matt Carter In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. With the expanding breadth of Airship, as well as a small amount of attrition, I think there's great opportunity to add additional Core Reviewers in the near term. I'd encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. I'd also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don't need to elaborate on how much of Airship's success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Wed Aug 28 05:38:39 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 28 Aug 2019 07:38:39 +0200 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <72193421-BD05-42EC-B654-BF7FDFC047B6@gmail.com> +1 > On 27 Aug 2019, at 22:11, MCEUEN, MATT wrote: > > Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at openstack.org Wed Aug 28 06:16:50 2019 From: chris at openstack.org (Chris Hoge) Date: Tue, 27 Aug 2019 23:16:50 -0700 Subject: [Airship-discuss] Airship OSF August Sync Message-ID: <6356B7CA-FE0B-4696-BB06-1C32ECEE14E4@openstack.org> This Thursday, August 29 we will have a Foundation/Airship sync meeting. This will conform to the new proposed meeting schedule of sync during the monthly TC meeting, then a second afternoon meeting in the later half of the month. Airship OSF August Sync Scheduled: Aug 29, 2019 at 2:00 PM to 3:00 PM Location: https://zoom.us/j/132898992 Airship OSF Last Thursday Sync Meeting (2nd Thursday coincides with Airship TC Meeting) https://etherpad.openstack.org/p/2019_Airship_OSF_sync -------------- next part -------------- A non-text attachment was scrubbed... Name: airship.ics Type: text/calendar Size: 1362 bytes Desc: not available URL: From dukov at mirantis.com Wed Aug 28 06:55:47 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Wed, 28 Aug 2019 10:55:47 +0400 Subject: [Airship-discuss] Cloud init script generator for airshipctl Message-ID: Hello all, Since we a re moving to Ironic-based bare metal provisioning using metal3-io we need to implement solution for cloud-init script creation based on new document model. There is Golang library and cli tool [1] shared by Alan Meadows recently. We can leverage it in scope of airshipctl. Unfortunately it supports only Ubuntu, Debian, Centos, Fedora and Redhat. So I see 2 options here: 1. Use this library and try to contribute to it by adding more Linux distributions 2. Reimplement same approach as a part of airshipctl codebase What do you think? [1] https://github.com/moshloop/konfigadm -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kanwar.sbl at gmail.com Wed Aug 28 09:51:16 2019 From: kanwar.sbl at gmail.com (Kanwar Saad) Date: Wed, 28 Aug 2019 12:51:16 +0300 Subject: [Airship-discuss] Fw: Cloud init script generator for airshipctl In-Reply-To: References: Message-ID: Hi Dmitry, Airship will be using kubernetes cluster-api and cloud-init generation will be taken care by "Cluster api bootstrap provider kubeadm(CABPK)" and final specifics of cloud-init(like network config) for bare metal hosts will be provided by CAPI baremetal provider. So from the airship point of view cloud init generation is not our task. Br, Kanwar On Wed, Aug 28, 2019 at 12:42 PM Mael Kimmerlin wrote: > > > ------------------------------ > *From:* Dmitry Ukov > *Sent:* Wednesday, August 28, 2019 9:55 AM > *To:* airship-discuss at lists.airshipit.org < > airship-discuss at lists.airshipit.org> > *Subject:* [Airship-discuss] Cloud init script generator for airshipctl > > Hello all, > > Since we a re moving to Ironic-based bare metal provisioning using > metal3-io we need to implement solution for cloud-init script creation > based on new document model. > There is Golang library and cli tool [1] shared by Alan Meadows recently. > We can leverage it in scope of airshipctl. > Unfortunately it supports only Ubuntu, Debian, Centos, Fedora and Redhat. > So I see 2 options here: > > 1. Use this library and try to contribute to it by adding more Linux > distributions > 2. Reimplement same approach as a part of airshipctl codebase > > What do you think? > > [1] https://github.com/moshloop/konfigadm > > -- > Kind regards > Dmitry Ukov > Principal Deployment Engineer > Mirantis, Inc. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dukov at mirantis.com Wed Aug 28 09:59:10 2019 From: dukov at mirantis.com (Dmitry Ukov) Date: Wed, 28 Aug 2019 13:59:10 +0400 Subject: [Airship-discuss] Fw: Cloud init script generator for airshipctl In-Reply-To: References: Message-ID: Kanwar, that's excellent point but from bootstrap perspective there is no CABPK so far since there is no K8s. The only thing we have at the beginning of the deployment is LiveCD/LiveUSB image for ephemeral K8s cluster. Ephemeral cluster on this Live image should be deployed using the same mechanism as Target cluster for consistency sake. Therefore we need something that generate this cloud init script. That being said we can try to use CABPK Golang library for generating cloud-config. On Wed, Aug 28, 2019 at 1:51 PM Kanwar Saad wrote: > Hi Dmitry, > > Airship will be using kubernetes cluster-api and cloud-init generation > will be taken care by "Cluster api bootstrap provider kubeadm(CABPK)" and > final specifics of cloud-init(like network config) for bare metal hosts > will be provided by CAPI baremetal provider. So from the airship point of > view cloud init generation is not our task. > > Br, > Kanwar > > On Wed, Aug 28, 2019 at 12:42 PM Mael Kimmerlin > wrote: > >> >> >> ------------------------------ >> *From:* Dmitry Ukov >> *Sent:* Wednesday, August 28, 2019 9:55 AM >> *To:* airship-discuss at lists.airshipit.org < >> airship-discuss at lists.airshipit.org> >> *Subject:* [Airship-discuss] Cloud init script generator for airshipctl >> >> Hello all, >> >> Since we a re moving to Ironic-based bare metal provisioning using >> metal3-io we need to implement solution for cloud-init script creation >> based on new document model. >> There is Golang library and cli tool [1] shared by Alan Meadows recently. >> We can leverage it in scope of airshipctl. >> Unfortunately it supports only Ubuntu, Debian, Centos, Fedora and Redhat. >> So I see 2 options here: >> >> 1. Use this library and try to contribute to it by adding more Linux >> distributions >> 2. Reimplement same approach as a part of airshipctl codebase >> >> What do you think? >> >> [1] https://github.com/moshloop/konfigadm >> >> -- >> Kind regards >> Dmitry Ukov >> Principal Deployment Engineer >> Mirantis, Inc. >> >> -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nchase at mirantis.com Wed Aug 28 12:34:01 2019 From: nchase at mirantis.com (Nick Chase) Date: Wed, 28 Aug 2019 08:34:01 -0400 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: I found the problem. First off, I was citing the wrong repo. I actually was coming from https://opendev.org/airship/treasuremap/ Second, apparently the requirements cited for the machine are too small. The README says 4vCPU/20GB RAM/32GB but with that I was in a periodic crashloop for Postgres. GCE was suggesting I increase the machine to 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of drive space is used. With the bigger machine, everything deployed properly and seems to be running smoothly. ---- Nick On Tue, Aug 27, 2019 at 9:56 AM Nick Chase wrote: > OK, I feel ridiculous saying this, but I can't find the Ingress. I get > plenty of output from > > kubectl get --all-namespaces ing > > but "no resources" from > > kubectl get ing > > ---- Nick > > On Tue, Aug 27, 2019 at 9:51 AM Nick Chase wrote: > >> I ran the airship-in-a-bottle.sh script from >> https://opendev.org/airship/airship-in-a-bottle. Is there another >> preferred way? I can try the Vagrantfile. >> >> I'll check out the logs. >> >> ---- Nick >> >> On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov >> wrote: >> >>> Hi Nick, >>> >>> Which script did you run and from which repo? >>> I would start with checking logs and config of running ingress. >>> >>> Best regards, >>> — >>> Roman Gorshunov >>> >>> >>> > On 26 Aug 2019, at 22:40, Nick Chase wrote: >>> > >>> > I'm pleased to say that I've successfully run the script to install >>> Airship in a Bottle -- or at least I think I did. When I try to access >>> most of the endpoints, I get >>> > >>> > default backend - 404 >>> > >>> > Except for the Horizon endpoint, where I get nothing at all. >>> > >>> > I'm assuming this is a K8s issue, but I'm not sure where to look >>> further. >>> > >>> > Any ideas? >>> > >>> > ---- Nick >>> > _______________________________________________ >>> > Airship-discuss mailing list >>> > Airship-discuss at lists.airshipit.org >>> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>> >>> >>> _______________________________________________ >>> Airship-discuss mailing list >>> Airship-discuss at lists.airshipit.org >>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Aug 28 14:52:19 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 28 Aug 2019 14:52:19 +0000 Subject: [Airship-discuss] Canceled [sig][airship-ui] - Friday Aug 30th Message-ID: <4A328A0D-A31B-41C9-901D-E0FC314C652D@att.com> NEED TO Cancel this week’s meeting Many are off because of the US Holiday, and long weekend ahead. On Sept. 6 will continue with this Agenda. * Found a candidate for BAKE OFF against STRATOS § https://github.com/vmware/octant/ § LETS DO OUR DUE DILLIGENCE!!! * Announce Repo Name for Airship UI * Remember to vote on a name in the mailing list. * Airship Features for MVP Discussion Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rv6848 at att.com Wed Aug 28 14:59:51 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Wed, 28 Aug 2019 14:59:51 +0000 Subject: [Airship-discuss] Canceled [sig][airship-ui] - Friday Aug 30th In-Reply-To: <4A328A0D-A31B-41C9-901D-E0FC314C652D@att.com> References: <4A328A0D-A31B-41C9-901D-E0FC314C652D@att.com> Message-ID: <50C6B4CC-74EA-42E0-A317-5CA36289C8A3@att.com> Let’s make sure RBAC is a critical part of MVP. +1 for cockpit as the name. Ryan van Wyk Assistant Vice President (AVP) – Network Cloud Engineering C: 312-860-0966 rv6848 at att.com Assistant: Lisa Selsor | 314.450.2687 | ls2276 at att.com On Aug 28, 2019, at 10:54 AM, PACHECO, RODOLFO J > wrote: ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. NEED TO Cancel this week’s meeting Many are off because of the US Holiday, and long weekend ahead. On Sept. 6 will continue with this Agenda. * Found a candidate for BAKE OFF against STRATOS § https://github.com/vmware/octant/ § LETS DO OUR DUE DILLIGENCE!!! * Announce Repo Name for Airship UI * Remember to vote on a name in the mailing list. * Airship Features for MVP Discussion Regards Rodolfo Pacheco Home/Office 732 5337671 _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=CXUZ4nQ3OEMXP344JOLWVg&m=rvgxBm1FMXBqb254ETPKkOn7vlW4XVJFx4Wt1a1EjCs&s=yn7Eo3KlLaXDtj8yr3OO2-doZT0lfX0AdLlSjyfDOik&e= -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Wed Aug 28 15:24:26 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 28 Aug 2019 17:24:26 +0200 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: Very nice to hear that it worked, Nick. But sad to know that requirements have almost doubled - something for us to look at and thank you for the report. Regards, -- Roman Gorshunov On Wed, Aug 28, 2019 at 2:34 PM Nick Chase wrote: > > I found the problem. First off, I was citing the wrong repo. I actually was coming from https://opendev.org/airship/treasuremap/ > > Second, apparently the requirements cited for the machine are too small. The README says 4vCPU/20GB RAM/32GB but with that I was in a periodic crashloop for Postgres. GCE was suggesting I increase the machine to 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of drive space is used. > > With the bigger machine, everything deployed properly and seems to be running smoothly. > > ---- Nick > > On Tue, Aug 27, 2019 at 9:56 AM Nick Chase wrote: >> >> OK, I feel ridiculous saying this, but I can't find the Ingress. I get plenty of output from >> >> kubectl get --all-namespaces ing >> >> but "no resources" from >> >> kubectl get ing >> >> ---- Nick >> >> On Tue, Aug 27, 2019 at 9:51 AM Nick Chase wrote: >>> >>> I ran the airship-in-a-bottle.sh script from https://opendev.org/airship/airship-in-a-bottle. Is there another preferred way? I can try the Vagrantfile. >>> >>> I'll check out the logs. >>> >>> ---- Nick >>> >>> On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov wrote: >>>> >>>> Hi Nick, >>>> >>>> Which script did you run and from which repo? >>>> I would start with checking logs and config of running ingress. >>>> >>>> Best regards, >>>> — >>>> Roman Gorshunov >>>> >>>> >>>> > On 26 Aug 2019, at 22:40, Nick Chase wrote: >>>> > >>>> > I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get >>>> > >>>> > default backend - 404 >>>> > >>>> > Except for the Horizon endpoint, where I get nothing at all. >>>> > >>>> > I'm assuming this is a K8s issue, but I'm not sure where to look further. >>>> > >>>> > Any ideas? >>>> > >>>> > ---- Nick >>>> > _______________________________________________ >>>> > Airship-discuss mailing list >>>> > Airship-discuss at lists.airshipit.org >>>> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>>> >>>> >>>> _______________________________________________ >>>> Airship-discuss mailing list >>>> Airship-discuss at lists.airshipit.org >>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From am495p at att.com Wed Aug 28 15:27:59 2019 From: am495p at att.com (MAHMOUDI, AHMAD) Date: Wed, 28 Aug 2019 15:27:59 +0000 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D0D4@MOKSCY3MSGUSRGI.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D0D4@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: +1 From: SKELS, KASPARS Sent: Tuesday, August 27, 2019 6:15 PM To: 'airship-discuss at lists.airshipit.org' Cc: MCEUEN, MATT Subject: Re: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. +1 From: MCEUEN, MATT > Sent: Tuesday, August 27, 2019 3:12 PM To: 'airship-discuss at lists.airshipit.org' > Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: For Promenade: Nishant Kumar For Shipyard: Michael Beaver, Matt Carter In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. With the expanding breadth of Airship, as well as a small amount of attrition, I think there's great opportunity to add additional Core Reviewers in the near term. I'd encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. I'd also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don't need to elaborate on how much of Airship's success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Wed Aug 28 15:42:45 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Wed, 28 Aug 2019 15:42:45 +0000 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D805@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi Nick, this is great to hear! I would suggest to add documentation patchset to the AIAB readme to state minimal requirements for GCU in the AIAB! Kindly, Kaspars From: Nick Chase Sent: Wednesday, August 28, 2019 7:34 AM To: Roman Gorshunov Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] AIAB and default backend - 404 I found the problem. First off, I was citing the wrong repo. I actually was coming from https://opendev.org/airship/treasuremap/ Second, apparently the requirements cited for the machine are too small. The README says 4vCPU/20GB RAM/32GB but with that I was in a periodic crashloop for Postgres. GCE was suggesting I increase the machine to 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of drive space is used. With the bigger machine, everything deployed properly and seems to be running smoothly. ---- Nick On Tue, Aug 27, 2019 at 9:56 AM Nick Chase > wrote: OK, I feel ridiculous saying this, but I can't find the Ingress. I get plenty of output from kubectl get --all-namespaces ing but "no resources" from kubectl get ing ---- Nick On Tue, Aug 27, 2019 at 9:51 AM Nick Chase > wrote: I ran the airship-in-a-bottle.sh script from https://opendev.org/airship/airship-in-a-bottle. Is there another preferred way? I can try the Vagrantfile. I'll check out the logs. ---- Nick On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov > wrote: Hi Nick, Which script did you run and from which repo? I would start with checking logs and config of running ingress. Best regards, — Roman Gorshunov > On 26 Aug 2019, at 22:40, Nick Chase > wrote: > > I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get > > default backend - 404 > > Except for the Horizon endpoint, where I get nothing at all. > > I'm assuming this is a K8s issue, but I'm not sure where to look further. > > Any ideas? > > ---- Nick > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From nchase at mirantis.com Wed Aug 28 17:22:30 2019 From: nchase at mirantis.com (Nick Chase) Date: Wed, 28 Aug 2019 13:22:30 -0400 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D805@MOKSCY3MSGUSRGI.ITServices.sbc.com> References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> <2ADBF0C373B7E84E944B1E06D3CDDFC91E82D805@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: Will do. I'm seeing how low I can go and have it still work. Thanks! ---- Nick On Wed, Aug 28, 2019 at 11:43 AM SKELS, KASPARS wrote: > Hi Nick, this is great to hear! > > > > I would suggest to add documentation patchset to the AIAB readme to state > minimal requirements for GCU in the AIAB! > > > > Kindly, Kaspars > > > > > > *From:* Nick Chase > *Sent:* Wednesday, August 28, 2019 7:34 AM > *To:* Roman Gorshunov > *Cc:* airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] AIAB and default backend - 404 > > > > I found the problem. First off, I was citing the wrong repo. I actually > was coming from https:*//opendev.org/airship/treasuremap/* > > > > > Second, apparently the requirements cited for the machine are too small. > The README says 4vCPU/20GB RAM/32GB but with that I was in a periodic > crashloop for Postgres. GCE was suggesting I increase the machine to > 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of drive > space is used. > > > > With the bigger machine, everything deployed properly and seems to be > running smoothly. > > > > ---- Nick > > > > On Tue, Aug 27, 2019 at 9:56 AM Nick Chase wrote: > > OK, I feel ridiculous saying this, but I can't find the Ingress. I get > plenty of output from > > > > kubectl get --all-namespaces ing > > > > but "no resources" from > > > > kubectl get ing > > > > ---- Nick > > > > On Tue, Aug 27, 2019 at 9:51 AM Nick Chase wrote: > > I ran the airship-in-a-bottle.sh script from > https://opendev.org/airship/airship-in-a-bottle > . > Is there another preferred way? I can try the Vagrantfile. > > > > I'll check out the logs. > > > > ---- Nick > > > > On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov wrote: > > Hi Nick, > > Which script did you run and from which repo? > I would start with checking logs and config of running ingress. > > Best regards, > — > Roman Gorshunov > > > > On 26 Aug 2019, at 22:40, Nick Chase wrote: > > > > I'm pleased to say that I've successfully run the script to install > Airship in a Bottle -- or at least I think I did. When I try to access > most of the endpoints, I get > > > > default backend - 404 > > > > Except for the Horizon endpoint, where I get nothing at all. > > > > I'm assuming this is a K8s issue, but I'm not sure where to look further. > > > > Any ideas? > > > > ---- Nick > > _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss at lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nk613n at att.com Fri Aug 30 18:30:08 2019 From: nk613n at att.com (KUMAR, NISHANT) Date: Fri, 30 Aug 2019 18:30:08 +0000 Subject: [Airship-discuss] Let's name the Airship GUI In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A27955@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hello Everyone, This is a reminder to please vote or propose names for the "airshipui" project. So far we have the following names that have been proposed: 1. airshipui 2. stratos 3. admiral 4. ship-to-shore 5. Airship Copilot 6. crowsnest 7. masthead I have added these names to the meeting agenda [0] for the next irc meeting to be held on 09/03. We would be voting on the names during the meeting, If you can't make it to the meeting then please reply to this thread with your votes or suggest a name. You could also add your votes directly in the etherpad. Once the voting is completed we need to submit the PS for project creation. Please reply to this ML if you are interested in taking up that work. [0] https://etherpad.openstack.org/p/airship-meeting-2019-09-03 Regards, Nishant -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 26, 2019 2:47 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] Let's name the Airship GUI *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_SUSE_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=1lYApeS3F4_-BtMIxOEuvA&m=sXfbADu5ioXPNuDMWOhitC6Nr4Pk8WQC6QXkk4BUmnM&s=zEH71xKKrJUKZCZrIypvx1AOffGsb6gbYeMtYJYZ_o4&e= 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=1lYApeS3F4_-BtMIxOEuvA&m=sXfbADu5ioXPNuDMWOhitC6Nr4Pk8WQC6QXkk4BUmnM&s=93DdjvlEmLOMCKsKcfs_GvfIkRBMexLJRtD9yohA4FY&e= We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23_c_673900_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=1lYApeS3F4_-BtMIxOEuvA&m=sXfbADu5ioXPNuDMWOhitC6Nr4Pk8WQC6QXkk4BUmnM&s=6Pd5gtZhxVoPyYBoqLw3OIX01uReVpQo7xE8ay-6NYQ&e= - Use the https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_stratos&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=1lYApeS3F4_-BtMIxOEuvA&m=sXfbADu5ioXPNuDMWOhitC6Nr4Pk8WQC6QXkk4BUmnM&s=93DdjvlEmLOMCKsKcfs_GvfIkRBMexLJRtD9yohA4FY&e= repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=1lYApeS3F4_-BtMIxOEuvA&m=sXfbADu5ioXPNuDMWOhitC6Nr4Pk8WQC6QXkk4BUmnM&s=lHItsmUNHqHzp887wh9wGIDD3a-dKJ7bsXSds8BMSCw&e= From kennelson11 at gmail.com Sat Aug 24 03:47:07 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Sat, 24 Aug 2019 03:47:07 -0000 Subject: [Airship-discuss] PTG Attendance Message-ID: Hello Everyone! This is the list of groups that are plannning on attending the PTG. Thank you PTLs/Chairs/Leads that responded on time :) I hesitate to say it's the 'final' list since I had a few groups respond with a 'Maybe', but it's probably pretty close. Please also note that the tentative activities at the PTG vary by group. Some groups are planning on only doing onboarding for example. Without further ado, here is the list! Airship Auto-Scaling SIG Barbican Blazar CInder Cyborg Edge Computing Group Fenix First Contact SIG Gitea Glance Heat Horizon I18n Ironic K8s SIG Karbor Kata Containers Keystone Loci Manila Meta SIG Monasca Neutron Nova Octavia OpenStack Charms OpenStack Infra / OpenDev OpenStack TC Openstack-helm OpenStack Operators (Ops Docs SIG and Meetup group) Oslo Public Cloud SIG Quality Assurance Release Management Scientific SIG Self-healing SIG Storlets StoryBoard Swift Tacker StarlingX If your team is missing from the list, please let me know ASAP as we are starting to put together a draft schedule. -Kendall Nelson(diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From se136c at att.com Tue Aug 27 21:31:38 2019 From: se136c at att.com (EAGAN, SEAN) Date: Tue, 27 Aug 2019 21:31:38 -0000 Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A2BAF6@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <5B9C5644A0B2414E90A7F40249CF6A955EEEDC5E@MOSTLS1MSGUSRFA.ITServices.sbc.com> +1 Thanks, Sean Eagan ________________________________ From: MCEUEN, MATT Sent: Tuesday, August 27, 2019 3:11 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] Shipyard & Promenade Core Reviewer Nominations Airship team, Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: For Promenade: Nishant Kumar For Shipyard: Michael Beaver, Matt Carter In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. With the expanding breadth of Airship, as well as a small amount of attrition, I think there’s great opportunity to add additional Core Reviewers in the near term. I’d encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. I’d also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don’t need to elaborate on how much of Airship’s success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From nchase at mirantis.com Thu Aug 29 02:45:50 2019 From: nchase at mirantis.com (Nick Chase) Date: Thu, 29 Aug 2019 02:45:50 -0000 Subject: [Airship-discuss] AIAB and default backend - 404 In-Reply-To: References: <26DEA561-032C-4565-BACC-D67ECEB22FC7@gmail.com> Message-ID: OK, unfortunately I'm wrong, it does NOT work. :( Horizon does come up, and the sample instance is there, but the actual Airship URLs are still giving me the "default backend - 404" error. I found the following in the airflow-web container in the shipyard-api pod, which is in a crashloop: 2019-08-29 02:42:23,471 ERROR models.py:380:process_file models Failed to import: /usr/local/airflow/dags/redeploy_server.py Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/airflow/models.py", line 377, in process_file m = imp.load_source(mod_name, filepath) File "/usr/lib/python3.5/imp.py", line 172, in load_source module = _load(spec) File "", line 693, in _load File "", line 673, in _load_unlocked File "", line 665, in exec_module File "", line 222, in _call_with_frames_removed File "/usr/local/airflow/dags/redeploy_server.py", line 57, in targets=[BAREMETAL] File "/usr/local/airflow/dags/common_step_factory.py", line 171, in get_validate_site_design dag=self.dag) File "/usr/local/lib/python3.5/dist-packages/airflow/utils/db.py", line 74, in wrapper return func(*args, **kwargs) File "/usr/lib/python3.5/contextlib.py", line 66, in __exit__ next(self.gen) File "/usr/local/lib/python3.5/dist-packages/airflow/utils/db.py", line 45, in create_session session.commit() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 943, in commit self.transaction.commit() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 465, in commit self._assert_active(prepared_ok=True) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 276, in _assert_active % self._rollback_exception sqlalchemy.exc.InvalidRequestError: This Session's transaction has been rolled back due to a previous exception during flush. To begin a new transaction with this Session, first issue Session.rollback(). Original exception was: (psycopg2.OperationalError) could not connect to server: Connection refused Is the server running on host "postgresql.ucp.svc.cluster.local" (10.96.212.170) and accepting TCP/IP connections on port 5432? (Background on this error at: http://sqlalche.me/e/e3q8) 2019-08-29 02:42:23,507 ERROR models.py:380:process_file models Failed to import: /usr/local/airflow/dags/samples/airflow_task_state_operators.py Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/airflow/models.py", line 377, in process_file m = imp.load_source(mod_name, filepath) File "/usr/lib/python3.5/imp.py", line 172, in load_source module = _load(spec) File "", line 693, in _load File "", line 673, in _load_unlocked File "", line 665, in exec_module File "", line 222, in _call_with_frames_removed File "/usr/local/airflow/dags/samples/airflow_task_state_operators.py", line 19, in from airflow.operators import TaskStateOperator ImportError: cannot import name 'TaskStateOperator' /usr/local/lib/python3.5/dist-packages/psycopg2/__init__.py:144: UserWarning: The psycopg2 wheel package will be renamed from release 2.8; in order to keep installing from binary please use "pip install psycopg2-binary" instead. For details see: < http://initd.org/psycopg/docs/install.html#binary-install-from-pypi>. """) Traceback (most recent call last): File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 2158, in _wrap_pool_connect return fn() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 400, in connect return _ConnectionFairy._checkout(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 788, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 529, in checkout rec = pool._do_get() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 1193, in _do_get self._dec_overflow() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/langhelpers.py", line 66, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 249, in reraise raise value File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 1190, in _do_get return self._create_connection() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 347, in _create_connection return _ConnectionRecord(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 474, in __init__ self.__connect(first_connect_check=True) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 671, in __connect connection = pool._invoke_creator(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/strategies.py", line 106, in connect return dialect.connect(*cargs, **cparams) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/default.py", line 412, in connect return self.dbapi.connect(*cargs, **cparams) File "/usr/local/lib/python3.5/dist-packages/psycopg2/__init__.py", line 130, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) psycopg2.OperationalError: could not connect to server: Connection refused Is the server running on host "postgresql.ucp.svc.cluster.local" (10.96.212.170) and accepting TCP/IP connections on port 5432? The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/bin/airflow", line 32, in args.func(args) File "/usr/local/lib/python3.5/dist-packages/airflow/utils/cli.py", line 74, in wrapper return f(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/airflow/bin/cli.py", line 793, in webserver app = cached_app_rbac(conf) if settings.RBAC else cached_app(conf) File "/usr/local/lib/python3.5/dist-packages/airflow/www/app.py", line 187, in cached_app app = create_app(config, testing) File "/usr/local/lib/python3.5/dist-packages/airflow/www/app.py", line 72, in create_app from airflow.www import views File "/usr/local/lib/python3.5/dist-packages/airflow/www/views.py", line 2232, in class ChartModelView(wwwutils.DataProfilingMixin, AirflowModelView): File "/usr/local/lib/python3.5/dist-packages/airflow/www/views.py", line 2323, in ChartModelView 'conn_id': _connection_ids() File "/usr/local/lib/python3.5/dist-packages/airflow/utils/db.py", line 74, in wrapper return func(*args, **kwargs) File "/usr/local/lib/python3.5/dist-packages/airflow/www/views.py", line 2227, in _connection_ids .group_by(models.Connection.conn_id) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/query.py", line 2995, in __iter__ return self._execute_and_instances(context) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/query.py", line 3016, in _execute_and_instances close_with_result=True) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/query.py", line 3025, in _get_bind_args **kw File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/query.py", line 3007, in _connection_from_session conn = self.session.connection(**kw) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 1035, in connection execution_options=execution_options) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 1040, in _connection_for_bind engine, execution_options) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/orm/session.py", line 409, in _connection_for_bind conn = bind.contextual_connect() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 2123, in contextual_connect self._wrap_pool_connect(self.pool.connect, None), File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 2162, in _wrap_pool_connect e, dialect, self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 1476, in _handle_dbapi_exception_noconnection exc_info File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 265, in raise_from_cause reraise(type(exception), exception, tb=exc_tb, cause=cause) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 248, in reraise raise value.with_traceback(tb) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/base.py", line 2158, in _wrap_pool_connect return fn() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 400, in connect return _ConnectionFairy._checkout(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 788, in _checkout fairy = _ConnectionRecord.checkout(pool) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 529, in checkout rec = pool._do_get() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 1193, in _do_get self._dec_overflow() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/langhelpers.py", line 66, in __exit__ compat.reraise(exc_type, exc_value, exc_tb) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/util/compat.py", line 249, in reraise raise value File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 1190, in _do_get return self._create_connection() File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 347, in _create_connection return _ConnectionRecord(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 474, in __init__ self.__connect(first_connect_check=True) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/pool.py", line 671, in __connect connection = pool._invoke_creator(self) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/strategies.py", line 106, in connect return dialect.connect(*cargs, **cparams) File "/usr/local/lib/python3.5/dist-packages/sqlalchemy/engine/default.py", line 412, in connect return self.dbapi.connect(*cargs, **cparams) File "/usr/local/lib/python3.5/dist-packages/psycopg2/__init__.py", line 130, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) sqlalchemy.exc.OperationalError: (psycopg2.OperationalError) could not connect to server: Connection refused Is the server running on host "postgresql.ucp.svc.cluster.local" (10.96.212.170) and accepting TCP/IP connections on port 5432? (Background on this error at: http://sqlalche.me/e/e3q8) The postgresql pod appears to be running. Any thoughts? ---- Nick On Wed, Aug 28, 2019 at 11:32 AM Roman Gorshunov wrote: > Very nice to hear that it worked, Nick. > But sad to know that requirements have almost doubled - something for > us to look at and thank you for the report. > > Regards, > -- Roman Gorshunov > > On Wed, Aug 28, 2019 at 2:34 PM Nick Chase wrote: > > > > I found the problem. First off, I was citing the wrong repo. I > actually was coming from https://opendev.org/airship/treasuremap/ > > > > Second, apparently the requirements cited for the machine are too > small. The README says 4vCPU/20GB RAM/32GB but with that I was in a > periodic crashloop for Postgres. GCE was suggesting I increase the machine > to 8vCPU/48GB RAM. Ultimately I'm at 16vCPU/60GB RAM and about 32GB of > drive space is used. > > > > With the bigger machine, everything deployed properly and seems to be > running smoothly. > > > > ---- Nick > > > > On Tue, Aug 27, 2019 at 9:56 AM Nick Chase wrote: > >> > >> OK, I feel ridiculous saying this, but I can't find the Ingress. I get > plenty of output from > >> > >> kubectl get --all-namespaces ing > >> > >> but "no resources" from > >> > >> kubectl get ing > >> > >> ---- Nick > >> > >> On Tue, Aug 27, 2019 at 9:51 AM Nick Chase wrote: > >>> > >>> I ran the airship-in-a-bottle.sh script from > https://opendev.org/airship/airship-in-a-bottle. Is there another > preferred way? I can try the Vagrantfile. > >>> > >>> I'll check out the logs. > >>> > >>> ---- Nick > >>> > >>> On Tue, Aug 27, 2019 at 2:06 AM Roman Gorshunov > wrote: > >>>> > >>>> Hi Nick, > >>>> > >>>> Which script did you run and from which repo? > >>>> I would start with checking logs and config of running ingress. > >>>> > >>>> Best regards, > >>>> — > >>>> Roman Gorshunov > >>>> > >>>> > >>>> > On 26 Aug 2019, at 22:40, Nick Chase wrote: > >>>> > > >>>> > I'm pleased to say that I've successfully run the script to install > Airship in a Bottle -- or at least I think I did. When I try to access > most of the endpoints, I get > >>>> > > >>>> > default backend - 404 > >>>> > > >>>> > Except for the Horizon endpoint, where I get nothing at all. > >>>> > > >>>> > I'm assuming this is a K8s issue, but I'm not sure where to look > further. > >>>> > > >>>> > Any ideas? > >>>> > > >>>> > ---- Nick > >>>> > _______________________________________________ > >>>> > Airship-discuss mailing list > >>>> > Airship-discuss at lists.airshipit.org > >>>> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > >>>> > >>>> > >>>> _______________________________________________ > >>>> Airship-discuss mailing list > >>>> Airship-discuss at lists.airshipit.org > >>>> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From ajay.chhabria at spirent.com Mon Aug 12 19:35:16 2019 From: ajay.chhabria at spirent.com (Chhabria, Ajay) Date: Mon, 12 Aug 2019 19:35:16 -0000 Subject: [Airship-discuss] AIB installation issue Message-ID: Hi, I am trying to install airship in bottle and hitting an error at the following step. Please find the install logs file attached to this email and you will find the snippet at the end of it. Any help is appreciated. Please let me know if any further information is needed. Looking forward to hear back from the team. ################################################################################################################ Creating KeyPair + popd ~/deploy/treasuremap/tools/deployment/aiab + publish_horizon_dashboard + kubectl -n openstack expose service/horizon-int --type=NodePort --name=horizon-dashboard Error from server (NotFound): namespaces "openstack" not found + error 'publishing Horizon dashboard' + set +x Error when publishing Horizon dashboard. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy/treasuremap/../. This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. ################################################################################################################ root at master:~/deploy/treasuremap/tools/deployment/aiab# kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE default log-test-master-1565635735 0/1 Completed 0 29m default log-test-master-1565636918 0/1 Completed 0 9m default log-test-master-1565636942 0/1 Completed 0 9m kube-system airship-coredns-test 0/1 Completed 0 58m kube-system airship-haproxy-haproxy-test 0/1 Completed 0 57m kube-system airship-kubernetes-calico-etcd-etcd-test 0/1 Completed 0 59m kube-system airship-kubernetes-etcd-etcd-test 0/1 Completed 0 57m kube-system apiserver-key-rotate-77qqb 0/1 Completed 0 57m kube-system auxiliary-etcd-master 3/3 Running 0 1h kube-system calico-etcd-anchor-2lq6g 1/1 Running 0 1h kube-system calico-etcd-master 1/1 Running 0 59m kube-system calico-kube-controllers-74b4879ddd-26tx8 1/1 Running 0 59m kube-system calico-node-m682h 1/1 Running 0 59m kube-system calico-settings-vsxgg 0/1 Completed 0 59m kube-system coredns-559d468f6d-94hsx 1/1 Running 0 58m kube-system coredns-559d468f6d-hp7rg 1/1 Running 0 58m kube-system coredns-559d468f6d-p4qmd 1/1 Running 0 58m kube-system haproxy-anchor-m867h 1/1 Running 0 57m kube-system haproxy-master 1/1 Running 1 57m kube-system ingress-6b95789f8-qv66q 1/1 Running 0 55m kube-system ingress-error-pages-8689d4c48-zp7q9 1/1 Running 0 55m kube-system kubernetes-apiserver-anchor-kvmfh 1/1 Running 0 57m kube-system kubernetes-apiserver-master 1/1 Running 0 56m kube-system kubernetes-controller-manager-anchor-ts78n 1/1 Running 0 57m kube-system kubernetes-controller-manager-master 1/1 Running 3 57m kube-system kubernetes-etcd-anchor-4cs6d 1/1 Running 0 58m kube-system kubernetes-etcd-master 1/1 Running 0 57m kube-system kubernetes-proxy-gqwfl 1/1 Running 0 1h kube-system kubernetes-scheduler-anchor-tcvhj 1/1 Running 0 57m kube-system kubernetes-scheduler-master 1/1 Running 2 57m kube-system tiller-deploy-579c8b4f9b-cjvh9 1/1 Running 0 44m nfs nfs-provisioner-5767d6b9cc-drb67 1/1 Running 0 55m openstack airship-glance-test 0/1 Completed 0 7m openstack airship-keystone-test 0/1 Completed 0 11m openstack airship-neutron-test 0/1 PodInitializing 0 1m openstack airship-openstack-mariadb-test 0/1 Completed 0 15m openstack airship-openstack-memcached-memcached-f58bc754c-2r8qh 1/1 Running 0 13m openstack airship-openstack-rabbitmq-cluster-wait-xspdd 0/1 Completed 0 14m openstack airship-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 14m openstack airship-openstack-rabbitmq-rabbitmq-exporter-5dd6bd8647-gdhp6 1/1 Running 0 14m openstack airship-openstack-rabbitmq-test 0/1 Completed 0 13m openstack exporter-create-sql-user-c6njz 0/1 Completed 0 18m openstack glance-api-7c46597bc9-tdptb 1/1 Running 0 9m openstack glance-bootstrap-jcrw7 0/1 Completed 0 9m openstack glance-db-init-2mxz6 0/1 Completed 0 9m openstack glance-db-sync-d72ff 0/1 Completed 0 9m openstack glance-ks-endpoints-5x5mc 0/3 Completed 0 9m openstack glance-ks-service-v8d27 0/1 Completed 0 9m openstack glance-ks-user-k8s89 0/1 Completed 0 9m openstack glance-rabbit-init-wb2zx 0/1 Completed 0 9m openstack glance-storage-init-pkcww 0/1 Completed 0 9m openstack ingress-68d76b8cc5-99mh7 1/1 Running 0 18m openstack ingress-error-pages-65f4f88f5f-4bvpf 1/1 Running 0 18m openstack keystone-api-647f9b6bd-nmwrm 1/1 Running 0 13m openstack keystone-bootstrap-btp5v 0/1 Completed 0 13m openstack keystone-credential-setup-cdktn 0/1 Completed 0 13m openstack keystone-db-init-qhdwp 0/1 Completed 0 13m openstack keystone-db-sync-2k67j 0/1 Completed 0 13m openstack keystone-domain-manage-ldg77 0/1 Completed 0 13m openstack keystone-fernet-setup-c2pwb 0/1 Completed 0 13m openstack libvirt-libvirt-default-n6lzv 1/1 Running 0 6m openstack mariadb-ingress-557b64d876-kzcpq 1/1 Running 0 18m openstack mariadb-ingress-error-pages-74788d8b7c-6qtd7 1/1 Running 0 18m openstack mariadb-server-0 1/1 Running 0 18m openstack neutron-db-init-4zd2d 0/1 Completed 0 6m openstack neutron-db-sync-llg8m 0/1 Completed 0 6m openstack neutron-dhcp-agent-default-lffgd 1/1 Running 0 6m openstack neutron-ks-endpoints-t58pv 0/3 Completed 0 6m openstack neutron-ks-service-8sn8h 0/1 Completed 0 6m openstack neutron-ks-user-v4bm6 0/1 Completed 0 6m openstack neutron-l3-agent-default-wqvhk 1/1 Running 0 6m openstack neutron-metadata-agent-default-2lqps 1/1 Running 0 6m openstack neutron-ovs-agent-default-qlhtz 1/1 Running 0 6m openstack neutron-rabbit-init-cvnml 0/1 Completed 0 6m openstack neutron-server-7988fdc68-jnlrk 1/1 Running 0 6m openstack neutron-server-7988fdc68-n7rbh 1/1 Running 0 6m openstack nova-api-metadata-68d88697f6-lvld4 1/1 Running 0 6m openstack nova-api-osapi-795d45b75-s7j2g 1/1 Running 0 6m openstack nova-bootstrap-qbfdf 0/1 Completed 0 6m openstack nova-cell-setup-x6pjd 0/1 Init:0/2 0 6m openstack nova-compute-default-9jfzn 0/1 Running 0 6m openstack nova-conductor-7f94bd8bb9-lvt4b 0/1 Running 0 6m openstack nova-consoleauth-59684768df-r4fvq 0/1 Running 0 6m openstack nova-db-init-np8kb 0/3 Completed 0 6m openstack nova-db-sync-mbmcl 0/1 Completed 0 6m openstack nova-ks-endpoints-2vj6d 0/3 Completed 0 6m openstack nova-ks-service-77nqq 0/1 Completed 0 6m openstack nova-ks-user-rwz6n 0/1 Completed 0 6m openstack nova-novncproxy-76df4f685f-fm7lp 0/1 Init:2/3 0 6m openstack nova-placement-api-77f8dcb59b-qs8mv 1/1 Running 0 6m openstack nova-rabbit-init-84plp 0/1 Completed 0 6m openstack nova-scheduler-759b9765c7-jzvcj 0/1 Running 0 6m openstack openvswitch-db-d4j9f 1/1 Running 0 6m openstack openvswitch-vswitchd-6vbcx 1/1 Running 0 6m openstack placement-ks-endpoints-lmt8v 0/3 Completed 0 6m openstack placement-ks-service-2sz2w 0/1 Completed 0 6m openstack placement-ks-user-zqfwv 0/1 Completed 0 6m openstack prometheus-mysql-exporter-84d99848bd-4fbdd 1/1 Running 0 18m ucp airflow-db-init-rwfns 0/1 Completed 0 32m ucp airflow-db-sync-6jc79 0/1 Completed 0 32m ucp airflow-rabbit-init-j9l25 0/1 Completed 0 32m ucp airflow-scheduler-6779bf76c4-hg85f 1/1 Running 0 32m ucp airflow-worker-0 3/3 Running 0 32m ucp airship-drydock-api-test 0/1 Completed 0 37m ucp airship-drydock-auth-test 0/1 Completed 0 37m ucp airship-maas-api-test 0/1 Completed 0 19m ucp airship-ucp-armada-armada-api-test 0/1 Completed 0 43m ucp airship-ucp-barbican-test 0/1 Completed 0 42m ucp airship-ucp-deckhand-deckhand-api-test 0/1 Completed 0 41m ucp airship-ucp-keystone-memcached-memcached-5857498fdf-7rxh4 1/1 Running 0 49m ucp airship-ucp-keystone-test 0/1 Completed 0 47m ucp airship-ucp-mariadb-test 0/1 Completed 0 51m ucp airship-ucp-promenade-api-test 0/1 Completed 0 32m ucp airship-ucp-rabbitmq-cluster-wait-85xvt 0/1 Completed 0 54m ucp airship-ucp-rabbitmq-rabbitmq-0 1/1 Running 0 54m ucp airship-ucp-rabbitmq-rabbitmq-exporter-6777747ccb-vhccb 1/1 Running 0 54m ucp airship-ucp-rabbitmq-test 0/1 Completed 0 53m ucp airship-ucp-shipyard-shipyard-api-test 0/1 Completed 0 29m ucp armada-api-74df6754b7-xngbd 2/2 Running 0 44m ucp armada-ks-endpoints-bpmgj 0/3 Completed 0 44m ucp armada-ks-service-7t72q 0/1 Completed 0 44m ucp armada-ks-user-vj5f9 0/1 Completed 0 44m ucp barbican-api-7d56457598-hwczl 1/1 Running 0 43m ucp barbican-db-init-xh4px 0/1 Completed 0 43m ucp barbican-db-sync-54tlh 0/1 Completed 0 43m ucp barbican-ks-endpoints-tv5hc 0/3 Completed 0 43m ucp barbican-ks-service-4k2lg 0/1 Completed 0 43m ucp barbican-ks-user-chknz 0/1 Completed 0 43m ucp barbican-rabbit-init-k9jth 0/1 Completed 0 43m ucp deckhand-api-5fd595d687-shmvs 1/1 Running 0 43m ucp deckhand-db-init-wrwkp 0/1 Completed 0 43m ucp deckhand-db-sync-6m2f5 0/1 Completed 0 43m ucp deckhand-ks-endpoints-8qz66 0/3 Completed 0 43m ucp deckhand-ks-service-4nwkr 0/1 Completed 0 43m ucp deckhand-ks-user-wmmx2 0/1 Completed 0 43m ucp divingbell-apt-default-5ckwf 1/1 Running 0 44m ucp divingbell-exec-default-m4pg5 1/1 Running 0 44m ucp drydock-api-7dc9bfc74c-s7dfl 1/1 Running 0 41m ucp drydock-db-init-r6psq 0/1 Completed 0 41m ucp drydock-db-sync-j27xg 0/1 Completed 0 41m ucp drydock-ks-endpoints-f7qdl 0/3 Completed 0 41m ucp drydock-ks-service-5sbl6 0/1 Completed 0 41m ucp drydock-ks-user-hmbbw 0/1 Completed 0 41m ucp ingress-69d8678658-bbct4 1/1 Running 0 54m ucp ingress-error-pages-cf9f484fd-f44hv 1/1 Running 0 54m ucp keystone-api-55b65f9795-2svn8 1/1 Running 0 49m ucp keystone-bootstrap-4w7vp 0/1 Completed 0 49m ucp keystone-credential-setup-pgcsv 0/1 Completed 0 49m ucp keystone-db-init-s62bd 0/1 Completed 0 49m ucp keystone-db-sync-j52cc 0/1 Completed 0 49m ucp keystone-domain-manage-9wx7w 0/1 Completed 0 49m ucp keystone-fernet-setup-b7v26 0/1 Completed 0 49m ucp keystone-rabbit-init-5g2kc 0/1 Completed 0 49m ucp maas-bootstrap-admin-user-t2mt2 0/1 Completed 0 20m ucp maas-bootstrap-admin-user-z4zk9 0/1 Completed 0 41m ucp maas-db-init-9f4pf 0/1 Completed 0 20m ucp maas-db-init-bw8nt 0/1 Completed 0 41m ucp maas-db-sync-mbswj 0/1 Completed 0 41m ucp maas-db-sync-st98r 0/1 Completed 0 20m ucp maas-export-api-key-n4bkp 0/1 Completed 0 41m ucp maas-export-api-key-zqck7 0/1 Completed 0 20m ucp maas-import-resources-c96tk 0/1 Completed 0 41m ucp maas-import-resources-x927n 0/1 Completed 0 20m ucp maas-ingress-errors-5bd84f86df-7pm85 1/1 Running 0 41m ucp maas-rack-0 1/1 Running 0 41m ucp maas-region-0 2/2 Running 0 41m ucp mariadb-ingress-65c4d459c9-fpgcj 1/1 Running 0 54m ucp mariadb-ingress-error-pages-5bf58fc7f8-4bc2t 1/1 Running 0 54m ucp mariadb-server-0 1/1 Running 0 54m ucp postgresql-0 1/1 Running 0 54m ucp promenade-api-7fcc7987b9-5dgl9 1/1 Running 0 32m ucp promenade-ks-endpoints-6gnx2 0/3 Completed 0 32m ucp promenade-ks-service-sdgcg 0/1 Completed 0 32m ucp promenade-ks-user-9wm2w 0/1 Completed 0 32m ucp shipyard-api-685bb866f4-srtpt 2/2 Running 0 32m ucp shipyard-db-auxiliary-lmtwg 0/1 Completed 0 32m ucp shipyard-db-init-l4wb4 0/1 Completed 0 32m ucp shipyard-db-sync-59svl 0/1 Completed 0 32m ucp shipyard-ks-endpoints-ml9r8 0/3 Completed 0 32m ucp shipyard-ks-service-52zwl 0/1 Completed 0 32m ucp shipyard-ks-user-vwvc4 0/1 Completed 0 32m Thanks and Regards, Ajay Chhabria Technical Marketing Engineer T: 408-752-7368 | M: 408-797-7485 ajay.chhabria at spirent.com | www.spirent.com 2708 Orchard Parkway, Suite 20, San Jose, CA 95134 [Spirent] [Spirent] [Spirent] [Spirent] [Spirent] Spirent Communications e-mail confidentiality. This email and the information contained therein may contain private, confidential or privileged material solely meant for the intended recipient. If you are not the intended recipient review, copying or distribution is forbidden. Further, if you are not the intended recipient, please contact the sender immediately and permanently delete this email and any copies or attachments. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.gif Type: image/gif Size: 1905 bytes Desc: image001.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.gif Type: image/gif Size: 1880 bytes Desc: image002.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.gif Type: image/gif Size: 1962 bytes Desc: image003.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.gif Type: image/gif Size: 1832 bytes Desc: image004.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.gif Type: image/gif Size: 5356 bytes Desc: image005.gif URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: install_logs Type: application/octet-stream Size: 1086020 bytes Desc: install_logs URL: From cloud24x7 at ieee.org Thu Aug 22 11:04:11 2019 From: cloud24x7 at ieee.org (Prakash Ramchandran) Date: Thu, 22 Aug 2019 11:04:11 -0000 Subject: [Airship-discuss] [aiship-discuss][airchipctl] Development Testing Backend options Message-ID: Hi all, Do you see these as possible options for Airshipctl code testing for backends Option 1: Call airshipctl commands from cmd to pass on to metal3 to execute through cloud controller and corresponding plugins. Option 2: Call airshipctl commands to by pass metal3 and call directly go-wrapped (sushy client) or Redfish APIs (URL) for BareMetal testing. 2.a Use real Redfish standard APIs (code reference- > ? 2.b Use fake calls to vBMC to enable emulated/simulated testing including libvirt calls and using oslo/openstack SDK tools -> 2.c Use Docker container as was suggested in the bootstrap SIG today same as an 2.b but use containers. Refer: Outrechy Summary Based on this link: Q1. Are we using tox for test framework? Q2. Is py3 the way to us (latest py3.6 is used in sushy & suhsy-tools? Q3. If we use go are we still planning to use standard sushy-tools and then is that call using URL to a daemon (Redfish or IPMI in a Docker container as suggested by bootstrap SIG call today?) Welcome to help us with your expertise in shaping the Airshipctl Development/Testing Thanks Prakash -------------- next part -------------- An HTML attachment was scrubbed... URL: From julien.bertozzi at intl.att.com Tue Aug 13 14:20:33 2019 From: julien.bertozzi at intl.att.com (Bertozzi, Julien) Date: Tue, 13 Aug 2019 14:20:33 -0000 Subject: [Airship-discuss] AIB install issue In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A0C4F5@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970A0C4F5@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hello Matt ! Well, as per recommendation on the aiab site, I always wipe between tries. I've had it a few times before posting to the ML. I retried now that I got your message (same image on the same usb key, same machine). Only difference that shouldn't affect anything is that I let it upgrade during install instead of doing it after the install Anyway, it seems to work, I got my k8s env 😊 Helm wasn't working properly though, it didn't created it's files. Doing a new `helm init` didn't fixed. Although it said the files were created, well, they were nowhere to be found Onto the next step Thanks for your time, J -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 12, 2019 4:07 PM To: Bertozzi, Julien ; 'airship-discuss at lists.airshipit.org' Subject: RE: AIB install issue Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN ; airship-discuss at lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e= From julien.bertozzi at intl.att.com Fri Aug 16 13:53:20 2019 From: julien.bertozzi at intl.att.com (Bertozzi, Julien) Date: Fri, 16 Aug 2019 13:53:20 -0000 Subject: [Airship-discuss] AIB install issue In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A0CD90@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A0881F@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970A0C4F5@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970A0CD90@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hello Matt ! Clarification: At installed, when asked if it could install upgrades, I said yes this time. I'm not sure that it changed anything but that's the only thing I can think of As for the helm issue, it was a pretty unexpected behavior, none of us encountered this before. Next time I'll see if I can give you access to the vm Thanks for your time ! Julien -----Original Message----- From: MCEUEN, MATT Sent: Tuesday, August 13, 2019 6:00 PM To: Bertozzi, Julien ; 'airship-discuss at lists.airshipit.org' ; PARK, HYON H Subject: RE: AIB install issue Hey Julien, Happy to hear of progress! Can you please clarify this one: "I let it upgrade during install instead of doing it after the install" -- do you mean that you did some of the steps here [1] in parallel? I learned yesterday that Hyon Park is getting the same error when running AIAB, consistently (just like you were), and I'm not sure what the common thread is yet. He was running in a VM on a public cloud on an Ubuntu 16.04 host. I'm not able to reproduce the issue, but I suspect there may be a common thread between your old environment and his current one. I'm also interested in your new issue. AIAB should be pretty turn-key, installing its own dependencies, etc! [1]: https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab -----Original Message----- From: BERTOZZI, JULIEN Sent: Tuesday, August 13, 2019 9:20 AM To: MCEUEN, MATT ; 'airship-discuss at lists.airshipit.org' Subject: RE: AIB install issue Hello Matt ! Well, as per recommendation on the aiab site, I always wipe between tries. I've had it a few times before posting to the ML. I retried now that I got your message (same image on the same usb key, same machine). Only difference that shouldn't affect anything is that I let it upgrade during install instead of doing it after the install Anyway, it seems to work, I got my k8s env 😊 Helm wasn't working properly though, it didn't created it's files. Doing a new `helm init` didn't fixed. Although it said the files were created, well, they were nowhere to be found Onto the next step Thanks for your time, J -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 12, 2019 4:07 PM To: Bertozzi, Julien ; 'airship-discuss at lists.airshipit.org' Subject: RE: AIB install issue Hi Julien, just wanted to confirm whether you're still seeing this issue? Thanks Matt -----Original Message----- From: MCEUEN, MATT Sent: Monday, August 5, 2019 1:45 PM To: BERTOZZI, JULIEN ; airship-discuss at lists.airshipit.org Subject: RE: AIB install issue Hi Julien, sorry for the delay. The "Unable to connect to server" messages are referring to the kubernetes apiserver being unreachable, and from your logs, it looks like the apiserver failed to start up with the error "failed to listen on 0.0.0.0:6444: listen tcp 0.0.0.0:6444: bind: address already in use". Is the issue reproducible, or did you just hit it the one time? If reproducible, can you confirm whether anything is listening on port 6444 prior to running the AIAB script? Thanks, Matt -----Original Message----- From: BERTOZZI, JULIEN Sent: Thursday, July 18, 2019 4:07 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] AIB install issue *** Security Advisory: This Message Originated Outside of AT&T ***. Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_JulienBe_airship-2Din-2Da-2Dbottle-2Dtesting&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=4PFygK135CuVlwdFm5y3c1kN-8p786y6mSWfEpqp6wE&e= Does it ring a bell for anyone ? Thanks for your time, Julien _______________________________________________ Airship-discuss mailing list Airship-discuss at 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=if7XuYhdAb5Dh3Yfbh7Ktwk7jjwAfCFuOTjJaXwGBZ8&s=W_MUU5RD5NVllVkZUHLiT5EG-BZvQGizNKrqS4zyCMI&e=