From jimmy at openstack.org Tue Sep 1 15:07:25 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 1 Sep 2020 10:07:25 -0500 Subject: [Airship-discuss] 2020 Virtual Summit: Forum Submissions Now Accepted Message-ID: <65B34330-0DA1-4A6F-8C1B-A6D1D353B18B@getmailspring.com> Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport at openstack.org. Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Sep 4 14:22:15 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 4 Sep 2020 14:22:15 +0000 Subject: [Airship-discuss] [sig][ui] Meetings cadence and discussions Message-ID: <716A12BC-4B21-40B6-B42F-F0EE3B590E53@att.com> All, Meeting Cadence: We are not going to be having meeting’s for the rest of the year on Friday’s. No more explicit SIG UI meetings for the rest of 2020. Starting today. The meeting is canceled. Regarding Design Discussions : We will bring the sig ui topics that need to be discussed into the Tuesday/Thursday Design Meetings given that most of the participants of the sig attend those as well. Regarding Scope and Issues: We will incorporate discussion about the issues on the Flight Plan meetings on Wednesday’s. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mjhooker at gmail.com Sat Sep 5 20:07:21 2020 From: mjhooker at gmail.com (Matthew Hooker) Date: Sat, 5 Sep 2020 21:07:21 +0100 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Message-ID: Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Wed Sep 9 15:00:33 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 9 Sep 2020 10:00:33 -0500 Subject: [Airship-discuss] Schedule is Live for the 2020 Virtual Open Infrastructure Summit Message-ID: <7B553231-9B05-4D97-8587-2E58581E8966@openstack.org> Hi everyone, We are excited to announce that the schedule for the virtual 2020 Open Infrastructure Summit is now live featuring keynotes and sessions from users like Volvo, Workday, Société Générale and Ant Group. View the schedule for the 2020 virtual Open Infrastructure Summit The virtual event takes place October 19-23 and includes more than 100 sessions and thousands of attendees are expected to participate, representing 30+ open source communities from more than 100 countries. Sessions for the virtual summit are led by users from global enterprises and research institutions building and operating open infrastructure at scale. The Summit includes: Sessions spanning 30+ open source projects from technical community leaders and organizations including Alibaba Cloud, AT&T, China Mobile, CERN, European Weather Cloud, GE Digital and Volvo Cars and many more. Collaborative sessions with project leaders and open source communities, including Airship, Ansible, Ceph, Docker, Kata Containers, Kubernetes, ONAP, OpenStack, Open vSwitch, OPNFV, StarlingX, and Zuul. Get hands on workshops around open source technologies directly from the developers and operators building the software. Familiarize with the updated Certified OpenStack Administrator (COA) exam and test your OpenStack knowledge at the COA sessions, sponsored by the OpenStack Foundation, in collaboration with Mirantis. Now what? Register for your free virtual Summit pass and meet the users, developers, and vendors who are building and operating open infrastructure on October 19-23! Thank you to our Summit Headline, Premier and Exhibitor sponsors: Huawei, Cisco, InMotion Hosting, Trilio and ZTE. Event sponsors gain visibility with a wide array of open source infrastructure developers, operators and decision makers. Download the Open Infrastructure Summit sponsor prospectus for more information. Questions? Reach out to summit at openstack.org “See you” in October! Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Sep 9 18:28:35 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 9 Sep 2020 11:28:35 -0700 Subject: [Airship-discuss] vPTG October 2020 Team Signup Reminder In-Reply-To: <7177465D-7A62-4AC7-BEFC-CFA475695428@openstack.org> References: <7177465D-7A62-4AC7-BEFC-CFA475695428@openstack.org> Message-ID: Hello Everyone! This is your final reminder! You have until *September 11th at 7:00 UTC to sign up your team for the PTG! You must complete **BOTH** the survey[1] AND reserve time in the ethercalc[2] to sign up your team. * And don't forget to register! [3] - TheKendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb [3] PTG Registration: https://october2020ptg.eventbrite.com On Mon, Aug 31, 2020 at 10:41 AM Kendall Waters wrote: > Hello Everyone! > > Wanted to give you all a reminder that the deadline for signing up teams > for the PTG is approaching! > > The virtual PTG will be held from Monday October 26th to Friday October > 30th, 2020. > > *To signup your team, you must complete **BOTH** the survey[1] AND > reserve time in the ethercalc[2] by September 11th at 7:00 UTC.* > > We ask that the PTL/SIG Chair/Team lead sign up for time to have their > discussions in with 4 rules/guidelines. > > 1. Cross project discussions (like SIGs or support project teams) should > be scheduled towards the start of the week so that any discussions that > might shape those of other teams happen first. > 2. No team should sign up for more than 4 hours per UTC day to help keep > participants actively engaged. > 3. No team should sign up for more than 16 hours across all time slots to > avoid burning out our contributors and to enable participation in multiple > teams discussions. > > Once your team is signed up, please register[3]! And remind your team to > register! Registration is free, but since it will be how we contact you > with passwords, event details, etc. it is still important! > > If you have any questions, please let us know. > > -The Kendalls (diablo_rojo & wendallkaters) > > [1] Team Survey: > https://openstackfoundation.formstack.com/forms/oct2020_vptg_survey > [2] Ethercalc Signup: https://ethercalc.openstack.org/7xp2pcbh1ncb > [3] PTG Registration: https://october2020ptg.eventbrite.com > > > > _______________________________________________ > 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 jimmy at openstack.org Wed Sep 9 22:54:52 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 9 Sep 2020 17:54:52 -0500 Subject: [Airship-discuss] REMINDER: 2020 Virtual Summit: Forum Submissions Now Accepted In-Reply-To: <65B34330-0DA1-4A6F-8C1B-A6D1D353B18B@getmailspring.com> References: <65B34330-0DA1-4A6F-8C1B-A6D1D353B18B@getmailspring.com> Message-ID: Hello Everyone! We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Virtual Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. The timeline for submissions is as follows: Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Sept 28th | Forum schedule final Oct 19th | Forum begins! If you have questions or concerns, please reach out to speakersupport at openstack.org (mailto:speakersupport at openstack.org). Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/2020/ [3] https://cfp.openstack.org [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 On Sep 1 2020, at 10:07 am, Jimmy McArthur wrote: > Hello Everyone! > > We are now accepting Forum [1] submissions for the 2020 Virtual Open Infrastructure Summit [2]. Please submit your ideas through the Summit CFP tool [3] through September 14th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. > > This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. > > The timeline for submissions is as follows: > > Aug 31st | Formal topic submission tool opens: https://cfp.openstack.org. > Sep 14th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. > Sep 21st | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. > Sept 28th | Forum schedule final > Oct 19th | Forum begins! > > If you have questions or concerns, please reach out to speakersupport at openstack.org. > > Cheers, > Jimmy > > [1] https://wiki.openstack.org/wiki/Forum > [2] https://www.openstack.org/summit/2020/ > [3] https://cfp.openstack.org > [4]https://wiki.openstack.org/wiki/Forum/Virtual2020 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Sep 9 23:01:47 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 9 Sep 2020 23:01:47 +0000 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff In-Reply-To: References: Message-ID: <003adccb63a741c6983ca0a7f8eac0bc@att.com> Hi Matthew, We are able to reproduce the issue, and have a fix that should be merged in the next couple hours. Can you please give it another try and see if you still have any issues? Sorry for the inconvenience! Matt From: Matthew Hooker Sent: Saturday, September 5, 2020 3:07 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Sep 10 19:50:20 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 10 Sep 2020 19:50:20 +0000 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff In-Reply-To: <85c766e7adb041fba680d8ee948fccbf@att.com> References: <003adccb63a741c6983ca0a7f8eac0bc@att.com> <85c766e7adb041fba680d8ee948fccbf@att.com> Message-ID: +Sreejith & Siraj – could you please take a look at Ben’s error below? From: JAYARAJ, BEN Sent: Thursday, September 10, 2020 2:40 PM To: MCEUEN, MATT Cc: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org; Matthew Hooker Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Matt, I have seen the same error shown below (CrashLoopBackOff) yesterday when I was trying the deploy. Today we tried the deploy with your suggestions - we got the error shown below at the end of install. Just a thought - Should we have run swapoff -a before the script begins. (WARNING: No swap limit – in the error message below) Thanks Ben 0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>Thu Sep 10 13:25:35 CDT 2020 API not returning node list before timeout.<br>Thu Sep 10 13:25:35 CDT 2020 General docker state report<br>Containers: 0<br> Running: 0<br> Paused: 0<br> Stopped: 0<br>Images: 3<br>Server Version: 18.06.3-ce<br>Storage Driver: overlay2<br> Backing Filesystem: extfs<br> Supports d_type: true<br> Native Overlay Diff: true<br>Logging Driver: json-file<br>Cgroup Driver: cgroupfs<br>Plugins:<br> Volume: local<br> Network: bridge host macvlan null overlay<br> Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog<br>Swarm: inactive<br>Runtimes: runc<br>Default Runtime: runc<br>Init Binary: docker-init<br>containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e<br>runc version: a592beb5bc4c4092b1b1bac971afed27687340c5<br>init version: fec3683<br>Security Options:<br> apparmor<br> seccomp<br> Profile: default<br>Kernel Version: 4.4.0-186-generic<br>Operating System: Ubuntu 16.04.7 LTS<br>OSType: linux<br>Architecture: x86_64<br>CPUs: 16<br>Total Memory: 31.42GiB<br>Name: tma-airship<br>ID: 4MOE:NJSF:L37S:ACYI:DNPJ:77BR:IFFL:L77C:6JXB:ZYEE:SVC2:2DUO<br>Docker Root Dir: var/lib/docker<br>Debug Mode (client): false<br>Debug Mode (server): false<br>Registry: https://index.docker.io/v1<br>Labels:<br>Experimental: false<br>Insecure Registries:<br> 127.0.0.0/8<br>Live Restore Enabled: true<br><br>WARNING: No swap limit support<br>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br>Thu Sep 10 13:25:35 CDT 2020 General cluster state report<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>+ error 'running genesis'<br>+ set +x<br>Error when running genesis.<br>+ exit 1<br>+ clean<br>+ set +x<br>To remove files generated during this script's execution, delete /root/deploy/treasuremap/../.<br>This VM is disposable. Re-deployment in this same VM will lead to unpredictable results.<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port? Thanks Ben From: MCEUEN, MATT > Sent: Wednesday, September 9, 2020 7:02 PM To: Matthew Hooker > Cc: BOSE, ARIJIT >; airship-discuss at lists.airshipit.org; JAYARAJ, BEN > Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi Matthew, We are able to reproduce the issue, and have a fix that should be merged in the next couple hours. Can you please give it another try and see if you still have any issues? Sorry for the inconvenience! Matt From: Matthew Hooker > Sent: Saturday, September 5, 2020 3:07 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From bj2343 at att.com Thu Sep 10 19:39:58 2020 From: bj2343 at att.com (JAYARAJ, BEN) Date: Thu, 10 Sep 2020 19:39:58 +0000 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff In-Reply-To: <003adccb63a741c6983ca0a7f8eac0bc@att.com> References: <003adccb63a741c6983ca0a7f8eac0bc@att.com> Message-ID: <85c766e7adb041fba680d8ee948fccbf@att.com> Matt, I have seen the same error shown below (CrashLoopBackOff) yesterday when I was trying the deploy. Today we tried the deploy with your suggestions - we got the error shown below at the end of install. Just a thought - Should we have run swapoff -a before the script begins. (WARNING: No swap limit – in the error message below) Thanks Ben 0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>Thu Sep 10 13:25:35 CDT 2020 API not returning node list before timeout.<br>Thu Sep 10 13:25:35 CDT 2020 General docker state report<br>Containers: 0<br> Running: 0<br> Paused: 0<br> Stopped: 0<br>Images: 3<br>Server Version: 18.06.3-ce<br>Storage Driver: overlay2<br> Backing Filesystem: extfs<br> Supports d_type: true<br> Native Overlay Diff: true<br>Logging Driver: json-file<br>Cgroup Driver: cgroupfs<br>Plugins:<br> Volume: local<br> Network: bridge host macvlan null overlay<br> Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog<br>Swarm: inactive<br>Runtimes: runc<br>Default Runtime: runc<br>Init Binary: docker-init<br>containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e<br>runc version: a592beb5bc4c4092b1b1bac971afed27687340c5<br>init version: fec3683<br>Security Options:<br> apparmor<br> seccomp<br> Profile: default<br>Kernel Version: 4.4.0-186-generic<br>Operating System: Ubuntu 16.04.7 LTS<br>OSType: linux<br>Architecture: x86_64<br>CPUs: 16<br>Total Memory: 31.42GiB<br>Name: tma-airship<br>ID: 4MOE:NJSF:L37S:ACYI:DNPJ:77BR:IFFL:L77C:6JXB:ZYEE:SVC2:2DUO<br>Docker Root Dir: var/lib/docker<br>Debug Mode (client): false<br>Debug Mode (server): false<br>Registry: https://index.docker.io/v1<br>Labels:<br>Experimental: false<br>Insecure Registries:<br> 127.0.0.0/8<br>Live Restore Enabled: true<br><br>WARNING: No swap limit support<br>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br>Thu Sep 10 13:25:35 CDT 2020 General cluster state report<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>+ error 'running genesis'<br>+ set +x<br>Error when running genesis.<br>+ exit 1<br>+ clean<br>+ set +x<br>To remove files generated during this script's execution, delete /root/deploy/treasuremap/../.<br>This VM is disposable. Re-deployment in this same VM will lead to unpredictable results.<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port? Thanks Ben From: MCEUEN, MATT Sent: Wednesday, September 9, 2020 7:02 PM To: Matthew Hooker Cc: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org; JAYARAJ, BEN Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi Matthew, We are able to reproduce the issue, and have a fix that should be merged in the next couple hours. Can you please give it another try and see if you still have any issues? Sorry for the inconvenience! Matt From: Matthew Hooker > Sent: Saturday, September 5, 2020 3:07 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From ab7180 at att.com Thu Sep 10 19:55:30 2020 From: ab7180 at att.com (BOSE, ARIJIT) Date: Thu, 10 Sep 2020 19:55:30 +0000 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff In-Reply-To: References: <003adccb63a741c6983ca0a7f8eac0bc@att.com> <85c766e7adb041fba680d8ee948fccbf@att.com> Message-ID: <0bbebf837f704082af5ace32f37ce70b@att.com> Hello Ben, Can you please share the testing environment details. The crashloop issue was resolved and we had a issue with the etcd server. This is the fix for it was pushed last night : https://review.opendev.org/#/c/750866/ I had two success runs last night with this PS. Request you to test it on a fresh 16.04 vm and getting the PS pulled in. In case the problem persists , please share the “docker ps -a “. BR, Arijit Bose From: MCEUEN, MATT Sent: Thursday, September 10, 2020 2:50 PM To: JAYARAJ, BEN ; YASIN, SIRAJUDEEN MOHAMMED ; PUNNAPUZHA, SREEJITH Cc: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org; Matthew Hooker ; BAILEY, ALEXANDER Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff +Sreejith & Siraj – could you please take a look at Ben’s error below? From: JAYARAJ, BEN Sent: Thursday, September 10, 2020 2:40 PM To: MCEUEN, MATT Cc: BOSE, ARIJIT ; airship-discuss at lists.airshipit.org; Matthew Hooker Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Matt, I have seen the same error shown below (CrashLoopBackOff) yesterday when I was trying the deploy. Today we tried the deploy with your suggestions - we got the error shown below at the end of install. Just a thought - Should we have run swapoff -a before the script begins. (WARNING: No swap limit – in the error message below) Thanks Ben 0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>Thu Sep 10 13:25:35 CDT 2020 API not returning node list before timeout.<br>Thu Sep 10 13:25:35 CDT 2020 General docker state report<br>Containers: 0<br> Running: 0<br> Paused: 0<br> Stopped: 0<br>Images: 3<br>Server Version: 18.06.3-ce<br>Storage Driver: overlay2<br> Backing Filesystem: extfs<br> Supports d_type: true<br> Native Overlay Diff: true<br>Logging Driver: json-file<br>Cgroup Driver: cgroupfs<br>Plugins:<br> Volume: local<br> Network: bridge host macvlan null overlay<br> Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog<br>Swarm: inactive<br>Runtimes: runc<br>Default Runtime: runc<br>Init Binary: docker-init<br>containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e<br>runc version: a592beb5bc4c4092b1b1bac971afed27687340c5<br>init version: fec3683<br>Security Options:<br> apparmor<br> seccomp<br> Profile: default<br>Kernel Version: 4.4.0-186-generic<br>Operating System: Ubuntu 16.04.7 LTS<br>OSType: linux<br>Architecture: x86_64<br>CPUs: 16<br>Total Memory: 31.42GiB<br>Name: tma-airship<br>ID: 4MOE:NJSF:L37S:ACYI:DNPJ:77BR:IFFL:L77C:6JXB:ZYEE:SVC2:2DUO<br>Docker Root Dir: var/lib/docker<br>Debug Mode (client): false<br>Debug Mode (server): false<br>Registry: https://index.docker.io/v1<br>Labels:<br>Experimental: false<br>Insecure Registries:<br> 127.0.0.0/8<br>Live Restore Enabled: true<br><br>WARNING: No swap limit support<br>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br>Thu Sep 10 13:25:35 CDT 2020 General cluster state report<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>+ error 'running genesis'<br>+ set +x<br>Error when running genesis.<br>+ exit 1<br>+ clean<br>+ set +x<br>To remove files generated during this script's execution, delete /root/deploy/treasuremap/../.<br>This VM is disposable. Re-deployment in this same VM will lead to unpredictable results.<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port? Thanks Ben From: MCEUEN, MATT > Sent: Wednesday, September 9, 2020 7:02 PM To: Matthew Hooker > Cc: BOSE, ARIJIT >; airship-discuss at lists.airshipit.org; JAYARAJ, BEN > Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi Matthew, We are able to reproduce the issue, and have a fix that should be merged in the next couple hours. Can you please give it another try and see if you still have any issues? Sorry for the inconvenience! Matt From: Matthew Hooker > Sent: Saturday, September 5, 2020 3:07 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From bj2343 at att.com Thu Sep 10 20:12:02 2020 From: bj2343 at att.com (JAYARAJ, BEN) Date: Thu, 10 Sep 2020 20:12:02 +0000 Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff In-Reply-To: <0bbebf837f704082af5ace32f37ce70b@att.com> References: <003adccb63a741c6983ca0a7f8eac0bc@att.com> <85c766e7adb041fba680d8ee948fccbf@att.com> <0bbebf837f704082af5ace32f37ce70b@att.com> Message-ID: Hi Arijit The VM is running Ubuntu 16.04.07. The VM has 32 GB ram, 100GB storage, 8vCPU. The error shown below is what is showing up today at the end of the install. This is running in an VMWare ESXI Server. Ben From: BOSE, ARIJIT Sent: Thursday, September 10, 2020 3:56 PM To: MCEUEN, MATT ; JAYARAJ, BEN ; YASIN, SIRAJUDEEN MOHAMMED ; PUNNAPUZHA, SREEJITH Cc: airship-discuss at lists.airshipit.org; Matthew Hooker ; BAILEY, ALEXANDER Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hello Ben, Can you please share the testing environment details. The crashloop issue was resolved and we had a issue with the etcd server. This is the fix for it was pushed last night : https://review.opendev.org/#/c/750866/ I had two success runs last night with this PS. Request you to test it on a fresh 16.04 vm and getting the PS pulled in. In case the problem persists , please share the “docker ps -a “. BR, Arijit Bose From: MCEUEN, MATT > Sent: Thursday, September 10, 2020 2:50 PM To: JAYARAJ, BEN >; YASIN, SIRAJUDEEN MOHAMMED >; PUNNAPUZHA, SREEJITH > Cc: BOSE, ARIJIT >; airship-discuss at lists.airshipit.org; Matthew Hooker >; BAILEY, ALEXANDER > Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff +Sreejith & Siraj – could you please take a look at Ben’s error below? From: JAYARAJ, BEN > Sent: Thursday, September 10, 2020 2:40 PM To: MCEUEN, MATT > Cc: BOSE, ARIJIT >; airship-discuss at lists.airshipit.org; Matthew Hooker > Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Matt, I have seen the same error shown below (CrashLoopBackOff) yesterday when I was trying the deploy. Today we tried the deploy with your suggestions - we got the error shown below at the end of install. Just a thought - Should we have run swapoff -a before the script begins. (WARNING: No swap limit – in the error message below) Thanks Ben 0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>.The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>Thu Sep 10 13:25:35 CDT 2020 API not returning node list before timeout.<br>Thu Sep 10 13:25:35 CDT 2020 General docker state report<br>Containers: 0<br> Running: 0<br> Paused: 0<br> Stopped: 0<br>Images: 3<br>Server Version: 18.06.3-ce<br>Storage Driver: overlay2<br> Backing Filesystem: extfs<br> Supports d_type: true<br> Native Overlay Diff: true<br>Logging Driver: json-file<br>Cgroup Driver: cgroupfs<br>Plugins:<br> Volume: local<br> Network: bridge host macvlan null overlay<br> Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog<br>Swarm: inactive<br>Runtimes: runc<br>Default Runtime: runc<br>Init Binary: docker-init<br>containerd version: 468a545b9edcd5932818eb9de8e72413e616e86e<br>runc version: a592beb5bc4c4092b1b1bac971afed27687340c5<br>init version: fec3683<br>Security Options:<br> apparmor<br> seccomp<br> Profile: default<br>Kernel Version: 4.4.0-186-generic<br>Operating System: Ubuntu 16.04.7 LTS<br>OSType: linux<br>Architecture: x86_64<br>CPUs: 16<br>Total Memory: 31.42GiB<br>Name: tma-airship<br>ID: 4MOE:NJSF:L37S:ACYI:DNPJ:77BR:IFFL:L77C:6JXB:ZYEE:SVC2:2DUO<br>Docker Root Dir: var/lib/docker<br>Debug Mode (client): false<br>Debug Mode (server): false<br>Registry: https://index.docker.io/v1<br>Labels:<br>Experimental: false<br>Insecure Registries:<br> 127.0.0.0/8<br>Live Restore Enabled: true<br><br>WARNING: No swap limit support<br>CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES<br>Thu Sep 10 13:25:35 CDT 2020 General cluster state report<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>The connection to the server 127.0.0.1:6553 was refused - did you specify the right host or port?<br>+ error 'running genesis'<br>+ set +x<br>Error when running genesis.<br>+ exit 1<br>+ clean<br>+ set +x<br>To remove files generated during this script's execution, delete /root/deploy/treasuremap/../.<br>This VM is disposable. Re-deployment in this same VM will lead to unpredictable results.<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port?<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab#<br>root at tma-airship:~/deploy/treasuremap/tools/deployment/aiab# kubectl get namespaces<br>The connection to the server localhost:8080 was refused - did you specify the right host or port? Thanks Ben From: MCEUEN, MATT > Sent: Wednesday, September 9, 2020 7:02 PM To: Matthew Hooker > Cc: BOSE, ARIJIT >; airship-discuss at lists.airshipit.org; JAYARAJ, BEN > Subject: RE: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi Matthew, We are able to reproduce the issue, and have a fix that should be merged in the next couple hours. Can you please give it another try and see if you still have any issues? Sorry for the inconvenience! Matt From: Matthew Hooker > Sent: Saturday, September 5, 2020 3:07 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship in a Bottle - CrashLoopBackOff Hi, I've tried getting AiaB working several times on various machines but always end up with this: NAMESPACE NAME READY STATUS RESTARTS AGE kube-system auxiliary-etcd-ubuntu 3/3 Running 0 13h kube-system bootstrap-armada-ubuntu 4/4 Running 0 13h kube-system haproxy-ubuntu 1/1 Running 0 13h kube-system kubernetes-apiserver-ubuntu 1/1 Running 1 13h kube-system kubernetes-controller-manager-ubuntu 1/1 Running 0 13h kube-system kubernetes-etcd-ubuntu 1/1 Running 0 13h kube-system kubernetes-proxy-f279z 0/1 Pending 0 2m32s kube-system kubernetes-scheduler-ubuntu 0/1 CrashLoopBackOff 167 13h This may be easily solvable by someone with sufficient knowledge of the underlying systems but I'm stuck. Full transcript here: https://drive.google.com/file/d/10l1hrtRNEMA0OYujk2V9sRILazQ2wZeq/view Any help appreciated Matthew -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Mon Sep 14 19:06:37 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 14 Sep 2020 19:06:37 +0000 Subject: [Airship-discuss] Design Call - Tuesday Sep 15, 2020 - Cancelled Message-ID: <6AE9445A-388E-4F5A-A16B-9346B6BDBDD6@att.com> Folks I am out of the office tomorrow Need to cancel the call. Will move etherpad items to the Thursday call. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Sep 14 22:05:40 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 14 Sep 2020 22:05:40 +0000 Subject: [Airship-discuss] Cancelled: IRC (8/31) and WC (9/8) meetings In-Reply-To: <2a6b68d5ffd74a12a6074862dbd642d1@att.com> References: <2a6b68d5ffd74a12a6074862dbd642d1@att.com> Message-ID: <986c800531514e16be8b832cc026eb34@att.com> Team, Tomorrow's IRC team meeting is cancelled. Please add any discussion topics to the agenda for the next meeting, on September 29th: https://etherpad.opendev.org/p/airship-team-meeting Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Thu Sep 17 17:13:29 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Thu, 17 Sep 2020 12:13:29 -0500 Subject: [Airship-discuss] Open Infrastructure Summit Airship 101 Content Message-ID: <08572669-0EA3-4C66-9D75-497568049B0A@openstack.org> Hi everyone, I mentioned on recent call that we were planning on having a “101”/Overview session of each OSF project during the virtual Summit. Below are some details around suggested content, recording and submission deadlines, etc. Is anyone available to help pull together this content? Two people is an option as well if anyone wants to tag-team. Let me know if you have any questions! Thanks, Ashlee — This session can be up to 25 minutes long, but we think around 15 minutes will be the most digestible for viewers. If the presenter or someone else from the Airship community is able to be online when the recording shows, we recommend utilizing the remainder of the time for Q&A with attendees in the virtual event platform chat for your session (for a total time of 30 minutes). Please read through slides 1-6 before you begin recording. We recommend using Zoom if possible. For the Airship Overview content, we’re hoping for it to be relatively beginner oriented. Some things you'll probably want to include are: Explain what the project is Where it fits in the software stack Open source projects it integrates with Tools used to contribute/where to find us online How it follows the 4 Opens We’ll share more details on how to submit your recording soon, but please plan on having it ready by October 1. — Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Sep 17 17:27:47 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 17 Sep 2020 17:27:47 +0000 Subject: [Airship-discuss] Open Infrastructure Summit Airship 101 Content In-Reply-To: <08572669-0EA3-4C66-9D75-497568049B0A@openstack.org> References: <08572669-0EA3-4C66-9D75-497568049B0A@openstack.org> Message-ID: Hi Ashlee, I can work on this. If anyone would like to collaborate, please let me know! Thanks, Matt From: Ashlee Ferguson Sent: Thursday, September 17, 2020 12:13 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Open Infrastructure Summit Airship 101 Content Hi everyone, I mentioned on recent call that we were planning on having a “101”/Overview session of each OSF project during the virtual Summit. Below are some details around suggested content, recording and submission deadlines, etc. Is anyone available to help pull together this content? Two people is an option as well if anyone wants to tag-team. Let me know if you have any questions! Thanks, Ashlee — This session can be up to 25 minutes long, but we think around 15 minutes will be the most digestible for viewers. If the presenter or someone else from the Airship community is able to be online when the recording shows, we recommend utilizing the remainder of the time for Q&A with attendees in the virtual event platform chat for your session (for a total time of 30 minutes). Please read through slides 1-6 before you begin recording. We recommend using Zoom if possible. For the Airship Overview content, we’re hoping for it to be relatively beginner oriented. Some things you'll probably want to include are: * Explain what the project is * Where it fits in the software stack * Open source projects it integrates with * Tools used to contribute/where to find us online * How it follows the 4 Opens We’ll share more details on how to submit your recording soon, but please plan on having it ready by October 1. — Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Thu Sep 17 18:50:18 2020 From: amy at demarco.com (Amy Marrich) Date: Thu, 17 Sep 2020 13:50:18 -0500 Subject: [Airship-discuss] [Diversity] Diversity & Inclusion WG Meeting 9/21 - Removing Divisive Language Message-ID: The Diversity and Inclusion WG will be holding a meeting to continue drafting the OSF's stance on the removal of Divisive Language within the OSF projects. The WG invites members of all OSF projects to participate in this effort and to join us at our next meeting Monday, September 21, at 17:00 UTC which will be held at https://meetpad.opendev.org/osf-diversity-and-inclusion. Drafts for the stance can be found at https://etherpad.opendev.org/p/divisivelanguage If you have any questions please let me and the team know here, on #openstack-diversity on IRC, or you can email me directly. Thanks, Amy Marrich (spotz) -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Mon Sep 21 18:35:54 2020 From: amy at demarco.com (Amy Marrich) Date: Mon, 21 Sep 2020 13:35:54 -0500 Subject: [Airship-discuss] [Diversity] Community feedback on Divisive Language stance Message-ID: The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Sep 21 22:18:00 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 21 Sep 2020 15:18:00 -0700 Subject: [Airship-discuss] Fwd: Forum schedule is now LIVE! In-Reply-To: References: Message-ID: Hello Everyone! The forum schedule is now live: https://www.openstack.org/summit/2020/summit-schedule/global-search?t=forum Please let myself or Jimmy McArthur know as soon as possible if you see any conflicts. Speakers will be contacted shortly (if not already) with more details about the event and your sessions. Thanks! -Kendall Nelson (diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Wed Sep 23 16:09:03 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 23 Sep 2020 11:09:03 -0500 Subject: [Airship-discuss] Community voting for the 2020 Open Infrastructure Summit Superuser Awards is now open! Message-ID: Hi everyone, It’s time for the community to help determine the winner of the 2020 Open Infrastructure Summit Superuser Awards. The Superuser Editorial Advisory Board will review the nominees and determine the finalists and overall winner after the community has had a chance to review and rate nominees. Now, it’s your turn. Review the nominees and rate them before the deadline September 28 at 11:59 p.m. PDT . Make sure to check out the SK Telecom 5GX Labs nomination highlighting their Airship use case! Share your top pick for the Superuser Awards on Twitter , Facebook , and LinkedIn with #OpenInfraSummit. Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Sep 28 23:44:12 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 28 Sep 2020 23:44:12 +0000 Subject: [Airship-discuss] Airship IRC/Slack team meeting 9/29 Message-ID: Team, We are on for tomorrow's team meeting! The agenda can be found here; please add anything else you'd like to bring up. https://etherpad.opendev.org/p/airship-team-meeting Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From bob.monkman at intel.com Tue Sep 29 22:09:02 2020 From: bob.monkman at intel.com (Monkman, Bob) Date: Tue, 29 Sep 2020 22:09:02 +0000 Subject: [Airship-discuss] [Diversity] Community feedback on Divisive Language stance In-Reply-To: References: Message-ID: Amy, et al, Thanks for sharing this and I think Draft 5 seems like a good statement to build from. I am working on a Linux Foundation Networking (LFN) task force looking at this issue for the projects under that umbrella. As a part of that process, on our wiki page for this task force, we have compiled some links and a table of example recommended replacement terms that could be of interest to your OSF work as well. Please see this reference at https://wiki.lfnetworking.org/display/LN/Inclusive+Language+Initiative If this is of interest. Best regards, Bob Monkman LFN Contributor, Strategic Planning Committee member, Marketing Chair CNTT/OPNFV From: Amy Marrich Sent: Monday, September 21, 2020 11:36 AM To: starlingx-discuss at lists.starlingx.io; airship-discuss at lists.airshipit.org; kata-dev at lists.katacontainers.io; zuul-discuss at lists.zuul-ci.org; openstack-discuss ; foundation at lists.openstack.org Subject: [Airship-discuss] [Diversity] Community feedback on Divisive Language stance The OSF Diversity & Inclusion WG has been working on creating the OSF's stance concerning divisive language. We will be holding one more meeting before sending the stance to the OSF Board for any changes before bringing it back to the Community. Our goal however is to get your input now to reduce any concerns in the future! Please check out Draft 4 on the etherpad[0] and place your comments there and join us on October 5th (meeting information will be sent out closer to the meeting) Thanks, Amy (spotz) 0 - https://etherpad.opendev.org/p/divisivelanguage -------------- next part -------------- An HTML attachment was scrubbed... URL: From amy at demarco.com Tue Sep 29 22:21:46 2020 From: amy at demarco.com (Amy Marrich) Date: Tue, 29 Sep 2020 17:21:46 -0500 Subject: [Airship-discuss] [Diversity] Community feedback on Divisive Language stance In-Reply-To: References: Message-ID: Bob, Thanks for the feedback and the link. At this time we're leaving the new wording to the individual projects vs saying all OSF projects must use Y instead of X. In part it's because projects have found that words have different meanings in the context of where they're located within their code, at least in the case of blacklist/whitelist. Ultimately we're hoping to have a list of suggested replacements but realize what may work for one project may not for another. Thanks again! Amy Marrich (spotz) On Tue, Sep 29, 2020 at 5:09 PM Monkman, Bob wrote: > Amy, et al, > > Thanks for sharing this and I think Draft 5 seems like a > good statement to build from. I am working on a Linux Foundation Networking > (LFN) task force looking at this issue for the projects under that > umbrella. > > As a part of that process, on our wiki page for this task > force, we have compiled some links and a table of example recommended > replacement terms that could be of interest to your OSF work as well. > > Please see this reference at > https://wiki.lfnetworking.org/display/LN/Inclusive+Language+Initiative > > If this is of interest. > > Best regards, > > Bob Monkman > > LFN Contributor, Strategic Planning Committee member, Marketing Chair > CNTT/OPNFV > > > > > > > > *From:* Amy Marrich > *Sent:* Monday, September 21, 2020 11:36 AM > *To:* starlingx-discuss at lists.starlingx.io; > airship-discuss at lists.airshipit.org; kata-dev at lists.katacontainers.io; > zuul-discuss at lists.zuul-ci.org; openstack-discuss < > openstack-discuss at lists.openstack.org>; foundation at lists.openstack.org > *Subject:* [Airship-discuss] [Diversity] Community feedback on Divisive > Language stance > > > > The OSF Diversity & Inclusion WG has been working on creating the OSF's > stance concerning divisive language. We will be holding one more meeting > before sending the stance to the OSF Board for any changes before bringing > it back to the Community. > > > > Our goal however is to get your input now to reduce any concerns in the > future! Please check out Draft 4 on the etherpad[0] and place your comments > there and join us on October 5th (meeting information will be sent out > closer to the meeting) > > > > Thanks, > > > > Amy (spotz) > > 0 - https://etherpad.opendev.org/p/divisivelanguage > -------------- next part -------------- An HTML attachment was scrubbed... URL: