June 2018 - Airship-discuss - lists.airshipit.org

Airship F2F Meeting at PTG Denver - September 2018
by Claire Massey 24 Jul '18

24 Jul '18

Hello Airship team, Myself and other members of the OpenStack Foundation will be working closely with you to provide support and guidance over the coming weeks and months as we work together to organize the project's structure and processes and build out the community. Stay tuned for resources to be shared soon. In the meantime I want to make sure you’re aware of and plan to participate in the PTG (https://www.openstack.org/ptg/ <https://www.openstack.org/ptg/>). It's a 5-day long meeting series that provides face to face time for project teams under the OpenStack Foundation umbrella. The next PTG will be held in Denver, Colorado the week of September 10. This is a great opportunity for the Airship team to meet in person to discuss both project specific items and schedule cross-project collaborative sessions with other participating teams. Airship will have a dedicated spaced reserved to hold a two-day meeting at the PTG, the exact schedule will be announced later. Below you'll find some information from my colleague Kendall on participating teams and administrative info on the PTG. Please make sure you register for the event early (as prices will increase) and have your hotel booked so you don’t miss the discounted rate if you’re planning to attend. Add your name to the following etherpad if you plan on attending: https://etherpad.openstack.org/p/AirshipPTG4 <https://etherpad.openstack.org/p/AirshipPTG4> and from there we can build out the Airship agenda. Feel free to ping me if you have any questions about the information below or about the PTG itself. Thanks, Claire Massey OpenStack Foundation ----------------------------------------------- Hello Everyone! Wanted to give you some updates on PTG4 planning. We have finalized the list of SIGs/ Groups/WGs/Teams that are attending. They are as follows: * Airship * API SIG * Barbican/Security SIG * Blazar * Chef OpenStack * Cinder * Cyborg * Designate * Documentation * Edge Computing Group * First Contact SIG * Glance * Heat * Horizon * Infrastructure * Interop WG * Ironic * Kata * Keystone * Kolla * LOCI * Manila * Masakari * Mistral * Monasca * Neutron * Nova * Octavia * OpenStack Ansible * OpenStack Charms * OpenStack Helm * OpenStackClient * Operator Meetup * Puppet OpenStack * QA * Oslo * Public Cloud WG * Release Management * Requirements * Sahara * Scientific SIG * Self-Healing SIG * SIG-K8s * StarlingX * Swift * OpenStack TC * TripleO * Upgrades SIG * Watcher * Zuul (pending confirmation) Thierry and I are working on placing them into a strawman schedule to reduce conflicts between related or overlapping groups. We should have more on what that will look like and a draft for you all to review in the next few weeks. We also wanted to remind you all of the Travel Support Program. We are again doing a two phase selection. The first deadline is approaching: July 1st. At this point we have less than a dozen applicants so if you need it or even think you need it, I urge you to apply here[1]. Also! Reminder that we have a finite number of rooms in the hotel block so please book early to make sure you get the discounted rate before they run out. You can book those rooms here[2] (pardon the ugly URL). Can't wait to see you all there! -Kendall Nelson (diablo_rojo) P.S. Gonna try to do a game night again since you all seemed to enjoy it so much last time :) [1] https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018 <https://openstackfoundation.formstack.com/forms/travelsupportptg_denver_2018> [2] https://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupC… <https://www.marriott.com/meeting-event-hotels/group-corporate-travel/groupC…>

1 1

[airship-in-a-bottle] DNS configurable?
by Frank Zdarsky 22 Jun '18

22 Jun '18

Hi all, I'm trying to deploy Airship-in-a-Bottle in a VM on libvirt/KVM. During the "generate genesis" step, the script overwrites /etc/resolve.conf to use the Google DNS servers (8.8.8.8 and 8.8.4.4), but those servers are blocked by our firewall, so FQDNs don't resolve and the script fails. Is there a way to configure the DNS server used or to simply keep the DNS server configured via DHCP? BTW, where are issues/RFEs filed against Airship? In Launchpad? Thanks, Frank

2 4

Libvirt Issue with AirShip
by KATARIA, DEEPAK 22 Jun '18

22 Jun '18

Hello, I had good run of the airship code today. Unfortunately libvirt container failed to come up and makes nova resources unavailable. So my test-stack deployment failed to create a VM. I am sharing the output from my deployment. I need some to fix this issue. Here are the status of cluster Successfully performed deploy_site + echo -e '\n' + break + [[ Complete == \C\o\m\p\l\e\t\e ]] + exit 0 + [[ 40 -ge 40 ]] + execute_create_heat_stack + set +x Performing basic sanity checks by creating heat stacks + cd /root/deploy/airship-in-a-bottle/manifests/dev_single_node + bash test_create_heat_stack.sh Creating KeyPair Downloading heat-public-net-deployment.yaml % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 895 100 895 0 0 3670 0 --:--:-- --:--:-- --:--:-- 3683 Creating public-net Heat Stack 2018-06-20 00:59:09Z [public-net]: CREATE_IN_PROGRESS Stack CREATE started 2018-06-20 00:59:09Z [public-net.public_net]: CREATE_IN_PROGRESS state changed 2018-06-20 00:59:09Z [public-net.public_net]: CREATE_COMPLETE state changed 2018-06-20 00:59:09Z [public-net.private_subnet]: CREATE_IN_PROGRESS state changed 2018-06-20 00:59:09Z [public-net.private_subnet]: CREATE_COMPLETE state changed 2018-06-20 00:59:09Z [public-net]: CREATE_COMPLETE Stack CREATE completed successfully +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | id | a2c34493-1f93-46bf-8483-a6ec8ca097db | | stack_name | public-net | | description | No description | | creation_time | 2018-06-20T00:59:08Z | | updated_time | None | | stack_status | CREATE_COMPLETE | | stack_status_reason | Stack CREATE completed successfully | +---------------------+--------------------------------------+ Downloading heat-basic-vm-deployment.yaml % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2361 100 2361 0 0 8147 0 --:--:-- --:--:-- --:--:-- 8141 Errors: 2018-06-20 01:00:46Z [test-stack-01.server]: CREATE_FAILED ResourceInError: resources.server: Went to status ERROR due to "Message: No valid host was found. There are not enough hosts available., Code: 500" 2018-06-20 01:00:46Z [test-stack-01]: CREATE_FAILED Resource CREATE failed: ResourceInError: resources.server: Went to status ERROR due to "Message: No valid host was found. There are not enough hosts available., Code: 500" Stack test-stack-01 CREATE_FAILED + error 'creating heat stack' + set +x Error when creating heat stack. libvirt-nf45j 0/1 CrashLoopBackOff 39 2h nova-compute-default-59zkh 0/1 CrashLoopBackOff 25 2h

2 3

Airship Logo
by James Cole 19 Jun '18

19 Jun '18

Hi Airship Crew, I’m James, a graphic designer with the OpenStack Foundation, and I’ve been working with the Airship leadership team to design a new logo. The concept is pretty accessible, with an icon of a stylized airship silhouette flying across a capital “A” shape. It works well both stacked and horizontally and in single or multiple colors. The color palette incorporates the teal and sky tones from the current landing page. I’ve attached a PDF showing the logo in a few different formats, as well as a couple of mockups to show you some practical applications. In case the attached document does not make it do you, you can view it on Dropbox here. <https://www.dropbox.com/s/zqtnbho6t5j1wg1/Airship_Logo.pdf?dl=0> We’d love to hear your thoughts on this design or if you have any other feedback you think might be important for the Airship brand. Thank you! James Cole Graphic Designer OpenStack Foundation

2 2

Looking to integrate drydock with AWS
by Manoj Meka 19 Jun '18

19 Jun '18

Hi, I'm trying to integrate drydock with AWS. From Drydock i would like to provision resources in AWS. Any suggestions as to where to begin within drydock, would be helpful. Regards, Manoj. -- Disclaimer: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please notify the sender immediately and do not disclose the contents to anyone or make copies thereof.

2 1

Deployment documents
by James Devon 14 Jun '18

14 Jun '18

