August 2019 - Airship-discuss - lists.airshipit.org

Let's name the Airship GUI
by MCEUEN, MATT 04 Sep '19

04 Sep '19

Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://github.com/SUSE/stratos 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://github.com/mattmceuen/stratos We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://review.opendev.org/#/c/673900/ - Use the https://github.com/mattmceuen/stratos repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "<new project name>" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt

6 6

AIAB and default backend - 404
by Nick Chase 03 Sep '19

03 Sep '19

I'm pleased to say that I've successfully run the script to install Airship in a Bottle -- or at least I think I did. When I try to access most of the endpoints, I get default backend - 404 Except for the Horizon endpoint, where I get nothing at all. I'm assuming this is a K8s issue, but I'm not sure where to look further. Any ideas? ---- Nick

4 15

Canceled [sig][airship-ui] - Friday Aug 30th
by PACHECO, RODOLFO J 28 Aug '19

28 Aug '19

NEED TO Cancel this week’s meeting Many are off because of the US Holiday, and long weekend ahead. On Sept. 6 will continue with this Agenda. * Found a candidate for BAKE OFF against STRATOS § https://github.com/vmware/octant/ § LETS DO OUR DUE DILLIGENCE!!! * Announce Repo Name for Airship UI * Remember to vote on a name in the mailing list. * Airship Features for MVP Discussion Regards Rodolfo Pacheco Home/Office 732 5337671

2 1

Re: [Airship-discuss] Fw: Cloud init script generator for airshipctl
by Kanwar Saad 28 Aug '19

28 Aug '19

Hi Dmitry, Airship will be using kubernetes cluster-api and cloud-init generation will be taken care by "Cluster api bootstrap provider kubeadm(CABPK)" and final specifics of cloud-init(like network config) for bare metal hosts will be provided by CAPI baremetal provider. So from the airship point of view cloud init generation is not our task. Br, Kanwar On Wed, Aug 28, 2019 at 12:42 PM Mael Kimmerlin <mael.kimmerlin(a)est.tech> wrote: > > > ------------------------------ > *From:* Dmitry Ukov <dukov(a)mirantis.com> > *Sent:* Wednesday, August 28, 2019 9:55 AM > *To:* airship-discuss(a)lists.airshipit.org < > airship-discuss(a)lists.airshipit.org> > *Subject:* [Airship-discuss] Cloud init script generator for airshipctl > > Hello all, > > Since we a re moving to Ironic-based bare metal provisioning using > metal3-io we need to implement solution for cloud-init script creation > based on new document model. > There is Golang library and cli tool [1] shared by Alan Meadows recently. > We can leverage it in scope of airshipctl. > Unfortunately it supports only Ubuntu, Debian, Centos, Fedora and Redhat. > So I see 2 options here: > > 1. Use this library and try to contribute to it by adding more Linux > distributions > 2. Reimplement same approach as a part of airshipctl codebase > > What do you think? > > [1] https://github.com/moshloop/konfigadm > > -- > Kind regards > Dmitry Ukov > Principal Deployment Engineer > Mirantis, Inc. > >

2 1

Cloud init script generator for airshipctl
by Dmitry Ukov 27 Aug '19

27 Aug '19

Hello all, Since we a re moving to Ironic-based bare metal provisioning using metal3-io we need to implement solution for cloud-init script creation based on new document model. There is Golang library and cli tool [1] shared by Alan Meadows recently. We can leverage it in scope of airshipctl. Unfortunately it supports only Ubuntu, Debian, Centos, Fedora and Redhat. So I see 2 options here: 1. Use this library and try to contribute to it by adding more Linux distributions 2. Reimplement same approach as a part of airshipctl codebase What do you think? [1] https://github.com/moshloop/konfigadm -- Kind regards Dmitry Ukov Principal Deployment Engineer Mirantis, Inc.

1 0

Airship OSF August Sync
by Chris Hoge 27 Aug '19

27 Aug '19

This Thursday, August 29 we will have a Foundation/Airship sync meeting. This will conform to the new proposed meeting schedule of sync during the monthly TC meeting, then a second afternoon meeting in the later half of the month. Airship OSF August Sync Scheduled: Aug 29, 2019 at 2:00 PM to 3:00 PM Location: https://zoom.us/j/132898992 Airship OSF Last Thursday Sync Meeting (2nd Thursday coincides with Airship TC Meeting) https://etherpad.openstack.org/p/2019_Airship_OSF_sync

1 0

Shipyard & Promenade Core Reviewer Nominations
by MCEUEN, MATT 27 Aug '19

27 Aug '19

Airship team, Based on their record of quality code review and substantial/meaningful code contributions to specific Airship projects, as well as on needs of the community, I would like to nominate the following individuals as Airship Core Reviewers: For Promenade: Nishant Kumar For Shipyard: Michael Beaver, Matt Carter In my opinion all of these folks have demonstrated their ability to enhance these projects as well as guide the enhancements of others, helping to ensure a high-quality Airship. Current Core Reviewers over these projects are invited to reply with a +1/-1 by EOD next Tuesday (9/3). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. With the expanding breadth of Airship, as well as a small amount of attrition, I think there's great opportunity to add additional Core Reviewers in the near term. I'd encourage anyone who is interested in these responsibilities to continue to contribute meaningful reviews and enhancements for their repositories. I'd also like to share that two key members of the Airship team, Scott Hussey and Bryan Strassner, have decided to bow out of Airship Core Reviewer responsibilities. I don't need to elaborate on how much of Airship's success is owed to the efforts of these two, the technical and community foundations that they laid, and to their continued contributions! Luckily for us they remain key members of the Airship community and trusted team members. Thanks, Matt

8 8

Re: [Airship-discuss] Let's name the Airship GUI
by BILLOVITS, CYNTHIA 26 Aug '19

26 Aug '19

How about ship-to-shore or ship2shore? ----- Forwarded Message ----- Date: Mon, 26 Aug 2019 19:47:10 +0000 From: "MCEUEN, MATT" <MM9745(a)att.com> To: "'airship-discuss(a)lists.airshipit.org'" <airship-discuss(a)lists.airshipit.org> Subject: [Airship-discuss] Let's name the Airship GUI Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A27955(a)MOSTLS1MSGUSRFF.ITServices.sbc.com> Content-Type: text/plain; charset="us-ascii" Airship team, I wanted to make sure folks are aware of our airship GUI direction and hopefully get a little bit of brainstorming as well... 1. As agreed last week in the IRC meeting, we'll be creating a new Airship project to host a GUI 2. The Airship-UI SIG has agreed that it will be begin from the current codebase: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_SUSE_strato… 3. I've forked the repo and pruned down to a single master branch (f.k.a. v2-master) to import into opendev: https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_… We'd discussed calling the new project "airshipui", and I'm fine with using that (or keeping "stratos" if appropriate). However, as Airship has a long tradition of fun, nautical names, I wanted to open it up for brainstorming! If you have an idea for a good nautical project name for the Airship GUI please respond in the mailing list before the IRC team meeting on 9/3. If there's no clear winner already, we can discuss & vote in the IRC meeting. Let's target getting the PS submitted ASAP after that so we can review the new project on the 9/6 Airship-UI SIG meeting. Note: I'll be on vacation 8/28-9/5, so I'd appreciate it if a volunteer (especially someone with an interest in the UI project) could put in the patchset to import the project into opendev. It can be modeled closely after this one: - https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23… - Use the https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_mattmceuen_… repo as the upstream in the projects.yaml - Everything else should be a basic search and replace of "kubernetes-entrypoint" -> "<new project name>" - Don't forget to set the Topic to "new-project", as per the OpenStack Project Creator's Guide If you'd like to volunteer please reply to the ML. Thanks! Matt

