From Jerry.Sun at windriver.com Wed Jun 5 17:56:26 2019 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Wed, 5 Jun 2019 17:56:26 +0000 Subject: [Airship-discuss] Reporting Armada bugs Message-ID: Hi All, I am trying to report a bug in armada. I do not see a launchpad for this project. Is the correct procedure to create an item here in storyboard: https://storyboard.openstack.org/#!/project/airship/armada Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Jun 5 18:01:51 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 5 Jun 2019 18:01:51 +0000 Subject: [Airship-discuss] Reporting Armada bugs In-Reply-To: References: Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709B3C51@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Jerry, yes that's the right place! If you don't mind, since we have a ML thread on this now anyway :) would you mind dropping a link to the issue in a reply here as well? We've been discussing Armada in the IRC channel today, and your issue might be something we're discussing already as well. Thanks, Matt From: Sun, Yicheng (Jerry) Sent: Wednesday, June 5, 2019 12:56 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Reporting Armada bugs Hi All, I am trying to report a bug in armada. I do not see a launchpad for this project. Is the correct procedure to create an item here in storyboard: https://storyboard.openstack.org/#!/project/airship/armada Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From guoyongxhzhf at 163.com Thu Jun 6 11:28:06 2019 From: guoyongxhzhf at 163.com (=?GBK?B?ufnTwg==?=) Date: Thu, 6 Jun 2019 19:28:06 +0800 (CST) Subject: [Airship-discuss] [airship] Is Ironic ready for Airship? Message-ID: <72e321e4.b816.16b2c8bc868.Coremail.guoyongxhzhf@163.com> I know Airship choose Maas as bare mental management tool. I want to know whether Maas is more suitable for Airship when it comes to under-infrastructure? If Maas is more suitable, then what feature should ironic develop? Thanks for your reply -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Thu Jun 6 11:53:37 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Thu, 6 Jun 2019 11:53:37 +0000 Subject: [Airship-discuss] [airship] Is Ironic ready for Airship? In-Reply-To: <72e321e4.b816.16b2c8bc868.Coremail.guoyongxhzhf@163.com> References: <72e321e4.b816.16b2c8bc868.Coremail.guoyongxhzhf@163.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709B450F@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Guoyong, MaaS is the bare metal management tooling that’s currently used by Airship (1.x), but we have long wanted to Integrate Ironic for provisioning. At the Open Infra PTG in Denver, we fleshed out our Airship 2.0 roadmap, and have decided to achieve that integration by using the metal3 project [1], which is under active development and which will expose bare metal provisioning via the Kubernetes Cluster API [2]. We’re drilling down on design for that (and other Airship 2.0 scope) in our twice-weekly design calls - if you’d like to join to discuss Ironic you are most welcome, and can find details on our wiki [3]. Links to recordings for previous discussions are captured in the design call agenda etherpad [4]. You can also add discussion topics to the agenda ahead of time. Let me know if you have any other questions! Matt [1] https://metal3.io [2] https://github.com/kubernetes-sigs/cluster-api [3] https://wiki.openstack.org/wiki/Airship#Design_Call_-_Twice-weekly [4] https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions From: 郭勇 Sent: Thursday, June 6, 2019 6:28 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] [airship] Is Ironic ready for Airship? I know Airship choose Maas as bare mental management tool. I want to know whether Maas is more suitable for Airship when it comes to under- infrastructure? If Maas is more suitable, then what feature should ironic develop? Thanks for your reply -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jerry.Sun at windriver.com Thu Jun 6 13:30:44 2019 From: Jerry.Sun at windriver.com (Sun, Yicheng (Jerry)) Date: Thu, 6 Jun 2019 13:30:44 +0000 Subject: [Airship-discuss] Reporting Armada bugs In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D89709B3C51@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <7C64A75C21BB8D43BD75BB18635E4D89709B3C51@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Hi Matt, Thanks for the reply. I created the following story on storyboard: https://storyboard.openstack.org/#!/story/2005834 I assigned it to myself since I already looked at it a bit and am working on a fix. Thanks, Jerry From: MCEUEN, MATT [mailto:MM9745 at att.com] Sent: June-05-19 2:02 PM To: Sun, Yicheng (Jerry) ; airship-discuss at lists.airshipit.org Subject: RE: Reporting Armada bugs Hi Jerry, yes that's the right place! If you don't mind, since we have a ML thread on this now anyway :) would you mind dropping a link to the issue in a reply here as well? We've been discussing Armada in the IRC channel today, and your issue might be something we're discussing already as well. Thanks, Matt From: Sun, Yicheng (Jerry) > Sent: Wednesday, June 5, 2019 12:56 PM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Reporting Armada bugs Hi All, I am trying to report a bug in armada. I do not see a launchpad for this project. Is the correct procedure to create an item here in storyboard: https://storyboard.openstack.org/#!/project/airship/armada Thanks, Jerry -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Fri Jun 7 20:42:20 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Fri, 7 Jun 2019 20:42:20 +0000 Subject: [Airship-discuss] Airship Governance Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709BA1F1@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, After much feedback, discussion, and refinement, the Airship Governance model has been approved and merged [1][2]! Thank you to everyone who helped steer our governance into an inclusive structure that will enable our project to quickly grow and mature. I plan to kick off the initial Nomination process for our Technical Committee next week, following OpenStack norms for timing and process. If you are interested in nominating for the Airship TC, please review its vision and responsibilities in our governance documentation, and stay tuned for instructions. Thank you, Matt [1]: https://opendev.org/airship/governance [2]: https://review.opendev.org/#/c/653865/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Jun 11 15:57:18 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 11 Jun 2019 15:57:18 +0000 Subject: [Airship-discuss] Canceled: Airship Jun 13, 18, 20 - Open Design Calls Message-ID: <30AD74B1-3695-4255-97AC-0DE098EBCBCA@att.com> REMINDER –Airship Design Call will be – CANCELLED Jun 13, Jun 18, Jun 20 Will resume calls on Jun 25, 2019 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 -------------- next part -------------- An HTML attachment was scrubbed... URL: From kennelson11 at gmail.com Tue Jun 11 22:57:39 2019 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 11 Jun 2019 15:57:39 -0700 Subject: [Airship-discuss] Shanghai PTG Changes Message-ID: Hello All, After Denver we were able to take time to reflect on the improvements we can make now that the PTG will occur immediately following the summit for the near future. While Shanghai will have its own set of variables, it's still good to reevaluate how we allocate time for groups and how we structure the week overall. tldr; - Onboarding is moving into the PTG for this round (updates stay a part of the Summit) - You can still do regular PTG stuff (or both onboarding and regular PTG stuff) - PTG slots can be as short as 1/4 of a day - More shared space at the Shanghai venue, less dedicated space - New breakdown: 1.5 days of Forum and 3.5 days of PTG - Survey will be out in a few weeks for requesting PTG space We'll have our traditional project team meetings at the PTG in Shanghai as the default format, that won't change. However, we know many of you don't expect to have all your regulars attend the PTG in Shanghai. To combat this and still help project teams make use of the PTG in the most effective way possible we are encouraging teams that want to meet but might not have all the people they need to have technical discussions to meet anyway and instead focus on a more thorough onboarding of our Chinese contributors. Project teams could also do a combination of the two, spend an hour and a half on onboarding (or however much time you see fit) and then have your regular technical discussions after. Project Updates will still be a part of the Summit like normal, its just the onboardings that will be compacted into the PTG for Shanghai. We are making PTG days more granular as well and will have the option to request 1/4 day slots in an effort to leave less empty space in the schedule. So if you are only doing onboarding, you probably only need 1/4 to 1/2 of a day. If you are doing just your regular technical discussions and still need three days, thats fine too. The venue itself (similar to Denver) will have a few large rooms for bigger teams to meet, however, most teams will meet in shared space. For those teams meeting to have only technical discussions and for teams that have larger groups, we will try to prioritize giving them their own dedicated space. For the shared spaces, we will add to the PTGbot more clearly defined locations within the shared space so its easier to find teams meeting there. I regret to inform you that, again, projection will be a very limited commodity. Yeah.. please don't shoot the messenger. Due to using mainly shared space, projection is just something we are not able to offer. The other change I haven't already mentioned is that we are going to have the PTG start a half day early. Instead of only being 3 days like in Denver, we are going to add more time to the PTG and subtract a half day from the Forum. Basically the breakdown will be 1.5 Forum and 3.5 PTG with the Summit overlapping the first two days. I will be sending the PTG survey out to PTLs/Project Leads in a couple weeks with a few changes. -Kendall Nelson (diablo_rojo) -------------- next part -------------- An HTML attachment was scrubbed... URL: From bh526r at att.com Wed Jun 12 19:42:16 2019 From: bh526r at att.com (HU, BIN) Date: Wed, 12 Jun 2019 19:42:16 +0000 Subject: [Airship-discuss] Airship 2.0 Blog Series #1 Published: Evolution towards 2.0 Message-ID: <179FD336116F754C876A9347238FE29A61136075@CAFRFD1MSGUSRIA.ITServices.sbc.com> Greetings, Airship community. I am very excited to share with everyone here that our Airship 2.0 Blog Series #1: Evolution towards 2.0 is published. This blog post is the first in a series that will be published over the coming months. The intent of the blog series is to provide community with some insights into the evolutionary steps we are taking with Airship to take advantage of evolving open source projects that cover some of the context domains, as well as the technological realignment we are planning as we grow towards Airship 2.0. We will cover the existing design, how we will evolve that design, as well as the benefits we anticipate with each of those changes. Enjoy reading. Bin -------------- next part -------------- An HTML attachment was scrubbed... URL: From bluejay.ahn at gmail.com Thu Jun 13 02:43:43 2019 From: bluejay.ahn at gmail.com (Jaesuk Ahn) Date: Thu, 13 Jun 2019 11:43:43 +0900 Subject: [Airship-discuss] some open design etherpad contents changed from English into Chinese Message-ID: Hi, In the following etherpad, someone changed sentences written in English into Chinese. I believe it must be some unintentional accident. https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions If you go through all the previous meeting logs, some sections are also written Chinese. If someone know how to revert the current etherpad to "before accident happen", it would be great. I am also trying to fix it manually with google translation. :) Please be careful when you do something on etherpad. Thanks. *Jaesuk Ahn*, Ph.D. Software Labs, SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From cheng1.li at intel.com Thu Jun 13 03:22:17 2019 From: cheng1.li at intel.com (Li, Cheng1) Date: Thu, 13 Jun 2019 03:22:17 +0000 Subject: [Airship-discuss] some open design etherpad contents changed from English into Chinese In-Reply-To: References: Message-ID: From my view, the Chinese is not native enough. So I guess it was translated with a translation(maybe google translation). Or some web auto translation tool? Thanks, Cheng From: Jaesuk Ahn [mailto:bluejay.ahn at gmail.com] Sent: Thursday, June 13, 2019 10:44 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] some open design etherpad contents changed from English into Chinese Hi, In the following etherpad, someone changed sentences written in English into Chinese. I believe it must be some unintentional accident. https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions If you go through all the previous meeting logs, some sections are also written Chinese. If someone know how to revert the current etherpad to "before accident happen", it would be great. I am also trying to fix it manually with google translation. :) Please be careful when you do something on etherpad. Thanks. Jaesuk Ahn, Ph.D. Software Labs, SK Telecom -------------- next part -------------- An HTML attachment was scrubbed... URL: From aswain at osidigital.com Mon Jun 17 14:48:43 2019 From: aswain at osidigital.com (Amarendra Swain) Date: Mon, 17 Jun 2019 14:48:43 +0000 Subject: [Airship-discuss] unable to install airship-in-a-bottle dev_single_node Message-ID: Hi Team, Am facing challenges to install airship-in-a-bottle dev_single_node and facing the followings error continuously. ment/v1', 'deckhand/CertificateKey/v1', 'metadata/Control/v1', 'deckhand/Certificate/v1'] 2019-06-13 15:09:54,952 INFO req_id=- ctx=- end_user=- user=- promenade.config:config.py: 41:init Deckhand engine returned 177 documents. 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- promenade.builder:builder.py: 94:build_genesis_script Building genesis script 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- promenade.config:config.py: 26:init Parsing document schemas. 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- promenade.config:config.py: 27:init Building config from 177 documents. 2019-06-13 15:10:10,928 WARNING req_id=- ctx=- end_user=- user=- promenade.tar_bundler:tar_bundler.py: 38:add Zero length file added to path=etc/apt/sources.list.d/promenade-sources.list 2019-06-13 15:10:11,803 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 " Could you please help me on this. Regards, Amar -------------- next part -------------- An HTML attachment was scrubbed... URL: From eli at mirantis.com Mon Jun 17 19:10:49 2019 From: eli at mirantis.com (Evgeny L) Date: Mon, 17 Jun 2019 12:10:49 -0700 Subject: [Airship-discuss] unable to install airship-in-a-bottle dev_single_node In-Reply-To: References: Message-ID: Hi Amarendra, Lately we've been working on transitioning Airship in a Bottle installation into a Treasuremap repository, to provide more up-to-date (and hopefully more stable) installation scripts, can you try installing it using the instruction from here? https://github.com/airshipit/treasuremap/tree/master/tools/deployment/aiab Thanks, On Mon, Jun 17, 2019 at 7:49 AM Amarendra Swain wrote: > Hi Team, > > > > Am facing challenges to install airship-in-a-bottle dev_single_node and facing the followings error continuously. > > > > ment/v1', 'deckhand/CertificateKey/v1', 'metadata/Control/v1', > 'deckhand/Certificate/v1'] > 2019-06-13 15:09:54,952 INFO req_id=- ctx=- end_user=- user=- > promenade.config:config.py: 41:*init* Deckhand engine returned 177 > documents. > 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- > promenade.builder:builder.py: 94:build_genesis_script Building genesis > script > 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- > promenade.config:config.py: 26:*init* Parsing document schemas. > 2019-06-13 15:09:55,020 INFO req_id=- ctx=- end_user=- user=- > promenade.config:config.py: 27:*init* Building config from 177 documents. > 2019-06-13 15:10:10,928 WARNING req_id=- ctx=- end_user=- user=- > promenade.tar_bundler:tar_bundler.py: 38:add Zero length file added to > path=etc/apt/sources.list.d/promenade-sources.list > 2019-06-13 15:10:11,803 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 " > > > > Could you please help me on this. > > > > > > Regards, > > Amar > > > > > > > _______________________________________________ > 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 Jun 17 20:34:01 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 17 Jun 2019 20:34:01 +0000 Subject: [Airship-discuss] Voting for Airship IRC Meeting Times Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709D1736@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi team, As discussed in the Denver PTG, Airship has a number of contributors across Europe, Asia, and the US, and there's no single weekly meeting time that works well for everyone. There are also different approaches that could be used to better accommodate team members in different time zones. Let's vote as a team to get the Times/Approaches that work for the majority of contributors. Tuesday meeting times: - Time A: [2pm UTC] https://everytimezone.com/s/1ecfaf84 - Time B: [4pm UTC] https://everytimezone.com/s/769eb585 - Time C: [9pm UTC] https://everytimezone.com/s/c5ee2f54 - Time D: [10pm UTC] https://everytimezone.com/s/c428653b Time B is our current meeting time. We also have three different ways we can approach those meeting times: - Uniform: same meeting time every week - Alternating: switch between two different times, every other week - Doubled: have two meetings every Tuesday on opposite ends of the day If we did "Doubled", I would generally facilitate both meetings, along with anyone who wanted to attend both; in general team members wouldn't be expected to be at both. INSTRUCTIONS: Please use the following etherpad: https://etherpad.openstack.org/p/airship-meeting-vote-2019 Please vote for your top five preferred meeting schedules, one per line, including a Time and an Approach. Please include your name/nick. Example: example_person: 1. Time A Uniform 2. Time D Uniform 3. Time A and D Alternating 4. Time A and C Doubled 5. Time C Uniform I will abstain from voting, do a by-hand Condorcet tally, and share the results. Voting is open to all Airship Contributors, will conclude EOD Tuesday the 25th, so I get two shots at reminding folks in the team meetings. Thanks! Matt From MM9745 at att.com Tue Jun 18 18:59:05 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Tue, 18 Jun 2019 18:59:05 +0000 Subject: [Airship-discuss] Airship 2019 Technical Committee Nominations are Open Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709D24C7@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, Nominations for the Airship Technical Committee are now open, and will remain open until June 25th, 19:00 UTC. All nominations must be submitted as a text file to the airship/election repository as explained at [1]. Please make sure to follow the candidacy file naming convention: candidates/2019/TC/ . Anyone who has demonstrated a commitment to Airship (community building, communications, or has had code merged to the Airship project repositories) within the last 12 months is eligible to run for the Technical Committee, as specified in the Airship Governance. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed here [2]. The electorate is requested to confirm their email addresses in gerrit prior to June 25th, so that the emailed ballots are mailed to the correct email addresses. Happy running, Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst [2]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst#2019-tc-candidates From kbaegis at gmail.com Wed Jun 19 10:16:41 2019 From: kbaegis at gmail.com (Stephen Nemeth) Date: Wed, 19 Jun 2019 04:16:41 -0600 Subject: [Airship-discuss] Divestiture In-Reply-To: <538741c8-c896-4ce4-a401-4ff93a8e5b4e@Spark> References: <538741c8-c896-4ce4-a401-4ff93a8e5b4e@Spark> Message-ID: Hi there everyone, Is airship still interested in incorporating openstack ironic for deployments? While metal kubed and cluster-api are cool, this simply increases the dependencies to run airship to begin with doesn’t it? It functionally assumes that you already have kubernetes available just to deploy a new kubernetes environment. Am I missing something critical here? Sorry in advance for being late to the discussion. Thanks, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Jun 19 14:29:23 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 19 Jun 2019 14:29:23 +0000 Subject: [Airship-discuss] Divestiture In-Reply-To: References: <538741c8-c896-4ce4-a401-4ff93a8e5b4e@Spark> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709D2D9B@MOSTLS1MSGUSRFF.ITServices.sbc.com> Hi Stephen, Don’t worry, the discussion is still very active. But yes, we still are planning to incorporate ironic using metal kubed. A driver for that to reduce the amount of custom code that Airship needs to drive provisioning – in the target state, the plan is metal kubed + cluster API will care for, * Ironic-based machine provisioning * Kubeadm-based cluster management * Declarative interfaces for the above Like you said, this does present a chicken and egg problem around using a k8s cluster to provision a k8s cluster. We’re designing for that now – in some use cases an ephemeral cluster can be spun up, and in some there would be a centralized management cluster (we call this “cloud harbor”) already. We have notes, draft design docs, and design meeting recordings if you’re interested, https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions and you’re most welcome to join the design discussion as well (times listed on our wiki https://wiki.openstack.org/wiki/Airship) Thanks, Matt From: Stephen Nemeth Sent: Wednesday, June 19, 2019 5:17 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Divestiture Hi there everyone, Is airship still interested in incorporating openstack ironic for deployments? While metal kubed and cluster-api are cool, this simply increases the dependencies to run airship to begin with doesn’t it? It functionally assumes that you already have kubernetes available just to deploy a new kubernetes environment. Am I missing something critical here? Sorry in advance for being late to the discussion. Thanks, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From kbaegis at gmail.com Wed Jun 19 15:01:09 2019 From: kbaegis at gmail.com (Stephen Nemeth) Date: Wed, 19 Jun 2019 09:01:09 -0600 Subject: [Airship-discuss] Divestiture In-Reply-To: <7C64A75C21BB8D43BD75BB18635E4D89709D2D9B@MOSTLS1MSGUSRFF.ITServices.sbc.com> References: <538741c8-c896-4ce4-a401-4ff93a8e5b4e@Spark> <7C64A75C21BB8D43BD75BB18635E4D89709D2D9B@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: Thank you for the inclusion and the links! My core concern with this approach is that it excludes or invalidates use-cases for airship; hence the title. Is it possible to design the inclusion of M^3 and cluster-api in a manner that doesn’t preclude using an ironic-drydock integration in the future that’s more lightweight (absent the chicken/egg issue)? Ironic standalone is incredibly lightweight and flexible. The footprint doesn’t require any complex clustering, key exchange, etc and it makes a very nice starting point for bootstrapping infrastructure. You can get started with some image blobs and a python venv. By comparison, a multi-tiered or ephemeral kubernetes clustering schema is going to give a lot of folks headaches trying to wrap their heads around and troubleshoot. As a consequence, it’s going to be more difficult to maintain and support. It may also couple your solutions to particular versions, operating systems, or network architectures with fewer workarounds as a side-effect. In my particular case, I use ironic-standalone on a MacBook. I made efforts to containerize it, however my container runtime doesn’t play nice with dhcp/tftp in particular (https://docs.docker.com/docker-for-mac/networking/). Fortunately, everything is nicely decoupled and the pxe/ipxe interfaces for ironic just need to be pointed at a directory to function. If we start from the assumption that everything is operating in a container provided by a particular registry then this would invalidate my approach and I believe that I would be blocked on using airship for a deployment. I’ll try to make that meeting and maybe we can figure this out then. Thanks, Stephen On Jun 19, 2019, 8:31 AM -0600, MCEUEN, MATT , wrote: > Hi Stephen, > > Don’t worry, the discussion is still very active.  But yes, we still are planning to incorporate ironic using metal kubed.  A driver for that to reduce the amount of custom code that Airship needs to drive provisioning – in the target state, the plan is metal kubed + cluster API will care for, > > • Ironic-based machine provisioning > • Kubeadm-based cluster management > • Declarative interfaces for the above > > > Like you said, this does present a chicken and egg problem around using a k8s cluster to provision a k8s cluster.  We’re designing for that now – in some use cases an ephemeral cluster can be spun up, and in some there would be a centralized management cluster (we call this “cloud harbor”) already.  We have notes, draft design docs, and design meeting recordings if you’re interested,  https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions > and you’re most welcome to join the design discussion as well (times listed on our wiki https://wiki.openstack.org/wiki/Airship) > > Thanks, > Matt > > From: Stephen Nemeth > Sent: Wednesday, June 19, 2019 5:17 AM > To: airship-discuss at lists.airshipit.org > Subject: [Airship-discuss] Divestiture > > Hi there everyone, > > Is airship still interested in incorporating openstack ironic for deployments? While metal kubed and cluster-api are cool, this simply increases the dependencies to run airship to begin with doesn’t it? It functionally assumes that you already have kubernetes available just to deploy a new kubernetes environment. Am I missing something critical here? > > Sorry in advance for being late to the discussion. > > Thanks, > > Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Jun 19 15:46:05 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 19 Jun 2019 15:46:05 +0000 Subject: [Airship-discuss] Divestiture In-Reply-To: References: <538741c8-c896-4ce4-a401-4ff93a8e5b4e@Spark> <7C64A75C21BB8D43BD75BB18635E4D89709D2D9B@MOSTLS1MSGUSRFF.ITServices.sbc.com> Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709D2F02@MOSTLS1MSGUSRFF.ITServices.sbc.com> Gotcha. Yes, I think this is something we could discuss in our design calls, starting with the use case and working out from there. This Thursday’s call is cancelled but we’ll pick back up next week. However, I don’t think we’d want to sidestep a containerized approach for Ironic, since that is one of Airship’s core principles for dependency management/distribution. E.g., we put quite a bit of effort into containerizing maas for Airship 1.x. In any case, keep in mind that the Airship 2.0 design is modular, and if you’d like to use something other than Airship to manage host provisioning, that should be fine – you’ll still be able manage workloads on top of the cluster via Airship. Thanks, Matt From: Stephen Nemeth Sent: Wednesday, June 19, 2019 10:01 AM To: MCEUEN, MATT Cc: airship-discuss at lists.airshipit.org Subject: RE: [Airship-discuss] Divestiture Thank you for the inclusion and the links! My core concern with this approach is that it excludes or invalidates use-cases for airship; hence the title. Is it possible to design the inclusion of M^3 and cluster-api in a manner that doesn’t preclude using an ironic-drydock integration in the future that’s more lightweight (absent the chicken/egg issue)? Ironic standalone is incredibly lightweight and flexible. The footprint doesn’t require any complex clustering, key exchange, etc and it makes a very nice starting point for bootstrapping infrastructure. You can get started with some image blobs and a python venv. By comparison, a multi-tiered or ephemeral kubernetes clustering schema is going to give a lot of folks headaches trying to wrap their heads around and troubleshoot. As a consequence, it’s going to be more difficult to maintain and support. It may also couple your solutions to particular versions, operating systems, or network architectures with fewer workarounds as a side-effect. In my particular case, I use ironic-standalone on a MacBook. I made efforts to containerize it, however my container runtime doesn’t play nice with dhcp/tftp in particular (https://docs.docker.com/docker-for-mac/networking/). Fortunately, everything is nicely decoupled and the pxe/ipxe interfaces for ironic just need to be pointed at a directory to function. If we start from the assumption that everything is operating in a container provided by a particular registry then this would invalidate my approach and I believe that I would be blocked on using airship for a deployment. I’ll try to make that meeting and maybe we can figure this out then. Thanks, Stephen On Jun 19, 2019, 8:31 AM -0600, MCEUEN, MATT >, wrote: Hi Stephen, Don’t worry, the discussion is still very active. But yes, we still are planning to incorporate ironic using metal kubed. A driver for that to reduce the amount of custom code that Airship needs to drive provisioning – in the target state, the plan is metal kubed + cluster API will care for, * Ironic-based machine provisioning * Kubeadm-based cluster management * Declarative interfaces for the above Like you said, this does present a chicken and egg problem around using a k8s cluster to provision a k8s cluster. We’re designing for that now – in some use cases an ephemeral cluster can be spun up, and in some there would be a centralized management cluster (we call this “cloud harbor”) already. We have notes, draft design docs, and design meeting recordings if you’re interested, https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions and you’re most welcome to join the design discussion as well (times listed on our wiki https://wiki.openstack.org/wiki/Airship) Thanks, Matt From: Stephen Nemeth > Sent: Wednesday, June 19, 2019 5:17 AM To: airship-discuss at lists.airshipit.org Subject: [Airship-discuss] Divestiture Hi there everyone, Is airship still interested in incorporating openstack ironic for deployments? While metal kubed and cluster-api are cool, this simply increases the dependencies to run airship to begin with doesn’t it? It functionally assumes that you already have kubernetes available just to deploy a new kubernetes environment. Am I missing something critical here? Sorry in advance for being late to the discussion. Thanks, Stephen -------------- next part -------------- An HTML attachment was scrubbed... URL: From paye600 at gmail.com Thu Jun 20 16:58:22 2019 From: paye600 at gmail.com (Roman Gorshunov) Date: Thu, 20 Jun 2019 18:58:22 +0200 Subject: [Airship-discuss] New Airship mailing list Message-ID: Hello Jonathan, You are listed as admin of our 2 existing mailing lists. Would you kindly take care of one more list for us? airship-job-failures - Notification messages for failures from CICD jobs. https://review.opendev.org/#/c/666606/ Thank you! Best regards, -- Roman Gorshunov From rp2723 at att.com Mon Jun 24 19:09:48 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Mon, 24 Jun 2019 19:09:48 +0000 Subject: [Airship-discuss] =?utf-8?q?REMINDER_=E2=80=93_Airship_Design_Cal?= =?utf-8?q?l__will_RESUME_Tomorrow_Jun_25=2C_2019?= Message-ID: <5082F140-C515-4CDA-9963-8DA863203BB6@att.com> REMINDER –Airship Design Call will RESUME Tomorrow Jun 25, 2019 at 9:00 AM EST/1:00 PM UTC Notice >>> Tomorrows call will be on a different bridge : attcorp.webex.com/join/mm9745 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs JIRA for Airship https://airship.atlassian.net/projects/AIR/issues https://airship.atlassian.net/secure/RapidBoard.jspa?rapidView=1&projectKey=AIR&view=planning.nodetail&epics=visible __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Mon Jun 24 21:01:39 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Mon, 24 Jun 2019 21:01:39 +0000 Subject: [Airship-discuss] Reminder: Airship 2019 Technical Committee Nominations are Open Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709D9212@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, Just a reminder that the window for Airship TC nominations will close tomorrow, June 25th at 19:00 UTC. If you'd like to nominate, please do so before then. Thanks, Matt -----Original Message----- From: MCEUEN, MATT Sent: Tuesday, June 18, 2019 1:59 PM To: airship-discuss at lists.airshipit.org Subject: Airship 2019 Technical Committee Nominations are Open Airship community, Nominations for the Airship Technical Committee are now open, and will remain open until June 25th, 19:00 UTC. All nominations must be submitted as a text file to the airship/election repository as explained at [1]. Please make sure to follow the candidacy file naming convention: candidates/2019/TC/ . Anyone who has demonstrated a commitment to Airship (community building, communications, or has had code merged to the Airship project repositories) within the last 12 months is eligible to run for the Technical Committee, as specified in the Airship Governance. Additional information about the nomination process can be found here [1]. Shortly after election officials approve candidates, they will be listed here [2]. The electorate is requested to confirm their email addresses in gerrit prior to June 25th, so that the emailed ballots are mailed to the correct email addresses. Happy running, Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst [2]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst#2019-tc-candidates From MM9745 at att.com Wed Jun 26 14:35:42 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 26 Jun 2019 14:35:42 +0000 Subject: [Airship-discuss] Airship 2019 Technical Committee Nominations are Closed Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709DC0D5@MOSTLS1MSGUSRFF.ITServices.sbc.com> Airship community, Nominations for the Airship Technical Committee are now closed, and the following individuals have nominated: * Alexander Hughes * Alexey Odinokov * Jaesuk Ahn * James Gu * Jan-Erik Mangs * Ryan van Wyk Their candidacy submissions can be found here [1]. The election will run from July 2, 2019 19:00 UTC through July 9, 2019 19:00 UTC. Instructions for voting will be forthcoming and will be sent to the electorate via their email addresses in gerrit. Good luck to our nominees! Matt McEuen [1]: https://opendev.org/airship/election/src/branch/master/doc/source/index.rst#2019-tc-candidates From jimmy at openstack.org Wed Jun 26 17:48:11 2019 From: jimmy at openstack.org (Jimmy McArthur) Date: Wed, 26 Jun 2019 12:48:11 -0500 Subject: [Airship-discuss] CFP Deadline for Open Infrastructure Summit Shanghai Message-ID: <5D13AFDB.2090306@openstack.org> Hi Everyone! The July 2 deadline to submit a presentation [1] for the Open Infrastructure Summit [2] in Shanghai is in less than one week! Submit your session today and join the global community in Shanghai, November 4-6, 2019. Sessions will be presented in both Mandarin and English, so you may submit your presentation in either language. Submit your presentations, panels, and hands-on workshops [3] before July 2 at 11:59 pm PT (July 3, 2019 at 15:00 China Standard Time). Tracks [4]: Container Infrastructure Hands-on Workshops AI, Machine Learning & HPC Private & Hybrid Cloud Public Cloud 5G, NFV & Edge Open Development Getting Started CI/CD Security Upcoming Shanghai Summit Deadlines * Register now [5] before the early bird registration deadline in early August (USD or RMB options available) * Apply for Travel Support [6] before August 8. For more information on the Travel Support Program, go here [7]. * Interested in sponsoring the Summit? [8]. * The content submission process for the Forum and Project Teams Gathering will be managed separately in the upcoming months. We look forward to your submissions! Cheers, Jimmy [1] https://cfp.openstack.org/ [2] https://www.openstack.org/summit/shanghai-2019/ [3] https://cfp.openstack.org/ [4] https://www.openstack.org/summit/shanghai-2019/summit-categories/ [5] https://www.openstack.org/summit/shanghai-2019/ [6] https://openstackfoundation.formstack.com/forms/travelsupportshanghai [7] https://www.openstack.org/summit/shanghai-2019/travel/ [8] https://www.openstack.org/summit/shanghai-2019/sponsors/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Wed Jun 26 19:40:56 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Wed, 26 Jun 2019 19:40:56 +0000 Subject: [Airship-discuss] =?utf-8?q?REMINDER_=E2=80=93_Airship_Design_Cal?= =?utf-8?q?l___Tomorrow_Jun_27=2C_2019?= Message-ID: REMINDER –Airship Design Calls continue Tomorrow Jun 27, 2019 at 11:00 AM EST/3:00 PM UTC Notice >>> We can return to the normal bridge now : attcorp.webex.com/join/rp2723 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs JIRA for Airship https://airship.atlassian.net/projects/AIR/issues https://airship.atlassian.net/secure/RapidBoard.jspa?rapidView=1&projectKey=AIR&view=planning.nodetail&epics=visible __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 Regards Rodolfo Pacheco Home/Office 732 5337671 Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From MM9745 at att.com Wed Jun 26 19:57:41 2019 From: MM9745 at att.com (MCEUEN, MATT) Date: Wed, 26 Jun 2019 19:57:41 +0000 Subject: [Airship-discuss] Meeting Time Results: 2pm UTC, starting July 9th Message-ID: <7C64A75C21BB8D43BD75BB18635E4D89709DC354@MOSTLS1MSGUSRFF.ITServices.sbc.com> 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_EkjTAcLJ56VkxKXQxOLlIx7CzKK0peNwj8OSM -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Thu Jun 27 15:01:32 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Thu, 27 Jun 2019 15:01:32 +0000 Subject: [Airship-discuss] =?utf-8?q?REMINDER_=E2=80=93_Airship_Design_Cal?= =?utf-8?q?l___Tomorrow_Jun_27=2C_2019?= In-Reply-To: References: Message-ID: <8EB15784-2F9E-470A-9220-D314E6550C3C@att.com> Please notice link below sends you to the wrong place : Try http://attcorp.webex.com/join/rp2723 Regards Rodolfo Pacheco Home/Office 732 5337671 From: "PACHECO, RODOLFO J" Date: Wednesday, June 26, 2019 at 3:40 PM To: "airship-discuss at lists.airshipit.org" Subject: REMINDER – Airship Design Call Tomorrow Jun 27, 2019 REMINDER –Airship Design Calls continue Tomorrow Jun 27, 2019 at 11:00 AM EST/3:00 PM UTC Notice >>> We can return to the normal bridge now : attcorp.webex.com/join/rp2723 Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs JIRA for Airship https://airship.atlassian.net/projects/AIR/issues https://airship.atlassian.net/secure/RapidBoard.jspa?rapidView=1&projectKey=AIR&view=planning.nodetail&epics=visible __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 Regards Rodolfo Pacheco Home/Office 732 5337671 Regards Rodolfo Pacheco Home/Office 732 5337671 -------------- next part -------------- An HTML attachment was scrubbed... URL: From aodinokov at mirantis.com Fri Jun 21 19:23:47 2019 From: aodinokov at mirantis.com (Alexey Odinokov) Date: Fri, 21 Jun 2019 19:23:47 -0000 Subject: [Airship-discuss] Airship TC: Adding Alexey Odinokov candidacy for TC role Message-ID: Hi, My name is Alexey Odinokov and I'd like to announce my candidacy for election to the Airship Technical Committee. Please find my nomination letter here: https://review.opendev.org/666903 I’m a senior development manager in Mirantis for more than 5 years and all that time I was leading (from engineering, architecture and project management perspectives) teams which were responsible for Openstack and K8S clouds deployment automation and feature enablement including clouds based on Airship. Before that I was working as a software engineer and later manager in Networking and system programming e.g. Linux kernel driver development that was a very good knowledge basement for cloud technologies. I believe that open source and community work helps building much stronger and feature-rich products that everyone benefits from. Since my team is already involved in the different parts of Airship 1.0, like Promenade, Treasuremap and etc ( https://www.stackalytics.com/?project_type=openstack-others&metric=commits&company=mirantis&release=all&module=airship-group ), I along with my team wish to make Airship community a successful by contributing more into Airship itself and underlying project’s. We were excited to see and to collaborate into the Airship 2.0 roadmap, because it resonates with our personal understanding of where the project should be developed. Working in the technical committee I’ll be able to contribute by bringing some additional resources provided by my company, representing my company to align its roadmap and Airship, find and contribute into common parts and share our expertise. I feel I am well equipped to help Airship to reach the next release, and I hope you do too. Thank you, Alexey -------------- next part -------------- An HTML attachment was scrubbed... URL: From cheng1.li at intel.com Sun Jun 9 05:58:42 2019 From: cheng1.li at intel.com (Li, Cheng1) Date: Sun, 09 Jun 2019 05:58:42 -0000 Subject: [Airship-discuss] [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment In-Reply-To: References: Message-ID: Finally, I have been able to deploy airsloop on virtual env. I created two VMs(libvirt/kvm driven), one for genesis and the other for compute node. These two VMs were on the same host. As the compute node VM is supposed to be provisioned by maas via ipmi/pxe. So I used virtualbmc to simulate the ipmi. I authored the site by following these two guides[1][2]. It’s the mix of guide[1] and guide[2]. The commands I used are all these ones[3]. After fixing several issue, I have deployed the virtual airsloop env. I list here some issues I met: 1. Node identify failed. At the beginning of step ‘prepare_and_deploy_nodes’, the drydock power on the compute node VM via ipmi. Once the compute VM starts up via pxe boot, it runs script to detect local network interfaces and sends the info back to drycok. So the drydock can identify the node based on the received info. But the compute VM doesn’t have real ILO interface, so the drydock can’t identify it. What I did to workaround this was to manually fill the ipmi info on maas web page. 2. My host doesn’t have enough CPU cores, neither the VMs. So I had to increase --pods-per-core in kubelet.yaml. 3. The disk name in compute VM is vda, instead of sda. Drydock can’t map the alias device name to vda, so I had to used the fixed alias name ‘vda’ which is the same as it’s real device name.(it was ‘bootdisk’) 4. My host doesn’t have enough resource(CPU, memory), so I removed some resource consuming components(logging, monitoring). Besides, I disabled the neutron rally test. As it failed with timeout error because of the resource limits. I also paste my site changes[4] for reference. [1] https://airship-treasuremap.readthedocs.io/en/latest/authoring_and_deployment.html [2] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html [3] https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started [4] https://github.com/cheng1li/treasuremap/commit/7a8287720dacc6dc1921948aaddec96b8cf2645e Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Thursday, May 30, 2019 7:29 PM To: Li, Cheng1 ; airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, I am trying to create Airship-Seaworthy from the link https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html It requires 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes to be configured, but there is no documentation of how to install and getting started with Airship-Seaworthy. Do we need to follow the “Getting Started” section mentioned in Airsloop or will there be any difference in case of Seaworthy. https://airship-treasuremap.readthedocs.io/en/latest/airsloop.html#getting-started Also what all configurations need to be run from the 3 controller nodes and what needs to be run from 3 computes? Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) From: Li, Cheng1 > Sent: 30 May 2019 08:29 To: Anirudh Gupta >; airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: RE: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment I have the same question. I haven’t seen any docs which guides how to deploy airsloop/air-seaworthy in virtual env. I am trying to deploy airsloop on libvirt/kvm driven virtual env. Two VMs, one for genesis, the other for compute. Virtualbmc for ipmi simulation. The genesis.sh scripts has been run on genesis node without error. But deploy_site fails at prepare_and_deploy_nodes task(action ‘set_node_boot’ timeout). I am still investigating this issue. It will be great if we have official document for this scenario. Thanks, Cheng From: Anirudh Gupta [mailto:Anirudh.Gupta at hsc.com] Sent: Wednesday, May 29, 2019 3:31 PM To: airship-discuss at lists.airshipit.org; airship-announce at lists.airshipit.org; openstack-dev at lists.openstack.org; openstack at lists.openstack.org Subject: [Airship-Seaworthy] Deployment of Airship-Seaworthy on Virtual Environment Hi Team, We want to test Production Ready Airship-Seaworthy in our virtual environment The link followed is https://airship-treasuremap.readthedocs.io/en/latest/seaworthy.html As per the document we need 6 DELL R720xd bare-metal servers: 3 control, and 3 compute nodes. But we need to deploy our setup on Virtual Environment. Does Airship-Seaworthy support Installation on Virtual Environment? We have 2 Rack Servers with Dual-CPU Intel® Xeon® E5 26xx with 16 cores each and 128 GB RAM. Is it possible that we can create Virtual Machines on them and set up the complete environment. In that case, what possible infrastructure do we require for setting up the complete setup. Looking forward for your response. Regards अनिरुद्ध गुप्ता (वरिष्ठ अभियंता) Hughes Systique Corporation D-23,24 Infocity II, Sector 33, Gurugram, Haryana 122001 DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rp2723 at att.com Tue Jun 11 15:55:20 2019 From: rp2723 at att.com (PACHECO, RODOLFO J) Date: Tue, 11 Jun 2019 15:55:20 -0000 Subject: [Airship-discuss] Canceled: Airship - Open Design Call - Tuesdays Message-ID: <99088997CCAD0C4BA20008FD094344963C2AF2C3@MISOUT7MSGUSRDI.ITServices.sbc.com> REMINDER –Airship Design Call – CANCELLED Will resume calls on Jun 25, 2019 Based on the doodle votes the meeting length will be 90 mins Join us to continue Airship 2.0 Design discussions Etherpad for the Airship Open Design discussion https://etherpad.openstack.org/p/Airship_OpenDesignDiscussions Storyboard in flight Specs https://storyboard.openstack.org/#!/project/openstack/airship-specs Github Airship Specs https://github.com/openstack/airship-specs/tree/master/specs Inflight/reviewing specs https://review.openstack.org/#/q/status:open+airship-specs __________________________________________ Join by video system i Dial rp2723 at attcorp.webex.com and enter your host PIN 02083790. You can also dial 173.243.2.68 and enter your meeting number. Join by phone 1-844-517-1415 United States Toll Free 1-618-230-6039 United States Toll Access code: 733 333 726 Host PIN: 02083790 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/calendar Size: 3963 bytes Desc: not available URL: