Monday, 2015-11-30

*** openstack has joined #openstack-meeting-314:23
*** openstack has joined #openstack-meeting-314:35
*** ChanServ sets mode: +o openstack14:35
*** klkumar has joined #openstack-meeting-314:36
*** openstack has joined #openstack-meeting-315:43
*** ChanServ sets mode: +o openstack15:43
*** klkumar has joined #openstack-meeting-315:43
*** Sukhdev_ has joined #openstack-meeting-315:46
*** flaper87 has joined #openstack-meeting-315:46
*** e0ne has joined #openstack-meeting-315:48
*** salv-orlando has joined #openstack-meeting-315:49
*** dims has joined #openstack-meeting-315:49
*** shaohe_feng has joined #openstack-meeting-315:50
*** sankarshan is now known as sankarshan_away15:50
*** bpokorny has joined #openstack-meeting-315:51
*** jtomasek has joined #openstack-meeting-315:52
*** corvus is now known as jeblair15:52
*** bpokorny has quit IRC15:52
*** amotoki has quit IRC15:53
*** vtech_ has quit IRC15:53
*** vtech has joined #openstack-meeting-315:53
*** vtech has quit IRC15:54
*** vtech has joined #openstack-meeting-315:54
*** ajmiller has joined #openstack-meeting-315:56
*** ^Gal^ has joined #openstack-meeting-315:57
*** jasondotstar has joined #openstack-meeting-315:58
*** sdague has joined #openstack-meeting-315:59
*** msambol has joined #openstack-meeting-316:00
jklare#startmeeting openstack_chef16:00
openstackMeeting started Mon Nov 30 16:00:29 2015 UTC and is due to finish in 60 minutes.  The chair is jklare. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: openstack_chef)"16:00
openstackThe meeting name has been set to 'openstack_chef'16:00
jklarehi all16:00
calbershi16:00
jklarei will wait some minutes for more people to join :)16:01
sc`hi!16:01
jklareyay16:01
jklarehi sc`16:01
*** e0ne has quit IRC16:02
sc`morning/afternoon16:02
jklarei guess we can start with our first and probably most important topic16:03
jklare#topic we need more active contributors16:03
*** openstack changes topic to "we need more active contributors (Meeting topic: openstack_chef)"16:03
*** haleyb has joined #openstack-meeting-316:03
*** banix has joined #openstack-meeting-316:04
jklarecurrently we are down a max of 5 people in our meetings16:04
jklareand although the we have made some progress regarding the designate cookbook and the refactoring process, the whole work is down to only a few people16:04
jklarewhich is "not ideal"16:05
sc`the main issue i see is that most folks that are active consumers are taking a point in time snapshot and working off of that16:05
*** vsaienko has left #openstack-meeting-316:05
sc`so they're not even looking towards master developments16:05
*** btully has quit IRC16:05
jklaresure, but usually you would come back from time to time to get the hot new stuff16:06
*** kevinbenton_ has quit IRC16:07
sc`depends. out of my team, i'm the only one keeping up with the project's goings on16:07
j^2hey guys16:07
*** btully has joined #openstack-meeting-316:07
j^2i'm sick so i'm not happy :(16:07
*** kevinbenton has joined #openstack-meeting-316:07
sc`'tis the season16:07
jklarei was thinking about maybe contacting the users commitee and ask them if we can start a short survey to figure out if people are acutally interested in using the cookbooks16:08
jklareso we could design the survey16:08
j^2jklare: they already have it as part of the survey16:08
j^2it's in the report16:08
jklarei guess they asked if people are using chef16:08
j^2yeah that's the best well get out of them16:09
jklarei think we need more detailed information16:10
markvan_hi16:10
jklarehi16:10
*** markvan_ is now known as markvan16:10
jklareand i guess that we could design a more detailed survey16:10
j^2jklare: yeah and i don't think they'll do that16:10
jklarequestion is if we can get people to answer this survey16:10
j^2from what i've been apart of the UC doesnt have that granulaity16:10
sc`there needs to be a better understanding as to who is actually using the cookbooks and would be interested in the continued development16:10
sc`surveys are nice, but they're totally opt-in16:11
jklareany other ideas on how to figure that out?16:11
j^2not a damn thing16:11
sc`unfortunately not16:11
j^2we have to just "continue" and push forward, make something for _us_ and if other want to join they will16:11
j^2it's becoming this over time16:12
j^2unless you speak up you'll get what we create16:12
*** irenab has joined #openstack-meeting-316:12
jklareyeah, but that sounds more like making people angry and then come and shout at us16:12
jklareits not an active process of getting people involved16:13
sc`we don't get much in the way of foot traffic on the ml or in the channel, unless someone hits a wtf moment or is just totally in the wrong channel16:13
j^2well as we all know we don't have involement right now, so even negitive involvement is better then no involement16:13
jklarenot sure about that16:15
jklarebut well16:15
sc`even the complainers are better than nothing at all16:15
jklarehow about trying to put some basic presentation together, that all of us can use and present whenever possible16:15
*** openstackstatus has joined #openstack-meeting-316:15
*** ChanServ sets mode: +v openstackstatus16:15
jklarei was thinking about giving one in some user groups16:16
jklarelike the openstack one16:16
jklareand the chef one16:16
sc`that might be a good thing to do. get some meatspace involvement in our local user groups16:16
jklareand the devops one16:16
jklareso like a short presentation on how cool it is to deploy a aio_neutron with our cookbooks16:16
sc`it's extremely inconvenient for me to attend meetups in my local area, but i can try to carve out some time to put on the sales hat16:17
sc`aio_neutron is a quick enough thing where one can kick off the build at the beginning of a presentation and end with showing off horizon or nova boot16:18
jklareyeah16:18
jklareexactly16:18
j^2nice16:18
j^2yeah like what i did i the model-t presenation? but positive not the "OH SHIT" converstation16:19
*** jlanoux has joined #openstack-meeting-316:20
jklarei am very short on time right now, but i guess i can try to put up some slides in the next weeks whenever i have some minutes16:21
j^2to quote sc` "tis the season"16:21
sc`:D16:21
sc`i like where things are going16:21
jklareyou do?16:21
sc`we need to do the sales-y thing to get active contributors16:22
j^2any free cycles are going to be decicated to what i wanted to talk about here actually16:22
j^2it seems i've been nominated to be on the ballot for OpenStack Board of Directors16:22
j^2i actually have a real shot at it16:23
sc`do you have enough nominations?16:23
j^2yep16:23
j^2and more so16:23
sc`nice :D16:23
j^2i've had people come to me and say they wanted to nominate me but couldn't16:23
j^2people i don't even know16:24
*** pballand has joined #openstack-meeting-316:24
sc`wow. really cool16:24
j^2:D16:24
jklaresounds great16:25
j^2can i ask yall to look something over for me?16:25
sc`sure16:26
jklare?16:26
*** rhagarty has joined #openstack-meeting-316:27
j^2nice, i have a doc, for my "answers for the ballot" I'll add you to a repo and post it there. Would you mind putting PRs against it for anything ranging from horrible grammar to odd wording?16:28
jklarei will try to take a look at it16:28
j^2rock on thanks guys16:29
*** shaohe_feng has quit IRC16:29
*** baoli has quit IRC16:29
j^2oh and i havent moved on the dnaas cookbook16:31
*** baoli has joined #openstack-meeting-316:31
j^2the meeting was canceled last week16:31
j^2so i'll be there this week talkiing about what we're doing with it16:32
jklarecool16:32
sc`awesome16:32
jklaremaybe some of the guys from the project are interested in helping16:32
j^2hopefully i'll have it "production ready changes" to it then from there docs then i'll ask yall to try it then we can get it in our namespace16:32
j^2jklare: that's the idea16:32
j^2right now their "dev environment" takes...30-40-60?ish mins to set up16:33
*** neiljerram has joined #openstack-meeting-316:33
j^2with this cookbook less then 10 with a chef exec kitchen verify16:33
j^2and you validate that it's up with serverspec16:33
j^2that's pretty sweet you have to admit16:33
jklareit is16:34
sc`that'd great stuff j^216:34
sc`that's16:34
j^2it's not converging since the last time i worked on it...but still; i have it in my sights. I just need cycles16:34
sc`as we all do. you should probably focus on getting better :p16:35
j^2sc`: ha!16:35
*** mwagner_lap has quit IRC16:35
*** mwagner_lap has joined #openstack-meeting-316:35
*** mounica has joined #openstack-meeting-316:35
jklare#topic refactoring16:38
*** openstack changes topic to "refactoring (Meeting topic: openstack_chef)"16:38
jklareno much new here16:38
jklarewe made some progress16:38
j^2:D16:38
jklareand i started the refactoring of the common cookbook and the libraries in it16:38
jklareits horrible16:38
jklarebut well16:38
j^2yeah the theory of common is amazing. but the implimenation has been...horrendus16:39
jklare^^16:39
sc`common == there be dragons16:39
jklare:)16:40
jklareany thoughts about moving all the endpoint attributes from common to the corresponding cookbooks?16:41
jklarei started that for identity16:41
j^2that seems logical to have them in their cookbooks, you may not need an endpoint created and if you call the common cookbook you might have it created16:42
j^2right?16:42
*** sdake has joined #openstack-meeting-316:42
sc`makes sense to move them to their own corresponding cookbooks and out of common16:42
j^2sc`: exactly16:43
jklareit makes the handling much easier16:43
jklareand the dependencies less confusing16:44
jklaremaybe we can reduce the common cookbook to just a library one16:44
j^2that'll be awesome16:44
sc`yup. easier to trace when things go wrong too16:44
jklare^^16:45
jklarei do not have any other topics for today16:46
*** sdake_ has joined #openstack-meeting-316:46
jklareanything from you guys?16:46
sc`i'm good16:46
j^2:D16:46
*** sdake has quit IRC16:46
*** carl_baldwin_ is now known as carl_baldwin16:47
*** baoli has quit IRC16:48
jklareok16:48
jklarethanks for attending and see your around16:48
jklare#endmeeting16:49
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:49
openstackMeeting ended Mon Nov 30 16:49:03 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-30-16.00.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-30-16.00.txt16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_chef/2015/openstack_chef.2015-11-30-16.00.log.html16:49
*** dtantsur has joined #openstack-meeting-316:50
*** calbers has quit IRC16:50
*** baoli has joined #openstack-meeting-316:50
*** rloo has joined #openstack-meeting-316:51
*** cinerama has joined #openstack-meeting-316:53
*** rpioso has joined #openstack-meeting-316:53
*** jpomeroy has joined #openstack-meeting-316:53
*** armax has joined #openstack-meeting-316:54
*** yuriyz|2 has joined #openstack-meeting-316:57
*** vtech has quit IRC16:58
*** vtech has joined #openstack-meeting-316:58
*** mjturek1 has joined #openstack-meeting-316:59
*** markvan has quit IRC16:59
*** pas-ha has joined #openstack-meeting-316:59
devananda#startmeeting ironic17:00
openstackMeeting started Mon Nov 30 17:00:25 2015 UTC and is due to finish in 60 minutes.  The chair is devananda. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
NobodyCamo/17:00
TheJuliao/17:00
mjturek1o/17:00
betherlyo/17:00
devanandahello everyone!17:00
NobodyCamgood morning17:00
pas-hao/17:00
*** mgould has joined #openstack-meeting-317:00
NobodyCam:)17:00
mgouldo/17:01
devanandaas usual, our agenda can be found on the wiki page here: https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting17:01
yuriyz|2o/17:01
JayFo/17:01
*** coolsvap has quit IRC17:01
dtantsuro/17:01
devanandatoday is a bit light, but I'll start with the announcements17:01
*** cdearborn has joined #openstack-meeting-317:01
vdroko/17:01
cdearborno/17:01
rpiosoo/17:01
*** markvan has joined #openstack-meeting-317:02
devanandaalso - for those who were out last week, welcome back from thanksgiving holiday :)17:02
*** vsaienko has joined #openstack-meeting-317:02
devananda#topic announcements17:02
*** sambetts has joined #openstack-meeting-317:02
*** openstack changes topic to "announcements (Meeting topic: ironic)"17:02
sambettso/17:02
rlooo/17:02
devanandajroll is out pretty much all week17:02
*** pc_m has joined #openstack-meeting-317:02
devanandahe's asked me to handle the M1 milestone and release, which I'll be doing by Thursday17:02
jrollhi, I'm sort-of-not-really-here for a few :)17:03
devanandaso let's focus on stability this week -- fixing bugs and not landing any half-baked or risky features17:03
devanandajroll: ohhai!17:03
devananda#chair jroll17:03
openstackCurrent chairs: devananda jroll17:03
jrollthanks for running things :D17:03
devanandasecond announcement is that we've moved away from launchpad for release notes generation, and are already using the new Reno project17:04
cineramao/17:04
*** jcook has joined #openstack-meeting-317:04
jroll(still need to move to reno for IPA, and ironicclient)17:04
*** egallen has joined #openstack-meeting-317:04
dtantsurdevananda, not for ironicclient yet, right?17:04
dtantsuryeah, and ironic-lib :)17:05
jroll^^17:05
*** gcb has quit IRC17:05
devanandayep17:05
devanandajroll: we're not planning a release of IPA or ironicclient this week though, correct?17:05
*** coolsvap has joined #openstack-meeting-317:05
rloowe probably should move to reno for all -- volunteers? :)17:05
jrolldevananda: correct17:05
*** Sukhdev_ has quit IRC17:06
*** sdake_ has quit IRC17:06
*** krtaylor has joined #openstack-meeting-317:06
devanandatldr; when you write a patch (or review a patch) that completes a feature, bug fix, or impacts anyone running ironic, please make sure it includes a release note update.17:06
*** derekh has joined #openstack-meeting-317:06
*** BadCub has joined #openstack-meeting-317:07
devananda#topic subteam status reports17:07
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"17:07
devanandaI'll give everyone a few minutes to look over the whiteboard ... :)17:07
NobodyCam#link http://docs.openstack.org/developer/reno/usage.html#creating-new-release-notes17:07
NobodyCamjust fyi17:07
rloois IPA a subteam report any more? Wondering if we should remove it17:07
devanandaNobodyCam: ty17:07
*** Nisha has joined #openstack-meeting-317:07
krtayloro/  sorry I'm late17:07
dtantsurrloo, IPA is everyone now ;)17:08
dtantsuryeah, ++ for removing17:08
rloodtantsur: yeah, i was wondering what would go there, but we have IPA like we have ironic-inspector so I guess yes, it should stay in.17:08
*** salv-orl_ has joined #openstack-meeting-317:08
dtantsurrloo, inspector is much more independent17:09
dtantsurIPA now is even more important than ironicclient now17:09
rloodtantsur: ++ for importance of IPA!17:09
*** vtech has quit IRC17:10
rloothe multiple compute hosts work is dependent on the node filter api/claims work, right?17:10
*** vtech has joined #openstack-meeting-317:10
devanandarloo: yah17:11
*** yuikotak_ has joined #openstack-meeting-317:11
rloowrt the spec for node filter API..., are there any major blockers?17:11
devanandawe've discussed doing an API-only POC for the claims/filtering, so that the nova driver work can start in earnest17:11
devanandabut the API itself is blocked in discussions in the spec17:11
*** salv-orlando has quit IRC17:11
*** Sukhdev_ has joined #openstack-meeting-317:12
*** Sukhdev_ has quit IRC17:12
devanandaI'll try to spend some time this week with penick to resolve his concerns17:12
rloodevananda: ok thx.17:12
*** sinval-afk has joined #openstack-meeting-317:12
rlooilo has 3rd party CI? Anyone know the status of that?17:13
dtantsurthere is a post on the ML, they just introduced it17:13
NobodyCamlast I heard they were working on getting external networkaccess17:13
devanandadtantsur: with a release coming later this week, I see you've noted a few bugs that should be prioritized17:13
sambettsit also got added as non-voting initally and was blocking the gate earlier today I believe17:14
NobodyCamrloo: I can follow up on that17:14
sambettsI think jroll fixed it17:14
jrollright - fyi, they aren't supposed to be announcing those on the dev list, if someone told them to do that please don't in the future :)17:14
jrollre ilo ^17:14
dtantsurilo announcement: http://lists.openstack.org/pipermail/openstack-dev/2015-November/080806.html17:14
rloojroll: what are they supposed to do?17:14
dtantsurdevananda, yeah, at least worth taking a look. one of them is the reason of big rant among tripleo folks :)17:14
dtantsurjroll, why?17:14
*** mariojv has joined #openstack-meeting-317:15
*** JeanBriceCombebi has quit IRC17:15
devanandasambetts: you mean ilo 3rd party ci was blocking the gate, or something else was?17:15
jrolldtantsur: rloo: I'm not sure, but the instructions are in third party CI docs... anteaya is replying to that mail about it17:15
sambettsdevananda: yes17:15
sambettsthe ilo ci17:15
*** vtech has quit IRC17:15
devanandasambetts: :-/17:15
rloojroll: if anteaya is replying, she'll set us all straight :)17:15
jrollyep :D17:16
anteayahow was a ci system blocking the gate?17:16
anteayaci systems vote verified on a patch at best17:16
jrollsambetts: devananda: I don't believe ilo ci was ever blocking the gate17:16
jrollthink that was a false alarm17:16
anteayathat does not block the gate17:16
jrollit *looks* to be voting but does not block17:16
* dtantsur asks17:16
devanandajroll: ok, that's what I would expect17:16
sambettsooo thats good then, sorry for the noise17:16
anteayaeven a ci system voting -1 verified on a patch does not block the gate17:16
devanandaI'm looking at a recent run right now and it seems fine17:16
*** Swami has joined #openstack-meeting-317:17
rlooyeah, I think it was a false alarm (that the 3rd party CI was affecting the gate)17:17
jrollya17:17
anteayareviewers are free to disregard any third party ci results when they review17:17
jrollilo CI suddenly appearing makes me so happy \o/17:17
dtantsur\o/17:17
devanandaindeed!17:17
rlooanteaya: but jroll sez that 3rd party CIs shouldn't be announced on dev list?17:17
sambettsYup :D17:17
anteayacorrect17:17
dtantsuranteaya, +1 to question, I've repeated it on the ML17:18
dtantsurwhere should I get such announcements?17:18
anteaya#link http://lists.openstack.org/pipermail/openstack-dev/2015-November/080808.html17:18
anteaya#link https://wiki.openstack.org/wiki/ThirdPartySystems17:18
sambettsthe ironic QA subteam/meeting has an etherpad here for status updates so that we can discuss them in the Ironic QA meeting on Wednesday's at 5 UTC17:18
sambettshttps://etherpad.openstack.org/p/IronicCI17:18
anteayaif you feel the need to have announcements you may announce in the ironic meeting17:18
anteayamost projects get tired of that fairly quickly but suit yourselves17:19
dtantsuranteaya, these links do not seem to answer our question..17:19
rlooanteaya: but I think it is fine to announce them in [ironic]17:19
rlooanteaya: as well as doing all that other stuff you have pointed out :)17:19
anteayarloo: in the channel fine, please not on the mailing list17:19
* dtantsur disagrees17:19
devanandaI think it is reasonable for each driver team, if they want to announce it in the meeting, to do so on the whiteboard section for their driver. we'll all see that in the weekly meeting17:19
devanandabut it will avoid spamming the whole openstack list17:20
anteayadevananda: +117:20
jrollI agree there's no need on the ML17:20
jrollI'm going to go continue my vacation, have a good week y'all and thanks for running things devananda :)17:20
devanandaanyway, we can discuss that further at another time. let's move on with the meeting17:20
devanandajroll: np! enjoy your vacation :)17:20
devananda#topic stuck specs17:20
*** openstack changes topic to "stuck specs (Meeting topic: ironic)"17:20
devananda#link https://review.openstack.org/#/c/224022/17:21
devanandarloo added this to the agenda17:21
devanandaI gave it a review just before the meeting17:21
*** nicodemos has joined #openstack-meeting-317:21
rloodevananda: i think yuiko wants an API that will tell them, for a particular node, what actions they can do next17:22
*** Piet has joined #openstack-meeting-317:22
devanandayuikotak_: around?17:23
rloodevananda: cuz it looks like they want to present some sort of GUI17:23
yuikotak_devananda, yes17:23
devanandakrotscheck: also, I think you had an interest in this work as it relates to building a UI17:23
*** dconde has joined #openstack-meeting-317:23
devanandarloo: that could be done muchmore efficiently by requesting the full set of states+verbs17:23
rloodevananda: well, someone could write something to get the full set of states/verbs, and get the list of nodes-with-provision-states, then write the mapping between the two.17:24
devanandafetching that data and dispaying the relevant item for each node in the client UI is much more efficient than fetching it for every node in a given display17:24
devanandarloo: right17:24
rloodevananda: or should we provide the mapping?17:24
rloodevananda: i have no idea whether this is something that lots of folks want or not.17:24
rloodevananda: my objection was to adding node.allowed_transitions :)17:25
devanandathe mapping may change in different versions of the server, so, yes, the server should expose the mapping17:25
devanandarloo: I agree with your objection, fwiw17:25
rloodevananda: ok, then we're good for that part. I guess yuikotak_ and others will have to convince devananda for some endpoint to show the allowed transitions for a particular node.17:26
rloodevananda: or did you mean it would be OK to have an endpoint to show the info for a particular node, vs an endpoint to show the possible states/transitions in the FSM?17:27
devanandarloo, yuikotak_: as I understand the problem statement, there are two situations where this info is needed17:27
devananda* client requested a state change, got an error, and wants to know what is allowed next17:27
devananda* client wants to display the potential actions for a lot of nodes without having to request an action first17:28
*** ihrachys has quit IRC17:28
devananda#1 is fixed by simply having better error messages. #2 would be fixed by adding a new general endpoint that returns the state machine as a dict17:28
devanandadoes that work?17:29
yuikotak_devananda, yes, exactly. thanks.17:29
devanandagreat :)17:29
rloothx yuikotak_, glad that handles your problem!17:30
rloothx devananda too :)17:30
yuikotak_rloo, thanks :)17:30
*** kzaitsev_mb has quit IRC17:30
devanandalast week was somewhat light, so that's it for the agenda today.17:31
devananda#topic open discussion17:31
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:31
devanandaanyone have stuff to discuss? :)17:31
vdrokI've had a question about adding new service under ironic umbrella, and would like to hear your thoughts about it :)17:32
vdrokWe're considering adding new hardware compositor service under ironic umbrella17:32
devanandavdrok: great - tell me about this service pls17:32
vdrokThere is this thing called intel racj scale architecture - http://www.intel.com/content/www/us/en/architecture-and-technology/rack-scale-architecture/intel-rack-scale-architecture-resources.html17:32
vdrokWhich supports creating servers on demand, based on redfish, e.g. you can post a request with some hw requirements and it will create this "node" if possible, and return the link to it17:32
vdrokmaybe there are similar things from other vendors17:33
vdrokThe current idea is that nova will use it to compose new nodes if there are no bm servers available and then register them in ironic17:33
vdrokironic may use it too, e.g. free the resources on node-deletion17:34
vdrokso the idea is to have some generic api that will be able to work with intel rsa and other alike services17:34
devanandavdrok: it sounds sort of like a new driver that, when a node is enrolled, actually does some interaction with the rack to "create" the hardware17:35
devanandaor s/create/compose/17:35
krtaylorwhy wouldn't that be a redfish driver for ironic, what is extra17:35
devanandavdrok: fwiw, there are several folks (myself included) interested in creating a generic redfish driver17:35
krtaylor++17:36
devanandabcornec and I started hacking on a python redfish client about a year ago17:36
sambettsI think this is more similar to something I'd like to see which is letting flavors decide the hardware not the other way around17:36
vdrokyeah, but the idea is that nova can create it too, if e.g. no machines match the flavor17:36
*** jlanoux has quit IRC17:36
devanandaperhaps its time to get more folks working on that17:36
dtantsurby the way, enrolling hooks is something that people definitely want17:36
devanandasambetts: right17:36
devanandaanyone from the oneview team here?17:37
sambettsit doesn't look like it but we talks about that at the summit because that was something they are looking out for17:37
devanandaI think they were talking about something similar at one point, where the nova flavor is used to inform or customize the hardware17:37
NobodyCamdevananda: I would also toss out there the ablity to create a "active" node17:37
vdrokthis is all just an idea for now, what is a preferred way to gather feedback, as in meeting seems to be too short on time?17:38
*** nkrinner has quit IRC17:38
vdrokshould it be a spec that describes everything in detail>17:38
devanandavdrok: yea, meeting is a good way to bring it up and raise the topic, but we should follow it up in long-form on the ML17:38
vdrokor blueprint, or ml post?17:38
sambettsI was actually thinking that the claims API might be a good place to put the logic for something like this, because we'd be injesting the whole flavor17:38
devanandavdrok: if you have a design in mind, a spec is a good idea. but if you're still gathering ideas (wnat to see what other vendors need) then the ML is a good next step17:39
krtaylorvdrok, I am wondering why nova would be handling BM directly at all when that is what ironic is for17:39
* krtaylor is curious, learning17:40
vdrokkrtaylor, well, this is not a "hardware" when nova does the request to it17:40
devanandakrtaylor: nova holds the concept of a flavor. the ironic virt driver could determine that a request came in but doesn't match any existing hardware, and then go "compose" that hardware and enroll it in Ironic17:40
devanandakrtaylor: at least that is what I htink folks are suggesting17:40
vdrokdevananda, yep :)17:40
sambetts:)17:40
krtaylorah, ok, interesting, thanks for the clarification17:40
dtantsurdevananda, that would make nova aware of our drivers, right?17:41
devanandadtantsur: good point ....17:41
sambettsnot if it was through the claims API ;)17:41
rlooalthough the nova-ironic driver would have to get that new composed node into 'available' state to be able to use it right away.17:41
devanandadtantsur: if it were a new interface or service, then no?17:41
*** paul-carlton1 has joined #openstack-meeting-317:41
dtantsurdevananda, or just internal part of claims API?17:41
devanandarloo: right. and it may take some time for the hardware to become available, so such a request may be much slower ...17:42
dtantsurI see value in not sharing too many details with nova17:42
devanandadtantsur: ++17:42
*** vkmc has joined #openstack-meeting-317:42
*** egallen has quit IRC17:42
devanandadtantsur: I'm trying to imagine how this fits in the claim API and struggling, perhaps because that API isn't well defined yet17:42
devanandathe claims API that I proposed at least, is essentially just a search API with an extra field saying "reserve N of these if you find them"17:43
devanandabut it could express non-equality as well17:43
devanandaso it isn't a good fit for "make me a server with X, Y, Z"17:43
dtantsurgood point about non-equality, yeah17:43
devanandait seems like a closer fit to the enroll->manageable transition17:44
*** Nisha has quit IRC17:44
devanandacould reach out and "create" the hardware according to the specifications, as long as the mgmt info is good17:44
dtantsurmmmmm, right17:44
dtantsuryeah, so we can enroll virtual (wannabe) nodes17:44
sambettsbut then thats not being driven by the nova/flavor right?17:44
dtantsurand them materialize them17:44
devanandavdrok: so, I do think there are other vendors interested in this17:44
devanandasambetts: not right now, but it could be17:45
*** egallen has joined #openstack-meeting-317:45
devanandaSoftLayer folks demo'd something similar in Tokyo17:45
devanandawhere a nova-scheduler plugin they wrote enrolled nodes in Ironic in order to satisfy requests17:45
devanandait had nothing to do with composable hardware, but the effect (add a new server to ironic between "nova boot" and the virt driver taking over) was similar17:46
NobodyCamI could see a case for this in both claim and enroll api,17:46
sambettsdid it call out to a separate system to check for avalible resources?17:46
devanandasambetts: yah17:46
sambettshmmm, thats cool /me adds postit note to go dig up that presentation17:47
vdrokso ok, will put something up in ml discussion till tomorrow, thanks :)17:47
devanandavdrok: thanks! good discussion17:48
sambettsvdrok: thanks for bring it up17:48
devanandaany other topics folks want to discuss?17:49
derekhbefore the end I'd like to draw people attention the a mail I sent earlier today http://lists.openstack.org/pipermail/openstack-dev/2015-November/080796.html17:49
derekhessentially I'd like to turn tripleo ci back on for ironic, it would be great if ye could take a look at the mail and weigh in etc...17:50
NobodyCamas this is my first meeting back I wanted to thank every one for the well wishes when I was out.. Thank you all :)17:50
*** klkumar has quit IRC17:50
rlooderekh: i was just replying. i don't understand - would the tripleo be voting or non voting?17:50
devanandaNobodyCam: welcome back :)17:50
NobodyCam:)17:51
*** egallen_ has joined #openstack-meeting-317:51
rloowelcome back NobodyCam!17:51
*** egallen has quit IRC17:51
*** egallen_ is now known as egallen17:51
derekhrloo: it would be the exact same way as it used to be but I would aks you now to ignore the results when pressing approve17:52
devanandaderekh: are changes in ironic causing frequent breakages in tripleo's gate?17:52
derekh*aks17:52
derekh*ask17:52
rlooderekh: you mean 'not ignore' :)17:52
derekhrloo: yup17:52
derekhdevananda: not frequently, now that we are not currently running trunk its hard to know for sure17:53
rlooderekh: why not make it vote then? or do we want to try it as you suggest and see what happens?17:53
devanandaderekh: running those jobs on ironic's gate cascadingly affects other projects' gate (nova, etc) as well17:53
derekhdevananda: you wouldn't be running it in the gate, it would be a check job run when the patch is proposed17:54
devanandaderekh: so any instability in any tripleo projects' gates will have a compounding effect on the merge queue, especially during release crunches17:54
devanandaderekh: oh17:54
*** dimtruck is now known as zz_dimtruck17:55
devanandaderekh: hm, ok. wdyt about adding it as a third-party system to ironic? that may be a terrible idea, just throwing it out there :)17:55
derekhdevananda: this is the same thing ironic used to have17:55
devanandaderekh: at one point, dib was voting in our gate IIRC17:55
rloodevananda: what does it matter if it is a 'third-party system' or not?17:55
devanandaso that's what I thought you were suggesting at first17:55
devanandarloo: the way in which it gets reported. it affects jenkins17:56
derekhdevananda: I don't think it can be a 3rd party system as its being run by infra, but its only a cosmetic thing17:56
*** salv-orl_ has quit IRC17:56
derekhdevananda: you may have had some DIB job in your gate but it wasn't the tripleo job, tripleo jobs were never in the gate17:57
*** salv-orlando has joined #openstack-meeting-317:57
devanandaderekh: right17:57
devanandawhen I was active in tripleo, we had discussed with infra running those as third-party jobs. a lot has changed since then ...17:57
devanandain any case, a voting check job that fails will effectively prevent a patch from merging17:58
*** [1]cdearborn has joined #openstack-meeting-317:58
*** [1]cdearborn has left #openstack-meeting-317:59
NobodyCam*time*17:59
devanandarloo: whereas a third-party vote will not prevent a patch from merging17:59
derekhdevananda: it doesn't and core can approve and ignore the result, all I would be asking is that you don't ignore the result unless you have a good reason not to17:59
devanandaderekh: non-voting job seems fine to me, but I still think it would get more visibility as a third-party job18:00
*** paul-carlton1 has quit IRC18:00
devanandaanyhow, time..18:00
betherlyThanks :)18:00
devanandathanks everyone!18:00
devananda#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Nov 30 18:00:20 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-30-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-30-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2015/ironic.2015-11-30-17.00.log.html18:00
NobodyCamthank you all good meeting18:00
derekhok, thanks, gotta run, reply to email if there is more to discusse18:00
*** pc_m has left #openstack-meeting-318:00
*** yuikotak_ has quit IRC18:01
*** salv-orlando has quit IRC18:01
mgouldo/18:02
*** mgould has left #openstack-meeting-318:02
*** dtantsur has left #openstack-meeting-318:02
*** zz_dimtruck is now known as dimtruck18:02
*** derekh has quit IRC18:02
*** rpioso has left #openstack-meeting-318:03
*** jwang_ has quit IRC18:04
*** vgridnev has joined #openstack-meeting-318:07
*** jwang has joined #openstack-meeting-318:08
*** baoli_ has joined #openstack-meeting-318:10
*** sambetts is now known as sambetts-afk18:11
*** cdearborn has quit IRC18:11
*** paul-carlton1 has joined #openstack-meeting-318:12
*** baoli has quit IRC18:14
*** sarob has quit IRC18:14
*** jpomeroy has quit IRC18:15
*** sarob has joined #openstack-meeting-318:17
*** flwang has quit IRC18:17
*** baoli_ has quit IRC18:18
*** fungi has quit IRC18:20
*** davidlenwell has quit IRC18:21
*** davidlenwell has joined #openstack-meeting-318:23
*** krtaylor has quit IRC18:23
*** reed has quit IRC18:24
*** mrmartin has joined #openstack-meeting-318:25
*** TheJulia has quit IRC18:26
*** yamamoto has quit IRC18:27
*** doug-fish has quit IRC18:28
*** reed has joined #openstack-meeting-318:28
*** banix has quit IRC18:29
*** aweeks has quit IRC18:33
*** paul-carlton1 has quit IRC18:33
*** fungi has joined #openstack-meeting-318:34
*** fitoduarte has joined #openstack-meeting-318:36
*** BadCub has left #openstack-meeting-318:37
*** flwang has joined #openstack-meeting-318:38
*** ifat_afek has quit IRC18:39
*** krtaylor has joined #openstack-meeting-318:41
*** banix has joined #openstack-meeting-318:43
*** s3wong has joined #openstack-meeting-318:44
*** TheJulia has joined #openstack-meeting-318:46
*** jpomeroy has joined #openstack-meeting-318:55
*** TheJulia has quit IRC18:55
*** salv-orlando has joined #openstack-meeting-318:57
*** markmcclain has joined #openstack-meeting-318:57
*** TheJulia has joined #openstack-meeting-319:04
*** egallen has quit IRC19:09
*** sdake has joined #openstack-meeting-319:10
*** neelashah has joined #openstack-meeting-319:10
*** btully has quit IRC19:10
*** btully has joined #openstack-meeting-319:11
*** salv-orlando has quit IRC19:19
*** egallen has joined #openstack-meeting-319:19
*** salv-orlando has joined #openstack-meeting-319:20
*** egallen has quit IRC19:23
*** ihrachys has joined #openstack-meeting-319:23
*** safchain has quit IRC19:24
*** yamamoto has joined #openstack-meeting-319:28
*** neelashah has quit IRC19:31
*** yamamoto has quit IRC19:33
*** markmcclain has quit IRC19:41
*** markmcclain has joined #openstack-meeting-319:41
*** sdake has quit IRC19:43
*** pas-ha has left #openstack-meeting-319:54
*** sinval-afk is now known as sinval19:56
*** dimtruck is now known as zz_dimtruck19:56
*** kzaitsev_mb has joined #openstack-meeting-320:01
*** egallen has joined #openstack-meeting-320:02
*** zz_dimtruck is now known as dimtruck20:11
*** doug-fish has joined #openstack-meeting-320:14
*** ihrachys has quit IRC20:23
*** egallen has quit IRC20:25
*** kzaitsev_mb has quit IRC20:27
*** neelashah has joined #openstack-meeting-320:28
*** salv-orlando has quit IRC20:35
*** salv-orlando has joined #openstack-meeting-320:35
*** neelashah has quit IRC20:38
*** neiljerram has quit IRC20:38
*** matrohon has joined #openstack-meeting-320:44
*** doug-fish has quit IRC20:51
*** belmoreira has joined #openstack-meeting-320:53
*** dims_ has joined #openstack-meeting-320:53
*** doug-fish has joined #openstack-meeting-320:54
*** doug-fis_ has joined #openstack-meeting-320:55
*** dims has quit IRC20:56
*** doug-fi__ has joined #openstack-meeting-320:57
*** doug-fish has quit IRC20:58
*** doug-fis_ has quit IRC21:00
*** sarob_ has joined #openstack-meeting-321:01
*** doug-fi__ has quit IRC21:02
*** dims_ has quit IRC21:03
*** Piet has quit IRC21:04
*** doug-fish has joined #openstack-meeting-321:04
*** doug-fish has quit IRC21:09
*** vgridnev has quit IRC21:13
*** dims has joined #openstack-meeting-321:14
*** mrmartin has quit IRC21:22
*** sdake has joined #openstack-meeting-321:25
*** doug-fish has joined #openstack-meeting-321:32
*** doug-fis_ has joined #openstack-meeting-321:35
*** doug-fis_ has quit IRC21:35
*** doug-fis_ has joined #openstack-meeting-321:35
*** doug-fish has quit IRC21:37
*** Piet has joined #openstack-meeting-321:41
*** dims_ has joined #openstack-meeting-321:42
*** baoli has joined #openstack-meeting-321:43
*** baoli has quit IRC21:43
*** dims has quit IRC21:43
*** sdake_ has joined #openstack-meeting-321:47
*** sdake has quit IRC21:47
*** baoli has joined #openstack-meeting-321:52
*** vgridnev has joined #openstack-meeting-321:53
*** fitoduarte has quit IRC21:54
*** matrohon has quit IRC21:55
*** dedery has joined #openstack-meeting-321:56
*** mwagner_lap has quit IRC21:57
*** sarob_ has quit IRC21:57
*** Haunted has joined #openstack-meeting-321:57
*** Haunted has left #openstack-meeting-321:59
*** sdake_ has quit IRC22:02
*** notmyname has quit IRC22:05
*** notmyname has joined #openstack-meeting-322:06
*** markvoelker has joined #openstack-meeting-322:07
*** Haunted has joined #openstack-meeting-322:13
*** Haunted has left #openstack-meeting-322:15
*** julim has quit IRC22:16
*** neelashah has joined #openstack-meeting-322:21
*** neelashah has quit IRC22:26
*** vgridnev has quit IRC22:27
*** Haunted has joined #openstack-meeting-322:28
Hauntedhi22:28
*** Haunted has left #openstack-meeting-322:28
*** vijendar has quit IRC22:34
*** neelashah has joined #openstack-meeting-322:34
*** egallen has joined #openstack-meeting-322:38
*** btully has quit IRC22:41
*** neelashah has quit IRC22:43
*** btully has joined #openstack-meeting-322:43
*** doug-fis_ has quit IRC22:44
*** doug-fish has joined #openstack-meeting-322:44
*** jpomeroy has quit IRC22:46
*** lkoranda_ has joined #openstack-meeting-322:48
*** doug-fish has quit IRC22:49
*** doug-fish has joined #openstack-meeting-322:49
*** lkoranda has quit IRC22:50
*** doug-fis_ has joined #openstack-meeting-322:50
*** lkoranda_ has quit IRC22:52
*** doug-fish has quit IRC22:54
*** doug-fis_ has quit IRC22:55
*** mounica has quit IRC22:56
*** mwagner_lap has joined #openstack-meeting-322:57
*** lkoranda has joined #openstack-meeting-322:58
*** yamahata has joined #openstack-meeting-322:58
*** banix has quit IRC22:59
*** dims has joined #openstack-meeting-323:02
*** doug-fish has joined #openstack-meeting-323:03
*** dims_ has quit IRC23:03
*** doug-fish has quit IRC23:07
*** mariojv has left #openstack-meeting-323:08
*** msambol has quit IRC23:10
*** dtardivel has quit IRC23:17
*** jmckind has quit IRC23:23
*** peristeri has quit IRC23:23
*** hichihara has joined #openstack-meeting-323:30
*** barra204 has quit IRC23:38
*** shakamunyi has joined #openstack-meeting-323:38
*** f13o has joined #openstack-meeting-323:41
*** sigmavirus24 is now known as sigmavirus24_awa23:44
*** egallen has quit IRC23:45

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