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

OSF Individual Membership and Annual Board of Directors Election
by Chris Hoge 17 Jul '19

17 Jul '19

Hi everyone, As members of the Airship community, a pilot project project supported by the OpenStack Foundation (OSF), we want to encourage you to become individual members of the OpenStack Foundation. One of the benfits of membership is eligibility to participate in the upcoming annual Foundation Board of Directors election. The OSF board represents all of the projects[1], not just OpenStack, and so it’s important for every community member to actively participate, as both voters and candidates, in this election process. If you are not already an OpenStack Foundation member, please consider joining by July 21 to have a voice in the 2020 election. It’s free to join and only takes a few minutes to complete the form. https://www.openstack.org/join/register/?membership-type=foundation Eligibility is time sensitive! In order to be eligible to in the January 2020 Individual Board of Directors election[2] you must join as an Individual Foundation Member no later than this Sunday, July 21, 2019 at 11:59pm PT. The OpenStack Foundation Board of Directors provides strategic and financial oversight of Foundation resources and staff. The 24 person Board is composed of directors elected by the Individual Foundation Members (8), directors elected by the Gold Members (8) and directors appointed by the Platinum Members (8). Individual Member Directors are there to represent the individual members of the Foundation, people like yourself! These Directors act a direct link between the thousands of members of the Foundation and the Board, not as appointed representatives of the companies for which they work. Meet the current Board of Directors[3] and learn more here[4]. For further OpenStack Foundation updates and news, please sign up for the OpenStack Foundation mailing list[5]. You can also select the type of content you receive from the OpenStack Foundation, including our biweekly newsletter convering all of the Foundation activities[6]. Thanks! Chris [1] We’re aware that some of the language about the election on openstack.org is still “openstack project” specific, and we’ll be updating that prior to the 2020 elections to more accurately reflect that the OSF Board represents all OSF projects. Please don’t let this dissuade you from joining if you’re interested in voting! [2] Individual Election https://www.openstack.org/election/2020-individual-director-election/ [3] Foundation Board of Directors https://www.openstack.org/foundation/board-of-directors/ [4] OpenStack Foundation https://www.openstack.org/foundation/ [5] OpenStack Foundation Mailing List http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation [6] Foundation Newsletter https://www.openstack.org/community/email-signup

1 0

Community Voting is now Open!
by Jimmy McArthur 16 Jul '19

16 Jul '19

Community voting for the Open Infrastructure Summit Shanghai sessions is open! You can VOTE HERE <https://www.openstack.org/summit/shanghai-2019/vote-for-speakers>, but what does that mean? Now that the Call for Presentations has closed, all submissions are available for community vote and input. After community voting closes, the volunteer Programming Committee members will receive the results to review to help them determine the final selections for Summit schedule. While community votes are meant to help inform the decision, Programming Committee members are expected to exercise judgment in their area of expertise and help ensure diversity of sessions and speakers. View full details of the session selection process <https://cfp.openstack.org/#selection-process>. In order to vote, you need an OSF community membership. If you do not have an account, please create one by going to openstack.org/join <https://www.openstack.org/join>. If you need to reset your password, you can do that here <https://www.openstack.org/Security/lostpassword>. Hurry, voting closes Monday, July 22 at 11:59pmPacific Time (Tuesday, July 23 at 6:59 UTC). Continue to visit https://www.openstack.org/summit/shanghai-2019 for all Summit-related information. REGISTER Register for the Summit <https://www.openstack.org/summit/shanghai-2019> before prices increase on August 7th! VISA APPLICATION PROCESS Make sure to secure your Visa soon. More information <https://www.openstack.org/summit/shanghai-2019/travel/#travel-support> about the Visa application process. TRAVEL SUPPORT PROGRAM August 8th is the last day to submit applications. Please submit your applications <https://openstackfoundation.formstack.com/forms/travelsupportshanghai> by 11:59pm Pacific Time (August 9th at 6:59am UTC). If you have any questions, please email summit(a)openstack.org <mailto:summit@openstack.org>. Cheers, Jimmy

1 0

[sig][airship-yaml] Meetings
by PACHECO, RODOLFO J 15 Jul '19

15 Jul '19

