From alexander.w.hughes at accenture.com Mon Mar 9 11:48:50 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Mon, 9 Mar 2020 11:48:50 +0000 Subject: [Airship-discuss] Airship Community Events: US Daylight Saving Time Message-ID: Hello Airship Community, Please be advised that meetings are scheduled in US Central Time. As a result of daylight saving time over the weekend meeting times for those that do not observe daylight saving time will be moving backwards by 1 hour. For example, a meeting previously held at 10:00 CST / 16:00 UTC will be changing to 10:00 CDT / 15:00 UTC. Please be on the lookout for updated calendar invitations from meeting organizers. For more information please see the Airship wiki which was updated this morning to reflect the time changes. Regards, Alexander Hughes ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Mon Mar 9 18:59:28 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Mon, 9 Mar 2020 13:59:28 -0500 Subject: [Airship-discuss] New Zoom Reminder Message-ID: <936ACED0-75BD-46DC-8FAD-7A11356301D8@openstack.org> Hey all, Just a reminder that we’ve switched to a new Zoom link for WC and TC calls - https://zoom.us/j/9725717388 See you all in a couple minutes for the WC call! Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.w.hughes at accenture.com Mon Mar 9 19:38:49 2020 From: alexander.w.hughes at accenture.com (Hughes, Alexander W.) Date: Mon, 9 Mar 2020 19:38:49 +0000 Subject: [Airship-discuss] Airship Community Events: US Daylight Saving Time In-Reply-To: References: Message-ID: Hello Airship Community, Bumping this e-mail thread, apologies if you receive it twice - some community members did not receive the initial message. Regards, Alexander Hughes From: Hughes, Alexander W. Sent: Monday, March 9, 2020 7:49 AM To: airship-discuss at lists.airshipit.org Subject: Airship Community Events: US Daylight Saving Time Hello Airship Community, Please be advised that meetings are scheduled in US Central Time. As a result of daylight saving time over the weekend meeting times for those that do not observe daylight saving time will be moving backwards by 1 hour. For example, a meeting previously held at 10:00 CST / 16:00 UTC will be changing to 10:00 CDT / 15:00 UTC. Please be on the lookout for updated calendar invitations from meeting organizers. For more information please see the Airship wiki which was updated this morning to reflect the time changes. Regards, Alexander Hughes ________________________________ This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy. ______________________________________________________________________________________ www.accenture.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Mon Mar 9 19:52:41 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 9 Mar 2020 19:52:41 +0000 Subject: [Airship-discuss] Airship Community Events: US Daylight Savings Time Message-ID: Hello all, We have been experiencing issues with the airship-discuss mail server, and some messages have not reached everyone. Please see the email below from Alex Hughes regarding Airship community meeting times. Regards, Drew Walters Airship Working Committee > Hello Airship Community, > Please be advised that meetings are scheduled in US Central Time. As a > result of daylight saving time over the weekend meeting times for those that > do not observe daylight saving time will be moving backwards by 1 hour. > For example, a meeting previously held at 10:00 CST / 16:00 UTC will be > changing to 10:00 CDT / 15:00 UTC. > Please be on the lookout for updated calendar invitations from meeting > organizers. For more information please see the Airship > wiki which was updated this morning > to reflect the time changes. > Regards, > Alexander Hughes From digambarpat at gmail.com Tue Mar 10 16:17:18 2020 From: digambarpat at gmail.com (Digambar Patil) Date: Tue, 10 Mar 2020 21:47:18 +0530 Subject: [Airship-discuss] [BMO][HCC] New Project Hardware-Classification-Controller for Hardware validation and labelling Message-ID: Hi Airship, We (DellTeam) have started hardware-classification-controller project under Metal3 repo some days back after having multiple discussions with Metal3 community. HCC proposal - https://github.com/metal3-io/metal3-docs/pull/60 Idea here is to classify Hosts and label the Host CR's which is matching to provided profile which will be helpful for user to fetch all the labelled hosts based on profiles and plan for futher provisioning. Currently we are implementing classification filter for supporting Minimum hardware configuration. https://github.com/metal3-io/hardware-classification-controller/pull/3 We are closely working with Metal3 community since last couple of weeks. I also had brought this topic couple of times in our last meetings to finalize the Profiles for Airship. I have filed couple of issues under Airshipctl repo. Define Host profile - https://github.com/airshipit/airshipctl/issues/78 Document for deployment of HCC CRD - https://github.com/airshipit/airshipctl/issues/79 Define Labels for HCC - https://github.com/airshipit/airshipctl/issues/80 I have also attached sample Minimum Hardware configuration CR file. Request everyone to review attached file. Looking at broader goals for edge level baremetal node deployment, I believe we are having multiple hardware profiles or scenarios. I request you all to send multiple hardware profiles/scenarios for edge so that I will design hardware profile for HCC. Matt McEuen - I am fine working closely with you for designing hardware profiles and other baremetal plans. Thanks, Digambar -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: metal3.io_v1alpha1_hardwareclassificationcontroller.yaml Type: application/octet-stream Size: 867 bytes Desc: not available URL: From pramchan at yahoo.com Tue Mar 10 18:15:28 2020 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Tue, 10 Mar 2020 18:15:28 +0000 (UTC) Subject: [Airship-discuss] [airship] New Zoom Reminder (Ashlee Ferguson) References: <870446168.7325645.1583864128215.ref@mail.yahoo.com> Message-ID: <870446168.7325645.1583864128215@mail.yahoo.com> Can you edit and update TC and WC links on airship wiki  with new zoom link plus update the times. If need get help from Alex (Alexander Noskov). thx prakash Sent from Yahoo Mail on Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From bluejay.ahn at gmail.com Tue Mar 10 21:46:31 2020 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Wed, 11 Mar 2020 06:46:31 +0900 Subject: [Airship-discuss] Airship Community Events: US Daylight Savings Time In-Reply-To: References: Message-ID: Dear All, Regarding meeting time, I do want to suggest that it should be fixed based on UTC, not based on a certain country's local time zone. IMHO, although the most participants are from a certain country, ensuring a common / fixed meeting time regardless of each region's local time change is important for the global community. Thank you. 2020년 3월 10일 (화) 오전 4:54, WALTERS, ANDREW 님이 작성: > Hello all, > > We have been experiencing issues with the airship-discuss mail server, and > some messages have not reached everyone. Please see the email below from > Alex Hughes regarding Airship community meeting times. > > Regards, > > Drew Walters > Airship Working Committee > > > > Hello Airship Community, > > > Please be advised that meetings are scheduled in US Central Time. As a > > result of daylight saving time over the weekend meeting times for those > that > > do not observe daylight saving time will be moving backwards by 1 hour. > > > For example, a meeting previously held at 10:00 CST / 16:00 UTC will be > > changing to 10:00 CDT / 15:00 UTC. > > > Please be on the lookout for updated calendar invitations from meeting > > organizers. For more information please see the Airship > > wiki which was updated this > morning > > to reflect the time changes. > > > Regards, > > Alexander Hughes > > _______________________________________________ > 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 Mar 11 14:04:44 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 11 Mar 2020 14:04:44 +0000 Subject: [Airship-discuss] Airship Community Events: US Daylight Savings Time In-Reply-To: References: , Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B0509D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hey Jay, Thanks for the feedback; that's definitely something we'll keep in mind as we want to encourage/include Airship collaborators from around the globe. A couple things which have led us to our present mode of operation: It's not only the US that suffers from DST - most areas in Europe and North America observe it (albeit start/end times don't always align). Since that's where the majority of Airship contributors are, we want to avoid conflicts/confusion on their behalf when possible. The US itself is a broad country, and since we have many contributors on the west coast, we need to be considerate of their ability to join in the early morning -- balanced against the ability of contributors in the eastern hemisphere to join as well at the end of their day. That doesn't leave a lot of good time slots, and when DST changes, commitments like school start times, traffic patterns, etc. change with them. We've added recording to all of our audio-based calls to help ensure clarity & openness with collaborators unable to attend. We've explored many different schemes over the last few years, in an effort to encourage participation from additional countries - fixed UTC time, recurring meeting voting, alternating times, multiple meetings, etc. At the end of the day, the folks working on Airship are the folks who attend their working meetings, and we need to serve them. We are always completely open to adjusting meeting times, formats, etc, but experience has shown to me that those decisions need to be made by & for the participants, rather than in an effort to entice folks to become participants. As someone who thinks DST is a terrible idea, I hope we can escape from the whole confusing mess at some point! In the meantime, I think we'll just need to try to manage the confusion as best we can. Next time we'll do a better job of communicating this ahead of time. Thanks! Matt ________________________________ From: Jaesuk Ahn [bluejay.ahn at gmail.com] Sent: Tuesday, March 10, 2020 4:46 PM To: WALTERS, ANDREW Cc: airship-discuss at lists.airshipit.org Subject: Re: [Airship-discuss] Airship Community Events: US Daylight Savings Time Dear All, Regarding meeting time, I do want to suggest that it should be fixed based on UTC, not based on a certain country's local time zone. IMHO, although the most participants are from a certain country, ensuring a common / fixed meeting time regardless of each region's local time change is important for the global community. Thank you. 2020년 3월 10일 (화) 오전 4:54, WALTERS, ANDREW >님이 작성: Hello all, We have been experiencing issues with the airship-discuss mail server, and some messages have not reached everyone. Please see the email below from Alex Hughes regarding Airship community meeting times. Regards, Drew Walters Airship Working Committee > Hello Airship Community, > Please be advised that meetings are scheduled in US Central Time. As a > result of daylight saving time over the weekend meeting times for those that > do not observe daylight saving time will be moving backwards by 1 hour. > For example, a meeting previously held at 10:00 CST / 16:00 UTC will be > changing to 10:00 CDT / 15:00 UTC. > Please be on the lookout for updated calendar invitations from meeting > organizers. For more information please see the Airship > wiki> which was updated this morning > to reflect the time changes. > Regards, > Alexander Hughes _______________________________________________ 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 Wed Mar 11 15:54:34 2020 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Thu, 12 Mar 2020 00:54:34 +0900 Subject: [Airship-discuss] Airship Community Events: US Daylight Savings Time In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970B0509D@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970B0509D@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hi Matt, I really appreciate your long and kind response. I still believe community should have "a common way of understanding, not influenced by a certain region's specific situation", including "what time this meeting is happening". However, I also do understand what you are saying, difficulty of finding a good time for everyone, and those decisions need to be made by & for the active participants. For now, acknowledging my opinion and explaining logically are more than enough for me. Thanks again. :) Stay safe and healthy. 2020년 3월 11일 (수) 오후 11:04, MCEUEN, MATT 님이 작성: > Hey Jay, > > Thanks for the feedback; that's definitely something we'll keep in mind as > we want to encourage/include Airship collaborators from around the globe. > A couple things which have led us to our present mode of operation: > > It's not only the US that suffers from DST - most areas in Europe and > North America observe it (albeit start/end times don't always align). > Since that's where the majority of Airship contributors are, we want to > avoid conflicts/confusion on their behalf when possible. > > The US itself is a broad country, and since we have many contributors on > the west coast, we need to be considerate of their ability to join in the > early morning -- balanced against the ability of contributors in the > eastern hemisphere to join as well at the end of their day. That doesn't > leave a lot of good time slots, and when DST changes, commitments like > school start times, traffic patterns, etc. change with them. We've added > recording to all of our audio-based calls to help ensure clarity & openness > with collaborators unable to attend. > > We've explored many different schemes over the last few years, in an > effort to encourage participation from additional countries - fixed UTC > time, recurring meeting voting, alternating times, multiple meetings, etc. > At the end of the day, the folks working on Airship are the folks who > attend their working meetings, and we need to serve them. We are always > completely open to adjusting meeting times, formats, etc, but experience > has shown to me that those decisions need to be made by & for the > participants, rather than in an effort to entice folks to become > participants. > > As someone who thinks DST is a terrible idea, I hope we can escape from > the whole confusing mess at some point! In the meantime, I think we'll > just need to try to manage the confusion as best we can. Next time we'll > do a better job of communicating this ahead of time. > > Thanks! > Matt > > ------------------------------ > *From:* Jaesuk Ahn [bluejay.ahn at gmail.com] > *Sent:* Tuesday, March 10, 2020 4:46 PM > *To:* WALTERS, ANDREW > *Cc:* airship-discuss at lists.airshipit.org > *Subject:* Re: [Airship-discuss] Airship Community Events: US Daylight > Savings Time > > Dear All, > > Regarding meeting time, I do want to suggest that it should be fixed based > on UTC, not based on a certain country's local time zone. > > IMHO, although the most participants are from a certain country, ensuring > a common / fixed meeting time regardless of each region's local time change > is important for the global community. > > Thank you. > > > > > 2020년 3월 10일 (화) 오전 4:54, WALTERS, ANDREW 님이 작성: > >> Hello all, >> >> We have been experiencing issues with the airship-discuss mail server, >> and some messages have not reached everyone. Please see the email below >> from Alex Hughes regarding Airship community meeting times. >> >> Regards, >> >> Drew Walters >> Airship Working Committee >> >> >> > Hello Airship Community, >> >> > Please be advised that meetings are scheduled in US Central Time. As a >> > result of daylight saving time over the weekend meeting times for those >> that >> > do not observe daylight saving time will be moving backwards by 1 hour. >> >> > For example, a meeting previously held at 10:00 CST / 16:00 UTC will be >> > changing to 10:00 CDT / 15:00 UTC. >> >> > Please be on the lookout for updated calendar invitations from meeting >> > organizers. For more information please see the Airship >> > wiki> > >> which was updated this morning >> > to reflect the time changes. >> >> > Regards, >> > Alexander Hughes >> >> _______________________________________________ >> 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 ashlee at openstack.org Thu Mar 12 18:04:21 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Thu, 12 Mar 2020 13:04:21 -0500 Subject: [Airship-discuss] [OpenDev] We want your discussion ideas! Message-ID: <4BBA2919-CF4C-4493-BD82-16261D081DAA@openstack.org> Hi everyone, We still need your help shaping the discussion content for OpenDev + PTG, June 8-11, 2020 ! Our vision is for the content to be programmed by you-- the community. Programming Committees for each Track have begun meeting to discuss potential topics for the event, but they need your ideas and input to make sure all of the content is relevant and interesting to the community. The Programming Committee will also select moderators who will lead interactive discussions on a particular topic within the Track, so make sure to volunteer through the form below if you’re interested in that as well. Check out this etherpad to see what topics the Committees are currently discussing. If you’re interested in volunteering as an OpenDev discussion moderator, or would like to suggest topics for moderated discussions within a particular Track, please read the details below, and then fill out this form . We’re looking for discussion topics and Moderators for the following OpenDev Tracks: - Hardware Automation - Large-scale Usage of Open Source Infrastructure Software - Containers in Production - Key Challenges for Open Source in 2020 OpenDev Discussion Moderators will: - Be appointed by the Programming Committees - Facilitate discussions within a particular Track - Have adequate knowledge and experience to lead and moderate discussion around certain topics during the event - Work with Programming Committee to decide focal point of discussion Moderators need to be available to attend OpenDev, June 8 - 10, 2020. Volunteer to be a moderator or suggest discussion topics here before March 20: https://openstackfoundation.formstack.com/forms/opendev_vancouver2020_volunteer Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From pramchan at yahoo.com Fri Mar 13 01:28:32 2020 From: pramchan at yahoo.com (prakash RAMCHANDRAN) Date: Fri, 13 Mar 2020 01:28:32 +0000 (UTC) Subject: [Airship-discuss] [Airship] CNTT RI1 for Airship - CAPM3 YAML References: <2092325298.11627.1584062912565.ref@mail.yahoo.com> Message-ID: <2092325298.11627.1584062912565@mail.yahoo.com> Hi all, CAPI is defining Bare Metal Provider  CAPM3/M3 (Metal3.io) and hence BMO object Specs as part on V1alpha3 CAPI efforts. Refer.https://cluster-api.sigs.k8s.io/clusterctl/provider-contract.html#clusterctl-provider-contract Next to followup on OPNFV is driving Airship 1.0 into SDV project using CNTT RI1.Refer.OPNFV SDV Approval https://wiki.opnfv.org/display/CIRV/Software+Delivery+Validation Intern sought forhttps://wiki.lfnetworking.org/plugins/servlet/mobile#content/view/33423841 More relevant for M3 comparison of Ironic chart Object s in BMOCNTT RI1https://github.com/cntt-n/CNTT/blob/master/doc/ref_impl/cntt-ri/chapters/chapter03.md Although it appeared random walks by different projects, we in YAML SIG call were over similar discussion on how to frame YAML descriptors ideally to be able to render.  Having agreed in YAML SIG call that we go top down for Site level, Let us agree to CAPM3 to provide us CNTT RI1 complaint  and negotiate with them for Basic B and Network Intensive N profiles later we can bring in Advanced A with Accelerators, storage etc. Refer to table in 3.4 for specs. 3.4 NFVI Hardware Profile. Plus then we can adapt the CNTT state definitions borrowed from ETSI so to speak of. Let us review this and I will ask Digambar to engage with M3 and Matt should be able to get this same from Armada to Ironic. Let's exchange emails before Monday call to bring fresh ideas to YAML SIG. ThanksPrakash Sent from Yahoo Mail on Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From ag878f at att.com Fri Mar 13 17:26:45 2020 From: ag878f at att.com (GAUTAM, ANIRUDDHA SINGH) Date: Fri, 13 Mar 2020 17:26:45 +0000 Subject: [Airship-discuss] update in configuration of manifest repos in airshipctl Message-ID: Hello, What is the format of the command to update the configuration related to manifest repos in airshipctl? Use cases: (1) user/operator wants to change the repo from treasuremap to a private repo (2) user / operator wants to add a repo for security documents. There is one option --manifest that is available set-context sub-command, which set a manifest object to the config. However it is not very obvious from help how new manifest object and its configuration like url, credentials to access repo can be appended / updated. root at ubuntu:~/airshipctl# ./bin/airshipctl config set-context -h Sets a context entry in arshipctl config. Specifying a name that already exists will merge new fields on top of existing values for those fields. Usage: airshipctl config set-context NAME [flags] Examples: # Create a completely new e2e context entry airshipctl config set-context e2e --namespace=kube-system --manifest=manifest --user=auth-info --cluster-type=target # Update the current-context to e2e airshipctl config set-context e2e # Update attributes of the current-context airshipctl config set-context --current --manifest=manifest Flags: --cluster string sets the cluster for the specified context in the airshipctl config --cluster-type string sets the cluster-type for the specified context in the airshipctl config --current use current context from airshipctl config -h, --help help for set-context --manifest string sets the manifest for the specified context in the airshipctl config --namespace string sets the namespace for the specified context in the airshipctl config --user string sets the user for the specified context in the airshipctl config Global Flags: --airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config") --debug enable verbose output --kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig") It does not seem to be right output. Instead of printing the help it is actually processing the command inputs root at annie:~/airshipctl# ./bin/airshipctl config set-context --manifest -h you must specify a non-empty context name root at annie:~/airshipctl# ./bin/airshipctl config set-context --manifest --help you must specify a non-empty context name root at annie:~/airshipctl# ./bin/airshipctl config set-context default --manifest --help context "default" modified. Regards, Aniruddha -------------- next part -------------- An HTML attachment was scrubbed... URL: From ag878f at att.com Fri Mar 13 18:05:30 2020 From: ag878f at att.com (GAUTAM, ANIRUDDHA SINGH) Date: Fri, 13 Mar 2020 18:05:30 +0000 Subject: [Airship-discuss] update in configuration of bootstrap module in airshipctl Message-ID: Hello, What is the format of the command to update the configuration bootstrap module in airshipctl? Use cases: (1) user/operator wants to update user-data or network data for cloudinit. (2) user / operator wants to update the url for iso for the consumption of "remotedirect". "airship confit init" generates below configuration for bootstrap module. modules-config: bootstrapInfo: default: builder: networkConfigFileName: network-config outputMetadataFileName: output-metadata.yaml userDataFileName: user-data container: containerRuntime: docker image: quay.io/airshipit/isogen:latest volume: /srv/iso:/config remoteDirect: isoUrl: http://localhost:8099/debian-custom.iso remoteType: redfish However it is not very obvious from help, how configuration for bootstrap module can be updated. root at ubuntu-annie:~/airshipctl# ./bin/airshipctl config Modify airshipctl config files using subcommands like "airshipctl config set-context my-context" Usage: airshipctl config [command] Available Commands: get-cluster Display a specific cluster or all defined clusters if no name is provided get-context Display a specific context, the current-context or all defined contexts if no name is provided get-credentials Gets a user entry from the airshipctl config init Generate initial configuration files for airshipctl set-cluster Sets a cluster entry in the airshipctl config set-context Switch to a new context or update context values in the airshipctl config set-credentials Sets a user entry in the airshipctl config use-context Switch to a different airshipctl context. Flags: -h, --help help for config Global Flags: --airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config") --debug enable verbose output --kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig") Use "airshipctl config [command] --help" for more information about a command. Regards, Aniruddha -------------- next part -------------- An HTML attachment was scrubbed... URL: From ag878f at att.com Fri Mar 13 18:13:08 2020 From: ag878f at att.com (GAUTAM, ANIRUDDHA SINGH) Date: Fri, 13 Mar 2020 18:13:08 +0000 Subject: [Airship-discuss] update in configuration of bootstrap module in airshipctl In-Reply-To: References: Message-ID: One correction in highlighted part! Regards, Aniruddha From: GAUTAM, ANIRUDDHA SINGH Sent: Friday, March 13, 2020 11:06 AM To: airship-discuss at lists.airshipit.org Cc: GAUTAM, ANIRUDDHA SINGH Subject: [Airship-discuss] update in configuration of bootstrap module in airshipctl Hello, What is the format of the command to update the configuration bootstrap module in airshipctl? Use cases: (1) user/operator wants to update user-data or network data for cloudinit. (2) user / operator wants to update the url for iso for the consumption of "remotedirect". "airshipctl confit init" generates below configuration for bootstrap module. modules-config: bootstrapInfo: default: builder: networkConfigFileName: network-config outputMetadataFileName: output-metadata.yaml userDataFileName: user-data container: containerRuntime: docker image: quay.io/airshipit/isogen:latest volume: /srv/iso:/config remoteDirect: isoUrl: http://localhost:8099/debian-custom.iso remoteType: redfish However it is not very obvious from help, how configuration for bootstrap module can be updated. root at ubuntu-annie:~/airshipctl# ./bin/airshipctl config Modify airshipctl config files using subcommands like "airshipctl config set-context my-context" Usage: airshipctl config [command] Available Commands: get-cluster Display a specific cluster or all defined clusters if no name is provided get-context Display a specific context, the current-context or all defined contexts if no name is provided get-credentials Gets a user entry from the airshipctl config init Generate initial configuration files for airshipctl set-cluster Sets a cluster entry in the airshipctl config set-context Switch to a new context or update context values in the airshipctl config set-credentials Sets a user entry in the airshipctl config use-context Switch to a different airshipctl context. Flags: -h, --help help for config Global Flags: --airshipconf string Path to file for airshipctl configuration. (default "$HOME/.airship/config") --debug enable verbose output --kubeconfig string Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig") Use "airshipctl config [command] --help" for more information about a command. Regards, Aniruddha -------------- next part -------------- An HTML attachment was scrubbed... URL: From jimmy at openstack.org Fri Mar 13 20:26:20 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 13 Mar 2020 15:26:20 -0500 Subject: [Airship-discuss] [airshipit.org] SEO Improvements Message-ID: <5E6BEC6C.6030606@openstack.org> Hi all - We've contracted a professional SEO firm to help improve search placement for all OSF projects. I'd like to crowd source this on each of the project mailing lists, so the community is able to be involved. Could you all help out in providing the below: “Wish List” of keywords: 8-12 big terms you think fit your domain (if you only have 4-5 to share, fewer is okay) - open source ci - ? At least 3 competitors - Jenkins - ? Any other input on positioning, offerings, etc. that you think will help best filter for relevance - ? Cheers, Jimmy From jimmy at openstack.org Fri Mar 13 20:51:23 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 13 Mar 2020 15:51:23 -0500 Subject: [Airship-discuss] [airshipit.org] SEO Improvements In-Reply-To: <5E6BEC6C.6030606@openstack.org> References: <5E6BEC6C.6030606@openstack.org> Message-ID: <5E6BF24B.3000901@openstack.org> Sorry - I accidentally left Zuul keywords and examples in there. Fixed below: > Jimmy McArthur > March 13, 2020 at 3:26 PM > Hi all - > > We've contracted a professional SEO firm to help improve search > placement for all OSF projects. I'd like to crowd source this on each > of the project mailing lists, so the community is able to be > involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if > you only have 4-5 to share, fewer is okay) > - cloud provisioning > - ? > > At least 3 competitors > - ? > - ? > > Any other input on positioning, offerings, etc. that you think will > help best filter for relevance > - ? > > Cheers, > Jimmy > > _______________________________________________ > 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 jimmy at openstack.org Fri Mar 13 20:59:02 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Fri, 13 Mar 2020 15:59:02 -0500 Subject: [Airship-discuss] [airshipit.org] SEO Improvements In-Reply-To: <5E6BF24B.3000901@openstack.org> References: <5E6BEC6C.6030606@openstack.org> <5E6BF24B.3000901@openstack.org> Message-ID: <5E6BF416.3050104@openstack.org> Also, this is not spam :) It's me. OpenStack Foundation employee. I really want to help you with your SEO. > Jimmy McArthur > March 13, 2020 at 3:51 PM > Sorry - I accidentally left Zuul keywords and examples in there. Fixed > below: > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Jimmy McArthur > March 13, 2020 at 3:26 PM > Hi all - > > We've contracted a professional SEO firm to help improve search > placement for all OSF projects. I'd like to crowd source this on each > of the project mailing lists, so the community is able to be > involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if > you only have 4-5 to share, fewer is okay) > - open source ci > - ? > > At least 3 competitors > - Jenkins > - ? > > Any other input on positioning, offerings, etc. that you think will > help best filter for relevance > - ? > > Cheers, > Jimmy > > _______________________________________________ > 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 Mon Mar 16 14:21:27 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 16 Mar 2020 14:21:27 +0000 Subject: [Airship-discuss] Airship Virtual Meetup Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship team, In lieu of the planned face-to-face team meetup in Amsterdam around KubeCon, we'd like to hold a virtual team meetup that serves much the same purpose. Hopefully this will also lead to increased participation and even more valuable conversation. The goals for the meetup include aligning on Airship use cases and high-level design, finalizing actionable low-level design for upcoming scope, reviewing work in progress, a retrospection, and open floor discussion. The working time for the meetup is Tuesday, March 31, 9am-5pm CST (2pm-10pm UTC), and we'll plan to record it. This is during the planned KubeCon timeslot that many folks had previously earmarked, and also overlaps with several recurring Airship meetings, so my plan is to simply absorb them into the meetup. We can adjust this timing if something else works better for the majority of attendees - please reply to this thread in that case. The working agenda is below; pleas add anything you'd like to discuss! https://etherpad.openstack.org/p/airship-virtual-meetup-2020 Really looking forward to meeting with you all then; let's make this a springboard for the rest of the year and Airship in 2021. Thanks, Matt McEuen -------------- next part -------------- An HTML attachment was scrubbed... URL: From aw442m at att.com Mon Mar 16 14:22:05 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 16 Mar 2020 14:22:05 +0000 Subject: [Airship-discuss] update in configuration of manifest repos in airshipctl In-Reply-To: References: Message-ID: Hello Aniruddha! > What is the format of the command to update the configuration related to manifest repos in airshipctl? The preferred way of updating your airshipctl config file is by modifying the configuration file directly; however, we have added capabilities to change some options on an "as-needed" basis using command-line arguments and flags. For example, you can use the command-line to switch between pre-defined contexts in your configuration file and modify which manifests, module configurations, etc a context uses. As far as I am aware, this functionality has not been extended to manifest configuration, and I am not sure that it is planned. I encourage you to file a feature request on our GitHub issues page [0]. Each new issue is reviewed during our weekly flightplan call [1], and the issue could even be assigned that day if the functionality is desired. In the meantime, I recommend updating manifest data in the configuration file. > (1) user/operator wants to change the repo from treasuremap to a private repo Each manifest holds multiple repositories [2]. Therefore, if your active context references a manifest with multiple repositories, all of those repositories will be cloned. There is no need to identify which repository you would like to use; identify which set of repositories (the manifest) you would like to use. > It does not seem to be right output. Instead of printing the help it is actually processing the command inputs I agree; we should print the help menu options whenever -h or --help is passed, even if using a sub-command. I have filed an issue to track this [3]. Best regards, Drew Walters [0] https://github.com/airshipit/airshipctl/issues [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Management_Meetings [2] https://github.com/airshipit/airshipctl/blob/master/pkg/config/utils.go#L37 [3] https://github.com/airshipit/airshipctl/issues/114 From petebirley at googlemail.com Mon Mar 16 14:31:23 2020 From: petebirley at googlemail.com (Pete Birley) Date: Mon, 16 Mar 2020 09:31:23 -0500 Subject: [Airship-discuss] Airship Virtual Meetup In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Sounds great, look forward to seeing you all virtually at the end of the month. On Mon, 16 Mar 2020 at 09:25, MCEUEN, MATT wrote: > Airship team, > > > > In lieu of the planned face-to-face team meetup in Amsterdam around > KubeCon, we’d like to hold a virtual team meetup that serves much the same > purpose. Hopefully this will also lead to increased participation and even > more valuable conversation. The goals for the meetup include aligning on > Airship use cases and high-level design, finalizing actionable low-level > design for upcoming scope, reviewing work in progress, a retrospection, and > open floor discussion. > > > > The working time for the meetup is Tuesday, March 31, 9am-5pm CST > (2pm-10pm UTC), and we’ll plan to record it. This is during the planned > KubeCon timeslot that many folks had previously earmarked, and also > overlaps with several recurring Airship meetings, so my plan is to simply > absorb them into the meetup. We can adjust this timing if something else > works better for the majority of attendees – please reply to this thread in > that case. > > > > The working agenda is below; pleas add anything you’d like to discuss! > > https://etherpad.openstack.org/p/airship-virtual-meetup-2020 > > > > Really looking forward to meeting with you all then; let’s make this a > springboard for the rest of the year and Airship in 2021. > > > > Thanks, > > Matt McEuen > _______________________________________________ > 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 aw442m at att.com Mon Mar 16 14:34:02 2020 From: aw442m at att.com (WALTERS, ANDREW) Date: Mon, 16 Mar 2020 14:34:02 +0000 Subject: [Airship-discuss] update in configuration of bootstrap module in airshipctl In-Reply-To: References: Message-ID: Hello again Aniruddha! > What is the format of the command to update the configuration bootstrap module in airshipctl? > Use cases: > (1) user/operator wants to update user-data or network data for cloudinit. > (2) user / operator wants to update the url for iso for the consumption of "remotedirect". This is the same circumstance as the manifest section; details in the "bootstrapInfo" section must be modified in the configuration file. The command-line arguments will allow you to change which "bootstrapInfo" options are used for a particular context, but they do not provide a means for changing the ISO URL, user-data, or network data that cloudinit consumes. We always encourage filing issues [0] for these enhancements so they can be evaluated by the team at our weekly flightplan call [1] :) Best regards, Drew Walters [0] https://github.com/airshipit/airshipctl/issues [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Management_Meetings From: GAUTAM, ANIRUDDHA SINGH Sent: Friday, March 13, 2020 1:13 PM To: airship-discuss at lists.airshipit.org Cc: GAUTAM, ANIRUDDHA SINGH Subject: Re: [Airship-discuss] update in configuration of bootstrap module in airshipctl ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. One correction in highlighted part! Regards, Aniruddha From: GAUTAM, ANIRUDDHA SINGH Sent: Friday, March 13, 2020 11:06 AM To: mailto:airship-discuss at lists.airshipit.org Cc: GAUTAM, ANIRUDDHA SINGH Subject: [Airship-discuss] update in configuration of bootstrap module in airshipctl Hello, What is the format of the command to update the configuration bootstrap module in airshipctl? Use cases: (1) user/operator wants to update user-data or network data for cloudinit. (2) user / operator wants to update the url for iso for the consumption of "remotedirect". "airshipctl confit init" generates below configuration for bootstrap module. modules-config:   bootstrapInfo:     default:       builder:         networkConfigFileName: network-config         outputMetadataFileName: output-metadata.yaml         userDataFileName: user-data       container:         containerRuntime: docker         image: quay.io/airshipit/isogen:latest         volume: /srv/iso:/config       remoteDirect:         isoUrl: http://localhost:8099/debian-custom.iso         remoteType: redfish However it is not very obvious from help, how configuration for bootstrap module can be updated. root at ubuntu-annie:~/airshipctl# ./bin/airshipctl config Modify airshipctl config files using subcommands like "airshipctl config set-context my-context" Usage:   airshipctl config [command] Available Commands:   get-cluster     Display a specific cluster or all defined clusters if no name is provided   get-context     Display a specific context, the current-context or all defined contexts if no name is provided   get-credentials Gets a user entry from the airshipctl config   init            Generate initial configuration files for airshipctl   set-cluster     Sets a cluster entry in the airshipctl config   set-context     Switch to a new context or update context values in the airshipctl config   set-credentials Sets a user entry in the airshipctl config   use-context     Switch to a different airshipctl context. Flags:   -h, --help   help for config Global Flags:       --airshipconf string   Path to file for airshipctl configuration. (default "$HOME/.airship/config")       --debug                enable verbose output       --kubeconfig string    Path to kubeconfig associated with airshipctl configuration. (default "$HOME/.airship/kubeconfig") Use "airshipctl config [command] --help" for more information about a command. Regards, Aniruddha From ag878f at att.com Mon Mar 16 17:10:01 2020 From: ag878f at att.com (GAUTAM, ANIRUDDHA SINGH) Date: Mon, 16 Mar 2020 17:10:01 +0000 Subject: [Airship-discuss] update in configuration of manifest repos in airshipctl In-Reply-To: References: Message-ID: Thanks Drew... Appreciate your response! Regards, Aniruddha -----Original Message----- From: WALTERS, ANDREW Sent: Monday, March 16, 2020 7:22 AM To: GAUTAM, ANIRUDDHA SINGH ; airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] update in configuration of manifest repos in airshipctl Hello Aniruddha! > What is the format of the command to update the configuration related to manifest repos in airshipctl? The preferred way of updating your airshipctl config file is by modifying the configuration file directly; however, we have added capabilities to change some options on an "as-needed" basis using command-line arguments and flags. For example, you can use the command-line to switch between pre-defined contexts in your configuration file and modify which manifests, module configurations, etc a context uses. As far as I am aware, this functionality has not been extended to manifest configuration, and I am not sure that it is planned. I encourage you to file a feature request on our GitHub issues page [0]. Each new issue is reviewed during our weekly flightplan call [1], and the issue could even be assigned that day if the functionality is desired. In the meantime, I recommend updating manifest data in the configuration file. > (1) user/operator wants to change the repo from treasuremap to a private repo Each manifest holds multiple repositories [2]. Therefore, if your active context references a manifest with multiple repositories, all of those repositories will be cloned. There is no need to identify which repository you would like to use; identify which set of repositories (the manifest) you would like to use. > It does not seem to be right output. Instead of printing the help it is actually processing the command inputs I agree; we should print the help menu options whenever -h or --help is passed, even if using a sub-command. I have filed an issue to track this [3]. Best regards, Drew Walters [0] https://github.com/airshipit/airshipctl/issues [1] https://wiki.openstack.org/wiki/Airship#AIRSHIP_Flight_Plan_-_Community_Management_Meetings [2] https://github.com/airshipit/airshipctl/blob/master/pkg/config/utils.go#L37 [3] https://github.com/airshipit/airshipctl/issues/114 From paye600 at gmail.com Tue Mar 17 19:00:22 2020 From: paye600 at gmail.com (Roman Gorshunov) Date: Tue, 17 Mar 2020 20:00:22 +0100 Subject: [Airship-discuss] [airshipit.org] SEO Improvements In-Reply-To: <5E6BF416.3050104@openstack.org> References: <5E6BEC6C.6030606@openstack.org> <5E6BF24B.3000901@openstack.org> <5E6BF416.3050104@openstack.org> Message-ID: Hello Jimmi, Thank you for your help :) We are in progress of getting a list for you here: https://etherpad.openstack.org/p/airshipit.org_SEO_Improvements Hold on just a bit, please, and Airship working committee will reply to you with all keywords and all information you have requested. Best regards, Roman Gorshunov On Fri, Mar 13, 2020 at 9:59 PM Jimmy McArthur wrote: > > Also, this is not spam :) It's me. OpenStack Foundation employee. I really want to help you with your SEO. > > Jimmy McArthur March 13, 2020 at 3:51 PM > Sorry - I accidentally left Zuul keywords and examples in there. Fixed below: > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Jimmy McArthur March 13, 2020 at 3:26 PM > Hi all - > > We've contracted a professional SEO firm to help improve search placement for all OSF projects. I'd like to crowd source this on each of the project mailing lists, so the community is able to be involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if you only have 4-5 to share, fewer is okay) > - open source ci > - ? > > At least 3 competitors > - Jenkins > - ? > > Any other input on positioning, offerings, etc. that you think will help best filter for relevance > - ? > > Cheers, > Jimmy > > _______________________________________________ > 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 jimmy at openstack.org Tue Mar 17 19:06:28 2020 From: jimmy at openstack.org (Jimmy McArthur) Date: Tue, 17 Mar 2020 14:06:28 -0500 Subject: [Airship-discuss] [airshipit.org] SEO Improvements In-Reply-To: References: <5E6BEC6C.6030606@openstack.org> <5E6BF24B.3000901@openstack.org> <5E6BF416.3050104@openstack.org> Message-ID: <5E711FB4.9080105@openstack.org> Awesome! Thanks Roman! > Roman Gorshunov > March 17, 2020 at 2:00 PM > Hello Jimmi, > > Thank you for your help :) We are in progress of getting a list for > you here: https://etherpad.openstack.org/p/airshipit.org_SEO_Improvements > Hold on just a bit, please, and Airship working committee will reply > to you with all keywords and all information you have requested. > > Best regards, > Roman Gorshunov > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Jimmy McArthur > March 13, 2020 at 3:59 PM > Also, this is not spam :) It's me. OpenStack Foundation employee. I > really want to help you with your SEO. > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Jimmy McArthur > March 13, 2020 at 3:51 PM > Sorry - I accidentally left Zuul keywords and examples in there. Fixed > below: > > > _______________________________________________ > Airship-discuss mailing list > Airship-discuss at lists.airshipit.org > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > Jimmy McArthur > March 13, 2020 at 3:26 PM > Hi all - > > We've contracted a professional SEO firm to help improve search > placement for all OSF projects. I'd like to crowd source this on each > of the project mailing lists, so the community is able to be > involved. Could you all help out in providing the below: > > “Wish List” of keywords: 8-12 big terms you think fit your domain (if > you only have 4-5 to share, fewer is okay) > - open source ci > - ? > > At least 3 competitors > - Jenkins > - ? > > Any other input on positioning, offerings, etc. that you think will > help best filter for relevance > - ? > > Cheers, > Jimmy > > _______________________________________________ > 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 cboylan at sapwetik.org Tue Mar 17 20:29:53 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 17 Mar 2020 13:29:53 -0700 Subject: [Airship-discuss] OpenDev now using #opendev on Freenode for Discussions Message-ID: <0f65e2c7-0790-494f-a013-f0f543a9779d@www.fastmail.com> Hello all, We are now using #opendev on Freenode to discuss the OpenDev Infrastructure. We hope this gives you all a more friendly neutral location to discuss the tools we use to develop our software. Feel free to join us and bring your ideas and questions. Hope to see you there, Clark From cboylan at sapwetik.org Tue Mar 17 21:08:59 2020 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 17 Mar 2020 14:08:59 -0700 Subject: [Airship-discuss] review.opendev.org Downtime March 20, 2020 at 1400UTC Message-ID: <52b5659e-79e0-4681-beb2-28b4c5c3bbd8@www.fastmail.com> The OpenDev team is planning to take a short downtime March 20, 2020 from 14:00UTC to 15:00UTC. This outage will enable us to rename a few projects and redeploy Gerrit using containers. The container based deployment is an important first step in our longer term plan for upgrading Gerrit to a modern version. We recognize that this will be a disruption during an already disrupted week for many. We feel this is worthwhile as it fits into project release schedules and sets us up well for the future. Thank you for your patience. Feel free to ask us any questions you may have on this thread or in #opendev on Freenode. Clark From ashlee at openstack.org Wed Mar 18 20:44:11 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Wed, 18 Mar 2020 15:44:11 -0500 Subject: [Airship-discuss] Fwd: [OpenStack Foundation] Update on OpenDev + PTG (Vancouver) References: <1584563593.8598643@emailsrvr.com> Message-ID: Hi everyone, Please see Mark’s email below regarding OpenDev + PTG. Thanks, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation > Begin forwarded message: > > From: "Mark Collier" > Subject: [OpenStack Foundation] Update on OpenDev + PTG (Vancouver) > Date: March 18, 2020 at 3:33:13 PM CDT > To: foundation at lists.openstack.org > > Hi everyone, > > Based on the input from the community, board, and the latest information available from the health experts, we've made the decision not to hold the OpenDev + PTG in Vancouver this June. Instead, we're exploring ways to turn it into a virtual event and would love the help of everyone in the community. > > We will be reaching out to participants who have already registered to issue full refunds. > > We have always aimed to produce events "of the community, by the community," and this change for OpenDev + PTG is no exception. We would like to virtualize the PTG, since it is critical to producing the next release, targeting the same timeframe. We would like to recruit community volunteers to form a Virtual PTG Organization Team to collaborate with the OSF staff to incorporate best practices and ensure the event continues to meet the goals of the upstream community. We will need to begin pulling this plan together soon, so please add your name ot this etherpad if you are interested in helping: https://etherpad.openstack.org/p/Virtual_PTG_Planning. > > For OpenDev, discussions are also meant to be collaborative and free-flowing but are less time bound by the release schedule, so rather than trying to recreate that during a single virtual event at the same time as the virtual PTG, we are thinking about other ways to accomplish the same goals. We've already assembled an awesome team of Program Committee volunteers who have received proposals for moderated discussions, and we will be working with them on some ideas on the best way to move forward. > > For the time being, we are continuing with the plan for the Open Infrastructure Summit in Berlin October 19-23. For updates on OpenDev + PTG and the Summit, please continue to read and bookmark this status page which we will continue to update: https://www.openstack.org/events/covid-19-coronavirus-disease-updates > > Mark Collier > COO, OpenStack Foundation > > > _______________________________________________ > Foundation mailing list > Foundation at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Mar 19 19:38:06 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 19 Mar 2020 19:38:06 +0000 Subject: [Airship-discuss] Airship Virtual Meetup In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B094DE@MOSTLS1MSGUSRFF.ITServices.sbc.com> The agenda for the virtual meetup is shaping up nicely. Just a reminder: if anyone has any concerns with the timing, etc, please let me know by EOD Thursday so that we can communicate out the final timing. Thanks! From: MCEUEN, MATT Sent: Monday, March 16, 2020 9:21 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship Virtual Meetup ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, In lieu of the planned face-to-face team meetup in Amsterdam around KubeCon, we'd like to hold a virtual team meetup that serves much the same purpose. Hopefully this will also lead to increased participation and even more valuable conversation. The goals for the meetup include aligning on Airship use cases and high-level design, finalizing actionable low-level design for upcoming scope, reviewing work in progress, a retrospection, and open floor discussion. The working time for the meetup is Tuesday, March 31, 9am-5pm CST (2pm-10pm UTC), and we'll plan to record it. This is during the planned KubeCon timeslot that many folks had previously earmarked, and also overlaps with several recurring Airship meetings, so my plan is to simply absorb them into the meetup. We can adjust this timing if something else works better for the majority of attendees - please reply to this thread in that case. The working agenda is below; pleas add anything you'd like to discuss! https://etherpad.openstack.org/p/airship-virtual-meetup-2020 Really looking forward to meeting with you all then; let's make this a springboard for the rest of the year and Airship in 2021. Thanks, Matt McEuen -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Mar 19 19:39:28 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 19 Mar 2020 19:39:28 +0000 Subject: [Airship-discuss] FW: [openstack-helm] Virtual Midcycle In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B094F1@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community: FYI that the OpenStack-Helm team is holding their virtual midcycle next Tuesday. Please feel free to join if you’re interested in participating! From: Gage Hugo Sent: Tuesday, March 17, 2020 1:51 PM To: openstack-discuss at lists.openstack.org Subject: [openstack-helm] Virtual Midcycle Good afternoon, The openstack-helm team will be hosting their virtual midcycle next Tuesday, March 24th 2020 at 1400 to 1700 UTC. Please check out the etherpad link for more details about the agenda and conferencing tool. Since this meeting is overlapping our normal meeting time, the actual IRC meeting will be canceled for next week. https://etherpad.openstack.org/p/osh-virtual-ptg-2020-03 Hope to see you all there. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Mon Mar 23 21:16:04 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Mon, 23 Mar 2020 16:16:04 -0500 Subject: [Airship-discuss] Airship User Survey Message-ID: <6D002D33-CA95-4B2E-9281-13F28FAC8ABC@openstack.org> Hi everyone, Today on the Working Committee call, we discussed the creation of an Airship user survey. This survey is for people running Airship as well as those evaluating it. A user survey will help the community gain insight into specific Airship use cases and gather feedback to help improve and develop the project going forward. There are some basic questions we will include as a starting point, but we would also like community input around what other valuable information you all are interested in gathering. To begin the brainstorming process, I’ve attached A PDF of the Kata Containers survey questions as an example. Please drop any ideas for the Airship user survey in this etherpad: https://etherpad.openstack.org/p/AirshipUserSurvey_Brainstorm Let me know if you have any questions! Thanks, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Kata Containers User Survey_EN.pdf Type: application/pdf Size: 141292 bytes Desc: not available URL: -------------- next part -------------- An HTML attachment was scrubbed... URL: From pandeysachinbirendra at gmail.com Wed Mar 25 03:43:42 2020 From: pandeysachinbirendra at gmail.com (Sachin Pandey) Date: Wed, 25 Mar 2020 09:13:42 +0530 Subject: [Airship-discuss] Suspected high vulnarability Message-ID: Hey support team, Can i know the technical support email id please? Also like to know that you run bug bounty or rewards for the same? Thanks & Best Regards, Sachin -------------- next part -------------- An HTML attachment was scrubbed... URL: From roman.gorshunov at att.com Thu Mar 26 09:05:19 2020 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Thu, 26 Mar 2020 09:05:19 +0000 Subject: [Airship-discuss] Suspected high vulnarability In-Reply-To: References: Message-ID: Hello Sachin, Thank you for reaching out to us. Please, follow Airship Security Vulnerability Management process [0]. In short, vulnerabilities should be disclosed to the mailto:airship-security%40lists.airshipit.org mailing list. I’m not aware of any existing bug bounty or rewards program which covers Airship at the moment. [0] https://airship-docs.readthedocs.io/en/latest/security/vulnerabilities.html Roman Gorshunov Principal, Systems Engineering AT&T Technology Development, Network and Shared Services Lakeside Park 01, Tomasikova 64, Bratislava, Slovakia 831 04 +421 2 322 17290 | mailto:Roman.Gorshunov at att.com Keep your eyes on the road, not on your phone. Take the pledge…http://www.itcanwait.com/ > From: Sachin Pandey > Sent: Wednesday, March 25, 2020 4:44 AM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Suspected high vulnarability > > Hey support team, > > Can i know the technical support email id please?  > > Also like to know that you run bug bounty or rewards for the same? > > Thanks & Best Regards, > Sachin > From roman.gorshunov at att.com Thu Mar 26 10:40:58 2020 From: roman.gorshunov at att.com (Gorshunov, Roman) Date: Thu, 26 Mar 2020 10:40:58 +0000 Subject: [Airship-discuss] Airship User Survey In-Reply-To: <6D002D33-CA95-4B2E-9281-13F28FAC8ABC@openstack.org> References: <6D002D33-CA95-4B2E-9281-13F28FAC8ABC@openstack.org> Message-ID: <06fee4f88c5643db9253fc9ddbd8e63e@att.com> Hello Ashlee, I have added a few questions I would be interested to know answers to. Thank you! Roman Gorshunov Principal, Systems Engineering AT&T Technology Development, Network and Shared Services Lakeside Park 01, Tomasikova 64, Bratislava, Slovakia 831 04 +421 2 322 17290 | Roman.Gorshunov at att.com Keep your eyes on the road, not on your phone. Take the pledge…http://www.itcanwait.com/ From pandeysachinbirendra at gmail.com Thu Mar 26 09:08:00 2020 From: pandeysachinbirendra at gmail.com (Sachin Pandey) Date: Thu, 26 Mar 2020 14:38:00 +0530 Subject: [Airship-discuss] Suspected high vulnarability In-Reply-To: References: Message-ID: Thanks for your response. I hope I get a probable bug bounty aor reward as such critical vulnerability. On Thu, 26 Mar 2020, 2:35 pm Gorshunov, Roman, wrote: > Hello Sachin, > > Thank you for reaching out to us. Please, follow Airship Security > Vulnerability Management process [0]. > In short, vulnerabilities should be disclosed to the mailto: > airship-security%40lists.airshipit.org mailing list. > I’m not aware of any existing bug bounty or rewards program which covers > Airship at the moment. > > [0] > https://airship-docs.readthedocs.io/en/latest/security/vulnerabilities.html > > Roman Gorshunov > Principal, Systems Engineering > > AT&T Technology Development, Network and Shared Services > Lakeside Park 01, Tomasikova 64, Bratislava, Slovakia 831 04 > +421 2 322 17290 | mailto:Roman.Gorshunov at att.com > > Keep your eyes on the road, not on your phone. > Take the pledge…http://www.itcanwait.com/ > > > From: Sachin Pandey > > Sent: Wednesday, March 25, 2020 4:44 AM > > To: airship-discuss at lists.airshipit.org > > Subject: [Airship-discuss] Suspected high vulnarability > > > > Hey support team, > > > > Can i know the technical support email id please? > > > > Also like to know that you run bug bounty or rewards for the same? > > > > Thanks & Best Regards, > > Sachin > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From allison at openstack.org Thu Mar 26 19:43:00 2020 From: allison at openstack.org (Allison Price) Date: Thu, 26 Mar 2020 14:43:00 -0500 Subject: [Airship-discuss] How to Contribute to the Airship Blog and Superuser Magazine Message-ID: Hi everyone, Thank you all for helping with the SEO content that Jimmy sent out last week. I mentioned this on the Working Committee call this week, but I think this is also a great list of keywords to provide a foundation for what kind of content we should be creating for Airship as a community. Accompanied by the amount of events that have been transformed to virtual experiences, the OpenStack Foundation has been working on ways for the community to centrally share learnings online, and create a place where the community can send project and overall community updates. Both the Airship blog and Superuser Magazine are two community channels where I encourage everyone to contribute content when they have updates that will impact the broader community. I wanted to remind everyone of the process and of course, you can reach out to Ashlee or myself if you have any questions or ideas. Here’s how you can contribute: Airship Blog The Airship blog is a great place for updates that are more related to the Airship software releases, including bug fixes or changes that may affect users who are running Airship in production. Once you have an idea of what you would like to share or have questions, please email info at airshipit.org . We can also keep track of a running list of ideas / calls for content for people who have questions that would be great to get answered on the blog. Superuser Superuser has evolved to cover the open infrastructure landscape covering different use cases and open source projects. Whether it’s a video or an article, this content is typically more in depth than what you would see on a project blog and includes things like hands on tutorials, case studies, thought leadership articles, Q&As with open source community leaders, and updates and highlights from open source events around the world. If you have an idea you would like to share, fill out this form and the editorial team will reach out. If you have questions about whether your topic is the right fit, email editor at openstack.org . You can also attend the OSF community meeting next week to learn more about how you can get involved and contribute! Thanks! Allison -------------- next part -------------- An HTML attachment was scrubbed... URL: From digambarpat at gmail.com Fri Mar 27 09:44:51 2020 From: digambarpat at gmail.com (Digambar Patil) Date: Fri, 27 Mar 2020 15:14:51 +0530 Subject: [Airship-discuss] Error status of Disks Message-ID: Hi Airship, We had a discussion in OpenDesign meeting last thursday on bringing error states for disks and other devices so that we can label appropriate error in HOST CR. I had done good amount of investigation on Ironic Introspection data. After studying Ironic introsepction data, Ironic has taken care of these things already. Here is my understanding - - If one of the disk is error state, then Ironic introsepction fails in that case or it stuck in inpecting state for long time and fails after it. - We are pulling only BM hosts which are in READY state, so READY state comes after successful execution of Introspection state. - Here we can consider that current hardware inventory data is suffice. - HCC (Hardware-classifcation-controller) will perform classification and validation filter by comparing with HCC profile and label the BaremetalHost CR as BMO-OK. Thanks, Digambar -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Fri Mar 27 15:03:36 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Fri, 27 Mar 2020 15:03:36 +0000 Subject: [Airship-discuss] Error status of Disks In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B0B40F@MOSTLS1MSGUSRFF.ITServices.sbc.com> Thanks for the update, Digambar. Is it fair to summarize it this way? * Airship can rely on the HCC to ensure servers have the right disks (etc) * Airship can rely on existing Ironic introspection to ensure the disks are healthy Matt From: Digambar Patil Sent: Friday, March 27, 2020 4:45 AM To: airship-discuss at lists.airshipit.org Cc: Prakash ; J T Subject: [Airship-discuss] Error status of Disks Hi Airship, We had a discussion in OpenDesign meeting last thursday on bringing error states for disks and other devices so that we can label appropriate error in HOST CR. I had done good amount of investigation on Ironic Introspection data. After studying Ironic introsepction data, Ironic has taken care of these things already. Here is my understanding - - If one of the disk is error state, then Ironic introsepction fails in that case or it stuck in inpecting state for long time and fails after it. - We are pulling only BM hosts which are in READY state, so READY state comes after successful execution of Introspection state. - Here we can consider that current hardware inventory data is suffice. - HCC (Hardware-classifcation-controller) will perform classification and validation filter by comparing with HCC profile and label the BaremetalHost CR as BMO-OK. Thanks, Digambar -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Fri Mar 27 15:04:47 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Fri, 27 Mar 2020 15:04:47 +0000 Subject: [Airship-discuss] Canceled: [sig][airship-ui] - Friday March 27, 2020 Message-ID: <1DE87AA2-2AF0-4415-BFEC-AB6706469656@att.com> I won’t be available to host this meeting today. The only topic on the Agenda is a discussion I was going to lead. Will postpone that until next week. Cancelling the call. Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From digambarpat at gmail.com Fri Mar 27 17:12:28 2020 From: digambarpat at gmail.com (Digambar Patil) Date: Fri, 27 Mar 2020 22:42:28 +0530 Subject: [Airship-discuss] Error status of Disks In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970B0B40F@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970B0B40F@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Yes Matt. You are right. We are performing Ironic introspection on BM nodes with multiple scenarios. I have got expected results as explained in previous mail. Thanks, Digambar On Fri, Mar 27, 2020 at 8:33 PM MCEUEN, MATT wrote: > > Thanks for the update, Digambar. Is it fair to summarize it this way? > > Airship can rely on the HCC to ensure servers have the right disks (etc) > Airship can rely on existing Ironic introspection to ensure the disks are healthy > > > > Matt > > > > From: Digambar Patil > Sent: Friday, March 27, 2020 4:45 AM > To: airship-discuss at lists.airshipit.org > Cc: Prakash ; J T > Subject: [Airship-discuss] Error status of Disks > > > > Hi Airship, > > We had a discussion in OpenDesign meeting last thursday on bringing error states for disks and other devices so that we can label appropriate error in HOST CR. > I had done good amount of investigation on Ironic Introspection data. > After studying Ironic introsepction data, Ironic has taken care of these things already. Here is my understanding - > - If one of the disk is error state, then Ironic introsepction fails in that case or it stuck in inpecting state for long time and fails after it. > - We are pulling only BM hosts which are in READY state, so READY state comes after successful execution of Introspection state. > - Here we can consider that current hardware inventory data is suffice. > > - HCC (Hardware-classifcation-controller) will perform classification and validation filter by comparing with HCC profile and label the BaremetalHost CR as BMO-OK. > > > Thanks, > Digambar From rp2723 at att.com Mon Mar 30 14:05:30 2020 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 30 Mar 2020 14:05:30 +0000 Subject: [Airship-discuss] REMINDER - No Airship Design Call Tuesday March 31 - Virtual Meetup Day instead Message-ID: <5621B205-069C-4C12-815B-C9CD2972CE52@att.com> There will be no Design Call tomorrow. Instead please attend the Airship Virtual Meetup • Tuesday March 31, 2020 • 9am CST(2pm UTC) - 5pm CST (10pm UTC) • Zoom bridge:  https://zoom.us/j/613001653 https://etherpad.openstack.org/p/airship-virtual-meetup-2020 Regards Rodolfo Pacheco From MM9745 at att.com Mon Mar 30 17:30:56 2020 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 30 Mar 2020 17:30:56 +0000 Subject: [Airship-discuss] Airship Virtual Meetup In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D8970B094DE@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D8970B07442@MOSTLS1MSGUSRFF.ITServices.sbc.com> <7C64A75C21BB8D43BD75BB18635E4D8970B094DE@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D8970B0C012@MOSTLS1MSGUSRFF.ITServices.sbc.com> Just a reminder that the Airship Virtual Meetup will be held tomorrow - a calendar invite is attached. Hope to see you there! Agenda: https://etherpad.openstack.org/p/airship-virtual-meetup-2020 Join Zoom Meeting https://zoom.us/j/613001653 Meeting ID: 613 001 653 One tap mobile +13462487799,,613001653# US (Houston) +16699006833,,613001653# US (San Jose) Dial by your location +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 646 876 9923 US (New York) +1 253 215 8782 US +1 301 715 8592 US +1 312 626 6799 US (Chicago) Meeting ID: 613 001 653 Find your local number: https://zoom.us/u/adZUJ6wQrj From: MCEUEN, MATT Sent: Thursday, March 19, 2020 2:38 PM To: 'airship-discuss at lists.airshipit.org' Subject: RE: [Airship-discuss] Airship Virtual Meetup The agenda for the virtual meetup is shaping up nicely. Just a reminder: if anyone has any concerns with the timing, etc, please let me know by EOD Thursday so that we can communicate out the final timing. Thanks! From: MCEUEN, MATT > Sent: Monday, March 16, 2020 9:21 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Airship Virtual Meetup ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Airship team, In lieu of the planned face-to-face team meetup in Amsterdam around KubeCon, we'd like to hold a virtual team meetup that serves much the same purpose. Hopefully this will also lead to increased participation and even more valuable conversation. The goals for the meetup include aligning on Airship use cases and high-level design, finalizing actionable low-level design for upcoming scope, reviewing work in progress, a retrospection, and open floor discussion. The working time for the meetup is Tuesday, March 31, 9am-5pm CST (2pm-10pm UTC), and we'll plan to record it. This is during the planned KubeCon timeslot that many folks had previously earmarked, and also overlaps with several recurring Airship meetings, so my plan is to simply absorb them into the meetup. We can adjust this timing if something else works better for the majority of attendees - please reply to this thread in that case. The working agenda is below; pleas add anything you'd like to discuss! https://etherpad.openstack.org/p/airship-virtual-meetup-2020 Really looking forward to meeting with you all then; let's make this a springboard for the rest of the year and Airship in 2021. Thanks, Matt McEuen -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded message was scrubbed... From: "MCEUEN, MATT" Subject: Airship Virtual Meetup Date: Mon, 30 Mar 2020 17:27:49 +0000 Size: 49005 URL: From ag878f at att.com Mon Mar 30 18:38:11 2020 From: ag878f at att.com (GAUTAM, ANIRUDDHA SINGH) Date: Mon, 30 Mar 2020 18:38:11 +0000 Subject: [Airship-discuss] output of airshipctl in yaml or json format Message-ID: Hello, One question: is it supported in airshipctl to generate output in yaml or json format? It will be useful for automation (say using Jenkins) of the process/steps to deploy a NC site using Airship 2.0. Regards, Aniruddha -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Mon Mar 30 22:42:37 2020 From: kennelson11 at gmail.com (Kendall Nelson) Date: Mon, 30 Mar 2020 15:42:37 -0700 Subject: [Airship-discuss] Fwd: [all] Virtualized PTG Brainstorming Community Meetings In-Reply-To: References: Message-ID: Hello Everyone! So! After Marks initial email[1] that announced we would be virtualizing the PTG and collected volunteers[2] to help brainstorm the best way to hold the PTG virtually, we polled the volunteers for the best times to meet. In trying to be the most inclusive we have settled on three meetings to brainstorm together as a community. They are as follows: - April 2nd at 12:00 UTC - April 6th at 17:00 UTC - April 7th at 2:00 UTC We will be using my zoom[3] and continue using the same etherpad [2] that we collected volunteers in for all the notes from all three meetings. All are welcome! And if you can attend more than one meeting, please do! The more overlap we have the more cohesive discussions we will have. Hope to see you all there! -Kendall Nelson (diablo_rojo) [1] http://lists.openstack.org/pipermail/foundation/2020-March/002854.html [2] https://etherpad.openstack.org/p/Virtual_PTG_Planning [3] https://zoom.us/my/diablorojo -------------- next part -------------- An HTML attachment was scrubbed... URL: From ashlee at openstack.org Tue Mar 31 21:34:03 2020 From: ashlee at openstack.org (Ashlee Ferguson) Date: Tue, 31 Mar 2020 16:34:03 -0500 Subject: [Airship-discuss] Virtual OpenDev Update Message-ID: <7DE2209B-2B37-4F95-BFEA-D9F23E2AEEE7@openstack.org> Hi everyone, As we continue to gather feedback and discuss what a virtual OpenDev will look like, we wanted to provide you with an update around the event. While we are still attempting to solve some of the riddles of virtual event world, we did come up with some decisions that give us something to build on, which are based on input and experience from members of the Programming Committee. Decisions: - OpenDev will happen after the Virtual PTG (exact format and timing TBD) - Will not be simultaneous/parallel Tracks so everyone has the opportunity to participate in more than one - 3 Tracks, each on different date: - Hardware Automation - Large Scale Ops - Containers in Production We also discussed the original intent and goals of OpenDev to make sure we’re still heading in a direction that’s beneficial for the community, especially since it will no longer directly precede the upcoming PTG. Similar to past OpenDev events, the goal is to identify the questions we don’t have the answers for, and to use that time to dive in and determine the work ahead of us, working together, sharing use cases, and learning from other people asking those same questions. High-level decisions, goals, and some areas we’re looking for feedback are in the etherpad below. As you continue to experience this new amazing world of virtual events, please add any feedback or ideas to the etherpad below. We’re looking forward to creating virtual OpenDev with you all! https://etherpad.openstack.org/p/Virtual_OpenDev_Planning Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: