Thursday, 2016-12-15

kfox1111we really need that cache. :/00:00
*** tonanhngo has quit IRC00:01
pronhey friends00:02
pronanyone can comment little bit about kollas netowkr cnfig?00:02
proni am not sure wha functionality lives where =)00:03
pronneutron_external_interface, is where public etoworks live?00:03
openstackgerritsayantani proposed openstack/kolla: Clean up kolla-ansible related files from Kolla  https://review.openstack.org/40642900:04
sayantan_Hi pron00:05
pronhey00:05
*** tonanhngo has joined #openstack-kolla00:06
sayantan_Yes, you can do that. You can assign a public IP to the neutron_external_interface00:06
pronhow its ment to be used?00:06
sayantan_In that way, you can access the services using public URL of the service endpoints00:06
pronif you open globals.conf00:06
pronthere are bunc of interfaces00:06
sbezverkkfox1111: we can disable ubuntu until they catch up00:07
prontunnel_interface is interface where all privat networks live?00:07
SamYaplepron: no, it is where all of the tunneled networks live00:08
SamYaplepron: as in vxlan or gre tunneled networks00:08
sbezverkso far we did not see any differences in behavior of our code on centos and ubuntu00:08
pronsbezverk: okay00:09
sayantan_Sorry, I read it as kolla_external_vip00:09
kfox1111sbezverk: its not voting, so we can just ignore it.00:09
sbezverkpron: sorry, my message was for kfox111100:10
*** tonanhngo has quit IRC00:10
sbezverkkfox1111: can we attach jinja2 teamplating to helm? the way they deal with variables just kills me :-(00:11
pron:]] okay00:11
kfox1111sbezverk: would be nice. they have a template engine flag so in theory it coudl work.00:11
kfox1111but they would have to do soeme hard work to get python working with go.00:12
kfox1111I don't think it will happen any time soon. :/00:12
sayantan_kfox1111 if we create a public network once openstack is deployed using Kolla, won't it be connected to the neutron_external_interface through a bridge?00:12
*** Pavo has quit IRC00:12
sayantan_Oh. That's the external_network_interface00:13
kfox1111sayantan_: kolla-kubernetes or kolla-ansible?00:14
kfox1111I think with kolla-ansible, thats true.00:14
sayantan_Oh, it would be different for kolla-kubernetes?00:14
sayantan_I have very limited knowledge on kolla-kubernetes00:14
*** diogogmt has quit IRC00:15
*** Pavo has joined #openstack-kolla00:17
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046400:18
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046400:22
sayantan_Pron, you can refer to this document for for information00:22
sayantan_http://docs.openstack.org/developer/kolla/production-architecture-guide.html#interface-configuration00:22
pronsayantan_: <3 thx00:22
sayantan_You need a minimum of two interfaces on your host machines to start with. One should be used as the network_interface and the other as neutron_external_interface. You must edit the globals.yml file to configure these two interfaces00:25
SamYaplesayantan_: it can all be done with a single interface00:26
SamYaplehttps://github.com/openstack/kolla-ansible/blob/master/ansible/group_vars/all.yml#L10500:27
sayantan_I agree00:27
sayantan_But in that case wouldn't we need veth etc?00:28
SamYaplenah you wouldn't00:28
SamYaplethe issue is when it adds the interface into openvsiwtch/linuxbridge it drops connections and you have to move the ip up00:28
pronsayantan_: okay i have 2 interfaces ( bridges with lacp ) one for network_interface and other for storage, that was the plan00:29
kfox1111I haven't done it with kolla, but I have a cloud running off of single 40g ports trunked in. so openstack does support it.00:29
SamYapleit actually could be orchastrated, but kolla-ansible "doesnt touch the host"00:29
SamYaplekfox1111: its not an openstack thing, its an orchastration thing.00:29
kfox1111SamYaple: k.00:29
*** yingjun has joined #openstack-kolla00:29
pronsayantan_: and the plan was to put tagged vlans on the  nonstorage one and pyt other stuff there00:29
SamYaplepron: you can't use a bridge as the interface direction, because that interface gets added to a bridge itself for neutron00:30
pronSamYaple: how to solve lacp then?00:30
SamYaplelacp isnt bridging00:30
SamYaplelscp is bonding00:30
SamYaplelacp*00:31
pronah well00:31
pronyes00:31
pronso00:31
proni am fine then00:31
SamYaplebridging is a different thing. are you saying you have two bonds? one for storage and one for everything else?00:31
pronyes i do have binds00:31
pronbonds*00:31
pronmy bad00:31
SamYapleok. thats doable, but its a bit tricky00:31
SamYaplei would recommend setting up a vlan on that bond, for example bond0.10 for vlan 1000:32
SamYapleand using that for "network_interface"00:32
prondo i need that neutron interface if i dont plan to use vlans for my private netowrks00:32
pron?00:32
SamYaplewell you need vlan or flat network for external network pron00:33
SamYapleif you dont have that you can't get to the internet from you instances00:33
sayantan_SamYaple, are you saying that we can use the same physical interface for both network_interface and neutron_external_interface?00:33
SamYaplesayantan_: yea00:33
sayantan_oh, got it00:33
SamYaplesayantan_: _really_ easy when you use vlans00:33
sayantan_I agree00:34
SamYaplesayantan_: 'network_interface: bond0.10' 'neutron_external_inteface: bond0'00:34
pronSamYaple: amm i can make a vlan for that and put it as interface for neutron interface?00:34
SamYaplewithout vlans its trickier, there is a chicken-and-egg problem00:34
SamYaplepron: you can. but you can only use that as a "flat" interface in neutron then00:34
*** ipsecguy has quit IRC00:35
prondo i have to speify it somehwere?00:35
*** lamt has quit IRC00:35
pronsomewhere else i mean00:35
*** ipsecguy has joined #openstack-kolla00:36
SamYaplepron: what are your interface names, and what vlans would you like to do what? i can give you a sample config00:36
pronno all of them are there00:36
sayantan_SamYaple I think we should document this part00:37
SamYaplesayantan_: should all be documented00:37
*** hawi has joined #openstack-kolla00:38
SamYaplepron: http://paste.openstack.org/show/592407/00:38
SamYapleif you want vlans for neutron, leave the neutron interface bare (just "bond0")00:38
pronSamYaple: http://pastebin.com/7XXCNRVK00:38
pronSamYaple: its goin this way00:39
pronso what happens when i need ot add one more external network?00:39
*** tonanhngo has joined #openstack-kolla00:39
SamYaplepron: with flat networking, its not really setup to do that00:39
SamYapleyoud have to do it with external commands, and thats not documented00:39
SamYaplethough it is safe00:40
SamYaplewith vlan networks, its really easy00:40
pronbut then i need dedicated boundx for that?00:40
pronand that starts ti be abit tricky00:41
pronespecialy if one wants lacp on double switches00:41
SamYaplewhat?00:41
pronwell00:41
pronif you want 2 switches for storage, you need 2 interfaces right?00:42
pronad so on00:43
SamYapleno?00:43
SamYaplethats not how networking works, no00:43
SamYapleif you are talking about lacp bonding, you have multiple interfaces in the bond, but only one interface presented to you ("bond0")00:44
pronyes00:44
SamYapleso for configuration you would only be refering to bond000:44
SamYaplewhat goes on behind the bond is a different story00:44
pronyes but that means i need 3 bond interfaces00:45
SamYapleyou cant use two different bonds for storage if thats what you are asking00:46
pronunless i can have same interfaces in multiple bonds00:46
SamYaplethats not how networking works htough00:47
SamYapleim not sure what you are trying to do00:47
pronno that is not what i am asking :P00:47
proni am saying that if i need to have dedicted interface ( bond in my case ) for neutron_netwrk, that meeans i need aditional 2 nics for that00:48
SamYaplein kolla, there are 5 types of traffic. you can send them over whatever interface you would like. neutron traffic (flat/vlan), neutron traffic (tunnel), storage, api, external (like public ip for endpoints)00:48
pronunless same interfaces can be in the sme bond ( i dint think it works tha way )00:48
SamYapleyea, all of these interfaces can use the same bond00:49
SamYaplekolla _can_ run on a single interface00:49
SamYaplethough that can be tricky to configure00:49
pronso00:49
pronthere is smething i am missing =000:50
pronso kolla can handle multple flat public netoworks?00:51
proni think thats what i want to ask00:51
SamYapleyou can configure that, but you have to configure it by hand. kolla does not have any support for setting up the proper openvswitch bonds for _multiple_ flat interfaces00:52
SamYaplehowever, it sounds like you are going to be using vlans, so im confused as to why you want to do flat networking00:52
pronokay00:52
pronlets forget abound bonds00:53
pronhow do i achive thos with 2 interfaces00:53
pronif one of them is dedicated to storage00:53
SamYaplewith no vlans, you cannot do this with 2 interfaces if one of them is storage00:53
*** duonghq has joined #openstack-kolla00:53
SamYapleflat networking requires the whole interface00:54
duonghqmorning guys00:54
pronwe are circledancing ;(00:54
SamYapleduonghq: morning. updated your zero downtime patch with some comments00:54
pronSamYaple: i can configure vlans, i want to use kolla, and wwant to have  more then one public network00:55
duonghqSamYaple, I just read your comment, tyvm00:55
pronSamYaple: how to get this done00:55
pron:P00:55
SamYapleduonghq: sorry for confusion about neutron upgrade. i was mistake :)00:55
*** fragatina has joined #openstack-kolla00:55
SamYaplepron: does the external network ("public network") need to be a flat network?00:55
duonghqSamYaple, np, you comment is invaluable,00:56
proni start to think i am not sure what the term "flat netowk" means00:56
duonghqSamYaple, I thought about your approach once before but don't pay much attention to it, until you bring it to your comment00:57
*** JRobinson__ has quit IRC00:57
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046400:57
SamYaplepron: "flat network" is a neutron network that goes over the raw/bare interface. vlan network is a network that neutron encpsulates in a vlan00:57
SamYaplepron: i believe you want vlan networks for what its worth. thats teh common setup00:57
pronyes00:57
pronso00:58
SamYapleif you want vlan networks, this is what your config should look like based on your other info http://paste.openstack.org/show/592408/00:59
*** Marcellin__ has quit IRC00:59
pronSamYaple: this looks weird for me01:00
proncause bond0 is also used for provisioning01:01
Pavoflat networks are networks that are eternal and do not need a VLAN ID01:01
Pavoexternal*01:01
Pavobasically like pluggin into a access port01:02
pronor as everyone else calls it, untagged?01:02
Pavoyeap01:03
pron~.~01:03
Pavountagged=access tagged=trunked01:03
pronuntagged=access=flat!!!!!01:03
pron:P01:03
Pavoroger01:04
pronat least we fogured that out01:04
* pron hugs Pavo01:04
*** JRobinson__ has joined #openstack-kolla01:07
*** JRobinson__ has quit IRC01:13
*** diogogmt has joined #openstack-kolla01:13
*** JRobinson__ has joined #openstack-kolla01:13
SamYaplepron: bond0 in this case would be an interface that was used by neutron to send tagged vlan traffic only. if you used it as a "flat" network it would send traffic out bond0 untagged01:17
SamYapleusing it as a flat network is not common01:17
*** zhubingbing_ has joined #openstack-kolla01:19
kfox1111hmm...01:20
kfox1111did job output fetching change?01:20
kfox1111in 1.5?01:20
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046401:22
pronSamYaple: the flat ( untagged ) netowrk will be used on bond0 for provisioning01:22
pronmaas in our case01:22
pronanyways 3:30 am here gn fols and thx for your time01:29
*** jrich523 has quit IRC01:29
*** dupengfei has joined #openstack-kolla01:35
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046401:45
kfox1111they seem to have changed the behavior of pod listing slightly via the cli. :/01:45
*** huzhengchuan has joined #openstack-kolla01:46
*** HyperJohnGraham has joined #openstack-kolla01:47
*** srwilkers has joined #openstack-kolla01:53
srwilkersevening o/01:54
*** adrian_otto has quit IRC01:54
*** elynn has joined #openstack-kolla01:56
*** huzhengchuan has quit IRC01:58
kfox1111thats alittle better...01:59
kfox1111srwilkers: hi.01:59
kfox1111o/01:59
*** elynn_ has joined #openstack-kolla02:00
*** elynn has quit IRC02:01
*** goldyfruit has joined #openstack-kolla02:02
*** goldyfruit has quit IRC02:05
*** elynn__ has joined #openstack-kolla02:06
kfox1111hmm... the renaming the node after the ip trick fails now...02:08
kfox1111fun.02:08
*** why_dejavu has joined #openstack-kolla02:08
*** elynn_ has quit IRC02:08
why_dejavuhello02:08
*** why_dejavu has left #openstack-kolla02:09
*** elynn__ has quit IRC02:09
*** huzhengchuan has joined #openstack-kolla02:10
*** sdake has joined #openstack-kolla02:11
*** Pavo has quit IRC02:12
srwilkershey kfox1111 o/02:14
srwilkershey sdake02:14
*** sdake_ has quit IRC02:14
kfox1111getting closer...02:17
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046402:17
*** Pavo has joined #openstack-kolla02:17
*** why_dejavu has joined #openstack-kolla02:21
openstackgerritzhangshuai proposed openstack/kolla-ansible: Add karbor ansible role  https://review.openstack.org/40222902:23
openstackgerritqiankun.zhang proposed openstack/kolla: Install tacker-horizon into horizon image  https://review.openstack.org/40781002:33
*** eaguilar has quit IRC02:36
*** zhubingbing_ has quit IRC02:39
*** unicell has quit IRC02:41
duonghqsup kfox111102:41
kfox1111duonghq: hi02:45
kfox1111its running a long time now. should be close.02:45
*** zhubingbing_ has joined #openstack-kolla02:45
duonghqkfox1111, have we had something about kolla-k8s use case?02:48
duonghqlast night I sleep quite early02:48
duonghqWe should use spec or...?02:48
duonghqetherpad?02:48
kfox1111not yet.02:50
duonghqshould we use etherpad for jot down some use case? like helm install ..... w/ some configuration? by example?02:51
sdakekfox1111 need to hit the rack - your patch needs the blueprint attached to it02:52
kfox1111couldn't hurt. though I guess it depends on how contentious it will be.02:52
sdakenight all :)02:52
duonghqsdake, night02:52
kfox1111sdake: good night.02:52
kfox1111sdake: yeah. just tring to get somethign working. its close. :/02:52
*** sdake has quit IRC02:52
kfox1111etherpad's good for jotting stuff down easily. but it doesn't track changes so hard to ensure stuff isn't changed/removed/dropped.02:53
duonghqkfox1111, just for initial use case02:54
*** dave-mccowan has joined #openstack-kolla02:54
*** tyrola has quit IRC02:54
kfox1111theres a tun of use cases I think, and I'm sure some will be contentious. :/02:54
kfox1111but you can start one if you want. I'll add to it.02:54
*** tyrola has joined #openstack-kolla02:55
kfox1111what I'm a bit afraid of, is kind of what was happening. some people give out use cases, and others just shoot it down as not a valid use case, as their favorite tool doesnt' support that easily.02:56
kfox1111but we should stick to pure use cases, not what tools best for the job.02:56
duonghqkfox1111, can you give me some example?02:56
*** qiliang27 has joined #openstack-kolla02:57
duonghqI think we should done this quickly then we can put something on service layer for O02:57
kfox1111the whole microservcie thing's a big contentious thing there where is a use case for me and others, and its been continuiously questioned as helms not noramlly used that way.02:57
duonghqkfox1111, agree w/ you on pure user cases02:57
kfox1111the tool should not be driving use cases, but the use cases driving tools.02:58
duonghqnot just helm, I mean kolla-k8s in general02:58
kfox1111+102:58
duonghqand then we can break down it02:58
kfox1111sounds good to me. :)02:58
jascott1duonghq i want to do similar for upgrade workflows was that part included in your idea?02:59
duonghqkfox1111, for example: we have 5 top-levels use case, for use case 1, we decides how depth we want user can interact with Kolla and then put some use case for these.03:00
duonghqjascott1, sure03:00
duonghqtop-level use cases will like: install openstack, install compute-kit, upgrade cluster,....? (just for example)03:01
duonghqlevel 2 is: install openstack --options.....03:01
duonghq and then we can try match these use cases down to layer in Ryan's spec03:01
*** harlowja has quit IRC03:03
*** srwilkers has quit IRC03:04
jascott1duonghq sounds great to me03:05
kfox1111duonghq: I've been working on something kind of a kin to a design phylosophy.03:06
kfox1111kind of writing down how kolla's been operating and kolla-kubernetes has been operating.03:06
kfox1111http://paste.openstack.org/show/1mxHBqkCF7P3Gw95QiHh/03:06
kfox1111thoughts on it?03:07
kfox1111jascott1: you too?03:07
kfox1111pastebin didn't wrap that well. :/03:08
portdirecto/03:08
jascott1portdirect o/03:08
kfox1111portdirect: hi. :) you too if you don't mind? :)03:08
kfox1111and anyone else who wants. :)03:08
* kfox1111 covers all bases03:08
duonghqkfox1111, nice03:08
* portdirect rebooting brain03:09
jascott1I think #4 will be *the* selling point eventually03:09
jascott1and 303:09
kfox1111jascott1: yeah.03:10
duonghqkfox1111, so I'll drop a use case on doc/ in kolla-k8s? just for change tracking, (do not merge?) but it'll consume some gerrit resource due to we have not had good tox config03:10
duonghqit's ok? kfox1111 jascott103:10
jascott1i agree03:10
duonghquse_case.rst for ex03:10
kfox1111duonghq: works for me.03:10
portdirectduonghq: im was going to get a thing on the mailing list but toally passed out after the meeting :/03:11
kfox1111darn... well, its continuing on, as its stuck now. :/03:11
kfox1111and its all ipv6 backed so I cna't see where its stuck. hate when that happens. :/03:11
kfox1111its got only maybe 10ish mroe min though.03:11
kfox1111hard slimit.03:11
jascott1duonghq mentioned in meeting this https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-deployment-upgrade , thinking these workflows would be separate03:13
duonghqjascott1, I'm reading your bp, moment, network at my place is starting slow down03:15
duonghqjascott1, you mean workflow from technical PoV?03:15
jascott1not much there but wanted to start something to start so we could gather these upgrade cases down03:15
jascott1oh is that overloaded03:16
kfox1111jascott1: bp looks good.03:16
jascott1?03:16
duonghqjascott1, just good03:16
jascott1cool thx03:16
jascott1i wouldnt say it im nervous but wont feel relaxed until weve shown how the whole thing will work ;)03:17
kfox1111+1.03:18
kfox1111I'm  abit afraid by design by committee too much on this one.03:18
jascott1isnt that OSS life?03:18
jascott1:D03:18
kfox1111have you guys read the mythical man month?03:18
kfox1111jascott1: in some orgs.03:19
jascott1i have not03:19
jascott1nor rework. man i need to read more03:19
kfox1111very good book. I recommend it.03:19
kfox1111if nothing else, so you chan help your managers understand some of the mistakes that plague sofware development.03:19
openstackgerritjimmygc proposed openstack/kolla: Add murano dashboard into horizon source image  https://review.openstack.org/41066903:20
jascott1might check it out over the holiday03:20
jascott1plan to do nothing but read non sw related things as much as possible but wont count that one03:20
kfox1111they talk about something they call the surgeon model.03:21
openstackgerritDuong Ha-Quang proposed openstack/kolla-kubernetes: Use case for kolla-kubernetes  https://review.openstack.org/41104303:22
kfox1111basically, the idea there is in surgery, they nominate one lead cutter. that person keeps track of the others so that the patient doesn't bleed out.03:22
kfox1111kind of the too many cooks thing.03:23
kfox1111in opensource, lots of contirbutors is a good thing most of the time.03:23
kfox1111when bootstrapping a project though, it can sometimes prevent the sofware from being bootstrapepd if there are too many conflicting intrests and lack of communication and not well defined goals, etc.03:24
kfox1111the various surgeon's just keep cutting on their part and all it ends up with is a bloody mess. :/03:24
portdirectkfox1111: i hear what you are sayingbut rememeber over 50% of the cruurent codebase has been written by you i think?03:25
kfox1111I don't think its that much.03:25
openstackgerritDuong Ha-Quang proposed openstack/kolla-kubernetes: [DO NOT MERGE] Use case for kolla-kubernetes  https://review.openstack.org/41104303:25
kfox1111I've probably touched that much of it. but didn't write that much I think.03:25
duonghqkfox1111, jascott1 should I send out a email for notice about this ps? https://review.openstack.org/#/c/411043/03:25
portdirectkfox1111: http://stackalytics.com/?module=kolla-kubernetes&metric=loc03:26
kfox1111portdirect: http://stackalytics.com/?module=kolla-kubernetes&metric=loc&release=all03:26
portdirectanyway i wasnt trying to attack you with that statment, just recognising how much yu have contributed to getting the probject up and running03:27
kfox1111and a fair amount of what I've done is combining things, generalizing things, etc. so others code repackages. which I think counts me up further then due.03:28
kfox1111portdirect: yeah. no attack percieved. just wanting to give credit where its due. :)03:28
kfox1111duonghq: sure03:29
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: [DO NOT MERGE] Use case for kolla-kubernetes  https://review.openstack.org/41104303:31
kfox1111interesting. I'v enever tried using gerrit this weay. but works pretty good. :)03:31
*** goldyfruit has joined #openstack-kolla03:32
kfox1111gate finally failed...03:32
kfox1111k. got pretty far really.03:33
kfox1111looks like glance isn't running though.03:33
v1k0d3nhey portdirect03:34
*** dave-mccowan has quit IRC03:34
v1k0d3nyou mentioned that there could be an interesting way to spin up docker builds inside of a docker container?03:34
v1k0d3nmind sharing your thoughts?03:34
* portdirect talks a good game03:34
v1k0d3nlol dude...you have game. :)03:34
v1k0d3nyou're like lebron james man03:34
portdirectright - so you wanna go full dind?03:35
portdirectso the main issue with the dind stuff that you are using (affaik) is that it is using vfs at the storage driver03:37
openstackgerritzhubingbing proposed openstack/kolla-ansible: Integrate ceph-rgw with keystone  https://review.openstack.org/40697103:37
v1k0d3ni'm in all the way. bought into kube based docker builds.03:37
portdirectit does this as its the saftest thing for it to do03:37
v1k0d3nfinishing up this container. working pretty well, but as always could be faster.03:37
portdirectbut if you can move to overlay2 you will get much better performance03:37
portdirectthe other thisn is in your ci/cd system you may be able to sidestep koll build for the building whihch may help you03:38
portdirecthave ajob that reneder out the dockerfile templates and then load the output into a get repo03:38
portdirectGit03:38
portdirectthen use your build jobs to build direct from those prerendered dockerfiles03:39
portdirectand run mutiple jobs sysmutaniously to distribute the workload03:39
*** huzhengchuan has quit IRC03:40
v1k0d3nah, yeah.03:41
v1k0d3nso for poc we're using the container; again as i stated for "impact". opens the door for namespaces and basic claim concepts for future architect. then for 1-2Q we're definitely going with something more robust.03:42
v1k0d3nwe have a few groups that are just crazy good at CI03:42
v1k0d3ndigital entertainment is amazing (DirecTV folks in el segundo)03:43
*** gomarivera has joined #openstack-kolla03:45
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046403:45
duonghqportdirect, are you working on ceph-osd microservice? or I'll take care that03:47
portdirectyours if you want it!03:47
kfox1111duonghq: start with the ps in review right now. has a few fixes.03:47
kfox1111unfortunately, some of the existing ps's will need a bit of reworkign there too.03:48
kfox1111would have bee nreally nice if 1.5 hit one week later. :/03:48
kfox1111oh well.03:48
duonghqkfox1111, thank you03:48
kfox1111np.03:48
*** gomarivera has quit IRC03:49
portdirectyeah - I've got the upstream working really well here and am about to put some pull requests in over there, but not sure if its reall sutable for what we have?03:51
*** goldyfruit has quit IRC03:52
*** huzhengchuan has joined #openstack-kolla03:54
Pavoin /usr/share/kolla/ansible/roles/baremetal/templates/docker_systemd_service.j2 why is there 2 ExecStart=?03:56
duonghqPavo, it's for append 2nd line to current ExecStart setting03:57
duonghqor it'll override03:57
Pavooh ok what about  -H fd:// in the same file03:57
Pavobecause if I delete that line and the first ExecStart= empty line I can use docker-engine 1.12.003:58
kfox1111portdirect: sure. :)03:58
portdirectkfox1111: dont follow?03:59
portdirectgot right notes here if yo want to check em out?03:59
sbezverkkfox1111: how is 1.5? running?03:59
portdirectat home and ccant ssh back into work :/03:59
kfox1111sbezverk: very close now I think.04:00
portdirect*right - rough04:00
kfox1111sbezverk: https://review.openstack.org/#/c/410464/04:00
*** mdnadeem has joined #openstack-kolla04:00
kfox1111last round identified a bunch of init containers not having the pull yet. but most of the services started.04:00
kfox1111I fixed all the ones it identified. so maybe one or two more rounds I thinik should do it.04:01
*** adrian_otto has joined #openstack-kolla04:01
*** hfu has joined #openstack-kolla04:02
Pavolike this duonghq04:02
Pavohttp://paste.openstack.org/show/592414/04:02
kfox1111I think I fixed the issue with multinode too.04:02
duonghqPavo, strange04:03
sbezverkkfox1111: ps getting bigger and bigger ;-)04:03
*** gomarivera has joined #openstack-kolla04:03
duonghqPavo,  seems that 2nd line mess up with default setting or other setting04:03
openstackgerritMerged openstack/kolla-ansible: Allow neutron-fwaas to be enabled in Neutron  https://review.openstack.org/39833604:03
kfox1111sbezverk: yeah. :/04:03
Pavoyeah I did a yum update which updated docker-engine on the target nodes and it would not start the docker daemon04:04
kfox1111I'm realy disapointed in k8s over a few things they did that broke things.04:04
PavoI removed those lines and now I am using docker-engine 1.12.0 and works fine now04:04
kfox1111we should show k8s the completed patch when done.04:04
Pavoso... duonghq think I am gonna change the docker-engine version in the defaults/main.yml file to 1.12.* to allow supporting newest docker engine04:06
kfox1111is docker 1.12+ supporting that use case officially?04:07
duonghqPavo, which repo do you get the docker from?04:07
Pavodocker engine?04:07
duonghqyup04:07
Pavopublic mirror that is chosen by which one is closest to me04:08
duonghqI mean from distro's repo or Docker'srepo\04:09
openstackgerritMerged openstack/kolla: Add monasca images  https://review.openstack.org/40642204:09
kfox1111so close now...04:10
kfox1111http://logs.openstack.org/64/410464/17/check/gate-kolla-kubernetes-deploy-centos-binary-external-ovs-nv/d5afe51/console.html04:11
kfox1111vms launched. cinder working. glance working.04:11
kfox1111looks like maybe just a little more neutron....04:11
Pavoduonghq I did a normal yum update which is from CentOS 7 distro repo04:11
duonghqPavo,  okay04:11
*** Pavo has quit IRC04:12
*** Pavo has joined #openstack-kolla04:13
*** adrian_otto has quit IRC04:13
Pavoduonghq when I deployed kolla installs docker-engine 1.11.* and if you do a yum update it will update the docker-engine to 1.12.0 and since those settings are already in the systemd file after updating the docker daemon will not start because of those lines being in the systemd file, removing those lines will allow the docker daemon to start and allow the docker containers to use the newest docker-engine04:14
sbezverkkfox1111: Unless I am missing it, but I do not see openvswitch running in the log you pasted04:15
kfox1111yeah. thats the external ovs job.04:15
*** l4yerffeJ__ has joined #openstack-kolla04:19
duonghqPavo, these lines override default docker settings, I didn't use it recently, soryr04:21
kfox1111The DaemonSet "neutron-dhcp-agent" is invalid: spec.template.spec.initContainers[1].imagePullPolicy: Required value here we go...04:21
*** l4yerffeJ_ has quit IRC04:21
kfox1111oh. it was a second init container...04:22
Pavoduonghq yeah but those settings changed with docker-engine 1.12.0 and since thats the latest version of the docker-engine, I would assume we would want people to use the latest docker-engine since it provides newer features, security patches and so on04:24
Pavocorrect?04:24
sbezverkkfox1111: I am off now, talk yo you tomorrow04:24
duonghqPavo, sure04:24
duonghqIf it can run all container04:24
Pavoduonghq you would mind teaching me how push this up as a proposal to a code change?04:24
PavoI haven't done that yet and not sure where to start04:25
kfox1111sbezverk: k.04:25
kfox1111please check the review int he morning. should be ready.04:25
kfox1111good night.04:25
duonghqnight kfox111104:27
kfox1111duonghq: I'll be around for a bit longer.04:28
duonghqkfox1111, which is your tz?04:29
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046404:29
kfox1111duonghq: pst04:29
duonghqk04:29
duonghqmany guys in PST04:29
kfox1111yeah.04:30
PavoEST here04:31
duonghqWhy PST but not WST...04:32
*** JRobinson__ is now known as JRobinson__afk04:32
*** yingjun has quit IRC04:36
*** l4yerffeJ__ has quit IRC04:40
*** l4yerffeJ__ has joined #openstack-kolla04:41
*** saneax-_-|AFK is now known as saneax04:46
kfox1111there we go. first success.04:51
*** tonanhngo has quit IRC04:56
*** adrian_otto has joined #openstack-kolla04:56
portdirectwhoop!04:57
portdirectany idea what might have cause the mariadb crash? - though awesome work kfox1111, thanks man04:59
*** unicell has joined #openstack-kolla05:01
*** unicell has quit IRC05:05
*** unicell1 has joined #openstack-kolla05:05
*** why_dejavu has left #openstack-kolla05:06
*** JRobinson__afk is now known as JRobinson__05:10
*** zhangqiankun has joined #openstack-kolla05:10
kfox1111not sure yet...05:12
*** saneax is now known as saneax-_-|AFK05:12
*** britthouser3 has joined #openstack-kolla05:14
*** britthouser has quit IRC05:14
*** hfu has quit IRC05:14
kfox1111it kind of looks like a crash too... it seems to start.05:16
*** saneax-_-|AFK is now known as saneax05:17
kfox1111nothing obvious. it just dies.....05:21
kfox1111Dec 15 04:47:09 localhost kubelet: E1215 04:47:09.747271   22965 runtime.go:64] Observed a panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)05:29
kfox1111strange.05:29
kfox1111gota head out. l8r.05:33
jascott1woah nil pointer deref wtf05:34
*** sayanta__ has joined #openstack-kolla05:34
jascott1kfox1111 before your well deserved rest, do you have stacktrace?05:34
kfox1111unfortunately not.05:36
*** yingjun has joined #openstack-kolla05:36
kfox1111we may need to crank up debugging and or inject a gdb.05:36
kfox1111or it may be a kube 1.5 bug.05:37
kfox1111since it has been so stable, it may be the latter.05:37
*** sayantan_ has quit IRC05:37
*** zhangshuai has quit IRC05:37
kfox1111or, it could be a bad vm it landed on.05:38
*** tonanhngo has joined #openstack-kolla05:38
*** zhangshuai has joined #openstack-kolla05:38
jascott1what log file is that error in?05:48
jascott1portdirect did you see this? https://github.com/asobti/kube-monkey05:49
*** Jeffrey4l has joined #openstack-kolla05:50
portdirectahhh! why does everyone send me that?!! I'm perfectly capable of distroying things myself!05:53
jascott1lol05:54
zhangqiankunLOL05:54
portdirectyeah, v1k0d3n  hit me up with that a few days ago, cant wait untill we are at the stage where we can use it, it would be one of the best ways we could validate our work i think05:54
jascott1i know!05:54
v1k0d3n:)05:54
v1k0d3nyeah, cool stuff.05:55
*** fragatina has quit IRC05:55
v1k0d3nmust be making it's twitter rounds.05:55
jascott1it was on HN a couple days ago methinks05:55
portdirectthat would exaplain it05:55
portdirectat the incubator im in (which has foos, and table tennis!) everyones been overely exiticed about it over the last few days :)05:56
jascott1my intelcubator has foos and tt!05:57
v1k0d3nit's so funny, i'm a huge HN fan...but a lot of stories get circulated between that and twitter these days.05:57
v1k0d3nboth are great tools for knowing what's out there!05:57
jascott1i just dont have anyone to foos with atm, will have to draft inc0 when he gets settled05:57
jascott1ya reddit is still got some good stuff despite the bad05:58
portdirectyeah - i had to leave reddit recently, just too depressing05:58
jascott1golang flipped their 5h17 the other day cause of what reddit CEO did, dont know you guys are familar?05:58
portdirectno?05:59
portdirectwhats a 5h17? (think is a visa?)05:59
jascott1r/golang luminaries were talking about shutting down the whole subredit as reaction to reddit CEO editing peoples comments05:59
jascott15h17/sh17/shi7/shit06:00
portdirectoh just worked out your l33t06:00
portdirectha!06:00
jascott1but people rebelled, its not official channel for go anyway06:00
jascott1well not anymore at least06:00
jascott1but some "big go ppl" were moderators06:01
v1k0d3nman, what a mess that whole situation has become.06:01
portdirectyeah, i think thats the point at whihc you need to call it a day :/06:02
v1k0d3nkinda hard though. reddit does provide some pretty awesome value.06:02
v1k0d3njust need to get back into a good place.06:02
jascott1i had lunch with those guys about 6 years ago, they had corner office in Wired (Conde Nast) and my good friends was friendly with them. They took us to lunch and even told us where a cool park was nearby to chill. nice guys06:04
jascott1those guys = reddit devs06:04
jascott1the older I get the more i hate that I cannot remember anyones name06:05
v1k0d3nlol06:05
v1k0d3nhappens06:05
portdirectv1k0d3n: exactly, my comments about leaving it, were more a relection of the political climate here in the uk at the moment (let just not go there), as its such a good forum for people to express their opionion.06:05
jascott1my buddy knows all that, RTS, idk he gets around with his shoulder rubbin06:05
v1k0d3nmy teammate and i split knowing various people. it's kind of funny06:05
jascott1not going there with them crazy lawz06:06
v1k0d3noh gosh...yeah politics have become a hot mess. both over by you, and over here in the states.06:06
jascott1we have our own crazy lawz to worry about here :(06:06
openstackgerritJeffrey Zhang proposed openstack/kolla: DO_NOT_MERGE: TEST NEWTON BRANCH  https://review.openstack.org/38698106:06
v1k0d3njascott1: you're states?06:07
openstackgerritqiankun.zhang proposed openstack/kolla: Install tacker-horizon into horizon image  https://review.openstack.org/40781006:07
jascott1Portland06:07
jascott1OR06:07
jascott1acutally Hillsboro06:07
v1k0d3noh that's right...you're working with inc0 now, right?06:07
v1k0d3nintel foks06:07
jascott1yup!06:07
v1k0d3nvery cool!06:07
v1k0d3nportland is a good place. used to do a few jobs out that way when i worked at red hat.06:08
jascott1except me and Qin and Sayantan are working, inc0 is off traversing the lands w his wife!06:08
jascott1love it here. even got snow outside right now06:08
v1k0d3nyeah, lucky him. he deserves it though.06:08
v1k0d3nyou say that as if it's a good thing :)06:08
jascott1v1k0d3n are you in desert lands?06:08
jascott1a little snow is nice06:09
v1k0d3ni'm in charlotte we shut down with just a dash of snow06:09
jascott1like being a little snowed in when I am prepared as I currently am06:09
*** gomarivera has quit IRC06:09
jascott1oh i used to live in NC06:09
v1k0d3nin fact...the mere thought of snow...no schools06:09
jascott1Asheville and Boone06:09
v1k0d3nRTP?06:09
v1k0d3nah!06:09
v1k0d3nlove it there.06:09
jascott1gems06:09
v1k0d3ni would like to move out that way honestly. mountain people are my kind of folks.06:10
jascott1West NC is awesome06:10
jascott1not a lot of tech tho06:10
v1k0d3nplus i like to ride motorcycles...so mountains are my jam06:10
v1k0d3nnot at all. plenty of beer though :)06:10
jascott1i msure more than when I was there in 96-2002ish06:10
portdirectpushbikes ftw06:10
*** coolsvap has joined #openstack-kolla06:11
v1k0d3npush or peddle?06:11
jascott1those places all want to be Eugene OR imo06:11
v1k0d3nreally? is that similar to what eugene is like06:11
v1k0d3n?06:11
jascott1pushbike?06:11
portdirectpeddles :) (what motocrossers call mountainbikers in the uk)06:12
jascott1to me Eugene is the hippiest place ever and Asheville and Boone trying to be something similiar06:12
jascott1college towns06:12
v1k0d3ntbh i'm a huge mtnbike fan too :)06:12
jascott1love it, seen some great shows in all them places06:12
*** Pavo has quit IRC06:12
v1k0d3noh yeah, they are definitely hippie out there06:12
jascott1ha played some shows in boone and asheville06:13
v1k0d3nyup i've gone to some good shows in asheville. at the orange peel06:13
v1k0d3nnice! what instrument?06:13
jascott1at the time bass in a 3 piece prog rock band06:14
jascott1prog rock but with silliness and humor06:14
jascott1like zappa without all the talent06:14
jascott1there is a bar in Blowing Rock that we house band'd at for several months. crazy fun times06:14
jascott1do you guys play?06:15
jascott1kolla band!06:15
v1k0d3nportdirect: so totally different approach than your container.06:15
v1k0d3nhttps://github.com/att-comdev/dockerfiles/tree/master/kolla-builder06:15
portdirectnot real insuments :/ used to do a lot of VJ work for Drum&Bass and HipHop stuff here in the uk06:15
v1k0d3n(btw...like yours...just had a certain thought/goal with this)06:16
portdirectdid some creazy geeky things - uses to run midi over openvswitch...06:16
jascott1lol06:16
jascott1you win06:16
jascott1idk what the contest was but you won06:16
v1k0d3nhaha!06:16
v1k0d3nthat's awesome portdirect! seriously?06:16
portdirectdude you acutally played stuff - i just pushed buttons, we both win!06:16
v1k0d3ni like like sounds.06:17
v1k0d3n:)06:17
v1k0d3ni have a few synths, try to play the banjo and guitar.06:17
*** Pavo has joined #openstack-kolla06:17
jascott1cool!06:17
v1k0d3ni have a juper 80, access virus, fantom, FA06, Gaia, few others.06:17
portdirectv1k0d3n: that readme's full of winning :)06:17
jascott1portdirect as long as music is being made its all good w me06:18
v1k0d3ni try...but i really just love synthesis truth be told.06:18
*** huzhengchuan has quit IRC06:18
*** unicell1 has quit IRC06:18
v1k0d3nportdirect not really06:18
jascott1my brother that lives here (also a transplant) plays keys06:18
v1k0d3njust that we get asked all the time...what can you do with a container. i hate that question. so...06:18
jascott1we play downtown hillsboro and just play whatever we want. its great06:19
v1k0d3njascott1: where are you orig from?06:19
portdirectyeah dude - i hear ya06:19
v1k0d3nthis way?06:19
jascott1(for us)06:19
jascott1AL,FL and MS06:19
v1k0d3nportdirect: i just like having a franken-tainer hack06:19
jascott1i come from south east, grew up on allman brothers and the dead, the band, yes, rush and my fav phish06:19
v1k0d3nthat's really all.06:19
v1k0d3nall great bands06:20
v1k0d3nrush is one of my favs06:20
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Optimized reconfigure action for glance  https://review.openstack.org/40697806:20
jascott1pink floyd of course, zep, jimi etc06:20
v1k0d3nled zep too06:20
v1k0d3npink floyd definitely that one06:20
v1k0d3njimi all those.06:20
portdirect+1 to that, and jimi nothing beats that06:20
v1k0d3nagreed06:20
v1k0d3ntaken too young06:21
v1k0d3nimagine if some of those lived longer06:21
v1k0d3nwow06:21
jascott1took wife to see Gillian Welch and Dave Rawlings in Eugene and John Paul Jones from Led Zep was on mandolin and *killing it*06:21
* portdirect plays voodo chile on youtube06:21
*** unicell has joined #openstack-kolla06:21
jascott1jimi's blues album omg06:21
jascott1not big on classic blues but love the jimi and allman kinda take06:22
jascott1alright cool we got strings and synth and beat06:22
v1k0d3ni like all music06:22
v1k0d3nanything from beach boys to grunch of the 90s06:23
jascott1i try kinda but am a little snooty about pop06:23
jascott1little/lot06:23
v1k0d3nthat's why i stopped where i did06:23
*** unicell has quit IRC06:23
portdirectjascott1: its all good, apart from the stuff that's not.06:23
*** unicell has joined #openstack-kolla06:23
jascott1but yeah I admit its all relative.. try to find something good in there. even if its crap if its popular there was probably hell production values, mixing etc06:23
jascott1portdirect exactly :)06:24
portdirectyeah the crazy thing is how much of the crap is produced by amazing people06:24
jascott1att got a music room06:24
jascott1?06:24
portdirectbut you gotta pay the bills06:24
v1k0d3ni do like quite a few bands from the recent british invasion though; snow patrol, feeder, etc06:24
jascott1afaik google is the only one I have ever read about06:24
portdirectdid sclub7 ever make it over there?06:25
v1k0d3njascott1:  you me? do i have a music room?06:25
jascott1see im so out of it my brother (who is actualy a couple years older than me) has to try to turn me onto new stuff06:25
portdirect(beause if they did i have storied that are awesome, but not for logged chan :) )06:25
jascott1ya06:25
v1k0d3nsort of a music game room06:25
jascott1haha06:25
jascott1oh cool06:26
v1k0d3ni like being "that dude" from att06:26
v1k0d3nlol06:26
jascott1we have a small kolla contingent forming here :)06:26
v1k0d3ni'm sure att likes to be represented by a bullish dude like me :) haahaha06:26
v1k0d3n(which i'm typically not btw....this was a rare week).06:26
v1k0d3ndont think sclub7 ever made it that i'm aware of.06:27
jascott1ive been talking to you long enough to know you seem pretty cool and reasonable and have great rep06:27
v1k0d3ni know a couple of bucket list items out your way for me is to go to a festival on the isle of wight06:28
jascott1im sure att is very happy to have you rep'n06:28
portdirectv1k0d3n: trust me without context it'll make no sense, they were a terrble offshot of a kids tv servies06:28
jascott1jimi's last show06:28
v1k0d3nbut before that is go to the isle of man tt06:28
jascott1or was it man. dang memory06:28
jascott1i thought it was white but idk06:28
*** sayanta__ has quit IRC06:29
jascott1oh wow Isle of Fehmarn06:29
jascott1boy i bet rock lore has taken a hit since the advent of this here internet06:29
v1k0d3nnever been to any, but would like to go some time.06:29
jascott1where are you again? sorry i think you told06:30
jascott1west coast?06:30
*** huzhengchuan has joined #openstack-kolla06:30
jascott1portdirect are you going to ptg?06:32
portdirectgonna apply for frunding, didnt realise i just missed the first round06:32
portdirect*funding06:32
v1k0d3ncrap port...you're approach was way better :)06:33
v1k0d3nimages aren't pushing the way i thought/wanted them too.06:33
portdirectlol06:33
jascott1talking about DinD?06:33
v1k0d3nyeah, crazy hack06:33
portdirecti hid one of my memes in the base64 for you too06:34
*** sayantan_ has joined #openstack-kolla06:34
jascott1yeah i read "absolutely do not do this" but of course did it and it worked fine for what I was doing06:34
v1k0d3noh i kept a nice disclaimer on our page too :)06:35
portdirectwhats up with pushing though? that should work?06:35
v1k0d3nyeah it really should06:35
portdirectyour method looks finw06:35
v1k0d3nthing is it's not logging either, which means the images aren't really...there.06:35
v1k0d3nstrange.06:35
jascott1oh man i want to write some golang anyone need little utility?06:35
portdirectoh on that note - I saw that the tc is reviewing lettig golang into openstack06:36
jascott1again?06:36
portdirectoh :(06:36
jascott1they just voted it down recently06:36
portdirecti hoped this was the first time06:36
jascott1but its been months06:36
jascott1idk 6 mo ago maybe?06:37
portdirectv1k0d3n: you running from docker or k8s?06:37
jascott1it will happen eventually i think/hope06:37
v1k0d3ndocker actually as a test06:37
* jascott1 is not really py guy06:37
v1k0d3ni have python error handling.06:38
v1k0d3njust saying06:38
jascott1i like py and think go stole a lot a good stuff from it ;)06:38
jascott1but ya go is far from perfect but is perfect for container werld06:38
portdirectv1k0d3n: try running with -t as well06:38
portdirectalso it will be *much* happier if you bind mount /var/lib/docker somewhere06:39
v1k0d3n^^ good suggestion06:39
*** adrian_otto has quit IRC06:39
v1k0d3nquestion, what's a container that has almost no dependancies that i can build?06:40
jascott1what do you need?06:40
v1k0d3ndoing keystone is stupid...takes way too long for a test run.06:40
jascott1busybox ou mean?06:40
jascott1oh kolla06:40
portdirectno kolla06:40
v1k0d3nyeah06:40
portdirectopensatck-base, off the top of my head06:40
jascott1toolbox? sorry idk06:40
portdirectopenvswitch-base will be the fastes i think06:41
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Optimized reconfigure action for glance  https://review.openstack.org/40697806:41
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Optimized reconfigure action for nova  https://review.openstack.org/40741606:41
portdirecti dont know how to build just 'base' very time I've tried it builds all of the images with base in the name06:42
*** adrian_otto has joined #openstack-kolla06:42
v1k0d3nyeah, that behavior could be improved at some point.06:43
jascott1there is no way? i though it could do that06:44
v1k0d3nno, portdirect is right...if you say base, it takes everything with base in the name06:44
portdirectprobably is, but who read the manual?06:44
* v1k0d3n lowers head in shame06:44
* v1k0d3n raises back up06:45
* portdirect is no better06:45
v1k0d3nthat's not really true06:45
v1k0d3ni do a fairly good job06:45
v1k0d3ni think anyone who works with this hipster stuff has to06:45
* jascott1 has already confessed to not RTFM for petset upgrade earlier06:45
v1k0d3n:)06:45
* v1k0d3n slams foot on the ground06:45
jascott1haha06:45
portdirecti'm that horrible guy who usually just goes to the source, make me feel all superior for 30 seconds, untill the deep felling of regeret and WTF sets in06:46
jascott1lol06:46
v1k0d3nso portdirect i have to admit06:46
v1k0d3nimage sizes are absolutely out of control for a kubernetes architecture standpoint06:46
v1k0d3nlike holy yikes06:46
portdirectok - we can fix that06:47
v1k0d3nbuilding these things in dind...and you REALLY feel the pain06:47
portdirectSamYaple: has deone some awesome things06:47
v1k0d3nyeah, i know. just a realization, that's all06:47
v1k0d3nall fixable06:47
portdirective got most things under 150mb with alpine, but thes done stuff with ubuntu that may interest you06:48
v1k0d3noh that dude's awesome with image sizes. i forget his name...from oracle...went to out out shooting with SamYaple...he's impressed with his image skillz :)06:48
* v1k0d3n laughs thinking that he's going to read that tomorrow morning06:48
jascott1oh yeah there is a little golang in openstack already in hummingbird (swift)06:48
v1k0d3nyeah, but for us alpine won't work. yet anyway.06:49
portdirectfigured06:49
v1k0d3ni would have to find a way to make it work with ubuntu/centos or at least debian something based.06:49
jascott1wow 150 is big for alpine06:49
v1k0d3nyeah, you know why...CVE's06:49
v1k0d3nyeah, but compared to 700-800 now?06:49
v1k0d3nin kubernetes terms that's like a giant elephant sitting in a bathtub06:50
jascott1woah havent been paying attention i guess thats insane06:50
portdirectyeah SamYaple's managed to get keystone down to 40mb in ubuntu i think06:50
portdirect(though that image transfer size)06:50
v1k0d3nyup. that's what i'm interested in hearing about06:50
jascott1squashing?06:51
v1k0d3nyes06:51
v1k0d3npart of it06:51
portdirectyeah06:51
portdirectand stripping out all the rubbish thats in the base container06:51
portdirecti've stopped squashing my images becuase the extra time it tok was a killer06:51
portdirectincreases the build but about 3 times in my expereince06:52
portdirectbut can save huge amounts of space if you get it right06:52
*** afranc has quit IRC06:52
jascott1they should start switching to go, horizon could be 6MB + assets06:52
portdirectsooo... jascott1 you hang with the clearos crew at all?06:53
jascott1dont know them but work nearby06:53
jascott1clear containers06:53
jascott1some other interesting projects, a lot of 01.org projects actually06:54
portdirectyeah i was getting confused i think, but arnt some of the 01.org lot up to a openstack in go kinda thing?06:54
jascott1i run internal golang "message board" but not a lot of participation :/06:54
jascott1which?06:55
jascott1they have a lot of stuff06:55
jascott1oh yeah06:55
jascott1there is but its kinda openstack and k8s ish06:56
portdirecthttps://github.com/01org/ciao#ciao-project, though haven't looked into it06:56
v1k0d3nyeah portdirect amazingly it skips right over this bash script06:57
v1k0d3nthat makes no sense to me06:57
jascott1i have seen a presentation on it, it was neat. i hope it works out for them cause it looks well made but fear k8s has the mindshare momentum and google name06:58
*** adrian_otto has quit IRC06:58
portdirectthat image pushed?06:58
v1k0d3nnope nothing06:58
* portdirect fires up terminal, puts on coffee06:59
v1k0d3nno worries06:59
v1k0d3ni'll figure it out06:59
dupengfeiHello, For help, When do "helm install", I get Error: could not find a ready tiller pod, what 's the problem?06:59
v1k0d3nit's cake. just annoying cake that you have eat just because you're at a wedding.06:59
v1k0d3nif you do kubectl do you have a tiller container?07:00
v1k0d3ndupengfei: ^^07:00
v1k0d3nor did you do helm init first?07:00
dupengfeiv1k0d3n : No07:00
jascott1portdirect do you have a gist/wanna make one for that dev setup? i will help propagate from there after I understand it :) no rush, you seem busy07:00
v1k0d3nhelm init07:01
*** afranc has joined #openstack-kolla07:01
dupengfeiv1k0d3n : I have did helm init, it show me "Warning: Tiller is already installed in the cluster."07:01
v1k0d3nkubectl get pods -o wide --all-namespaces07:01
v1k0d3nno tiller still?07:01
v1k0d3ntiller appears that it's there07:02
dupengfeikube-system   tiller-deploy-2885612843-fz0cw   0/1       ContainerCreating   0          40m       <none>    node307:02
portdirectjascott1: that would be awesome, i could tidy up the ps i have in and then would be really happy for you to take it of my hands or help me get it in shape07:02
v1k0d3nok...wait until that loads. takes a little bit of time07:02
dupengfeiv1k0d3n : I got it .,thanks07:02
v1k0d3nhow long since you helm init?07:02
portdirectjascott1: apart form anything its really imoprtant to make sure it works for maor than just me :)07:02
dupengfei10 minutes07:02
v1k0d3noh wow07:02
v1k0d3nok07:02
v1k0d3nthat's a problem07:02
portdirectdupengfei: what country are you in?07:02
v1k0d3ngood question07:03
jascott1portdirect I am perfect for testing 'fool proofiness'07:03
v1k0d3nkubectl get pods -o wide --all-namespaces -w07:03
*** sayantan_ has quit IRC07:03
*** zhangshuai has quit IRC07:03
jascott1whats the w?07:03
v1k0d3n^ i use that when i know my environment is good and download is speedy07:03
v1k0d3nwait show changes07:03
jascott1oh yea07:03
*** zhangshuai has joined #openstack-kolla07:03
v1k0d3ni'm a big fan. first thing i alias :)07:04
dupengfeiportdirect: China, The country which are blocked by firewall to internet.07:04
jascott1mine first alias is k=kubectl07:05
v1k0d3nouch07:05
dupengfeiportdirect: I 'm afraid i have to find another way to get the image07:05
v1k0d3nksa = kubectl get pods -o wide --all-namespaces -w07:05
v1k0d3nkube show all :)07:05
jascott1kgp is get pods07:05
jascott1ha07:05
portdirectdupengfei: i can help you there07:05
v1k0d3noh no07:05
v1k0d3nhere go the tor instructions07:05
v1k0d3n:))07:05
portdirectcan you use docker registry07:06
dupengfeiportdirect: thanks, i have a VPN to get the image.07:06
v1k0d3nalright guys...gotta go get sleep07:06
v1k0d3nlate here.07:06
jascott1where you is?07:06
jascott1ah must be east coastin it07:07
openstackgerritjimmygc proposed openstack/kolla: Trivial fix of horizon image  https://review.openstack.org/41113807:07
v1k0d3ncharlotte nc07:07
jascott1oh duh07:07
jascott1alright i only have to publicly embarrass myself to remember things07:07
jascott1so cool.07:07
jascott1have a good one man07:07
jascott1im going to work on dev setup for a few, snowed in so no office tomorrow <thunderous applause>07:08
portdirectok - give me 2 mins and I'll make a gist if you want?07:08
jascott1thatd be great07:09
openstackgerritPete Birley proposed openstack/kolla-kubernetes: WIP: Add Development Setup Script for use with Kubernetes Helm  https://review.openstack.org/40572007:12
portdirectjascott1:  you using halycon?07:13
jascott1yup07:13
jascott1thats all set07:13
portdirectk07:14
jascott1(afaik)07:14
portdirect2 more min07:14
jascott1no rush man!07:14
* portdirect drops everything07:14
* jascott1 starts cloud native DOG related side project in golang while waiting07:14
*** JRobinson__ has quit IRC07:18
*** portdirect has quit IRC07:19
*** portdirect has joined #openstack-kolla07:19
portdirectword07:21
* portdirect wishes he had the time to walk a dog, but untill he does will hold childish grudges against them...07:22
portdirectjascott1: you will need to run this on the node that you want ceph to run on (i recommend kube2):07:23
portdirecthttps://gist.githubusercontent.com/intlabs/4f432a79814f065f953ef2b08de78711/raw/69a7634996d8673b49d711e11232b8105742b503/loopback.yaml07:23
portdirectcan either build a new cluster or just ssh in and do it07:23
jascott1ok07:24
portdirectthen i hope that that ps: https://review.openstack.org/#/c/405720/ should now be ok07:24
*** msimonin has quit IRC07:24
portdirectoh - you will need to remove the kolla dir!07:24
jascott1?07:25
portdirect2 sec I'll fix it07:25
jascott1oh i see07:25
jascott1np07:25
*** magicboiz has joined #openstack-kolla07:26
openstackgerritPete Birley proposed openstack/kolla-kubernetes: WIP: Add Development Setup Script for use with Kubernetes Helm  https://review.openstack.org/40572007:26
portdirectfrom there i recomend going though it pretty slowly at first07:27
portdirectusing the docker run command in the dockerfile label07:27
jascott1cool thank you07:27
portdirectand working your way trhough tools/setup_dev_env.sh07:27
openstackgerritjianyi proposed openstack/kolla: [WIP] Add zun container  https://review.openstack.org/41061607:28
portdirectdont know how to link directly to line on gerrit, but the major hacks are in this file https://review.openstack.org/#/c/405720/9/tests/bin/build_dev_ceph.sh07:28
portdirectwhere I'm just swapping out the hostname using sed07:29
jascott1ah ok07:29
portdirectbut event wothout that - i found the best way to get the microservices over was getting the kollakube template cmd working, whihc allowed me to check the output from helm debug to see that it matched07:30
*** magicboiz has quit IRC07:31
portdirectbetter go as well, but feel free to take over that ps, ar just comment on it when you enevitbly run onto issues07:31
jascott1thanks again man07:32
portdirectl8rs dude :)07:32
jascott1see ya on helm mtn!07:32
*** magicboiz has joined #openstack-kolla07:34
*** portdirect is now known as portdirect_away07:36
*** zhugaoxiao has quit IRC07:39
*** zhugaoxiao has joined #openstack-kolla07:39
openstackgerritzhubingbing proposed openstack/kolla-ansible: add panko role  https://review.openstack.org/40012207:43
openstackgerritjimmygc proposed openstack/kolla: Readability improvement to base image  https://review.openstack.org/41115407:49
jascott1anyone know how to get a raw file out of review.openstack.org without downloading? more like github raw07:49
portdirect_awayjascott1: nope :(07:49
portdirect_awayI've tended to download the entire tarball when I've needed that :/07:50
portdirect_awayoh07:51
portdirect_awayif you get the file you want up: eg https://review.openstack.org/#/c/405720/9/tests/bin/ceph_dev_workflow.sh07:51
portdirect_awaythere is a download link by where you can select the patchset that just gets that file on its own07:52
*** portdirect_away has quit IRC07:53
jascott1oh ive got it locally but im always wanting a raw of something on here, i bet there is a way07:53
jascott1looks like infra or whoever maybe hacked on gitweb?07:53
*** tonanhngo has quit IRC07:54
*** gfidente has joined #openstack-kolla07:58
*** gfidente has joined #openstack-kolla07:58
dupengfeiportdirect : Can you help me to get "gcr.io/kubernetes-helm/tiller:v2.1.0" Image ?08:01
openstackgerritzhubingbing proposed openstack/kolla-ansible: add panko role  https://review.openstack.org/40012208:02
dupengfeiportdirect : I just get the v2.0.1, but i can't work seemly.08:02
*** tonanhngo has joined #openstack-kolla08:02
openstackgerritjimmygc proposed openstack/kolla: Improve bash command used in bifrost-base image  https://review.openstack.org/41115808:04
*** tonanhngo has quit IRC08:04
openstackgerritzhubingbing proposed openstack/kolla-ansible: Integrate ceph-rgw with keystone  https://review.openstack.org/40697108:05
*** matrohon has joined #openstack-kolla08:12
*** Pavo has quit IRC08:12
*** shardy_afk is now known as shardy08:17
*** Pavo has joined #openstack-kolla08:17
*** b_bezak has joined #openstack-kolla08:27
*** jianyi has joined #openstack-kolla08:27
jianyican someone see my words?  use this tool for the first time,and test08:30
*** msimonin has joined #openstack-kolla08:30
*** msimonin has quit IRC08:31
zhangqiankunyes I can08:31
*** rmart04 has joined #openstack-kolla08:32
openstackgerritzhubingbing proposed openstack/kolla-ansible: Fix ceilometer api logs name  https://review.openstack.org/41116408:33
*** fragatina has joined #openstack-kolla08:33
zhangqiankuncan somebody tail me why CI faild :https://review.openstack.org/#/c/407810/08:33
*** pcaruana has joined #openstack-kolla08:37
zhubingbing_<zhangqiankun  i help you look it08:37
*** fragatina has quit IRC08:37
*** egonzalez90 has joined #openstack-kolla08:40
zhubingbing_http://logs.openstack.org/10/407810/8/check/gate-kolla-dsvm-deploy-oraclelinux-binary-centos-7-nv/2d201b3/console.html#_2016-12-15_06_38_18_76924408:40
zhubingbing_sup egonazalez9008:41
zhubingbing_https://review.openstack.org/#/c/411164/ can u look it08:41
egonzalez90morning08:41
zhubingbing_ceilometer api  logs name is error;08:42
egonzalez90whats the issue with with name?08:42
zhubingbing_we want to use log names for some flags08:43
zhubingbing_for example . use wsgi apache start service api;08:44
zhubingbing_we should service-apache-xxx.log08:44
zhubingbing_you can see keyestone logs name08:44
zhubingbing_I think we should name the style to be uniform08:45
egonzalez90is OK with me, but there is a PS under review who use ceilometer-api* for log name https://review.openstack.org/#/c/400716/3/ansible/roles/common/templates/heka-ceilometer.toml.j208:50
egonzalez90can you sync with magicboiz ?08:50
egonzalez90duonghq: around?08:52
matrohonhi08:53
matrohonI'm investigating this bug : https://bugs.launchpad.net/kolla/+bug/164984708:53
openstackLaunchpad bug 1649847 in kolla "elasticsearch : WARN too many open files" [Undecided,New]08:53
matrohonanybody already had issues that needs to update an ulimit inside a container?08:54
zhubingbing_ egonzalez90  understand08:55
matrohonactually I'd like to restart the elasticsearch container and setting a new limit for the number of open files08:56
egonzalez90matrohon: fluentd dockerfile modifies it08:56
egonzalez90my guess is that elastic will need too08:57
matrohonI'm in mitaka, fluentd is not included, but i'll have a look at it08:57
matrohonegonzalez90, thanks08:57
egonzalez90matrohon: https://github.com/openstack/kolla/blob/master/docker/fluentd/Dockerfile.j2#L3508:58
matrohonegonzalez90, ok so I'll ne to build a new elasticsearch image and redeploy elasticsearch based on that image08:59
matrohonis there any how-to for that?08:59
*** athomas has joined #openstack-kolla09:04
egonzalez90also, you can set ulimit option in docker, so when container start inherit limits from the host09:04
egonzalez90the issue is with your deployment or is general to kolla?09:04
des_consoladoHey howcome the main.yml task explicitly includes the other tasks in the tasks/ directory? Doesn't Ansible include these implicitly anyway by being in the tasks/ dir in the role's dir and there being a main.yml? e.g. https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/prechecks/tasks09:05
des_consoladoI'm just going through the kolla-ansible code and reading the Ansible documentation alongside, it's all pretty new to me, was just reading here: http://docs.ansible.com/ansible/playbooks_roles.html#roles09:05
des_consolado"If roles/x/tasks/main.yml exists, tasks listed therein will be added to the play"09:06
duonghqegonzalez90, ping09:07
matrohonegonzalez90, I'm facing the issue on a deployment, so I'm trying to fix it on this running deloyment09:08
des_consoladoah I suppose being explicit about it could ensure the order, otherwise maybe it is lexicographical?09:09
matrohonegonzalez90, I'm surprised the "RUN ulimit" work from within the dockerfile, since it's explicitly said that setting a ulimit from inside a container is forbidden09:12
matrohonI just tried, and it ends up with this error when running the docker build : Step 1 : FROM centos09:13
matrohon ---> 97063303644409:13
matrohonStep 2 : RUN ulimit -n 6553609:13
matrohon ---> Running in 301eaa75781b09:13
matrohon/bin/sh: line 0: ulimit: open files: cannot modify limit: Operation not permitted09:13
*** jianyi has quit IRC09:21
*** bmace has quit IRC09:27
*** wanghongxu has joined #openstack-kolla09:29
*** Serlex has joined #openstack-kolla09:32
*** b_bezak has quit IRC09:36
egonzalez90duonghq: i'm a bit busy atm, will ping you later if still around here. Is to talk about  the upgrade09:36
egonzalez90matrohon: can you try https://docs.oracle.com/cd/E37670_01/E75728/html/ch04s16.html09:38
duonghqegonzalez90, nice, I'll around for about 1hrs09:39
openstackgerritVladislav Belogrudov proposed openstack/kolla-ansible: HAproxy start fails if controller NIC names differ  https://review.openstack.org/41119309:41
*** hawi has quit IRC09:45
*** yingjun has quit IRC09:46
*** HyperJohnGraham has quit IRC09:47
*** zhubingbing__ has joined #openstack-kolla09:48
*** zhubingbing_ has quit IRC09:49
*** zhugaoxiao has quit IRC09:50
*** zhugaoxiao has joined #openstack-kolla09:51
matrohonegonzalez90, thanks, I tried with the --ulimit arg of the run cmd, and it work09:52
matrohonegonzalez90, actually, I'm wondering why docker has such a low nofile limit by default, I can't find where this default param is set09:53
duonghqmatrohon, it's distro default, iirc09:54
duonghqin the image09:54
matrohonduonghq, it is said that containers inherit their limits from docker daemon limit09:56
duonghqhttps://docs.docker.com/engine/reference/commandline/dockerd/09:56
duonghqmatrohon, you right09:56
matrohonbut my docker daemon is run as root user, and the root user has higher limit...09:57
duonghqso, you can set it in docker daemon09:59
duonghqwhich host os are you using09:59
matrohondebian10:02
duonghqyou can edit the init file of Docker10:03
* matrohon testing10:03
duonghqI do not use Debian for awhile10:03
duonghqsoryr10:03
duonghqsorry10:03
*** zhubingbing_ has joined #openstack-kolla10:04
duonghqsup zhubingbing_10:04
zhubingbing_hi10:05
zhubingbing_sup duonghq10:06
*** zhubingbing__ has quit IRC10:07
openstackgerritVladislav Belogrudov proposed openstack/kolla-ansible: Some tasks fail if NIC names differ  https://review.openstack.org/41119310:11
*** Pavo has quit IRC10:12
*** Pavo has joined #openstack-kolla10:17
*** tovin07_ has quit IRC10:17
*** openstackgerrit has quit IRC10:18
*** zhubingbing_ has quit IRC10:26
*** nihilifer has quit IRC10:39
*** nihilifer has joined #openstack-kolla10:40
*** openstackgerrit has joined #openstack-kolla10:41
openstackgerritjimmygc proposed openstack/kolla: Improve bash command used in bifrost-base image  https://review.openstack.org/41115810:41
*** nihilifer has joined #openstack-kolla10:44
*** duonghq has quit IRC10:51
*** zhangqiankun has quit IRC10:55
*** zhangqiankun has joined #openstack-kolla10:55
*** negronjl has quit IRC10:56
openstackgerritjimmygc proposed openstack/kolla: Readability improvement to base image  https://review.openstack.org/41115410:59
*** negronjl has joined #openstack-kolla11:02
*** zhubingbing has joined #openstack-kolla11:05
des_consoladohey, if action=deploy like here https://github.com/openstack/kolla-ansible/blob/master/tools/kolla-ansible#L182 then what happens next? In site.yml there is no play to handle the action being deploy (there is with the prechecks command, so I'm confused)11:14
des_consoladoI mean if I run it I can see that it tries to do a bunch of stuff11:14
*** mdnadeem has quit IRC11:15
Jeffrey4lit will load the deploy.yml file in each role.11:18
Jeffrey4ldes_consolado, https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/aodh/tasks/main.yml check here11:18
des_consoladoJeffrey4l: ah thank you11:25
sp_Jeffrey4l: hi11:33
des_consoladoso it just goes and applies all the roles in the site.yml playbook, I see.11:38
*** shardy is now known as shardy_lunch11:39
des_consoladoHowever if I run the prechecks command, it doesn't because there is no relevant action to run any of the tasks in each role's tasks dir...11:39
Jeffrey4lsup sp_11:41
sp_Jeffrey4l: is there way to find the coverage of kolla or kolla-ansible ??11:42
Jeffrey4lsp_, unittest? or?11:42
sp_Jeffrey4l: via running unittest, I am trying to find the how much code has been hit11:43
Jeffrey4lshould be possible. but i am not familiar with this now.11:43
sp_like implementation of coverage of python11:43
sp_Jeffrey4l: np11:43
sp_Jeffrey4l: Thanks for the response11:44
Jeffrey4lnp ;)11:45
Jeffrey4lsp_, try this python setup.py testr --coverage11:46
Jeffrey4lyou need install coverage and ddt11:46
sp_Jeffrey4l: Thanks I will try this11:47
Jeffrey4lthere is a little unittest in kolla/kolla-ansible. and we have no idea how to test the playbook , too.11:47
*** wanghongxu has quit IRC11:48
mliimamorning guys11:48
sp_Jeffrey4l: Yes, the same i was thinking that we should have some coverage and unittest part too11:49
Jeffrey4lsp_, definitely.11:49
Jeffrey4lmorning mliima11:49
sp_mliima: mrg11:49
Jeffrey4lmliima, could u review this https://review.openstack.org/410733  ;)11:50
*** Serlex has quit IRC11:50
mliimasure Jeffrey4l11:51
Jeffrey4lthanks11:51
mliimaJeffrey4l, did you remember my issue "clnt_create-RPC-Unknown-host" in cinder_volume?11:54
Jeffrey4lmliima, hrm nfs issue?11:54
mliimayes11:54
mliimaovs package was missing in cinder_volume container11:55
mliima:/11:55
Jeffrey4lmliima, did u fix it ?11:55
Jeffrey4lwhy nfs driver need ovs package?11:55
mliimano nfs driver, but cinder-volume container can't reach the host or any ip11:56
*** tonanhngo has joined #openstack-kolla11:56
mliimain same environment, nova_compute container ran showmount -e successfully, but cinder-volume nto11:58
Jeffrey4lstill do not get the point why ovs is required.11:58
mliimanot*11:58
Jeffrey4lyep11:58
mliimaI was wondering if you could confirm this behavior Jeffrey4l11:58
mliima:D11:58
Jeffrey4lthen how to reproduce this? just deploy cinder + nfs , and try showmount -e in cinder-volume container?11:59
mliimayes11:59
Jeffrey4lok. i will try11:59
Jeffrey4lmliima, another review https://review.openstack.org/406978 ;)12:01
mliimaI'll still find a better name that recreate_or_restart_container12:02
Jeffrey4lmliima, how about rollin_configuration or rollin_container ;12:02
mliimalets merge it first12:03
mliima:)12:03
Jeffrey4lok. ( may need some language expert here lol )12:03
mliimaI'll open a vote on ML12:04
*** britthouser has joined #openstack-kolla12:04
Jeffrey4lthanks.12:04
mliimabetter a "name contest"12:04
*** britthouser3 has quit IRC12:05
*** david-lyle has quit IRC12:05
Jeffrey4llol12:05
*** david-lyle has joined #openstack-kolla12:05
mliimaback to my issue, I wondered if it is really needed to install the package within that cinder container12:06
*** tonanhngo_ has joined #openstack-kolla12:06
Jeffrey4lok. i am testing it.12:06
mliimaso I need someone else confirm this12:06
Jeffrey4lfirst step: reproduce12:06
mliima\o/12:06
*** qwang_ has joined #openstack-kolla12:07
*** tonanhngo has quit IRC12:08
*** qwang has quit IRC12:08
*** qwang_ is now known as qwang12:08
*** msimonin has joined #openstack-kolla12:09
berendtIs anybody using Clair to scan generated Docker images?12:10
berendthttps://github.com/coreos/clair12:10
berendtv1k0d3n: thanks for providing your dockerfiles on github, i just found something useful :)12:11
*** Pavo has quit IRC12:12
*** dupengfei has quit IRC12:14
*** Pavo has joined #openstack-kolla12:17
openstackgerritMerged openstack/kolla: Trivial fix of horizon image  https://review.openstack.org/41113812:20
*** skramaja has quit IRC12:28
*** skramaja_ has joined #openstack-kolla12:28
openstackgerritjimmygc proposed openstack/kolla: Readability improvement to base image  https://review.openstack.org/41115412:42
*** msimonin has quit IRC12:43
*** mnasiadka has joined #openstack-kolla12:43
openstackgerritjimmygc proposed openstack/kolla: Readability improvement to base image  https://review.openstack.org/41115412:47
*** huzhengchuan has quit IRC12:47
*** rhallisey has joined #openstack-kolla12:47
openstackgerritjimmygc proposed openstack/kolla: Readability improvement to base image  https://review.openstack.org/41115412:48
*** jianyi has joined #openstack-kolla12:52
*** msimonin has joined #openstack-kolla13:01
*** mdnadeem has joined #openstack-kolla13:04
*** skramaja_ has quit IRC13:06
*** skramaja has joined #openstack-kolla13:06
*** shardy_lunch is now known as shardy13:06
*** dave-mccowan has joined #openstack-kolla13:08
openstackgerritjimmygc proposed openstack/kolla: Improve bash command used in bifrost-base image  https://review.openstack.org/41115813:12
*** eaguilar has joined #openstack-kolla13:17
openstackgerritSurya Prakash Singh proposed openstack/kolla: Cover environment for kolla  https://review.openstack.org/41131313:21
*** SamYaple has quit IRC13:22
*** SamYaple has joined #openstack-kolla13:22
*** saneax is now known as saneax-_-|AFK13:23
*** ayoung_dadmode is now known as ayoung13:32
*** jheroux has joined #openstack-kolla13:32
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Allow cinder-volume to be configured to use HNAS iscsi  https://review.openstack.org/40988313:39
v1k0d3nha! berendt of course :) that's how we roll.13:39
v1k0d3nwhich one?13:39
v1k0d3n(working on one of them now actually for a fix).13:39
*** Serlex has joined #openstack-kolla13:43
v1k0d3noh and berendt yes, have used clair with these images before, both on host and tied with a registry.13:44
v1k0d3nhaven't gotten around to it in a while; was in a security group...then went to more of a cloud arch & open source role (much more fun).13:45
*** zhangqiankun has quit IRC13:50
*** srwilkers has joined #openstack-kolla13:50
srwilkersmorning p/13:50
srwilkerso/13:50
sbezverkgood morning13:55
srwilkershows it going sbezverk13:56
openstackgerritVladislav Belogrudov proposed openstack/kolla-ansible: Some tasks fail if NIC names differ  https://review.openstack.org/41119313:59
sbezverksrwilkers: so far so good ;-), holidays are really near :-)13:59
srwilkerssbezverk, thats great to hear :) im excited for the holidays. looking forward to less time in the office ;)13:59
sbezverksrwilkers: I work from home14:00
*** zhubingbing has quit IRC14:00
srwilkerssbezverk, im jealous. im "encouraged" to work in the office as much as possible14:00
srwilkerss/encouraged/told14:01
sbezverksrwilkers: I would work from the office too if it were not a sales office where everybody wear ties and suits14:01
sbezverksrwilkers: and no way to get a parking spot14:01
openstackgerritMerged openstack/kolla-ansible: Integrate ceph-rgw with keystone  https://review.openstack.org/40697114:02
srwilkerssbezverk, ugh, suits and ties. not for me14:03
*** eaguilar_ has joined #openstack-kolla14:03
sbezverksrwilkers: exactly my sentiment too..14:04
*** goldyfruit has joined #openstack-kolla14:06
*** eaguilar has quit IRC14:06
*** lrensing has joined #openstack-kolla14:09
*** lamt has joined #openstack-kolla14:10
*** Pavo has quit IRC14:12
*** HyperJohnGraham has joined #openstack-kolla14:13
Jeffrey4lpbourke, could u review this? https://review.openstack.org/40697814:15
pbourkelooking14:15
Jeffrey4lthanks.14:15
*** fguillot has joined #openstack-kolla14:16
*** Pavo has joined #openstack-kolla14:17
*** portdirect_away has joined #openstack-kolla14:18
*** portdirect_away is now known as portdirect14:19
portdirectafternoon o/14:19
*** portdirect is now known as portdirect_14:19
*** portdirect_ is now known as portdirect14:19
mliimahello portdirect \õ14:20
portdirectnice haircut mliima :)14:21
mliimahehehe14:23
Jeffrey4lhow to tigger a recheck in gate pipeline?14:27
Jeffrey4l"recheck" only trigger check pipeline14:28
*** huzhengchuan has joined #openstack-kolla14:30
*** Jeffrey4l_ has joined #openstack-kolla14:30
*** l4yerffeJ_ has joined #openstack-kolla14:30
*** Jeffrey4l_ has quit IRC14:31
*** Jeffrey4l_ has joined #openstack-kolla14:34
*** sdake has joined #openstack-kolla14:34
*** Jeffrey4l has quit IRC14:34
*** l4yerffeJ__ has quit IRC14:34
*** magicboiz has quit IRC14:37
*** l4yerffeJ_ has quit IRC14:37
*** l4yerffeJ_ has joined #openstack-kolla14:38
openstackgerritMerged openstack/kolla: Add logrotate configuration for elasticsearch  https://review.openstack.org/41021714:38
*** magicboiz has joined #openstack-kolla14:41
*** eaguilar has joined #openstack-kolla14:42
v1k0d3nmorning all14:42
*** eaguilar_ has quit IRC14:42
pronif i install kolla from git where i can find example inventory files?14:43
*** jtriley has joined #openstack-kolla14:46
kfox1111morning14:48
srwilkersmorning v1k0d3n o/14:48
srwilkershey kfox1111 o//14:48
*** eaguilar_ has joined #openstack-kolla14:49
kfox1111srwilkers: hey14:49
kfox1111hi v1k0d3n14:49
kfox1111nice. looks like ubuntu cut their release and the gate worked with it.14:50
*** eaguilar has quit IRC14:50
kfox1111sbezverk: should we workflow https://review.openstack.org/#/c/410464/ ?14:50
*** athomas has quit IRC14:53
v1k0d3nhey kfox1111 morning14:54
*** jianyi has quit IRC14:55
pronis the ansible folder gone from kolla repo?14:56
kfox1111pron: it was split into kolla-ansible repo.14:57
pronjust content of  that folder or ?14:58
pronwhat does kolla provide and what does kolla-ansible provide at the moment? i am confused now14:59
berendtpron: kolla: docker images and tools14:59
berendtpron: kolla-ansible: everything related to ansible14:59
berendtall docs life in kolla repository at the moment15:00
pronso how to actualy use them15:00
* pron loooks at all this with tears on eyes15:00
berendtcheck the quickstart guide, it should be up to date15:01
*** athomas has joined #openstack-kolla15:01
sbezverkkfox1111: morning, so ready to merge 1.5?15:04
pronberendt: i think it doesnt15:04
egonzalez90berendt: not yet, is under rework yet15:05
kfox1111sbezverk: Yeah. I think so.15:05
kfox1111we can fix further gate instability as it shows I think.15:06
sbezverkkfox1111: ok flipping the switch then ;-)15:07
kfox1111thanks.15:08
*** mnasiadka has quit IRC15:10
egonzalez90pron: is the same usage but in different folders, when using kolla-ansible move to kolla-ansible folder, at tools/ have the scripts15:10
openstackgerritMerged openstack/kolla-kubernetes: Switch to helm 2.1.0 and kubernetes 1.5+  https://review.openstack.org/41046415:11
*** tonanhngo_ has quit IRC15:16
*** yingjun has joined #openstack-kolla15:17
openstackgerritPete Birley proposed openstack/kolla-kubernetes: Helm Keystone API  https://review.openstack.org/41056415:19
srwilkershey portdirect o/15:20
openstackgerritPete Birley proposed openstack/kolla-kubernetes: Helm Keystone API  https://review.openstack.org/41056415:20
portdirecthey srwilkers o/15:21
portdirectsup dude15:21
srwilkerscertainly not me yet. how are you?15:21
portdirectlol - almost back on proper uk time :) about to head into a meeting thou :/ you gonna be about in an hour?15:22
srwilkersyeah, im here all day15:24
*** jhaleblian has joined #openstack-kolla15:26
portdirectnice - just cooked this up was gonna fix it up to talk to google cal, but may be of use? http://port.direct/dev-cal/ if there's anything i should put on it just hit me up15:26
srwilkersoh man, i like this15:28
srwilkersgoing to fork that upstream repo and replace my outlook calendar at work with this as much as possible. hate outlook15:29
*** mdnadeem has quit IRC15:34
*** portdirect has quit IRC15:43
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron db stuff  https://review.openstack.org/41033615:48
openstackgerritMerged openstack/kolla: Fix manila-ui  https://review.openstack.org/41090615:51
*** TxGirlGeek has joined #openstack-kolla15:54
*** gomarivera has joined #openstack-kolla15:56
egonzalez90magicboiz: ping15:57
magicboizHi egonzalez9015:58
*** gomarivera has quit IRC16:02
des_consoladohey, in kolla-ansible where do we put the ssh user and does it automatically know where to look for keys?16:05
des_consoladoI'm using it like sudo -s tools/kolla-ansible [blah blah blah]16:05
des_consoladoit should then know my username and look in my .ssh for keys and everything, right?16:06
*** klindgren__ is now known as klindgren16:06
*** eaguilar has joined #openstack-kolla16:10
*** matrohon has quit IRC16:11
*** diogogmt has quit IRC16:12
*** Pavo has quit IRC16:12
*** krtaylor has quit IRC16:13
*** dave-mccowan has quit IRC16:13
*** eaguilar_ has quit IRC16:13
*** Pavo has joined #openstack-kolla16:13
*** matrohon has joined #openstack-kolla16:16
*** ayoung has quit IRC16:17
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Allow cinder-volume to be configured to use HNAS iscsi  https://review.openstack.org/40988316:18
*** sayantan_ has joined #openstack-kolla16:22
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Allow cinder-volume to be configured to use HNAS iscsi  https://review.openstack.org/40988316:23
*** bmace has joined #openstack-kolla16:24
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm chart for cinder-scheduler  https://review.openstack.org/41052516:24
*** eaguilar has quit IRC16:25
*** rmart04 has quit IRC16:27
*** adrian_otto has joined #openstack-kolla16:28
openstackgerritJeffrey Zhang proposed openstack/kolla: [wip] collect logs  https://review.openstack.org/41140316:29
*** dave-mccowan has joined #openstack-kolla16:29
*** fguillot has quit IRC16:34
*** jmcevoy has quit IRC16:36
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron db stuff  https://review.openstack.org/41033616:38
*** pcaruana has quit IRC16:42
openstackgerritJeffrey Zhang proposed openstack/kolla: Move openvswitch db file into docker volume  https://review.openstack.org/41073316:42
*** matrohon has quit IRC16:49
*** fragatina has joined #openstack-kolla16:53
*** jmcevoy has joined #openstack-kolla16:57
*** fragatina has quit IRC16:57
v1k0d3nwow portdirect_zzzzz this is good man!16:59
v1k0d3n(the cal)17:00
*** huzhengchuan has quit IRC17:01
srwilkersv1k0d3n, +117:02
*** diogogmt has joined #openstack-kolla17:04
*** egonzalez90 has quit IRC17:05
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron db stuff and add svc.  https://review.openstack.org/41033617:06
*** HyperJohnGraham has quit IRC17:08
*** vbel has joined #openstack-kolla17:09
*** ajafo has quit IRC17:09
*** ajafo has joined #openstack-kolla17:10
*** mdnadeem has joined #openstack-kolla17:17
*** portdirect_zzzzz has quit IRC17:19
*** rhallisey has quit IRC17:19
*** unicell has quit IRC17:19
*** portdirect_zzzzz has joined #openstack-kolla17:22
*** portdirect_zzzzz is now known as portdirect17:22
*** tonanhngo has joined #openstack-kolla17:25
*** portdirects_lapt has joined #openstack-kolla17:27
vbelhi everyone, I try to get normal user in _member_ group working with swift and getting no access. Do we have a setting somewhere to enable such? I see elsewhere that by default swift belongs to operators :)17:27
portdirects_lapto/17:28
*** tonanhngo has quit IRC17:29
*** Jeffrey4l_ has quit IRC17:33
*** Jeffrey4l_ has joined #openstack-kolla17:33
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092317:33
kfox1111sbezverk: https://review.openstack.org/#/c/410336/ should be ready.17:36
sdakehey fellas, we have a shutdown at work 20th-5th17:37
*** yingjun has quit IRC17:38
sdakeI will be shutting down most of this time as well but checking email periodically17:38
kfox1111sdake: does it affect sbezverk as well?17:38
sdakenot sure what sbezverk 'z plans are17:38
kfox1111k17:38
*** tonanhngo has joined #openstack-kolla17:38
sdakeour shutdown is actually the 23rd-3rd i think, but I'm shutting down 20th-5th :)17:38
sdakei'll be on and off17:39
kfox1111I'm off work till the end of the year, but will be away on vacation visiting family the 26-30'th. the rest of the time I'm around.17:39
sdakebut mostly busy with family activities17:39
openstackgerritMerged openstack/kolla-kubernetes: Hel-ming horizon components  https://review.openstack.org/40897517:39
kfox1111kk. thanks for the heads up.17:39
srwilkersThe helm devs call is happening now17:39
kfox1111which call?17:39
sdakeunfortunately i ahve a conflict in 20 minutes so won't be able to make it17:39
openstackgerritYann Provost proposed openstack/kolla-ansible: Add storage interface address  https://review.openstack.org/41143217:40
srwilkersThe kubernetes helm devs call17:40
sdakeperhaps kfox1111 or sbezverk can17:40
sdakeand need to prep for my meeting17:40
sdakebbl17:40
kfox1111srwilkers: got a link? is it open?17:40
srwilkerskfox1111, https://engineyard.zoom.us/j/36642554917:41
srwilkersits open17:41
sdakezoom is a pretty cool service17:41
sdakebetter then google hangouts17:41
srwilkersi like it17:41
kfox1111strarts in 20? or going on now?17:41
srwilkersgoing on now17:41
kfox1111for how much longer?17:41
srwilkers18m left17:42
kfox1111k17:42
*** jmcevoy has quit IRC17:42
*** mdnadeem has quit IRC17:45
openstackgerritMauricio Lima proposed openstack/kolla: Fix ceilometer not sending logs to heka  https://review.openstack.org/41143417:46
srwilkersisnt that the truth, re: openstack being a special snowflake here17:46
kfox1111not just that, but its  the most nontrivial app they've ever had.17:47
*** eaguilar has joined #openstack-kolla17:47
kfox1111it will show all the gaps in the software.17:48
*** Bico_Fino has joined #openstack-kolla17:48
srwilkersi agree. thats why i like the idea of having a sig focused on openstack in helm. i think maintaining that tie with their community will really help as we identify those gaps17:48
*** jrich523 has joined #openstack-kolla17:49
*** msimonin has quit IRC17:49
Bico_FinoAnyone running ironic-inspector with Kolla(3.0.1)?17:50
kfox1111+117:50
kfox1111well, with one caviot...17:50
Bico_FinoGetting a lot of errors like : ERROR oslo_db.sqlalchemy.exc_filters InternalError: (1054, u"Unknown column 'nodes.finished_at' in 'where clause'")17:50
kfox1111we've tried to make kolla-kubernetes a place to do that.17:50
kfox1111in a way.17:50
*** unicell has joined #openstack-kolla17:51
Bico_FinoI got ironic-conductor working and such. Working on ironic-inspector.17:51
kfox1111how much do we encurage more independent implementations outside of kolla-kubernetes?17:51
kfox1111that in some ways can be less hea[C[Clthy for the community.17:52
Bico_Finowhat you mean?17:53
srwilkersideally, i wouldnt like to encourage it at all. that does require some give and take however. that was the last point of discussion in our meeting yesterday. we need to look long term and see what's best so we can make sure this is the place that can happen in openstack17:53
kfox1111yeah.17:54
kfox1111multiple competing deployment tools can be healthy, if there are good reasons for the differences.17:54
kfox1111but I'm not convinced we're there.17:54
kfox1111at least at the helm+k8s layer.17:55
kfox1111I think the compoitition couild be good around gui's and such.17:55
* v1k0d3n reading back17:55
v1k0d3nsdake: yeah, big fan of zoom over hangouts. better on my poor memory!17:56
*** unicell has quit IRC17:56
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm chart for cinder-scheduler  https://review.openstack.org/41052517:57
*** TxGirlGeek has quit IRC17:58
v1k0d3njust couple of thoughts.17:58
*** TxGirlGeek has joined #openstack-kolla17:59
v1k0d3nfor us, no need for gui's but can understand how others would need that.17:59
v1k0d3nhopefully no requirement though.17:59
Bico_FinoJust removed and deployed the ironic_inspector container, these are the errors -> http://pastebin.com/wvVh3LbJ17:59
v1k0d3nsorry requirement for a gui to do things.17:59
Bico_FinoShould I open a bug?17:59
v1k0d3nalso, competing deployments is ok from my perspective at least, along with competition.18:00
v1k0d3nto your point kfox111118:00
*** gomarivera has joined #openstack-kolla18:00
v1k0d3nprojects typically split because of different architectures (like what is considered to be first class).18:00
*** unicell has joined #openstack-kolla18:00
kfox1111v1k0d3n: I think the differeence in my head is, most deployment tools compete with each other on their opinionated stuff.18:01
v1k0d3n+118:01
kfox1111kolla-kubernetes is striving for a totally unopinionated building block layer that shoudl be sharable by anyone wanting to build a distro on top.18:01
kfox1111so those opinionated distros shoudl be able to share that part.18:01
v1k0d3nto that though, i consider helm as a template too first, deployment tool for kubernetes (native to kubernetes) second.18:02
kfox1111and we can then work on it all together rather then fighting over it.18:02
v1k0d3nno fighting18:02
v1k0d3ni think just different uses.18:02
*** fragatina has joined #openstack-kolla18:02
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092318:02
kfox1111well, I'm saying, the different uses shoudl be handled by the building blocks for all use cases.18:02
v1k0d3nformatting and required steps to use it.18:02
kfox1111so no reason to make two different objects in different projecgs that do the same thing.18:03
kfox1111like, a k8s object for neutron-l3-agent for example.18:03
*** fragatina has quit IRC18:03
kfox1111we should be able to come up with a common object an share.18:03
v1k0d3nshould be. but don't have to.18:03
kfox1111I think most of the contention will be in the how its orchestrated /deployed.18:04
v1k0d3nit's perfectly fine to have different approaches.18:04
*** fragatina has joined #openstack-kolla18:04
* kfox1111 shrugs.18:04
v1k0d3nfor instance, one project may make it a requirement to run some sort of prebuild before the charts are usable.18:04
kfox1111thats the, should I contribute to linux, or one of the bsd's thing.18:04
kfox1111the compitition is good, kind of.18:04
v1k0d3nanother may consider their charts usable before any pre-processing.18:04
v1k0d3nand both are ok; just different approachs.18:04
*** rhallisey has joined #openstack-kolla18:04
kfox1111but linux has progressed so much farther because it kept  the infighting/forking at a minimum.18:04
v1k0d3n* approaches18:04
*** pbourke has quit IRC18:04
v1k0d3noperators will decide in the end what they like. both have place.18:05
*** gomarivera has quit IRC18:05
v1k0d3ni don't agree with you18:05
*** pbourke has joined #openstack-kolla18:05
kfox1111v1k0d3n: ok. phylisophical disagreement then. thats  fine. no further talkign will probably convince the other then.18:05
*** sayantan_ has quit IRC18:05
v1k0d3ni.e. coreos, atomic, fedora, rhel, centos, ubuntu, manjaro, archlinux, etc.18:05
v1k0d3nall have communities and use cases.18:05
kfox1111v1k0d3n: distro's are way less forky then bsd os's.18:06
*** sayantan_ has joined #openstack-kolla18:06
v1k0d3nok. i think we see each others point.18:06
kfox1111yeah.18:06
kfox1111distro's are kind of a fork in a way, yeah.18:06
v1k0d3nbut both points have merit imho.18:06
kfox1111agreed.18:06
kfox1111I was more talking about hte linux kernel.18:06
v1k0d3ni don't know...i consider that so different from what we're talking about here...18:07
kfox1111the discuraging of forks has caused the community to come together as a whole and contribute to each other.18:07
v1k0d3ni don't compare the linux kernel to a helm usecase for openstack+kubernetes :-/18:07
kfox1111and ultimately has led to linux gaining so much more traction over other os's on number of deployments18:07
kfox1111from microwaves up throug supercomputers.18:07
kfox1111the philosophy applies to generically to all opensource.18:08
*** Bico_Fino has quit IRC18:08
*** Bico_Fino_ has joined #openstack-kolla18:08
kfox1111forks are good when needed for sure.18:08
kfox1111but exsessive forks splinters the community and harms the momentum of any solution.18:08
v1k0d3nsometimes forks are needed to grab attention too :)18:08
*** TxGirlGeek has quit IRC18:08
srwilkersi feel were getting off topic here.  heres what i see18:08
v1k0d3ni.e. docker vs. rkt18:08
kfox1111yup.18:09
v1k0d3nlook how much good came out of that.18:09
kfox1111rkt was a case of a needed fork.18:09
v1k0d3nhave they merged, even though docker relaxed? nope.18:09
v1k0d3nand both good products?18:09
v1k0d3nyup18:09
*** TxGirlGeek has joined #openstack-kolla18:09
v1k0d3nwell, when a fork occurs, the user feels they have a good case.18:09
v1k0d3nsomething has broken down somewhere.18:09
* portdirect forked vanilia icecream once18:09
*** shardy has quit IRC18:10
* v1k0d3n sporked ice cream once18:10
kfox1111yes. but a lot of forks happen for kind of bad reasons. political/communication breakdown or a dev just wanting to reimplement the wheel.18:10
* v1k0d3n sidenote: it was peach ice cream :)18:10
v1k0d3nso let's call this one out to get it in the open, ok?18:10
*** TxGirlGeek has quit IRC18:10
srwilkersafter working with this project for awhile (ive enjoyed it, ive learned a lot) and chewing on what ive seen and whats been said, it really comes down to this: i see value in building these packages the way we're doing now kfox1111, and i get why you've been pushing this and why you're devoting your time here. its been well received. lets consider though: would there not be value in having a deployment project under the18:10
srwilkerskolla umbrella (ala 'kolla-ansible) that focuses on v1k0d3n's point, as in the helm charts should be assumed to be consumable already and uses helm as a native solution for deploying charts (think: kolla-helm)18:10
kfox1111better to heal the political/communication issues when possible.18:11
v1k0d3nthat is not the case with our project to be clear.18:11
srwilkersi see potential value in both use cases here18:11
*** TxGirlGeek has joined #openstack-kolla18:11
srwilkersat that point its not a fork really -- it's a different result under the same umbrella18:11
v1k0d3ni think for us, it was respectful of direction kolla is going to do outside of kolla.18:11
v1k0d3nturning this around into a positive.18:11
kfox1111srwilkers: I think thats the batteries included phylosophy of kolla. we provide a deployment too too, if users want to use it, great. if theyu want to use a vendors project that wraps up the lower kolla-kubernetes layers, great.18:12
jascott1srwilkers helm with a kolla plugin might be another way18:12
*** athomas has quit IRC18:12
kfox1111I'm aguing though, that they shouldn't be implmenting the lower layers themselves though.18:12
portdirectjascott1: I've been thinking quite a lot about that actually18:12
*** Pavo has quit IRC18:12
kfox1111we should be able to work on those together.18:12
*** Bico_Fino_ has quit IRC18:12
*** Bico_Fino has joined #openstack-kolla18:12
portdirectjascott1: it may be a way to allow uses to intall a meta chrat for a service, or via a plugin decomopse it into micro-micro services18:13
*** Pavo has joined #openstack-kolla18:13
jascott1yes i think in general can be 'kolla magic happens in plugin" and user doesnt have to use a different tool kolla-whatever for preprocessing18:14
kfox1111jascott1: I don't think helm plugins can be outside of helm process?18:14
kfox1111which means you have to builda custom helm?18:15
kfox1111I'd kind of like to avoid that.18:15
portdirectbut ultimatly srwilkers, may have a point, which is why the thread duonghq started would be a good place to have this discussion i think?18:15
*** portdirects_lapt has quit IRC18:15
kfox1111rather, encurage helm to gain the features needed to be useful for deploying apps as complex as openstack.18:15
kfox1111portdirect: +118:15
portdirectkfox1111: helm plugins dont require a custom helm build as far as i know -at least not that ive seen18:15
srwilkersportdirect, definitely need to hit the ML with this discussion. just vomiting out some thoughts ive been rolling around18:16
*** TxGirlGeek has quit IRC18:16
srwilkerskfox1111, yes. i think we stand a greater chance of driving that change if we're bringing as many eyes to the table as possible. something along the lines of kolla-helm could help bring those folks back to the table in addition to the work being done on kolla-k8s as a package builder currently18:17
kfox1111to be clear, your aruing for a more visible helm orchestrated deployment subproject to distinguish itself from the lower level helm microservices stuff?18:18
*** lrensing has quit IRC18:19
srwilkersif theres value to it and im making sense to others beyond myself, yeah. im just suggesting its something we may and probably should consider18:21
kfox1111portdirect: ah. ok.I'd be more comfortable wit that.18:21
kfox1111srwilkers: I'm actually +1 myself to that.18:21
kfox1111that follows the same pattern established for kolla-ansible vs kolla containers.18:22
srwilkersyes, precisely18:22
portdirectsrwilkers: i think there maybe value in what your saying, but I'm honestly not sure atm so +1 to thinking about it18:22
srwilkersand i feel thats what has caused the colorful discussions we've seen here the past few weeks18:22
jascott1portdirect plugin capability has landed in helm?18:23
kfox1111srwilkers: +1.18:23
srwilkersinstead of discussing the same thing, i feel we may have been talking past each other based off a misunderstanding. i include myself there18:23
kfox1111srwilkers: I actually arged for that a while back. but so far the general concensus has been fewer repo's are better.18:24
kfox1111I'm hoping if enough of us weigh in on that though, the general concensus will change.18:24
* v1k0d3n on phone, but will scroll back soon18:24
portdirectjascott1: https://github.com/kubernetes/helm/blob/master/docs/plugins.md18:24
kfox1111srwilkers: I've got something I started writing up:18:24
srwilkersin this case, i think having another repo is an added value, because it has the potential to bring others back to the table18:24
portdirectjascott1: played with some examples i found via technosophos, but cant see them offhand18:24
jascott1so its working? I was worried they might have delayed that for 2.2 since that doc was created before hand before 2.1 was split18:25
kfox1111http://paste.openstack.org/show/ZQ9qGc8NCRXNZpdRmtHU/18:25
sbezverkportdirect: helm plugin, at which point it gets called/executed?18:25
portdirectjascott1: https://github.com/technosophos/helm-plugins18:25
kfox1111srwilkers: if we had a kolla-helm for orchestration, then it adds a 3rd layer to that,18:26
portdirectas far as know after rendering, but alanmeadows would be the best person to ask18:26
jascott1wewt! thanks18:26
kfox1111and a #6: "use helm for orchestrating the deployment of openstack.18:26
portdirectsbezverk: was thinking that using one with dry run, could actually spit out micropackages from a chart18:27
jascott1is this not like what we want? https://github.com/technosophos/helm-plugins/tree/master/gpg18:27
jascott1helm kolla install foo18:27
sbezverkportdirect: one thing that really bugs me is limitations I keep hitting with helm templating variables, you try to do something less straight forward, you hit the wall..18:27
*** HyperJohnGraham has joined #openstack-kolla18:28
sbezverkI was hoping plugin could address some of these issues18:28
kfox1111yeah. gotl's not well liked by the golang community I think. :/18:28
kfox1111sbezverk: or, working in the golang community to get them fixed.18:28
* portdirect thinks that there is sometimes an advantage to being a sheep18:28
kfox1111its not an issue that is specific to kolla-kubernetes.18:29
kfox1111golang or helm should fix gotl to be nicer to use.18:29
sbezverkkfox1111: how long should I wait until it gets implemented ;-), my retirement??18:29
jascott1ive been using go for years and nver had to use the tpl18:29
srwilkersdepends sbezverk -- how far off is that? ;)18:29
kfox1111sbezverk: no, but I'm just saying, if you wanted it fixed, you could contribute to those projects?18:29
srwilkerskfox1111, yeah. im actually going to work on hopefully contributing to helm as well so i can keep a foot on both sides and help bridge the gaps or at least point them out18:30
jascott1not insurmountable to get something into sprig or would that not suffice?18:30
sbezverkkfox1111: ok save yourself appraoch ;-)18:30
kfox1111srwilkers: nice. :)18:30
kfox1111sbezverk: sounds like srwilkers will help out there. :)18:31
*** harlowja has joined #openstack-kolla18:31
srwilkerskfox1111, looking at your paste. i agree with what you have, and also agree with adding a third layer18:32
kfox1111srwilkers: cool. :)18:32
jascott1so is 'helm kolla install foo' an abomination?18:33
kfox1111jascott1: it kind of feels to me to be an admission that helm can't do something it should itself?18:33
jascott1i thought we were well int that realization ;)18:34
kfox1111or that something is being crammed into it not intended.18:34
kfox1111hehe.18:34
portdirectbut thats what a plugin is for?18:34
kfox1111I guess the distinctioin for me is this.18:34
jascott1but so is 'go install py,reqs, and run a script/make'18:34
portdirectso i really dont think it's an admission but an opportinity to exiend it18:34
portdirector run a docker container...18:34
kfox1111plugins are for adding aditional optional features.18:34
jascott1cleaner UX18:34
portdirectyup18:35
jascott1look at that gpg it just runs sh18:35
kfox1111there shouldn't be anythign in openstack that isn't a normal thing for deploying a major web application.18:35
kfox1111generically.18:35
jascott1helm gpg plugin18:35
kfox1111so if helm can't do it, helm's got a problem with deploying other major web apps too.18:35
kfox1111I think thats a very useful goal for helm to have though, to handle that use case.18:36
jascott1i think helm does have a problem and plugins might be a piece of the solution18:36
kfox1111so a plugin seems hacky.18:36
kfox1111yeah. I can see plugins having a place in the solution.18:36
kfox1111but a plugin for kolla specifically seems  like its working around the lack of major web app functionality in helm.18:37
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092318:37
jascott1think I see what you are saying, my point is i think user would rather run helm kolla install than having to deal with external preprocess system18:37
*** TxGirlGeek has joined #openstack-kolla18:38
kfox1111jascott1: ah. yeah.18:38
kfox1111jascott1: so to combine both, maybe helm majorapp install ... over helm kolla install though.18:39
jascott1yea was thinking it might need ot be more openstack component specific also18:39
v1k0d3nkfox1111:  to this point (i agree) "rather, encurage helm to gain the features needed to be useful for deploying apps as complex as openstack." ....18:39
kfox1111cause I know for sure at least 2 other major web applications that coudl benifit from the same thing.18:39
kfox1111I'm sure there are others.18:40
v1k0d3nthis is what i brought up on the call with my statement "find the gaps".18:40
v1k0d3nso we're in agreement.18:40
kfox1111v1k0d3n: +118:40
v1k0d3nand kfox1111 "to be clear, your aruing for a more visible helm orchestrated deployment subproject to distinguish itself from the lower level helm microservices stuff?" ....18:41
v1k0d3nthere are two points in there. "more visible helm orchestrated deployment subproject"....18:41
v1k0d3nfor that, i would say that there is a notion from other projects and this was our thought, that helm would be really all that is needed.18:41
portdirectI tend to agree with v1k0d3n here18:42
kfox1111v1k0d3n: yeah. but that's where the contentious part is. the whole community hasn't come to that same conlusion.18:42
v1k0d3nand through trial and error and talking with other teams...i think we're really close...and still keeping the value of having user-defined "values.yaml". << that's the whole pint anyway.18:42
v1k0d3nand this point18:42
kfox1111v1k0d3n: let me reprase that last tatement I made just a bit to be clear.18:43
v1k0d3n"to distinguish itself from the lower level helm microservices stuff?" your focus on microservices is a bit primary than the other deployments that i am aware of, which is fine. i'm just saying that this is open to debate (which i'd rather not debate here...please).18:43
*** fguillot has joined #openstack-kolla18:43
kfox1111v1k0d3n: the community is not reached a consensus around that we should only use helm for that. there are other aproaches some folks want to support.18:44
kfox1111v1k0d3n: in which case, I think having a subproject leaves room for other subprojects following the different aporach18:44
kfox1111the same way kolla-ansible getting its own repo encuraged kolla-kubernetes to become a thing.18:44
*** gfidente has quit IRC18:44
kfox1111v1k0d3n: sure.18:44
srwilkerskolla-helm gives those looking for a helm specific approach can offer them exactly that18:45
v1k0d3noh and to srwilkers part about "colorful discussions"...yes they have been colorful unfortunately. i think we need to start over, rewind, etc on that. my tone is much more soft partially because i don't think we have to agree on everything. color is better in this world anyway :)18:45
portdirectwe may benifit from some additonal tooling (eg plugin) but i really think that helm should be the entrypoint for kolla deplyment and management. if the only way to ackhive that is through a sub or parallel project then maybe we should consider it?18:45
v1k0d3nand srwilkers yes...unfortunately talking past one another. this is bad for the community. let's focus on the areas we agree from now on? :)18:45
kfox1111portdirect: I agree at the very most root. but there is a wildy different potential aporach that may require a seperate subproject. that of operators.18:46
srwilkersv1k0d3n, i agree18:46
kfox1111k.18:47
v1k0d3nand portdirect plugins...yes...that's great! that's one reason why we think helm may be able to do this alone, but that's understandably debatable depending on a users choice/path forward.18:47
v1k0d3nsrwilkers: and of course, i'm all for having smaller, more laser focused repos. i've alluded to this, but not come out and stated it. others have expressed this as well (generally speaking of any repo).18:48
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron db stuff and add svc.  https://review.openstack.org/41033618:49
*** unicell has quit IRC18:51
v1k0d3n kfox1111: yeah. gotl's not well liked by the golang community I think. :/ / true...this is why coreos is holding on to kpm. they prefer jasnette. they even use it with their bare metal tool (which i freaking love)!18:51
*** harlowja has quit IRC18:52
*** unicell has joined #openstack-kolla18:53
kfox1111is jasnette a go thing?18:53
jascott1probably?18:54
jascott1not familiar18:54
kfox1111if its go, then tehy should be able to plug it into helm directly.18:54
kfox1111there is a template engine flag in the Chart.18:54
kfox1111the currently dont' suport anything but gotl but that coudl change. :)18:54
v1k0d3nsrwilkers: love that there's cross-polination of kolla and helm. :) (to your point)18:54
v1k0d3nso just a suggestion?18:54
kfox1111would love to see it. :)18:55
v1k0d3nsee what the devs of helm intended. could be opportunity in what's already there. nothing worse to a dev than to have your tool worked around in strange ways, but if a user can bring it to new heights by exhausting what it can already do...there's nothing more rewarding than that! :)18:56
v1k0d3njascott1: to "helm kolla"...what about just a helm project for anyone...not just kolla users?18:56
kfox1111yeah.18:56
v1k0d3nthe idea was to stretch beyond helm18:56
portdirectkfox1111: any chance you could give me some more feedback here, when yo get a minute? https://review.openstack.org/#/c/410564/18:57
jascott1why for anyone?18:57
kfox1111v1k0d3n: isn't that hust helm itself?18:57
kfox1111just18:57
kfox1111portdirect: sure18:57
v1k0d3njust a thought. either way...your call. there's just a lot of kolla-* projects. perhaps having a fresh perspective that happens to work wtih kolla would be really good for the community?18:57
kfox1111portdirect: already did. :)18:57
* v1k0d3n sorry still working now...LOT of reading and catching up here...18:57
portdirectv1k0d3n: lol needed to referesh :)18:58
kfox1111v1k0d3n: I'd be for a kolla-kubernetes subproject for helm based deployment using kolla-kubernetes microservice packages.18:58
portdirectkfox1111: but its in _common_api_apython_deployment?18:58
kfox1111I'd be against a complete alternative to kolla-kubernetes, duplicating effort and spliting the community.18:59
portdirectkfox1111: so that would be a contradction i think? unless i'm missing waht you are saying?18:59
portdirectkfox1111: also is that flag documented anywhere I coundt find it?18:59
v1k0d3njascott1: omg...yes...that is better in my little opinion. i like that better. "my point is i think user would rather run helm kolla install than having to deal with external preprocess system"18:59
kfox1111portdirect: the _common_api_python_deployment has the annoitation leting end users know its safe to do a zero tdowntime upgrade.18:59
v1k0d3nbut again, we've found that helm has what we need. so has SAP.19:00
kfox1111portdirect: the apache one currently has the annotation and isn't safe.19:00
v1k0d3njust...saying19:00
* v1k0d3n and ducks19:00
portdirectbut it has a graceful-stop?19:00
portdirectiam i miussing somthing?19:00
jascott1haha19:00
kfox1111portdirect: without an apachectl stop in apache, the container can be just shot and existing connections severed.19:00
portdirectplase look at line 32?19:01
kfox1111portdirect: which will manifest in a downtime in amn upgrade.19:01
kfox1111k.19:01
kfox1111portdirect: wow. sorry. I'm just blind. I could have swarn I looked for that. :/19:01
portdirectnp :)19:02
kfox1111portdirect: then no objection and its workflowable. :)19:02
portdirectwhoop!19:02
v1k0d3nkfox1111: v1k0d3n: yeah. but that's where the contentious part is. the whole community hasn't come to that same conlusion. --- i agree...but there are a few projects that find agreement. maybe we could see what they actually agree on. this was the point of the Helm+Openstack SIG...so everyone has an equal seat at the table and help each other.19:02
jascott1v1k0d3n there is a makefile in aic tho right ? ;)19:03
portdirectjascott1: yeah but it makes v1k0d3n cry19:03
v1k0d3nkfox1111: the same way kolla-ansible getting its own repo encuraged kolla-kubernetes to become a thing. ---- that still makes kolla the single source of truth when there are others who only want "openstack" to be the source of truth.19:03
v1k0d3ni can explain later in a second....19:03
* v1k0d3n *sigh* still catching up....19:04
kfox1111jascott1: yeah. aic-helm and kolla-kubernetes aporaches are actually closer then first look.19:04
kfox1111jascott1: just that they have started top down, and we have bottom up.19:04
kfox1111jascott1: so some things are more complete on one or the other.19:05
portdirectthough that depends on the direction, they stared with a clean sheet of paper, so the comarison is a bit more east-west i think19:05
*** eaguilar_ has joined #openstack-kolla19:05
portdirectI hate to say it but I much prefer the keystone over there to the one i just did :( though thats mainly down to config at the moment.19:06
portdirectand somthing that we can hopfull recify at the hight levels19:07
v1k0d3nkfox1111: the currently dont' suport anything but gotl but that coudl change. :) ---- that leaves it open for others to build on. just like CNI or runtime interface. that's how i understood that anyway :-/19:07
v1k0d3njascott1: there is...but do you know what the make file is doing?19:08
kfox1111v1k0d3n: for the agreement comment, if you can convince the rest your way is the best way, great. then we can just to dthe one way. I'm staying out of it though. :)19:08
*** eaguilar has quit IRC19:08
sbezverkportdirect: could you be more specific in which sense or why you prefer keystone implementation?19:08
v1k0d3nkfox1111: man, we gotta get off this train dude, please.19:08
v1k0d3n"yours"...19:08
kfox1111v1k0d3n: kolla is openstack. I don't understand.19:08
v1k0d3nit was an experiment man.19:08
v1k0d3nwe're collaborating with helm and other folks to experience.19:09
v1k0d3ni'd like to take the tone down a bit.19:09
v1k0d3ni think we gotta start over.19:09
kfox1111v1k0d3n: yeah. I agree on helm building. seems like a good thing in the long run not to be limited to just gotl.19:09
*** eaguilar has joined #openstack-kolla19:09
portdirectsbezverk: yeah - just that if i need to change somthing its easier to work with a fat manifest, and have the config together.19:09
*** eaguilar_ has quit IRC19:09
kfox1111v1k0d3n: which train?19:09
portdirectsbezverk: https://github.com/att-comdev/aic-helm/tree/master/keystone/templates/etc & https://github.com/att-comdev/aic-helm/blob/master/keystone/templates/deployment.yaml are things I can hack on much easier at the moment19:10
kfox1111v1k0d3n: ok. not trying to take a bad tone. sorry if its being percieved that way.19:10
v1k0d3nwell, i don't know, but i get a sense there's still some frustration.19:10
sbezverkportdirect: if you have link handy, could you pass it to me19:10
kfox1111jsut trying to keep up with a quick pace of irc. :/19:10
sbezverkportdirect: :-)19:10
portdirect:)19:10
v1k0d3nyeah, that's why i ran through the whole list to get context in order.19:10
openstackgerritMerged openstack/kolla-kubernetes: Helm Keystone API  https://review.openstack.org/41056419:11
v1k0d3ni get it though. so my bad if i misunderstood.19:11
kfox1111v1k0d3n: yeah. but there is lots of other conversaionts happening too. so its hard to keep up with it all.19:11
v1k0d3nword19:11
*** Bico_Fino has quit IRC19:11
*** fragatina has quit IRC19:11
kfox1111it may b e one of those things better left up to email. so anttention is not split mid topic.19:11
v1k0d3nso i have a question. just generally speaking here to kfox1111 cores and group?19:12
kfox1111v1k0d3n: sure.19:12
v1k0d3noh and btw... jascott1 the make file just sets up users secrets that can be used for the project. that's about it.19:12
v1k0d3nbecause those are required for things like ceph.19:12
v1k0d3nbase64 etc19:12
v1k0d3nso what if helm could deploy and upgrade19:13
portdirectv1k0d3n: chatting to upstream about that at the start of next week :)19:13
portdirectv1k0d3n: see if we can make it easier re pod CIDR19:13
*** Bico_Fino has joined #openstack-kolla19:13
v1k0d3noh yeah portdirect great!19:13
v1k0d3nso kfox1111 sorry (distracted)19:14
kfox1111v1k0d3n: it wil ltake a while to prove helm can deply/upgrade/ and handle day2 operators. probably 8 months or more to really get operators comfortable with it.19:14
kfox1111for production.19:14
v1k0d3nwhat if helm deployed and upgraded like advertised, you could deploy microservices, openstack is the only source of truth (meaning no kolla ties, no ansible required, etc), and users bring their own helm install proceedures and kubernetes installation to the table.19:15
v1k0d3nwhat are your thoughts on that?19:15
v1k0d3nno preprocessing, just what if helm could do it all19:15
v1k0d3nout of the box19:15
kfox1111so, whats the source of truth for the microservices though?19:15
kfox1111who provides them?19:15
kfox1111kolla is today.19:15
v1k0d3nopenstack upstream.19:15
portdirectas in nova, gance, etc?19:16
kfox1111you mean, get every openstack project to provide the pieces themselves?19:16
v1k0d3ni mean, debatably....that's what's common with openstack people...all of them want openstack.19:16
kfox1111I think thats somethign akin to saying, every open source project should rpovide an rpm specfile.19:16
v1k0d3nyup19:16
kfox1111ideally, yes. they should19:16
kfox1111but it never has worked in the past. :/19:16
v1k0d3n^^ we agree19:16
v1k0d3n^^ also agree19:16
v1k0d3nbut kolla does this...19:17
v1k0d3nwith a container made for kolla19:17
v1k0d3nso it's a kolla source is what i'm saying.19:17
v1k0d3nbut what if ansible and everything else was gone.19:17
v1k0d3nand helm did what it claims to do.19:17
kfox1111its the distinction between the software developer, and the package maintainer.19:17
kfox1111some people play both roles, some just one.19:17
kfox1111but usually most just play one.19:18
kfox1111v1k0d3n: I think it would be an interesting world your proposing. I don't see it happening anytime soon though. :/19:18
kfox1111if you want to work on making it happen, great. :)19:18
v1k0d3nso you're saying that images can't be created wtihout kolla19:18
*** Bico_Fino has quit IRC19:18
v1k0d3nthis is what i'm getting at.19:19
v1k0d3ni think we're off a bit19:19
v1k0d3nwell, to be clear OSAD is starting work on some of this in a way.19:19
portdirectwhy not try? adding a dockerfile to the root of each projects repo? so you could run docker build https://github.com/openstack/foo ?19:19
v1k0d3nas in...just give me an artifact. that's it.19:19
kfox1111images can be created without kolla, but kolla has made certain api choises with thier containers to further the goals setout by kolla.19:20
kfox1111unopionated deployment.19:20
*** portdirect is now known as portdirect_away19:21
*** HyperJohnGraham has quit IRC19:21
kfox1111so, for example, kolla provides a mariadb container as a batteries included thing.19:22
kfox1111you can launch mariadb without containers, or with different containers and point kolla at it and it will still work.19:22
kfox1111same with ceph. rabbit, etc.19:23
v1k0d3ni mean that's a general cloud native approach anyway.19:24
*** portdirects_lapt has joined #openstack-kolla19:24
kfox1111yeah19:25
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron db stuff and add svc.  https://review.openstack.org/41033619:27
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092319:29
v1k0d3nanyway, good talk. not sure covered a lot, but i like seeing the different project approaches.19:29
jascott1v1k0d3n true enough about the makefile but I guess Im trying to figure out what everyone thinks about using helm/helm plugins to wrap everything. is that a valuable prop?19:29
kfox1111v1k0d3n: +1 :)19:29
kfox1111be back in a few.19:31
v1k0d3njascott1: our point has been to go all in on helm, bridge gaps where their core developers say there are gaps, use it as the source of truth along with openstack.19:31
jascott1maybe the kolla plugin has hooks instead of being so implementation specific, sub plugins. oh is that what you meant by 'for everyone'?19:31
v1k0d3nby not having anything else (enter opinion, and controversy i'm sorry) helm is stronger, we have a simpler approach, can use helm pipelines for development of the overal project end to end, and remain very close to openstack upstream.19:32
v1k0d3nwhen i say "we" i really don't mean "we" as where i work or project specific.19:32
jascott1sure19:33
v1k0d3ni am not comparing, i want to make that clear. i'm done comparing :)19:33
v1k0d3nthat's not getting us anywhere because both have value in their own rights.19:33
jascott1agreed. i think kolla-k8s is trying to use helm as much as possible and still achieve its goals tho. are plugins the place we use to bridge the gaps?19:33
*** portdirect_away is now known as portdirect19:34
*** portdirects_lapt has quit IRC19:34
jascott1for instance, what if kolla plugin had generic pre helm init hook that could run whatever19:35
jascott1before pre hook in helm19:36
jascott1cause that helm hook doesnt use shell and there is no other way to hook in afaik19:36
jascott1also at the time of that helm has already rendered templates19:37
v1k0d3nbridge the gaps with what? - jascott119:37
jascott1the UX gaps19:39
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for glance api and glance registry pods  https://review.openstack.org/41048119:39
v1k0d3nlet me think of a different way to put this...19:39
v1k0d3ni want a brick19:39
v1k0d3nnot a brick wall19:39
jascott1helm install openstack is a lie, everuone has a script19:39
v1k0d3ni want to build my own wall.19:39
v1k0d3nso atomic level is where we're focused.19:39
*** jmccarthy has quit IRC19:39
*** jmccarthy has joined #openstack-kolla19:40
v1k0d3nbring your own k8s on whatever system, install helm your own way, we NEED to set up persistent storage (i'd like this to be bring your own at some point too), and bring your own values, or have us create them for your greenfield.19:41
jascott1sure but plugin is very high level abstraction, in the case of current kolla-k8s approach, it could be used to call prebuild and for aic it could be used to call make19:41
v1k0d3nso in this way, it's very simple. i can choose to use jenkins to deploy.19:41
v1k0d3ni can use ansible playbooks or any other CAPS.19:41
jascott1sure19:41
v1k0d3ni don't want a bridge, i just want some boards.19:42
v1k0d3nthis is why the tone is changed on my end.19:42
v1k0d3nand perfectly willing to do whatever it takes to align.19:42
v1k0d3nwithout changing kolla, and without changing the building block approach too.19:42
jascott1cool sounds great19:42
kfox1111back.19:44
jascott1i think we all want "bricks" TM C 2016 flandev enterprises LLC19:44
jascott1sorry that was a simpsons reference, they just come out sometimes19:45
kfox1111cool. :)19:46
kfox1111+1 to bricks. :)19:46
kfox1111I was actually considering proposing renameing microservices "bricks" or "block" to avoid some connotation around microservices.19:46
* portdirect thinks jascott1 has bought up all cloud native lego ip...19:47
jascott1>:)19:47
kfox1111hehe. I gave a presentation on k8s that used a lot of lego pictures. :)19:47
jascott1<excellent>19:47
kfox1111everyone see the lego car?19:47
kfox1111I think its a great analogy for kolla-kubernetes.19:48
v1k0d3nkfox1111: why renaming?19:48
*** hyakuhei has joined #openstack-kolla19:48
kfox1111v1k0d3n: just to avoid confusion. if its clear enough, we can keep it.19:48
v1k0d3ni think many people understand microservices. or maybe i'm just hanging out with the right people.19:49
v1k0d3ni think we were talking about different type of bricks19:49
v1k0d3nwasn't talking about microservices.19:50
kfox1111ah. ok.19:50
v1k0d3ngtg19:50
v1k0d3ntake care and have a good holiday break guys.19:50
jascott1you too v1k0d3n! ive got another week before that happens :(19:51
v1k0d3nlol i have 14 days that i can't use because i just have too much work.19:51
v1k0d3noh well.19:51
kfox1111v1k0d3n: you too dude! :)19:52
jascott1oh man hope you get that pto19:52
kfox1111yeah. they are forcing me to take mine.19:52
jascott1reminds them how valuable you are :)19:52
kfox1111jascott1: +1 :)19:53
* v1k0d3n sings all we are is dust in the wind19:53
srwilkersv1k0d3n, youre my boy blue19:53
*** msimonin has joined #openstack-kolla19:53
jascott1LOL beat me to it!19:53
v1k0d3nLOL19:53
jascott1additional generic Old School reference here19:53
*** eaguilar_ has joined #openstack-kolla19:54
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953819:54
*** eaguilar has quit IRC19:54
jascott1for those un educated https://www.youtube.com/watch?v=Vnywlzr7Y1o19:54
v1k0d3nit's what we do...19:55
*** lrensing has joined #openstack-kolla19:56
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092319:57
*** gomarivera has joined #openstack-kolla20:02
*** hyakuhei has quit IRC20:04
*** hyakuhei has joined #openstack-kolla20:04
*** hyakuhei has quit IRC20:04
*** hyakuhei has joined #openstack-kolla20:04
*** adrian_otto has quit IRC20:05
*** gomarivera has quit IRC20:07
*** Pavo has quit IRC20:12
*** Pavo has joined #openstack-kolla20:13
*** jemcevoy has joined #openstack-kolla20:14
*** portdirects_lapt has joined #openstack-kolla20:20
*** afranc has quit IRC20:23
*** sayantan_ has quit IRC20:24
*** sayantan_ has joined #openstack-kolla20:25
*** sdake has quit IRC20:27
*** ayoung has joined #openstack-kolla20:27
*** afranc has joined #openstack-kolla20:27
*** lamt has quit IRC20:29
*** sdake has joined #openstack-kolla20:29
srwilkershey sdake20:31
*** portdirects_lapt has quit IRC20:31
kfox1111sbezverk: still here?20:34
kfox1111https://review.openstack.org/#/c/410336/ is finally ready again.20:34
*** sdake has quit IRC20:36
*** kbyrne has quit IRC20:36
*** sayantan_ has quit IRC20:41
*** sayantan_ has joined #openstack-kolla20:41
*** TxGirlGeek has quit IRC20:41
*** eaguilar_ has quit IRC20:43
*** TxGirlGeek has joined #openstack-kolla20:43
*** TxGirlGeek has quit IRC20:46
*** TxGirlGeek has joined #openstack-kolla20:46
*** eaguilar has joined #openstack-kolla20:47
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149320:53
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149320:54
*** eaguilar has quit IRC20:55
*** TxGirlGeek has quit IRC20:56
*** TxGirlGeek has joined #openstack-kolla20:56
*** TxGirlGeek has quit IRC21:02
*** TxGirlGeek has joined #openstack-kolla21:02
*** JRobinson__ has joined #openstack-kolla21:06
sbezverkkfox1111: yes I am back21:10
*** adrian_otto has joined #openstack-kolla21:11
*** TxGirlGeek has quit IRC21:11
*** TxGirlGeek has joined #openstack-kolla21:12
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953821:12
srwilkershey sbezverk :)21:12
*** HyperJohnGraham has joined #openstack-kolla21:13
*** TxGirlGeek has quit IRC21:14
sbezverksrwilkers: did I miss anything exciting? some starwars episode 24?21:14
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149321:16
*** eaguilar has joined #openstack-kolla21:17
openstackgerritMerged openstack/kolla-kubernetes: Helmize neutron db stuff and add svc.  https://review.openstack.org/41033621:17
kfox1111sbezverk: heh. lot of conversations.21:17
kfox1111sbezverk: thanks.21:17
proni fo have a question21:20
*** HyperJohnGraham has quit IRC21:20
pron kolla_external_vip_interface21:20
*** hawi has joined #openstack-kolla21:20
pronif i understand correctly it has to be same as neutron network? or how does this work?21:21
kfox1111its where the openstack services show up.21:22
srwilkerssbezverk, nothing that i know of :) i still need to see rogue one21:22
kfox1111doesn't have to be on the same subnet as the public network.21:22
pronkfox1111: thats something like "admin network" ?21:24
pronits network from wich i will access horison right?21:25
kfox1111portdirect: its usually expected that its reachable from the vm's public network somewow.21:25
kfox1111somehow21:25
kfox1111either by being the same subnet,21:26
*** HyperJohnGraham has joined #openstack-kolla21:26
kfox1111or having some router infrastructure between.21:26
Pavokolla_external_vip_interface is for public API and public horizon access21:26
kfox1111sorry. ment for pron, not portdirect.21:26
portdirectyou called ? :D21:27
Pavokolla_internal_vip_interface is for admin API and admin horizon access21:27
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for cinder keystone endpoints  https://review.openstack.org/41092321:28
*** portdirects_lapt has joined #openstack-kolla21:30
pronPavo: do i need ip for tunnel interface?21:31
hawilets as this way - which ones of them i need to make routable, which ones dont have to have gw and go outside their network?21:31
*** TxGirlGeek has joined #openstack-kolla21:32
*** l4yerffeJ__ has joined #openstack-kolla21:32
Pavono only interface that needs an IP is the network_interface: and if you want to seperate admin traffic and public traffic then the kolla_external_vip_interface:21:33
pronstorage and cluster doesnt need ip?21:33
Pavothat should be using network_interface if thats the API interface21:34
pronthose are separate interfaces for storage21:34
Pavogot a net layout of how you are deploying on your network pron?21:35
*** Jeffrey4l_ has quit IRC21:35
*** l4yerffeJ_ has quit IRC21:35
Pavopron this is my net layout21:35
Pavohttps://www.gliffy.com/go/publish/1130918721:35
*** fguillot has quit IRC21:37
*** HyperJohnGraham has quit IRC21:37
pronPavo: il try to write something down now21:38
Pavoyeah would help to help you21:39
Pavotook a few days to figure out how the networking worked also pron so I know what you are going threw21:40
*** portdirects_lapt has quit IRC21:40
*** jgriffith is now known as jgriffith_AutoAw21:40
*** sdake has joined #openstack-kolla21:41
pronPavo: http://paste.openstack.org/show/592555/21:42
Pavooh so you are using sub-interfaces21:43
pronyes i want lacp21:43
pronwell actualy atm i do have only bond021:43
Pavoneutron_interface and network_interface can not be on same interface21:43
pronamm21:43
pronso how can i do that21:44
Pavoneutron will use that interface for ovs bridge mapping21:44
Pavopron this is probably the way I would do it21:46
Pavohttp://paste.openstack.org/show/592557/21:46
*** fragatina has joined #openstack-kolla21:46
pronPavo: do i realy need network_interface if i have all the sub things defined?21:47
Pavooh yeah forgot about that hang on21:47
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953821:48
Pavolike this pron http://paste.openstack.org/show/592558/21:48
*** Jeffrey4l_ has joined #openstack-kolla21:48
pronPavo: so i cant have any tagged vlans on network interface?21:49
pronemm neutron*21:49
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149321:49
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953821:50
*** sdake has quit IRC21:51
jemcevoykolla-build on CentOS 7 is running incredibly slow with today's release of 7.3... yum is having lots of issues reaching the repos with a binary build...  Is there a way that I can fix this?21:51
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953821:52
portdirectjemcevoy: thats probably just the centos servers getting hammered..21:52
*** jgriffith_AutoAw is now known as jgriffith21:52
Pavopron not from what I have seen21:52
portdirectjemcevoy: you may be able to edit the /etc/yum.repos.d to point to a less loaded mirror21:52
openstackgerritSteve Wilkerson proposed openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953821:53
Pavopron if you assign network_interface as a sub-interface it would work because the sub-interface would have an IP on it21:53
*** HyperJohnGraham has joined #openstack-kolla21:53
*** adrian_otto1 has joined #openstack-kolla21:54
*** adrian_otto1 has quit IRC21:54
*** adrian_otto has quit IRC21:55
*** eaguilar has quit IRC21:55
jemcevoyportdirect: does the build use my yum.repos.d files?   Is so I can do a cobbler repo-update and just take the hit ones then use the local repo  if the docker build uses the yum.repos.do on my build VM...21:56
Pavojemcevoy have you tried building using a custom repo option in your /etc/kolla/kolla-build.conf file?21:56
Pavojemcevoy try adding rpm_setup_config = address to local cobbler repo in your /etc/kolla/kolla-build.conf file21:57
jemcevoyI have not and the tool in the doc that generates the /etc/kolla/kolla-build.conf was not there... so I copied the one over from /usr/share/kolla21:57
jemcevoyI will try that...21:57
PavoI create my own /etc/kolla/kolla-build.conf file21:57
*** gomarivera has joined #openstack-kolla21:58
*** srwilkers has quit IRC21:58
Pavobut yes there are a ton of mirror issue with the normal build21:58
PavoI agree21:58
*** adrian_otto has joined #openstack-kolla21:58
jemcevoyI have three repos mirrored locally... centos7, centos7-updates and epel21:58
Pavojemcevoy http://docs.openstack.org/developer/kolla/image-building.html21:59
PavoCustom Repo section21:59
jemcevoyPavo: can I confiure three21:59
Pavoyes21:59
jemcevoyCool  Thanks21:59
Pavoseperate with a ,22:00
Pavojemcevoy are you able to use cobbler on UEFI devices?22:01
Pavobecause I was never able to get that working with cobbler22:01
jemcevoyPavo: yes... there was a bug in the dhcpd.conf template... The efi boot instruction gets figured out the overwritten later...22:06
Pavoyou mind helping me out someday with it?22:06
*** HyperJohnGraham has quit IRC22:07
openstackgerritsayantani proposed openstack/kolla: Update Quick Start Guide for singlenode deployment  https://review.openstack.org/40499322:08
jemcevoyThis sets the boot file which get overwritten later...  } else if option pxe-system-type = 00:07 {22:09
jemcevoy                  filename "grub/grub-x86_64.efi";22:09
Pavook cool thanks jemcevoy22:09
pronon what interface kolla_internal_vip_address this is goin?22:09
pronthats api interface?22:10
Pavopron that your management network interface22:10
*** ayoung has quit IRC22:10
jemcevoyPavo: it gets set back to pxelinux.0 later on... just get rid of the reset.22:10
pronPavo: thats where i access horison?22:10
Pavowhatever interface you want only admin access22:10
Pavoyes22:10
pronokay thx22:11
pron=)22:11
*** Pavo has quit IRC22:12
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149322:13
*** Pavo has joined #openstack-kolla22:13
openstackgerritsayantani proposed openstack/kolla: Divide Quick Start Guide into 2 docs  https://review.openstack.org/40499322:13
jemcevoyPavo: When I try running "tox -e genconfig" I get this for a response.  "ERROR: toxini file 'tox.ini' not found" The tox.ini file does not get installed when following the end user instructions for a binary install22:16
openstackgerritsayantani proposed openstack/kolla: Divide Quick Start Guide into 2 docs  https://review.openstack.org/40499322:16
kfox1111srwilker-: is there anything left in https://review.openstack.org/#/c/409349/ that isn't in other reviews?22:16
kfox1111should we abandon it?22:17
Pavodid you install kolla using pip or git from github22:17
jemcevoypip22:17
pronso atm kolla cant setup ceph as swift backend?22:18
Pavothen you shouldn't need tox22:18
Pavojemcevoy run kolla-ansible genconfig instead22:19
*** Serlex has left #openstack-kolla22:21
*** jheroux has quit IRC22:21
openstackgerritDavid Moreau Simard proposed openstack/kolla-ansible: Add PyYAML to requirements.txt, dependency of genpwd  https://review.openstack.org/41152022:22
dmsimard^ this is an easy bugfix, please review :)22:23
openstackgerritJustin Scott proposed openstack/kolla-kubernetes: WIP Helmize Heat-engine  https://review.openstack.org/41004822:23
*** TxGirlGeek has quit IRC22:23
*** sayantan_ has quit IRC22:23
*** sdake has joined #openstack-kolla22:24
*** JRobinson__ is now known as JRobinson__afk22:26
*** msimonin has quit IRC22:29
*** msimonin has joined #openstack-kolla22:29
*** lrensing has quit IRC22:34
*** rhallisey has quit IRC22:35
*** jtriley has quit IRC22:36
*** goldyfruit has quit IRC22:39
*** saneax-_-|AFK is now known as saneax22:40
*** sdake_ has joined #openstack-kolla22:43
*** sdake has quit IRC22:45
dmsimardUgh, natively including a specific kolla-ansible role is a lot of work22:46
*** jgriffith is now known as jgriffith_AutoAw22:47
*** jgriffith_AutoAw is now known as jgriffith22:47
*** saneax is now known as saneax-_-|AFK22:48
*** JRobinson__afk is now known as JRobinson__22:48
openstackgerritMerged openstack/kolla-kubernetes: Helm charts for creating and managing the Glance database  https://review.openstack.org/40953822:49
*** msimonin has quit IRC22:50
portdirectjemcevoy: are you still haveing trouble with installing kolla?22:52
jemcevoyYes... Pavo told me about "kolla-ansible genconfig"  instead of tox-e genconfig... That got me further but I failed when it got to ceph-mon and ceph-osd22:54
Pavoin build process jemcevoy?22:55
jemcevoyportdirect: this is the errorfailed: [localhost] (item=ceph-mon) => {"failed": true, "item": "ceph-mon", "msg": "AnsibleUndefinedVariable: 'dict object' has no attribute u'ansible_eth2'"}22:55
*** huzhengchuan has joined #openstack-kolla22:55
jemcevoyin kolla-ansible genconfig22:55
portdirectjemcevoy: sorry i might have missed somthing with the scrollback, are you trying to build kolla images (i can help possibly)? or deply with ansible (i cant)?22:56
portdirect*deploy22:56
jemcevoyI originally built with the gened  config... So I am doing the build again...22:57
jemcevoybut now stuck on buildconfig with the eth2 issue22:58
portdirectjemcevoy: sorry I'm confused are you trying to build docker images, or build the config for depolyment?22:58
Pavoyeah I am confused also22:59
Pavokolla-ansible genconfig has nothing to do with building images22:59
Pavokolla-build is what you use to build images23:00
jemcevoyOh OK...23:00
sbezverkkfox1111: ping23:00
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149323:01
jemcevoySo I can run the kolla-build before I the genconfig...23:01
jemcevoysince the update on  my local repos completed I will restart the "kolla-build --registry kolla4echo.scm.penguincomputing.com:4000 --push --threads=1" command23:03
*** saneax-_-|AFK is now known as saneax23:03
Pavojemcevoy unless you want to customize the container configs there is really no reason that you need to even run kolla-ansible genconfig23:03
portdirectyeah - perhaps this docker container will help? https://github.com/portdirect/dockerfiles/tree/master/kolla-builder23:04
*** dave-mccowan has quit IRC23:04
jemcevoyI will need to customize nova for pci-passthough of the nVidia Grid cards23:04
Pavojemcevoy you can do that by making a /etc/kolla/config/nova directory and then add any custom settings to the nova.conf and put it that directory23:06
Pavokolla-ansible deploy will merge your custom settings to the default nova.conf during deployment23:07
Pavoand you can even use that same directory for other custom settings and add them to an environment that has already been deployed by using kolla-ansible reconfigure23:07
*** sdake_ has quit IRC23:08
openstackgerritJustin Scott proposed openstack/kolla-kubernetes: WIP Helmize Heat-engine  https://review.openstack.org/41004823:10
*** huzhengchuan has quit IRC23:12
*** sdake has joined #openstack-kolla23:15
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149323:25
*** ayoung has joined #openstack-kolla23:29
*** gomarivera has quit IRC23:32
klindgrenhola - trying to get kolla-ansible to just run a single tag as is documented, running with: sible-playbook  -i inventory site.yml --tags common,glance23:33
klindgrenbut I get an error at TASK common: include of 'action' is undefined23:34
klindgrenTASK [common : include] ********************************************************23:34
klindgrenfatal: [kolla-glance.cloud.dev1.gdg]: FAILED! => {"failed": true, "msg": "'action' is undefined"}23:34
klindgrenthis seems like its no longer possible to use tags to deploy just a single service?23:35
*** sdake_ has joined #openstack-kolla23:40
*** sdake has quit IRC23:43
openstackgerritJoshua Harlow proposed openstack/kolla: Allow for image additions archives (as well as plugins)  https://review.openstack.org/41153423:48
*** wwriverrat has quit IRC23:52
*** srwilkers has joined #openstack-kolla23:54
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Helmize neutron dhcp/metadata agents.  https://review.openstack.org/41149323:55
*** dave-mccowan has joined #openstack-kolla23:55
*** adrian_otto has quit IRC23:57
*** harlowja has joined #openstack-kolla23:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!