When: Occurs every Monday from 11:00 AM to 12:00 PM effective 7/22/2019 until 1/22/2020. (UTC-05:00) Eastern Time (US & Canada) Where: https://attcorp.webex.com/join/rp2723 *~*~*~*~*~*~*~*~*~* 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(a)lists.airshipit.org<mailto:airship-discuss@lists.airshipit.org> when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671

1 0

OpenInfra Days Vietnam 2019 (Hanoi) - Call For Presentations
by Trinh Nguyen 12 Jul '19

12 Jul '19

Hello, Hope you're doing well :) The OpenInfra Days Vietnam 2019 [1] is looking for speakers in many different topics (e.g., container, CI, deployment, edge computing, etc.). If you would love to have a taste of Hanoi, the capital of Vietnam, please join us this one-day event and submit your presentation [2]. *- Date:* 24 AUGUST 2019 *- Location:* INTERCONTINENTAL HANOI LANDMARK72, HANOI, VIETNAM Especially this time, we're honored to have the Upstream Institute Training [3] hosted by the OpenStack Foundation on the next day (25 August 2019). [1] http://day.vietopeninfra.org/ [2] https://forms.gle/iiRBxxyRv1mGFbgi7 [3] https://docs.openstack.org/upstream-training/upstream-training-content.html See you in Hanoi! Bests, On behalf of the VietOpenInfra Group. -- *Trinh Nguyen* *www.edlab.xyz <https://www.edlab.xyz>*

1 1

Re: [Airship-discuss] ?==?utf-8?q? Unable to install airship-in-a-bottle
by Soujanya R M 12 Jul '19

12 Jul '19

Hi Team, Thanks for the response. I tried it with the patch[0] and it works fine. Except for one additional change, where I had to change the path of the files "run_shipyard.sh" and "pegleg.sh" because the path mentioned in the script "airship-in-a-bottle/manifests/common/deploy-airship.sh" is not the same as the paths generated in the local environment. After this change, the deployment went smoothly and I'm able to access the dashboard. Regards, Soujanya R M -------- Original Message -------- Subject: Re: [Airship-discuss] Unable to install airship-in-a-bottle Date: Wednesday, July 10, 2019 09:03 PM IST From: Roman Gorshunov <paye600(a)gmail.com> To: airship-discuss(a)lists.airshipit.org References: <46cb-5d259a80-31-53fb8680@266349328> Hi, Sorry, here is the link to the patch which could help: https://review.opendev.org/#/c/664426/ On Wed, Jul 10, 2019 at 9:58 AM Soujanya R M <soujanya(a)atsgen.com> wrote: > > Hi Roman, > > Thank you for your response. > I am not able to view the link of the patch that you are referring to. I tried following this deployment: https://github.com/airshipit/treasuremap/tree/master/tools/deployment/aiab > Even then I am facing an error: > > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller [-] [chart=ucp-keystone]: Error while testing release airship-ucp-keystone: grpc._ch > annel._Rendezvous: <_Rendezvous of RPC that terminated with: > status = StatusCode.DEADLINE_EXCEEDED > details = "Deadline Exceeded" > debug_error_string = "{"created":"@1562743212.057730337","description":"Error received from peer","file":"src/core/lib/surface/call.cc" > ,"file_line":1017,"grpc_message":"Deadline Exceeded","grpc_status":4}" > > > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller Traceback (most recent call last): > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/dist-packages/armada/handlers/tiller.py", line 509, > in test_release > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller for test_message in test_message_stream: > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 364, in __nex > t__ > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller return self._next() > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 358, in _next > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller raise self > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller status = StatusCode.DEADLINE_EXCEEDED > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller details = "Deadline Exceeded" > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller debug_error_string = "{"created":"@1562743212.057730337","description":"Error r > eceived from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"Deadline Exceeded","grpc_status":4}" > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller > > 2019-07-10 07:20:12.059 12502 ERROR armada.handlers.tiller > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada [-] Chart deploy [ucp-keystone] failed: armada.exceptions.tiller_exceptions.ReleaseE > xception: Failed to Test release: airship-ucp-keystone - Tiller Message: b'Install complete' > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada Traceback (most recent call last): > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/tiller.py", line 509, > in test_release > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada for test_message in test_message_stream: > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 364, in __nex > t__ > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada return self._next() > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/grpc/_channel.py", line 358, in _next > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada raise self > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada grpc._channel._Rendezvous: <_Rendezvous of RPC that terminated with: > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada status = StatusCode.DEADLINE_EXCEEDED > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada details = "Deadline Exceeded" > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada debug_error_string = "{"created":"@1562743212.057730337","description":"Error r > eceived from peer","file":"src/core/lib/surface/call.cc","file_line":1017,"grpc_message":"Deadline Exceeded","grpc_status":4}" > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada > > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada During handling of the above exception, another exception occurred: > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada Traceback (most recent call last): > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/armada.py", line 223, in handle_result > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada result = get_result() > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/lib/python3.5/concurrent/futures/_base.py", line 398, in result > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada return self.__get_result() > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/lib/python3.5/concurrent/futures/_base.py", line 357, in __get_result > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada raise self._exception > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada result = self.fn(*self.args, **self.kwargs) > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/armada.py", line 212, in deploy_chart > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada prefix, known_releases) > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/chart_deploy.py", line 257, in execute > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada self._test_chart(release_name, test_handler) > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/chart_deploy.py", line 268, in _test_chart > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada success = test_handler.test_release_for_success() > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/test.py", line 120, in test_release_for_success > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada self.release_name, timeout=self.timeout, cleanup=self.cleanup) > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada File "/usr/local/lib/python3.5/dist-packages/armada/handlers/tiller.py", line 522, in test_release > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada raise ex.ReleaseException(release, status, 'Test') > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada armada.exceptions.tiller_exceptions.ReleaseException: Failed to Test release: airship-ucp-keystone - Tiller Message: b'Install complete' > 2019-07-10 07:20:12.374 12502 ERROR armada.handlers.armada > 2019-07-10 07:20:12.379 12502 ERROR armada.handlers.armada [-] Chart deploy(s) failed: ['ucp-keystone'] > 2019-07-10 07:20:13.127 12502 INFO armada.handlers.lock [-] Releasing lock > 2019-07-10 07:20:13.140 12502 ERROR armada.cli [-] Caught internal exception: armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['ucp-keystone'] > 2019-07-10 07:20:13.140 12502 ERROR armada.cli Traceback (most recent call last): > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/cli/__init__.py", line 39, in safe_invoke > 2019-07-10 07:20:13.140 12502 ERROR armada.cli self.invoke() > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/cli/apply.py", line 209, in invoke > 2019-07-10 07:20:13.140 12502 ERROR armada.cli resp = self.handle(documents, tiller) > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/handlers/lock.py", line 63, in func_wrapper > 2019-07-10 07:20:13.140 12502 ERROR armada.cli return future.result() > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/lib/python3.5/concurrent/futures/_base.py", line 398, in result > 2019-07-10 07:20:13.140 12502 ERROR armada.cli return self.__get_result() > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/lib/python3.5/concurrent/futures/_base.py", line 357, in __get_result > 2019-07-10 07:20:13.140 12502 ERROR armada.cli raise self._exception > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/lib/python3.5/concurrent/futures/thread.py", line 55, in run > 2019-07-10 07:20:13.140 12502 ERROR armada.cli result = self.fn(*self.args, **self.kwargs) > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/cli/apply.py", line 252, in handle > 2019-07-10 07:20:13.140 12502 ERROR armada.cli return armada.sync() > 2019-07-10 07:20:13.140 12502 ERROR armada.cli File "/usr/local/lib/python3.5/dist-packages/armada/handlers/armada.py", line 250, in sync > 2019-07-10 07:20:13.140 12502 ERROR armada.cli raise armada_exceptions.ChartDeployException(failures) > 2019-07-10 07:20:13.140 12502 ERROR armada.cli armada.exceptions.armada_exceptions.ChartDeployException: Exception deploying charts: ['ucp-keystone'] > > Please help me if you know anything about this. > > Thank you and Regards, > Soujanya R M > > On Tuesday, July 09, 2019 08:58 EDT, Roman Gorshunov <paye600(a)gmail.com> wrote: > > > Hello Soujanya, > > Seems that a change related to this [0] patch has not been applied to > the AIAB environment. Try to change site documents accordingly and > re-run deployment. > > Best regards, > -- > Roman Gorshunov > > On Tue, Jul 9, 2019 at 12:19 PM Soujanya R M <soujanya(a)atsgen.com> wrote: > > > > Hi Everyone, > > > > I am facing an issue while installing airship-in-a-bottle dev_single_node. This is the error that appears. > > > > 2019-07-09 09:10:09,683 ERROR req_id=- ctx=- end_user=- user=- promenade.renderer:renderer.py: 78:render_template_into_bundler Error rendering template (/opt/promenade/promenade/templates/roles/genesis/etc/kubernetes/manifests/bootstrap-armada.yaml) > > Traceback (most recent call last): > > File "/opt/promenade/promenade/renderer.py", line 76, in render_template_into_bundler > > data = template.render(config=config, now=now) > > File "/usr/local/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render > > return original_render(self, *args, **kwargs) > > File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render > > return self.environment.handle_exception(exc_info, True) > > File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception > > reraise(exc_type, exc_value, tb) > > File "/usr/local/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise > > raise value.with_traceback(tb) > > File "<template>", line 120, in top-level template code > > jinja2.exceptions.UndefinedError: No match found for path HostSystem:images.monitoring_image > > 2019-07-09 09:10:09,684 ERROR req_id=- ctx=- end_user=- user=- promenade.exceptions:exceptions.py:222:display Error rendering template (/opt/promenade/promenade/templates/roles/genesis/etc/kubernetes/manifests/bootstrap-armada.yaml): No match found for path HostSystem:images.monitoring_image > > + error 'generating genesis' > > + set +x > > Error when generating genesis. > > + exit 1 > > + clean > > + set +x > > To remove files generated during this script's execution, delete /root/deploy. > > This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. > > > > A similar issue has been called out previously here: http://lists.airshipit.org/pipermail/airship-discuss/2019-June/000492.html > > > > Can someone help me fix this? > > > > Regards, > > Soujanya RM _______________________________________________ > > Airship-discuss mailing list > > Airship-discuss(a)lists.airshipit.org > > http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss > > > > > _______________________________________________ Airship-discuss mailing list Airship-discuss(a)lists.airshipit.org http://lists.airshipit.org/cgi-bin/mailman/listinfo/airship-discuss=cdde1dj…>

