| *** anyrude10_ has joined #starlingx | 03:27 | |
| anyrude10_ | [Kubernetes] Is there any support for k8s in starlingx release? and is 2019.05 officially released? | 03:28 |
|---|---|---|
| *** Samiam1999DTP has joined #starlingx | 06:54 | |
| *** Samiam1999 has quit IRC | 06:57 | |
| *** boxiang has quit IRC | 07:07 | |
| *** boxiang has joined #starlingx | 07:07 | |
| *** Samiam1999 has joined #starlingx | 07:08 | |
| *** Samiam1999DTP has quit IRC | 07:11 | |
| dtroyer | anyrude10_: master now has k8s as the basic control plane, 2019.05 is not a thing, the next release is now scheduled for August and will probably be called 2.0 | 12:30 |
| *** ijolliffe has joined #starlingx | 12:34 | |
| *** sgw has quit IRC | 15:33 | |
| *** sgw has joined #starlingx | 15:38 | |
| *** iamweswilson has joined #starlingx | 16:22 | |
| sgw | dpenney_: around? thanks for pointing out some additional issues. It also dawned on my that I need to do TIS_PATCH_VER bumps all over. | 16:35 |
| *** marosales has quit IRC | 16:41 | |
| dpenney_ | sgw: back now | 17:19 |
| sgw | dpenney_: hi there, asked a question in the revew about the usage of the _P in the sudo specfile, is it an initial password before the kickstart password is applied? | 17:20 |
| dpenney_ | did you get my second email this morning? I don't think that anaconda-ks.cfg I pointed you to at first is actually used | 17:21 |
| dpenney_ | so the password in that spec is the one set when the userid is created | 17:22 |
| sgw | dpenney_: somehow missed it, looking now | 17:22 |
| dpenney_ | I replied to my email about ten minutes after the first one :) | 17:23 |
| sgw | that makes sense since after I changed it in the ks file it still failed to be set to the new password, will try here, I also realized I left out TIS_PATCH_VER bumps | 17:23 |
| *** boxiang has quit IRC | 17:44 | |
| *** boxiang has joined #starlingx | 17:45 | |
| sgw | dpenney_: any idea about wrs-provider in NEUTRON_WRS_PROVIDER_ALIAS, I found it usages are both commented out. | 17:52 |
| sgw | dpenney_: BTW, I have a tox setup for fault, but we need to add a tools directory with the spec checking script, I will put a WIP/DO NOT MERGE patch out later and you can try it with update | 18:03 |
| dpenney_ | sgw: we can float that wrs-provider thing with our network guys, but I suspect it's old stuff that can be dropped | 18:08 |
| sgw | dpenney_: ok, I will leave it for later then | 18:15 |
| *** ijolliffe has quit IRC | 18:19 | |
| *** dklyle_ has joined #starlingx | 19:02 | |
| *** luzC has quit IRC | 19:02 | |
| *** david-lyle has quit IRC | 19:04 | |
| *** luzC has joined #starlingx | 19:08 | |
| *** iamweswilson has left #starlingx | 20:26 | |
| *** iamweswilson has joined #starlingx | 20:26 | |
| dpenney_ | sgw: got confirmation that the NEUTRON_WRS_PROVIDER_ALIAS is something missed during cleanup and could be removed | 20:59 |
| sgw | dpenney_: shell I just remove it as part of this or will the networking folks go back and clean it up? | 20:59 |
| sgw | they are slightly different | 20:59 |
| dpenney_ | I'd say feel free to remove it, or we can add a task to some cleanup story to remove it separately... as you said, it's not really related to what you're doing, just something you came across | 21:01 |
| dpenney_ | Al has a generic cleanup story we could add a task to: https://storyboard.openstack.org/#!/story/2004515 | 21:02 |
| dpenney_ | drop unused wrs-provider reference | 21:03 |
| *** sgw has quit IRC | 21:04 | |
| dpenney_ | looks like there's related code cleanup there that could be done, so I'd leave it out of your update | 21:07 |
| *** sgw has joined #starlingx | 21:09 | |
| dpenney_ | sgw: Al has added a task and notes to his openstack cleanup story https://storyboard.openstack.org/#!/story/2004764 | 21:12 |
| sgw | dpenney_: Ok thanks, have a great weekend! | 21:28 |
| *** bwensley has quit IRC | 21:31 | |
| dpenney_ | sgw: you too! | 22:13 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!