| *** uzumaki has joined #airshipit | 02:42 | |
| *** uzumaki has quit IRC | 03:14 | |
| *** evrardjp has quit IRC | 04:33 | |
| *** evrardjp has joined #airshipit | 04:33 | |
| airship-irc-bot | <alexander.hughes> hello all! today's IRC/Slack meeting will begin in about 20 minutes. please add any agenda items you would like to discuss here: | 13:37 |
|---|---|---|
| airship-irc-bot | <alexander.hughes> #link https://etherpad.opendev.org/p/airship-team-meeting | 13:38 |
| *** dwalt has joined #airshipit | 13:42 | |
| *** muhaha has joined #airshipit | 13:59 | |
| alexanderhughes | #startmeeting airship | 14:01 |
| openstack | Meeting started Tue Oct 13 14:01:15 2020 UTC and is due to finish in 60 minutes. The chair is alexanderhughes. Information about MeetBot at http://wiki.debian.org/MeetBot. | 14:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 14:01 |
| *** openstack changes topic to " (Meeting topic: airship)" | 14:01 | |
| openstack | The meeting name has been set to 'airship' | 14:01 |
| alexanderhughes | #topic Rollcall | 14:01 |
| *** openstack changes topic to "Rollcall (Meeting topic: airship)" | 14:01 | |
| dwalt | o/ | 14:01 |
| mattmceuen | o/ | 14:01 |
| alexanderhughes | hello all! let's give it a few minutes for people to transition over from the design call. today's agenda is here: https://etherpad.opendev.org/p/airship-team-meeting | 14:01 |
| airship-irc-bot | <ih616h> o/ | 14:01 |
| airship-irc-bot | <mf4716> o/ | 14:01 |
| airship-irc-bot | <mb551n> o/ | 14:02 |
| airship-irc-bot | <james.gu> 0/ | 14:02 |
| portdirect | o/ | 14:02 |
| *** roman_g has joined #airshipit | 14:02 | |
| airship-irc-bot | <sirajudeen.yasin> o/ | 14:02 |
| alexanderhughes | alright let's hop into the agenda, Matt I believe this first one is yours | 14:03 |
| alexanderhughes | #topic New project proposal: airship/airship-in-a-pod | 14:03 |
| *** openstack changes topic to "New project proposal: airship/airship-in-a-pod (Meeting topic: airship)" | 14:03 | |
| mattmceuen | Thanks. So Ian has been working on a project that essentially wraps up the VM-oriented CICD process inside a pod | 14:04 |
| mattmceuen | It will be great for several use cases: | 14:04 |
| mattmceuen | CICD | 14:04 |
| mattmceuen | Dev local testing | 14:04 |
| mattmceuen | Demo environment | 14:04 |
| mattmceuen | It's name has evolved to usually be called "Airship-in-a-Pod" | 14:05 |
| mattmceuen | I wanted to make sure folks were aware of this, and that we fit it into airship appropriately (it's up in Ian's github atm) | 14:05 |
| mattmceuen | I am going to guess that it was Pete who suggested that AiaP live in-tree with airshipctl itself, as opposed to a standalone project? | 14:06 |
| portdirect | you guess right | 14:06 |
| mattmceuen | bam | 14:06 |
| portdirect | that was the original intent when we started this | 14:06 |
| mattmceuen | wfm! any concerns with that approach, @ih616h? | 14:06 |
| airship-irc-bot | <ih616h> no concerns here | 14:07 |
| portdirect | update this: https://review.opendev.org/#/c/739753/ | 14:07 |
| mattmceuen | great. any other updates / info you'd share, Ian? | 14:07 |
| portdirect | with the work ians done over the last couple of weeks and and i think it should be good to go? | 14:07 |
| airship-irc-bot | <ih616h> no other updates, but any feedback on that repo would be helpful | 14:07 |
| mattmceuen | #link https://github.com/ian-howell/v_nodes | 14:08 |
| portdirect | please can we get this in gerrit? | 14:08 |
| * portdirect knows he sounds like a broken record now | 14:08 | |
| airship-irc-bot | <ih616h> I'll get a PS up today | 14:08 |
| alexanderhughes | sounds good, looking forward to that patch Ian and thanks for all your hard work on airship in a pod! | 14:08 |
| portdirect | nice - #739753 should be ready for it | 14:09 |
| mattmceuen | adding on to stacey's PS might probably help illuminate diffs | 14:09 |
| portdirect | thx :) | 14:09 |
| portdirect | yup | 14:09 |
| airship-irc-bot | <ih616h> sounds good | 14:09 |
| alexanderhughes | great :) moving on to the PTG I believe this one is yours as well @mattmceuen | 14:09 |
| alexanderhughes | #topic PTG Etherpad | 14:09 |
| *** openstack changes topic to "PTG Etherpad (Meeting topic: airship)" | 14:09 | |
| mattmceuen | Awesome. Thanks Ian, looking forward to that very much, and to portdirect & stacey for getting that thing started | 14:09 |
| mattmceuen | So next week is the Summit, and the following week is the PTG | 14:10 |
| mattmceuen | (now /I/ sound like a broken record :) | 14:10 |
| mattmceuen | Here is the etherpad where we can form up our PTG agenda: https://etherpad.opendev.org/p/wallaby-ptg-airship | 14:10 |
| mattmceuen | Please feel encouraged to add on any topics -- not just design topics, but also community practices, dev practices, demos, etc | 14:11 |
| mattmceuen | I think that's all I have on that, any q's? | 14:12 |
| alexanderhughes | I think everyone has seen the registration links for both the PTG and Summit by now, each are free to attend | 14:12 |
| mattmceuen | don't forget to register for both events | 14:12 |
| alexanderhughes | the links to both, and the schedules are available on last month's blog https://www.airshipit.org/blog/airship-update-september-2020/ | 14:12 |
| alexanderhughes | thanks Matt! moving on to the next item | 14:13 |
| alexanderhughes | #topic Daylight Saving Time ending November 1st - meetings will continue to observe CST timezone | 14:13 |
| *** openstack changes topic to "Daylight Saving Time ending November 1st - meetings will continue to observe CST timezone (Meeting topic: airship)" | 14:13 | |
| alexanderhughes | this is something we've struggled with over the last year or so - is communicating when DST ends in the US and how it affects meetings | 14:14 |
| alexanderhughes | so we'll send out some reminders over the next few weeks. November 1st, DST ends so we "fall back" an hour. this will effectively make meetings one hour later for UTC timezones as we will continue to observe CST times for meeting schedules | 14:14 |
| alexanderhughes | please be sure to check the wiki for updated meeting times, and keep an eye on the airship discuss mailing list as we get closer to November | 14:15 |
| alexanderhughes | #topic Roundtable | 14:15 |
| *** openstack changes topic to "Roundtable (Meeting topic: airship)" | 14:15 | |
| alexanderhughes | we've run through the agenda items in record time, opening the floor for any roundtable items :) | 14:16 |
| mattmceuen | One review request from me: https://review.opendev.org/#/c/755672/ -- Add version replacement for calico, helm-operator, hwcc functions | 14:16 |
| mattmceuen | As well as a request-request -- as we add new functions, let's please take version replacement into account right off the bat, now that we have it | 14:16 |
| roman_g | https://review.opendev.org/685038 https://review.opendev.org/685047 https://review.opendev.org/755456 - small review requests from me | 14:17 |
| alexanderhughes | thanks Matt and Roman. Community - let's get some eyes on these patches please as you have time and help get these merged in a timely manner | 14:18 |
| alexanderhughes | #endmeeting | 14:18 |
| *** openstack changes topic to "https://opendev.org/airship || https://wiki.openstack.org/wiki/Airship || https://review.opendev.org/#/q/projects:airship+status:open+NOT+label:Verified%253D-1+NOT+label:Workflow%253D-1+NOT+message:DNM+NOT+message:WIP" | 14:18 | |
| openstack | Meeting ended Tue Oct 13 14:18:19 2020 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:18 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-10-13-14.01.html | 14:18 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-10-13-14.01.txt | 14:18 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/airship/2020/airship.2020-10-13-14.01.log.html | 14:18 |
| alexanderhughes | thanks everyone! | 14:18 |
| roman_g | Thanks! | 14:19 |
| airship-irc-bot | <mf4716> thanks all | 14:19 |
| *** StaceyF has joined #airshipit | 14:25 | |
| airship-irc-bot | <sidney.shiba> Hello, can someone point me to the Go code I should look into to understand the Phase Execution design, may be where baremetal is creating a management cluster so I can refactor the bootstrap ephemeral cluster code as per new design? | 16:04 |
| airship-irc-bot | <kk6740> @sidney.shiba Hi | 16:05 |
| *** muhaha has quit IRC | 16:05 | |
| airship-irc-bot | <kk6740> I think i did share the link, but let me share it again | 16:05 |
| airship-irc-bot | <kk6740> https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_317/755116/14/check/openstack-tox-docs/3173ecb/docs/phases.html | 16:06 |
| airship-irc-bot | <kk6740> please take a look at. this, if it’s not sufficient, we can have a call and discuss this further | 16:06 |
| airship-irc-bot | <kk6740> and i can help u | 16:06 |
| airship-irc-bot | <sidney.shiba> I was looking at an old document. This one has more details. Will go through it first. Thanks. | 16:08 |
| airship-irc-bot | <sidney.shiba> @se6518, @mattmceuen could you please review patch sets https://review.opendev.org/#/c/748537/ and https://review.opendev.org/#/c/752298/. They have been re-factorized to only use Go code as per review comments. | 16:31 |
| *** uzumaki has joined #airshipit | 16:34 | |
| uzumaki | hey @mattmceuen you there? | 16:44 |
| uzumaki | I missed the meeting(s) today, wanted to talk about that RAID hw-profile thing, the rebase passed the gates, and I'm thinking that should be it? or do we still follow the path of new profile? @mattmceuen | 16:45 |
| uzumaki | Take a look at it if you have some time, thanks :) | 16:57 |
| *** uzumaki has quit IRC | 16:57 | |
| airship-irc-bot | <sidney.shiba> @kk6740 I scanned the document and need some concrete example to consolidate the design in my head. Was "airshipctl baremetal remotedirect" command re-factored with the Executor design or is there something else you suggest I look into to better grasp the this design pattern? | 17:10 |
| airship-irc-bot | <kk6740> one second | 17:14 |
| airship-irc-bot | <kk6740> there are links to other executors, with links in code that you can use | 17:15 |
| airship-irc-bot | <kk6740> remote direct is used as command line right now, there is WIP to move it to executors | 17:16 |
| airship-irc-bot | <kk6740> but its not complete yet | 17:16 |
| airship-irc-bot | <kk6740> others are avaiable though | 17:16 |
| airship-irc-bot | <kk6740> isogen for example https://github.com/airshipit/airshipctl/blob/master/pkg/bootstrap/isogen/executor.go | 17:17 |
| airship-irc-bot | <sidney.shiba> so, if I "debug" the command "airshipctl phase run bootstrap", I should be able to see how it works and be able to refactor "bootstrap ephemeral" command? | 17:20 |
| airship-irc-bot | <kk6740> `airshipctl phase run` command in general | 17:20 |
| airship-irc-bot | <kk6740> argument `bootstrap` is just a name of the phase that is defined by user, like explained in the document i’ve shared | 17:21 |
| airship-irc-bot | <sidney.shiba> Any other examples of "_airshipctl phase run_ *bootstrap*" examples that I can draw from? "*bootstrap*" is one of them. Can you provide a list of implemented _run_ commands? | 17:23 |
| airship-irc-bot | <kk6740> > argument `bootstrap` is just a name of the phase that is defined by user we don’t implement bootstrap command, it is an argument to `run` command | 17:25 |
| *** GoldenBear has joined #airshipit | 17:25 | |
| airship-irc-bot | <kk6740> and its up for user to define what he is running, and the name of the phases, if u go to here https://github.com/airshipit/airshipctl/blob/master/manifests/phases/phases.yaml | 17:25 |
| airship-irc-bot | <sidney.shiba> I understand `bootstrap`is just an argument but reverse engineering will help me better understand the documentation. | 17:26 |
| airship-irc-bot | <kk6740> you will see list of *user defined* phases | 17:26 |
| airship-irc-bot | <kk6740> i think i didn’t understand this question :slightly_smiling_face:, > Any other examples of “_airshipctl phase run_ *bootstrap*” examples that I can draw from? “*bootstrap*” is one of them. Can you provide a list of implemented _run_ commands? | 17:27 |
| airship-irc-bot | <kk6740> I am open for discussion, we can hop on the bridge and discuss it to speed things up if needed | 17:28 |
| airship-irc-bot | <sidney.shiba> ok, found what I was looking for when analyzing the phases.yaml file. | 17:29 |
| airship-irc-bot | <kk6740> so essentially phases directory can u give you concrete examples with executors and phases put together | 17:30 |
| airship-irc-bot | <sidney.shiba> let me start from there and if needed will setup a call with you. thanks. | 17:31 |
| airship-irc-bot | <kk6740> :+1: | 17:31 |
| airship-irc-bot | <kk6740> just dont hesitate to ask :slightly_smiling_face: | 17:31 |
| *** StaceyF has quit IRC | 17:38 | |
| *** roman_g has quit IRC | 17:52 | |
| airship-irc-bot | <sidney.shiba> :+1: | 19:10 |
| *** dwalt has quit IRC | 19:22 | |
| airship-irc-bot | <sidney.shiba> @kk6740 where I can find an example of $HOME/.airship/config file. Mine does not have "MetadataPath" and is exiting "airshipctl phase run bootstrap" with error because of it. | 19:52 |
| airship-irc-bot | <kk6740> one second | 19:56 |
| airship-irc-bot | <sidney.shiba> I think I found the way. Testing now. | 19:56 |
| airship-irc-bot | <sidney.shiba> `targetPath: /home/esidshi/projects/phase2/airshipctl` `metadataPath: /home/esidshi/projects/phase2/airshipctl/manifests/metadata.yaml` | 19:57 |
| airship-irc-bot | <kk6740> that’s a bad idea :slightly_smiling_face: | 19:57 |
| airship-irc-bot | <kk6740> let me show u | 19:57 |
| airship-irc-bot | <sidney.shiba> ok | 19:57 |
| airship-irc-bot | <kk6740> i do realize that metadata is missing piece in that doc,. | 19:58 |
| airship-irc-bot | <kk6740> it should be relative to targetpath | 19:58 |
| airship-irc-bot | <kk6740> so in your case it looks like it should be: ```targetPath: /home/esidshi/projects/phase2/airshipctl metadataPath: airsshipctl/manifests/metadata.yaml``` | 19:59 |
| airship-irc-bot | <sidney.shiba> ok, changing it | 19:59 |
| airship-irc-bot | <kk6740> here is example in airshipctl deployments: https://github.com/airshipit/airshipctl/blob/master/tools/deployment/templates/airshipconfig_template#L31-L32 and here is what are those variables: https://github.com/airshipit/airshipctl/blob/master/tools/deployment/22_test_configs.sh#L40 https://github.com/airshipit/airshipctl/blob/master/tools/deployment/22_test_configs.sh#L33 | 20:03 |
| airship-irc-bot | <sidney.shiba> metadataPath should be `metadataPath: manifests/metadata.yaml` | 20:03 |
| airship-irc-bot | <sidney.shiba> or `targetPath: /home/esidshi/projects/phase2` `metadataPath: airshipctl/manifests/metadata.yaml` | 20:05 |
| airship-irc-bot | <kk6740> yes | 20:05 |
| airship-irc-bot | <kk6740> the last one is correct | 20:05 |
| airship-irc-bot | <kk6740> sorry for my mistake | 20:05 |
| airship-irc-bot | <kk6740> so basically targetPath + metadataPath should give u path to metadata file | 20:05 |
| airship-irc-bot | <sidney.shiba> reverse engineering it so saw the issue. | 20:05 |
| airship-irc-bot | <sidney.shiba> but phases are coded in the yaml file as `airshipctl/manifests/phases` so `targetPath` must not include `airshipctl`directory | 20:07 |
| airship-irc-bot | <kk6740> yes, targetPath is a place where all repositories in manifest are cloned | 20:08 |
| airship-irc-bot | <kk6740> they are cloned in `targetPath + <repo name>` | 20:08 |
| airship-irc-bot | <kk6740> so `airshipctl` part should not be in `targetPath` | 20:08 |
| airship-irc-bot | <sidney.shiba> What is the `inventory.Path` used for? It is currently equals to `targetPath`. Is this supposed to be that way? | 20:13 |
| airship-irc-bot | <kk6740> inventory path is not used yet | 20:13 |
| airship-irc-bot | <kk6740> that is more a placeholder | 20:13 |
| airship-irc-bot | <kk6740> so u can ignore that | 20:13 |
| airship-irc-bot | <sidney.shiba> ok | 20:13 |
| airship-irc-bot | <mattmceuen> Hey @uzumaki - yep, I will take a look today! | 20:29 |
| airship-irc-bot | <sidney.shiba> @kk6740 while reverse engineering `airshipctl phase run bootstrap`, it is exiting with error in `pkg/bootstrap/isogen/executor.go/NewExecutor()` with `cfg.BundleFactory()` returning the error `loading generator plugins: accumulateFile "accumulating resources from 'hostgenerator': '/home/esidshi/projects/phase2/airshipctl/manifests/site/test-site/ephemeral/bootstrap/hostgenerator' must resolve to a file", accumulateDirector: | 21:06 |
| airship-irc-bot | "recursed accumulation of path '/home/esidshi/projects/phase2/airshipctl/manifests/site/test-site/ephemeral/bootstrap/hostgenerator': expected file with Go object code at: /home/esidshi/.airship/kustomize-plugins/airshipit.org/v1alpha1/replacementtransformer/ReplacementTransformer.so"`. What else do I need to configure or setup to get it moving forward? | 21:06 |
| airship-irc-bot | <kk6740> i think that is kustomize fails to render | 21:08 |
| airship-irc-bot | <kk6740> can u try to do kustomize build <path to document entrypoint in bootstrapphase> ? | 21:09 |
| airship-irc-bot | <sidney.shiba> yes, this is a kustomize error. I rebased my local repo late this morning. What am I supposed to do? | 21:43 |
| airship-irc-bot | <sidney.shiba> `esidshi@Airship2:~/projects/phase2/airshipctl$ pwd` `/home/esidshi/projects/phase2/airshipctl` `esidshi@Airship2:~/projects/phase2/airshipctl$ kustomize build manifests/site/test-site/ephemeral/bootstrap` `Error: loading generator plugins: accumulateFile "accumulating resources from 'hostgenerator': '/home/esidshi/projects/phase2/airshipctl/manifests/site/test-site/ephemeral/bootstrap/hostgenerator' must resolve to a file", | 21:44 |
| airship-irc-bot | accumulateDirector: "recursed accumulation of path '/home/esidshi/projects/phase2/airshipctl/manifests/site/test-site/ephemeral/bootstrap/hostgenerator': external plugins disabled; unable to load external plugin 'ReplacementTransformer'"` | 21:44 |
| airship-irc-bot | <kk6740> first i would analyze how ur manifest differs from master, because this should work on master | 21:45 |
| airship-irc-bot | <kk6740> compare changes and find a breaking one | 21:45 |
| airship-irc-bot | <sidney.shiba> I cloned the master today and this folder was not changed at all by the patchset I merged with (`git-review -d 737864`) so I guess it should be working. Anyway, will investigate then. | 21:48 |
| airship-irc-bot | <kk6740> can u try to recompile airshipctl binary from the current master? | 21:51 |
| airship-irc-bot | <kk6740> @mattmceuen can help a bit here i think, he has more details on how Transformer works, and where it looks for airshipctl binary | 21:51 |
| airship-irc-bot | <sidney.shiba> I also did "make build" this morning. | 21:51 |
| airship-irc-bot | <sidney.shiba> And error is from kustomize so rebuilding airshipctl binary wouldn't help. | 21:52 |
| airship-irc-bot | <kk6740> kustomize uses airshipctl binary as plugin | 21:53 |
| airship-irc-bot | <kk6740> but i think i know what’s the prbolem | 21:53 |
| airship-irc-bot | <kk6740> when doing kustomize build | 21:53 |
| airship-irc-bot | <kk6740> i think u need to pass flag to enable alpha plugins | 21:53 |
| airship-irc-bot | <sidney.shiba> what are the flags to use? are they "kustomize" flags or "airshipctl"? | 21:54 |
| airship-irc-bot | <kk6740> --enable_alpha_plugins | 21:54 |
| airship-irc-bot | <kk6740> to kustomzie | 21:55 |
| airship-irc-bot | <sirajudeen.yasin> or run ./tools/document/build_kustomize_plugin.sh | 21:55 |
| airship-irc-bot | <kk6740> thank you @sirajudeen.yasin | 21:55 |
| airship-irc-bot | <sidney.shiba> executed script shell as suggested then `kustomize build --enable_alpha_plugins` and got following error: `esidshi@Airship2:~/projects/phase2/airshipctl$ kustomize build --enable_alpha_plugins` `2020/10/13 17:06:05 unable to find plugin root - tried: (''; homed in $KUSTOMIZE_PLUGIN_HOME), ('kustomize/plugin'; homed in $XDG_CONFIG_HOME), ('/home/esidshi/.config/kustomize/plugin'; homed in default value of $XDG_CONFIG_HOME), | 22:07 |
| airship-irc-bot | ('/home/esidshi/kustomize/plugin'; homed in home directory)` | 22:07 |
| airship-irc-bot | <sidney.shiba> This is the stdout from the script: `esidshi@Airship2:~/projects/phase2/airshipctl$ ./tools/document/build_kustomize_plugin.sh` `The airshipctl kustomize plugin has been installed.` `Run kustomize with:` `KUSTOMIZE_PLUGIN_HOME=/home/esidshi/.airship/kustomize-plugins $GOPATH/bin/kustomize build --enable_alpha_plugins ...` | 22:08 |
| airship-irc-bot | <kk6740> try build now | 22:09 |
| airship-irc-bot | <kk6740> after the script | 22:09 |
| airship-irc-bot | <sidney.shiba> I did. | 22:09 |
| airship-irc-bot | <sidney.shiba> I just reported backward. | 22:09 |
| airship-irc-bot | <kk6740> did u point it to the correct directory `kustomize build --enable_alpha_plugins <documentRoot>` | 22:10 |
| airship-irc-bot | <sidney.shiba> was missing the env var `KUSTOMIZE_PLUGIN_HOME` | 22:11 |
| *** GoldenBear has quit IRC | 23:03 | |
| *** GoldenBear has joined #airshipit | 23:04 | |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!