2 1

[sig][airship-ui] Announcing SIG-AIRSHIP-UI
by PACHECO, RODOLFO J 11 Jul '19

11 Jul '19

As discussed on Tuesday July 8, 2019 Design Call we are starting a special interest group called 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 The following doodle proposes times for the sig group meeting times : https://doodle.com/poll/rmscdht6yir84d3u Will close the Poll COB Friday July 18, 2019 The following individuals expressed interest on participating on this sig. Please make sure you vote for the meeting times. • Rodolfo Pacheco - rjpu(a)att.com • Alan Meadows - alan.meadows(a)att.com / PST • James Gu - jamesgu • Jemery Moffitt (SUSE) jeremy.moffitt(a)suse.com / PST • Gary Smith (SUSE) • T. R. Bosworth (SUSE) tbosworth(a)suse.com • Pete Birley - pete.birley(a)att.com / CST Regards Rodolfo Pacheco Home/Office 732 5337671

1 0

Unable to install airship-in-a-bottle
by Soujanya R M 10 Jul '19

10 Jul '19

Hi Everyone, I am facing an issue while installing airship-in-a-bottle dev_single_node. This is the error that appears. 2019-07-09 09:10:09,683 ERROR req_id=- ctx=- end_user=- user=- promenade.renderer:renderer.py: 78:render_template_into_bundler Error rendering template (/opt/promenade/promenade/templates/roles/genesis/etc/kubernetes/manifests/bootstrap-armada.yaml) Traceback (most recent call last): File "/opt/promenade/promenade/renderer.py", line 76, in render_template_into_bundler data = template.render(config=config, now=now) File "/usr/local/lib/python3.6/site-packages/jinja2/asyncsupport.py", line 76, in render return original_render(self, *args, **kwargs) File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 1008, in render return self.environment.handle_exception(exc_info, True) File "/usr/local/lib/python3.6/site-packages/jinja2/environment.py", line 780, in handle_exception reraise(exc_type, exc_value, tb) File "/usr/local/lib/python3.6/site-packages/jinja2/_compat.py", line 37, in reraise raise value.with_traceback(tb) File "<template>", line 120, in top-level template code jinja2.exceptions.UndefinedError: No match found for path HostSystem:images.monitoring_image 2019-07-09 09:10:09,684 ERROR req_id=- ctx=- end_user=- user=- promenade.exceptions:exceptions.py:222:display Error rendering template (/opt/promenade/promenade/templates/roles/genesis/etc/kubernetes/manifests/bootstrap-armada.yaml): No match found for path HostSystem:images.monitoring_image + error 'generating genesis' + set +x Error when generating genesis. + exit 1 + clean + set +x To remove files generated during this script's execution, delete /root/deploy. This VM is disposable. Re-deployment in this same VM will lead to unpredictable results. A similar issue has been called out previously here: http://lists.airshipit.org/pipermail/airship-discuss/2019-June/000492.html Can someone help me fix this? Regards, Soujanya RM

