| *** sgw has quit IRC | 00:26 | |
| *** tingjie has joined #starlingx | 01:34 | |
| *** lcastell has joined #starlingx | 01:37 | |
| *** lcastell has quit IRC | 01:41 | |
| *** ijolliffe has quit IRC | 02:50 | |
| *** zhubx has quit IRC | 03:46 | |
| *** zhubx has joined #starlingx | 03:47 | |
| *** zhubx has quit IRC | 03:57 | |
| *** zhubx has joined #starlingx | 03:58 | |
| *** gkadam has quit IRC | 06:13 | |
| *** tingjie has quit IRC | 06:44 | |
| *** Kunpeng has quit IRC | 06:52 | |
| *** tingjie has joined #starlingx | 06:58 | |
| *** tingjie has left #starlingx | 07:53 | |
| *** dbadea has joined #starlingx | 08:01 | |
| *** gkadam has joined #starlingx | 08:14 | |
| *** dbadea has quit IRC | 08:31 | |
| *** zhubx has quit IRC | 10:59 | |
| *** zhubx has joined #starlingx | 10:59 | |
| *** sgw has joined #starlingx | 11:19 | |
| *** jsun3 has quit IRC | 11:22 | |
| *** jsun3 has joined #starlingx | 11:23 | |
| *** jsun3 has quit IRC | 11:25 | |
| *** ijolliffe has joined #starlingx | 13:25 | |
| *** gkadam_ has joined #starlingx | 14:16 | |
| *** gkadam has quit IRC | 14:19 | |
| *** jsun3 has joined #starlingx | 14:32 | |
| *** gkadam__ has joined #starlingx | 15:00 | |
| *** gkadam_ has quit IRC | 15:03 | |
| slittle1 | Anyone else having problems with building f/centos76 | 15:29 |
|---|---|---|
| slittle1 | looks like stx-upstream was recently merged from master, but stx-manifest was not | 15:30 |
| slittle1 | the tripping point was python-aodhclient, which has moved from a patched src.rpm to a git | 15:32 |
| slittle1 | the git is not being populated by stx-manifest under f/centos76. | 15:33 |
| sgw | slittle1: if you have a suggested patch, please get it into gerrit, the PRC likely won't get to this until their tomorrow morning | 15:37 |
| slittle1 | it's not a patch, it's a merge | 15:38 |
| slittle1 | so it's you or me I think | 15:38 |
| slittle1 | you merged stx-upstream on March 4 | 15:39 |
| sgw | slittle1: can you take a crack at it, I am on and off line today, mostly off | 15:39 |
| slittle1 | but there wasn't a matching merge on stx-manifest | 15:39 |
| slittle1 | K, I can do it | 15:39 |
| sgw | slittle1: was not asked to do stx-manifest by Shuicheng, so it got missed I guess | 15:39 |
| sgw | thanks for doing it, I can give it a +2 when I see it. | 15:40 |
| slittle1 | just want to make sure in future, when merging,that you merge ALL gits that are on the feature branch... including manifest | 15:40 |
| sgw | slittle1: sorry, was an oversight on my part | 15:42 |
| slittle1 | was stx-manifest the only oversight? I'm wondering if I need to move merge them all ? | 15:54 |
| slittle1 | looks like it was just stx-manifest | 16:03 |
| slittle1 | https://review.openstack.org/641431 | 16:06 |
| *** ijolliffe has quit IRC | 16:26 | |
| slittle1 | merged | 16:27 |
| slittle1 | attempting to build ... | 16:27 |
| *** ijolliffe has joined #starlingx | 16:28 | |
| *** gkadam__ has quit IRC | 16:42 | |
| *** ijolliffe has quit IRC | 16:57 | |
| *** ijolliffe has joined #starlingx | 16:58 | |
| *** lcastell has joined #starlingx | 17:33 | |
| *** lcastell has quit IRC | 17:37 | |
| *** sgw has quit IRC | 19:04 | |
| dtroyer | So I am looking for a better home for the stx-devstack-base job for Zuul. It is currently in stx-fault but that is not the rigth home, it is just where I started working on devstack plugins. | 19:12 |
| dtroyer | After looking at the tangle of dependencies it seems like stx-integ might be the best choice. So far, only platform-util is actually used there but everything else seems to need that, or needs something that needs that. | 19:13 |
| dtroyer | Thoughts? Anyone? | 19:14 |
| dpenney | what are the considerations here? I'd probably say stx-config or stx-integ, as they're probably the main repos, without knowing the full implications of stx-devstack-base job | 19:20 |
| dtroyer | we define the base job one time and anything else can use it (Zuul's job namespace is global). Every other devstack plugin will need to include the repo where the base job lives | 19:28 |
| dtroyer | it is kind of a wash regarding the mechanics, I'm more curious about conceptual fit and what makes sense | 19:29 |
| dtroyer | I want to put some common initialization stuff in the same repo | 19:31 |
| dpenney | I'd lean towards stx-config, as stx-integ would be more "3rd-party" stuff. Although from your description, maybe stx-root is the correct spot for it. slittle1, what do you think? | 19:34 |
| dtroyer | ok, that is helpful, it is an improvement over stx-fault for sure, and (so far) everything except integ and update need config anyway | 19:36 |
| dtroyer | I did not consider root as it doesn't have a devstack plugin and I didn't want to add one unnecessarily | 19:37 |
| dtroyer | same with tools | 19:37 |
| dpenney | so the idea is that these is a base zuul job that can be referenced by the zuul.ini in any repo? stx-root sounds like the right spot, given that description. It wouldn't, itself, make use of the job though, so maybe that makes it easy to break? | 19:39 |
| dtroyer | right, making it be self-testing is part of the goal | 19:41 |
| dpenney | ok... so it sounds to me like stx-root is the right place logically, but stx-config may be the preferred place in practice... Just my two cents, of course | 19:43 |
| dpenney | I can ping slittle1, in case he has a differing opinion | 19:44 |
| slittle1 | I'm back | 19:45 |
| dtroyer | slittle1: do you see the scrollback or should I repeat my question? | 19:48 |
| slittle1 | I can see it all | 19:48 |
| dtroyer | kk | 19:48 |
| slittle1 | I'm not up to date on how your using devstack | 19:49 |
| slittle1 | is this validation of openstack components | 19:49 |
| slittle1 | ? | 19:49 |
| dtroyer | no, the testing of flock services and components alongside a running OpenStack. At least as much as we can do in that configuration | 19:50 |
| dtroyer | so the idea is to be able to start a minimal number of things to enable say fm-rest-api to run and be tested | 19:51 |
| dtroyer | so we don't necessarily assume the entire starlingx is present | 19:51 |
| dtroyer | which is why I am trying to enable using the smallest set of things possible for testing components | 19:52 |
| slittle1 | Have you considered a new repo? stx-test-util or something? | 19:55 |
| dtroyer | I have and that is part of the POC I am doing in stx-tis-repo now. but again, making that self-testing is a bit harder | 19:56 |
| slittle1 | seems likes a poor fit vs the intended content of stx-config. | 19:57 |
| slittle1 | I'd float it by Brent | 19:58 |
| dtroyer | which is part of why I laded on integ, as it is specifically for interfacing with the rest of the world... | 19:58 |
| *** zhubx has quit IRC | 19:59 | |
| *** zhubx007 has joined #starlingx | 19:59 | |
| slittle1 | Of the two, I'd lean toward stx-integ myself. | 19:59 |
| dtroyer | slittle1, dpenney: thanks for the thoughts, it has been helpful. | 20:00 |
| dtroyer | not to cut off anyone else who has something to add... | 20:00 |
| *** fdegir has quit IRC | 20:53 | |
| *** fdegir has joined #starlingx | 20:54 | |
| *** ijolliffe has quit IRC | 22:20 | |
| *** lcastell has joined #starlingx | 22:36 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!