From rp2723 at att.com Tue Oct 1 14:42:02 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 1 Oct 2019 14:42:02 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-yaml] Meetings Message-ID: <99088997CCAD0C4BA20008FD094344963C3FC5FE@MISOUT7MSGUSRDI.ITServices.sbc.com> I am out of the office away , unable to host this meeting This was the time with the most votes on the doodle meeting time poll. First sig-airship-yaml meetigns will be next week. · 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 at lists.airshipit.org when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2452 bytes Desc: not available URL: From rp2723 at att.com Tue Oct 1 14:43:53 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 1 Oct 2019 14:43:53 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-ui] Meetings - Friday Oct 11, 2019 Message-ID: <6626BC00-D0FF-450D-A6CB-4A8F072FFCDF@att.com> I am out of the office , unable to host this meeting Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Oct 1 14:43:13 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 1 Oct 2019 14:43:13 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-yaml] Meetings - Monday Oct 7, 2019 Message-ID: I am out of the office , unable to host this meeting Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Oct 1 14:44:57 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 1 Oct 2019 14:44:57 +0000 Subject: [Airship-discuss] Canceled: Airship Design Meetings - Tuesday Oct 8 & Thursday Oct 10 , 2019 Message-ID: I am out of the office , unable to host this meeting Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Oct 2 15:23:19 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 2 Oct 2019 15:23:19 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting Friday Oct 4, 2019 - Webex URL Change Message-ID: All, I am out of the office on Friday. Alan Meadows will host the sig airship ui meeting at https://attcorp.webex.com/join/am240k Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Wed Oct 2 19:25:58 2019 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 2 Oct 2019 14:25:58 -0500 Subject: [Airship-discuss] Fwd: OOK,Airship References: <963B5DA1-1C3D-481B-A41B-D11369BC1848@openstack.org> Message-ID: Hi Charles, Glad to hear you’re interested! Forwarding this to the Airship ML since there may be folks on this mailing list that will have pointers who didn't see the openstack-discuss post. Ashlee > > >> Begin forwarded message: >> >> From: Charles > >> Subject: OOK,Airship >> Date: October 2, 2019 at 5:39:16 PM GMT+2 >> To: openstack-discuss at lists.openstack.org >> >> Hi, >> >> >> We are interested in OOK and Openstack Helm. >> >> Has anyone any experience with Airship (now that 1.0 is out)? >> >> Noticed that a few Enterprise distributions are looking at managing the Openstack control plane with Kubernetes and have been testing Airship with a view to rolling it out (Mirantis,SUSE) >> >> Is this a signal that there is momentum around Openstack Helm? >> >> Is it possible to roll out an open source production grade Airship/Openstack Helm deployment today, or is it too early? >> >> >> Thoughts? >> >> >> Charles >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rv6848 at att.com Thu Oct 3 10:29:25 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Thu, 3 Oct 2019 10:29:25 +0000 Subject: [Airship-discuss] October TC Meeting Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA559FD119@MOSTLS1MSGUSREG.ITServices.sbc.com> The October TC meeting will be rescheduled to 8am PST on Wednesday the 16th. Thanks, Ryan van Wyk Airship TC -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Oct 3 11:04:10 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 3 Oct 2019 13:04:10 +0200 Subject: [Airship-discuss] Fwd: OOK,Airship In-Reply-To: References: <963B5DA1-1C3D-481B-A41B-D11369BC1848@openstack.org> Message-ID: Thanks Ashlee! Charles, A few companies who work on development of Airship do use it, including production uses: AT&T, SUSE, Mirantis, Ericsson, SK Telekom and others. Many of those companies (if not all) use Airship + OpenStack Helm as well. Airship, as you have mentioned, is a collection of components for undercloud control plane, which helps to deploy nodes with OS+Docker+Kubernetes on it, configure/manage it all in GitOps way, and then help to maintain the configuration. It also allows to manage deploys and maintenance of whatever runs on top of Kubernetes cluster, would that be OpenStack Helm or other software packaged in Helm format. OpenStack Helm does not really require to be running on Airship-managed cluster. It could run standalone. Yes, you can roll out an open source production grade Airship/Openstack Helm deployment today. Good example of production grade configuration could be found in airship/treasuremap repository [0] as 'seaworthy' site definition. You are welcome to try, of course. For the questions - reach out to us on IRC #airshipit at Freenode of via Airship-discuss mailing list. [0] https://opendev.org/airship/treasuremap Best regards, -- Roman Gorshunov On Wed, Oct 2, 2019 at 9:27 PM Ashlee Ferguson wrote: > > Hi Charles, > > Glad to hear you’re interested! Forwarding this to the Airship ML since there may be folks on this mailing list that will have pointers who didn't see the openstack-discuss post. > > Ashlee > > > > Begin forwarded message: > > From: Charles > Subject: OOK,Airship > Date: October 2, 2019 at 5:39:16 PM GMT+2 > To: openstack-discuss at lists.openstack.org > > Hi, > > > We are interested in OOK and Openstack Helm. > > Has anyone any experience with Airship (now that 1.0 is out)? > > Noticed that a few Enterprise distributions are looking at managing the Openstack control plane with Kubernetes and have been testing Airship with a view to rolling it out (Mirantis,SUSE) > > Is this a signal that there is momentum around Openstack Helm? > > Is it possible to roll out an open source production grade Airship/Openstack Helm deployment today, or is it too early? > > > Thoughts? > > > Charles > > > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From claire at openstack.org Thu Oct 3 12:12:37 2019 From: claire at openstack.org (claire at openstack.org) Date: Thu, 03 Oct 2019 12:12:37 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC meetings @ Wed Oct 16, 2019 10am - 11am (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <0000000000004f8fc505940080a0@google.com> This event has been changed. Title: Airship TC meetings Agendas: https://wiki.openstack.org/wiki/Airship/Airship-TC Join Zoom Meeting https://zoom.us/j/384128660 One tap mobile +16699006833,,384128660# US (San Jose) +16468769923,,384128660# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 384 128 660 Find your local number: https://zoom.us/u/adA54OXFxP When: Wed Oct 16, 2019 10am – 11am Central Time - Chicago (changed) Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * airship-discuss at lists.airshipit.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzZjbzMwYzFoOGQwajJiYTM2OHAzZ2I5azhwMmpjYmEyNjRwa2NiOWg3NTI0NGQxbjg0cjRjZDlqOGNfMjAxOTEwMTBUMTQwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmc2ZTI2YmRmMjViNGE4NzE5MDg3ZjA3ODcyY2Y3NzVjZGVhMjFkYTIz&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2342 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2401 bytes Desc: not available URL: From cems at ebi.ac.uk Thu Oct 3 12:13:28 2019 From: cems at ebi.ac.uk (Charles) Date: Thu, 3 Oct 2019 13:13:28 +0100 Subject: [Airship-discuss] Fwd: OOK,Airship In-Reply-To: References: <963B5DA1-1C3D-481B-A41B-D11369BC1848@openstack.org> Message-ID: <69277446-4470-3bd2-6cd4-b0f61c3e21e3@ebi.ac.uk> Hi Roman, Many thanks for the reply. I posted this on openstack-discuss because I was wondering if any users/Openstack operators out there (outside large corporations who are members of the Airship development framework) are actually running OOK in production. This could be Airship, or some other Kubernetes distribution running Openstack Helm. Our several years experience of managing Openstack so far (RHOSP/TripleO) has been bumpy due to issues with configuration maintenance /upgrades. The idea of using CI/CD and Kubernetes/Helm to manage Openstack is compelling and fits nicely into the DevOps framework here. If we were to explore this route we could 'roll our own' with a deployment say based on https://opendev.org/airship/treasuremap , or pay for and Enterprise solution that incorporates the OOK model (upcoming Mirantis and SUSE potentially). Regards Charles On 03/10/2019 12:04, Roman Gorshunov wrote: > Thanks Ashlee! > > Charles, > A few companies who work on development of Airship do use it, > including production uses: AT&T, SUSE, Mirantis, Ericsson, SK Telekom > and others. Many of those companies (if not all) use Airship + > OpenStack Helm as well. > > Airship, as you have mentioned, is a collection of components for > undercloud control plane, which helps to deploy nodes with > OS+Docker+Kubernetes on it, configure/manage it all in GitOps way, and > then help to maintain the configuration. It also allows to manage > deploys and maintenance of whatever runs on top of Kubernetes cluster, > would that be OpenStack Helm or other software packaged in Helm > format. > > OpenStack Helm does not really require to be running on > Airship-managed cluster. It could run standalone. > > Yes, you can roll out an open source production grade > Airship/Openstack Helm deployment today. Good example of production > grade configuration could be found in airship/treasuremap repository > [0] as 'seaworthy' site definition. You are welcome to try, of course. > For the questions - reach out to us on IRC #airshipit at Freenode of via > Airship-discuss mailing list. > > [0] https://opendev.org/airship/treasuremap > > Best regards, > -- > Roman Gorshunov > > On Wed, Oct 2, 2019 at 9:27 PM Ashlee Ferguson wrote: >> Hi Charles, >> >> Glad to hear you’re interested! Forwarding this to the Airship ML since there may be folks on this mailing list that will have pointers who didn't see the openstack-discuss post. >> >> Ashlee >> >> >> >> Begin forwarded message: >> >> From: Charles >> Subject: OOK,Airship >> Date: October 2, 2019 at 5:39:16 PM GMT+2 >> To: openstack-discuss at lists.openstack.org >> >> Hi, >> >> >> We are interested in OOK and Openstack Helm. >> >> Has anyone any experience with Airship (now that 1.0 is out)? >> >> Noticed that a few Enterprise distributions are looking at managing the Openstack control plane with Kubernetes and have been testing Airship with a view to rolling it out (Mirantis,SUSE) >> >> Is this a signal that there is momentum around Openstack Helm? >> >> Is it possible to roll out an open source production grade Airship/Openstack Helm deployment today, or is it too early? >> >> >> Thoughts? >> >> >> Charles >> >> >> >> >> _______________________________________________ >> Airship-discuss mailing list >> Airship-discuss at lists.airshipit.org >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss -- Charles Short Senior Cloud Engineer EMBL-EBI Hinxton 01223494205 From nchase at mirantis.com Fri Oct 4 03:35:22 2019 From: nchase at mirantis.com (Nick Chase) Date: Thu, 3 Oct 2019 23:35:22 -0400 Subject: [Airship-discuss] [airship-discuss] Error when changing simple parameters for AIAB? Message-ID: So i was able to deploy Airship in a Bottle, albeit on a much larger machine (but that's a separate issue). I wanted to demonstrate how the manifests control things, so I started up a fresh VM and edited /root/deploy/treasuremap/site/aiab/software/config/common-software-config.yaml to change the region name: I then went ahead and ran the script as usual, but it was unable to deploy/find Horizon. To make sure that the change was the issue, I then went and created a THIRD fresh VM and ran it without the change, and it deployed successfully. Is this expected? To duplicate: sudo -i mkdir -p /root/deploy && cd "$_" git clone https://opendev.org/airship/treasuremap/ cd /root/deploy/treasuremap/tools/deployment/aiab/ Then Edit :~/deploy/treasuremap/site/aiab/software/config/common-software-config.yaml --- schema: pegleg/CommonSoftwareConfig/v1 metadata: schema: metadata/Document/v1 name: common-software-config layeringDefinition: abstract: false layer: site storagePolicy: cleartext data: osh: region_name: ThisIsMyRegion ... Then ./airship-in-a-bottle.sh If someone can recommend a value that I could successfully change as a demonstration, I would really appreciate it. Thanks! ---- Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Fri Oct 4 12:55:20 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 04 Oct 2019 07:55:20 -0500 Subject: [Airship-discuss] Proposed Forum Schedule In-Reply-To: <5D962502.8080207@openstack.org> References: <5D962502.8080207@openstack.org> Message-ID: <5D974138.4080909@openstack.org> The forum schedule is now live: https://www.openstack.org/summit/shanghai-2019/summit-schedule/global-search?t=forum If you'd prefer to use the spreadsheet view: https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF Please let Kendall Nelson or myself know as soon as possible if you see any conflicts. Cheers, Jimmy Jimmy McArthur wrote: > Hello! > > I'm attaching a PDF of the proposed Shanghai Forum Schedule. I'll > publish the same on the actual website later this afternoon. However, > there is still time for feedback/time changes, assuming there aren't > conflicts for speakers/moderators. > > This is also available for download here: > https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF/view?usp=sharing > > > Please respond to this thread with any concerns. > > Cheers, > Jimmy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Fri Oct 4 16:07:01 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Fri, 4 Oct 2019 16:07:01 +0000 Subject: [Airship-discuss] [airship-discuss] Error when changing simple parameters for AIAB? In-Reply-To: References: Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8B5456@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi Nick, I think you may need to look into the AIAB scripts to see more if changing the region name may impact the changes in actual deployment scripts/assumptions of AIAB. It is definitely the right idea but then on the other hand AIAB are sort of demo/development case with various assumptions/simplifications to make it possible to do a single touch deployment in a single VM - without any user input. I would suggest to poke around and initially try some config changes that may have lesser impact on the system as a whole. The particular variable, region_name is definitely possible to change, for example see Seaworthy deployment https://github.com/airshipit/treasuremap/blob/master/site/seaworthy/software/config/common-software-config.yaml#L15 . I think simple visible things could be updating pod replicas or logging levels of OpenStack components to start with. For example Heat https://github.com/airshipit/treasuremap/blob/master/site/aiab/software/charts/osh/openstack-heat/heat.yaml You may add replica part to the site manifests (borrowed from type) https://github.com/airshipit/treasuremap/blob/master/type/sloop/charts/osh/comps/heat.yaml#L18 For all the available variables you can change for Heat or any component will be in values.yaml in openstack-helm project, including OpenStack image that can be changed and overridden for chart deployment (in case you have a custom build) https://opendev.org/openstack/openstack-helm/src/branch/master/heat/values.yaml#L42 There is also another way to update site deployments with config changes, without full re-deploy, that is when site is running (day 2 operations) https://airship-treasuremap.readthedocs.io/en/latest/config_update_guide.html Kindly, Kaspars ________________________________ From: Nick Chase [nchase at mirantis.com] Sent: Thursday, October 03, 2019 10:35 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] [airship-discuss] Error when changing simple parameters for AIAB? So i was able to deploy Airship in a Bottle, albeit on a much larger machine (but that's a separate issue). I wanted to demonstrate how the manifests control things, so I started up a fresh VM and edited /root/deploy/treasuremap/site/aiab/software/config/common-software-config.yaml to change the region name: I then went ahead and ran the script as usual, but it was unable to deploy/find Horizon. To make sure that the change was the issue, I then went and created a THIRD fresh VM and ran it without the change, and it deployed successfully. Is this expected? To duplicate: sudo -i mkdir -p /root/deploy && cd "$_" git clone https://opendev.org/airship/treasuremap/ cd /root/deploy/treasuremap/tools/deployment/aiab/ Then Edit :~/deploy/treasuremap/site/aiab/software/config/common-software-config.yaml --- schema: pegleg/CommonSoftwareConfig/v1 metadata: schema: metadata/Document/v1 name: common-software-config layeringDefinition: abstract: false layer: site storagePolicy: cleartext data: osh: region_name: ThisIsMyRegion ... Then ./airship-in-a-bottle.sh If someone can recommend a value that I could successfully change as a demonstration, I would really appreciate it. Thanks! ---- Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From pramchan at yahoo.com Fri Oct 4 17:06:14 2019 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Fri, 4 Oct 2019 17:06:14 +0000 (UTC) Subject: [Airship-discuss] [airship-discuss] Bootstrap using Virtual Media and Ironic L3 based deployment References: <2034711470.3785874.1570208774299.ref@mail.yahoo.com> Message-ID: <2034711470.3785874.1570208774299@mail.yahoo.com> Hi all, We in Bootstrap SIG as well Metal3 will be impacted by thechanges to Virtual Media and its associated Network Interface usage. There is a change to the “Ironic L3 based deployment”specification in OpenStack Ironic and needs review upstream for the Airshipproject, as we need that functionality. It is available here  https://review.opendev.org/#/c/672780/  I would appreciate it, especially Service Providers andVendors who have stake in Redfish / Virtual Media Boot review it. Your input is  most welcome. Review existing comments too to get insighton what other opinions are for scaling , OEM, L2,L3 capabilities etc. andparameters to pass  Please note that Ilya Etingof and Julia Kreger, both withRed Hat, and Richard Pioso  from Dell will give a presentation on that inShanghai Summit in November, we need to have Airship view of how this shouldwork for Ironic Operator/K8s CRDs .  Hope to gather expert inputs on these from community.Appreciate the suggestion by Roman Gorshunov on IRC  to send thisto wider audience here and have added the topic to https://etherpad.openstack.org/p/Airship_bootstrapfor next meeting.   Thank you, and regards, Prakash  -------------- next part -------------- An HTML attachment was scrubbed... URL: From ks3019 at att.com Fri Oct 4 19:38:18 2019 From: ks3019 at att.com (SKELS, KASPARS) Date: Fri, 4 Oct 2019 19:38:18 +0000 Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site In-Reply-To: References: Message-ID: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8B5ACD@MOKSCY3MSGUSRGI.ITServices.sbc.com> Hi Hilbert, perhaps not well documented item for the process. Make sure you delete the old certificates.yaml from site manifests. In other words, there should be no certificates.yaml file before you start installation. Once you run the promenade gen-certs you will have a new certificates.yaml file which at that point you can place where the original file was. E.g. input is the PKI. Let me know if this works! /Kaspars ________________________________ From: Hilbert Mixelplix [mixelplix at ineffectual.org] Sent: Thursday, September 12, 2019 10:52 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site I have been working on a custom Airship site definition (starting from the Airsloop reference), and am running into an issue during the creation of the genesis.sh script where the certificates included in the bundle still have the default names (airsloop-control-1, etc) and default IP addresses instead of those specified in my pki-catalog.yaml file. After running `sudo tools/airship promenade generate-certs \ -o /target/${NEW_SITE}_certs /target/${NEW_SITE}_collected/*.yaml` and manually inspecting the file by extracting the cert data and doing an openssl read, I see that the certificates and SANs are correct. Similarly when I inspect the collected yaml document after running the pegleg collect process, I find that the certificates are correct. Despite this, when running `sudo tools/airship promenade build-all --validators -o /target/${NEW_SITE}_bundle /target/${NEW_SITE}_collected/*.yaml` I can see the log line outputs where the certificates are added to the bundle, and the corresponding md5sums match those of the default certificates. When I execute the genesis script it is these default certificates that are extracted to /etc/genesis/ and as a result the etcd containers are unable to join a cluster together, failing with an error of: "2019-09-12 06:39:15.264601 W | rafthttp: health check for peer b9e987dd1344ab69 could not connect: x509: certificate is valid for 10.22.72.21, 127.0.0.1, 10.96.0.2, not 10.9.22.21". I've looked everywhere I can think of to try to identify where these certificates are being re-introduced (having carefully removed all copies of them before I execute the build-all process), but am unable to track them down. Has anyone run into this issue before or know what may be happening? -Hilbert -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanvanwyk at gmail.com Sun Oct 6 07:29:15 2019 From: ryanvanwyk at gmail.com (Ryan van Wyk) Date: Sun, 6 Oct 2019 08:29:15 +0100 Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site In-Reply-To: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8B5ACD@MOKSCY3MSGUSRGI.ITServices.sbc.com> References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8B5ACD@MOKSCY3MSGUSRGI.ITServices.sbc.com> Message-ID: <0A52776E-4E43-4238-B970-F23AD7AC6054@gmail.com> Should we add answers to questions like this to a Q&A not the wiki? Ryan van Wyk Cell: 312-860-0966 Email: ryanvanwyk at gmail.com > On Oct 4, 2019, at 8:43 PM, SKELS, KASPARS wrote: > >  > Hi Hilbert, > > perhaps not well documented item for the process. > > Make sure you delete the old certificates.yaml from site manifests. In other words, there should be no certificates.yaml file before you start installation. > > Once you run the promenade gen-certs you will have a new certificates.yaml file which at that point you can place where the original file was. E.g. input is the PKI. > > Let me know if this works! > /Kaspars > > > > From: Hilbert Mixelplix [mixelplix at ineffectual.org] > Sent: Thursday, September 12, 2019 10:52 AM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site > > I have been working on a custom Airship site definition (starting from the Airsloop reference), and am running into an issue during the creation of the genesis.sh script where the certificates included in the bundle still have the default names (airsloop-control-1, etc) and default IP addresses instead of those specified in my pki-catalog.yaml file. > > After running `sudo tools/airship promenade generate-certs \ > -o /target/${NEW_SITE}_certs /target/${NEW_SITE}_collected/*.yaml` and manually inspecting the file by extracting the cert data and doing an openssl read, I see that the certificates and SANs are correct. Similarly when I inspect the collected yaml document after running the pegleg collect process, I find that the certificates are correct. > > Despite this, when running `sudo tools/airship promenade build-all --validators -o /target/${NEW_SITE}_bundle /target/${NEW_SITE}_collected/*.yaml` I can see the log line outputs where the certificates are added to the bundle, and the corresponding md5sums match those of the default certificates. When I execute the genesis script it is these default certificates that are extracted to /etc/genesis/ and as a result the etcd containers are unable to join a cluster together, failing with an error of: > "2019-09-12 06:39:15.264601 W | rafthttp: health check for peer b9e987dd1344ab69 could not connect: x509: certificate is valid for 10.22.72.21, 127.0.0.1, 10.96.0.2, not 10.9.22.21". > > I've looked everywhere I can think of to try to identify where these certificates are being re-introduced (having carefully removed all copies of them before I execute the build-all process), but am unable to track them down. Has anyone run into this issue before or know what may be happening? > > -Hilbert > _______________________________________________ > 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 bluejay.ahn at gmail.com Mon Oct 7 10:36:50 2019 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Mon, 7 Oct 2019 19:36:50 +0900 Subject: [Airship-discuss] Fwd: OOK,Airship In-Reply-To: <69277446-4470-3bd2-6cd4-b0f61c3e21e3@ebi.ac.uk> References: <963B5DA1-1C3D-481B-A41B-D11369BC1848@openstack.org> <69277446-4470-3bd2-6cd4-b0f61c3e21e3@ebi.ac.uk> Message-ID: Hi Charles, As briefly mentioned in the previous email, SKT is running OOK in several productions: SKT's LTE/5G NSA infrastructure for a certain VNF (Virtualized Network Function), Private Cloud, Cloud infrastructure for VDI. SKT started navigating OOK in late 2016 exactly because of "bumpy experience due to issues with configuration maintenance /upgrade". We got very lucky to work with AT&T from the beginning both on openstack-helm and airship-armada. SKT now has a slightly different technology set from Airship, we have ansible+ironic+kubeadm+airship-armada+openstack-helm. You can see all the code and information from the following link. We opened our codebase in July (we call it "taco: skt all container openstack). - https://github.com/openinfradev - https://github.com/openinfradev/tacoplay In addtion, we have a concrete plan to develop "2nd generation of ook" that will be very similar to what Airship 2.0 look like. We will work with Airship community on this route. I hope it help your research on ook option. You can always ask me any question on this topic. I will be happy to help you. FYI, here is a presentation about what we did. - https://www.openstack.org/videos/summits/berlin-2018/you-can-start-small-and-grow-sk-telecoms-use-case-on-armada Thanks! Thanks. 2019년 10월 3일 (목) 오후 9:14, Charles 님이 작성: > Hi Roman, > > > Many thanks for the reply. > > I posted this on openstack-discuss because I was wondering if any > users/Openstack operators out there (outside large corporations who are > members of the Airship development framework) are actually running OOK > in production. This could be Airship, or some other Kubernetes > distribution running Openstack Helm. > > Our several years experience of managing Openstack so far > (RHOSP/TripleO) has been bumpy due to issues with configuration > maintenance /upgrades. The idea of using CI/CD and Kubernetes/Helm to > manage Openstack is compelling and fits nicely into the DevOps framework > here. If we were to explore this route we could 'roll our own' with a > deployment say based on https://opendev.org/airship/treasuremap , or pay > for and Enterprise solution that incorporates the OOK model (upcoming > Mirantis and SUSE potentially). > > Regards > > Charles > > > > > > On 03/10/2019 12:04, Roman Gorshunov wrote: > > Thanks Ashlee! > > > > Charles, > > A few companies who work on development of Airship do use it, > > including production uses: AT&T, SUSE, Mirantis, Ericsson, SK Telekom > > and others. Many of those companies (if not all) use Airship + > > OpenStack Helm as well. > > > > Airship, as you have mentioned, is a collection of components for > > undercloud control plane, which helps to deploy nodes with > > OS+Docker+Kubernetes on it, configure/manage it all in GitOps way, and > > then help to maintain the configuration. It also allows to manage > > deploys and maintenance of whatever runs on top of Kubernetes cluster, > > would that be OpenStack Helm or other software packaged in Helm > > format. > > > > OpenStack Helm does not really require to be running on > > Airship-managed cluster. It could run standalone. > > > > Yes, you can roll out an open source production grade > > Airship/Openstack Helm deployment today. Good example of production > > grade configuration could be found in airship/treasuremap repository > > [0] as 'seaworthy' site definition. You are welcome to try, of course. > > For the questions - reach out to us on IRC #airshipit at Freenode of via > > Airship-discuss mailing list. > > > > [0] https://opendev.org/airship/treasuremap > > > > Best regards, > > -- > > Roman Gorshunov > > > > On Wed, Oct 2, 2019 at 9:27 PM Ashlee Ferguson > wrote: > >> Hi Charles, > >> > >> Glad to hear you’re interested! Forwarding this to the Airship ML since > there may be folks on this mailing list that will have pointers who didn't > see the openstack-discuss post. > >> > >> Ashlee > >> > >> > >> > >> Begin forwarded message: > >> > >> From: Charles > >> Subject: OOK,Airship > >> Date: October 2, 2019 at 5:39:16 PM GMT+2 > >> To: openstack-discuss at lists.openstack.org > >> > >> Hi, > >> > >> > >> We are interested in OOK and Openstack Helm. > >> > >> Has anyone any experience with Airship (now that 1.0 is out)? > >> > >> Noticed that a few Enterprise distributions are looking at managing the > Openstack control plane with Kubernetes and have been testing Airship with > a view to rolling it out (Mirantis,SUSE) > >> > >> Is this a signal that there is momentum around Openstack Helm? > >> > >> Is it possible to roll out an open source production grade > Airship/Openstack Helm deployment today, or is it too early? > >> > >> > >> Thoughts? > >> > >> > >> Charles > >> > >> > >> > >> > >> _______________________________________________ > >> Airship-discuss mailing list > >> Airship-discuss at lists.airshipit.org > >> http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > -- > Charles Short > Senior Cloud Engineer > EMBL-EBI > Hinxton > 01223494205 > > > _______________________________________________ > 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 kennelson11 at gmail.com Mon Oct 7 19:53:29 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 7 Oct 2019 12:53:29 -0700 Subject: [Airship-discuss] [all] Final PTG Schedule Message-ID: Hello Everyone! After a few weeks of shuffling and changes, we have a final schedule! It can be seen here on the 'Schedule' tab[1]. -Kendall (diablo_rojo) [1] https://www.openstack.org/PTG -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Wed Oct 9 09:54:20 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Wed, 9 Oct 2019 11:54:20 +0200 Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site In-Reply-To: <0A52776E-4E43-4238-B970-F23AD7AC6054@gmail.com> References: <2ADBF0C373B7E84E944B1E06D3CDDFC91E8B5ACD@MOKSCY3MSGUSRGI.ITServices.sbc.com> <0A52776E-4E43-4238-B970-F23AD7AC6054@gmail.com> Message-ID: Hilbert, Did you succeed to get proper documents rendered? Ryan, It's documented as one of the forst steps when starting to write new site definition. https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html#preparing-deployment-documents Best regards, -- Roman Gorshunov On Sun, Oct 6, 2019 at 9:30 AM Ryan van Wyk wrote: > > Should we add answers to questions like this to a Q&A not the wiki? > > Ryan van Wyk > > Cell: 312-860-0966 > Email: ryanvanwyk at gmail.com > > On Oct 4, 2019, at 8:43 PM, SKELS, KASPARS wrote: > >  > Hi Hilbert, > > perhaps not well documented item for the process. > > Make sure you delete the old certificates.yaml from site manifests. In other words, there should be no certificates.yaml file before you start installation. > > Once you run the promenade gen-certs you will have a new certificates.yaml file which at that point you can place where the original file was. E.g. input is the PKI. > > Let me know if this works! > /Kaspars > > > > ________________________________ > From: Hilbert Mixelplix [mixelplix at ineffectual.org] > Sent: Thursday, September 12, 2019 10:52 AM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Incorrect (default) certificates in genesis bundle for custom site > > I have been working on a custom Airship site definition (starting from the Airsloop reference), and am running into an issue during the creation of the genesis.sh script where the certificates included in the bundle still have the default names (airsloop-control-1, etc) and default IP addresses instead of those specified in my pki-catalog.yaml file. > > After running `sudo tools/airship promenade generate-certs \ > -o /target/${NEW_SITE}_certs /target/${NEW_SITE}_collected/*.yaml` and manually inspecting the file by extracting the cert data and doing an openssl read, I see that the certificates and SANs are correct. Similarly when I inspect the collected yaml document after running the pegleg collect process, I find that the certificates are correct. > > Despite this, when running `sudo tools/airship promenade build-all --validators -o /target/${NEW_SITE}_bundle /target/${NEW_SITE}_collected/*.yaml` I can see the log line outputs where the certificates are added to the bundle, and the corresponding md5sums match those of the default certificates. When I execute the genesis script it is these default certificates that are extracted to /etc/genesis/ and as a result the etcd containers are unable to join a cluster together, failing with an error of: > "2019-09-12 06:39:15.264601 W | rafthttp: health check for peer b9e987dd1344ab69 could not connect: x509: certificate is valid for 10.22.72.21, 127.0.0.1, 10.96.0.2, not 10.9.22.21". > > I've looked everywhere I can think of to try to identify where these certificates are being re-introduced (having carefully removed all copies of them before I execute the build-all process), but am unable to track them down. Has anyone run into this issue before or know what may be happening? > > -Hilbert > _______________________________________________ > 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 sh8121 at att.com Wed Oct 9 14:04:43 2019 From: sh8121 at att.com (HUSSEY, SCOTT T) Date: Wed, 9 Oct 2019 14:04:43 +0000 Subject: [Airship-discuss] MAAS 2.6 support In-Reply-To: References: Message-ID: Lukasz, Glad to hear you have found some use of the MAAS chart. It is part of the greater Airship project which actually uses a instance of Gerritt for code review/acceptance. https://review.opendev.org/airship/maas. Sorry there isn't much contributing documentation, but the project would absolutely appreciate any work you've done. I had started to look at MAAS 2.6, but with the re-architecture in MAAS 2.5 I wasn't sure the current chart would work. Unfortunately I'll be leaving the project in 2 days, but I'd encourage you to reach out to the Airship core developers via IRC or the developer mailing list with any questions on contributing your changes or questions on using the chart. Good luck. https://www.airshipit.org/community/ From: Lukasz Mateusz Pawlowski Sent: Monday, October 07, 2019 11:26 AM To: HUSSEY, SCOTT T Subject: MAAS 2.6 support Hi Scott I am looking for a way to raise PR to airship/maas to get official support for MAAS 2.6 I have rewrote your 2.3 patches to support 2.6 so I can use latest MAAS (https://github.com/teluka/maas/commits/maas-v2.6). We're successfully using modified airship/maas that installed 2.6 in testing and production environments. I was wondering if you guys are accepting PRs to airship/maas and if yes then were I can raise them ? I think other users would benefit as well if this chart would support latest version of the MAAS. BTW: Your MAAS chart is simply awesome. :) Regards Lukasz Mateusz Pawlowski -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Oct 9 17:26:27 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 9 Oct 2019 10:26:27 -0700 Subject: [Airship-discuss] Fwd: Important Shanghai PTG Information In-Reply-To: <9FDF61D8-22A5-4CA6-8F5B-BAF8122121BA@openstack.org> References: <9FDF61D8-22A5-4CA6-8F5B-BAF8122121BA@openstack.org> Message-ID: Wanted to make sure you all saw this too :) -Kendall (diablo_rojo) ---------- Forwarded message --------- From: Kendall Waters Date: Wed, Oct 9, 2019 at 10:09 AM Subject: Important Shanghai PTG Information To: OpenStack Discuss Hello Everyone! As I’m sure you already know, the Shanghai PTG is going to be a very different event from PTGs in the past so we wanted to spell out the differences so you can be better prepared. Registration & Badges Registration for the PTG is included in the cost of the Summit. It is a single registration for both events. Since there is a single registration for the event, there is also one badge for both events. You will pick it up when you check in for the Summit and keep it until the end of the PTG. The Space Rooms The space we are contracted to have for the PTG will be laid out differently. We only have a couple dedicated rooms which are allocated to those groups with the largest numbers of people. The rest of the teams will be in a single larger room together. To help people gather teams in an organized fashion, we will be naming the arrangements of tables after OpenStack releases (Austin, Bexar, Cactus, etc). Food & Beverage Rules Unfortunately, the venue does not allow ANY food or drink in any of the rooms. This includes coffee and tea. Lunch will be from 12:30 to 1:30 in the beautiful pre-function space outside of the Blue Hall. Moving Furniture You are allowed to! Yay! If the table arrangements your project/team/group lead requested don’t work for you, feel free to move the furniture around. That being said, try to keep the tables marked with their names so that others can find them during their time slots. There will also be extra chairs stacked in the corner if your team needs them. Hours This venue is particularly strict about the hours we are allowed to be there. The PTG is scheduled to run from 9:00 in the morning to 4:30 in the evening. Its reasonably likely that if you try to come early or stay late, security will talk to you. So please be kind and respectfully leave if they ask you to. Resources Power While we have been working with the venue to accomodate our power needs, we won’t have as many power strips as we have had in the past. For this reason, we want to remind everyone to charge all their devices every night and share the power strips we do have during the day. Sharing is caring! Flipcharts While we won’t have projection available, we will have some flipcharts around. Each dedicated room will have one flipchart and the big main room will have a few to share. Please feel free to grab one when you need it, but put it back when you are finished so that others can use it if they need. Again, sharing is caring! :) Onboarding A lot of the usual PTG attendees won’t be able to attend this event, but we will also have a lot of new faces. With this in mind, we have decided to add project onboarding to the PTG so that the new contributors can get up to speed with the projects meeting that week. The teams gathering that will be doing onboarding will have that denoted on the print and digital schedule on site. They have also been encouraged to promote when they will be doing their onboarding via the PTGBot and on the mailing lists. If you have any questions, please let us know! Cheers, The Kendalls (wendallkaters & diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Wed Oct 9 18:06:53 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Wed, 9 Oct 2019 11:06:53 -0700 Subject: [Airship-discuss] PTG Team Photos Message-ID: Hello Everyone! We are excited to see you in a few weeks at the PTG and wanted to share that we will be taking team photos again! Here is an ethercalc signup for the available time slots [1]. We will be providing time on Thursday Morning/Afternoon and Friday morning to come as a team to get your photo taken. Slots are only ten minutes so its *important that everyone be on time*! The location is TBD at this point, but it will likely be in the prefunction space near registration. Thanks, -Kendall Nelson (diablo_rojo) [1] https://ethercalc.openstack.org/lnupu1sx6ljl -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Oct 9 19:08:16 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 9 Oct 2019 19:08:16 +0000 Subject: [Airship-discuss] Nominations open for Airship 2019 WC special election Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A6F1C4@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, Nominations for the special election of the Airship Working Committee's fifth seat are now open, and will remain open until August 6th, 19:00 UTC. This seat will have a nine-month term (to synchronize re-election with the rest of the WC). The Working Committee is off to a great start, and we'd love to add a non-AT&T, non-Ericsson team member (allowing for two-seat maxima per employer) to help continue to advance the Airship community! All nominations must be submitted as a text file to the airship/election repository as explained at [1]. Please make sure to follow the candidacy file naming convention: candidates/2019/WC/ . Anyone who has contributed to the Airship project within the last 12 months is eligible to run for the Working Committee, as specified in the Airship Governance. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed on the same page. Happy running, Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst From MM9745 at att.com Wed Oct 9 19:10:55 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 9 Oct 2019 19:10:55 +0000 Subject: [Airship-discuss] Nominations open for Airship 2019 WC special election In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A6F1C4@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A6F1C4@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A6F207@MOSTLS1MSGUSRFF.ITServices.sbc.com> Correction to date... -----Original Message----- From: MCEUEN, MATT Sent: Wednesday, October 9, 2019 2:08 PM To: 'airship-discuss at lists.airshipit.org' Subject: [Airship-discuss] Nominations open for Airship 2019 WC special election Airship community, Nominations for the special election of the Airship Working Committee's fifth seat are now open, and will remain open until October 16th, 19:00 UTC. This seat will have a nine-month term (to synchronize re-election with the rest of the WC). The Working Committee is off to a great start, and we'd love to add a non-AT&T, non-Ericsson team member (allowing for two-seat maxima per employer) to help continue to advance the Airship community! All nominations must be submitted as a text file to the airship/election repository as explained at [1]. Please make sure to follow the candidacy file naming convention: candidates/2019/WC/ . Anyone who has contributed to the Airship project within the last 12 months is eligible to run for the Working Committee, as specified in the Airship Governance. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed on the same page. Happy running, Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst From l.legal.astellia at gmail.com Thu Oct 10 10:09:18 2019 From: l.legal.astellia at gmail.com (Loic Le Gal) Date: Thu, 10 Oct 2019 12:09:18 +0200 Subject: [Airship-discuss] Aiab Site update with Shipyard fails Message-ID: Hi Airshipers, We successfully deployed the aiab from treasuremap for a while and activated the Prometheus monitoring. Instead of deploying again from Genesis, Now I try to use the site update mechanism: (cf. https://airship-treasuremap.readthedocs.io/en/latest/config_update_guide.html ) - Pegleg lint + collected yaml generation - Shipyard create and commit docs (No error) In fact we only modify the initial site by adding a parameter in Prometheus Chart using Deckhand substitution mechanism. The site syntax seems Ok and has been committed, but the update_site action fails: Name: update_site Action: action/01DPTGTT31Y7CVYFGZYJVDV402 Lifecycle: Complete Parameters: {} Datetime: 2019-10-10 09:43:37.826039+00:00 Dag Status: success Context Marker: 649459d0-239e-4a86-ad23-73daa304b588 User: shipyard Steps Index State Footnotes step/01DPTGTT31Y7CVYFGZYJVDV402/action_xcom 1 success step/01DPTGTT31Y7CVYFGZYJVDV402/dag_concurrency_check 2 success step/01DPTGTT31Y7CVYFGZYJVDV402/get_rendered_doc 3 success step/01DPTGTT31Y7CVYFGZYJVDV402/deployment_configuration 4 success step/01DPTGTT31Y7CVYFGZYJVDV402/preflight 5 success step/01DPTGTT31Y7CVYFGZYJVDV402/validate_site_design 6 success step/01DPTGTT31Y7CVYFGZYJVDV402/drydock_build 7 failed step/01DPTGTT31Y7CVYFGZYJVDV402/armada_build 8 upstream_failed step/01DPTGTT31Y7CVYFGZYJVDV402/decide_airflow_upgrade 9 upstream_failed step/01DPTGTT31Y7CVYFGZYJVDV402/verify_site 10 success step/01DPTGTT31Y7CVYFGZYJVDV402/prepare_site 11 success step/01DPTGTT31Y7CVYFGZYJVDV402/skip_upgrade_airflow 12 upstream_failed step/01DPTGTT31Y7CVYFGZYJVDV402/upgrade_airflow 13 upstream_failed step/01DPTGTT31Y7CVYFGZYJVDV402/armada_get_status 14 None step/01DPTGTT31Y7CVYFGZYJVDV402/verify_nodes_exist 15 failed step/01DPTGTT31Y7CVYFGZYJVDV402/create_action_tag 16 success step/01DPTGTT31Y7CVYFGZYJVDV402/armada_post_apply 17 None step/01DPTGTT31Y7CVYFGZYJVDV402/ucp_preflight_check 18 success step/01DPTGTT31Y7CVYFGZYJVDV402/deployment_status 19 success step/01DPTGTT31Y7CVYFGZYJVDV402/deckhand_validate_site_design 20 success step/01DPTGTT31Y7CVYFGZYJVDV402/drydock_validate_site_design 21 success step/01DPTGTT31Y7CVYFGZYJVDV402/promenade_validate_site_design 22 success step/01DPTGTT31Y7CVYFGZYJVDV402/armada_validate_site_design 23 success step/01DPTGTT31Y7CVYFGZYJVDV402/prepare_and_deploy_nodes 24 upstream_failed step/01DPTGTT31Y7CVYFGZYJVDV402/final_deployment_status 25 success step/01DPTGTT31Y7CVYFGZYJVDV402/armada_get_releases 26 None As I previously already faced such this error when activating Prometheus, I wonder whether the aiab site allows the update_site action or if it contains some specific scripted actions that prevent running this action? BR, Loïc -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Oct 11 16:54:31 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 11 Oct 2019 16:54:31 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting Times Announcement Message-ID: <99108FE2-B793-4AA5-BAB1-2FA7F620E12D@att.com> As per the results from the doodle https://doodle.com/poll/rmscdht6yir84d3u, there were 2 times with equal amount of votes. Will start the sig-airship-ui meetings on Friday’s, starting this Friday Jul 26 at 13:00 PM EST/ 18:00 PM UTC Etherpad for this meetings : https://etherpad.openstack.org/p/Airship_UI The purpose for this group will be to : • - Will focus on the scope and goals for Airship UI • - Will identify MVP or Initial State target for the ui, such as i.e. start work by leveraging existing argo ui as a demonstration • - Will define target for ui framework to define: Auth/AuthZ Logging Etc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2468 bytes Desc: not available URL: From rp2723 at att.com Fri Oct 11 17:53:51 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 11 Oct 2019 17:53:51 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting Times Announcement Message-ID: <8548F2BF-5304-4152-8552-9445D800EBA1@att.com> As per the results from the doodle https://doodle.com/poll/rmscdht6yir84d3u, there were 2 times with equal amount of votes. Will start the sig-airship-ui meetings on Friday’s, starting this Friday Jul 26 at 13:00 PM EST/ 18:00 PM UTC Etherpad for this meetings : https://etherpad.openstack.org/p/Airship_UI The purpose for this group will be to : • - Will focus on the scope and goals for Airship UI • - Will identify MVP or Initial State target for the ui, such as i.e. start work by leveraging existing argo ui as a demonstration • - Will define target for ui framework to define: Auth/AuthZ Logging Etc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2468 bytes Desc: not available URL: From rp2723 at att.com Fri Oct 11 17:53:53 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 11 Oct 2019 17:53:53 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting Times Announcement Message-ID: As per the results from the doodle https://doodle.com/poll/rmscdht6yir84d3u, there were 2 times with equal amount of votes. Will start the sig-airship-ui meetings on Friday’s, starting this Friday Jul 26 at 13:00 PM EST/ 18:00 PM UTC Etherpad for this meetings : https://etherpad.openstack.org/p/Airship_UI The purpose for this group will be to : • - Will focus on the scope and goals for Airship UI • - Will identify MVP or Initial State target for the ui, such as i.e. start work by leveraging existing argo ui as a demonstration • - Will define target for ui framework to define: Auth/AuthZ Logging Etc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2468 bytes Desc: not available URL: From rp2723 at att.com Fri Oct 11 18:05:11 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 11 Oct 2019 18:05:11 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting Times Announcement Message-ID: <472F54EE-37FB-4942-8BB0-30B347C67C92@att.com> As per the results from the doodle https://doodle.com/poll/rmscdht6yir84d3u, there were 2 times with equal amount of votes. Will start the sig-airship-ui meetings on Friday’s, starting this Friday Jul 26 at 13:00 PM EST/ 18:00 PM UTC Etherpad for this meetings : https://etherpad.openstack.org/p/Airship_UI The purpose for this group will be to : • - Will focus on the scope and goals for Airship UI • - Will identify MVP or Initial State target for the ui, such as i.e. start work by leveraging existing argo ui as a demonstration • - Will define target for ui framework to define: Auth/AuthZ Logging Etc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2580 bytes Desc: not available URL: From denise at openstack.org Tue Oct 15 12:13:20 2019 From: denise at openstack.org (denise at openstack.org) Date: Tue, 15 Oct 2019 06:13:20 -0600 (MDT) Subject: [Airship-discuss] OSF booth at KubeCon+CloudNativeCon in San Diego Message-ID: <1571141600.054118968@apps.rackspace.com> Hello Everyone, We wanted to let you know that the OpenStack Foundation will have a booth at the upcoming KubeCon+CloudNativeCon event in San Diego, CA on November 18-21, 2019. We are in booth #S23 and we will be featuring the OpenStack Foundation in addition to all the projects - Airship, Kata Containers, StarlingX, OpenStack and Zuul. At the booth we will have stickers and educational collateral about each project to distribute. We would like to invite you to help us in the following areas: Represent your project by staffing the OSF booth If you can spare 1 hour/day (or any time at all!) to represent your specific project in the OSF booth Here is the [ link ]( https://docs.google.com/spreadsheets/d/1mZzK0GHm9OQ0IL9njTWLxPLuAeR6jqmyeM60T7sQQOc/edit#gid=0 ) to the google doc to sign up Project Demos in the OSF booth If you are interested in delivering a project-specific demo in the OSF booth, please contact [ Denise ]( http://denise at openstack.org ) Looking forward to seeing all of you in San Diego! Best regards, OSF Marketing team Denise, Claire, Allison and Ashlee -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Thu Oct 3 16:42:42 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Thu, 03 Oct 2019 11:42:42 -0500 Subject: [Airship-discuss] Proposed Forum Schedule Message-ID: <5D962502.8080207@openstack.org> Hello! I'm attaching a PDF of the proposed Shanghai Forum Schedule. I'll publish the same on the actual website later this afternoon. However, there is still time for feedback/time changes, assuming there aren't conflicts for speakers/moderators. This is also available for download here: https://drive.google.com/file/d/1qp0I9xnyOK3mhBitQnk2a7VuS9XClvyF/view?usp=sharing Please respond to this thread with any concerns. Cheers, Jimmy -------------- next part -------------- A non-text attachment was scrubbed... Name: Forum Mock Schedule.pdf Type: application/pdf Size: 88937 bytes Desc: not available URL: From pap08527 at yahoo.com Wed Oct 9 14:43:17 2019 From: pap08527 at yahoo.com (Paul Potochniak) Date: Wed, 9 Oct 2019 14:43:17 +0000 (UTC) Subject: [Airship-discuss] Airsloop Building of site documents fail when following Deploying Behind a Proxy References: <1316234304.3806537.1570632197496.ref@mail.yahoo.com> Message-ID: <1316234304.3806537.1570632197496@mail.yahoo.com> Hello,   I have been working on creating an Airsloop  two node instance.  I’m able to build the Site documents(following the Airsloop document) but when I follow the instruction for “DeployingBehind a Proxy” I encounter errors generating the certs.    Running:  tools/airshippromenade generate-certs   -o/target/${NEW_SITE}_certs /target/${NEW_SITE}_collected/*.yaml   Gives these errors:   2019-10-09 14:32:32,180 ERROR    req_id=- ctx=- end_user=- user=-promenade.config:config.py: 38:__init__ An unknown Deckhand exception occurredwhile trying to render documents. Traceback (most recent call last):   File"/opt/promenade/promenade/config.py", line 34, in __init__    fail_on_missing_sub_src=not allow_missing_substitutions)   File"/usr/local/lib/python3.6/site-packages/deckhand/engine/layering.py",line 447, in __init__     d for d inself._documents_by_index.values()   File"/usr/local/lib/python3.6/site-packages/deckhand/engine/layering.py",line 97, in _calc_replacements_and_substitutions    replacement.check_only_one_level_of_replacement(src_ref)   File"/usr/local/lib/python3.6/site-packages/deckhand/engine/_replacement.py",line 82, in check_only_one_level_of_replacement    layer=src_ref.layer, reason=error_message) deckhand.errors.InvalidDocumentReplacement: Replacementdocument [armada/Chart/v1, type] glance is invalid. Reason: A replacementdocument cannot itself be replaced by another document. 2019-10-09 14:32:32,181 ERROR    req_id=- ctx=- end_user=- user=-promenade.exceptions:exceptions.py:222:display Replacement document[armada/Chart/v1, type] glance is invalid. Reason: A replacement documentcannot itself be replaced by another document.     Again, when I run without applying the additionalfiles/edit for “Deploying Behind a Proxy” the command completes successfully.   Thanks,   Paul -------------- next part -------------- An HTML attachment was scrubbed... URL: From robson.rbarreto at gmail.com Tue Oct 15 21:48:16 2019 From: robson.rbarreto at gmail.com (Robson Ramos Barreto) Date: Tue, 15 Oct 2019 18:48:16 -0300 Subject: [Airship-discuss] Ubuntu release Message-ID: Hi, I'm planing with Airship to deploy some Openstack regions and I have a doubt about the Ubuntu release (16.04) used to Genesis node and the rest of the nodes deployed by MaaS. I'd like to know if I can use Ubuntu 18.04 instead of Ubuntu 16.04 without any concern or if there is a roadmap. Thank you Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Tue Oct 15 22:08:57 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 15 Oct 2019 22:08:57 +0000 Subject: [Airship-discuss] Ubuntu release In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A82204@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Robson, Migrating Airship from Ubuntu 16.04 to 18.04 at the host level is actually a work-in-progress, and we hope to have that represented as the default in treasuremap in the near future. Ahmad, MattC, is there anything Robson would need to be aware of if he wanted to run with bionic ahead of treasuremap being updated? Please see: https://review.opendev.org/#/c/685802/ https://review.opendev.org/#/c/684138/ Thanks, Matt From: Robson Ramos Barreto Sent: Tuesday, October 15, 2019 4:48 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Ubuntu release Hi, I'm planing with Airship to deploy some Openstack regions and I have a doubt about the Ubuntu release (16.04) used to Genesis node and the rest of the nodes deployed by MaaS. I'd like to know if I can use Ubuntu 18.04 instead of Ubuntu 16.04 without any concern or if there is a roadmap. Thank you Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From kire at kth.se Wed Oct 16 08:36:52 2019 From: kire at kth.se (=?iso-8859-1?Q?Jan-Erik_M=E5ngs?=) Date: Wed, 16 Oct 2019 08:36:52 +0000 Subject: [Airship-discuss] Gap Analysis studies result In-Reply-To: References: Message-ID: Hi Anwar, Is the link correct? Best regards /Jan-Erik On 5 Sep 2019, at 14:42, Anwar Hassen > wrote: Hello, This is in reference to the gap analysis list created during our face to face meeting in June, f2f notes We have done some studies with respect to the action points. Please see this link for the result. Would you please review and give comments. Best regards, Anwar Hassen _______________________________________________ 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 claire at openstack.org Wed Oct 16 14:57:08 2019 From: claire at openstack.org (claire at openstack.org) Date: Wed, 16 Oct 2019 14:57:08 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC meetings @ Wed Oct 16, 2019 10am - 11am (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <000000000000989f6b0595085043@google.com> This event has been changed. Title: Airship TC meetings Agendas: https://wiki.openstack.org/wiki/Airship/Airship-TC Join Zoom Meeting https://zoom.us/j/2146866821 Meeting ID: 214 686 6821 One tap mobile +16699006833,,2146866821# US (San Jose) +16468769923,,2146866821# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 214 686 6821 Find your local number: https://zoom.us/u/abitj0TUE (changed) When: Wed Oct 16, 2019 10am – 11am Central Time - Chicago Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * airship-discuss at lists.airshipit.org * Alexey Odinokov * Boris Renski Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzZjbzMwYzFoOGQwajJiYTM2OHAzZ2I5azhwMmpjYmEyNjRwa2NiOWg3NTI0NGQxbjg0cjRjZDlqOGNfMjAxOTEwMTBUMTQwMDAwWiBhaXJzaGlwLWRpc2N1c3NAbGlzdHMuYWlyc2hpcGl0Lm9yZw&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmc2ZTI2YmRmMjViNGE4NzE5MDg3ZjA3ODcyY2Y3NzVjZGVhMjFkYTIz&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2834 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2905 bytes Desc: not available URL: From claire at openstack.org Wed Oct 16 14:58:02 2019 From: claire at openstack.org (Claire Massey) Date: Wed, 16 Oct 2019 09:58:02 -0500 Subject: [Airship-discuss] New link / dial in for TODAY'S TC call, at 10am CT Message-ID: <1A910B07-6B55-4B5B-933F-D566E9AD4B64@openstack.org> Hi everyone, Please use this link for today’s TC call at 10am CT Join Zoom Meeting https://zoom.us/j/2146866821 Meeting ID: 214 686 6821 One tap mobile +16699006833,,2146866821# US (San Jose) +16468769923,,2146866821# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 214 686 6821 Find your local number: https://zoom.us/u/abitj0TUE -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Oct 16 15:04:46 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 16 Oct 2019 15:04:46 +0000 Subject: [Airship-discuss] CANCELED - October 16 Meeting Message-ID: <9BF5852C-6834-499B-8A5C-F3CD5D3E64DD@att.com> Weekly Meeting Agenda : • Perform JIRA Management o Make sure JIRA Tasks identified in community meetings are getting created. o Manage priority . • Identify issues that need to be reprioritized, o Manage association/Milestones/Themed Sprints o Open Questions on Milestones/Tasks/Issues Priorities • Patchsets Management o Open Discussion about Comments or Patchsets o Help push Patchsets to the Finish Line • Any other Roadmap type Q/A and Mgmt. Activities Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mc981n at att.com Wed Oct 16 15:08:52 2019 From: mc981n at att.com (CARTER, MATTHEW) Date: Wed, 16 Oct 2019 15:08:52 +0000 Subject: [Airship-discuss] Ubuntu release In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A82204@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A82204@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <51C9FE08D3D651468541A95D10D248620B366071@MOSTLS1MSGUSRFB.ITServices.sbc.com> Hi Robson As Matt already stated, many of the components have recently been updated to add support for 18.04. We are still early in the development process for full-fledged support of 18.04, and one of the gaps that again Matt has identified is the treasuremap repo. We hope to address that soon, as we get further along in our testing. If you wish to attempt a deployment with 18.04, it should be possible by updating the treasuremap documents yourself and attempting a deployment using those updated docs. Outside of that, you’d also need to make sure you rebuild the MaaS images for 18.04 (see https://review.opendev.org/#/c/684138/), and use those updated images. Since we are still early in the process, we can’t guarantee there aren’t other issues with deploying 18.04. If you do attempt a deployment please let us know how it goes! We’d be happy to help along the way, as I think it’d closely align with our efforts. Thanks! - Matt From: MCEUEN, MATT Sent: Tuesday, October 15, 2019 5:09 PM To: Robson Ramos Barreto ; airship-discuss at lists.airshipit.org; MAHMOUDI, AHMAD ; CARTER, MATTHEW Subject: RE: [Airship-discuss] Ubuntu release Hi Robson, Migrating Airship from Ubuntu 16.04 to 18.04 at the host level is actually a work-in-progress, and we hope to have that represented as the default in treasuremap in the near future. Ahmad, MattC, is there anything Robson would need to be aware of if he wanted to run with bionic ahead of treasuremap being updated? Please see: https://review.opendev.org/#/c/685802/ https://review.opendev.org/#/c/684138/ Thanks, Matt From: Robson Ramos Barreto > Sent: Tuesday, October 15, 2019 4:48 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Ubuntu release Hi, I'm planing with Airship to deploy some Openstack regions and I have a doubt about the Ubuntu release (16.04) used to Genesis node and the rest of the nodes deployed by MaaS. I'd like to know if I can use Ubuntu 18.04 instead of Ubuntu 16.04 without any concern or if there is a roadmap. Thank you Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: From robson.rbarreto at gmail.com Wed Oct 16 18:40:26 2019 From: robson.rbarreto at gmail.com (Robson Ramos Barreto) Date: Wed, 16 Oct 2019 15:40:26 -0300 Subject: [Airship-discuss] Ubuntu release In-Reply-To: <51C9FE08D3D651468541A95D10D248620B366071@MOSTLS1MSGUSRFB.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A82204@MOSTLS1MSGUSRFF.ITServices.sbc.com> <51C9FE08D3D651468541A95D10D248620B366071@MOSTLS1MSGUSRFB.ITServices.sbc.com> Message-ID: Thank you guys, I'll have a look so I let you know how it goes Thanks Robson On Wed, Oct 16, 2019 at 12:09 PM CARTER, MATTHEW wrote: > Hi Robson > > > > As Matt already stated, many of the components have recently been updated > to add support for 18.04. We are still early in the development process for > full-fledged support of 18.04, and one of the gaps that again Matt has > identified is the treasuremap repo. We hope to address that soon, as we get > further along in our testing. > > If you wish to attempt a deployment with 18.04, it should be possible by > updating the treasuremap documents yourself and attempting a deployment > using those updated docs. Outside of that, you’d also need to make sure you > rebuild the MaaS images for 18.04 (see > https://review.opendev.org/#/c/684138/), and use those updated images. > Since we are still early in the process, we can’t guarantee there aren’t > other issues with deploying 18.04. > > > > If you do attempt a deployment please let us know how it goes! We’d be > happy to help along the way, as I think it’d closely align with our efforts. > > > > Thanks! > > > > - Matt > > > > *From:* MCEUEN, MATT > *Sent:* Tuesday, October 15, 2019 5:09 PM > *To:* Robson Ramos Barreto ; > airship-discuss at lists.airshipit.org; MAHMOUDI, AHMAD ; > CARTER, MATTHEW > *Subject:* RE: [Airship-discuss] Ubuntu release > > > > Hi Robson, > > > > Migrating Airship from Ubuntu 16.04 to 18.04 at the host level is actually > a work-in-progress, and we hope to have that represented as the default in > treasuremap in the near future. Ahmad, MattC, is there anything Robson > would need to be aware of if he wanted to run with bionic ahead of > treasuremap being updated? > > > > Please see: > > https://review.opendev.org/#/c/685802/ > > https://review.opendev.org/#/c/684138/ > > > > Thanks, > > Matt > > > > *From:* Robson Ramos Barreto > *Sent:* Tuesday, October 15, 2019 4:48 PM > *To:* airship-discuss at lists.airshipit.org > *Subject:* [Airship-discuss] Ubuntu release > > > > Hi, > > > > I'm planing with Airship to deploy some Openstack regions and I have a > doubt about the Ubuntu release (16.04) used to Genesis node and the rest of > the nodes deployed by MaaS. I'd like to know if I can use Ubuntu 18.04 > instead of Ubuntu 16.04 without any concern or if there is a roadmap. > > > > Thank you > > > > Regards > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rv6848 at att.com Wed Oct 16 19:08:35 2019 From: rv6848 at att.com (VAN WYK, RYAN L) Date: Wed, 16 Oct 2019 19:08:35 +0000 Subject: [Airship-discuss] Travel Planning Message-ID: <9B4615ED4FEDC74EA1FAF8B11F578BFA55A5AD9A@MOSTLS1MSGUSREG.ITServices.sbc.com> All, one discussion point on the TC meeting today was when and where to make a splash publicly re Airship 2.0 reaching its BETA milestone. Given this is targeted by the end of Feb/Early March, we are planning on trying to have talks and potentially a keynote @ KubeCon March 31 - April 2 in Amsterdam. We would then follow this with a lot of focus on the delivery on Airship 2.0 (May) in the June OSF event that is planned in North America. Please keep this in mind for any travel planning in 2020. Thanks, Ryan van Wyk Airship TC Member -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Oct 16 20:13:29 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 16 Oct 2019 20:13:29 +0000 Subject: [Airship-discuss] Welcome Stas to the WC Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A82796@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, Nominations for the special election of the Airship Working Committee's fifth seat have closed. Because exactly one member of the community has nominated, we are able to forego formal voting. Please welcome Stanislav Egorov[1] (segorov) to the Airship Working Committee! I have worked with Stas in the Airship community for a while now, and I know he'll make an excellent team member to complete the WC. He has already played a key role in ensuring that the Airship project and development efforts within Mirantis remain aligned in the community, so continuing those responsibilities within the WC should be a natural fit. Thanks, Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/candidates/2019/WC/segorov at mirantis.com From ashlee at openstack.org Wed Oct 16 20:18:51 2019 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 16 Oct 2019 15:18:51 -0500 Subject: [Airship-discuss] Airship Working Session at KubeCon Message-ID: <3B3DE5F0-22B2-43A8-AED8-F3673BB986C4@openstack.org> Hi everyone, We’ve been floating the idea of an Airship-focused, PTG-style working session around KubeCon in San Diego, so I wanted to confirm details around the space we can provide. We’ll have the Cobalt Room (501) at the Hilton on Monday, November 18 from 12:30-6:30pm, with space for about 15 people. Below is an etherpad where you can indicate if you plan on attending. Sounds like 1:00pm will be a good target start time. Denise (copied) will be onsite if you all need any assistance. https://etherpad.openstack.org/p/airship-kubecon-san-diego Exact Location: Cobalt Room (501) Hilton San Diego Bayfrot 1 Park Blvd, San Diego, CA Thanks, Ashlee Ashlee Ferguson OpenStack Foundation ashlee at openstack.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From kire at kth.se Wed Oct 16 21:52:15 2019 From: kire at kth.se (=?utf-8?Q?Jan-Erik_M=C3=A5ngs?=) Date: Wed, 16 Oct 2019 23:52:15 +0200 Subject: [Airship-discuss] Airship Working Session at KubeCon In-Reply-To: <3B3DE5F0-22B2-43A8-AED8-F3673BB986C4@openstack.org> References: <3B3DE5F0-22B2-43A8-AED8-F3673BB986C4@openstack.org> Message-ID: <8EE6DF08-3A38-43F3-91A0-DF8E4824D65A@kth.se> Matt, you did a Doodle on KubeCon, right? Did you get any response? I think Monday is difficult as there are tons of other events that day (I’m planning to attend the Network Service Mesh event NSMcon myself). Friday Nov 22, or Sunday Nov 17 would be better, or just some evening. Best regards Jan-Erik > On 16 Oct 2019, at 22:19, Ashlee Ferguson wrote: > >  Hi everyone, > > We’ve been floating the idea of an Airship-focused, PTG-style working session around KubeCon in San Diego, so I wanted to confirm details around the space we can provide. We’ll have the Cobalt Room (501) at the Hilton on Monday, November 18 from 12:30-6:30pm, with space for about 15 people. Below is an etherpad where you can indicate if you plan on attending. Sounds like 1:00pm will be a good target start time. Denise (copied) will be onsite if you all need any assistance. > > https://etherpad.openstack.org/p/airship-kubecon-san-diego > > Exact Location: > Cobalt Room (501) > Hilton San Diego Bayfrot > 1 Park Blvd, San Diego, CA > > > Thanks, > Ashlee > > > Ashlee Ferguson > OpenStack Foundation > ashlee at openstack.org > > > > > _______________________________________________ > 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 MM9745 at att.com Wed Oct 16 22:06:21 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 16 Oct 2019 22:06:21 +0000 Subject: [Airship-discuss] Airship Working Session at KubeCon In-Reply-To: <8EE6DF08-3A38-43F3-91A0-DF8E4824D65A@kth.se> References: <3B3DE5F0-22B2-43A8-AED8-F3673BB986C4@openstack.org> <8EE6DF08-3A38-43F3-91A0-DF8E4824D65A@kth.se> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A829BC@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hey Jan-Erik, Yes, here are the results: https://www.surveymonkey.com/results/SM-HS35GPGJ7/ The Monday time slot was the highly preferred one by the voters – I know that some folks won’t be able to be there for Sunday or Friday, and there are also a number of nighttime events that may be difficult to schedule around. I think conflicts might be inevitable no matter what time slot we choose, unfortunately. It looks like the Service Mesh event is scheduled from 8am-5pm Monday; would you be able to duck out a few minutes early and join us? I’m happy to stay till 6. Worst case we can definitely circle back as a smaller group during the week and sync up at a convenient time. Thanks, Matt From: Jan-Erik Mångs Sent: Wednesday, October 16, 2019 4:52 PM To: Ashlee Ferguson Cc: airship-discuss at lists.airshipit.org; Claire Massey ; Denise Ridolfo Subject: Re: [Airship-discuss] Airship Working Session at KubeCon Matt, you did a Doodle on KubeCon, right? Did you get any response? I think Monday is difficult as there are tons of other events that day (I’m planning to attend the Network Service Mesh event NSMcon myself). Friday Nov 22, or Sunday Nov 17 would be better, or just some evening. Best regards Jan-Erik On 16 Oct 2019, at 22:19, Ashlee Ferguson > wrote:  Hi everyone, We’ve been floating the idea of an Airship-focused, PTG-style working session around KubeCon in San Diego, so I wanted to confirm details around the space we can provide. We’ll have the Cobalt Room (501) at the Hilton on Monday, November 18 from 12:30-6:30pm, with space for about 15 people. Below is an etherpad where you can indicate if you plan on attending. Sounds like 1:00pm will be a good target start time. Denise (copied) will be onsite if you all need any assistance. https://etherpad.openstack.org/p/airship-kubecon-san-diego Exact Location: Cobalt Room (501) Hilton San Diego Bayfrot 1 Park Blvd, San Diego, CA Thanks, Ashlee Ashlee Ferguson OpenStack Foundation ashlee at openstack.org _______________________________________________ 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 claire at openstack.org Thu Oct 17 18:52:33 2019 From: claire at openstack.org (Claire Massey) Date: Thu, 17 Oct 2019 13:52:33 -0500 Subject: [Airship-discuss] Travel Planning In-Reply-To: <9B4615ED4FEDC74EA1FAF8B11F578BFA55A5AD9A@MOSTLS1MSGUSREG.ITServices.sbc.com> References: <9B4615ED4FEDC74EA1FAF8B11F578BFA55A5AD9A@MOSTLS1MSGUSREG.ITServices.sbc.com> Message-ID: <53B6C9B9-3658-4310-8DBC-C545B8771191@openstack.org> Hi everyone, Just want to flag that the KubeCon Amsterdam CFP deadline will be here before we know it! December 4, 2019 is the CFP deadline. You can submit talks now, here - https://events19.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2020/call-for-proposals/ . While it may be too soon to have all of the details to include in an abstract, I still suggest submitting a presentation, demo or workshop about Airship 2.0. If the talk is accepted you can always request the abstract to be updated later. Cheers, Claire > On Oct 16, 2019, at 2:08 PM, VAN WYK, RYAN L wrote: > > All, one discussion point on the TC meeting today was when and where to make a splash publicly re Airship 2.0 reaching its BETA milestone. > > Given this is targeted by the end of Feb/Early March, we are planning on trying to have talks and potentially a keynote @ KubeCon March 31 – April 2 in Amsterdam. We would then follow this with a lot of focus on the delivery on Airship 2.0 (May) in the June OSF event that is planned in North America. > > Please keep this in mind for any travel planning in 2020. > > Thanks, > > Ryan van Wyk > Airship TC Member > > _______________________________________________ > 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 pramchan at yahoo.com Mon Oct 21 21:45:20 2019 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Mon, 21 Oct 2019 21:45:20 +0000 (UTC) Subject: [Airship-discuss] [YAML-SIG] Airship Beta MVP - Strawman Proposal Discussions References: <1937258569.61803.1571694320302.ref@mail.yahoo.com> Message-ID: <1937258569.61803.1571694320302@mail.yahoo.com> Hi all,  YAMSIG brought to notice old Airship 1.0 terminology for defining BareMetalRequirements & NodeDef This is to describe Site/ Type / Composite / Function Naming convention in Treasuremap v2. https://etherpad.openstack.org/p/Airship_Yaml (referOct 12 Discussions) Here is the new Jira Story added by RodolfoPacheco. https://airship.atlassian.net/browse/AIR-185   I will assume following and have started the documentation ingoogle docs added to YAML SIG etherpad as well 1.     StrawmanProposal for Identifying Site Type and associated MVP BareMetal Descriptor. 2.     Createa Draft Proposal for What a Site should look like for Airship v2? 3.     Outlineyour thoughts/ideas on your initial judgement/ideas to improve Airship v2 basedon three configurations available in Airship 1.0: 4.     Getfeedback from YAML SIG 5.     UpdateDraft till Final and Summarize the Conclusion.   - airshipctl cluster  https://docs.google.com/document/d/15zRU5c5cCJLdFzE1P9UArdu19u-nRVrYk8p_JKTmhK0/edit?usp=sharing     +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Airship MVP Beta (V2) -YAML SIG Google Doc sharing for Treasuremap StrawmanProposal +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ·       Referto above link,  Matt & Jared, if you can add your tables T1(Seaworthy) & T2 (Airsloop)   ·        Let me know your suggestions of  Airship 2.0 terminology and the Topology toclarify hierarchy (Region, Zone(AZ), Cluster, Site, Node) data elements,labels, annotations, and terms we will use different from Airship 1.0 andinterpretations we appear to have now. Of-course code is king, and k8s is default,still we need to rationalize this for v2(Beta) branch now for design anddeployment of BareMetal Node and Cluster using Metal-3/Cluster APIs, OSHOperator, Ironic plus all Plugins we plan to use modules like Kustomize etc. Thanks Prakash -------------- next part -------------- An HTML attachment was scrubbed... URL: From pramchan at yahoo.com Tue Oct 22 00:57:49 2019 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Tue, 22 Oct 2019 00:57:49 +0000 (UTC) Subject: [Airship-discuss] [PTG-Shanghai] Please Register your name for participation in MVP Beta (v2) contributions References: <992465261.132510.1571705869965.ref@mail.yahoo.com> Message-ID: <992465261.132510.1571705869965@mail.yahoo.com> Hi all, We seek active participation from community to enable Airship design and deployment for new release v2 in progress.Join us at PTG & mini-PTG to complete the Specs for MVP Beta (v2) before we get to November monthly sprint targets. PTG at Shnnghai -  Airship PTG Ussuri Half day Thursday Nov 7th, full day Friday Nov 8th https://etherpad.openstack.org/p/airship-ptg-ussuri Airship KubeCon mini-PTG San DiegoMonday, 12:30-6:30 [planning on kicking off @ 1pm] https://etherpad.openstack.org/p/airship-kubecon-san-diego ThanksPrakash / For Airship PTG/mini-PTGs -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Tue Oct 22 20:47:49 2019 From: ashlee at openstack.org (Ashlee Ferguson) Date: Tue, 22 Oct 2019 15:47:49 -0500 Subject: [Airship-discuss] Fwd: [OpenStack Foundation] October 22, 2019 Board Meeting References: Message-ID: <26FF8C2F-DE8E-40C4-9F50-3F79CACA2828@openstack.org> Hi everyone, We wanted to congratulate the Airship community on its confirmation by the OSF Board of Directors today. You can read the full notes in Jonathan Bryce’s email to the Foundation mailing list below. Thank you to everyone who provided feedback and collaborated with the Airship community to reach this milestone. You can view the presentation that was shared with the board earlier today here: https://www.airshipit.org/images/airship-confirmation-review-for-the-osf-board.pdf/ Congratulations Airship! Cheers, Ashlee > Begin forwarded message: > > From: Jonathan Bryce > Subject: [OpenStack Foundation] October 22, 2019 Board Meeting > Date: October 22, 2019 at 3:03:52 PM CDT > To: foundation at lists.openstack.org > > Hi everyone, > > The OSF Board of Directors met today. The agenda was posted online[1]. The primary purpose of today’s meeting was confirmation review of the Airship project, although I opened the meeting by giving a review of some community and market stats as well as information about the recently completed Train development cycle for OpenStack. > > Four members of the Airship community, Matt McEuen, Alex Hughes, Kaspars Skels and Jaesuk Ahn, gave a detailed presentation[2] on the project, its progress during the pilot phase and how it meets the confirmation guidelines the Board has adopted. The Board raised several questions with the Airship team, reviewed feedback from the OpenStack TC and discussed the project in general. One question that created quite a bit of discussion dealt with licensing of golang libraries that may be pulled in as dependencies for certain Airship components. The Board felt that this was something that could be reviewed and dealt with by the project and OSF resources to make sure any dependencies comply with our overall license policies. With this agreed on, the Board voted unanimously to confirm Airship as a new top-level Open Infrastructure Project in the Foundation and the meeting concluded. > > Congrats to the Airship team and community! > > Jonathan > > 1. https://wiki.openstack.org/wiki/Governance/Foundation/22October2019BoardMeeting > 2. https://www.airshipit.org/images/airship-confirmation-review-for-the-osf-board.pdf/ > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation From rp2723 at att.com Thu Oct 24 16:57:37 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 24 Oct 2019 16:57:37 +0000 Subject: [Airship-discuss] [sig][airship-ui] Meeting October 25, 2019 - Cancelled Message-ID: I need to cancel this meeting tomorrow Will continue the discussion next Week Nov 1. For those interested in this discussion, Please try to get https://github.com/vmware-tanzu/octant functional in your dev environments We will continue to focus in the MVP needs. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Oct 24 19:06:09 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 24 Oct 2019 19:06:09 +0000 Subject: [Airship-discuss] Shanghai/KubeCon etherpads Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A8838A@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi, Airship team, With both the Shanghai summit and KubeCon around the corner, just a reminder: if you're able to join our design/dev discussions at these conferences, please add your name and anything you'd like to discuss to the agenda. This will help us to plan and make sure we're well prepared. Shanghai PTG: https://etherpad.openstack.org/p/airship-ptg-ussuri KubeCon Meeting: https://etherpad.openstack.org/p/airship-kubecon-san-diego Thanks, Matt From thierry at openstack.org Mon Oct 28 15:08:58 2019 From: thierry at openstack.org (Thierry Carrez) Date: Mon, 28 Oct 2019 16:08:58 +0100 Subject: [Airship-discuss] [ptg] ptgbot HOWTO Message-ID: <8c97aa34-17bc-4dc3-942c-2fbc73595717@openstack.org> Hi everyone, In a few days, some contributor teams will meet in Shanghai for our 6th Project Teams Gathering. The event is organized around separate 'tracks' (generally tied to a specific team/group). Topics of discussion are loosely scheduled in those tracks, based on the needs of the attendance. This allows to maximize attendee productivity, but the downside is that it can make the event a bit confusing to navigate. To mitigate that issue, we are using an IRC bot to expose what's happening currently at the event at the following page: http://ptg.openstack.org/ptg.html It is therefore useful to have a volunteer in each room who makes use of the PTG bot to communicate what's happening. This is done by joining the #openstack-ptg IRC channel on Freenode and voicing commands to the bot. Usage of the bot is of course optional, but in past editions it was really useful to help attendees successfully navigate this dynamic event. How to keep attendees informed of what's being discussed in your room --------------------------------------------------------------------- To indicate what's currently being discussed, you will use the track name hashtag (found in the "Scheduled tracks" section on the above page), with the 'now' command: #TRACK now Example: #swift now brainstorming improvements to the ring You can also mention other track names to make sure to get people attention when the topic is transverse: #ops-meetup now discussing #cinder pain points There can only be one 'now' entry for a given track at a time. To indicate what will be discussed next, you can enter one or more 'next' commands: #TRACK next Example: #api-sig next at 2pm we'll be discussing pagination woes Note that in order to keep content current, entering a new 'now' command for a track will automatically erase any 'next' entry for that track. Finally, if you want to clear all 'now' and 'next' entries for your track, you can issue the 'clean' command: #TRACK clean Example: #ironic clean How to make your track etherpad easily found -------------------------------------------- We traditionally use an etherpad for each track, to plan and document the topics being discussed. In the past we used a wiki to list those etherpads, but now we publish a list of them at: http://ptg.openstack.org/etherpads.html PTGbot generates a default URL for your etherpad. If you already have one, you can update the URL by issuing the following command: #TRACK etherpad How to book reservable rooms ---------------------------- In Shanghai we will have some additional reservable space for extra un-scheduled discussions. The PTG bot page shows which track is allocated to which room, as well as available reservable space, with a slot code (room name - time slot) that you can use to issue a 'book' command to the PTG bot: #TRACK book Example: #release-management book Ocata-WedA1 Any track can book additional space and time using this system. If your topic of discussion does not fall into an existing track, it is easy to add a track on the fly. Just ask PTG bot admins (ttx, diablo_rojo...) on the channel to create a track for you (which they can do by getting op rights and issuing a ~add command). For more information on the bot commands, please see: https://opendev.org/openstack/ptgbot/src/branch/master/README.rst Let me know if you have any additional questions. -- Thierry Carrez (ttx) From MM9745 at att.com Tue Oct 29 16:33:27 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 29 Oct 2019 16:33:27 +0000 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: * Alexander Hughes (alexanderhughes) * Dmitry Ukov (dukov) * Roman Gorshunov (roman_g) Airshipctl is a fairly new project, and so doesn't have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From am240k at att.com Tue Oct 29 16:55:49 2019 From: am240k at att.com (MEADOWS, ALAN) Date: Tue, 29 Oct 2019 16:55:49 +0000 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <15C64B16127ACA46A5BD581D320C788187079B92@MISOUT7MSGUSRCE.ITServices.sbc.com> +1 Dmitry From: MCEUEN, MATT Sent: Tuesday, October 29, 2019 9:33 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex Airship team, Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: * Alexander Hughes (alexanderhughes) * Dmitry Ukov (dukov) * Roman Gorshunov (roman_g) Airshipctl is a fairly new project, and so doesn't have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Oct 29 17:16:16 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 29 Oct 2019 17:16:16 +0000 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex Message-ID: * +1 Dmitry Ukov (dukov) Regards Rodolfo Pacheco Home/Office 732 5337671 From: "MCEUEN, MATT" Date: Tuesday, October 29, 2019 at 12:36 PM To: "airship-discuss at lists.airshipit.org" Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: * Alexander Hughes (alexanderhughes) * Dmitry Ukov (dukov) * Roman Gorshunov (roman_g) Airshipctl is a fairly new project, and so doesn’t have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From kkalynovskyi at mirantis.com Tue Oct 29 17:52:46 2019 From: kkalynovskyi at mirantis.com (Kostiantyn Kalynovskyi) Date: Tue, 29 Oct 2019 12:52:46 -0500 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: References: Message-ID: +1 Dmitry Ukov (dukov) On Tue, Oct 29, 2019 at 12:18 PM PACHECO, RODOLFO J wrote: > > - +1 Dmitry Ukov (dukov) > > > > > > Regards > > > > *Rodolfo Pacheco* > > > > *Home/Office* 732 5337671 > > > > *From: *"MCEUEN, MATT" > *Date: *Tuesday, October 29, 2019 at 12:36 PM > *To: *"airship-discuss at lists.airshipit.org" < > airship-discuss at lists.airshipit.org> > *Subject: *[Airship-discuss] [airship-discuss] Nominations for airshipctl > Cores: Roman, Dmitry, & Alex > > > > ****Security Advisory:* This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > > Airship team, > > > > Based on their record of quality code review and substantial/meaningful > code contributions to the airshipctl project, as well as on needs of the > community, I would like to nominate the following individuals as core > reviewers for airshipctl: > > > > - Alexander Hughes (alexanderhughes) > - Dmitry Ukov (dukov) > - Roman Gorshunov (roman_g) > > > > Airshipctl is a fairly new project, and so doesn’t have a long history of > contributions yet. However, these folks have all proven their dedication > through substantial and meaningful code review, participation in the > design, and initial contributions to the project. > > > > Per our community current airshipctl Core Reviewers are invited to reply > with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all > three candidates, otherwise please spell out votes individually for the > candidates. > > > > Thanks, > > Matt > > > _______________________________________________ > 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 anoskov at mirantis.com Tue Oct 29 17:59:13 2019 From: anoskov at mirantis.com (Alexander Noskov) Date: Tue, 29 Oct 2019 12:59:13 -0500 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: References: Message-ID: <4B08DEF1-B8DE-4DE0-89C9-1452623829B6@mirantis.com> +1 Dmitry Ukov (dukov) > On Oct 29, 2019, at 12:52 PM, Kostiantyn Kalynovskyi wrote: > > +1 Dmitry Ukov (dukov) > > On Tue, Oct 29, 2019 at 12:18 PM PACHECO, RODOLFO J > wrote: > +1 Dmitry Ukov (dukov) > > > > > Regards > > > > Rodolfo Pacheco > > > > Home/Office 732 5337671 > > > > From: "MCEUEN, MATT" > > Date: Tuesday, October 29, 2019 at 12:36 PM > To: "airship-discuss at lists.airshipit.org " > > Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex > > > > ***Security Advisory: This Message Originated Outside of AT&T *** > Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. > > > > Airship team, > > > > Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: > > > > Alexander Hughes (alexanderhughes) > Dmitry Ukov (dukov) > Roman Gorshunov (roman_g) > > > Airshipctl is a fairly new project, and so doesn’t have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. > > > > Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. > > > > Thanks, > > Matt > > > > _______________________________________________ > 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 MM9745 at att.com Tue Oct 29 18:12:35 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 29 Oct 2019 18:12:35 +0000 Subject: [Airship-discuss] [aiship-discuss] No IRC meeting on 11/5 Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A8977B@MOSTLS1MSGUSRFF.ITServices.sbc.com> Team, Due to the Open Infra Summit in Shanghai next week, we'll be skipping our regularly scheduled Tuesday 11/5 IRC team meeting. Good luck to everyone who is driving Airship forward at the Summit & PTG! Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From segorov at mirantis.com Tue Oct 29 18:31:56 2019 From: segorov at mirantis.com (Stas Egorov) Date: Tue, 29 Oct 2019 11:31:56 -0700 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <41488DA6-6A24-4BC3-A89F-579DD4E35D2E@mirantis.com> +1 Dmitry Ukov (dukov) > On Oct 29, 2019, at 9:33 AM, MCEUEN, MATT wrote: > > Airship team, > > Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: > > Alexander Hughes (alexanderhughes) > Dmitry Ukov (dukov) > Roman Gorshunov (roman_g) > > Airshipctl is a fairly new project, and so doesn’t have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. > > Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. > > Thanks, > Matt > > _______________________________________________ > 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 ca846m at att.com Tue Oct 29 18:41:10 2019 From: ca846m at att.com (ANDERSON, CRAIG) Date: Tue, 29 Oct 2019 18:41:10 +0000 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: <15C64B16127ACA46A5BD581D320C788187079B92@MISOUT7MSGUSRCE.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> <15C64B16127ACA46A5BD581D320C788187079B92@MISOUT7MSGUSRCE.ITServices.sbc.com> Message-ID: +1 From: MCEUEN, MATT Sent: Tuesday, October 29, 2019 9:33 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex Airship team, Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: * Alexander Hughes (alexanderhughes) * Dmitry Ukov (dukov) * Roman Gorshunov (roman_g) Airshipctl is a fairly new project, and so doesn't have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Wed Oct 30 12:08:25 2019 From: claire at openstack.org (Claire Massey) Date: Wed, 30 Oct 2019 07:08:25 -0500 Subject: [Airship-discuss] Shanghai/KubeCon etherpads In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970A8838A@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970A8838A@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: With that in mind, would you like to keep or skip the standing WC calls on Nov 4 (during the summit) and Nov 18 (day of the Airship meetup at KubeCon)? LMK and I’ll update the meeting invite. Thanks, Claire > On Oct 24, 2019, at 2:08 PM, MCEUEN, MATT wrote: > > Hi, Airship team, > > With both the Shanghai summit and KubeCon around the corner, just a reminder: if you're able to join our design/dev discussions at these conferences, please add your name and anything you'd like to discuss to the agenda. This will help us to plan and make sure we're well prepared. > > Shanghai PTG: https://etherpad.openstack.org/p/airship-ptg-ussuri > KubeCon Meeting: https://etherpad.openstack.org/p/airship-kubecon-san-diego > > Thanks, > Matt > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss From claire at openstack.org Wed Oct 30 12:10:46 2019 From: claire at openstack.org (claire at openstack.org) Date: Wed, 30 Oct 2019 12:10:46 +0000 Subject: [Airship-discuss] Updated invitation: Airship TC / OSF Sync meetings @ Monthly from 9am to 10am on the fourth Thursday from Thu Sep 26 to Wed Nov 27 (CDT) (airship-discuss@lists.airshipit.org) Message-ID: <0000000000006cdf7305961f9f8e@google.com> This event has been changed. Title: Airship TC / OSF Sync meetings Notes - https://etherpad.openstack.org/p/2019_Airship_OSF_sync Join Zoom Meeting https://zoom.us/j/384128660 One tap mobile +16699006833,,384128660# US (San Jose) +16468769923,,384128660# US (New York) Dial by your location +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) Meeting ID: 384 128 660 Find your local number: https://zoom.us/u/adA54OXFxP When: Monthly from 9am to 10am on the fourth Thursday from Thu Sep 26 to Wed Nov 27 Central Time - Chicago (changed) Where: https://zoom.us/j/384128660 Calendar: airship-discuss at lists.airshipit.org Who: * claire at openstack.org - organizer * airship-discuss at lists.airshipit.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=XzcwcmoyaGhpNzUzNGNiYTE2b29rYWI5azhoMzRjYmEyNzUyNDhiYTY4NG8zMGdxMTZzcGs4aGEyOGcgYWlyc2hpcC1kaXNjdXNzQGxpc3RzLmFpcnNoaXBpdC5vcmc&tok=MjAjY2xhaXJlQG9wZW5zdGFjay5vcmcyNzJjNTUxZmYzOWRjNTkyZTBlMTVjMGI1NDMzZWRiMTRkZWEwNjk1&ctz=America%2FChicago&hl=en&es=0 Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account airship-discuss at lists.airshipit.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 2813 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: invite.ics Type: application/ics Size: 2889 bytes Desc: not available URL: From MM9745 at att.com Wed Oct 30 13:39:07 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 30 Oct 2019 13:39:07 +0000 Subject: [Airship-discuss] Shanghai/KubeCon etherpads In-Reply-To: References: <7C64A75C21BB8D43BD75BB18635E4D8970A8838A@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970A89B25@MOSTLS1MSGUSRFF.ITServices.sbc.com> Let's please keep them, I think we'll still have quorum to get some good work done. We can end early in case of a light agenda. I'd say we could reschedule to 11/ 11, except I know the full WC won't be able to make that one either. Thanks for checking! Matt -----Original Message----- From: Claire Massey Sent: Wednesday, October 30, 2019 7:08 AM To: MCEUEN, MATT Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Shanghai/KubeCon etherpads With that in mind, would you like to keep or skip the standing WC calls on Nov 4 (during the summit) and Nov 18 (day of the Airship meetup at KubeCon)? LMK and I’ll update the meeting invite. Thanks, Claire > On Oct 24, 2019, at 2:08 PM, MCEUEN, MATT wrote: > > Hi, Airship team, > > With both the Shanghai summit and KubeCon around the corner, just a reminder: if you're able to join our design/dev discussions at these conferences, please add your name and anything you'd like to discuss to the agenda. This will help us to plan and make sure we're well prepared. > > Shanghai PTG: https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_airship-2Dptg-2Dussuri&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=7q1EkQH93HdEqET86qOXtpYWObNiIVLB-F4YYesoRtM&s=krdpDG98jMupm2NBZJK5aXu8GUGg5nwbfnztEvRDv2A&e= > KubeCon Meeting: https://urldefense.proofpoint.com/v2/url?u=https-3A__etherpad.openstack.org_p_airship-2Dkubecon-2Dsan-2Ddiego&d=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=7q1EkQH93HdEqET86qOXtpYWObNiIVLB-F4YYesoRtM&s=GjYoQfj3F08FSkIwJh2M_TAe-W7IkG4y07YID0NAsHc&e= > > Thanks, > Matt > > _______________________________________________ > 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=DwIFaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=_C5hC_103uW491yNPPpNmA&m=7q1EkQH93HdEqET86qOXtpYWObNiIVLB-F4YYesoRtM&s=mvKFdA72w9MzAbYv9il1x4VRASAFf5yWV2_q79ZPDP8&e= From ih616h at att.com Wed Oct 30 13:46:25 2019 From: ih616h at att.com (HOWELL, IAN) Date: Wed, 30 Oct 2019 13:46:25 +0000 Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex In-Reply-To: References: <7C64A75C21BB8D43BD75BB18635E4D8970A896AE@MOSTLS1MSGUSRFF.ITServices.sbc.com> <15C64B16127ACA46A5BD581D320C788187079B92@MISOUT7MSGUSRCE.ITServices.sbc.com> Message-ID: <2A7C8018C01D6044934139A38A7891EC13D3C158@MOSTLS1MSGUSREH.ITServices.sbc.com> +1 Dmitry Ukov Thanks, Ian From: MCEUEN, MATT Sent: Tuesday, October 29, 2019 9:33 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] [airship-discuss] Nominations for airshipctl Cores: Roman, Dmitry, & Alex Airship team, Based on their record of quality code review and substantial/meaningful code contributions to the airshipctl project, as well as on needs of the community, I would like to nominate the following individuals as core reviewers for airshipctl: * Alexander Hughes (alexanderhughes) * Dmitry Ukov (dukov) * Roman Gorshunov (roman_g) Airshipctl is a fairly new project, and so doesn't have a long history of contributions yet. However, these folks have all proven their dedication through substantial and meaningful code review, participation in the design, and initial contributions to the project. Per our community current airshipctl Core Reviewers are invited to reply with a +1/-1 by EOD next Tuesday (11/5). A lone +1/-1 will apply to all three candidates, otherwise please spell out votes individually for the candidates. Thanks, Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: From claire at openstack.org Wed Oct 30 14:13:55 2019 From: claire at openstack.org (Claire Massey) Date: Wed, 30 Oct 2019 09:13:55 -0500 Subject: [Airship-discuss] TC and WC Zoom Meetings Are Recorded Message-ID: <969CF616-AAEC-43D9-B2AE-5EBC206D7221@openstack.org> Hi everyone, Friendly public service announcement…. If you’ve previously attended any of the standing Airship TC[1] or WC[2] calls then you know that they are recorded. Following the meeting the recording link is added to the wiki along with the etherpad with meeting agendas and notes. In order to prevent myself from becoming a bottleneck I’ve gone ahead and set the Airship Zoom link to auto record each time a meeting is started using the link. If you are hosting a meeting, please also notify the participants that the meeting is being recorded. Zoom should also provide an audio message upon joining, “this call is being recorded”. Let me know if you have any questions. Thanks, Claire [1] https://wiki.openstack.org/wiki/Airship/Airship-TC [2] https://wiki.openstack.org/wiki/Airship/Airship-WC -------------- next part -------------- An HTML attachment was scrubbed... URL: From garima.misra at calsoftinc.com Tue Oct 22 15:08:02 2019 From: garima.misra at calsoftinc.com (Garima Misra) Date: Tue, 22 Oct 2019 15:08:02 -0000 Subject: [Airship-discuss] Query related to Airskiff deployment Message-ID: <608de1fa-d993-14be-b567-3cf25d31af5f@calsoftinc.com> Hello Everyone, I am trying to deploy Airskiff using following URL: *https://airship-treasuremap.readthedocs.io/en/latest/airskiff.html* And in one of the step /(Deploy Kubernetes with Minikube) /ta script file "./tools/deployment/common/005-deploy-k8s.sh" is mentioned, which is missing from the github repository. Thus, there is no installation of k8s done in this case. *Note:* I am using Master branch in this case. Moreover, there is no "/tools/deployment/common" folder in 'treasuremap' directory. Please suggest any resolutions to these. -- Thanks and Regards, *Garima Misra* -------------- next part -------------- An HTML attachment was scrubbed... URL: From anwar.hassen at est.tech Wed Oct 16 09:39:43 2019 From: anwar.hassen at est.tech (Anwar Hassen) Date: Wed, 16 Oct 2019 09:39:43 -0000 Subject: [Airship-discuss] Gap Analysis studies result In-Reply-To: References: , Message-ID: Hi, This email has arrived after serveral weeks. It could be that I was not approved for the mailing list and was in the pipeline. Due to that the content of the email is no longer relevant and can be ignored. However, the studies can be found at https://github.com/Nordix/airship-clusterapi-docs/blob/master/airship/README.md Br. Anwar ________________________________ From: Jan-Erik Mångs Sent: Wednesday, October 16, 2019 11:36 AM To: Anwar Hassen Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Gap Analysis studies result Hi Anwar, Is the link correct? Best regards /Jan-Erik On 5 Sep 2019, at 14:42, Anwar Hassen > wrote: Hello, This is in reference to the gap analysis list created during our face to face meeting in June, f2f notes We have done some studies with respect to the action points. Please see this link for the result. Would you please review and give comments. Best regards, Anwar Hassen _______________________________________________ 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: