Wednesday, 2016-11-23

awiddersheimor haproxy changes00:00
inc0scaling up controllers nodes *might* work after you deploy -> reconfigure00:00
inc0never tested it00:00
awiddersheimok00:00
jascott1sdake: just playing soundboard00:00
sdakejascott1 right, still recommended reading :)00:00
inc03 controllers (minimum for HA) can handle 100s of compute nodes00:00
inc0so well...00:00
jascott1will read again sir! and pay attention this time even00:00
sdakeoh if you read it already00:01
sdakenm then :)00:01
inc0also scaling up rabbitmqs doens't actually make it faster00:01
inc0I should read it myself at some point..00:01
*** Bico_Fino has quit IRC00:01
sdakeits short and sweet00:01
inc0I know, kidding00:01
awiddersheiminc0: great thanks for the help00:03
*** Pavo has quit IRC00:03
inc0np, ping me if you need anything else00:03
*** Pavo has joined #openstack-kolla00:03
inc0...for now, I'm off00:03
sdakewell that was fun :)00:03
inc0have a good night ladies and gents00:03
sdakelater inc000:03
*** inc0 has quit IRC00:03
sdakev1k0d3n [16:43:23]  <v1k0d3n>sdake: The request you have made requires authentication. (HTTP 401) (Request-ID: req-5742fcb9-447d-4fa1-9556-82372433b7bc)00:05
sdakev1k0d3n this still a problem?00:06
sdakeor did you sort it out00:06
v1k0d3nno, that is part of the problem.00:08
v1k0d3ni have correct auth.00:08
sdakecool00:08
sdakelets debug that00:08
sdakefirst ,what type of host are you on?00:08
sdakei've got about 5-10 mins :)00:08
sdakerun that same commnd with --debug00:09
v1k0d3ndont worry about it. i can get this later. today is one of those days.00:09
sdakeit should spit out a bunch of crap and at the end it will tell you what went wrong00:09
sdakev1k0d3n today is one of thos edays every day of my life it seems :)00:11
v1k0d3nthe error debug doesnt really give anymore content00:11
sdakeyour looking for something with TLS or tls in it00:12
sdakev1k0d3n reading the googles00:12
sdakei may ahve been wrong00:12
sdakethe correct cert command may be OS_CA_CERT00:12
sdakerather environment00:13
sdakev1k0d3n if tls isnt' displayed inthe debug output the environment variable is definately wrong00:14
sdakev1k0d3n reference: https://bugs.launchpad.net/python-keystoneclient/+bug/108627800:15
openstackLaunchpad bug 1086278 in python-keystoneclient "OS_CA_CERT is not consistent with help message" [Low,Fix released] - Assigned to Wu Wenxiang (wu-wenxiang)00:15
sdakev1k0d3n if you click through it explains what keystoneclient does at that partuclar bug point in time00:16
sdakeso I am pretty sure its OS_CACERT00:16
sdakebut not 100% positive00:16
sdakewife dinner time bbl00:22
*** hyang_ has joined #openstack-kolla00:24
*** yingjun has joined #openstack-kolla00:27
hyang_Hi all, I’m trying to use Kolla for all-in-one deployment of OpenStack on CentOS 7 in virtualbox. I’m following the QuickStart doc and when it comes to set up “network_interface” variable in globals.yml, I’m confused about which network interface should I use here.00:42
hyang_My vm has 1 NAT interface by default, but using that will get error “Hostname has to resolve to IP address of api_interface” in kolla pre-checks. I also tried to use more network interfaces of NAT, Host-only, Bridged, but still got the same error.00:42
hyang_Could someone point out which network interface type is the correct choice? Appreciate for any help.00:42
*** sdake has quit IRC00:43
*** sdake has joined #openstack-kolla00:45
*** zhubingbing_ has joined #openstack-kolla00:57
*** hyang_ has quit IRC00:59
*** tovin07 has joined #openstack-kolla00:59
*** tovin07 has quit IRC00:59
*** tovin07 has joined #openstack-kolla01:00
*** tovin07 has quit IRC01:01
*** sayantani01 has quit IRC01:01
*** tovin07 has joined #openstack-kolla01:01
*** tovin07 has quit IRC01:02
*** tovin07 has joined #openstack-kolla01:02
*** f13o has joined #openstack-kolla01:03
*** sdake has quit IRC01:05
*** sdake has joined #openstack-kolla01:06
*** f13o has quit IRC01:08
*** kristian__ has joined #openstack-kolla01:11
*** tovin07_ has joined #openstack-kolla01:15
*** kristian__ has quit IRC01:15
duonghqmorning guys01:18
*** zhurong has joined #openstack-kolla01:19
*** liyifeng has quit IRC01:20
*** newmember has quit IRC01:23
openstackgerritDuong Ha-Quang proposed openstack/kolla-ansible: Specify 'become' for only neccesary tasks (all other roles)  https://review.openstack.org/39868501:24
*** sdake has quit IRC01:27
*** sdake has joined #openstack-kolla01:29
*** dave-mccowan has joined #openstack-kolla01:34
*** jtriley has joined #openstack-kolla01:38
*** diogogmt has quit IRC01:46
*** eaguilar has joined #openstack-kolla01:47
*** sdake has quit IRC01:50
*** prameswar has joined #openstack-kolla01:52
*** sdake has joined #openstack-kolla01:53
openstackgerritJeffrey Zhang proposed openstack/kolla: Remove adding repo in magnum-base Dockerfile  https://review.openstack.org/40103201:59
*** Pavo has quit IRC02:03
*** Pavo has joined #openstack-kolla02:03
*** prameswar has quit IRC02:05
openstackgerritMerged openstack/kolla-ansible: Fix congress broken  https://review.openstack.org/40062302:06
*** liyifeng has joined #openstack-kolla02:08
*** DaveTurner has quit IRC02:10
*** inc0 has joined #openstack-kolla02:10
*** dave-mcc_ has joined #openstack-kolla02:11
*** dave-mccowan has quit IRC02:12
*** dave-mccowan has joined #openstack-kolla02:13
*** sdake has quit IRC02:14
*** sdake has joined #openstack-kolla02:15
*** dave-mcc_ has quit IRC02:16
*** hieulq has joined #openstack-kolla02:18
*** dave-mccowan has quit IRC02:18
*** hieulq has quit IRC02:21
*** hieulq has joined #openstack-kolla02:23
*** fguillot has quit IRC02:27
*** jascott1 has quit IRC02:28
*** sdake has quit IRC02:36
*** sdake has joined #openstack-kolla02:37
*** dave-mccowan has joined #openstack-kolla02:39
*** inc0 has quit IRC02:44
*** dave-mccowan has quit IRC02:48
*** tonanhngo has quit IRC02:53
*** fragatina has quit IRC02:53
*** diogogmt has joined #openstack-kolla02:56
*** sdake has quit IRC02:57
*** sdake has joined #openstack-kolla02:59
*** zhurong has quit IRC03:04
*** zhurong has joined #openstack-kolla03:06
*** kollabot has quit IRC03:15
*** kollabot has joined #openstack-kolla03:16
*** sdake has quit IRC03:19
*** sdake has joined #openstack-kolla03:21
*** unicell has quit IRC03:34
*** zhurong has quit IRC03:35
*** zhurong has joined #openstack-kolla03:36
*** sdake has quit IRC03:41
*** sdake has joined #openstack-kolla03:43
*** fragatina has joined #openstack-kolla03:51
*** fragatina has quit IRC03:52
*** fragatina has joined #openstack-kolla03:52
*** Pavo has quit IRC04:03
*** sdake has quit IRC04:03
*** sdake has joined #openstack-kolla04:04
*** Pavo has joined #openstack-kolla04:07
*** mdnadeem has joined #openstack-kolla04:08
*** jgriffith is now known as jgriffith_away04:10
*** sayantani01 has joined #openstack-kolla04:22
*** sdake has quit IRC04:25
*** sdake has joined #openstack-kolla04:28
*** eaguilar has quit IRC04:28
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-ansible: Updated from global requirements  https://review.openstack.org/40078904:31
*** tonanhngo has joined #openstack-kolla04:32
openstackgerritDuong Ha-Quang proposed openstack/kolla-ansible: Specify 'become' to neccesary tasks (general roles)  https://review.openstack.org/39868204:37
*** sdake has quit IRC04:49
*** sdake has joined #openstack-kolla04:53
*** hyang_ has joined #openstack-kolla04:53
*** hyang_ has quit IRC04:54
sdakesup peeps05:06
*** Jeffrey4l has quit IRC05:06
*** sayantani01 has quit IRC05:06
*** sayantani01 has joined #openstack-kolla05:07
*** newmember has joined #openstack-kolla05:08
*** unicell has joined #openstack-kolla05:14
*** senk has joined #openstack-kolla05:24
*** unicell has quit IRC05:26
*** unicell has joined #openstack-kolla05:26
*** senk_ has joined #openstack-kolla05:28
openstackgerritSteven Dake proposed openstack/kolla: Add specs are advisory readme.rst to kolla repo  https://review.openstack.org/40057005:28
*** senk has quit IRC05:31
*** sdake_ has joined #openstack-kolla05:31
*** sdake has quit IRC05:35
*** senk has joined #openstack-kolla05:37
*** senk_ has quit IRC05:40
*** yingjun has quit IRC05:43
*** prameswar has joined #openstack-kolla05:49
*** skramaja has joined #openstack-kolla05:50
*** zhangshuai has quit IRC06:00
*** Pavo has quit IRC06:03
*** Pavo has joined #openstack-kolla06:07
*** zhangshuai has joined #openstack-kolla06:12
*** yingjun has joined #openstack-kolla06:14
*** kristian__ has joined #openstack-kolla06:16
*** jtriley has quit IRC06:19
*** kristian__ has quit IRC06:20
bjolomorning06:33
sdake_sup bjolo06:33
bjolosup dake06:34
sdake_not much just reviewing06:35
sdake_review queue long06:35
bjoloi hear ya06:38
openstackgerritcaoyuan proposed openstack/kolla-ansible: Update the version for hacking from global requirement  https://review.openstack.org/40108306:38
bjolosdake_, where can i see all new PS in gerrit?06:39
sdake_bjolo you can add the projects you want to watch to your watched project list06:39
sdake_to do so, click your username then click watched projects then type in something like openstack/kolla-ansible06:39
sdake_i watch kolla, kolla-ansible, and kolla-kubernetes06:40
bjoloi want to help out more, both with reviews and code, but im sooo swamped in work right now06:41
sdake_bjolo there is no expectation that you do reviews and code :)06:41
bjolobut i want to :)06:41
sdake_bjolo imo you help quite a bit in the community already06:41
bjoloi want to take a crack on the db backup06:41
sdake_keep in mind this is a volunteer effort06:41
sdake_cool that would be pretty sweet06:42
bjoloyes it is, but it is also a great learning place06:42
sdake_right, that is the magic of irc ;)06:42
*** kristian__ has joined #openstack-kolla06:42
bjoloive learned so much about openstack and ansible just by hanging out here and do what i can to contribute06:42
openstackgerritcaoyuan proposed openstack/kolla: Updated from global requirements  https://review.openstack.org/40108506:43
bjoloabout the backup... we really want this feature. Not to long ago we wanted to add some more compute nodes to our fuel based cloud06:43
bjolothe deploy failed, which is kinda normal for fuel06:44
bjoloso the normal procedure is to delete the node from fuel06:44
*** kristian__ has quit IRC06:44
*** kristian__ has joined #openstack-kolla06:44
bjolosomehow fuel got this wrong and deleted every node in the cloud06:44
bjolobasically wiped discs and rebooted every node. controllers, network, compute, storage06:45
*** msimonin has joined #openstack-kolla06:45
*** senk has quit IRC06:46
bjolowe had local db backups on every controller node06:46
bjolobut they got wiped as well06:46
bjolothis was only a test cloud, but still...06:47
bjoloeven if we restored the database, whole ceph was gone anyway06:48
*** msimonin has quit IRC06:48
bjololesson learned. dont but all eggs in the same basket06:49
openstackgerritMerged openstack/kolla-ansible: Pull swift-object-expirer image  https://review.openstack.org/40089406:49
bjolosdake_, one of my patches are in confligt, but i dont really see where.06:56
bjolohttps://review.openstack.org/#/c/372678/206:56
*** kristian__ has quit IRC07:08
*** senk has joined #openstack-kolla07:14
*** sayantani01 has quit IRC07:18
openstackgerritEduardo Gonzalez proposed openstack/kolla: Pull swift-object-expirer image  https://review.openstack.org/40109707:24
sdake_bjolo we split kolla and kolla-ansible repositories07:29
sdake_so you need to resubmit that change to kolla-ansible07:29
openstackgerritEduardo Gonzalez proposed openstack/kolla: typo error of keyring spelling  https://review.openstack.org/40110307:39
openstackgerritEduardo Gonzalez proposed openstack/kolla: Fix neutron.conf.j2 metadata_workers spelling error  https://review.openstack.org/40110707:44
sdake_bjolo that makes me cry a little inside (your story about cloud deletion)07:44
*** jascott1 has joined #openstack-kolla07:47
sdake_sup jascott107:47
sdake_i see you run my hours :)07:47
jascott1hey07:48
jascott1been a night owl since I can remember07:48
jascott1dont hold a candle to the hours you appear to put in tho ;)07:49
jascott1just got back from pre thanksgiving grocery store run07:50
jascott1:(07:50
*** jtriley has joined #openstack-kolla07:53
sdake_just got back from dinner with wife07:53
jascott1nice. good meal?07:55
sdake_ya melting pot07:55
jascott1ive never been. theres one downtown but idk just never have gotten by there (or the other million places around here)07:56
jascott1big fan of cheese tho :D07:56
*** matrohon has joined #openstack-kolla07:56
sdake_ya i dont roll wit h chese often - just pizza and cheese crisp07:57
*** tonanhngo has quit IRC07:57
*** jtriley has quit IRC07:58
jascott1if I ever give up on talking to these robots and was insane enough to start a food releated biz, i would consider a place that sells fried cheese07:58
*** jtriley has joined #openstack-kolla07:58
jascott1one cool thing about portland is, if you are into something weird there is a good chance others are as well ;)07:59
sdake_i ahve a friend in hit ech that opened a food truck07:59
jascott1hows it going?07:59
sdake_he obviously doesn't make the kind of money he did prior07:59
sdake_but some times career changes are good for people08:00
sdake_and in this case that is true08:00
jascott1no doubt'08:00
jascott1between my fam and wifes fam and  friends we have about 20 people here from our hometown in MS08:01
jascott1down there we have 'slug burgers'08:01
*** tonanhngo has joined #openstack-kolla08:01
jascott1which we all think would be a hit ina food cart08:01
sdake_say jascott1 michal said your working on helm related things?08:02
jascott1i am08:02
jascott1trying to figure it all out08:02
jascott1whats up?08:02
*** Pavo has quit IRC08:03
*** jtriley has quit IRC08:03
*** tonanhngo has quit IRC08:03
jascott1im supposed to be xpert for our team on k8s/helm08:04
sdake_jascott1 nice08:05
sdake_jascott1 since your an expert and kevin is an expert, it would be nice to get you two working together08:05
sdake_i use the term expert here loosly :)08:05
jascott1we have definitely had some good conversations08:05
jascott1me too!08:05
sdake_since this is all new territory08:05
sdake_would you mind reviewing his helm implementation08:05
sdake_https://review.openstack.org/#/c/396296/08:05
jascott1no doubt and changing every few mins08:05
jascott1yes I have been looking at it but not since last week08:06
jascott1i do need to catch him cause I have a couple questions08:06
sdake_the way to do that is via gerrit :)08:07
*** Pavo has joined #openstack-kolla08:07
sdake_are you familiar with the tool?08:07
jascott1true08:07
jascott1yes and have been using but dont have a ton of experience with it yet08:07
sdake_cool08:08
sdake_it takes a little bit to get the hang of it08:08
jascott1i heard bad things but so far its been pretty cool08:08
sdake_but once you do, its pretty straightforward08:08
jascott1especially seeing the PS revisions08:08
jascott1ya takes a minute to remember the git workflow with the ammends08:09
jascott1so used to regular git feature branch approach08:09
sdake_yup - to work successfully in openstack key is to learn the workflow08:10
sdake_which is pretty straightforwrd08:10
jascott1yes08:10
sdake_have prior experience in openstck workflow?08:10
jascott1no but have been trained at Rackspace08:10
jascott1i 'get it' but need more experience actually doing the things08:11
sdake_ok - i dont know what trined at rax means :)08:11
jascott1haha08:11
*** berendt has joined #openstack-kolla08:12
berendtmorning guys08:12
jascott1so Intel and Rackspace have a partnership, OSIC and when I joined they sent me Rackspace for 3 weeks to train08:12
sdake_sup berendt08:12
jascott1good morning08:12
sdake_experience > training08:12
jascott1thats the usual for me08:13
sdake_i see 27 patch reviews on that helm chart08:13
jascott1RTFM -> bang head on keyboard -> repeat08:13
sdake_roger that :)08:13
sdake_it would be helpful to see your reviews08:13
jascott1will do08:14
sdake_more minds working together > less minds working together08:14
jascott1i wanted to talk w him again to get more of a sense of where he is going with the layout in wrt to installing things08:14
jascott1ya weve had some good talks so far on it08:15
sdake_ya the downside of that is all that context is lost to the other reviewers08:15
jascott1good point08:15
sdake_so other reviewer dont know where you think rpoblems are in the implementation08:16
sdake_reviewers08:16
sdake_you see sbezverk and kfox1111 in that review have alot of conversation going on08:16
sdake_I can spend 30 minutes reading the review log08:16
sdake_and then make a decision whether to +2 the patch or not08:16
sdake_otherwise if it needs further revision leave a -1 on the patch08:17
jascott1right08:17
sdake_-1 = signal that further revision is required08:17
sdake_if the core reviewers can't see that work happening in the review queue, we can't actually make a determination if the work is solid enough to merge08:18
jascott1sure08:18
sdake_cool if i'm repating stuff you alredy know just ignore me :)08:19
sdake_you know how to use the comment feature?08:19
jascott1all good man. thanks for the nudge!08:19
jascott1yeah the inline one?08:19
sdake_yup08:19
jascott1funny I did that on the helm spec but it didnt make it to the next revision08:19
jascott1wasnt a big deal at all tho08:20
*** senk has quit IRC08:20
sdake_ya specs are an odd thing08:20
sdake_different then implementation08:20
sdake_specs = design08:20
sdake_lots of commentary on design = hard to merge everyones thoughts into one coherent document08:20
*** derekjhyang has quit IRC08:21
*** senk has joined #openstack-kolla08:21
sdake_sometimes comments are missed08:21
jascott1ya gotta admit feeling new to openstack and kolla (and somewhat gerrit) has made me more hesitant to jump in08:21
jascott1BUT08:21
sdake_The way I deal with this is to always use "reply done" when i've addressed a comment08:21
jascott1pretty soon you will be saying 'oh that guy again'08:22
jascott1ah08:22
sdake_doubtful :)08:22
sdake_if you are an expert on helm an k8s, your input would be much valued in that review08:23
jascott1will do08:23
jascott1think I will rock that first thing in the morning :)08:24
sdake_sounds good08:24
sdake_i'm about beat for the day too08:24
jascott1hey whats your opinion on our test 'coverage'?08:24
jascott1could we be doing more or its alright or?08:24
*** tonanhngo has joined #openstack-kolla08:24
sdake_gating is a continous improvement process08:25
jascott1sorry thats kinda dumb question since we could always do more08:25
*** tonanhngo has quit IRC08:25
*** senk_ has joined #openstack-kolla08:25
jascott1yeah ive learned alot from setup_gate.sh and friends08:26
sdake_pragmatically speaking writing gating is the hardest part of development08:26
sdake_especially functional tests08:26
jascott1still trying to grok enough ceph for kk8s purposes08:26
sdake_we struggle to have the minimal gates we have in place operational08:27
*** Serlex has joined #openstack-kolla08:28
*** Satya_ has joined #openstack-kolla08:28
*** senk has quit IRC08:28
jascott1yeah id like to be able to help out there. ill spend some more time on it08:28
sdake_imo not the place to start ;)08:29
jascott1something todo in parallel tho right08:29
jascott1ive done previous CI pipeline work with docker08:30
sdake_i dont think gating is our most pressing issue atm08:30
jascott1internally and at AWS08:30
*** shardy has joined #openstack-kolla08:30
jascott1imean not *for* AWS08:30
jascott1not moving to SEA08:30
*** msimonin has joined #openstack-kolla08:31
openstackgerritSurya Prakash Singh proposed openstack/kolla-ansible: use uuidutils instead of uuid.uuid4()  https://review.openstack.org/39984708:31
jascott1its was very helpful to study the gate, helped me to start on getting a minimal ceph going08:31
sdake_yup, our development environment is not ideal08:32
jascott1i did goto an AWS mixer a couple months ago when intel was whacking ppl left and right08:32
jascott1any huge gaps with the env that jump out?08:33
jascott1oh wow that was 6 months ago08:33
sdake_jascott1 an ideal dev environment would be something that launches multiple vms on a machine in an automated way and deploys kubernetes within with whatever nodecount specified08:35
jascott1multinode08:37
sdake_jascott1 v1k0d3n mentioned earlier today  he has a dev environment almost ready to go with deploys ceph for persistent volumes for k8s08:37
sdake_he mentioned that PVC is broken in the implementation08:37
sdake_duonghq pingola08:38
jascott1yes my team is trying to help out so Ive been following.  I started glance chart but the PVC has hindered some08:38
duonghqhi sdake_08:38
sdake_sup duonghq08:38
jascott1kollabot hi08:39
kollabotHey08:39
sdake_jascott1 cool, so my team yoru team its team - we are the kolla team :)08:39
jascott1yes!08:39
jascott1btw really digging our little community here08:39
jascott1glad to help out with whatever so please ask if I can help with something08:39
duonghqI'm looking forward to kolla-k8s base stuff and doc, guess that today irc meeting is a very interesting meeting08:40
jascott1like the helm review :)08:40
sdake_jascott1 i did and you mentioend you would review08:40
jascott1i shall08:40
sdake_duonghq right, in the meantime mind taking a look at https://review.openstack.org/#/c/396296/08:41
duonghqsure08:41
sdake_jascott1 if you have a glance chart, another way you can help is to submit it to gerrit08:42
duonghqbtw, you know Brazilian? http://www.dicionarioinformal.com.br/pingola/ (j/k)08:42
sdake_jascott1 typically we use blueprints to track thi stuff08:42
jascott1it was for v1k0d3ns repo, i was checking out their implementation08:42
sdake_duonghq dont knwo brazillian08:42
jascott1but its all for kolla-k8s08:42
jascott1they are just poc'ing over there and have a deadline08:42
jascott1everyone is templating differently tho08:43
jascott1do we need to have a come to jeebus meeting08:43
sdake_pretty much - in a review :)08:43
sdake_jascott1 what other deltas do you notice08:43
sdake_i'm not particularly up to speed on helm08:44
jascott1ya I was thinking about carving up a gist for the meeting or post meeting08:44
jascott1should do that right quick08:44
sdake_a gist containing which?08:44
jascott1opens around different approaches08:44
sdake_best way to do that is in the review process08:45
sdake_if you could submit your glance implementation for helm that would be helpful08:45
sdake_the outcome of that is that templating is done in one way08:47
sdake_whichever way is sorted in the review queue for the kolla-kubernetes repository08:47
duonghqsdake_, sorry I cannot recall atm, but what is our etherpad to keeptrack who do which on kolla-k8s?08:48
sdake_duonghq thats what launchpad is for dude :)08:48
sdake_duonghq https://launchpad.net/kolla-kubernetes/+milestone/occata-108:49
duonghqso, as I can see, we do not have work items for kolla-k8s bp: helm-packaging?08:49
sdake_duonghq can you fix that pls08:49
*** jmccarthy has quit IRC08:49
jascott1sdake_ yes all good w all of that.08:49
*** jmccarthy has joined #openstack-kolla08:50
*** jmccarthy has left #openstack-kolla08:50
duonghqas I understand, from now and then, we use operator for manage our cluster?08:50
*** jmccarthy has joined #openstack-kolla08:50
duonghqsdake_, I think helm-packaging should be targeted to o-1?08:51
*** liyifeng has quit IRC08:51
duonghqor we need more PoC?08:52
sdake_duonghq well we ae actually in o2 atm08:52
duonghqah, sorry08:52
sdake_but launchpad is not really up to date08:52
sdake_we need to fix that08:52
jascott1where does "Mongodb Integration" come in?08:53
sdake_jascott1 who knows :)08:53
sdake_are you working on that part related to glance?08:53
jascott1or fit in rather08:53
sdake_mongodb is a dep for a bunch of services unrelated to compute kit08:53
jascott1no i just noticed it on the blueprint  list08:53
jascott1oh ha kevin beat me to it "Why? The only thing I know of that uses mongodb is ceilometer, and I believe they deprecated it? - kfox1111"08:54
sdake_ya they moved to gnocchi08:54
sdake_we adapt to our upstreams in kolla08:54
sdake_that blueprint can likely be deprecated08:54
*** tonanhngo has joined #openstack-kolla08:54
duonghqdo we follow this: https://releases.openstack.org/ocata/schedule.html08:55
sdake_jeffrey4l is the foremost expert in how all that stuff works - so i'd rather let him deprecate it :)08:55
sdake_duonghq thats the idea08:55
sdake_duonghq since o1 has shipped08:55
duonghqso, the helm-packaging should be the same milestone as operator-base?08:55
SerlexMorning, I see nova_compute is not started if ironic is enabled. why so?08:56
sdake_duonghq the way we typically handle launchpad is we put everything in o208:56
duonghqah, now I can recall that the 4.0.0 is tagged :)08:56
sdake_4.0.0.0b1 of kolla-ansible08:56
sdake_we are working on 1.0.0.0b2 of kolla-kubernetes08:56
*** tonanhngo has quit IRC08:57
sdake_4.0.0.0b1 of kolla repo08:57
duonghqcan we add o-2 to our projects?08:58
*** jtriley has joined #openstack-kolla08:59
sdake_duonghq sure what date you got for it09:00
sdake_Serlex no clue09:01
sdake_Serlex file a bug maybe someone will triage it :)09:01
sdake_duonghq i can add o2 - what is the schedule date09:02
duonghqI think if we want to keep up with OpenStack schedule, it's Dec 12-16?09:02
sdake_cool09:02
sdake_so thats the 15th - wednesday09:02
sdake_release team likes releases on the 15th09:02
sdake_rather on wednesdays :)09:02
duonghqroger :)09:03
sdake_duonghq your a member of kolla-drivers correct?09:04
duonghqyeah09:04
sdake_jascott1 your a member of kolla-drivers?09:04
jascott1yes09:04
sdake_cool09:04
sdake_i could use a bit of help moving stuff from o1 to o2 that is unfinished09:05
*** jtriley has quit IRC09:05
sdake_we file a bunch of blueprints, target them for a release, and if they miss, we kick em down the road09:05
sdake_o2 is created09:05
sdake_can both of you help me move the unfinished stuff to o2?09:06
jascott1sure09:06
sdake_i grow weary of pushing launchpd around09:06
sdake_thanks09:06
sdake_we can do it all together :)09:06
jascott110 each?09:07
sdake_i'll start at bottom 3rd, jascott top 3rd, duong somewhere in middle09:07
jascott1ha ok09:07
sdake_dont move the ones that are implemented09:07
duonghqsdake_, roger, but the ocata is ocata, not occata09:07
*** rmart04 has joined #openstack-kolla09:07
sdake_duonghq moment i'll fi that typo09:07
duonghqroger09:07
*** Satya_ has quit IRC09:08
jascott1im looking at how to do it :)09:08
jascott1found it09:08
jascott1uh09:09
jascott1i changed 2 and now I get 'lost something'09:09
Serlexok sdake09:09
duonghqjascott1, the milestone's name is changed09:11
jascott1hmm ok im just working off of 'all blueprints' now09:12
sdake_ya sorry about that - i marked the o1 inactive accidentally09:13
sdake_launchpad takes some experience to manage properly09:13
sdake_stil make mistakes 5 years later :(09:13
*** tonanhngo has joined #openstack-kolla09:15
*** tonanhngo has quit IRC09:15
sdake_nice faster with 3 then with 1 :)09:16
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-ansible: Updated from global requirements  https://review.openstack.org/40078909:16
jascott1fan out!09:16
openstackgerritZhigang Li proposed openstack/kolla-kubernetes: Replace basestring with six.string_types  https://review.openstack.org/40114409:16
sdake_winning :)09:16
duonghqnot much for o-109:16
jascott1are done?09:16
duonghqjascott1, done in my PoV09:16
sdake_done with that step09:16
sdake_depends how much launchpad torture you want tonight :)09:17
jascott1heheh09:17
duonghqguys should update current status09:17
openstackgerritJack Ning proposed openstack/kolla: Add customized plugin to keystone image  https://review.openstack.org/40114509:17
sdake_yup lets do that09:17
jascott1sorry what exactly?09:18
duonghqsdake_, iirc, we have compute-kit from newton?09:19
duonghqdo we need to move it to operator pattern?09:19
sdake_duonghq we can implement any way we like09:20
sdake_as long as we meet the spec ;)09:20
*** fragatina has quit IRC09:20
duonghqroger09:20
*** fragatina has joined #openstack-kolla09:20
jascott1brb09:21
*** egonzalez90 has joined #openstack-kolla09:21
egonzalez90morning09:21
sdake_sup egonzalez9009:23
sdake_duonghq jascott lets work on breaking this blueprint into parts09:23
sdake_https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-packaging09:23
sdake_rather jascott109:24
duonghqsdake_, you mean break it into "sub" bp?09:24
sdake_right09:24
sdake_helm for ceph09:24
egonzalez90sdake_: read the other day that we need to abandon changes pointing to stable/liberty to tag liberty as eol09:24
egonzalez90these are the changes ATM https://review.openstack.org/#/q/status:open+project:openstack/kolla+branch:stable/liberty09:25
sdake_egonzalez90 inc0 is your man :)09:25
sdake_egonzalez90 ryan wont be able to continue on kolla-kubernetes it appears09:25
sdake_so in the mean time i'll fill in for him09:26
sdake_egonzalez90 so really have no bandwidth to deal with wider project issues that are the ptl's job :)09:26
duonghqsdake_, why rhallisey do not continue with kolla-k8s?09:26
sdake_duonghq its personal in nature and i don't discuss other people's personal business09:27
egonzalez90roger sdake_ , i just was wondering if we force abandons or request the author to abandon the change09:27
duonghqroger09:27
sdake_he did a fantastic job getting us rolling09:27
egonzalez90yeah, a great job!09:27
sdake_egonzalez90 force abandons are rude however if this is an opentack process i'd typicllly consult ttx on the matter09:28
sdake_egonzalez90 but ttx can't have a million people consulting with him, so inc0 cna do that :)09:28
sdake_so scope of kolla-kubernetes is compute kit09:29
sdake_inc0 set context he would like to see it done by ocata09:30
sdake_so thats what we are doing now09:30
sdake_duonghq the scope answer was for you09:31
duonghqthank you sdake_09:31
sdake_i think we need ceph in the mix too from what i gather :)09:31
egonzalez90sdake_: i will join k8s for christmas, i dont have enough free time to be in ansible and k8s at the same time now.09:31
sdake_egonzalez90 roger volunteer project - work on what you want :)09:32
jascott1wasnt ryan working on operator?09:33
sdake_jascott1 yup09:33
egonzalez90yup i want to work on k8s too, but need more time09:33
sdake_egonzalez90 cool - would be good to see everyone work on all the projects :)09:33
sdake_rather deliverables09:33
sdake_duonghq you got a date for o3?09:34
duonghqsdake_,  Jan 23-2709:34
sdake_thanks so jan 25 then09:34
duonghqya,09:35
duonghqI must go to my class in about 20mins, see you guys in today meeting09:38
*** yingjun has quit IRC09:38
*** yingjun has joined #openstack-kolla09:38
duonghqmove through Hanoi traffic jam09:38
*** strigazi_AFK is now known as strigazi09:39
jascott1good luck!09:39
sdake_duonghq enjoy09:40
*** gfidente has joined #openstack-kolla09:40
sdake_jascott1 willing to pitch in and finish the job on organizing launchpad appropriately09:41
jascott1sure09:41
sdake_cool09:41
jascott1can we do in ~20 mins?09:41
jascott1prob force myself to get some sleep09:41
jascott1but yea lets get er done09:41
duonghqjascott1, I've daily report to be done on my deck, sorry09:42
jascott1np we will knock it out09:42
sdake_i think it will take more then 20 minutes09:42
jascott140?09:42
jascott1np lets rock it09:42
sdake_but if people have to drop off thats cool09:42
*** yingjun has quit IRC09:43
jascott1what are we doing?09:43
sdake_so the trick here is figuring out what is essential09:43
sdake_and what isn't09:43
sdake_to deliver compute kit09:44
sdake_according to the specification09:44
jascott1werd09:44
sdake_the stuff that isn't essential we can put in discussion state09:44
jascott1spec for compute kit? I havent seen it09:44
*** tonanhngo has joined #openstack-kolla09:44
sdake_the kolla-kubernetes architecture specification09:44
jascott1oh ok09:44
sdake_scope limited to compute dkit09:45
jascott1ok09:45
*** tonanhngo has quit IRC09:46
sdake_swift - not part of compute kit09:46
jascott1the ones listed here? https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-packaging09:47
jascott1thats what I have been thinking compute kit means09:47
sdake_yes those09:48
sdake_pretty much :)09:48
jascott1cool09:48
sdake_that is a meta-blueprint09:48
sdake_duonghq do you mind dropping work on swift to focus on compute kit ?09:48
duonghqsdake_, np09:49
openstackgerritZhigang Li proposed openstack/kolla-kubernetes: Replace basestring with six.string_types  https://review.openstack.org/40114409:49
duonghqsdake_, I'll join the compute-kit force09:49
sdake_duonghq cool09:49
jascott1with helm and operators?09:50
sdake_yup and init containers with entrypoint09:50
jascott1got it09:50
sdake_thats the architecture09:50
sdake_first order of business is to get launchpad organized09:51
sdake_because atm, it isn't09:51
sdake_duonghq can you untarget swift in launchpad09:52
sdake_from ocata09:52
sdake_we are in essence kicking it out of ocata :)09:52
duonghqsdake_, sure09:53
sdake_lights out recovery09:53
sdake_soudns nice09:53
sdake_not part of our objective09:53
*** jtriley has joined #openstack-kolla09:53
duonghqsdake_, done :)09:53
sdake_i'll untarget that one09:53
sdake_mongodb jascott1 you mentioned you took a look at the contents, can you untarget09:54
jascott1sure09:55
sdake_ssl support sounds nice09:56
sdake_we didn't have it for kolla 1.0.009:56
jascott1we are setting 'Definition' to 'Discussion' correct?09:56
sdake_i think we can untarget that for now and revisit09:56
sdake_yup set definition to discussion09:56
jascott1not actual Re-target09:56
jascott1ok thanks09:56
sdake_ya and remove from ocata release09:57
jascott1"Run ceilometer on Kubernetes"?09:57
sdake_so thats the retarget part09:57
sdake_ya nix that :)09:57
jascott1Re-target blueprint and leave blank?09:57
sdake_we can always add em back in09:57
sdake_do your thing on that blueprint and i'll have a look09:57
sdake_and see if its correct :)09:57
duonghqcya in today meeting09:58
*** duonghq has quit IRC09:58
*** jtriley has quit IRC09:58
jascott1oh its doesnt accept blank09:58
*** jtriley has joined #openstack-kolla09:59
jascott1is it Seried Goal?09:59
sdake_jascott1 not a series goal09:59
jascott1sorry, how to un-target ?09:59
sdake_jascott1 can you link - i dont' see the blueprint in launchpad09:59
jascott1https://blueprints.launchpad.net/kolla-kubernetes/+spec/ceilometer-kubernetes09:59
sdake_i'll teach you10:00
sdake_see accepted for ocata10:00
jascott1yes10:00
sdake_see yellow button next to it10:00
jascott1under 'Series Goal'10:00
sdake_click that one10:00
sdake_the yellow button10:00
jascott1ok check it now10:01
sdake_looks good - one note - all launchpad blueprints shoudl be set to not started10:01
*** zhurong has quit IRC10:01
jascott1ok10:01
jascott1lemme fix mongo one up10:01
sdake_that are in the state that particular one is in10:01
sdake_dunn owhy launchpad has that set the way it does10:02
sdake_oh set priority to undefined as well :)10:02
jascott1oh what about milestone target?10:02
sdake_since its not accepted for ocata, it can't hav ea priority10:02
sdake_milestone target should be untargeted too10:02
jascott1ok10:02
*** Pavo has quit IRC10:03
*** jtriley has quit IRC10:03
sdake_https://blueprints.launchpad.net/kolla-kubernetes/+spec/ceilometer-kubernetes looks pretty good but currently set to implementation unknown10:03
sdake_we need to get rid of the noise10:04
jascott1what should implementation be set to?10:05
*** tonanhngo has joined #openstack-kolla10:05
*** YuYangWang has joined #openstack-kolla10:05
*** tovin07_ has quit IRC10:06
*** tonanhngo has quit IRC10:07
jascott1"Lights off recovery" is out correct?10:07
sdake_ya10:07
sdake_in the meeting today people can pull this stuff back in if they want10:07
*** Pavo has joined #openstack-kolla10:08
sdake_need to get things rolling - lots of blockages10:08
sdake_general rule of thumb stuff in good progress state stays in until deadlines are hit :)10:09
sdake_even if its extra10:09
jascott1sounds like nice to have: https://blueprints.launchpad.net/kolla-kubernetes/+spec/cli-resource-types10:10
sdake_people always add extra stuff - which is cool - atm i see a sea of blueprints and as a developer its har to know where to start10:10
jascott1but not sure10:10
jascott1i will take it out and they can pull it back liek you say10:10
sdake_no implementation10:10
sdake_medium priority10:10
sdake_not part of objective or spec10:11
sdake_again ppl can always pull stuff back in if they implmeent it10:11
sdake_jascott1 re https://blueprints.launchpad.net/kolla-kubernetes/+spec/init-container-fail10:14
sdake_does that make any sense to you :)10:14
jascott1yes10:15
jascott1started, i would say keep10:15
jascott1init container runs a script but only fails out if last command in script fails10:16
jascott1needs to fail out if any command fails10:16
jascott1but10:16
jascott1are we using init containers for that anymore10:17
*** zhangshuai has quit IRC10:17
jascott1since it goes to consistency/reliability of compute kit I would keep it10:17
jascott1sdake should we be setting ocata-2 if its something we are keeping?10:18
jascott1this needs more detail imo, as its written this is covered by entrypoint https://blueprints.launchpad.net/kolla-kubernetes/+spec/health-checks10:22
sdake_jascott1 yup ocata-2 if keeping10:22
*** zhangshuai has joined #openstack-kolla10:23
sdake_jascott1 do containers need healthchecks built in?10:23
sdake_our architcture has entrypoint in an init container10:23
jascott1right10:23
sdake_so init-container-fail stays?10:24
jascott1entrypoint handles those deps10:24
*** tonanhngo has joined #openstack-kolla10:24
sdake_ok sounds like we have some container work to do as well10:24
sdake_we can tackle that later ;)10:24
jascott1yes10:24
jascott1yes init-container-fail stays10:24
sdake_cool10:24
jascott1its about correctnes10:25
sdake_wfm10:25
*** tonanhngo has quit IRC10:25
sdake_i just dont understnd what the content is in the blueprint :)10:25
*** zhubingbing_ has quit IRC10:26
jascott1i hear ya. thats how I usually feel around here :)10:26
jascott1but have sense of k8s/helm and have looked at several of the new implementations going on10:26
jascott1but yeah this guys is covered by entrypoint unless they are intending more advanced logic https://blueprints.launchpad.net/kolla-kubernetes/+spec/health-checks10:27
jascott1and if its advanced logic then they should update it to say 'that entrypoint doesnt provide'10:27
jascott1or similar10:27
jascott1one prob for me is sometimes ppl say init container and they mean the stackanets entrypoint that simply waits for deps and sometimes they mean a Job container to 'init' the service10:30
jascott1like this one https://blueprints.launchpad.net/kolla-kubernetes/+spec/dependency-init-container10:30
jascott1that one is entrypoint afaik10:31
sdake_jascott1 sorry was working in launchpad give mea moment to read10:33
sdake_ok so health checks sounds like something for kolla repo10:34
*** jascott1_ has joined #openstack-kolla10:34
sdake_where as dependency-init-contianer sounds like something more for kolla-kubernetes10:34
sdake_jascott1_ [03:34:34]  <sdake_>ok so health checks sounds like something for kolla repo10:35
sdake_[03:34:50] jascott1_ (jascott1@nat/intel/x-hqtginzhsxxzhsii) joined the channel10:35
sdake_[03:34:52]  <sdake_>where as dependency-init-contianer sounds like something more for kolla-kubernetes10:35
*** jascott1 has quit IRC10:35
jascott1_well health check is part of k8s container def10:35
sdake_if we really aren't certain lets punt and keep it in and we can hash it out in todays meeting10:35
jascott1_cool10:35
*** ppalacios has joined #openstack-kolla10:36
sdake_probably those blueprints need to be merged10:36
jascott1_ya i was going to leave it also10:36
jascott1_yea10:36
sdake_or one needs to go to kolla to implement the healthchecking10:36
*** ppalacios has left #openstack-kolla10:36
jascott1_going to change my avatar https://lh3.googleusercontent.com/_5CNFBJhHzCw/S0VHrZYKESI/AAAAAAAApNE/0bkOKq1nb5Q/Futurama-Hermes-Conrad.jpg10:37
*** newmember has quit IRC10:37
jascott1_:)10:37
sdake_zomg10:37
sdake_that guy rocks :)10:37
sdake_fwiw we dont rubber stamp reviews unless they need rubber stamping10:37
jascott1_sounds legit10:38
sdake_and there is still an expectation of core reviewers that htey should check out the code10:38
sdake_and make sure it is right10:38
sdake_rubber stamping is rare10:38
jascott1_oh this one https://blueprints.launchpad.net/kolla-kubernetes/+spec/kolla-kubernetes-tools10:39
jascott1_just says 'tools'10:39
jascott1_paraphrasing10:39
jascott1_im sure it was a placeholder10:39
*** jascott1 has joined #openstack-kolla10:41
jascott1vpn choked or something idk10:41
jascott1thoughts on tools? (sorry if ye replied already, bouncer is on the fritz today)10:42
jascott1ha we just edited same10:44
jascott1password-secrets10:44
*** mmoster_ has quit IRC10:44
*** jascott1_ has quit IRC10:45
*** liyifeng has joined #openstack-kolla10:45
jascott1sdake ?10:45
jascott1imean sdake_10:46
sdake_sorry10:47
sdake_was working :)10:47
sdake_its a kolla-in-a-box10:47
sdake_thsi hsa been discussed multiple times10:47
sdake_people want to work on it10:47
sdake_is it a priority for spec + compute kit?10:47
sdake_think not10:47
sdake_if someone comes along and wants to work on it, more power to em10:48
jascott1nuking in 3 . 210:48
sdake_we dont force people to work on things or kick out work if its mergable10:48
berendtanybody knows why it could happen that rabbitmq does not startup ?10:48
sdake_berendt no idea10:48
berendtprocess in the container is running (/bin/sh -e /usr/lib/rabbitmq/bin/rabbitmq-server), but nothing happens10:49
sdake_berendt no time to debug atm10:49
sdake_rabbitmq is a pile of shit10:49
sdake_what more can be said10:49
jascott1similar https://blueprints.launchpad.net/kolla-kubernetes/+spec/pre-checks10:49
sdake_ya that can go10:49
sdake_its a feature we have in kolla10:50
sdake_what ryan did wit hteh blueprints is wrote a whole slew of em to give the community work to focus on10:50
sdake_the problem was they are all approved for ocata10:50
sdake_and there is not enough capacity to execute for ocata10:50
sdake_with all the stuff that is in there10:51
sdake_kolla-kubernetes 1.0.0 will not be equivalent feature wise to kolla-ansible10:51
sdake_it will probably take some time to catch up10:51
sdake_we are not doing a poc, we are doing a 1.0.0 project10:51
sdake_ryan was doing a 4.0.0 project ;)10:51
*** athomas has quit IRC10:52
*** jtriley has joined #openstack-kolla10:53
*** tonanhngo has joined #openstack-kolla10:54
jascott1yeah its such a moving target, helms 'about to' have plugins which would open up flexibility for us wrt to sub chart releases and what not10:54
jascott1sorry blabbering a bit there10:55
berendtlooks like it is an issue with the rabbitmq-clusterer plugin, single node deployment works10:56
jascott1sdake know any details on this one? https://blueprints.launchpad.net/kolla-kubernetes/+spec/ssl-support10:57
*** jtriley has quit IRC10:57
*** jtriley has joined #openstack-kolla10:58
jascott1sounds like a bug?10:58
*** tonanhngo has quit IRC10:59
sdake_no details known10:59
sdake_work ittems not filled out10:59
sdake_i am kind of a security nut10:59
sdake_however kolla-ansible lacked a tls implementation11:00
sdake_adding tls is fairly easy11:00
sdake_if we have time we can do it11:00
sdake_or if someone wants to tackle it cool :)11:00
*** athomas has joined #openstack-kolla11:00
jascott1leave?11:01
jascott1nuking kuryr11:01
*** Bico_Fino has joined #openstack-kolla11:02
jascott1this looks like re-target project to kolla-ansible https://blueprints.launchpad.net/kolla-kubernetes/+spec/bool-filter11:02
*** jtriley has quit IRC11:03
sdake_check it out - something achievable :) https://launchpad.net/kolla-kubernetes/+milestone/ocata-211:03
sdake_nice work jascott :)11:03
sdake_not sure if we move that or not - lets keep where it is for the moment11:04
*** tonanhngo has joined #openstack-kolla11:04
sdake_we have this funky genconfig thing at present11:04
sdake_which basically generates configuration from the defaults11:04
sdake_the defaults are jinja211:05
*** tonanhngo has quit IRC11:05
sdake_ansible runs the genconfig11:05
sdake_it was a short term hack to get dev moving11:05
sdake_intent there is to move the config into docker repo11:06
sdake_rather then kolla-kubernetes repo11:06
sdake_inc0 said he would write a spec on it11:06
*** msimonin has quit IRC11:06
sdake_i suggested blueprint but he wants to write a spec, god help him :)11:06
sdake_ok  - since i perceive alot of people working on helm11:08
sdake_the way we handle that is with one blueprint11:08
sdake_with work items11:08
sdake_jascott1 mind learning how to do that11:09
sdake_jascott1 i already know how :011:09
*** prameswar has quit IRC11:09
sdake_will walk yo uthrough it11:09
sdake_important thing to know11:09
jascott1creating blueprint with workitems?11:10
sdake_we already have the bleuprint11:11
sdake_not sure how familiar you are with launchpad11:11
jascott1oh spec right11:11
jascott1increasingly11:11
sdake_;)11:11
jascott1i havent written a spec or authored much in general in our systems11:12
jascott1but am familiar11:12
sdake_nah thats not what i mean11:13
sdake_work items in launchpad - let me show you11:13
*** liyifeng has quit IRC11:13
*** Jeffrey4l has joined #openstack-kolla11:14
*** igordcard has quit IRC11:14
jascott1ok11:14
*** msimonin has joined #openstack-kolla11:15
*** igordcard has joined #openstack-kolla11:15
sdake_https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-packaging11:15
jascott1o11:15
jascott1ok11:15
sdake_you see the field that says whiteboard?11:15
jascott1yes11:16
sdake_see how it has all that stuff in there11:16
jascott1i do11:16
sdake_that needs to go into the workitems section11:16
sdake_this is how we divide up work so people dont do the same thing11:16
jascott1ok11:17
jascott1so just copy pasta11:17
jascott1?11:17
sdake_sometimes that happens, but typically not becaue the blueprints are wrong :)11:17
sdake_nah the work items have a specific format11:17
jascott1so go ahead and create them with these titles11:17
jascott1?11:17
sdake_dont create blueprintgs11:18
sdake_create work items with the stuff in the whiteboard11:18
jascott1i get that but I hit the pencil and its just a text field11:18
jascott1i can look at another11:19
jascott1oh none of them have them it seems11:19
sdake_there is one11:20
sdake_the syntax is (unassigned)ceph: TODO11:20
sdake_i believe11:20
jascott1found some here but idk correctness https://blueprints.launchpad.net/kolla-kubernetes/+spec/swift-kubernetes11:20
sdake_yup that is right11:21
sdake_INPROGRESS = in progress11:21
sdake_unassigned = unassigned11:21
sdake_rather TODO = undone11:22
sdake_(unassigned)ceph: TODO11:22
sdake_give that a go11:22
jascott1gotcha. so do them all that format with TODO11:23
sdake_ya11:23
sdake_although one isn't todo11:23
*** tonanhngo has joined #openstack-kolla11:24
*** prameswar has joined #openstack-kolla11:25
jascott1which?11:25
sdake_not sure11:25
sdake_mark em all todo atm11:25
sdake_let me hunt down that review11:25
jascott1ok11:25
*** tonanhngo has quit IRC11:25
jascott1https://blueprints.launchpad.net/kolla-kubernetes/+spec/helm-packaging11:26
sdake_neutron is in progress11:28
*** liyifeng has joined #openstack-kolla11:29
Jeffrey4lsdake_, what that means in https://review.openstack.org/401032 ?   conversion to proper j2 macro?  we do not have j2 macro in mitaka branch.11:31
mliima_morning guys11:33
jascott1good morning!11:35
Jeffrey4lhi mliima_11:35
jascott1sdake_ done11:35
mliima_hey Jeffrey4l \o11:35
sdake_Jeffrey4l sorry dude11:35
sdake_didn't catch that was mitaka11:35
Jeffrey4lcould u review this https://review.openstack.org/#/c/400922/  and all the following patches. it unblock the mitaka branch11:36
Jeffrey4lsdake_, ;) ^^11:36
sdake_Jeffrey4l can you get another core to review pls11:36
openstackgerritMerged openstack/kolla-ansible: Remove docker folder from kolla-ansible  https://review.openstack.org/39832011:36
mliima_\o/11:36
mliima_i'm here Jeffrey4l sdake_11:37
Jeffrey4lall patches are:  https://review.openstack.org/400922  https://review.openstack.org/400892   https://review.openstack.org/40103211:37
Jeffrey4lsdake_, ok. np.11:37
sdake_jascott1 isn't glance in progress too?11:44
*** tonanhngo has joined #openstack-kolla11:44
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Added support for a stop playbook in kolla  https://review.openstack.org/39928911:45
*** Bico_Fino has quit IRC11:46
jascott1yes but i started it in v1k0d3n's format11:46
*** tonanhngo has quit IRC11:46
jascott1in the same manner in which their poc is implemented11:47
sdake_jascott1 cool thanks for your help - that got things moving in the right direction11:47
jascott1I appreciate the lesson!11:47
sdake_jascott1 ok - so thats still TODO then11:47
jascott1ya but I will convert it and update the work item :)11:48
sdake_sounds good :)11:48
jascott1gonna catch some z's. tty in the meeting11:48
sdake_enjoy11:48
jascott1|)11:48
Jeffrey4lklindgren, around?11:51
*** Bico_Fino has joined #openstack-kolla11:55
*** msimonin has quit IRC11:55
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Remove fragments of docker files  https://review.openstack.org/40122211:55
sdake_ok Jeffrey4l still need reviews or all set?11:56
*** jtriley has joined #openstack-kolla11:59
*** mkoderer has joined #openstack-kolla11:59
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Remove fragments of docker files  https://review.openstack.org/40122211:59
*** Pavo has quit IRC12:03
Jeffrey4lsdake_, yep.  https://review.openstack.org/400922  and its following https://review.openstack.org/400892  and last one you reviewed https://review.openstack.org/401032 .12:03
Jeffrey4lthe last one get green gate.12:03
*** openstackgerrit has quit IRC12:03
sdake_Jeffrey4l you got it looking12:03
Jeffrey4lthanks.12:03
*** openstackgerrit has joined #openstack-kolla12:03
*** jtriley has quit IRC12:04
*** jascott1 has quit IRC12:04
sdake_Jeffrey4l this patch is -112:04
sdake_https://review.openstack.org/#/c/400922/12:04
sdake_from jenkins12:04
sdake_not sure why12:04
sdake_your patch stream wont merge unless you fix that problem12:04
Jeffrey4lbecause percona repo issue see the logs http://logs.openstack.org/22/400922/1/check/gate-kolla-dsvm-build-oraclelinux-source-centos-7/3117f6f/console.html#_2016-11-22_18_33_11_14456512:05
Jeffrey4lthe second patch https://review.openstack.org/400892 fix this12:06
Jeffrey4lsdake_, ^^12:06
sdake_you will have to collapse the patches tehn12:06
sdake_rather squash12:06
sdake_to get past the gate12:06
sdake_are they dependent?12:07
Jeffrey4lcollapse means squash?12:07
Jeffrey4lis there any other workaround for such case?12:07
sdake_you could reorder the patches12:07
sdake_welcome to voting gates ;)12:08
*** Pavo has joined #openstack-kolla12:08
mliima_sdake_, Jeffrey4l should i remove https://github.com/openstack/kolla-ansible/blob/master/tests/test_kolla_docker.py and https://github.com/openstack/kolla-ansible/blob/master/tests/test_set_config.py ?12:08
openstackgerritMerged openstack/kolla: Pull swift-object-expirer image  https://review.openstack.org/40109712:08
Jeffrey4lsdake_, no. if put the percona first won't work, because disable ipv6 bust the gate.12:08
sdake_i see12:08
sdake_yup squash is only answer12:08
sdake_actually there is another answer12:09
sdake_make the gates nonvoting that are cusing jenkisn to fail12:09
Jeffrey4lmliima_,  test_kolla_docker no. test_set_config yes. the former is used by ansible, the latter is used by docker images.12:09
sdake_but that answer isn't what inc0 wants12:09
mliima_ok12:09
sdake_so squash is what needs to happen when gate bustages happen12:10
*** schwicht has joined #openstack-kolla12:10
Jeffrey4lsdake_, OK. i will squash there two patches into one.12:10
openstackgerritMauricio Lima proposed openstack/kolla-ansible: Remove fragments of docker files  https://review.openstack.org/40122212:11
openstackgerritMerged openstack/kolla: typo error of keyring spelling  https://review.openstack.org/40110312:12
mliima_sdake_, Jeffrey4l i need some review here https://review.openstack.org/#/c/400734/ and https://review.openstack.org/#/c/399715/12:14
Jeffrey4lroger, reviewing12:15
*** tonanhngo has joined #openstack-kolla12:15
Jeffrey4lmliima_, should we backport the sahara nfs issue to newton?12:15
*** tonanhngo has quit IRC12:16
mliima_no12:16
Jeffrey4lbecause manila-data is added in O, right?12:16
Jeffrey4lmliima_, ^12:16
mliima_yes Jeffrey4l12:16
Jeffrey4lmliima_, does manila support ceph-fs right now? is it recommended to use in production?12:18
mliima_ceph-fs?12:20
Jeffrey4lyup.12:20
mliima_no12:20
mliima_well12:20
mliima_i tested manila generic backend using ceph12:20
mliima_because cinder + lvm doesn't works in ubuntu 16.0412:21
mliima_so i tested using cinder + ceph, cinder is required to use manila + generic backend12:21
mliima_but ceph-fs, btw ceph-fs = ceph-filesystem?12:22
openstackgerritMerged openstack/kolla: Fix neutron.conf.j2 metadata_workers spelling error  https://review.openstack.org/40110712:22
Jeffrey4lmliima_, yep http://docs.ceph.com/docs/jewel/cephfs/12:22
openstackgerritMerged openstack/kolla: Fix Designate source image container assets  https://review.openstack.org/40073012:22
openstackgerritMerged openstack/kolla: Add specs are advisory readme.rst to kolla repo  https://review.openstack.org/40057012:22
openstackgerritJeffrey Zhang proposed openstack/kolla: Fix the gate  https://review.openstack.org/40092212:23
mliima_manila doesn't support ceph-fs Jeffrey4l , but I can do.12:23
mliima_http://docs.openstack.org/developer/manila/devref/cephfs_native_driver.html12:23
mliima_basically Manila is ready to support any backend, you just need set the configs inside manila.conf12:25
Jeffrey4lmliima_, never tried manila before ;).  but cephfs native driver is stable and ready for production use, right?12:25
mliima_yes12:26
Jeffrey4lsound cool.12:26
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Move glance precheck into its own role  https://review.openstack.org/39935412:28
*** mdnadeem has quit IRC12:33
*** schwicht has quit IRC12:33
*** alteriks has joined #openstack-kolla12:34
*** tonanhngo has joined #openstack-kolla12:34
*** tonanhngo has quit IRC12:35
*** msimonin has joined #openstack-kolla12:36
*** shardy is now known as shardy_lunch12:39
*** mmoster_ has joined #openstack-kolla12:40
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible: Add missing pull task for neutron-vpnaas-agent  https://review.openstack.org/40124012:41
openstackgerritJeffrey Zhang proposed openstack/kolla: Add socat into haproxy image  https://review.openstack.org/40124212:45
*** liyifeng has quit IRC12:47
openstackgerritJeffrey Zhang proposed openstack/kolla: Remove adding repo in magnum-base Dockerfile  https://review.openstack.org/40103212:52
sean-k-mooneyspeaking of ceph has anyone used the rbd volumn driver for docker?12:57
sean-k-mooneyi need to redeploy my ceph cluster this week.12:58
sean-k-mooneysorry kolla cluster12:58
sean-k-mooneyhas anyone used the rbd storage driver for docker before?12:58
sean-k-mooneyhttp://ceph.com/planet/getting-started-with-the-docker-rbd-volume-plugin/12:59
*** Bico_Fino has quit IRC12:59
*** liyifeng has joined #openstack-kolla12:59
pbourkeJeffrey4l: Im still getting denied by rootwrap in the vpnaas container :(13:03
Jeffrey4lpbourke, enable debug log and post the log file out in neutron-server.13:04
*** msimonin has quit IRC13:05
*** tonanhngo has joined #openstack-kolla13:05
*** prameswar has quit IRC13:06
*** tonanhngo has quit IRC13:06
*** Bico_Fino has joined #openstack-kolla13:06
*** schwicht has joined #openstack-kolla13:17
openstackgerritsatya proposed openstack/kolla-ansible: added separate interface for rabbitmq  https://review.openstack.org/40125613:21
*** Satya_ has joined #openstack-kolla13:22
Satya_hi sdake13:22
openstackgerritJeffrey Zhang proposed openstack/kolla: Bump OpenStack service version  https://review.openstack.org/39427113:23
Satya_hi jeffrey13:23
*** Bico_Fino has quit IRC13:23
*** jtriley has joined #openstack-kolla13:23
Satya_Please review https://review.openstack.org/#/c/401256/13:24
*** tonanhngo has joined #openstack-kolla13:25
Jeffrey4lroger.13:25
*** tonanhngo has quit IRC13:26
*** newmember has joined #openstack-kolla13:26
*** shardy_lunch is now known as shardy13:28
openstackgerritJeffrey Zhang proposed openstack/kolla: Bump OpenStack service version  https://review.openstack.org/39427113:29
*** sp__ has joined #openstack-kolla13:30
*** Bico_Fino has joined #openstack-kolla13:32
*** kristian__ has joined #openstack-kolla13:34
*** srwilkers has joined #openstack-kolla13:35
kristian__Hi I have a question. Can someone make a script or add it to the configs an automatic horizon plugin installer?13:35
*** zhubingbing_ has joined #openstack-kolla13:35
zhubingbing_hello guys13:35
sdake_sup zhubingbing_13:35
*** saneax-_-|AFK is now known as saneax13:36
sdake_sup srwilkers13:36
zhubingbing_hi13:36
srwilkershey sdake_13:36
openstackgerritJeffrey Zhang proposed openstack/kolla: Add socat into haproxy image  https://review.openstack.org/40124213:36
zhubingbing_sdake, can u help me review trove role?13:36
sdake_srwilkers quick q13:36
sdake_zhubingbing_ moment13:36
srwilkerssdake_, shoot13:36
zhubingbing_:)13:36
zhubingbing_ok thanks13:36
zhubingbing_https://review.openstack.org/#/c/400580/13:36
openstackgerritJeffrey Zhang proposed openstack/kolla: Add socat into haproxy image  https://review.openstack.org/40124213:36
*** ppalacios has joined #openstack-kolla13:37
sdake_srwilkers https://launchpad.net/kolla-kubernetes/+milestone/ocata-213:38
sdake_your blueprint is marked good progress13:38
sdake_i think we are in general agreement kolla-kubernetes needs a dev env13:38
*** lamt has joined #openstack-kolla13:39
*** schwicht has quit IRC13:39
srwilkersagreed -- when we started looking at getting involved months back, it was definitely something we saw as an opportunity13:39
sdake_i was speaking with v1k0d3n last night but lost laptop power13:40
sdake_he mentioned a problem with PVC13:40
sdake_2 qs.13:40
sdake_actually :)13:40
sdake_what is the PVC problem and how can we help solve it13:40
sdake_and when are the docs going to be in usable shape13:41
*** jtriley has quit IRC13:43
sdake_zhubingbing_ gate is green, thats a positive sign :)13:44
mliima_hi zhubingbing_13:45
*** dmsimard|away is now known as dmsimard13:45
*** zhubingbing_ has quit IRC13:45
openstackgerritMerged openstack/kolla: Fix the gate  https://review.openstack.org/40092213:46
*** kristian__ has quit IRC13:46
*** kristian__ has joined #openstack-kolla13:47
Jeffrey4lanyone is familiar with cross project testing? http://docs.openstack.org/infra/zuul/gating.html#cross-project-testing13:49
*** kristia__ has joined #openstack-kolla13:50
*** zhubingbing has joined #openstack-kolla13:51
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: Move glance precheck into its own role  https://review.openstack.org/39935413:52
*** kristian__ has quit IRC13:52
*** tonanhngo has joined #openstack-kolla13:55
*** tonanhngo has quit IRC13:56
*** BIOS_Hazard has joined #openstack-kolla13:57
BIOS_HazardWhat up Kolla people!13:57
BIOS_HazardI have had an eye on this project for a while and finally got a chance to try it out yesterday. I got all the way to the prechecks and am unsure of how to overcome an error (though I suspect I am simply misunderstanding the proper way to configure the globals).13:58
BIOS_HazardHere is my issue:13:59
BIOS_Hazard~~~13:59
BIOS_HazardTASK [prechecks : Checking if kolla_internal_vip_address is in the same network as network_interface on all nodes] ***13:59
BIOS_Hazardfatal: [localhost]: FAILED! => {"changed": false, "cmd": ["ip", "-4", "-o", "addr", "show", "dev", "enp4s0"], "delta": "0:00:00.003768", "end": "2016-11-22 22:53:55.705335", "failed": true, "failed_when_result": true, "rc": 0, "start": "2016-11-22 22:53:55.701567", "stderr": "", "stdout": "2: enp4s0    inet 198.136.52.141/29 brd 198.136.52.143 scope global enp4s0\\       valid_lft forever preferred_lft forever", "stdout_lines"13:59
BIOS_Hazard        to retry, use: --limit @/usr/share/kolla/ansible/prechecks.retry13:59
BIOS_Hazard~~~13:59
sdake_BIOS_Hazard please use a paste service13:59
BIOS_Hazardthat makes sense13:59
sdake_srwilkers ^^ not sure if you saw my msg above13:59
mliima_paste.openstack.org BIOS_Hazard13:59
mliima_:)13:59
BIOS_Hazardhttp://pastebin.com/dYwaT06i13:59
BIOS_HazardThanks mliima_14:00
BIOS_HazardI will use that next time14:00
sdake_zhubingbing looking good dude !14:00
sdake_zhubingbing few minor nitpicks i see in there14:00
zhubingbingok14:00
zhubingbingthanks14:00
BIOS_Hazardand here are my globals14:01
BIOS_Hazardhttp://paste.openstack.org/show/590208/14:01
sdake_zhubingbing unfortunately i dont know how to recommend how to fix - Jeffrey4l should provide a review i think since he touched that code last ;)14:01
BIOS_HazardOn enp4s0 I have 198.136.52.141/29 configured14:01
Jeffrey4lzhubingbing, sup14:01
zhubingbinghere14:02
BIOS_HazardI found the playbook section for this precheck, but I am unsure of what the "failed_when" logic entails14:02
*** Pavo has quit IRC14:02
*** duonghq has joined #openstack-kolla14:03
sdake_sup pavo14:04
duonghqevening guys14:04
sdake_pavo any chance you can help BIOS_Hazard with his network setup :)14:04
sdake_oops pavo is gone14:04
BIOS_HazardThanks sdake_14:04
*** jascott1 has joined #openstack-kolla14:04
sdake_duonghq sup dude14:04
BIOS_HazardI am very excited to pass the prechecks and get this all-in-one deployed.14:04
sdake_how was the ower nap jascott114:04
*** fguillot has joined #openstack-kolla14:05
sdake_power nap14:05
BIOS_Hazardkolla is clearly the future of openstack deployment and upkeep14:05
duonghqthank BIOS_Hazard14:05
BIOS_Hazardthank you guys, for putting so much work into this14:05
duonghqcannot figure out why the h button on my keyboard is unstable hmmm14:06
*** Pavo has joined #openstack-kolla14:07
*** jascott1 has quit IRC14:09
BIOS_HazardHowdy, Pavo14:09
sdake_pavo can you help BIOS_Hazard out with his network problem14:09
sdake_Pavo i think your our foremost expert on network debug atm :)14:09
Bico_FinoOdd behavior14:09
BIOS_HazardI love when the foremost expert hops on these IRC channels14:10
BIOS_Hazardlol14:10
BIOS_HazardIts happened to me in almost every other channel I go to14:10
Bico_FinoI enabled Debug on Horizon and ironic-ui started working. o_O14:10
openstackgerritJeffrey Zhang proposed openstack/kolla: Install mkfs.vfat tool in ironic-conductor image  https://review.openstack.org/40070914:11
sean-k-mooneyBico_Fino: could that be because fo the allowed_hosts?14:13
sean-k-mooneyBico_Fino: didi you have an error in the apache log before?14:14
Bico_Finosean-k-mooney:  no errors.14:14
Bico_Finosean-k-mooney: That’s why I enabled the Debug.14:14
sean-k-mooneyBico_Fino: strange14:14
Bico_FinoAlso allowed hosts looks fine14:14
Bico_FinoALLOWED_HOSTS = ['*']14:14
sean-k-mooneywell ALLOWED_HOSTS = ['*'] is a sledge hammer14:15
duonghqanybody using some irc bouncer?14:15
Bico_FinoBut earlier I ran /var/lib/kolla/venv/bin/manage.py compress14:15
sean-k-mooneyit should be retricted to your loadblancer ip and i think the ip/domain name of each of the host running horizon14:15
Bico_FinoI tried various ironic-ui versions14:16
Bico_FinoI’m using ironic-ui==2.0.0 now14:16
egonzalez90BIOS_Hazard: your internal_vip_address is in a different network as your network interface14:16
egonzalez90vip_address  198.136.52.14114:16
BIOS_Hazardoh wait, should that just be my main IP then??14:17
BIOS_Hazardsec14:17
egonzalez90sorry network itnerface have that IP14:17
egonzalez90vip is 198.49.65.17414:17
egonzalez90vip address is where services are going to communicate, and network_interface need to be in that network in order to communicate with it14:18
BIOS_Hazard> When running an All-In-One14:18
BIOS_Hazard# without haproxy and keepalived, this should be the first IP on your14:18
BIOS_Hazard# 'network_interface' as set in the Networking section below.14:18
BIOS_Hazard2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 100014:18
BIOS_Hazard    link/ether 00:25:90:61:cf:5e brd ff:ff:ff:ff:ff:ff14:18
BIOS_Hazard    inet 198.136.52.141/29 brd 198.136.52.143 scope global enp4s014:18
BIOS_Hazard(err, sorry, should have used a paste)14:18
BIOS_Hazardthis suggests to me that I should use that one IP I have on enp4s014:19
sean-k-mooneyyes14:19
sean-k-mooneyit is a security thing14:19
BIOS_Hazarddoing this fails the check before:14:19
sean-k-mooneybasically that controls the cross orgin request checking as far as i know14:19
BIOS_Hazardhttp://paste.openstack.org/show/590212/14:19
BIOS_Hazard"services are going to communicate"14:20
BIOS_Hazardmeaning with each other?14:20
BIOS_Hazardor with me, the API end user?14:20
srwilkerssdake_, sorry. got pulled away. pretty sure we've got it worked out. patches should be going in today14:20
sean-k-mooneyBIOS_Hazard: for allin one with out haproxy they are the same14:21
sean-k-mooneyBIOS_Hazard: you can use a different external api endpoint when you use haproxy14:21
BIOS_HazardThat makes sense14:21
BIOS_Hazardhowever, "Checking if kolla_internal_vip_address and kolla_external_vip_address are not pingable from any node" precheck fails when I use the one IP on my enp4s0 `network_interface`14:22
sean-k-mooneyfor an all in one test deployment * is fine but i would tighten it up in production14:22
BIOS_Hazardoh, so this precheck can be ignored?14:22
BIOS_HazardIs there a preferred means of skipping this check then?14:22
sean-k-mooneyyes the precheck dose not take acount of your haproxy setting14:22
BIOS_Hazardah14:22
sean-k-mooneyit a bug that should be fixed14:22
BIOS_Hazardthat makes sense then. the globals config does a good job of explaining how to do this then14:23
sean-k-mooneybut that should be skipped if not using haproxy14:23
BIOS_Hazardand the precheck is simply trollin me14:23
sean-k-mooneyyep14:23
sdake_srwilkers sweet thats the pvc issue then?14:23
BIOS_HazardIs there a place I can open a report for this all-in-one issue?14:23
BIOS_HazardI would be happy to submit my issue14:23
*** mgiles has joined #openstack-kolla14:24
BIOS_Hazardevery other part of this process has been smooth so far14:24
srwilkerssdake_, yeah, shouldve clarified. the patches are for the pvc issue. in terms of docs being ready, im hoping to have something up for review within a few days, but most likely post holiday14:24
sean-k-mooneynormally i would say open a bug here https://bugs.launchpad.net/kolla14:24
BIOS_Hazardand knowing now that this precheck can be ignored for all-in-one, I am back to zero real issues14:24
sdake_srwilkers cool thanks14:24
sean-k-mooneythough with the repo split it might be https://bugs.launchpad.net/kolla-ansible now14:24
BIOS_Hazard"the repo split"14:24
*** goldyfruit has joined #openstack-kolla14:25
sean-k-mooneyBIOS_Hazard: the ansible deployment code is being moved into its own repo kolla-ansibel14:25
*** tonanhngo has joined #openstack-kolla14:25
BIOS_Hazardah!14:25
BIOS_Hazardthanks for clarifying14:25
sean-k-mooneypreviously it was in the main kolla repo14:25
BIOS_Hazardmakes sense to separate14:25
BIOS_HazardI will use that one then per your recommendation14:26
*** tonanhngo has quit IRC14:26
sean-k-mooneythe prechecks are part of the ansible playbooks so any bugs with them should go to https://bugs.launchpad.net/kolla-ansible now14:26
BIOS_Hazardexcellent14:26
BIOS_Hazardand I will simply ignore these prechecks in my testing14:26
BIOS_Hazardeverything else set up with zero issues14:26
BIOS_Hazardso I would expect this to work14:26
*** jtriley has joined #openstack-kolla14:26
sean-k-mooneythe note in the docs say that the no ha proxy senario is not tested so this was obviosly not checked when the precheck was added.14:27
*** imcsk8 has quit IRC14:27
portdirectafternoon all o/14:27
srwilkershey portdirect14:27
*** liyifeng has quit IRC14:28
BIOS_Hazardsean-k-mooney: would I find that in the globals file? or in the online docs? (just want to see where I missed it)14:28
sean-k-mooneyBIOS_Hazard: actully looking at master you should not be executing that test https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/prechecks/tasks/port_checks.yml#L18-L3414:28
BIOS_Hazardoh, I checked out stable/newton14:28
portdirecthey srwilkers, looks like I've got a lot of k8s related logs to go through!14:28
BIOS_Hazardshould I be using master?14:28
BIOS_Hazardhmm, my precheck playbook has this same code14:29
BIOS_Hazardnow I suspect I missed a configuration to disable haproxy :\14:29
BIOS_Hazardsince this only runs if thats enabled (right?)14:29
*** imcsk8 has joined #openstack-kolla14:30
sean-k-mooneyyes you sibly need to set enable_haproxy: False in the global.yml14:30
sean-k-mooneyBIOS_Hazard: https://github.com/openstack/kolla/blob/stable/newton/doc/advanced-configuration.rst#ip-address-constrained-environments14:31
BIOS_Hazardhot damn! precheck successful14:31
sean-k-mooneynice14:32
sean-k-mooneyjust so you know the precheck can also be used multinode when you get to that point by add -i and specifying your multinode inventory14:32
BIOS_HazardExcellent :)14:32
BIOS_HazardAlright, looks like I am ready to deploy. Thanks again!14:33
sean-k-mooneyBIOS_Hazard: just so you are aware you last time i ran with enable_haproxy: "no" the deploy failed because seting up clustering for rabbitmq or mysql.14:34
sean-k-mooneyif you hit an issue with either let us know here because it may be a bug14:34
BIOS_Hazardwill do14:34
BIOS_Hazardand otherwise, I can implement multi-node, just seemed easier to do AIO for the first test14:35
v1k0d3nsdake_: ping14:35
*** srwilkers has quit IRC14:35
*** srwilkers has joined #openstack-kolla14:35
sean-k-mooneyyep all in one is simpler but as the docs say we dont regually test the enable_haproxy: "no" config so we only fix thing if people tell us its broken14:36
v1k0d3nsrwilkers mentioned you had some questions about halcyon?14:36
*** schwicht has joined #openstack-kolla14:36
*** Bico_Fino has quit IRC14:36
BIOS_Hazardsean-k-mooney: I think thats reasonable.14:37
*** Bico_Fino has joined #openstack-kolla14:37
*** srwilkers_ has joined #openstack-kolla14:39
sean-k-mooneyv1k0d3n: halcyon? is that the kubernetes thing you wrote?14:41
sean-k-mooneyv1k0d3n: this https://github.com/v1k0d3n/halcyon-kubernetes ?14:42
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add trove role  https://review.openstack.org/40058014:43
*** mmoster_ has quit IRC14:46
*** YuYangWang has quit IRC14:49
*** srwilkers_ has quit IRC15:04
v1k0d3nsean-k-mooney: yes15:06
*** srwilkers_ has joined #openstack-kolla15:06
v1k0d3nwell, there's the vagrant one...which uses the link you sent as a submodule.15:06
v1k0d3nso they can be used any way the operator really wants.15:06
openstackgerritSurya Prakash Singh proposed openstack/kolla-ansible: use uuidutils instead of uuid.uuid4()  https://review.openstack.org/39984715:07
v1k0d3ni should probably add a sample inventory for admins looking to just use halcyon-kubernetes.15:07
sean-k-mooneyv1k0d3n: so the vagrent one reuses halcyon-kubernetes for all the heavy lifting15:07
v1k0d3n(for things like bare-metal...since the vagrant one covers pretty much everything else non-bare-metal).15:08
portdirectv1k0d3n: that would be awesome - I know a few folks who would prob pick it up if you added that. :)15:08
v1k0d3nsean-k-mooney: yup. the vagrant one uses providers: currently libvirt, openstack and virtualbox (aws coming...it's just been a lower priority)...and then uses the submodule for doing the work.15:08
v1k0d3nboth are heavily influenced by variables, so the operator/developer as as many options as possible.15:09
sean-k-mooneyi was hopinging to extend the kolla-host playbook we have to deploy kubbernetes for kolla-kubernetess at some point but is halcyon going to be used for that instead?15:09
v1k0d3nportdirect: the AWS portion would be helpful?15:09
*** papacz2 has quit IRC15:10
v1k0d3nsean-k-mooney: halcyon installs kubernetes, correct.15:10
openstackgerritJeffrey Zhang proposed openstack/kolla: NO_MERGE: test mitaka branch  https://review.openstack.org/39387715:10
v1k0d3nit takes a kubeadm approach, since that is what will be supported by kuberenetes directly going forward.15:10
v1k0d3nwe're ok for now, since nobody is attempting to deploy "production" workloads of kolla-kube yet. as things firm up, we will shift support to kubeadm...(if needed) to make sure that is prod-ready in preparation for kolla-kube prod.15:11
v1k0d3nthere are so many things in flux at the moment.15:12
v1k0d3nit would be nice to have an etherpad or some sort of document just to keep track of the state of things currently.15:12
*** senk has joined #openstack-kolla15:12
portdirectv1k0d3n: I'd like that, but think a few other people are looking at 'bare-metal' esq deployments.15:12
*** msimonin has joined #openstack-kolla15:13
v1k0d3nfor instance, items about kubeadm...and where that's at. pvc's we're working with in 1.5.0beta1 because PetSets are no longer (in favor of StatefulSets...so there is a huge renaming effort going on for 1.5.0)...things like this impact the state of kolla0k8s.15:13
v1k0d3nportdirect: bare-metal works today. just use https://github.com/v1k0d3n/halcyon-kubernetes directly.15:13
v1k0d3nand oh! not that...15:14
v1k0d3nsean-k-mooney: ...15:14
v1k0d3ndont use v1k0d3n fork. use this one https://github.com/att-comdev/halcyon-vagrant-kubernetes15:14
sean-k-mooneyv1k0d3n: hi just in other channel reading back15:14
v1k0d3natt-comdev15:14
*** senk_ has quit IRC15:14
v1k0d3nportdirect: if you want...you can use our bare-metal solution for MaaS in kubernetes as well if you want :)15:15
v1k0d3nhttps://github.com/att-comdev/dockerfiles/tree/master/maas15:15
v1k0d3nin deployment.15:15
*** senk_ has joined #openstack-kolla15:15
sean-k-mooneyv1k0d3n: so currently the kolla host playbook can install the dependcies for kolla-ansible to deploy. i was thinking it might be nice to extend it to do the same for kolla-k8s but it might not be required15:16
portdirectv1k0d3n: nice - I'll check that out for sure :) I'm started moving away from foreman (was also running that in k8s... <- dont do that) and have been playing with pixiecore quite a bit recently.15:17
*** inc0 has joined #openstack-kolla15:17
inc0good morning15:17
*** senk has quit IRC15:18
v1k0d3nah, portdirect i was using pixiecore as well. it's nice. danderson created that repo, and i believe he's now at coreos possibly?15:18
v1k0d3nportdirect: were you using pixiecore for coreos installations?15:19
duonghqmorning inc015:19
v1k0d3nor just for the simplicity + api?15:20
v1k0d3nmorning inc015:20
srwilkers_hey inc015:20
*** schwicht has quit IRC15:20
inc0how it's going guys?15:21
*** diogogmt has quit IRC15:22
portdirectv1k0d3n: simplicity, though I've started to play with the api in the last week. I've basicly been using CentOS atomic, with an updated LTS Kernel for my stuff: https://github.com/portdirect/harbor/blob/latest/docker/mandracchio/mandracchio-repo-assets/assets/opt/mandracchio/harbor-host.json15:22
*** unicell has quit IRC15:25
v1k0d3nah! ok. good stuff!15:25
v1k0d3nthis can be intalled with maas too if you're interested15:26
BIOS_HazardThe all-in-one looks to have installed correctly. I was able to log into Horizon and everything. kolla is baller AF. thanks again for all the assistance!15:26
v1k0d3nalso...there is the bifrost/ironic stuff which will eventually make it's way into kolla-kube at some point.15:26
openstackgerritJeffrey Zhang proposed openstack/kolla: Bump OpenStack service version  https://review.openstack.org/39427115:28
sean-k-mooneyv1k0d3n: yep i keep leaning twords the idea of haveing a kolla-host repo that could be shared between kolla-ansibel and kolla-k8s to do all the host prep including biforst15:28
sean-k-mooneyi would also move ceph into that and maybe ovs at some point as it would allow use to do more advanced network configuration then what we do now15:29
sean-k-mooneyBIOS_Hazard: awsome15:30
portdirectv1k0d3n: yeah, I need to look at maas: I was using foreman as it provided a nice intergration with FreeIPA; which I was using for to enroll hosts for Kerberos and Cert management/provisoning via certmonger.15:30
sean-k-mooneyBIOS_Hazard: glad to hear you got it working15:30
BIOS_Hazard:)15:30
BIOS_HazardLooks like I forgot to enable ceph when I deployed15:30
BIOS_HazardCan I just enable it and re-run deploy?15:30
sean-k-mooneyBIOS_Hazard: you might need to run deploy then reconfigure15:31
sean-k-mooneyBIOS_Hazard: that is not really something we have tested15:31
BIOS_Hazardfair enough15:31
BIOS_Hazardim just gonna see what happens! I can always re-install :P15:31
sean-k-mooneyBIOS_Hazard: just so you know singel node ceph is not really a thing. you can do it but normally you should not15:32
*** papacz has joined #openstack-kolla15:32
*** unicell has joined #openstack-kolla15:32
BIOS_Hazardsean-k-mooney: understood. I just have some proof-of-concept stuff I want to try and this seemed like the ideal approach. I do understand that this approach is not production-compatible15:33
sean-k-mooneyBIOS_Hazard: well its not that. ceph upstream is not intended to run on one server it assumes 3 by default15:33
BIOS_Hazardoh, like it will fail?15:34
sean-k-mooneyBIOS_Hazard: https://github.com/openstack/kolla/blob/stable/newton/doc/ceph-guide.rst#managing-ceph has the extra stpes you need to do for all in one15:34
BIOS_Hazardsean-k-mooney: thanks!!!15:34
*** tonanhngo has joined #openstack-kolla15:34
sean-k-mooneyBIOS_Hazard: actully there are a few other steps but all covered in that guide15:34
inc0looking for someone knowing puppet15:35
*** tonanhngo has quit IRC15:36
BIOS_Hazardah yes, I remember seeing this now...15:36
BIOS_Hazard[global]15:36
BIOS_Hazardosd pool default size = 115:36
BIOS_Hazardosd pool default min size = 115:36
BIOS_Hazardthanks!15:36
sean-k-mooneyinc0: sorry one of the reason i like kolla is the lack of puppet15:37
*** schwicht has joined #openstack-kolla15:37
*** sayantani01 has joined #openstack-kolla15:38
inc0sean-k-mooney, yeah...but that puts as at disadvantage in writing support for stuff in infra15:38
inc0stuff we could really use15:38
sean-k-mooneyinc0: infra use ansible to orcestrate puppet right15:39
inc0yeah15:39
inc0but module itself has to be puppet unfortunatly15:39
sean-k-mooneythat makes my head hurt a little but i understand why they did it15:39
sdake_v1k0d3n ya srwilkers_ answered em thanks15:39
sean-k-mooneyinc0: one thing i would like to add to kolla is the ablity to deploy infra services e.g. zuul/nodepool nativly so that kolla could spin up an instace of the upstream ci plus provided the ci cloud15:40
sean-k-mooneyinc0: our ci master node is currently deployed with the puppet script from infra but we use kolla for the cloud15:41
sdake_v1k0d3n we have something that keeps track of state in openstack called launchpad :)15:42
inc0I think it's cool idea, just infra people are overworked even now15:42
sean-k-mooneyinc0: well i was thinking that our team might do it when we get time15:42
inc0"when we get time";)15:42
zhubingbingIn 20 minutes later we have a weekly meeting15:42
zhubingbing;)15:42
sean-k-mooneyinc0: we have higher proiry stuff for our ci but i added it too our ci backlog.15:43
*** prameswar has joined #openstack-kolla15:43
*** berendt has quit IRC15:44
sean-k-mooneyinc0: assuming we are both there we should discuss this at the ptg. by then i hope we will have capasity to look at doing it. it would be a nice addtion for pike15:45
*** berendt has joined #openstack-kolla15:45
v1k0d3nsdake_: you keep track of the state of kubernetes and helm in launchpad?15:46
sdake_v1k0d3n state of implementation yup15:47
openstackgerritJeffrey Zhang proposed openstack/kolla: DO_NOT_MERGE: TEST MASTER BRANCH  https://review.openstack.org/39989715:47
sdake_each review links to launchpad15:47
sdake_then reviews are reviewed by core reviewers15:47
sdake_and hashed out15:47
sdake_https://launchpad.net/kolla-kubernetes/+milestone/ocata-215:47
v1k0d3ni wouldn't even know where to begin keeping STATE tracking on other projects...15:47
v1k0d3nthis is very much in daily flux.15:48
sdake_nah not on other projects15:48
*** schwicht has quit IRC15:48
v1k0d3nok15:48
sdake_on kolla itself15:48
v1k0d3ni'm talking about other projects.15:48
v1k0d3nbecause kolla has impacts.15:48
v1k0d3nlike petset vs statefulset15:48
*** Bico_Fino_ has joined #openstack-kolla15:48
*** Bico_Fino has quit IRC15:49
*** Bico_Fino_ is now known as Bico_Fino15:49
v1k0d3nlike the current state and tracking of userland pvc claims for rdb.15:49
v1k0d3nthings like that.15:49
v1k0d3nthey impact sure, but kolla will need to work around.15:49
sdake_yup seems like a reasonable thing to track if someone cares to maintain it :)15:50
*** Serlex has quit IRC15:52
sean-k-mooneymaybe you could use tags to track it?15:53
Bico_Finosean-k-mooney: I upgrade the ironic-ui version to 2.1.115:53
Bico_Finosean-k-mooney: Got this error -> You have offline compression enabled but key "8745f6f37b1fe160569fae654663c71a" is missing from offline manifest. You may need to run "python manage.py compress".15:53
Bico_Finolooks easy to fix. ;)15:53
sean-k-mooneyBico_Fino: did you run the upgrade playbook to change the version or redeploy with that version?15:54
v1k0d3nso just as an example sdake_: https://github.com/kubernetes/kubernetes/issues/2743015:54
openstackgerritJeffrey Zhang proposed openstack/kolla: DO_NOT_MERGE: TEST NEWTON BRANCH  https://review.openstack.org/38698115:54
v1k0d3nso there is a hard break from 1.4 to 1.515:54
*** tonanhngo has joined #openstack-kolla15:54
Bico_Finosean-k-mooney: nope. Where is this upgrade playbook?15:54
v1k0d3nthe resource type from petset will no longer be available, and there is no plan to keep running workloads either.15:55
v1k0d3nit's a hard break. things like this need tracked, otherwise a project like kolla-k8s will be in a bug fix mode often.15:55
*** tonanhngo has quit IRC15:56
sean-k-mooneyBico_Fino: you can use kolla-ansible updgade to upgrade between releases but that was never tested for ironic as well ironic was broken untill this releases15:56
v1k0d3nkeeping an eye ahead in one place would help ease fixes later.15:56
Bico_Finosean-k-mooney: but that will work for plugins? Example: ironic-ui15:56
sean-k-mooneyBico_Fino: well for the plugins you can just run python manage.py compress in the template override i guess15:57
sean-k-mooneyupgrade works by upgrading the docker images so if the plugin is in that it might work15:57
Bico_Finosean-k-mooney: I just entered the horizon container and installed the plugin15:58
sean-k-mooneyin any case we actully dont use the horizon plugin for ironic in our enviroment so not sure15:58
inc0guess what's time is it!? its meeeeeting time!15:58
sean-k-mooneyBico_Fino: ah there is a way to do that at build time15:58
Bico_Finosean-k-mooney: the ironic-ui is working now, but the button Enroll Node don’t.15:59
Bico_FinoNeed do more tests.15:59
sean-k-mooney#openstack-meeting3?15:59
duonghqdo we still use meeting-4?15:59
sean-k-mooneyduonghq: i guess we should check the wiki15:59
duonghqwiki tell that we use no-416:00
sean-k-mooneycool16:00
duonghqinc0 sdake_ , ping16:00
openstackgerritsatya proposed openstack/kolla-ansible: Added separate interface for rabbitmq as rabbitmq requires primary interface to communicate  https://review.openstack.org/40132916:00
sdake_sup16:00
duonghqdo we use meeting4 as usual?16:00
*** senk_ has quit IRC16:01
sdake_yes duonghq16:01
*** jascott1 has joined #openstack-kolla16:01
sean-k-mooneyBico_Fino: https://github.com/openstack/kolla/blob/stable/newton/doc/image-building.rst#plugin-functionality discribes how to add plugins at build time16:01
duonghqhmm Heat guys still use that16:02
Bico_Finothanks sean-k-mooney16:02
*** Pavo has quit IRC16:02
Satya_hi16:03
Satya_please review https://review.openstack.org/#/c/401329/16:03
Satya_jeffrey there?16:03
Satya_hi sdake16:03
*** tonanhngo has joined #openstack-kolla16:03
*** schwicht has joined #openstack-kolla16:04
*** strigazi is now known as strigazi_AFK16:04
*** Pavo has joined #openstack-kolla16:07
*** magicboiz has joined #openstack-kolla16:09
*** lrensing has joined #openstack-kolla16:09
Bico_Finosean-k-mooney: fixed the Enroll issue, collectstatic is our friend. ;)16:10
*** cnf has left #openstack-kolla16:10
kristia__sdake_: Hi do you think gpu passthrough will work on openstack-ansible?16:11
*** DaveTurner has joined #openstack-kolla16:14
v1k0d3nso sdake_working on the pvc today.16:16
v1k0d3nmost likely tonight, honestly.16:16
sdake_v1k0d3n sweet - its key for 1.0.0 of kolla to be a reality16:17
v1k0d3ntalking with kubeadm folks on how i could add custom controller to it.16:17
sdake_rather kolla-kubernetes16:17
v1k0d3nyup16:17
*** eaguilar has joined #openstack-kolla16:21
*** mdnadeem has joined #openstack-kolla16:22
*** fguillot has quit IRC16:24
*** jgriffith_away is now known as jgriffith16:25
*** unicell has quit IRC16:25
*** fguillot has joined #openstack-kolla16:26
*** dkehn__ has joined #openstack-kolla16:28
*** Satya_ has quit IRC16:31
*** Satya_ has joined #openstack-kolla16:31
openstackgerritsatya proposed openstack/kolla-ansible: Added separate interface for rabbitmq as rabbitmq requires primary interface to communicat  https://review.openstack.org/40134116:33
*** srwilkers_ has left #openstack-kolla16:33
*** eaguilar has quit IRC16:36
*** kristia__ is now known as kristian__16:36
*** senk has joined #openstack-kolla16:37
*** zhubingbing__ has joined #openstack-kolla16:37
openstackgerritsatya proposed openstack/kolla-ansible: Added separate interface for rabbitmq as rabbitmq requires primary  interface to communicate  https://review.openstack.org/40134116:39
*** zhubingbing has quit IRC16:39
*** mdnadeem has quit IRC16:42
*** schwicht has quit IRC16:48
*** rmart04 has quit IRC16:50
Satya_Hi jeffrey4l16:56
Jeffrey4lSatya_, sup16:56
*** Pavo has quit IRC16:56
Satya_Please review https://review.openstack.org/#/c/401341/16:57
*** rhallisey_ has joined #openstack-kolla16:57
Jeffrey4lok16:57
Satya_Thanks16:57
Satya_i messed with the precious commit so abandoned that...16:58
*** Pavo has joined #openstack-kolla16:59
v1k0d3nand we shift back to here :)16:59
Pavomorning16:59
duonghqmorning Pavo17:00
*** sp__ has quit IRC17:00
portdirectok I'm quite up for documenting getting a kolla-k8s dev env set up (also morning Pavo)17:00
zhubingbing__hi17:00
zhubingbing__i have 2 problemes17:00
zhubingbing__about  elk17:01
zhubingbing__1.https://blueprints.launchpad.net/kolla/+spec/heka-deprecation17:01
PavoI agree portdirect17:01
zhubingbing__2.https://blueprints.launchpad.net/kolla/+spec/bp-elasticsearch-upgrade17:01
Pavoand morning duonghq and portdirect17:01
*** srwilkers_ has joined #openstack-kolla17:01
Pavoso........ who wants to walk me through a kolla-k8s deployment?17:04
*** athomas has quit IRC17:04
Pavoas in from start to finish17:04
pbourkezhubingbing__: what are the problems17:05
zhubingbing__1.https://blueprints.launchpad.net/kolla/+spec/heka-deprecation17:05
pbourkethat is a spec, not a problem :)17:05
zhubingbing__We have not considered this matter17:06
pbourkeok I get you17:06
portdirectPavo: I dont want to yet; as we dont yet have to docs together for the current state of the project - soon as we do I'd love you to be the guinea pig; your input and insight would be really valuble17:06
PavoI am game17:06
pbourkezhubingbing__: someone will need to research both, draw up a conclusion in a spec17:06
zhubingbing__We have not decided which one, so I can go to the test17:06
zhubingbing__ok17:06
Pavoand also game for anything else17:06
pbourkezhubingbing__: sounds good17:06
*** egonzalez90 has quit IRC17:07
Pavoalso got my TLS working from outside portdirect17:08
sdake_oenstack workflow http://docs.openstack.org/infra/manual/developers.html17:08
Pavofinally17:08
sdake_rather OpenStack workflow17:08
Pavocheck it out https://ddi.hopto.org17:08
sdake_this unfortunately doesn't cover blueprints much17:08
sdake_mgiles ^^17:08
Pavocan someone test the non https redirect for me at ddi.hopto.org17:08
mgilessdake thanks17:08
mgilesrather... sdake_ thanks.  :)17:09
*** sdake_ is now known as sdake17:09
sdakenp mgiles17:09
openstackgerritMerged openstack/kolla: Remove adding repo in magnum-base Dockerfile  https://review.openstack.org/40103217:10
openstackgerritMerged openstack/kolla: Bump OpenStack service version  https://review.openstack.org/39427117:10
portdirectwhoop! routing?17:10
duonghqsdake, who is take care helm packaging/neutron?17:10
zhubingbing__pbourke  thank you17:11
sdakeduonghq sign up for work item in the blueprints17:11
duonghqI'm try to grab something from work items17:11
duonghqbut neutron is in progress without assignee17:11
*** senk has quit IRC17:11
duonghqI'm confusing17:11
sdakeduonghq yup - workflow hard :)17:12
sdakeduonghq moment17:12
sdakehttps://launchpad.net/kolla-kubernetes/+milestone/ocata-217:12
duonghqas I see, it's kfox1111?17:12
*** rhallisey_ has quit IRC17:12
Jeffrey4lSatya_, done nit.17:12
sdakeclick the helm link17:12
*** rhallisey_ has joined #openstack-kolla17:12
sdakeit has work items in it17:12
duonghqsdake, I'm already on this bp, I mean the work items in this17:13
duonghqfor example: the neutron is inprogress w/o assignee17:13
sdakeduonghq scroll down17:13
sdakeduonghq to WORK ITEMS17:13
sdakeor search for unassigned17:13
duonghqI'm try to find out with item do not have anybody take care yet17:14
sdakethose are the ones that are unassigned17:14
sdakeduonghq right neutron is kfox111117:14
duonghq (unassigned)neutron: INPROGRESS <- somebody should update this17:14
duonghqya17:14
portdirectduonghq: it would be great if someone took on mariadb, and keystone17:15
sdakeduonghq duonghq can you update it since your there17:15
duonghqso I'll take the mariadb or nova, need some review17:16
duonghqI'll update tomorrow17:16
duonghqin the bp17:16
sdakeduonghq sounds good17:16
portdirectok - I can get going on keystone17:17
*** msimonin has quit IRC17:17
portdirectthen we will at least have a base for everything else above it :)17:17
duonghqportdirect, I can update the bp for you17:18
duonghqportdirect,  can I mark it as inprogress?17:18
portdirectduonghq: great - thanks (what TZ are you in?)17:18
duonghqUTC+7,17:19
portdirectduonghq: it will be in 8 hours :)17:19
duonghqportdirect, np17:19
rhallisey_sdake, did you get kube setup>17:19
sdakerhallisey_ nope and have to jet atm17:19
sdakefamily emergency17:19
sdakesee folks later17:19
rhallisey_kk17:19
duonghqcya sdake17:19
sdakeenjoy holidays if you got em17:20
portdirectbye sdake17:20
*** portdirect is now known as portdirect_away_17:21
openstackgerritMerged openstack/kolla: Install mkfs.vfat tool in ironic-conductor image  https://review.openstack.org/40070917:22
*** portdirect_away_ is now known as portdirect_back_17:23
duonghqI need some sleep, see you later guys17:26
*** duonghq has quit IRC17:27
*** hogepodge has joined #openstack-kolla17:28
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add trove role  https://review.openstack.org/40058017:28
*** diogogmt has joined #openstack-kolla17:29
*** matrohon has quit IRC17:30
*** hogepodge has quit IRC17:33
openstackgerritzhubingbing proposed openstack/kolla-ansible: Add trove role  https://review.openstack.org/40058017:34
*** zhubingbing__ has quit IRC17:37
pbourkevpnaas is fubared on the redhat base17:38
pbourkeim very surprised it works even for ubuntu17:39
*** Bico_Fino_ has joined #openstack-kolla17:39
*** Bico_Fino has quit IRC17:40
*** Bico_Fino_ is now known as Bico_Fino17:40
*** msimonin has joined #openstack-kolla17:41
*** shardy has quit IRC17:43
*** mkoderer has quit IRC17:43
*** hogepodge has joined #openstack-kolla17:43
pbourkeJeffrey4l: ping17:44
Jeffrey4lpbourke, pong17:44
pbourkeJeffrey4l: im just looking at your 'move glance precheck' change17:45
pbourkeJeffrey4l: whats the purpose of the new module17:45
openstackgerritMerged openstack/kolla: Update docs around TrivialFix  https://review.openstack.org/39771217:45
Jeffrey4lpbourke, yep. get all container status by using one module.17:45
openstackgerritsatya proposed openstack/kolla-ansible: Added separate interface for rabbitmq as rabbitmq requires primary  interface to communicate  https://review.openstack.org/40134117:45
Jeffrey4ljust like ansible's docker_image_facts17:45
Satya_hi jeffrey17:46
*** matrohon has joined #openstack-kolla17:46
Satya_accommodated the comment17:46
Jeffrey4lSatya_, hi. ( please use jeffrey4l rather than jeffrey, then i can get a notification ;) )17:47
Satya_sue :) jeffrey4l17:47
Jeffrey4lmuch better ;)17:47
Satya_Thanks17:47
pbourkeJeffrey4l: why not just kolla_docker17:48
Jeffrey4lkolla_docker just support one container and normally it failed when container is not exist.17:49
Jeffrey4lpbourke,17:49
pbourkeJeffrey4l: it would just be nice if we could get away without another module17:50
pbourkeJeffrey4l: but if you think not then I get it's ok17:50
pbourke*guess17:50
*** lrensing has quit IRC17:51
Jeffrey4li think it should be OK. extend kolla_docker will make it more complicated and kolla_container_facts make it simple enough. ;)17:52
v1k0d3nportdirect_back_:17:52
Jeffrey4li should be OK to write our own module, especially when it do not exist in official modules.17:52
v1k0d3nhey man, so for the changes for pvc ( inc0 you may be interested in this as well)...i'm just replacing the following:17:53
*** eaguilar has joined #openstack-kolla17:53
Jeffrey4lpbourke, ^^17:53
v1k0d3nin /etc/kubernetes/manifests/kube-controller-manager.json just make that line point to our image: "image": "quay.io/attcomdev/kube-controller-manager:v1.5.0-beta.1"17:53
v1k0d3nand boom. pvc works for rdb17:53
*** sdake has quit IRC17:54
*** kristian__ has quit IRC17:55
*** dave-mccowan has joined #openstack-kolla17:56
*** dave-mccowan has quit IRC17:57
*** alteriks has quit IRC17:58
*** ppalacios has quit IRC18:00
Pavoanyone know how to fix init-runonce when using TLS I am getting these errors18:00
Pavohttp://paste.openstack.org/show/590242/18:00
*** Pavo has quit IRC18:02
*** Pavo has joined #openstack-kolla18:03
*** senk has joined #openstack-kolla18:05
*** Bico_Fino has quit IRC18:07
sbezverkv1k0d3n: if you are going (I hope you do) push this fix upstream, please let me know Kubernetes issue ID..18:08
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: NO_MERGE: Testing  https://review.openstack.org/40137018:10
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible: NO_MERGE: Testing  https://review.openstack.org/40137018:11
*** senk has quit IRC18:13
*** pbourke has quit IRC18:14
*** pbourke has joined #openstack-kolla18:14
*** senk has joined #openstack-kolla18:14
*** senk has quit IRC18:17
*** eaguilar has quit IRC18:17
v1k0d3nyeah, really strange why the kube-controller just doesn't include the rbd fixes...18:19
v1k0d3nsbezverk: ^^18:19
*** portdirect_back_ is now known as portdirect_18:20
v1k0d3nyou saw my notes on getting it working though?18:20
portdirect_v1k0d3n: yo!18:20
v1k0d3nhey portdirect_18:20
v1k0d3nyou see my message?18:20
portdirect_no?18:20
v1k0d3nin /etc/kubernetes/manifests/kube-controller-manager.json just make that line point to our image: "image": "quay.io/attcomdev/kube-controller-manager:v1.5.0-beta.1"18:21
v1k0d3nthen rdb patches are in place18:21
v1k0d3nfor pvc18:21
portdirect_oh - sweet18:21
v1k0d3ngoing to update update halcyon18:21
*** eaguilar has joined #openstack-kolla18:21
v1k0d3nsbezverk: then you can use halcyon for the ceph rdb stuff you've been working on as well18:22
v1k0d3n:)18:22
*** unicell has joined #openstack-kolla18:24
*** unicell has quit IRC18:25
*** unicell has joined #openstack-kolla18:27
inc0ok, so gates and registry18:27
inc0Jeffrey4l, moved good point, if we implement registry in infra18:28
inc0depends-on cross project wont' work18:28
inc0as images in registry will always be out of merged changes18:28
inc0so you can't gate ansible code on unmerged change to images18:28
Jeffrey4lyep. we need support two case: when there is no depends-on in commit message, use the tarball registry directly. otherwise, build the image by using the depends-on kolla ref18:29
inc0that's going to be hard to implement:/18:30
*** msimonin has quit IRC18:31
sean-k-mooneyany reson not to tag images with the changeid18:32
sean-k-mooneythen for depends on you could pull the tagged images18:32
*** ppalacios has joined #openstack-kolla18:33
sean-k-mooneyJeffrey4l: inc0  ^^18:33
inc0sean-k-mooney, thing is, we want to pull images from unmerged change18:33
inc0and we won't keep all unmerged change images in registry18:33
*** ppalacios has left #openstack-kolla18:33
sean-k-mooneyhum ok if you dont keep all unmerge changes then yes that wont work18:34
inc0keeping unmerged changes in registry would destroy it;)18:34
inc0every patchset -> new build and upload18:34
inc0and it wouldn't take long to have 1000s of garbage images18:35
Jeffrey4li do not think tarball site can has enough disk for tagging images with changeid. since the tarball file will not be removed or override.18:35
sean-k-mooneyyes basically with a periodic task to delete untagged images18:35
inc0so no, we will only keep up-to-date master images18:35
sean-k-mooneyok then as Jeffrey4l said i guess you will need two workflows18:35
sean-k-mooneyone for normal commits and second for dependson18:36
inc0or we just agree to having red gates until kolla change merges18:36
inc0and do recheck after it merges18:36
inc0not ideal, but I for one think it will be managable18:36
inc0you need to wait for kolla merge before ansible code merge anyway18:36
inc0and gates aren't meant for debugging, you should have it tested locally18:36
Jeffrey4ldo u mean do not use depends-on in any way?18:37
inc0no, you do use depends-on18:37
inc0from ansible to kolla18:37
sean-k-mooneywell yes and no. unit tests basic deployment yes you should do locallly gates are for testing full intergration18:37
inc0just not for gates - to ensure that ansible change won't merge before kolla change18:37
Jeffrey4lhmm, let me think..18:37
inc0kolla change merges - > you do recheck on ansible patchset and gates should green-up18:38
Jeffrey4li strongly against this gates aren't meant for debugging, you should have it tested locally18:38
inc0what he said^18:38
inc0infra has limited resources as they are18:38
inc0let's not use them to avoid testing code locally18:38
sean-k-mooneyyes but oftten things break in the gate that work locally.18:39
sean-k-mooneywell not often. i test every locally before i push but not everyone does18:39
inc0yeah, but that will become apparent after kolla change emrges18:39
Jeffrey4lsean-k-mooney, yep.18:39
inc0only thing you lose with this solution is that you won't see this coming *before* change to kolla merges18:40
inc0Jeffrey4l, how about addint experimental gate to ansible with build and deploy18:40
inc0so you'll be able to call it on demand18:40
Jeffrey4linc0, nice solution ;)18:40
Jeffrey4llike it.18:41
inc0it will limit our options regarding scenerios tested18:41
inc0(as seting up registry fees up lots of resources and time and we can use it to increase number of scenerios)18:41
inc0but it's something18:41
Jeffrey4lacually depends-on should be edge case, there should few patch need this.18:41
inc0exactly18:41
*** jgriffith is now known as jgriffith_away18:42
inc0and we should not use gates for debugging anyway18:42
sean-k-mooneywell any patch chain that adds a new service will18:42
Jeffrey4lOK. let's make things more clear.18:42
sean-k-mooneybut yes they should be the minority of changes18:42
inc0sean-k-mooney, yeah, but I hope we won't add that many new services tbh;)18:42
inc0I think we have lots of them already18:43
Jeffrey4l1. in kolla, how the deploy gate image come from? should be build locally, right?18:43
inc0kolla will have image building18:43
Jeffrey4lsean-k-mooney, when adding new service, there should be no gate/job to test it.  so depends-on is useless.18:43
inc0not sure how we'll solve deploy in kolla, but I guess we can use zuul cloner for both deploy gates for ansible and k8s18:43
inc0yeah, Jeffrey4l is right, unless you create gate scenerio for your service in same patch, it's not going to do anything anyway18:44
sean-k-mooneyinc0: well kolla could use the master of kolla-ansible or you could say that kolla will not deploy at all jsut build but then you have an issue with docker changes breakin ansible18:44
inc0Jeffrey4l, but I think kolla changes should never have depend-on ansible change18:44
inc0which means change to image is good if master kolla-ansible works18:45
Jeffrey4linc0, deploy in kolla should use building image, and use zuul cloner to pull kolla-ansible or kolla-k8s.18:45
inc0if one of changes ongoing in kolla-ansible doesn't well, tough luck18:45
Jeffrey4lhrm18:46
sean-k-mooneyif you dont have a depens-on form kolla-ansible to kolla you could have  ansible chages merge that expect contianers that have not merged so depens on is needed18:46
inc0kolla is common core18:46
inc0it's baseline18:46
*** sayantani01 has quit IRC18:46
*** portdirect_ is now known as portdirect_away18:46
inc0changes to kolla takes precedence on changes to kolla-ansible18:46
*** sayantani01 has joined #openstack-kolla18:47
Jeffrey4linc0, technical yes. but depends-on make it easier. and when u using zuul-cloner, you can use depends-on18:47
inc0yeah, but again, deadlock18:47
inc0changes can't have depends-on each other18:47
inc0as zuul won't allow it to merge before other merges18:48
inc0and that creates deadlock18:48
Jeffrey4lwe can use depends-on in kolla. use tarball image in kolla-ansilbe/kolla-k8s18:48
sean-k-mooneywell if you never allow depens-on from kolla to kolla-* then no deadlock18:48
inc0so dependency should always go ansible > kolla18:48
inc0thats my point18:48
*** kristian__ has joined #openstack-kolla18:48
Jeffrey4linc0, ansible-> kolla only use by experimental.18:48
Jeffrey4lright?18:48
inc0so deploy gates in Kolla should *always* pull merged master from ansible18:48
inc0no, hold on18:49
inc0depends-on is more than just pulling code in gates18:49
*** cnf has joined #openstack-kolla18:49
inc0it's main role is that Zuul gates will -2 merge of changeX if it depends on unmerged changeY18:49
*** dave-mccowan has joined #openstack-kolla18:49
Jeffrey4lyep, you are right.  kolla -> kolla-ansible is bad.18:49
*** rhallisey_ has quit IRC18:49
inc0so you can put 2*+2+A on ansible change but it won't land until depends-on change lands18:49
sean-k-mooneyyep that is its main role18:50
inc0so kolla will always pull master ansible and k8s18:50
Jeffrey4linc0, get your point. so rule: never use depends-on in kolla project.18:50
inc0and kolla-ansible will use tarballed registry + experimental gate with build18:50
inc0yeah18:50
*** newmember has quit IRC18:50
inc0how does that sound?18:51
sean-k-mooneydepens on in kolla could be uses aslong as you dont depend on kolla-ansibel or kolla-k8s18:51
Jeffrey4lthe deploy jobs in kolla will never be voting, right? inc018:51
Jeffrey4lsean-k-mooney, yep.18:51
sean-k-mooneye.g. depens-on to glance would be fine for say a pending config change18:51
inc0Jeffrey4l, I don't expect them to, no18:51
inc0but if never? dunno18:52
Jeffrey4lsean-k-mooney, but kolla depends-on nothing actually.18:52
inc0not initially18:52
*** eaguilar has quit IRC18:52
*** kristian__ has quit IRC18:53
Jeffrey4linc0, how about in kolla-ansible use build image when depends-on exist in commit message?18:53
sean-k-mooneyyes but as the config gen code will live in kolla if i am extending kolla for an unmerged config change i can and should use depends-on to track that18:53
sean-k-mooneyanyway that beside the point sorry18:53
inc0Jeffrey4l, then it can't be voting18:53
*** sayantani01 has quit IRC18:53
inc0I don't want to change voting gate logic based on commit message..18:54
inc0so, I'd rather have separate gates18:54
inc0for build18:54
Jeffrey4li do not it change anything.18:54
Jeffrey4lthe ansible changes won't be merged until its depends docker change is merged.18:55
sean-k-mooneywhy not only execute the deploy in the gate pipeline and just to do the image build in the check pipeline18:55
*** sayantani01 has joined #openstack-kolla18:56
inc0sean-k-mooney, most of the time we won't need to build images at all18:56
Jeffrey4lsean-k-mooney, for kolla project?   isn't there a rule: gate pipeline should be exist in check pipeline?18:56
sean-k-mooneyso before you merge a docker change it will pull master or stable/X ansible and test it can deploy but normaly it will only check it can build18:56
inc0why waste time?18:56
*** sayantani01 has quit IRC18:56
*** sayantani01 has joined #openstack-kolla18:56
sean-k-mooneyfor kolla. it should save time as you dont always have run the deploy job18:57
Jeffrey4linc0, if we do not support depends-on, we break the zuul voting/merge progress, imho18:57
*** DaveTurner has quit IRC18:57
sean-k-mooneychanges to kolla would only trigger the build job and would only trigger deploy job after +2+w. just a taught18:58
Jeffrey4lin in default.18:58
inc0no, depends-on will work just fine18:58
Jeffrey4lsean-k-mooney, i think it will slow down the merge speed.18:59
inc0sean-k-mooney, no, we need to know if it deploys before +218:59
*** dave-mcc_ has joined #openstack-kolla18:59
sean-k-mooneyinc0: even if its non voteing?18:59
inc0sean-k-mooney, what's value of it if it's not voting and only runs after merge?18:59
Jeffrey4lsean-k-mooney, we want all jobs voting, inc0 right?18:59
inc0"oh...we merged broken code"19:00
inc0Jeffrey4l, I don't think we'll have all jobs voting19:00
inc0but I want to have more of them19:00
sean-k-mooneymy point was it should be voteing if we only run it on merge19:00
Jeffrey4lor at least all job green.19:00
inc0like...build binary won't be voting anytime soon19:00
inc0all jobs green - agree19:00
sean-k-mooneyi taught you were saying the deploy would be non voting for kolla19:00
inc0deploy will be non voting for kolla19:01
inc0but will be information for cores19:01
Jeffrey4lsean-k-mooney, after two day, i got +w, but i found deploy gate red, because i made a mistake ( like wrong shell script syntax error ).  then i start from beginning.19:02
*** dave-mccowan has quit IRC19:02
*** prameswar has quit IRC19:02
Jeffrey4lthat will be terrible.19:02
*** msimonin has joined #openstack-kolla19:03
sean-k-mooneythats valid.19:03
sean-k-mooneyis the intent for the deploy jobs to be voteing eventually?19:04
Jeffrey4lsean-k-mooney, in kolla project, i do not think so.19:04
Jeffrey4lif the deploy gate failed, it may cause dead lock .19:04
Jeffrey4lkolla changes red, and kolla-ansible changed red, too.19:05
Jeffrey4lso kolla only enable build image voting. and kolla-ansible/kolla-k8s only enable deploy job voting.19:05
sean-k-mooneyif +2 is depentend on deploy gate passing in kolla then it is effectivly voteing but i think we are rat holing19:05
Jeffrey4linc0, again please re-consider the support depends-on in kolla-ansible or kolla-k8s. i still it should be OK.  even though the gate broken, we can push a fix in kolla, then the gate will be green.19:07
inc0Jeffrey4l, depends on will work on kolla-ansible -> kolla19:08
Jeffrey4lwithout experimental?19:08
inc0I'd keep build gates experimental19:09
inc0because most of changes wont ever need that19:09
sean-k-mooneyexperimental for kolla-ansible that is right inc0?19:09
Jeffrey4lwait. add build gate in kolla-ansible?19:09
inc0and few that needs that will have voting gates red until kolla change merges19:09
inc0ok, again, problem is: we have change (changeX) in kolla-ansible that requres kolla change (changeY)19:10
inc0so state 1. changeX and changeY not merged19:10
inc0voting gates in changeX will be red because we have image missing or something19:11
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: WIP Hierarchical approach for helm charts  https://review.openstack.org/40139419:11
inc0but we can call check experimental and we'll call version of jobs that will also build images and pull changeY19:11
inc0so we'll have voting gates red and experimental gates green (or red, but then you know you need to fix stuff)19:12
inc0then, changeY merges in kolla19:12
inc0and all the gates in changeX becomes green, free to merge19:12
*** msimonin1 has joined #openstack-kolla19:12
sean-k-mooneyyes that workflow should work fine19:13
sean-k-mooneyit will also work for k8s19:13
inc0yeah19:13
Jeffrey4linc0, all the issue is : we need run `recheck` after change Y is merged.19:13
inc0yeah19:13
inc0not a big deal imho19:13
inc0especially that our gates will have much more scenerios than experimental19:14
sean-k-mooneywell wont zull to a merge check after the depens-on change has merged19:14
inc0because we'll have more time in gates for valuable tests19:14
sean-k-mooneycould you trigger the recheck automatically?19:14
*** kristian__ has joined #openstack-kolla19:14
inc0not sure, maybe19:14
*** jgriffith_away is now known as jgriffith19:14
inc0either way, really not a big deal19:14
Jeffrey4land when using depends-on, may be all the job except experimental is a wast :(19:14
*** msimonin has quit IRC19:14
Jeffrey4ljust fyi.19:15
sean-k-mooneyits only a wast if the depens-on is to kolla19:15
Jeffrey4li am Ok with the current implement this :)19:15
Jeffrey4lkolla-ansible should only support kolla. ( it do not use others project's git url )19:16
*** kristian__ has quit IRC19:16
inc0Jeffrey4l, waste, yeah, not a bit waste tho19:16
*** kristian__ has joined #openstack-kolla19:16
Jeffrey4lanyway, let's implement this ;)19:16
Jeffrey4lso conclusion:19:17
inc0cool, I'll keep talking to infra about getting registry up one way or another19:17
Jeffrey4lin kolla project:  1. voting build source gate ( done )19:17
Jeffrey4l2.  push tarball after merged.19:17
inc0or 6 different tarballs19:17
Jeffrey4l3. in deploy gate, using build19:17
Jeffrey4linc0, yep.19:18
Jeffrey4lthat's all, anything else?19:18
inc0well, if 3 means adding deploy gates to kolla - non voting19:18
inc0than that's all19:18
Jeffrey4l4. deploy jobs will be non-voting19:19
inc0yeah19:19
Jeffrey4l in kolla-ansible project:   1. pull image from tarball site19:19
Jeffrey4l2. add experimental jobs to use build image19:19
Jeffrey4l3. enable deploy+source gate19:20
Jeffrey4lanything else?19:20
sean-k-mooneyJeffrey4l: why pull from tarball site?19:20
Jeffrey4lsean-k-mooney, that why we want set docker registry in infra19:20
sean-k-mooneyyes but you would pulll the images from the regestry19:21
sean-k-mooneynot tarballs of kolla19:21
inc0sean-k-mooney, if we run registry in infra19:21
inc0tarball == tarball of built images19:21
Jeffrey4lsean-k-mooney, ^^ yes19:21
harlowjaqq, if i wanted to also get the test dependencies into images, whats the best way19:21
inc0sean-k-mooney, either way, this is only couple of solutions to "how to have registry in infra"19:22
harlowjaseems like the usual install only installs the non-test dependencies19:22
*** fragatina has quit IRC19:22
inc0harlowja, what do you mean by test dependencies?19:22
harlowjahttps://gist.github.com/harlowja/5fabeed44f957859a099ca33ecc7929719:22
Jeffrey4lpip install -r test-requirement.txt?19:22
harlowjaya19:22
harlowjaJeffrey4l i'm doing that19:22
sean-k-mooneya tarbasll of all built images will take much more space the storing in a regestry as you loose the space saving of the deltas19:22
Jeffrey4lsean-k-mooney, tarball means /var/lib/registry tarball file.19:23
harlowjabut Jeffrey4l since pip has a shitty dep resolver, u can't really do that by itself and expect it to be correct19:23
Jeffrey4lit shouldn't that big.19:23
inc0it will be as big as registry itself...;)19:23
harlowjahttps://github.com/openstack/kolla/blob/master/docker/glance/glance-base/Dockerfile.j2#L36 (seems like it just installs the project requirements, not say the test ones)19:23
Jeffrey4l2 - 3 GB may be?19:23
inc0maybe less even19:24
sean-k-mooneyok so you are just taring up the regestry. you are not running a regestry and pulling the images indivgually over http19:24
inc0per distro19:24
inc0sean-k-mooney, correct19:24
Jeffrey4lsean-k-mooney, yep.19:24
Jeffrey4lharlowja, why u need that?19:24
sean-k-mooneyok that was the disconnect19:24
Jeffrey4lsean-k-mooney, sorry?19:25
sean-k-mooneyi was assuming you would just push to a regsitry as normal and pull as normal19:25
harlowjaJeffrey4l to be able to test that the apps inside the images unittests still work post-build19:25
inc0sean-k-mooney, it was idea about "how to enable registry in infra without actually installing it there"19:25
*** lrensing has joined #openstack-kolla19:25
Jeffrey4lharlowja, you can add all you need in openstack-base image. because all the pip requirements exist in upper-constrain.txt file.19:26
harlowjai don't want to have to install the whole upper-constraints file, lol19:26
Jeffrey4lharlowja, run unittest in doker by using kolla? interesting.19:26
*** sayantani01 has quit IRC19:26
harlowjaya, https://gist.github.com/harlowja/971645fd17013c9fcd13f37aed3c0d34 (what our jenkins is doing)19:27
Jeffrey4lharlowja, it will be hard to install in each service. because you may need install some develop packages.19:27
sean-k-mooneyinc0: i see. rsync might work better. basically build in registry into the base image nightly via node pool, rsync latest regstry as part of kolla-ansible job19:27
harlowjaJeffrey4l i don't mind hard19:27
harlowjalol19:27
inc0sean-k-mooney, so tarballs.o.o already have infra for it19:28
sean-k-mooneyinc0: on merge push delta with rsync to infra hosting19:28
inc0we just say "after merge I want this file uploaded"19:28
Jeffrey4lre "after merge I want this file uploaded"  we need this. otherwise , it may cause kolla-ansible failed.19:28
Jeffrey4lfor one day.19:28
sean-k-mooneyinc0: if it will prune all the old versions for you automatically then ya that will work too19:28
inc0it will literally override full registry19:29
harlowjaJeffrey4l http://i.imgur.com/Miu2rSp.png what our jenkins is currently doing19:29
sean-k-mooneyJeffrey4l: i was suggesting "after merge rsync delta"19:29
Jeffrey4lnamed the file like: registry_centos_source_master.tar.gz19:29
sean-k-mooneyinc0: yes the only down side is every kolla-ansibel build will also have to download the full regestry19:30
Jeffrey4lsean-k-mooney, does rsync possible right now? if so, it will be nice.19:30
sean-k-mooneyinc0: and every merged kolla change will have to upload it.19:30
sean-k-mooneyJeffrey4l: im not sure. how are the docs uploaded19:30
inc0sean-k-mooney, yup, well, not ideal19:30
Jeffrey4liirc, it use scp.19:30
sean-k-mooneyscp would work for the registry too19:31
sean-k-mooneyrsycn can run over it and reduce the amount of bandwidth used19:31
Jeffrey4lbut it is not delta transport.19:31
Jeffrey4lyep19:32
sean-k-mooneybasically with tarballs its a 2-3G upload everytimes a kolla change and a 2-3GB download for every time a kolla-ansible job runs19:32
*** schwicht has joined #openstack-kolla19:32
*** msimonin1 has quit IRC19:33
sean-k-mooneywith rsyc its a couple of megs hopfully since previous nights build19:33
inc0sean-k-mooney, but for rsync we need different hosting19:33
inc0not tarballs.o.o19:33
Jeffrey4lwe can specify the tarball's image. like we won't need bifrost right now. then we can not push it into tarball site.19:33
sean-k-mooneyyes perhaps.19:34
sean-k-mooneywell rsync can be an optimsiate at a later date19:34
inc0nah, I'd keep all of them19:34
*** eaguilar has joined #openstack-kolla19:34
inc0simply because when someone actually will need bifrost19:35
inc0I don't want to change infra19:35
Jeffrey4lfyi, during scp, it use this plugin https://ant.apache.org/manual/Tasks/scp.html19:35
Jeffrey4linc0, sean-k-mooney i added all conclusion in here https://etherpad.openstack.org/p/kolla-repo-split19:39
inc0thanks Jeffrey4l19:44
inc0I'll keep digging registry19:44
sean-k-mooneyinc0: what is the current issue with the registry by the way?19:45
Jeffrey4lcool19:45
sean-k-mooneyyou posted a review before?19:45
inc0sean-k-mooney, decision on direction we want to take with infea19:45
sean-k-mooneyah ok19:45
inc0either they host normal registry - then we need to create puppet for installing it19:45
inc0or tarball hack19:45
inc0then we need to implement it ourselves19:45
sean-k-mooneyi see.19:46
sean-k-mooneyi would personally install docker and just spin up a regesty in docker.19:47
sean-k-mooneyaparently there is already a docker puppet module https://puppet.com/blog/simplify-managing-docker-puppet19:48
sean-k-mooneyhttps://github.com/garethr/garethr-docker19:49
jrich523hey guys, i realize this is mildy off topic, but im trying to hit the API for login and im going to the /v3/auth/token with a post based on a payload defined in the docs, and its telling me i need to auth first... i though thats what i was doing?19:49
*** dave-mcc_ has quit IRC19:49
inc0jrich523, I'd say check if password is correct:)19:53
jrich523hmm well, it is, i copy pasted it :)19:53
jrich523seems like an odd error for that tho... but i guess based on the error msgs i've seen, thats normal for openstack lol19:54
jrich523"The request you have made requires authentication."19:54
inc0jrich523, that's how error "wrong password" looks like too19:54
jrich523hmm ok19:54
inc0clients will display it with any auth problem19:55
jrich523perhaps its the domain/scope, tried to leave it as default, i'll try being specific19:55
inc0check OS_AUTH_USERNAME and stuff19:55
inc0envs19:55
jrich523lol awesome19:55
jrich523yup im pulling that from the RC file19:55
inc0yeah it's not great error handling19:55
jrich523making calls from powershell, read in the RC file to grab what i need to auth19:55
inc0maybe powershell adds some strange windows'y whitespaces?;)19:56
*** fragatina has joined #openstack-kolla19:56
jrich523lol perhaps, but probably not.. i've used powershell against a LOT of REST api's19:56
inc0I never used it, so I'm jsut shooting blind19:57
jrich523arent we all :)19:57
inc0hear hear19:58
jrich523boom!19:58
jrich523using the domain rather than default did it19:58
jrich523hmm, weird since the default domain is the domain im using, either way, thanks!19:59
inc0np, glad it works19:59
sean-k-mooneyinc0: im not a puppet guy but naively http://paste.openstack.org/show/590252/ should be all that is needed no?20:00
inc0well we want to add auth too20:00
inc0but yeah, it's not like hard either way20:00
inc0running registry outside docker is super easy too20:01
inc0apt-get install docker-registry -> docker-registry path/to/config/file20:01
inc0or service docker regsitry start20:01
sean-k-mooneyoh ok. when ever i have had to use puppt i just made it exec bash so im a bad person but it worth it to not learn ruby20:02
*** tonanhngo has quit IRC20:05
inc0lol20:06
jrich523lol... it responded, but i dont see the token object in the response as the docs say20:07
jrich523nvm i think i know what they did20:07
*** sayantani01 has joined #openstack-kolla20:09
*** msimonin has joined #openstack-kolla20:12
*** inc0 has quit IRC20:16
*** sayantani01 has quit IRC20:16
*** sayantani01 has joined #openstack-kolla20:17
*** eaguilar has quit IRC20:19
*** msimonin has left #openstack-kolla20:25
*** fragatina has quit IRC20:30
openstackgerritPaul Belanger proposed openstack/kolla: DO NOT MERGE  https://review.openstack.org/40141220:38
*** pabelanger has joined #openstack-kolla20:38
openstackgerritsatya proposed openstack/kolla-ansible: Added separate interface for rabbitmq Enable rabbitmq to listen on different interface when primary hostname not based on api_interface.  https://review.openstack.org/40134120:39
*** v1k0d3n has quit IRC20:46
*** newmember has joined #openstack-kolla20:47
openstackgerritPaul Belanger proposed openstack/kolla: DO NOT MERGE  https://review.openstack.org/40141220:47
*** Satya_ has quit IRC20:49
*** sayantani01 has quit IRC20:51
*** flaper87 has quit IRC20:52
*** sayantani01 has joined #openstack-kolla20:53
*** sdake has joined #openstack-kolla20:54
sdakehey peeps20:54
sean-k-mooneyhey :) it pretty quite at the momen20:56
sean-k-mooneymoment20:56
sdakewhich moment20:56
sdakeor quiet :)20:57
sean-k-mooneymy spelling should never be trusted20:57
pabelangerfor the gate-kolla-dsvm-build-ubuntu-binary-ubuntu-xenial-nv job, where would the images be stored on the filesystem it produces? /var/lib/docker?20:59
sean-k-mooneyyes21:00
sean-k-mooneybasically /var/lib/docker/image/btrfs21:01
*** fragatina has joined #openstack-kolla21:01
sean-k-mooneythe last part is storage driver dependent21:02
*** lrensing has quit IRC21:04
*** schwicht has quit IRC21:04
pabelangerthanks21:06
-openstackstatus- NOTICE: Due to a problem with the cinder volume backing the log server, jobs are failing with POST_FAILURE. Please avoid issuing 'recheck' commands until the issue is resolved.21:08
*** ChanServ changes topic to "Due to a problem with the cinder volume backing the log server, jobs are failing with POST_FAILURE. Please avoid issuing 'recheck' commands until the issue is resolved."21:08
openstackgerritAlexis Rivera proposed openstack/kolla-ansible: renaming-kolla-build-command  https://review.openstack.org/40100521:12
*** inc0 has joined #openstack-kolla21:13
*** unicell has quit IRC21:14
*** jtriley has quit IRC21:15
*** unicell1 has joined #openstack-kolla21:21
pabelangerso, if I wanted to export an image, looks like: docker save lokolla/ubuntu-binary-base | gzip > lokolla_ubuntu-binary-base.tar.gz would be an example21:22
inc0pabelanger, we don't want to do that21:23
inc0reason being21:23
pabelangerright, I am just testing docker commands21:23
inc0we have ubuntu binary and ubuntu source21:23
inc0ok21:23
pabelangerlooks like it sqashs things21:23
inc0it does21:23
inc0but on the other hand21:23
inc0if you look at docker registry storage volume21:24
inc0it understands layers21:24
*** fguillot has quit IRC21:24
inc0so it will be lot smaller than sum of images21:24
inc0currently in our build gates we always download ubuntu base image21:24
pabelanger/var/lib/docker is currently 7gb21:24
pabelangerand looks to be a loopback mount21:25
inc0pabelanger, depends on storage driver21:25
inc0docker info <- this command should tell you which storage driver you use21:25
pabelangerbtrfs21:25
inc0ok, that's cool21:25
inc0ubuntu xenial I presume21:26
pabelangerthis is a gate-kolla-dsvm-build-ubuntu-binary-ubuntu-xenial-nv vm btw21:26
pabelangerI held a node to poke at it21:26
*** schwicht has joined #openstack-kolla21:26
inc0ok21:26
inc0so if we use full registry21:27
pabelangerso, step 1, could be unmount /var/lib/docker, compress and store on tarballs.o.o. To see how much time that takes21:27
inc0I wouldn't do that21:27
pabelangerif it is a really long time, then I say we move back to docker-register in infra21:27
inc0I'd rather run local registry21:27
inc0push images there21:27
inc0and tarball it's storage21:27
pabelangerokay21:27
inc0it will be less error-prone21:28
pabelangerso, after you build, import into local registry then export21:28
pabelangerthen upload that data21:28
pabelanger?21:28
inc0yeah21:29
pabelangerokay21:30
inc0I'll try to build ubuntu source, upload it to fresh registry21:30
inc0and will check how much tarball will take21:30
*** schwicht has quit IRC21:31
inc0pabelanger, we don't have swift available anywhere right?21:32
pabelangerinc0: if you dump them into the images folder, I can setup the publisher macro today21:33
pabelangerinc0: no21:33
inc0I'll put them in some better directory - I can work that one out21:33
pabelangerinc0: so, $WORKSPACE/images or name of choice21:34
inc0good thing about that all - we already run docker in gates, so running registry is literally single command21:34
pabelangerbut needs to be under $WORKSPACE for publisher to work21:34
inc0$WORKSPACE/images it is21:34
pabelangerI'll setup macro now21:35
*** Jeffrey4l has quit IRC21:35
inc0so if that's how we do it21:35
inc0we'll have 6 different tars there21:35
inc0binary+source * ubuntu+oraclelinux+centos21:35
*** Jeffrey4l has joined #openstack-kolla21:35
inc0I'll make sure that tar.gz will be named correctly21:36
inc0each gate will upload different flavor21:36
inc0and each deploy gate will download correct flavor21:36
inc0to minimize amount of data21:36
*** f13o has joined #openstack-kolla21:36
pabelangerYes, the publisher will match *.tar.gz, storing them in tarballs.o.o/(openstack-)kolla/images21:37
pabelangercan't check what format you use today, since our drive is offline21:37
inc0cool21:37
*** schwicht has joined #openstack-kolla21:37
inc0tar.gz works21:37
*** mgiles has quit IRC21:39
*** schwicht has quit IRC21:39
*** schwicht has joined #openstack-kolla21:40
inc0pabelanger, ok can't build source because tarballs are down;)21:41
*** MarcisK has joined #openstack-kolla21:47
*** srwilkers_ has quit IRC21:51
MarcisKHi, guys! Couple of months ago I asked here if there are any plans on implementing SELinux for nova-compute. Last time there were no plans on doing that. Are there any updates regarding SELinux?21:51
*** jtriley has joined #openstack-kolla21:52
*** schwicht has quit IRC21:55
inc0MarcisK, it's not about lack of plans21:56
inc0it's about lack of people to do it:)21:56
inc0we want it, just nobody had written this yet21:56
sdakekolla runs on selinux does it not?21:56
inc0well, it requires to not be enforcing21:57
sdakethe gate enables selinux21:57
inc0afair21:57
sdakepabelanger could verify - my understanding is centos enables selinux by default21:57
sdakeand our gate scripts do not disable it21:57
MarcisKThe biggest issue is with nova-compute. Normally libvirt would put every instance into it's own "selinux domain", isolating it from another instances and protecting the host from virtualization security bugs21:58
inc0sdake, either you're wrong or this doc is https://github.com/openstack/kolla/blob/d75847772d0e880329eef5867caf4b87035d2ae0/doc/security.rst#selinux21:58
MarcisKBut as far as I've seen - in kolla all libvirt guests are running into a same selinux domain21:58
*** jtriley has quit IRC21:59
sdakeinc0 doc is wrong pretty sure21:59
sdakelet me grep repo for selinux moment21:59
inc0I'm not sure, I'm ubuntu guy21:59
sean-k-mooneyim not sure selinux in its default config on centos will work.22:00
sean-k-mooneyi know that at least on ubuntu you sometimes have apparmor issues with libvirt22:01
sdakeya kolla-ansible does not disable selinux22:01
inc0sdake, ofc it doesn't22:02
sdakethose docs re selinux are old22:02
inc0but it may require22:02
sdakei mena the gate scripts there of22:02
inc0it to be not enforcing22:02
inc0kk22:02
sdakeand i'm certain infra enabled selinux on all images22:02
sean-k-mooneysdake: selinux may be disabled in the image building22:02
sean-k-mooneysdake: after all devstack requires selinux to be off22:02
*** Pavo has quit IRC22:02
sdakethat is because devstack touches a whole lotta files22:03
*** Pavo has joined #openstack-kolla22:03
sdakeand doesnt do it through proper channels22:03
sdakeso MarcisK the short answer i think from our discussion is kolla works on selinux22:03
sean-k-mooneydoes kolla have custom images or does it use the default infra images22:03
MarcisKRDO worked just fine with SELinux. Both controller and compute.22:03
MarcisKI'm now deploying kolla on a lab machine. Will provide you with additional details soon.22:04
sdakesean-k-mooney we use default infra images, there is no way I know of to make our own "custom images"22:04
inc0sdake, btw read through log here22:04
sdakeas far as libvirt putting every instance into its own security domain22:04
sdakeno clue on that22:04
inc0around 3hrs ago22:05
inc0me, Jeffrey4l, sean-k-mooney and pabelanger devised a way to enable registry-like behaviour22:05
inc0in infra22:05
sdakenice22:05
sdakei'll take your word for it :)22:05
sdakenot super interested in working on gating personally22:06
*** tonanhngo has joined #openstack-kolla22:06
*** tonanhngo has quit IRC22:08
*** BIOS_Hazard has quit IRC22:10
sean-k-mooneydoes kolla support osp currently?22:10
*** v1k0d3n has joined #openstack-kolla22:10
sean-k-mooneyas in RHEL osp as a build target22:11
MarcisKBtw, guys, while my kolla setup is getting ready. Are there any known large production deployments of kolla?22:13
*** tonanhngo has joined #openstack-kolla22:13
britthouserI believe its untested sean-k-mooney.  The package names should be the same as CentOS.  And the RHEL container is *supposed* to inherit the entitlements from the host.  But we’ve had issues with that in the past.22:13
britthouserSo it seems like it would be straightforward, but I’m betting there are few devils in the details.22:14
*** tonanhngo has quit IRC22:14
inc0MarcisK, how much is large?:)22:14
sean-k-mooneybritthouser: the reason i ask is for ovs-dpdk. its part of osp but not in rdo on centos22:14
MarcisKinc0: good question :) for example, at least 30 compute nodes?22:15
inc0hah, I was thinking 200+, yeah, we have several ~10022:15
inc0that I know of22:15
inc0but I expect that there is much more22:15
inc0Pavo, how's your "small" PoC going?;)22:16
inc0if you think of images22:16
inc0not ansible part22:16
inc0then there is one rather big I know22:16
inc014000 servers22:16
inc0or something like that22:16
*** harbor has joined #openstack-kolla22:17
sean-k-mooneyinc0: can you remeber if vlan tenant networks were tested in osic or in general?22:17
MarcisKinc0: thanks :)22:18
*** slagle has quit IRC22:18
inc0sean-k-mooney, I think we didnt test vlan22:18
inc0in general yeah22:18
inc0but you need to play around nutron ini22:19
sean-k-mooneywe dont actully document how to enable vlan tenant networks22:19
sean-k-mooneyya i am doing that now22:19
inc0no I dont think so22:19
inc0we should22:19
*** harbor is now known as portdirect__22:19
sean-k-mooneyim also going to enable the conntrack security group dirver that way but should i make that an option in ansible?22:20
pabelangersdake: yes, centos-7 has selinux enforced22:20
pabelangerhttp://nodepool.openstack.org/dib.centos-7.log is the log of our builds22:20
inc0sean-k-mooney, I don't see why not22:20
sean-k-mooneyinc0: well is more how much shold be done via config override and just document and how much should be done as ansible/template change and variable in global.yml22:21
inc0pabelanger, registry for ubuntu binary takes 2.7Gig22:23
inc0after tar22:23
inc0source should be little less22:23
sean-k-mooneyhow fast are the network connection on the vms in the gate?22:24
sean-k-mooney1G?22:24
pabelangerfirst step is to get it onto tarballs.o.o22:24
pabelangerthen we can import it into afs22:24
inc0pabelanger, tarballs are local to regions or hosted somewhere?22:24
pabelangereach region then has a cache22:25
portdirect__sbezverk: ping22:25
inc0cool, upload won't be that common22:25
pabelangertarballs.o.o is in rackspace22:25
pabelangerbut each cloud region has a mirror22:25
inc0ok, so most of the time we'll have nice 10Gig22:25
pabelangermoving them to the mirror will address bandwidth issues22:25
inc0pabelanger, any way for gate to know if it's merge-gate or just normal check?22:26
inc0we wouldn't tar-gz these things every time22:26
inc0it takes couple minutes to tar.gz whole repo22:27
*** f13o has quit IRC22:27
pabelangerI am building a post pipeline job to do that22:27
pabelangerso, after code is merged into git, we build and upload them22:28
inc0cool22:28
pabelangershould be uploaded shortly22:28
inc0let me know where you want code to be22:28
pabelangerwill uses experimental first, so we can iterate on testing22:28
openstackgerritBorneMace proposed openstack/kolla-ansible: Ignore dom0 qemu processes during destroy  https://review.openstack.org/39920322:28
pabelangerthen, once good. move it into post22:28
inc0cool22:28
inc0thanks a lot22:28
pabelangernp, once we get this working and your gates voting, I can circle back to a per region docker-registry22:29
pabelangerjust don't have time right now to focus on it22:29
*** kristian__ has quit IRC22:29
sean-k-mooneyjust out of interest.22:30
sean-k-mooneysince we will basically be uploading all container when the merge to infra22:31
inc0cool, thanks22:31
sean-k-mooneycan we also auto push to docker hub?22:31
inc0sean-k-mooney, well, that will be harder22:31
inc0it takes good amount of time for upload22:31
inc0and network traffic22:31
sdakepabelanger thanks for the confirmation22:31
sean-k-mooneyok i guess we could push that to them.22:32
sean-k-mooneywe could set up a git webhook that would have them rebuild the continers on each commit22:32
sean-k-mooneyits not needed but it would be neat22:32
inc0or do nightly somewhere22:32
pabelangerit would be easier to do, yes.  The next step would be to download said tarballs in a secure vm (which has username / password) for docker hub, then do the upload from it.22:33
*** matrohon has quit IRC22:33
pabelangerthat's the process we do for publishing to pypi for python packages22:33
sean-k-mooneywell you could upload the built images but dockerhub support building the continers for you as far a i know22:34
sean-k-mooneywe would just have to have a webhook to trigger the build the issue would be creeating the docker file templates automatically22:35
sean-k-mooneyeither would work though22:35
inc0someday;)22:35
inc0building with dockerhub won't work because afair it doesn't support COPY22:36
sean-k-mooneyah ok we basically would have to run kolla-build --template-only also before sending it to them22:37
*** pomac has quit IRC22:38
sean-k-mooneyhonestly i think a nightly build would be more the sufficent form most usecases22:39
inc0sean-k-mooney, even with --template-only, still COPY won't work, so source build is a no-no22:40
inc0but pushing nightly is doable22:40
sean-k-mooneyit would be nice for the stable branches once upgrade to same branch is supported.22:41
inc0it is supported22:42
sean-k-mooneynot that you upgrade nightly but if you are not building your own images it would be nice to be able to pull a regurally pattached/build image22:42
*** huikang has joined #openstack-kolla22:42
inc0minor upgrades (3.0.0->3.0.1) are supported ofc22:42
sean-k-mooneyi can upgrade form old stable/newton to latest stable/newton?22:42
inc0ofc22:42
sdakeinc0 the consensus view is kolla-ansible runs on selinux - since it runs that way in the gate22:43
inc0sdake, cool22:43
inc0then docs needs update22:43
sdakewhether or not it meets MarcisK 's requirements is another question22:43
sdakeok i'll take that particlar part on - which plenty of conditionals :)22:44
sdakewhich/with22:44
sdake(that part = fixing the docs)22:44
sdakescoped to selinux only22:45
sdakeclear?22:45
inc0sure, whatever you can do:)22:50
inc0I'm going off guys, happy turkey day22:50
inc0I was meant to say happy turkey, but I bet they're not exactly happiest bunch around now22:50
inc0bye!22:51
*** inc0 has quit IRC22:51
sean-k-mooneyis today thanksgiving in the us22:51
sean-k-mooneyi taught that was next week?22:51
sean-k-mooneynot from us so dont understand this holiday other then like christmas but not celebrating meal between native americans and european settelers22:52
*** ChanServ changes topic to "Looking for Ansible deployment? git checkout http://github.com/openstack/kolla-ansible; New to Kolla? Please read the documentation here: http://docs.openstack.org/developer/kolla/; Kolla IRC meetngs on Wednesdays @ 16:00 UTC - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA):"22:52
-openstackstatus- NOTICE: The affected filesystems on the log server are repaired. Please leave 'recheck' comments on any changes which failed with POST_FAILURE.22:52
*** sayantani01 has quit IRC22:53
*** MarcisK has quit IRC22:59
pronhmm is it posible that running kolla inside openstack fails cause of networking issues?23:02
sean-k-mooneypron: it depend on what you are trying to do23:06
proni created 10-15 instances23:06
pronand tryng ot play with kolla23:07
sean-k-mooneykolla on openstack over a vlan tenatn networking with vxlan for kolla should work fine23:07
pronbut it stuck atm with not being able to to konnect to network alias23:07
sean-k-mooneynetwork alias?23:07
pronemm23:07
pronthat another ip that keepalived puts on interface23:07
pron;P23:07
pronand then haproxy uses ir23:07
pronit*23:08
sean-k-mooneyah you have to add that other ip to the allowed adress pairs on the neutron port23:08
pronah m can i do that with gui?23:09
sean-k-mooneythe admin gui definetly not sure about the tenent verion23:09
pronokay then you propably can point me to the cli line :P23:10
* pron smiles and looks sean-k-mooney in the eye23:10
sean-k-mooneylet me check ... look for cli docs23:11
*** bmace has quit IRC23:12
proni am not yet familiar with them23:12
*** bmace has joined #openstack-kolla23:12
sean-k-mooneyneutron port-update --allowed-address-pair ip_address=<IP_ADDR> <port uuid>23:13
pronthat rises more questions that it solves but thx :P23:13
proni somehow tought its atm one universal cli for everything23:14
sean-k-mooneyyes there is the unified openstack client23:14
sean-k-mooneyaparently port updates are not supproted yet23:14
pronah i seee23:14
sean-k-mooneyhench i gave the neutorn client example23:15
proni see23:15
* pron scratches scratchable parts23:15
*** pomac has joined #openstack-kolla23:15
pronthx =)23:15
sean-k-mooneyso in our case the neutron port you use for you haproxy interface should be updated with the vip address23:16
*** liyifeng has joined #openstack-kolla23:16
pronaye23:16
proni suspected that!23:17
sean-k-mooneyi know this at least work for all in one deployment of kolla on openstack. have not tried multinode yet23:18
*** tonanhngo has joined #openstack-kolla23:18
*** srwilker has joined #openstack-kolla23:20
*** tonanhngo has quit IRC23:20
pronfor all n one i didnt bother i just used floating ip23:25
pron;D23:25
pronsean-k-mooney: looks like it did the trick23:29
*** dkehn__ has quit IRC23:29
sean-k-mooneycool are you deploying multiple controlers?23:30
pronyes23:30
proni am not sure what to use for hardware provisioning23:30
pronand insalling23:31
pronchecked out cobller but it looks liek a huge mess23:31
sean-k-mooneywell there some support for bifrost that i added last cycle but the code is pretty new. others have used maas23:31
proni do use some silly stuff for debian deployment alrdy23:32
proni have no clue what is bitforst tho ;x23:32
sean-k-mooneypron: https://github.com/openstack/kolla/blob/master/doc/bifrost.rst its standalone ironic23:33
sean-k-mooneyi use it at home but we have not tested it at scale.23:34
*** msimonin1 has joined #openstack-kolla23:35
*** msimonin1 has quit IRC23:35
pronso you end with soem registry of phisical hardware on the host you run it? or the hardware ends in your openstack ?23:36
pron( i am pretty new there :P )23:36
*** sdake has quit IRC23:37
sean-k-mooneyyou provide a yaml inventor of the node you want to deploy and os on and then run kolla-ansible deploy-servers wich enroles them in the standalone instance of ironic and ironic cleans them down and install the os23:38
pronahaa23:39
proni will look into it thx23:39
*** tonanhngo has joined #openstack-kolla23:40
*** sdake has joined #openstack-kolla23:40
*** sdake has quit IRC23:40
*** sdake has joined #openstack-kolla23:40
*** tonanhngo has quit IRC23:40
*** huikang has quit IRC23:40
*** huikang has joined #openstack-kolla23:41
pronsean-k-mooney: you actualy helped a lot today and saved so much time thx23:42
sean-k-mooneyno worries23:42
sean-k-mooneyglad to help23:42
pronanother thign i am wondering how do i tell kolla i want use tagged vlans for things23:43
*** lamt has quit IRC23:43
sean-k-mooneyfor example your storage network or api network?23:43
sean-k-mooneyor for tenant netowrks?23:44
pronyeh23:44
pronno no storage/mgmt/etc23:44
sean-k-mooneywell for api,storage etc. current that has to be done before you deploy kolla. then you tell kolla to use the vlan subport23:44
proni see23:45
sean-k-mooneyso instead of storage_interface: "enp8s0f0" you would do storage_interface: "enp8s0f0.1" or whatever23:45
proni point kolla to vlan interface23:45
sean-k-mooneyyep23:45
pronsean-k-mooney: that bitfrost thing can do that for me?23:45
*** huikang has quit IRC23:46
sean-k-mooneythis is somthing i would like to add to the kolla-ansible bootstrap-servers command in the future but its not there now.23:46
sean-k-mooneypron: maybe. not directly but you could bake it into the image.23:46
pronwich means i have to do my own ansible work for that atm23:46
sean-k-mooneyya basically23:46
sean-k-mooneyubuntu maas and cobler i think can do it but im not that familar with them23:47
pronhmm image?23:47
pronit doesnt use some kind of preseed/kickstart?23:47
sean-k-mooneythe os image you deploy to the server.23:47
prondeploy is abstraction :P can be million ways :P23:48
sean-k-mooneywell bifrost use ironic so you can use cloud-init to configure the server which is installed via pxe boot and ipmi by default23:48
sean-k-mooneyironic has a bunch of backend drivers23:49
pronguess it sounds like a homework for me =) unless someone wants to give me free lecture23:49
pronso i have to read ironic things and then move to bitfrost23:51
sean-k-mooneythat is one option yes but as you are probably aware there are many ways to do baremetal deployment so the final choice will depend on what you are looking for23:52
proni am looking for something more elegant then http://hands.com/d-i/23:56
pron;=)23:56
*** newmember has quit IRC23:57
pronbut this is fallback for me23:57
*** tonanhngo has joined #openstack-kolla23:58
*** goldyfruit has quit IRC23:59
*** tonanhngo has quit IRC23:59

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