Tuesday, 2016-11-29

*** catintheroof has joined #openstack-operators00:08
*** ducttape_ has joined #openstack-operators00:09
*** Apoorva has quit IRC00:28
*** liverpooler has quit IRC00:46
*** Apoorva has joined #openstack-operators01:00
*** piet has quit IRC01:04
*** liverpooler has joined #openstack-operators01:37
*** mriedem has joined #openstack-operators01:38
*** liverpooler has quit IRC01:48
*** Apoorva has quit IRC02:16
*** catintheroof has quit IRC02:16
*** catintheroof has joined #openstack-operators02:16
*** catintheroof has quit IRC02:20
*** liverpooler has joined #openstack-operators02:23
*** liverpooler has quit IRC02:37
*** VW has joined #openstack-operators02:47
*** sudipto has joined #openstack-operators03:01
*** sudipto_ has joined #openstack-operators03:01
*** VW has quit IRC03:07
*** VW_ has joined #openstack-operators03:16
*** catintheroof has joined #openstack-operators03:25
*** udesale has joined #openstack-operators03:32
stupidnicDoes anybody know if openstack service config files support the ability to include files?03:37
stupidnicI would like to steal a page from debian and do something like /etc/nova/conf.d/ and then have various files in there03:37
*** armax has quit IRC04:16
jlknot really04:20
jlksome do in some various ways, but it's not a general or generic thing04:21
*** catinthe_ has joined #openstack-operators04:23
*** catintheroof has quit IRC04:26
*** catinthe_ has quit IRC04:26
*** catintheroof has joined #openstack-operators04:27
stupidnicjlk: alright... thanks for the info04:27
*** catintheroof has quit IRC04:27
*** sudipto has quit IRC04:59
*** sudipto_ has quit IRC04:59
*** ecrehar has joined #openstack-operators05:29
*** sudipto has joined #openstack-operators05:29
*** sudipto_ has joined #openstack-operators05:29
*** VW_ has quit IRC06:13
*** saneax-_-|AFK is now known as saneax06:42
*** Apoorva has joined #openstack-operators06:43
*** Apoorva has quit IRC06:46
*** pcaruana has joined #openstack-operators07:21
*** simon-AS559 has quit IRC07:26
*** makowals has joined #openstack-operators07:28
*** simon-AS559 has joined #openstack-operators07:42
*** jsheeren has joined #openstack-operators07:56
*** jsheeren has quit IRC07:56
*** jsheeren has joined #openstack-operators08:05
*** matrohon has joined #openstack-operators08:08
*** VW has joined #openstack-operators08:13
*** rmart04 has joined #openstack-operators08:16
*** VW has quit IRC08:18
*** beddari has joined #openstack-operators08:31
*** ecrehar has quit IRC08:45
*** ecrehar has joined #openstack-operators08:47
*** paramite has joined #openstack-operators08:53
*** rcernin has joined #openstack-operators08:56
*** zioproto has joined #openstack-operators09:13
*** derekh has joined #openstack-operators09:18
*** openstackgerrit has quit IRC09:48
*** makowals_ has joined #openstack-operators09:48
*** openstackgerrit has joined #openstack-operators09:49
*** makowals has quit IRC09:51
*** racedo has joined #openstack-operators09:52
*** electrofelix has joined #openstack-operators09:55
*** racedo has quit IRC10:47
*** udesale has quit IRC10:58
*** sudipto_ has quit IRC11:03
*** sudipto has quit IRC11:03
*** catinthe_ has joined #openstack-operators12:37
*** jsheeren has quit IRC12:47
*** dbecker has joined #openstack-operators12:49
zioprotomfisch: hello Matt, during my upgrade I got stuck into this https://bugs.launchpad.net/puppet-openstacklib/+bug/161209313:24
openstackLaunchpad bug 1612093 in puppet-openstacklib "creating multiple databases with same db username is not possible with puppet-openstacklib" [Wishlist,Confirmed]13:24
zioprotomfisch: there is any testing beta patch around for this ?13:24
zioprotomfisch: I dont see any openstack review yet, right ?13:25
*** dtrainor has joined #openstack-operators13:39
*** sudipto has joined #openstack-operators13:45
*** sudipto_ has joined #openstack-operators13:45
*** udesale has joined #openstack-operators13:47
*** VW has joined #openstack-operators13:57
*** mihalis68 has joined #openstack-operators13:58
*** dc_mattj has joined #openstack-operators14:00
dc_mattjafternoon14:00
mihalis68morning14:01
VWhola14:01
mihalis68I remembered my action and just sent the email :)14:02
mihalis68dc_mattj will you run the meeting today?14:02
dc_mattjyes14:02
dc_mattjanyone else here ?14:02
mihalis68no, it's just Matts14:03
mihalis68oh, and me14:03
mihalis68I get the feeling this time of the day isn't working very well14:04
dc_mattjok14:04
dc_mattj#startmeeting Ops Meetups Team14:04
openstackMeeting started Tue Nov 29 14:04:18 2016 UTC and is due to finish in 60 minutes.  The chair is dc_mattj. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
openstackThe meeting name has been set to 'ops_meetups_team'14:04
*** rmart04_ has joined #openstack-operators14:04
*** rmart04 has quit IRC14:04
*** rmart04_ is now known as rmart0414:04
dc_mattjHello all, and welcome to the Ops Meetups Team meeting :)14:05
dc_mattjNB: If you're new, or just idling in the channel, be sure to have read:14:05
dc_mattj#link https://wiki.openstack.org/wiki/Ops_Meetups_Team14:05
dc_mattjfor background.14:05
dc_mattjCheck out our agenda items at:14:05
dc_mattj# link https://etherpad.openstack.org/p/ops-meetups-team14:05
dc_mattjAs always: please write your name down on the agenda etherpad as a way of introduction.14:05
dc_mattjSecondly, if there's something else burning to put on the agenda, please add it to that same etherpad.14:05
dc_mattj#topic Review of action items from the previous meeting14:05
dc_mattjFirst up, a quick run-through of our action items from the previous meeting.14:05
dc_mattjso on our action items from the last meeting, I haven't added the regional meeting discussion for today14:06
dc_mattjto be honest I think that needs more of a quorum to discuss14:06
VWI would agree14:07
dc_mattjI'd vote that we put that back for a face to face, perhaps in Milan ?14:07
dc_mattjI do have some updates on Milan - I had a video conference with Mariano from Enter this morning14:07
VWThat could work - just know you might have a limited perspective there - regionally speaking14:07
dc_mattjVW, true14:08
dc_mattjwe could also put back until the Boston summit14:08
VWe.g. - I probably won't make Milan14:08
dc_mattjwhere we would have wider participation14:08
VWideally, we could have some more conversation about it, but yes, I think the OPs Meetup session(s) in Boston should explore it in detail14:08
dc_mattj+114:08
dc_mattjmihalis68, do you have anything else to add to that point or shall we park that for the minute14:10
dc_mattjI've made a note on the ether pad14:10
mihalis68Nothing to add14:10
dc_mattjok, so on Milan14:10
dc_mattjMariano and I went through the basics of the logistical stuff14:11
mihalis68how is the venue looking?14:11
dc_mattjvenue looks good - main room 120+, room 2 30+, room 3 and 4 20ish14:11
dc_mattjdepending if we need all of them14:12
mihalis68very good14:12
dc_mattjyou can see some of the space at http://www.coworkinglogin.it/14:12
mihalis68Do we require the possibility of an all-hands meeting?14:12
mihalis68Just thinking about capping the max attendance14:12
dc_mattjwhen ?14:12
mihalis68in Milan. Is 120 the de facto maximum number of attendees?14:13
mihalis68I'm asking as I don't recall if that's a rule14:13
zioprotohello all14:13
mihalis68hello14:13
dc_mattjwe discussed this previously, with 120 as a guideline IIRC14:13
dc_mattjhello zioproto14:13
dc_mattjso Enter are finding someone to sit in on these meetings14:14
mihalis68#info 120 is the likely maximum attendance in Milan as it is the size of the biggest room14:14
*** nemesis-ninux has joined #openstack-operators14:14
dc_mattjI have asked Mariano to get some rough costings for the event, so they can decide how much sponsorship they can carry, and if we need to get additional sponsors14:15
dc_mattjthat will take them a couple of weeks to do14:15
dc_mattjthey are happy to handle the logistical side, but have requested that we drive the content and moderators piece14:15
mihalis68right... precisely why a benevolent dictator is needed on that side14:16
mihalis68well done, dc_mattj :)14:16
dc_mattjI have explained that is driven via a community process anyway so I don't particularly see any issues with that14:16
dc_mattjand I am happy to liaise with them14:16
zioprotoif Mariano needs a sponsor I can try asking here at SWITCH, but I need to know what kind of cost we are talking about14:16
dc_mattjzioproto, great idea14:17
dc_mattjwhen we get the rough costings we will know what sponsorship we need to raise14:17
*** jamesdenton has joined #openstack-operators14:17
dc_mattjas a guideline, for MCR each sponsor put in around €100014:17
dc_mattjbut smaller or larger amounts are also possible14:17
mihalis68I have no idea if Bloomberg would stump up again, however I know we are strongly considering sponsoring the first PTG, therefore if you cc: me on the costs and "funding gap" I could find out14:17
zioprotothat should be something I can ask at SWITCH14:17
*** zul has quit IRC14:18
dc_mattjso lets park this until Enter have done the costings, and can say how much they can contribute14:18
dc_mattjthen we can work out what additional sponsorship we need14:18
mrhillsmano/14:18
mrhillsmansorry i'm tardy14:18
VW+1 dc_mattj14:19
VWhowdy mrhillsman14:19
mihalis68dc_mattj agreed. I can't say officially but I would think Bloomberg could go at least up to the $1k mentioned14:19
dc_mattjhi mr14:19
dc_mattjhi mrhillsman14:19
mihalis68morning mrhillsman14:19
dc_mattjEnter are also going to look at discount hotel rates locally14:19
mihalis68I have now added two things to today's agenda14:20
mihalis68so let's move on14:20
dc_mattjI saw14:20
dc_mattjso basically on agenda item 2, we are waiting on Enter to provide a liaison person and rough costings14:21
dc_mattjanything more on item 2 ?14:21
zioproto#agreed we are waiting on Enter to provide a liaison person and rough costings14:21
dc_mattjty :)14:21
dc_mattj#topic Follow on from session structure review14:22
dc_mattjhas anyone got any input on the session analysis I circulated ?14:22
mihalis68nice work pulling all the ether pad links together and roughing out the popular topics14:22
mihalis68I haven't reviewed it more than a brief look, sorry14:22
zioprotoshould we post the link to the google excel doc ?14:22
mihalis68have been away since last meeting, so buried in work14:22
mihalis68https://docs.google.com/spreadsheets/d/1-WEsEmwms2SLyjt2jtCMvpepmiHwoiDkMWMWk37rkRA/edit#gid=014:22
zioproto#link https://docs.google.com/spreadsheets/d/1-WEsEmwms2SLyjt2jtCMvpepmiHwoiDkMWMWk37rkRA/edit#gid=014:23
VWI'm still going through it, dc_mattj14:23
*** vijaykc4 has joined #openstack-operators14:23
mihalis68my observation is this work will be extremely valuable to the specific milan itinerary work14:23
*** jamesdenton has quit IRC14:23
zioprotohow do we read this ? is the color a topic ?14:23
dc_mattjsorry - colours are a bit confusing, just my shorthand for trying to link things together14:23
zioprotothe idea is to merge those ones on the same color ?14:24
dc_mattjbottom of the coloured section is the summary14:24
dc_mattjI suggested a couple of the ways we could look at the data in the email I circulated14:24
zioprotoI think that upgrades, patches and packaging can go together with config management. These two I think should be merged14:25
dc_mattjjust some food for thought really when we start to do the session planning14:26
dc_mattjnot really any definitive take aways, but we can definitely pre-load some sessions which come up repeatedly14:26
dc_mattjand we also might consider allocating time slots against a 'track' rather than a specific topic, and we can then add to the tracks more fluidly in the run up to the event14:27
*** ducttape_ has quit IRC14:27
zioprotothis makes sense14:27
zioprotomaking the tracks14:27
mihalis68You mention nova, neutron, logging and monitoring as the popular ones. I would add scaling and containerization (two)14:27
dc_mattj+114:27
zioproto+114:27
dc_mattjthose were just examples really14:27
*** ducttape_ has joined #openstack-operators14:27
zioprotomaking tracks we make sure that people interested in a specific area dont miss talks that happen in parallel14:28
dc_mattjI think there's a set of clearly defined topics, plus a set of fairly clearly defined 'tracks', then we can also reach out to the wider community to fill in content under the 'tracks', and to add any other topics not covered already14:28
zioproto+114:29
zioprotoShould we try to make this track skeleton in the Milano etherpad ?14:29
*** mriedem has quit IRC14:29
mrhillsman#link https://etherpad.openstack.org/p/MIL-ops-meetup14:30
dc_mattjI don't have time for the full hour today so I suggest we aim to start populating the Milano ether pad in next weeks meeting ?14:30
*** jamesdenton has joined #openstack-operators14:30
VWso, I have one higher level meta observation we should keep in the back of our minds when digesting dc_mattj's work and using it for future meetups14:31
zioprotookay14:31
VWin theory, the structure of the "Ops" stuff is going to change at the forums14:31
mihalis68Tracks seem popular, certainly that seems a good idea, however I think we need some ground rules before people start filling up the ether pad or it will get hopelessly confusing14:31
*** ducttape_ has quit IRC14:31
VWsince sessions will be much more focused on dev and ops together discussing features, needs, etc14:32
VWso, that will put a lot of pressure on what the more general topics are at the meetups14:32
VWand should force us to push working group time/meetings back to the forum - where the Foundation seems to be taking over the scheduling of that (at least they did in BCN)14:32
VWwe should follow up on those assumptions14:32
VWbut the data in this sheet has meetups where all these kinds of activities took place, and it's worth thinking about the fact that some of that focus may shift around from one event type to another14:33
dc_mattjok, lot of unknown unknowns in that area at the minute but I think I follow your logic14:33
mihalis68the forum is the new thing at the summit now that the design summit is no more?14:33
mihalis68the Yin to the PTG Yang?14:34
dc_mattjyes14:34
VWyes, but, as I understood, it it's a melding of the design and ops summit14:35
mihalis68VW are you suggesting that for Milan we remove things from that meet up that can be done in Boston?14:35
VWthe $100,000 question is where there still be an Ops "meetup" at the forum14:35
mihalis68Sorry, i'm finding this all hard to follow14:35
VWI know - text is hard14:35
VWmore that we should confirm what the intent is for "ops" activities at the forum14:35
VWand then make sure we are maximizing what goes on at the mid-cycles based on that14:36
VWin case there aren't opportunities for general sessions in Boston (and beyond)14:36
dc_mattjteasing out cross project issues from the ops perspective, which can then inform session schedules at the forum, will be important14:36
zioprotoso we should avoid WG presentations and updates at the ops meetup, and keep focused on ops discussion, bugs, and features ? But not talking on stuff like update from the XYZ WG .. Did I understand ?14:36
dc_mattjand some of that comes out of the more general ops discussions14:36
VWI would think so zioproto, but we need to confirm if the Foundation will continue to manage the WGs like they did in BCN14:37
VWbut I think we decided after NYC, that we can really focus the mid-cycles on topics/discussion14:37
dc_mattjagreed14:37
zioprotois any operator going also to the PTG in Atlanta ?14:38
VWand let the WG/teams meet up at the forums - where they will likely be driving various session topics along with devs14:38
dc_mattjzioproto, I think that's our next topic14:38
mihalis68I've added PTG to agenda... I can't see how it makes sense for anyone from my team to attend PTG14:38
dc_mattjanything else on this topic ?14:38
VWnone for this one, dc_mattj14:38
VWsorry if I confused14:38
dc_mattjno, important input14:38
mihalis68I think I agree but I would need a clearer statement to be sure, honestly14:38
dc_mattjand it is somewhat confusing14:38
dc_mattjuntil we do one cycle I don't think it will get less confusing14:39
mihalis68I was confused before BCN, and also after BCN14:39
mihalis68maybe having only one person from Bloomberg Engineering attempt to "do" Barcelona was a mistake! :)14:39
VWwell, we'll just blame Tom till he returns :D14:39
dc_mattj#topic Weekly meeting time-slot?14:40
dc_mattj#topic Weekly meeting time-slot?14:40
dc_mattj#topic Weekly meeting time-slot?14:40
dc_mattj#topic weekly meeting time-slot14:40
dc_mattjwhoops14:40
mihalis68Yes that's actually the next item, not that I mind14:40
dc_mattjso time slot - who has thoughts on this  ?14:40
mihalis689am for me is doable, but Tom comments it's not doable for him14:40
* VW thinks dc_mattj really wants to talk about the time slot14:40
VWI think that was just this week14:40
mihalis68it's even earlier for VW and mrhillsman, right?14:40
mrhillsman8am for me14:41
mrhillsmanfor VW as well14:41
mrhillsmanunless he is earth exploring14:41
zioprotowhat timezone are we talking avout ?14:41
mihalis68trouble with this agenda item: everyone for whom this slot is impossible is ... not here14:41
VWyep - I can do 8am - it's not as easy as 9 because of school drop offs and such, but I can make it work14:41
mrhillsmanlol14:41
mihalis68i'm in EST14:41
dc_mattjif you mean Tom's email, I thought he was saying that he's currently in a bad time zone14:41
dc_mattjunless someone knows different14:41
mihalis68I thought he was always in a bad timezone, no? Korea?14:42
mrhillsmanyeah, looks like it is just today14:42
VWyeah, it's his current location.  His normal time zone, it would be 10:00pm14:42
mihalis68bad meaning "for this meeting", obviously14:42
dc_mattjis it better at 1500 ?14:42
zioprotoanything that is in the morning in the US usually works for me14:42
mrhillsmanwe don't need to change it14:42
dc_mattjfor most folks14:42
dc_mattjI am happy with either14:42
mihalis68I notice that attendance has been worse since the end of DST here14:42
mihalis68can't prove cause and effect14:42
VWyeah, I'd hate to push it further back14:42
VWit's already 10:00pm for Tom14:43
VWand 11:00pm for shintaro14:43
VWboth of whom we all value14:43
VW:D14:43
mrhillsman+214:43
mrhillsmanone for each :)14:43
mihalis68ok, sounds like it's fine14:43
mihalis68not easy for me but I was worried that it had become a bad time for too many14:43
dc_mattjdo we want to vote ?14:44
VWI just may be late some weeks - until daylight savings - if I can't get the younger VW's moving in the morning ;)14:44
mihalis68we can move on as far as I'm concerned14:44
VW+114:44
*** dc_mattj has quit IRC14:44
zioproto+114:44
zioprotoMatt left the room ?14:44
mihalis68uh-oh, the chair quit14:44
mihalis68he said he can't do the whole hour today14:44
*** dc_mattj has joined #openstack-operators14:45
mihalis68last item was PTG. Bloomberg is sponsoring the first one and sending people from our CTO office14:45
dc_mattjsorry14:45
dc_mattjwifi dropped14:45
mihalis68and they encouraged me to go or send someone, and yet I still can't see it being appropriate for me14:45
dc_mattj#topic Operators at PTG?14:45
mihalis68the writeup emphasizes you should go if you have a specific speciality14:45
mihalis68yes14:46
VWI think we need to encourage all Operators to look at the ops mid-cycle in the same light a dev would look at PTG14:46
mihalis68none of my guys are interested in the slightest14:46
zioprotomihalis68: on the web page they say that should go "Operators that are specialists on a given project (and are willing to spend their time giving feedback on their use case and contributing their usage experience to the team)"14:46
dc_mattjThierry's view on the list was that the sessions are definitely work sessions14:46
zioprotoI will try to be there to give feedback about Neutron stuff mostly14:46
VWThink of it like this.  We want the conversation at the forums to be about the 'What' - bugs needing fixing, features, gaps, etc14:46
mihalis68There' nothing there for me14:46
dc_mattjso unless you want to get involved in development it's probably not that useful14:46
VWand the PTG gets in to the "how"14:46
dc_mattjzioproto, I think the idea is that the feedback bit is for the forum14:47
dc_mattjVW, +114:47
mihalis68i wish Tom were here. I believe he said that some operators need to go to the PTG14:47
zioprotodc_mattj: I did cut and paste from here https://www.openstack.org/ptg/14:47
VWso, in a perfect world, general discussions at an Ops mid-cycle lead to WG's and others generating propsoals for forum sessions (ideally with co-opration from some devs14:47
VWat those forum sessions, decisions get made on what to do14:47
VWand at the PTG, the devs dive in to all the messy bits of how to do them14:48
dc_mattjthat's my understanding too14:48
VWwhile the Ops folks are back to have general discussions on the next thing on the pile14:48
VWsimple - right :D14:48
zioprotoplease look at this https://www.openstack.org/ptg/ and there is a section "https://www.openstack.org/ptg/"14:48
zioprotosection "who should attend"14:48
zioprotoit says operatios14:48
zioprotoam I wrong ?14:48
zioprotowe are referred as "downstream"14:48
zioprotois that about the forum >14:49
zioproto?14:49
mihalis68yes I've read that repeatedly. It's a qualified set of operators "who are specialists on a given project"14:49
mrhillsmannot sure why they put upstream and downstream -_- confuse-stream14:49
mihalis68I run a team where my guys do quite a bit of nova, cep, cinder, glance, keystone14:49
mihalis68but they STILL don't really qualify14:49
mrhillsmani agreep on VWs perspective14:50
mrhillsmani do not think any operator is "discouraged" from going, if they want14:50
zioprotomihalis68: do your guys send patches upstream with the review platform ?14:50
zioprotoif yes I think they should go14:50
mrhillsmanbut should expect the focus to be on how to accomplish the what14:50
*** dminer has joined #openstack-operators14:50
mrhillsmanvs what to accomplish14:50
dc_mattjguys, I'm going to have to drop off in a minute14:50
mihalis68we've tried a couple of times. It's really off-putting. Lots of minutiae14:50
mihalis68not sure if we got anything merged14:51
dc_mattjI'm not sure this particular topic has a definitive outcome ?14:51
mrhillsmani think general consensus is, if you want to go, go :)14:51
*** rmart04 has quit IRC14:51
dc_mattjother than we're still somewhat confused :)14:51
mihalis68Seems like there's only minimal interest in going from people on this chat, emirate?14:51
mihalis68amirite14:51
mihalis68yet Tom thinks some of us "should" go14:51
zioprotomihalis68: that exactly the point. After meeting devs in person it is easier to get stuff merged upstream14:51
VWthe tl;dr is - if a n Operator has a reason to go to PTG , then go14:51
mrhillsmanthere's not hard rule to not go14:51
dc_mattjmihalis68, +1 from me unless I had someone in my team who was contributing to upstream code significantly14:52
mrhillsmanpretty sure we should bury this :)14:52
VWbut if someone is just trying to decide what is best - mid-cycle for OPs should be encouraged14:52
zioproto8 minutes to the end of the meeting14:52
mihalis68ok. I'm going to let tom and my CTO colleagues know that it' s not a fit for us, despite us running all the openstack here14:52
*** rmart04 has joined #openstack-operators14:52
dc_mattjI have to go, so I'm going to end this meeting here unless anyone has anything else urgent14:53
mrhillsmanpretty sure after the first or second iteration of the changes things will settle where appropriate14:53
mihalis68I know I could go, but I was surprised to hear from two sources that operators should go and make their voices heard. I think not, unless as you say they are deep specialists on a particular chunk of openstack tech14:53
dc_mattjnext week we will start putting together the agenda14:53
mrhillsmannothing urgent here14:53
dc_mattj#endmeeting14:53
openstackMeeting ended Tue Nov 29 14:53:31 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.html14:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.txt14:53
openstackLog:            http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-11-29-14.04.log.html14:53
zioprotothanks for the meeting :)14:53
dc_mattjthank you all for coming :)14:53
zioprotobye14:53
mrhillsmanthx everyone14:53
mihalis68I wasn't actually done14:53
mrhillsmanlol14:53
mihalis68no really14:53
mihalis68I was typing14:54
mrhillsmanit's matt's fault14:54
mihalis68I don't think we should shut down the meeting because someone has to go14:54
mrhillsmani don't think anyone could have ended it14:54
zioprotohey14:55
*** ducttape_ has joined #openstack-operators14:55
mrhillsmanhey14:55
zioprotoanyone had problems with DJANGO and south python library14:55
zioprotowhen upgrading from liberty to Mitaka ?14:55
zioprotothere is nothing in the release notes14:55
zioprotoand I am getting crazy to get this working14:55
mrhillsmanmihalis68 unless you know moderator can be changed14:55
mrhillsmandon't think we had a choice14:55
zioprotoI can believe it worked at the first shot for everyonelese ? :)14:56
mihalis68We're only getting to Liberty in production here14:56
mrhillsmani can ask but do not think that was an issue14:56
zioprotomrhillsman: on Ubuntu ?14:56
*** pilgrimstack1 has quit IRC14:56
mrhillsmanyeah, 14.0414:56
mihalis68ok the meeting's over, but can I ask : who is actually planning to attend PTG?14:56
mrhillsmannot me mihalis6814:56
dc_mattjsorry14:56
zioprotomihalis68: I still have to decide, it could be14:56
dc_mattj:(14:56
dc_mattjthought everyone was done14:56
mihalis68no14:57
mihalis68but it's ok14:57
zioprotomihalis68: I will decide beginning of January14:57
*** mriedem has joined #openstack-operators14:57
mihalis68think I'm not going to PTG and I'll have to let Tom know because he specifically encouraged us to attend and represent14:57
mrhillsmani missed that then14:58
mrhillsmanwas this during bcn meeting?14:58
mihalis68It feels that the PTG is tightly defined by devs for devs so there's no forum for us to say our piece14:58
*** dc_mattj has quit IRC14:58
zioprotomrhillsman: I would like to know if you guys had problem upgrading the ubuntu package openstack-dashboard from liberty to mitaka on trusty :) thanks !14:58
*** ecrehar has quit IRC14:58
mrhillsmanzioproto i did not run into an issue14:59
mrhillsmanbut i use openstack-ansible project14:59
mrhillsmans/i/we14:59
zioprotomrhillsman: thanks14:59
mrhillsmanliberty > mitaka / mitaka > newton14:59
*** dc_mattj has joined #openstack-operators14:59
mrhillsmanlet me ask osa folks14:59
mihalis68mrhillsman it could have been in-person, sorry, I don't recall15:00
mrhillsmanok15:00
logan-I didn't have that problem zioproto (osa managed deployment here). however I did run into that dogpile cache issue w/ nova that you posted in here last week zioproto :P15:01
mrhillsmanzioproto no issues15:01
mrhillsmanthx logan-15:01
*** dc_mattj has quit IRC15:01
mrhillsmanzioproto15:02
mrhillsmancustom dashboard?15:02
zioprotono, ubuntu dashboard15:02
zioprotoopenstack-dashboard                  2:9.1.0-0ubuntu1~cloud015:03
zioprotologan-: Oh ! I have short memory, what did I paste about logpile ?15:04
zioprotowas it with nova ?15:05
logan-https://bugs.launchpad.net/nova/+bug/161558215:05
openstackLaunchpad bug 1615582 in OpenStack Compute (nova) "Error: Unable to create the server. Unexpected API Error." [Undecided,New]15:05
logan-yep15:05
mrhillsmanzioproto your dashboard has ubuntu logo or openstack logo by default?15:05
zioprotoby dashboard has the SWITCH logo :D15:06
zioprotobut we remove the ubuntu customization package15:06
zioprotoand we just replace the jpg logo with puppet15:06
logan-it only happened in our env during the middle of the upgrade where the controllers were on mitaka and the computes were moving to liberty. once everything was on mitaka it disappeared15:06
zioprotologan-: did you use the upgrade levels in your nova.conf ?15:07
logan-no during the post mortem of it all I suspected that might be part of the cause15:07
mrhillsmanthere was a jump in angular version, not sure if that is your problem, but upstream horizon untouched works15:07
logan-have not validated whether that would have prevented it15:08
zioprotologan-: ah yes now I remember ! thanks for the link :) I fixed so quickly that it did not stick into my mind15:08
zioprotomrhillsman: as soon as I fill fix it I will let you know :)15:08
zioprotothe angular stuff is in the release notes15:09
mrhillsmanok cool15:09
zioprotoneed coffee ! see you guys later15:09
mrhillsmanl8r15:09
logan-cya15:10
*** slaweq_ has quit IRC15:11
*** slaweq_ has joined #openstack-operators15:12
*** saneax is now known as saneax-_-|AFK15:23
*** pilgrimstack has joined #openstack-operators15:23
*** pilgrimstack has left #openstack-operators15:23
*** chlong has joined #openstack-operators15:27
*** mriedem is now known as mriedem_meeting15:29
*** sfrode has joined #openstack-operators15:34
*** vijaykc4 has quit IRC15:35
*** zul has joined #openstack-operators15:38
*** udesale has quit IRC15:55
*** mriedem_meeting is now known as mriedem16:00
*** _ducttape_ has joined #openstack-operators16:00
*** rcernin has quit IRC16:03
*** ducttape_ has quit IRC16:03
*** ckonstanski has quit IRC16:05
*** vijaykc4 has joined #openstack-operators16:06
*** chlong has quit IRC16:07
*** _ducttape_ has quit IRC16:11
*** ducttape_ has joined #openstack-operators16:12
*** chlong has joined #openstack-operators16:20
*** armax has joined #openstack-operators16:32
*** pcaruana has quit IRC16:36
*** akanksha__ has joined #openstack-operators16:38
*** ducttape_ has quit IRC16:39
*** ducttape_ has joined #openstack-operators16:39
*** akanksha__ is now known as ApheleiaS16:41
*** _ducttape_ has joined #openstack-operators16:41
*** ducttape_ has quit IRC16:41
*** jamesdenton has quit IRC16:45
*** rmart04 has quit IRC16:47
zioprotomrhillsman: it ended up we had a django extension in our horizon based on the south library, that was removed in django 1.8.716:49
*** dbecker has quit IRC16:54
*** jamesdenton has joined #openstack-operators16:54
*** ckonstanski has joined #openstack-operators17:00
*** chlong has quit IRC17:10
*** zioproto has quit IRC17:22
*** chlong has joined #openstack-operators17:24
*** makowals_ has quit IRC17:25
*** matrohon has quit IRC17:26
*** vijaykc4 has quit IRC17:27
stupidnicI am wondering if somebody can point me in the right direction here. I am trying to change the path that horizon uses from /horizon to / but when I login I am getting redirected to /identity which isn't found. I thought I fixed the local_settings.py correctly but I must be missing something.17:38
*** nemesis-ninux has quit IRC17:40
*** matrohon has joined #openstack-operators17:42
*** vijaykc4 has joined #openstack-operators17:44
*** markvoelker has quit IRC17:45
*** markvoelker has joined #openstack-operators17:50
*** derekh has quit IRC17:51
*** Apoorva has joined #openstack-operators18:02
*** simon-AS559 has quit IRC18:11
*** vijaykc4 has quit IRC18:12
*** sudipto_ has quit IRC18:13
*** sudipto has quit IRC18:13
*** zul has quit IRC18:13
mdormanstupidnic:  we have these settings in local_settings:  WEBROOT = '/dashboard/' , LOGIN_REDIRECT_URL = '/dashboard' , LOGIN_URL = '/dashboard/auth/login/' , LOGOUT_URL = '/dashboard/auth/logout/'18:13
stupidnicmdorman: Thanks. I have determined that I can access other endpoints /project /admin, etc just not identity, so something else might be going on here.18:14
mdormanstupidnic: i vaguely remember some problem with using / as the root from a while back.  there was some other setting inside horizon taht would cause the css and other resources to get path’d incorrectly if the root was set to /   but i think that has since been fixed18:14
mdormanah ok18:14
stupidnicmdorman: yeah I am trying this on Newton, so I would hope that was addressed. We have no problem using / in Liberty18:15
*** zul has joined #openstack-operators18:21
stupidnicsigh... switching it back to /horizon/ makes it work.18:23
stupidnicmdorman: so it looks like you are correct...18:23
mdormani would have to go dig a little bit to find the bug again.  unfortunately i don’t remember all the details off the top of my hea18:27
mgagneused to be $webroot variable in _variables.scss18:28
mdormanyes, that sounds very familiar18:28
mgagneyou will need to recompress static files after changing it18:28
stupidnicmgagne: I did so. The other areas display correctly (no CSS issues or missing images) it's only the /identity endpoint18:29
stupidnic/project and /admin both work18:29
mgagneok, can't help you more on that one. Do you happen to host Keystone service on the same server under the /identity path?18:29
stupidnicKeystone is on the same server, but keystone runs under a different port18:30
mgagneok18:30
stupidniclet me follow that thread though18:30
*** makowals has joined #openstack-operators18:30
mgagneother than checking horizon logs, I have no idea. enabling debug too18:30
stupidnicmgagne: damn it... you are spot on18:31
stupidnicmgagne: there is an alias endpoint in the keystone defintion for /identity that is clrearly conflicting with horizon's when you move it to the root url18:31
mgagne=)18:32
stupidnicAlias /identity /usr/bin/keystone-wsgi-public18:32
mgagneglad you found it18:32
stupidnicAny clue what that is used for?18:32
*** VW has quit IRC18:32
mgagnekeystone auth?18:32
stupidnicshouldn't that occur on the keystone ports?18:33
mgagnelooks like it imo (the service running on 5000 tcp port)18:33
david-lylestupidnic: the problem is horizon has /identity as one of the dashboards and it's keystone's default endpoint18:33
david-lyleso when you log into horizon at / the default dash is /identity if you have access to that dashboard18:33
stupidnicdavid-lyle: what is that keystone endpoint actually used for? doesn't most stuff auth with the keystone ports?18:33
david-lyleno, no special port under apache18:34
david-lylethat's the actual endpoint now18:34
mgagnedepends on your setup, could be some installer moved all services under path (/identity, /volume, etc.) instead of ports. Moving horizon at root increases the risk of conflicts.18:34
david-lylewhat you can do is put a redirect in apache for / to got to horizon/18:35
stupidnicYeah, I hate that (personal style issue)18:35
david-lyleand then you won't see the conflict and still can hit / for horizon18:35
david-lylesure18:35
david-lylenot very elegant for sure18:35
stupidnicSo, just help me understand this here...18:35
stupidnicwhat exactly is the purpose of the http://controller/indentiy and http://controller/identity_admin endpoints?18:36
stupidnicis that just public aliases to the keystone service?18:36
*** VW has joined #openstack-operators18:37
stupidnicso that users don't have to hit 5000 or 3535718:37
stupidnicAs near as I can tell that looks to be the purpose of those two endpoints18:39
david-lylehttps://github.com/openstack/keystone/blob/master/httpd/wsgi-keystone.conf#L52 is the config, maybe just for HEAD ?18:41
david-lyleoh, it's just another alias, pasted without looking :(18:42
stupidnicYeah. It's cool. I believe that nothing native in Openstack is hitting those endpoints... they are just a helper aliases for users that might be behind a firewall that would block access to port 5000 or 3535718:43
david-lyleI think the idea was to hide the need for magic ports18:43
david-lylebut the keystone room would know better18:44
stupidnicYeah I am not going to stress over it too much. Horizon is what 99% of our users use, so getting that to parity with our current Liberty install is more important18:45
stupidnicThanks for the help in getting to the bottom of this.18:45
*** electrofelix has quit IRC18:55
*** mihalis68 has quit IRC19:11
*** matrohon has quit IRC19:14
*** VW_ has joined #openstack-operators19:20
*** VW_ has quit IRC19:21
*** racedo has joined #openstack-operators19:22
*** racedo has quit IRC19:23
*** racedo has joined #openstack-operators19:23
*** VW has quit IRC19:24
*** racedo has quit IRC19:25
*** paramite has quit IRC19:30
*** VW has joined #openstack-operators19:39
*** paramite has joined #openstack-operators19:43
*** paramite has quit IRC19:49
*** slaweq_ has quit IRC19:57
*** slaweq_ has joined #openstack-operators19:58
*** rockyg has joined #openstack-operators20:02
*** rockyg has quit IRC20:04
*** rockyg has joined #openstack-operators20:04
*** slaweq_ has quit IRC20:16
*** slaweq_ has joined #openstack-operators20:17
*** VW has quit IRC20:18
*** slaweq_ has quit IRC20:22
*** slaweq_ has joined #openstack-operators20:23
*** VW has joined #openstack-operators20:24
*** VW has quit IRC20:32
*** VW has joined #openstack-operators20:32
*** catinthe_ has quit IRC20:35
*** slaweq_ has quit IRC20:42
*** slaweq_ has joined #openstack-operators20:44
*** VW has quit IRC20:54
*** matrohon has joined #openstack-operators20:57
*** rocky_g has joined #openstack-operators20:59
*** rockyg has quit IRC21:00
*** VW has joined #openstack-operators21:02
*** VW has quit IRC21:04
*** VW has joined #openstack-operators21:05
*** liverpooler has joined #openstack-operators21:27
*** catintheroof has joined #openstack-operators21:34
*** catintheroof has quit IRC21:38
*** catintheroof has joined #openstack-operators21:47
*** matrohon has quit IRC21:54
*** matrohon has joined #openstack-operators21:54
*** dtrainor has quit IRC22:00
*** simon-AS559 has joined #openstack-operators22:00
*** slaweq_ has quit IRC22:03
*** racedo has joined #openstack-operators22:05
*** rocky_g has quit IRC22:10
*** chlong has quit IRC22:12
*** jamesdenton has quit IRC22:15
*** matrohon has quit IRC22:22
*** dminer has quit IRC22:24
*** rcernin has joined #openstack-operators22:31
*** mriedem has quit IRC22:48
*** racedo has quit IRC22:59
*** racedo has joined #openstack-operators23:01
*** rcernin has quit IRC23:01
*** rcernin has joined #openstack-operators23:03
*** catinthe_ has joined #openstack-operators23:03
*** rcernin has quit IRC23:04
*** rcernin has joined #openstack-operators23:04
*** catintheroof has quit IRC23:06
*** ducttape_ has joined #openstack-operators23:14
*** mriedem has joined #openstack-operators23:14
*** _ducttape_ has quit IRC23:17
*** ducttape_ has quit IRC23:19
mdormanis it possible to delete multiple floating IPs in a single neutron call?   i have a large number (~1000) that i want to delete as simultaneously as possible, and if i just have to for loop that it’s going to take a while.23:31
yankcrimeanyone know if it's possible to remove a neutron lbaas (v1) pool from an agent and then add it to another?23:33
*** rcernin has quit IRC23:41
*** ckonstanski has quit IRC23:48
*** VW_ has joined #openstack-operators23:51
*** VW has quit IRC23:55
*** VW_ has quit IRC23:56
yankcrimedoesn't look like it is23:58
yankcrimeto the database!23:58

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