Tuesday, 2014-01-14

*** harlowja has joined #openstack-meeting-alt00:00
*** sarob has quit IRC00:02
*** yamahata has joined #openstack-meeting-alt00:06
*** csaba is now known as csaba|afk00:09
*** sarob has joined #openstack-meeting-alt00:09
*** sarob has quit IRC00:13
*** zz_ajo has quit IRC00:13
*** sarob has joined #openstack-meeting-alt00:13
*** zz_ajo has joined #openstack-meeting-alt00:13
*** zz_ajo is now known as ajo00:14
*** sarob has quit IRC00:18
*** balajiiyer has quit IRC00:20
*** mozawa has joined #openstack-meeting-alt00:22
*** tian has quit IRC00:23
*** amytron has quit IRC00:25
*** boris-42 has quit IRC00:32
*** sacharya has joined #openstack-meeting-alt00:36
*** betsy has quit IRC00:42
*** yamahata has quit IRC00:44
*** yamahata has joined #openstack-meeting-alt00:44
*** balajiiyer1 has joined #openstack-meeting-alt00:47
*** balajiiyer2 has joined #openstack-meeting-alt00:50
*** markwash has quit IRC00:51
*** balajiiyer1 has quit IRC00:52
*** balajiiyer2 has quit IRC00:55
*** colinmcnamara has joined #openstack-meeting-alt00:56
*** beyounn has quit IRC00:57
*** beyounn has joined #openstack-meeting-alt00:58
*** nati_uen_ has quit IRC00:58
*** nati_ueno has joined #openstack-meeting-alt01:02
*** nati_ueno has quit IRC01:02
*** nati_ueno has joined #openstack-meeting-alt01:04
*** nati_uen_ has joined #openstack-meeting-alt01:05
*** colinmcnamara has quit IRC01:06
*** rudrarugge has joined #openstack-meeting-alt01:06
*** nati_ueno has quit IRC01:08
*** rnirmal has joined #openstack-meeting-alt01:10
*** rudrarugge has quit IRC01:11
*** nosnos has joined #openstack-meeting-alt01:13
*** rnirmal_ has joined #openstack-meeting-alt01:16
*** rnirmal has quit IRC01:17
*** rnirmal_ is now known as rnirmal01:17
*** ViswaV has quit IRC01:20
*** michael-yu has quit IRC01:21
*** harlowja has quit IRC01:22
*** nati_uen_ has quit IRC01:22
*** nati_ueno has joined #openstack-meeting-alt01:23
*** sarob has joined #openstack-meeting-alt01:24
*** sarob_ has joined #openstack-meeting-alt01:24
*** sarob_ has quit IRC01:26
*** sarob_ has joined #openstack-meeting-alt01:26
*** beyounn has quit IRC01:27
*** sarob has quit IRC01:28
*** sarob_ has quit IRC01:30
*** harlowja has joined #openstack-meeting-alt01:33
*** gokrokve has quit IRC01:35
*** gokrokve has joined #openstack-meeting-alt01:36
*** pballand has quit IRC01:36
*** gokrokve_ has joined #openstack-meeting-alt01:37
*** gokrokve has quit IRC01:41
*** gokrokve_ has quit IRC01:42
*** xuhanp has joined #openstack-meeting-alt01:44
*** beyounn has joined #openstack-meeting-alt01:45
*** IlyaE has quit IRC01:45
*** bdpayne has quit IRC01:51
*** balajiiyer1 has joined #openstack-meeting-alt01:51
*** balajiiyer1 has quit IRC01:55
*** nati_uen_ has joined #openstack-meeting-alt02:11
*** yamahata has quit IRC02:13
*** demorris has joined #openstack-meeting-alt02:14
*** nati_ueno has quit IRC02:15
*** yamahata has joined #openstack-meeting-alt02:16
*** esker has joined #openstack-meeting-alt02:17
*** pballand has joined #openstack-meeting-alt02:19
*** sacharya has quit IRC02:37
*** sc68cal has quit IRC02:40
*** pballand has quit IRC02:40
*** sc68cal has joined #openstack-meeting-alt02:41
*** balajiiyer1 has joined #openstack-meeting-alt02:45
*** sc68cal has joined #openstack-meeting-alt02:46
*** demorris has quit IRC02:46
*** nati_uen_ has quit IRC02:50
*** ijw has quit IRC02:51
*** nati_ueno has joined #openstack-meeting-alt02:51
*** coolsvap has quit IRC02:53
*** balajiiyer1 has left #openstack-meeting-alt02:54
*** vipul is now known as vipul-away02:59
*** nati_ueno has quit IRC03:00
*** colinmcnamara has joined #openstack-meeting-alt03:05
*** banix has quit IRC03:07
*** pballand has joined #openstack-meeting-alt03:10
*** SushilKM has joined #openstack-meeting-alt03:11
*** sbalukoff has quit IRC03:13
*** doug_shelley66 has quit IRC03:17
*** vipul-away is now known as vipul03:19
*** SushilKM has quit IRC03:21
*** SushilKM has joined #openstack-meeting-alt03:21
*** amytron has joined #openstack-meeting-alt03:31
*** pballand has quit IRC03:32
*** rnirmal has quit IRC03:33
*** michael-yu has joined #openstack-meeting-alt03:34
*** banix has joined #openstack-meeting-alt03:46
*** ashaikh has joined #openstack-meeting-alt03:52
*** michael-yu has quit IRC03:52
*** amcrn has quit IRC03:56
*** SushilKM has quit IRC03:57
*** nati_ueno has joined #openstack-meeting-alt04:10
*** michael-yu has joined #openstack-meeting-alt04:12
*** esker has quit IRC04:13
*** dguitarbite has joined #openstack-meeting-alt04:13
*** dguitarbite_ has joined #openstack-meeting-alt04:14
*** nati_ueno has quit IRC04:15
*** beyounn has quit IRC04:15
*** michael-yu has quit IRC04:16
*** beyounn has joined #openstack-meeting-alt04:19
*** beyounn has quit IRC04:20
*** bdpayne has joined #openstack-meeting-alt04:23
*** coolsvap has joined #openstack-meeting-alt04:39
*** csaba|afk is now known as csaba04:47
*** SergeyLukjanov has joined #openstack-meeting-alt04:52
*** nati_ueno has joined #openstack-meeting-alt04:53
*** nati_ueno has quit IRC04:55
*** nati_ueno has joined #openstack-meeting-alt04:55
*** markwash has joined #openstack-meeting-alt05:04
*** akuznetsov has joined #openstack-meeting-alt05:10
*** aignatov has joined #openstack-meeting-alt05:11
*** michael-yu has joined #openstack-meeting-alt05:18
*** pballand has joined #openstack-meeting-alt05:19
*** michael-yu has quit IRC05:22
*** arnaud has quit IRC05:23
*** chandankumar has joined #openstack-meeting-alt05:24
*** michael-yu has joined #openstack-meeting-alt05:24
*** arnaud__ has quit IRC05:24
*** markwash has quit IRC05:27
*** markwash has joined #openstack-meeting-alt05:29
*** markwash has quit IRC05:30
*** pballand has quit IRC05:39
*** aignatov has quit IRC05:41
*** markwash has joined #openstack-meeting-alt05:42
*** bdpayne has quit IRC05:46
*** michael-yu has quit IRC05:48
*** sc68cal has quit IRC05:49
*** sc68cal has joined #openstack-meeting-alt05:49
*** nati_uen_ has joined #openstack-meeting-alt05:49
*** nati_uen_ has quit IRC05:50
*** nati_uen_ has joined #openstack-meeting-alt05:50
*** nati_ueno has quit IRC05:53
*** nadya_ has joined #openstack-meeting-alt05:57
*** bdpayne has joined #openstack-meeting-alt05:58
*** banix has quit IRC05:58
*** beyounn has joined #openstack-meeting-alt06:02
*** sbalukoff has joined #openstack-meeting-alt06:04
*** denis_makogon has joined #openstack-meeting-alt06:06
*** coolsvap has quit IRC06:07
*** sbalukoff has quit IRC06:11
*** SergeyLukjanov has quit IRC06:12
*** sbalukoff has joined #openstack-meeting-alt06:14
*** nadya_ has quit IRC06:15
*** boris-42 has joined #openstack-meeting-alt06:18
*** bdpayne has quit IRC06:22
*** csaba is now known as csaba|afk06:24
*** bdpayne has joined #openstack-meeting-alt06:26
*** irenab_ has joined #openstack-meeting-alt06:26
*** irenab_ has left #openstack-meeting-alt06:30
*** coolsvap has joined #openstack-meeting-alt06:32
*** nati_ueno has joined #openstack-meeting-alt06:38
*** nati_uen_ has quit IRC06:41
*** dguitarbite has quit IRC06:46
*** dguitarbite_ has quit IRC06:46
*** doug_shelley66 has joined #openstack-meeting-alt06:46
*** gokrokve has joined #openstack-meeting-alt06:47
*** akuznets_ has joined #openstack-meeting-alt06:49
*** akuznetsov has quit IRC06:49
*** gokrokve has quit IRC06:53
*** SushilKM has joined #openstack-meeting-alt06:55
*** bdpayne has quit IRC07:03
*** boris-42 has quit IRC07:04
*** ashaikh has quit IRC07:09
*** beyounn has quit IRC07:20
*** nati_uen_ has joined #openstack-meeting-alt07:26
*** nati_uen_ has quit IRC07:26
*** nati_uen_ has joined #openstack-meeting-alt07:27
*** nati_ueno has quit IRC07:30
*** akuznets_ has quit IRC07:32
*** akuznetsov has joined #openstack-meeting-alt07:33
*** SergeyLukjanov has joined #openstack-meeting-alt07:35
*** aignatov has joined #openstack-meeting-alt07:46
*** jtomasek has joined #openstack-meeting-alt07:47
*** jcoufal has quit IRC07:48
*** gokrokve has joined #openstack-meeting-alt07:48
*** gokrokve has quit IRC07:52
*** harlowja is now known as harlowja_away08:00
*** xuhanp has quit IRC08:07
*** jcoufal has joined #openstack-meeting-alt08:08
*** ijw has joined #openstack-meeting-alt08:15
*** ijw has quit IRC08:15
*** ijw has joined #openstack-meeting-alt08:16
*** xuhanp has joined #openstack-meeting-alt08:19
*** nati_ueno has joined #openstack-meeting-alt08:21
*** nati_uen_ has quit IRC08:24
*** nati_ueno has quit IRC08:25
*** nati_ueno has joined #openstack-meeting-alt08:25
*** michael-yu has joined #openstack-meeting-alt08:28
*** matrohon__ has joined #openstack-meeting-alt08:32
*** pnavarro has joined #openstack-meeting-alt08:34
*** flaper87|afk is now known as flaper8708:36
*** denis_makogon has quit IRC08:42
*** pnavarro has quit IRC08:44
*** gokrokve has joined #openstack-meeting-alt08:48
*** ruhe has joined #openstack-meeting-alt08:49
*** _ruhe has joined #openstack-meeting-alt08:53
*** gokrokve has quit IRC08:53
*** ruhe has quit IRC08:53
*** _ruhe is now known as ruhe08:54
*** xuhanp has quit IRC08:56
*** michael-yu has quit IRC08:56
*** coolsvap has quit IRC09:05
*** markwash has quit IRC09:06
*** NikitaKonovalov has joined #openstack-meeting-alt09:07
*** mozawa has quit IRC09:13
*** nati_uen_ has joined #openstack-meeting-alt09:20
*** xuhanp has joined #openstack-meeting-alt09:20
*** ijw has quit IRC09:22
*** ijw has joined #openstack-meeting-alt09:23
*** nati_ueno has quit IRC09:23
*** ijw_ has joined #openstack-meeting-alt09:27
*** ijw_ has joined #openstack-meeting-alt09:28
*** pnavarro has joined #openstack-meeting-alt09:31
*** ijw has quit IRC09:31
*** derekh has joined #openstack-meeting-alt09:36
*** coolsvap has joined #openstack-meeting-alt09:38
*** lsmola_ has quit IRC09:39
*** ruhe is now known as ruhe_away09:41
*** ruhe_away is now known as ruhe09:41
*** ruhe is now known as ruhe_away09:42
*** gokrokve has joined #openstack-meeting-alt09:48
*** ruhe_away is now known as ruhe09:49
*** lsmola_ has joined #openstack-meeting-alt09:51
*** gokrokve has quit IRC09:53
*** rook has quit IRC09:58
*** ruhe is now known as ruhe_away10:00
*** ruhe_away is now known as ruhe10:01
*** flaper87 is now known as flaper87|afk10:06
*** nati_ueno has joined #openstack-meeting-alt10:07
*** nati_uen_ has quit IRC10:11
*** nati_ueno has quit IRC10:13
*** nati_ueno has joined #openstack-meeting-alt10:13
*** flaper87|afk is now known as flaper8710:13
*** xuhanp has quit IRC10:16
*** dmakogon_ is now known as denis_makogon10:18
*** NikitaKonovalov has quit IRC10:24
*** NikitaKonovalov has joined #openstack-meeting-alt10:27
*** coolsvap has quit IRC10:27
*** ruhe is now known as ruhe_away10:31
*** akuznetsov has quit IRC10:31
*** akuznetsov has joined #openstack-meeting-alt10:32
*** aignatov has quit IRC10:39
*** lsmola_ has quit IRC10:40
*** ruhe_away is now known as _ruhe10:41
*** gokrokve has joined #openstack-meeting-alt10:48
*** gokrokve has quit IRC10:52
*** lsmola_ has joined #openstack-meeting-alt10:53
*** ashestakov has joined #openstack-meeting-alt10:59
*** nati_uen_ has joined #openstack-meeting-alt11:01
*** nati_ueno has quit IRC11:05
*** boris-42 has joined #openstack-meeting-alt11:07
*** _ruhe is now known as ruhe11:11
*** aignatov has joined #openstack-meeting-alt11:12
*** flaper87 is now known as flaper87|afk11:16
*** flaper87|afk is now known as flaper8711:26
*** SushilKM has quit IRC11:32
*** amotoki_ has quit IRC11:46
*** jcoufal has quit IRC11:47
*** gokrokve has joined #openstack-meeting-alt11:48
*** gokrokve has quit IRC11:53
*** jcoufal has joined #openstack-meeting-alt11:54
*** yamahata has quit IRC12:01
*** jtomasek has quit IRC12:10
*** nati_uen_ has quit IRC12:12
*** HenryG_ has quit IRC12:13
*** jtomasek has joined #openstack-meeting-alt12:13
*** nati_ueno has joined #openstack-meeting-alt12:17
*** SergeyLukjanov has quit IRC12:18
*** SergeyLukjanov has joined #openstack-meeting-alt12:19
*** pnavarro has quit IRC12:21
*** coolsvap has joined #openstack-meeting-alt12:24
*** heyongli has joined #openstack-meeting-alt12:39
*** ruhe is now known as ruhe_away12:42
*** mozawa has joined #openstack-meeting-alt12:45
*** coolsvap has quit IRC12:46
*** irenab_ has joined #openstack-meeting-alt12:48
*** gokrokve has joined #openstack-meeting-alt12:48
*** yamahata has joined #openstack-meeting-alt12:48
*** ruhe_away is now known as ruhe12:51
*** itzikb1 has joined #openstack-meeting-alt12:52
*** SergeyLukjanov has quit IRC12:53
*** gokrokve has quit IRC12:53
*** SergeyLukjanov has joined #openstack-meeting-alt12:54
*** nati_ueno has quit IRC12:54
*** BrianB_ has joined #openstack-meeting-alt12:56
*** baoli has joined #openstack-meeting-alt12:57
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Tue Jan 14 13:00:23 2014 UTC and is due to finish in 60 minutes.  The chair is baoli. Information about MeetBot at http://wiki.debian.org/MeetBot.13:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:00
*** openstack changes topic to " (Meeting topic: PCI Passthrough)"13:00
openstackThe meeting name has been set to 'pci_passthrough'13:00
ijw_peeps13:01
*** yjiang5 has joined #openstack-meeting-alt13:01
irenab_hi13:02
baoliHi everyone13:02
itzikb1hi13:02
baoliIs the proposed agenda ok?13:03
heyonglihi13:03
irenab_baoli:yes13:03
baoliSo let's start with pci flavor13:03
baoli#topic pci flavor13:03
*** openstack changes topic to "pci flavor (Meeting topic: PCI Passthrough)"13:03
yjiang5baoli: I have a question on PCI flavor. Seems you and IJW cares for the PCI flavor overlaping a lot, what's your concern?13:04
baoliit's similar to pci alias, but can be created with an API, and updated with an API to set keys. Keys: vendor_id, product_id, bdf, host_id.13:04
*** sadasu has joined #openstack-meeting-alt13:05
ijw_yjiang5: there's that and the fact that you can't optimise communications with the compute nodes if flavor is essentially arbitrary, though would be the two points.13:05
heyonglisuggest no host_id, keep it global13:05
baoliYongli, that's good13:05
baoliConcerns:13:06
ijw_Also, given baoli's definition of it just there all identical devices would end up in the same flavor which wouldn't be acceptable, but I think that's a more limited description than we discussed previously.13:06
baoliwith overlapping, how do you do counts/stats based scheduling13:07
ijw_If you can annotate devices (preferably on the compute node as you add them) I think that problem goes away13:07
yjiang5baoli,  pci_stats served for the scheduling.13:07
heyonglistats can but implement by longest match, if a device have a,b,c,d it will only in the stats(a,b,c,d) and not in the (a,b)13:08
ijw_baoli: the proposal I had is you pre-group devices into groups where the devices are user-indistinguishable so that you get stats, then your flavors are based on the stat groups.  And you do that by grouping on unique combinations of a set of attrs and only allowing flavors to filter on those attrs.13:08
ijw_heyongli: that implies an ordering of stats13:08
ijw_Of attributes rather13:08
*** ijw_ is now known as ijw13:09
heyongliijw: this will elimate one device in many pci stats and keep scheculer work correctly13:09
ijwWhich 'this' are you referring to13:09
heyongliand make pci flavor it should be13:09
heyonglimy suggest algorithm13:10
baoliyjiang5, pci_stats has keys, right? The keys correspond to the keys assigned to a flavor, right?13:10
*** pdmars has joined #openstack-meeting-alt13:10
yjiang5ijw: yes, exactly.13:10
baoliLet's have one converstation at a time13:10
ijwOK, so we're starting with flavors based on only the 4 stats you listed and vague matching.13:11
baoliSo, yes, the scheduler needs to be smart enough to handle it.13:11
heyongliijw: if you say based on 4 stats, what's this mean13:11
ijwbaoli listed vendor product bdf host13:12
baoliAnother concern is: pci slot (or bdf) info is compute node specific, isn't it?13:12
*** xuhanp has joined #openstack-meeting-alt13:12
irenab_ijw: why host is part of the flavor?13:12
heyongliyeah, seem bdf should be in the global flavor13:12
heyonglishould not13:13
ijwEven if it isn't the same problems come up13:13
ijwheyongli's system won't work because he needs to order the stats for longest match and therefore you can't do an efficient match when the first stat is vague.  And you can't distinguish between identical devices which you want to be in different flavors13:13
baoliYongli, then you can only include vendor_id and product_id in the pci flavor, am I right?13:13
heyonglimight add extra info into flavor13:14
baoliwhat are those extra info?13:14
irenab_heyongli: will this exta info be used for scheduling?13:14
heyonglithat's nutron want ,13:14
yjiang5ijw: seems the pci flavor baoli is talking about is different with our discussion on mailing list .13:14
ijwYes13:15
ijwI think if the extra info is just arbitrary this works better13:15
irenab_can we start with definition of pci favor and then discuss it?13:15
heyongliirenab_ , +113:15
baoliSounds like that we have multiple definitions of PCI flavor13:16
baoliLet's start with Yjang5 and Ijw's13:16
yjiang5irenab_: ok13:16
ijwThe way I would define it is: it's user facing, it can be changed by API, and two flavors can both include the same device13:16
irenab_it is global ?13:16
baoliijw, we want something concrete13:16
ijw(versus group, which, when we were discussing it, was not changeable by API and one device, one group)13:16
heyongliijw, fine, what the exactly define it?13:17
baoliijw, something very concrete13:17
ijwI would expect to define it by matching attributes of the PCI device - and that might include configuration-introduced attributes, not just the ones baoli listed - with a vague match (that is more than one value would hit the match.13:17
heyongligiven a example of vague math13:18
heyonglis/math/match13:18
ijwFor instance, vendor = 0x8086|0x808713:18
heyongliwe can do this by intro duce a simple reguler expresion, so it's ok13:19
*** jtomasek has quit IRC13:19
irenab_ijw: should it represent the provider network connectivity concern?13:19
ijwOr vendor, device = (a, b) or (c, d)13:19
ijwirenab_: I think so.  Also multiple GPUs that are OK13:19
baoliFirst of all, you need to define what attributes can be used to classify the devices13:19
heyonglibaoli: i think except local to host, all if fine for this13:20
yjiang5ijw: I'd define vague match as, a device can be matched by multiple flavor.13:20
ijwbaoli: as I said - ones which are concrete properties of the device (vendor, device) and ones which can be config-supplied and are arbitrary (e.g. connection)13:20
*** esker has joined #openstack-meeting-alt13:20
*** jtomasek has joined #openstack-meeting-alt13:20
irenab_how config-supplied will be managed by scheduler?13:20
ijwyjiang5: I would define that as 'flavors can overlap' because it's not the same thing - I can have a flavor that matches multiple device types and still insist that flavors don't overlap13:20
yjiang5ijw: ok :)13:21
heyongliso flavor to device is m to m , that's fin13:21
heyonglie13:21
ijwirenab_: the proposal on the mailing list suggests that we have a configuration item that lists the properties that can be used in a flavor.  (Or an API item, I'm not choosy, but it would be difficult to change it because you'd need to check all the old flavors were still valid)13:21
baoliijw, any use case for what you have talked about?13:22
ijwYes.13:22
baoliWhy do you need to overlap?13:22
*** matrohon__ has quit IRC13:23
ijwI've added that because people have talked about overlapping in the past, to be honest.  I'm not so certain an overlap is essential.  But you would find it hard to redefine flavors if you couldn't overlap them, I think13:23
*** ruhe is now known as ruhe_away13:23
*** yamahata has quit IRC13:23
heyongliijw; good point13:23
yjiang5irenab_: do you have more question to ijw's definition.13:23
ijwFor instance, I've created a machine that needs device type X, and now I change the flavor to X|Y - but the running machine, if I migrate it, still needs X13:23
*** yamahata has joined #openstack-meeting-alt13:23
baolithat's why we make it autonamous13:24
baoliAnd it's a simple solution13:24
ijwautonomous meaning what?13:24
*** esker has quit IRC13:24
irenab_ijw: so pci flavor is a new resource (object) that can be managed via APIs, no config?13:25
baoliijw, autonomy means the host can elect to join which flavor, rather than defined by some criteria that doesn't meet future requirements13:25
heyonglialias should extend to pci flavor in config file13:25
ijwirenab_: yes.  That was very clearly a popular use case.  John had a good argument, that as you improve your cloud you may want to change your resource types.13:25
irenab_heyongli: so now we have alias, pci flavor and white-list?13:26
heyongliirenab_: no13:26
ijwbaoli: that implies that every identical device in a given host group is interchangeable, but that's not necessarily true.  I think we have to accept that if you have two devices that discover the same on the PCI bus they may have different things attached to them and therefore belong in different flavors.13:26
heyonglialias might should be fade out, maybe13:26
ijwThat's not just network, it applies to storage, for instance, or peripherals13:26
irenab_heyongli: so pci flavor and white list?13:27
heyongliirenab_: i think so13:27
baoliijw, I am lost. that's why the host can say that a device with the same bdf can belong to a different flavor13:28
ijwbaoli: how does it say that?13:28
ijwYou've skipped that bit13:28
heyongliirenab_: and might be a pci_infomation config to add info to device, let's talk it later13:28
baoliijw, in the case of pci group, we define that in the pci passthrough list, right?13:28
heyonglibaoli: what the pci passthrough list?13:29
ijwOk, and if we go back to that we lose the flexibility of being able to redefine flavors because the host defines them (and host state is hard if not impossible to control via API)13:29
baoliijw, why do you need to change the host once it's deployed?13:29
*** jdob has joined #openstack-meeting-alt13:30
baoliheyongli, it's the whitelist13:30
ijwJohn's use case was that you wanted to change the GPUs you were offering to customers, maybe to add a new device type because the new GPU in new machines was as powerful as the old one, maybe to remove a device type because that GPU type had a bug13:30
ijwThe add is not so bad, providing you know you're going to do it when you set the machine up, but the remove is hard to do if your state is on the hosts.13:31
ijwThe add is hard if it's deferred.13:31
baoliijw, we can create PCI group throught APIs, then it's not a problem to do so.13:31
irenab_guys, just to validate and understand better what is going on with all the definitions, can we cover what admin should define in few use cases?13:31
*** ruhe_away is now known as _ruhe13:31
ijwBut if you create PCI group via APIs you then have to propagate that PCI group to all the hosts when it changes13:31
ijwThe idea I had was to try and split the problem down the middle.13:32
baoliWell, no.13:32
*** _ruhe is now known as ruhe13:32
ijwSome of the configuration is static, to simplify the scheduling problem.  Some is dynamic, because you want to be able to modify flavors after the event.13:32
heyongliijw: good example to demo the group is not good13:32
baoliWhen you remove a group, you invalidate all the hosts that use the group, effectively not scheduling any instance on them13:32
ijwPotentially, that's all the hosts.13:32
ijwThough I see where you're going with this and it does work13:33
ijwIt's more complex but more flexible13:33
irenab_simple networking use case, need cisco vNIC, have machines with single cisco NIC. what should be predefined by admin?13:34
baoliijw, I would suggest that you wrote down the proposal in very much detail, including use cases. Then we can further discuss it.13:34
ijwI did, how many times would you like me to write it down again?13:34
baoliI'd like to see the APIs, the attributes that can be included, the exact use cases that it would cover.13:35
baoliIf you check the jan. 8th agenda, that's something we want13:36
irenab_ijw: can we go over the items on today  agenda? I cannot connect between proposed nova boot api and pci flavor/group.13:36
baoliSo that we know what exactly we are proposing, and the pros and cons of it13:36
ijwI have not defined the APIs (which are merely of flavor specification and I've made it clear what is acceptable in a flavor specification), the attributes are explicitly not specified because any attribute can be used providing it's declared in config in advance.  I grant you I could list the use cases.13:36
baoliOk, can we continue to talk about Yongli's PCI flavor, then?13:37
heyonglibaoli: my flavor is ijw's flavor13:38
baoliIt's the same as you have put down in your wiki?13:38
heyonglibaoli: no13:38
yjiang5irenab_: do you want the use case on the meeting or after the meeting?13:38
irenab_if possible, now13:38
heyonglibaoli , my wiki page is kind of old,13:38
irenab_<yjiang513:39
baoliyongli, all right. then let's refine the PCI flavor13:39
irenab_just to see we on the same page13:39
yjiang5ijw: so will you give example, or I need do that?13:39
yjiang5ijw: I'd prefer you, you describe  very clearly :)13:39
*** SergeyLukjanov is now known as _SergeyLukjanov13:40
ijwSorry, lost track.  Example of what, and where, on here or in mail or in a document?13:40
*** _SergeyLukjanov has quit IRC13:40
yjiang5(5:31:29 AM) irenab_: guys, just to validate and understand better what is going on with all the definitions, can we cover what admin should define in few use cases?13:40
yjiang5(5:34:21 AM) irenab_: simple networking use case, need cisco vNIC, have machines with single cisco NIC. what should be predefined by admin?13:40
ijwAh, sorry13:40
ijwYes, so in my case if it's that simple then I think we'd configure that the two attributes we cared about were device and vendor.  We could whitelist the Cisco NICs on the backend and not add any extra_info to them.  The flavor would match a specific device and vendor ID and nothing else.13:41
ijwThe flavor would be created with pci-flavor-create ...13:41
ijw(or however heyongli defined it, I'm not going to argue with his API definition)13:42
irenab_ijw: and when calling nova boot, what will be the command?13:42
ijwDepends.13:42
heyongliijw: any way it's GPUD13:43
ijwIf you're using the NIC as a PCI passthrough device without nova, (like a GPU would be) then:13:43
irenab_ijw: SRIOV13:43
ijwnova flavor-create with extra specs specifying cisco-nic:1 - then nova boot with the flavor13:43
ijwIf it's Neutron then13:43
ijwnova boot --nic net-id=xxx,vnic-mode=passthrough,pci-flavor=cisco-nic ...13:44
baoliijw, this is how it works today13:44
ijwWithout the flavor-create13:44
ijwAnd the ability to change flavors13:44
baolithat's right, but ti's the same functionality13:44
irenab_ijw: so it is not according to what is stated in today's agenda, right?13:45
ijwI didn't write today's agenda, I wrote on the mailing list13:45
irenab_ijw: I thought the agenda represents the points to go with...13:45
ijwIt's largely the same as we were planning.  What the proposal does is try and avoid the scheduler being a nightmare because we can still use the pci_stats table to group PCI devices by attribute, reducing the amount of information the scheduler has to consider.13:45
ijwI was assuming it represented what Robert wanted to discuss13:46
baoliijw, what if on a machine, you want a PCI device with the same vendor id and product id to be excluded from the flavor?13:46
irenab_baoli: I think it won't be on the white-list13:46
ijwbaoli: two options13:46
ijwwe already have a whitelist that would let us exclude it13:46
ijwAlternatively, you can tag up your devices hen you whitelist them with extra_specs, broadly similar to what heyongli's patch does now (though I don't like his config format much)13:47
baoliok13:47
ijwThen you say that that extra_info should be included as a parameter you can use in flavors in the config item, and you can use it as part of the matching expression when you flavor-create13:47
heyongliijw: my patch should be clean up13:48
*** rook has joined #openstack-meeting-alt13:48
irenab_how all this is related to host aggregates?13:48
*** gokrokve has joined #openstack-meeting-alt13:48
ijwIt isn't, I wasn't going anywhere near host aggregates - honestly, I think that's misusing host aggregates13:48
irenab_it is on today's agenda13:48
baoliijw, the extra_specs can't be arbitrary, right? it has to be defined13:48
ijwI would recommend that we don't use host aggregates, in fact13:48
ijwThere's no reason it can't be a dict13:49
*** doug_shelley66 has quit IRC13:49
baoliijw, what if on a host, I want a device with the same vendor id and product id to classified into a different flavor13:49
yjiang5ijw: +1 for host aggregate13:49
ijwbaoli: give me a reason why you would do that13:49
ijwThere are certainly other options than host aggregates.13:50
baoliijw, I agree that we shouldn't add host aggregate in the discussion13:50
irenab_baoli: please remove it from the list on wiki, it is confusing13:50
baoliijw, I thought that we have discussed it over and over again13:50
baoliirenab, which one?13:50
heyonglibaoli: if you really want to , add a tag info for that, in ijw's proposal13:50
ijwbaoli: No, I accept that you would want to do it, but you haven't given a use case there, you've given a requirement.  What drives the requiremetn?13:51
ijwheyongli: absolutely, and I'm trying to understand if baoli's thinking is compatible with that approach13:51
baoliI could have a host with multiple physical connections13:51
ijwSo, baoli - why would you want to do that - what is it that would make you choose to do that, precisely?  An example case would really help here13:51
irenab_baoli: on new proposal for admin api: "configured using host aggregates AP" on meeting wiki13:52
baoliirenab, I didn't add that13:52
ijwYep - and that's a case for tagging, definitely, because I can't choose between those connections by host aggregate13:52
baoliEveryone is trying to update that wiki13:52
baoliijw, please wirte down how exactly that's done13:53
ijwAlternatively, you're saying that you have some hosts with more NICs than others, or some with NICs connected?13:53
baoliRight, I could have multiple NICs that are connected to different subsystems13:53
irenab_baoli: +113:53
*** gokrokve has quit IRC13:53
baoliThat's why we want something such as PCI groups.13:54
baoliWe want to use them as a tool to desgin the cloud13:54
ijwYes, if they're differently connected I don't see how host aggregates help at all, because the NICs are in the same host aggregate and you can't choose between them.13:54
heyonglipci_infomation =  match: {vendor,} , extra: {connection=xxx}13:54
ijwCan I suggest we write *one* document with *absolutely no* implementation details in that lists *just* the use cases that we can then check against our solutions?13:54
baoliijw, host aggregate can be used on top of flavor or group, I have no issue with that13:54
irenab_ijw: actually same host can be in many host aggregates13:54
ijwirenab_: yeah, but the two NICs are on the same host so they're in all its host aggregates13:55
*** akuznetsov has quit IRC13:55
heyonglihost aggregate might be another thing ,we can skip this for later discuss, i think13:55
yjiang5irenab_: so you want host aggregate, or you simply want resolve baoli's case, i.e. different connection for nic on same host?13:55
ijwSo yes - standalone use case document, please - *why* you're trying to do this makes a lot of difference - you might be using a host aggregate here to mark hosts with different hardware or you might be using them for any number of reasons.13:56
irenab_yjiang5: just to resolve baoli case, I didn't add host aggregate eiter13:56
yjiang5irenab_: I think ijw has answer to baoli's question :)13:56
ijwIf it's hardware or connectivity I would go back to arguing that config is more appropriate than host aggregate, because the hardware and connectivity can't be changed by someone on the outside of the API13:56
ijwcan't easily be changed, I should say13:57
irenab_ijw: agree13:57
yjiang5ijw: I don't think anyone here want host aggregate, john is on vocation :)13:57
heyonglii think you want is this: define connect: pci_infomation =  match: {vendor, bdf , } , extra: {connection=xxx}  and select want you want in flavor13:57
ijwOK - apparently you're all playing devil's advocate then, but hopefully I've given you good reasons13:57
baoliyongli, I thought that you are saying that bdf shouldn't be included in the flaour because it's host specific stuff13:58
ijwAnd I think we should add the chosen list of attrs at the outset before we end up with an impossible scheduler13:58
heyonglibaoli: this is not flavor13:58
baoliijw, how do you manage tags. YOu neeed another set of APIs to do that, aren't you?13:58
irenab_we have 2 minutes left13:59
heyonglibaoli: i write is the tag, i think13:59
yjiang5irenab_: for baoli's usacage case, the solution is, when we defien white_list config, (or any other name), we add the connection information, and that connect information will be pci_device's attribute. The flavor can be created with that connect information as key to select device.13:59
baoliyongli, understood13:59
ijwNo, per what heyongli's documented the values are in the inforomation config, and for now at least (and until it proves necessary to change it) I would have the available list in config on the server13:59
ijwWe should be able to hit 99% of use cases with that13:59
heyongliijw: i not talke the key should be use, just how to add a avaliable tag14:00
ijwyjiang5: I see it as a useful place to put arbitrary other information that irenab_'s plugin might want too14:00
baoliOk, i would suggest this given that the time is running out. Write down the exact APIs/concepts for your PCI flavor and we continue tomorrow14:00
yjiang5ijw: yes14:00
baoliAn example would be the jan. 8th's agenda on the wiki14:00
ijwbaoli - use cases.  Please.14:00
irenab_baoli: fine with me14:00
ijwStart a document.  We'll add stuff.  We can check it tomorrow.14:00
baoli#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Tue Jan 14 14:01:08 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-14-13.00.html14:01
ijwnd *no* code, nor implementation suggestions.14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-14-13.00.txt14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-14-13.00.log.html14:01
ijw... or just ignore me, that's fine too.14:01
*** flaper87 has quit IRC14:01
irenab_ijw: are you still here?14:01
ijwyup14:02
ijw-> #openstack-neutron in case another meeting comes along?14:02
yjiang5to openstack-dev?14:02
irenab_ok14:02
irenab_which one?14:02
ijwAh, #openstack-dev.  That's a better plan14:02
*** pcm_ has joined #openstack-meeting-alt14:03
*** pcm_ has left #openstack-meeting-alt14:03
*** dprince has joined #openstack-meeting-alt14:04
*** shshang has joined #openstack-meeting-alt14:04
*** heyongli has quit IRC14:05
*** lblanchard has joined #openstack-meeting-alt14:05
*** SergeyLukjanov has joined #openstack-meeting-alt14:06
shshanghello?14:06
*** shshang has quit IRC14:06
*** demorris has joined #openstack-meeting-alt14:16
*** antigluk has quit IRC14:16
*** antigluk has joined #openstack-meeting-alt14:18
ijwHm, so when's the ipv6 meeting this week...14:21
*** julim has joined #openstack-meeting-alt14:22
*** esker has joined #openstack-meeting-alt14:23
*** pnavarro has joined #openstack-meeting-alt14:23
*** balajiiyer has joined #openstack-meeting-alt14:24
*** balajiiyer has quit IRC14:25
*** flaper87|afk has joined #openstack-meeting-alt14:29
*** flaper87|afk is now known as flaper8714:30
*** flaper87 has quit IRC14:32
*** flaper87 has joined #openstack-meeting-alt14:32
*** shau7246 has joined #openstack-meeting-alt14:33
*** irenab_ has quit IRC14:36
*** codekobe- has joined #openstack-meeting-alt14:39
*** doug_shelley66 has joined #openstack-meeting-alt14:39
*** yjiang5 has quit IRC14:39
*** alcabrera has joined #openstack-meeting-alt14:42
*** sadasu has quit IRC14:43
*** SushilKM has joined #openstack-meeting-alt14:45
*** ajo has quit IRC14:46
*** codekobe- is now known as codekobe14:47
*** ajo has joined #openstack-meeting-alt14:47
*** gokrokve has joined #openstack-meeting-alt14:48
*** sebasmagri has joined #openstack-meeting-alt14:49
*** eharney has joined #openstack-meeting-alt14:50
*** nosnos has quit IRC14:50
*** banix has joined #openstack-meeting-alt14:51
*** gokrokve has quit IRC14:53
*** chandankumar has quit IRC14:55
*** acabrera has joined #openstack-meeting-alt14:56
*** cpallares has joined #openstack-meeting-alt14:58
*** alcabrera has quit IRC14:58
*** malini has joined #openstack-meeting-alt14:59
*** acabrera is now known as alcabrera14:59
alcabrerao/15:00
flaper87o/15:00
*** sarob has joined #openstack-meeting-alt15:00
*** SushilKM has left #openstack-meeting-alt15:00
flaper87Marconi peopleeeeeeeeeeeeee !!!!!!15:00
alcabrerahere, and ready to meet. :D15:01
flaper87I'll kick the meeting off15:01
flaper87#startmeeting Marconi15:01
openstackMeeting started Tue Jan 14 15:01:32 2014 UTC and is due to finish in 60 minutes.  The chair is flaper87. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: Marconi)"15:01
openstackThe meeting name has been set to 'marconi'15:01
malinio/15:01
*** sarob has quit IRC15:01
flaper87#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda15:01
flaper87#topic actions from last meeting15:02
*** openstack changes topic to "actions from last meeting (Meeting topic: Marconi)"15:02
*** slagle has quit IRC15:02
*** sarob has joined #openstack-meeting-alt15:02
flaper87so, most of the action items where on kurt15:02
*** mpanetta has joined #openstack-meeting-alt15:02
alcabrerait also seems like he was able to complete most of the actions, too.15:02
flaper87there's one on me which I didn't address. I'll do it right after this meeting15:03
flaper87#action flaper87 to document service catalog name - make it canonical or whatever15:03
flaper87alcabrera: right15:03
flaper87I saw the updates on the graduation bps15:03
flaper87Did you guys reviewed 1.1 spec ?15:03
*** coolsvap has joined #openstack-meeting-alt15:04
flaper87Any comments?15:04
alcabrera#link https://blueprints.launchpad.net/marconi/+spec/graduation15:04
alcabreraI have not reviewed that spec - recently, anyway.15:04
alcabreraI need to look at v1.115:04
alcabreraMy last impression, of long ago, was that it was looking good.15:04
*** xuhanp has quit IRC15:04
flaper87#link https://wiki.openstack.org/wiki/Marconi/specs/api/v1.1#Changes_from_v1.015:04
alcabreraflaper87: thanks!15:04
alcabreraI'm very happy about the required x-project-id15:05
flaper87alcabrera: agreed, that was my impression too! We also discussed the health API a bit15:05
alcabreraalso, that the client-id is required across the board is also cool. more consistent.15:05
*** ruhe is now known as ruhe_away15:05
flaper87and we finally sorted out the message_max_size thing15:05
alcabrerayes! :)15:05
flaper87#info the spec 1.1 is looking good! We should go through it one more time and have a final review next week15:05
alcabrera+115:06
alcabrerare: max message size15:06
alcabrerait's been simplified nicely, so that we limit based on content length, rather than invesitigating the mesasge contents15:06
alcabreraso, lemme wrap that up in an #info15:06
flaper87alcabrera: go ahead15:06
flaper87thanks15:06
alcabrera#info new message max length approach - simply limit based on content length rather than investigating messages15:07
alcabreraall set15:07
flaper87ok, next topic15:07
flaper87#topic I-2 status15:07
*** openstack changes topic to "I-2 status (Meeting topic: Marconi)"15:07
flaper87#link https://launchpad.net/marconi/+milestone/icehouse-215:07
flaper87we still have a bunch of open bugs15:07
alcabreraOh yes.15:08
flaper87#info open bugs: 3 -> High 4 -> Medium15:08
flaper87we should all focus on close them all15:08
flaper87There are also a bunch of blueprints under development15:08
alcabreralet's check the progress on those.15:08
flaper87and they need to be updated15:08
flaper87alcabrera: out of my head15:09
flaper87thanks!15:09
flaper87:D15:09
alcabrera:)15:09
flaper87Evaluate Pecan FW ?15:09
alcabrerabalajiiyer has been working on that. He won't be able to join us this morning.15:09
alcabreraI'd say slow progress atm.15:09
flaper87#link https://blueprints.launchpad.net/marconi/+spec/pecan-framework15:09
flaper87#info pecan-framework slow progress15:10
flaper87I'll update the BP15:10
flaper87#link https://blueprints.launchpad.net/marconi/+spec/tempest-integration15:10
flaper87malini: ^15:10
alcabrerathanks!15:10
flaper87I saw some of your patches in devstack landed15:10
flaper87congrats!15:10
flaper87thanks for the hard work there15:10
maliniflaper87: thanks :) Reviews are the bottleneck15:10
flaper87malini: yeah, :(15:10
maliniSo I wud still rate is Slow Progress15:10
maliniit*15:10
malinimarconi is a low priority for the tempest team15:11
flaper87#info tempest-integration slow progress15:11
maliniflaper87: Do you think I shud push to have a higher priority?15:11
alcabreraI've +1'd all the things on that one, malini. :)15:11
*** ruhe_away is now known as _ruhe15:11
flaper87it shouldn't be low priority, TBH15:11
maliniSee https://blueprints.launchpad.net/tempest/+spec/add-basic-marconi-tests15:11
flaper87it's just like every other project15:11
flaper87I do think gate issues and blockers should have a higher priority than marconi15:12
flaper87but adding marconi support to tempest should have a high priority15:12
*** _ruhe is now known as ruhe15:12
maliniI'll try to get tht bp  upgarded to high15:12
flaper87I see they're targeting i-315:12
flaper87which means we should move our bp to i-315:12
alcabreracool - consistency + 115:13
flaper87done15:13
flaper87cross transport15:13
malinithanks!15:13
flaper87cpallares: update ?15:13
alcabrera#info tempest integration targeting i-315:13
flaper87#link https://blueprints.launchpad.net/marconi/+spec/cross-transport-api-spec15:13
cpallaresI'm working on the generic communication between the api and the storage15:14
flaper87alcabrera: thnx15:14
*** amitgandhi has joined #openstack-meeting-alt15:14
flaper87cpallares: I moved it to i-3, it won't be ready for i-215:14
cpallaresok15:14
flaper87#info moved cross=transport-api-spec to i-315:14
flaper87cpallares: anything blocking you?15:14
flaper87(besides me)15:14
flaper87:D15:14
cpallaresNope :)15:15
flaper87not even me... good!15:15
cpallareshaha15:15
flaper87#info cross-transport-api-spec moving slow15:15
flaper87#link https://blueprints.launchpad.net/marconi/+spec/load-test15:15
flaper87malini: ^ ?15:15
flaper87it's targeted for i-2 and good progress15:16
flaper87I don't see any patch15:16
maliniI dont know why I never submitted a patch for tht :-$15:16
maliniI have everything in the rackerlabs repo15:16
maliniI'll submit a patch today for tht15:16
flaper87Is it something you can do this week and we can get approve before i-2 ?15:16
maliniI can do it this week15:16
flaper87malini: is i-2 still realistic ?15:16
maliniwhen is i2 deaddline ?15:16
flaper87Jan 23rd15:17
*** itzikb1 has quit IRC15:17
flaper87next week15:17
maliniI can get it in this week15:17
*** sarob has quit IRC15:17
maliniits justa  bunch of xmls & readme15:17
flaper87if you submit it today, we can all review it and get it merged before next week15:17
malinisure15:17
flaper87malini: WHAT?15:17
flaper87you said xml?15:17
malinijust a15:17
flaper87forget it15:17
maliniyes :)15:17
flaper87that won't get in, EVER!15:17
flaper87:D15:17
* flaper87 obviously kidding15:17
alcabreralol15:18
maliniYou'll get a special json poptart15:18
flaper87pls, add 1 line to the bp explaining this15:18
flaper87:)15:18
maliniok15:18
alcabrera{"to": "flaper87", "contents":  ["$"]}15:18
malini:D15:18
flaper87#info load-test bp, good progress! i-2 realistic but kinda mission impossible... pan pan panpan panpan (mission impossible soundtrack)15:18
alcabrera:)15:19
flaper87#link https://blueprints.launchpad.net/marconi/+spec/perf-testing15:19
flaper87erm, Oz ? ^15:19
flaper87is that still valid?15:19
flaper87does any of you know?15:19
malinioz is away this morning15:19
maliniBut I dont think its possible for i215:19
flaper87is icehouse realistic at all?15:19
flaper87if no, I'll remove it from the Ith series15:20
maliniIt'll be better to move it from Ith15:20
alcabreramalini: agreed15:20
*** kgriffs has joined #openstack-meeting-alt15:21
alcabrerakgriffs: o/15:21
flaper87#info removed perf-testing from Ith15:21
flaper87#link https://blueprints.launchpad.net/marconi/+spec/limit-number-queues15:21
kgriffso/15:21
flaper87that hasn't even been approved yet15:21
* kgriffs *really* hates traffic15:21
flaper87kgriffs: yo yo!15:21
flaper87how ya doing?15:21
kgriffssorry guys, the commute was horribad today15:21
flaper87I removed it from i215:21
alcabrerano worries15:21
malinikgriffs: thts what happens when you move away from ATL :|15:21
kgriffslol15:21
flaper87kgriffs: no worries!15:21
kgriffsATL was bad too15:21
* kgriffs wishes he worked from home15:22
malinitht didnt work :(15:22
flaper87#info limit-number-queues removed from i215:22
flaper87#link https://blueprints.launchpad.net/marconi/+spec/http-error-bodies15:22
flaper87#chair kgriffs15:22
openstackCurrent chairs: flaper87 kgriffs15:22
flaper87kgriffs: we're going through https://launchpad.net/marconi/+milestone/icehouse-215:22
kgriffsflaper87: carry on15:22
flaper87we're at http-error-bodies15:22
*** betsy has joined #openstack-meeting-alt15:22
*** shau7246_ has joined #openstack-meeting-alt15:23
flaper87I guess we could move it to i-315:23
kgriffsflaper87: you can keep driving the meeting if you like15:23
flaper87kgriffs: sure, let me finish with the bps and then you can go on if you want15:23
alcabreraflaper87: +1 for moving it15:23
alcabrerato i-315:23
kgriffsso, this sort of falls under "user docs"15:23
flaper87#info http-error-bodies moved to i-315:24
flaper87#link https://blueprints.launchpad.net/marconi/+spec/redis-storage-driver15:24
kgriffsso, I guess that means "low" but we bump it up to "high" for Juno15:24
flaper87kgriffs: agreed15:24
*** gokrokve has joined #openstack-meeting-alt15:24
flaper87alcabrera: ?15:24
alcabrera+115:24
alcabreraoh15:24
alcabrerathat15:24
alcabrerayes15:24
alcabrerait's been very delayed15:24
alcabreraso it's in the same state as a month ago15:25
flaper87alcabrera: i-3 then ?15:25
flaper87boooooo15:25
alcabreralol15:25
alcabreraj-1, realistically15:25
flaper87btw, is this somthing we still want to pull into Marconi's code base ?15:25
kgriffsRedis you mean?15:25
alcabrerahmmm15:25
flaper87yep15:25
kgriffsmmm15:25
*** shau7246 has quit IRC15:25
flaper87I remember we discussed something about keeping the num of sotrage/transport drivers low15:26
alcabreraOn the one hand, having a memory-mostly driver would be a nice analogue to disk-stroage targeting drivers15:26
alcabreraOn the other hand, it's another driver to add to core.15:26
alcabrera*storage15:26
flaper87I'm not against having it15:26
kgriffsI think this is really useful when you start talking queue flavors15:26
kgriffsand we don't have that feature yet either15:26
kgriffsmegan_w: thoughts?15:26
kgriffswhat is the priority on this?15:26
flaper87I think we should've 1 nosql, 1 rdbms, 1 memory and 1 amqp(or some real messaging backend)15:27
flaper87kgriffs: just moved it out from ith15:27
flaper87kgriffs: sounds like Jth thing15:27
alcabreraflaper87: that's the logic I was considering. :)15:27
kgriffsyeah, TBH I don't think we will have time to do the "1 memory and 1 AMQP/bridge"15:27
flaper87ah, flavors you mean, erm dunnon if we have a priority for that15:27
kgriffs(in Icehouse)15:27
*** gokrokve_ has joined #openstack-meeting-alt15:27
kgriffsflaper87: should be a bp for flavors15:27
flaper87not enough time for that, agreed15:27
*** betsy has quit IRC15:27
kgriffsthat should be scheduled to land same time as Redis15:27
*** kevinconway has joined #openstack-meeting-alt15:28
flaper87fwiw, I approved the redis patch, not scheduled yet, though.15:28
*** gokrokve has quit IRC15:28
flaper87#link https://blueprints.launchpad.net/marconi/+spec/nose-testr15:28
kgriffs#link https://blueprints.launchpad.net/marconi/+spec/marconi-queue-flavors15:28
kgriffs(fwiw ^^^)15:28
alcabreracool15:28
alcabreranose-testr is getting close15:28
kgriffs(there is no "Juno" series yet - we can schedule those later)15:28
flaper87good progress, pypy decided to block me, though!15:29
flaper87hopefully, I'll sort that out this week15:29
flaper87#link https://blueprints.launchpad.net/marconi/+spec/make-ttl-optional15:29
flaper87kgriffs: yup, I'm just removing the series for now15:29
flaper87I haven't started working on that (AFAIK) :P15:30
*** Barker has joined #openstack-meeting-alt15:30
flaper87so, I guess i-315:30
*** IlyaE has joined #openstack-meeting-alt15:30
flaper87I think it makes sense for Ith, though.15:30
flaper87so keeping it in the Ith series15:31
alcabrera+115:31
flaper87just moving it to i-315:31
kgriffsyes, since it requires api version rev15:31
kgriffsso we want to get that in along with v1.115:31
flaper87#link https://blueprints.launchpad.net/marconi/+spec/flag-private-log-data15:31
flaper87kgriffs: agreed15:31
flaper87that bp looks empty :P15:31
flaper87I just removed the i-2 milestone15:32
kgriffshmmm15:32
kgriffslet's see...15:32
*** baoli has quit IRC15:32
flaper87kgriffs: mind explaining it a bit15:32
flaper87?15:32
kgriffsat the moment, are we logging anything we shouldn't?15:32
kgriffsbasically, we don't want to log sensitive data by accident15:32
flaper87is it related to the logging discussion we had in #solum ?15:32
kgriffsflaper87: yes15:32
flaper87cool15:32
alcabreraThe wiki page linked to is very informative15:33
flaper87alcabrera: agreed!15:33
kgriffsreally, oslo logging needs to support designating sensitive data15:33
flaper87the bp says: Track what solum is doing.15:33
flaper87Will it require doing some coding?15:33
kgriffsanyway, I kinda think this can wait for i3, low or even Juno15:33
alcabreraWe can audit our log calls using `grep` and find out where we're logging sensitive details.15:33
alcabreraI'm +1 for j-115:33
flaper87kgriffs: it didn't have a series assigned15:34
kgriffsi know we aren't logging creds15:34
kgriffsor message bodies afaik15:34
flaper87so, I removed the milestone and I'd lean towards Jth15:34
flaper87kgriffs: correct15:34
kgriffsflaper87: make it so15:34
flaper87we don't even have creds, AFAIK!15:34
flaper87:P15:34
flaper87I mean, keystone but...15:34
kgriffstokens15:34
flaper87yeah, we barely touch them15:34
*** jecarey has joined #openstack-meeting-alt15:34
kgriffs(which is a good thing)15:34
flaper87s/touch/use/15:34
flaper87kgriffs: agreed15:34
kgriffskk15:35
flaper87ok, so for i-2 we now have 3 bps pending15:35
flaper87pecan sounds like it will be moved to i-315:35
*** adrian_otto has joined #openstack-meeting-alt15:35
flaper87and a bunch of bugs that we should fix asap15:35
flaper87those seem like good fit for i-215:35
flaper87flwang is not around15:36
flaper87nor is ykaplan15:36
flaper87so, the extra items in the meeting agenda can't be addressed15:36
kgriffs#link https://launchpad.net/marconi/+milestone/icehouse-215:36
flaper87kgriffs: want to talk about Push-based message consumption ?15:36
kgriffssure15:37
flaper87#info Today we have a mid-cycle incubation review15:37
flaper87#topic Push-based message consumption15:37
*** openstack changes topic to "Push-based message consumption (Meeting topic: Marconi)"15:37
flaper87kgriffs: floor is yours15:37
kgriffsso, we sort of touched on this a couple weeks back15:37
kgriffsbasically, we need to decide first whether we need it, and second the simplest way to do it that could possibly work15:38
kgriffsso, I think we need it for notifications, if nothing else15:38
kgriffsthoughts?15:38
alcabrerahmmmm15:38
alcabrerawe do need it for notifications15:39
alcabrerathere's no way around that15:39
kgriffslet me play devil's advocate15:39
flaper87mmh, the way I see it is that: 1) It's transport specific, 2) Although we need it for notifications, we shouldn't limit it to notifications15:39
flaper87dunno if that makes sense15:39
alcabreraflaper87: what you say makes sense15:40
kgriffswhy do we need it for notifiactions?15:40
* kgriffs takes off devil horns15:40
alcabreraheh15:40
alcabreraso, good question15:40
alcabreraIf we need it for notifications, it's because we want to take the burden of polling for new notifications off the client.15:41
kgriffscan we quantify that burden?15:41
kgriffslet us assume the following:15:41
flaper87I'd say it's more related to the technical requirement than the usability itself15:42
alcabrerayup, though it's tricky. I'm thinking of mobile, battery-powered clients on one end.15:42
kgriffsMarconi can serve a poll request in 20-30ms15:42
flaper87for example, it's cheaper to keep the connection open than opening every time15:42
kgriffsMarconi can enable keep-alive for extended periods (say 2-3 minutes)15:42
flaper87also, push notifications imply a nearer real-time messaging delivery15:42
kgriffsconsider that a client gets batches of messages, not just one at a time15:43
kgriffsso, if I get a new big batch every 20-30 ms15:43
flaper87wait, are we just talking about http or transports in general ?15:43
kgriffsand I am pushing to something like SMS, email, APN15:43
kgriffsthe bottleneck is going to be the target sink, not the polling15:43
kgriffsflaper87: specifically, notifications with HTTP15:44
kgriffsthis is a thought experiment to see if it is viable15:44
flaper87ohhhhhh, that changes my thoughts, then!15:44
kgriffs(without long-polling or websocket)15:44
flaper87if we enable keep-alive you're doing long-polling15:45
*** paulmo has joined #openstack-meeting-alt15:45
flaper87s/you're/we're/15:45
alcabrerathere's also this coming in the not-too-distant future: http://http2.github.io/http2-spec/#PushResources15:45
kgriffsah, yes15:45
kgriffshttp 2.015:45
kgriffsw00t15:45
alcabrera:)15:45
flaper87so, http specific notifications15:45
kgriffsright15:45
flaper87I agree with you15:45
kgriffsso, here is what I think15:45
kgriffsyou could do something pretty decent just using polling plus keep-alive15:46
kgriffsthe pro is this keeps the backend simple15:46
flaper87the important bit here is: "We're not preventing anyone to do it, we just don't want it in the code base because polling is good enough based on these assumptions"15:46
alcabreraflaper87: +115:46
kgriffs(i.e., keeping track of everyone listening to different channels on different boxes and notifying them when something happens is a PITA)15:47
kgriffsflaper87: so, right15:47
flaper87kgriffs: marconiclient itself can handle this, which removes the burden from the user15:47
kgriffsif we do implement true push messaging15:47
*** shau7246_ has quit IRC15:47
kgriffsthat driver is going to be pretty complicated unless you assume that every client that is listening on a particular queue is routed to the same physical box15:48
kgriffsand even then, you would probably want the same proc, but you could use IPC15:48
kgriffsanyway, it is doable with zmq and stuff, just not trivial15:48
alcabrerakgriffs: agreed15:48
flaper87kgriffs: correct!15:49
flaper87the overall architecture suggests that using polling is better15:49
flaper87(Marconi's architecture, I mean)15:49
kgriffsso, to flaper8715:49
kgriffsi mean15:49
kgriffsto flaper87's point15:49
kgriffswe don't want to prevent someone from doing all that work15:50
kgriffsbut I don't feel like it is high priority to do this within Marconi for a while yet, at least15:50
flaper87agreed15:50
flaper87I think it's still premature to think about this15:50
*** shau7246 has joined #openstack-meeting-alt15:50
flaper87we don't want to get ahead of ourselves with this specific feature15:50
flaper87I think time and users will dictate what should happen15:51
kgriffswith, say, a zmq transport driver15:51
alcabreraI think we'll get a better idea about what we need when we start working on notifications15:51
kgriffswe can just have RPC style request-response15:51
flaper87kgriffs: I did that in glance15:51
flaper87:)15:51
kgriffsif we want to do AMQP then we kinda have to do push, right?15:51
*** dtroyer has joined #openstack-meeting-alt15:51
flaper87glance-api -> glance-registry (RPC over http)15:51
*** ViswaV has joined #openstack-meeting-alt15:51
flaper87anyway15:51
*** aignatov has quit IRC15:51
flaper87kgriffs: yea15:51
flaper87kgriffs: yeah15:51
kgriffstbh, I have had more people request JMS than AMQP15:52
kgriffsbut that may just be the circles I walk in15:52
*** psumkin has joined #openstack-meeting-alt15:52
*** ViswaV has quit IRC15:52
flaper87#agreed Lets not worry about push messaging support. The overall architecture suggests that polling is good enough for the current status of the project and use cases15:53
*** NikitaKonovalov has quit IRC15:53
kgriffslet's run with that15:53
alcabreracool15:53
*** noorul has joined #openstack-meeting-alt15:53
flaper87awesome15:53
kgriffswe will have to actually try it to be sure15:53
alcabreraany other thoughts on push-based messaging?15:53
kgriffsthat's it from me15:53
flaper87#topic Open Discussion15:53
*** openstack changes topic to "Open Discussion (Meeting topic: Marconi)"15:53
kgriffslet me just plug this: https://wiki.openstack.org/wiki/Marconi/specs/api/v1.115:53
flaper87Everyone, remember today's TC meeting15:53
*** SergeyLukjanov has quit IRC15:53
kgriffsmegan_w: ^^^15:53
alcabreraI have it on my calendar! :D15:53
kgriffswhere's balaji?15:53
alcabrerahe's out for the day, I think15:54
kgriffsoh15:54
kgriffsok15:54
alcabreraGeorgia Tech or some such. :)15:54
*** jmontemayor has joined #openstack-meeting-alt15:54
kgriffsmalini: have you had a chance to review the v1.1 draft?15:54
kgriffsI'd like everyone to review the v1.1 spec for next time15:54
maliniI did not :(15:54
maliniI'll review the 1.1 spec15:55
kgriffskk, no worries. Just curious15:55
flaper87kgriffs: we kinda talked about it. The summary of our comments is: "It looks good, we need to go through it one more time"15:55
flaper87but it looks good and we're all happy15:55
kgriffsmalini: can you copy the error responses tables ?15:55
flaper87gotta run15:55
kgriffsI would like a v1.1 version. I think status codes may change in a couple spots15:55
flaper87kgriffs: could you end the meeting15:55
kgriffsflaper87: thanks for leading the mtg!15:55
kgriffswill do15:55
kgriffsok folks, anything else?15:55
alcabreraI'll update the minutes.15:56
alcabrera:)15:56
malinikgriffs: https://wiki.openstack.org/wiki/Marconi/specs/api/v1/errors15:56
kgriffsalcabrera: ur my hero!15:56
alcabreralol15:56
*** devkulkarni has joined #openstack-meeting-alt15:56
*** vgnbkr_1 has quit IRC15:56
kgriffsmalini: right, let's copy that and but under /v1.1/errors15:56
kgriffss/but/put15:56
*** pballand has joined #openstack-meeting-alt15:56
malinikgriffs: ok15:57
kgriffs#action malini to copy v1/errors page to v1.1/errors15:57
kgriffsthanks!15:57
kgriffs#endmeeting15:57
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:57
openstackMeeting ended Tue Jan 14 15:57:19 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-14-15.01.html15:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-14-15.01.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-01-14-15.01.log.html15:57
*** vgnbkr_1 has joined #openstack-meeting-alt15:58
*** mspreitz has joined #openstack-meeting-alt15:58
*** aratim has joined #openstack-meeting-alt15:58
*** paulczar has joined #openstack-meeting-alt15:58
*** muralia has joined #openstack-meeting-alt15:59
*** alcabrera has left #openstack-meeting-alt16:00
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Jan 14 16:00:18 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:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: Solum Team Meeting)"16:00
openstackThe meeting name has been set to 'solum_team_meeting'16:00
*** ruhe is now known as ruhe_away16:00
adrian_otto#topic Agenda16:00
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-01-14_1600_UTC Today's Agenda16:00
*** openstack changes topic to "Agenda (Meeting topic: Solum Team Meeting)"16:00
*** le089 has joined #openstack-meeting-alt16:00
adrian_otto#topic Roll Call16:00
*** openstack changes topic to "Roll Call (Meeting topic: Solum Team Meeting)"16:00
adrian_ottoAdrian Otto16:00
*** Barker has quit IRC16:00
coolsvapSwapnil16:00
gokrokve_Georgy Okrokvertskhov16:00
paulmoPaul Montgomery16:00
noorulNoorul Islam16:00
muraliamurali16:00
paulczarPaul Czarkowski16:00
*** mpanetta has left #openstack-meeting-alt16:00
devkulkarniDevdatta16:00
aratimArati Mahimane16:00
nmarchenkoNikita Marchenko, Mirantis16:01
julienveyJulien Vey16:01
le089Leonid Kornilenko, Mirantis16:01
stanniePierre Padrixe16:01
*** sc68cal has quit IRC16:01
*** claytonc has joined #openstack-meeting-alt16:01
claytoncClayton16:01
*** eharney_ has joined #openstack-meeting-alt16:01
psumkinPavel Sumkin, Mirantis16:01
*** sc68cal has joined #openstack-meeting-alt16:01
adrian_ottogood morning everyone!16:01
*** eharney has quit IRC16:02
muraliamorning, and happy new year to everyone.16:02
*** eharney_ is now known as eharney16:02
*** Barker has joined #openstack-meeting-alt16:02
adrian_ottofeel free to chime in to record your attendance as we proceed16:02
adrian_otto#topic Announcements16:02
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:02
adrian_ottoWelcome to the first Solum Team Meeting of 2014. Happy New Year!16:02
gokrokve_Happy New Year!16:02
coolsvapHappy New Year!16:02
*** sebasmagri has left #openstack-meeting-alt16:02
adrian_ottoOur planned announcements:16:03
adrian_otto1) I updated our Roadmap wiki at: https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap to transition version numbering to milestone name, and added an additional feature grouping for additional granularity.16:03
*** ashaikh has joined #openstack-meeting-alt16:03
*** cpallares has left #openstack-meeting-alt16:03
adrian_ottoI wanted to call this to your attention just in case there was any input from the team that should be integrated at this stage. We will continue to revise the roadmap, so this should not be considered a permanent plan.16:04
devkulkarnimilestone based grouping is looking nice16:04
*** demorris_ has joined #openstack-meeting-alt16:04
gokrokve_Are we going to implement R2.2?16:04
gokrokve_It looks like quite complex task.16:04
*** kraman has joined #openstack-meeting-alt16:04
adrian_ottogokrokve_: good catch16:04
*** demorris has quit IRC16:04
*** demorris_ is now known as demorris16:04
adrian_ottowe did actually put that out of scope, so I will move that to M216:05
adrian_ottoother thoughts on this?16:05
gokrokve_R2.3 also looks out of scope.16:05
adrian_ottogokrokve_: R2.3 is currently targeted for M216:06
*** sarob has joined #openstack-meeting-alt16:06
devkulkarniadrian_otto: what is meaning of P1, P2 etc.+16:06
gokrokve_Ok. We will need to check progress in this direction. I don't see anything for that in the code.16:07
gokrokve_P2 is a second priority.16:07
adrian_ottothe R coes are what we used in the roadmap before we had all the BP's created.16:07
adrian_ottoWe could just link the the BP's, or link to the BP list for the release16:07
adrian_ottodevkulkarni: does that make sense?16:07
*** ifarkas has joined #openstack-meeting-alt16:08
paulmols16:08
paulmooops16:08
devkulkarniyes. linking BPs would help..16:08
adrian_ottogokrokve_: yes, the language pack framework is a WIP still16:08
adrian_otto#action adrian_otto to update https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap with links to find milestone blueprints16:08
gokrokve_Who is driving LP development?16:09
adrian_otto#action adrian_otto to remove R2.2 from M1 in the roadmap wiki16:09
devkulkarniLP working group16:09
gokrokve_Probably we can split this ctivity and do something in parallel.16:09
adrian_ottogokrokve_: the working group for LP. I will get you the link for the meeting series, one sec16:09
gokrokve_I have it.16:09
adrian_otto#link https://wiki.openstack.org/wiki/Solum/BreakoutMeetings16:09
*** ruhe_away is now known as _ruhe16:09
adrian_ottook, any more thoughts on the roadmap update before I proceed to other announcements?16:10
adrian_ottonext announcement:16:10
adrian_otto2) Notice that we have a CLI action item on our agenda after the BP updates.16:10
dtroyerand I made it in time… ;)16:11
adrian_ottoso when we get our BP update for the CLI work item, we will be tempted to discuss that, but please hold back a bit until we get to that part of the agenda16:11
devkulkarnidtroyer: thanks :)16:11
adrian_ottodtroyer: YES! THanks for coming16:11
adrian_ottoAre there other announcements other team members would like to make?16:11
adrian_ottook, proceeding16:12
adrian_otto#topic Review Blueprints16:12
*** openstack changes topic to "Review Blueprints (Meeting topic: Solum Team Meeting)"16:12
adrian_otto#link https://launchpad.net/solum/+milestone/milestone-1 Milestone-1 Blueprints16:12
adrian_ottoNOTE: I don't expect a ton of progress to be reported on these because many of us took a holiday break. If there is no progress, that's okay, just indicate such with a "no change" update.16:12
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-minimal-cli Command Line Interface for Solum (devdatta-kulkarni)16:12
devkulkarniUpdates are as follows:16:13
devkulkarni1) Noorul has been working on the API side that can be consumed by cli16:13
devkulkarni2) paulmo has been working on the cli proper.16:13
devkulkarninoorul, paulmo, you want to give updates etc. from your side?16:13
noorulIt is ready for review https://review.openstack.org/#/c/58067/16:13
*** akuznetsov has joined #openstack-meeting-alt16:14
adrian_ottolinks to the respective reviews will be provided in a few minutes as well. They are in the new wiki page16:14
devkulkarninoorul: great!!16:14
paulmoI just made a pull request with a hopefully pep8 compliant argparse-based CLI: https://review.openstack.org/#/c/66617/116:14
devkulkarnipaulmo: cool16:14
adrian_ottothanks to all of you for your progress on this.16:14
noorulnp16:14
devkulkarnithats it for minimal-cli16:15
adrian_ottook, so we will come back to this in just a moment after the other bp updates, and set some clarity on our direction for next steps16:15
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/user-authentication User authentication for incoming requests (gokrokvertskhov)16:15
adrian_otto#link https://review.openstack.org/58811 Change I16aa0ba6: This patch adds a user authentication of incoming request. (merged)16:15
adrian_ottoCongratulations gokrokve_!16:15
* paulmo cheers!16:15
*** ashaikh has quit IRC16:15
devkulkarnigokrokve_: congrats!!16:16
gokrokve_Thank you!16:16
adrian_ottoany remarks on this? I think we are ready to drop it form the status list and mark the BP as completed16:16
noorul+116:16
adrian_otto#action adrian_otto to drop https://blueprints.launchpad.net/solum/+spec/user-authentication from the weekly agenda and mark the BP as finished16:16
*** jcoufal has quit IRC16:16
adrian_ottothanks to gokrokve_ and our reviewers for a lot of attention to that work16:17
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/specify-lang-pack pecify the language pack to be used for app deploy (devdatta-kulkarni)16:17
*** markwash has joined #openstack-meeting-alt16:17
adrian_otto+s16:17
devkulkarniOkay. so updates on this are as follows:16:17
devkulkarnithis bp is about storing langpacks; we discussed in the metadata repository meeting to create bps against glance to store langpack metadata16:18
adrian_ottowe have Change Ib5a05908: WIP: Defined a resource to query available language packs. (abandoned)16:18
*** ViswaV has joined #openstack-meeting-alt16:18
adrian_ottois that work no longer relevant to this BP?16:18
devkulkarnioh yes. that WIP was based on the code that murali had not merged yet.16:18
adrian_ottoshould that be re-opened, or are we starting over?16:18
devkulkarniit can be abandoned; or reviewed to make it follow murali's current work16:18
devkulkarniI will touch base with Murali about it.16:19
muraliasure16:19
gokrokve_devkulkarni: I don't think we have to wait for Glance here.16:19
adrian_ottocan we issue some action items for the tasks to open the glance blueprints? Who should draft those?16:19
gokrokve_There is no final decision in Glance when this repository will be implemented.16:19
devkulkarnigokrokve_: yes, for the GET calls we don't have to wait16:19
devkulkarnigokrovkve_: what is the current status of the metadata repository working group?16:20
gokrokve_devkulkarni: I propose to have somethink done in SOlum and then move it to Glance.16:20
devkulkarnigokrokve_: sure. makes sense.16:20
gokrokve_devkulkarni: We are waiting for the mini-sumit which will occur on Jan 27th16:20
devkulkarniI will follow up my WIP with the additional work then16:21
adrian_ottoclarification: the Glance mini-summit happens Jan 2716:21
gokrokve_devkulkarni: We will work with Glance team to understand how this new repo will be implemented.16:21
*** boris-42 has quit IRC16:21
gokrokve_Yep. Glance mini-sumit in Washington DC, Jan 27th-28th16:21
devkulkarniokay. so that is little long term. for solum, as you are suggesting, we can do work first here and parallely work with Glance team16:21
gokrokve_devkulkarni: Sure. Right now our LP is not big. Just keep all LP data in SQL DB for now.16:22
devkulkarniadrian_otto: so to answer your question, here is what I propose.16:22
adrian_otto#action 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:22
gokrokve_Otherwise we will not finish LP work before M2.16:22
devkulkarnigokrokve_: yep! I was about to say exactly that.16:23
adrian_ottodevkulkarni: was there more to your thought about what you propose?16:23
gokrokve_adrian_otto: I will be on this summit. Do you have anyone from Solum team as a representative?16:23
devkulkarniadrian_otto: you kind of captured it. I will touch base with murali16:23
adrian_ottogokrokve_: where is it being held?16:23
devkulkarnithat is all.16:23
adrian_ottoare there other Stackers besides gokrokve_ who we should send to attend in person?16:24
gokrokve_Hilton Washington Dulles Airport16:24
gokrokve_13869 Park Center Road16:24
gokrokve_Herndon, Virginia 2017116:24
gokrokve_adrian_otto: Washington DC,16:24
devkulkarnigokrokve_: randall_burt is going to there as well (representing heat). I am syncing up with him on solum requirements16:24
adrian_ottogokrokve_: tx16:24
adrian_ottook, that will work nicely I think16:25
adrian_ottoclaytonc or kraman do either of you plan to attend?16:25
gokrokve_devkulkarni: Cool!16:25
kramanI wont be able to attend this one16:25
claytoncadrian_otto: not currentyl planned, going to sync with other red hatters who might be there16:26
gokrokve_adrian_otto: What do you think about Solum mini-summit? Do we need to meet face 2 face?16:26
devkulkarniadrian_otto: as an aside, the specify-lang-pack bp is just a part of the overall lang-pack work. I think we should discuss the overall lang-pack work as well.16:26
gokrokve_devkulkarni: Do you need help with specify LP BP?16:27
adrian_ottook, let's come back to the Solum summit question during open discussion16:27
*** Barker has quit IRC16:27
devkulkarnigokrokve_: let me check back with you (need to sync up with murali about the current state of the code)16:28
*** Barker has joined #openstack-meeting-alt16:28
devkulkarnigokrokve_: thanks for the offer16:28
*** IgorYozhikov has joined #openstack-meeting-alt16:28
paulmols16:28
claytoncre: lang pack the working item right now is https://blueprints.launchpad.net/solum/+spec/lang-pack-examples which paulczar and funzo have been working on.  funzo is under the weather, but we have working templates for the existing images and have poc'd the docker cloud-init flow16:28
gokrokve_We plan to add one more engineer from Mirantis to Solum.16:28
devkulkarnigokrokve_: cool16:29
muraliawoohoo!16:29
adrian_ottogokrokve_: that's terrific!16:29
devkulkarniclaytonc: thanks for the updates16:29
claytoncthere was discussion about using disk image builder to generate images - the issue raised was security isolation of the images (since prepare is an untrusted set of code) and steve dake shared some examples of dib running untrusted.  however for right now the flow that will work will be cloud-init with nova16:29
adrian_ottook, so we have just a couple more BP's to visit16:29
claytoncso we're ready to integretae at least some of those flows with krishna's git-flow16:29
paulczarPOC'd cloud-init flow is described here - https://gist.github.com/paulczar/db83487376fcbc9b75de16:30
paulczarI need to move that to the wiki, and see if I can puts together some scripts for contrib/16:30
paulczar^ docker16:30
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo)16:31
adrian_ottoI'm pretty sure we don't have news on this one, right?16:31
paulmoThat is on hold right now with CLI activity.  Also, I don't think we have consensus on direction with this one.16:31
adrian_ottopaulmo: what is your suggestion for proceeding on this?16:32
paulmoWell, gokrokve_ and I have 2 different pull requests for context implementation consideration...16:32
paulmoI think we need to have a meeting and wrestle this topic to the ground soon.16:33
gokrokve_paulmo: These security context is a small part of logging.16:33
adrian_ottook, would you like any help with arranging that, or will you work that out individually?16:33
paulmoFor instance, is supportability in scope for Solum (logging control plane issues and letting the customers take a peak at it)16:33
paulmoI would love help… this has been churning for a while.16:33
gokrokve_paulmo: I can start thinking in logging direction too if you want.16:34
adrian_otto#action adrian_otto to schedule a meeting about security context and logging features for M116:34
adrian_ottook, we'll make a time for that16:34
devkulkarniadrian_otto, paulmo, gokrokve_: +116:34
adrian_ottoanyone interested in that, so I can be sure to make you aware of the meeting time?16:34
paulmoI think russellb is needed, he had a vested interest16:34
kgriffsadrian_otto: me16:34
coolsvap+116:35
* kgriffs would like to attend that security/logging thing16:35
paulmoclaytonc interested since you were involved early?16:35
claytoncpaulmo: sure cc me16:35
paulczarthere's probably a second topic in that of how much exposure to logs we'd give the customer via solum vs letting the operator solve it.  either way the context stuff is super important.16:35
*** MarkAtwood has joined #openstack-meeting-alt16:35
paulmoI think that covers the folks I know of with a vested interest in this topic.16:35
adrian_ottook, if anyone else wants to be clued in, just let me know16:36
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-zuul-integration Solum integration with Zuul (devdatta-kulkarni)16:36
paulmoYes, I think this isn't so much of a technical discussion but more of a discussion about how far Solum will cover supportability and other such areas.16:36
devkulkarnikraman will be the person to discuss about this bp :)16:36
kramanI have a hacked up POC https://github.com/kraman/zuul/compare/solum_hacks16:36
adrian_ottodevkulkarni: tx16:36
adrian_ottooh!16:37
kramanneed to run this by mordred and jeblair when they are back from vacation16:37
kramanand plan to submit patches to zuul after the discussion16:37
adrian_ottoso this is a patched zuul?16:37
kramanthe POC accepts a message over M and triggers a workflow which can handle LP build for now16:37
kramanadrian_otto: yes16:37
kramanM = message queue16:38
*** sarob has quit IRC16:38
adrian_ottothat's great news. I'm happy to hear about progress on this, thanks!16:38
kramanwe didnt have enough participants for git workflow group last week so will continue discussion in tomorrows meeting16:38
*** Barker has quit IRC16:39
adrian_ottook, good, thanks16:39
kramanthats about it16:39
adrian_ottoplease drop a reminder now to remind our team when that meeting is tomorrow16:39
kramanTomorrow's meting is at 9 AM PST in #solum. http://www.worldtimebuddy.com/?qm=1&lid=100,8,524901,2158177&h=100&date=2014-01-15&sln=17-1816:39
adrian_ottook, and the last blueprint on the agenda today:16:40
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/api-worker-architecture API service/worker architecture for async operation (murali-allada)16:40
muraliaok, so here are some updates since we met last.16:40
muralia1) the patch for the API workers framework has got two +2's and is waiting to be merged. https://review.openstack.org/#/c/62466/16:40
muraliaThe gate is currently broken, so it's not merged yet. We should talk about that during open discussion.16:40
adrian_ottonoorul: were you looking at the merge problem?16:40
* paulmo gives a big cheer to Murali! That was a decent chunk of code. :)16:41
muraliaI'd be happy to help anyone working on fixing the gate.16:41
*** SergeyLukjanov has joined #openstack-meeting-alt16:41
noorulhttps://review.openstack.org/#/c/65507/16:41
noorulThat fixes the gate16:41
noorulNeeds one more +2 and +a16:42
muraliathanks. we need another +2 for this16:42
adrian_ottook kgriffs can you look at that?16:42
muraliaok, moving on.16:42
muralia2) I've been doing some research this week to extend this framework with a DB layer. I've looked at Trove and Marconi for ideas. I've looked at old logs from the Solum Irc channel and mailing list to see if we discussed which DB to use and why, I don't think we have. So I'm working on a blueprint to open this up for discussion. I'm going with MySql so far. If everyone is ok with that, I won't bother starting a blueprint or email t16:42
paulmoJust a comment: Don't use cascading triggers with MySQL.16:43
adrian_ottowe discussed that a bit at the Solum F2F in November16:43
claytoncmysql i believe was consensus16:43
paulmoYep, MySQL + InnoDB16:44
russellbsqlalchemy?16:44
devkulkarnithat is what I am remembering too16:44
claytoncthe abstraction is there to allow a future implementor to choose  to add a non-relational store, but as long as the abstraction isn't broken we're ok16:44
claytoncyes16:44
adrian_ottoyes, using SQLalchemy, right?16:44
paulmoYes russellb16:44
claytoncsqlalchemy16:44
russellbshouldn't assume mysql only16:44
brianclineAs long as the way it's implemented still provides compatibility between MySQL/MariaDB/Percona, that seems fine16:44
russellbideally postgres will work too16:44
briancline+1 for Postgres16:44
russellbshould be fine without much extra effort16:44
claytoncobjects/sqlalchemy is the sqlalchemy abstraction to the object persistence model16:44
*** slagle has joined #openstack-meeting-alt16:44
russellbdon't waste your time with sqlite though IMO (other than perhaps for unit tests)16:44
paulmoI personally like postgres better but yeah, don't use any MySQL specific features16:44
russellbeasy enough to support both16:45
claytoncfolks making model changes there have to take into account transacitonal operations (tohse have to be wrapped in a single method call and take objects that can be transformed into a transactional save), and it also should be reviewed with an eye for live updatse16:45
russellbwith sqlalchemy that is16:45
muraliafor now I'm going to work with sqlalchemy and mysql. we can come back to defining a proper abstraction layer, the way marconi has to plug in any DB16:45
claytoncmuralia: we have that abstraction layer16:45
claytoncit's objects/sqlalchemy16:45
paulmoSQLAlchemy is that abstraction :)16:45
muraliayes, the nova object model.16:45
russellbyou don't want to use the sqlalchemy models throughout your code base16:45
muraliaand sqlalchemy16:45
flaper87marconi++16:45
russellbit's painful16:45
* flaper87 STFU16:46
claytoncrussellb: yeah the objects abstract that16:46
russellbclaytonc: +1 :)16:46
paulmoflaper87 ?16:46
claytoncalso fyi on objects/sqlalchemy you are allowed to use any method defined on the public objects16:46
claytoncbut not depend on any sqlalchemy underlying methods16:46
*** Barker has joined #openstack-meeting-alt16:46
muraliaok, should do we need an email to take this discussion further?16:46
claytoncwill -1 heavily for that as we review changes16:46
claytoncmuralia: ground rules and concept would be good16:46
muraliaor just work with mysql and sqlalchemy for now16:46
claytoncto make sure everyone understands16:46
muraliaclaytonc: sounds good16:46
adrian_ottomuralia: good idea. I want to be sure we revisit the CLI topic because we invited experts to participate16:47
kgriffsmuralia: if we are limiting solum to SQL backends, then you won't need a higher-level storage driver model like marconi has16:47
kgriffss/won't/may not16:47
claytonckgriffs: we said we'd be open to nosql but we wouldn't be doing the implementaiton ourselves16:47
adrian_ottosounds like we have enough input to make a meaningful ML discussion on this.16:47
*** rajdeep has joined #openstack-meeting-alt16:47
kgriffsclaytonc: gtk16:47
muraliagreat.16:47
paulmoI can't imagine that the Solum control plane could really feasibly use a nosql db could it?16:47
kgriffsclaytonc: that informs the architecture16:47
claytoncpaulmo: it could, just probably not worth doing16:47
kgriffswe can't couple tightly to sqlalchemy if you want to afford nosql16:47
adrian_ottook, last comments on this one?16:47
muraliaok, lastly.16:48
muralia3) I'm also working on blueprint that discusses how we should go about integrating the DB layer with the API framework. Trove and Marconi do things a little differently, so it'll be great to open this up for discussion with this blueprint.16:48
claytonckgriffs: will go over via email but we covered that mostly16:48
claytoncat the f2f16:48
kgriffscool beans16:48
muraliathats it from me.16:48
* kgriffs secretly hates email16:48
* kgriffs prefers realtime communications16:49
adrian_ottomuralia: please be sure to subscribe claytonc and me, and the others who made remarks aove as subscribers to that new BP16:49
muraliayes. will do16:49
adrian_ottotx16:49
adrian_ottoThat concludes our BP status review.16:49
adrian_otto#topic CLI Development Planning16:49
*** openstack changes topic to "CLI Development Planning (Meeting topic: Solum Team Meeting)"16:49
adrian_otto#link https://wiki.openstack.org/wiki/Solum/BreakoutMeetings#CLI_Working_Group_Series CLI working group16:49
adrian_ottothis is a new (probably short term) working group for the CLI topic16:50
adrian_ottoPlease participate in the Doodle poll to help us select good times to hold CLI specific discussions. I am open to additional suggestions for the schedule.16:50
adrian_ottoOnce enough input has been supplied by CLI stakeholders, I will close the poll and publish the meeting schedule to by published on our wiki at the link provided above.16:50
adrian_otto#link https://wiki.openstack.org/wiki/Solum/CLI CLI Wiki Page16:50
adrian_ottoPlease review this with links to relevant materials and a statement of our intended development approach.16:50
*** beekneemech is now known as bnemec16:50
paulmoAll 8-10 PM times?16:50
*** aignatov has joined #openstack-meeting-alt16:50
*** ashaikh has joined #openstack-meeting-alt16:50
*** _ruhe is now known as ruhe16:51
*** ativelkov has joined #openstack-meeting-alt16:51
*** sergmelikyan has joined #openstack-meeting-alt16:51
adrian_ottoI did that initially to accommodate noorul, but he expects to be out of the office16:51
paulmoAh, thought the AM and PM flipped, sorry :)16:51
adrian_ottoso we could move that to an earlier timeslot, particularly if we have no attendees from AUS16:51
adrian_ottoAUS = Australia16:51
rajdeepi was planning to attend from india if time is not too odd16:52
adrian_ottook, so you are welcome to make comments on the Doodle poll about the scheduling, and I will incorporate your input16:52
adrian_ottothoughts on the wiki page?16:52
rajdeepthankss16:52
devkulkarni+1 to rajdeep's suggestion.16:52
adrian_ottoAre we all happy with this, or should it be revisited?16:53
adrian_ottobasically we are suggesting that we have an approach for each of the CLI blueprints referenced16:53
paulmoI like it :)16:54
adrian_ottoone that's for a minimal prototype that helps us clear the M1 milestone ASAP16:54
kgriffslooks good to me16:54
adrian_ottoand another that gets us a CLI that we will own long term16:54
paulmonoorul: Are you good with this direction?16:54
adrian_ottothat's consistent with the state of the art for OpenStack and fits well16:54
kgriffsI think the prototype thing can also act as a source for feedback into improving OSC16:54
noorulI have no issues16:54
kgriffswhen we migrate over to OSC stuff we may discover gaps or whatever that dtroyer can use to improve OSC16:55
paulmoAnd here it is, passing pep8 finally: https://review.openstack.org/#/c/66617/16:55
kgriffsanyway, just my $0.0216:55
paulmoApp/assembly create and delete are in there16:55
adrian_ottopaulmo: thanks for grinding through that!16:55
*** shau7246 has quit IRC16:55
paulmoOnce I get some comments on that, I'll make it non-WIP16:56
adrian_ottook, sounds like we have no controversy to resolve, awesome16:56
devkulkarniseems like a good plan16:56
paulmoYay!16:56
adrian_otto#topic Open Discussion16:56
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:56
paulmoJust an announcement:16:57
dtroyerFWIW I think that is a workable plan.  I would suggest keeping https://wiki.openstack.org/wiki/OpenStackClient/HumanInterfaceGuidelines#Command_Structure in mind when structuring your commands…16:57
paulmoThe OpenStack Security Group accepted our Solum security guidelines and are adopting them to promote across all projects: https://wiki.openstack.org/wiki/Security/Guidelines16:57
noorulpaulmo: Congrats!16:57
adrian_otto#agreed to proceed with both a prototype and long term CLI, as described in 2014-01-13 revision of https://wiki.openstack.org/wiki/Solum/CLI16:57
adrian_ottopaulmo: WHOOT16:58
kramanAre we planning another F2F?16:58
adrian_ottokraman: currently we are not, but that's a good idea to consider16:58
paulmoIsn't there an OpenStack meeting in Atlanta coming up soon?16:59
adrian_ottopaulmo: that's in April16:59
adrian_ottokraman is aking about something between now and then16:59
adrian_ottoasking16:59
paulmoAh, forgot it was so far out :)16:59
*** tsufiev_ has joined #openstack-meeting-alt16:59
adrian_ottoin November we got a ton of value from our F2F meeting. Several attendees mentioned they felt it was more productive than our time at OSC in HKG.17:00
dtroyerNext Design Summit is May 12-1617:00
adrian_ottobecause we can focus just on Solum topics17:00
adrian_ottodtroyer: tx! sorry for the misinformation!17:01
*** esker has quit IRC17:01
dtroyerit has been april until now…threw me too17:01
* paulmo notes that Austin is 70F right now and pretty central. :)17:01
devkulkarniadrian_otto: is that right? then f2f will be useful again as well17:01
*** esker has joined #openstack-meeting-alt17:01
*** amitgandhi has left #openstack-meeting-alt17:01
adrian_ottoI am sure that Rackspace is willing to host the event again if you wanted a Texas venue17:02
*** aignatov has quit IRC17:02
adrian_ottoit might be nice to think about rotating the host role too17:02
*** tnurlygayanov_ has joined #openstack-meeting-alt17:02
katyaferventHi everyone17:02
adrian_otto#endmeeting17:02
tnurlygayanov_Hi )17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Tue Jan 14 17:02:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-14-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-14-16.00.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-01-14-16.00.log.html17:02
adrian_ottosorry for the time runover guys17:02
*** paulczar has left #openstack-meeting-alt17:03
tnurlygayanov_no problem.17:03
*** paulmo has left #openstack-meeting-alt17:03
ativelkov#startmeeting Murano17:03
openstackMeeting started Tue Jan 14 17:03:34 2014 UTC and is due to finish in 60 minutes.  The chair is ativelkov. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: Murano)"17:03
openstackThe meeting name has been set to 'murano'17:03
*** noorul has left #openstack-meeting-alt17:03
*** devkulkarni has left #openstack-meeting-alt17:03
tsufiev_hi there17:03
ativelkovHi Muranoers!17:03
*** claytonc has left #openstack-meeting-alt17:03
*** muralia has left #openstack-meeting-alt17:03
tnurlygayanov_Hi ))17:03
*** adrian_otto has left #openstack-meeting-alt17:04
IgorYozhikovHi17:04
*** dtroyer has left #openstack-meeting-alt17:04
ativelkovSeems like this is our first meeting ater NY holidays17:04
ativelkovI hope you all had a good vacation17:04
ativelkovThis is our agenda for today: https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Next_meetings17:05
*** sarob has joined #openstack-meeting-alt17:05
ativelkovLet's start with the AI review17:05
ativelkov#topic AI review17:06
*** openstack changes topic to "AI review (Meeting topic: Murano)"17:06
*** esker has quit IRC17:06
ativelkovFirst item was "update https://wiki.openstack.org/wiki/Murano/Roadmap for 3.0 and 4.0"17:06
*** akuznetsov has quit IRC17:06
*** mspreitz has quit IRC17:06
ativelkovDo I understand correctly that this was done?17:06
tsufiev_this was on me, done17:07
ativelkovGood, thanks17:07
*** le089 has quit IRC17:07
ativelkov#info roadmap for 0.3 and 0.4 was updated17:07
*** ruhe is now known as ruhe_away17:07
ativelkovnext one, tsufiev make sure that 0.4 known issues are marked with 0.4.1 milestone17:07
tsufiev_again, done, but not all the known issues of 0.4 are planned for 0.4.117:08
*** bdpayne has joined #openstack-meeting-alt17:08
katyaferventI guess wee did it ob our bug triage17:08
katyafervent* we17:08
ativelkovtsufiev_: why are not they?17:08
*** kgriffs has left #openstack-meeting-alt17:08
ativelkovSome has to be fixed only in 0.5?17:09
tsufiev_because as tnurlygayanov said, we don't have time to setup lab for Neutron in 0.4.117:09
tnurlygayanov_or 0.5+17:09
tnurlygayanov_yes, I will try to do this on this week.17:10
ativelkovThis is important17:10
ativelkov0.5 is not a proper release for bugfixing17:10
katyaferventDo we have list of known issues in our openstack wiki page?17:10
ativelkovit will introduce completely new functionality, and even some of the features will be missing17:10
*** gokrokve_ has quit IRC17:11
ativelkovso all the fixes for 0.4.* have to be done in 0.4.*17:11
*** joel_c1 has joined #openstack-meeting-alt17:11
*** gokrokve has joined #openstack-meeting-alt17:11
*** bdpayne has quit IRC17:11
tsufiev_katyafervent: yes, we have17:11
ativelkovif if don't do somthing important in 0.4.1 it means that we will have to do 0.4.217:11
tnurlygayanov_https://wiki.openstack.org/wiki/Murano/ReleaseNotes_v0.4#Known issues17:11
ativelkovor - as another option - we may postpone 0.4.1 a bit, to have more time for neutron testing17:12
*** rakhmerov has joined #openstack-meeting-alt17:12
ativelkovtnurlygayanov_: what are your estimates: how much time may we need to setup lab and fix them?17:13
*** mozawa has quit IRC17:13
tnurlygayanov_I belive that we will have time for testing with Neutron load balancer before the end of Jun17:13
katyaferventand why do we need fuel for that?17:13
ativelkovJun??17:13
tsufiev_tnurlygayanov_: June :)?17:13
tnurlygayanov_it is one-two days17:14
ativelkovJan, I hope )17:14
tnurlygayanov_yes, sorry, Jan )17:14
*** michael-yu has joined #openstack-meeting-alt17:14
ativelkovIs this Neutron LB a separate module, which does not come installed with MOS?17:15
tnurlygayanov_katyafervent, we do not need fuel for it17:15
katyaferventtnurlygayanov, ok)17:15
tnurlygayanov_yes17:15
tnurlygayanov_we can install and configure it with devstack and I plan to do this in our QA lab17:16
sergmelikyanativelkov, Neutron LB may be installed separatly and joined with MOS installed via Fuel17:16
*** cp16net has quit IRC17:16
*** gokrokve has quit IRC17:16
ativelkovOk, but for distribution we will need to either add its support to Fuel or to have a separate deploymnet routine for it17:16
ativelkovI see17:17
tnurlygayanov_today we finished murano installation script, which allow to install Murano using the devstack - I plan to test Neutron LB and this script in parallel.17:17
*** ruhe_away is now known as _ruhe17:17
katyaferventbut we are working on devstack integration, right? could it helped with this issue?17:17
katyaferventOh, cool17:17
ativelkovSo, let's then plan to add Neutron LB support into the 0.4.1 - postponing the release if nessesary17:17
tnurlygayanov_yes, need to add this LB in Fuel installation17:18
ativelkovAny objections on this?17:18
katyaferventok, I'll add it to 0.4.1 deliverables17:18
tnurlygayanov_ativelkov, ok17:18
*** akuznetsov has joined #openstack-meeting-alt17:18
*** aratim has left #openstack-meeting-alt17:18
sergmelikyanWhat integration we are talking about?17:18
ativelkov#agreed add Neutron LB support into the 0.4.1 - postponing the release if necessary17:19
sergmelikyanIntegration Neutron LBaaS to MOS? How it is related to Murano?17:19
ativelkovIt is a different topic indeed17:19
tnurlygayanov_sergmelikyan, it is for another meeting )17:20
ativelkovlet's continues with the AIs17:20
ativelkov"consider possibility to provide the way to share environments across BUs without involving admins"17:20
*** rajdeep has quit IRC17:20
ativelkovI guess this is irrelevant now, as we have changed the suggested implementation for per-tenant isolation, right?17:21
tsufiev_it was the thing that our unidentified guest on the previous meeting wanted17:21
ativelkovWas that about environments or about service definitions?17:22
tsufiev_wait a minute....17:22
tsufiev_i don't remember, need to see logs17:22
tnurlygayanov_yes, in 0.4.11 we can just make per tenant isolation, but for 0.5 need to support RBAC.17:23
tnurlygayanov_*0.4.117:23
katyaferventdo we have time for it in 0.5?17:24
tsufiev_<tsufiev> we decided that there should be 'Common' Services&Metadata objects + per-tenant Services and objects17:24
tsufiev_<tsufiev> Common one should be read-only via WebUI, but can be changed via file-system17:24
ativelkovIt depends on how do we implement metadata storagde17:24
tsufiev_<tsufiev> per-tenant ones are modifiable by any user of that tenant17:24
tsufiev_ <Guest36589> this is instead of enabling ownership of the object by a tenant with a sharing attribute?17:24
tsufiev_<Guest36589> post .6 i hope this can be reconsidered.  We have many BUs that will innovate and want to share with related BUs with having to have the provider IT involved.17:25
ativelkovAh, I see17:25
ativelkovWe have plans for this17:25
ativelkovIf we use Glance for storing artifact, we may use the same system for sharing artifacts which is currently present for sharing images17:25
ativelkovbut for 0.4.1 this will not be possible17:26
*** boris-42 has joined #openstack-meeting-alt17:26
ativelkovimplementation for 0.5 is tentative - depends on the glance arttifacts repo implementation and our adoption of it17:26
ativelkovBut this is planned anyway17:26
ativelkovAre we done with AIs?17:27
katyaferventativelkov, I guess so17:27
ativelkovThen lets move on17:27
ativelkov#topic Status for release 0.4.1 features17:28
*** openstack changes topic to "Status for release 0.4.1 features (Meeting topic: Murano)"17:28
*** psumkin has left #openstack-meeting-alt17:28
katyaferventRelease 0.4.1 is on it's way, wiki page is up to date with information about it17:28
*** dim_ has joined #openstack-meeting-alt17:28
ativelkovWill 0.4.1 contain the devstack integration which we have discussed above?17:28
katyaferventSo we do have two main features: per-tenant isolation and managing key-pairs17:29
katyaferventAlso we'll improve dynamic UI - it should be work faster17:29
tsufiev_(but if we use OS Lab on the opposite side of the world, you won't notice that)17:30
tsufiev_:)17:30
*** sankarshan has joined #openstack-meeting-alt17:30
katyaferventYes, and it's almost done afaik17:30
ativelkovI see17:30
ativelkovgood, thanks17:30
ativelkovmoving on17:31
*** sankarshan is now known as sankarshan_away17:31
ativelkov#topic Changes in per-tenant isolation17:31
*** openstack changes topic to "Changes in per-tenant isolation (Meeting topic: Murano)"17:31
ativelkovSo, since out last meeting there it was decided to change the proposed implementation of per-tenant isolation17:31
tsufiev_yes, and it simplifies an implementation very much17:32
ativelkovThere will be no managable "common" repository, instead, commons will be "forked" at the moment when the tenant uses Murano for the first time17:32
ativelkovkatyafervent - is the new approach documented on wiki somewhere?17:33
katyaferventativelkov, Yes, the specification was updated17:33
*** shau7246_ has joined #openstack-meeting-alt17:33
katyaferventhttps://wiki.openstack.org/wiki/Murano/Specifications/Per_Tenant_Isolation17:33
ativelkovThanks17:34
ativelkov#info new approach to per-tenant isolation is documented at https://wiki.openstack.org/wiki/Murano/Specifications/Per_Tenant_Isolation17:34
ativelkov#topic New DSL engine17:35
*** openstack changes topic to "New DSL engine (Meeting topic: Murano)"17:35
*** stanlagun has joined #openstack-meeting-alt17:35
ativelkovSo, speaking about new DSL engine - stanlagun, can you share the update?17:35
*** bdpayne has joined #openstack-meeting-alt17:36
*** bdpayne has quit IRC17:36
*** kraman has left #openstack-meeting-alt17:37
ativelkovstanlagun, are you here?17:37
stanlagunthere is a prototype that has nearly everything that is required for 0.5 with exclusion of correct YAQL function registration. I'm going to make if complete today and commit to custom repository so that it can be used as a code base17:37
ativelkovah, thanks17:37
stanlagunI also expect to have demo service (AD) on new DSL17:38
stanlagunby tomorrow17:38
ativelkov#info new DSL proptotype is almost ready, will include an engine PoS and a demo service17:38
ativelkov#action stanlagun to submit the sources to a custom repo17:38
ativelkovThanks17:38
rakhmerovguys, sorry if that's a dummy question.. Do you have this new DSL documented somewhere?17:38
rakhmerovI'm curious to take a look17:38
ativelkovrakhmerov: yes, there is a blueprint and etherpad17:38
stanlagunit is slightly outdated17:39
rakhmerovcould you please provide links?17:39
stanlagunI'm going to write more detailed and up-to-date description as soon as I finish with PoC17:39
rakhmerovok17:40
stanlagunhttps://etherpad.openstack.org/p/MuranoMetadata17:40
rakhmerovok, thanks17:40
ativelkovso, the spec will be updated during this week, right?17:41
ativelkov#action stanlagun to update the DSL description according to the implemented PoC17:41
ativelkovAnd then we will have a meeting with Dmitry Meytin to demostrate the proptotype to him and discuss the contribution possibilities17:42
ativelkov#action ativelkov to schedule a meeting with Dmitry17:42
*** yjiang5_1 is now known as yjiang517:42
ativelkovThat is all on DSL17:43
ativelkov#topic Open Discussion17:43
*** openstack changes topic to "Open Discussion (Meeting topic: Murano)"17:43
ativelkovDoes anybody has something unplanned to discuss?17:44
katyaferventI have not17:44
IgorYozhikovnope17:45
ativelkovWell, then I think we are done17:45
ativelkovThanks for joining17:45
katyaferventThanks everyone!17:45
ativelkov#endmeeting17:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:45
openstackMeeting ended Tue Jan 14 17:45:24 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-01-14-17.03.html17:45
* IgorYozhikov is now away: went away...17:45
*** IgorYozhikov is now known as IYozhikov_away17:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-01-14-17.03.txt17:45
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-01-14-17.03.log.html17:45
*** joel_c1 has left #openstack-meeting-alt17:45
*** akuznetsov has quit IRC17:46
*** NikitaKonovalov has joined #openstack-meeting-alt17:47
*** shau7246_ has quit IRC17:48
*** akuznetsov has joined #openstack-meeting-alt17:49
*** michael-yu has quit IRC17:49
*** akuznetsov has quit IRC17:50
*** NikitaKonovalov has quit IRC17:51
*** NikitaKonovalov has joined #openstack-meeting-alt17:52
*** jcoufal-m has joined #openstack-meeting-alt17:53
*** derekh has quit IRC17:54
*** yisun has joined #openstack-meeting-alt17:56
*** NikitaKonovalov has quit IRC17:57
*** NikitaKonovalov has joined #openstack-meeting-alt17:57
*** tsufiev_ has quit IRC17:59
*** arnaud__ has joined #openstack-meeting-alt18:00
*** arnaud has joined #openstack-meeting-alt18:00
pballandhi18:00
*** NikitaKonovalov has quit IRC18:01
*** thinrichs has joined #openstack-meeting-alt18:02
thinrichsHi--sorry I'm late.18:02
*** stanlagun has left #openstack-meeting-alt18:02
pballandnp - you and I again18:02
pballand#startmeeting CongressTeamMeeting18:02
openstackMeeting started Tue Jan 14 18:02:57 2014 UTC and is due to finish in 60 minutes.  The chair is pballand. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"18:03
openstackThe meeting name has been set to 'congressteammeeting'18:03
*** harlowja_away is now known as harlowja18:03
pballand#link https://wiki.openstack.org/wiki/Meetings/Congress18:03
pballandagenda is short18:03
pballandwe've started a google doc for design discussions18:04
pballand#link http://goo.gl/Ib4ujX18:04
pballandother updates: we are now pushing code through stack forge18:04
*** amcrn has joined #openstack-meeting-alt18:05
thinrichsGreat!18:05
pballandI am in the process of getting unit tests running there18:05
thinrichsGood deal18:05
pballandone next step is to fill in details on the design18:05
*** gokrokve has joined #openstack-meeting-alt18:06
pballandwe currently only have stubs for the service abstractions, language, and enforcement sections18:07
pballandare you available to work on any of those?18:07
*** NikitaKonovalov has joined #openstack-meeting-alt18:07
thinrichsSure.  I could work on the Policy Language18:07
pballandok, from the design doc perspective, I can work on the service abstraction parts18:07
*** BrianB_ has quit IRC18:08
thinrichsDepending on my free cycles, I could also work on Policy Enforcement.18:08
pballandperfect18:08
pballand#action thinrichs will work on Policy Language and Policy Enfocement sections of design doc18:08
pballand#action pballand will work on service abstraction sections of design doc18:08
pballandfor now, small comments/questions can be handled in the doc18:09
*** jcoufal has joined #openstack-meeting-alt18:09
*** NikitaKonovalov has quit IRC18:10
pballandanything big (or controversial) should be done in a meeting or in the mailing list18:10
pballand#topic open discussion18:10
*** openstack changes topic to "open discussion (Meeting topic: CongressTeamMeeting)"18:10
pballandanything to discuss?18:10
thinrichsNot right now--I'm starting to free up some cycles and will hope to have more to say in upcoming weeks.18:11
*** yogesh has joined #openstack-meeting-alt18:11
pballandsounds good18:11
thinrichsYep.18:12
pballandthanks for coming18:12
pballand#endmeeting18:12
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:12
openstackMeeting ended Tue Jan 14 18:12:13 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:12
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-01-14-18.02.html18:12
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-01-14-18.02.txt18:12
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-01-14-18.02.log.html18:12
*** nadya_ has joined #openstack-meeting-alt18:14
*** NikitaKonovalov has joined #openstack-meeting-alt18:15
*** thinrichs has quit IRC18:16
*** amytron has quit IRC18:17
*** tnurlygayanov_ has quit IRC18:20
*** cloudpie has joined #openstack-meeting-alt18:21
*** michael-yu has joined #openstack-meeting-alt18:24
*** cloudpie has quit IRC18:24
*** esker has joined #openstack-meeting-alt18:25
*** cloudpie has joined #openstack-meeting-alt18:25
*** NikitaKonovalov has quit IRC18:28
*** _ruhe is now known as ruhe18:30
*** NikitaKonovalov has joined #openstack-meeting-alt18:33
*** vipul is now known as vipul-away18:35
*** krtaylor has quit IRC18:36
*** cloudpie has quit IRC18:36
*** nam_nguyen has joined #openstack-meeting-alt18:37
*** NikitaKonovalov has quit IRC18:37
*** NikitaKonovalov has joined #openstack-meeting-alt18:38
*** krtaylor has joined #openstack-meeting-alt18:39
*** beyounn has joined #openstack-meeting-alt18:41
*** SushilKM has joined #openstack-meeting-alt18:41
*** IlyaE has quit IRC18:41
*** SushilKM has left #openstack-meeting-alt18:41
*** SushilKM has joined #openstack-meeting-alt18:41
*** SushilKM has left #openstack-meeting-alt18:41
*** beyounn has quit IRC18:43
*** morazi has joined #openstack-meeting-alt18:44
*** amytron has joined #openstack-meeting-alt18:45
*** lsmola has joined #openstack-meeting-alt18:47
*** NikitaKonovalov has quit IRC18:47
*** matty_dubs has joined #openstack-meeting-alt18:49
*** jcoufal-m has quit IRC18:51
*** NikitaKonovalov has joined #openstack-meeting-alt18:52
*** vipul-away is now known as vipul18:53
*** beyounn has joined #openstack-meeting-alt18:54
*** dim_ has quit IRC18:54
*** rnirmal has joined #openstack-meeting-alt18:55
*** rnirmal_ has joined #openstack-meeting-alt18:57
*** rnirmal_ has quit IRC18:57
*** rnirmal_ has joined #openstack-meeting-alt18:57
*** NikitaKonovalov has quit IRC18:57
*** jprovazn has joined #openstack-meeting-alt18:57
*** rnirmal_ has quit IRC18:57
*** rnirmal_ has joined #openstack-meeting-alt18:57
*** SergeyLukjanov has quit IRC18:58
*** NikitaKonovalov has joined #openstack-meeting-alt18:58
*** rpodolyaka1 has joined #openstack-meeting-alt18:58
*** rlandy has joined #openstack-meeting-alt18:58
*** jamezpolley has joined #openstack-meeting-alt18:59
*** SergeyLukjanov_ has joined #openstack-meeting-alt18:59
lifelessmorning everyone18:59
dprincehello18:59
rpodolyaka1o/18:59
marios\o18:59
*** rnirmal has quit IRC18:59
*** rnirmal_ is now known as rnirmal18:59
lsmolahello18:59
matty_dubso/18:59
shadowerhey19:00
*** jistr has joined #openstack-meeting-alt19:00
jprovaznhi19:00
lifeless#startmeeting tripleo19:00
jistrhi19:00
openstackMeeting started Tue Jan 14 19:00:55 2014 UTC and is due to finish in 60 minutes.  The chair is lifeless. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: tripleo)"19:00
ifarkaso/19:00
openstackThe meeting name has been set to 'tripleo'19:01
slaglehello19:01
jtomasekhey19:01
lifeless#topic agenda19: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
SpamapSo/19:02
lifelesswe have some untriaged bugs in tripleo19:02
lifelessand a bunch of criticals19:02
lifelessdib has many untriaged bugs19:02
*** pblaho has joined #openstack-meeting-alt19:03
*** SergeyLukjanov_ has quit IRC19:03
slaglei'll handle https://bugs.launchpad.net/diskimage-builder/+bug/1263902 as i already fixed it19:03
SpamapSlifeless: I wonder if we could get reviewday to show untriaged bugs mixed in with reviews.19:03
slagledidn't know there was a bug for it :/19:03
lifelessso we had the commitment from everyone to do a little triage one day a week19:03
*** NikitaKonovalov has quit IRC19:03
*** SergeyLukjanov has joined #openstack-meeting-alt19:03
pleia2SpamapS: there is also bugday, which might be worth a look19:04
pleia2SpamapS: right now it's just graphs, but can probably be modified19:04
SpamapSpleia2: moar placesss19:04
lifelesslooking at the dates, clearly that isn't happening (holidays notwithstanding)19:04
SpamapSI just discovered I was not subscribed to diskimage-builder19:04
SpamapSI tend to use my email for bug triage19:04
*** rbrady has joined #openstack-meeting-alt19:04
*** beyounn has quit IRC19:05
*** krtaylor has quit IRC19:05
lifelessI'll do a pass this evening, make sure we'll all triaged; shall we recommit to each do triage no less than once a week ?19:05
lifelesswith 20 odd folk thats /more/ than sufficient19:05
SpamapSlifeless: is https://bugs.launchpad.net/tripleo/+bug/1266800 still an issue (boot-seed-vm failing) ?19:06
slagleprocess question: can we triage our own bugs?19:06
SpamapSslagle: yes19:06
lifelessslagle: yes19:06
slaglethen i'll triage the 2 i filed :)19:06
*** e0ne has joined #openstack-meeting-alt19:06
lifelessslagle: you should never file a bug untriaged if you have access to set the right bits19:06
slagleack19:06
*** ccrouch has joined #openstack-meeting-alt19:07
*** MarkAtwood has quit IRC19:07
*** demorris has quit IRC19:07
lifelessSpamapS: I fstrimmed and the issue hasn't reoccured19:08
*** aignatov has joined #openstack-meeting-alt19:09
*** beyounn has joined #openstack-meeting-alt19:09
*** NikitaKonovalov has joined #openstack-meeting-alt19:10
SpamapS1265807 is a duplicate of 126651319:10
SpamapScan somebody confirm that?19:10
*** tzumainn has joined #openstack-meeting-alt19:10
rpodolyaka1seems so19:11
jprovaznSpamapS, yes19:11
SpamapSok will mark as such19:11
lifelessyep19:11
lifelessSpamapS: I don't tink 1261253 is critical; there is a workaround19:12
lifelessSpamapS: and the default setup doesn't use a mirror19:13
SpamapSlifeless: agreed, High is more appropriate. Changing.19:13
lifelesshttps://bugs.launchpad.net/tripleo/+bug/1254555 is fixreleased from out perspective I think19:14
lifelessisn't it?19:14
*** NikitaKonovalov has quit IRC19:14
SpamapSlifeless: IIRC we are just working around it with lots of retries19:14
lifelesshmm, see comment 719:15
SpamapSlifeless: we can maybe lower it to High as well since it is worked around.19:15
lifelessneutron reckon it shouldn't be presenting symptoms any more19:15
SpamapSlifeless: I think that is sort of "the problem" with race conditions.. work around them and people think they go away. :(19:15
lifelessso, we should take the bandaid off, if the problem is gone, great, if not we should ask neutron to re-prioritise it19:16
rpodolyaka1+119:16
*** e0ne_ has joined #openstack-meeting-alt19:16
lifelesshttps://bugs.launchpad.net/tripleo/+bug/1254246 looks like it's stuck in review19:17
rpodolyaka1so it's actually kind of fixed for us19:17
rpodolyaka1due to how we do db-sync in neutron19:17
rpodolyaka1but to be 'fully fixed' that patch must be merged19:17
lifelessrpodolyaka1: ok. devananda hit it yesterday, but I don't know how old his seed was19:18
rpodolyaka1lifeless: hmm, should be fixed for a while now19:18
lifelessrpodolyaka1: his seed might be quite old :)19:18
rpodolyaka1I think so19:18
lifelessok, so lets FR it19:19
SpamapSsounds like it needs somebody to reconfirm and adjust status appropriately19:19
lifelessfor tripleo19:19
lifelessI certainly haven't seen it19:19
*** NikitaKonovalov has joined #openstack-meeting-alt19:19
lifelessand I've been doing lots of fresh builds recently19:19
lifelessok so19:20
lifelessany more bug discussion?19:20
dprincelifeless: real quick19:21
dprincehttps://bugs.launchpad.net/diskimage-builder/+bug/123948019:21
dprincelifeless: is truncating /etc/network/interfaces an option there?19:22
dprincelifeless: I just messed w/ dhcp-all-interfaces and am happy to clean triage on its bugs... but need clarification on that one issue19:22
lifelessdprince: good question19:22
dprincelifeless: you can look at it later too, just thought it worth a mention.19:23
lifelessdprince: I think truncating is probably a bad idea, because unlike fedora its all munged into one file19:23
lifelessdprince: editing 'auto eth0' out would be more surgical19:23
SpamapSlifeless: I just made a debian cloud image and I just didn't even bother to make /etc/network/interfaces .. I just used dhcp-interfaces-all19:23
lifelessI'm thinking about folk with bridges or vpns defined19:23
dprincelifeless: yeah. well then its going to have to be sliced out then :(19:23
SpamapSor dhcp-all-interfaces.. :)19:24
lifeless#topic reviews19:24
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:24
lifelesshttp://russellbryant.net/openstack-stats/tripleo-openreviews.html19:24
mariosdown for me all day ^^19:24
lifelessok, guess we're skipping it :)19:25
lifeless#topic  Projects needing releases19:25
*** openstack changes topic to "Projects needing releases (Meeting topic: tripleo)"19:25
*** obondarev_ has joined #openstack-meeting-alt19:25
lifelessDo we have a volunteer ?19:25
SpamapShttp://webcache.googleusercontent.com/search?q=cache:7IE9twHe6I8J:russellbryant.net/openstack-stats/tripleo-openreviews.html+&cd=1&hl=en&ct=clnk&gl=us&client=ubuntu19:26
SpamapScached version19:26
SpamapSdoh19:26
SpamapSJan 819:26
SpamapScome on google.. that thing changes every hour at least :)19:26
lifelesshe might have moved it to an infra host19:26
lifelesswill follow up out of band19:26
lifelessrussellb: ^19:26
lifelessrpodolyaka1: are you up for doing releases?19:26
rpodolyaka1sure:)19:26
lifelesscool19:27
lifeless#topic CD Cloud status19:27
*** openstack changes topic to "CD Cloud status (Meeting topic: tripleo)"19:27
lifelessdprince: hows the RH region coming along?19:27
dprincelifeless: still pushing to get a set of IPv4 IPs.19:28
dprincelifeless: and to get everyone public access19:28
lifelessdprince: ok. No IPv6 either?19:28
dprincelifeless: internally I have access now and I've got my seed, undercloud, overcloud running now.19:29
russellbit hasn't moved to infra, it's just down19:29
dprincelifeless: mostly just testing the water, etc to work the kinks out ahead of time.19:29
russellbit's hosted by "random friend hosting inc"19:29
dprincelifeless: IPv6 is going to be harder than getting IPv4 I think. At least in our current datacenter.19:29
dprincelifeless: so progress, and I'm pushing on it as much as I can....19:30
lifelessdprince: so I had an idea on IPv619:30
lifelessdprince: if we get one ipv4 address19:30
SpamapSFor our CD cloud, we're experiencing some weirdness on the undercloud box regarding networking.19:30
lifelessdprince: we can get a IPv6 subnet from HE19:30
dprincelifeless: what is HE?19:30
*** ruhe is now known as ruhe_away19:30
lifelesshurricane electric19:30
SpamapStunnel ftw19:31
dprinceah, that. Sure. We could go that route I suppose.19:31
dprinceIf that works, and allows us to hook it up to infra I'm fine w/ it.19:31
lifelessok, so HP region19:31
lifelessSpamapS: thoroughly weirdness19:32
*** IlyaE has joined #openstack-meeting-alt19:32
dprinceI'm still going for a set of IPv4 address, if it ends up being a small set then perhaps the tunneling is a good option.19:32
dprinceSpamapS: is this another mellanox driver thing?19:32
*** ruhe_away is now known as ruhe19:33
*** NikitaKonovalov has quit IRC19:34
SpamapSdprince: no19:34
SpamapSdprince: I bumped it earlier today and it had no effect19:34
SpamapSone thing.. perhaps the box is being DoS'd or used as a reflector. It has basically no firewall.19:35
lifelessSpamapS: nope19:36
*** e0ne_ has quit IRC19:36
lifelessSpamapS: 1.5kb of traffic on the public itnerface19:37
SpamapSlifeless: its also healthy right now19:37
lifelessSpamapS: not really19:37
SpamapSlifeless: we should probably graph traffic19:37
lifelesswe should implement the monitoring we've been mubmling about19:37
SpamapSlifeless: it is screaming fast for me now.. much better than it has been the last 4 hours19:38
SpamapSyeah19:38
lifelessok so19:38
lifelesswas the bastion ill too ?19:38
lifelessor other ips?19:38
*** NikitaKonovalov has joined #openstack-meeting-alt19:38
*** nadya_ has quit IRC19:39
lifelessso, lets look at tht out of the meeting19:39
lifelessI've spun up a new cloud19:40
lifelessci-overcloud.tripleo.org19:40
lifelessthe intent is to use this for jenkins slaves19:40
lifelessand the broker19:40
lifelessit has a new baremetal network 192.168.1.0 for the test traffic to be on19:40
lifelessand ssl courtesy of ng19:40
SpamapSwoo19:41
lifelesslike the poc, this will be static - as soon as we have nodowntime deploys of the cd-overcloud we can ditch it19:41
lifelessit has one compute node19:41
lifelessso the intent (if it's not obvious) is that it won't have a lot of load on it ever19:41
lifelesswith the state everythings in I hope we can be in the silent queue next week19:43
SpamapSwooot19:44
lifeless#topic CI virtualized testing progress19:44
*** openstack changes topic to "CI virtualized testing progress (Meeting topic: tripleo)"19:44
lifelesspleia2: / dprince: ^19:45
pleia2I don't have updates myself, but I would like to do a sync up call with dprince and derekh soon (tomorrow?)19:45
*** krtaylor has joined #openstack-meeting-alt19:45
dprinceYes. It is time for a sync up. I'll send out an invite here shortly for tommorow19:45
pleia2dprince: great, thanks19:46
lifeless#topic open discussion19:46
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:46
*** NikitaKonovalov has quit IRC19:46
*** hub_cap has joined #openstack-meeting-alt19:46
SpamapSI just wanted to bring up that I could use help working on Heat for TripleO purposes.19:46
dprinceSpamapS: what specifically needs helping with?19:47
SpamapSWe're going to want to start using resource/server groups, and rolling updates.. and retry updates.. and...19:47
lifelesswe finished migrating stuff to /mnt/state as far as we know right?19:47
SpamapSdprince: hot-software-config is a blueprint that we need to clean up the templates and make them not rely on merge.py19:47
dprincelifeless: BTW. I reviewed most of the use_ephemeral Nova branches today. I think those are all very close to being able to land. The last branch in the series needs a little fixup though...19:47
SpamapSlifeless: not /etc19:48
SpamapSlifeless: we're at a state where we survive rebuild19:48
SpamapSlifeless: but readonly / is still a lot of patches away19:48
dprincelifeless: I haven't tested a read only image on Fedora yet19:48
lifelessSpamapS: ok19:48
lifelessdprince: see SpamapS ^ we're not expecting ro to work [yet]19:48
dprincelifeless: I'd say we have a good bit of work on our side yet.19:48
dprincelifeless: right.19:48
lifelessdprince: for anyone ;)19:48
SpamapSlifeless: it works because os-collect-config re-asserts all the state again.19:48
lifelesswhich is ok, the first goal was /mnt state preservation19:48
lifelessreadonly / isn't immediate19:49
*** nadya_ has joined #openstack-meeting-alt19:49
SpamapSalso rabbit does not perserve state across rebuild19:49
SpamapSpreserve19:50
dprinceSpamapS: So if I work on the hot-software-config does that mean I get to say I'm a hot developer?19:50
* dprince jokes19:50
slaglei may have some cycles soon'ish to look at Heat related stuff19:50
SpamapSdprince: you already say that, but now we might not roll our eyes :)19:50
lifelessboom-tish19:51
dprinceI'll say boom to that19:51
slaglewhere's a good place to start? just getting familiar with hot-software-config?19:51
* dprince BOOM19:51
SpamapSanyway, just suggesting that I think our Heat usage has suffered and is the ugliest part of TripleO IMO.19:51
*** NikitaKonovalov has joined #openstack-meeting-alt19:51
SpamapSslagle: getting familiar with running heat beyond 'stack-create' will help.19:51
*** vipul is now known as vipul-away19:52
*** vipul-away is now known as vipul19:52
slaglei stack-delete a lot too19:52
SpamapSstack-update is where the trouble starts19:52
slagleok :)19:52
*** alazarev has joined #openstack-meeting-alt19:53
SpamapSI will start tagging Heat bugs with tripleo if I see things that would be good for all of us to track19:54
SpamapSthat is all.19:54
ccrouchslagle: SpamapS: i was talking to sdake about  https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config yesterday19:54
ccrouchhe expects it to land by milestone 319:55
lsmolaSpamapS, great19:55
*** pballand has quit IRC19:55
SpamapSYeah if we all got out and pushed on it, we could, in parallel, switch TripleO to using it and thus improve Heat at the same time we improve TripleO.19:55
ccrouchso i dont know if we can help move that along, or just make sure that what will land will be sufficient for us to get rid of merge.py19:55
SpamapSccrouch: last I checked stevebaker had made a call for volunteers on a few pieces19:56
*** nadya_ has quit IRC19:56
ccrouchok cool19:56
dprinceSpamapS: when we do this I would also like to refactor things to support an all-in-one overcloud as well.19:56
lifelessis everyone tracking trello still ? Sounds like hot should be in there19:56
slagledprince: +1, that would be nice19:56
SpamapShttp://lists.openstack.org/pipermail/openstack-dev/2013-December/022269.html19:56
SpamapSlifeless: I don't know if that is a trello thing or not. It will pay off a bunch of technical debt in merge.py and the resulting painful-to-maintain templates...19:57
dprinceslagle: thanks, I postponed my previous effort there because HOT is so close19:57
lifelessSpamapS: so the basic ideas is that we're moving as a group tackling things together rather than siloing off19:58
lifelessSpamapS: you're saying this is the next thing we need, no?19:58
*** obondarev_ has quit IRC19:58
lifelessSpamapS: heat work, to get update working properly?19:58
mariosSpamapS: do you guys think its close enough that i shouldn't waste any more time with https://review.openstack.org/#/c/52045/ and related?19:58
SpamapSdprince: yeah the whole point of hot-software-config is to make it easier to write config separate from server placement.19:58
SpamapSlifeless: no. It is not the next thing.19:59
SpamapSwe can keep going deeper in debt to merge.py for a long time to come.19:59
*** denis_makogon_ has joined #openstack-meeting-alt19:59
*** obondarev_ has joined #openstack-meeting-alt19:59
SpamapSlifeless: the next thing we need in heat is updatable wait conditions and retry-on-update19:59
lsmolaSpamapS, so we are keepig merge.py in I ?19:59
lifeless#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Jan 14 20:00:03 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-14-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-14-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-01-14-19.00.log.html20:00
*** jcoufal has quit IRC20:00
lifelesssorry, out of time20:00
lifeless-> #tripleo for more chat20:00
*** banix has quit IRC20:00
mariosgoodnight/good-day all o/20:00
*** tzumainn has left #openstack-meeting-alt20:01
*** pdmars has quit IRC20:01
pblahogood night20:01
jistrnight20:01
ifarkassee you all20:01
*** pblaho has quit IRC20:01
*** pdmars has joined #openstack-meeting-alt20:01
shadowersee ya20:01
lsmolasee ya20:02
*** pdmars has quit IRC20:02
*** pdmars_ has joined #openstack-meeting-alt20:02
*** jcoufal has joined #openstack-meeting-alt20:02
*** pdmars_ has quit IRC20:03
*** e0ne has quit IRC20:03
*** nam_nguyen has quit IRC20:04
*** beyounn has quit IRC20:06
*** pdmars has joined #openstack-meeting-alt20:06
*** denis_makogon has quit IRC20:06
*** denis_makogon_ is now known as denis_makogon20:06
*** dmakogon_ has joined #openstack-meeting-alt20:06
*** NikitaKonovalov has quit IRC20:06
*** pdmars has quit IRC20:07
*** pdmars has joined #openstack-meeting-alt20:07
*** vipul is now known as vipul-away20:08
*** esker has quit IRC20:08
*** pdmars has quit IRC20:08
*** pdmars has joined #openstack-meeting-alt20:10
*** resker has joined #openstack-meeting-alt20:10
*** pdmars has quit IRC20:10
*** pdmars has joined #openstack-meeting-alt20:11
*** beyounn has joined #openstack-meeting-alt20:12
*** vipul-away is now known as vipul20:12
*** rook has quit IRC20:13
*** NikitaKonovalov has joined #openstack-meeting-alt20:13
*** morazi has left #openstack-meeting-alt20:15
*** obondarev_ has quit IRC20:16
*** rlandy has quit IRC20:20
*** sarob has quit IRC20:23
*** HenryG has joined #openstack-meeting-alt20:24
*** irenab_ has joined #openstack-meeting-alt20:25
*** NikitaKonovalov has quit IRC20:25
*** vipul is now known as vipul-away20:27
*** early has quit IRC20:28
*** irenab_ is now known as irenab20:28
*** malini has left #openstack-meeting-alt20:30
*** NikitaKonovalov has joined #openstack-meeting-alt20:33
*** NikitaKonovalov has quit IRC20:35
*** jtomasek has quit IRC20:39
*** jtomasek has joined #openstack-meeting-alt20:41
*** jistr has quit IRC20:42
*** tmckay has joined #openstack-meeting-alt20:46
*** sarob has joined #openstack-meeting-alt20:48
*** jamezpolley has left #openstack-meeting-alt20:49
*** sarob has quit IRC20:50
*** sarob has joined #openstack-meeting-alt20:51
*** early has joined #openstack-meeting-alt20:52
*** beyounn has quit IRC20:54
*** rpodolyaka1 has left #openstack-meeting-alt20:54
*** tomblank has joined #openstack-meeting-alt20:56
*** sreshetnyak has joined #openstack-meeting-alt20:56
*** lblanchard has quit IRC20:58
*** lblanchard has joined #openstack-meeting-alt21:03
*** lblanchard has quit IRC21:03
*** banix has joined #openstack-meeting-alt21:06
*** dprince has quit IRC21:06
*** julim has quit IRC21:06
*** irenab has quit IRC21:09
*** alazarev has quit IRC21:14
*** alazarev has joined #openstack-meeting-alt21:18
*** jmontemayor has quit IRC21:22
*** jprovazn has quit IRC21:23
*** vipul-away is now known as vipul21:26
*** rnirmal has quit IRC21:40
*** ifarkas has quit IRC21:45
*** alazarev has quit IRC21:54
*** jdob has quit IRC21:54
*** alazarev has joined #openstack-meeting-alt21:55
*** lblanchard has joined #openstack-meeting-alt21:59
*** beyounn has joined #openstack-meeting-alt21:59
*** jtomasek has quit IRC22:01
*** jtomasek has joined #openstack-meeting-alt22:01
*** doug_shelley66 has quit IRC22:03
*** resker has quit IRC22:05
*** tmckay is now known as _tmckay22:05
*** pdmars has quit IRC22:12
*** sarob has quit IRC22:15
*** sarob has joined #openstack-meeting-alt22:16
*** Barker has quit IRC22:19
*** ruhe is now known as _ruhe22:21
*** Barker has joined #openstack-meeting-alt22:25
*** pnavarro has quit IRC22:26
*** Barker has quit IRC22:28
*** julim has joined #openstack-meeting-alt22:29
*** doug_shelley66 has joined #openstack-meeting-alt22:30
*** obondarev_ has joined #openstack-meeting-alt22:30
*** kevinconway has quit IRC22:35
*** sreshetnyak has quit IRC22:35
*** SergeyLukjanov has quit IRC22:36
*** jcoufal has quit IRC22:43
*** tomblank has quit IRC22:46
*** lsmola has quit IRC22:48
*** julim has quit IRC22:52
*** lblanchard has quit IRC22:55
*** obondarev_ has quit IRC22:58
*** obondarev_ has joined #openstack-meeting-alt22:59
*** obondarev_ has quit IRC23:07
*** ccrouch1 has joined #openstack-meeting-alt23:09
*** ccrouch has quit IRC23:10
*** jtomasek has quit IRC23:10
*** jecarey has quit IRC23:13
*** denis_makogon has quit IRC23:16
*** aignatov has quit IRC23:17
*** ashaikh has quit IRC23:21
*** safchain has joined #openstack-meeting-alt23:26
*** sarob has quit IRC23:32
*** eharney has quit IRC23:33
*** nati_ueno has joined #openstack-meeting-alt23:38
*** garyduan has joined #openstack-meeting-alt23:39
*** ccrouch1 has quit IRC23:45
*** ViswaV has quit IRC23:47
*** banix has quit IRC23:51
*** ijw has quit IRC23:57

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