| *** evrardjp has quit IRC | 04:33 | |
| *** evrardjp has joined #airshipit | 04:33 | |
| *** uzumaki has joined #airshipit | 04:45 | |
| *** lamt has joined #airshipit | 05:25 | |
| *** uzumaki has quit IRC | 13:11 | |
| *** uzumaki has joined #airshipit | 13:59 | |
| mattmceuen | Hey all, FYI that today is the last day to vote for the Open Infrastructure Superuser Awards: https://superuser.openstack.org/awards/ | 14:16 |
|---|---|---|
| mattmceuen | There is mention of Airship among the nominees, so I wanted to make sure folks were aware! | 14:16 |
| *** uzumaki has quit IRC | 15:17 | |
| airship-irc-bot | <ak3216> @mattmceuen @kk6740 wanted to follow up on the discussion from this morning's SIG YAML call. I created https://github.com/airshipit/airshipctl/issues/356 for changing the documentEntryPoint to remove the site specific reference. The suggestion was to use the phase's relative path, but wanted to make sure we were on the same page & if there's some more I can add as far as details go. Thanks! | 17:54 |
| airship-irc-bot | <kk6740> i didn’t quite follow the path forward from the call. so i think this discussion can take place here | 17:55 |
| mattmceuen | I believe the idea was to change the Phase resource's path from e.g. `manifests/site/test-site/ephemeral/bootstrap`to `ephemeral/bootstrap`, so that it could (by convention) be the same across different sites, so that you don't need to override it at the site level in general; while allowing it to still be overridden at the site level if you want to get phases from somewhere else, in unusual circumstances | 17:59 |
| mattmceuen | Somehow that would require airshipctl to know the rest of the path (`manifests/site/test-site`) for the site itself -- maybe it would make sense to add it to metadata.yaml? | 18:00 |
| airship-irc-bot | <dwalt> Could we take the site name that is supplied in the airshipctl config file? Since we are already defining it in the manifest block. If we defined the site path in `metadata.yaml` , it would work too, but we probably don't want them to have the opportunity to be different from each other | 18:06 |
| mattmceuen | Sounds reasonable to me | 18:14 |
| airship-irc-bot | <kk6740> @dwalt i don’t think we do have site name in manifests | 18:16 |
| mattmceuen | we have subPath | 18:16 |
| mattmceuen | which is better than site name, because it includes the "rest of the path" (`manifests/site`) | 18:17 |
| mattmceuen | can we say: subPath + phase doc path = full path to phase entrypoint (relative to the directory you're running airshipctl from)? | 18:17 |
| airship-irc-bot | <kk6740> i really don’t think it is a good idea to have sitename mandatory part when creating a document root | 18:17 |
| mattmceuen | or I guess rather, "targetPath + subPath + phase doc path" would be the string math I suppose | 18:19 |
| mattmceuen | Do you like the metadata.yaml option better Konstantine? That would allow you to specify the path arbitrarily (if you wanted to point outside the site definition, for example) | 18:19 |
| airship-irc-bot | <kk6740> i like the idea where u can specify that pass arbitrary. it feels very wrong, to force someone to have specific directory structure. Trying to come up with some alternatives here | 18:22 |
| airship-irc-bot | <sudeep.batra> Hey Guys, Can anyone help me with a quick fix to this error • airshipctl phase run bootstrap --debug • open /tmp/airship/manifests/metadata.yaml: no such file or directory It should try to open /tmp/airship/airshipctl.manifests/metadata.yaml instead. Thanks. | 18:27 |
| airship-irc-bot | <kk6740> heh, that’s relative to discussion we are having right now. :slightly_smiling_face: @sudeep.batra is that on gates or localy? | 18:28 |
| airship-irc-bot | <sudeep.batra> locally, I am manually running step by step to understand whats going on :slightly_smiling_face: | 18:29 |
| airship-irc-bot | <sudeep.batra> wondering if I can modify the script , so that I can proceed with next steps , would you know what needs to change ? | 18:30 |
| airship-irc-bot | <sudeep.batra> opened bug as well - https://github.com/airshipit/airshipctl/issues/357 | 18:30 |
| airship-irc-bot | <kk6740> there is a fix for that, in progress, https://review.opendev.org/#/c/752595/ but for now you can simply modify path to metadata.yaml file i think | 18:31 |
| airship-irc-bot | <kk6740> @mattmceuen @dwalt, would u be able to discuss this today a short call? | 18:38 |
| airship-irc-bot | <kk6740> later | 18:38 |
| airship-irc-bot | <rp2723> The original idea was to rely on the manifest information to define the root , as matt accurately states use target + sub paths. Is there a proposed alternative I am missing in the discussion above | 18:40 |
| mattmceuen | @kk6740 today is a bit tight, but it looks like we already have it on the agenda for tomorrow's design call; we could discuss there? | 18:44 |
| airship-irc-bot | <kk6740> yes, if we do, ofc | 18:45 |
| mattmceuen | ok cool. @rp2723: the alternative approach would be to add a new path to metadata.yaml, which would specify the path to use for phase entrypoints. The "con" of that would be that it's basically duplicating targetPath+subPath; the "pro" would be that it allows someone to specify a phase entrypoint location wherever they want, if they want to have them outside of the site definition | 18:47 |
| airship-irc-bot | <kk6740> @rp2723 i think, it maybe a little confusing what that subpath is for a user. For example we have: ```manifests: dummy_manifest: primaryRepositoryName: primary repositories: primary: checkout: branch: ${AIRSHIP_CONFIG_PRIMARY_REPO_BRANCH} force: false remoteRef: "" tag: "" url: ${AIRSHIP_CONFIG_PRIMARY_REPO_URL} metadataPath: manifests/metadata.yaml | 18:48 |
| airship-irc-bot | targetPath: ${AIRSHIP_CONFIG_MANIFEST_DIRECTORY}``` as you can see, we have `primaryRepositoryName: primary` | 18:48 |
| airship-irc-bot | <kk6740> and you know that that repository is source of your `phases` | 18:49 |
| airship-irc-bot | <kk6740> and hence it’s going to be prepended when building kustomize root | 18:49 |
| airship-irc-bot | <kk6740> and also, it seems like, what is actually inside of those entrypoints, depends on other repositories, defined in your manifests. So it seems like whoever is authoring the config, should be aware what is inside the document set, and it’s dependencies, that is why it seems reasonable to put those repos as dependencies into metadata.yaml file, and clone them to targetpath afterwards ? I think this is what we dicsussed today at the call | 18:52 |
| airship-irc-bot | bit, and @am240k said, he had impression that we are going that way | 18:52 |
| airship-irc-bot | <rp2723> I see let’s try to close and agree on a path in the design call . Should be simple to the user , if it’s not obvious then we are doing something wrong | 18:54 |
| airship-irc-bot | <sudeep.batra> Did you mean modify the export AIRSHIP_CONFIG_MANIFEST_DIRECTORY=${AIRSHIP_CONFIG_MANIFEST_DIRECTORY:-"/tmp/airship"} pls ? | 19:24 |
| airship-irc-bot | <kk6740> try something like: `export AIRSHIP_SITE_NAME="."` | 19:27 |
| airship-irc-bot | <sudeep.batra> sorry, that doesnt help me execute the 24_ script from within the airshipctl directory | 19:29 |
| airship-irc-bot | <kk6740> sorry, i may be missing variable, try : `AIRSHIP_CONFIG_PRIMARY_REPO_NAME="."` | 19:30 |
| airship-irc-bot | <kk6740> `export AIRSHIP_CONFIG_PRIMARY_REPO_NAME="."` | 19:31 |
| airship-irc-bot | <sudeep.batra> nope :slightly_smiling_face: | 19:35 |
| airship-irc-bot | <kk6740> sorry, nope? | 19:35 |
| airship-irc-bot | <sudeep.batra> that didnt work, I mean :slightly_smiling_face: | 19:36 |
| airship-irc-bot | <kk6740> yes, but are there any messages ? | 19:36 |
| airship-irc-bot | <kk6740> errors ? | 19:36 |
| airship-irc-bot | <kk6740> and did u run 22_* before that ? | 19:36 |
| airship-irc-bot | <kk6740> to regenerate config | 19:36 |
| airship-irc-bot | <sudeep.batra> oh ok run the 22 again, sorry I didnt do that | 19:37 |
| airship-irc-bot | <sudeep.batra> 1 sec | 19:37 |
| airship-irc-bot | <sudeep.batra> yes, export AIRSHIP_CONFIG_PRIMARY_REPO_NAME="." and then 22,23,24 are working, :thumbsup: ty | 19:38 |
| airship-irc-bot | <sudeep.batra> ./tools/deployment/25_deploy_ephemeral_node.sh [airshipctl] 2020/09/28 19:49:26 opendev.org/airship/airshipctl@/pkg/remote/remote_direct.go:60: Bootstrapping ephemeral host 'node02' with ID 'air-ephemeral' and BMC Address 'redfish+https://localhost:8443/redfish/v1/Systems/air-ephemeral'. redfish client encountered an error: HTTP request failed. Redfish may be temporarily unavailable. Please try again. Are we not using the | 19:53 |
| airship-irc-bot | Metal3-dev-env locally for testing ? | 19:53 |
| airship-irc-bot | <kk6740> what is metal3-dev-env ? | 19:54 |
| airship-irc-bot | <sudeep.batra> https://github.com/metal3-io/metal3-dev-env | 20:09 |
| airship-irc-bot | <kk6740> sorry, i am not very familiar with this as of now | 20:10 |
| airship-irc-bot | <sudeep.batra> I see | 20:10 |
| airship-irc-bot | <sudeep.batra> but the airshipctl scripts suppose to run and build a target cluster right ? using scripts here - https://github.com/airshipit/airshipctl/tree/master/tools/deployment | 20:12 |
| airship-irc-bot | <kk6740> yes | 20:13 |
| airship-irc-bot | <sudeep.batra> on a baremetal node or VM enabled with nested-virt | 20:13 |
| airship-irc-bot | <kk6740> yes | 20:13 |
| airship-irc-bot | <sudeep.batra> ah, ok I think we have to use 26(for using metal3) instead of 25.. | 20:15 |
| airship-irc-bot | <sudeep.batra> esudbat@airshipctl:~/airshipctl$ ./tools/deployment/26_deploy_metal3_capi_ephemeral_node.sh Error events received on channel, errors are: [Post https://10.23.25.101:6443/api/v1/namespaces: dial tcp 10.23.25.101:6443: i/o timeout] | 20:22 |
| airship-irc-bot | <kk6740> well step 25_ has failed for u as i remember | 20:22 |
| airship-irc-bot | <sudeep.batra> yeah | 20:23 |
| airship-irc-bot | <kk6740> obvsiously nothing happened and nothing was bootsteapped | 20:23 |
| airship-irc-bot | <sudeep.batra> so there is something more needed to make these scripts work on a Baremetal Node (or Nested virtualization enabled VM) | 20:24 |
Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!