Hello, 1) Is there any existing example of deployment documents (site, global? There is some documentation here : https://treasuremap.readthedocs.io/en/latest/deployment.html#building-site-… and https://pegleg.readthedocs.io/en/latest/artifacts.html but a concrete example would really help people outside of ATT to get started and understand it. I see that there are Jenkins pipelines downloading some files here : https://github.com/att-comdev/cicd/blob/master/integration/genesis-full/Jen… I have a 7 nodes cluster that I deployed using the default values here : https://github.com/openstack/openstack-helm/tree/master/tools/deployment/ar… and I'm really happy with Airship but I would like to go further :) 2) Also, how to add another node in an existing cluster after genesis and openstack deployed on it? Best, James

2 1

"Unable to find image error" from airship-in-a-bottle script
by syed.shah＠12techllc.com 14 Jun '18

14 Jun '18

Hi, We are trying to deploy Airship in a bottle using the following commands, but getting a timeout error on some docker image download: 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 We are seeing the following error: Unable to find image 'artifacts-aic.atlantafoundry.com/att-comdev/pegleg:ef47933903047339bd63fcfa…' locally docker: Error response from daemon: Get https://artifacts-aic.atlantafoundry.com/v1/_ping: dial tcp 12.37.173.37:443: i/o timeout. Last Thursday this url was working but not anymore. Thanks for the help!

2 4

osh-infra ldap error with promenade + armada
by James Devon 14 Jun '18

14 Jun '18

Hi, After having tried airship-in-a-bottle, I'm trying to setup a Kubernetes cluster and install openstack on it using promenade and armada. I'm using the basic example : https://github.com/openstack/airship-promenade/tree/master/examples/basic, I've changed the ip addresses to match my environment of 4 nodes (n0 for genesis and then n1, n2, n3). At this point I'm facing only one problem: promenade-api.ucp.svc.cluster.local is resolvable but the resolution is bad (192.168.150.165). So instead of promenade-api.ucp.svc.cluster.local, I used the pod address with the good port and it is working fine. Then, I am able to make n1,n2 and n3 join the cluster and I use the scripts from https://github.com/openstack/openstack-helm/tree/master/tools/deployment/ar… to apply armada manifests. osh-infra is not able to start the ldap pod. Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 6m (x4 over 6m) default-scheduler pod has unbound PersistentVolumeClaims (repeated 3 times) Normal Scheduled 6m default-scheduler Successfully assigned ldap-0 to n3 Normal SuccessfulAttachVolume 6m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-85d6770b-6b4c-11e8-b6e5-080027ee1df7" Normal SuccessfulAttachVolume 6m attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-85dc46a5-6b4c-11e8-b6e5-080027ee1df7" Normal SuccessfulMountVolume 6m kubelet, n3 MountVolume.SetUp succeeded for volume "ldap-token-txdqp" Warning FailedMount 13s (x11 over 6m) kubelet, n3 MountVolume.WaitForAttach failed for volume "pvc-85dc46a5-6b4c-11e8-b6e5-080027ee1df7" : fail to check rbd image status with: (executable file not found in $PATH), rbd output: () Warning FailedMount 12s (x11 over 6m) kubelet, n3 MountVolume.WaitForAttach failed for volume "pvc-85d6770b-6b4c-11e8-b6e5-080027ee1df7" : fail to check rbd image status with: (executable file not found in $PATH), rbd output: () Warning FailedMount 2s (x3 over 4m) kubelet, n3 Unable to mount volumes for pod "ldap-0_osh-infra(85e73018-6b4c-11e8-b6e5-080027ee1df7)": timeout expired waiting for volumes to attach or mount for pod "osh-infra"/"ldap-0". list of unmounted volumes=[ldap-config ldap-data]. list of unattached volumes=[ldap-config ldap-data ldap-token-txdqp] I've checked the logs of ceph-osd and there's also something: *ceph-2.1 | *starting osd.2 at - osd_data /var/lib/ceph/osd/ceph-2 /var/lib/ceph/journal/journal.2 *ceph-2.1 | **2018-06-08 18:41:03.854234 7f7cd7d58e00 -1 journal FileJournal::_open: disabling aio for non-block journal. Use journal_force_aio to force use of aio anyway* *ceph-2.1 | **2018-06-08 18:41:03.855499 7f7cd7d58e00 -1 journal do_read_entry(8192): bad header magic* *ceph-2.1 | **2018-06-08 18:41:03.855567 7f7cd7d58e00 -1 journal do_read_entry(8192): bad header magic* *ceph-2.1 | **2018-06-08 18:41:03.901804 7f7cd7d58e00 -1 osd.2 0 log_to_monitors {default=true}* *ceph-2.1 | **2018-06-08 18:41:04.529480 7f7cbb2c7700 -1 osd.2 0 waiting for initial osdmap* Did anybody encountered this error and how to fix it? Best, James

2 5

Re: [Airship-discuss] Trying out Airship
by Roman Gorshunov 13 Jun '18

13 Jun '18

Hello Prabhjot, Apologize for the inconvenience. There is a network maintenance going on, and that is the reason artifacts-aic.atlantafoundry.com is currently inaccessible. Engineers are working to get everything running soon, and in addition to that we are working on moving our docker images to publicly accessible repositories. Thank you very much for trying Airship! I will let you know once artifacts-aic.atlantafoundry.com is up again, so that you could re-try deployment. Best regards, -- Roman Gorshunov On 7 June 2018 at 11:41, Prabhjot Singh Sethi <prabhjot.lists at gmail.com> wrote: > After resolving the DNS issue, i still see artifacts-aic.atlantafoundry.com > as unreachable and failing the installation. > > Regards, > Prabhjot > ... > docker: Error response from daemon: Get > https://artifacts-aic.atlantafoundry.com/v1/_ping: dial tcp 12.37.173.37:443: > i/o timeout.

3 5

Re: [Airship-discuss] Trying out Airship
by Prabhjot Singh Sethi 07 Jun '18

07 Jun '18

After resolving the DNS issue, i still see artifacts-aic.atlantafoundry.com as unreachable and failing the installation. Regards, Prabhjot Setting up nmap (7.01-2ubuntu2) ... Processing triggers for libc-bin (2.23-0ubuntu10) ... Processing triggers for systemd (229-4ubuntu21.1) ... Processing triggers for ureadahead (0.100.0-19) ... + [[ 40 -ge 10 ]] + run_pegleg_collect + IMAGE= artifacts-aic.atlantafoundry.com/att-comdev/pegleg:ef47933903047339bd63fcfa… + /root/deploy/airship-pegleg/tools/pegleg.sh site -p /workspace/airship-in-a-bottle/deployment_files collect demo -s /workspace/collected == NOTE: Workspace /root/deploy is available as /workspace in container context == Unable to find image ' artifacts-aic.atlantafoundry.com/att-comdev/pegleg:ef47933903047339bd63fcfa…' locally docker: Error response from daemon: Get https://artifacts-aic.atlantafoundry.com/v1/_ping: dial tcp 12.37.173.37:443: i/o timeout. See 'docker run --help'. + error 'running pegleg collect' + set +x Error when running pegleg collect. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy. On 7 June 2018 at 15:16, Prabhjot Singh Sethi <prabhjot.lists(a)gmail.com> wrote: > Hi, > i am trying to use airship single node "airship in a bottle" example > on http://www.airshipit.org/. but installation fails with following > message. > i observation is that /etc/resolv.conf is changed by airship script to the > following > cat /etc/resolv.conf > options timeout:1 attempts:1 > > nameserver 10.96.0.10 > > nameserver 8.8.8.8 > nameserver 8.8.4.4 > > where ip "10.96.0.10" is not reachable. i will try to change this for my > setup, however need help in understanding if this is a bug. > > + DEBIAN_FRONTEND=noninteractive > + apt-get install -y --no-install-recommends nfs-common docker.io > socat=1.7.3.1-1 > Reading package lists... Done > Building dependency tree > Reading state information... Done > docker.io is already the newest version (1.13.1-0ubuntu1~16.04.2). > The following additional packages will be installed: > keyutils libnfsidmap2 libtirpc1 rpcbind > Suggested packages: > watchdog > Recommended packages: > python > The following NEW packages will be installed: > keyutils libnfsidmap2 libtirpc1 nfs-common rpcbind socat > 0 upgraded, 6 newly installed, 0 to remove and 100 not upgraded. > Need to get 700 kB of archives. > After this operation, 2328 kB of additional disk space will be used. > Err:1 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 > libnfsidmap2 amd64 0.25-5 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > Err:2 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 > libtirpc1 amd64 0.2.5-1 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > Err:3 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 > keyutils amd64 1.5.9-8ubuntu1 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > Err:4 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/main amd64 > rpcbind amd64 0.2.3-0.2 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > Err:5 http://nova.clouds.archive.ubuntu.com/ubuntu xenial-updates/main > amd64 nfs-common amd64 1:1.2.8-9ubuntu12.1 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > Err:6 http://nova.clouds.archive.ubuntu.com/ubuntu xenial/universe amd64 > socat amd64 1.7.3.1-1 > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > E: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/pool/main/ > libn/libnfsidmap/libnfsidmap2_0.25-5_amd64.deb Temporary failure > resolving 'nova.clouds.archive.ubuntu.com' > > E: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/pool/main/ > libt/libtirpc/libtirpc1_0.2.5-1_amd64.deb Temporary failure resolving ' > nova.clouds.archive.ubuntu.com' > > E: Failed to fetch http://nova.clouds.archive. > ubuntu.com/ubuntu/pool/main/k/keyutils/keyutils_1.5.9-8ubuntu1_amd64.deb > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > > E: Failed to fetch http://nova.clouds.archive. > ubuntu.com/ubuntu/pool/main/r/rpcbind/rpcbind_0.2.3-0.2_amd64.deb > Temporary failure resolving 'nova.clouds.archive.ubuntu.com' > > E: Failed to fetch http://nova.clouds.archive. > ubuntu.com/ubuntu/pool/main/n/nfs-utils/nfs-common_1.2.8- > 9ubuntu12.1_amd64.deb Temporary failure resolving ' > nova.clouds.archive.ubuntu.com' > E: Failed to fetch http://nova.clouds.archive.ubuntu.com/ubuntu/pool/ > universe/s/socat/socat_1.7.3.1-1_amd64.deb Temporary failure resolving ' > nova.clouds.archive.ubuntu.com' > > E: Unable to fetch some archives, maybe run apt-get update or try with > --fix-missing? > ++ date +%s > + now=1528264267 > + [[ 1528264267 -gt 1528264232 ]] > + log Failed to install apt packages. > ++ date > + echo Wed Jun 6 05:51:07 UTC 2018 Failed to install apt packages. > Wed Jun 6 05:51:07 UTC 2018 Failed to install apt packages. > + exit 1 > + error 'running genesis' > + set +x > Error when running genesis. > + exit 1 > + clean > + set +x > To remove files generated during this script's execution, delete > /root/deploy. > > >

1 0