1 0

Canceled: Airship - Open Design Call - Tuesdays Aug 27, 2019
by PACHECO, RODOLFO J 26 Aug '19

26 Aug '19

REMINDER –Airship Design Call – Cancelled tomorrow Aug 27, 2019 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs __________________________________________ Join by video system i<https://collaborationhelp.cisco.com/article/njmhfgbb> Dial rp2723(a)attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790

1 0

[WC] 2019-08-19 Meeting Notes
by MCEUEN, MATT 26 Aug '19

26 Aug '19

Meeting notes from the 8/19 Airship Working Committee meeting: . Start an every-other week WC meeting cadence beginning on August 26th . The last fifteen minutes of every WC meeting will be an "open forum" for non-WC members . Proposal: hold a special election for the fifth WC seat, three months after the first election, with a duration of 9 months . The WC will create a feedback survey to gather input on Airship community pain points and opportunities . Nishant will host IRC meeting on the 20th, Kaspars on the 27th Full agenda and notes can be found here [1]. Thanks, Matt [1]: https://etherpad.openstack.org/p/airship-wc-meeting-2019-08-19

1 2

PTG Attendance
by Kendall Nelson 23 Aug '19

23 Aug '19

Hello Everyone! This is the list of groups that are plannning on attending the PTG. Thank you PTLs/Chairs/Leads that responded on time :) I hesitate to say it's the 'final' list since I had a few groups respond with a 'Maybe', but it's probably pretty close. Please also note that the tentative activities at the PTG vary by group. Some groups are planning on only doing onboarding for example. Without further ado, here is the list! Airship Auto-Scaling SIG Barbican Blazar CInder Cyborg Edge Computing Group Fenix First Contact SIG Gitea Glance Heat Horizon I18n Ironic K8s SIG Karbor Kata Containers Keystone Loci Manila Meta SIG Monasca Neutron Nova Octavia OpenStack Charms OpenStack Infra / OpenDev OpenStack TC Openstack-helm OpenStack Operators (Ops Docs SIG and Meetup group) Oslo Public Cloud SIG Quality Assurance Release Management Scientific SIG Self-healing SIG Storlets StoryBoard Swift Tacker StarlingX If your team is missing from the list, please let me know ASAP as we are starting to put together a draft schedule. -Kendall Nelson(diablo_rojo)

1 0

Canceled: Airship - Open Design Call - Tuesday Aug 27, 2019
by PACHECO, RODOLFO J 22 Aug '19

22 Aug '19

CANCELLED – TUESDAY, AUGUST 27, 2019 - AIRSHIP DESIGN CALL Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions __________________________________________ Join by video system i<https://collaborationhelp.cisco.com/article/njmhfgbb> Dial rp2723(a)attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790

1 0

[sig][airship-yaml] Canceled: Meeting - Sept 2 , 2019
by PACHECO, RODOLFO J 22 Aug '19

22 Aug '19

Cancelled, This is a Holiday in the US Etherpad : https://etherpad.openstack.org/p/Airship_Yaml Notice that the subject line includes [sig][airship-yaml] , please make sure you add this to any email to airship-discuss(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org> when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671

1 0

Canceled: [sig][airship-yaml] Meetings
by PACHECO, RODOLFO J 22 Aug '19

22 Aug '19

Canceling, This is a Holiday in the US · Etherpad : https://etherpad.openstack.org/p/Airship_Yaml Notice that the subject line includes [sig][airship-yaml] , please make sure you add this to any email to airship-discuss(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org> when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671

1 0

[aiship-discuss][airchipctl] Development Testing Backend options
by Prakash Ramchandran 22 Aug '19

22 Aug '19

