*** hfu_ has joined #openstack-kolla | 00:00 | |
*** hfu has quit IRC | 00:01 | |
*** hfu_ has quit IRC | 00:13 | |
*** sdake has joined #openstack-kolla | 00:15 | |
*** sdake_ has joined #openstack-kolla | 00:18 | |
*** sdake has quit IRC | 00:19 | |
*** jtriley has joined #openstack-kolla | 00:35 | |
*** jtriley has quit IRC | 00:41 | |
*** tovin07 has joined #openstack-kolla | 00:48 | |
*** yingjun has joined #openstack-kolla | 00:49 | |
*** tovin07_ has joined #openstack-kolla | 00:49 | |
*** zhubingbing has joined #openstack-kolla | 00:59 | |
sdake_ | zhubingbing sup dude | 01:01 |
---|---|---|
zhubingbing | hi | 01:01 |
zhubingbing | good morning | 01:01 |
sdake_ | say, are you interested in tackling monasca | 01:01 |
zhubingbing | yeah | 01:02 |
sdake_ | its really hard i think because htey have a bajillion repos | 01:02 |
sdake_ | i'd like to see it in action | 01:02 |
zhubingbing | np | 01:03 |
zhubingbing | I will integrate it into kolla | 01:03 |
zhubingbing | https://wiki.openstack.org/wiki/Monasca | 01:03 |
*** tovin07 has quit IRC | 01:04 | |
zhubingbing | this week,i will finish it | 01:04 |
sdake_ | well i wouldn't put such a tight timer on it | 01:06 |
sdake_ | it will probably take awhile | 01:06 |
sdake_ | it has a slew of dependencies | 01:06 |
zhubingbing | understand | 01:06 |
zhubingbing | I'll deal with it as the top priority. | 01:07 |
sdake_ | zhubingbing also do you have any interest in learning about kubernetes arches? | 01:07 |
sdake_ | top priority is actually probably barbican - to enable magnum security | 01:07 |
zhubingbing | K8s I was very familiar with it. | 01:07 |
zhubingbing | ;) | 01:07 |
sdake_ | ya i was too | 01:07 |
sdake_ | its changed quite a bit | 01:07 |
sdake_ | reason i ask is we have the kolla-kubernetes work as well | 01:08 |
sdake_ | atm we aer cranking out helm charts | 01:08 |
zhubingbing | I've done k8s related work 6month ago | 01:08 |
sdake_ | which is a whole new brave world to learn | 01:08 |
*** goldyfruit has joined #openstack-kolla | 01:10 | |
*** portdirect is now known as harbor | 01:13 | |
*** tonanhngo has joined #openstack-kolla | 01:13 | |
*** tonanhngo has quit IRC | 01:16 | |
openstackgerrit | Li Yingjun proposed openstack/kolla-ansible: Update repo in documentation https://review.openstack.org/400017 | 01:17 |
*** tovin07 has joined #openstack-kolla | 01:17 | |
*** zhurong has joined #openstack-kolla | 01:27 | |
*** jtriley has joined #openstack-kolla | 01:30 | |
*** jtriley has quit IRC | 01:36 | |
*** sdake_ has quit IRC | 01:37 | |
*** hfu has joined #openstack-kolla | 01:37 | |
*** hfu has quit IRC | 01:40 | |
*** brad[] has quit IRC | 01:40 | |
*** hfu has joined #openstack-kolla | 01:41 | |
*** brad[] has joined #openstack-kolla | 01:42 | |
*** hieulq has joined #openstack-kolla | 01:44 | |
*** sdake has joined #openstack-kolla | 01:46 | |
*** Pavo has quit IRC | 01:47 | |
sdake | sbezverk about? | 01:47 |
sbezverk | sdake: yes but for 2 minutes, what is up? | 01:50 |
sdake | nothing just wondering why working on a sunday :) | 01:51 |
sdake | saw your review of rabbitmq | 01:51 |
sdake | ;) | 01:51 |
sdake | !!!does not need reviews!!! | 01:51 |
openstack | sdake: Error: "!!does" is not a valid command. | 01:51 |
*** Pavo has joined #openstack-kolla | 01:52 | |
sbezverk | sdake: :-) I needed to push it so I could get on another host where I do debugging | 01:52 |
sdake | cool | 01:52 |
sdake | i am going to copy that structure for mariadb | 01:52 |
sbezverk | as soon as I clean it up I will remove first line | 01:52 |
sbezverk | I hope I did not ofend anybody ;-) | 01:52 |
sdake | nah i thought it was funny :) | 01:53 |
sdake | enjoy sleep time ;) | 01:53 |
sbezverk | sdake: no I am watching "the medici" series.. | 01:54 |
sbezverk | my wife is a fanatic of Florence | 01:54 |
sdake | raining dogs and cats here | 01:55 |
sbezverk | sdake: well it is better than snow | 01:55 |
sdake | possible - miss four seasons | 01:55 |
sdake | although i'll never miss shoveling snow | 01:55 |
*** liyifeng_seu has joined #openstack-kolla | 01:56 | |
sbezverk | sdake: oh man do not remind me. the one winter before last was really bruttal. had to shovel almost every week | 01:56 |
sdake | dude if i lived somewhere where it snowed ever agagain | 01:57 |
sdake | snowblower | 01:57 |
sdake | no iffs ands or butts | 01:57 |
sdake | buts that is | 01:57 |
*** liyifeng has joined #openstack-kolla | 01:57 | |
sbezverk | sdake: got to go, have a great evening, talk to you tomorrow.. | 01:58 |
sdake | later dude | 01:58 |
*** jtriley has joined #openstack-kolla | 02:01 | |
*** tovin07_ has quit IRC | 02:05 | |
openstackgerrit | wangwei proposed openstack/kolla-ansible: Add remove-garbage function in kolla-ansible https://review.openstack.org/402362 | 02:06 |
*** tovin07_ has joined #openstack-kolla | 02:08 | |
*** duonghq has joined #openstack-kolla | 02:10 | |
*** tonanhngo has joined #openstack-kolla | 02:11 | |
*** jtriley has quit IRC | 02:12 | |
*** tonanhngo has quit IRC | 02:12 | |
*** goldyfruit has quit IRC | 02:16 | |
*** sdake has quit IRC | 02:21 | |
*** hfu has quit IRC | 02:22 | |
*** hfu has joined #openstack-kolla | 02:24 | |
*** Jeffrey4l has joined #openstack-kolla | 02:28 | |
*** sdake has joined #openstack-kolla | 02:35 | |
*** sdake_ has joined #openstack-kolla | 02:41 | |
*** hfu has quit IRC | 02:41 | |
*** liyifeng_seu has quit IRC | 02:45 | |
*** hfu has joined #openstack-kolla | 02:45 | |
*** sdake has quit IRC | 02:45 | |
*** liyifeng_seu has joined #openstack-kolla | 02:47 | |
*** jtriley has joined #openstack-kolla | 02:53 | |
*** tonanhngo has joined #openstack-kolla | 02:57 | |
*** zhurong has quit IRC | 02:58 | |
*** zhurong_ has joined #openstack-kolla | 02:58 | |
*** tonanhngo has quit IRC | 02:58 | |
*** tonanhngo has joined #openstack-kolla | 03:03 | |
*** tonanhngo has quit IRC | 03:07 | |
*** ayoung has joined #openstack-kolla | 03:38 | |
*** Pavo has quit IRC | 03:47 | |
*** Pavo has joined #openstack-kolla | 03:47 | |
*** hfu has quit IRC | 03:56 | |
*** f13o has quit IRC | 04:02 | |
*** jtriley has quit IRC | 04:18 | |
*** jtriley has joined #openstack-kolla | 04:18 | |
*** mdnadeem has joined #openstack-kolla | 04:28 | |
*** mdnadeem has quit IRC | 04:28 | |
*** jtriley has quit IRC | 04:30 | |
sdake_ | duonghq around? | 04:31 |
*** mdnadeem has joined #openstack-kolla | 04:31 | |
*** mdnadeem_ has joined #openstack-kolla | 04:32 | |
*** mdnadeem has quit IRC | 04:32 | |
*** jtriley has joined #openstack-kolla | 04:34 | |
*** yuanying has quit IRC | 04:57 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Add ironic-ui to horizon image https://review.openstack.org/403445 | 05:06 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Install sahara dashboard into horizon image https://review.openstack.org/403502 | 05:06 |
*** AnswerGuy has quit IRC | 05:12 | |
*** jascott1 has joined #openstack-kolla | 05:15 | |
*** jascott1 has quit IRC | 05:15 | |
*** jtriley has quit IRC | 05:17 | |
*** jtriley has joined #openstack-kolla | 05:17 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla-ansible: Enable sahara dashboard when enable_sahara is yes https://review.openstack.org/403504 | 05:24 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla-ansible: Enable sahara dashboard when enable_sahara is yes https://review.openstack.org/403504 | 05:24 |
*** jascott1 has joined #openstack-kolla | 05:35 | |
*** yingjun has quit IRC | 05:38 | |
*** yingjun has joined #openstack-kolla | 05:38 | |
*** jrist has quit IRC | 05:39 | |
*** tonanhngo has joined #openstack-kolla | 05:43 | |
*** tonanhngo has quit IRC | 05:45 | |
*** Pavo has quit IRC | 05:47 | |
*** Pavo has joined #openstack-kolla | 05:51 | |
*** hfu has joined #openstack-kolla | 05:58 | |
*** yuanying has joined #openstack-kolla | 06:02 | |
*** hfu has quit IRC | 06:04 | |
*** hfu has joined #openstack-kolla | 06:06 | |
*** hfu has quit IRC | 06:09 | |
*** hfu has joined #openstack-kolla | 06:14 | |
*** saneax-_-|AFK is now known as saneax | 06:16 | |
*** jtriley_ has joined #openstack-kolla | 06:19 | |
*** jtriley has quit IRC | 06:22 | |
sdake_ | duonghq you about | 06:30 |
*** hfu has quit IRC | 06:31 | |
duonghq | sdake_, helol | 06:31 |
duonghq | hello | 06:31 |
*** hfu has joined #openstack-kolla | 06:32 | |
sdake_ | hi fine sir | 06:32 |
sdake_ | wondering if your interested in getting your dev env setup for kolla-kubernetes dev | 06:33 |
sdake_ | requirements are workstation running linux with 16-32 gb of ram | 06:33 |
*** jtriley_ has quit IRC | 06:34 | |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Bump Ubuntu cloud-archive repo to Ocata https://review.openstack.org/403516 | 06:34 |
duonghq | you mean the minimum is 16GB of RAM? | 06:34 |
sdake_ | not sure, it works on 32gb | 06:34 |
sdake_ | we can probably make it work on 16gb if that is what you got | 06:34 |
sdake_ | it may work on 16gb out of the box | 06:34 |
duonghq | so, is there any reasons for it requires more RAM than kolla-ansible? | 06:35 |
duonghq | as I tested, the k8s does not consume much resource | 06:35 |
sdake_ | the dev environment sets up 4 virtual machines | 06:35 |
sdake_ | the 4 virtual machines make up your kubernetes cluster | 06:35 |
duonghq | hmm, so the requirements should be 4 nodes with resource for each node is ....? | 06:35 |
sdake_ | our dev environment at present is virtual | 06:36 |
sdake_ | focused towards developers that only have one server to work with | 06:36 |
sdake_ | relies on vagrant | 06:37 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla: Install cloudkitty dashboard in horizon image https://review.openstack.org/396535 | 06:37 |
sdake_ | tell me what you have to work with | 06:38 |
duonghq | so, we decided using Vagrant for kolla-k8s dev env? | 06:39 |
sdake_ | for the moment | 06:39 |
sdake_ | makes things easier, we have code ready to go for that | 06:39 |
sdake_ | and it works - i have a dev env on my gear in about 30 minutes-1hr | 06:40 |
duonghq | I do not have experience w/ Vagrant yet, still use kube-deploy to setup k8s cluster | 06:40 |
*** jtriley has joined #openstack-kolla | 06:40 | |
sdake_ | not familiar with kube-deploy | 06:40 |
sdake_ | if you have a 4 node cluster with kubernetes running on it your all set | 06:40 |
sdake_ | we don't dictate a development environment | 06:40 |
sdake_ | its only to help people that don't have acccess to multiple servers | 06:41 |
sdake_ | which is most people ;) | 06:41 |
openstackgerrit | Jeffrey Zhang proposed openstack/kolla-ansible: Enable cloudkitty ui when enable_cloudkitty is yes https://review.openstack.org/403520 | 06:41 |
duonghq | basically, developers need 4 node k8s and then everything is the same? | 06:41 |
sdake_ | right | 06:41 |
duonghq | got it | 06:41 |
sdake_ | we may need more nodes in teh future | 06:41 |
sdake_ | got it s in you have a 4 node k8s cluster? | 06:42 |
duonghq | atm, and in my company, it's easier to get 2 16GB workstation than 1 32GB ws, so I think I can test if I can get 4 VM on 1 16GB VM, it's more popular than 32GB ws? (at least for vagrant) | 06:43 |
duonghq | sdake_, yup, as many nodes as the RAM can hold on | 06:43 |
duonghq | kube-deploy is nice | 06:43 |
sdake_ | you dont need vms, you could deploy to bare metal | 06:44 |
sdake_ | not sure if vagrant can cross two nodes | 06:44 |
sdake_ | so basically you would need 4 16gb ws or 1 32gb ws | 06:44 |
sdake_ | or maybe it would run on 1 16gb ws | 06:44 |
duonghq | for many people, it should work on 1 16GB ws | 06:45 |
sdake_ | ok, well you want a walk thru on that? | 06:45 |
duonghq | sure, | 06:45 |
sdake_ | now? | 06:46 |
*** sdake_ is now known as sdake | 06:47 | |
*** jtriley has quit IRC | 06:48 | |
*** zhurong_ has quit IRC | 06:56 | |
*** zhurong has joined #openstack-kolla | 06:57 | |
*** msimonin has quit IRC | 07:02 | |
*** yuanying has quit IRC | 07:04 | |
sdake | you seek yoda! | 07:16 |
*** sdake_ has joined #openstack-kolla | 07:22 | |
*** sdake has quit IRC | 07:24 | |
*** f13o has joined #openstack-kolla | 07:30 | |
*** harbor has joined #openstack-kolla | 07:33 | |
*** harbor is now known as portdirect___ | 07:33 | |
portdirect___ | morning o/ | 07:34 |
*** Jeffrey4l has quit IRC | 07:35 | |
*** liyifeng has quit IRC | 07:37 | |
*** liyifeng has joined #openstack-kolla | 07:39 | |
duonghq | moring portdirect___ | 07:39 |
duonghq | nice to see you | 07:39 |
sdake_ | sup portdirect___ | 07:39 |
sdake_ | do you sleep ;) | 07:40 |
portdirect___ | lol, I deserved that - 7:30 am here :) | 07:40 |
sdake_ | ahh thats a normal time | 07:40 |
sdake_ | i am usually up at 6am | 07:41 |
portdirect___ | just going through logs - duonghq/sdake that vagrant setup only really requires 1gb of ram per machine when just running k8s- though i think we'll need 4gb for the workers once we have some services running | 07:42 |
sdake_ | portdirect___ cool | 07:42 |
duonghq | portdirect___, so people should have more than 16GB RAM box if they do not want swap is utilized? | 07:43 |
*** Jeffrey4l has joined #openstack-kolla | 07:43 | |
sdake_ | sp_ pingola | 07:44 |
*** hfu has quit IRC | 07:44 | |
sp_ | sdake_: | 07:44 |
sp_ | sdake_: hi | 07:44 |
sdake_ | sp_ you put your john hancock on https://github.com/openstack/kolla-kubernetes/blob/master/specs/kolla-kubernetes-arch.rst | 07:45 |
*** hfu has joined #openstack-kolla | 07:45 | |
sdake_ | sp_ if your still interested, ready to ramp you up on how to get your dev environment setup | 07:45 |
sp_ | sdake_: sure | 07:46 |
sdake_ | sp_ what type of gear do you have | 07:46 |
portdirect___ | duonghq: currently, though we only need 3 workers for ceph and mariadb - so we should be able to get a two (or even single) node setup in less than that | 07:46 |
sdake_ | sp_ typically we expect a single machine with 16gb of ram | 07:46 |
sdake_ | sp_ hopefully running centos although ubuntu should work | 07:46 |
*** Pavo has quit IRC | 07:47 | |
sp_ | sdake_: though this time dont have 16GB machine, but 1-2 day i can arrange that for env dev | 07:47 |
sdake_ | sp_ what do you have available? | 07:48 |
sp_ | sdake_: its 8gb, 2 core 100GB HDD | 07:49 |
sdake_ | portdirect___ will that work? | 07:49 |
sp_ | sdake_: yes | 07:49 |
sdake_ | sp_ running which os? | 07:51 |
portdirect___ | sdake_/sp_: wouldn't want to use that for more than a single (maybe 2) machine really - but thats still usefull. | 07:51 |
sp_ | sdake_: ubuntu 16.04 | 07:51 |
portdirect___ | sp_: virtualbox? | 07:51 |
*** Pavo has joined #openstack-kolla | 07:52 | |
sdake_ | portdirect___ ubuntu rolls with libvirt | 07:52 |
*** matrohon has joined #openstack-kolla | 07:52 | |
sdake_ | portdirect___ are ou asking if sp_ is running on bare metal? | 07:53 |
duonghq | anybody try to add gpg key manually for centos base (w/o download from server)? | 07:53 |
sdake_ | duonghq that works | 07:53 |
sdake_ | duonghq that is how it used to be setup | 07:54 |
portdirect___ | sdake_: should have phrased that better, was meaning to ask if he had (or was using) virtualbox | 07:54 |
sp_ | portdirect___: yes it is VM | 07:54 |
duonghq | but we don't have option for custom key atm? (from local file)? | 07:55 |
sdake_ | sp_ what does your bare metal look like? | 07:55 |
sdake_ | duonghq not sure, ask inc0 - he wrote all the customization stuff, I think its possible via customization to do what you want | 07:55 |
duonghq | ok, I'm reading the source code and see that code fragment, only wonder if I can get it done through kolla-build.conf | 07:56 |
sdake_ | duonghq no idea - not sure its documented | 07:56 |
duonghq | roger | 07:56 |
sp_ | sdake_: are you talking about H/W spec. Seems like i didn't get you | 07:57 |
Jeffrey4l | duonghq, a workaround https://github.com/openstack/kolla-ansible/blob/master/tools/setup_gate.sh#L49 | 07:57 |
sdake_ | sp_ yup hardware spec | 07:58 |
sdake_ | yo uwill want to run the dev env on bare metal | 07:58 |
sdake_ | because it uses virtual machines | 07:59 |
sdake_ | virt on virt on virt not ideal ;) | 07:59 |
sdake_ | we got virt for your virt for your containers to run virt in, YO DAWG! | 07:59 |
portdirect___ | vagrant can also pull the strings on via openstack - never tried it though | 08:00 |
sp_ | sdake_: ok, i will try to arrange it soon and will make sure that env get setup | 08:00 |
sdake_ | sp_ you will need help setting up the env | 08:00 |
sdake_ | as it is undocumented | 08:00 |
sdake_ | our deadline is 20th for ocata-2 | 08:00 |
sdake_ | we dont hvae alot of time to jerk around :) | 08:00 |
*** DTadrzak has joined #openstack-kolla | 08:01 | |
portdirect___ | sdake, what should my prority be this morning? documenting the dev env? | 08:01 |
sp_ | sdake_: roger | 08:01 |
duonghq | Jeffrey4l, thank you, | 08:01 |
sdake_ | portdirect___ nah srwilkers is doing that | 08:02 |
portdirect___ | great :) | 08:02 |
sdake_ | portdirect___ i dunno what your priority should be | 08:02 |
sdake_ | work on what you think is important :) | 08:02 |
*** tonanhngo has joined #openstack-kolla | 08:02 | |
portdirect___ | did you manage to have time to look at maridb? | 08:02 |
sdake_ | portdirect___ i looked at the k8s templates | 08:03 |
sdake_ | looked like greek to me :) | 08:03 |
sdake_ | but i'll get to it tomorrow morning | 08:03 |
sdake_ | it is afterall sunday | 08:03 |
sdake_ | ;) | 08:03 |
sdake_ | and i've totally brain dumped since thursday | 08:04 |
*** tonanhngo has quit IRC | 08:04 | |
portdirect___ | :) | 08:04 |
sdake_ | portdirect___ one thing we need is to ramp up peoples dev environments | 08:04 |
sdake_ | duonghq and sp_ are interested in contributing | 08:04 |
sdake_ | sp_ may i guide you to the following launchpad | 08:05 |
portdirect___ | great - duonghq/sp_ hit me up if you need anything | 08:05 |
duonghq | sure, portdirect___ | 08:05 |
duonghq | what is your tz, portdirect___? | 08:05 |
portdirect___ | sp_: I may be able to get you some hardware in an hour once I'm in the office if that helps | 08:05 |
portdirect___ | duonghq: GMT | 08:05 |
duonghq | roger | 08:06 |
sdake_ | https://launchpad.net/kolla-kubernetes/+milestone/ocata-2 | 08:06 |
*** yingjun has quit IRC | 08:07 | |
sdake_ | sp_ if you want to choose a thing to work on that would rock :) | 08:07 |
sp_ | sdake_: ok | 08:08 |
sdake_ | sp_ are you in the drivers team? if not, what is your launchpad id | 08:09 |
sp_ | sdake_: yes I am in driver team | 08:09 |
*** jtriley has joined #openstack-kolla | 08:09 | |
sdake_ | sp_ nic | 08:09 |
sdake_ | e | 08:09 |
sp_ | sdake_: yes | 08:10 |
sdake_ | anyone else in channel interested in contributing to kolla-kubernetes at this time? | 08:10 |
sp_ | sdake_: nic "sp_" | 08:10 |
berendt | morning | 08:11 |
*** shardy has joined #openstack-kolla | 08:11 | |
sdake_ | sup berendt | 08:12 |
*** jtriley has quit IRC | 08:15 | |
berendt | opened a wishlist bug for nova vmware driver a few days ago and they implemented the features as requested 2 days later. very cool. | 08:15 |
sdake_ | berendt i thought nova already had a vmware driver? | 08:19 |
berendt | yes of course, i needed a new config parameter to be able to change the scheduling behavior | 08:19 |
sdake_ | i see | 08:19 |
sdake_ | nice | 08:20 |
*** egonzalez90 has joined #openstack-kolla | 08:20 | |
sdake_ | sup egonzalez90 | 08:20 |
sdake_ | you are beaten | 08:20 |
sdake_ | its useless to resist | 08:20 |
sdake_ | don't let yourself be destroyed as obi-one did! | 08:20 |
duonghq | Jeffrey4l, the workaround only disable apt key check, but if the key cannot be retrieved, the build process still fails? | 08:21 |
egonzalez90 | morning | 08:21 |
sdake_ | ok peeps well got to hit the rack | 08:22 |
Jeffrey4l | duonghq, sorry, didn't u want add some file into images? | 08:22 |
duonghq | Jeffrey4l, I want to add some key the to image | 08:22 |
portdirect___ | laters sdake_ | 08:22 |
sdake_ | portdirect___ if you see folks kicking around that are signed up as contributors on the specification, could you get them setup dev env wise? | 08:22 |
duonghq | Jeffrey4l, got you idea | 08:22 |
duonghq | thank you | 08:22 |
Jeffrey4l | duonghq, add the file and import it ;) | 08:22 |
portdirect___ | np - I'll be communiting for the next 45 - but will be here for the rest of the day | 08:23 |
sdake_ | portdirect___ roger - ok night all | 08:23 |
*** sdake_ has quit IRC | 08:23 | |
*** yingjun has joined #openstack-kolla | 08:28 | |
openstackgerrit | Vladislav Belogrudov proposed openstack/kolla-ansible: Add tool to merge passwords during release upgrade https://review.openstack.org/402534 | 08:32 |
openstackgerrit | Merged openstack/kolla-ansible: Update repo in documentation https://review.openstack.org/400017 | 08:40 |
*** portdirect___ has quit IRC | 08:48 | |
openstackgerrit | jimmygc proposed openstack/kolla: Add strongswan/openswan package to vpn-agent source image Lacking of strongswan/openswan package make it impossible to use create vpn connections on images built from source. Adding strongswan/openswan package fixes this bug. https://review.openstack.org/403561 | 08:50 |
*** unicell1 has joined #openstack-kolla | 08:55 | |
*** unicell has quit IRC | 08:57 | |
*** jtriley has joined #openstack-kolla | 09:03 | |
openstackgerrit | zhubingbing proposed openstack/kolla-ansible: Fix kibana command path error https://review.openstack.org/403569 | 09:05 |
*** jtriley has quit IRC | 09:09 | |
*** Serlex has joined #openstack-kolla | 09:13 | |
berendt | neutron vpnaas is not loger part of the neutron governance, we should keep this in mind | 09:16 |
*** portdirect_away is now known as portdirect | 09:17 | |
berendt | Besides, I fear my implementation in kolla has never worked properly :( | 09:17 |
*** DTadrzak has quit IRC | 09:20 | |
*** nradojevic has joined #openstack-kolla | 09:21 | |
openstackgerrit | Vladislav Belogrudov proposed openstack/kolla-ansible: Add tool to merge passwords during release upgrade https://review.openstack.org/402534 | 09:23 |
*** gfidente has joined #openstack-kolla | 09:24 | |
*** mgoddard has joined #openstack-kolla | 09:24 | |
*** rmart04 has joined #openstack-kolla | 09:36 | |
*** liyifeng has quit IRC | 09:42 | |
*** liyifeng_seu has quit IRC | 09:42 | |
*** yingjun has quit IRC | 09:43 | |
*** yingjun has joined #openstack-kolla | 09:43 | |
*** DTadrzak has joined #openstack-kolla | 09:43 | |
*** yingjun has quit IRC | 09:46 | |
nradojevic | Hi there, I want to deploy an additional neutron container (lbaas) into my environment. I built the neutron images and started a deployment for neutron, but this did not affect my old neutron containers. Now I have the problem that I get a new UID for the neutron user in the lbaas container, but in the old ones there is still the old UID. Is there a way to handle this without deleting all neutron containers? | 09:46 |
*** yingjun has joined #openstack-kolla | 09:46 | |
*** Pavo has quit IRC | 09:47 | |
*** athomas has joined #openstack-kolla | 09:47 | |
*** mdnadeem_ has quit IRC | 09:50 | |
*** yingjun has quit IRC | 09:51 | |
*** Pavo has joined #openstack-kolla | 09:51 | |
*** mdnadeem_ has joined #openstack-kolla | 09:53 | |
*** jtriley has joined #openstack-kolla | 09:58 | |
*** hfu has quit IRC | 09:59 | |
*** zhurong has quit IRC | 10:02 | |
*** jtriley has quit IRC | 10:03 | |
*** mgoddard_ has joined #openstack-kolla | 10:03 | |
*** jascott1 has quit IRC | 10:05 | |
*** mgoddard has quit IRC | 10:06 | |
*** DTadrzak has quit IRC | 10:09 | |
nradojevic | Any ideas? | 10:14 |
*** stevemar has quit IRC | 10:19 | |
pbourke | berendt: vpnaas works fine, I tested it just last week | 10:20 |
pbourke | berendt: well a few patches were needed for redhat but overall it works | 10:20 |
berendt | pbourke: good to know, thanks | 10:20 |
berendt | I am actually not sure if we should deprecate the feature because of the missing neutron governance | 10:20 |
pbourke | berendt: na I think we should keep it unless it goes into complete disrepair | 10:21 |
berendt | makes sense, what about a warning note in the docs? | 10:21 |
egonzalez90 | berendt: is there any info about that, not hear about deprecation of vpnaas | 10:22 |
egonzalez90 | maybe they move into a separate repository? | 10:22 |
berendt | egonzalez90: it is already in a separate repository | 10:23 |
berendt | egonzalez90: http://lists.openstack.org/pipermail/openstack-dev/2016-November/107384.html | 10:23 |
egonzalez90 | berendt: thanks | 10:25 |
*** jmccarthy has quit IRC | 10:30 | |
*** jmccarthy has joined #openstack-kolla | 10:31 | |
*** lukl has quit IRC | 10:31 | |
egonzalez90 | I think we should deprecate the service, not this release. but in next releases will be potentially broken. | 10:31 |
berendt | egonzalez90: this is my fear.. | 10:32 |
*** lukl has joined #openstack-kolla | 10:34 | |
pbourke | we could move it to the contrib directory | 10:35 |
*** ccesario has quit IRC | 10:36 | |
*** DTadrzak has joined #openstack-kolla | 10:38 | |
*** pcaruana has joined #openstack-kolla | 10:45 | |
*** ccesario has joined #openstack-kolla | 10:46 | |
*** tovin07_ has quit IRC | 10:50 | |
*** duonghq has quit IRC | 10:53 | |
*** mgoddard_ has quit IRC | 10:54 | |
*** mgoddard has joined #openstack-kolla | 10:56 | |
*** Bico_Fino has joined #openstack-kolla | 10:59 | |
*** lukl has quit IRC | 10:59 | |
*** zhubingbing has quit IRC | 11:09 | |
*** mliima has joined #openstack-kolla | 11:22 | |
*** portdirect is now known as portdirect_away | 11:22 | |
*** Bico_Fino has quit IRC | 11:23 | |
mliima | morning guys | 11:24 |
egonzalez90 | morning mliima | 11:27 |
*** lukl has joined #openstack-kolla | 11:31 | |
openstackgerrit | jimmygc proposed openstack/kolla: Add strongswan to neutron-vpn-agent source image https://review.openstack.org/401834 | 11:39 |
*** derekjhyang has joined #openstack-kolla | 11:43 | |
*** rock_ has joined #openstack-kolla | 11:44 | |
*** Pavo has quit IRC | 11:47 | |
*** sdake has joined #openstack-kolla | 11:48 | |
*** slagle has joined #openstack-kolla | 11:49 | |
*** Pavo has joined #openstack-kolla | 11:51 | |
*** duonghq has joined #openstack-kolla | 12:00 | |
pbourke | harlowja: ping | 12:05 |
*** yingjun has joined #openstack-kolla | 12:10 | |
*** portdirect_ has joined #openstack-kolla | 12:15 | |
*** dave-mccowan has joined #openstack-kolla | 12:19 | |
pbourke | egonzalez90: berendt: any of you guys actively using kibana? | 12:24 |
egonzalez90 | pbourke: no, zhubinbing is using it IIRC | 12:24 |
*** portdirect__ has joined #openstack-kolla | 12:31 | |
* portdirect__ slaps portdirect_ around a bit with a large trout | 12:31 | |
*** yingjun_ has joined #openstack-kolla | 12:32 | |
*** mdnadeem_ has quit IRC | 12:35 | |
*** yingjun has quit IRC | 12:36 | |
*** mdnadeem_ has joined #openstack-kolla | 12:39 | |
*** pbourke has quit IRC | 12:41 | |
*** pbourke has joined #openstack-kolla | 12:42 | |
berendt | pbourke: yes | 12:43 |
pbourke | berendt: do you have any visualisations/searches you recommend? Trying to make use it to see if I can more easily diagnose problems with my deploys | 12:44 |
sdake | morning peeps | 12:48 |
sdake | pbourke sup dude | 12:48 |
pbourke | morning sdake | 12:48 |
sdake | portdirect__ egonzalez90 berendt yo | 12:49 |
sdake | pbourke why the q about kibana | 12:49 |
pbourke | sdake: trying to start actually making use of it | 12:50 |
sdake | i have some experience with it - setup a dashboard - its a pretty cool tool | 12:50 |
sdake | it took me about 8 hours to setup a dashboard | 12:50 |
pbourke | sdake: so far I've been using the ol ssh n' grep | 12:50 |
sdake | 6 of those was learning | 12:50 |
pbourke | which leaves a lot to be desired | 12:50 |
portdirect__ | hey sdake | 12:51 |
sdake | pbourke the dashboard functionality is super impressive | 12:51 |
sdake | one of hte things that was on akwasnie 's plate was making an autoloading dashboard | 12:52 |
sdake | perhaps she can share her dashboard she used for her demo | 12:52 |
sdake | perhaps elemoine_ can share it as well | 12:52 |
sdake | I no longer have the dashboard I created | 12:52 |
pbourke | sdake: yeah Im touching up the docs as part of my learnings | 12:52 |
sdake | or if I do, its on a laptop half disassembled | 12:52 |
*** tonanhngo has joined #openstack-kolla | 12:53 | |
sdake | what is really needed there is to autoload the dashboard | 12:53 |
sdake | so we ship a default | 12:53 |
sdake | i dont have the dashboard that was used for austin summit | 12:53 |
*** tonanhngo has quit IRC | 12:55 | |
sdake | also perhaps inc0 hsa the dashboard | 12:55 |
sdake | someone of those 3 who presented the "These are not the logs you are looking for" talk would hopefully have the kolla dashboard | 12:55 |
*** lamt has quit IRC | 12:58 | |
openstackgerrit | Mauricio Lima proposed openstack/kolla-ansible: Load manila-ui in horizon https://review.openstack.org/403680 | 13:01 |
openstackgerrit | Merged openstack/kolla: Add strongswan to neutron-vpn-agent source image https://review.openstack.org/401834 | 13:02 |
*** DTadrzak has quit IRC | 13:09 | |
openstackgerrit | Mauricio Lima proposed openstack/kolla: Add manila-ui in horizon image https://review.openstack.org/403689 | 13:13 |
*** nradojevic has quit IRC | 13:13 | |
berendt | At the moment I only have basic dashboards. I think it makes most sense when we add basic dashboards to the Kibana Ansible role. This way we can ship some basics. | 13:15 |
berendt | Is anybody using irccloud? I am using the trial version at the moment... Are they stable and trustworthy? | 13:20 |
*** liyifeng has joined #openstack-kolla | 13:29 | |
*** dims has quit IRC | 13:33 | |
*** jtriley has joined #openstack-kolla | 13:40 | |
*** mdnadeem_ has quit IRC | 13:41 | |
*** tovin07_ has joined #openstack-kolla | 13:42 | |
*** dims has joined #openstack-kolla | 13:44 | |
*** athomas has quit IRC | 13:44 | |
*** zhubingbing has joined #openstack-kolla | 13:45 | |
*** jtriley has quit IRC | 13:45 | |
*** Pavo has quit IRC | 13:47 | |
*** tonanhngo has joined #openstack-kolla | 13:51 | |
*** Pavo has joined #openstack-kolla | 13:51 | |
*** portdirect__ has quit IRC | 13:52 | |
*** tonanhngo has quit IRC | 13:52 | |
*** sp_ has quit IRC | 13:53 | |
*** jheroux has joined #openstack-kolla | 13:53 | |
sdake | pbourke berendt can I get some action on https://review.openstack.org/#/c/399582/ | 13:56 |
sdake | egonzalez90 too :) | 13:56 |
*** fguillot has joined #openstack-kolla | 13:56 | |
*** yingjun has joined #openstack-kolla | 13:59 | |
*** lamt has joined #openstack-kolla | 14:00 | |
*** BIOS_Hazard has joined #openstack-kolla | 14:01 | |
*** inc0 has joined #openstack-kolla | 14:01 | |
inc0 | good morning | 14:02 |
*** yingjun_ has quit IRC | 14:02 | |
*** BIOS_Hazard has left #openstack-kolla | 14:03 | |
inc0 | guys, I'm a bit sick, so please give me a slack this week;) | 14:04 |
sdake | sup inc0 | 14:05 |
inc0 | started from food poisoning, now muscle inflammation, popping codeine | 14:05 |
inc0 | mild fever | 14:05 |
openstackgerrit | Merged openstack/kolla: Clean up README.rst in docker repo https://review.openstack.org/399582 | 14:06 |
sdake | sounds like painful and fun at same time :) | 14:06 |
inc0 | nothing too bad, but thinking is hard | 14:06 |
sdake | surprised your do gave you codeine for inflammation | 14:06 |
sdake | there re much better meds for that | 14:06 |
inc0 | yeah me too | 14:06 |
inc0 | but after food poisoning options are limited too | 14:07 |
sdake | right- not a doctor myself :) | 14:07 |
inc0 | also, I'm not sure (neither they were) that it is inflammation | 14:07 |
inc0 | so just for the pain;) | 14:07 |
sdake | just armchair phsychiatrist ;) | 14:07 |
*** liyifeng_seu has joined #openstack-kolla | 14:07 | |
duonghq | I build kolla image successfully on Arch linux w/ Python 2.7, anybody try Python 3.5? I got error relate to bytes/str compatible | 14:08 |
sdake | duonghq our build script doesn't work oon python 3.5 iirc | 14:08 |
sdake | it does work on python 3.4 i think tho | 14:08 |
sdake | it needs some porting i think | 14:08 |
duonghq | do we have plan migrate it to python 3.5? | 14:08 |
*** goldyfruit has joined #openstack-kolla | 14:08 | |
sdake | duonghq that was part of the goals discussion for ocata | 14:09 |
sdake | the goal got shot down | 14:09 |
rock_ | Hi. I want to know one thing. who is using kolla mostly? | 14:09 |
sdake | or pushed down the road | 14:09 |
duonghq | sdake, so, I'll write a bp or bug for this? | 14:09 |
sdake | rock_ operators | 14:09 |
sdake | duonghq whatever you think makes sense I think | 14:09 |
rock_ | sdake: may I know who were those operators? In which cases kolla is more suitable for them? | 14:10 |
duonghq | sdake, roger, so I'll make it in the same way as other project | 14:11 |
sdake | rock_ you said 1 tihng not 2 :) | 14:11 |
sdake | rock_ so its not like we have a master list of operators using kolla | 14:11 |
inc0 | rock_, mostly when they want to deploy openstack;) | 14:11 |
sdake | kolla has no typical analytics companies use | 14:11 |
sdake | rock_ because kolla is a project not a product | 14:12 |
*** hvlad has joined #openstack-kolla | 14:12 | |
sdake | rock_ so I can't answer #2 for you :) | 14:12 |
inc0 | rock_, what is exactly you want to know? | 14:12 |
rock_ | sdake/inc0 : Hi. i am new to Kolla, magnum and kuryr. I want to know which one is used by industries mostly and why? | 14:15 |
inc0 | rock_, they solve *totally* different problems | 14:16 |
*** lrensing has joined #openstack-kolla | 14:16 | |
inc0 | I suggest to watch "Containers: mapping the landscape" keynote from last summit | 14:16 |
sdake | magnum -> join chnanel #openstack-containers | 14:16 |
sdake | kuryr -> join channel #openstack-kuryr | 14:17 |
sdake | kolla is used by operators to deploy openstack as per our mission - why do operators use operators to deploy Kolla? We don't have hard fast data, but my opinion it all comes down to ease of use | 14:18 |
duonghq | sdake, inc0 https://blueprints.launchpad.net/kolla/+spec/support-python-3.5 here is the bp I set the milestone to o-3 due to we have many work has higher priority for o-2 | 14:19 |
inc0 | duonghq, thanks | 14:19 |
rock_ | inc0/sdake: OK. Thank you. Yes I had a look on "Containers: mapping the landscape" keynote . | 14:19 |
sdake | rock_ we are not experts in magnum nor kuryr | 14:20 |
sdake | they have their own irc channels, if you want ot understand their roles, ask there | 14:20 |
duonghq | anybody think the magnum channel's name is somewhat misleading? | 14:20 |
rock_ | sdake: OK. thank you . | 14:20 |
egonzalez90 | duonghq: yes, sound more like a general containers in openstack | 14:21 |
*** yingjun has quit IRC | 14:22 | |
*** yingjun has joined #openstack-kolla | 14:22 | |
duonghq | inc0, np | 14:22 |
duonghq | my keyboard has one more key screw up | 14:22 |
sdake | duonghq pretty much :) | 14:24 |
openstackgerrit | Paul Bourke (pbourke) proposed openstack/kolla: Update Kibana documentation https://review.openstack.org/403729 | 14:24 |
*** yingjun has quit IRC | 14:26 | |
*** yingjun has joined #openstack-kolla | 14:27 | |
*** openstackstatus has quit IRC | 14:28 | |
*** openstackstatus has joined #openstack-kolla | 14:29 | |
*** ChanServ sets mode: +v openstackstatus | 14:29 | |
*** yingjun has quit IRC | 14:31 | |
*** rhallisey has joined #openstack-kolla | 14:32 | |
*** inc0 has quit IRC | 14:37 | |
mliima | guys, need some act here https://review.openstack.org/#/c/403680/ and https://review.openstack.org/#/c/403689/ | 14:40 |
mliima | and here https://review.openstack.org/#/c/403445/2 | 14:40 |
*** v1k0d3n has joined #openstack-kolla | 14:42 | |
*** liyifeng has quit IRC | 14:45 | |
*** sdake_ has joined #openstack-kolla | 14:46 | |
*** mgiles has joined #openstack-kolla | 14:48 | |
*** ccesario has quit IRC | 14:48 | |
*** sdake has quit IRC | 14:49 | |
*** fguillot has quit IRC | 14:52 | |
*** fguillot has joined #openstack-kolla | 14:52 | |
*** liyifeng has joined #openstack-kolla | 14:53 | |
openstackgerrit | Serguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Rabbitmq HELM Chart https://review.openstack.org/403456 | 14:57 |
*** TxGirlGeek has joined #openstack-kolla | 15:00 | |
*** ccesario has joined #openstack-kolla | 15:00 | |
openstackgerrit | Serguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Rabbitmq HELM Chart https://review.openstack.org/403456 | 15:02 |
*** tonanhngo has joined #openstack-kolla | 15:03 | |
*** tonanhngo has quit IRC | 15:04 | |
*** saneax is now known as saneax-_-|AFK | 15:11 | |
openstackgerrit | Merged openstack/kolla: Add ironic-ui to horizon image https://review.openstack.org/403445 | 15:14 |
*** v1k0d3n has quit IRC | 15:15 | |
*** v1k0d3n has joined #openstack-kolla | 15:16 | |
*** hvlad has quit IRC | 15:17 | |
*** v1k0d3n has quit IRC | 15:19 | |
*** v1k0d3n has joined #openstack-kolla | 15:19 | |
*** f13o has quit IRC | 15:22 | |
*** liyifeng_seu has quit IRC | 15:25 | |
*** v1k0d3n has quit IRC | 15:27 | |
*** v1k0d3n has joined #openstack-kolla | 15:31 | |
*** portdirect__ has joined #openstack-kolla | 15:31 | |
sdake_ | mgiles up for ramping up your dev env for kolla-kubernetes dev? | 15:33 |
*** jtriley has joined #openstack-kolla | 15:33 | |
*** portdirect_ has quit IRC | 15:35 | |
*** dims has quit IRC | 15:36 | |
*** liyifeng_seu has joined #openstack-kolla | 15:40 | |
*** dims has joined #openstack-kolla | 15:41 | |
*** mliima_ has joined #openstack-kolla | 15:41 | |
*** awidders_ has joined #openstack-kolla | 15:42 | |
*** sdake has joined #openstack-kolla | 15:42 | |
*** mliima has quit IRC | 15:44 | |
*** awiddersheim has quit IRC | 15:44 | |
*** sdake_ has quit IRC | 15:45 | |
*** Pavo has quit IRC | 15:47 | |
*** harlowja_at_home has joined #openstack-kolla | 15:51 | |
openstackgerrit | Merged openstack/kolla-ansible: Add tool to merge passwords during release upgrade https://review.openstack.org/402534 | 15:51 |
*** Pavo has joined #openstack-kolla | 15:52 | |
*** hvlad has joined #openstack-kolla | 15:52 | |
*** sayantan_ has joined #openstack-kolla | 15:53 | |
*** derekjhyang has quit IRC | 16:01 | |
*** hieulq has quit IRC | 16:01 | |
*** tovin07 has quit IRC | 16:01 | |
*** cliles has quit IRC | 16:01 | |
*** david-lyle has quit IRC | 16:01 | |
*** nihilifer has quit IRC | 16:01 | |
*** karlamrhein has quit IRC | 16:01 | |
*** Kimmo__ has quit IRC | 16:01 | |
*** zigo has quit IRC | 16:01 | |
*** tovin07_ is now known as tovin07 | 16:01 | |
*** zigo has joined #openstack-kolla | 16:01 | |
*** Kimmo__ has joined #openstack-kolla | 16:02 | |
*** cliles has joined #openstack-kolla | 16:02 | |
*** tovin07_ has joined #openstack-kolla | 16:02 | |
*** david-lyle has joined #openstack-kolla | 16:02 | |
*** hieulq has joined #openstack-kolla | 16:02 | |
*** nihilifer has joined #openstack-kolla | 16:02 | |
*** Satya_ has joined #openstack-kolla | 16:03 | |
*** jtriley has quit IRC | 16:04 | |
openstackgerrit | Mauricio Lima proposed openstack/kolla: Add manila-ui in horizon image https://review.openstack.org/403689 | 16:04 |
*** karlamrhein has joined #openstack-kolla | 16:07 | |
*** shardy has quit IRC | 16:10 | |
jmccarthy | Hiya I'm looking at an mtu related change in this commit here https://github.com/openstack/kolla-ansible/commit/a627681eec09eacd208b21d35ab7ad76245319e4#diff-4bf34bbf9cbc26c3eeb2f87a100bc631 | 16:11 |
jmccarthy | There is some accompanying docs that say advertise_mtu is True by default: | 16:11 |
jmccarthy | https://review.openstack.org/#/c/302165/4/doc/networking-guide/source/adv-config-mtu.rst | 16:11 |
jmccarthy | Does this mean it should be specified in ansible/roles/neutron/templates/neutron.conf.j2, or that even if it is omitted from here (which it looks like it is) that it will advertise by default ? | 16:11 |
jmccarthy | I'm thinking we may need to have an entry in here to explicitly set this to True ? | 16:11 |
*** vhosakot has joined #openstack-kolla | 16:14 | |
openstackgerrit | Merged openstack/kolla-ansible: Updated from global requirements https://review.openstack.org/402187 | 16:15 |
*** f13o has joined #openstack-kolla | 16:18 | |
sdake | jmccarthy openstack-neutron is where i'd ask - tell em your doing dev on kolla should help you get some kind of answer ;) | 16:18 |
sdake | jmccarthy otherwise they will consider it some kind of support question | 16:19 |
sdake | which neutron doesn't do :) | 16:19 |
sdake | dave-mccowan sbezverk ^^ any idea on jmccarthy 's question? | 16:19 |
jmccarthy | sdake: Ok, thanks ! I'm going to test it out a bit more myself also and see what happens :) Will be able to tell soon hopefully | 16:20 |
sdake | jmccarthy sounds good | 16:20 |
sdake | jmccarthy note the defaults are printed in the container logs | 16:21 |
sdake | looking at the neutron logs should help you understand the defaults as well | 16:21 |
*** zhubingbing has quit IRC | 16:21 | |
*** v1k0d3n has quit IRC | 16:22 | |
openstackgerrit | Merged openstack/kolla: Install sahara dashboard into horizon image https://review.openstack.org/403502 | 16:23 |
sbezverk | jmccarthy: sdake: It makes sense to have mtu advertisement on by default as there are lots of higher level protocols in networking world relying on this feature | 16:23 |
*** MarMat has joined #openstack-kolla | 16:24 | |
vhosakot | back from a great vacation. Hope everyone is doing great and had a great Thanksgiving! I needed all day yesterday to catch up on 1 month's emails | 16:24 |
vhosakot | lothian [11:22 AM] | 16:24 |
vhosakot | @vhosakot you were gone? | 16:24 |
vhosakot | haha, bad paste! | 16:24 |
duonghq | hmm, I use all-in-one playbook to deploy to one node and then run post-deploy con deploy node, it still try to connect to target node with local connection -> failed | 16:28 |
duonghq | target node != deploy-node | 16:29 |
duonghq | iirc, we do not have this issue before? | 16:29 |
*** kristian__ has joined #openstack-kolla | 16:30 | |
duonghq | ah, see the problem | 16:30 |
sdake | vhosakot you been out for a mo? | 16:30 |
duonghq | need sleep now, bye all | 16:30 |
sdake | vhosakot wtb your schedule ;) | 16:30 |
*** duonghq has quit IRC | 16:30 | |
vhosakot | sdake: haha, yes.. was out for a month... couldn't chat with you in Barcelona.. attended all your talks.. they were great | 16:31 |
sdake | thanks | 16:31 |
sdake | didn't see ya in audience but there were slews of people | 16:31 |
openstackgerrit | Mauricio Lima proposed openstack/kolla: Add manila-ui in horizon image https://review.openstack.org/403689 | 16:32 |
sdake | vhosakot you making it to PTG? | 16:32 |
*** kristian__ has quit IRC | 16:35 | |
*** kristian__ has joined #openstack-kolla | 16:35 | |
sbezverk | sdake: I cleaned up rabbitmq charts, still WIP but please share your thoughts if you have time. | 16:37 |
sdake | sbezverk sure you got it | 16:37 |
sdake | would like kfox1111 's input as well, since he started the helm work | 16:38 |
sdake | sbezverk note i noticed a patch was +w'ed with only 1 +2 | 16:38 |
sbezverk | sdake: that was the agreement we had for kube ps | 16:38 |
sdake | sbezverk because core team was too small? | 16:39 |
*** schwicht has joined #openstack-kolla | 16:39 | |
sbezverk | sdake: because there were only 3 guys working on it before | 16:39 |
*** eaguilar has joined #openstack-kolla | 16:41 | |
*** v1k0d3n has joined #openstack-kolla | 16:41 | |
*** jascott1 has joined #openstack-kolla | 16:41 | |
*** schwicht has quit IRC | 16:42 | |
*** harlowja_at_home has quit IRC | 16:42 | |
kfox1111 | morning. | 16:42 |
*** schwicht has joined #openstack-kolla | 16:42 | |
sdake | ok - well there is bound to be some deltas in the patches - lets sort out the delta with 2 +2s :) | 16:43 |
sdake | kfox1111 sup dude - can you hit the review queue, have some qs in your review, and had a slew of em in sbezverk 's as well | 16:43 |
kfox1111 | sdake: yeah. was going to try and do that this morning. | 16:43 |
sdake | kfox1111 also - thanks to portdirect__ got my env setup | 16:43 |
kfox1111 | along with everything else. :) | 16:43 |
sdake | kfox1111 tell me about it :) | 16:43 |
kfox1111 | portdirect__: thanks. :) | 16:44 |
sdake | kfox1111 working on mariadb chart today if the stars align (as in I can fix my $460 water bill leak) | 16:44 |
kfox1111 | ouch. | 16:44 |
kfox1111 | k. | 16:44 |
sdake | normally my water bill runs about 80 bucks | 16:44 |
sdake | ya the 380 isn't isn't too bad but hate to waste resources :) | 16:45 |
sdake | the 380 being resources and the water being resources | 16:45 |
kfox1111 | yeah. thats a fair amount. several hot tubs worth I think. | 16:45 |
sdake | its about 120*8 showers :) | 16:46 |
sbezverk | kfox1111: good morning! | 16:46 |
kfox1111 | sbezverk: good monring. :) | 16:46 |
sdake | kfox1111 sbezverk you fellas might consider beefing up the core team with nominations at some point | 16:47 |
kfox1111 | sdake: yeah. | 16:47 |
kfox1111 | need to see more 3rd party reviews. have had some. hopfully more this last week? | 16:47 |
sdake | yup i think srwilkers and portdirect__ going to hit it harder ;) | 16:48 |
*** v1k0d3n has quit IRC | 16:48 | |
vhosakot | sdake: I'll let you know about PTG.. sure | 16:48 |
kfox1111 | sdake: +1 | 16:49 |
sdake | and possibly dounghq and mgiles :) | 16:49 |
kfox1111 | sdake: yeah. PTG would be good to know about. I think I'm tentitively scheduled to go. | 16:49 |
*** tovin07 has left #openstack-kolla | 16:49 | |
sdake | kfox1111 did you get a ticket yet? | 16:49 |
sdake | kfox1111 they may be sold out | 16:49 |
sdake | there were only 500 available | 16:49 |
kfox1111 | sbezverk: so, have you tried to implement a service package yet? I don't think your global aproach will work with them. | 16:49 |
kfox1111 | sdake: already? | 16:50 |
kfox1111 | wow... | 16:50 |
kfox1111 | hmm... | 16:50 |
sdake | i dont know for sure if they are sold out | 16:50 |
sdake | the tickets are 100$ | 16:50 |
kfox1111 | that would be unfortunate | 16:50 |
kfox1111 | looks like they may still be open. | 16:50 |
kfox1111 | so is anyone else going? | 16:51 |
sdake | ya i think core team members would not be part of the limit but what do I know | 16:51 |
sdake | kfox1111 don't have that information - inc0 may | 16:51 |
sdake | inc0 out sick today i think | 16:51 |
kfox1111 | k. cause that may infuence if I can go. | 16:51 |
kfox1111 | and if they are hard to come by, I shoudl get them asap. | 16:52 |
kfox1111 | k. | 16:52 |
sdake | kfox1111 all I can tell you about my attendance at this point is I've bought a ticket ;) | 16:52 |
sdake | however kolla has scheduled time at the ptgs | 16:52 |
sdake | so it would be a serious shame to waste that scheduled f2f time | 16:52 |
sdake | kfox1111 service package = e.g. nova? | 16:53 |
kfox1111 | sdake: yeah. thanks. | 16:53 |
kfox1111 | sdake: yes. | 16:53 |
sbezverk | kfox1111: I am waiting for helm 2.1 it should bring missing piece, lots of people asking for the same functionality | 16:54 |
kfox1111 | sbezverk: have an issue link? | 16:54 |
sbezverk | kfox1111: yep, one sec | 16:54 |
kfox1111 | there's a huge amount of duplication in here without templating charts. :/ | 16:54 |
mliima_ | sdake, can you review https://review.openstack.org/#/c/403689/ and https://review.openstack.org/#/c/403680/ | 16:54 |
sbezverk | kofx1111: https://github.com/kubernetes/helm/issues/1568#issuecomment-262086504 | 16:55 |
mliima_ | thanks sdake | 16:56 |
sdake | mliima_ both lgtm | 16:56 |
kfox1111 | sbezverk: thanks. looking... | 16:57 |
*** rmart04 has quit IRC | 16:57 | |
openstackgerrit | Merged openstack/kolla-ansible: Load manila-ui in horizon https://review.openstack.org/403680 | 16:58 |
kfox1111 | sbezverk: that aproach you linked to sounds like a variant of my first prototype but with a plugin. | 17:00 |
kfox1111 | I made a single package conditionally include subresources using just the engine. | 17:00 |
kfox1111 | I don't like the proposed solution in the issue though. it would make it very difficult on automation that could do upgrades. | 17:00 |
kfox1111 | I'd rather be able to actually launch the packages without having a parent at all. | 17:01 |
*** liyifeng_seu has quit IRC | 17:01 | |
kfox1111 | and it doesn't address having 2 layers of parents. | 17:01 |
kfox1111 | which I think will break the globals idea. | 17:01 |
*** liyifeng_seu has joined #openstack-kolla | 17:02 | |
kfox1111 | for my use case, I need to be able to lauch the individual microservices as helm instances, so I can upgrade them or change them a single piece at a time. | 17:03 |
kfox1111 | I need 0 orchestration that could break things running. | 17:04 |
*** matrohon has quit IRC | 17:04 | |
*** egonzalez90 has quit IRC | 17:04 | |
sdake | kfox1111 can we get htis information in the reviews | 17:05 |
sdake | kfox1111 in irc is cool too, but without reviews, people reviewing won't have this context if they aren't in irc at this particular point in time :) | 17:05 |
kfox1111 | yup. | 17:05 |
sdake | kfox1111 justto be clear, you want to launch each individual microservice such s nova-proxynovnc as a helm chart? | 17:07 |
sdake | or whatever that component is called :) | 17:08 |
kfox1111 | sdake: correct. | 17:08 |
kfox1111 | then when I update nova-novncproxy, there should be 0 risk of nova-api getting affected. | 17:08 |
kristian__ | Hi sdake please may you help me? | 17:09 |
kfox1111 | helm list should show them all. | 17:09 |
kristian__ | We may have a solution | 17:09 |
sdake | kristian__ solution to what | 17:09 |
kristian__ | Change libvirt to 1.2.17 | 17:09 |
kristian__ | https://bugs.launchpad.net/nova/+bug/1642419 | 17:09 |
openstack | Launchpad bug 1642419 in kolla-ansible "GPU Passthrough isn't working" [Low,Confirmed] | 17:09 |
sdake | kristian__ i don't see that solution in the bug log - where did you come up with that | 17:10 |
sdake | note we have no control over libvirt versions - those come from upstream distros | 17:10 |
kristian__ | from nova team | 17:10 |
kristian__ | oh | 17:10 |
sdake | which version of libvirt is in your container | 17:11 |
kristian__ | dunno | 17:11 |
*** eaguilar has quit IRC | 17:11 | |
portdirect__ | kfox1111: word up! | 17:11 |
sdake | docker exec nova_libvirt rpm -qi libvirt | 17:11 |
sdake | kfox1111 that sounds pretty cool | 17:11 |
kristian__ | 1.3.1 | 17:11 |
kfox1111 | portdirect__: morning. | 17:12 |
sdake | kfox1111 that isn't something that helm supports correct? | 17:12 |
sdake | kristian__ so we have a newer version then 1.2.17 | 17:12 |
kristian__ | than 1.2.17 | 17:12 |
kristian__ | yes | 17:12 |
sdake | downstreams follow upstreams, not the other way around | 17:12 |
kfox1111 | sdake: well, each helm root chart is 'instantiated'. its given a name and can then be acted upon. | 17:12 |
kfox1111 | I don't think subcharts get names. | 17:12 |
sdake | nova should be following the latest upstream, not some specific version that is old :) | 17:12 |
kristian__ | he did that gpu passthrough with 1.2.17 and it worked for him | 17:13 |
sdake | did he see the ethtool spam | 17:13 |
kristian__ | yes | 17:13 |
sdake | his take on that was what? | 17:13 |
kristian__ | kristian__: it doesn't makes sense that libvirt tries to do something with ethtool on this kind of device | 17:13 |
sdake | dberrange is the fella to talk to in the nova channel | 17:14 |
sdake | he maintains libvirt | 17:14 |
sdake | get em to put the stuff in the buglog | 17:14 |
sdake | :) | 17:14 |
sdake | ther eis no wy to run 1.2.17 of libvirt | 17:15 |
sdake | that I know of | 17:15 |
sdake | not sure how the person that tested gpu passthrough has 1.2.17 | 17:15 |
kristian__ | ok going to ping him | 17:15 |
sdake | maybe thats what is shipped with ubuntu? | 17:15 |
kristian__ | maybe before they've updated the repos | 17:15 |
sdake | actually he may not maintian libvirt anymore | 17:15 |
kristian__ | ok | 17:15 |
sdake | but he will know who does ;) | 17:15 |
kristian__ | first Im going to manually install that version | 17:16 |
*** sdake has quit IRC | 17:16 | |
kristian__ | and then we will see | 17:16 |
kfox1111 | we've not had very good luck over here with gpu passthrouhg. :/ | 17:16 |
*** sdake has joined #openstack-kolla | 17:16 | |
kfox1111 | redhat's been recommending to use efi to make it work smoothly, but nova doesn't support it well yet. :/ | 17:17 |
kristian__ | I had but dunno on what libvirt | 17:17 |
*** eaguilar has joined #openstack-kolla | 17:18 | |
*** pcaruana has quit IRC | 17:19 | |
*** portdirect__ has left #openstack-kolla | 17:23 | |
*** liyifeng has quit IRC | 17:29 | |
*** liyifeng_seu has quit IRC | 17:29 | |
*** unicell1 has quit IRC | 17:29 | |
*** sdake_ has joined #openstack-kolla | 17:34 | |
*** v1k0d3n has joined #openstack-kolla | 17:35 | |
*** v1k0d3n has quit IRC | 17:35 | |
*** Guest81558 has joined #openstack-kolla | 17:36 | |
*** sdake has quit IRC | 17:36 | |
kfox1111 | is there a length limit to a review? | 17:37 |
kfox1111 | :/ | 17:37 |
sdake_ | kfox1111 how do you mean | 17:42 |
sdake_ | the contents of a review? | 17:42 |
kfox1111 | yeah. | 17:43 |
sdake_ | I am not sure - but i suspect there may be - there are always limits in all kinds of software :( | 17:43 |
kfox1111 | well, it took it. :) | 17:43 |
*** Guest81558 has quit IRC | 17:44 | |
*** gfidente is now known as gfidente|afk | 17:45 | |
*** Pavo has quit IRC | 17:47 | |
*** Pavo has joined #openstack-kolla | 17:52 | |
openstackgerrit | satya proposed openstack/kolla-ansible: Added separate interface for rabbitmq https://review.openstack.org/401957 | 17:56 |
*** aric49 has joined #openstack-kolla | 17:59 | |
Satya_ | hi jeffrey4l | 17:59 |
Satya_ | hi sdake | 17:59 |
Satya_ | hi sdake_ | 18:00 |
harlowja | pbourke whats up | 18:00 |
*** sayantan_ has quit IRC | 18:01 | |
*** sayantan_ has joined #openstack-kolla | 18:01 | |
*** Serlex has quit IRC | 18:01 | |
Satya_ | hi pbourke | 18:03 |
pbourke | harlowja: just wondering if you guys are using kibana actively in godaddy? | 18:03 |
pbourke | Satya_: hi | 18:04 |
*** portdirect_away is now known as portdirect | 18:04 | |
Satya_ | Please review | 18:04 |
harlowja | pbourke yes | 18:04 |
harlowja | klindgren ^ | 18:04 |
harlowja | pbourke klindgren knows more of the godaddy history than i do though :-P | 18:04 |
klindgren | hi | 18:05 |
pbourke | harlowja: I was just wondering if you had any useful searches or dashboards you could point me at | 18:05 |
harlowja | klindgren 'harlowja: just wondering if you guys are using kibana actively in godaddy?' | 18:05 |
pbourke | since this morning I've managed to learn a bit more though | 18:05 |
harlowja | pbourke redirect to klindgren :-P | 18:05 |
klindgren | so we moved over to a kibana4 infra | 18:05 |
klindgren | but I can point you to our stuff that we did for kibana2 and logstash | 18:06 |
*** tonanhngo has joined #openstack-kolla | 18:06 | |
klindgren | https://github.com/godaddy/openstack-logstash | 18:06 |
klindgren | we use a similar one to that just done up in kibana4 now days | 18:07 |
harlowja | why isn't that updated klindgren :-P | 18:08 |
*** sayantan_ has quit IRC | 18:08 | |
klindgren | because I didn't do the move to the kibana4 infra. and kibana4 took something simple and made it so where you need a phd in kibana to do crap in it :-D | 18:08 |
harlowja | lol | 18:09 |
klindgren | as I understand kibana4 bascially you have to create views. That individually give you parts of the dash board. Then you have to create a dashboard that references the views. Since we dont run our own elk infra anymore. I am not sure wher those views/dashboard get sotred or if tis possible to save them off into a single uploadedable json format anymore. | 18:10 |
klindgren | which also means - I am pretty sure that stuff is not under source control. :-/ | 18:11 |
sbezverk | kfox1111: sorry was on the meeting. Yes, I took your common and placed it in _helpers.tpl which will make it avaiable to all sub charts | 18:14 |
sbezverk | kfox1111: when that plugin is avaiable then we can deploy parent/child/grand-child independently but using globally defined code.. | 18:15 |
sbezverk | kfox1111: also it should apply to packaging | 18:15 |
*** rhallisey has quit IRC | 18:16 | |
klindgren | pbourke, I think the osops repo also has other peoples logstash/kibana configs as well. | 18:16 |
*** rhallisey has joined #openstack-kolla | 18:16 | |
klindgren | https://github.com/openstack/osops-tools-logging/tree/master/logstash | 18:18 |
*** sdake has joined #openstack-kolla | 18:18 | |
*** sdake_ has quit IRC | 18:21 | |
aric49 | Hi everyone --- quick question about Kolla OS support. Can anyone here confirm that the kolla build and deploy works on Ubuntu 16.04? | 18:25 |
*** jascott1_ has joined #openstack-kolla | 18:26 | |
*** jascott1 has quit IRC | 18:26 | |
*** jascott1_ has quit IRC | 18:26 | |
*** jascott1 has joined #openstack-kolla | 18:26 | |
portdirect | aric49: though I use CentOS, I am aware of people on here who use Ubuntu 16.04 | 18:29 |
*** inc0 has joined #openstack-kolla | 18:30 | |
portdirect | aric49: there is also gates that run for both building and deployment of kolla on ubuntu | 18:30 |
*** tonanhngo has quit IRC | 18:30 | |
inc0 | hey, I'm back | 18:31 |
*** kristian__ has quit IRC | 18:31 | |
sdake | aric49 can fonfirm it works | 18:31 |
aric49 | @portdirect - Thanks. Have you successfully built and deployed kolla on 16.04? | 18:37 |
inc0 | aric49, I did, multiple times | 18:38 |
inc0 | xenial works fine | 18:38 |
portdirect | aric49: ^^ | 18:39 |
*** kristian__ has joined #openstack-kolla | 18:39 | |
inc0 | careful tho, I think aufs is a no-no with xenial | 18:40 |
inc0 | btrfs should be ok tho | 18:40 |
*** unicell has joined #openstack-kolla | 18:41 | |
aric49 | perfect. Thank you | 18:42 |
*** rmart04 has joined #openstack-kolla | 18:42 | |
*** v1k0d3n has joined #openstack-kolla | 18:42 | |
*** mgoddard_ has joined #openstack-kolla | 18:44 | |
*** tonanhngo has joined #openstack-kolla | 18:44 | |
*** tonanhngo has quit IRC | 18:45 | |
kfox1111 | back. | 18:46 |
kristian__ | sdake: are you here? | 18:46 |
sdake | OTP | 18:46 |
sdake | kristian__ there is plenty of other people here who can help :) | 18:46 |
*** rmart04 has quit IRC | 18:47 | |
*** lbeliveau has joined #openstack-kolla | 18:47 | |
kristian__ | ok lbeliveau from nova team | 18:47 |
*** mgoddard has quit IRC | 18:47 | |
kristian__ | could you two or with portdirect do a script to load an older version of libvirt? | 18:48 |
kfox1111 | sbezverk: having a plugin change the behavior of helm in the client seems kind of sketchy to me. | 18:48 |
*** mgoddard_ has quit IRC | 18:48 | |
kfox1111 | I'd rather have the safest unit of deployment be just the thing I'm trying to update. | 18:48 |
inc0 | kristian__, like build image with older libvirt? | 18:48 |
kristian__ | yes | 18:49 |
kristian__ | because with the newer one gpu passthrough doesnt work | 18:49 |
inc0 | http://docs.openstack.org/developer/kolla/image-building.html#dockerfile-customisation | 18:49 |
inc0 | ahh so it was issue with libvirt version? | 18:50 |
kristian__ | yes | 18:50 |
lbeliveau | we still need to validate that, but it looks like it | 18:50 |
lbeliveau | I booted guest with non-NIC passthrough on 1.2.17 | 18:51 |
inc0 | https://github.com/openstack/kolla/blob/master/docker/nova/nova-libvirt/Dockerfile.j2#L24 <- change this package to version you want | 18:51 |
*** aric49 has quit IRC | 18:52 | |
kristian__ | to libvirt-bin=1.2.17? | 18:52 |
*** v1k0d3n has quit IRC | 18:52 | |
*** v1k0d3n has joined #openstack-kolla | 18:52 | |
inc0 | kristian__, you're running ubuntu? | 18:52 |
kristian__ | yes | 18:53 |
*** v1k0d3n has quit IRC | 18:53 | |
lbeliveau | FYI on latest centos, libvirt version is 1.2.17 | 18:53 |
*** v1k0d3n has joined #openstack-kolla | 18:53 | |
sdake | lbeliveau we use virtualization sig version | 18:54 |
inc0 | 1.3.1 for ubuntu xenial | 18:54 |
kristian__ | so should I try and build for centos? | 18:54 |
sdake | which is 1.3.z | 18:54 |
sdake | kristian__ aren't you already on centos? | 18:54 |
kristian__ | no | 18:54 |
kristian__ | Im on ubuntu | 18:54 |
lbeliveau | yeah, I've never tried passthrough on newer versions of libvirt (1.3.x) | 18:54 |
sdake | let me check qemu sig version - moment | 18:55 |
inc0 | and yes kristian__ create your customization file with nova_libvirt_packages_remove = ['libvirt-bin'] and nova_libvtirt_packages_append=['libvirt-bin=1.2.17'] | 18:55 |
kristian__ | inc0 where to create that file? | 18:56 |
*** aric49 has joined #openstack-kolla | 18:56 | |
inc0 | it's in docs, you need to build it with customization line, but for now maybe just edit our dockerfile | 18:56 |
inc0 | to quickly test if it works | 18:56 |
kristian__ | ok | 18:57 |
sdake | virt sig uses 1.2.17 | 18:57 |
inc0 | if it's case indeed, I'll walk you through adding this customization | 18:57 |
inc0 | and probably write it down as workaround for this bug | 18:57 |
sdake | if it works on 1.2.17 looks like a bug not in kolla to me ;) | 18:57 |
inc0 | yeah, it's libvirt bug | 18:58 |
inc0 | we can hardcode version of libvirt for ubuntu, but I'd rather not | 18:58 |
sdake | possibly not - libvirt does a whole bunch of trickery in docker containers | 18:58 |
inc0 | well not something like that tbh, but let's see | 18:58 |
kristian__ | quick question where is kolla from pip located? | 18:58 |
sdake | kristian__ on pypi | 18:59 |
kristian__ | path on machine | 18:59 |
kfox1111 | if the bug can be tested automatically, someone should add a gate job. :) | 18:59 |
inc0 | in site-packages I'd think | 18:59 |
sdake | on centos its in /usr/lib/python2.7/site-packages/kolla for cmd line code | 19:00 |
sdake | on centos /usr/share/kolla for ansible playbooks/dockerfiles | 19:00 |
sdake | on ubuntu no idea | 19:00 |
kristian__ | ok I will look | 19:01 |
sdake | kfox1111 that is a dream that never becomes reality ;( | 19:01 |
portdirect | We need a newer version of libvirt to support efi guests (Clear Linux) | 19:01 |
sdake | and it also can't be tested automatically since no infra gear has gpus | 19:01 |
openstackgerrit | Mauricio Lima proposed openstack/kolla: Add manila-ui in horizon image https://review.openstack.org/403689 | 19:02 |
*** jgriffith is now known as jgriffith_away | 19:02 | |
inc0 | /usr/local/share/kolla for buntu | 19:03 |
portdirect | kristian__: what version of libvirt is in your containers? what version of the containers are you using? | 19:03 |
kfox1111 | sdake: yeah.... but if we don't try at least for known issues, then we're at least doomed to repleat the same mistakes. :/ | 19:03 |
sdake | kfox1111 agree - hopefully someone will take on writing some gating for kolla-ansible | 19:04 |
kristian__ | 3.0.1 the containers and the latest libvirt 1.3.1 | 19:04 |
kfox1111 | sdake: and kolla containers. | 19:04 |
sdake | kfox1111 what is needed there is cross-deliverable gating | 19:05 |
kfox1111 | I kind of hoped the package tests by rdo/ubuntu would be enough though. :/ | 19:05 |
kfox1111 | +1 | 19:05 |
sdake | the real only way to learn gating is to actually do the job yourself | 19:05 |
sdake | i've attempted training | 19:05 |
sdake | that didn't work out | 19:05 |
kfox1111 | yeah. :/ | 19:05 |
kristian__ | building | 19:06 |
kristian__ | Version '1.2.17' for 'libvirt-bin' was not found | 19:06 |
portdirect | kristian__: both the centos binary and source packages are currently building with 1.2.17, you can pull it from the docker hub. | 19:07 |
kristian__ | ok | 19:07 |
inc0 | you can try to run centos on ubuntu | 19:07 |
inc0 | but well, usually not great idea | 19:07 |
inc0 | I'd rather look for different version that is available | 19:07 |
kristian__ | pulling it right now | 19:08 |
sdake | kristian__ atleast that will answer if its a libvirt version problem | 19:08 |
kristian__ | yes | 19:08 |
kfox1111 | inc0: had an issue last t ime I tried that. | 19:08 |
kfox1111 | ubuntu container expected something of the centos kernel that just wasn't there. | 19:09 |
sdake | kfox1111 this is centos containers on ubuntu host - maybe different result | 19:09 |
kfox1111 | oh. k. | 19:10 |
inc0 | fun fact, it will be libvirt 2.1 in Yakkety | 19:10 |
kristian__ | if it will be a libvirt problem then we will need to talk with the maintainers | 19:10 |
portdirect | kfox1111: I've had the same but the other way round is usually a bit better - as ubuntu packages often expect a newer kernel | 19:10 |
kristian__ | or we yan build yakkety containers | 19:10 |
kristian__ | currently pulling libvirt :) | 19:11 |
portdirect | man - I never worked so hard to get doom working - software rendering FTW :) | 19:12 |
kfox1111 | portdirect: makes sense | 19:12 |
kristian__ | be right back (in max 1-2 hours) | 19:13 |
*** kristian__ has quit IRC | 19:13 | |
*** sayantan_ has joined #openstack-kolla | 19:14 | |
kfox1111 | ugg.. a revew is a horible way to do this... :/ | 19:15 |
sdake | kfox1111 on this plugin thing - assuming that works, does it meet the microservice targeted deployment requirement you have? | 19:15 |
*** Satya_ has quit IRC | 19:16 | |
kfox1111 | sdake: It makes me really uneasy as an op. | 19:17 |
sdake | kfox1111 better then a spec ;) | 19:17 |
sdake | could you expand as to why | 19:17 |
kfox1111 | sdake: but a spec, I can reply inline. we're starting to have to copy/paste/manually append who said what now. :/ | 19:17 |
sdake | that is what the reply button is for, not the post button :) | 19:18 |
*** kristian__ has joined #openstack-kolla | 19:19 | |
kfox1111 | sdake: can't do that in the main message. :/ | 19:20 |
sdake | right - the main message is not really intended for debate - that is what the reply button is for ;) | 19:20 |
kfox1111 | but thats what we're dealing with now. :/ | 19:21 |
*** hvlad has quit IRC | 19:21 | |
kfox1111 | I have to respond to a response in the main message now. :/ | 19:21 |
sdake | i see | 19:21 |
sdake | well it helps if everyone uses the same workflow ;) | 19:21 |
kfox1111 | true. :/ | 19:22 |
kfox1111 | but the issue is, there's not code to comment on. :/ | 19:22 |
sdake | as in debate with reply leave comments in review on technical matters | 19:22 |
kfox1111 | its a more general discussion. :/ | 19:22 |
*** kristian__ has quit IRC | 19:24 | |
*** kristian__ has joined #openstack-kolla | 19:30 | |
*** tonanhngo has joined #openstack-kolla | 19:30 | |
sbezverk | sdake: so how do you propose to reply to other people comments? It is difficult without quoting since comments are huge. | 19:37 |
sdake | in the main message you can use the reply button | 19:37 |
sdake | that will quote them | 19:37 |
sdake | that can be used for whatever - generally i try to avoid it at :) | 19:38 |
*** schwicht has quit IRC | 19:39 | |
*** schwicht has joined #openstack-kolla | 19:40 | |
kfox1111 | sdake: k. I'll try that next time. | 19:41 |
kristian__ | Hi | 19:41 |
kristian__ | it looks to be the same error on centos | 19:41 |
kristian__ | gonna check libvirt version | 19:42 |
kristian__ | finally got another error | 19:42 |
kfox1111 | sdake: ah. I see. it doesn't look like a button, so I missed it. :/ | 19:43 |
kristian__ | Exceeded maximum number of retries. Exceeded max scheduling attempts 10 for instance f39d1172-8ded-4dce-b54a-173a48e11934. Last exception: internal error: process exited while connecting to monitor: 2016-11-28T19:42:08.353179Z qemu-kvm: -device vfio-pci,h | 19:43 |
kfox1111 | I thought that was part of the collapse message functionality they have. | 19:43 |
*** matrohon has joined #openstack-kolla | 19:44 | |
kfox1111 | sdake: fair enough. didn't know the procedure. figured -2 was for strong disagreement without further convincing. will remove it. | 19:45 |
sdake | kfox1111 np - -2 means "GTFO" :) | 19:45 |
sdake | the only time i ever -2 a review is if it is flat out wrong or for e.g. when we had the docker repo removal of ansible, people had a ton of reviews outstanding for kolla repo | 19:46 |
sdake | those needed -2s to block their merge | 19:46 |
kfox1111 | sdake: ah. k. I think your definition might be stronger then some other projects I've worked on. but works for me. :) | 19:47 |
*** Pavo has quit IRC | 19:47 | |
kfox1111 | I've seen it as a way to get more discussion amungst cores when 2 +2's wouldn't be enough. | 19:47 |
kfox1111 | or my memory's just shotty. :) | 19:47 |
inc0 | -1 from core should be enough to not merge it | 19:51 |
inc0 | -2 is "never merge it" | 19:52 |
*** Pavo has joined #openstack-kolla | 19:52 | |
inc0 | we should have -3 too "and don't come back" | 19:52 |
inc0 | (that was a joke...) | 19:52 |
kristian__ | inc0: what do you think of the error I pasted? | 19:52 |
inc0 | kristian__, seems like qemu from centos can't work with kernel from ubuntu | 19:53 |
kristian__ | ok | 19:53 |
inc0 | (you tried to run centos on ubuntu right?) | 19:53 |
kristian__ | then what | 19:53 |
kristian__ | yes | 19:53 |
inc0 | hmm, soo I have idea | 19:54 |
kristian__ | then edit all dockerfiles to use 17.04? | 19:54 |
inc0 | I was thinking 14.04 | 19:54 |
kristian__ | to use the new libvirt and it may be fixed there | 19:54 |
kristian__ | or | 19:54 |
inc0 | 1.2.2 for trusty | 19:54 |
kristian__ | download that kolla image? | 19:55 |
inc0 | won't work | 19:55 |
inc0 | we changed few things since then | 19:55 |
kristian__ | does it have newton? | 19:55 |
inc0 | might not work at least | 19:55 |
inc0 | no | 19:55 |
inc0 | you can try to curl + dpkg tho | 19:55 |
inc0 | with dockerfile customization | 19:55 |
kristian__ | but what about 17.04 | 19:56 |
kristian__ | it should work | 19:56 |
inc0 | well, might | 19:56 |
inc0 | 16.10 tho | 19:56 |
inc0 | 17.04 is future | 19:56 |
kristian__ | ok so need to edit all dockerfiles to 16.10 right? | 19:57 |
inc0 | so, not really | 19:57 |
inc0 | hold on | 19:58 |
kristian__ | ok | 19:58 |
inc0 | https://github.com/openstack/kolla/blob/master/docker/base/sources.list.ubuntu <- you need to prep sources.list for yakkety | 19:58 |
inc0 | and in your kolla-build.conf change base_tag=16.10 | 19:59 |
inc0 | this *might* work | 19:59 |
inc0 | never tried that | 19:59 |
*** schwicht has quit IRC | 19:59 | |
inc0 | depends how much stuff canonical broke between xenial and yekkety | 20:00 |
inc0 | I hope not too much | 20:00 |
inc0 | and that's assuming libvirt 2+ will have it fixed | 20:00 |
*** mgiles has quit IRC | 20:00 | |
inc0 | you're doing major version upgrade of libvirts | 20:00 |
kristian__ | inc0: where is kolla-build.conf? | 20:02 |
*** schwicht has joined #openstack-kolla | 20:04 | |
*** mnasiadka has joined #openstack-kolla | 20:05 | |
sdake | kfox1111 apologies otp - 2 +2s are always enough | 20:13 |
sdake | kfox1111 its not like we rollcall reviews for code ;) | 20:13 |
sdake | 1 +2 isn't sufficient because people can ram shit through that is busted | 20:13 |
inc0 | kristian__, check out building containers doc section | 20:13 |
inc0 | I gtg - doctors appointment | 20:14 |
kfox1111 | yeah, but something this fundimental shouldn't be left up to just 2 devs. | 20:14 |
inc0 | be back later | 20:14 |
kfox1111 | arguably needs a spec. but we're trying to shortcut that. | 20:14 |
kristian__ | inc0: ERROR: unknown environment 'genconfig' | 20:14 |
sdake | 2 +2s should be sufficient in all cases for code | 20:15 |
sdake | if you really want a rollcall vote on the topic, the best way to do that is via spec | 20:15 |
sdake | because rollcall votes are reserved for architectural decisions not implementation decisions | 20:15 |
kfox1111 | sdake: this is like, ansible vs chef though. its really really inherent in which direction the code base will go in. that isn't a 2 +2 thing I think. | 20:15 |
sdake | i think in the case of helm the issue is of implementation not architecture | 20:15 |
kfox1111 | (not that it matters much, considering how many cores kolla-kubernetes has) | 20:15 |
kfox1111 | sdake: no, its kidn of a architecture thinig. operators vs helm/endpoint like. | 20:16 |
kfox1111 | my poc has tried to allow both. sbezverk's is more oriented towards helm/endpoint from my feel of it. (my 2 cents. I can be wrong) | 20:17 |
kfox1111 | I want to be able to completely devorce orchestration from packages when desired. | 20:17 |
kfox1111 | so I want as fine grained packages as I can get. microsservices level, | 20:18 |
kfox1111 | not service package, with flags that turn off stuff. | 20:18 |
*** inc0 has quit IRC | 20:18 | |
*** jgriffith_away is now known as jgriffith | 20:18 | |
sbezverk | kfox1111: I could not care less about helm and endpoint, I was really happy with jinja2 :-) but since community decided to go with helm, my point is to use it as much as possible before inventing new tools | 20:18 |
kfox1111 | that fits the operator workflow too. | 20:18 |
kfox1111 | sbezverk: but the way your are aranging it is the heml/endpoint aproach. | 20:19 |
kfox1111 | service packages. | 20:19 |
kfox1111 | I'm with you, it would be nice if helm supported natively everything we want. | 20:20 |
sbezverk | kfox1111: that is not true. the only reason I used entrypoint was because of real dependency | 20:20 |
kfox1111 | Id be 100% on board with having helm do both package build templateing and package instantiation templating if it supported it today. | 20:20 |
kfox1111 | sbezverk: I'm not talking etnrypoint specificially. just the pattern discussed in the spec. | 20:20 |
sbezverk | but helm install microservice could be executed from operators as well | 20:20 |
sbezverk | that was my understanding | 20:20 |
kfox1111 | sbezverk: complexity. | 20:20 |
kfox1111 | I don't want the complexity of the orchestration engine of select super package, cut out junk just to get the single package I really want getting in the way. | 20:21 |
kfox1111 | thats complicated and potentially dangerious. | 20:21 |
kfox1111 | I'd rather just have it do the 1 exact thing I need it to do. | 20:21 |
sbezverk | kfox1111: and then invent something on top of that to get everything together? | 20:22 |
kfox1111 | temporarlily, until helm can do it itself. | 20:22 |
kfox1111 | I need the packages to have a good api. the build procedure can evolve over time. | 20:22 |
kfox1111 | if helm can do it natively at some point, I'm all for switching to native tools. | 20:23 |
sdake | apis are permanent things :) | 20:23 |
kfox1111 | but it cant today. | 20:23 |
kfox1111 | exactly. build tools come and go. but api's are semi-forever. :) | 20:23 |
sbezverk | kfox1111: if I get confirmation from helm that new release will be released before next holidays, would it be soon enough for you? | 20:24 |
kfox1111 | the packages provide an api. that of the vars used when instantiating them. | 20:24 |
kfox1111 | sbezverk: I think that means we can continue the discussion. I'm still not sold on having to use a super package to deploy the primary pacakges. | 20:24 |
kfox1111 | that api seems very wrong. | 20:25 |
sdake | ok just for reality check, goal is to release this stuff in ocata | 20:25 |
sbezverk | kfox1111: your manipulation with helm files to get them into package does not sounds safe to me | 20:25 |
sdake | 1.0.0 | 20:25 |
kfox1111 | sbezverk: is it different then how our containers are being built? | 20:25 |
kfox1111 | it parallels that workflow. | 20:26 |
sdake | build.py is a monster | 20:26 |
kfox1111 | I'm totally ok with redefining how we build it. | 20:26 |
kfox1111 | sdake: yeah. it could use some love. | 20:26 |
kfox1111 | it is a poc after all. | 20:26 |
sbezverk | kfox1111: we are trying to simplify things not complicate with new tools | 20:26 |
sdake | so i mean kolla repos build.py | 20:26 |
kfox1111 | sdake: no, I disagree. simplification is just one aspect of writing sofware. | 20:27 |
sdake | so/no | 20:27 |
kfox1111 | not turning off users by lack of features that meet their needs is another. | 20:27 |
kfox1111 | sdake: ah. | 20:27 |
sdake | if we can't make a decision we wont have any users to turn off :) | 20:27 |
kfox1111 | we have to ballance features that let users use the system with maintainability (code complexity, maintainability, etc) | 20:28 |
sdake | i think life was simpler pre-helm ;) | 20:28 |
sbezverk | sdake: +2 | 20:28 |
kfox1111 | sdake: orchestration in packages for me is a pretty strong showstopper for us. | 20:28 |
kfox1111 | thats why we agreed to helm being a simple packaging mechanism in the spec. :/ | 20:28 |
sdake | right | 20:29 |
sbezverk | kfox1111: I do not see orchestration in a package | 20:29 |
sdake | who said anything about orchestration in packages? | 20:29 |
kfox1111 | requiring super packages to depoy the real ones (from our perspective) is not following that agreement. | 20:29 |
sdake | (minus the entrypoint thing rolling in sbezverk's patch that needs attention) | 20:29 |
kfox1111 | imo | 20:29 |
sbezverk | if you are refering me using entrypoint once for vswitchd, then it is a requirmenet and not orchestration | 20:29 |
sdake | our=Kolla perspective? | 20:29 |
kfox1111 | sorry. my empoyer. | 20:29 |
sdake | ok so lets leave the entrypoint discussion in vswitchd out for now - that is an annoying special case | 20:30 |
sdake | since it just complicates the discussion with no real value | 20:30 |
kfox1111 | I want to be able to deploy nova-novncserver package. if I have to jump through nova to do so, it is involving orchestration like things in the mix. | 20:30 |
kfox1111 | I have to trust helms orchestration features won't mess with my deployment. :/ | 20:30 |
*** eaguilar has quit IRC | 20:30 | |
kfox1111 | I'm not that trusting. | 20:31 |
sbezverk | kfox1111: nova only holds global values | 20:31 |
kfox1111 | and the source to all the other services. | 20:31 |
sbezverk | which you can easily override at lower levels | 20:31 |
kfox1111 | if helm decides wronglyh to update something else, I'm screwed. | 20:31 |
kfox1111 | its far safer/simpler to just not have that code involved so it can't screw things up. | 20:31 |
sbezverk | kfox1111: if you decide wrongly ;-) ?? | 20:31 |
sdake | yup i had hoped helm would have slayed the problem you want solved kevin | 20:31 |
kfox1111 | sbezverk: then its on me. thats my job. | 20:32 |
kfox1111 | sdake: it can. my prototype does do it that way. | 20:32 |
kfox1111 | it just can't do it completely 100% with helm's build pipeline as the root of the build process. | 20:32 |
sdake | helm doesn't slay it your build tool does so | 20:32 |
sbezverk | kfox1111: I do not get you do not trust helm but explicitely trust your builder packager?? I am not sure if it a right approach | 20:32 |
kfox1111 | it still uses helm to do the build. ist just assembles the chart before telling helm to build it. | 20:33 |
sdake | sbezverk i think the builder package tool would be trustworthy as long as helm doesn't change directory layout and structure | 20:33 |
kfox1111 | sbezverk: heh. I especially trust that, condisering I did not write helm, but am writing the packages. ;) | 20:33 |
kfox1111 | but thats an edge case. ;) | 20:34 |
kfox1111 | sdake: and their layout is their contract. | 20:34 |
sbezverk | kfox1111: what stopps other people not to trush your software like you do to helm? | 20:34 |
kfox1111 | and we unit test things. | 20:34 |
sdake | the code looks straightforward enough - have concerns of it turning into a frankensystem if helm doesn't grow the necessary sub-deploy features | 20:34 |
sdake | sbezverk nothing really stops that | 20:34 |
sdake | sbezverk either people trust until given reason not to, or dont trust to begin with :) | 20:35 |
sdake | is portdirect alive | 20:35 |
portdirect | hi guys! | 20:35 |
sdake | portdirect are you following the conversation | 20:35 |
portdirect | 2 mins | 20:35 |
sdake | k | 20:35 |
kfox1111 | sdake: sub-deploy is out I think for me.... its like building a clock, throwing 10x the number of gears in it, and only ever using a subset of them. sure, they probably won't mess things up.... but they can get conected accidently for numberious reasions.. better just to leave them out. less complicated. | 20:36 |
portdirect | lots to parse | 20:36 |
kfox1111 | sdake: sbezverk: The primary differece beteen devs and ops is this | 20:36 |
sdake | portdirect take your time :) | 20:36 |
kfox1111 | devs are in the job of making the impossible possible. therefore, they tend to be optimists. | 20:36 |
sdake | i'm a dev and i'm definately a pragmatist | 20:36 |
kfox1111 | ops are tankless. they are either in 1 of 2 states. they are doing their job well, so nothings broken, and then people ask, "why do we need an op? Things are working great" | 20:37 |
kfox1111 | or, the system is broken, and you are the badguy. | 20:37 |
sdake | ok so lets stick on this sub-deploy idea | 20:37 |
sdake | you mention its out for you - so that means if helm ever implements subdeploy, that won't be an option we can use? | 20:37 |
sbezverk | gents I have meeting for 2 hours. Hopefully you will not the decision yet :-) | 20:37 |
kfox1111 | ops, trying to make the best out of the bad situation try hard not to get noticed, so try really hard to figure out what twill break things and avoid it. | 20:37 |
sbezverk | I meant take the decision.. | 20:38 |
kfox1111 | sdake: I'm pretty woried about that, yeah. | 20:38 |
sdake | kfox1111 so to take that to its logical conclusion we are going to be stuck with a custom build tool forever? | 20:38 |
kfox1111 | sdake: no, we just need to ensure that the functionality of our custom build tool makes it into helm. | 20:39 |
sayantan_ | Hi guys, I am trying to work on a multinode deployment using kolla-ansible. I am getting an error when I execute tools/build.py -p default | 20:39 |
sayantan_ | Traceback (most recent call last): | 20:39 |
sayantan_ | File "tools/build.py", line 39, in <module> | 20:39 |
sayantan_ | sys.exit(main()) | 20:39 |
sbezverk | no until kfox1111 starts trusting helm ;-) | 20:39 |
kfox1111 | the features that are lacking get implemneted. | 20:39 |
sayantan_ | File "tools/build.py", line 30, in main | 20:39 |
sayantan_ | statuses = build.run_build() | 20:39 |
sayantan_ | File "/root/kolla-ansible/kolla/image/build.py", line 960, in run_build | 20:39 |
sayantan_ | kolla.create_dockerfiles() | 20:39 |
kfox1111 | there are 2 as far as I can tell. | 20:39 |
sayantan_ | File "/root/kolla-ansible/kolla/image/build.py", line 693, in create_dockerfiles | 20:39 |
sdake | sayantan_ use a paste service plz | 20:39 |
sayantan_ | content = template.render(values) | 20:39 |
sayantan_ | File "/usr/local/lib/python2.7/dist-packages/jinja2/environment.py", line 989, in render | 20:39 |
sayantan_ | return self.environment.handle_exception(exc_info, True) | 20:39 |
sayantan_ | File "/usr/local/lib/python2.7/dist-packages/jinja2/environment.py", line 754, in handle_exception | 20:39 |
sayantan_ | reraise(exc_type, exc_value, tb) | 20:39 |
sayantan_ | File "/tmp/kolla-2016-11-28_20-37-04_quyOIE/docker/base/Dockerfile.j2", line 6, in top-level template code | 20:39 |
sayantan_ | {% import "macros.j2" as macros with context %} | 20:39 |
sayantan_ | File "/usr/local/lib/python2.7/dist-packages/jinja2/loaders.py", line 187, in get_source | 20:39 |
kfox1111 | 1. common packages. | 20:39 |
sayantan_ | raise TemplateNotFound(template) | 20:39 |
sayantan_ | jinja2.exceptions.TemplateNotFound: macros.j2 | 20:39 |
sdake | sayantan_ i can tell you your not going to get an answer with a spam of 30 lines int he channel :) | 20:39 |
kfox1111 | 2. templating for Chart/Variables. | 20:39 |
sayantan_ | How do I do that? I am new to IRC | 20:40 |
kfox1111 | sbezverk: you assume I don't think like other operators. ;) | 20:40 |
sdake | paste your stuff into paste.openstack.org | 20:40 |
sdake | it prints out a link | 20:40 |
sdake | put the link in irc | 20:40 |
kfox1111 | sbezverk: in a op world, trust is erned. | 20:40 |
sayantan_ | Thanks :P | 20:41 |
sdake | kfox1111 can you break out the commmon packages part a bit | 20:41 |
sbezverk | kfox1111: on this matter no. I think if we selected a tool, we need to leverage it as much as we can, otherwise why we selected it at the first place | 20:41 |
kfox1111 | sbezverk: because it solves real problem. just not every problem. dont use a hammer to screw in a nail. | 20:41 |
sdake | ok so - lets assume we use this custom build tool | 20:41 |
kfox1111 | sdake: talk more about it? | 20:41 |
sdake | question | 20:41 |
sdake | will we be able to deploy from one master chart? | 20:42 |
sdake | and also deploy from subcharts? | 20:42 |
kfox1111 | sdake: yes. I proof of concepted one master chart deploy and individual deploys. | 20:42 |
sdake | how is that different then having one package that has a subdeploy as a feature? | 20:42 |
sayantan_ | http://paste.openstack.org/raw/590710/ | 20:42 |
kfox1111 | sdake: there is no risk of nova update nova-novnc-proxy messing with nova-api if they are seperate packages. | 20:43 |
portdirect | sdake: this is the question I have - I think we need to see how helm implemnts the subdeploy feature | 20:43 |
kfox1111 | well, or should I say, drastically reduced. | 20:43 |
*** gfidente|afk has quit IRC | 20:43 | |
sdake | i think portdirect is spot on here | 20:44 |
kfox1111 | helm is really doing someting weird when it comes to package managers. | 20:44 |
portdirect | kfox1111: unless I've missed somthing helm is essentially just a templating engine that keeps track of the templates its thrown at the k8s api? | 20:44 |
sdake | its doing bundled libraries in essence (in the rpm world) | 20:44 |
kfox1111 | it is mixing package management, (yum like) with orchestration (puppet, deploy complex applications using packages) | 20:44 |
kfox1111 | its considerd bad form in the rpm world to make one rpm that goes and rpm -Uvh's a bunch of other rpms. | 20:45 |
kfox1111 | (after many years of blood due to peple trying it and getting hurt. :/ ) | 20:45 |
kfox1111 | but helm's doing that. deploy one super package, and it deployos lots of little packages. | 20:45 |
kfox1111 | I get the desire to do it, but to me, thats a strong antipattern. I'm ok supporting those that want to do it that way, | 20:46 |
kfox1111 | but I have no desire to get bit by that way of doing things. seen it go horribly wrong too many times. | 20:46 |
sdake | back on portdirect 's point, if subdeploy only affects the subdeployed package, then the argument that orchestration is involved doesn't exist? | 20:46 |
*** rhallisey has quit IRC | 20:46 | |
*** aric49 has quit IRC | 20:46 | |
sdake | kfox1111 ^^ | 20:46 |
kfox1111 | sdake: I'm trying to come up with an analogy that can explain that... | 20:47 |
kfox1111 | its basically telling the orchestration system to try and ignore parts of itself. | 20:47 |
kfox1111 | "lets make the complicated orchestration system more complicated to try and get it to do something simple, and hope it doesn't get in the way" | 20:47 |
kfox1111 | I just want to do the basic thing without any of the complexity in the first place. | 20:48 |
sbezverk | kfox1111: not orchestration but rendering system | 20:48 |
kfox1111 | what helm was originally intended to do. | 20:48 |
kfox1111 | here's a simple package, load it up for me. | 20:48 |
portdirect | kfox1111: I think I see where you are coming from, but i think this is a matter of perspective and how we build/layout the packages | 20:48 |
kfox1111 | it grew the idea of superpackages later, when someone thought that was a good idea. :/ | 20:48 |
kfox1111 | portdirect: I think those are two seperate issues. | 20:48 |
sdake | well we do need subdeploy | 20:49 |
kfox1111 | portdirect: build/layout of the files in the packages | 20:49 |
sdake | that is an essnetial feature of our architecture | 20:49 |
kfox1111 | sdake: I think we're not matching up on terminology. | 20:49 |
sdake | let me defifne subdeploy then | 20:49 |
portdirect | bear with me here, it will take me a min to get this out | 20:49 |
sdake | subdeploy is something like helm deploy openstack --sub-package=nova-novncproxy | 20:50 |
kfox1111 | sdake: that is one way to do it. | 20:50 |
kfox1111 | the other is just helm deploy nova-novncporxy | 20:50 |
kfox1111 | helm deploy openstack --sub-package=nova-novncproxy makes me nervious. helm deploy nova-novncporxy does not. | 20:50 |
sdake | ok so boiled down to essence these are the two options? | 20:50 |
portdirect | i think that it may be possible to get the best of both worlds using a lightweight build tool - one that build's a super package and another that builds micro-pakages for each service | 20:51 |
kfox1111 | there is no reason, you can't do a stand alone nova-novncproxy that can get bundled into a package 'openstack' | 20:51 |
kfox1111 | so that 'helm deploy openstack' works too. | 20:51 |
portdirect | as the superpackae is essentially just composed of the micropackages | 20:51 |
kfox1111 | portdirect: yeah. thats what mine does actaully. | 20:51 |
kfox1111 | portdirect: it build the micropackages. the super packages pretty well normal helm packages. would just have dependencies on the micropackages. | 20:52 |
sdake | ok i guess i'm good with that model - if the build system doesn't spiral into a frankensystem | 20:52 |
kfox1111 | the tradeoff is, where is the complexity. at build time, where it can be easily tested afterwards, or instantiation time. | 20:53 |
sdake | kfox1111 however the patch you submitted does not follow the "slew of packages" lets build them into a metapackage | 20:53 |
kfox1111 | I'd rather see a bit more pushed towards build time. thats all. | 20:53 |
portdirect | my issue with your method is with the directory structure - as what I'm proposing I think cloud be achived in about 30 lines of bash - if we went with a similar layout to sbezverk's | 20:53 |
sdake | right directory structure | 20:53 |
sdake | exactly my problem too :) | 20:53 |
kfox1111 | sdake: portdirect that could be. I tried something like that initially, but was harder then it looked when I got into it. | 20:54 |
kfox1111 | I'm not tied to structure. | 20:54 |
kfox1111 | it can be anything that works. | 20:54 |
kfox1111 | I kind of like ryan's idea of making a templates subdir. | 20:54 |
portdirect | so looking at: https://review.openstack.org/#/c/401394/ | 20:55 |
portdirect | if we symlinked the _helpers.tpl into the right place for each set of templates, and then added the appropriate values (via som method, to each subchart) we could then spit out a bunch of packages, or leave it as-is and spit out a single meta-package - unless I'm mistaken | 20:56 |
kfox1111 | portdirect: I reversed the flow, and did it with a common package. | 20:57 |
kfox1111 | put the shared library in a single package, then made it a dep for each microservice. | 20:57 |
kfox1111 | it worked well, except that vars would have to be done as globals, which I think is problematic for other reasons. | 20:57 |
sdake | shared library seems like a premature optimizatio nto me | 20:57 |
kfox1111 | so I wroked around that with the common-vars stuff being merged into vars. | 20:57 |
sdake | which is a super anti-pattern in softwar eengineering | 20:57 |
sbezverk | kfox1111: what you did with common it looks more like a workaround solution than the right use of tool.. | 20:57 |
kfox1111 | sdake: we've had a shared lib for a while now. it has sped thigns up significantly. | 20:57 |
kfox1111 | sbezverk: quite possibly. they really need a concept of a lib/common package. | 20:58 |
kfox1111 | not a sub program package. | 20:58 |
sdake | sped up development? | 20:58 |
kfox1111 | sdake: we didn't have to keep updating dozens of files to add common things. | 20:58 |
kfox1111 | and dealing with the review of all of that. | 20:58 |
sdake | ok kfox1111 - can you write down in the whiteboard what exactly helm needs with exquisite detail from your pov | 20:59 |
sdake | i guess this build system will have to do - with a resorted directory structure | 20:59 |
sdake | i think each subpackage should have a consistent directory structure that is used in helm proper | 21:00 |
sdake | e.g. nova-novncproxy | 21:00 |
sdake | kfox1111 roger - apologies for not being able to focus any attention on kolla-kubernetes during my ptl-ship - it was literally a 20 hr a day 7 day a week job just to stay on top of the kolla repo | 21:01 |
kfox1111 | sdake: so, what I think the build should do, and what helm should do, or staring at the goals I stated in the review, and showing which peices solve which problems? | 21:01 |
kfox1111 | sdake: no worries. we're all busy. | 21:02 |
sdake | kfox1111 too many statements in your question for me to parse properly could you restate? | 21:03 |
kfox1111 | sdake: "ok kfox1111 - can you write down in the whiteboard what exactly helm needs with exquisite detail from your pov | 21:03 |
kfox1111 | " | 21:03 |
kfox1111 | I'm having trouble parsing that. | 21:03 |
sdake | ok above in the scrollback you listed 2 things | 21:03 |
kfox1111 | "what exactly helm needs" | 21:03 |
kfox1111 | helm's a tool, without needs. I'm confused. | 21:03 |
sdake | what we need exactly from helm | 21:04 |
sdake | we have needs of helm that it doesn't fulfill | 21:04 |
kfox1111 | ah. | 21:04 |
kfox1111 | gotcha. | 21:04 |
kfox1111 | that, I can do. :) | 21:05 |
sdake | whiteboard section of launchpad on the blueprint | 21:05 |
sdake | so i think where we stand re helm packaging is we need the following | 21:05 |
sdake | a directory that contains pristine helm charts for each single microservice | 21:05 |
kfox1111 | I don't think we can make prestine helm charts without some templating. | 21:06 |
kfox1111 | which then arn't exactly helm charts. | 21:06 |
sdake | and meta packages which are built | 21:06 |
sdake | ok lets tackle templating next up | 21:06 |
kfox1111 | k | 21:06 |
sdake | so pristine helm charts | 21:06 |
sdake | then some type of chart that packages them into services, like nova, neutorn, etc | 21:07 |
sdake | then some type of chart that packages all the subpackages into one big master chart | 21:07 |
sdake | then eveyrone gets what they want and the architecture is consistent with the implementation | 21:07 |
kfox1111 | right. s/chart/package/ on the your first line and we're in agreement. | 21:07 |
kfox1111 | how the micropackages are built is my concern. the rest I think are fairlyl standard for helm. | 21:08 |
sdake | chart package I dunno the difference :) | 21:08 |
kfox1111 | package is a binary tarball looking thing. | 21:08 |
kfox1111 | chart is... source for it I'd say. | 21:08 |
kfox1111 | the dir thing you "helm package foo" | 21:08 |
sdake | i think we want to work from source to build the packages | 21:09 |
portdirect | right - so now we are back to templating :) | 21:09 |
kfox1111 | right. templating. | 21:09 |
sdake | ok lets make sbezverk is in agreement :) | 21:09 |
sdake | make sure that is | 21:09 |
sdake | he said he would be on a call for a bit | 21:09 |
portdirect | yeah - untill he is onboard this is just discussion | 21:09 |
v1k0d3n | i see debates. | 21:10 |
v1k0d3n | :) | 21:10 |
v1k0d3n | hi guys | 21:10 |
portdirect | well hello. | 21:10 |
v1k0d3n | lol | 21:10 |
sdake | v1k0d3n there ya go :) | 21:10 |
kfox1111 | v1k0d3n: hey. :) | 21:10 |
kfox1111 | v1k0d3n: no worries. theres a few details about helm to nail down, and we're working through them. :) | 21:11 |
v1k0d3n | cool cool | 21:11 |
sdake | ok kfox1111 this is where we put into the review the log of the irc commentary | 21:11 |
sdake | http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-11-28.log.html#t2016-11-28T20:13:13 | 21:11 |
sdake | so people understand the high bandwidth conversation thta just took place | 21:12 |
kfox1111 | sdake: looks good. thanks. | 21:12 |
sdake | when they look at the reviews later | 21:12 |
portdirect | v1k0d3n: if you have any input it would be appricated | 21:12 |
sdake | lets wait for sbezverk to get off his call before tackling templating | 21:12 |
portdirect | +1 | 21:13 |
kfox1111 | yeah. if it weren't for the templating, he's right, we should just use helm natively to build everyting. | 21:13 |
kfox1111 | so that part needs to be discussed and agreed on. | 21:13 |
sdake | kfox1111 that doesn't handle your subdeploy case | 21:13 |
kfox1111 | (main deploy! :) | 21:14 |
kfox1111 | well, the overarching packages can be built in the normal helm way I htink. with 'dependencies' on the subpackages. | 21:15 |
kfox1111 | I did it that way when testing the poc. | 21:15 |
v1k0d3n | have you guys asked alanmeadows? | 21:16 |
*** bmace has quit IRC | 21:16 | |
kfox1111 | v1k0d3n: ask what? | 21:16 |
*** bmace has joined #openstack-kolla | 21:16 | |
v1k0d3n | he's been working out some things on our end which we believe are extremely flexible. | 21:16 |
v1k0d3n | kfox1111 "portdirect: v1k0d3n: if you have any input it would be appricated" | 21:16 |
kfox1111 | ah. | 21:17 |
portdirect | kfox1111: they have been working with helm for a bit | 21:17 |
sdake | v1k0d3n i think the best method there is for alanmeadows to read the two reviews, and the irc log i linked above | 21:17 |
sdake | so he has context for the conversation | 21:17 |
sdake | so we don't have to catch him up again | 21:18 |
* alanmeadows scrolls up | 21:18 | |
sdake | alanmeadows it begins here: http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-11-28.log.html#t2016-11-28T20:13:13 | 21:18 |
kfox1111 | yeah. helm's looking pretty nice. I'm totally sold on it for package management/instantiation. I'm just very sceptical of it for orchestrating large apps. | 21:18 |
sdake | alanmeadows recommend reading reviews first | 21:18 |
kfox1111 | I just want to be able to skip that part when desired. | 21:18 |
sdake | kfox1111 i'm tired of clicking any chance you can link the two reviews for alanmeadows | 21:19 |
portdirect | https://review.openstack.org/#/c/401394/ | 21:19 |
alanmeadows | if this re: uber chart, subchart, etc | 21:19 |
sdake | thanks portdirect | 21:19 |
kfox1111 | https://review.openstack.org/#/c/396296/ is the other. | 21:19 |
alanmeadows | and indeed it appears so :) | 21:19 |
portdirect | https://review.openstack.org/#/c/401394/ | 21:19 |
sdake | thanks kfox1111 | 21:19 |
alanmeadows | let me take a look | 21:19 |
alanmeadows | but on the whole one of the challenging things | 21:20 |
portdirect | lol my bad | 21:20 |
alanmeadows | is the SAP approach is if you dont use the uber chart, too bad, you cant play | 21:20 |
alanmeadows | and I'm not really sure I like that | 21:20 |
kfox1111 | alanmeadows: exactly. :/ | 21:20 |
alanmeadows | its especially painful during development | 21:20 |
kfox1111 | thats what I've been trying to avoid. :/ | 21:20 |
alanmeadows | so the way we're architecting aic-helm PoC is each chart is always install-able individually | 21:20 |
alanmeadows | but this creates some problems | 21:21 |
alanmeadows | (you can still use the uber chart, but its a convenience, not a requirement) | 21:21 |
kfox1111 | cool. so aic-helm sounds like its going in the same direction I'm wanting to go. | 21:21 |
kfox1111 | what issues have you hit? | 21:22 |
*** kristia__ has joined #openstack-kolla | 21:22 | |
alanmeadows | this requires the implementation of some kind of helper though which is now not exactly 100% helm, but its a stop gap in my mind | 21:22 |
* kfox1111 nods | 21:22 | |
kfox1111 | yeah. | 21:22 |
*** kristian__ has quit IRC | 21:22 | |
alanmeadows | imagine something like your FQDN | 21:22 |
alanmeadows | you want that global everywhere | 21:22 |
alanmeadows | but you dont want to repeat it in 30 values.yaml files | 21:23 |
sdake | imo lets solve that iteratively | 21:24 |
alanmeadows | an uber chart could solve that but again, back to the uber chart being a requirement | 21:25 |
alanmeadows | so our stop gap right now until helm can solve this (i've got an issue creation in my todo) | 21:25 |
alanmeadows | is Make magic shoving a "_common.tpl" into every subchart | 21:25 |
kfox1111 | alanmeadows: basically what I did too. | 21:25 |
alanmeadows | a pre-build step... not 100% native but not sure what else to do right now, I hate to give up on the dream of independent charts | 21:26 |
*** fguillot has quit IRC | 21:26 | |
kfox1111 | I cheeted a little more, and put it in a subchart. if wrapped in a macro, it shows up in the parent package when instantiated. | 21:26 |
portdirect | alanmeadows: I'd come to a similar conclusiion that this is our only option right now | 21:26 |
kfox1111 | alanmeadows: so, please review https://review.openstack.org/#/c/396296/ and tell me what you think. | 21:26 |
kfox1111 | it seems similar to your approach. | 21:26 |
alanmeadows | kfox1111: started there too, I am trying to remember what issue was hit that ended up with the even more hacky _common.tpl insertion.... | 21:27 |
kfox1111 | the directory layout is a bit confusing/suboptimal. as its just a poc. | 21:27 |
alanmeadows | but that is definitely more desirable | 21:27 |
alanmeadows | as at least its all helm | 21:27 |
kfox1111 | alanmeadows: ah. I'd do the same as you, if I bumped into something. | 21:27 |
kfox1111 | easy enough to just copy it into the package itself rather then a subpackage. | 21:28 |
alanmeadows | yeah just removes some of the magic ;-) | 21:28 |
*** kristia__ is now known as kristian__ | 21:28 | |
kfox1111 | we can even change it now to avoid some pain later. | 21:28 |
kfox1111 | I'm not tied to it. was curious if it would wrok at all in helm, and surprisingly it did. | 21:29 |
alanmeadows | so if memory serves defines in the "helper" subchart will bubble up | 21:31 |
alanmeadows | but globals wont | 21:31 |
kfox1111 | right. | 21:31 |
*** lrensing has quit IRC | 21:32 | |
alanmeadows | which was depressing | 21:32 |
kfox1111 | vars defined in the template can't buble back to the calling template. :/ | 21:32 |
alanmeadows | which makes sense | 21:32 |
kfox1111 | heh. yeah. | 21:32 |
alanmeadows | but it makes it messy | 21:32 |
kfox1111 | I had the same response. :) | 21:32 |
*** schwicht has quit IRC | 21:32 | |
kfox1111 | would be nice if you could return a hash. | 21:32 |
kfox1111 | I guess I did end up solving it the same way you did... | 21:32 |
kfox1111 | I have a main that's copied to every package... | 21:33 |
*** sdake_ has joined #openstack-kolla | 21:33 | |
kfox1111 | https://review.openstack.org/#/c/396296/27/helm/src/common_main.yaml | 21:33 |
alanmeadows | I can't find it in my history I think what I hit | 21:33 |
kfox1111 | which then calls the template from the package. | 21:33 |
alanmeadows | was literally inconsistency | 21:33 |
alanmeadows | in other words a define in a child | 21:33 |
alanmeadows | would work *some of the time* | 21:34 |
kfox1111 | yeah. I saw that too. | 21:34 |
alanmeadows | best exampled | 21:34 |
alanmeadows | by running dry-run --debug | grep ... | 21:34 |
alanmeadows | and it was hit or miss | 21:34 |
alanmeadows | so I shelved it | 21:34 |
kfox1111 | if you go up a level, and make super package that depends on 2 subpackages and they both depend on common, and you try and shre some template filenames, it can get ugly. :/ | 21:34 |
kfox1111 | sry. macronames | 21:35 |
kfox1111 | so a main macro in subpackage a, and one in b, | 21:35 |
kfox1111 | you might get an instantiation of a & b, a & a, or a & b. | 21:35 |
*** Jeffrey4l has quit IRC | 21:35 | |
*** sdake has quit IRC | 21:35 | |
kfox1111 | you might get an instantiation of a & b, a & a, or b & b. | 21:35 |
*** YefimG has joined #openstack-kolla | 21:35 | |
kfox1111 | they definitely are doing some kind of random hashing on template load ordering. | 21:36 |
alanmeadows | so we now have an openstack-base, which I'll be renaming to something more generic as this also applies to ceph, maas, etc. to just "common" or whatever and its only purpose is to be included everywhere for some other helpful things, like ceph secret installation but also _common.tpl generation | 21:36 |
kfox1111 | which they do note in the docs | 21:36 |
*** schwicht has joined #openstack-kolla | 21:36 | |
alanmeadows | I can live with the workaround because I think we can pressure helm to come up with a solution for this | 21:37 |
alanmeadows | I have great concerns | 21:37 |
kfox1111 | +1 | 21:37 |
alanmeadows | about the uber chart and future upgrades | 21:37 |
kfox1111 | me too. | 21:37 |
alanmeadows | if you break it or something goes wrong | 21:38 |
sdake_ | you can't pressure upstreams into doing anything they don't want to do fwiw :) | 21:38 |
alanmeadows | you need to what, redo everything including mariadb, etc? | 21:38 |
kfox1111 | sdake_: as in, add development effort, or shine a light on a use case not covered. | 21:38 |
alanmeadows | sdake_: you havent seen how fast I can type into separate message windows! | 21:38 |
kfox1111 | alanmeadows: exactly. scares me as an op. | 21:38 |
sdake_ | alanmeadows :) | 21:38 |
alanmeadows | also | 21:39 |
alanmeadows | the uberchart breaks the potential | 21:39 |
alanmeadows | for namespace chunking | 21:39 |
kfox1111 | alanmeadows: seems like we've hit convergent evolution. :) | 21:39 |
alanmeadows | as far as I can see at least | 21:39 |
kfox1111 | right. | 21:39 |
YefimG | Hi, guys! Trying to install ceilometer with gnocchi backend, but having Ceilometer bootstrap container failed: Container exited with non-zero return code. Is that even a supported configuration? | 21:39 |
sdake_ | YefimG your looking for jeffrey4l | 21:40 |
kfox1111 | I've got multiple regions and multiple host aggregates too, | 21:40 |
sdake_ | YefimG he is in apac | 21:40 |
kfox1111 | which I think will fit poorly in the uberchart model. | 21:40 |
kfox1111 | (oh, and dvr) | 21:40 |
kfox1111 | multiple types of l3 agents, etc. | 21:40 |
kfox1111 | I don't think helm will support a 1 super package, multiple instances of a sub package use case well, or soon for a while. | 21:41 |
kfox1111 | and openstack really needs it for non trivial clouds from my experience. | 21:41 |
sdake_ | who knows what helm will support | 21:41 |
sdake_ | we follow our upstreams not visa versa :) | 21:41 |
akwasnie | sdake: pbourke: here is the dashboard from summit http://paste.openstack.org/show/590718/ | 21:41 |
kfox1111 | sdake_: sure. just saying its hard, so hard things usually take longer then easy things. so unlikely soon. :) | 21:41 |
sdake_ | this is why dependency management is so important :) | 21:41 |
jrich523 | hey guys, i was just using the openstack client, was going to try and look up a user (user ID on an image) and im getting a 401 (needs auth) which is odd because im able to run other things... i was wondering if i needed to set a domain context like i do on the web ui | 21:42 |
akwasnie | sdake: pbourke: sorry for late notice, I forgot I had it on another laptop :) | 21:42 |
jrich523 | i dont know what you're talking about sdake_ but i couldnt agree more :) | 21:42 |
sdake_ | jrich523 did you create your admin-oepnrc.sh via kolla post-deploy? | 21:43 |
jrich523 | yeah the source'ing works fine | 21:43 |
YefimG | sdake_: Thanks! | 21:43 |
jrich523 | i can query images, vms etc | 21:43 |
jrich523 | its just with Users, which happens to be ldap so i know that also makes things funky | 21:43 |
sdake_ | YefimG no problem - ffwiw it is supported in 3.0.1 - doesn't mean it works for you tho - jeffrey4l can sort out if its been fixed and awaiting a backport tag | 21:44 |
jrich523 | if the user list should just work, (no need for domain context or whatever) then its not the CLI and i'll go deal with that... just wanted to make sure i wasnt missing some basic step | 21:44 |
*** hvlad has joined #openstack-kolla | 21:44 | |
alanmeadows | kfox1111: https://github.com/alanmeadows/aic-helm/blob/master/Makefile#L40 | 21:44 |
alanmeadows | thats my workaround for now | 21:45 |
sdake_ | jrich523 no experience with ldap and kolla | 21:45 |
alanmeadows | so here is my thought | 21:45 |
jrich523 | k, thanks | 21:45 |
alanmeadows | and I think SAP came to this conclusion too | 21:45 |
*** matrohon has quit IRC | 21:45 | |
kfox1111 | ah. using make for it. | 21:45 |
jrich523 | so the short of it is, i shouldnt need to do anything like set context, it should just spew all users? | 21:46 |
kfox1111 | nice. | 21:46 |
alanmeadows | endpoint URLs get defined in something common like this, ports belong as globals per chart | 21:46 |
kfox1111 | do you template out version numbers too? | 21:46 |
alanmeadows | that way you combine the two you can create an endpoint for any service | 21:46 |
alanmeadows | I do not at the moment | 21:46 |
kfox1111 | as an operator, I'd like to be able to build an updated set of containers, then build an updated set of packages, then do a minor rolling upgrade. | 21:46 |
kfox1111 | ah. k. | 21:46 |
*** Pavo has quit IRC | 21:47 | |
* sdake_ dislikes agile fwiw kfox1111 :) | 21:47 | |
jrich523 | you're certainly one of the few sdake_ :) | 21:47 |
*** Jeffrey4l has joined #openstack-kolla | 21:47 | |
kfox1111 | sdake_: I have issues with agile too, btw. :) | 21:47 |
sdake_ | nah i prefer open source method | 21:47 |
jrich523 | Agile is good, agile is not... most places do agile | 21:47 |
kfox1111 | it works great, unless you have a team where your members are operators. ;) | 21:48 |
sdake_ | it works great unless your team is spread across the world | 21:48 |
kfox1111 | where their time is random due to machine uptime obligations. | 21:48 |
sdake_ | Agile requires collocationt o work effectively | 21:48 |
kfox1111 | then you have no idea how long anything will take, and it all falls apart. | 21:48 |
sdake_ | ya agile does provide capacity management - something sorely lacking from open source | 21:48 |
kfox1111 | guess that applies to opensource too. no idea how long anything wil take. | 21:48 |
kfox1111 | but, thats kind of the nature of opensource too. | 21:49 |
sdake_ | however open source is done by volunteers so capacity management in open source is impossible | 21:49 |
kfox1111 | no fixed capacity. | 21:49 |
kfox1111 | right. | 21:49 |
jrich523 | is there an "opensource" workflow? | 21:49 |
jrich523 | guess i've never looked, but would be neat to read about | 21:49 |
sdake_ | jrich523 there is - but it hasn't been written down ;) | 21:49 |
kfox1111 | jrich523: defacto. I don't know if its written down | 21:49 |
kfox1111 | heh | 21:49 |
jrich523 | lol, so no :) | 21:49 |
kfox1111 | :) | 21:49 |
*** inc0 has joined #openstack-kolla | 21:49 | |
sdake_ | ok well that was entertaining lets wait for sbezverk to catch up with the log posted in each review | 21:50 |
inc0 | hello | 21:50 |
sdake_ | sup inc0 | 21:50 |
*** sdake_ is now known as sdake | 21:50 | |
jrich523 | ticket based? open a ticket ("issue") with tasks, someone finishes it, sorta like agile, small sections of well defined work..... | 21:50 |
jrich523 | howdy inc0 | 21:50 |
v1k0d3n | portdirect: hey man | 21:50 |
sdake | jrich523 open source methodology scales to thousands of developers | 21:51 |
sdake | jrich523 agile does not | 21:51 |
sdake | that is my main beef ;) | 21:51 |
jrich523 | lol fair point | 21:51 |
jrich523 | i think the location point is a stronger one | 21:51 |
inc0 | sdake, also doesn't really support any form of concrete goal;) everybody does what the hell they want;) | 21:51 |
jrich523 | its all about working in groups, team dev etc | 21:51 |
sdake | ya that too :) | 21:51 |
*** Pavo has joined #openstack-kolla | 21:51 | |
inc0 | which is cool | 21:51 |
jrich523 | sorta | 21:52 |
kfox1111 | jrich523: its desire based. | 21:52 |
sdake | inc0 thats called the "Hidden Hand" | 21:52 |
kfox1111 | if someone cares enough about something, they fix it, or they somehow convince a dev to fix it. | 21:52 |
jrich523 | i think thats a category on porn hub sdake lol | 21:52 |
kfox1111 | (monitarily or otherwise) | 21:52 |
inc0 | yeah, but this hidden hand can smack people only so hard | 21:52 |
*** jheroux has quit IRC | 21:52 | |
alanmeadows | kfox111: the other thing to develop is consistent values across projects ;-) | 21:52 |
alanmeadows | it can quickly get out of hand | 21:53 |
sdake | inc0 https://en.wikipedia.org/wiki/Invisible_hand | 21:53 |
kfox1111 | alanmeadows: this looks very similar to where I was going. | 21:53 |
alanmeadows | had to nip that early on which even with 4 projects was a big effort | 21:53 |
inc0 | and build culture of quality in community | 21:53 |
kfox1111 | alanmeadows: yeah. and governence. far to often ignored but makes or breaks an effort. | 21:53 |
inc0 | getting good culture = win | 21:53 |
inc0 | governance in OpenStack is very lightweight, probably that's the only reason it still works | 21:54 |
kfox1111 | yeah. | 21:55 |
sdake | ok well while u guys debate which methodology is best this old man is gonna take a nap | 21:55 |
alanmeadows | either something about great minds or fools seldom differ | 21:55 |
kfox1111 | mostlly works... sort of... | 21:55 |
alanmeadows | one of those two | 21:55 |
sdake | (development methodology that is) | 21:55 |
kfox1111 | alanmeadows: hehe. exactly. :) | 21:55 |
kfox1111 | alanmeadows: at least we have company in our madness, if nothing else. :) | 21:55 |
jrich523 | lol | 21:55 |
jrich523 | so you've got that going for you | 21:55 |
kfox1111 | its always conforting to find someone else doing things the same way through experience. it either shows you your are on the right path, or the universe is playing a bigger trick on you then you think. ;) | 21:56 |
kfox1111 | (and you then don't take all the blame. :) | 21:57 |
alanmeadows | you can either take the credit or if it flops | 21:57 |
alanmeadows | just say you copied this guy over here | 21:57 |
alanmeadows | ;-) | 21:57 |
* kfox1111 nods :) | 21:57 | |
jrich523 | i'll be sure to blame you the next time i can alanmeadows :) | 21:57 |
jrich523 | alan did it! | 21:57 |
kfox1111 | sdake: I gota head out now for a couple hours. :/ | 21:58 |
kfox1111 | meetings. | 21:59 |
alanmeadows | kfox1111: when you get a moment | 21:59 |
kfox1111 | alanmeadows: whats up? | 22:00 |
alanmeadows | it might be nice to talk about your thinking wrt neutron components | 22:00 |
kfox1111 | yeah. that would be good. um... | 22:00 |
alanmeadows | I don't have a super strong preference but it does present two paths | 22:00 |
alanmeadows | does the operator control how to configure neutron via helm install <my list of comps> | 22:00 |
kfox1111 | I've got meetings until 4:30 pst though. :/ | 22:00 |
alanmeadows | or helm install neutron --set .... | 22:00 |
alanmeadows | yeah no rush | 22:00 |
kfox1111 | been debating that with sbezverk. | 22:01 |
kfox1111 | I prefer helm install neutron-l3-agent-compute, neutron-l3-agent-network, etc. | 22:01 |
kfox1111 | same package, instantiated multiple times with different flag. | 22:01 |
kfox1111 | rrr, sorry. | 22:01 |
alanmeadows | and thats fine its just this is not an area I've put much thought into | 22:01 |
kfox1111 | elm install neutron-l3-agent --set type=compute | 22:01 |
alanmeadows | so I think understanding what drove that is good | 22:02 |
alanmeadows | I've not put much | 22:02 |
alanmeadows | rather | 22:02 |
kfox1111 | yeah. should do the same for host aggretates too. | 22:02 |
*** jtriley has joined #openstack-kolla | 22:02 | |
alanmeadows | the only thing that complicates that | 22:02 |
kfox1111 | helm install nova-compute --set type=intel-foo | 22:02 |
alanmeadows | is the installer has to have more knowledge | 22:02 |
kfox1111 | helm install nova-compute --set type=amd-bar | 22:02 |
alanmeadows | i suppose either way its the same | 22:03 |
kfox1111 | yeah. | 22:03 |
alanmeadows | whether with sets | 22:03 |
alanmeadows | or multiple installs | 22:03 |
inc0 | one with amd won't work | 22:03 |
kfox1111 | ok. really gota go. lets talk soon. | 22:03 |
alanmeadows | yeah lates | 22:03 |
inc0 | I | 22:03 |
inc0 | I'm from intel, I think I'm required to say that | 22:03 |
alanmeadows | but that immediately raises suspicion | 22:03 |
alanmeadows | about your amd assertions | 22:04 |
alanmeadows | ;-) | 22:04 |
*** lamt has quit IRC | 22:05 | |
*** TxGirlGeek has quit IRC | 22:07 | |
*** jtriley has quit IRC | 22:10 | |
*** lamt has joined #openstack-kolla | 22:10 | |
sdake | inc0 i agree one with amd wont work and i'm not from intel so not required to say that ;-) | 22:10 |
inc0 | uff thanks sdake you just saved last shreds of my credibility | 22:11 |
portdirect | much better for heating your house though | 22:11 |
sdake | inc0 nah you got plenty | 22:11 |
*** TxGirlGeek has joined #openstack-kolla | 22:11 | |
inc0 | srwilkers, ping | 22:13 |
v1k0d3n | hey guys... | 22:16 |
inc0 | wassup v1k0d3n | 22:17 |
v1k0d3n | not sure it's totally clear to me yet, but does kolla-ansible work just fine on ubuntu 16.04? i'm hearing mixed things... | 22:17 |
inc0 | v1k0d3n, I'm running 16.04 all the time | 22:17 |
inc0 | if it doesn't I'd like to know, it should. | 22:18 |
*** goldyfruit has quit IRC | 22:18 | |
sdake | v1k0d3n if you mean 3.0.1 that was definately tested | 22:18 |
sdake | master is passing the gate - as enemic as it is | 22:18 |
inc0 | we run xenial inside container | 22:18 |
v1k0d3n | oh...wonder why i hear mixed things then. | 22:19 |
*** TxGirlGeek has quit IRC | 22:19 | |
v1k0d3n | so just follow instructions on ubuntu with systemd. | 22:19 |
v1k0d3n | ok | 22:19 |
inc0 | yeah, 2.0 was based on trusty, if they run mitaka it might be funky | 22:19 |
sdake | depends what mixed tings you hear | 22:19 |
sdake | for example we think gpu passthrough is busted on ubuntu | 22:19 |
inc0 | v1k0d3n, or use bootstrap-servers | 22:19 |
*** TxGirlGeek has joined #openstack-kolla | 22:20 | |
sdake | Jeffrey4l another report of problem with gnocchi and ceilometer | 22:20 |
sdake | Jeffrey4l i never tested that code - does it work for you? | 22:20 |
*** jrist has joined #openstack-kolla | 22:20 | |
v1k0d3n | inc0: good to know. i will play around again some more later and verify this. thanks for the heads up guys. | 22:21 |
inc0 | v1k0d3n, sure, by all means it should be good. let us know what issues people see | 22:21 |
inc0 | also, I have question | 22:21 |
inc0 | since you're around | 22:21 |
*** jheroux has joined #openstack-kolla | 22:22 | |
inc0 | v1k0d3n, have you guys seen work sbezverk and kfox1111 done with helm? | 22:22 |
*** jascott1 has quit IRC | 22:22 | |
*** jheroux has quit IRC | 22:24 | |
*** jascott1 has joined #openstack-kolla | 22:24 | |
v1k0d3n | not really. hard to keep up and just back from vacation. | 22:25 |
*** TxGirlGeek has quit IRC | 22:25 | |
inc0 | kk, check these out plz | 22:25 |
inc0 | let's get stuff merged and working together in kolla-k8s asap plz | 22:25 |
v1k0d3n | i can check out. | 22:25 |
v1k0d3n | bit stretched thin...but first priority for us 100% is our PoC. | 22:26 |
v1k0d3n | it's been that way all along for us. | 22:26 |
*** jascott1 has quit IRC | 22:26 | |
*** jascott1 has joined #openstack-kolla | 22:26 | |
inc0 | fair enough, let's just keep in mind that we'll want to have single project at the end of the day | 22:27 |
v1k0d3n | boss makes the calls. extremely happy to merge though. | 22:27 |
*** sayantan_ has quit IRC | 22:27 | |
v1k0d3n | i find myself in this place a lot. | 22:27 |
v1k0d3n | the intent is only to have one project when this is over..... | 22:28 |
sdake | portdirect do you have that irc log - it wasn't posted in either review | 22:28 |
v1k0d3n | saying this in the clear for everyone to see :) | 22:28 |
sdake | portdirect or must i hunt down the irc log myself | 22:28 |
sdake | yet again... | 22:28 |
inc0 | cool, that's what I'm saying, you guys should keep track on kolla-k8s community too | 22:28 |
portdirect | sdake: this one ? http://eavesdrop.openstack.org/irclogs/%23openstack-kolla/%23openstack-kolla.2016-11-28.log.html#t2016-11-28T20:13:13 | 22:29 |
*** zigo has quit IRC | 22:29 | |
inc0 | to make sure that 1. your poc is as good as it gets and 2. we won't close any doors by omission by agreeing on some approach | 22:29 |
sdake | portdirect mind posting those in the two reviews in question | 22:29 |
portdirect | np | 22:29 |
inc0 | or at least if we do - we do it counciously | 22:29 |
*** jascott1 has quit IRC | 22:31 | |
*** zigo has joined #openstack-kolla | 22:36 | |
*** kristian__ has quit IRC | 22:36 | |
* sdake requests the anestaphine from the medlock | 22:42 | |
sdake | alanmeadows fwiw the makefile approach works, but not keen on that - main reason being we shouldn't have to run make in a pip installed package to get things to work | 22:43 |
sdake | i know your working on a poc so this problem doesn't apply for you | 22:43 |
sdake | hunting down /usr/share/kolla-kubernetes (which is read only) and running make - not ideal :) | 22:44 |
alanmeadows | well the main thing is deciding on whether there needs to be some "helpful" hand in the interim | 22:44 |
alanmeadows | Make is just a means to an end | 22:45 |
alanmeadows | in our case | 22:45 |
sdake | right | 22:45 |
sdake | just sharing information :) | 22:45 |
sdake | as you did | 22:45 |
*** Pavo has quit IRC | 22:46 | |
*** vhosakot_ has joined #openstack-kolla | 22:48 | |
*** vhosakot has quit IRC | 22:50 | |
*** mnasiadka has quit IRC | 22:51 | |
*** jascott1 has joined #openstack-kolla | 22:53 | |
*** v1k0d3n has quit IRC | 22:54 | |
*** v1k0d3n has joined #openstack-kolla | 22:54 | |
*** Pavo has joined #openstack-kolla | 22:55 | |
*** hvlad has quit IRC | 22:55 | |
*** sayantan_ has joined #openstack-kolla | 22:56 | |
*** sayantan_ has quit IRC | 22:56 | |
*** sayantan_ has joined #openstack-kolla | 22:56 | |
*** Pavo has quit IRC | 22:57 | |
sbezverk | alanmeadows: question for you, if helm would have a way to render charts at each level would you use it or still use the workaround way? | 22:58 |
alanmeadows | would definitely prefer an entirely native helm approach | 22:58 |
*** v1k0d3n has quit IRC | 22:59 | |
*** Pavo has joined #openstack-kolla | 22:59 | |
*** TxGirlGeek has joined #openstack-kolla | 23:00 | |
sbezverk | alanmeadows: thank you,in this case, the aproach we choose now should not force us to use it forever and when this feature is available, and I suspect it will be sooner rather than later, it should allow people to use either one depending on their goals/preferences.. | 23:00 |
*** ipsecguy has quit IRC | 23:03 | |
alanmeadows | sbezverk: yup, agreed | 23:03 |
*** sayantan_ has quit IRC | 23:06 | |
*** jascott1 has quit IRC | 23:06 | |
*** saneax-_-|AFK is now known as saneax | 23:09 | |
*** jascott1 has joined #openstack-kolla | 23:10 | |
*** YefimG has quit IRC | 23:10 | |
*** sayantan_ has joined #openstack-kolla | 23:13 | |
kfox1111 | back for about 5 min. | 23:13 |
kfox1111 | sbezverk: like I said, I'm not aposed to using native helm when it has all the needed features. its just not there yet. | 23:13 |
kfox1111 | I'd prefer it actually. | 23:13 |
kfox1111 | I just don't think we should wait for it. | 23:14 |
sbezverk | kfox1111: maybe so, but again current approach breaks any possibility of using them in future! | 23:14 |
kfox1111 | sbezverk: I don't think so. | 23:14 |
sbezverk | since helm has some rules about how things needs to be placed | 23:14 |
kfox1111 | sbezverk: reordering a file system is easy enough. | 23:14 |
kfox1111 | nothing precludes that. | 23:14 |
kfox1111 | git even tracks changes across a rename | 23:15 |
sbezverk | why then use approach which will require in future reordering in stead of designing a solution that does not required it at the first place?? | 23:15 |
kfox1111 | because package api trumps filesystem layout. | 23:15 |
kfox1111 | package api is not easily changable. | 23:16 |
kfox1111 | filesystem layout is. | 23:16 |
kfox1111 | and like I said, I don't really care about file system layout, | 23:16 |
kfox1111 | just that we can template all the thinkgs we need to template. | 23:16 |
kfox1111 | which helm doesn't support at build time yet. | 23:16 |
sdake | i am leary of a huge git mv refactor | 23:17 |
sdake | i think its better to just c&p all the templates around for now | 23:17 |
kfox1111 | sdake: its like 6 months out I think. :/ not sure its worth stressing about. :/ | 23:17 |
*** lamt has quit IRC | 23:18 | |
kfox1111 | it would happen after helm supports build time templating. | 23:18 |
kfox1111 | which isn't on their roadmap currently. | 23:18 |
kfox1111 | but we can work to get it there. | 23:18 |
kfox1111 | 2 min. :/ | 23:18 |
portdirect | once we have a working implementation then we can make it DRY, I'm also wary of code restructuring | 23:20 |
kfox1111 | +1. really we could mirror our current existing structure as is, and restructure not when we go to helm, but when heml supports build templating. then move it only then. | 23:21 |
kfox1111 | might make it a little easier to review too, as you can just compare the two directory structures. | 23:22 |
kfox1111 | diff -ruN services tempates | 23:22 |
kfox1111 | ok. times up. be back later. :/ | 23:23 |
jascott1 | sbezverk wrt to your helm plugin, why cant we just take the globals and subtree we want and pass to child chart? seems like a simple stop gap script until helm plugins are baked. is that what you are thiking? | 23:28 |
jascott1 | thinking even | 23:28 |
sbezverk | jascott1: that is what I use currently | 23:28 |
sdake | portdirect ++ | 23:29 |
sbezverk | there is just one thing missing is to build micro-service with global vaules defined in paert | 23:29 |
sbezverk | oops parent | 23:29 |
sbezverk | jascott1: I was told that this plugin will add this missing piece and then you should be able to build parent/service or micro-service independently but considering values.yaml from higher levels too. | 23:30 |
sdake | sbezverk right - thats why i dont care if values.yaml is copied all over the place as long as each microservice is in a helm structured format | 23:31 |
sdake | if that feature comes, fantastic | 23:31 |
sdake | if ti doesn't, plan B | 23:31 |
sbezverk | sdake: agree as long as template format will be presereved and helm will be able to use them without any modification I am all up for plan B | 23:33 |
sdake | portdirect wfu? | 23:33 |
sdake | we have 150 microservices in the long haul to convert over | 23:33 |
sdake | lets focus on the ones that matter first - and make them helm native | 23:34 |
jascott1 | jeebus! | 23:34 |
sdake | jascott1 had a look at kolla container repo lately? :) | 23:34 |
jascott1 | i havent | 23:35 |
jascott1 | oh | 23:35 |
jascott1 | that huge list | 23:35 |
sdake | STDAKE-M-26CJ:docker sdake$ find . -name \*.j2 -ls | wc -l | 23:35 |
sdake | 180 | 23:35 |
sdake | rather 180 ;) | 23:35 |
portdirect | sdake: wfm | 23:35 |
*** inc0 has quit IRC | 23:35 | |
* jascott1 questions life choices | 23:36 | |
*** JRobinson__ has joined #openstack-kolla | 23:36 | |
jascott1 | starting to think I need k8s networking or complete idiots book | 23:38 |
jascott1 | or/for | 23:38 |
portdirect | jascott1: AMA (there are no stupid questions..) | 23:38 |
*** saneax is now known as saneax-_-|AFK | 23:39 | |
jascott1 | well I was going to try v1k0d3n and crew's work so I nuked my kargo based k8s deployment and tried to use kubadm so I could get k8s 1.5beta1 as they use. got the master and a node but cant even run a busybox image wihtout crash looping | 23:40 |
jascott1 | pretty sure its dns related, i see kube dns pod | 23:40 |
portdirect | ok - what vagrant backend are you using? | 23:41 |
jascott1 | i say its dns related because it was getting an error about not finding node-0 (worker) | 23:41 |
jascott1 | although its in the node list and everything | 23:41 |
portdirect | are you using halycon - or kubeadm on nodes you've set up yourself? | 23:42 |
jascott1 | terraform for node deployment (just vms) and then kubeadm | 23:42 |
sdake | portdirect perhaps you can walk jascott1 thru a kubernetes vagrant deploy | 23:42 |
jascott1 | well I need to use kubeadm with 1.5beta1 | 23:43 |
portdirect | jascott1: is that possible (vagrant)? or I can try and see whats going on with your current setup if you'd prefer | 23:43 |
portdirect | either way you should be able to install whatever version ok k8s you want | 23:44 |
*** sayantan_ has quit IRC | 23:44 | |
sbezverk | jascott1: can you show how you kubectl get pods --namespace=kube-system | 23:44 |
sbezverk | looks like | 23:44 |
jascott1 | sure thanks for the help guys | 23:44 |
jascott1 | oh wait I was re-nuking, maybe someone can help with kubeadm install ? I can paste what I am doing | 23:45 |
sdake | jascott1 why not use vagrant? | 23:45 |
sdake | jascott1 thats the dev env we are staandaridzing on | 23:45 |
sbezverk | jascott1: sure thing I really like kubeadm, it behaves nicely when supplied with right parameters :-) | 23:46 |
jascott1 | i was trying to go more prod-like basically | 23:46 |
sdake | are you dev or qa :) | 23:46 |
portdirect | jascott1: I wouldnt use use kubeadm in prod | 23:46 |
jascott1 | before I did sw, now I just swing a sword at k8s it seems :P | 23:47 |
sbezverk | portdirect: why, you hit any issues? | 23:47 |
jascott1 | it doesnt do some HA some missing logging? | 23:47 |
jascott1 | i read those shortcommings | 23:48 |
portdirect | sbezverk: no HA, setting cluster domain doesnt work and I'd prefer to use a PKI i have control over. | 23:48 |
sbezverk | jascott1: you can add to kubeadm built cluster by labeling additional nodes | 23:48 |
jascott1 | portdirect I thought it would be the new officially recommended way | 23:48 |
sbezverk | portdirect: you can easily add HA after it is installed, dns to work require 1 change | 23:49 |
jascott1 | eventually being good enough for PR | 23:49 |
jascott1 | PRD | 23:49 |
portdirect | jascott1: I think that it will be ready soon, but not yet i dont think | 23:49 |
sdake | ok folks so we have agreement on the fact that we need individual microservices | 23:50 |
sbezverk | portdirect: the only thing I did not try is to use custom PKI | 23:50 |
sdake | now on to the next thing, which is implementing all of those | 23:50 |
portdirect | sbezverk: PKI is the big one for me - but then I do wear a tinfoil hat | 23:51 |
sdake | we can sort out the service level packaging and metapackage stuff next once we have a working compute kit in helm we can manually deploy as kfox1111 intends to do | 23:51 |
sbezverk | portdirect: lol | 23:51 |
sdake | sbezverk can you break out your patch into the microservice model - its closest to hte dir structure i think we desire | 23:52 |
portdirect | sdake: I'm working on ceph right now, and then will hit keystone soon as we have a db | 23:52 |
sdake | so one patch on top of another | 23:52 |
jascott1 | http://paste.openstack.org/show/590729/ | 23:52 |
sdake | portdirect db coming - been busy today - monday funday | 23:52 |
sbezverk | sdake: it is based on microservice model already. All I need is to get rid on common library and then each microservice can be deployed individually | 23:53 |
sdake | cool so do each one as separate patches and remove the common lib | 23:54 |
sdake | common stuff is not essential at this point in time | 23:54 |
sdake | if its common it can be copied around | 23:54 |
sdake | annoying but workable | 23:54 |
sdake | this is how docker repo was run as well :) | 23:54 |
sdake | rather kolla's docker dir | 23:54 |
sdake | we went through about 6 iterations before we had it right ;) | 23:55 |
jascott1 | understandable goes a long way :) | 23:55 |
sdake | we can tckle common on o3 | 23:56 |
sbezverk | sdake: is it really required to do PS per microservice? I mean when common staff is gone then PS will be very small | 23:57 |
sdake | many of those iteratations were git mv | 23:57 |
sdake | yup that will maek it easier to review | 23:57 |
sdake | fill review queue up ;) | 23:57 |
jascott1 | yay! | 23:58 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!