*** jwcroppe has joined #openstack-powervm | 00:28 | |
*** thorst has joined #openstack-powervm | 00:31 | |
*** thorst has quit IRC | 00:36 | |
*** thorst has joined #openstack-powervm | 00:41 | |
*** seroyer has joined #openstack-powervm | 00:54 | |
*** thorst has quit IRC | 01:01 | |
*** smatzek_ has joined #openstack-powervm | 02:09 | |
*** smatzek_ has quit IRC | 02:09 | |
*** smatzek_ has joined #openstack-powervm | 02:10 | |
*** smatzek_ has quit IRC | 02:22 | |
*** seroyer has quit IRC | 02:41 | |
*** esberglu has joined #openstack-powervm | 02:43 | |
*** esberglu has quit IRC | 02:48 | |
*** thorst has joined #openstack-powervm | 03:50 | |
*** thorst has quit IRC | 03:50 | |
*** thorst has joined #openstack-powervm | 04:32 | |
*** thorst has quit IRC | 04:32 | |
*** esberglu has joined #openstack-powervm | 04:32 | |
*** esberglu has quit IRC | 04:36 | |
*** thorst has joined #openstack-powervm | 05:03 | |
*** thorst has quit IRC | 05:16 | |
*** k0da has joined #openstack-powervm | 05:34 | |
*** k0da has quit IRC | 05:54 | |
*** esberglu has joined #openstack-powervm | 06:21 | |
*** esberglu has quit IRC | 06:26 | |
*** edmondsw has joined #openstack-powervm | 06:32 | |
*** edmondsw has quit IRC | 06:56 | |
*** edmondsw has joined #openstack-powervm | 07:24 | |
*** edmondsw has quit IRC | 07:29 | |
*** edmondsw has joined #openstack-powervm | 07:29 | |
*** edmondsw has quit IRC | 07:34 | |
*** esberglu has joined #openstack-powervm | 08:10 | |
*** esberglu has quit IRC | 08:15 | |
*** k0da has joined #openstack-powervm | 08:41 | |
*** thorst has joined #openstack-powervm | 09:13 | |
*** thorst has quit IRC | 09:18 | |
*** BorD__ has quit IRC | 09:22 | |
*** BorD__ has joined #openstack-powervm | 09:24 | |
*** esberglu has joined #openstack-powervm | 09:59 | |
*** esberglu has quit IRC | 10:03 | |
*** k0da has quit IRC | 10:36 | |
*** thorst has joined #openstack-powervm | 11:14 | |
*** thorst has quit IRC | 11:19 | |
*** edmondsw has joined #openstack-powervm | 11:20 | |
*** edmondsw has quit IRC | 11:25 | |
*** k0da has joined #openstack-powervm | 12:12 | |
*** smatzek_ has joined #openstack-powervm | 12:20 | |
*** smatzek_ has quit IRC | 12:21 | |
*** smatzek_ has joined #openstack-powervm | 12:21 | |
*** thorst has joined #openstack-powervm | 12:45 | |
*** jwcroppe has quit IRC | 13:08 | |
*** seroyer has joined #openstack-powervm | 13:08 | |
*** jwcroppe has joined #openstack-powervm | 13:23 | |
*** esberglu has joined #openstack-powervm | 13:24 | |
*** jpasqualetto has joined #openstack-powervm | 13:24 | |
esberglu | #startmeeting | 13:30 |
---|---|---|
openstack | esberglu: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee' | 13:30 |
esberglu | #startmeeting powervm_ci_meeting | 13:30 |
openstack | Meeting started Thu Mar 2 13:30:21 2017 UTC and is due to finish in 60 minutes. The chair is esberglu. Information about MeetBot at http://wiki.debian.org/MeetBot. | 13:30 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 13:30 |
openstack | The meeting name has been set to 'powervm_ci_meeting' | 13:30 |
thorst | o/ | 13:31 |
esberglu | #topic OOT CI | 13:33 |
esberglu | Out of tree CI is still looking good | 13:33 |
esberglu | All of the compute nodes are back online, neutron and ceilometer are enabled on the silent pipeline again | 13:33 |
esberglu | I have patches out for a few things | 13:35 |
esberglu | One to only enable CI runs on the branches we want | 13:35 |
esberglu | And one to use the pvc-images server | 13:36 |
esberglu | 4935 and 4923 | 13:36 |
efried | o/ | 13:36 |
efried | You got that SSP sorted? | 13:36 |
esberglu | yeah | 13:36 |
efried | cool | 13:36 |
esberglu | #topic IT CI | 13:38 |
esberglu | In-tree CI is also looking good | 13:38 |
esberglu | Not much action here until we start getting changes merged | 13:38 |
esberglu | I also have a change up | 13:39 |
esberglu | 4918 | 13:39 |
esberglu | Which lets us add additional tests to the whitelist. I want to deploy with that on staging today | 13:39 |
efried | [I +1ed 4935 and 4923 - would like thorst or adreznec to approve.] | 13:40 |
esberglu | And continue work I started determining which tests we can add to the IT whitelist for some of our later changesets | 13:40 |
esberglu | Thanks | 13:41 |
efried | [ditto 4918] | 13:41 |
efried | Why are we patching in the power_opts stuff? | 13:41 |
efried | Is that just needed for cherry-pick compatibility purposes? | 13:41 |
thorst | I thought to help with stability (or a thought that it might help with stability) | 13:42 |
efried | Where did we land on the idea of including that in 1.0.0.4.1? | 13:42 |
esberglu | Yeah what thorst said | 13:43 |
thorst | we didn't...yet...because of the whole hubub getting 1.0.0.4.1 actually working | 13:43 |
efried | I just don't like the idea of piling on some nontrivial subset of the (.5 - .4) delta. | 13:45 |
efried | It may make the CI look better to the outside world, but it reduces my confidence in the sanity of what we're actually testing. | 13:45 |
efried | Do we have any actual evidence or other reason to believe these patches will add stability, or is it just a hunch? | 13:46 |
thorst | adreznec: did the release go out? Or can we add this bit in? | 13:47 |
esberglu | Release went out I believe | 13:47 |
esberglu | https://pypi.python.org/pypi/pypowervm/1.0.0.4.1 | 13:47 |
efried | Have we proposed the global reqs update to pike yet? | 13:48 |
efried | or was tonyb going to do that? | 13:48 |
*** tjakobs_ has joined #openstack-powervm | 13:49 | |
esberglu | Not sure | 13:51 |
esberglu | Doesn't look like it | 13:51 |
efried | I'll do it. | 13:53 |
esberglu | Cool | 13:53 |
efried | #action efried to propose requirements bump | 13:53 |
esberglu | So do we want to remove the patches we are currently piling onto 1.0.0.4 for in tree? | 13:53 |
esberglu | For the reason efried detailed above? | 13:54 |
efried | Update: requirements project is already done: https://review.openstack.org/#/c/439790/ | 13:55 |
*** tjakobs_ has quit IRC | 13:56 | |
efried | esberglu I'd say just kill 4931 and I'll be satisfied. | 13:58 |
efried | Those are straight up .5 changes. | 13:59 |
efried | They're not going to lend stability or fix any bugs. | 13:59 |
efried | And we're already getting burn-in on them with OOT. | 13:59 |
esberglu | Okay that's good with me | 13:59 |
esberglu | Anything have final topics? | 14:00 |
efried | We should try to keep in-tree as close as possible to the version in global requirements. | 14:00 |
esberglu | Yes I agree | 14:00 |
*** tblakes has joined #openstack-powervm | 14:00 | |
esberglu | Last thing I had was OSA CI. Still working on rebasing the playbooks for that. Nothing else to report | 14:01 |
efried | adreznec note -1 on 4932 | 14:08 |
efried | (You can mark that down as me disagreeing with thorst) | 14:08 |
adreznec | Oops, for some reason my calendar invite for this didn't pop up. What's broken on 4932? | 14:08 |
adreznec | The g-r bump already went out btw | 14:08 |
adreznec | They pushed it in last night and bumped pbr to >2 after that | 14:10 |
adreznec | which broke a bunch of other projects thanks to that hacking requirement | 14:10 |
adreznec | We should be good to go on that front with 4932 and the correspoding g-r bumps on the powervm projects | 14:10 |
efried | adreznec Take a look at my comments. If they're all bogus, feel free to merge. | 14:11 |
adreznec | Will do | 14:11 |
efried | But if we're aligning with g-r, I don't see a reason for our pbr req to be downrev. | 14:12 |
*** mdrabe has joined #openstack-powervm | 14:12 | |
efried | And the lxml thing bugs me. I think we should be able to keep our floor higher. | 14:12 |
adreznec | Yeah, that wasn't merged yet when I proposed that | 14:12 |
adreznec | and hmm ok, I'll have to look at the other comment | 14:12 |
efried | Any other topics for the CI meeting? | 14:13 |
adreznec | Doesn't sound like it | 14:14 |
efried | esberglu call it? | 14:22 |
esberglu | #endmeeting | 14:22 |
openstack | Meeting ended Thu Mar 2 14:22:44 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 14:22 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/powervm_ci_meeting/2017/powervm_ci_meeting.2017-03-02-13.30.html | 14:22 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/powervm_ci_meeting/2017/powervm_ci_meeting.2017-03-02-13.30.txt | 14:22 |
openstack | Log: http://eavesdrop.openstack.org/meetings/powervm_ci_meeting/2017/powervm_ci_meeting.2017-03-02-13.30.log.html | 14:22 |
*** edmondsw has joined #openstack-powervm | 14:32 | |
efried | esberglu Use this one to test the branch selection once that's active: https://review.openstack.org/#/c/430398/ | 14:36 |
efried | Expect that guy to run (and pass) OOT, but not run in-tree. | 14:36 |
*** tblakes has quit IRC | 14:39 | |
*** esberglu has quit IRC | 14:43 | |
*** nbante has joined #openstack-powervm | 14:47 | |
*** tblakes has joined #openstack-powervm | 14:57 | |
*** esberglu has joined #openstack-powervm | 15:01 | |
*** dwayne has joined #openstack-powervm | 15:03 | |
*** tjakobs_ has joined #openstack-powervm | 15:37 | |
efried | thorst You want those to be warnings or info? | 16:17 |
efried | https://review.openstack.org/#/c/438729/1/nova/virt/powervm/tasks/base.py@63 | 16:17 |
thorst | efried: looking...I just know they were different | 16:28 |
thorst | info seems fine to me | 16:28 |
thorst | they're part of an exception path, but they're info about the exception path. | 16:29 |
*** mdrabe has quit IRC | 16:31 | |
*** mdrabe has joined #openstack-powervm | 16:36 | |
*** seroyer has quit IRC | 16:38 | |
*** seroyer has joined #openstack-powervm | 16:51 | |
*** apearson has joined #openstack-powervm | 16:58 | |
thorst | esberglu: https://t.co/V9HiKuw2Zl | 17:14 |
*** jpasqualetto has quit IRC | 17:23 | |
*** jpasqualetto has joined #openstack-powervm | 17:24 | |
thorst | adreznec: around? | 17:24 |
adreznec | thorst: sup | 17:24 |
thorst | you said earlier that vxlan tunnels can be multicast or p2p...do you have docs on that? | 17:25 |
thorst | google is not finding it after 5 min of searching...figured I'd ask as I'm probably using the wrong wording :-) | 17:25 |
adreznec | which part are you looking for docs on? unicast or multicast? | 17:27 |
thorst | I want to try unicast. | 17:27 |
thorst | we're having issues with multicast | 17:27 |
adreznec | Here's some stuff on a multiple server unicast setup - https://lxadm.com/Unicast_VXLAN:_overlay_network_for_multiple_servers_with_dozens_of_containers | 17:28 |
adreznec | Had been looking at something else too, trying to find the bookmark | 17:29 |
adreznec | https://www.flockport.com/flockport-labs-lxc-and-vxlan/ | 17:29 |
thorst | is this just containers or openstack generic as well? | 17:29 |
adreznec | i've never used it with OpenStack, only manual setup, so not sure | 17:30 |
adreznec | You definitely don't need to be using containers with it | 17:30 |
adreznec | It's just using the kernel vxlan support | 17:30 |
adreznec | Idk how flexible the neutron config/support for handling how tunnels are set up is though | 17:31 |
thorst | ahh, I was under impression that you had done it with openstack | 17:35 |
*** jpasqualetto has quit IRC | 17:35 | |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: In-tree backports: TaskFlow base https://review.openstack.org/440726 | 17:42 |
efried | thorst https://review.openstack.org/438729 and ^^ | 17:43 |
*** jpasqualetto has joined #openstack-powervm | 17:48 | |
efried | thorst 4919 should be ready for your +2 now. | 17:50 |
thorst | efried: first two looked good | 18:06 |
thorst | looking at 4919 | 18:07 |
*** apearson has quit IRC | 18:24 | |
*** nbante has quit IRC | 18:25 | |
*** edmondsw has quit IRC | 18:29 | |
*** edmondsw has joined #openstack-powervm | 18:32 | |
*** edmondsw has quit IRC | 18:36 | |
*** thorst has quit IRC | 19:09 | |
*** thorst has joined #openstack-powervm | 19:10 | |
openstackgerrit | Merged openstack/nova-powervm master: In-tree backports: TaskFlow base https://review.openstack.org/440726 | 19:14 |
*** edmondsw has joined #openstack-powervm | 19:14 | |
*** thorst has quit IRC | 19:14 | |
*** edmondsw has quit IRC | 19:47 | |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Move _get_vg_uuid to pypowervm's find_vg https://review.openstack.org/440784 | 19:49 |
*** edmondsw has joined #openstack-powervm | 19:50 | |
*** thorst has joined #openstack-powervm | 20:35 | |
thorst | efried: good with me pushing up 4919? | 20:40 |
thorst | I just +2' | 20:40 |
efried | thorst Yup, make it happen. | 20:40 |
thorst | cool...on it | 20:40 |
thorst | ymadhavi will have a nice surprise tomorrow morning when she see's its merged. | 20:41 |
tonyb | efried: I offered to do it if y'all wanted to but I ddin't get a frim "go ahead" so I didn't | 20:48 |
efried | tonyb Somebody did. | 20:49 |
tonyb | efried: okay | 20:49 |
efried | tonyb https://review.openstack.org/#/c/439790/ Right? | 20:49 |
tonyb | efried: Oh yeah that thing. I thought you were asking about auto-syncing g-r into the nova-powervm repo | 20:50 |
tonyb | efried: like nova et.al. do | 20:50 |
efried | tonyb It would be really neat if we could do that (for nova-powervm and for pypowervm also). | 20:50 |
efried | We discussed it briefly. A question of putting the resources into it. | 20:51 |
tonyb | efried: pypowervm is on GH so we can't do it there | 20:51 |
efried | Well "we" can ;-) | 20:51 |
efried | Somehow. | 20:51 |
tonyb | efried: but I can write a script that will propose a PR for y'all but it wont be the same | 20:51 |
tonyb | efried: I'd be happy do the scripting if y'all have the permissions | 20:52 |
efried | tonyb No, for pypowervm we would probably write the script to propose to our internal gerrit. | 20:52 |
efried | or jenkins job, more likely. | 20:52 |
tonyb | efried: Oh I can do that assuming your internal gerrit has .gitreview stup right | 20:53 |
efried | tonyb Yeah; or it can be thus finagled. | 20:53 |
tonyb | efried: so I'll do the nova-powervm things and when you're ready I can help you with the pypowervm ones too but y'all will need to work out how you merge them | 20:54 |
tonyb | efried: sound reasonable? | 20:54 |
efried | adreznec esberglu Have either of you already made inroads on this front (automatic proposal of change sets to bump pypowervm requirements in line with openstack global reqs)? | 20:54 |
efried | tonyb Absolutely! Thank you for volunteering! | 20:55 |
tonyb | efried: It's what I do | 20:55 |
efried | Internally, I'm sure we'll be happy to review & merge them manually for pypowervm. | 20:55 |
efried | At least initially. We'll see how much volume it generates. | 20:55 |
tonyb | efried: Just run it (manually) once a week the load will be minimal | 20:58 |
openstackgerrit | Tony Breeds proposed openstack/nova-powervm master: Manual sync with openstack/requirements repo https://review.openstack.org/440811 | 21:02 |
tonyb | ^^ step one, just running tests on steps 2 and 3 | 21:06 |
efried | tonyb Thanks, I added our core team as reviewers. | 21:06 |
tonyb | efried: cool | 21:07 |
*** smatzek_ has quit IRC | 21:10 | |
*** kriskend has joined #openstack-powervm | 21:10 | |
*** jpasqualetto has quit IRC | 21:11 | |
efried | tonyb Help me understand this a little bit - does this review come from some kind of bot that's controlled outside of our purview? | 21:12 |
efried | Can we customize it a little bit - e.g. have exclusions/exceptions? | 21:12 |
tonyb | efried: Yes | 21:12 |
tonyb | efried: everytime there is a change in openstack/requirements:global-requirements.txt that affect you you'll see a bot generated chnage very similar to the one I just created | 21:13 |
tonyb | efried: let me find you some examples | 21:13 |
tonyb | efried: https://review.openstack.org/#/q/owner%3Aproposal-bot%20project%3Aopenstack/nova%20topic%3Aopenstack/requirements | 21:14 |
tonyb | efried: that's the nova ones | 21:14 |
efried | The thing is, because of the way our development stream coordinates between nova-powervm and pypowervm, we (at least) would need to exclude pypowervm from any bot updates. | 21:14 |
tonyb | efried: It's an all or nothing thing | 21:14 |
tonyb | efried: *you* will only update pypowervm in openstack/requirements:global-requirements.txt when you're ready | 21:15 |
tonyb | so it wont chnage unless you do it over there | 21:15 |
tonyb | efried: so when y'all release a new pypowervm it will within 24hours get added to upper-constratints.txt and you can start using it in the gate | 21:16 |
tonyb | efried: once you're happy that it works if needed you can do the raise the minimum in openstack/requirements:global-requirements.txt if needed | 21:16 |
tonyb | efried: It'll be good practise for when the powervm driver is merged into nova as you'll have *exactly* the same workflow there | 21:18 |
*** kjw3 has joined #openstack-powervm | 21:19 | |
*** tlian has joined #openstack-powervm | 21:20 | |
efried | tonyb Okay, I still don't fully grok who owns the bot or how it's run - but presumably human interaction is still required before the auto-proposed changes actually merge. | 21:25 |
tonyb | efried: requirement/Infra own the bit | 21:26 |
efried | tonyb And presumably it's a change set like any other, so if we need to go in and tweak something before we merge it, we can still do that. | 21:26 |
efried | tonyb Okay, then ^^ is especially important. | 21:26 |
tonyb | efried: Yeah core reviewers still need to merge the changes | 21:26 |
tonyb | efried: You can change it *BUT* the bot is dumb so if it suggest $thing and you say no, it'll just re-propose the same thing next time | 21:27 |
tonyb | efried: when the bot isn't doing what you want the *souce* data is openstack/requirements:global-requirements.txt | 21:27 |
efried | Oh. Next time that line is touched, or next time it runs? | 21:27 |
tonyb | efried: next time openstack/requirements:global-requirements.txt is touch the bot will re-run | 21:27 |
efried | Yeah, that'd be fine. As long as it doesn't just keep generating reviews for changing that one line over and over. | 21:28 |
efried | Cause we'll routinely be removing the constraints from pypowervm in the master branch for the forseeable future. | 21:28 |
*** tlian has quit IRC | 21:29 | |
tonyb | efried: that last line worries me | 21:29 |
tonyb | if you're rapidly changing things in *requirements.txt then a) you don't wnat auto sync and b) you're not really ready for integration in nova | 21:30 |
*** edmondsw has quit IRC | 21:31 | |
thorst | sorry...I've been catching up here. | 21:32 |
efried | tonyb Well, it's essentially because we don't support nova-powervm (out-of-tree compute driver) for a given release until that release is cut; so we're developing pypowervm in parallel. | 21:32 |
thorst | the stuff in nova is not changing rapidly at all... | 21:32 |
efried | The in-tree driver is going to lag for a while, and will always be against an official release of pypowervm. | 21:32 |
*** jpasqualetto has joined #openstack-powervm | 21:33 | |
thorst | yeah, I want to revisit that for the out of tree though. | 21:33 |
thorst | I think adreznec, efried and I should chat...I'm not sure oot needs that approach. | 21:34 |
*** edmondsw has joined #openstack-powervm | 21:35 | |
efried | Also tonyb FYI, the goal is for our g-r pypowervm version to change once per release. Unless something extreme happens, like this pbr thing. | 21:35 |
tonyb | efried: okay, that's fine but you're free to chnage it on *master* anytime up the RC1 so you don't need to stress to much about the 1 pypowervm per cycle | 21:36 |
thorst | that helps. | 21:38 |
efried | tonyb Except we didn't really want to be cutting a new pypowervm that frequently. But realistically, we're only talking like once a month. So if that kind of velocity is acceptable in the master requirements project... | 21:38 |
efried | Yeah, what thorst said. | 21:38 |
thorst | lol | 21:38 |
tonyb | efried: Yeah until RC1 once a month is fine | 21:38 |
tonyb | efried: You only need to update openstack/requirements:global-requirements.txt when you *require* a new feature from ppypowervm. Not just 'cause it was released | 21:39 |
efried | tonyb Understood. It's just... that'd be the only reason we would cut a new release. | 21:40 |
thorst | efried: RC1 is Aug 7 | 21:40 |
efried | ...other than normal release boundaries. | 21:40 |
tonyb | efried: okay that's somewhat strange but it's up to y'all | 21:40 |
efried | tonyb This may be TMI, but we try to hide as much PowerVM-specific esoterica in pypowervm so the nova cores don't have to look at it and try to grok it when looking at our community code. | 21:41 |
thorst | meh, that's not TMI. :-) | 21:42 |
efried | Okay, but this might be... | 21:42 |
tonyb | efried: Yeah that's fine. You'll just find it takes longer for things to land if you can't work with multiple releases of pypowervm | 21:43 |
* thorst drum roll | 21:43 | |
efried | So when we need to support a new feature, code goes into multiple parts of the stack, sometimes as low as the Power firmware, and has to trickle up until it eventually gets into the community code. | 21:43 |
efried | So if we were to skip pypowervm in that chain, there would be some fairly incomprehensible stuff going into nova(-powervm) | 21:43 |
tonyb | as you'll tie you nova features/bugfixes to the pypowervm cycle which you've just said will be 1/month so you'll only have say 5 windows to merge code into nova per cycle | 21:44 |
efried | That should be more than enough. | 21:44 |
tonyb | as opposed to relgualr small increments | 21:44 |
efried | It's better than having to lag a whole release or two. | 21:44 |
tonyb | okay if you're cool with that | 21:44 |
efried | We are if y'all are. | 21:45 |
tonyb | I guess if it's a problem once your integrated you can address it internally and alter the process if needed | 21:45 |
* tonyb needs to take kids to school | 21:46 | |
efried | Thanks for all the help today tonyb | 21:46 |
tonyb | efried: np | 21:46 |
openstackgerrit | Merged openstack/nova-powervm master: In-tree backports: Redundant args https://review.openstack.org/437016 | 22:00 |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Manual sync with openstack/requirements repo https://review.openstack.org/440811 | 22:01 |
efried | thorst adreznec esberglu ^^ Manual edit to remove pypowervm version spec. Do we want to merge this? | 22:03 |
efried | ...assuming it passes our CI | 22:03 |
adreznec | efried: It should, I pushed up an almost identical change yesterday... and forgot to add reviewers, of course | 22:06 |
* adreznec sighs | 22:06 | |
efried | okay. | 22:06 |
adreznec | I'll abandon mine though | 22:06 |
adreznec | Tony's has the updated pbr>2 req in it | 22:07 |
*** thorst has quit IRC | 22:08 | |
efried | If I understood correctly, we'll have to edit every time to do this. Until we get set up for a cadence with real pypowervm sub-releases in cycle. | 22:08 |
adreznec | ]Yeah | 22:08 |
adreznec | *Yeah | 22:08 |
efried | Which needs to be on the agenda for an internal discussion soon. | 22:08 |
adreznec | thorst and I had been pushing them in the past | 22:08 |
adreznec | periodically | 22:08 |
efried | Cause we can't have it take 24 hours of talkytalk every time we need to do that. | 22:08 |
adreznec | well most of the talk this time was because we'd been neglecting pypowervm | 22:09 |
efried | as far as global requirements? | 22:09 |
adreznec | not really anything to do with the *-powervm project requirements | 22:10 |
adreznec | Right | 22:10 |
adreznec | It's not an openstack project, so nobody had been keeping it in sync with g-r | 22:10 |
adreznec | Which didn't matter until we put it in requirements... | 22:10 |
adreznec | And now all of a sudden it matters | 22:10 |
efried | Okay, so hopefully we'll bot that, and not have so much churn next time. | 22:10 |
adreznec | Yup | 22:10 |
adreznec | Ah, one other thing from mine that bump that isn't in the one you just edited for nova-powervm was an update to our hacking requirement | 22:11 |
adreznec | Not sure why that didn't get picked up in the manual sync one... | 22:12 |
efried | could it be the blank line? | 22:13 |
adreznec | But hacking<0.12,>=0.11.0 definitely doesn't match https://github.com/openstack/requirements/blob/master/global-requirements.txt#L424 | 22:13 |
adreznec | Maybe | 22:13 |
efried | that would be... weird. | 22:13 |
openstackgerrit | Eric Fried proposed openstack/nova-powervm master: Manual sync with openstack/requirements repo https://review.openstack.org/440811 | 22:14 |
efried | adreznec edited | 22:14 |
*** thorst has joined #openstack-powervm | 22:36 | |
*** tblakes has quit IRC | 22:37 | |
*** thorst has quit IRC | 22:41 | |
*** seroyer has quit IRC | 22:44 | |
tonyb | efried: for the records here are the 3 parts of the process with appropriate Depends-Ons https://review.openstack.org/#/q/topic:nova-powervm-gr-sync | 23:00 |
*** mdrabe has quit IRC | 23:06 | |
*** kriskend_ has joined #openstack-powervm | 23:07 | |
*** dwayne has quit IRC | 23:08 | |
*** kriskend has quit IRC | 23:11 | |
*** seroyer has joined #openstack-powervm | 23:17 | |
*** thorst has joined #openstack-powervm | 23:17 | |
*** thorst has quit IRC | 23:19 | |
*** kriskend_ has quit IRC | 23:25 | |
*** seroyer has quit IRC | 23:47 | |
*** jpasqualetto has quit IRC | 23:56 | |
*** jwcroppe has quit IRC | 23:59 | |
*** jwcroppe has joined #openstack-powervm | 23:59 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!