Hi all, Do you see these as possible options for Airshipctl code testing for backends Option 1: Call airshipctl commands from cmd to pass on to metal3 to execute through cloud controller and corresponding plugins. Option 2: Call airshipctl commands to by pass metal3 and call directly go-wrapped (sushy client) or Redfish APIs (URL) for BareMetal testing. 2.a Use real Redfish standard APIs (code reference- > ? 2.b Use fake calls to vBMC to enable emulated/simulated testing including libvirt calls and using oslo/openstack SDK tools -> 2.c Use Docker container as was suggested in the bootstrap SIG today same as an 2.b but use containers. Refer: Outrechy Summary <https://ajya.github.io/> Based on this link: Q1. Are we using tox for test framework? Q2. Is py3 the way to us (latest py3.6 is used in sushy & suhsy-tools? Q3. If we use go are we still planning to use standard sushy-tools and then is that call using URL to a daemon (Redfish or IPMI in a Docker container as suggested by bootstrap SIG call today?) Welcome to help us with your expertise in shaping the Airshipctl Development/Testing Thanks Prakash

1 0

Shanghai Forum Selection Committee
by Jimmy McArthur 21 Aug '19

21 Aug '19

Hello Airship! The Forum in Shanghai is rapidly approaching. We would love 1 volunteer from Airship for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. For information on the Summit in Shanghai: https://www.openstack.org/summit/shanghai-2019/ For more information on the Forum, please see:https://wiki.openstack.org/wiki/Forum Please reach out to myself orknelson(a)openstack.org if you're interested. Volunteers should respond on or before September 2, 2019. Cheers, Jimmy

1 0

[TC - August 8th TC Meeting Action Items Follow-up]
by VAN WYK, RYAN L 20 Aug '19

20 Aug '19

As a follow-up to a few TC Action Items: 1. This is the link to the feedback from the OSF on our progress towards confirmation for your consideration: https://etherpad.openstack.org/p/AirshipConfirmation * I am happy with this feedback, since it is capturing a point in time of an upward trajectory. I believe both concerns were fair, and we're moving in the right direction. * Although the SIGs are all run by AT&T folks, I would like to see SUSE work with Rodolfo to take point on the UI SIG in the near future. * I believe the "non-AT&T usage" argument will work itself out as Mirantis and SUSE are successful with their products, and given our efforts to talk with other operators and companies like Starbucks. 2. Bin Hu is taking ownership of creating the monthly "Airship Update" that will be sent to companies and individuals who have expressed interest in Airship. The goal is to keep them aware of the progress our community is making, and hopefully help them make the decision to join us. The structure of the email that will go out at the start of each month follows: * What's New: i. E.g. new additions to the community (e.g. Dell joining the team) ii. Other news/ milestones * The Airship Blog: i. Topic/ Link the blog releases for that month. * JIRA Status: i. Any metrics we can pull from JIRA/ visualize to show progress on the project since last month. * Get Involved: i. List next month's meetings/ links to page with logistics. * End the email with instructions of how to opt out/ or correct the point of contact (e.g. email rv6848(a)att.com<mailto:rv6848@att.com>). Also ask if they have any news related to Airship (e.g. have started to use it) to share that back with rv6848(a)att.com<mailto:rv6848@att.com>. 1. To support the above, and other outreach efforts I am creating a contact list. I will maintain this and share on a need to know basis. For those of you who have points of contact for folks that have expressed an interest in Airship, please share their name/ email with me. 2. A new section has been created by Bin Hu on the Airship Wiki. The goal of this section is to create a collection of presentations related to Airship as a one stop shop to make it easier for folks to come up to speed. Bin has populated it with the list we have, but if others have more to add, please do so. * Wiki section for Airship presentations: https://wiki.openstack.org/wiki/Airship/Airship-Presentations. i. Bin Captured I captured all 8 current presentations from https://www.airshipit.org/community/. ii. The wiki section can be navigated from https://wiki.openstack.org/wiki/Airship , then click "8 Airship Presentations", then follow the link of "Airship Presentations". 1. I have invited Chris Hoge/ OSF team to join the TC meetings monthly, and we will have a agenda item for them to speak to OSF feedback. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848(a)att.com<mailto:rv6848@att.com>

1 0

Airship in the news
by VAN WYK, RYAN L 19 Aug '19

19 Aug '19

Press Release: https://about.att.com/story/2019/att_dell_opensource5g.html News: Bloomberg First Word [Newsletter] Dell, AT&T Collaborate on Open Source Edge Computing, 5G Infra | Giulia Camillo Aug. 15, 2019 Dell Technologies and AT&T are jointly exploring the development of open infrastructure technology areas to support new use cases and service opportunities in cloud-oriented 5G. * Goals include delivering open source automation capabilities across infrastructure stack, jointly enhancing additional open source efforts including Metal3-io and OpenStack Ironic, integrate Kubernetes Cluster API Channelnomics<https://www.channelnomics.com/2019/08/15/criticalstart-signs-distribution-a…> Dell, AT&T Partnering on the Network Edge | Channelnomics staff Aug. 15, 2019 CRN<https://www.crn.com/news/networking/at-t-dell-team-up-to-tackle-open-source…> AT&T, Dell Team Up To Tackle Open-Source Edge Computing, 5G | Gina Narcisi Aug. 15, 2019 EnterpriseAI<https://www.enterpriseai.news/2019/08/15/att-dell-partner-to-advance-5g-clo…> AT&T, Dell Partner to Advance 5G Cloud | George Leopold Aug. 15, 2019 FierceTelecom<https://www.fiercetelecom.com/telecom/led-by-at-t-dell-takes-flight-to-airs…> Led by AT&T, Dell takes flight to Airship open source project | Mike Robuck Aug. 15, 2019 Light Reading<https://www.lightreading.com/carrier-sdn/sdn-technology/dell-flying-to-5g-c…> Dell Flying to 5G Cloud on AT&T-Led 'Airship' | Mitch Wagner Aug. 15, 2019 SDxCentral<https://www.sdxcentral.com/articles/news/att-brings-dell-technologies-into-…> AT&T Brings Dell Technologies Into the Airship Project | Matt Kapko Aug. 15, 2019 Seeking Alpha<https://seekingalpha.com/news/3492147-dell-t-partner-open-source-tech> Dell, AT&T partner on open source tech | Brandy Betz Aug. 15, 2019 siliconANGLE<https://siliconangle.com/2019/08/15/dell-att-collaborate-open-source-5g-net…> Dell and AT&T collaborate on open-source 5G network edge infrastructure | Mike Wheatley Aug. 15, 2019 telecompaper<https://www.telecompaper.com/news/dell-technologies-atandt-collaborate-on-o…> Dell Technologies, AT&T collaborate on open source edge computing, 5G software infrastructure Aug. 15, 2019 Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848(a)att.com<mailto:rv6848@att.com>

1 0

[WC] Initial Working Committee meeting
by MCEUEN, MATT 19 Aug '19

19 Aug '19

The initial Airship Working Committee meeting will be today, 2pm-3pm USA Central Time (19:00-20:00 UTC). Connectivity info can be found here[1]. The Airship community is welcome to join and listen in, and I plan to save time at the end for open floor discussion. Apologies for the late notice, meant to send this out on Friday. However, I do plan to record this for anyone who'd like to catch up. Thanks, Matt [1]: https://wiki.openstack.org/wiki/Airship/Airship-WC

1 0

AIB install issue
by Bertozzi, Julien 16 Aug '19

16 Aug '19

Hello, I am trying to setup AIB on a fresh 16.04 install, without a proxy, but I'm getting some errors when running the setup script. Here is the first one that I can see: Unpacking docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Setting up docker-ce (17.03.3~ce-0~ubuntu-xenial) ... Installing new version of config file /etc/init.d/docker ... Installing new version of config file /etc/init/docker.conf ... Processing triggers for ureadahead (0.100.0-19.1) ... Processing triggers for systemd (229-4ubuntu21.21) ... Unable to connect to the server: EOF Unable to connect to the server: EOF E0627 11:11:38.937690 1 round_trippers.go:169] CancelRequest not implemented Unable to connect to the server: EOF E0627 11:12:09.786160 1 round_trippers.go:169] CancelRequest not implemented E0627 11:12:14.786265 1 round_trippers.go:169] CancelRequest not implemented The logs are quite long, so I organized everything in a repo: https://github.com/JulienBe/airship-in-a-bottle-testing Does it ring a bell for anyone ? Thanks for your time, Julien

2 5

[airship-announce] Airship Working Committee Election Results
by MCEUEN, MATT 13 Aug '19

13 Aug '19

Team, Voting for the Airship Working Committee has concluded, and detailed results can be found here [1]. The the following members of the Working Committee have been elected to a one-year term: - Drew Walters (AT&T) - Kaspars Skels (Ericsson) - Matt McEuen (AT&T) - Nishant Kumar (Ericsson) These results are subject to the eligibility requirements and two-per-employer cap as outlined in the Airship Governance. I'd like to sincerely thank all of the Airship community members who nominated to run for the WC. They reflect a strong, diverse team with a lot of ideas and energy to improve Airship, as a project and as a community. I encourage them to actively pursue these goals with support from the team, and to nominate for the WC in the future. Thanks, Matt [1]: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_2f5847e3165e9768

1 0

AIB installation issue
by Chhabria, Ajay 12 Aug '19

12 Aug '19

Hi, I am trying to install airship in bottle and hitting an error at the following step. Please find the install logs file attached to this email and you will find the snippet at the end of it. Any help is appreciated. Please let me know if any further information is needed. Looking forward to hear back from the team. ################################################################################################################ Creating KeyPair + popd ~/deploy/treasuremap/tools/deployment/aiab + publish_horizon_dashboard + kubectl -n openstack expose service/horizon-int --type=NodePort --name=horizon-dashboard Error from server (NotFound): namespaces "openstack" not found + error 'publishing Horizon dashboard' + set +x Error when publishing Horizon dashboard. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy/treasuremap/../. This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. ################################################################################################################ root@master:~/deploy/treasuremap/tools/deployment/aiab# kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE default log-test-master-1565635735 0/1 Completed 0 29m default log-test-master-1565636918 0/1 Completed 0 9m default log-test-master-1565636942 0/1 Completed 0 9m kube-system airship-coredns-test 0/1 Completed 0 58m kube-system airship-haproxy-haproxy-test 0/1 Completed 0 57m kube-system airship-kubernetes-calico-etcd-etcd-test 0/1 Completed 0 59m kube-system airship-kubernetes-etcd-etcd-test 0/1 Completed 0 57m kube-system apiserver-key-rotate-77qqb 0/1 Completed 0 57m kube-system auxiliary-etcd-master 3/3 Running 0 1h kube-system calico-etcd-anchor-2lq6g 1/1 Running 0 1h kube-system calico-etcd-master 1/1 Running 0 59m kube-system calico-kube-controllers-74b4879ddd-26tx8 1/1 Running 0 59m kube-system calico-node-m682h 1/1 Running 0 59m kube-system calico-settings-vsxgg 0/1 Completed 0 59m kube-system coredns-559d468f6d-94hsx 1/1 Running 0 58m kube-system coredns-559d468f6d-hp7rg 1/1 Running 0 58m kube-system coredns-559d468f6d-p4qmd 1/1 Running 0 58m kube-system haproxy-anchor-m867h 1/1 Running 0 57m kube-system haproxy-master 1/1 Running 1 57m kube-system ingress-6b95789f8-qv66q 1/1 Running 0 55m kube-system ingress-error-pages-8689d4c48-zp7q9 1/1 Running 0 55m kube-system kubernetes-apiserver-anchor-kvmfh 1/1 Running 0 57m kube-system kubernetes-apiserver-master 1/1 Running 0 56m kube-system kubernetes-controller-manager-anchor-ts78n 1/1 Running 0 57m kube-system kubernetes-controller-manager-master 1/1 Running 3 57m kube-system kubernetes-etcd-anchor-4cs6d 1/1 Running 0 58m kube-system kubernetes-etcd-master 1/1 Running 0 57m kube-system kubernetes-proxy-gqwfl 1/1 Running 0 1h kube-system kubernetes-scheduler-anchor-tcvhj 1/1 Running 0 57m kube-system kubernetes-scheduler-master 1/1 Running 2 57m kube-system tiller-deploy-579c8b4f9b-cjvh9 1/1 Running 0 44m nfs nfs-provisioner-5767d6b9cc-drb67 1/1 Running 0 55m openstack airship-glance-test 0/1 Completed 0 7m openstack airship-keystone-test 0/1 Completed 0 11m openstack airship-neutron-test 0/1 PodInitializing 0 1m openstack airship-openstack-mariadb-test 0/1 Completed 0 15m openstack airship-openstack-memcached-memcached-f58bc754c-2r8qh 1/1 Running 0 13m openstack airship-openstack-rabbitmq-cluster-wait-xspdd 0/1 Completed 0 14m openstack airship-openstack-rabbitmq-rabbitmq-0 1/1 Running 0 14m openstack airship-openstack-rabbitmq-rabbitmq-exporter-5dd6bd8647-gdhp6 1/1 Running 0 14m openstack airship-openstack-rabbitmq-test 0/1 Completed 0 13m openstack exporter-create-sql-user-c6njz 0/1 Completed 0 18m openstack glance-api-7c46597bc9-tdptb 1/1 Running 0 9m openstack glance-bootstrap-jcrw7 0/1 Completed 0 9m openstack glance-db-init-2mxz6 0/1 Completed 0 9m openstack glance-db-sync-d72ff 0/1 Completed 0 9m openstack glance-ks-endpoints-5x5mc 0/3 Completed 0 9m openstack glance-ks-service-v8d27 0/1 Completed 0 9m openstack glance-ks-user-k8s89 0/1 Completed 0 9m openstack glance-rabbit-init-wb2zx 0/1 Completed 0 9m openstack glance-storage-init-pkcww 0/1 Completed 0 9m openstack ingress-68d76b8cc5-99mh7 1/1 Running 0 18m openstack ingress-error-pages-65f4f88f5f-4bvpf 1/1 Running 0 18m openstack keystone-api-647f9b6bd-nmwrm 1/1 Running 0 13m openstack keystone-bootstrap-btp5v 0/1 Completed 0 13m openstack keystone-credential-setup-cdktn 0/1 Completed 0 13m openstack keystone-db-init-qhdwp 0/1 Completed 0 13m openstack keystone-db-sync-2k67j 0/1 Completed 0 13m openstack keystone-domain-manage-ldg77 0/1 Completed 0 13m openstack keystone-fernet-setup-c2pwb 0/1 Completed 0 13m openstack libvirt-libvirt-default-n6lzv 1/1 Running 0 6m openstack mariadb-ingress-557b64d876-kzcpq 1/1 Running 0 18m openstack mariadb-ingress-error-pages-74788d8b7c-6qtd7 1/1 Running 0 18m openstack mariadb-server-0 1/1 Running 0 18m openstack neutron-db-init-4zd2d 0/1 Completed 0 6m openstack neutron-db-sync-llg8m 0/1 Completed 0 6m openstack neutron-dhcp-agent-default-lffgd 1/1 Running 0 6m openstack neutron-ks-endpoints-t58pv 0/3 Completed 0 6m openstack neutron-ks-service-8sn8h 0/1 Completed 0 6m openstack neutron-ks-user-v4bm6 0/1 Completed 0 6m openstack neutron-l3-agent-default-wqvhk 1/1 Running 0 6m openstack neutron-metadata-agent-default-2lqps 1/1 Running 0 6m openstack neutron-ovs-agent-default-qlhtz 1/1 Running 0 6m openstack neutron-rabbit-init-cvnml 0/1 Completed 0 6m openstack neutron-server-7988fdc68-jnlrk 1/1 Running 0 6m openstack neutron-server-7988fdc68-n7rbh 1/1 Running 0 6m openstack nova-api-metadata-68d88697f6-lvld4 1/1 Running 0 6m openstack nova-api-osapi-795d45b75-s7j2g 1/1 Running 0 6m openstack nova-bootstrap-qbfdf 0/1 Completed 0 6m openstack nova-cell-setup-x6pjd 0/1 Init:0/2 0 6m openstack nova-compute-default-9jfzn 0/1 Running 0 6m openstack nova-conductor-7f94bd8bb9-lvt4b 0/1 Running 0 6m openstack nova-consoleauth-59684768df-r4fvq 0/1 Running 0 6m openstack nova-db-init-np8kb 0/3 Completed 0 6m openstack nova-db-sync-mbmcl 0/1 Completed 0 6m openstack nova-ks-endpoints-2vj6d 0/3 Completed 0 6m openstack nova-ks-service-77nqq 0/1 Completed 0 6m openstack nova-ks-user-rwz6n 0/1 Completed 0 6m openstack nova-novncproxy-76df4f685f-fm7lp 0/1 Init:2/3 0 6m openstack nova-placement-api-77f8dcb59b-qs8mv 1/1 Running 0 6m openstack nova-rabbit-init-84plp 0/1 Completed 0 6m openstack nova-scheduler-759b9765c7-jzvcj 0/1 Running 0 6m openstack openvswitch-db-d4j9f 1/1 Running 0 6m openstack openvswitch-vswitchd-6vbcx 1/1 Running 0 6m openstack placement-ks-endpoints-lmt8v 0/3 Completed 0 6m openstack placement-ks-service-2sz2w 0/1 Completed 0 6m openstack placement-ks-user-zqfwv 0/1 Completed 0 6m openstack prometheus-mysql-exporter-84d99848bd-4fbdd 1/1 Running 0 18m ucp airflow-db-init-rwfns 0/1 Completed 0 32m ucp airflow-db-sync-6jc79 0/1 Completed 0 32m ucp airflow-rabbit-init-j9l25 0/1 Completed 0 32m ucp airflow-scheduler-6779bf76c4-hg85f 1/1 Running 0 32m ucp airflow-worker-0 3/3 Running 0 32m ucp airship-drydock-api-test 0/1 Completed 0 37m ucp airship-drydock-auth-test 0/1 Completed 0 37m ucp airship-maas-api-test 0/1 Completed 0 19m ucp airship-ucp-armada-armada-api-test 0/1 Completed 0 43m ucp airship-ucp-barbican-test 0/1 Completed 0 42m ucp airship-ucp-deckhand-deckhand-api-test 0/1 Completed 0 41m ucp airship-ucp-keystone-memcached-memcached-5857498fdf-7rxh4 1/1 Running 0 49m ucp airship-ucp-keystone-test 0/1 Completed 0 47m ucp airship-ucp-mariadb-test 0/1 Completed 0 51m ucp airship-ucp-promenade-api-test 0/1 Completed 0 32m ucp airship-ucp-rabbitmq-cluster-wait-85xvt 0/1 Completed 0 54m ucp airship-ucp-rabbitmq-rabbitmq-0 1/1 Running 0 54m ucp airship-ucp-rabbitmq-rabbitmq-exporter-6777747ccb-vhccb 1/1 Running 0 54m ucp airship-ucp-rabbitmq-test 0/1 Completed 0 53m ucp airship-ucp-shipyard-shipyard-api-test 0/1 Completed 0 29m ucp armada-api-74df6754b7-xngbd 2/2 Running 0 44m ucp armada-ks-endpoints-bpmgj 0/3 Completed 0 44m ucp armada-ks-service-7t72q 0/1 Completed 0 44m ucp armada-ks-user-vj5f9 0/1 Completed 0 44m ucp barbican-api-7d56457598-hwczl 1/1 Running 0 43m ucp barbican-db-init-xh4px 0/1 Completed 0 43m ucp barbican-db-sync-54tlh 0/1 Completed 0 43m ucp barbican-ks-endpoints-tv5hc 0/3 Completed 0 43m ucp barbican-ks-service-4k2lg 0/1 Completed 0 43m ucp barbican-ks-user-chknz 0/1 Completed 0 43m ucp barbican-rabbit-init-k9jth 0/1 Completed 0 43m ucp deckhand-api-5fd595d687-shmvs 1/1 Running 0 43m ucp deckhand-db-init-wrwkp 0/1 Completed 0 43m ucp deckhand-db-sync-6m2f5 0/1 Completed 0 43m ucp deckhand-ks-endpoints-8qz66 0/3 Completed 0 43m ucp deckhand-ks-service-4nwkr 0/1 Completed 0 43m ucp deckhand-ks-user-wmmx2 0/1 Completed 0 43m ucp divingbell-apt-default-5ckwf 1/1 Running 0 44m ucp divingbell-exec-default-m4pg5 1/1 Running 0 44m ucp drydock-api-7dc9bfc74c-s7dfl 1/1 Running 0 41m ucp drydock-db-init-r6psq 0/1 Completed 0 41m ucp drydock-db-sync-j27xg 0/1 Completed 0 41m ucp drydock-ks-endpoints-f7qdl 0/3 Completed 0 41m ucp drydock-ks-service-5sbl6 0/1 Completed 0 41m ucp drydock-ks-user-hmbbw 0/1 Completed 0 41m ucp ingress-69d8678658-bbct4 1/1 Running 0 54m ucp ingress-error-pages-cf9f484fd-f44hv 1/1 Running 0 54m ucp keystone-api-55b65f9795-2svn8 1/1 Running 0 49m ucp keystone-bootstrap-4w7vp 0/1 Completed 0 49m ucp keystone-credential-setup-pgcsv 0/1 Completed 0 49m ucp keystone-db-init-s62bd 0/1 Completed 0 49m ucp keystone-db-sync-j52cc 0/1 Completed 0 49m ucp keystone-domain-manage-9wx7w 0/1 Completed 0 49m ucp keystone-fernet-setup-b7v26 0/1 Completed 0 49m ucp keystone-rabbit-init-5g2kc 0/1 Completed 0 49m ucp maas-bootstrap-admin-user-t2mt2 0/1 Completed 0 20m ucp maas-bootstrap-admin-user-z4zk9 0/1 Completed 0 41m ucp maas-db-init-9f4pf 0/1 Completed 0 20m ucp maas-db-init-bw8nt 0/1 Completed 0 41m ucp maas-db-sync-mbswj 0/1 Completed 0 41m ucp maas-db-sync-st98r 0/1 Completed 0 20m ucp maas-export-api-key-n4bkp 0/1 Completed 0 41m ucp maas-export-api-key-zqck7 0/1 Completed 0 20m ucp maas-import-resources-c96tk 0/1 Completed 0 41m ucp maas-import-resources-x927n 0/1 Completed 0 20m ucp maas-ingress-errors-5bd84f86df-7pm85 1/1 Running 0 41m ucp maas-rack-0 1/1 Running 0 41m ucp maas-region-0 2/2 Running 0 41m ucp mariadb-ingress-65c4d459c9-fpgcj 1/1 Running 0 54m ucp mariadb-ingress-error-pages-5bf58fc7f8-4bc2t 1/1 Running 0 54m ucp mariadb-server-0 1/1 Running 0 54m ucp postgresql-0 1/1 Running 0 54m ucp promenade-api-7fcc7987b9-5dgl9 1/1 Running 0 32m ucp promenade-ks-endpoints-6gnx2 0/3 Completed 0 32m ucp promenade-ks-service-sdgcg 0/1 Completed 0 32m ucp promenade-ks-user-9wm2w 0/1 Completed 0 32m ucp shipyard-api-685bb866f4-srtpt 2/2 Running 0 32m ucp shipyard-db-auxiliary-lmtwg 0/1 Completed 0 32m ucp shipyard-db-init-l4wb4 0/1 Completed 0 32m ucp shipyard-db-sync-59svl 0/1 Completed 0 32m ucp shipyard-ks-endpoints-ml9r8 0/3 Completed 0 32m ucp shipyard-ks-service-52zwl 0/1 Completed 0 32m ucp shipyard-ks-user-vwvc4 0/1 Completed 0 32m Thanks and Regards, Ajay Chhabria Technical Marketing Engineer T: 408-752-7368 | M: 408-797-7485 ajay.chhabria(a)spirent.com<mailto:arnel.flandez@spirent.com> | www.spirent.com<http://www.spirent.com> 2708 Orchard Parkway, Suite 20, San Jose, CA 95134 [Spirent]<https://www.linkedin.com/company/spirent-communications/> [Spirent] <https://twitter.com/intent/user?screen_name=Spirent> [Spirent] <https://www.youtube.com/user/spirentvideos> [Spirent] <https://www.facebook.com/spirent> [Spirent]<http://www.spirent.com/> Spirent Communications e-mail confidentiality. This email and the information contained therein may contain private, confidential or privileged material solely meant for the intended recipient. If you are not the intended recipient review, copying or distribution is forbidden. Further, if you are not the intended recipient, please contact the sender immediately and permanently delete this email and any copies or attachments.

1 0

Issue with intalling airship-in-a-bottle on dev_single_node
by Soujanya R M 12 Aug '19

12 Aug '19

Hi, I am facing an issue while installing airship-in-a-bottle dev_single_node. This is the error that appears. Status: Downloaded newer image for quay.io/airshipit/promenade:master + PORT=9000 + UWSGI_TIMEOUT=300 + PROMENADE_THREADS=1 + PROMENADE_WORKERS=4 + '[' promenade = server ']' + exec promenade generate-certs -o /target deployment_files.yaml Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2168, in __getattr__ return self._get(name) File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2602, in _get value, loc = self._do_get(name, group, namespace) File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2620, in _do_get info = self._get_opt_info(name, group) File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2796, in _get_opt_info raise NoSuchOptError(opt_name, group) oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/bin/promenade", line 10, in <module> sys.exit(promenade()) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 722, in __call__ return self.main(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 697, in main rv = self.invoke(ctx) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 1063, in invoke Command.invoke(self, ctx) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 895, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/local/lib/python3.6/site-packages/click/core.py", line 535, in invoke return callback(*args, **kwargs) File "/opt/promenade/promenade/cli.py", line 16, in promenade logging.setup(verbose=verbose) File "/opt/promenade/promenade/logging.py", line 87, in setup log_level = cfg.CONF.logging.log_level File "/usr/local/lib/python3.6/site-packages/oslo_config/cfg.py", line 2172, in __getattr__ raise NoSuchOptError(name) oslo_config.cfg.NoSuchOptError: no such option logging in group [DEFAULT] + cp /root/deploy/genesis/certificates.yaml /root/deploy/airship-in-a-bottle/deployment_files/site/demo/secrets cp: cannot stat '/root/deploy/genesis/certificates.yaml': No such file or directory + error 'setting up certs with Promenade' + set +x Error when setting up certs with Promenade. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy. This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. A similar issue has been called out previously here: [0] could someone please help me out with this issue. Thanks & Regards, Soujanya R M

2 1

Re: [Airship-discuss] Divestiture
by Aaron Blair 12 Aug '19

12 Aug '19

I'm trying to follow the latest progress/discussion of Airship 2.0 and the drydock ironic integration; is it best to join the open design discussions (https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions) or another method? Based on some of the comments from the drydock and standalone ironic integration ( https://review.opendev.org/#/c/613358/4/specs/approved/drydock_ironic_integ…) it seems at least some folks are partially aware of Bifrost; when using Kolla-Ansible for Bifrost ( https://docs.openstack.org/kolla-ansible/latest/reference/deployment-and-bo…) you have options for an automated deployment of a single docker container with: - standalone ironic (conductor and inspector) - keystone - dnsmasq for dhcp/tftp which supports pxe/ipxe deployments and uefi/bios boot modes - Nginx which masquerades as an unauthenticated 'Swift' object storage service for Inspector and hosts images for ipxe over http I currently have containerized Biforst deployed in this manner with an inventory of 8 baremetal nodes with which I would like to deploy treasuremap/seaworthy. Thanks, Aaron

2 1

Fwd: Activating Prometheus (& other monitoring tools) for aiab
by Loic Le Gal 09 Aug '19

09 Aug '19

Thanks again Kaspars, Adding all these charts seem too huge even for a 32 GB RAM VM (I'll try again, in case the failure came from a latency of our infra). Anyway, I succeed to add only Prometheus, AlertManager and Grafana by doing this: A - add these chartgroups in aiab bootstrap manifest - osh-infra-monitoring - osh-infra-ingress-controller - osh-infra-mariadb - osh-infra-dashboards B - Overload the osh-infra-dashboard chartgroup to include only grafana (using deckhand overloading mechanism instead of brute removal ) B1. add a label at the global layer to avoid Deckhand complains in B2 +++ b/global/software/charts/osh-infra/osh-infra-dashboards/chart-group.yaml @@ -6,6 +6,8 @@ metadata: layeringDefinition: abstract: false layer: global + labels: + name: osh-infra-dashboards-global storagePolicy: cleartext B2. create a new file at the type layer that only contains grafana: +++ b/type/sloop/charts/osh-infra/dashboards-chartgroup.yaml @@ -0,0 +1,20 @@ +--- +schema: armada/ChartGroup/v1 +metadata: + schema: metadata/Document/v1 + replacement: true + name: osh-infra-dashboards + layeringDefinition: + abstract: false + layer: type + parentSelector: + name: osh-infra-dashboards-global + actions: + - method: merge + path: . + storagePolicy: cleartext +data: + # disable kibana by changing the chartgroup content + chart_group: + - grafana +... C - Expose the services: kubectl expose pod/prometheus-0 -n osh-infra --type=NodePort --name=prometheus-dashboard kubectl expose pod/alertmanager-0 -n osh-infra --type=NodePort --name=alertmgr-dashboard kubectl expose service/grafana-dashboard -n osh-infra --type=NodePort --name=grafana-web Not every Grafana Dashboards are operational in aiab but those that are are really good ! BR, Loïc Le mer. 7 août 2019 à 17:27, SKELS, KASPARS <ks3019(a)att.com> a écrit : > Hi, > > these charts are used in Airsloop/Seaworthy runs, so they should be > tested, and especially since site/aiab uses sloop type, the resources are > scaled down (less replicas, less storage requests), see > https://github.com/airshipit/treasuremap/tree/master/type/sloop/charts/osh-…. > You should be able to deploy entire LMA (logging, monitoring, alerting) > stack by adding this to full-site manifest > > - osh-infra-ingress-controller > - osh-infra-ceph-config > - osh-infra-radosgw > - osh-infra-logging > - osh-infra-monitoring > - osh-infra-mariadb > - osh-infra-dashboards > > This will add things like promethius, elasticsearch, kibana, etc. > > Part of the reasoning for not including these charts in the default AIAB > site was to be able to limit resources to 20G of memory (so people can get > it up and running in VMs on their laptops, and other resources constrained > places). > > I wonder if you could investigate a way we could run AIAB (airship in a > bottle) with an option (say something like --with-lma) or similar. > > We are having community IRC meetings every Tuesday 9AM CST and it would be > a good topic to discuss. > > Kindly, Kaspars > > > > > ------------------------------ > *From:* Loic Le Gal [l.legal.astellia(a)gmail.com] > *Sent:* Wednesday, August 07, 2019 10:06 AM > *To:* airship-discuss(a)lists.airshipit.org > *Subject:* Re: [Airship-discuss] Activating Prometheus (& other > monitoring tools) for aiab > > Hi, > > Replying myself to close this thread. > I finally succeed in creating prometheus-0 and alerter-0 pods by adding > also -osh-infra-monitoring in the chart_groups: section of the > file site/aiab/manifests/bootstrap.yaml. > It seems to list the available charts, the deployment process looks in to > match labels set on nodes. > > Le mer. 7 août 2019 à 14:39, Loic Le Gal <l.legal.astellia(a)gmail.com> a > écrit : > >> Hi airshipers, >> >> I'd like to add Prometheus monitoring (+fluentbit, ...) to the new >> treasuremap/site/aiab; >> It seems that some charts already exist but I'm not sure the integration >> is finished because nothing usefull found in seaworthy site def. >> >> Server/client labels do not exist on the Genesis node so I've added them >> to site/aiab/profiles/genesis.yaml and launch again the whole genesis >> process from scratch but no new pods appear. (I also tried adding >> prometheus-global=true and prometheus-type=true labels) >> >> I've already searched in Armada read-the-docs. >> Even if the WIP in armada regarding automation of metrics collection is >> still a WIP [1), I just want to get prometheus pods (then add grafana, >> fluentbit, ...) >> >> Do you know where I can find information to add/activate the monitoring >> layer (osh-infra-monitoring) or just add a Prometheus pod ? >> >> [1] https://review.opendev.org/#/c/668980/ >> <https://urldefense.proofpoint.com/v2/url?u=https-3A__review.opendev.org_-23…> >> >> BR, Loïc >> >

1 0

[sig][airship-bootstrap] airshipctl golang module vs. airshipctl interacting with a docker container
by Roman Gorshunov 08 Aug '19

08 Aug '19

Hello team, Hello Alan, Following up on an Airship-bootstrap call we have had yesterday, Alan described his alternative (lines 92-95 here https://etherpad.openstack.org/p/Airship_bootstrap, search for "isogen uses native go-lang library") which he was talking about close to the end of the call. I remember Alan has described this approach previously on one of design calls, I did not forget about it and I love this solution. What I was thinking about yesterday, was that creating a golang module for the airshipctl would be more complicated (at least for me) than to create a container image for a proof-of-concept stage. I'm all for not having containerd dependency in release version of airshipctl. I'd like to hear your feedback on this. Alan, What was the golang library you were talking about which could open and amend ISO image contents? And another question is what are the standard ISO images (esp. LiveCD) provided by vendors which have built-in cloud-init? Recording: https://attcorp.webex.com/attcorp/lsr.php?RCID=a05f4d1d798f40d79dfda57c9fa0… Recording password: HkYjdjq3 Recordings are stored on the server for 30 days only. Best regards, -- Roman Gorshunov

3 3

Activating Prometheus (& other monitoring tools) for aiab
by Loic Le Gal 07 Aug '19

07 Aug '19

Hi airshipers, I'd like to add Prometheus monitoring (+fluentbit, ...) to the new treasuremap/site/aiab; It seems that some charts already exist but I'm not sure the integration is finished because nothing usefull found in seaworthy site def. Server/client labels do not exist on the Genesis node so I've added them to site/aiab/profiles/genesis.yaml and launch again the whole genesis process from scratch but no new pods appear. (I also tried adding prometheus-global=true and prometheus-type=true labels) I've already searched in Armada read-the-docs. Even if the WIP in armada regarding automation of metrics collection is still a WIP [1), I just want to get prometheus pods (then add grafana, fluentbit, ...) Do you know where I can find information to add/activate the monitoring layer (osh-infra-monitoring) or just add a Prometheus pod ? [1] https://review.opendev.org/#/c/668980/ BR, Loïc

2 2

Shanghai Summit Schedule is Live!
by Jimmy McArthur 06 Aug '19

06 Aug '19

Hi everyone, The agenda for the Open Infrastructure Summit <https://www.openstack.org/summit/shanghai-2019/summit-schedule> (formerly the OpenStack Summit) is now live! If you need a reason to join the Summit in Shanghai, November 4-6, here’s what you can expect: * Breakout sessions spanning 30+ open source projects from technical community leaders and organizations including ARM, WalmartLabs, China Mobile, China Railway, Shanghai Electric Power Company, China UnionPay, Haitong Securities Company, CERN, and more. * Project updates and onboarding from OSF projects: Airship, Kata Containers, OpenStack, StarlingX, and Zuul. * Join collaborative sessions at the Forum <https://wiki.openstack.org/wiki/Forum>, where open infrastructure operators and upstream developers will gather to jointly chart the future of open source infrastructure, discussing topics ranging from upgrades to networking models and how to get started contributing. * Get hands on training around open source technologies directly from the developers and operators building the software. Now what? * Register before prices increase <https://www.openstack.org/summit/shanghai-2019> on August 14 at 11:59pm PT (August 15 at 2:59pm China Standard Time). * Recruiting new talent? Pitching a new product? Enhance the visibility of your organization by sponsoring the Summit <https://t.e2ma.net/click/aq0kpb/ygpkur/q287bl>! Questions? Reach out to summit(a)openstack.org Cheers, Jimmy

1 0

TC Meeting Scheduled
by VAN WYK, RYAN L 06 Aug '19

06 Aug '19

Airship community. The Airship TC has determined the logistics for the monthly meeting. We will meet on the 1st Tuesday of every month at 9am CST, unless there is a conflict. The date/time and logistics for each meeting will be posted on the TC Wiki @ https://wiki.openstack.org/wiki/Airship/Airship-TC This is also where the meeting agenda/minutes will be posted. This is an open meeting, but Q&A from non-TC members will be limited to a defined time at the end of the meeting. Thanks, Ryan van Wyk Assistant Vice President (AVP) - Member of Technical Staff Network Cloud & Infrastructure, Network Cloud Software Engineering AT&T Services, Inc. 1010 Pine St., 18th Floor, St. Louis, MO 63101 m 312.860.0966 | o 314.450.2687| rv6848(a)att.com<mailto:rv6848@att.com>

1 2

Re: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment
by Li, Cheng1 05 Aug '19

05 Aug '19

Finally, I have been able to deploy airsloop on virtual env. I created two VMs(libvirt/kvm driven), one for genesis and the other for compute node. These two VMs were on the same host. As the compute node VM is supposed to be provisioned by maas via ipmi/pxe. So I used virtualbmc to simulate the ipmi. I authored the site by following these two guides[1][2]. It’s the mix of guide[1] and guide[2]. The commands I used are all these ones[3]. After fixing several issue, I have deployed the virtual airsloop env. I list here some issues I met: 1. Node identify failed. At the beginning of step ‘prepare_and_deploy_nodes’, the drydock power on the compute node VM via ipmi. Once the compute VM starts up via pxe boot, it runs script to detect local network interfaces and sends the info back to drycok. So the drydock can identify the node based on the received info. But the compute VM doesn’t have real ILO interface, so the drydock can’t identify it. What I did to workaround this was to manually fill the ipmi info on maas web page. 2. My host doesn’t have enough CPU cores, neither the VMs. So I had to increase --pods-per-core in kubelet.yaml. 3. The disk name in compute VM is vda, instead of sda. Drydock can’t map the alias device name to vda, so I had to used the fixed alias name ‘vda’ which is the same as it’s real device name.(it was ‘bootdisk’) 4. My host doesn’t have enough resource(CPU, memory), so I removed some resource consuming components(logging, monitoring). Besides, I disabled the neutron rally test. As it failed with timeout error because of the resource limits. I also paste my site changes[4] for reference. [1] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployme… [2] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html [3] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-… [4] https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aadde… Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com] Sent: Thursday, May 30, 2019 7:29 PM To: Li, Cheng1 <cheng1.li(a)intel.com>; airship-discuss(a)lists.airshipit.org; airship-announce(a)lists.airshipit.org; openstack-dev(a)lists.openstack.org; openstack(a)lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, I am trying to create Airship-Seaworthy from the link https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html It requires 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes to be configured, but there is no documentation of how to install and getting started with Airship-Seaworthy. Do we need to follow the “Getting Started” section mentioned in Airsloop or will there be any difference in case of Seaworthy. https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-… Also what all configurations need to be run from the 3 controller nodes and what needs to be run from 3 computes? Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) From: Li, Cheng1 <cheng1.li(a)intel.com<mailto:cheng1.li@intel.com>> Sent: 30 May 2019 08:29 To: Anirudh Gupta <Anirudh.Gupta(a)hsc.com<mailto:Anirudh.Gupta@hsc.com>>; airship-discuss(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org>; airship-announce(a)lists.airshipit.org<mailto:airship-announce@lists.airshipit.org>; openstack-dev(a)lists.openstack.org<mailto:openstack-dev@lists.openstack.org>; openstack(a)lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment I have the same question. I haven’t seen any docs which guides how to deploy airsloop/air-seaworthy in virtual env. I am trying to deploy airsloop on libvirt/kvm driven virtual env. Two VMs, one for genesis, the other for compute. Virtualbmc for ipmi simulation. The genesis.sh scripts has been run on genesis node without error. But deploy_site fails at prepare_and_deploy_nodes task(action ‘set_node_boot’ timeout). I am still investigating this issue. It will be great if we have official document for this scenario. Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta@hsc.com] Sent: Wednesday, May 29, 2019 3:31 PM To: airship-discuss(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org>; airship-announce(a)lists.airshipit.org<mailto:airship-announce@lists.airshipit.org>; openstack-dev(a)lists.openstack.org<mailto:openstack-dev@lists.openstack.org>; openstack(a)lists.openstack.org<mailto:openstack@lists.openstack.org> Subject: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fairship-t…> As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes. But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment? We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment. In that case, what possible infrastructure do we require for setting up the complete setup. Looking forward for your response. Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001 DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

2 1

[Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment
by Anirudh Gupta 05 Aug '19

05 Aug '19

Hi Team, We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html<https://ind01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fairship-t…> As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes. But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment? We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment. In that case, what possible infrastructure do we require for setting up the complete setup. Looking forward for your response. Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001 DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

3 2

[Aiab] Error building Gate multinode site : Quagga 3.3.2 image not found
by Loic Le Gal 05 Aug '19

05 Aug '19

Hello Airshipers, Back from holidays I try to launch a full rebuild of Airship in a bottle multinode and I get a strange error in the BGP_touter stage: the quagga image referenced doesn't exist anymore, and this is confirmed by browsing https://hub.docker.com/r/cumulusnetworks/quagga === Executing stage Create BGP router === Unable to find image 'cumulusnetworks/quagga:CL3.3.2' locally docker: Error response from daemon: pull access denied for cumulusnetworks/quagga, repository does not exist or may require 'docker login'. See 'docker run --help'. == Error in stage Create BGP router ( /tmp/tmp.ytMAznD1X5/gate.log ) == Note that we use a tag from March (we added minor changes) and everything was running correctly upto the Overcloud. The Quagga 3.3.2 is still referenced in latest version on master. => any idea to fix this? BR, Loïc

3 6

Invalid credentials for Openstack dashboard
by Soujanya R M 05 Aug '19

05 Aug '19

Hi All, I have deployed aiab using [0]. Deployment is successfully completed. I am unable to login to OpenStack dashboard due to Invalid credentials. Currently, I am using the same credentials that are displayed after the deployment. Credentials: Domain: default Username: admin Password: password Can someone please help me with this? Thanks & Regards, Soujanya R M

2 4

[sig][airship-bootstrap] Meeting time announcement
by Roman Gorshunov 02 Aug '19

02 Aug '19

When: Weekly from 2pm UTC to 3pm UTC (10 EST to 11 EST) on Wednesday from Wed Aug 7 to Tue Dec 31 Where: https://attcorp.webex.com/join/rg445d *~*~*~*~*~*~*~*~*~* This was the time with the most votes on the doodle meeting time poll. First sig-airship-bootstrap meeting will be next week. Etherpad: https://etherpad.openstack.org/p/Airship_bootstrap Notice that the subject line includes [sig][airship-bootstrap], please make sure you add this to any email to airship-discuss(a)lists.airshipit.org when the topic relates to the airship-bootstrap discussion. Best regards, -- Roman Gorshunov

1 0

Failed to connect to remote host: FD Shutdown
by Hemant Sonawane 01 Aug '19

01 Aug '19

Hi All, Deploying OpenStack from outside of Kubernetes cluster causing me some issue and I am using armada for the deployment. I am getting connection error related to "target_address" and honestly I really don't understand why is it like that. Also Is there any way to change the target_address? as now its pointing to tiller(helm) ClusterIP address. Basically my goal is to have contact with OpenStack-helm to be able to deploy OpenStack from outside the cluster. For better understanding of my issue please find attached logs and let me know if there is any solution to resolve it. -- Thanks and Regards, Hemant Sonawane

3 4