| *** zhiwei has joined #kolla | 00:56 | |
| sdake | evening folks | 01:05 |
|---|---|---|
| mandre | hi sdake | 01:05 |
| sdake | hey mandre | 01:11 |
| sdake | mandre here is my tube amp https://drive.google.com/file/d/0B8q6xDPETSkHWjdoaFFCT3RJMzUtLW1oSWlXY1lOMzVLcmJV/view | 01:12 |
| mandre | nice :) party time! | 01:16 |
| *** erkules_ has joined #kolla | 01:22 | |
| *** erkules has quit IRC | 01:25 | |
| *** fangfenghua has joined #kolla | 01:35 | |
| sdake | fangfenghua sup bro where ya been! | 01:37 |
| *** fangfenghua has quit IRC | 01:44 | |
| *** alisonholloway has joined #kolla | 02:09 | |
| *** dimsum__ has quit IRC | 02:22 | |
| *** dimsum__ has joined #kolla | 02:36 | |
| SamYaple | yo | 02:41 |
| SamYaple | hows it going | 02:41 |
| sdake | yo samyaple | 02:46 |
| sdake | any word on single nic networking? :) | 02:46 |
| SamYaple | heading into the office back in 10 | 02:47 |
| sdake | later | 02:47 |
| *** dimsum__ has quit IRC | 02:58 | |
| SamYaple | sdake: still not sure i can do single interface with linuxbridge | 03:04 |
| SamYaple | there is a reason the neutron guys dont _really_ support linuxbridge | 03:04 |
| SamYaple | it was shoved into neutron anyway | 03:04 |
| sdake | can you sync up with daneyon | 03:04 |
| sdake | he is a network rocket scientist | 03:04 |
| sdake | i'll shoot him a mail to hunt you down | 03:05 |
| SamYaple | heh probably not. we are around at polar opposite times | 03:05 |
| SamYaple | ping he pongs whe nthe other sleeps, been going on for weeks | 03:05 |
| sdake | maybe email :) | 03:05 |
| SamYaple | yea sure. i dont normally check my email so communication with me there is spotty. ill give it a go | 03:06 |
| SamYaple | the quickest way would probably just be to implement the OVS container | 03:07 |
| SamYaple | since that one is actually supported all around | 03:07 |
| SamYaple | sdake: any idea on that spec? i cant really continue until its approved. Maybe a new version with the thoughts summarized again? | 03:11 |
| sdake | samyaple you know what I did today | 03:12 |
| SamYaple | built a house | 03:12 |
| sdake | filled out 4 expense reports | 03:12 |
| sdake | all day doing that | 03:12 |
| sdake | monday for new spec | 03:12 |
| SamYaple | well maybe dont wait til the last second | 03:12 |
| SamYaple | pfff this guy | 03:12 |
| sdake | i know your blocked | 03:12 |
| SamYaple | so for extracting all the crudini/autoconfiguration bits in preperation for ansible, i see things like https://github.com/stackforge/kolla/blob/master/docker/centos/binary/keystone/start.sh#L132 | 03:13 |
| SamYaple | since most all of _all_ of the start.sh scripts are for crudini and autoconfiguration, are we basically going to move start.sh to crudini.sh? | 03:14 |
| sdake | i had a similar thought | 03:14 |
| SamYaple | most of the services can be started without anything else | 03:14 |
| sdake | are we keeping crux as a dep with ansile | 03:15 |
| SamYaple | no | 03:15 |
| SamYaple | https://gist.github.com/anonymous/564e13a5c15a166998b6 | 03:16 |
| SamYaple | so that was the idea i had | 03:16 |
| sdake | set_configs does what | 03:17 |
| SamYaple | oops let me post that code | 03:17 |
| SamYaple | https://gist.github.com/SamYaple/eddf94ecc94bf4dbe4c5 | 03:18 |
| sdake | its more like bind-readonce | 03:19 |
| sdake | and bind-readalways | 03:19 |
| sdake | right? | 03:19 |
| SamYaple | yes, but bind-copyonce|bind-copyalways would be most accurate | 03:19 |
| SamYaple | but ignore that part | 03:20 |
| *** tobe has joined #kolla | 03:20 | |
| SamYaple | i was just playing with that to see how it felt | 03:20 |
| sdake | ok i'll use that in the spec | 03:20 |
| sdake | we need to pass the parameter (always vs once) to the bind script | 03:20 |
| sdake | or have two different scripts | 03:21 |
| SamYaple | it would be in $CONFIG_TYPE | 03:21 |
| SamYaple | look at the case statement | 03:21 |
| sdake | oh sourced | 03:21 |
| sdake | got it | 03:21 |
| sdake | so that model works well for everyting but keystone | 03:22 |
| sdake | is that what you were pointing out? | 03:22 |
| SamYaple | yea | 03:22 |
| SamYaple | but actually the code as it is works for keystone too | 03:23 |
| SamYaple | since we exec /config-crudini.sh, it never gets back to the start.sh script | 03:23 |
| SamYaple | but it branches | 03:23 |
| sdake | got it | 03:23 |
| SamYaple | really this feels like we are setting up crudini for deprecation | 03:23 |
| SamYaple | thats what im worried about | 03:24 |
| SamYaple | i want everyone on the same page | 03:24 |
| sdake | how does it feel like we set up crudini for deprecation? | 03:24 |
| SamYaple | its now an entirely different script to maintain that branches away from start.sh | 03:24 |
| SamYaple | its not just configuration, its also setting endpoints and what not from containers | 03:24 |
| SamYaple | the containers are selfconfiguring which is not the case with ansible | 03:25 |
| SamYaple | that being said, last i checked no one said "self-configuring containers" in the manifesto | 03:25 |
| sdake | that isn't mandatory that is just how we developed them | 03:25 |
| sdake | we can just not +2 newcontainers without a crudini start.sh script | 03:26 |
| sdake | rather config-crudini.sh script | 03:26 |
| SamYaple | so entirely seperate duplicate containers for crudini? | 03:26 |
| sdake | it would be nice if we only had to support one model | 03:26 |
| sdake | no same container | 03:27 |
| SamYaple | just for the last layer i mean | 03:27 |
| sdake | like you have implemented | 03:27 |
| SamYaple | im confused then | 03:27 |
| SamYaple | right ok. yea we can do it like i have showed | 03:27 |
| sdake | confused about which | 03:28 |
| SamYaple | but that leads to new commiters having to support a script that they likely have never used | 03:28 |
| *** daneyon has quit IRC | 03:29 | |
| sdake | i agree it would be ideal if we could forget the past ever happened | 03:29 |
| SamYaple | no thats not needed | 03:30 |
| sdake | but that isnt how reality works :) | 03:30 |
| SamYaple | ii think it just needs to be clear. are we reruiing all new things to support crudini as well? | 03:30 |
| SamYaple | requiring* | 03:30 |
| sdake | yes | 03:31 |
| SamYaple | i thought there was talk of triple-o supporting ansible inside? | 03:31 |
| SamYaple | instead* | 03:31 |
| sdake | that wasn't talk coming out of the tripleo community | 03:31 |
| sdake | that is a discussion that needs to be had | 03:31 |
| sdake | but tripleo+heat communities have made a huge effort to support our current crudini model | 03:32 |
| *** dimsum__ has joined #kolla | 03:58 | |
| *** dimsum__ has quit IRC | 04:03 | |
| *** sdake_ has joined #kolla | 04:56 | |
| *** sdake has quit IRC | 04:59 | |
| *** nihilifer has joined #kolla | 05:18 | |
| *** bradjones has quit IRC | 05:46 | |
| *** bradjones has joined #kolla | 05:49 | |
| *** bradjones has joined #kolla | 05:49 | |
| *** fangfenghua has joined #kolla | 05:53 | |
| *** fangfenghua has quit IRC | 05:58 | |
| openstackgerrit | Sam Yaple proposed stackforge/kolla: Add openvswitch container https://review.openstack.org/191532 | 06:13 |
| *** inc0 has joined #kolla | 06:15 | |
| inc0 | good morning | 06:15 |
| dasm | o/ | 06:15 |
| dasm | inc0: where are you? | 06:15 |
| inc0 | home office today | 06:16 |
| dasm | mhm. | 06:16 |
| nihilifer | hello | 06:16 |
| inc0 | hello nihilifer | 06:16 |
| dasm | o/ nihilifer | 06:18 |
| SamYaple | morning guys | 06:21 |
| *** inc0 has quit IRC | 06:26 | |
| *** shardy has joined #kolla | 06:29 | |
| *** inc0 has joined #kolla | 06:31 | |
| *** tobe has quit IRC | 06:44 | |
| *** sdake has joined #kolla | 06:56 | |
| *** sdake has quit IRC | 06:57 | |
| *** sdake has joined #kolla | 06:57 | |
| sdake | hey inc0 | 06:58 |
| sdake | hey dasm | 06:58 |
| sdake | hey nih* | 06:58 |
| inc0 | morning sdake | 06:58 |
| *** sdake_ has quit IRC | 07:00 | |
| dasm | good morning sdake | 07:05 |
| dasm | why so early? | 07:05 |
| sdake | late actually | 07:05 |
| dasm | (or late?) | 07:05 |
| sdake | its midnight | 07:05 |
| SamYaple | psshh its 2am here | 07:05 |
| dasm | xD | 07:05 |
| dasm | last time, when i tried to attend the meeting at midnight, it was pretty hard to write something in plain english. | 07:06 |
| dasm | so this is hardcore hour for me. | 07:06 |
| dasm | kudos SamYaple | 07:06 |
| dasm | kudos sdake | 07:06 |
| SamYaple | i work 3rd shift | 07:06 |
| SamYaple | its not as impressive | 07:06 |
| sdake | i work 1,2,3,4 shift | 07:06 |
| *** tobe has joined #kolla | 07:07 | |
| *** fangfenghua has joined #kolla | 07:08 | |
| sdake | for the folks in europe, i styaed up late just to link this : | 07:12 |
| sdake | https://launchpad.net/kolla/+milestone/liberty-1 | 07:12 |
| sdake | hey fangfenghua whats up bro | 07:12 |
| sdake | you can see there we have done a mountain of work | 07:12 |
| sdake | almost all green :) | 07:12 |
| sdake | purple is also a good color :) | 07:12 |
| *** fangfenghua has quit IRC | 07:13 | |
| *** Haomeng|2 has joined #kolla | 07:15 | |
| SamYaple | sdake did you say fang was here? | 07:16 |
| sdake | he was and then ping timed out | 07:16 |
| SamYaple | ah | 07:17 |
| sdake | anyone not on the drivers team that would like to be | 07:17 |
| sdake | the drivers team allows you to muck with launchpad | 07:17 |
| dasm | SamYaple: you wrote several weeks ago about 3rd shift. Still the same? or always 3rd? | 07:17 |
| SamYaple | always 3rd | 07:17 |
| dasm | mhm. | 07:18 |
| SamYaple | (its a 15% bump in pay :) | 07:18 |
| *** Haomeng has quit IRC | 07:18 | |
| sdake | where is my 15% bump in pay for working 3rd shift | 07:18 |
| SamYaple | ill tell you what sdake, we switch pay and ill pay your 15% out of my new salary | 07:18 |
| dasm | xD | 07:19 |
| sdake | that sounds --- suboptimal ;) | 07:19 |
| sdake | are there any blueprints targeted for l2 that folks re working on that will finish by june 25th? | 07:19 |
| sdake | samyaple is this blueprint started? | 07:21 |
| sdake | https://blueprints.launchpad.net/kolla/+spec/openvswitch-container | 07:21 |
| sdake | or in needs-review? | 07:21 |
| sdake | samyaple can you create a blueprint for thin-ifying neutron as well? | 07:22 |
| inc0 | sdake, I saw review up | 07:22 |
| sdake | inc0 was someone working on haproxy? | 07:23 |
| * sdake needs help maintaing th elaunchpad i am not all-knowing :) | 07:23 | |
| SamYaple | sdake thinify blueprint exists | 07:23 |
| inc0 | I think I saw something ha-proxy like in a tree? | 07:24 |
| SamYaple | sdake: the openvswitch one shows that there are commits in progress | 07:24 |
| sdake | inc0 that needs a mulligan | 07:24 |
| sdake | samyaple i set it to needs review | 07:24 |
| sdake | i also sety ou to the owner of https://blueprints.launchpad.net/kolla/+spec/thin-neutron-agents | 07:24 |
| SamYaple | sounds good | 07:25 |
| sdake | for june 25th? | 07:25 |
| sdake | not owner, i mean assignee | 07:25 |
| SamYaple | i can do it by the 25th, but it needs reviews that may not be done by the 25th | 07:25 |
| sdake | wfm i'll keep in l1 then | 07:26 |
| *** prad has quit IRC | 07:27 | |
| inc0 | hmm, so noone works at haproxy I guess? | 07:27 |
| SamYaple | someone was i thought | 07:27 |
| sdake | during l2 we will work on ansible-ifying the codebase | 07:28 |
| sdake | probably need a blueprint per service for that | 07:29 |
| SamYaple | oh please dont | 07:30 |
| SamYaple | at least not for the openstack services | 07:30 |
| sdake | one blueprint then? | 07:31 |
| sdake | i want to be able to distribute the work | 07:31 |
| inc0 | I guess writing bps will be more work than actuall work;) once we have first one incubated | 07:31 |
| sdake | so folks like diga and harm can get involved | 07:31 |
| SamYaple | its just the code is basically the same one you get to the openstack services | 07:31 |
| inc0 | maybe just keep Sam (or someone) as assignee and have multiple patches? | 07:32 |
| sdake | samyaple thta didn't pass my syntax parser | 07:32 |
| SamYaple | the openstack services require copy/paste ansible code | 07:32 |
| sdake | i'm open to suggestions on how to split the work up ;) | 07:32 |
| sdake | you mean copy from yaodu? | 07:33 |
| sdake | we have about 5 weeks between l1 and l2 | 07:33 |
| SamYaple | here is the flow i see: i mplement the first keystone/glance containers other people can take over from there | 07:33 |
| SamYaple | the ansible stuff can stay one blueprint | 07:33 |
| sdake | doesn't each container have seperate defaults/etc? | 07:34 |
| SamYaple | the other things needed for the config things will be the majority of the work | 07:34 |
| SamYaple | ugh i dont know. just get the spec approved | 07:34 |
| sdake | the refactor of start.sh in all the containers can definately be one blueprint | 07:35 |
| SamYaple | that more work than the ansible stuff in my opinion | 07:36 |
| sdake | renaming start.sh and putting in a fresh start.sh is more work? | 07:36 |
| sdake | i would think sorting out the defaults would be more work | 07:37 |
| SamYaple | i already did the defaults | 07:37 |
| SamYaple | i did that a couple of days ago | 07:37 |
| sdake | with config inside the container (crudini) all the work for making a new container is in the defaults | 07:37 |
| SamYaple | i just need the spec to be approve to commit all the defaults | 07:38 |
| sdake | got it | 07:38 |
| sdake | well the spec being approved for ha hasnt stopped the ha work ;-) | 07:42 |
| SamYaple | it does change the implementation | 07:42 |
| *** prad has joined #kolla | 07:42 | |
| SamYaple | i need to remov ethe docker compose stuff | 07:42 |
| sdake | ack | 07:42 |
| sdake | well when I wake FDH in the morning i'll submit a new spec based upon the mountain of feedback in the original :) | 07:43 |
| *** Haomeng|2 is now known as Haomeng | 07:43 | |
| SamYaple | thoughts on getting rid of the env entirely? just using hte bind-copyonce bind-copyalways method? | 07:44 |
| SamYaple | that would also protect sensitive things like passwords from the env variables | 07:44 |
| sdake | agree | 07:45 |
| sdake | that is what i'm going to propose in take 2 | 07:45 |
| sdake | or whatever patch set i'm on +1 :) | 07:45 |
| SamYaple | i like it. i think everyone else will too | 07:46 |
| inc0 | uhh that's a major change in approach | 07:46 |
| SamYaple | inc0: not major at all | 07:47 |
| sdake | inc0 what samyaple failed to mention is config inside container (crudini) will also be supported | 07:47 |
| sdake | there will be 3 modes | 07:47 |
| SamYaple | yea its not major compared to the spec | 07:47 |
| sdake | feel free to comment on the ansimble-multi spec ;) | 07:47 |
| inc0 | I did, I just misunderstood "remove env entirely" | 07:48 |
| inc0 | ;) | 07:48 |
| sdake | sams suggested modes are for config outside container | 07:48 |
| SamYaple | inc0: sorry, i meant the informal name we gave to the dynamic "env" method | 07:48 |
| inc0 | yeah, I agree with that | 07:48 |
| inc0 | but I've lost this one: what's exactly bind-copyalways? | 07:50 |
| inc0 | it's syncing container | 07:50 |
| inc0 | container's /etc/whatever.conf with /opt/kolla/whatever.conf | 07:50 |
| inc0 | all the time? | 07:50 |
| SamYaple | inc0: it means the the config will be copied from the outside everytime the container restarts | 07:50 |
| inc0 | ahh, ok | 07:50 |
| SamYaple | vs the config compied only the first time the container starts (bind-copy-once) | 07:51 |
| inc0 | what's use case for bind-copy-once? | 07:51 |
| SamYaple | bind-copyonce allows for immutable containers | 07:51 |
| SamYaple | it will be default | 07:51 |
| inc0 | I'm afraid ops will hate it | 07:51 |
| inc0 | redeploy whenever you spot a mistake in conf? | 07:51 |
| SamYaple | thats why bind-copyalways exists ;) | 07:51 |
| SamYaple | ops _will_ hate it | 07:52 |
| SamYaple | but they dont have t ouse it | 07:52 |
| inc0 | who will then?:) | 07:52 |
| SamYaple | idk | 07:52 |
| sdake | pureists :) | 07:52 |
| SamYaple | ^ | 07:52 |
| diga | sdake: Hi | 07:52 |
| diga | my local firewall issue is resolved | 07:53 |
| diga | :) | 07:53 |
| *** athomas has joined #kolla | 07:53 | |
| sdake | diga grats! | 07:54 |
| sdake | morning athmoas | 07:54 |
| sdake | athomas thatis | 07:54 |
| athomas | sdake, Good morning! | 07:55 |
| sdake | ya 1am - time for bed soon :) | 07:55 |
| sdake | I work 6am-10am and 6pm-midnight | 07:55 |
| diga | I am heading for now ansible multinode | 07:55 |
| sdake | to fit the dev team on kolla :) | 07:55 |
| athomas | sdake, I was wondering whether you were very early or very late ;-) | 07:56 |
| SamYaple | yes | 07:56 |
| sdake | athomas yes ;) | 07:56 |
| sdake | this mortal form needs sleep | 08:02 |
| sdake | night all | 08:02 |
| nihilifer | good night | 08:02 |
| sdake | night nih* | 08:04 |
| *** athomas has quit IRC | 08:05 | |
| *** sdake has quit IRC | 08:06 | |
| *** jmccarthy has joined #kolla | 08:31 | |
| *** shardy_ has joined #kolla | 08:38 | |
| *** shardy has quit IRC | 08:39 | |
| *** athomas has joined #kolla | 08:39 | |
| *** shardy_ has quit IRC | 08:44 | |
| *** shardy has joined #kolla | 08:44 | |
| *** athomas has quit IRC | 08:52 | |
| *** gfidente has joined #kolla | 08:59 | |
| *** inc0 has quit IRC | 09:17 | |
| *** inc0_ has joined #kolla | 09:17 | |
| *** athomas has joined #kolla | 09:25 | |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images https://review.openstack.org/190117 | 09:38 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images https://review.openstack.org/190117 | 09:41 |
| *** mstachow has joined #kolla | 09:57 | |
| mstachow | o/ | 09:57 |
| SamYaple | \o | 09:57 |
| *** zhiwei has quit IRC | 10:01 | |
| inc0_ | \o/ | 10:02 |
| inc0_ | -o- | 10:02 |
| inc0_ | /o\ | 10:03 |
| inc0_ | ymca! | 10:03 |
| *** dimsum__ has joined #kolla | 10:09 | |
| *** vbel has quit IRC | 10:39 | |
| *** vbel has joined #kolla | 10:40 | |
| *** Slower has quit IRC | 11:04 | |
| *** Slower has joined #kolla | 11:04 | |
| inc0_ | Slower, you awake? | 11:05 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Add base image for oraclelinux https://review.openstack.org/191013 | 11:14 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Add base image for oraclelinux https://review.openstack.org/191013 | 11:16 |
| SamYaple | pdb: the double up of cetons-binary-centos-binary-bash comes from not properly setting up the PREFIX override | 11:22 |
| pdb | SamYaple: explain? | 11:22 |
| SamYaple | the .buildconf file for those resets the PREFIX variable in those bases | 11:22 |
| *** shardy_ has joined #kolla | 11:22 | |
| *** shardy has quit IRC | 11:24 | |
| *** tobe has quit IRC | 11:25 | |
| *** shardy_ has quit IRC | 11:28 | |
| *** shardy has joined #kolla | 11:29 | |
| *** rhallisey has joined #kolla | 11:40 | |
| *** ChanServ sets mode: +o rhallisey | 11:40 | |
| rhallisey | morning | 11:52 |
| dasm | rhallisey: hello | 11:53 |
| rhallisey | hey! | 11:53 |
| *** sdake has joined #kolla | 11:54 | |
| *** sdake has quit IRC | 11:55 | |
| *** sdake has joined #kolla | 11:55 | |
| sdake | morning | 11:59 |
| *** inc0_ has quit IRC | 11:59 | |
| *** inc0 has joined #kolla | 11:59 | |
| inc0 | hello rhallisey I hope you follow this review?: nosetests tests/test_engine_service.py:StackServiceTest.test_stack_resource_describe_noncreated_resource | 12:00 |
| inc0 | sry, wrong copy:( | 12:00 |
| inc0 | https://review.openstack.org/#/c/189157/ | 12:00 |
| sdake | morning rhallisey | 12:00 |
| sdake | can you finish the job on cinder? :) | 12:00 |
| inc0 | sdake, awake already? | 12:00 |
| sdake | unfortunately | 12:01 |
| sdake | my kids jacked with my ac | 12:01 |
| sdake | woke up in hot sweat | 12:01 |
| sdake | ac set to 85f | 12:01 |
| sdake | (I keep it at 68) | 12:01 |
| inc0 | <translating 85f to celsious...> | 12:01 |
| sdake | hot | 12:02 |
| sdake | 41 i think | 12:02 |
| inc0 | 85 == 29 | 12:02 |
| sdake | ya | 12:02 |
| sdake | hot | 12:02 |
| inc0 | yup | 12:02 |
| sdake | compared to 68 | 12:02 |
| inc0 | 41 would be like midday in Dubai | 12:02 |
| sdake | wed-fri is issupposed to get to115f | 12:03 |
| sdake | ac needs to be at 68 or the house is warm all day | 12:03 |
| sdake | even though I have a 5 ton ac it just can't keep up with the sun | 12:03 |
| inc0 | I'll never move to California. | 12:03 |
| sdake | in arizona | 12:04 |
| sdake | worlds apart from california | 12:04 |
| sdake | in arizona everyone packs heat | 12:04 |
| sdake | in california heat is banned | 12:04 |
| inc0 | well, even worse. I don't like hot weather | 12:05 |
| *** bradjones has quit IRC | 12:13 | |
| sdake | mandre still around | 12:13 |
| sdake | jpeleer are you up at this godawful hour | 12:14 |
| *** bradjones has joined #kolla | 12:15 | |
| *** bradjones has joined #kolla | 12:15 | |
| mstachow | hi rhallisey :) | 12:20 |
| *** diogogmt has quit IRC | 12:20 | |
| sdake | anyone want to check out my SET tube amp? https://drive.google.com/file/d/0B8q6xDPETSkHWjdoaFFCT3RJMzUtLW1oSWlXY1lOMzVLcmJV/view | 12:21 |
| sdake | dual monoblock hand point to point wiring (no circuit board) | 12:24 |
| inc0 | wow, no wonder you have high temp in home;) | 12:24 |
| sdake | haha :) | 12:24 |
| inc0 | I can only wonder how much heat this must produce | 12:24 |
| sdake | those two big boxes on top are transformers ;) | 12:25 |
| inc0 | have you seen new mad max sdake? music from this movie would be a killer on such stuff | 12:25 |
| sdake | it gets warm int he 6 inches sorrouding the amp | 12:25 |
| sdake | beyond that can't tell the difference | 12:25 |
| sdake | and its mostly around the tubes | 12:26 |
| sdake | i told my kids "do you know how long your dad has wanted a tube amp?" | 12:26 |
| sdake | "I dont care" | 12:26 |
| sdake | "since I was 20" | 12:26 |
| sdake | "I dont care" | 12:26 |
| inc0 | well, there is one way to make them care | 12:27 |
| sdake | i could have gotsomething a little less beastly and weighty if I didn't go with SET | 12:27 |
| sdake | but set is the way to roll :) | 12:28 |
| inc0 | play this loud when they're around https://www.youtube.com/watch?v=YT516h7QwA4 | 12:28 |
| openstackgerrit | Michal Stachowski proposed stackforge/kolla: Galera container https://review.openstack.org/187225 | 12:28 |
| inc0 | and in better quality than this | 12:28 |
| sdake | i have that lp | 12:28 |
| inc0 | lp? | 12:29 |
| *** prad has quit IRC | 12:30 | |
| sdake | record | 12:35 |
| sdake | the push pull amps dont weigh a million pounds | 12:39 |
| sdake | or rather 121 lbs | 12:39 |
| sdake | i wish my kids were in school so I could get some volume rolling | 12:39 |
| sdake | they complain whenever I go over .1 watts... | 12:39 |
| SamYaple | wow sdake up already | 12:40 |
| SamYaple | hey rhallisey | 12:40 |
| rhallisey | SamYaple, hey | 12:40 |
| rhallisey | mstachow, hi! | 12:40 |
| sdake | i'm sure i'll be back in bed in a few hours samyaple | 12:40 |
| sdake | 4 hours of sleep does not make for a good day | 12:42 |
| *** shardy_ has joined #kolla | 12:43 | |
| *** rhallisey has quit IRC | 12:44 | |
| *** rhallisey has joined #kolla | 12:46 | |
| *** shardy has quit IRC | 12:47 | |
| inc0 | rhallisey, do you follow ansible multi node spec? | 12:47 |
| rhallisey | inc0, I haven't looked at it yet, but I know you pointed it to me earlier | 12:47 |
| rhallisey | I'm going to push a new cinder patch first then I'll come back to it | 12:48 |
| inc0 | I saw yours and Ians patchset in heat templates | 12:48 |
| inc0 | and well, if we push this idea we're implementing, this will also affect how tripleo will deploy configs | 12:49 |
| rhallisey | ya it's very close. | 12:49 |
| rhallisey | cool | 12:49 |
| sdake | it has no immediate impact | 12:49 |
| sdake | inc0 ^^ | 12:49 |
| inc0 | what I mean is, crudini won't be necessary in tripleo | 12:49 |
| rhallisey | ok | 12:50 |
| inc0 | in fact, I think using bind-copyalways will be best for tripleo | 12:50 |
| *** shardy_ has quit IRC | 12:50 | |
| sdake | inc0 i think so as well | 12:50 |
| sdake | but again, no immediate impact | 12:50 |
| inc0 | and I wonder if we should start to deploy configs this way from the beggining | 12:50 |
| inc0 | yeah, sure, but we don't have code in main tripleo code yet | 12:51 |
| *** shardy has joined #kolla | 12:51 | |
| sdake | well if we dropped config inside container from get go that would be a big imrpovement | 12:51 |
| sdake | slagle you alive | 12:51 |
| inc0 | so we can do it the right way from start, and that's something I'd like to follow up, even help you with | 12:51 |
| *** dimsum__ has quit IRC | 12:52 | |
| rhallisey | inc0, awesome | 12:52 |
| inc0 | we should talk this through with Ian and maybe someone from tripleo? | 12:53 |
| sdake | inc0 that is what the slagle ping was about ;) | 12:53 |
| inc0 | well, I'd have this talk later on anyway since its like 6am on west coast;) | 12:54 |
| inc0 | not a good time to have architectural discussions;) | 12:54 |
| *** dimsum__ has joined #kolla | 12:54 | |
| *** dimsum__ is now known as dims | 12:55 | |
| *** dims has quit IRC | 12:55 | |
| *** dims has joined #kolla | 12:56 | |
| *** jtriley has joined #kolla | 12:56 | |
| sdake | jtriley around this fine morning? | 12:56 |
| *** shardy has quit IRC | 12:56 | |
| sdake | i wonder if houses wil ever install dc stragiht in the house | 13:00 |
| sdake | would make my life alot easier | 13:00 |
| inc0 | well, Nikola Tesla would want that | 13:01 |
| *** shardy has joined #kolla | 13:01 | |
| inc0 | but on the other hand, imagine how often you've tried to put usb in upside-down | 13:01 |
| sdake | ya that didn't even get done right | 13:02 |
| sdake | usbc ftw | 13:02 |
| sdake | i have several busted usb connectors on my z820 because of my kids and that problem :( | 13:03 |
| inc0 | you'd have much more broken things if it would be the case of 220V 2amp current;) | 13:03 |
| inc0 | AC | 13:04 |
| inc0 | DC I mean | 13:04 |
| sdake | it would put the wallwart peope out of business :) | 13:04 |
| inc0 | and probably out of existance at some percent | 13:05 |
| inc0 | with a fair amount of somke with it | 13:05 |
| sdake | trying to figure out which wall wart goes with which device is no bueno | 13:06 |
| inc0 | btw you all know where did "smoke tests" phrase came out? | 13:06 |
| *** nihilifer has quit IRC | 13:06 | |
| inc0 | all I'm saying, AC is more idiot friendly than DC, and world is full of idiots | 13:08 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Create keystone user in start.sh if it doesn't exist https://review.openstack.org/191071 | 13:08 |
| *** jtriley has quit IRC | 13:08 | |
| *** dwalsh has joined #kolla | 13:10 | |
| SamYaple | inc0: bind-copyalways also has the advantage of being a very traditional approch so lots of people will be immediately familiar with it | 13:17 |
| SamYaple | modify config in a certain place on teh host and restart the service | 13:17 |
| SamYaple | bam | 13:17 |
| inc0 | yeah, that's why I like this approach most really | 13:17 |
| SamYaple | anyones tooling can also lay down the config and work with the ansible stuff side by side if desired | 13:17 |
| inc0 | even tho its not very container-pure | 13:17 |
| SamYaple | inc0: thats why the default is bind-copyonce ;) | 13:17 |
| inc0 | people will grow to hate us for that;) | 13:18 |
| *** gfidente is now known as gfidente|afk | 13:19 | |
| inc0 | we should put a outstanding bug for "my config doesn't work", so every time someone would want to file a bug with this, launchpad will point him to our "its not a bug, its a feature" outstanding bug;) | 13:20 |
| *** prad has joined #kolla | 13:23 | |
| *** kevsi_ has joined #kolla | 13:31 | |
| *** kevsi has quit IRC | 13:32 | |
| *** pdb is now known as pbourke | 13:34 | |
| *** ccrouch has joined #kolla | 13:37 | |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Cinder container https://review.openstack.org/170965 | 13:39 |
| mstachow | inc0 are you here ? | 13:39 |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Add cinder into the docker compose setup https://review.openstack.org/173507 | 13:44 |
| *** absubram has joined #kolla | 13:56 | |
| *** athomas has quit IRC | 13:59 | |
| *** athomas has joined #kolla | 14:04 | |
| inc0 | mstachow, now I am | 14:07 |
| *** shardy_ has joined #kolla | 14:13 | |
| *** shardy has quit IRC | 14:15 | |
| *** shardy_ has quit IRC | 14:19 | |
| *** shardy has joined #kolla | 14:19 | |
| *** jtriley has joined #kolla | 14:20 | |
| mstachow | sdake what do You mean with INIT_DB in Your review message ? Is It prepare_db function or something ? | 14:22 |
| sdake | not that init-db but ttthere was another variable like ROW | 14:23 |
| sdake | iirc | 14:23 |
| sdake | ROW what? :) | 14:23 |
| sdake | a boat :) | 14:23 |
| sdake | shouldn't that be CLUSTER_DB_ROW? | 14:23 |
| sdake | init-db is a global | 14:23 |
| *** openstackgerrit has quit IRC | 14:24 | |
| mstachow | huh that one. It's just binlog format it's default value for galera here | 14:24 |
| *** openstackgerrit has joined #kolla | 14:24 | |
| *** diogogmt has joined #kolla | 14:24 | |
| mstachow | I can do some extra variable here for binlog, that's not problem for me (hero ;) ). | 14:26 |
| *** fangfenghua has joined #kolla | 14:27 | |
| mstachow | Another thing is that - galera is a boat, so ROW and galera match :) | 14:27 |
| *** fangfenghua has quit IRC | 14:31 | |
| *** jtriley has quit IRC | 14:32 | |
| *** jasonsb has quit IRC | 14:32 | |
| sdake | rhallisey around? | 14:35 |
| rhallisey | sdake, ya | 14:35 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Create keystone user in start.sh if it doesn't exist https://review.openstack.org/191071 | 14:35 |
| sdake | re https://review.openstack.org/#/c/187313/1/docker/centos/binary/cinder-data/Dockerfile | 14:35 |
| sdake | that will create an internal /etc/lvm directory that is persistent | 14:36 |
| sdake | is that what you want? | 14:36 |
| sdake | internal to the container | 14:36 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Add keystone source image for oraclelinux base https://review.openstack.org/191833 | 14:36 |
| sdake | pbourke ++ :) | 14:36 |
| pbourke | doing some rebasing, hate dependant patches...! | 14:37 |
| sdake | git rebase -i ftw ;) | 14:37 |
| sdake | pbourke have a few minutes to chat about your keystone container | 14:40 |
| pbourke | sure | 14:40 |
| rhallisey | sdake, ya I just want the host to be able to do a vgremove | 14:40 |
| sdake | pbourke so what i'd like to see is a base image (such as ol, centos, ubuntu, debian) | 14:41 |
| sdake | and then on top of that layer a distribution type "such as binary, or source" | 14:41 |
| sdake | for examplle, I'd like to compose ol + rdo | 14:41 |
| sdake | or centos+source | 14:42 |
| sdake | without having to have source copied to multiple places | 14:42 |
| sdake | do you think that is possible? | 14:42 |
| sdake | i see what samyaple did, he uses links for rdo in fedora images | 14:45 |
| *** absubram has quit IRC | 14:45 | |
| pbourke | hmm yeah I thought that was just because we didnt have fedora images yet though | 14:46 |
| pbourke | sdake: ill have a look and see | 14:49 |
| mstachow | Is it necessary to check variables twice ? | 14:49 |
| *** vinkman has joined #kolla | 14:49 | |
| sdake | mstachow no | 14:49 |
| sdake | pbourke here is another patch to consider | 14:49 |
| sdake | https://review.openstack.org/#/c/184222/ | 14:49 |
| mstachow | sdake thanks | 14:49 |
| sdake | pbourke here is the blueprint proposal | 14:54 |
| sdake | https://blueprints.launchpad.net/kolla/+spec/refactor-base-image-layout | 14:54 |
| *** jtriley has joined #kolla | 14:55 | |
| sdake | which is exactly what I want | 14:55 |
| sdake | under "proposed layout" | 14:55 |
| sdake | samyaple still awake? | 14:55 |
| *** jpeeler has quit IRC | 14:55 | |
| SamYaple | inc0: sdake and @everyone_else, should we vote on the default method then? bind-copyonce vs bind-copyalways? | 14:56 |
| SamYaple | sdake: maybe.... | 14:56 |
| sdake | samyaple your commit referenced above doesn't match the blueprint? | 14:56 |
| sdake | rather review 184222 | 14:56 |
| sdake | samyaple i'll add to the agenda | 14:56 |
| sdake | (the voting) | 14:56 |
| SamYaple | sdake: it was a commit before we required blueprints. im piggybacking onto it | 14:57 |
| rhallisey | sdake, bashate is all set for cinder | 14:57 |
| inc0 | SamYaple, I don't particuarally like democracy in terms of architectural decisions;) | 14:57 |
| SamYaple | the change is within the definition of the blueprint | 14:57 |
| SamYaple | inc0: i personally dont care one way or the other to be honest. i will say i will ony be using bind-copyalways though | 14:57 |
| inc0 | same as mee | 14:58 |
| inc0 | hence my question..who *really* will use copyonce? | 14:58 |
| SamYaple | in that case inc0, the default should probably be the most used option, but its not a battle i care to fight | 14:58 |
| SamYaple | inc0: as sdake said, "pureists" | 14:58 |
| inc0 | I mean, besides purists, let purists cofigure it themselves;) | 14:58 |
| SamYaple | or purists rather | 14:58 |
| inc0 | not many purists in ops really;) | 14:59 |
| sdake | i was being cheeky when I said that | 14:59 |
| SamYaple | sdake: we know :D | 14:59 |
| *** kevsi_ has quit IRC | 14:59 | |
| sdake | copy_once implements principle of least surprise | 14:59 |
| sdake | copy_once implements one source of truth | 14:59 |
| sdake | copy_always is the opposite of these two properties :) | 15:00 |
| SamYaple | unless of course someone changes the config outside the cotnaienr and expects it to change inside, when it doesnt that would be suprising | 15:00 |
| inc0 | I disagree with that really..."why my configs doesn't work? I've changed, restarted servie...it should work!" | 15:00 |
| SamYaple | ^ | 15:00 |
| sdake | ok source of truth then ? | 15:00 |
| pbourke | Im not sure its possible to have one dockerfile per service? that was why I went with the layout proposed on the whiteboard... | 15:00 |
| inc0 | external config really will be the soruce of truth | 15:00 |
| pbourke | reason being you can sed in the base combo easily enough but you wont know which packaging mechanism to use | 15:01 |
| openstackgerrit | Michal Stachowski proposed stackforge/kolla: Galera container https://review.openstack.org/187225 | 15:01 |
| SamYaple | pbourke: i dont think anyone was proposing one dockerfile per service | 15:01 |
| SamYaple | mandre and I were definetly against it | 15:02 |
| sdake | what I want and maybe its not possible | 15:02 |
| *** jtriley has quit IRC | 15:02 | |
| inc0 | actually I would go futher and set ln -s between /etc/keystone and /opt/kolla/keystone...but I know that might be one step too far;) | 15:02 |
| sdake | I want to say "give me distro ol + source" | 15:02 |
| sdake | and out comes a bunch of images with that setup | 15:02 |
| SamYaple | inc0: ill tell you why that has issues | 15:02 |
| sdake | i want to say "give me distro centos + source" | 15:02 |
| SamYaple | inc0: permissions. that uses the guid and uid of the host | 15:02 |
| sdake | and out comes a bunch of images with that setup | 15:02 |
| SamYaple | those dont always align with the container | 15:02 |
| inc0 | you already have SamYaple | 15:02 |
| inc0 | thats why I'm reluctant myself | 15:03 |
| SamYaple | inc0: sounds like something i would have done :P | 15:03 |
| SamYaple | sdake: thats the plan | 15:03 |
| pbourke | you can, but you need dockerfiles for each flavor as far as I can see. basically the way I have it in ol keystone review. SamYaple am I missing something? | 15:03 |
| inc0 | akwasne is playing around setup from source | 15:03 |
| sdake | pbourke can you link your review | 15:03 |
| pbourke | https://review.openstack.org/#/c/191833/ | 15:04 |
| sdake | so samyaple knows what your tlaking about :) | 15:04 |
| sdake | pbourke I was speaking of this one: | 15:04 |
| sdake | https://review.openstack.org/#/c/190117/4 | 15:04 |
| sdake | samyaple i further dont want to have a bajiillion source directories of duplicated content if it can be avoided :) | 15:05 |
| SamYaple | sdake: yes https://review.openstack.org/#/c/190117 and https://review.openstack.org/#/c/184222/ work together and dont conflict | 15:05 |
| sdake | or rdo directories | 15:05 |
| *** jtriley has joined #kolla | 15:06 | |
| SamYaple | sdake: no duplicated content, just symlinks | 15:06 |
| sdake | i can live with symlinks | 15:06 |
| sdake | and different dockerfiles | 15:06 |
| sdake | is that what we get out of these two changes? | 15:06 |
| SamYaple | i would never vote for something that violates DRY | 15:06 |
| SamYaple | sdake: yes | 15:07 |
| *** bmace has quit IRC | 15:07 | |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Cinder container https://review.openstack.org/170965 | 15:07 |
| sdake | what order do they need to go in the repo | 15:07 |
| SamYaple | sdake: either order. the other will have to rebase | 15:07 |
| SamYaple | lets get the oldest merged in first | 15:07 |
| sdake | lol | 15:07 |
| SamYaple | it removes all the buildconf files | 15:07 |
| inc0 | rhallisey, long shot here, can we specify that we don't want to install iscsi stuff while deploying container? | 15:08 |
| SamYaple | also i dont want to rebase, you caught me | 15:08 |
| sdake | pborke you opposed to the pain of rebasing | 15:08 |
| sdake | pbourke | 15:08 |
| sdake | sorry | 15:08 |
| sdake | typo | 15:08 |
| rhallisey | inc0, yes, I'm going to follow up with that | 15:08 |
| SamYaple | inc0: it would be installed in the contaienr, but it doesnt have to be used i dont think | 15:08 |
| SamYaple | say in the case of ceph | 15:08 |
| pbourke | mine is a little fiddily as you have to make sure all symlinks aren't broken. but i have a script so don't mind rebasing | 15:08 |
| rhallisey | I want to get a 'working cinder' up | 15:08 |
| *** blahRus has joined #kolla | 15:08 | |
| inc0 | SamYaple, well, we want to keep containers small and tidy right?;) | 15:09 |
| pbourke | I just hope we're all clear on the scope and purpose of the refactor-base-image-layout bp? | 15:09 |
| rhallisey | then scrape out that part because I've been having issues taking it out | 15:09 |
| sdake | pbourke thanks for taking one for the team :) | 15:09 |
| inc0 | allright Ryan, let's get this in and file a bug to remove this dependency later? | 15:09 |
| *** jpeeler has joined #kolla | 15:10 | |
| SamYaple | pbourke: mandre and I are on the same page, sdake you seem to be there since we clarified we arent violating DRY? | 15:10 |
| openstackgerrit | Merged stackforge/kolla: Separate base images into different folders https://review.openstack.org/184222 | 15:10 |
| sdake | file a wishlist bug with title "TechDebt: this is the debt" | 15:10 |
| *** gfidente|afk is now known as gfidente | 15:10 | |
| sdake | samyaple wfm | 15:10 |
| SamYaple | inc0: FAT CONTAINERS WOOOOO | 15:10 |
| sdake | pbourke the scope is to be able to compose any container os with any type of distribution method of openstack | 15:11 |
| rhallisey | inc0, correct | 15:11 |
| inc0 | today its one package, tomorrow another service...its like imigration policy propaganda | 15:11 |
| pbourke | SamYaple: I think we're all good just I thought sdake may have been thinking we were doing service base images | 15:11 |
| sdake | i had thought that until I scrolled down :) | 15:11 |
| rhallisey | I'll file a bug and reference it | 15:11 |
| pbourke | ok | 15:11 |
| inc0 | cool | 15:12 |
| pbourke | It may be possible to do that for the source installs given they should differ little to none between destros | 15:12 |
| pbourke | *distros | 15:12 |
| pbourke | but for now I think it's simplest to follow the pattern the binary images are using | 15:12 |
| sdake | that wfm as long as start.sh isnt' duplicated a million times | 15:12 |
| sdake | it is presently in teh source base between fedora and centos | 15:13 |
| SamYaple | pbourke: agreed mostly | 15:13 |
| SamYaple | sdake: it is not | 15:13 |
| pbourke | sdake: right but https://review.openstack.org/#/c/190117/4 fixes that | 15:13 |
| SamYaple | sdake: it is not duplicated at all | 15:13 |
| sdake | perhaps i am mistaken | 15:13 |
| sdake | 4 hours of sleep - 8am | 15:13 |
| SamYaple | its all symlinks currently as well | 15:13 |
| sdake | ok cool | 15:13 |
| inc0 | btw, crazy thought - do we want tempest to be run on our builds as CI? | 15:13 |
| SamYaple | i wont violate DRY not for all the +2s in the world | 15:13 |
| sdake | inc0 yes | 15:14 |
| sdake | inc0 we have gating of the building only atm | 15:14 |
| sdake | tempest gating is blocked on running kolla from a single nic with full neutron connectivity | 15:14 |
| inc0 | yeah, I know, hence my question | 15:14 |
| sdake | which maybe blockedo n the fact that linuxbridge can't operate single nic | 15:14 |
| *** jtriley has quit IRC | 15:15 | |
| SamYaple | correct, SamYaple cant make it work, but samyaple doesnt do linuxbridge well, he is an OVS man | 15:15 |
| SamYaple | pffff SamYaple | 15:15 |
| sdake | samyaple is working on ovs implementation | 15:15 |
| sdake | so we can get a single nic implentation working | 15:15 |
| sdake | then we can gate on ovs + singlenic + tempest ;) | 15:15 |
| SamYaple | cant do ovs without flat neutron containers | 15:16 |
| SamYaple | ARRRGGG | 15:16 |
| sdake | a path to unblocking has been devised, matter of execution at this point :) | 15:16 |
| sdake | oh ya I forgot that one | 15:16 |
| SamYaple | dont worry samyaple is working on that too | 15:16 |
| inc0 | noob question, what's single nic implementation? I thought with network=host we have exactly same network namespace inside containers? | 15:16 |
| sdake | inc0 neutron requires two nics to operate | 15:16 |
| SamYaple | inc0: neutron needs a nic to route out on | 15:16 |
| SamYaple | sdake: wrong! | 15:16 |
| SamYaple | you just cant access the box if you use a single nic with linuxbridge ;) | 15:17 |
| sdake | right | 15:17 |
| SamYaple | technically the floating ips should work | 15:17 |
| sdake | but it busts host networking | 15:17 |
| SamYaple | unless its OVS. i got that stuff down | 15:17 |
| inc0 | but why are we limited to 1 nic? | 15:17 |
| SamYaple | but ovs grabs the nic at layer2 | 15:17 |
| sdake | inc0 the gate has only 1 routable nic I guess | 15:18 |
| sdake | the other nic is private | 15:18 |
| *** bmace has joined #kolla | 15:18 | |
| inc0 | ah, and if we put linuxbridge over it, we lose routable nic right? | 15:18 |
| *** jtriley has joined #kolla | 15:18 | |
| sdake | yup | 15:18 |
| sdake | jtriley morning around? | 15:18 |
| inc0 | and we put linuxbridge due to contenerization | 15:18 |
| sdake | linuxbridge is what danyeon implemented first | 15:19 |
| inc0 | can't we just add virtual nic and brigdge together with container stuff? | 15:19 |
| sdake | don't know the details of why but i've heard alot of complaints from the field that ovs is unreliable | 15:19 |
| SamYaple | inc0: yea but it breaks floating ips | 15:19 |
| sdake | inc0 if you can figure it out i'll mail you 1$ USD | 15:19 |
| sdake | we have had 4+ people spend 5+ days each on it | 15:20 |
| sdake | al failed :) | 15:20 |
| inc0 | haha | 15:20 |
| SamYaple | sdake: lots of ovs is old, that is bad. OVS >2.1 should never be used, OVS 2.3.1 is prefered. Ubuntu packages 2.0.2 and otehrs also package old ones | 15:20 |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Cinder container https://review.openstack.org/170965 | 15:20 |
| SamYaple | <2.1 | 15:20 |
| inc0 | sounds like good, creative way to lose some time;) | 15:20 |
| SamYaple | inc0: youre welcome too it. i can get it to work upto having floating ips respond. thats where it breaks | 15:21 |
| rhallisey | I think cinder is all set now | 15:21 |
| SamYaple | ie floating ips wont respond locally or remotely | 15:21 |
| inc0 | yeah, 2.1 was the version where they had this big perfomance leap right? | 15:21 |
| SamYaple | inc0: and allowed arp responder/l2pop stuff | 15:21 |
| SamYaple | 2.3.1 is the latest LTS | 15:21 |
| inc0 | SamYaple, do you have any code yet you'd like to share? | 15:22 |
| inc0 | so we can coop there? | 15:22 |
| SamYaple | 2.4 will support conntracking and all the other firewall bits so we can remove the iptables dependancy! all the secgroup rules can be implemented as OVS flows | 15:22 |
| SamYaple | inc0: it was all by hand | 15:22 |
| sdake | inc0 hold i can share my go at it :) | 15:22 |
| inc0 | I'd gladly take a look to get my bearings, I know thing or two about networking, but containers are new to me | 15:23 |
| SamYaple | inc0: the container doesnt really come into play | 15:23 |
| *** sdake_ has joined #kolla | 15:23 | |
| inc0 | well, that's why I'm kinda puzzled, how does neutron CI work then? | 15:24 |
| sdake_ | inc0 here is a couple tries: | 15:24 |
| sdake_ | http://ur1.ca/mu10m -> http://paste.fedoraproject.org/232204/14343818 | 15:24 |
| sdake_ | http://ur1.ca/mu10r -> http://paste.fedoraproject.org/232205/38186914 | 15:24 |
| SamYaple | inc0: pretty sure they have multinic, dont know why we dont. i _know_ they have multihost, but they dont use it | 15:24 |
| sdake_ | let me ask on infra | 15:25 |
| inc0 | maybe just ask them?;) | 15:25 |
| *** sdake has quit IRC | 15:27 | |
| mstachow | SamYaple, about mariadb 5.5 vs 10 | 15:27 |
| mstachow | This dumps was totaly random | 15:27 |
| mstachow | Sometimes on one node I was able to join to cluster sometimes I wasn't. Logs wasn't clear for me, but I will investigate once again whole situation | 15:28 |
| SamYaple | mstachow: going to need more than that. everyone i know is moving to mariadb10, and ive been personally using it for a year just fine | 15:29 |
| SamYaple | i can help you if you tell me how to replicate | 15:29 |
| SamYaple | or want to share the logs if its interesting | 15:29 |
| mstachow | no problem, if I will had any problems again I will share logs with You | 15:29 |
| SamYaple | i saw the cache cause this once, galera does not work with query cache | 15:29 |
| mstachow | But cache and containers ? I am removing also storage for db each time when I'm recreating galera | 15:31 |
| slagle | sdake_: yea, i'm alive :) was all tied up last week | 15:31 |
| slagle | sdake_: i did see the spec, but haven't had a chance to read it thoroughly | 15:32 |
| SamYaple | mstachow: its a my.cnf option | 15:32 |
| sdake_ | slagle there is a long thread in the ansimble-multi spec | 15:32 |
| sdake_ | slagle let me summarize it for you since i know your busy :) | 15:32 |
| sdake_ | we are talking about having three modes of operation | 15:32 |
| SamYaple | pbourke: https://review.openstack.org/#/c/191833/ if you are around lets discuss that comment before i go to sleep | 15:32 |
| inc0 | sdake_, what if we use 127.0.0.1 as "private network"? | 15:32 |
| inc0 | can we run tests on same machine as services? | 15:32 |
| sdake_ | inc0 let me get back to you on that point :) | 15:32 |
| pbourke | SamYaple: sure - just reading your comment | 15:33 |
| *** pradk has joined #kolla | 15:33 | |
| sdake_ | slagle mode 1 - is the same mode that currently exists today - config inside container using crud ini | 15:33 |
| pbourke | SamYaple: all that makes sense | 15:33 |
| sdake_ | slagle mode 2 - is a new mode that is config OUTSIDE the container using a config managmenet tool, or for the foolhardy vi :) | 15:33 |
| sdake_ | slagle mode 3 is a new mode that is config OUTSIDE the container using a config managmenet tool, or for the foolhardy vi | 15:34 |
| SamYaple | pbourke: discussion over. yay :D | 15:34 |
| SamYaple | im goign to sleep | 15:34 |
| pbourke | :D | 15:34 |
| sdake_ | slagle mode 2 and mode 3 have slightly different semantics, config files are copied from outside the container to inside either one time or mulitiple times depending on mode | 15:34 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images https://review.openstack.org/190117 | 15:34 |
| SamYaple | night all | 15:34 |
| sdake_ | sweet dreams samyaple ;) | 15:34 |
| inc0 | cya SamYaple | 15:34 |
| sdake_ | slagle the key thing to think about is config inside container vs config outside container | 15:35 |
| slagle | sdake_: ok, not sure i grok the difference between 2 and 3 | 15:35 |
| slagle | yea, ok | 15:35 |
| sdake_ | config inside container = docker-compose | 15:35 |
| sdake_ | config outside container = puppet or chef or ansible or vi | 15:35 |
| mstachow | good night SamYaple :) | 15:35 |
| sdake_ | slagle difference between 2 and 3 is one maintains immutability one does not | 15:36 |
| slagle | sdake_: which (or all of?) the 3 is kolla planning to implement? | 15:36 |
| sdake_ | I dont want to disrupt tripleo's efforts | 15:36 |
| sdake_ | we already have #1 implemented | 15:36 |
| sdake_ | we are implementing 2 and 3 anew | 15:36 |
| sdake_ | they are very similair - its like a 3 line difference between the two models | 15:36 |
| sdake_ | (guessing on 3 lines no actual code:) | 15:37 |
| slagle | ok. i likely need to go read the spec to understand it better | 15:37 |
| sdake_ | if you want to understand it you will have to read and analyze each comment in detail | 15:37 |
| sdake_ | the big difference between mode 1, and mode 2/3 is mode 2/3 allow full customization | 15:37 |
| sdake_ | mode 1 is totally opinionated | 15:38 |
| sdake_ | mode 1 is what rhallisey has up for review in tripleo review queue | 15:38 |
| inc0 | point is, how do you like idea about tripleo generating config as tripleo does now - as a single file, then just put it in specified folder on host and deploy an container? | 15:38 |
| slagle | right, i see how it works now with docker compose | 15:38 |
| inc0 | instead of provide env variables and let crudini build config inside container as it is done now? | 15:38 |
| slagle | honestly, i'm not sure mode 1 is the right long term thing for tripleo | 15:38 |
| *** absubram has joined #kolla | 15:39 | |
| sdake_ | we are maintaining mode 1 for tripleo | 15:39 |
| sdake_ | we prefer to go straight to mode 2/3 permanelty and drop mode 1 | 15:39 |
| sdake_ | but we dont leave downstreams behind | 15:39 |
| sdake_ | but if tripleo doesn't even want mode 1 long term, then why ahve it :) | 15:40 |
| inc0 | do we have any downstreams *besides* tripleo? | 15:40 |
| sdake_ | inc0 nada | 15:40 |
| inc0 | then just drop mode 1, refactor existing tripleo patches to use mode 3 and be done with it? | 15:41 |
| slagle | well really i'm just saying, tripleo doesn't have any landed code yet | 15:41 |
| slagle | i dont know that we've even validated the full architecture based on mode 1 | 15:41 |
| sdake_ | slagle its important to know how we should proceed because it affects our strategy going forward | 15:42 |
| slagle | we are doing a lot of work to deploy via puppet...maybe it makes sense for us to consider mode 2/3 | 15:42 |
| sdake_ | strategy as defined by committing resources to achieve ad esired outcome :) | 15:42 |
| slagle | sdake_: sure, in all honestly, i'm not sure i'll be able to give you a concrete answer | 15:42 |
| inc0 | Slower, rhallisey probably you'd like to look at this conversation as well | 15:43 |
| slagle | the fact is, (aiui) no one has actually deployed a producton cloud with kolla mode 1 | 15:43 |
| sdake_ | actually not accurate | 15:43 |
| sdake_ | but they are pretty bleeding edge :) | 15:43 |
| *** pradk has quit IRC | 15:43 | |
| slagle | is there anything documented about how to do it? | 15:43 |
| sdake_ | heavy wizardy | 15:44 |
| rhallisey | mode 3 would allow puppet -> kolla | 15:44 |
| rhallisey | which would be nice | 15:44 |
| slagle | i'm just curious if mode 1 is going to break down if we start to do HA/multinode/orchestrating updates/ etc | 15:44 |
| slagle | ya know, all the long tail stuff that is actualy the 90% of the work to deploy the cloud :) | 15:44 |
| inc0 | slagle, that will require some handy env tinkering | 15:44 |
| slagle | and if mode 1 isn't the right model for that...i don't know that tripleo would use it | 15:44 |
| *** jtriley has quit IRC | 15:45 | |
| sdake_ | slagle it would be fantastic if you could say that in the review :) | 15:45 |
| slagle | sure, i need to review it | 15:45 |
| sdake_ | rhallisey if we drop mode 1 - is that going to cause a bunch of disruption for your work? | 15:45 |
| rhallisey | sdake_, no, because all we do it pull containers and run them | 15:46 |
| sdake_ | slagle when can you get er done, people chomping at bit to get started | 15:46 |
| rhallisey | we don't configure | 15:46 |
| sdake_ | where does yoru openstack.env file come from? | 15:46 |
| slagle | sdake_: i'll do it today | 15:47 |
| sdake_ | slagle sounds great | 15:47 |
| slagle | if not in detail, i'll at least add my thoughts | 15:47 |
| sdake_ | slagle i am working on a spec update - but would appreciate the comments in the previous review | 15:47 |
| inc0 | slagle, don't worry about ansible-technicalities, we are in agreement that ansible will not be hard requirement there | 15:47 |
| sdake_ | th eone with 30+ comments | 15:47 |
| rhallisey | sdake_, oh I see that will get yanked.. that's ok if we adjust | 15:48 |
| rhallisey | the change won't be hard | 15:48 |
| sdake_ | rhallisey your statement was unclear could you restate | 15:48 |
| inc0 | rhallisey, I've said that before - if you need any help, just honk | 15:48 |
| rhallisey | sdake_, if mode 1 is removed we will have to change it a bit, but it won't be too bad | 15:49 |
| rhallisey | because what we're doing is pretty simple, we can instead give a template openstack.env or something | 15:49 |
| sdake_ | slagle this model should work well with puppet buti am no puppet expert | 15:50 |
| rhallisey | sdake_, I agree, if puppet can gen the config it removes that step where we add openstack.env | 15:50 |
| inc0 | sdake_, puppet, at the end, just generates files, that will remain the same | 15:50 |
| slagle | yea, i'm just curious, how is puppet, doing something like configuring nova.conf | 15:51 |
| sdake_ | puppet also starts services and other things | 15:51 |
| inc0 | only difference might be it will put it to /opt/kolla instead of /etc | 15:51 |
| slagle | does a puppet apply run in the container? | 15:51 |
| slagle | or is puppet itself aware of the containers? | 15:51 |
| sdake_ | it runs on the host | 15:51 |
| inc0 | slagle, it doesn't have to know about containers | 15:51 |
| sdake_ | i wouldn't think puppet would be aware of th econtainers | 15:51 |
| sdake_ | but it could be if you wanted it to do so and had people to write the code :) | 15:52 |
| inc0 | I mean, we can then run container with puppet | 15:52 |
| inc0 | like ensure => run...or whatever you deploy container with puppet | 15:52 |
| slagle | i'm not asking for that, i was just asking how it works | 15:52 |
| inc0 | but that's completely decoupled from config | 15:53 |
| sdake_ | the host ends up with keystone.conf for example in /opt/kolla/openstack/keystone/keystone.conf | 15:53 |
| sdake_ | the container reads /opt/kolla/openstack/keystone/keystone.conf on startup | 15:53 |
| sdake_ | it either copies it once on continer create | 15:53 |
| sdake_ | or copies it every container start | 15:53 |
| slagle | ok. are the puppet openstack modules used to configure that keystone.conf? | 15:53 |
| sdake_ | (modes 2 or 3) | 15:53 |
| inc0 | slagle, yes | 15:54 |
| inc0 | just running keystone itself will differ | 15:54 |
| sdake_ | would require r&d I think | 15:54 |
| sdake_ | i am not a uppet expert - get one in channel and we can talk about it :) dprince perhaps :) | 15:54 |
| slagle | sdake_: ok, so when you say kolla is implemented mode 2/3...what does that mean? | 15:55 |
| slagle | is someone actually doing the puppet work? or... | 15:55 |
| sdake_ | nobody is doing puppet work for kolla | 15:55 |
| slagle | there's some interface there that shows how it might work | 15:55 |
| sdake_ | so puppet has a keystone module i assume, and that configures keystone.conf | 15:55 |
| sdake_ | atm in tripleo that occurs on the host correct? | 15:56 |
| slagle | yes | 15:56 |
| sdake_ | that would work the same way although the keystone.conf may be in a different place then puppet expects | 15:56 |
| sdake_ | this is the r&d I was tlaking about | 15:56 |
| sdake_ | the running of the container could be done by puppet as well, this requires r&d | 15:56 |
| inc0 | slagle, we will just mount folder from host:/opt/kolla/openstack/keystone/ from host to container, and then cp /opt/kolla/openstack/keystone/keystone.conf /etc/keystone | 15:57 |
| slagle | i see | 15:57 |
| inc0 | and whatever was in this keystone.conf (even Lorem ipsum) will land in /etc | 15:57 |
| sdake_ | hopefully it doesn't convert my ipman quote into "Horizontal." :) | 15:57 |
| slagle | inc0: i'm not sure the puppet openstack modules are setup with this flexibility. | 15:57 |
| inc0 | slagle, they have to generate config somehow right? | 15:58 |
| slagle | sure, but they expect to do things like install packages, restart services, sync db's, etc | 15:58 |
| slagle | especially if you were to make a change to keystone.conf | 15:58 |
| sdake_ | right, the config step isn't broken out into one concrete piece | 15:58 |
| inc0 | mhm, then we would have to decouple all additional logic | 15:58 |
| sdake_ | we being the puppet community in this case :) | 15:59 |
| slagle | right, so i guess that's what i'm trying to understand | 15:59 |
| slagle | this was a huge stumbling block for tripleo IMO | 16:00 |
| sdake_ | which part slagle | 16:00 |
| slagle | just saying we integrated with puppet/chef/whatever, didn't actually turn out to be true | 16:00 |
| slagle | so i'm just trying to understand what mode 2/3 is actually going to enalbe someone to do | 16:00 |
| sdake_ | slagle can you ping dprince to join the convo | 16:00 |
| sdake_ | mode 2/3 do no configuration | 16:01 |
| sdake_ | they just copy the config file on the host into the container and start the service | 16:01 |
| sdake_ | the service is installed in the docker fiels during the container build operation | 16:01 |
| sdake_ | http://blog.circleci.com/its-the-future/ | 16:02 |
| *** jtriley has joined #kolla | 16:02 | |
| slagle | lol | 16:02 |
| sdake_ | worth a read if you haven't :) | 16:02 |
| sdake_ | so basically puppet/chef/whatever do a whole bunch of things all in order | 16:03 |
| sdake_ | like install packages, sync db, etc | 16:04 |
| sdake_ | install packages -> dockerfile | 16:04 |
| slagle | but you wouldn't want to do any of that on the host | 16:04 |
| sdake_ | run service -> start.sh | 16:04 |
| sdake_ | agree | 16:04 |
| sdake_ | but you solved this problem for tripleo, how? | 16:04 |
| *** bmace has quit IRC | 16:05 | |
| slagle | what problem? we run puppet apply on the host itself | 16:05 |
| slagle | if it's a compute node, we appy the puppet manifests for nova compute, etc | 16:05 |
| sdake_ | you said it was a stumbling block? | 16:05 |
| sdake_ | we dont want to create more hurdles | 16:05 |
| slagle | the stumbling block was saying "this works with puppet/ansible/chef" without anyone actually validating that | 16:06 |
| *** bmace has joined #kolla | 16:06 | |
| slagle | as it turns out, the interface was actually quite poor to non-existant | 16:06 |
| slagle | we didn't start to refine the interface until we started to think about and actually making it work with a 2nd implementation | 16:06 |
| slagle | that's really what proved it out | 16:07 |
| slagle | so (i don't mean to nitpick)...but if kolla says mode 2/3 is going to enable all these things...i'm just curious what that actually looks like | 16:07 |
| slagle | is puppet enabled if i go off and write a bunch of custom puppet? | 16:07 |
| sdake_ | it is going to enable them for ansible | 16:07 |
| slagle | or do the puppet openstack modules just plug in | 16:07 |
| sdake_ | i suspect that would be an r&d exercise upstream slagle | 16:08 |
| slagle | yea, i think i've got that now :) | 16:08 |
| sdake_ | the ansible part, we are handling | 16:09 |
| sdake_ | brb need to switch networks | 16:10 |
| *** sdake has joined #kolla | 16:11 | |
| *** mstachow has quit IRC | 16:13 | |
| sdake | slagle if mode 1 is not viable long term for tripleo | 16:13 |
| sdake | and mode 2&3 require puppet r&d which our community is unequiped to contirbute to | 16:13 |
| sdake | what do you suggest ;) | 16:13 |
| slagle | 1) tripleo continues to use mode 1 so we can see how viable long term it might be | 16:14 |
| slagle | 2) we involve the tripleo/puppet folks to see what the r&d entails | 16:14 |
| *** sdake_ has quit IRC | 16:14 | |
| slagle | at that point, we could probably make a decision about going with mode 2/3 long term | 16:14 |
| sdake | wfm | 16:15 |
| slagle | like i said, not a concrete answer :) | 16:15 |
| sdake | related question about big tent | 16:15 |
| slagle | i do think though that the puppet folks are interested in container integration and making the modules work with containers | 16:15 |
| sdake | how does tripleo intend to handle big tent new components | 16:15 |
| slagle | we'll deploy them if theres interest | 16:16 |
| slagle | but tripleo isn't just adding everything big tent just for fun | 16:16 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images https://review.openstack.org/190117 | 16:17 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Add base image for oraclelinux https://review.openstack.org/191013 | 16:17 |
| sdake | kolla is adding all openstack namespaced projects just for kicks | 16:17 |
| sdake | atleast long term | 16:17 |
| sdake | i could put a requirement in there "dont do in-container config for new containers" | 16:17 |
| sdake | this would drastically reduce the amount of work we have to do | 16:17 |
| sdake | and we could address the ones you have interest in on an as needed basis | 16:18 |
| slagle | i think that would be fine | 16:18 |
| slagle | i'm not going to ask people to do more work just for tripleo's sake, when i don't even know if it would ever be used | 16:18 |
| sdake | slagle can we somehow get the puppet cats engaged in this conversation | 16:19 |
| sdake | sooner rather then later | 16:19 |
| sdake | so we can get to a decision point about mode 1 deprecation (if there is to be one) sooner rather then later | 16:19 |
| slagle | sure, i can ask | 16:19 |
| slagle | i can't speak for when anyoen would actually do it | 16:20 |
| sdake | yar | 16:20 |
| sdake | who can speak for anyone else? | 16:20 |
| sdake | Ican't even speak for my 10 and 12 year olds :) | 16:20 |
| inc0 | let's just try to scope out how much work that would be | 16:20 |
| sdake | yar if we can get a viable technical plan in place that would be helpful | 16:21 |
| sdake | slagle thanks for your time this conversation has been emmensly helpful | 16:23 |
| slagle | yep, thanks as well. i'll read over the spec and ping folks on it today | 16:24 |
| sdake | the second version will look drastically different from the first | 16:24 |
| sdake | be prepared :) | 16:24 |
| sdake | it is based upon a week of open debate on irc + the review | 16:24 |
| *** jtriley has quit IRC | 16:25 | |
| *** daneyon has joined #kolla | 16:26 | |
| *** dasm is now known as dasm|afk | 16:26 | |
| *** daneyon has quit IRC | 16:26 | |
| *** daneyon has joined #kolla | 16:27 | |
| inc0 | uhh, fruitful discussions | 16:27 |
| inc0 | let's start another one! 127.0.0.0/24 as private network for endpoints?:) | 16:28 |
| inc0 | for gates? | 16:28 |
| sdake | brain tired | 16:28 |
| sdake | need to refresh :) | 16:28 |
| inc0 | haha | 16:28 |
| inc0 | I'll think also how to build gates based on option 2/3 | 16:29 |
| inc0 | I mean we probably will just end up providing hardcoded config on infra | 16:29 |
| sdake | if you use the flat interface for the routed internet network, you lose connectivity to the vm | 16:30 |
| inc0 | why do we need connectivity at the end? | 16:31 |
| inc0 | once we build all? | 16:31 |
| inc0 | uh, nvm, giving any test feedback is useful | 16:32 |
| sdake | ya we need to know the tests success or failure :) | 16:32 |
| inc0 | we need to dig out how neutron does that | 16:33 |
| sdake | they do it via single nic via ovs via the unblocked workflow i've sorted out :) | 16:34 |
| sdake | it cannot be done apparently with linuxbridge | 16:34 |
| *** jtriley has joined #kolla | 16:36 | |
| *** fangfenghua has joined #kolla | 16:37 | |
| *** fangfenghua has quit IRC | 16:42 | |
| jpeeler | sdake: if this patch gets merged one day (https://github.com/docker/docker/pull/13525) would you be opposed to running systemd in containers? | 16:47 |
| sdake | in kolla containers? | 16:52 |
| sdake | pretty much, kolla uses thin containers | 16:52 |
| sdake | i.e. one process per container | 16:53 |
| jpeeler | yes, i know how it works now | 16:54 |
| openstackgerrit | Paul Bourke proposed stackforge/kolla: Symlink all non Dockerfile resources in images https://review.openstack.org/190117 | 16:54 |
| sdake | oh for some reason I saw jpeeler and read "slagle" | 16:54 |
| sdake | brain malfunction :) | 16:54 |
| sdake | jpeeler why doth thou ask :) | 16:55 |
| jpeeler | i assume this post is still relevant: https://blog.phusion.nl/2015/01/20/docker-and-the-pid-1-zombie-reaping-problem/ | 16:55 |
| jpeeler | that's why i ask | 16:55 |
| sdake | there are might lighter weight solutions to solve that problem then starting 20+ processes | 16:56 |
| sdake | even supervisord is a superior solution | 16:56 |
| jpeeler | sure, it doesn't have to be systemd necessarily | 16:56 |
| pbourke | jpeeler: the docker baseimage guys dont get containers imo... | 16:57 |
| sdake | if you read that blog they have a nice tidy 200 line python program that solves it | 16:57 |
| sdake | i am open to solving the zombie reaping problem but not really with systemd | 16:58 |
| sdake | reason being systemd will start all the stuff in the /lib/systemd directories on start | 16:58 |
| sdake | which is huge bloat for a container | 16:58 |
| sdake | if systemd didn't do that,i'd probably have a different viewpoint | 16:58 |
| jpeeler | pbourke: maybe i don't either! what makes you say that? | 16:59 |
| pbourke | jpeeler: i haven't read the blog you posted (yet) it maybe makes some good points. but I find https://phusion.github.io/baseimage-docker/ sort of annoying | 17:01 |
| pbourke | anyway have to head home, conversation for another day :) sdake, I rebased the symlink so it should be hopefully good to go | 17:03 |
| pbourke | *symlink patch | 17:05 |
| *** dwalsh has quit IRC | 17:07 | |
| openstackgerrit | Harm Weites proposed stackforge/kolla: Check if tools/genenv binary dependencies are met. https://review.openstack.org/191580 | 17:10 |
| harmw | mandre: you were absolutely right! | 17:10 |
| harmw | I took the wrong file :) | 17:10 |
| rhallisey | harmw, updated the cinder container | 17:16 |
| *** nihilifer has joined #kolla | 17:17 | |
| harmw | yea, just looking through my e-mail :) | 17:17 |
| rhallisey | no prob, thanks man | 17:18 |
| harmw | ah yes, the massive cinder review | 17:21 |
| harmw | I remember that | 17:21 |
| harmw | :p | 17:21 |
| *** jasonsb has joined #kolla | 17:24 | |
| *** dwalsh has joined #kolla | 17:24 | |
| jpeeler | sdake: I just updated https://review.openstack.org/#/c/191133/, but I can't decide if that's right or not | 17:27 |
| *** dims has quit IRC | 17:27 | |
| jpeeler | after reading: http://docs.openstack.org/infra/system-config/zuul.html | 17:27 |
| *** dims has joined #kolla | 17:28 | |
| jpeeler | the question is, do we think people will be uploading broken images? if not, then the review is good. if we do, then maybe putting the job in the check section is better than waiting on core reviews to get verification | 17:28 |
| harmw | never trust input or users! | 17:28 |
| jpeeler | well ultimately we don't! it's just a matter of when the feedback comes. one is faster merge time if we assume people are mostly good | 17:29 |
| *** jasonsb has quit IRC | 17:29 | |
| jpeeler | in fact, it's theoretically at least double the speed... | 17:30 |
| harmw | rhallisey: it scares me I discovered new 'issues' :p | 17:38 |
| harmw | *again | 17:38 |
| harmw | anyway, nothing big but one or two functional things | 17:39 |
| rhallisey | harmw, I'll look | 17:39 |
| rhallisey | harmw, :) I didn't know how copy works never used it | 17:40 |
| harmw | :) | 17:41 |
| *** fangfenghua has joined #kolla | 17:43 | |
| *** shardy_ has joined #kolla | 17:44 | |
| *** mstachow has joined #kolla | 17:45 | |
| *** shardy has quit IRC | 17:45 | |
| *** fangfenghua has quit IRC | 17:48 | |
| *** shardy_ has quit IRC | 17:50 | |
| *** shardy has joined #kolla | 17:51 | |
| *** jasonsb has joined #kolla | 17:55 | |
| sdake | jpeeler I saw but I don't know either | 17:58 |
| sdake | look at how you reverted it? | 17:58 |
| sdake | oh it should be a check as well | 17:58 |
| *** jasonsb has quit IRC | 18:00 | |
| jpeeler | ... so you mean you expect people to submit broken images? | 18:22 |
| sdake | it could happen | 18:25 |
| sdake | anything that has a gate should have a check imo :) | 18:25 |
| jpeeler | that sort of defeats the point of the check pipeline | 18:27 |
| jpeeler | maybe i'm misunderstanding, no idea why you would run the exact same tests. what am i missing? | 18:28 |
| *** sdake_ has joined #kolla | 18:29 | |
| sdake_ | jpeeler the check pipeline tells the core reviewers a patch is ready for review | 18:30 |
| sdake_ | jpeeler the gate pipeline tells gerrit the patch si ready for merge | 18:30 |
| sdake_ | that is the significant difference | 18:31 |
| sdake_ | make sense? | 18:31 |
| jpeeler | yes | 18:33 |
| jpeeler | i guess it's possible that code changes underneath that wouldn't require a rebase to the review gives value to double testing | 18:33 |
| jpeeler | that's something i just realized (if it's correct) | 18:33 |
| sdake_ | that is a technical reason but you asked why have two :) | 18:33 |
| *** sdake has quit IRC | 18:34 | |
| jpeeler | yes, i couldn't figure out the value. but now i can! i have to understand why i do things most of the time. not trying to be a pain! | 18:34 |
| sdake_ | all good | 18:35 |
| sdake_ | i'm here to please :) | 18:35 |
| *** jasonsb has joined #kolla | 18:37 | |
| *** mstachow has quit IRC | 18:41 | |
| openstackgerrit | Michal Rostecki proposed stackforge/kolla: [WIP] Add designate-sink service https://review.openstack.org/189393 | 18:47 |
| *** fangfenghua has joined #kolla | 18:50 | |
| *** mugsie has joined #kolla | 18:52 | |
| mugsie | nihilifer: hey - you around? | 18:53 |
| harmw | oh noes, designate ppl here! | 18:53 |
| mugsie | harmw: we are like a stray dog | 18:54 |
| harmw | :p | 18:54 |
| mugsie | just follow you around if you talk to us :) | 18:54 |
| *** fangfenghua has quit IRC | 18:54 | |
| harmw | haha | 18:54 |
| *** dwalsh has quit IRC | 18:56 | |
| mugsie | maybe you can anser one thing harmw - https://review.openstack.org/#/c/189393 - none of the domain names have trailing dots (eg. "example.com.") | 18:58 |
| mugsie | how are the designate client calls succeeding? is there a wrapper somewhere I cant see thats is appending it? | 18:58 |
| harmw | trailing dots are most probably not there | 18:58 |
| harmw | good one | 18:58 |
| harmw | this is the only designate container where it actually creates domains and such, and I missed it | 19:00 |
| harmw | damn | 19:00 |
| mugsie | :) | 19:00 |
| harmw | I still need to go through that code again, so I'll add a comment :) | 19:01 |
| harmw | *over | 19:01 |
| nihilifer | mugsie: yes | 19:01 |
| mugsie | it was disccusion on the designate sink container patch ^ | 19:01 |
| mugsie | was confusing myself | 19:01 |
| *** absubram has quit IRC | 19:01 | |
| mugsie | but it seems you *are* missing the trailing dots | 19:02 |
| nihilifer | yes, nice catch, will add the dots | 19:02 |
| mugsie | to be fair, it is the one thing that gets everyone when they use designate | 19:03 |
| harmw | lol, yes sire to that ! :p | 19:03 |
| mugsie | even me sometimes, even though I wrote the majority of the v2 API, and called it 100s of times a day | 19:04 |
| nihilifer | I was adding dots when I runned this container with my environment, that's the worst thing :P | 19:06 |
| *** dwalsh has joined #kolla | 19:09 | |
| mugsie | :D | 19:09 |
| openstackgerrit | Michal Rostecki proposed stackforge/kolla: [WIP] Add designate-sink service https://review.openstack.org/189393 | 19:11 |
| openstackgerrit | Michal Rostecki proposed stackforge/kolla: [WIP] Add designate-sink service https://review.openstack.org/189393 | 19:19 |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Cinder container https://review.openstack.org/170965 | 19:23 |
| inc0 | good night everyone | 19:24 |
| *** inc0 has quit IRC | 19:24 | |
| *** mstachow has joined #kolla | 19:28 | |
| *** mstachow has quit IRC | 19:47 | |
| *** fangfenghua has joined #kolla | 19:54 | |
| *** sdake has joined #kolla | 19:54 | |
| *** gfidente has quit IRC | 19:58 | |
| *** sdake_ has quit IRC | 19:58 | |
| *** daneyon_ has joined #kolla | 19:59 | |
| *** fangfenghua has quit IRC | 19:59 | |
| *** sdake_ has joined #kolla | 20:01 | |
| *** daneyon has quit IRC | 20:02 | |
| *** sdake has quit IRC | 20:05 | |
| *** nihilifer has quit IRC | 20:38 | |
| openstackgerrit | Steven Dake proposed stackforge/kolla: Ansible multi-node specification https://review.openstack.org/189157 | 20:43 |
| *** sdake has joined #kolla | 20:44 | |
| *** sdake_ has quit IRC | 20:48 | |
| *** mstachow has joined #kolla | 20:52 | |
| *** dims_ has joined #kolla | 20:56 | |
| jpeeler | it appears ironic also requires openvswitch | 20:57 |
| sdake | samyaple is on it | 20:58 |
| sdake | first we neeed to de-fatify neutron | 20:58 |
| sdake | which he is working on atm | 20:58 |
| jpeeler | yeah, maybe it'll be done by the time i'm ready to test | 20:59 |
| *** fangfenghua has joined #kolla | 20:59 | |
| sdake | i think he has openvswitch working | 20:59 |
| sdake | but it conflicts with the neutron agent container | 20:59 |
| sdake | how do you know ironic requires ovs? | 21:00 |
| sdake | is that documented somewhere? | 21:00 |
| jpeeler | http://docs.openstack.org/developer/ironic/deploy/install-guide.html#configure-neutron-to-communicate-with-the-bare-metal-server | 21:00 |
| *** dims has quit IRC | 21:00 | |
| *** dims_ has quit IRC | 21:00 | |
| sdake | only documented forovs | 21:01 |
| jpeeler | neutron is the last thing to configure before trying to figure out the PXE stuff | 21:01 |
| sdake | jpeeler take a stab at the ansible-multi spec :) | 21:02 |
| openstackgerrit | imain proposed stackforge/kolla: Set up glance to use a data container. https://review.openstack.org/191975 | 21:03 |
| daneyon_ | jpeller do u have a sec? | 21:04 |
| *** fangfenghua has quit IRC | 21:04 | |
| jpeeler | daneyon_: what's up | 21:05 |
| daneyon_ | Re: https://review.openstack.org/#/c/189974/3 | 21:05 |
| daneyon_ | Looks like the patch works when using the binary images but not the centos/rdo images | 21:05 |
| daneyon_ | would you like me to submit an updated PS with the centos/rdo fixes? | 21:06 |
| jpeeler | sure, but i'm confused. you're talking about in the docker directory with the rdo symlinking to binary? which binary images are you referring to? | 21:07 |
| *** rhallisey has quit IRC | 21:07 | |
| daneyon_ | I'm probably confused with the new DIR structure of the project. What is the diff between docker/centos/binary and docker/centos/rdo | 21:09 |
| jpeeler | i didn't think there was any currently | 21:10 |
| daneyon_ | So right now rdo images are using images from binary | 21:10 |
| *** dwalsh has quit IRC | 21:10 | |
| daneyon_ | why is rdo a sym to binary? | 21:10 |
| daneyon_ | should i use docker/centos/binary for building images and not docker/centos/rdo? | 21:11 |
| jpeeler | i really thought currently they were supposed to function exactly the same. i can't remember which i used | 21:11 |
| * jpeeler looks for a commit | 21:12 | |
| jpeeler | https://github.com/stackforge/kolla/commit/13062e23e86b5d86020949754540460cb5b0b4fe | 21:14 |
| jpeeler | the idea i thought was to eventually have source installs | 21:14 |
| jpeeler | what breaks when using the rdo directory? | 21:14 |
| daneyon_ | ok, i think i get it now. let me try your patch again, recheck and i'll let you know if i have any problems. thx | 21:16 |
| *** jasonsb has quit IRC | 21:17 | |
| sdake | jpeeler the plan is to be abel to select base container os and select source/binary and have the right thing happen | 21:26 |
| sdake | jpeeler rhallisey can you guys take a look at https://review.openstack.org/#/c/189157/ with tripleo in mind | 21:33 |
| sdake | jtriley if you want to take a look with puppet in mind that would be helpful too :) | 21:33 |
| jtriley | sdake: yep i'll give this a look when I get a chance | 21:34 |
| *** dims has joined #kolla | 21:35 | |
| *** jtriley_ has joined #kolla | 21:38 | |
| *** rhallisey has joined #kolla | 21:38 | |
| sdake | rhallisey can you take a look at https://review.openstack.org/#/c/189157/ with an eye towards triipleo when you hve a moment | 21:39 |
| sdake | it is a bit different then take 1 :) | 21:39 |
| rhallisey | I'll take a look tmr | 21:40 |
| rhallisey | or later.. I gota head home | 21:40 |
| sdake | wfm | 21:40 |
| sdake | thanks | 21:40 |
| sdake | good work on cinde as well :) | 21:40 |
| sdake | now just need to make it thin :) | 21:40 |
| rhallisey | thanks | 21:40 |
| *** rhallisey has quit IRC | 21:41 | |
| *** jtriley has quit IRC | 21:41 | |
| *** jasonsb has joined #kolla | 21:42 | |
| *** jtriley_ has quit IRC | 21:42 | |
| *** jasonsb has quit IRC | 21:43 | |
| *** rhallisey has joined #kolla | 21:46 | |
| openstackgerrit | Ryan Hallisey proposed stackforge/kolla: Cinder container https://review.openstack.org/170965 | 21:57 |
| *** fangfenghua has joined #kolla | 22:05 | |
| *** fangfenghua has quit IRC | 22:09 | |
| jpeeler | sdake: i'll look at it later on tonight | 22:12 |
| sdake | jpeeler wfm | 22:17 |
| *** dims has quit IRC | 22:34 | |
| *** jtriley has joined #kolla | 22:35 | |
| *** pbourke has quit IRC | 22:43 | |
| *** pbourke has joined #kolla | 22:44 | |
| *** Haomeng|2 has joined #kolla | 22:50 | |
| *** rhallisey has quit IRC | 22:53 | |
| *** Haomeng has quit IRC | 22:53 | |
| *** diogogmt has quit IRC | 22:53 | |
| sdake | pbourke around? | 22:57 |
| *** dims has joined #kolla | 23:03 | |
| *** dims has quit IRC | 23:03 | |
| *** dims has joined #kolla | 23:04 | |
| openstackgerrit | Daneyon Hansen proposed stackforge/kolla: Fixes MariaDB to Support Heat https://review.openstack.org/192011 | 23:10 |
| sdake | loth you about | 23:19 |
| loth | Whats up? | 23:20 |
| sdake | mind taking a look at https://review.openstack.org/#/c/189157/ with a vote :) | 23:22 |
| *** blahRus has quit IRC | 23:29 | |
| *** jtriley has quit IRC | 23:29 | |
| *** diogogmt has joined #kolla | 23:30 | |
| *** jtriley has joined #kolla | 23:33 | |
| *** daneyon_ has quit IRC | 23:43 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!