From kire at kth.se Mon Sep 3 20:50:09 2018 From: kire at kth.se (=?iso-8859-1?Q?Jan-Erik_M=E5ngs?=) Date: Mon, 3 Sep 2018 20:50:09 +0000 Subject: [Airship-discuss] scaled down version of site/airship-seaworthy Message-ID: <3BD4E031-3BEE-4704-883B-D93F32B86EE0@kth.se> (reposting again in plain text, my first attempt was too big >.40 KB due to formatting) We're playing around with http://git.openstack.org/cgit/openstack/airship-treasuremap/ and we're having some problems. We're trying to deploy a scaled down version of site/airship-seaworthy (a smaller "template" could come in handy, who has this many disks in their lab?). We're only using four servers (Dell 630s), with three SSDs/server, networking according to seaworthy etc. We've copied site/airship-seaworthy to our own site and tried to modify things to the best of our knowledge. When we run the genesis-script on the genesis node we see an error related to mariadb, see below. Any hints on what could be wrong are much appreciated. (Storage is always among the most difficult things, I really need to learn ceph :-)). (BTW, instructions here https://treasuremap.readthedocs.io/en/latest/deployment.html does not seem to be in sync with the repo above) Thanks for your help /Jan-Erik (et al.) Output from the genesis script: NAMESPACE NAME READY STATUS RESTARTS AGE ceph ceph-bootstrap-vb495 0/1 Completed 0 32m ceph ceph-cephfs-client-key-generator-jvc62 0/1 Completed 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-5pb88 1/1 Running 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-789vh 1/1 Running 0 21m ceph ceph-mds-6c757f9549-fqw9v 1/1 Running 0 21m ceph ceph-mds-keyring-generator-p2hzh 0/1 Completed 0 32m ceph ceph-mgr-5f985c796-fj6ql 1/1 Running 0 21m ceph ceph-mgr-keyring-generator-2xvvm 0/1 Completed 0 32m ceph ceph-mon-check-84c94dc8ff-wgblt 1/1 Running 0 32m ceph ceph-mon-keyring-generator-rln66 0/1 Completed 0 32m ceph ceph-mon-lv7hv 2/2 Running 0 32m ceph ceph-osd-default-83945928-xl2g5 2/2 Running 0 29m ceph ceph-osd-keyring-generator-zn6dg 0/1 Completed 0 32m ceph ceph-rbd-pool-t7b8d 0/1 Completed 0 21m ceph ceph-rbd-provisioner-86c99578d8-2689g 1/1 Running 0 21m ceph ceph-rbd-provisioner-86c99578d8-jtfd5 1/1 Running 0 21m ceph ceph-rgw-694b44bd5d-ckv8v 0/1 Running 6 21m ceph ceph-rgw-keyring-generator-chlhr 0/1 Completed 0 32m ceph ceph-storage-keys-generator-5g58r 0/1 Completed 0 32m ceph ingress-65dc849968-68nfm 1/1 Running 0 32m ceph ingress-65dc849968-gfwqq 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-jx8tb 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-kfd42 1/1 Running 0 32m kube-system auxiliary-etcd-radio-st-11 3/3 Running 0 39m kube-system bootstrap-armada-radio-st-11 4/4 Running 0 39m kube-system calico-etcd-anchor-rvghv 1/1 Running 0 37m kube-system calico-etcd-radio-st-11 1/1 Running 0 37m kube-system calico-kube-policy-controllers-5df8bcbfc6-swxn4 1/1 Running 0 37m kube-system calico-node-s9qfh 2/2 Running 0 37m kube-system calico-settings-ljc9s 0/1 Completed 0 37m kube-system coredns-5545b74458-6kmmf 1/1 Running 0 36m kube-system coredns-5545b74458-nfqwq 1/1 Running 0 36m kube-system haproxy-anchor-9zh6b 1/1 Running 0 34m kube-system haproxy-radio-st-11 1/1 Running 1 34m kube-system ingress-error-pages-5ccf96bf7d-2mzsl 1/1 Running 0 32m kube-system ingress-error-pages-5ccf96bf7d-x9p64 1/1 Running 0 32m kube-system ingress-kqxck 1/1 Running 0 32m kube-system kubernetes-apiserver-anchor-ppv9m 1/1 Running 0 34m kube-system kubernetes-apiserver-radio-st-11 1/1 Running 0 32m kube-system kubernetes-controller-manager-anchor-m2mm4 1/1 Running 0 33m kube-system kubernetes-controller-manager-radio-st-11 1/1 Running 0 33m kube-system kubernetes-etcd-anchor-v7nr9 1/1 Running 0 36m kube-system kubernetes-etcd-radio-st-11 1/1 Running 0 34m kube-system kubernetes-proxy-86gmf 1/1 Running 0 38m kube-system kubernetes-scheduler-anchor-dztff 1/1 Running 0 33m kube-system kubernetes-scheduler-radio-st-11 1/1 Running 0 33m ucp ceph-namespace-client-key-generator-tnng5 0/1 Completed 0 5m ucp ingress-6cd5b89d5d-2pw7x 1/1 Running 0 5m ucp ingress-6cd5b89d5d-z74xt 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-24rjr 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-qvbmt 1/1 Running 0 5m ucp mariadb-ingress-74f744b54c-n7wzt 0/1 Running 0 4m ucp mariadb-ingress-error-pages-5dc7dd974c-lbdh4 1/1 Running 0 4m ucp mariadb-server-0 0/1 Pending 0 4m 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller [-] Error while installing release airship-ucp-mariadb: grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller Traceback (most recent call last): 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller metadata=self.metadata) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller 2018-09-03 15:40:50.635 2392 ERROR armada.cli [-] Caught internal exception: armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli metadata=self.metadata) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.635 2392 ERROR armada.cli return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli During handling of the above exception, another exception occurred: 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/__init__.py", line 39, in safe_invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli self.invoke() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/apply.py", line 217, in invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli resp = armada.sync() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/armada.py", line 480, in sync 2018-09-03 15:40:50.635 2392 ERROR armada.cli timeout=timer) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 414, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise ex.ReleaseException(release, status, 'Install') 2018-09-03 15:40:50.635 2392 ERROR armada.cli armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli ^[[C 2018-09-03 15:41:04.365 3391 INFO armada.handlers.armada [-] Performing pre-flight operations. 2018-09-03 15:41:04.529 3391 INFO armada.handlers.armada [-] Cloning repo: https://git.openstack.org/openstack/airship-promenade from branch: f60f6d7a8569c5006d32c44c27f4584f10ffe57a From rp2723 at att.com Thu Sep 6 14:49:43 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 6 Sep 2018 14:49:43 +0000 Subject: [Airship-discuss] Canceled: Airship - Open Design Call - PM EST Call Message-ID: <99088997CCAD0C4BA20008FD09434496271FBDC8@MISOUT7MSGUSRDI.ITServices.sbc.com> Cancelling these meeting, many will be at the PTG We will use these ether pad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ To join the Meeting: https://bluejeans.com/421706689 To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 421706689 To join via phone : 1) Dial: +1.408.317.9254 (BlueJeans U.S. Toll) +1.866.226.4650 (US Toll Free) (see all numbers - http://bluejeans.com/numbers) 2) Enter Conference ID : 421706689 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2622 bytes Desc: not available URL: From mark.m.burnett at gmail.com Thu Sep 6 15:00:32 2018 From: mark.m.burnett at gmail.com (Mark Burnett) Date: Thu, 6 Sep 2018 10:00:32 -0500 Subject: [Airship-discuss] Airship Developer Update 2018-09-06 Message-ID: Hi all, This is an introductory email of what hopefully becomes a regular series to help digest development efforts in the Airship community. In case you missed it, our first community design call was held Thursday, 2018-08-30. Here's the recording [0]. On to the updates: The new airship-treasuremap repo [1] is intended to hold a realistic, up-to-date example of Airship configuration. It's still evolving, but will be supported by an AT&T-provided CICD pipeline to help automate and validate component updates. This should help ensure it remains a reasonable starting place for operators. Armada now uses Helm version 2.10. This upgrade enables new features, including an effort in OpenStack Helm to leverage Tiller to generate certificates. This is a breaking change that requires coordinating updates Tiller and Armada (Tiller first!). Shipyard supports a couple of new actions: update_software [2] and redploy_server [4]. There is still work to do, especially around redeploy_server, but these should improve the Airship operational experience. Finally, there have been a number of security improvements moving through the pipeline [6-5]. These improvements are part of a theme to harden Airship-based deployments across the board, so keep an eye out for future work in this area. Feel free to respond in this thread with questions or comments about current and future development themes. Best, Mark Burnett [0] Design meeting recording: https://bluejeans.com/s/8TTM1 [1] Treasuremap repo: https://github.com/openstack/airship-treasuremap [2] Shipyard update_software action: https://review.openstack.org/#/c/579990/ [3] Initial Shipyard redeploy_server action: https://review.openstack.org/#/c/583793/ [4] Disable anonymous auth in Kubelet: https://review.openstack.org/#/c/596898/ [5] Replace Deckhand ConfigMap with Secret: https://review.openstack.org/#/c/595386/ [6] First steps for security guide: https://review.openstack.org/#/c/587979/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kire at kth.se Mon Sep 3 20:44:07 2018 From: kire at kth.se (=?iso-8859-1?Q?Jan-Erik_M=E5ngs?=) Date: Mon, 3 Sep 2018 20:44:07 +0000 Subject: [Airship-discuss] airship-treasuremap problems (scaled down version of site/airship-seaworthy) Message-ID: We're playing around with http://git.openstack.org/cgit/openstack/airship-treasuremap/ and we're having some problems. We're trying to deploy a scaled down version of site/airship-seaworthy (a smaller "template" could come in handy, who has this many disks in their lab?). We're only using four servers (Dell 630s), with three SSDs/server, networking according to seaworthy etc. We've copied site/airship-seaworthy to our own site and tried to modify things to the best of our knowledge. When we run the genesis-script on the genesis node we see an error related to mariadb, see below. Any hints on what could be wrong are much appreciated. (Storage is always among the most difficult things, I really need to learn ceph :-)). (BTW, instructions here https://treasuremap.readthedocs.io/en/latest/deployment.html does not seem to be in sync with the repo above) Thanks for your help /Jan-Erik (et al.) Output from the genesis script: NAMESPACE NAME READY STATUS RESTARTS AGE ceph ceph-bootstrap-vb495 0/1 Completed 0 32m ceph ceph-cephfs-client-key-generator-jvc62 0/1 Completed 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-5pb88 1/1 Running 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-789vh 1/1 Running 0 21m ceph ceph-mds-6c757f9549-fqw9v 1/1 Running 0 21m ceph ceph-mds-keyring-generator-p2hzh 0/1 Completed 0 32m ceph ceph-mgr-5f985c796-fj6ql 1/1 Running 0 21m ceph ceph-mgr-keyring-generator-2xvvm 0/1 Completed 0 32m ceph ceph-mon-check-84c94dc8ff-wgblt 1/1 Running 0 32m ceph ceph-mon-keyring-generator-rln66 0/1 Completed 0 32m ceph ceph-mon-lv7hv 2/2 Running 0 32m ceph ceph-osd-default-83945928-xl2g5 2/2 Running 0 29m ceph ceph-osd-keyring-generator-zn6dg 0/1 Completed 0 32m ceph ceph-rbd-pool-t7b8d 0/1 Completed 0 21m ceph ceph-rbd-provisioner-86c99578d8-2689g 1/1 Running 0 21m ceph ceph-rbd-provisioner-86c99578d8-jtfd5 1/1 Running 0 21m ceph ceph-rgw-694b44bd5d-ckv8v 0/1 Running 6 21m ceph ceph-rgw-keyring-generator-chlhr 0/1 Completed 0 32m ceph ceph-storage-keys-generator-5g58r 0/1 Completed 0 32m ceph ingress-65dc849968-68nfm 1/1 Running 0 32m ceph ingress-65dc849968-gfwqq 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-jx8tb 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-kfd42 1/1 Running 0 32m kube-system auxiliary-etcd-radio-st-11 3/3 Running 0 39m kube-system bootstrap-armada-radio-st-11 4/4 Running 0 39m kube-system calico-etcd-anchor-rvghv 1/1 Running 0 37m kube-system calico-etcd-radio-st-11 1/1 Running 0 37m kube-system calico-kube-policy-controllers-5df8bcbfc6-swxn4 1/1 Running 0 37m kube-system calico-node-s9qfh 2/2 Running 0 37m kube-system calico-settings-ljc9s 0/1 Completed 0 37m kube-system coredns-5545b74458-6kmmf 1/1 Running 0 36m kube-system coredns-5545b74458-nfqwq 1/1 Running 0 36m kube-system haproxy-anchor-9zh6b 1/1 Running 0 34m kube-system haproxy-radio-st-11 1/1 Running 1 34m kube-system ingress-error-pages-5ccf96bf7d-2mzsl 1/1 Running 0 32m kube-system ingress-error-pages-5ccf96bf7d-x9p64 1/1 Running 0 32m kube-system ingress-kqxck 1/1 Running 0 32m kube-system kubernetes-apiserver-anchor-ppv9m 1/1 Running 0 34m kube-system kubernetes-apiserver-radio-st-11 1/1 Running 0 32m kube-system kubernetes-controller-manager-anchor-m2mm4 1/1 Running 0 33m kube-system kubernetes-controller-manager-radio-st-11 1/1 Running 0 33m kube-system kubernetes-etcd-anchor-v7nr9 1/1 Running 0 36m kube-system kubernetes-etcd-radio-st-11 1/1 Running 0 34m kube-system kubernetes-proxy-86gmf 1/1 Running 0 38m kube-system kubernetes-scheduler-anchor-dztff 1/1 Running 0 33m kube-system kubernetes-scheduler-radio-st-11 1/1 Running 0 33m ucp ceph-namespace-client-key-generator-tnng5 0/1 Completed 0 5m ucp ingress-6cd5b89d5d-2pw7x 1/1 Running 0 5m ucp ingress-6cd5b89d5d-z74xt 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-24rjr 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-qvbmt 1/1 Running 0 5m ucp mariadb-ingress-74f744b54c-n7wzt 0/1 Running 0 4m ucp mariadb-ingress-error-pages-5dc7dd974c-lbdh4 1/1 Running 0 4m ucp mariadb-server-0 0/1 Pending 0 4m 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller [-] Error while installing release airship-ucp-mariadb: grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller Traceback (most recent call last): 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller metadata=self.metadata) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller 2018-09-03 15:40:50.635 2392 ERROR armada.cli [-] Caught internal exception: armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli metadata=self.metadata) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.635 2392 ERROR armada.cli return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli During handling of the above exception, another exception occurred: 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/__init__.py", line 39, in safe_invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli self.invoke() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/apply.py", line 217, in invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli resp = armada.sync() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/armada.py", line 480, in sync 2018-09-03 15:40:50.635 2392 ERROR armada.cli timeout=timer) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 414, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise ex.ReleaseException(release, status, 'Install') 2018-09-03 15:40:50.635 2392 ERROR armada.cli armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli ^[[C 2018-09-03 15:41:04.365 3391 INFO armada.handlers.armada [-] Performing pre-flight operations. 2018-09-03 15:41:04.529 3391 INFO armada.handlers.armada [-] Cloning repo: https://git.openstack.org/openstack/airship-promenade from branch: f60f6d7a8569c5006d32c44c27f4584f10ffe57a -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Thu Sep 6 00:52:06 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 05 Sep 2018 19:52:06 -0500 Subject: [Airship-discuss] 6 days left for the Forum Brainstorming Period... Message-ID: <5B907A36.3060901@openstack.org> Hello All! The Forum Brainstorming session ends September 11 and the topic submission phase begins September 12. Thank you to all of the projects that have created a wiki and begun the Brainstorming Phase. I'd like to encourage projects that have not yet created an etherpad to do so at https://wiki.openstack.org/wiki/Forum/Berlin2018 This is an opportunity to get feedback, vet ideas, and garner support from the community on your ideas. Don't rely only on a PTL to make the agenda... step on up and place the items you consider important front and center :) If you have questions or concerns about the process, please don't hesitate to reach out. Cheers, Jimmy From MM9745 at att.com Thu Sep 6 17:44:50 2018 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 6 Sep 2018 17:44:50 +0000 Subject: [Airship-discuss] scaled down version of site/airship-seaworthy In-Reply-To: <3BD4E031-3BEE-4704-883B-D93F32B86EE0@kth.se> References: <3BD4E031-3BEE-4704-883B-D93F32B86EE0@kth.se> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D896CAA84FC@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hey Jan-Erik! If your lab is still in this state, could you check the pod logs for ceph-rgw-694b44bd5d-ckv8v and share what you see? Looks like that guy is Running but not completed (as of the time of the logs below). Please check `kubectl -n ceph exec ceph-mon-lv7hw -- ceph -s` to see the ceph status. We are in progress of updating the treasuremap readthedocs content, stay tuned! Thanks, Matt -----Original Message----- From: Jan-Erik Mångs Sent: Monday, September 3, 2018 3:50 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] scaled down version of site/airship-seaworthy (reposting again in plain text, my first attempt was too big >.40 KB due to formatting) We're playing around with https://urldefense.proofpoint.com/v2/url?u=http-3A__git.openstack.org_cgit_openstack_airship-2Dtreasuremap_&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=MyMpkoXeJDDM5X1b0oakc6awcXcRf74kWEKFp5iQp9w&s=i-lEaji6J8bUrRsLcZQNEzciBuYCTkRQAdOil7Lajow&e= and we're having some problems. We're trying to deploy a scaled down version of site/airship-seaworthy (a smaller "template" could come in handy, who has this many disks in their lab?). We're only using four servers (Dell 630s), with three SSDs/server, networking according to seaworthy etc. We've copied site/airship-seaworthy to our own site and tried to modify things to the best of our knowledge. When we run the genesis-script on the genesis node we see an error related to mariadb, see below. Any hints on what could be wrong are much appreciated. (Storage is always among the most difficult things, I really need to learn ceph :-)). (BTW, instructions here https://urldefense.proofpoint.com/v2/url?u=https-3A__treasuremap.readthedocs.io_en_latest_deployment.html&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=MyMpkoXeJDDM5X1b0oakc6awcXcRf74kWEKFp5iQp9w&s=MKTFp8gJE_JdUc2rKHp0oTUezN9h1rlsW0FU-RXDbXA&e= does not seem to be in sync with the repo above) Thanks for your help /Jan-Erik (et al.) Output from the genesis script: NAMESPACE NAME READY STATUS RESTARTS AGE ceph ceph-bootstrap-vb495 0/1 Completed 0 32m ceph ceph-cephfs-client-key-generator-jvc62 0/1 Completed 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-5pb88 1/1 Running 0 21m ceph ceph-cephfs-provisioner-cdfb7cfbf-789vh 1/1 Running 0 21m ceph ceph-mds-6c757f9549-fqw9v 1/1 Running 0 21m ceph ceph-mds-keyring-generator-p2hzh 0/1 Completed 0 32m ceph ceph-mgr-5f985c796-fj6ql 1/1 Running 0 21m ceph ceph-mgr-keyring-generator-2xvvm 0/1 Completed 0 32m ceph ceph-mon-check-84c94dc8ff-wgblt 1/1 Running 0 32m ceph ceph-mon-keyring-generator-rln66 0/1 Completed 0 32m ceph ceph-mon-lv7hv 2/2 Running 0 32m ceph ceph-osd-default-83945928-xl2g5 2/2 Running 0 29m ceph ceph-osd-keyring-generator-zn6dg 0/1 Completed 0 32m ceph ceph-rbd-pool-t7b8d 0/1 Completed 0 21m ceph ceph-rbd-provisioner-86c99578d8-2689g 1/1 Running 0 21m ceph ceph-rbd-provisioner-86c99578d8-jtfd5 1/1 Running 0 21m ceph ceph-rgw-694b44bd5d-ckv8v 0/1 Running 6 21m ceph ceph-rgw-keyring-generator-chlhr 0/1 Completed 0 32m ceph ceph-storage-keys-generator-5g58r 0/1 Completed 0 32m ceph ingress-65dc849968-68nfm 1/1 Running 0 32m ceph ingress-65dc849968-gfwqq 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-jx8tb 1/1 Running 0 32m ceph ingress-error-pages-768bd7c654-kfd42 1/1 Running 0 32m kube-system auxiliary-etcd-radio-st-11 3/3 Running 0 39m kube-system bootstrap-armada-radio-st-11 4/4 Running 0 39m kube-system calico-etcd-anchor-rvghv 1/1 Running 0 37m kube-system calico-etcd-radio-st-11 1/1 Running 0 37m kube-system calico-kube-policy-controllers-5df8bcbfc6-swxn4 1/1 Running 0 37m kube-system calico-node-s9qfh 2/2 Running 0 37m kube-system calico-settings-ljc9s 0/1 Completed 0 37m kube-system coredns-5545b74458-6kmmf 1/1 Running 0 36m kube-system coredns-5545b74458-nfqwq 1/1 Running 0 36m kube-system haproxy-anchor-9zh6b 1/1 Running 0 34m kube-system haproxy-radio-st-11 1/1 Running 1 34m kube-system ingress-error-pages-5ccf96bf7d-2mzsl 1/1 Running 0 32m kube-system ingress-error-pages-5ccf96bf7d-x9p64 1/1 Running 0 32m kube-system ingress-kqxck 1/1 Running 0 32m kube-system kubernetes-apiserver-anchor-ppv9m 1/1 Running 0 34m kube-system kubernetes-apiserver-radio-st-11 1/1 Running 0 32m kube-system kubernetes-controller-manager-anchor-m2mm4 1/1 Running 0 33m kube-system kubernetes-controller-manager-radio-st-11 1/1 Running 0 33m kube-system kubernetes-etcd-anchor-v7nr9 1/1 Running 0 36m kube-system kubernetes-etcd-radio-st-11 1/1 Running 0 34m kube-system kubernetes-proxy-86gmf 1/1 Running 0 38m kube-system kubernetes-scheduler-anchor-dztff 1/1 Running 0 33m kube-system kubernetes-scheduler-radio-st-11 1/1 Running 0 33m ucp ceph-namespace-client-key-generator-tnng5 0/1 Completed 0 5m ucp ingress-6cd5b89d5d-2pw7x 1/1 Running 0 5m ucp ingress-6cd5b89d5d-z74xt 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-24rjr 1/1 Running 0 5m ucp ingress-error-pages-6bff886f96-qvbmt 1/1 Running 0 5m ucp mariadb-ingress-74f744b54c-n7wzt 0/1 Running 0 4m ucp mariadb-ingress-error-pages-5dc7dd974c-lbdh4 1/1 Running 0 4m ucp mariadb-server-0 0/1 Pending 0 4m 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller [-] Error while installing release airship-ucp-mariadb: grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller Traceback (most recent call last): 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller metadata=self.metadata) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.523 2392 ERROR armada.handlers.tiller 2018-09-03 15:40:50.635 2392 ERROR armada.cli [-] Caught internal exception: armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 401, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli metadata=self.metadata) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 487, in __call__ 2018-09-03 15:40:50.635 2392 ERROR armada.cli return _end_unary_response_blocking(state, call, False, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/grpc/_channel.py", line 437, in _end_unary_response_blocking 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise _Rendezvous(state, None, None, deadline) 2018-09-03 15:40:50.635 2392 ERROR armada.cli grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with (StatusCode.UNKNOWN, release airship-ucp-mariadb failed: timed out waiting for the condition)> 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli During handling of the above exception, another exception occurred: 2018-09-03 15:40:50.635 2392 ERROR armada.cli 2018-09-03 15:40:50.635 2392 ERROR armada.cli Traceback (most recent call last): 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/__init__.py", line 39, in safe_invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli self.invoke() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/cli/apply.py", line 217, in invoke 2018-09-03 15:40:50.635 2392 ERROR armada.cli resp = armada.sync() 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/armada.py", line 480, in sync 2018-09-03 15:40:50.635 2392 ERROR armada.cli timeout=timer) 2018-09-03 15:40:50.635 2392 ERROR armada.cli File "/usr/local/lib/python3.5/site-packages/armada/handlers/tiller.py", line 414, in install_release 2018-09-03 15:40:50.635 2392 ERROR armada.cli raise ex.ReleaseException(release, status, 'Install') 2018-09-03 15:40:50.635 2392 ERROR armada.cli armada.exceptions.tiller_exceptions.ReleaseException: Failed to Install release: airship-ucp-mariadb - Tiller Message: b'Release "airship-ucp-mariadb" failed: timed out waiting for the condition' 2018-09-03 15:40:50.635 2392 ERROR armada.cli ^[[C 2018-09-03 15:41:04.365 3391 INFO armada.handlers.armada [-] Performing pre-flight operations. 2018-09-03 15:41:04.529 3391 INFO armada.handlers.armada [-] Cloning repo: https://urldefense.proofpoint.com/v2/url?u=https-3A__git.openstack.org_openstack_airship-2Dpromenade&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=MyMpkoXeJDDM5X1b0oakc6awcXcRf74kWEKFp5iQp9w&s=6DCFL5kcvZL7DFfRT81Zbyi6wbxOwwNQCel0W4pLQ8o&e= from branch: f60f6d7a8569c5006d32c44c27f4584f10ffe57a _______________________________________________ Airship-discuss mailing list Airship-discuss at lists.airshipit.org https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.airshipit.org_cgi-2Dbin_mailman_listinfo_airship-2Ddiscuss&d=DwIGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=MyMpkoXeJDDM5X1b0oakc6awcXcRf74kWEKFp5iQp9w&s=DzkWxm3aSJdAH_c6Kq0pn2OJ_pEbX15oIVdMlklUCs4&e= From ks3019 at att.com Fri Sep 7 19:27:47 2018 From: ks3019 at att.com (SKELS, KASPARS) Date: Fri, 7 Sep 2018 19:27:47 +0000 Subject: [Airship-discuss] [docs] Airship Treasuremap Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC90BEE6EC8@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi all, there are now site authoring and deployment documentation published for Airship https://airship-treasuremap.readthedocs.io/en/latest/ The source of the docs is available at https://github.com/openstack/airship-treasuremap/tree/master/docs Feel free to provide feedback/issues, may also use the storyboard https://storyboard.openstack.org/#!/project/openstack/airship-treasuremap Cheers, Kaspars -------------- next part -------------- An HTML attachment was scrubbed... URL: From ildiko.vancsa at gmail.com Fri Sep 7 20:52:55 2018 From: ildiko.vancsa at gmail.com (Ildiko Vancsa) Date: Fri, 7 Sep 2018 14:52:55 -0600 Subject: [Airship-discuss] Edge sessions and joint meeting at the Stein PTG Message-ID: Hi, I would like to draw your attention to the edge related sessions next week at the PTG which includes a joint session with Airship on Tuesday in the afternoon to explore deployment options for edge use cases. The Edge Computing Group is meeting all day Tuesday in Ballroom A[1] from 9am. The group is planning to talk about deployment options including Airship from 2:30pm - 4pm in the Edge Group room: https://etherpad.openstack.org/p/edge-deployment-options-stein-ptg For the whole agenda please see the following etherpad: https://etherpad.openstack.org/p/EdgeComputingGroupPTG4 Besides that you might also be interested in checking out some of the StarlingX sessions. The team is meeting all day Wednesday in Winter Park[1] from 9am, for their full agenda please see the following etherpad: https://etherpad.openstack.org/p/stx-PTG-agenda Please let me know if you have any questions. Thanks and Best Regards, Ildikó (IRC: ildikov) [1] https://web14.openstack.org/assets/ptg/Denver-map.pdf From jimmy at openstack.org Mon Sep 17 16:13:47 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 17 Sep 2018 11:13:47 -0500 Subject: [Airship-discuss] Forum Topic Submission Period Message-ID: <5B9FD2BB.3060806@openstack.org> Hello Everyone! The Forum Topic Submission session started September 12 and will run through September 26th. Now is the time to wrangle the topics you gathered during your Brainstorming Phase and start pushing forum topics through. Don't rely only on a PTL to make the agenda... step on up and place the items you consider important front and center. As you may have noticed on the Forum Wiki (https://wiki.openstack.org/wiki/Forum), we're reusing the normal CFP tool this year. We did our best to remove Summit specific language, but if you notice something, just know that you are submitting to the Forum. URL is here: https://www.openstack.org/summit/berlin-2018/call-for-presentations Looking forward to seeing everyone's submissions! If you have questions or concerns about the process, please don't hesitate to reach out. Cheers, Jimmy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Tue Sep 18 22:40:27 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 18 Sep 2018 17:40:27 -0500 Subject: [Airship-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> References: <5B9FD2BB.3060806@openstack.org> <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> Message-ID: <5BA17EDB.5060701@openstack.org> Hey Matt, Matt Riedemann wrote: > > Just a process question. Good question. > I submitted a presentation for the normal marketing blitz part of the > summit which wasn't accepted (I'm still dealing with this emotionally, > btw...) If there's anything I can do... > but when I look at the CFP link for Forum topics, my thing shows up > there as "Received" so does that mean my non-Forum-at-all submission > is now automatically a candidate for the Forum because that would not > be my intended audience (only suits and big wigs please). Forum Submissions would be considered separate and non-Forum submissions will not be considered for the Forum. The submission process is based on the track you submit to and, in the case of the Forum, we separate this track out from the rest of the submission process. If you think there is still something funky, send me a note via speakersupport at openstack.org or jimmy at openstack.org and I'll work through it with you. Cheers, Jimmy From bluejay.ahn at gmail.com Wed Sep 19 04:59:36 2018 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Wed, 19 Sep 2018 13:59:36 +0900 Subject: [Airship-discuss] Effort to pin down Design Meeting Time Message-ID: Hi This is Jaesuk Ahn from SKT. I was really trying to find this week's open design meeting time. I know the meeting happens on Thursday either on AM or PM time. I searched airship-discuss mailing archive, and read through the following two etherpads, still not able to see the exact time for this week. Maybe it is me not able to find the information exists somewhere. - https://etherpad.openstack.org/p/airship-team-meeting-agenda - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions I was going to introduce open flow based network switch configuration leveraging ONOS technology. I must ask SDN team to join and introduce what skt has in this domain. This requires advance notification for SDN team so that they can prepare. More importantly, meeting time is either very early in the morning or late at night for us here in Korea, we really need to know time in advance. However, unfortunately, since I am not able to find the exact meeting information, and this is already Wednesday afternoon here in Korea, I am afraid skt will not be able to present this week. Next week is a big holiday week in Korea, so not next week. I will try to schedule our presence in open design meeting sometime early in October. Thank you. -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgu at suse.com Wed Sep 19 05:31:24 2018 From: jgu at suse.com (James Gu) Date: Tue, 18 Sep 2018 22:31:24 -0700 Subject: [Airship-discuss] Effort to pin down Design Meeting Time In-Reply-To: References: Message-ID: Hi, FWIW, the next design meeting on my calendar shows at 7am U.S. pacific daylight saving time this Thursday. James Sent from my iPhone > On Sep 18, 2018, at 9:59 PM, Jaesuk Ahn wrote: > > Hi > > This is Jaesuk Ahn from SKT. I was really trying to find this week's open design meeting time. I know the meeting happens on Thursday either on AM or PM time. > > I searched airship-discuss mailing archive, and read through the following two etherpads, still not able to see the exact time for this week. Maybe it is me not able to find the information exists somewhere. > - https://etherpad.openstack.org/p/airship-team-meeting-agenda > - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions > > I was going to introduce open flow based network switch configuration leveraging ONOS technology. I must ask SDN team to join and introduce what skt has in this domain. This requires advance notification for SDN team so that they can prepare. More importantly, meeting time is either very early in the morning or late at night for us here in Korea, we really need to know time in advance. > > However, unfortunately, since I am not able to find the exact meeting information, and this is already Wednesday afternoon here in Korea, I am afraid skt will not be able to present this week. Next week is a big holiday week in Korea, so not next week. > > I will try to schedule our presence in open design meeting sometime early in October. > > Thank you. > > > -- > Jaesuk Ahn, Team Lead > Virtualization SW Lab, SW R&D Center > > SK Telecom > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Sep 19 11:43:51 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 19 Sep 2018 11:43:51 +0000 Subject: [Airship-discuss] Effort to pin down Design Meeting Time In-Reply-To: References: Message-ID: <77141456-C659-4F22-98F4-379F9BB11099@att.com> Jaesuk, Lets schedule the meeting for Thursday Oct 4, at 7 EST for that meeting. Should be early am in Korea. Will schedule the Design Call at that time that day. Regards Rodolfo Pacheco Home/Office 732 5337671 From: Jaesuk Ahn Date: Wednesday, September 19, 2018 at 1:00 AM To: "airship-discuss at lists.airshipit.org" Subject: [Airship-discuss] Effort to pin down Design Meeting Time Hi This is Jaesuk Ahn from SKT. I was really trying to find this week's open design meeting time. I know the meeting happens on Thursday either on AM or PM time. I searched airship-discuss mailing archive, and read through the following two etherpads, still not able to see the exact time for this week. Maybe it is me not able to find the information exists somewhere. - https://etherpad.openstack.org/p/airship-team-meeting-agenda - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions I was going to introduce open flow based network switch configuration leveraging ONOS technology. I must ask SDN team to join and introduce what skt has in this domain. This requires advance notification for SDN team so that they can prepare. More importantly, meeting time is either very early in the morning or late at night for us here in Korea, we really need to know time in advance. However, unfortunately, since I am not able to find the exact meeting information, and this is already Wednesday afternoon here in Korea, I am afraid skt will not be able to present this week. Next week is a big holiday week in Korea, so not next week. I will try to schedule our presence in open design meeting sometime early in October. Thank you. -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Sep 19 11:52:49 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 19 Sep 2018 11:52:49 +0000 Subject: [Airship-discuss] Effort to pin down Design Meeting Time In-Reply-To: <77141456-C659-4F22-98F4-379F9BB11099@att.com> References: <77141456-C659-4F22-98F4-379F9BB11099@att.com> Message-ID: <5834F1C5-F70B-4BB8-A2D3-15725EA6D64C@att.com> 7 PM EST to be precise. Regards Rodolfo Pacheco Home/Office 732 5337671 From: "PACHECO, RODOLFO J" Date: Wednesday, September 19, 2018 at 7:44 AM To: Jaesuk Ahn , "airship-discuss at lists.airshipit.org" Subject: Re: [Airship-discuss] Effort to pin down Design Meeting Time ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Jaesuk, Lets schedule the meeting for Thursday Oct 4, at 7 EST for that meeting. Should be early am in Korea. Will schedule the Design Call at that time that day. Regards Rodolfo Pacheco Home/Office 732 5337671 From: Jaesuk Ahn Date: Wednesday, September 19, 2018 at 1:00 AM To: "airship-discuss at lists.airshipit.org" Subject: [Airship-discuss] Effort to pin down Design Meeting Time Hi This is Jaesuk Ahn from SKT. I was really trying to find this week's open design meeting time. I know the meeting happens on Thursday either on AM or PM time. I searched airship-discuss mailing archive, and read through the following two etherpads, still not able to see the exact time for this week. Maybe it is me not able to find the information exists somewhere. - https://etherpad.openstack.org/p/airship-team-meeting-agenda - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions I was going to introduce open flow based network switch configuration leveraging ONOS technology. I must ask SDN team to join and introduce what skt has in this domain. This requires advance notification for SDN team so that they can prepare. More importantly, meeting time is either very early in the morning or late at night for us here in Korea, we really need to know time in advance. However, unfortunately, since I am not able to find the exact meeting information, and this is already Wednesday afternoon here in Korea, I am afraid skt will not be able to present this week. Next week is a big holiday week in Korea, so not next week. I will try to schedule our presence in open design meeting sometime early in October. Thank you. -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Wed Sep 19 13:13:24 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 19 Sep 2018 08:13:24 -0500 Subject: [Airship-discuss] [openstack-dev] Forum Topic Submission Period In-Reply-To: References: <5B9FD2BB.3060806@openstack.org> <5b5a669d-144c-bcc2-306c-c6410ef705ef@gmail.com> <5BA17EDB.5060701@openstack.org> Message-ID: <5BA24B74.8010301@openstack.org> Sylvain Bauza wrote: > > > Le mer. 19 sept. 2018 à 00:41, Jimmy McArthur > a écrit : SNIP > > > Same as I do :-) Unrelated point, for the first time in all the > Summits I know, I wasn't able to know the track chairs for a specific > track. Ideally, I'd love to reach them in order to know what they > disliked in my proposal. They were listed on an Etherpad that was listed under Presentation Selection Process in the CFP navigation. That has since been overwritten w/ Forum Selection Process, so let me try to dig that up. We publish the Track Chairs every year. > SNIP > > I have another question, do you know why we can't propose a Forum > session with multiple speakers ? Is this a bug or an expected > behaviour ? In general, there is only one moderator for a Forum > session, but in the past, I clearly remember we had some sessions that > were having multiple moderators (for various reasons). Correct. Forum sessions aren't meant to have speakers like a normal presentation. They are all set up parliamentary style w/ one or more moderators. However, the moderator can manage the room any way they'd like. If you want to promote the people that will be in the room, this can be added to the abstract. > > -Sylvain > > > Cheers, > Jimmy > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: > OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Sep 19 16:24:10 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 19 Sep 2018 16:24:10 +0000 Subject: [Airship-discuss] Airship - Open Design Call - AM EST Call Message-ID: <99088997CCAD0C4BA20008FD094344962723EB68@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Thursday, September 20, 2018 10:00 AM-11:00 AM. (UTC-05:00) Eastern Time (US & Canada) Where: https://bluejeans.com/421706689 *~*~*~*~*~*~*~*~*~* REMINDER ** We will use these ether pad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ To join the Meeting: https://bluejeans.com/421706689 To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 421706689 To join via phone : 1) Dial: +1.408.317.9254 (BlueJeans U.S. Toll) +1.866.226.4650 (US Toll Free) (see all numbers - http://bluejeans.com/numbers) 2) Enter Conference ID : 421706689 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2732 bytes Desc: not available URL: From rp2723 at att.com Fri Sep 21 16:56:45 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 21 Sep 2018 16:56:45 +0000 Subject: [Airship-discuss] Requesting comments of specification for Drydock - Introduce a RedFish based OOB Driver Message-ID: We haven’t formalized how we make folks aware of specifications in flight, using the discussion mailing list might or might not be the correct path. Welcome to suggestions. Regardless, For the Storyboard item Drydock - Introduce a RedFish based OOB Driver Specification at : https://review.openstack.org/#/c/584015/ There is a specification in place, please take some time to comment so we can move it forward. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Mon Sep 24 15:19:59 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Mon, 24 Sep 2018 10:19:59 -0500 Subject: [Airship-discuss] [Forum] Forum Topic Submission Period - Time Running out! Message-ID: <5BA9009F.6000405@openstack.org> Just a reminder that there is a little more than 60 hours left to submit your forum topics. Please make haste to the Forum submission tool: https://www.openstack.org/summit/berlin-2018/call-for-presentations Cheers, Jimmy > Jimmy McArthur > September 17, 2018 at 11:13 AM > Hello Everyone! > > The Forum Topic Submission session started September 12 and will run > through September 26th. Now is the time to wrangle the topics you > gathered during your Brainstorming Phase and start pushing forum > topics through. Don't rely only on a PTL to make the agenda... step on > up and place the items you consider important front and center. > > As you may have noticed on the Forum Wiki > (https://wiki.openstack.org/wiki/Forum), we're reusing the normal CFP > tool this year. We did our best to remove Summit specific language, > but if you notice something, just know that you are submitting to the > Forum. URL is here: > > https://www.openstack.org/summit/berlin-2018/call-for-presentations > > Looking forward to seeing everyone's submissions! > > If you have questions or concerns about the process, please don't > hesitate to reach out. > > Cheers, > Jimmy > > _______________________________________________ > Openstack-track-chairs mailing list > Openstack-track-chairs at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Sep 25 13:07:12 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 25 Sep 2018 13:07:12 +0000 Subject: [Airship-discuss] Airship - Open Design Call - AM EST Call Message-ID: <99088997CCAD0C4BA20008FD094344962725090E@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Occurs on Thursday every other week from 11:00 AM to 12:00 PM effective 8/30/2018 until 2/28/2019. (UTC-05:00) Eastern Time (US & Canada) Where: https://bluejeans.com/421706689 *~*~*~*~*~*~*~*~*~* We will use these ether pad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ To join the Meeting: https://bluejeans.com/421706689 To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 421706689 To join via phone : 1) Dial: +1.408.317.9254 (BlueJeans U.S. Toll) +1.866.226.4650 (US Toll Free) (see all numbers - http://bluejeans.com/numbers) 2) Enter Conference ID : 421706689 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2345 bytes Desc: not available URL: From rp2723 at att.com Tue Sep 25 13:10:02 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 25 Sep 2018 13:10:02 +0000 Subject: [Airship-discuss] Airship - Open Design Call - PM EST Call Message-ID: <99088997CCAD0C4BA20008FD09434496272509AB@MISOUT7MSGUSRDI.ITServices.sbc.com> When: Occurs on Thursday every other week from 5:00 PM to 6:00 PM effective 9/6/2018 until 3/6/2019. (UTC-05:00) Eastern Time (US & Canada) Where: https://bluejeans.com/421706689 *~*~*~*~*~*~*~*~*~* We will use these ether pad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ To join the Meeting: https://bluejeans.com/421706689 To join via Room System: Video Conferencing System: bjn.vc -or-199.48.152.152 Meeting ID : 421706689 To join via phone : 1) Dial: +1.408.317.9254 (BlueJeans U.S. Toll) +1.866.226.4650 (US Toll Free) (see all numbers - http://bluejeans.com/numbers) 2) Enter Conference ID : 421706689 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2343 bytes Desc: not available URL: From venugopal at kanumalla.com Tue Sep 25 20:57:04 2018 From: venugopal at kanumalla.com (Venugopal Kanumalla) Date: Tue, 25 Sep 2018 15:57:04 -0500 Subject: [Airship-discuss] Spyglass - Config data generator for AirShip Message-ID: Hello, We would like to discuss the SpyGlass Toolkit that will help extract site information from across multiple applications (excel, restful APIs et al) here is the outline of the proposal thats published. https://review.openstack.org/#/c/605227/1/specs/approved/data_config_generator.rst Appreciate any comments to move this quickly forward. Regards Venu -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Sep 25 21:30:28 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 25 Sep 2018 21:30:28 +0000 Subject: [Airship-discuss] Spyglass - Config data generator for AirShip In-Reply-To: References: Message-ID: <8A40CEB9-4215-46CA-92A1-7610B625A479@att.com> Please add request for discussion on the Design Call at https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions I already added these specifications for this Thursday call. Regards Rodolfo Pacheco Home/Office 732 5337671 From: Venugopal Kanumalla Date: Tuesday, September 25, 2018 at 4:57 PM To: "airship-discuss at lists.airshipit.org" , "purnendu at gmail.com" Cc: "mail2hemanth.n at gmail.com" , Gurpreet Singh Subject: [Airship-discuss] Spyglass - Config data generator for AirShip Hello, We would like to discuss the SpyGlass Toolkit that will help extract site information from across multiple applications (excel, restful APIs et al) here is the outline of the proposal thats published. https://review.openstack.org/#/c/605227/1/specs/approved/data_config_generator.rst Appreciate any comments to move this quickly forward. Regards Venu -------------- next part -------------- An HTML attachment was scrubbed... URL: From bluejay.ahn at gmail.com Wed Sep 26 08:41:27 2018 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Wed, 26 Sep 2018 17:41:27 +0900 Subject: [Airship-discuss] Effort to pin down Design Meeting Time In-Reply-To: <5834F1C5-F70B-4BB8-A2D3-15725EA6D64C@att.com> References: <77141456-C659-4F22-98F4-379F9BB11099@att.com> <5834F1C5-F70B-4BB8-A2D3-15725EA6D64C@att.com> Message-ID: I finally converted suggested meeting time to Korean Standard Time. As you said, for this specific meeting you suggested, 7PM EST is good time to have meeting for us. (It is 9AM here) Unfortunately, I will be on personal vacation on that day. Cloud we please reschedule this meeting later than Oct. 9th? Additionally, I would like to point out that the current design meeting time is either at midnight or 6am here in Korea, which make it very difficult for us to attend. (midnight would not be that bad, but 6am is difficult time to join) Would it be possible to discuss this meeting time issue? I know choosing a meeting time among America, Europe, and Asia is almost impossible task to do, however, 6am is too early for us. Thank you. On Wed, Sep 19, 2018 at 8:52 PM PACHECO, RODOLFO J wrote: > 7 PM EST to be precise. > > > > Regards > > > > *Rodolfo Pacheco* > > > > *Home/Office* 732 5337671 <(732)%20533-7671> > > > > *From: *"PACHECO, RODOLFO J" > *Date: *Wednesday, September 19, 2018 at 7:44 AM > *To: *Jaesuk Ahn , " > airship-discuss at lists.airshipit.org" > *Subject: *Re: [Airship-discuss] Effort to pin down Design Meeting Time > > > > ****Security Advisory:* This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > Jaesuk, > > > > Lets schedule the meeting for Thursday Oct 4, at 7 EST for that meeting. > > Should be early am in Korea. > > > > Will schedule the Design Call at that time that day. > > > > Regards > > > > *Rodolfo Pacheco* > > > > *Home/Office* 732 5337671 <(732)%20533-7671> > > > > *From: *Jaesuk Ahn > *Date: *Wednesday, September 19, 2018 at 1:00 AM > *To: *"airship-discuss at lists.airshipit.org" < > airship-discuss at lists.airshipit.org> > *Subject: *[Airship-discuss] Effort to pin down Design Meeting Time > > > > Hi > > > > This is Jaesuk Ahn from SKT. I was really trying to find this week's open > design meeting time. I know the meeting happens on Thursday either on AM or > PM time. > > > > I searched airship-discuss mailing archive, and read through the following > two etherpads, still not able to see the exact time for this week. Maybe it > is me not able to find the information exists somewhere. > > - https://etherpad.openstack.org/p/airship-team-meeting-agenda > > > - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions > > > > > I was going to introduce open flow based network switch configuration > leveraging ONOS technology. I must ask SDN team to join and introduce what > skt has in this domain. This requires advance notification for SDN team so > that they can prepare. More importantly, meeting time is either very early > in the morning or late at night for us here in Korea, we really need to > know time in advance. > > > > However, unfortunately, since I am not able to find the exact meeting > information, and this is already Wednesday afternoon here in Korea, I am > afraid skt will not be able to present this week. Next week is a big > holiday week in Korea, so not next week. > > > > I will try to schedule our presence in open design meeting sometime early > in October. > > > > Thank you. > > > > > > -- > > Jaesuk Ahn, Team Lead > Virtualization SW Lab, SW R&D Center > > SK Telecom > -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Sep 26 14:20:32 2018 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 26 Sep 2018 14:20:32 +0000 Subject: [Airship-discuss] Effort to pin down Design Meeting Time In-Reply-To: References: <77141456-C659-4F22-98F4-379F9BB11099@att.com> <5834F1C5-F70B-4BB8-A2D3-15725EA6D64C@att.com> Message-ID: Jaesuk Sure, let me know if Oct 16 is good at 7 EST for that discussion. We can discuss moving the meeting time again, would making the late Thursday 6 or 6:30 PM EST work? Regards Rodolfo Pacheco Home/Office 732 5337671 From: Jaesuk Ahn Date: Wednesday, September 26, 2018 at 4:41 AM To: "PACHECO, RODOLFO J" Cc: "airship-discuss at lists.airshipit.org" Subject: Re: [Airship-discuss] Effort to pin down Design Meeting Time I finally converted suggested meeting time to Korean Standard Time. As you said, for this specific meeting you suggested, 7PM EST is good time to have meeting for us. (It is 9AM here) Unfortunately, I will be on personal vacation on that day. Cloud we please reschedule this meeting later than Oct. 9th? Additionally, I would like to point out that the current design meeting time is either at midnight or 6am here in Korea, which make it very difficult for us to attend. (midnight would not be that bad, but 6am is difficult time to join) Would it be possible to discuss this meeting time issue? I know choosing a meeting time among America, Europe, and Asia is almost impossible task to do, however, 6am is too early for us. Thank you. On Wed, Sep 19, 2018 at 8:52 PM PACHECO, RODOLFO J > wrote: 7 PM EST to be precise. Regards Rodolfo Pacheco Home/Office 732 5337671 From: "PACHECO, RODOLFO J" > Date: Wednesday, September 19, 2018 at 7:44 AM To: Jaesuk Ahn >, "airship-discuss at lists.airshipit.org" > Subject: Re: [Airship-discuss] Effort to pin down Design Meeting Time ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Jaesuk, Lets schedule the meeting for Thursday Oct 4, at 7 EST for that meeting. Should be early am in Korea. Will schedule the Design Call at that time that day. Regards Rodolfo Pacheco Home/Office 732 5337671 From: Jaesuk Ahn > Date: Wednesday, September 19, 2018 at 1:00 AM To: "airship-discuss at lists.airshipit.org" > Subject: [Airship-discuss] Effort to pin down Design Meeting Time Hi This is Jaesuk Ahn from SKT. I was really trying to find this week's open design meeting time. I know the meeting happens on Thursday either on AM or PM time. I searched airship-discuss mailing archive, and read through the following two etherpads, still not able to see the exact time for this week. Maybe it is me not able to find the information exists somewhere. - https://etherpad.openstack.org/p/airship-team-meeting-agenda - https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions I was going to introduce open flow based network switch configuration leveraging ONOS technology. I must ask SDN team to join and introduce what skt has in this domain. This requires advance notification for SDN team so that they can prepare. More importantly, meeting time is either very early in the morning or late at night for us here in Korea, we really need to know time in advance. However, unfortunately, since I am not able to find the exact meeting information, and this is already Wednesday afternoon here in Korea, I am afraid skt will not be able to present this week. Next week is a big holiday week in Korea, so not next week. I will try to schedule our presence in open design meeting sometime early in October. Thank you. -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -- Jaesuk Ahn, Team Lead Virtualization SW Lab, SW R&D Center SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From nchase at mirantis.com Thu Sep 27 05:12:19 2018 From: nchase at mirantis.com (Nick Chase) Date: Thu, 27 Sep 2018 01:12:19 -0400 Subject: [Airship-discuss] User docs? Message-ID: Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it pretty easily. I think. I say "I think" because I'm not quite sure where to go from there. :) . Is there a "getting started" doc somewhere that talks about how to actually use it? If not, is there someone who could pass me a few tips? Thanks... ---- Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Sep 27 07:49:44 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 27 Sep 2018 09:49:44 +0200 Subject: [Airship-discuss] User docs? In-Reply-To: References: Message-ID: Hello Nick, Thanks for trying Airship-in-a-Bottle. Depending on your target goals, you may want either to use specific components of Airship to achieve specific results, or you may use them all together as Undercloud Platform to deploy OpenStack in OpenStack-Helm variant (containerized OpenStack components, running under Kubernetes supervision). Check out Airship Treasuremap: - https://airship-treasuremap.readthedocs.io/ - this is the main documentation - https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.ht ml - this is the Site Authoring and Deployment guide for a full-fleged deployment on bare-metal servers Feel free to reach out to us via mailing list or at irc://#airshipit at freenode. Best regards, -- Roman Gorshunov > On 27 Sep 2018, at 07:12, Nick Chase wrote: > > Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it pretty easily. I think. > > I say "I think" because I'm not quite sure where to go from there. :) . Is there a "getting started" doc somewhere that talks about how to actually use it? If not, is there someone who could pass me a few tips? > > Thanks... > > ---- Nick > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From nchase at mirantis.com Thu Sep 27 08:03:20 2018 From: nchase at mirantis.com (Nick Chase) Date: Thu, 27 Sep 2018 04:03:20 -0400 Subject: [Airship-discuss] User docs? In-Reply-To: References: Message-ID: Thanks, Roman! Basically at this point I just want to get an idea of how Airship works. I had seen those docs, but while they give a great overview of how the technology works, what I really need is a "Start here, and do this" type of thing. :) "Deploy OpenStack" is probably a good goal for this; from there I know what I'm doing. :) . So how would I get from "OK, Airship is (seemingly) running." to "Great, here's Horizon"? Thanks... ---- Nick On Thu, Sep 27, 2018 at 3:49 AM Roman Gorshunov wrote: > Hello Nick, > Thanks for trying Airship-in-a-Bottle. > > Depending on your target goals, you may want either to use specific > components > of Airship to achieve specific results, or you may use them all together > as > Undercloud Platform to deploy OpenStack in OpenStack-Helm variant > (containerized OpenStack components, running under Kubernetes supervision). > > Check out Airship Treasuremap: > - https://airship-treasuremap.readthedocs.io/ - this is the main > documentation > - > > https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.ht > ml > > - this is the Site Authoring and Deployment guide for a full-fleged > deployment on bare-metal servers > > Feel free to reach out to us via mailing list or at > irc://#airshipit at freenode. > > Best regards, > -- > Roman Gorshunov > > > > On 27 Sep 2018, at 07:12, Nick Chase wrote: > > > > Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it > pretty easily. I think. > > > > I say "I think" because I'm not quite sure where to go from there. :) . > Is there a "getting started" doc somewhere that talks about how to actually > use it? If not, is there someone who could pass me a few tips? > > > > Thanks... > > > > ---- Nick > > _______________________________________________ > > 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 cedricable at gmail.com Thu Sep 27 08:21:21 2018 From: cedricable at gmail.com (Cedric M) Date: Thu, 27 Sep 2018 10:21:21 +0200 Subject: [Airship-discuss] User docs? In-Reply-To: References: Message-ID: I have exactly the same type of request. I installed airship in a bottle but iam lost from where to start after installation. Any dashboard accessible ? cedric On Thu, Sep 27, 2018 at 10:03 AM Nick Chase wrote: > Thanks, Roman! Basically at this point I just want to get an idea of how > Airship works. I had seen those docs, but while they give a great overview > of how the technology works, what I really need is a "Start here, and do > this" type of thing. :) > > "Deploy OpenStack" is probably a good goal for this; from there I know > what I'm doing. :) . So how would I get from "OK, Airship is (seemingly) > running." to "Great, here's Horizon"? > > Thanks... > > ---- Nick > > On Thu, Sep 27, 2018 at 3:49 AM Roman Gorshunov wrote: > >> Hello Nick, >> Thanks for trying Airship-in-a-Bottle. >> >> Depending on your target goals, you may want either to use specific >> components >> of Airship to achieve specific results, or you may use them all together >> as >> Undercloud Platform to deploy OpenStack in OpenStack-Helm variant >> (containerized OpenStack components, running under Kubernetes >> supervision). >> >> Check out Airship Treasuremap: >> - https://airship-treasuremap.readthedocs.io/ - this is the main >> documentation >> - >> >> https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.ht >> ml >> >> - this is the Site Authoring and Deployment guide for a full-fleged >> deployment on bare-metal servers >> >> Feel free to reach out to us via mailing list or at >> irc://#airshipit at freenode. >> >> Best regards, >> -- >> Roman Gorshunov >> >> >> > On 27 Sep 2018, at 07:12, Nick Chase wrote: >> > >> > Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it >> pretty easily. I think. >> > >> > I say "I think" because I'm not quite sure where to go from there. :) . >> Is there a "getting started" doc somewhere that talks about how to actually >> use it? If not, is there someone who could pass me a few tips? >> > >> > Thanks... >> > >> > ---- Nick >> > _______________________________________________ >> > Airship-discuss mailing list >> > Airship-discuss at lists.airshipit.org >> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> >> _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Sep 27 11:56:44 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 27 Sep 2018 13:56:44 +0200 Subject: [Airship-discuss] User docs? In-Reply-To: References: Message-ID: Hello Cedric, When Airship in a Bottle run is complete, one of the last messages says that now you can ssh to the test VM, which is deployed on your newly installed OpenStack. Something like this: # ssh -i id_rsa cirros at 172.24.8.12 This would be tiny Cirros virtual machine. There is OpenStack Horizon dashboard running. You can access it by exposing service/horizon-in in Kubernetes, e.g.: # kubectl -n openstack expose service/horizon-int --type=NodePort \ --name=horizon-dashboard -o json | jq '.spec.ports[0].nodePort' 31348 Now you can access OpenStack Horizon dashboard on http://ip-of-your-vm:31348/. Use the following default credentials: domain: default user: admin password: password You can also run various OpenStack commands, using the wrapper available in /root/deploy/airship-in-a-bottle/manifests/dev_single_node directory once the installation completes, e.g.: # ./run_openstack_cli.sh stack list ... Best regards, -- Roman Gorshunov On Thu, Sep 27, 2018 at 10:21 AM Cedric M wrote: > > I have exactly the same type of request. > I installed airship in a bottle but iam lost from where to start after installation. > Any dashboard accessible ? > > cedric > > On Thu, Sep 27, 2018 at 10:03 AM Nick Chase wrote: >> >> Thanks, Roman! Basically at this point I just want to get an idea of how Airship works. I had seen those docs, but while they give a great overview of how the technology works, what I really need is a "Start here, and do this" type of thing. :) >> >> "Deploy OpenStack" is probably a good goal for this; from there I know what I'm doing. :) . So how would I get from "OK, Airship is (seemingly) running." to "Great, here's Horizon"? >> >> Thanks... >> >> ---- Nick >> >> On Thu, Sep 27, 2018 at 3:49 AM Roman Gorshunov wrote: >>> >>> Hello Nick, >>> Thanks for trying Airship-in-a-Bottle. >>> >>> Depending on your target goals, you may want either to use specific components >>> of Airship to achieve specific results, or you may use them all together as >>> Undercloud Platform to deploy OpenStack in OpenStack-Helm variant >>> (containerized OpenStack components, running under Kubernetes supervision). >>> >>> Check out Airship Treasuremap: >>> - https://airship-treasuremap.readthedocs.io/ - this is the main documentation >>> - >>> https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.ht >>> ml - this is the Site Authoring and Deployment guide for a full-fleged >>> deployment on bare-metal servers >>> >>> Feel free to reach out to us via mailing list or at irc://#airshipit at freenode. >>> >>> Best regards, >>> -- >>> Roman Gorshunov >>> >>> >>> > On 27 Sep 2018, at 07:12, Nick Chase wrote: >>> > >>> > Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it pretty easily. I think. >>> > >>> > I say "I think" because I'm not quite sure where to go from there. :) . Is there a "getting started" doc somewhere that talks about how to actually use it? If not, is there someone who could pass me a few tips? >>> > >>> > Thanks... >>> > >>> > ---- Nick >>> > _______________________________________________ >>> > Airship-discuss mailing list >>> > Airship-discuss at lists.airshipit.org >>> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >>> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From paye600 at gmail.com Thu Sep 27 12:06:29 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 27 Sep 2018 14:06:29 +0200 Subject: [Airship-discuss] User docs? In-Reply-To: References: Message-ID: Nick, I've just sent an e-mail with information on how to get to the Horizon dashboard: http://lists.airshipit.org/pipermail/airship-discuss/2018-September/000116.html, and I think I would be able to add this information to the lat output lines of deployment script. The Airship Treasuremap and the Site Authoring and Deployment Guide I have mentioned before would probably be good documents to proceed with, once Airship in a Bottle is up and running, and you have accessed the Horizon dashboard. Best regards, -- Roman Gorshunov On Thu, Sep 27, 2018 at 10:03 AM Nick Chase wrote: > > Thanks, Roman! Basically at this point I just want to get an idea of how Airship works. I had seen those docs, but while they give a great overview of how the technology works, what I really need is a "Start here, and do this" type of thing. :) > > "Deploy OpenStack" is probably a good goal for this; from there I know what I'm doing. :) . So how would I get from "OK, Airship is (seemingly) running." to "Great, here's Horizon"? > > Thanks... > > ---- Nick > > On Thu, Sep 27, 2018 at 3:49 AM Roman Gorshunov wrote: >> >> Hello Nick, >> Thanks for trying Airship-in-a-Bottle. >> >> Depending on your target goals, you may want either to use specific components >> of Airship to achieve specific results, or you may use them all together as >> Undercloud Platform to deploy OpenStack in OpenStack-Helm variant >> (containerized OpenStack components, running under Kubernetes supervision). >> >> Check out Airship Treasuremap: >> - https://airship-treasuremap.readthedocs.io/ - this is the main documentation >> - >> https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.ht >> ml - this is the Site Authoring and Deployment guide for a full-fleged >> deployment on bare-metal servers >> >> Feel free to reach out to us via mailing list or at irc://#airshipit at freenode. >> >> Best regards, >> -- >> Roman Gorshunov >> >> >> > On 27 Sep 2018, at 07:12, Nick Chase wrote: >> > >> > Hey, all. Nice job on Airship-in-a-bottle! I was able to deploy it pretty easily. I think. >> > >> > I say "I think" because I'm not quite sure where to go from there. :) . Is there a "getting started" doc somewhere that talks about how to actually use it? If not, is there someone who could pass me a few tips? >> > >> > Thanks... >> > >> > ---- Nick >> > _______________________________________________ >> > Airship-discuss mailing list >> > Airship-discuss at lists.airshipit.org >> > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss >> From nchase at mirantis.com Thu Sep 27 17:19:20 2018 From: nchase at mirantis.com (Nick Chase) Date: Thu, 27 Sep 2018 13:19:20 -0400 Subject: [Airship-discuss] Postgresql timing out on install Message-ID: So it seems that my problem is that Airship-in-a-bottle is hanging up on install on Postgresql. Helm is timing out on the Postegresql install. Note that this has been running for 2 days. I'm running on VirtualBox with 24GB RAM, 4vCPU, and (I think) 40GB drive, with a clean Ubuntu 16.04. Thanks... ----- Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Sep 27 18:47:42 2018 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 27 Sep 2018 20:47:42 +0200 Subject: [Airship-discuss] Postgresql timing out on install In-Reply-To: References: Message-ID: Nick, I would try to destroy VM, launch a new one, restart the process, and see if it helps. The run takes approximately 1h20min on a VM on my laptop, and whenever I run from scratch - I get it working (for the past few months). sudo -i mkdir -p /root/deploy && cd "$_" git clone https://git.openstack.org/openstack/airship-in-a-bottle cd /root/deploy/airship-in-a-bottle/manifests/dev_single_node ./airship-in-a-bottle.sh In case it still fails, try to collect logs of failing pods/deployments, and post them to https://paste.ubuntu.com/ (it accepts super long text documents). You may also reach out to us at irc://#airshipit at freenode. I'm in EU, and channel becomes more active during US working hours. Someone would definitely tell you what commands to run and what to check. Here is a [WIP] follow-up patch set with additional info being printed on ./airship-in-a-bottle.sh script completion. I will continue working on it tomorrow. https://review.openstack.org/#/c/605827/ Note: vagrant-based launch is broken at the moment, I will check and hopefully fix it later. Best regards, -- Roman Gorshunov On Thu, Sep 27, 2018 at 7:19 PM Nick Chase wrote: > > So it seems that my problem is that Airship-in-a-bottle is hanging up on install on Postgresql. Helm is timing out on the Postegresql install. > > Note that this has been running for 2 days. > > I'm running on VirtualBox with 24GB RAM, 4vCPU, and (I think) 40GB drive, with a clean Ubuntu 16.04. > > Thanks... > > ----- Nick > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From jimmy at openstack.org Fri Sep 28 13:24:34 2018 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 28 Sep 2018 08:24:34 -0500 Subject: [Airship-discuss] OpenStack Summit Forum Submission Process Extended Message-ID: <5BAE2B92.4030409@openstack.org> Hello Everyone We are extended the Forum Submission process through September 30, 11:59pm Pacific (6:59am GMT). We've already gotten a ton of great submissions, but we want to leave the door open through the weekend in case we have any stragglers. Please submit your topics here: https://www.openstack.org/summit/berlin-2018/call-for-presentations If you'd like to review the submissions to date, you can go to https://www.openstack.org/summit/berlin-2018/vote-for-speakers. There is no voting period, this is just so Forum attendees can review the submissions to date. Thank you! Jimmy From jgu at suse.com Fri Sep 28 21:47:11 2018 From: jgu at suse.com (James Gu) Date: Fri, 28 Sep 2018 15:47:11 -0600 Subject: [Airship-discuss] Airship linux distro support In-Reply-To: <5BAE2B92.4030409@openstack.org> References: <5BAE2B92.4030409@openstack.org> Message-ID: <5BAEA15F0200006C0003C1AF@prv-mh.provo.novell.com> Hello, I submitted a spec to enable multiple Linux distro capability in Airship and bring in OpenSUSE support in addition to Ubuntu. The spec is at https://review.openstack.org/#/c/601187 and has received positive feedback from the Airship core team on the direction. We wanted to make the effort known to broader audience through the mailing list and sincerely welcome more developers to join us, review the spec/code and/or implement the feature, expand to other Linux distros such as CentOS etc. Thanks, James -------------- next part -------------- An HTML attachment was scrubbed... URL: