From rp2723 at att.com Thu Jan 2 15:38:15 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 2 Jan 2020 15:38:15 +0000 Subject: [Airship-discuss] Airship - Community Design Call Message-ID: <99088997CCAD0C4BA20008FD094344963C4D0CCE@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Occurs every Thursday from 11:00 AM to 12:00 PM effective 1/9/2020. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/meet/rp2723 *~*~*~*~*~*~*~*~*~* Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Airship Repositories * https://opendev.org/airship/airshipctl * https://opendev.org/airship/go-redfish * https://opendev.org/airship/zuul-airship-roles * https://opendev.org/airship/apis * https://opendev.org/airship/images __________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2518 bytes Desc: not available URL: From rp2723 at att.com Thu Jan 2 15:38:15 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 2 Jan 2020 15:38:15 +0000 Subject: [Airship-discuss] Canceled: Airship - Community Design Call Message-ID: <99088997CCAD0C4BA20008FD094344963C4D0CC3@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Thursday, January 09, 2020 11:00 AM-12:00 PM. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/meet/rp2723 *~*~*~*~*~*~*~*~*~* Join us to continue Airship 2.0 Design discussions in 2020. 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2170 bytes Desc: not available URL: From rp2723 at att.com Thu Jan 2 15:38:19 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 2 Jan 2020 15:38:19 +0000 Subject: [Airship-discuss] Airship - Community Design Call Message-ID: <99088997CCAD0C4BA20008FD094344963C4D0CF3@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Occurs every Tuesday from 9:00 AM to 10:00 AM effective 1/7/2020. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/meet/rp2723 *~*~*~*~*~*~*~*~*~* Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Airship Repositories * https://opendev.org/airship/airshipctl * https://opendev.org/airship/go-redfish * https://opendev.org/airship/zuul-airship-roles * https://opendev.org/airship/apis * https://opendev.org/airship/images __________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2601 bytes Desc: not available URL: From rp2723 at att.com Thu Jan 2 15:45:14 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 2 Jan 2020 15:45:14 +0000 Subject: [Airship-discuss] Airship - Community Design Call Message-ID: <220DC9DB-44DB-45EC-AE75-645DB16E3B08@att.com> Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Airship Repositories * https://opendev.org/airship/airshipctl * https://opendev.org/airship/go-redfish * https://opendev.org/airship/zuul-airship-roles * https://opendev.org/airship/apis * https://opendev.org/airship/images __________________________________________ 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 -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2308 bytes Desc: not available URL: From rp2723 at att.com Thu Jan 2 15:45:15 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 2 Jan 2020 15:45:15 +0000 Subject: [Airship-discuss] Airship - Community Design Call Message-ID: Join us to continue Airship 2.0 Design discussions in 2020. 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 -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2055 bytes Desc: not available URL: From aw442m at att.com Fri Jan 3 19:49:35 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Fri, 3 Jan 2020 19:49:35 +0000 Subject: [Airship-discuss] WC and TC Special Elections Message-ID: Airship community, Both Airship committees, Working and Technical, each have a vacant seat at this time. Per the special election clause of our governance model [0], special elections for those positions will occur this month. We look forward to this opportunity to welcome new members in each committee that will foster the future of our community with their unique perspective. All it takes is a self-nomination to get started. Nominations for both committee seats will open on January 6th at 1900 UTC and close on January 13th at 1900 UTC. The Airship election guidelines [1] describe the process of self-nomination and election for committee seats. As a reminder, no more than two individuals from a company may serve on a single committee. The current Technical [2] and Working [3] Committee wiki pages have been updated to reflect each member's affiliation. Each term will conclude with the standard election cycles, June for the Technical Committee, and August for the Working Committee. Thank you in advance for your interest and participation in this election! Drew Walters Airship Working Committee [0] https://opendev.org/airship/governance#special-committee-elections [1] https://airship-election.readthedocs.io/en/latest/#how-to-submit-a-candidacy [2] https://wiki.openstack.org/wiki/Airship/Airship-TC#Overview [3] https://wiki.openstack.org/wiki/Airship/Airship-WC#Overview -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Fri Jan 3 20:28:30 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Fri, 3 Jan 2020 20:28:30 +0000 Subject: [Airship-discuss] January 6th Working Committee Meeting Postponed Message-ID: The Airship Working Committee meeting scheduled for January 6th will be postponed to January 13th due to scheduling conflicts. We will use the etherpad below for our meeting agenda. https://etherpad.openstack.org/p/airship-wc-meeting-2020-01-13 Best, Drew Walters Airship Working Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman.gorshunov at att.com Wed Jan 8 15:18:37 2020 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Wed, 8 Jan 2020 15:18:37 +0000 Subject: [Airship-discuss] [sig][airship-bootstrap] Bootstrap - On-demand meetings schedule Message-ID: <8039bd768dbd4860b5db9129bbd23dd3@att.com> Dear Airshipers, There are no Airship-bootstrap meetings in your calendar for the January and onward, there were no agenda and no meetings in December, 2019. If you would like a Bootstrap-specific meeting to be set up, please raise your topics on the Etherpad [0] (or contact me directly), and I would send an announcement to the mailing list and will get a teleconference bridge set up. The time would remain the same: Wednesday, 14:00 UTC. Airship Wiki page [1] has been updated. We would return to weekly or bi-weekly meetings when there would be many topics for the discussions. [0] https://etherpad.openstack.org/p/Airship_bootstrap [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_SIG_-_Special_Interest_Meetings Best regards, -- Roman Gorshunov Principal, Systems Engineering AT&T Technology Development, Network and Shared Services From alexander.w.hughes at accenture.com Fri Jan 10 14:15:27 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Fri, 10 Jan 2020 14:15:27 +0000 Subject: [Airship-discuss] WC and TC Special Elections In-Reply-To: References: Message-ID: Airship Community, Just a quick reminder that the nominations will be closing soon, on January 13th at 1900 UTC, for the TC and WC special elections. Regards, Alexander Hughes Airship Technical Committee From: WALTERS, ANDREW Sent: Friday, January 3, 2020 2:50 PM To: airship-discuss at lists.airshipit.org Cc: nishant.e.kumar at ericsson.com; MCEUEN, MATT ; segorov at mirantis.com; GU, JAMES ; alexander.hughes at pm.me; aodinokov at mirantis.com; LEASCK, ANDREW G ; Claire Massey Subject: [External] [Airship-discuss] WC and TC Special Elections This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments. ________________________________ Airship community, Both Airship committees, Working and Technical, each have a vacant seat at this time. Per the special election clause of our governance model [0], special elections for those positions will occur this month. We look forward to this opportunity to welcome new members in each committee that will foster the future of our community with their unique perspective. All it takes is a self-nomination to get started. Nominations for both committee seats will open on January 6th at 1900 UTC and close on January 13th at 1900 UTC. The Airship election guidelines [1] describe the process of self-nomination and election for committee seats. As a reminder, no more than two individuals from a company may serve on a single committee. The current Technical [2] and Working [3] Committee wiki pages have been updated to reflect each member's affiliation. Each term will conclude with the standard election cycles, June for the Technical Committee, and August for the Working Committee. Thank you in advance for your interest and participation in this election! Drew Walters Airship Working Committee [0] https://opendev.org/airship/governance#special-committee-elections [1] https://airship-election.readthedocs.io/en/latest/#how-to-submit-a-candidacy [2] https://wiki.openstack.org/wiki/Airship/Airship-TC#Overview [3] https://wiki.openstack.org/wiki/Airship/Airship-WC#Overview ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman.gorshunov at att.com Fri Jan 10 19:25:13 2020 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Fri, 10 Jan 2020 19:25:13 +0000 Subject: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 In-Reply-To: References: <414979D1-FC8F-4EA5-9310-22F6885CB603@gmail.com> Message-ID: <11878d3ce8a14a108eed0109ee19163d@att.com> Yes, sometimes. $30 per server, online purchase for SuperMicro [0]. https://store.supermicro.com/out-of-band-sft-oob-lic.html Roman Gorshunov Principal, Systems Engineering From: Kostiantyn Kalynovskyi Sent: Thursday, December 19, 2019 4:53 PM To: Roman Gorshunov Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Any interest in IPMI+SMASH support in Airship 2.0 I think you have to buy separate licence if you want support for redfish on many vendors? On Wed, Dec 18, 2019, 3:02 AM Roman Gorshunov > wrote: Dmitry, Which one’s don’t have RedFish support? I found out that although not advertised widely (SuperMicro), many do support it. All major vendors do support RedFish. Thank you. Best regards, — Roman Gorshunov > On 18 Dec 2019, at 09:29, Dmitry Ukov > wrote: >  > James, > I'd vote for IPMI support development since Redfish support is not that common for generic servers > > -- > Kind regards > Dmitry Ukov > Principal Deployment Engineer > Mirantis, Inc. > > _______________________________________________ > 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 rpocase at gmail.com Tue Jan 14 14:06:27 2020 From: rpocase at gmail.com (Robby Pocase) Date: Tue, 14 Jan 2020 08:06:27 -0600 Subject: [Airship-discuss] Problems with airship-in-a-bottle install Message-ID: I've attempted multiple times to install airship-in-a-bottle following the instructions at https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab. I'm running on a 64 GB, 6 core Ubuntu 16.04 VM. During installation, I consistently hit issues with the ucp namespace postgresql-0 and mariadb-server-0 going into CrashLoopBack due to permission issues. I worked around this using a thin wrapper to keep the expected permissions intact on the db data folders. #!/bin/sh while true; do kubectl exec --namespace ucp postgresql-0 -- chown postgres:postgres /var/lib/postgresql/pgdata kubectl exec --namespace ucp mariadb-server-0 -- chown mysql:mysql /var/lib/mysql sleep 30 done I have attached the final pod state and installer status. Any ideas on debugging this issue? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- MESPACE NAME READY STATUS RESTARTS AGE default log-test-n0-1578952463 0/1 Completed 0 15h kube-system airship-coredns-test 0/1 Completed 0 16h kube-system airship-haproxy-haproxy-test 0/1 Completed 0 16h kube-system airship-kubernetes-calico-etcd-etcd-test 0/1 Completed 0 16h kube-system airship-kubernetes-etcd-etcd-test 0/1 Completed 0 16h kube-system apiserver-key-rotate-kr6c9 0/1 Completed 0 16h kube-system auxiliary-etcd-n0 3/3 Running 0 16h kube-system calico-etcd-anchor-nnrnf 1/1 Running 0 16h kube-system calico-etcd-backup-1578960000-5cc58 0/1 Pending 0 13h kube-system calico-etcd-n0 1/1 Running 0 16h kube-system calico-kube-controllers-789d596595-crvwg 1/1 Running 0 16h kube-system calico-node-dl4sr 1/1 Running 1 16h kube-system calico-settings-b68bb 0/1 Completed 0 16h kube-system coredns-548d99bb86-8tthq 0/2 Running 0 16h kube-system coredns-548d99bb86-c9c2m 0/2 Running 0 16h kube-system coredns-548d99bb86-pwtnm 2/2 Running 2 16h kube-system haproxy-anchor-dncnt 1/1 Running 0 16h kube-system haproxy-n0 1/1 Running 0 16h kube-system ingress-7c656c8b5d-kk7wj 0/1 Running 4 16h kube-system ingress-error-pages-5b7f5c968b-rmmcr 1/1 Running 0 16h kube-system kubernetes-apiserver-anchor-7c54n 1/1 Running 0 16h kube-system kubernetes-apiserver-n0 1/1 Running 0 16h kube-system kubernetes-controller-manager-anchor-mxfwl 0/1 Running 0 16h kube-system kubernetes-controller-manager-n0 0/1 Error 6 16h kube-system kubernetes-etcd-anchor-l4bf4 1/1 Running 0 16h kube-system kubernetes-etcd-backup-1578960000-ktd44 0/1 Pending 0 13h kube-system kubernetes-etcd-n0 1/1 Running 0 16h kube-system kubernetes-proxy-r8ndw 1/1 Running 0 16h kube-system kubernetes-scheduler-anchor-hm49q 0/1 Running 0 16h kube-system kubernetes-scheduler-n0 0/1 Running 4 16h kube-system tiller-deploy-6c4cbc486-cvsfd 0/1 Running 3 16h nfs nfs-provisioner-5bdfddfd7-lvmn9 0/1 Error 3 16h openstack airship-glance-test 0/1 Completed 0 15h openstack airship-keystone-test 0/1 Completed 0 15h openstack airship-openstack-mariadb-test 0/1 Completed 0 15h openstack airship-openstack-memcached-memcached-bd4b4fc66-7xbgq 1/1 Running 0 15h openstack airship-openstack-rabbitmq-cluster-wait-hjpvr 0/1 Completed 0 15h openstack airship-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 15h openstack airship-openstack-rabbitmq-rabbitmq-exporter-68b97fbbdd-swtlf 1/1 Running 0 15h openstack airship-openstack-rabbitmq-test 0/1 Completed 0 15h openstack exporter-create-sql-user-7wmpn 0/1 Completed 0 15h openstack glance-api-6665dd55bc-rb2fk 1/1 Running 0 15h openstack glance-db-init-n5xhx 0/1 Completed 0 15h openstack glance-db-sync-lblmh 0/1 Completed 0 15h openstack glance-ks-endpoints-n5nmp 0/3 Completed 0 15h openstack glance-ks-service-4tpz2 0/1 Completed 0 15h openstack glance-ks-user-hpw9r 0/1 Completed 0 15h openstack glance-metadefs-load-9qw2t 0/1 Completed 0 15h openstack glance-rabbit-init-s5k89 0/1 Completed 0 15h openstack glance-storage-init-6vldx 0/1 Completed 0 15h openstack ingress-5f595778d4-jwb5f 0/1 Running 4 15h openstack ingress-error-pages-64d6f74658-plnsb 1/1 Running 0 15h openstack keystone-api-5b967fbcc-gbf4l 0/1 Running 14 15h openstack keystone-bootstrap-p6xvn 0/1 Completed 0 15h openstack keystone-credential-setup-6bz7z 0/1 Completed 0 15h openstack keystone-db-init-l4tts 0/1 Completed 0 15h openstack keystone-db-sync-lt4mq 0/1 Completed 0 15h openstack keystone-domain-manage-cv8x4 0/1 Completed 0 15h openstack keystone-fernet-rotate-1578960000-5wr22 0/1 Pending 0 13h openstack keystone-fernet-setup-8hz9j 0/1 Completed 0 15h openstack libvirt-libvirt-default-tpgds 0/1 Init:0/1 0 15h openstack mariadb-ingress-7867fdf447-ffx2v 0/1 RunContainerError 3 15h openstack mariadb-ingress-error-pages-57f5cd557f-2cjzv 1/1 Running 0 15h openstack mariadb-server-0 1/1 Running 1 15h openstack neutron-db-init-nlkf8 0/1 Completed 0 15h openstack neutron-db-sync-gm2lf 0/1 ErrImagePull 0 15h openstack neutron-dhcp-agent-default-gtr8b 0/1 Init:0/1 0 15h openstack neutron-ks-endpoints-sk287 0/3 Completed 0 15h openstack neutron-ks-service-wr6cd 0/1 Completed 0 15h openstack neutron-ks-user-kkzdx 0/1 Completed 0 15h openstack neutron-l3-agent-default-llx7q 0/1 Init:0/1 0 15h openstack neutron-metadata-agent-default-wx8zh 0/1 Init:0/2 0 15h openstack neutron-ovs-agent-default-vw2xk 0/1 Init:0/3 0 15h openstack neutron-rabbit-init-hswhp 0/1 Completed 0 15h openstack neutron-server-7674ccd4f5-zllkv 0/1 Init:0/1 0 15h openstack nova-api-metadata-6bfc5b65b8-s6pvs 0/1 Init:0/2 0 15h openstack nova-api-osapi-68b47d9664-nwzkz 0/1 Init:0/1 0 15h openstack nova-bootstrap-s2lsf 0/1 Init:0/1 0 15h openstack nova-cell-setup-1578956400-5n9bk 0/1 Pending 0 14h openstack nova-cell-setup-pkvrc 0/1 Init:0/2 0 15h openstack nova-compute-default-sgwp9 0/1 Init:0/3 0 15h openstack nova-conductor-ddb9c49fb-54gvm 0/1 Init:0/1 0 15h openstack nova-consoleauth-687d7d8b96-s8l2v 0/1 Init:0/1 0 15h openstack nova-db-init-c4s4r 0/3 Completed 0 15h openstack nova-db-sync-tpb6w 0/1 ErrImagePull 0 15h openstack nova-ks-endpoints-6swqt 0/3 Completed 0 15h openstack nova-ks-service-9z2xk 0/1 Completed 0 15h openstack nova-ks-user-btstq 0/1 Completed 0 15h openstack nova-novncproxy-5bb846d5c4-jnwsg 0/1 Init:0/3 0 15h openstack nova-placement-api-6ff7ccbcf-jsfgr 0/1 Init:0/1 0 15h openstack nova-rabbit-init-wxlwg 0/1 Completed 0 15h openstack nova-scheduler-746ff8c8d8-mjnc4 0/1 Init:0/1 0 15h openstack nova-service-cleaner-1578956400-4mlll 0/1 Pending 0 14h openstack openvswitch-db-xrrjk 1/1 Running 0 15h openstack openvswitch-vswitchd-cppbz 1/1 Running 0 15h openstack placement-ks-endpoints-hsrqq 0/3 Terminating 46 15h openstack placement-ks-service-vkpm8 0/1 Completed 0 15h openstack placement-ks-user-jqcs9 0/1 Completed 0 15h openstack prometheus-mysql-exporter-7ff8dcf656-5t97j 1/1 Running 0 15h ucp airflow-db-init-4khch 0/1 Completed 0 16h ucp airflow-db-sync-xqrvn 0/1 Completed 0 16h ucp airflow-rabbit-init-bkc9g 0/1 Completed 0 16h ucp airflow-scheduler-d77b8c77d-dhhjj 1/1 Running 0 16h ucp airflow-worker-0 1/3 Running 0 16h ucp airship-drydock-api-test 0/1 Completed 0 16h ucp airship-drydock-auth-test 0/1 Completed 0 16h ucp airship-maas-api-test 0/1 Completed 0 15h ucp airship-ucp-armada-armada-api-test 0/1 Completed 0 16h ucp airship-ucp-barbican-test 0/1 Completed 0 16h ucp airship-ucp-deckhand-deckhand-api-test 0/1 Completed 0 16h ucp airship-ucp-keystone-memcached-memcached-679d75dc4b-fqlhn 1/1 Running 0 16h ucp airship-ucp-keystone-test 0/1 Completed 0 16h ucp airship-ucp-mariadb-test 0/1 Completed 0 16h ucp airship-ucp-promenade-api-test 0/1 Completed 0 16h ucp airship-ucp-rabbitmq-cluster-wait-8p55s 0/1 Completed 0 16h ucp airship-ucp-rabbitmq-rabbitmq-0 1/1 Running 0 16h ucp airship-ucp-rabbitmq-rabbitmq-exporter-6468766459-z8rfc 1/1 Running 0 16h ucp airship-ucp-rabbitmq-test 0/1 Completed 0 16h ucp airship-ucp-shipyard-shipyard-api-test 0/1 Completed 0 15h ucp armada-api-b76fbd95-d26cs 2/2 Running 6 16h ucp armada-ks-endpoints-59x8b 0/3 Completed 0 16h ucp armada-ks-service-npg4w 0/1 Completed 0 16h ucp armada-ks-user-gll8w 0/1 Completed 0 16h ucp barbican-api-55f646d6dc-k962x 1/1 Running 0 16h ucp barbican-db-init-8m7kt 0/1 Completed 0 16h ucp barbican-db-sync-cwxc8 0/1 Completed 0 16h ucp barbican-ks-endpoints-xpzvs 0/3 Completed 0 16h ucp barbican-ks-service-d5drt 0/1 Completed 0 16h ucp barbican-ks-user-4rcsf 0/1 Completed 0 16h ucp barbican-rabbit-init-z9pgs 0/1 Completed 0 16h ucp deckhand-api-656d7468c-prht8 1/1 Running 0 16h ucp deckhand-db-init-kqpkb 0/1 Completed 0 16h ucp deckhand-db-sync-ng2jz 0/1 Completed 0 16h ucp deckhand-ks-endpoints-bzn4h 0/3 Completed 0 16h ucp deckhand-ks-service-n64s6 0/1 Completed 0 16h ucp deckhand-ks-user-47bw9 0/1 Completed 0 16h ucp divingbell-apt-default-hwr87 1/1 Running 0 16h ucp divingbell-exec-default-rc7j2 1/1 Running 0 16h ucp drydock-api-94d7c9bf4-8gw8x 1/1 Running 0 16h ucp drydock-db-init-k924x 0/1 Completed 0 16h ucp drydock-db-sync-w5t6j 0/1 Completed 0 16h ucp drydock-ks-endpoints-x99pd 0/3 Completed 0 16h ucp drydock-ks-service-mjhzz 0/1 Completed 0 16h ucp drydock-ks-user-k4bdb 0/1 Completed 0 16h ucp ingress-66d74bbbbc-s6s5r 0/1 RunContainerError 5 16h ucp ingress-error-pages-94986446f-kvtdh 0/1 RunContainerError 1 16h ucp keystone-api-64bd4795db-66hf9 0/1 Running 15 16h ucp keystone-bootstrap-d8znb 0/1 Completed 0 16h ucp keystone-credential-setup-zj2h2 0/1 Completed 0 16h ucp keystone-db-init-cvgpw 0/1 Completed 0 16h ucp keystone-db-sync-zx4bv 0/1 Completed 0 16h ucp keystone-domain-manage-m88nd 0/1 Completed 0 16h ucp keystone-fernet-rotate-1578960000-dpxxz 0/1 Pending 0 13h ucp keystone-fernet-setup-mmhbt 0/1 Completed 0 16h ucp keystone-rabbit-init-x4f2p 0/1 Completed 0 16h ucp maas-bootstrap-admin-user-w7m4r 0/1 Completed 0 15h ucp maas-db-init-tmpc5 0/1 Completed 0 15h ucp maas-db-sync-w7m6c 0/1 Completed 0 15h ucp maas-export-api-key-pgmsb 0/1 Completed 0 15h ucp maas-import-resources-qb96z 0/1 Completed 0 15h ucp maas-ingress-errors-867dddc667-l6wtm 1/1 Running 0 16h ucp maas-rack-0 1/1 Running 0 16h ucp maas-region-0 2/2 Running 0 16h ucp maas-syslog-0 2/2 Running 0 16h ucp mariadb-ingress-b9c7cd4d9-b6qck 0/1 RunContainerError 3 16h ucp mariadb-ingress-error-pages-7647578c8f-s5rxc 1/1 Running 0 16h ucp mariadb-server-0 1/1 Running 1 16h ucp postgresql-0 0/1 Error 0 16h ucp promenade-api-58bf7546b5-x8jc4 1/1 Running 0 16h ucp promenade-ks-endpoints-wf7bm 0/3 Completed 0 16h ucp promenade-ks-service-8g2cs 0/1 Completed 2 16h ucp promenade-ks-user-kmtcl 0/1 Completed 3 16h ucp shipyard-api-b7f5948d9-fh4tj 1/2 Error 14 16h ucp shipyard-db-auxiliary-v89tp 0/1 Completed 0 16h ucp shipyard-db-init-h87hl 0/1 Completed 0 16h ucp shipyard-db-sync-5826t 0/1 Completed 0 16h ucp shipyard-ks-endpoints-ppvmm 0/3 Completed 0 16h ucp shipyard-ks-service-smjkg 0/1 Completed 0 16h ucp shipyard-ks-user-ksshh 0/1 Completed 0 16h -------------- next part -------------- n0: Commands User Datetime n0: invoke shipyard 2020-01-13 21:59:21.792573+00:00 n0: n0: Validations: None n0: n0: Action Notes: n0: > action metadata:01DYGEP4DEHQ3B6SPSE3QA7T7P(2020-01-13 21:59:21.760905+00:00): Configdoc revision 2 n0: Name: deploy_site n0: Action: action/01DYGEP4DEHQ3B6SPSE3QA7T7P n0: Lifecycle: Processing n0: Parameters: {} n0: Datetime: 2020-01-13 21:59:17.680223+00:00 n0: Dag Status: running n0: Context Marker: 945365f8-748c-4387-bcfe-2871081d2941 n0: User: shipyard n0: n0: Steps Index State Footnotes n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/action_xcom 1 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/dag_concurrency_check 2 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/get_rendered_doc 3 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_configuration 4 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/preflight 5 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/validate_site_design 6 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_build 7 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/verify_site 8 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_build 9 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_status 10 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_site 11 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_post_apply 12 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/create_action_tag 13 None n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/ucp_preflight_check 14 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_status 15 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_validate_site_design 16 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/promenade_validate_site_design 17 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deckhand_validate_site_design 18 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_validate_site_design 19 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_and_deploy_nodes 20 success (1) n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_releases 21 scheduled n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/final_deployment_status 22 None n0: n0: Step Footnotes Note n0: (1) > Deployment Groups:deploy_site(2020-01-13 22:04:24.246060+00:00): Stage.DEPLOYED: masters(critical), workers(critical) n0: n0: Commands User Datetime n0: invoke shipyard 2020-01-13 21:59:21.792573+00:00 n0: n0: Validations: None n0: n0: Action Notes: n0: > action metadata:01DYGEP4DEHQ3B6SPSE3QA7T7P(2020-01-13 21:59:21.760905+00:00): Configdoc revision 2 n0: Name: deploy_site n0: Action: action/01DYGEP4DEHQ3B6SPSE3QA7T7P n0: Lifecycle: Processing n0: Parameters: {} n0: Datetime: 2020-01-13 21:59:17.680223+00:00 n0: Dag Status: running n0: Context Marker: 945365f8-748c-4387-bcfe-2871081d2941 n0: User: shipyard n0: n0: Steps Index State Footnotes n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/action_xcom 1 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/dag_concurrency_check 2 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/get_rendered_doc 3 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_configuration 4 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/preflight 5 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/validate_site_design 6 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_build 7 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/verify_site 8 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_build 9 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_status 10 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_site 11 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_post_apply 12 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/create_action_tag 13 None n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/ucp_preflight_check 14 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_status 15 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_validate_site_design 16 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/promenade_validate_site_design 17 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deckhand_validate_site_design 18 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_validate_site_design 19 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_and_deploy_nodes 20 success (1) n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_releases 21 scheduled n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/final_deployment_status 22 None n0: n0: Step Footnotes Note n0: (1) > Deployment Groups:deploy_site(2020-01-13 22:04:24.246060+00:00): Stage.DEPLOYED: masters(critical), workers(critical) n0: n0: Commands User Datetime n0: invoke shipyard 2020-01-13 21:59:21.792573+00:00 n0: n0: Validations: None n0: n0: Action Notes: n0: > action metadata:01DYGEP4DEHQ3B6SPSE3QA7T7P(2020-01-13 21:59:21.760905+00:00): Configdoc revision 2 n0: Name: deploy_site n0: Action: action/01DYGEP4DEHQ3B6SPSE3QA7T7P n0: Lifecycle: Processing n0: Parameters: {} n0: Datetime: 2020-01-13 21:59:17.680223+00:00 n0: Dag Status: running n0: Context Marker: 945365f8-748c-4387-bcfe-2871081d2941 n0: User: shipyard n0: n0: Steps Index State Footnotes n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/action_xcom 1 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/dag_concurrency_check 2 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/get_rendered_doc 3 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_configuration 4 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/preflight 5 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/validate_site_design 6 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_build 7 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/verify_site 8 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_build 9 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_status 10 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_site 11 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_post_apply 12 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/create_action_tag 13 None n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/ucp_preflight_check 14 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_status 15 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_validate_site_design 16 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/promenade_validate_site_design 17 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deckhand_validate_site_design 18 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_validate_site_design 19 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_and_deploy_nodes 20 success (1) n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_releases 21 scheduled n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/final_deployment_status 22 None n0: n0: Step Footnotes Note n0: (1) > Deployment Groups:deploy_site(2020-01-13 22:04:24.246060+00:00): Stage.DEPLOYED: masters(critical), workers(critical) n0: n0: Commands User Datetime n0: invoke shipyard 2020-01-13 21:59:21.792573+00:00 n0: n0: Validations: None n0: n0: Action Notes: n0: > action metadata:01DYGEP4DEHQ3B6SPSE3QA7T7P(2020-01-13 21:59:21.760905+00:00): Configdoc revision 2 n0: Name: deploy_site n0: Action: action/01DYGEP4DEHQ3B6SPSE3QA7T7P n0: Lifecycle: Processing n0: Parameters: {} n0: Datetime: 2020-01-13 21:59:17.680223+00:00 n0: Dag Status: running n0: Context Marker: 945365f8-748c-4387-bcfe-2871081d2941 n0: User: shipyard n0: n0: Steps Index State Footnotes n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/action_xcom 1 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/dag_concurrency_check 2 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/get_rendered_doc 3 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_configuration 4 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/preflight 5 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/validate_site_design 6 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_build 7 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/verify_site 8 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_build 9 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_status 10 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_site 11 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_post_apply 12 running n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/create_action_tag 13 None n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/ucp_preflight_check 14 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deployment_status 15 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/drydock_validate_site_design 16 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/promenade_validate_site_design 17 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/deckhand_validate_site_design 18 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_validate_site_design 19 success n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/prepare_and_deploy_nodes 20 success (1) n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/armada_get_releases 21 scheduled n0: step/01DYGEP4DEHQ3B6SPSE3QA7T7P/final_deployment_status 22 None n0: n0: Step Footnotes Note n0: (1) > Deployment Groups:deploy_site(2020-01-13 22:04:24.246060+00:00): Stage.DEPLOYED: masters(critical), workers(critical) n0: n0: Commands User Datetime n0: invoke shipyard 2020-01-13 21:59:21.792573+00:00 n0: n0: Validations: None n0: n0: Action Notes: n0: > action metadata:01DYGEP4DEHQ3B6SPSE3QA7T7P(2020-01-13 21:59:21.760905+00:00): Configdoc revision 2 n0: + popd n0: + [[ 40 -ge 40 ]] n0: + execute_create_heat_stack n0: + set +x n0: ~/deploy/treasuremap/tools/deployment/aiab n0: n0: Performing basic sanity checks by creating heat stacks n0: n0: ~/deploy/treasuremap/tools/deployment/aiab/common ~/deploy/treasuremap/tools/deployment/aiab n0: + pushd /root/deploy/treasuremap/..//treasuremap/tools/deployment/aiab/common/ n0: + bash test_create_heat_stack.sh n0: n0: WARNING: apt does not have a stable CLI interface. Use with caution in scripts. n0: Reading package lists... n0: Building dependency tree... n0: n0: Reading state information... n0: curl is already the newest version (7.47.0-1ubuntu2.14). n0: 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. n0: ~/deploy/treasuremap/tools/deployment/aiab ~/deploy/treasuremap/tools/deployment/aiab/common n0: n0: Creating KeyPair n0: the input device is not a TTY n0: ~/deploy/treasuremap/tools/deployment/aiab n0: + popd n0: + publish_horizon_dashboard n0: + kubectl -n openstack expose service/horizon-int --type=NodePort --name=horizon-dashboard n0: Error from server (NotFound): services "horizon-int" not found n0: Error when publishing Horizon dashboard. n0: To remove files generated during this script's execution, delete /root/deploy/treasuremap/../. n0: This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. n0: + error 'publishing Horizon dashboard' n0: + set +x n0: + exit 1 n0: + clean n0: + set +x From aw442m at att.com Tue Jan 14 19:09:12 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Tue, 14 Jan 2020 19:09:12 +0000 Subject: [Airship-discuss] Airship TC/WC Special Election Update Message-ID: Greetings Airship community! The nomination period for the Technical Committee special election has closed. There are two candidates: 1. Roman Gorshunov [0] 2. Andrew Leasck [1] Voting for the Technical Committee special election will open on January 13, 2020 at 19:00 UTC and close on January 20, 2020 at 1900 UTC. While there were no nominations for the vacant Working Committee seat, the Airship Working Committee has elected to extend the WC nomination period through January 13, 2020 1900 UTC after receiving a late nomination. In the event that there are two or more nominees by January 13th, the Airship Working Committee special election will occur during its originally scheduled election period, January 13, 2020 1900 UTC through January 20, 2020 1900 UTC. Voting instructions will be sent directly to the electorates' email addresses when voting commences. Best of luck to all candidates! Drew Walters Airship Working Committee [0] https://opendev.org/airship/election/src/branch/master/candidates/2020/TC/roman.gorshunov at att.com [1] https://opendev.org/airship/election/src/branch/master/candidates/2020/TC/al7689 at att.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Tue Jan 14 19:49:05 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Tue, 14 Jan 2020 19:49:05 +0000 Subject: [Airship-discuss] Problems with airship-in-a-bottle install In-Reply-To: References: Message-ID: Hello Robby! Sorry that the installation is giving you trouble. I have yet to come across this issue but may be able to help with a little more info. > I've attempted multiple times to install airship-in-a-bottle following the instructions at > https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab What version of treasuremap (i.e. commit SHA) do you have cloned? > Any ideas on debugging this issue? The only nfs-provisioner pod in your cluster also has an error; were you able to retrieve any logs from it? Also, are you using any custom images? Best, Drew Walters From aw442m at att.com Tue Jan 14 20:25:21 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Tue, 14 Jan 2020 20:25:21 +0000 Subject: [Airship-discuss] Airship TC/WC Special Election Update In-Reply-To: References: Message-ID: All, I made an error in my last email regarding the special election dates. > Voting for the Technical Committee special election will open on > January 13, 2020 at 19:00 UTC and close on January 20, 2020 at 1900 UTC. Voting for the TC special election will occur January 20, 2020 1900 UTC through January 27, 2020 1900 UTC. > While there were no nominations for the vacant Working Committee seat, the > Airship Working Committee has elected to extend the WC nomination period > through January 13, 2020 1900 UTC after receiving a late nomination. In the > event that there are two or more nominees by January 13th, the Airship > Working Committee special election will occur during its originally scheduled > election period, January 13, 2020 1900 UTC through January 20, 2020 1900 UTC. Nominations for the WC special election are open through January 20th at 1900 UTC. If a formal vote is required, it will occur at the same time as the TC vote, January 20, 2020 1900 UTC through January 27, 2020 1900 UTC. The official election dates can be found in the Airship election docs [0]. Sorry for the confusion! Drew Walters Airship Working Committee [0] https://airship-election.readthedocs.io/en/latest/#airship-elections From rpocase at gmail.com Wed Jan 15 15:04:23 2020 From: rpocase at gmail.com (Robby Pocase) Date: Wed, 15 Jan 2020 09:04:23 -0600 Subject: [Airship-discuss] Problems with airship-in-a-bottle install In-Reply-To: References: Message-ID: Hey Drew, Unfortunately, I had to tear down the system and did not get an exact SHA or get logs from the nfs-provisioner. I was not using any custom images. That said, I was finally able to get up and running after another full reinstall (SHA 40797b9d44d2e3ccced0ce2d31b8e2a839a34361). I have only done limited interactions, but all the dashboards seem to be up and will give me a chance to evaluate the system. Just in case any one else hits this kind of issue, one problem I had noticed before teardown was a lot of openstack components stuck in early init phases or in ImagePullBackOff. Checking their state through `kubectl describe pod` showed connection timeouts, TLS handshake timeouts, etc. When trying to manually pull the images in the VM I noticed the download and extract rate was painfully slow (and quite a bit slower than running directly on the host). This led me down the route of looking for any possible performance optimizations for the VM. I've attached my final Vagrantfile and pasted my most relevant environment information below. I continued to run the permissions monitoring script I pasted in discussion opening as well. vboxmanage -version 5.2.34_Ubuntur133883 vagrant version Installed Version: 2.2.6 Latest Version: 2.2.6 You're running an up-to-date version of Vagrant! vagrant plugin list vagrant-disksize (0.1.3, global) vagrant-vbguest (0.23.0, global) On Tue, Jan 14, 2020 at 1:49 PM WALTERS, ANDREW wrote: > Hello Robby! > > Sorry that the installation is giving you trouble. I have yet to come > across this issue but may be able to help with a little more info. > > > I've attempted multiple times to install airship-in-a-bottle following > the instructions at > > > https://opendev.org/airship/treasuremap/src/branch/master/tools/deployment/aiab > > What version of treasuremap (i.e. commit SHA) do you have cloned? > > > Any ideas on debugging this issue? > > The only nfs-provisioner pod in your cluster also has an error; were you > able to retrieve any logs from it? Also, are you using any custom images? > > Best, > Drew Walters > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Vagrantfile Type: application/octet-stream Size: 1206 bytes Desc: not available URL: From claire at openstack.org Tue Jan 21 16:21:25 2020 From: claire at openstack.org (Claire Massey) Date: Tue, 21 Jan 2020 10:21:25 -0600 Subject: [Airship-discuss] Welcome Ashlee, OSF Liaison for Airship Message-ID: <72D898A6-A16F-4561-A47A-1D54A023533B@openstack.org> Hi everyone, As we kick off 2020, I’m excited and proud to officially pass the torch to Ashlee as she steps into the community manager role to support Airship as the main point person representing OSF. Ashlee has been working at OSF for nearly four years supporting our marketing and community teams in many areas including global user groups, event planning, content creation, and communications. Over the past several months she has stepped up to support Airship and help shepherd the project through the OSF confirmation process, facilitate team meetings at KubeCon and the PTG and share guidance on specific topics from the OSF staff during standing WC and TC calls. Moving forward she will get even more involved and be able to help promote the project activities and milestones, increase awareness with new audiences, and provide other resources to support Airship's continued growth. You can reach her via these channels: - IRC: ashferg - WeChat: ashleeferguson - Email: ashlee at openstack.org Cheers, Claire From MM9745 at att.com Tue Jan 21 17:05:18 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 21 Jan 2020 17:05:18 +0000 Subject: [Airship-discuss] Welcome Ashlee, OSF Liaison for Airship In-Reply-To: <72D898A6-A16F-4561-A47A-1D54A023533B@openstack.org> References: <72D898A6-A16F-4561-A47A-1D54A023533B@openstack.org> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970ACF4A1@MOSTLS1MSGUSRFF.ITServices.sbc.com> Thank you Claire for all your work to make the Airship community thrive. It has been very valuable and appreciated. Welcome to your new role, Ashlee, and congratulations! You've done a lot of great things for the community already, and I look forward to collaborating even more closely. Thanks, Matt -----Original Message----- From: Claire Massey Sent: Tuesday, January 21, 2020 10:21 AM To: airship-discuss at lists.airshipit.org Cc: Ashlee Ferguson Subject: [Airship-discuss] Welcome Ashlee, OSF Liaison for Airship Hi everyone, As we kick off 2020, I’m excited and proud to officially pass the torch to Ashlee as she steps into the community manager role to support Airship as the main point person representing OSF. Ashlee has been working at OSF for nearly four years supporting our marketing and community teams in many areas including global user groups, event planning, content creation, and communications. Over the past several months she has stepped up to support Airship and help shepherd the project through the OSF confirmation process, facilitate team meetings at KubeCon and the PTG and share guidance on specific topics from the OSF staff during standing WC and TC calls. Moving forward she will get even more involved and be able to help promote the project activities and milestones, increase awareness with new audiences, and provide other resources to support Airship's continued growth. You can reach her via these channels: - IRC: ashferg - WeChat: ashleeferguson - Email: ashlee at openstack.org Cheers, Claire _______________________________________________ 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=RwVrX3OKWt8Yk0QYzlry0M-8EFvbguDaOkjDdqCBVjA&m=UBw2puV1MFvvcxELweSNR-lnMRx_7QhojGOLY2z75Wk&s=YVnnQKypnbdV9dTi8xmK-szojj2aAfXRwmNxcHaFYO8&e= From ashlee at openstack.org Tue Jan 21 17:09:32 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Tue, 21 Jan 2020 11:09:32 -0600 Subject: [Airship-discuss] Welcome Ashlee, OSF Liaison for Airship In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970ACF4A1@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <72D898A6-A16F-4561-A47A-1D54A023533B@openstack.org> <7C64A75C21BB8D43BD75BB18635E4D8970ACF4A1@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <920608DD-94F3-4C61-8037-215FE876C82D@openstack.org> Thanks, Matt! Glad I get to continue working with you all. Cheers, Ashlee > On Jan 21, 2020, at 11:05 AM, MCEUEN, MATT wrote: > > Thank you Claire for all your work to make the Airship community thrive. It has been very valuable and appreciated. > > Welcome to your new role, Ashlee, and congratulations! You've done a lot of great things for the community already, and I look forward to collaborating even more closely. > > Thanks, > Matt > > -----Original Message----- > From: Claire Massey > Sent: Tuesday, January 21, 2020 10:21 AM > To: airship-discuss at lists.airshipit.org > Cc: Ashlee Ferguson > Subject: [Airship-discuss] Welcome Ashlee, OSF Liaison for Airship > > Hi everyone, > > As we kick off 2020, I’m excited and proud to officially pass the torch to Ashlee as she steps into the community manager role to support Airship as the main point person representing OSF. > > Ashlee has been working at OSF for nearly four years supporting our marketing and community teams in many areas including global user groups, event planning, content creation, and communications. Over the past several months she has stepped up to support Airship and help shepherd the project through the OSF confirmation process, facilitate team meetings at KubeCon and the PTG and share guidance on specific topics from the OSF staff during standing WC and TC calls. > > Moving forward she will get even more involved and be able to help promote the project activities and milestones, increase awareness with new audiences, and provide other resources to support Airship's continued growth. > > You can reach her via these channels: > - IRC: ashferg > - WeChat: ashleeferguson > - Email: ashlee at openstack.org > > Cheers, > Claire > _______________________________________________ > 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=RwVrX3OKWt8Yk0QYzlry0M-8EFvbguDaOkjDdqCBVjA&m=UBw2puV1MFvvcxELweSNR-lnMRx_7QhojGOLY2z75Wk&s=YVnnQKypnbdV9dTi8xmK-szojj2aAfXRwmNxcHaFYO8&e= > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From rp2723 at att.com Wed Jan 22 03:08:52 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 22 Jan 2020 03:08:52 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan Meeting Jan 22, 2020 Message-ID: <30CA4D5B-3758-4B97-97C1-B19CA7064EDE@att.com> Folks, I need to cancel the Flight Plan Meeting tomorrow. We were going to continue the discussion regarding the GitHub POC and exploration that Drew has been doing. Details in the Etherpad https://github.com/orgs/airshipit/projects/1 Check out the https://github.com/orgs/airshipit/projects/1 Lets keep the POC going, answer Drew’s questions in the etherpad. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman.gorshunov at att.com Wed Jan 22 06:30:15 2020 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Wed, 22 Jan 2020 06:30:15 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan Meeting Jan 22, 2020 In-Reply-To: <30CA4D5B-3758-4B97-97C1-B19CA7064EDE@att.com> References: <30CA4D5B-3758-4B97-97C1-B19CA7064EDE@att.com> Message-ID: <6e5517724025446b85b4fe67563d67e6@att.com> Hello Rodolfo, The link you have provided returns “404 – not found”. Airship doesn’t have any public projects. Please, open access. Thank you. Roman Gorshunov Principal, Systems Engineering From aw442m at att.com Wed Jan 22 15:58:56 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Wed, 22 Jan 2020 15:58:56 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan Meeting Jan 22, 2020 In-Reply-To: <6e5517724025446b85b4fe67563d67e6@att.com> References: <30CA4D5B-3758-4B97-97C1-B19CA7064EDE@att.com> <6e5517724025446b85b4fe67563d67e6@att.com> Message-ID: > The link you have provided returns “404 – not found”. > Airship doesn’t have any public projects. Please, open access. Thank you. Sorry, I left the board visibility private. It's public now. Drew Walters From ashlee at openstack.org Thu Jan 23 18:13:24 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Thu, 23 Jan 2020 12:13:24 -0600 Subject: [Airship-discuss] Upcoming OSF Event: OpenDev + PTG, June 8-11 in Vancouver Message-ID: <6D3EE100-C598-442E-B9C5-DDA18C035C12@openstack.org> Join us this June in Vancouver for OpenDev + PTG, and grab your early bird tickets now ! OpenDev + PTG is a new collaborative event organized by the OpenStack Foundation gathering developers, system architects, and operators to address common open source infrastructure challenges. June 8-11, 2020 Vancouver Convention Centre - East Building OpenDev will include discussion oriented sessions around a particular topic to explore a problem within a topic area, share common architectures, and collaborate around potential solutions. This OpenDev will focus specifically on the following Tracks, spanning open source projects, including Airship, Ansible, Ceph, Kata Containers, Kubernetes, OpenStack, StarlingX, and Zuul: Hardware Automation Large-scale Usage of Open Source Infrastructure Software Containers in Production Key Challenges for Open Source in 2020 The conversations will continue into the afternoon with the Project Teams Gathering (PTG) . This is when the morning’s practices will be explored by project teams, SIGs and other workgroups who will have dedicated space to get work done in a productive setting, maximizing the ability of contributors to work through their project objectives in an environment that is focused towards work and productivity. Interested in Sponsoring? Sponsoring these events will help ensure the continued growth and success of open source infrastructure projects. A sponsorship prospectus will be available soon. If your organization is interested in participating and supporting the open infrastructure community, please contact events at openstack.org . P.S. - Stay tuned for more info on OSF’s Q4 event, the Open Infrastructure Summit you know and love! See you in Vancouver! The OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Mon Jan 27 22:16:12 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 27 Jan 2020 22:16:12 +0000 Subject: [Airship-discuss] Congratulations, Ian Pittwood! Message-ID: Airship community, I am sorry for the late notice. No additional nominations were received for the Airship Working Committee vacancy. As announced during our IRC meeting last week, Ian Pittwood is the newest member of the Airship Working Committee. Please join me in congratulating Ian! Drew Walters Airship Working Committee -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Mon Jan 27 22:26:33 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Mon, 27 Jan 2020 16:26:33 -0600 Subject: [Airship-discuss] OSF 2019 Annual Report Message-ID: <91030085-7BB9-4057-94F3-FF772D966462@openstack.org> Hi everyone, The OSF community had a productive year, merging 58k code changes to produce open source infrastructure software like Airship, Kata Containers, StarlingX, and Zuul, along with the third most active OSS project in the world, OpenStack. With 100,000 members and millions more visiting OSF websites in 2019 to get involved, the community made huge strides in addressing the 7.7B market for OpenStack and more than $12B combined OpenStack & Containers markets in the future. Each individual member, working group, SIG, and contributor was instrumental in continuing to support the OSF mission: helping people build and operate open infrastructure. The OSF 2019 Annual Report was published today highlighting the achievements across the community and the goals for the year ahead. Let’s break down some of the highlights of last year: The OSF confirmed three new open infrastructure projects to complement OpenStack in powering the world’s open infrastructure; OpenStack is one of the top three most active open source projects in number of changes, and is projected to be a $7.7 billion USD market by 2023; Some of the world’s largest brands—AT&T, Baidu, Blizzard Entertainment, BMW, China UnionPay, Walmart, and Volvo among others—shared their open source infrastructure use cases and learnings; Upstream contributors continued to prioritize cross-project integration with open source projects including Ceph, Kubernetes, Ansible, and Tungsten Fabric. New contributors were on-boarded through multiple internship and mentoring programs as well as OpenStack Upstream Institute, which was held in seven countries last year! The OSF would like to extend a huge thanks to the global community for all of the work that went into 2019 and is continuing in 2020 to help people build and operate open source infrastructure. Check out the full OSF 2019 Annual Report on the OpenStack website. Thank you for a great year— I look forward to working with you more in 2020! Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From manoj.alva at ericsson.com Wed Jan 29 14:39:47 2020 From: manoj.alva at ericsson.com (Manoj Alva) Date: Wed, 29 Jan 2020 14:39:47 +0000 Subject: [Airship-discuss] Redfish API support related question Message-ID: Hello All, I tried adding support for new APIs and generated code using 4.2.2 OpenAPI code generator. Reference Changeset : https://review.opendev.org/#/c/704314/ I am trying to add support to the following APIs * FirmwareInventoryDownloadImage * FirmwareInventory * GetTask * UpdateService * UpdateServiceSimpleUpdate I have a the following observations. 1. Here is diff of the code generated for older constructs and the ones present in the repo. The code is generated with two underscores "__". But the repo has single underscore. Is it that the generated code has been massaged for some reasons. If it is the case, will it not be an issue with extending the code for future APIs. I was under the assumption that no manual intervention is required w.r.t generated code. Client/openapi.yaml [cid:image002.jpg at 01D5D6DD.7188E0D0] 1. If the above case is not true and the generated code is used as is, why store the generated code ? Is there a specific reason around storing the generated code in repo ? 2. There is this case of firmware update. The flow as per documentation (IDRAC) is as follows * Call to UpdateService and extract the HTTPPushUri from the response header. * The HTTPPushUri for IDRAC seems to be listed as a POST call to FirmwareInventory .This POST call information is not listed in Redfish Specification (Redfish Schema Supplement Document Identifier: DSP0268). I have tried handling this an additional API under FirmwareInventory (Refer Changeset above). Is this fine ? How do we handle the HTTPPushUris from different vendors given they are free to implement it of their choice. LinkofIDRAC script implementation : https://github.com/dell/iDRAC-Redfish-Scripting/blob/master/Redfish%20Python/DeviceFirmwareSimpleUpdateREDFISH.py Thanks for your time Manoj Alva (manoj.alva at ericsson.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.jpg Type: image/jpeg Size: 57481 bytes Desc: image002.jpg URL: From rp2723 at att.com Wed Jan 29 16:00:53 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 29 Jan 2020 16:00:53 +0000 Subject: [Airship-discuss] Canceled: Airship - Community Design Call Message-ID: <99088997CCAD0C4BA20008FD094344963C5176BC@MISOUT7MSGUSRDI.ITServices.sbc.com> CANCELED – Thursday Jan 30, 2020 – I am unavailable to host this meeting tomorrow. __________________________________________ Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Airship Repositories · https://opendev.org/airship/airshipctl · https://opendev.org/airship/go-redfish · https://opendev.org/airship/zuul-airship-roles · https://opendev.org/airship/apis · https://opendev.org/airship/images __________________________________________ 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2534 bytes Desc: not available URL: From aw442m at att.com Wed Jan 29 16:20:08 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Wed, 29 Jan 2020 16:20:08 +0000 Subject: [Airship-discuss] Airship Technical Committee Special Election Results Message-ID: Airship community, It is my pleasure to announce the conclusion of the Airship Technical Committee special election; Andrew Leasck is the newest Technical Committee member, effective immediately. Congratulations! The official poll results [0] and Technical Committee roster [1] are now available for public consumption. Thank you, candidates and contributors, for participating. The Technical Committee will meet again Thursday, February 13th, at 1500 UTC. The meeting, as well as all other Airship committee meetings, are open to the community. Regards, Drew Walters Airship Working Committee [0] https://airship-election.readthedocs.io/en/latest/results/2020/tc.html [1] https://wiki.openstack.org/wiki/Airship/Airship-TC From rp2723 at att.com Wed Jan 29 15:52:17 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 29 Jan 2020 15:52:17 +0000 Subject: [Airship-discuss] Canceled: Airship Flight Plan - Meeting Message-ID: <99088997CCAD0C4BA20008FD094344963C5175A3@MISOUT7MSGUSRDI.ITServices.sbc.com> REMINDER THIS MEETING IS CANCELED TODAY – Weekly Meeting Agenda : • Perform JIRA Management o Make sure JIRA Tasks identified in community meetings are getting created. o Manage priority . • Identify issues that need to be reprioritized, o Manage association/Milestones/Themed Sprints o Open Questions on Milestones/Tasks/Issues Priorities • Patchsets Management o Open Discussion about Comments or Patchsets o Help push Patchsets to the Finish Line • Any other Roadmap type Q/A and Mgmt. Activities -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5884 bytes Desc: not available URL: From ashlee at openstack.org Wed Jan 29 22:04:57 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 29 Jan 2020 16:04:57 -0600 Subject: [Airship-discuss] Help Shape the Track Content for OpenDev + PTG, June 8-11 in Vancouver Message-ID: Hi everyone, Hopefully by now you’ve heard about our upcoming event, OpenDev + PTG Vancouver, June 8-11, 2020 . We need your help shaping this event! Our vision is for the content to be programmed by you-- the community. OSF is looking to kick things off by selecting members for OpenDev Programming Committees for each Track. That Program Committee will then select Moderators who will lead interactive discussions on a particular topic within the track. Below you'll have the opportunity to nominate yourself for a position on the Programming Committee, as a Moderator, or both, as well as suggesting specific Topics within each Track. PTG programming will kick off in the coming weeks. If you’re interested in volunteering as an OpenDev Programming Committee member, discussion Moderator, or would like to suggest topics for moderated discussions within a particular Track, please read the details below, and then fill out this form . We’re looking for subject matter experts on the following OpenDev Tracks: - Hardware Automation (accelerators, provisioning hardware, networking) - Large-scale Usage of Open Source Infrastructure Software (scale pain points, multi-location, CI/CD) - Containers in Production (isolation, virtualization, telecom containers) - Key Challenges for Open Source in 2020 (beyond licensing, public clouds, ethics) OpenDev Programming Committee members will: Work with other Committee members, which will include OSF representatives, to curate OpenDev content based on subject expertise, community input, and relevance to open source infrastructure Promote the individual Tracks within your networks Review community input and suggestions for Track discussions Solicit moderators from your network if you know someone who is a subject matter expert Ensure diversity of speakers and companies represented in your Track Focus topics around on real-world user stories and technical, in-the-trenches experiences Programming Committee members need to be available during the following dates/time commitments: 8 - 10 hours from February - May for bi-weekly calls with your Track's Programming Committee (plus a couple of OSF representatives to facilitate the call) OpenDev, June 8 - 10, 2020 (not required, but preferred) Programming Committee members will receive a complimentary pass to the event Programming Committees will be comprised of a few people per Track who will work to select a handful of topics and moderators for each Track. The exact topic counts will be determined before Committees begin deciding. OpenDev Discussion Moderators will Be appointed by the Programming Committees Facilitate discussions within a particular Track Have adequate knowledge and experience to lead and moderate discussion around certain topics during the event Work with Programming Committee to decide focal point of discussion Moderators need to be available to attend OpenDev, June 8 - 10, 2020, and will receive a complimentary pass. Programming Committee nominations are open until February 11. Deadlines to volunteer to be a moderator and suggest topics will be in late February. Nominate yourself or suggest discussion topics here: https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer Cheers, The OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From messenger at webex.com Fri Jan 31 17:18:17 2020 From: messenger at webex.com (RODOLFO J PACHECO) Date: Fri, 31 Jan 2020 17:18:17 +0000 (GMT) Subject: [Airship-discuss] Webex meeting invitation: Airship SIG UI Message-ID: <54169423.2077391580491097799.JavaMail.nobody@rva1rmd102.webex.com> Hi, airship-discuss at lists.airshipit.org, RODOLFO J PACHECO invites you to join this Webex meeting. Airship SIG UI Occurs every Friday effective Friday, January 31, 2020 from 1:00 PM to 2:00 PM, (UTC-05:00) Eastern Time (US & Canada) 1:00 pm | (UTC-05:00) Eastern Time (US & Canada) | 1 hr Meeting number (access code): 730 731 751 Meeting password: Abcd123! Add to Calendar https://attcorp.webex.com/attcorp/j.php?MTID=mc84c33cd06eadd59c3b656d14de1d33c When it's time, join the meeting. https://attcorp.webex.com/attcorp/j.php?MTID=mc7ebc731d41d3384c65e3c2acc73bf4b JOIN FROM A VIDEO SYSTEM OR APPLICATION Dial sip:730731751 at attcorp.webex.com You can also dial 173.243.2.68 and enter your meeting number. JOIN BY PHONE 1-844-517-1415 United States Toll Free Tap here to call (mobile phones only, hosts not supported): tel:1-844-517-1415,,*01*730731751%23%23*01* 1-618-230-6039 United States Toll Tap here to call (mobile phones only, hosts not supported): tel:%2B1-618-230-6039,,*01*730731751%23%23*01* Global call-in numbers https://attcorp.webex.com/attcorp/globalcallin.php?MTID=m82b426ee1781592e0997404f0a812350 Accessibility and Assistive Technologies Select this job aid: https://workspace.web.att.com/sites/etech/WebEx/Webex_Meetings_Accessibility.html for tips and guides to make Webex Meetings accessible to persons with disabilities who may rely on assistive technologies. Can't join the meeting? https://collaborationhelp.cisco.com/article/WBX000029055 IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5795 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Webex_Meeting.ics Type: application/octet-stream Size: 5795 bytes Desc: not available URL: From messenger at webex.com Fri Jan 31 17:47:02 2020 From: messenger at webex.com (RODOLFO J PACHECO) Date: Fri, 31 Jan 2020 17:47:02 +0000 (GMT) Subject: [Airship-discuss] Webex meeting invitation: Airship SIG Yaml Message-ID: <1633569740.2085391580492822572.JavaMail.nobody@rva1rmd102.webex.com> Hi, airship-discuss at lists.airshipit.org, RODOLFO J PACHECO invites you to join this Webex meeting. Airship SIG Yaml Occurs every Monday effective Monday, February 3, 2020 from 11:00 PM to 12:00 AM, (UTC-05:00) Eastern Time (US & Canada) 11:00 pm | (UTC-05:00) Eastern Time (US & Canada) | 1 hr Meeting number (access code): 739 604 226 Meeting password: Abcd123! Add to Calendar https://attcorp.webex.com/attcorp/j.php?MTID=m9b3f775c1449ab1c4c361412f5b4b6c9 When it's time, join the meeting. https://attcorp.webex.com/attcorp/j.php?MTID=m11cfd19f852160480c3afd970845c190 JOIN FROM A VIDEO SYSTEM OR APPLICATION Dial sip:739604226 at attcorp.webex.com You can also dial 173.243.2.68 and enter your meeting number. JOIN BY PHONE 1-844-517-1415 United States Toll Free Tap here to call (mobile phones only, hosts not supported): tel:1-844-517-1415,,*01*739604226%23%23*01* 1-618-230-6039 United States Toll Tap here to call (mobile phones only, hosts not supported): tel:%2B1-618-230-6039,,*01*739604226%23%23*01* Global call-in numbers https://attcorp.webex.com/attcorp/globalcallin.php?MTID=md313baaed24a4dc555c71f3f3090a1b6 Accessibility and Assistive Technologies Select this job aid: https://workspace.web.att.com/sites/etech/WebEx/Webex_Meetings_Accessibility.html for tips and guides to make Webex Meetings accessible to persons with disabilities who may rely on assistive technologies. Can't join the meeting? https://collaborationhelp.cisco.com/article/WBX000029055 IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5797 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Webex_Meeting.ics Type: application/octet-stream Size: 5797 bytes Desc: not available URL: From messenger at webex.com Fri Jan 31 18:56:17 2020 From: messenger at webex.com (RODOLFO J PACHECO) Date: Fri, 31 Jan 2020 18:56:17 +0000 (GMT) Subject: [Airship-discuss] Webex meeting changed: Airship SIG Yaml Message-ID: <1983085891.2103661580496977901.JavaMail.nobody@rva1rmd102.webex.com> Hi, airship-discuss at lists.airshipit.org, RODOLFO J PACHECO changed the Webex meeting information. Airship SIG Yaml Occurs every Monday effective Monday, February 3, 2020 from 11:00 AM to 12:00 PM, (UTC-05:00) Eastern Time (US & Canada) 11:00 am | (UTC-05:00) Eastern Time (US & Canada) | 1 hr Meeting number (access code): 739 604 226 Meeting password: Abcd123! When it's time, join the meeting. https://attcorp.webex.com/attcorp/j.php?MTID=m11cfd19f852160480c3afd970845c190 Add to Calendar https://attcorp.webex.com/attcorp/j.php?MTID=maf5988858fec11a342518a0b35a5b6f7 JOIN BY PHONE 1-844-517-1415 United States Toll Free Tap here to call (mobile phones only, hosts not supported): tel:1-844-517-1415,,*01*739604226%23%23*01* 1-618-230-6039 United States Toll Tap here to call (mobile phones only, hosts not supported): tel:%2B1-618-230-6039,,*01*739604226%23%23*01* Global call-in numbers https://attcorp.webex.com/attcorp/globalcallin.php?MTID=md313baaed24a4dc555c71f3f3090a1b6 JOIN FROM A VIDEO SYSTEM OR APPLICATION Dial sip:739604226 at attcorp.webex.com You can also dial 173.243.2.68 and enter your meeting number. Join using Microsoft Lync or Microsoft Skype for Business Dial sip:739604226.attcorp at lync.webex.com Can't join the meeting? https://collaborationhelp.cisco.com/article/WBX000029055 IMPORTANT NOTICE: Please note that this Webex service allows audio and other information sent during the session to be recorded, which may be discoverable in a legal matter. By joining this session, you automatically consent to such recordings. If you do not consent to being recorded, discuss your concerns with the host or do not join the session. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 5797 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Webex_Meeting.ics Type: application/octet-stream Size: 5797 bytes Desc: not available URL: