Tuesday, 2014-01-21

*** rraja has quit IRC00:00
*** amytron has quit IRC00:01
*** mozawa has joined #openstack-meeting-alt00:04
*** IlyaE has quit IRC00:07
*** rakhmerov has quit IRC00:08
*** rakhmerov1 has joined #openstack-meeting-alt00:08
*** ashaikh has quit IRC00:12
*** julienvey_ has quit IRC00:13
*** rakhmerov1 has quit IRC00:14
*** markwash has quit IRC00:16
*** aelkikhia has quit IRC00:17
*** markwash has joined #openstack-meeting-alt00:18
*** safchain has quit IRC00:20
*** svetlanad has quit IRC00:33
*** svetlanad has joined #openstack-meeting-alt00:34
*** rnirmal has quit IRC00:45
*** banix has joined #openstack-meeting-alt00:59
*** ashaikh has joined #openstack-meeting-alt01:08
*** svetlanad has quit IRC01:33
*** svetlanad has joined #openstack-meeting-alt01:34
*** jaypipes has quit IRC01:37
*** xuhanp_ has joined #openstack-meeting-alt01:41
*** bdpayne has quit IRC01:46
*** coolsvap has quit IRC01:51
*** hockeynut has joined #openstack-meeting-alt01:59
*** nosnos has joined #openstack-meeting-alt01:59
*** flwang has quit IRC02:02
*** hockeynut has quit IRC02:04
*** balajiiyer has joined #openstack-meeting-alt02:17
*** yogesh has quit IRC02:21
*** colinmcnamara has quit IRC02:28
*** yamahata has quit IRC02:29
*** colinmcnamara has joined #openstack-meeting-alt02:29
*** svetlanad has quit IRC02:33
*** svetlanad has joined #openstack-meeting-alt02:33
*** amcrn has joined #openstack-meeting-alt02:40
*** flwang has joined #openstack-meeting-alt02:46
*** amytron has joined #openstack-meeting-alt02:53
*** IlyaE has joined #openstack-meeting-alt03:02
*** flwang has quit IRC03:16
*** flwang has joined #openstack-meeting-alt03:16
*** AlanClark has quit IRC03:22
*** colinmcnamara has quit IRC03:27
*** sbalukoff has quit IRC03:27
*** dguitarbite has joined #openstack-meeting-alt03:28
*** yamahata has joined #openstack-meeting-alt03:32
*** doug_shelley66 has quit IRC03:32
*** svetlanad has quit IRC03:33
*** svetlanad has joined #openstack-meeting-alt03:34
*** woodster1 has joined #openstack-meeting-alt03:40
*** hockeynut has joined #openstack-meeting-alt03:43
*** hockeynut has quit IRC03:47
*** sankarshan_away is now known as sankarshan03:54
*** mattgriffin has quit IRC04:17
*** bdpayne has joined #openstack-meeting-alt04:25
*** yogesh_ has joined #openstack-meeting-alt04:27
*** yogesh has joined #openstack-meeting-alt04:30
*** svetlanad has quit IRC04:33
*** svetlanad has joined #openstack-meeting-alt04:33
*** yogesh_ has quit IRC04:34
*** coolsvap has joined #openstack-meeting-alt04:38
*** mattgriffin has joined #openstack-meeting-alt04:40
*** IlyaE has quit IRC05:04
*** SergeyLukjanov_ is now known as SergeyLukjanov05:06
*** chandankumar_ has joined #openstack-meeting-alt05:14
*** bdpayne has quit IRC05:16
*** IlyaE has joined #openstack-meeting-alt05:26
*** IlyaE has quit IRC05:32
*** svetlanad has quit IRC05:33
*** svetlanad has joined #openstack-meeting-alt05:34
*** banix has quit IRC05:36
*** SushilKM has joined #openstack-meeting-alt05:44
*** balajiiyer has quit IRC05:48
*** SushilKM has left #openstack-meeting-alt05:49
*** aignatov_ has joined #openstack-meeting-alt05:52
*** akuznetsov has quit IRC05:59
*** rakhmerov has joined #openstack-meeting-alt06:03
*** nati_ueno has quit IRC06:06
*** SergeyLukjanov is now known as SergeyLukjanov_a06:12
*** SergeyLukjanov_a is now known as SergeyLukjanov_06:13
*** bdpayne has joined #openstack-meeting-alt06:16
*** nati_ueno has joined #openstack-meeting-alt06:22
*** nati_ueno has quit IRC06:23
*** nati_ueno has joined #openstack-meeting-alt06:24
*** akuznetsov has joined #openstack-meeting-alt06:26
*** woodster1 has quit IRC06:31
*** svetlanad has quit IRC06:33
*** markvoelker has quit IRC06:33
*** svetlanad has joined #openstack-meeting-alt06:34
*** doug_shelley66 has joined #openstack-meeting-alt06:36
*** akuznetsov has quit IRC06:37
*** akuznetsov has joined #openstack-meeting-alt06:37
*** aignatov_ has quit IRC06:38
*** amytron has quit IRC06:38
*** SergeyLukjanov_ is now known as SergeyLukjanov06:42
*** bdpayne has quit IRC06:55
*** akuznets_ has joined #openstack-meeting-alt07:05
*** akuznetsov has quit IRC07:08
*** csaba|afk is now known as csaba07:09
*** nati_uen_ has joined #openstack-meeting-alt07:12
*** nati_uen_ has quit IRC07:13
*** nati_uen_ has joined #openstack-meeting-alt07:14
*** aignatov_ has joined #openstack-meeting-alt07:14
*** nati_ueno has quit IRC07:16
*** ashaikh has quit IRC07:26
*** sankarshan is now known as sankarshan_away07:26
*** sankarshan_away is now known as sankarshan07:27
*** sankarshan is now known as sankarshan_away07:27
*** SergeyLukjanov is now known as SergeyLukjanov_07:29
*** IlyaE has joined #openstack-meeting-alt07:30
*** nadya__ has joined #openstack-meeting-alt07:31
*** nadya__ has quit IRC07:31
*** svetlanad has quit IRC07:33
*** svetlanad has joined #openstack-meeting-alt07:33
*** amotoki has joined #openstack-meeting-alt07:38
*** amcrn has quit IRC07:45
*** NikitaKonovalov_ is now known as NikitaKonovalov07:45
*** mattgriffin has quit IRC07:54
*** jtomasek has joined #openstack-meeting-alt07:56
*** aignatov_ has quit IRC08:01
*** nati_ueno has joined #openstack-meeting-alt08:02
*** nati_ueno has quit IRC08:02
*** nati_ueno has joined #openstack-meeting-alt08:03
*** nati_uen_ has quit IRC08:05
*** IlyaE has quit IRC08:10
*** _ruhe is now known as ruhe08:11
*** jcoufal has joined #openstack-meeting-alt08:13
*** flaper87|afk is now known as flaper8708:14
*** julienvey_ has joined #openstack-meeting-alt08:19
*** julienvey_ has quit IRC08:28
*** woodster1 has joined #openstack-meeting-alt08:32
*** woodster1 has quit IRC08:36
*** SergeyLukjanov_ is now known as SergeyLukjanov08:37
*** mattgriffin has joined #openstack-meeting-alt08:37
*** DinaBelova_ is now known as DinaBelova08:43
*** safchain has joined #openstack-meeting-alt08:43
*** yamahata has quit IRC08:45
*** nati_uen_ has joined #openstack-meeting-alt08:51
*** aignatov_ has joined #openstack-meeting-alt08:51
*** nati_ueno has quit IRC08:55
*** nati_uen_ has quit IRC08:56
*** markwash has quit IRC08:56
*** nati_ueno has joined #openstack-meeting-alt08:57
*** mattgriffin has quit IRC09:00
*** boris-42 has quit IRC09:00
*** derekh has joined #openstack-meeting-alt09:00
*** boris-42 has joined #openstack-meeting-alt09:00
*** woodster1 has joined #openstack-meeting-alt09:02
*** aignatov_ has left #openstack-meeting-alt09:03
*** woodster1 has quit IRC09:06
*** aignatov has joined #openstack-meeting-alt09:10
*** mozawa has quit IRC09:49
*** nati_uen_ has joined #openstack-meeting-alt09:50
*** nati_ueno has quit IRC09:54
*** nati_uen_ has quit IRC09:57
*** nati_ueno has joined #openstack-meeting-alt09:58
*** johnthetubaguy has joined #openstack-meeting-alt10:05
*** coolsvap has quit IRC10:09
*** coolsvap has joined #openstack-meeting-alt10:12
*** rakhmerov has quit IRC10:12
*** coolsvap has quit IRC10:23
*** coolsvap has joined #openstack-meeting-alt10:27
*** aignatov is now known as aignatov_10:29
*** dguitarbite has quit IRC10:29
*** dguitarbite has joined #openstack-meeting-alt10:29
*** xuhanp_ has quit IRC10:29
*** flwang has quit IRC10:30
*** boris-42 has quit IRC10:38
*** ruhe is now known as _ruhe10:39
*** rakhmerov has joined #openstack-meeting-alt10:42
*** IgorYozhikov has quit IRC10:44
*** IgorYozhikov has joined #openstack-meeting-alt10:44
*** nati_uen_ has joined #openstack-meeting-alt10:46
*** rakhmerov has quit IRC10:47
*** nati_ueno has quit IRC10:49
*** _ruhe is now known as ruhe10:54
*** yogesh has quit IRC10:54
*** aignatov_ is now known as aignatov11:01
*** SergeyLukjanov is now known as SergeyLukjanov_11:15
*** jcoufal has quit IRC11:17
*** SergeyLukjanov_ is now known as SergeyLukjanov11:19
*** jcoufal has joined #openstack-meeting-alt11:42
*** rakhmerov has joined #openstack-meeting-alt11:43
*** rakhmerov has quit IRC11:48
*** dguitarbite has quit IRC11:58
*** dguitarbite has joined #openstack-meeting-alt12:03
*** yogesh has joined #openstack-meeting-alt12:05
*** ruhe is now known as _ruhe12:05
*** boris-42 has joined #openstack-meeting-alt12:05
*** csaba is now known as csaba|afk12:07
*** yogesh has quit IRC12:10
*** _ruhe is now known as ruhe12:11
*** coolsvap has quit IRC12:22
*** svetlanad has quit IRC12:28
*** flwang has joined #openstack-meeting-alt12:29
*** DinaBelova is now known as DinaBelova_12:37
*** rakhmerov has joined #openstack-meeting-alt12:44
*** rakhmerov has quit IRC12:49
johnthetubaguyis there are PCI passthrough meeting today?12:51
ijwof course12:52
ijwWe're hard workers12:52
*** xuhanp has joined #openstack-meeting-alt12:52
ijwyou have 8 minutes.  Go read the doc12:53
johnthetubaguycool, I am back from my travels so can join,  the google doc you send around right?12:53
ijwyup12:56
ijwIt's current and currently we seem to agree on it12:56
ijwIf you hate it, then beware the wrath of angry PCI developers12:56
*** irenab has joined #openstack-meeting-alt12:56
ijwIt's probably akin to being mauled by kittens, but hey, cat scratch fever12:56
*** sgordon_ has joined #openstack-meeting-alt12:57
*** heyongli has joined #openstack-meeting-alt12:57
ijwthey come.12:58
heyonglihi, ijw12:58
*** amotoki has quit IRC12:58
*** sadasu has joined #openstack-meeting-alt12:58
irenabhi all12:58
sadasuHello!12:59
ijwhey12:59
irenabijw: are you starting the meeting?13:00
ijwCan do, isn't Robert about today?13:01
ijw#startmeeting pci_passthrough13:01
openstackMeeting started Tue Jan 21 13:01:26 2014 UTC and is due to finish in 60 minutes.  The chair is ijw. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** BrianB_ has joined #openstack-meeting-alt13:01
*** openstack changes topic to " (Meeting topic: pci_passthrough)"13:01
openstackThe meeting name has been set to 'pci_passthrough'13:01
ijwWelcome one and all.13:01
heyongli#link https://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#API_interface13:01
heyonglibp update13:01
ijwMarvellous13:01
ijwIs it any good?13:02
ijw;)13:02
heyonglimaybe miss sth, or sth wrong ,please check it13:02
johnthetubaguyso are the blueprints ready to review, and inline with the google doc now?13:02
*** SergeyLukjanov is now known as SergeyLukjanov_a13:02
heyonglijohnthetubaguy, updated bp based on these days discuss, i don't update any google docs.13:03
*** markvoelker has joined #openstack-meeting-alt13:03
ijwOK, I see a couple of typos but it's basically good.  Seems like it's pretty much the same as the google doc13:03
*** SergeyLukjanov_a is now known as SergeyLukjanov_13:03
heyongliijw, it should be.13:03
irenabheyongli: I'll take a look after the meeting13:03
heyongliirenab, sure, i suggest edit the wiki directly tag with your name, maybe13:04
ijwHow are we transitioning from the old config items to the new ones?13:04
irenabjohnthetubaguy: there is Ian's google doc, that may be worth to look at13:04
johnthetubaguyyeah, had a quick read13:04
ijwSimply remove the old ones and deny everything?  I don't know if that will fly.13:05
johnthetubaguyjust looking at the blueprint13:05
heyonglii link it to bp already.13:05
irenabheyongli: will do13:06
ijwheyongli: OK, we're in the lull between I2 and I3 practically (more so cos the gate is down) so I suggest we line up our patches ready to get in when I3 opens13:06
*** baoli has joined #openstack-meeting-alt13:06
baoliHi13:06
irenabbaoli: hi13:06
johnthetubaguywe can do the review now, I would just get your code up right away13:06
johnthetubaguyits going to be hard getting into I3, its quite full already13:07
ijwbaoli for arguments, heyongli for libvirt data gathering, bobball (who's avoiding us again) for xenapi and irenab for Neutron.  I guess I'll take the scheduler?13:07
johnthetubaguyI can cover the xenapi side a little bit13:07
ijwjohnthetubaguy: if we had code that would work better.13:07
*** DinaBelova_ is now known as DinaBelova13:07
ijwAnd we managed H3 last time as I recall13:08
baolisorry for joining late. ARe we talking about work division?13:08
johnthetubaguyijw: what are the XenAPI worries, I chair the subteam meeting, so I can bring those up there if you like13:08
heyongliwhat's the libvirt data gathering?13:08
ijwjohnthetubaguy: mainly that bob was saying they'd started on implementation of current functionality without regard to the new plans13:08
ijwheyongli: pci_information basically13:08
johnthetubaguyijw: right, I don't think its a big deal, its mostly low level plumbing13:09
sadasubaoli: yes13:09
*** SergeyLukjanov_ is now known as SergeyLukjanov13:09
heyongliijw, sure, and we had one people more for API13:09
johnthetubaguyijw: I did warn them about the new plans, but not sure I got the full picture across13:09
irenabfor neutron rkukura is also doing some patch that we may use for extending port attributes13:09
ijwOK - well the BP is there and I think subject to some minor edits it looks like I expected.13:09
ijwWe all need to review that for tomorrow13:09
irenabijw: action item?13:10
ijw#action All to review the BP by tomorrow13:10
ijwNot that the meetingbot loves me13:10
baoliSorry, which BP?13:10
ijwhttps://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#API_interface13:10
ijwWell, all of it, not just that section13:11
baolisure.13:11
baoliWhat's the plan for today?13:11
ijwWe don't have one as such13:12
johnthetubaguyI have some initial feedback on that blueprint, it seems unclear to me where pci_flavor is stored?13:12
ijwUnless we want to discuss the network scheduling (I put a section in the google doc but I think we all agreed that we wouldn't do it yet)13:12
ijwjohnthetubaguy: DB13:12
irenabbaoli: ijw: lets try to see that all parts have owner and relevant bp13:13
ijwjohnthetubaguy: Section at the bottom referring to DB13:13
irenabijw: lets try focus on plan A, to make some to I-3?13:13
ijwirenab: indeed13:13
johnthetubaguyijw: but in what format in the DB? it seemed to suggest it was in configuration earlier in the doc, may have missread13:13
ijwThe section at the bottom sketches out the table format13:14
*** amotoki has joined #openstack-meeting-alt13:14
heyonglijohnthetubaguy, store them in Database i think, DB in the later section.13:14
*** pdmars has joined #openstack-meeting-alt13:14
johnthetubaguyAh, my quick reading failed me again13:14
johnthetubaguyseems like a duplication of host aggregates to me, but that might not be a bad thing13:14
irenabjohnthetubaguy: we may need host agggregates in addition13:15
johnthetubaguyI don't see why you need both, but I could be missing something13:16
sdaguethere isn't any existing metadata store you could use instead? seems odd to create whole new table for this.13:16
johnthetubaguyyeah, host aggregates does seem to fit what you need quite well13:17
ijwjohnthetubaguy: It's not host aggregates, not least because two network cards in the same machine can be connected to different things and therefore be in different flavors13:17
johnthetubaguyijw: thats just a question of mapping to host aggregates correctly13:18
irenabijw: till we have neutron aware scheduler13:18
johnthetubaguyijw: a host can be in many aggregates13:18
ijwjohnthetubaguy: No, it's a question of being able to separate one card from another when they have identical devices and vendors, which is what the PCI flavor does13:18
johnthetubaguyijw: that was still possible in the host aggregate approach, using a host aggregate for each PCI flavor13:18
ijwEr, host aggregates presumably refer to hosts?13:19
ijwWhereas what we're talking about has nothing to do with hosts13:19
ijwI mean, I can create two flavors that don't make any attempt to distinguish the host that a card is in13:20
ijwAnd need additional information that isn't in host aggregates like device ID, vendor ID, connection, group...13:20
johnthetubaguyijw: PCI flavor described in a host aggregate metadata, the hosts you want to allow requests to, just get added into that aggregate13:20
irenabjohnthetubaguy: do you suggest to define host aggregates by physicla connectivity?13:20
johnthetubaguyiranab: nope, just that you persist the PCI flavor in host aggregate metadata13:21
ijwjohnthetubaguy: I'm confused.  The primary point of host aggregates is to define groups of hosts.  The primary point of PCI flavors is to define groups of PCI devices of which there are almost always many per host.  how would I put that into a host aggregate?13:21
ijweww13:21
johnthetubaguyit might not be quite right, but its what you are replacing, so needs some thought13:21
ijwIn what sense is it what we're replacing?  The flavor doesn't have a host in it at all13:22
heyongliwhat the property of pci device in  pci flavor should be kind of global, not bind to host, i think.13:23
johnthetubaguyijw: the question is more, should PCI flavor be an extra DB table or use existing data storage13:23
ijw(or, at least, I suppose you could filter by flavor, but in fact that's pretty much the one thing no-one has suggested because I think we all agree that filtering by location in cloud isn't a great administrative idea13:23
ijwjohnthetubaguy: understood - but I think you're saying 'use host aggregates to add an aggregate with additional information that you actually want to store, then use host aggregates where PCI flavors are'13:24
johnthetubaguyif there is a feature you want to restrict to a subset of hosts, we currently do that using host aggregates13:24
ijwOther than 'host aggregates have metadata' I really don't see the overlap13:24
ijwI could equally use glance images if that were the argument13:24
ijwThere isn't a feature you restrict to a subset of hosts13:25
johnthetubaguythere is, I just can't remember what it is now, its how pClouds got implemented13:25
ijwThere's a constraint that limits you, ultimately, to a subset of hosts based on resource availability, but only in the same way that CPU and memory do13:25
johnthetubaguyso availability zone, thats a grouping of hosts13:25
johnthetubaguyit is stored in host aggregates today13:25
ijwYes, I understand what you mean by host grouping, I'm missing how that's relevant to PCI13:25
*** woodster1 has joined #openstack-meeting-alt13:26
ijwOr, more accurately, I think I see where you're going with this and it's not really relevant to the use cases13:26
irenabI think the discussed issue is if PCI flavor is new stand alone resource or somehting that should be bound to exsisting constract?13:27
johnthetubaguyso PCI whitelist + PC flavor could = host aggregates grouping available PCI devices13:27
johnthetubaguythe question we ask when adding DB tables is, do we really need this extra concept13:27
johnthetubaguythe answer maybe yes, I just need to think though why it couldn't be host aggregates13:28
ijwSo, to be clear, PCI flavors aren't intended to restrict a feature to a subset of hosts.  They're intended to find a device matching criteria.  And the device criteria are specified on the compute node, largely because - like provider networks and quantity of RAM - they're very much a property of the individual compute node and not something that changes.13:28
ijwSo there's a logical reason why the information is divided between the compute config (which is, I think, really what you're arguing against) and the PCI flavor.  The config defines what hardware is in the cloud.  The flavor defines what the user can use.13:29
irenabijw: if we were doing plan B, I think it could be much easier to manage13:29
ijwIn much the same as Neutron config defines a provider network and Neutron API defines a network that lives on that provider network, for instance13:29
ijwirenab: I'm not sure it really helps - you could still quite easily end up scheduling to an aggregate that doesn't have the network you want13:30
*** nosnos has quit IRC13:30
johnthetubaguyijw: I am just worried about the extra DB tables, and wonder if we really need them13:30
irenabijw: thats why I think host aggregate is not a way here13:31
johnthetubaguyijw: staying with compute node config, just makes me worry about a global concept being cut and paste across every node in the cloud13:31
ijwjohnthetubaguy: well, I'm not sure if we need it or not, but I don't think host aggregate is the right substitute13:31
ijwWhy is it a crime to add a DB table?  I'm missing the concern here13:31
*** jdob has joined #openstack-meeting-alt13:31
*** nosnos has joined #openstack-meeting-alt13:31
johnthetubaguywell, don't want to re-invent an existing abstraction by accident, but just need to work out how different it is from what we already have13:32
ijwjohnthetubaguy: It's specific to a host and if you have multiple host types then actually your average admin will use a deployment system that determines that config.  From my perspective (and I've installed Openstack plenty of times using puppet) it's the right approach13:32
*** safchain has quit IRC13:32
ijwAnd you need the whitelist on the backend anyway, at least - otherwise using the API you can unplug hosts from their control interfaces by assigning them to passthrough - which even for an administrator is probably not what we're looking for13:33
johnthetubaguyin this case it might be the right approach, in which case, don't add extra DB stuff we will never use I guess13:33
*** sankarshan_away is now known as sankarshan13:33
baolijohn, with host aggregate with meta-data, does it maintain count per host aggregate?13:33
johnthetubaguyyeah, the count per host should be in the current host stats, using existing scheduler update paths, for my money13:34
johnthetubaguybut maybe I am missing something13:34
ijwjohnthetubaguy: maybe you could review the document to see what you think?  My take here is that PCI flavor is a publicly exposed object and having a table to back it is probably the right approach, and having been around and around I think the backend/frontend split we have here is the one we all like most, so the question is probably if another nova-exposed object suits the task13:34
ijwHost aggregate just seems such an odd choice, because we've almost religiously avoided categorising by host to date13:35
ijwNot explicitly, it's just not come up, and I think because it just doesn't fit the model13:35
johnthetubaguyright, and I think host aggregates + current scheduler host node stats, plus an extra filter, does what you need, I just need to know why that doesn't work13:36
ijwWell, we already have pci stats in any case13:36
ijwBut that aside I think I need to talk this over with you a bit more, I'm just not seeing it (but I certainly wouldn't claim to be an expert on host aggregates)13:37
johnthetubaguyyeah, there is a blueprint for making the current node stats extensible already, which should deal with the replacement for that13:37
johnthetubaguyanyways, it needs more though from me too13:37
baoliIn a case of host aggregate, a host join an aggregate by means of an API. In the case of flavor, a host joins by configuration, and stats is maintained per PCI flavor. However, host aggregate meta-data and the PCI flavor definition seems to be the same.13:37
*** nosnos has quit IRC13:38
ijwWhat I would say is that, again from experience, I absolutely wouldn't want to say 'a machine of type X has *these* PCI devices and these machines are of type X'.  Independently of that, it still doesn't actually get rid of the need for a flavor.13:38
johnthetubaguyhost aggregates is much simpler...13:39
johnthetubaguyyou define a new aggreage13:39
johnthetubaguyadd something that makes it a PCI flavor13:39
johnthetubaguysomething=metadata13:39
ijwBut (and I'll say it again) a PCI flavor doesn't apply to a host13:39
johnthetubaguyadd extra metadata to describe it13:39
ijwNo, I mean it's not a concept you apply to hosts13:39
johnthetubaguythen add the hosts that have the possibility of reporting a present PCI device13:40
ijwWhat if they have two?13:40
ijwOr (in the case of SRIOV) 64?13:40
johnthetubaguyOK, but you are applying it to hosts, its just you do that in the config file on the host, right?13:40
ijwNo, that's the PCI information, not the flavor13:40
ijwAnd it doesn't have a DB table13:40
johnthetubaguyhost aggregates says the have "N" devices, where N could be 013:40
baoliJohn, with a host aggregate, it just says a host POTENTIALLY has the resource, is that understanding correct?13:40
johnthetubaguyyeah, the scheduler needs to report the in-use devices, per flavor, and you can work out what happens later13:41
johnthetubaguyits just an approach13:41
ijwActually it's not reporting in use devices per flavor in case of overlaps, too, but that's a whole other can of worms...13:41
baoliif the host aggregate can take hosts that joins during boot up, and maintains counts per aggregate, and I see the pci flavor can definitely use it.13:42
johnthetubaguyoverlaps just mean more scheduler races, which we have semi-solutions for anyways13:42
*** ruhe is now known as _ruhe13:42
ijwThe thing I'm confused about here is that this doesn't actually make the PCI flavor go away13:42
johnthetubaguythe host aggregate would not store any counts13:43
baolithat's probably make the pci flavor necessary13:43
ijwIt could potentially be used to hold the PCI information and make that go away, but there are open questions as to whether that's a good idea independently13:43
ijwjohnthetubaguy: maybe you could explain what you think a PCI flavor is?13:44
johnthetubaguyI am guess its changed again, just trying to re-read the doc13:44
johnthetubaguyI assume PCI flavor is a description of a set of PCI devices the user is requesting13:44
johnthetubaguyif not, we shouldn't call it a flavor13:45
*** _ruhe is now known as ruhe13:45
ijwNo, it's a description of a type of device that the user is requesting13:45
johnthetubaguywell, thats what I was trying to day13:45
*** rakhmerov has joined #openstack-meeting-alt13:45
johnthetubaguyits the description of the device the user is requesting13:45
ijwMore accruately, it's a match expression for one of the types of device that a user is requesting for an instance13:46
johnthetubaguyhost aggregates also maps in a secondary whitelist, effectively, which is possibly annoying, possibly useful13:46
irenabijw: but type may have some labels, not physical properties13:46
*** dzyu has joined #openstack-meeting-alt13:47
*** safchain has joined #openstack-meeting-alt13:47
ijwyup, though that's because we specify them on the backend at the moment and the labels are a convenience for scheduling (though host aggregates doesn't really solve the Neutron information issue)13:47
*** safchain has quit IRC13:47
*** safchain has joined #openstack-meeting-alt13:48
johnthetubaguyeither way, I recon you need a way to say this group of devices are attached to this group of neutron networks13:48
johnthetubaguyI would add that to metadata in the host aggreate13:48
ijwjohnthetubaguy: we do and at the moment it's in the pci_information extra_info13:48
*** julim has joined #openstack-meeting-alt13:49
ijwWhich is just combining it with the whitelist on the compute node rather than bringing it to the DB (and again, this is intimately bound with the physical setup of your cloud so I think it *is* config, inasmuch as we've drawn a line between config and DB content)13:49
*** rakhmerov has quit IRC13:50
johnthetubaguyright, well I guess that would get joined at the scheduler if its not in the PCI flavor, which, sucks but still works I guess13:51
ijwSeems only logical to me - in much the same way that hosts report their CPU type, instances demand CPU type and the scheduler finds a host that meets demand13:51
*** doug_shelley66 has quit IRC13:51
ijwHere, hosts report PCI device summaries, instances demand a certain number and type of PCI devices and the scheduler attempts to meet demand13:52
johnthetubaguyAnyways, I am afraid I have spent too long reviewing this, its going to need a strong argument around this persistence story to get the blueprint approved, we can agree on that13:52
ijwI think I'd like to talk to you after the meeting about this - I don't think we're really seeing eye to eye on what PCI flavors are for.13:53
irenabijw: please share the summary on ml13:53
ijwirenab: will do13:53
johnthetubaguyYeah, I am being fast and loose with everything to make it fit what we have in nova13:53
heyongliijw,  johnthetubaguy, if you guy  talked, share that with us.13:53
sgordon_so what is the canonical location for the up to date design document?13:54
baoliThe sticking point is the count that host aggregate doesn't maintain, therefore it can only tell a host can potentailly meet the demand, but exact selection of a host based on exact resource demand cannot be done by host aggregate in its current state.13:54
ijwjohnthetubaguy: if host aggregates seemed like the right concept then I would be entirely with you, absolutely, but that doesn't seem to be what we're defining with a flavor and that's why I'd like to go over it a bit more13:54
*** jjmb has joined #openstack-meeting-alt13:54
johnthetubaguyafraid, will have to do something later in the week, I have to do some coding this afternoon, really need to get some code pushed up before a meeting at 15:00 UTC13:54
*** jjmb has quit IRC13:54
ijwbaoli: not really - the sticking point is more that host aggregates group hosts and nothing in the current design groups hosts at all13:55
*** vkmc has joined #openstack-meeting-alt13:55
johnthetubaguyI can't clearly see all the concepts described in this doc:13:55
johnthetubaguyhttps://wiki.openstack.org/wiki/PCI_passthrough_SRIOV_support#API_interface13:55
johnthetubaguythey are all there, just its a bit mixed in with other things13:55
baoliijw, you mean pci doesn't group hosts?13:55
ijwno13:55
ijwnot as it defines resources and not as it defines PCI flavors, no13:56
johnthetubaguydescribing the use cases, the user CLI calls, then defining all the concepts, and where they are persisted, then describe how the admin sets stuff up, would really help13:56
baolithat's interesting13:56
*** noslzzp has joined #openstack-meeting-alt13:56
ijwWe end up in the scheduler with a set of machines meeting the resources, but that's the only machine set involved and we didn't create that13:56
sgordon_johnthetubaguy, +113:57
johnthetubaguyfor me, PCI flavor is the user concept of what resources they can request13:57
johnthetubaguythe admin has to map that to reality, and the rest is implementation details13:57
irenabjohnthetubaguy: user tenant or user admin?13:57
ijwIt is, but they can request multiple PCI flavors per instance and multiple devices per flavor so it's not too close to anything else we're using13:57
ijwThough I do see how you might see that being an intersection of host aggregates13:58
johnthetubaguyits a user's concept of a PCI device they are requesting13:58
johnthetubaguyI see that as the key bit13:58
johnthetubaguyanyways, I think spliting that wiki into those sections I described should help13:58
ijwIndeed, and an administrator's offering13:58
johnthetubaguywhere admin is the guy defining flavors and setting up the hosts13:59
johnthetubaguyuser is the person who only calls nova boot13:59
ijwyup - though the events can be separated13:59
*** flwang has quit IRC13:59
*** dprince has joined #openstack-meeting-alt14:00
heyonglitime is up..14:00
*** dzyu has left #openstack-meeting-alt14:00
ijwYup14:00
ijw#action johnthetubaguy and ijw to discuss host aggregates, alternatives to a flavor table14:00
ijw#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
*** aveiga has joined #openstack-meeting-alt14:00
openstackMeeting ended Tue Jan 21 14:00:35 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-21-13.01.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-21-13.01.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-21-13.01.log.html14:00
*** lblanchard has joined #openstack-meeting-alt14:00
*** coolsvap has joined #openstack-meeting-alt14:00
*** heyongli has quit IRC14:02
*** aveiga has left #openstack-meeting-alt14:05
*** BrianB_ has quit IRC14:06
*** jdob_ has joined #openstack-meeting-alt14:08
*** eankutse has joined #openstack-meeting-alt14:12
*** eankutse has quit IRC14:13
*** reaperhulk has left #openstack-meeting-alt14:13
*** eankutse has joined #openstack-meeting-alt14:13
*** vkmc has quit IRC14:15
*** Barker has joined #openstack-meeting-alt14:20
*** baoli has quit IRC14:26
*** jjmb has joined #openstack-meeting-alt14:29
*** jpich has joined #openstack-meeting-alt14:29
*** doug_shelley66 has joined #openstack-meeting-alt14:31
*** banix has joined #openstack-meeting-alt14:32
*** woodster1 has quit IRC14:33
*** jdob_ has quit IRC14:34
*** balajiiyer has joined #openstack-meeting-alt14:35
*** irenab has quit IRC14:36
*** SergeyLukjanov is now known as SergeyLukjanov_a14:42
*** balajiiyer has quit IRC14:43
*** balajiiyer has joined #openstack-meeting-alt14:43
*** SergeyLukjanov_a is now known as SergeyLukjanov_14:43
*** coolsvap_away has joined #openstack-meeting-alt14:45
*** aignatov is now known as aignatov_14:45
*** rakhmerov has joined #openstack-meeting-alt14:46
*** gokrokve has joined #openstack-meeting-alt14:46
*** coolsvap has quit IRC14:47
*** coolsvap_away is now known as coolsvap14:48
*** kevinconway has joined #openstack-meeting-alt14:49
*** SergeyLukjanov_ is now known as SergeyLukjanov14:50
*** rakhmerov has quit IRC14:50
*** aignatov_ is now known as aignatov14:52
*** boris-42 has quit IRC14:54
*** amotoki has quit IRC14:55
*** IlyaE has joined #openstack-meeting-alt14:57
*** sadasu has quit IRC14:58
*** malini has joined #openstack-meeting-alt14:58
*** amitgandhi has joined #openstack-meeting-alt14:58
*** flwang has joined #openstack-meeting-alt15:01
flaper87flwang: amitgandhi malini around ?15:02
flaper87Kurt is not, nor Alej15:02
balajiiyerflaper87: Im here15:02
*** jcoufal has quit IRC15:02
*** jcoufal_ has joined #openstack-meeting-alt15:02
malinio/15:02
flaper87#startmeeting Marconi15:03
openstackMeeting started Tue Jan 21 15:03:06 2014 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.15:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:03
*** openstack changes topic to " (Meeting topic: Marconi)"15:03
openstackThe meeting name has been set to 'marconi'15:03
*** alcabrera has joined #openstack-meeting-alt15:03
flaper87alcabrera: yo15:03
flaper87good morning15:03
*** ametts has joined #openstack-meeting-alt15:03
alcabrerahey!15:03
flaper87'sup people?15:03
flwanghey15:03
flaper87how are your queues doing ?15:03
alcabreramy queues are tired... :P15:04
*** cpallares has joined #openstack-meeting-alt15:04
flaper87alcabrera: LOL15:04
flaper87:D15:04
flaper87so, first item15:04
flaper87actually15:04
amitgandhio/15:04
flaper87#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda15:04
flaper87that's today's agenda15:04
flaper87#topic I-2 Status15:04
*** openstack changes topic to "I-2 Status (Meeting topic: Marconi)"15:04
flaper87#link https://launchpad.net/marconi/+milestone/icehouse-215:04
flaper87#link https://blueprints.launchpad.net/marconi/+spec/pecan-framework15:05
*** chmouel has quit IRC15:05
alcabreraicehouse 2 - coming soon to an OS near you.15:05
flaper87balajiiyer: ^ ?15:05
*** chmouel_ has joined #openstack-meeting-alt15:05
flaper87I guess that should be moved to i-315:05
alcabrerayes, definitely.15:05
balajiiyerflaper87: yes, i315:05
flaper87awesome, the rest of the bps are implemented15:06
flaper87now, bugs15:06
alcabrera#link https://wiki.openstack.org/wiki/Icehouse_Release_Schedule15:06
*** chmouel_ is now known as chmouel15:06
flaper87:S :S :S :S15:06
flaper87#info i-2 bps implemented15:06
flaper87#link https://bugs.launchpad.net/marconi/+bug/125859115:07
flaper87alcabrera: ^15:07
flaper87any update?15:07
alcabrerathe update is - no progress. :/15:07
flaper87alcabrera: np, moving it to i-315:07
alcabrerakk15:07
flaper87#link https://bugs.launchpad.net/marconi/+bug/125861815:08
flaper87alcabrera: ^ ?15:08
*** vkmc has joined #openstack-meeting-alt15:08
*** vkmc has joined #openstack-meeting-alt15:08
flaper87alcabrera: Do you want me to un-assign you so that other folks interested can pick that bug up?15:09
flaper87alcabrera: still there?15:09
flaper87:D15:09
alcabrerayes15:09
alcabreraI was looking at sharding for a moment, heh15:09
alcabreranow lemme see...15:09
flaper87hehe, ok ok :D15:09
*** woodster1 has joined #openstack-meeting-alt15:09
*** dane_ has joined #openstack-meeting-alt15:10
alcabrerayeah, unassign that flaper87. I'd love to advise on the fix, but I can't do it at the moment.15:10
alcabrera:)15:10
flaper87ok, done15:10
alcabreracool15:10
*** kgriffs has joined #openstack-meeting-alt15:10
flaper87moved to i-3 as well15:10
*** woodster2 has joined #openstack-meeting-alt15:10
flaper87kgriffs: goood morning15:10
kgriffso/15:10
flaper87#link https://bugs.launchpad.net/marconi/+bug/124389915:10
kgriffssorry guys15:10
kgriffsbaby was sick last night15:10
flaper87flwang: updates?15:10
flaper87kgriffs: np, hope he/she is better now15:11
alcabrerakgriffs: dang. Hope the little one feels better soon.15:11
kgriffsthanks15:11
*** sebasmagri has joined #openstack-meeting-alt15:11
malinikgriffs: soory to hear that :(15:11
flaper87flwang: around?15:11
kgriffshe seems a little better this morning - stomach bug or something.15:11
kgriffsaaaanyway15:11
flwangflaper87: yep, I'd like to raise the discussion about the /health15:11
flaper87flwang: sure, lets talk about that later. Do you have updates about https://bugs.launchpad.net/marconi/+bug/124389915:11
flaper87#chair kgriffs15:12
openstackCurrent chairs: flaper87 kgriffs15:12
flwangflaper87: nope, I may have to fix it in i3 if it's ok for you guys15:12
flaper87kgriffs: we're going through the bug list: https://launchpad.net/marconi/+milestone/icehouse-215:12
kgriffskk15:12
flaper87#link https://bugs.launchpad.net/marconi/+bug/123983415:13
flwangflaper87: sorry about that15:13
flaper87kgriffs: want to take over?15:13
flaper87flwang: np15:13
kgriffssure15:13
flwangwas distracted by some other stuff15:13
kgriffslet's seee15:13
flaper87I think we should move that one15:13
flaper87I've no info about it15:13
flaper87the last comment is kgriffs'15:13
kgriffsok, we can move the attribute bug - I'll do that15:14
kgriffsnext: Health endpoint should be admin only15:14
*** woodster1 has quit IRC15:14
kgriffsso, that is going into v1.1 now, right?15:14
flaper87kgriffs: yeah + /ping15:14
flaper87flwang: did you want to say something about /healt ?15:15
chandankumar_kgriffs, donot take that bug, sorry i will do that https://bugs.launchpad.net/marconi/+bug/123983415:15
flwangflaper87:  after last meeting, we discussed that a little bit, I'd like to get more thoughts about what should we expose by the new api15:16
kgriffschandankumar_: oh, can you do it today?15:16
chandankumar_kgriffs, i will try my best15:16
kgriffswe only have until end of the day before the i-2 tag15:16
flaper87chandankumar_: the question was whether move it to -315:16
chandankumar_move it to -315:16
kgriffskk15:16
flaper87also, lets remember the gate is..... 'stressed'15:16
flaper87:D15:17
flwangflaper87: i'd like to know what's the 'health' metrics instead of 'performance' metrics15:17
flaper87so, I'm not sure many patches will make it15:17
flaper87flwang: health => I feel good, performance => Look how good i'm doing15:17
flaper87:D15:17
kgriffsflaper87: yeah, we will just have to see what we get over the next few hours.15:17
kgriffsflwang: wrt health15:18
kgriffsI would say that you can base health of of operational stats as well as "i am alive"15:18
kgriffsso, you could say that as long as I am responding to requests under X ms, I am healthy15:19
kgriffsbasically you want to expose key performance indicators (KPIs)15:19
kgriffsthen the operator can set up their monitoring/alerting system to trigger on those15:19
kgriffsso, to summarize15:20
kgriffs /ping says "I'm alive"15:20
kgriffsand /health says "here are my vital signs"15:20
kgriffsflwang: does that make sense?15:21
chandankumar_kgriffs, flaper87 thank you15:21
flwangkgriffs: thanks the suggestion. so basically, we'd like to provide some KPI with /health, right?15:21
kgriffsright15:21
kgriffslet's keep it is simple the first iteration15:21
kgriffsI'd say pick 3 KPIs15:22
flwanguptime?15:22
kgriffs(3-5)15:22
flwangresponse times and reqs/sec?15:22
*** cpallares has left #openstack-meeting-alt15:22
kgriffsflwang: let's break out that discussion in #openstack-meeting-alt15:22
kgriffs(and pull in some ops guys)15:22
kgriffsoops15:22
flwangok, sure15:22
*** cpallares has joined #openstack-meeting-alt15:22
kgriffsI meant, break out in #openstack-marconi15:22
*** mattgriffin has joined #openstack-meeting-alt15:23
flwangkgriffs: got it15:23
kgriffs#action flwang to get suggestions for KPIs for health from ops folks15:24
kgriffskk15:24
kgriffsnext15:24
flaper87flwang: thanks :)15:24
kgriffsflaper87: mind if I move the health endpoint bug to i-3, since v1.1 api is in i-3?15:24
flaper87kgriffs: np, lets move it15:24
kgriffsflwang: yes, thanks!15:24
* kgriffs does that15:25
kgriffsalcabrera: Cached shard state is not updated/deleted when shard is updated/deleted15:25
alcabreraI need to double check that, kgriffs.15:25
kgriffsalcabrera: will that get done in the next few hours?15:25
*** sfineberg has quit IRC15:25
alcabrerahmmmm15:26
kgriffs#link https://bugs.launchpad.net/marconi/+bug/125861815:26
alcabreraLet me get back to you on that.15:26
* alcabrera checks code15:26
kgriffsok15:26
kgriffsnext: Autoreconnect not handled in all cases15:27
kgriffsso, this one is waiting on the atomic batch insert patch15:27
alcabrerakgriffs: sure, I can fix that bug in the next hour (re: cached shard state)15:27
kgriffsmalini: any chance that patch will get benchmarked in the next few hours?15:27
kgriffsalcabrera: cool, thanks!15:27
malinikgriffs: I just ran it now & have the results15:27
maliniwas abt to update the patchset15:27
kgriffsah, cool15:27
kgriffsthanks!15:27
malinikgriffs: sorry..it took me long to get to it..Have lot of other stuff going on15:28
flaper87we'll need another patch besides the batch one15:28
flaper87right ?15:28
kgriffsso, the autoreconnect fix may slip into i-3, we'll see15:28
kgriffsflaper87: right15:28
kgriffsbut it will be fairly simple15:28
flaper87then yeah, i-315:28
kgriffsnext: hecking whether queue exists adds latency15:29
kgriffsso, i just noticed there were some gate errors on that patch15:29
kgriffsI need to look into that15:29
flaper87I just submitted a patch updating our cache code15:29
kgriffsflaper87: cool15:29
flaper87rm common/cache add openstack/common/cache15:29
kgriffsit would be good to get that in for i-215:30
*** amytron has joined #openstack-meeting-alt15:30
flaper87if jenkins is happy, we can merge it in15:30
kgriffsnext: [wsgi] Duplicate config options relating to max Content-Length15:30
kgriffsflaper87: sounds like a plan!15:30
kgriffsso, that config patch sort of morphed into a grab-bag of fixes15:30
flaper87but if we had to choose between this and other more important patch, I'd pick the more important (gate load wise)15:30
*** rnirmal has joined #openstack-meeting-alt15:30
kgriffsflaper87: kk15:30
kgriffstbh, I think that if all we got landed in time were the shard state and the atomic posts, I'd be OK with that.15:32
kgriffsmalini: did https://review.openstack.org/#/c/67320/ degrade performance significantly?15:32
kgriffs?15:32
malinikgriffs: yes15:32
malini& for some strange reason other API calls were also slowed down, not just post messages15:33
kgriffshmmm15:33
kgriffsok15:33
* kgriffs sad panda15:33
malini:(15:33
flaper87brb15:33
kgriffsok, well, I'll look into that15:33
kgriffsmalini: can you do another round of testing, just to be sure?15:34
malinikgriffs: sure15:34
kgriffsso... it looks like that may slip into i-3 if I can't find anything obvious to fix wrt performance15:34
kgriffsok, anything else anyone wants to discuss for i-2?15:34
kgriffs#topic Heat template status update15:35
*** openstack changes topic to "Heat template status update (Meeting topic: Marconi)"15:35
*** jecarey has joined #openstack-meeting-alt15:35
kgriffsI see this has a -1 on it: https://review.openstack.org/#/c/61036/15:36
kgriffsflwang: do you know the status of this? Is Liang in the channel?15:36
*** ashaikh has joined #openstack-meeting-alt15:36
*** jjmb has quit IRC15:36
flwangkgriffs: sorry, i don't sure, since now Liang is taking over it15:37
kgriffsflwang: what is his irc nick?15:37
*** tanisdl has joined #openstack-meeting-alt15:37
flwangkgriffs: liang15:37
kgriffsheh15:37
flwangiirc15:37
kgriffsok15:38
flwangI can catch him tomorrow15:39
kgriffsflwang: that would be cool15:39
kgriffsJust want to keep this patch moving forward15:39
flwangand have a sync with flaper8715:39
kgriffs#action flwang to follow up on heat patch with liang15:40
*** nati_uen_ has quit IRC15:40
kgriffs#topic SQLAlchemy status update15:40
*** openstack changes topic to "SQLAlchemy status update (Meeting topic: Marconi)"15:40
kgriffsso, I haven't seen much activity on that work lately15:40
kgriffsmakes me nervous. :p15:40
kgriffsflaper87: have you heard from Yeela lately (not sure if I spelled her name correctly)15:42
*** woodster2 has left #openstack-meeting-alt15:42
* kgriffs watches a tumbleweed roll by15:43
kgriffsflaper87: can you follow up with Yeela?15:43
kgriffsI would like to see this driver land in the next few weeks15:44
* alcabrera notices everyone is so busy lately15:44
kgriffsalcabrera: srsly.15:44
kgriffsalcabrera: let's leave this on the agenda for next time. we may need someone else to step up if Yeela doesn't have the bandwidth.15:45
*** rakhmerov has joined #openstack-meeting-alt15:46
kgriffs#topic SQLalchemy storage driver strategy15:46
*** openstack changes topic to "SQLalchemy storage driver strategy (Meeting topic: Marconi)"15:46
kgriffsalcabrera: what was this one about, do you recall?15:46
*** jecarey has quit IRC15:46
alcabreralet's see...15:46
alcabreraI vaguely remember this being about how we were going to break up the remaining work for the sqlalchemy driver15:47
alcabrerakgriffs: we may need to decide to move forward with it sooner, or to punt it for beyond icehouse.15:47
kgriffsoh, so between shard stuff and queue stuff, for example?15:47
alcabrerayes, things of that nature. :)15:47
kgriffsok15:48
kgriffshmmm15:48
kgriffsalcabrera: can you make a note to chase down yeela and get this sorted?15:48
kgriffsflaper87 should have some contact info15:48
*** lblanchard has quit IRC15:48
alcabrerakgriffs: sure thing15:48
kgriffsthanks!15:48
alcabreraflaper87: let's talk about this later15:49
* flaper87 just got back15:49
flaper87sorry guys15:49
flaper87erm15:49
alcabrerano worries15:49
kgriffs#action alcabrera to work with ykaplan and flaper87 to come up with a plan to reboot the SQL driver work15:49
flaper87alcabrera: sqla ? sure, lets talk about that right after the meeting15:49
*** sgordon_ has left #openstack-meeting-alt15:49
alcabreracool, thanks!15:49
kgriffs#topic tempest-integration15:50
*** openstack changes topic to "tempest-integration (Meeting topic: Marconi)"15:50
kgriffsmalini: status?15:50
maliniIt is stalled at this point :(15:50
maliniI am not getting any reviews15:50
kgriffsoh15:50
maliniI need a couple of devstack patches merged15:50
maliniI pinged in openstack-infra, no luck yet :(15:50
kgriffsmalini: ah, they are probably swamped with i-215:51
malinithe qa folks need those patches merged before they'll merge my tempest patch15:51
kgriffsoic15:51
*** lblanchard has joined #openstack-meeting-alt15:51
maliniI hope I can get some folks to review it after i-215:51
*** NikitaKonovalov is now known as NikitaKonovalov_15:51
kgriffsmalini: ok, try again friday/monday15:52
kgriffsping jaypipes15:52
maliniI will15:52
*** kraman has joined #openstack-meeting-alt15:52
malinijaypipes is qa, rt?15:52
maliniWe need some infra help, before tht15:52
*** markwash has joined #openstack-meeting-alt15:52
kgriffs#action malini to follow up with infra after i-2 lands15:52
kgriffsmalini: mmm, not sure15:52
kgriffsI thought he was infra, but I could be wrong15:53
kgriffsflaper87: do you know?15:53
*** tomblank has joined #openstack-meeting-alt15:53
maliniI'll check again & follow up15:53
flaper87kgriffs: infra15:53
kgriffskk15:53
malinicool!!15:53
kgriffs#topic pecan-framework15:53
*** openstack changes topic to "pecan-framework (Meeting topic: Marconi)"15:53
kgriffsbalajiiyer: status?15:54
balajiiyerkgriffs: going slow.15:54
balajiiyerupdated BP milestone to i315:54
kgriffsok15:55
kgriffsbalajiiyer: btw, have you done anything with Falcon in the past?15:55
balajiiyerkgriffs: small apps during hackathons, yes15:55
*** mspreitz has joined #openstack-meeting-alt15:55
kgriffsok15:55
kgriffsit would be great if you could take notes about your experience using Pecan15:56
kgriffshow easy it is to learn, how productive you feel using it, etc.15:56
balajiiyerkgriffs: Ok. can I also take notes about stevedore? ;)15:56
kgriffsyes15:56
kgriffsplease do15:56
kgriffs:)15:56
kgriffsso, obviously part of your learning curve is just the semantics of Marconi15:57
*** jcoufal_ has quit IRC15:57
*** SergeyLukjanov is now known as SergeyLukjanov_15:57
kgriffsbut, I'd like to get a view into the part that involves the framework and stuff15:57
kgriffsone last thing15:57
*** hockeynut has joined #openstack-meeting-alt15:58
*** kebray_ has joined #openstack-meeting-alt15:58
kgriffsyou may wish to also use WSME15:58
balajiiyerkgriffs: yes, I have a standalong pecan app running that delivers mock endpoints15:58
kgriffsthat is something that the oslo team is pushing pretty hard along with pecan15:58
* flaper87 has to notes to add15:58
flaper87to the meeting15:58
flaper87not the pecan discussion15:58
flaper87:D15:58
kgriffskk15:58
balajiiyerkgriffs: Im spending a lot of time trying to fit that into marconi framework15:58
kgriffsoic15:58
* flaper87 is sick of that discussion15:58
flaper87:D15:58
kgriffsfor sure!15:59
flaper87(just kidding and being pedantic)15:59
flaper87hahaha15:59
* kgriffs doesn't think it should even be an issue15:59
kgriffsok15:59
kgriffslast item15:59
kgriffs#topic docs15:59
*** openstack changes topic to "docs (Meeting topic: Marconi)"15:59
*** adrian_otto has joined #openstack-meeting-alt15:59
kgriffsso...15:59
*** paulmo has joined #openstack-meeting-alt15:59
flaper871 min left15:59
kgriffsturns out having user and operator docs is a req. for graduation now15:59
kgriffsjust FYI15:59
kgriffsso, i made a bp16:00
*** paulczar has joined #openstack-meeting-alt16:00
kgriffssee also:16:00
kgriffs#link http://git.openstack.org/cgit/openstack/governance/tree/reference/incubation-integration-requirements16:00
kgriffs#topic open discussion16:00
*** openstack changes topic to "open discussion (Meeting topic: Marconi)"16:00
kgriffs30 seconds. :p16:00
flaper87the -2 cut will be the first tarball creation for marconi, right?16:01
kgriffsflaper87: yep16:01
flaper87cool, so that everyone knows16:01
flaper87:D16:01
*** jmontemayor has joined #openstack-meeting-alt16:01
flaper87also, we may be interviewed in today's TC meeting16:01
kgriffsok, anything else?16:01
*** noorul has joined #openstack-meeting-alt16:01
*** Leonr has joined #openstack-meeting-alt16:01
flaper87not written on stone though16:01
flaper87that's it16:01
kgriffsflaper87: right, thanks for the reminder16:01
*** aratim has joined #openstack-meeting-alt16:01
*** jecarey has joined #openstack-meeting-alt16:01
*** colinmcnamara has joined #openstack-meeting-alt16:01
alcabrerathanks for the meeting, everyone.16:01
kgriffsthat is 3pm EST, btw16:02
*** DinaBelova is now known as DinaBelova_16:02
kgriffs(that meeting)16:02
alcabrera#info TC Meeting @ 3pm EST16:02
balajiiyerin this room?16:02
adrian_ottoplease #endmeeting16:02
*** boris-42 has joined #openstack-meeting-alt16:02
kgriffsbalajiiyer: in #openstack-meeting I believe16:02
kgriffsk guys, thanks!16:02
flaper87o/16:02
kgriffs#endmeeting16:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:02
openstackMeeting ended Tue Jan 21 16:02:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-21-15.03.html16:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-21-15.03.txt16:02
*** cpallares has left #openstack-meeting-alt16:03
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-21-15.03.log.html16:03
adrian_otto#startmeeting Solum Team Meeting16:03
openstackMeeting started Tue Jan 21 16:03:03 2014 UTC and is due to finish in 60 minutes.  The chair is adrian_otto. Information about MeetBot at http://wiki.debian.org/MeetBot.16:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:03
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:03
openstackThe meeting name has been set to 'solum_team_meeting'16:03
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum Our Agenda16:03
adrian_otto#topic Roll Call16:03
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:03
adrian_ottoAdrian Otto16:03
kramanKrishna Raman16:03
coolsvapSwapnil16:03
paulmoPaul Montgomery16:03
tomblankTom Blankenship16:03
nmarchenkoNikita Marchenko, Mirantis16:03
julienveyJulien Vey16:03
paulczarPaul Czarkowski16:03
*** stannie has joined #openstack-meeting-alt16:04
*** amitgandhi has left #openstack-meeting-alt16:04
stanniePierre Padrixe16:04
gokrokveGeorgy Okrokvertskhov16:04
noorulNoorul Islam16:05
aratimArati Mahimane16:05
adrian_ottook, welcome everyone!! Feel free to chime in as we proceed with Today's agenda. You can say anything in the channel during our meeting to record your attendance.16:05
adrian_otto#topic Announcements16:05
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:05
adrian_otto1) CLI Working Group cancelled.16:05
adrian_ottoit turns out that we did not need another meeting for that16:06
adrian_ottoI'm open to revisiting this if renewed interest builds around this topic16:06
adrian_otto2) New core reviewers will be nominated this week . I will do this with a message to the ML.16:06
adrian_ottowe will also have another round of additions and pruning in a couple of months.16:07
adrian_otto#topic Review Action Items16:07
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"16:07
adrian_otto1) COMPLETED: adrian_otto to update https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap with links to find milestone blueprints16:07
adrian_otto2) COMPLETED: adrian_otto to remove R2.2 from M1 in the roadmap wiki16:07
adrian_otto3) COMPLETED: adrian_otto to drop https://blueprints.launchpad.net/solum/+spec/user-authentication from the weekly agenda and mark the BP as finished16:08
*** nati_ueno has joined #openstack-meeting-alt16:08
adrian_otto4) COMPLETED: adrian_otto to add a note to the agenda to follow up about any Glance blueprints for https://blueprints.launchpad.net/solum/+spec/specify-lang-pack16:08
adrian_otto5) PENDING: adrian_otto to schedule a meeting about security context and logging features for M116:08
adrian_ottoStatus: We can discuss these items today. See agenda items below.16:08
adrian_ottoso in a few minutes, this will also be completed16:08
adrian_ottopaulmo16:08
paulmoYes16:08
adrian_ottoI will need input from you on the next two16:08
adrian_ottoand probably also noorul16:09
adrian_otto#topic Security Context feature for M1 (paulmo)16:09
*** openstack changes topic to "Security Context feature for M1 (paulmo) (Meeting topic: Solum Team Meeting)"16:09
adrian_ottoand also gokrokve16:09
*** SushilKM has joined #openstack-meeting-alt16:09
adrian_ottoWhat should the scope and expectations be for M1?16:09
*** balajiiyer has left #openstack-meeting-alt16:09
paulmoWell, we just need some place to put session data for use around the solum project.  Right now we have 2 options available that need discussion.16:09
*** xuhanp has quit IRC16:10
paulmoThere are pull requests up for both.16:10
adrian_ottoare we happy with what has already posted in reviews?16:10
*** alcabrera has left #openstack-meeting-alt16:10
adrian_ottoor are we contemplating additional scope beyond that?16:10
*** chandankumar_ has quit IRC16:10
paulmoWe have some divergent reviews right now (for and against each option)… probably needs more discussion to reach consensus.16:10
paulmoOh, no, I'm not looking to extend scope right now so much as consolidate on a single approach.16:10
adrian_ottodo we need additional preparation to have that discussion, or can we hammer that out in this meeting?16:11
*** luqas has joined #openstack-meeting-alt16:11
paulmoIs Angus here?  I think he had a vested interest in this topic.16:11
adrian_ottono, it's really early AM his time16:11
paulmoWe could talk now but without him, I'm not sure we'll have all key folks together.16:11
paulmoPerhaps this afternoon we could schedule a meeting?16:12
adrian_ottook, in that case I can revisit the #5 action item again, and do this a bit later in the day16:12
paulmoThanks :)16:12
adrian_ottopaulmo are you open to leading the meeting and scheduling it?16:12
adrian_ottoI will be on flights later today16:12
paulmoSure, no problem!16:12
paulmoOh apologies, just looked at my calendar, I have no time this afternoon unfortunately… would tomorrow work instead?16:13
adrian_otto#action paulmo to schedule follow up IRC chat about Security Context16:13
adrian_ottosure16:13
paulmoCool; apologies16:13
adrian_ottoI just want to be sure we don't lose track of the item16:13
paulmoAgreed16:13
adrian_ottosame for Logging Features16:13
*** SushilKM has quit IRC16:13
adrian_ottoor do we have everyone present needed for that?16:13
adrian_otto#topic Logging Features for M1 (paulmo)16:14
*** openstack changes topic to "Logging Features for M1 (paulmo) (Meeting topic: Solum Team Meeting)"16:14
adrian_ottoWhat should the scope and expectations be for M1?16:14
paulmorussellb angus here?  I think they had interest in this topic.16:14
*** sebasmagri has left #openstack-meeting-alt16:14
paulmoangus isn't obviously :)16:14
russellbhi, fighting gate fires, but around kinda16:14
adrian_ottook, seems that we could bundle these two topics inthe same follow-up16:14
adrian_ottoit's probably best not to force a decision16:15
paulmoProbably a good idea, I think they are related and getting the context set will also give a better idea for the logging path.16:15
adrian_otto#action paulmo to add Logging Features to the Security Context followup meeting agenda16:15
adrian_ottothat fair?16:15
paulmoYep!16:15
*** markwash has quit IRC16:15
adrian_ottook, thanks!16:15
adrian_otto#topic Review Blueprints: https://launchpad.net/solum/+milestone/milestone-116:16
*** openstack changes topic to "Review Blueprints: https://launchpad.net/solum/+milestone/milestone-1 (Meeting topic: Solum Team Meeting)"16:16
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-minimal-cli Command Line Interface for Solum (devdatta-kulkarni)16:16
adrian_otto#link https://review.openstack.org/66617 (WIP)16:16
adrian_otto#link https://review.openstack.org/58067 (Pending Review)16:16
adrian_ottoDevdatta is not attending today, right?16:17
paulmoSo I have a pull request outstanding on that and there is discussion ongoing.  Hopefully we can reach a consensus in the next day or two. :)16:17
paulmoRight, he is flying now.16:17
adrian_ottook16:17
noorulThe client is ready fore review16:17
paulmoIf you have time after noorul, can we work through some review topics?16:18
*** dane_ has quit IRC16:18
adrian_ottoSHould we toggle off the WIP designation on 66617 if it is now a merge candidate?16:18
noorulAnd couple more resources are added here https://review.openstack.org/#/c/66184/16:18
noorulpaulmo: sure16:18
adrian_otto#link https://review.openstack.org/66184 CLI resource managers16:18
paulmoGood, I think working through just a few review topics will get our code to the point of merging very soon16:18
adrian_ottook, that's great news16:19
adrian_ottoanything more on this topic?16:19
paulmoNot from me16:19
noorulpaulmo: Why are we adding commands that are not yet implemented in solum16:19
noorulI mean commands for API that is not yet in solum repo16:19
paulmoI can remove them… just seemed weird to not have a list command to see if things are working.16:19
adrian_ottoI asked for that16:20
adrian_ottobecause M1 will need to demo nicely16:20
adrian_ottoand without a list function it will be really awkward to demo16:20
noorulRight now there is only one API implemented in solum and that is listing16:21
adrian_ottonoorul: do you want additional assistance with fleshing out the API?16:21
paulmoIf it is an extra unplanned burden noorul, perhaps I could offer my help?16:21
adrian_ottoas it pertains to enabling the CLI16:21
noorulThere are no API to consume for create, delete, etc16:22
noorulI think that should be implemented first, right?16:22
adrian_ottoyes, we need those16:23
paulmoUnfortunately, muralia isn't here today but I think he is working on expanding the API.16:23
aratimshs16:23
adrian_ottoI can make sure that we have enough Stackers working on the enablement of the CLI16:23
paulmoIf there is something you need sooner, perhaps we can chat with him to prioritize16:23
aratimsorry  - pls ignore16:23
noorulok16:24
tomblankyes, we can prioritize this work (CLI) if needed16:24
*** Leonr has quit IRC16:24
adrian_ottook, any more thoughts on this subject?16:25
*** Leonr has joined #openstack-meeting-alt16:25
*** SushilKM has joined #openstack-meeting-alt16:25
paulmoSo it sounds like create and delete app and assembly would be first APIs you'd want if I take a guess right?16:25
*** SushilKM has left #openstack-meeting-alt16:25
paulmo(sorry, didn't mean to rathole there, we can move on) :)16:25
adrian_ottoNest is...16:25
adrian_ottonext is...16:25
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo)16:25
adrian_ottoI think we can skip it16:25
noorulpaulmo: Yes16:26
adrian_ottopursuant to other comments earlier, correct16:26
paulmoYes, agreed16:26
adrian_ottonext16:26
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni)16:26
adrian_ottoWe got an exciting update on this last week:16:26
adrian_otto#link https://github.com/kraman/zuul/compare/solum_hacks POC presented last week16:26
adrian_ottokraman: can you update us?16:26
kramansure16:27
kramanthe solum_hacks branch accepts a message via queue and triggers the build of lang pack16:27
kramani didnt make as much preogress last week but am trying to cleanup the branch and send patches upstream to zuul16:28
kramanthis should allow us to complete the git-pull BP16:28
adrian_ottoFor anyone who missed last week, we are working on a POC to demonstrate that we can use Zuul as the basis for a build service for Git integration16:28
adrian_ottokraman: good, do you need any help, or are you all set?16:29
kramanWe also decided last week that git-push workflow should be done after m116:29
kramanthe workgroup on git is already helping16:29
*** Leonr has quit IRC16:29
kramanI should be fine with their help16:29
kramanso all set16:29
adrian_ottook, awesome16:29
kramanthats it from my end16:29
adrian_otto#topic Open Discussion16:30
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:30
adrian_ottoI do have one item for this16:30
adrian_ottoI'd like to ask us to consider moving this meeting to later in the day16:30
aratimadrian_otto: I think we missed review for BP https://blueprints.launchpad.net/solum/+spec/specify-lang-pack16:30
*** aignatov is now known as aignatov_16:30
adrian_ottoaratim:16:31
adrian_ottook, do you have an update for us? We can do that now.16:31
*** Leonr has joined #openstack-meeting-alt16:31
aratimsure16:31
aratimDetails about language pack attributes: https://etherpad.openstack.org/p/Solum-Language-pack-json-format16:31
aratimPull request: https://review.openstack.org/#/c/67292/  (Created a language pack resource and implemented GET request. This code is based on the new API worker architecture)16:31
aratimadrian_otto: each language pack will also be listed as a service and I will be working on it.16:31
adrian_ottoAre there any glance blueprints to discuss?16:32
adrian_ottofor the lang pack?16:32
aratimi dont think so16:32
adrian_ottook, thanks16:33
aratimI will need to ask devdatta once he is back16:33
adrian_ottoany more on this topic for this week?16:33
aratimthanks16:33
adrian_ottook, so let's continue Open Discussion16:33
*** DinaBelova_ is now known as DinaBelova16:33
adrian_ottoif we attempt to move the meeting to later in the day, how would that impact our attendees?16:34
adrian_ottomeeting = Solum Team Meeting (weekly)16:34
coolsvapadrian_otto: later by how much time?16:34
noorulwill be an issue for IST people I believe16:34
adrian_ottomaybe UTC 2100 instead?16:34
kramanadrian_otto: doodle poll to find a good time for everyone?16:35
adrian_ottokraman: good suggestion16:35
paulmoThat is a fine time for me.16:35
*** claytonc has joined #openstack-meeting-alt16:35
adrian_ottoI think that would work for any US attendees16:35
adrian_ottothe only time I might expect India and Australia, and the US to be awake at the same time is in the evening for the US16:36
*** sbalukoff has joined #openstack-meeting-alt16:36
adrian_ottoin the 7PM US/Pacific timeframe16:36
coolsvapI think it would be around 0230 here16:36
adrian_ottoanother possibility might be alternating the meeting time16:37
adrian_ottoon alternate weeks16:37
paulczar+1 for alternating16:37
adrian_ottoso those who are inconvenienced by one of the meeting times could at least attend every other week16:37
coolsvapI think 7PM PST can work16:37
adrian_ottook, so maybe thing a bit on that one, and let's see if we can do better to include more of our contributors. I know it's hard working with so many different timezones.16:38
adrian_ottos/thing/think/16:39
paulczar7pm is 9pm for CST16:39
*** mspreitz has left #openstack-meeting-alt16:39
adrian_ottoyep.16:39
coolsvap:)16:39
adrian_ottoit's outside business hours for the majority of us16:39
*** SushilKM has joined #openstack-meeting-alt16:40
adrian_ottoat any rate, I'm open to more suggestions if there are other ideas16:40
*** SushilKM has left #openstack-meeting-alt16:40
kramanadrian_otto: can we change the day? or do you want to keep it tuesday?16:40
kramanT/Th 7pm would not work for me16:41
adrian_ottosure, we could do any day besides Fri-Sun16:41
*** markwash has joined #openstack-meeting-alt16:41
adrian_ottoMonday can also be tricky, as we would frequently contend with holiday schedules16:42
adrian_ottoso I'll put up a doodle poll16:42
*** sankarshan is now known as sankarshan_away16:42
adrian_ottowhen you look at the doodle poll, remember that you can make comments on it16:42
paulmoYeah, this may be the hardest problem in the project. :)16:42
adrian_ottoand make suggestions for additional times16:42
adrian_ottoworking groups help to mitigate this to some extent16:43
adrian_ottoany other discussion topics?16:44
*** vkmc has quit IRC16:44
adrian_ottook, looks like we might wrap up a bit early today16:44
adrian_ottoThanks everyone for attending. We'll meet again next week!16:45
adrian_otto#endmeeting16:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:45
openstackMeeting ended Tue Jan 21 16:45:48 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-21-16.03.html16:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-21-16.03.txt16:45
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-21-16.03.log.html16:45
*** paulmo has left #openstack-meeting-alt16:45
*** paulczar has left #openstack-meeting-alt16:46
*** kraman has left #openstack-meeting-alt16:47
*** gokrokve has quit IRC16:49
*** gokrokve has joined #openstack-meeting-alt16:49
*** gokrokve_ has joined #openstack-meeting-alt16:51
*** FallenPegasus has joined #openstack-meeting-alt16:51
*** claytonc has left #openstack-meeting-alt16:52
*** ativelkov has joined #openstack-meeting-alt16:52
*** Duane_ has joined #openstack-meeting-alt16:53
*** katyafervent2 has joined #openstack-meeting-alt16:54
*** gokrokve has quit IRC16:54
*** wendar has joined #openstack-meeting-alt16:56
*** doug_shelley66 has quit IRC16:57
*** DinaBelova is now known as DinaBelova_16:58
*** doug_shelley66 has joined #openstack-meeting-alt16:58
*** bdpayne has joined #openstack-meeting-alt16:58
*** SushilKM has joined #openstack-meeting-alt16:59
*** SushilKM has left #openstack-meeting-alt16:59
*** stanlagun has joined #openstack-meeting-alt16:59
ativelkov#startmeeting Murano Community Meeting17:00
openstackMeeting started Tue Jan 21 17:00:26 2014 UTC and is due to finish in 60 minutes.  The chair is ativelkov. 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: Murano Community Meeting)"17:00
openstackThe meeting name has been set to 'murano_community_meeting'17:00
ativelkovHi folks17:00
ativelkovIt's time for Murano meeting, isn't it?17:01
katyafervent2Hi17:01
ativelkovLet's start then17:02
stanlagunhi17:02
ativelkov#topic AI review17:02
*** openstack changes topic to "AI review (Meeting topic: Murano Community Meeting)"17:02
*** nati_uen_ has joined #openstack-meeting-alt17:02
*** tnurlygayanov_ has joined #openstack-meeting-alt17:02
*** nati_uen_ has quit IRC17:02
ativelkovWe had lot's of actions related to the new DSL17:02
*** joel_c has joined #openstack-meeting-alt17:02
ativelkovstanlagun to submit the sources to a custom repo17:02
*** nati_uen_ has joined #openstack-meeting-alt17:03
ativelkovStan, as far as I remember you've done that17:03
ativelkovCould you please remind us the url to this repo?17:03
*** noorul has left #openstack-meeting-alt17:03
*** nati_ueno has quit IRC17:03
stanlagunhttps://github.com/istalker2/MuranoDsl17:03
*** markwash has quit IRC17:03
ativelkov#info new DSL is temporary availalble at custom repo at https://github.com/istalker2/MuranoDsl17:04
ativelkovWe'll need to decide where to put it when it is ready for integration into 0.517:04
katyafervent2Right now?)17:05
ativelkovWe'll, there is no rush, but we need to start working on the actual 0.5 soon17:06
*** johnthetubaguy1 has joined #openstack-meeting-alt17:06
katyafervent2I suggest murano-common or repository17:06
*** aratim has left #openstack-meeting-alt17:06
ativelkov+1 for murano-common for DSL17:06
ativelkovDSL engine is reusable, so common is a good placce for it17:07
stanlagunmurano-shared17:07
*** yjiang5_1 has joined #openstack-meeting-alt17:07
ativelkovstanlagun: is it going to be a new repo?17:07
tnurlygayanov_ok, let's move it to murano-common. One more repository& )17:07
*** gokrokve_ has quit IRC17:08
*** FallenPegasus has quit IRC17:08
katyafervent2We do have murano common and shared has the same meaning though17:08
*** julim has quit IRC17:09
*** kgriffs has quit IRC17:09
*** johnthetubaguy has quit IRC17:09
*** shadower has quit IRC17:09
*** lifeless has quit IRC17:09
*** csaba|afk has quit IRC17:09
*** csaba|afk has joined #openstack-meeting-alt17:09
*** shadower_ has joined #openstack-meeting-alt17:09
*** csaba|afk has quit IRC17:09
*** csaba|afk has joined #openstack-meeting-alt17:09
ativelkovWe will need to reorganize our repos. But this requires a discussion - let's first cover all the open AIs first17:09
*** lifeless1 has joined #openstack-meeting-alt17:09
*** yjiang5 has quit IRC17:09
*** jeblair has quit IRC17:09
*** isviridov has quit IRC17:09
stanlagunI would suggest having "murano" for reusable parts and "murano-services" for services17:09
*** isviridov has joined #openstack-meeting-alt17:09
*** kgriffs has joined #openstack-meeting-alt17:10
ativelkovSecond AI is "stanlagun to update the DSL description according to the implemented PoC"17:10
*** julim has joined #openstack-meeting-alt17:10
*** jeblair has joined #openstack-meeting-alt17:10
ativelkovPoC is still in its final implementation steps, right?17:10
stanlagunnot yet done as PoC is not fully implemented and still there are several problems left. But it is close to final steps as today I've done ~70% of remaining changes in DSL17:11
ativelkovGood.17:12
ativelkovSo, the last AI is not applicable as weel. It was on me, and I was supposed to organize a call with Dmitry to demonstrate the PoC17:12
ativelkovSo, we expect this to happen during this week17:12
ativelkovright?17:13
stanlagunnot sure on documentation, but as for PoC - yes17:14
ativelkov#info DSL PoC to be completed this week. Documentation could be delayed17:14
ativelkovSo, the AIs remain the same17:14
ativelkov#action stanlagun to update the DSL description according to the implemented PoC17:14
ativelkov#action ativelkov to schedule a meeting with Dmitry17:14
ativelkovOK, we are done with the AIs17:15
ativelkov#topic New DSL17:15
*** openstack changes topic to "New DSL (Meeting topic: Murano Community Meeting)"17:15
ativelkovSo, speaking about the new DSL: what remain to be done in terms of implementation?17:15
*** bdpayne has quit IRC17:15
stanlagunSeveral APIs to talk to Heat and Agents, several YAQL functions/macro  and most difficult - memoization of some DSL methods17:17
ativelkovwhat do you mean by memoization?17:17
stanlagunThat is make Deploy be callable many times without side effects17:17
stanlagunAnd syncronization between several parallel callers17:18
*** MarkAtwood has joined #openstack-meeting-alt17:18
ativelkovAh, you mean the logic when a method can be caused only once with the given set of parameters, and the result is kept in memory, so subsequent calls return the same without actual computations?17:19
ativelkovcan be alled*17:19
ativelkovcalled**, sorry )17:19
stanlagunyes, more or less17:20
*** Duane_ has quit IRC17:21
ativelkovOk. Any estimates on this?17:21
*** Duane_ has joined #openstack-meeting-alt17:21
stanlagunthis is all parts of PoC17:22
stanlagunso this week, as i said17:22
*** SergeyLukjanov_ is now known as SergeyLukjanov17:22
ativelkovAh, good17:23
ativelkovAnything else to discuss about the New DSL?17:24
stanlagunlets continue on next CM17:24
ativelkovOk17:25
*** ametts has left #openstack-meeting-alt17:25
ativelkov#topic Release 0.4.1 status17:25
*** openstack changes topic to "Release 0.4.1 status (Meeting topic: Murano Community Meeting)"17:25
ativelkovkatyafervent2, can you give an update on the ststaus of the release?17:25
*** Duane_ has quit IRC17:26
katyafervent2Heap, everything is on track17:26
*** dteselkin has joined #openstack-meeting-alt17:26
*** jjmb has joined #openstack-meeting-alt17:26
ativelkovOn the last meeting we agreed to add support for Neutron LB in this delivery. Any progress on this?17:27
katyafervent2Work for all items that we were added to our deliverables are in progress17:27
tnurlygayanov_ativelkov, yes17:27
katyafervent2First part of  blueprint was implemented by Serg17:27
tnurlygayanov_neutron support was reviewed and added two new blueprints17:28
tnurlygayanov_for 0.4.117:28
ativelkovtnurlygayanov_: have we deployed the LB to some of our labs?17:28
tnurlygayanov_https://blueprints.launchpad.net/murano/+spec/auto-assign-floating-ip17:28
katyafervent2And just small piece left17:28
tnurlygayanov_and https://blueprints.launchpad.net/murano/+spec/auto-assign-virtual-ip17:28
*** rakhmerov has quit IRC17:28
katyafervent2Also we do have several medium bugs left17:28
tnurlygayanov_yes, I deployed it on my QA environment with devstack17:28
*** vkmc has joined #openstack-meeting-alt17:29
*** vkmc has joined #openstack-meeting-alt17:29
ativelkov#info Neutron LB support implementation in progress17:29
ativelkov#info release 0.4.1 on track17:29
katyafervent2And from now we do need to concentrate more on testing17:30
ativelkovPlease note that 0.4.1 should not have any strict dependencies on IceHouse artifacts or trunk17:30
katyafervent2Also Dmitry is done with devstack integration17:30
*** redrobot has left #openstack-meeting-alt17:30
tnurlygayanov_yes, we will test it with devstack from trank17:31
ativelkovtnurlygayanov_: please test in on latest Havana17:31
katyafervent2Let's move on17:31
tnurlygayanov_ativelkov, it it already done.17:32
ativelkovgood.17:32
ativelkovThe reason I am asking is that it is likely that 0.4.1 may be included in MOS 4.1, which will be Havana-based17:32
ativelkovSo, the next item in our agenda17:33
ativelkov#topic Repository reorganization17:33
*** openstack changes topic to "Repository reorganization (Meeting topic: Murano Community Meeting)"17:33
*** Leonr has quit IRC17:33
ativelkovThat's a long topic and probably will require more meetings17:33
ativelkovBut in general I see a problem with our infrastructure17:34
ativelkovwe have 11 (eleven) repositories17:34
ativelkovthat is about 5 times more then optimal :)17:34
ativelkovWe need to reorganize them17:35
ativelkovAt the same time, we need to preserve testability17:35
*** hockeynut has quit IRC17:36
*** Duane_ has joined #openstack-meeting-alt17:36
ativelkovAlso, it is ok to have a separate repos for python bindings (python-muranoclient or whatever it is called) and OpenStack Dashboard plugin17:36
ativelkovI would suggest to have a signle repository for the main components of Murano (we will need to merge murano-api, murano-conductor and murano-repository), a single repo for python bindings (need to merge python-muranoclient and murano-metadataclient)17:39
stanlagunservices + python-client + UI + app catalog services metadata + (maybe) shared code + docs = 5-6 at minimum. How do you make less?17:39
dteselkinwhat about murano-deployment ?17:39
stanlagun+117:39
ativelkovwhat is the diff between "service" and "app catalog services metadata"?17:40
stanlagunservices = api/conductor etc.17:40
ativelkovmetadata should be there as well17:40
ativelkovit is a core component for us17:40
stanlagunmetadata = app templates, sample services. Those are pure YAML/templates etc17:40
ativelkovAh, the examples17:41
ativelkovThey should go to extra17:41
*** kgriffs has left #openstack-meeting-alt17:41
ativelkovas well as deployment scripts, buildable docs etc17:41
*** esker has joined #openstack-meeting-alt17:41
stanlagunDon't think that metadata for core classes like Object can be considered as extra17:41
ativelkovI don't speak about core classes17:42
ativelkovcore shoould be stored in the main repo, altogether with the engine itself17:42
*** gokrokve has joined #openstack-meeting-alt17:43
ativelkovI don't see the reason for such granularity17:43
*** gokrokve has quit IRC17:43
*** gokrokve has joined #openstack-meeting-alt17:43
stanlagunCore classes are part of initial AppCatalog content and should be also installed to glance17:43
ativelkovAnd what is the problem with that if they reside in the primary repo?17:44
stanlagunAlongside with common base class library17:44
*** DinaBelova_ is now known as DinaBelova17:45
stanlagunIf they would be in a separate repository companies could make forks with custom basic workflows adopted for concrete IT17:45
ativelkovWe don't want any forks of our base library!17:46
stanlagunWhy?17:46
ativelkovWe have inheritence for that17:46
ativelkovForking is not an openstack way of doing this17:46
ativelkovBase library should remain base :)17:46
ativelkovAnd anyway, if somebody wants to fork, they can fork the whole repo17:47
*** sarob has joined #openstack-meeting-alt17:48
ativelkovThe packaging and glance-publsihing should be done by deploymnet scripts17:48
stanlagunI don't speak about inheritance. I talk about uses cases like "all Vms in our cloud must be booted from volume" or have additional security constraints or additional workflow steps. If you use inheritance for this you would have to create a custom version of every possible service in catalog instead of modifying one class "Instance"17:48
ativelkovAnd the location of the sources for these packages is irrelevant17:48
*** Leonr has joined #openstack-meeting-alt17:50
ativelkovin this case yes, the custom fork of the library is possible, but I don't see reasons to have different repo for that17:50
*** nati_ueno has joined #openstack-meeting-alt17:51
ativelkovThere may be need to modify the engine as well - with approximately the same probability of this need17:51
*** nati_ueno has quit IRC17:51
ativelkovSo, they can fork the whole repo17:51
*** harlowja_away is now known as harlowja17:51
*** nati_ueno has joined #openstack-meeting-alt17:51
ativelkovAnyway, I would suggest to initiate a discussion17:52
ativelkovProbably there is more then one way of doing this17:52
ativelkovI suggest to write to infra ML and ask for better practises and some advices from openstack folks17:52
stanlagunWell not with same probability. Metadata is designed to be modified by cloud-ops while code is not. But this not neccessary mean you're wrong :)17:53
*** rakhmerov has joined #openstack-meeting-alt17:53
stanlagunFo me metadata is an advanced version of config files17:54
ativelkovCool. Do you suggest to have a separate repo for all the config files? ;)17:54
*** coolsvap is now known as coolsvap_away17:54
*** amcrn has joined #openstack-meeting-alt17:54
*** mestery has quit IRC17:55
ativelkov#action ativelkov to write to ML about repository re-organization17:55
*** nati_uen_ has quit IRC17:55
ativelkovGuys, we have 5 minutes left. It seems like we have to continue the repo discussion later17:55
*** vkmc has quit IRC17:55
ativelkovOne more note: next week gokrokve and me will be at Glance mini-summit in Washington DC17:55
*** sarob_ has joined #openstack-meeting-alt17:56
ativelkovCould someone else lead a community meeting on the next week?17:56
*** ashaikh has quit IRC17:57
*** sarob__ has joined #openstack-meeting-alt17:57
*** ruhe is now known as _ruhe17:57
*** sarob has quit IRC17:58
*** sarob___ has joined #openstack-meeting-alt17:58
*** derekh has quit IRC17:58
ativelkovAny volunteers? ;)17:58
gokrokveVolunteers will be assigned :-)17:59
ativelkovNice idea )17:59
ativelkovI likee this way of volunteering! )17:59
ativelkovOk, thank's all for joining17:59
ativelkov#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:59
openstackMeeting ended Tue Jan 21 17:59:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano_community_meeting/2014/murano_community_meeting.2014-01-21-17.00.html17:59
*** sarob has joined #openstack-meeting-alt17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano_community_meeting/2014/murano_community_meeting.2014-01-21-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/murano_community_meeting/2014/murano_community_meeting.2014-01-21-17.00.log.html17:59
*** stanlagun has left #openstack-meeting-alt18:00
*** sarob has quit IRC18:00
*** sarob_ has quit IRC18:00
*** sarob__ has quit IRC18:02
*** sarob___ has quit IRC18:03
*** bdpayne has joined #openstack-meeting-alt18:04
*** arnaud has joined #openstack-meeting-alt18:05
*** arnaud__ has joined #openstack-meeting-alt18:05
*** adrian_otto has quit IRC18:07
*** eankutse has quit IRC18:07
*** hockeynut has joined #openstack-meeting-alt18:09
*** nadya__ has joined #openstack-meeting-alt18:09
*** pcarver_ has joined #openstack-meeting-alt18:09
*** tnurlygayanov_ has quit IRC18:10
*** safchain has quit IRC18:12
*** yamahata has joined #openstack-meeting-alt18:13
*** sarob has joined #openstack-meeting-alt18:13
*** markwash has joined #openstack-meeting-alt18:15
*** Duane_ has quit IRC18:15
*** nadya__ has quit IRC18:18
*** aignatov_ is now known as aignatov18:19
*** morazi has joined #openstack-meeting-alt18:22
*** aignatov is now known as aignatov_18:23
*** wendar has quit IRC18:28
*** wendar has joined #openstack-meeting-alt18:28
*** eankutse has joined #openstack-meeting-alt18:29
*** dripton is now known as dripton_shovelin18:30
*** Duane_ has joined #openstack-meeting-alt18:37
*** markwash has quit IRC18:38
*** nati_uen_ has joined #openstack-meeting-alt18:40
*** IlyaE has quit IRC18:40
*** markwash has joined #openstack-meeting-alt18:41
*** ccrouch has joined #openstack-meeting-alt18:42
*** Duane_ has quit IRC18:42
*** ccrouch has quit IRC18:43
*** nati_ueno has quit IRC18:43
*** yogesh has joined #openstack-meeting-alt18:43
*** jprovazn has joined #openstack-meeting-alt18:47
*** obondarev_ has joined #openstack-meeting-alt18:47
*** jistr has joined #openstack-meeting-alt18:47
*** lsmola has joined #openstack-meeting-alt18:48
*** luqas has quit IRC18:48
*** ashaikh has joined #openstack-meeting-alt18:48
*** matty_dubs has joined #openstack-meeting-alt18:52
*** ashaikh has quit IRC18:53
*** katyafervent2 has quit IRC18:53
*** dripton_shovelin is now known as dripton18:54
*** rpodolyaka1 has joined #openstack-meeting-alt18:55
*** tzumainn has joined #openstack-meeting-alt18:55
*** pcarver_ has quit IRC18:57
*** jcoufal-mobile has joined #openstack-meeting-alt18:57
*** rlandy|bbl has joined #openstack-meeting-alt18:57
*** akuznets_ has quit IRC18:59
*** lifeless1 is now known as lifeless18:59
*** greghaynes has joined #openstack-meeting-alt19:00
jistrhi19:00
marios\o19:00
pleia2o/19:00
matty_dubsHowdy19:00
lsmolahello19:00
lifelesso/19:00
lifeless#startmeeting tripleo19:00
rpodolyaka1o/19:01
openstackMeeting started Tue Jan 21 19:00:59 2014 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
jprovaznhi19:01
*** openstack changes topic to " (Meeting topic: tripleo)"19:01
openstackThe meeting name has been set to 'tripleo'19:01
slaglehello19:01
greghayneshi19:01
cody-somervilleHiya19:01
lifeless#topic agenda19:01
*** IlyaE has joined #openstack-meeting-alt19:01
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:01
lifeless     bugs19:01
lifeless    reviews19:01
lifeless    Projects needing releases19:01
lifeless    CD Cloud status19:01
lifeless    CI virtualized testing progress19:01
lifeless    Insert one-off agenda items here19:01
lifeless    open discussion19:01
lifeless#topic bugs19:01
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:01
lifeless#link https://bugs.launchpad.net/tripleo/19:01
lifeless#link https://bugs.launchpad.net/diskimage-builder/19:01
lifeless#link https://bugs.launchpad.net/os-refresh-config19:01
lifeless#link https://bugs.launchpad.net/os-apply-config19:01
lifeless#link https://bugs.launchpad.net/os-collect-config19:01
lifeless#link https://bugs.launchpad.net/tuskar19:01
lifeless#link https://bugs.launchpad.net/tuskar-ui19:01
lifeless#link https://bugs.launchpad.net/python-tuskarclient19:01
dkehnhi19:02
jtomasekhi19:02
tzumainnhiya19:02
jcoufal-mobileHeya! o/19:02
shadower_hey19:02
lifelessso bugs19:02
*** shadower_ is now known as shadower19:02
lifelesswe've got untriaged bugs second week in a row :(19:02
*** rlandy|bbl is now known as rlandy19:02
lifelesshttps://bugs.launchpad.net/diskimage-builder/+bug/126867819:02
*** jrist has joined #openstack-meeting-alt19:03
SpamapSwe've also got a non-working devtest right now.19:03
lifelessruh roh19:03
SpamapShttps://bugs.launchpad.net/heat/+bug/127119019:03
SpamapSbreaking all Heat in-instance users19:03
SpamapSthe patch to fix has been approved19:04
SpamapSNot sure if it is worth marking as affecting TripleO since it will be resolved in Heat within a few hours.19:04
lifelessI am not a big fan of paperwork for paperwork sake19:05
lifelessso meh19:05
SpamapSI suppose knowing what patch to cherry-pick while it wends its way through the gate might be helpful19:05
lifelesswe have criticals already19:05
lifelesshttps://bugs.launchpad.net/tripleo/+bug/127064619:05
lifelessthis breaks tenants19:05
jomara_ahoy19:05
*** ccrouch has joined #openstack-meeting-alt19:05
lifeless2kbps if you're lucky19:05
lifelessanyone with deep network experience feel like owning that and chasing it down to ground?19:06
*** johnthetubaguy1 has quit IRC19:06
SpamapSI think I am the opposite of that person. :)19:06
lsmolahehe19:07
lifelessok, so no volunteers; will take it to the list19:08
lifelesshttps://bugs.launchpad.net/tripleo/+bug/126651319:08
lifelessSpamapS: you're assigned on this, whats the status ?19:08
SpamapSlifeless: I have been badgering the upstreams to host on pypi... netaddr responded immediately, the others did not.19:09
*** ccrouch1 has joined #openstack-meeting-alt19:09
SpamapSlifeless: We can of course do the exception thing for pip. I dropped it late last week hoping to give the upstreams more time.19:09
SpamapSI think there are two.. netifaces may be abandoned.. and I forget the other one.19:09
lifelessSpamapS: so AIUI it's critical because our builds fail right?19:09
*** ccrouch has quit IRC19:10
SpamapSlifeless: I think invididual projects all adapted .. not sure how.19:11
SpamapSJust never revisited to lower it to High.19:11
lifelessSpamapS: since we don't seem to have any actual symptoms at the moment, I think High is better19:11
bnemecDidn't the other projects whitelist the externally hosted deps in tox.ini?19:11
*** julienvey_ has joined #openstack-meeting-alt19:11
SpamapSlifeless: ah, we're not installing any of the ones that need netifaces19:12
lifelessSpamapS: either way :_19:12
SpamapSand we don't install review-day so lazr.restful is not needed19:12
lifelessSpamapS: sounds like its either not a bug for us19:12
lifelessSpamapS: or not hitting us19:12
SpamapSlifeless: I think I may close it.19:12
lifelessSpamapS: I'd F-R it for us19:12
SpamapSi want to verify that swift is not affected somehow and we're just not testing swift19:12
lifelessok https://bugs.launchpad.net/tripleo/+bug/1254246 is also assigned to SpamapS19:12
rpodolyaka1this can be probably be closed too19:13
rpodolyaka1as I already said it's kind of fixed for us19:13
rpodolyaka1and we aren't hitting this, I believe19:13
lifelessrpodolyaka1: you were going to do some validation or something last week?19:13
rpodolyaka1though, there is 'proper fix' waiting on review19:13
rpodolyaka1lifeless: yeah, it works for me19:14
lifelessso, f-r for tripleo?19:14
rpodolyaka1I think, so19:14
SpamapSYeah agreed19:14
SpamapSThough it may also just be masked now.19:14
rpodolyaka1will continue to track this in neutron19:14
lifelessok19:14
lifelesswhat about https://bugs.launchpad.net/tripleo/+bug/125455519:15
lifelessI'm fairly sure we still have a hack in our tree19:15
*** julienvey_ has quit IRC19:16
rpodolyaka1hasn't it been removed?19:17
rpodolyaka1I thought, it was here https://github.com/openstack/tripleo-image-elements/blob/master/elements/tripleo-cd/tripleo-cd.sh19:17
lifeless38ac22ce7c4ea4ee9a86e1b6f2c3e5e31c8ba65219:17
lifelessin incubator19:17
lifelessDate:   Thu Dec 19 10:36:48 2013 +000019:19
lifeless    Merge "Revert "Work around neutron floatingip race condition""19:19
lifelessok, so its gone19:19
lifelesswe can f-r that bug too19:19
lifelessok so that gives us two criticals, one with a fix landing in heat, one that may go all the way to ovs19:20
lifeless#action lifeless to seek owner for network bug on list19:22
lifeless#topic reviews19:22
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:22
lifeless#undo19:22
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3a10d10>19:22
lifelessheh, undo fail19:22
*** krtaylor has quit IRC19:22
lifelessanyhow, I was going to say - please do do one day of triage, collectively we can make sure all the projects are triaged easily19:22
lifeless#topic reviews19:23
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:23
lifelesshttp://russellbryant.net/openstack-stats/tripleo-openreviews.html19:23
lifeless19:23
lifelessStats since the last revision without -1 or -2 :19:23
lifeless3rd quartile wait time: 0 days, 21 hours, 40 minutes19:23
lifelessstill in ok shape - good stuff19:23
lifelesshowever19:23
lifeless19:24
lifelessLongest waiting reviews (based on oldest rev without -1 or -2):19:24
lifeless    12 days, 4 hours, 1 minutes https://review.openstack.org/65699 (WIP: Make rabbitmq-server keep state in /mnt/state)19:24
lifeless    8 days, 2 hours, 42 minutes https://review.openstack.org/52045 (Using merge.py from tuskar to generate overcloud.yaml)19:24
lifeless    4 days, 17 hours, 28 minutes https://review.openstack.org/67348 (Add SSL configuration metadata for overclouds.)19:24
lifeless    4 days, 16 hours, 47 minutes https://review.openstack.org/67356 (Permit deploying an overcloud with SSL endpoints.)19:24
lifeless    4 days, 13 hours, 26 minutes https://review.openstack.org/67358 (Use OS::Heat::UpdateWaitConditionHandle)19:24
lifelesssorry for the size19:24
lifelessthis is a collective fail19:25
SpamapSthis means we're not starting at oldest first maybe?19:25
lifelessI don't know19:25
lifelessbut if you look at those reviews19:25
lifelessthey haven't been -1 or -2'd19:25
lifelessthey've been sitting for days19:25
slaglei just reviewed the ssl stuff this morning19:25
slaglei wanted to test it19:26
lsmolalifeless, I will review the merge.pz, though I think it is still work in progress19:26
*** sarob has quit IRC19:26
slaglealthough, somehow i missed 6734819:26
lifelesslsmola: if its work in progress, it should be marked WIP19:26
lsmolalifeless, I will ask marios19:26
slaglei don't think this reviewable reviews query is very accurate. b/c that one is not in my list19:26
lifelessThis isn't an individual responsibility issue19:26
lifelessslagle: what reviewable reviews query ?19:27
marioslsmola: lifeless: it *is* still wip in the sense that the models/controllers are yet tbd in tuskar19:27
marioslifeless: lsmola : but -1 with appropriate comments are very very welcome at this stage19:27
marioslifeless: lsmola: hence i removed the wip19:27
lifelessmarios: if its not ready for review yet; please mark it WIP, otherwise folk will be trying to review it to get it landed19:27
slaglelifeless: very last link on https://wiki.openstack.org/wiki/TripleO#Review_team19:27
lifelessmarios: ack19:27
lsmolamarios, ok19:27
*** nati_ueno has joined #openstack-meeting-alt19:27
*** gokrokve has quit IRC19:28
slaglei don't typically use it, unless there's lots of reviews. which there have been last few days19:28
lifelessslagle: indeed, that review is missing!19:29
slagleweird19:29
slagletripleo-heat-templates is in the query19:29
lifelessah19:29
lifelessremove is:reviewable19:29
lifelessthat means 'passed jenkins'19:29
*** IlyaE has quit IRC19:29
lifelessbut jenkins was on holiday19:29
lifelessslagle: I'm inclined to suggest we remove that from the wiki page link19:30
slagleright, but then you just get all reviews, including ones you've already reviewed19:30
slaglewhereas is:reviewable removes one you've already done19:30
slagleand your own changes for that matter19:30
lifelessslagle: does it put them back once someone else comments ?19:30
slaglei don't know19:31
SpamapSslagle: sounds like the baby went out with the bathwater there..19:31
slagleit seems to do several things. not all of them well19:31
SpamapSslagle: I'd rather work around ones I've done and my own than miss stuff. :-P19:31
slagleso, yes, i'm with you. let's just remove from teh wiki19:31
*** nati_uen_ has quit IRC19:31
SpamapSFTR I just use gerrit and round-robin among the various tripleo projects.19:32
*** pblaho has joined #openstack-meeting-alt19:32
lifelessok, so this isn't about individual reviewers; we have a large team19:32
pblahogood evening19:32
*** IlyaE has joined #openstack-meeting-alt19:32
lifelessbut we've consistently missed 5 reviews for 2 whole days (ignoring the weekend)19:32
lifelesshas everyone else been using the unified link as well?19:32
*** yamahata has quit IRC19:33
rpodolyaka1me19:33
jdobi use the second to last one, the All one19:33
jdobnot the Reviewable one19:33
*** yamahata has joined #openstack-meeting-alt19:33
lifelessjdob: ok so you'd see everything19:33
jdobi do see my own and things I've commented on, so assuming it aggregates right with no special sauce, then yes19:34
lifelessyeah19:34
lifelessso I don't think 'work harder' will fix this, we've something systemic thats happened; assuming everyone is doing some daily review19:34
lifelessI've been a bit slack this week - sorry19:35
lifelessso - experiment, can folk please try to review the *oldest by submission date* first ?19:35
rpodolyaka1makes sense19:36
slagleack19:36
lifelesshmm, but I can't see how to get that from the unified review19:36
lifelessso this might be a wishlist19:36
jdobi normally tend to check the newest, so i'll start going in reverse19:36
lifelessshall we move on?19:36
lifelesswell, oldest on that page will be least update - which for a change w/out updates will also be oldest submitted19:36
lifelessso yeah, oldest is probably an ok metric19:37
lifelesstrivial rebases will inherit -1's19:37
jdober, the ones at the top of the list is what I meant by newest, not sure if that meant by submission or state19:37
*** michael-yu has joined #openstack-meeting-alt19:37
lifelessso it should be pretty fast to open and check there is no replies etc19:37
lifelessjdob: thats the newest by last-modification19:38
lifelessreviewing counts as a modification19:38
lifelessok, moving on19:38
lifeless#topic  Projects needing releases19:38
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:38
lifelessAFAIK all our projects are in reasonable shape - the issue right now is just heat, right?19:38
rpodolyaka1seems so19:39
marioslifeless: tuskar is obviously still in flux, working out models/controllers etc19:39
lifelessdo we have a release volunteer this week? excluding tuskar* ?19:39
marioslifeless: but no blockers atm19:39
lifelessmarios: or do you want a release cut?19:39
marioslifeless: i don't know what we'de release (no)19:39
mariosimo19:39
jdobi second that no19:39
lifelessok, so excluding tuskar*19:40
rpodolyaka1lifeless: I can take it for this week, but will need a rain check for the next two weeks19:40
lifelessrpodolyaka1: ok!19:40
lifeless#topic  CD Cloud status19:41
*** openstack changes topic to "CD Cloud status (Meeting topic: tripleo)"19:41
jdobmarios: see #tripleo19:41
lifelessHP region - generally good shape, though we've got a number of DC tickets open at the moment19:41
*** mestery has joined #openstack-meeting-alt19:41
lifelessundercloud is happy; cd-overcloud is I believe paused while we put the finishing touches on stateful upgrades19:41
SpamapSlifeless: I don't actually recall why we paused most recently19:42
lifelessci-overcloud is happy19:42
SpamapSovs maybe?19:42
lifelessSpamapS: no, not sure19:42
lifelesslets make sure there's no local patches and restart it19:42
lifelessin incubator/templates/elements19:43
lifelessdprince: hows the RH region ?19:43
SpamapSlifeless: ok, I need to get some Heat retry-on-update patches in shape in the review queue and then I will see if we can resurrect it.19:43
lifelessSpamapS: do we have the waitcondition fix we needed ?19:43
lifelessSpamapS: if you say 'thats waiting for review' I will lol.19:43
SpamapSlifeless: it is awaiting review in Heat. We cherry picked it into the undercloud's heat.19:43
lifelessSpamapS: ok, cool19:44
SpamapShttps://review.openstack.org/#/c/63245/19:44
SpamapSlol away :)19:44
lifelesslol19:44
SpamapSHeat review team seems overwhelmed with i2 surge.19:44
lifelesswe'll come back to dprince I think, time is short19:44
lifeless#topic  CI virtualized testing progress19:44
*** openstack changes topic to "CI virtualized testing progress (Meeting topic: tripleo)"19:44
lifelesspleia2: you is up19:45
* dprince tunes in19:45
*** aignatov_ is now known as aignatov19:45
pleia2this morning I went through the etherpad of our most recent todo list from last week and crossed off what I know was done19:46
pleia2#link https://etherpad.openstack.org/p/tripleo-test-cluster19:46
pleia2we might want to add the ongoing review nodepool work to that (but it was a holiday here yesterday, so I'm still catching up)19:46
lifelessthe node pool patches we need are merged19:47
lifelessthat was just network support19:47
lifelessthe big set thats open is trying to help infra with overload19:47
pleia2ah, gotcha19:47
*** sarob has joined #openstack-meeting-alt19:47
lifelesswhats next for ci virt testing ?19:48
pleia2I think derekh would have a better view of that19:49
lifelessENODEREK19:49
lifelessok19:49
lifelessdprince: RH region of tripleo-cloud, status update?19:49
dprincelifeless: They are disconnecting ports from our internal network to prep for making it public.19:50
lifeless\o/19:50
pleia2sweet19:50
dprincelifeless: in prep for this they downed the ports on the switches19:50
dprinceSo I've lots access :(19:51
* dprince is sad not having access19:51
lifelessprogress is great news19:51
lifelessok19:51
dprinceStill waiting on the IPv4 request too though19:51
lifeless#topic open discussion19:51
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:51
pleia2dprince: shall we have our weekly syncup tomorrow?19:51
dprincepleia2: yes. I think they are still productive for everyone19:52
pleia2great19:52
slaglei'd like to discuss the stable branches for our projects19:52
slaglesounds like we got somewhat of a general concensus on the mailing list discussion19:52
dprincepleia2: although I myself feel like I'm struggling to make progress sometimes :-|19:53
slaglei don't honestly know if there is enough time to do something by I2 which is the 23rd19:53
slaglebut, i plan to start making progress towards it19:53
slaglesound ok?19:53
lifelessslagle: I'd like some time to talk package install stuff with you too :) maybe after my run of meetings today19:53
ekarlsoQ: is there a easy way to setup a testing env for tuskar ?19:53
lsmolaekarlso, devtest19:54
SpamapSHm19:54
ekarlsolsmola: ?19:54
SpamapSwe don't currently include horizon/tuskar in devtest do we?19:54
ekarlsodevstack ?19:54
SpamapSekarlso: http://docs.openstack.org/developer/tripleo-incubator/devtest.html19:54
slaglelifeless: sure, just ping me at some point. i'm on EST time (utc - 5), but am often on in the evenings19:54
lsmolaSpamapS, though it easy to install it in undercloud19:55
lifelessslagle: cool19:55
shadowerekarlso: devtest is a way of setting up tripleo for development/testing19:55
bnemecThere is a horizon element for use in devtest.19:55
ekarlsodoes that do tuskar ? :)19:55
lifelessso stable branches - yeah, I think if someone's going to do it, they should do it in the tent ;)19:55
shadowerekarlso: you'll need to add it to the undercloud image elements19:55
shadowernot sure if we have the UI elementized yet though19:55
mariosekarlso: you'll need to setup tuskar once you've got devtest and an undercloud running19:55
slaglelifeless: the tent?19:56
shadowermarios: iirc the tuskar element's in, the UI maybe not19:56
mariosshadower: ic19:56
shadowermarios: https://github.com/openstack/tripleo-image-elements/tree/master/elements/tuskar19:56
lifelessslagle: oh, there's a saying do you want the camel outside the tent pissing in, or inside the tent pissing out19:56
lifelessslagle: its rather vivid :)19:56
slaglelol. i think i get it :)19:56
lifelessslagle: and I'm not actually comparing you to a camel :)19:56
lifelessplus19:57
ccrouch1i had no idea it was LBJ: http://izquotes.com/quote/24119219:57
jcoufal-mobileshadower: we should have a look on that19:57
lifelesson incubator specifically19:57
*** joel_c has left #openstack-meeting-alt19:57
lifelessI don't want stable releases being done to be blocked on, or force premature matriculation, of incubator contents19:57
*** GheRivero has quit IRC19:57
shadowerekarlso: so before the step 1. here: http://docs.openstack.org/developer/tripleo-incubator/devtest_undercloud.html you'd do `export UNDERCLOUD_DIB_EXTRA_ARGS=tuskar`19:57
lifelessIt's not that I *want* incubator released, but if you're taking a snapshot, it is what it is19:58
shadowerekarlso: once it's launched, you'd have to ssh in and install the tuskar UI manually (for now)19:58
slagleright, well the first thing i was going to do was to get the docs updated to say "it is what it is" and set expectations19:58
*** GheRivero has joined #openstack-meeting-alt19:58
lsmolaekarlso, install devtest then this https://github.com/openstack/tuskar-ui/blob/master/docs/install.rst19:58
lifelessslagle: cool19:58
*** gokrokve has joined #openstack-meeting-alt19:58
lifelessok folks, we're out of time. -> #tripleo for more19:59
lifeless#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Jan 21 19:59:15 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-21-19.00.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-21-19.00.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-21-19.00.log.html19:59
lsmolathanks everybody, have a good night19:59
jcoufal-mobileThanks, have a great night19:59
rpodolyaka1night!19:59
*** sarob has quit IRC20:00
*** greghaynes has left #openstack-meeting-alt20:00
*** tzumainn has left #openstack-meeting-alt20:00
*** gokrokve_ has joined #openstack-meeting-alt20:00
*** matty_dubs has left #openstack-meeting-alt20:00
*** sarob has joined #openstack-meeting-alt20:00
*** tomblank has quit IRC20:01
*** nadya__ has joined #openstack-meeting-alt20:01
pblahogood night20:02
*** pblaho has quit IRC20:02
*** rpodolyaka1 has left #openstack-meeting-alt20:02
*** dguitarbite has quit IRC20:03
*** gokrokve has quit IRC20:03
*** tomblank has joined #openstack-meeting-alt20:04
*** rakhmerov has quit IRC20:04
*** amitgandhi has joined #openstack-meeting-alt20:04
*** sarob has quit IRC20:05
*** gokrokve_ has quit IRC20:05
*** Duane_ has joined #openstack-meeting-alt20:06
*** Leonr has quit IRC20:07
*** hockeynut has left #openstack-meeting-alt20:08
*** DinaBelova is now known as DinaBelova_20:08
*** morazi has left #openstack-meeting-alt20:09
*** rlandy has left #openstack-meeting-alt20:09
*** jistr has quit IRC20:11
*** dteselkin has quit IRC20:11
*** markwash has quit IRC20:12
*** Leonr has joined #openstack-meeting-alt20:13
*** nadya__ has quit IRC20:15
*** krtaylor has joined #openstack-meeting-alt20:16
*** nati_uen_ has joined #openstack-meeting-alt20:16
*** jcoufal-mobile has quit IRC20:18
*** nati_ueno has quit IRC20:19
*** NikitaKonovalov_ is now known as NikitaKonovalov20:24
*** malini is now known as malini_afk20:31
*** nati_uen_ has quit IRC20:33
*** jdob has quit IRC20:35
*** jdob has joined #openstack-meeting-alt20:36
*** sarob has joined #openstack-meeting-alt20:39
*** gokrokve has joined #openstack-meeting-alt20:43
*** jdob has quit IRC20:47
*** jdob has joined #openstack-meeting-alt20:47
*** gokrokve has quit IRC20:47
*** obondarev_ has quit IRC20:59
*** gokrokve has joined #openstack-meeting-alt21:03
*** lblanchard has quit IRC21:05
*** chadlung has joined #openstack-meeting-alt21:06
*** tomblank has quit IRC21:06
*** markwash has joined #openstack-meeting-alt21:07
*** chadlung has quit IRC21:08
*** Duane_ has quit IRC21:08
*** chadlung has joined #openstack-meeting-alt21:08
*** chadlung_ has joined #openstack-meeting-alt21:09
*** chadlung has quit IRC21:09
*** julim has quit IRC21:09
*** markwash_ has joined #openstack-meeting-alt21:10
*** doug_shelley66 has quit IRC21:11
*** pballand has joined #openstack-meeting-alt21:11
*** markwash has quit IRC21:12
*** markwash_ is now known as markwash21:12
*** tomblank has joined #openstack-meeting-alt21:12
*** doug_shelley66 has joined #openstack-meeting-alt21:12
*** michael-yu has quit IRC21:15
*** chadlung_ is now known as chadlung21:16
*** MarkAtwood has quit IRC21:16
*** nati_ueno has joined #openstack-meeting-alt21:23
*** dprince has quit IRC21:23
*** michael-yu has joined #openstack-meeting-alt21:28
*** amcrn has quit IRC21:31
*** amitgandhi has quit IRC21:32
*** NikitaKonovalov is now known as NikitaKonovalov_21:32
*** amcrn has joined #openstack-meeting-alt21:33
*** Duane_ has joined #openstack-meeting-alt21:34
*** jprovazn has quit IRC21:37
*** chadlung has quit IRC21:40
*** ccrouch1 has left #openstack-meeting-alt21:43
*** tomblank has left #openstack-meeting-alt21:45
*** Barker has quit IRC21:53
*** sarob_ has joined #openstack-meeting-alt21:53
*** sarob_ has quit IRC21:54
*** sarob_ has joined #openstack-meeting-alt21:55
*** doug_shelley66 has quit IRC21:56
*** sarob has quit IRC21:56
*** doug_shelley66 has joined #openstack-meeting-alt21:56
*** jcoufal has joined #openstack-meeting-alt21:56
*** sarob_ has quit IRC21:57
*** jdob has quit IRC21:58
*** sarob has joined #openstack-meeting-alt22:00
*** sarob has quit IRC22:00
*** sarob has joined #openstack-meeting-alt22:01
*** sarob_ has joined #openstack-meeting-alt22:02
*** sarob_ has quit IRC22:02
*** lblanchard has joined #openstack-meeting-alt22:02
*** sarob has quit IRC22:06
*** Barker has joined #openstack-meeting-alt22:07
*** sarob has joined #openstack-meeting-alt22:09
*** nati_ueno has quit IRC22:10
*** doug_shelley66 has quit IRC22:10
*** nati_ueno has joined #openstack-meeting-alt22:11
*** esker has quit IRC22:12
*** harlowja is now known as harlowja_away22:14
*** vipul is now known as vipul-away22:19
*** aignatov is now known as aignatov_22:23
*** nati_ueno has quit IRC22:24
*** vipul-away is now known as vipul22:25
*** vipul is now known as vipul-away22:25
*** Duane_ has quit IRC22:25
*** bdpayne has quit IRC22:28
*** eankutse1 has joined #openstack-meeting-alt22:34
*** eankutse1 has quit IRC22:35
*** harlowja_away is now known as harlowja22:35
*** eankutse has quit IRC22:39
*** doug_shelley66 has joined #openstack-meeting-alt22:40
*** IlyaE has quit IRC22:41
*** krtaylor has quit IRC22:42
*** sarob has quit IRC22:45
*** sarob has joined #openstack-meeting-alt22:45
*** yamahata has quit IRC22:50
*** SergeyLukjanov is now known as SergeyLukjanov_a22:50
*** yamahata has joined #openstack-meeting-alt22:50
*** SergeyLukjanov_a is now known as SergeyLukjanov_22:51
*** jmontemayor has quit IRC22:51
*** Barker has quit IRC22:56
*** sarob has quit IRC22:58
*** jpich has quit IRC23:00
*** lsmola has quit IRC23:01
*** sarob has joined #openstack-meeting-alt23:03
*** kevinconway has quit IRC23:03
*** jaypipes has joined #openstack-meeting-alt23:03
*** rnirmal has quit IRC23:04
*** jcoufal has quit IRC23:04
*** HenryG has quit IRC23:07
*** lblanchard has quit IRC23:07
*** sarob has quit IRC23:07
*** harlowja has quit IRC23:07
*** amytron has quit IRC23:09
*** jecarey has quit IRC23:13
*** michael-yu has quit IRC23:16
*** michael-yu has joined #openstack-meeting-alt23:17
*** jtomasek has quit IRC23:19
*** HenryG has joined #openstack-meeting-alt23:19
*** krtaylor has joined #openstack-meeting-alt23:27
*** yogesh has quit IRC23:28
*** lblanchard has joined #openstack-meeting-alt23:29
*** safchain has joined #openstack-meeting-alt23:34
*** safchain has quit IRC23:34
*** amcrn has quit IRC23:40
*** flwang has quit IRC23:42
*** banix has quit IRC23:45
*** Leonr has quit IRC23:48
*** lblanchard has quit IRC23:52
*** flwang has joined #openstack-meeting-alt23:57

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