2 3

Airship TC Election Results
by MCEUEN, MATT 10 Jul '19

10 Jul '19

Airship community, Our initial Technical Committee election has concluded. Our initial TC has been elected for a one-year term, and effective immediately consists of: Ryan van Wyk James Gu Jan-Erik Mangs Alexander Hughes Alexey Odinokov It was a close race. Thank You to both the nominees and to the electorate for your participation; it's a milestone and point of maturity for the Airship community! Details can be found here[1], and the results will soon be published here [2]. Thanks, Matt McEuen [1]: https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8c97e01284ff9301 [2]: https://airship-election.readthedocs.io

3 2

Meeting Time Results: 2pm UTC, starting July 9th
by MCEUEN, MATT 09 Jul '19

09 Jul '19

Airship team, The results are in - the far and away most popular times were: 2pm UTC (score of 48) 2pm and 4pm UTC alternating (score of 41) 4pm UTC (score of 35) Nothing else was close. Based on this, we'll be switching to our new time of 2pm UTC (9am US CT) beginning on July 9th. Please note that this will overlap with the Airship design call by a half hour (until that shrinks down to one hour, as is planned). Let's do our best with the overlap and see how it goes. The raw data and instructions can be found here [1], and the tallies can be found here [2]. Thanks! Matt [1] https://etherpad.openstack.org/p/airship-meeting-vote-2019 [2] https://docs.google.com/spreadsheets/d/12RLKZ_EkjTAcLJ56VkxKXQxOLlIx7CzKK0p…

1 2

[sig][airship-yaml] Announcing SIG-AIRSHIP-YAML
by PACHECO, RODOLFO J 01 Jul '19

01 Jul '19

As discussed on Thursday’s June 27, 2019 Design Call we are starting a special interest group called airship-yaml. The purpose for this group will be to : • Design the YAML document structure • Optimize how will use Kustomize utilize the structure to implement the notion of service layers • Define the document interaction or interdependency with airshipctl • The result of this discussions should be , one or more Specs. • This work will define the document Index/Structure o How can sets of documents with specific purposes are to be identified. o i.e. identify bootstrap documents vs other types o Define mechanism to provide sequencing or ordering when appropriate. • Identify any other gaps needed in Kustomize • Identify any other functionality for airshipctl interaction with documents not yet identified in the airshipctl specification The following doodle proposes three times for the sig group meeting times : https://doodle.com/poll/eedcsm4khtidxbxd The following individuals expressed interest on participating on this sig. Please make sure you vote. • Alan Meadows - alan.meadows(a)att.com • Matt McEuen - matt.mceuen(a)att.com • James Gu - jgu(a)suse.com • Roman Gorshunov - Roman.Gorshunov(a)att.com • Ian Pittwood - ian.h.pittwood(a)accenture.com • Saket Sharma - saket.bihari(a)atsgen.com • Rodolfo Pacheco - mailto:rodolfo.pacheco@att.com • Jerome Brette ( I added hime). Notice that the subject line includes [sig][airship-yaml] , please make sure you add this to any email to airship-discuss(a)lists.airshipit.org when the topic relates to the airship-yaml discussion. Regards Rodolfo Pacheco Home/Office 732 5337671

1 0