Tuesday, 2014-04-15

*** nati_ueno has quit IRC00:01
*** derekh has quit IRC00:02
*** Sukhdev has joined #openstack-meeting-alt00:02
*** nati_uen_ has joined #openstack-meeting-alt00:02
*** ujuc has joined #openstack-meeting-alt00:02
*** nati_uen_ has quit IRC00:03
*** nati_ueno has joined #openstack-meeting-alt00:04
*** ujuc has quit IRC00:07
*** eguz has quit IRC00:08
*** nati_ueno has quit IRC00:15
*** arnaud has quit IRC00:17
*** nati_ueno has joined #openstack-meeting-alt00:18
*** arnaud has joined #openstack-meeting-alt00:19
*** Leonr has quit IRC00:20
*** michael-yu has quit IRC00:21
*** nosnos has joined #openstack-meeting-alt00:26
*** Sukhdev is now known as Sukhdev__00:27
*** colinmcnamara has joined #openstack-meeting-alt00:28
*** nosnos has quit IRC00:31
*** nosnos has joined #openstack-meeting-alt00:32
*** demorris has joined #openstack-meeting-alt00:37
*** rueb7363 has quit IRC00:43
*** nati_uen_ has joined #openstack-meeting-alt00:43
*** demorris has quit IRC00:44
*** colinmcnamara has quit IRC00:44
*** nati_ueno has quit IRC00:47
*** rueb7363 has joined #openstack-meeting-alt00:49
*** rmoe has quit IRC00:51
*** amytron has joined #openstack-meeting-alt00:56
*** ameade has joined #openstack-meeting-alt00:56
*** rueb7363 has quit IRC00:58
*** julienvey has joined #openstack-meeting-alt00:58
*** nati_uen_ has quit IRC00:59
*** mozawa has joined #openstack-meeting-alt00:59
*** nati_ueno has joined #openstack-meeting-alt01:00
*** ameade has quit IRC01:00
*** nati_ueno has quit IRC01:00
*** nati_ueno has joined #openstack-meeting-alt01:00
*** mattgriffin has quit IRC01:02
*** SumitNaiksatam has quit IRC01:07
*** ekarlso has quit IRC01:11
*** ekarlso has joined #openstack-meeting-alt01:13
*** ekarlso has quit IRC01:13
*** ekarlso has joined #openstack-meeting-alt01:18
*** zz_gondoi is now known as gondoi01:21
*** khyati has quit IRC01:21
*** SumitNaiksatam has joined #openstack-meeting-alt01:24
*** kgriffs is now known as kgriffs|afk01:28
*** gyee has quit IRC01:35
*** xuhanp has joined #openstack-meeting-alt01:42
*** richm has quit IRC01:46
*** amcrn has quit IRC01:50
*** harlowja has quit IRC01:52
*** harlowja_ has joined #openstack-meeting-alt01:52
*** marun has joined #openstack-meeting-alt01:55
*** alee has quit IRC01:56
*** ameade has joined #openstack-meeting-alt01:56
*** MarkAtwood has joined #openstack-meeting-alt01:57
*** gondoi is now known as zz_gondoi01:58
*** pleia2 has quit IRC02:00
*** sbalukoff has quit IRC02:00
*** ameade has quit IRC02:01
*** Sukhdev__ has quit IRC02:02
*** pleia2 has joined #openstack-meeting-alt02:06
*** mattgriffin has joined #openstack-meeting-alt02:08
*** rmoe has joined #openstack-meeting-alt02:15
*** spzala has quit IRC02:17
*** mattgriffin has quit IRC02:29
*** coolsvap|afk is now known as coolsvap02:30
*** Barker has quit IRC02:35
*** david-lyle has joined #openstack-meeting-alt02:38
*** zz_gondoi is now known as gondoi02:45
*** venkatesh has joined #openstack-meeting-alt02:45
*** mattgriffin has joined #openstack-meeting-alt02:49
*** eankutse has joined #openstack-meeting-alt02:54
*** khyati has joined #openstack-meeting-alt02:55
*** demorris has joined #openstack-meeting-alt02:58
*** ujuc has joined #openstack-meeting-alt02:58
*** gondoi is now known as zz_gondoi03:00
*** yamamoto_ has joined #openstack-meeting-alt03:01
*** marun has quit IRC03:02
*** zns has quit IRC03:02
*** amotoki has quit IRC03:06
*** nati_ueno has quit IRC03:10
*** nati_ueno has joined #openstack-meeting-alt03:11
*** nati_ueno has quit IRC03:17
*** zns has joined #openstack-meeting-alt03:19
*** harlowja_ is now known as harlowja_away03:21
*** eankutse has quit IRC03:23
*** zhiyan_ is now known as zhiyan03:30
*** zhiyan is now known as zhiyan_03:31
*** beyounn has quit IRC03:32
*** amytron has quit IRC03:32
*** eghobo has joined #openstack-meeting-alt03:36
*** betsy has joined #openstack-meeting-alt03:38
*** nosnos has quit IRC03:39
*** demorris has quit IRC03:41
*** rueb7363 has joined #openstack-meeting-alt03:44
*** rueb7363 has quit IRC03:45
*** zhiyan_ is now known as zhiyan03:47
*** MarkAtwood has quit IRC03:52
*** harlowja_away is now known as harlowja_03:53
*** zns has quit IRC03:55
*** rand738 has quit IRC04:01
*** ameade has joined #openstack-meeting-alt04:01
*** david_lyle_ has joined #openstack-meeting-alt04:01
*** michael-yu has joined #openstack-meeting-alt04:01
*** ameade has quit IRC04:01
*** rand738 has joined #openstack-meeting-alt04:01
*** david-lyle has quit IRC04:01
*** venkatesh has quit IRC04:02
*** amytron has joined #openstack-meeting-alt04:07
*** chandan_kumar has joined #openstack-meeting-alt04:08
*** lblanchard has joined #openstack-meeting-alt04:11
*** chandan_kumar has quit IRC04:17
*** nosnos has joined #openstack-meeting-alt04:31
*** david_lyle_ has quit IRC04:37
*** david-lyle has joined #openstack-meeting-alt04:38
*** akuznetsov has joined #openstack-meeting-alt04:41
*** chandan_kumar has joined #openstack-meeting-alt04:50
*** gokrokve has quit IRC04:51
*** akuznetsov has quit IRC05:02
*** akuznetsov has joined #openstack-meeting-alt05:03
*** michael-yu has quit IRC05:03
*** eghobo has quit IRC05:05
*** eghobo has joined #openstack-meeting-alt05:05
*** lblanchard has quit IRC05:14
*** akuznetsov has quit IRC05:14
*** samstav has quit IRC05:19
*** akuznetsov has joined #openstack-meeting-alt05:21
*** noslzzp has quit IRC05:23
*** mattgriffin has quit IRC05:24
*** amotoki has joined #openstack-meeting-alt05:28
*** michael-yu has joined #openstack-meeting-alt05:29
*** mattgriffin has joined #openstack-meeting-alt05:32
*** venkatesh has joined #openstack-meeting-alt05:35
*** harlowja_ is now known as harlowja_away05:37
*** khyati has quit IRC05:41
*** ewindisch has quit IRC05:45
*** PeterSchwaller_ has joined #openstack-meeting-alt05:48
*** ewindisch has joined #openstack-meeting-alt05:49
*** PeterSchwaller has quit IRC05:51
*** akuznetsov has quit IRC05:52
*** venkatesh has quit IRC05:55
*** yamahata has joined #openstack-meeting-alt06:00
*** betsy has quit IRC06:01
*** denis_makogon has joined #openstack-meeting-alt06:02
*** _nadya_ has joined #openstack-meeting-alt06:06
*** akuznetsov has joined #openstack-meeting-alt06:10
*** dguitarbite has joined #openstack-meeting-alt06:12
*** akuznetsov has quit IRC06:13
*** tnurlygayanov has quit IRC06:17
*** tnurlygayanov has joined #openstack-meeting-alt06:18
*** yamahata has quit IRC06:24
*** alex_didenko has joined #openstack-meeting-alt06:25
*** michael-yu has quit IRC06:26
*** mattgriffin has quit IRC06:27
*** _nadya_ has quit IRC06:35
*** nacim has joined #openstack-meeting-alt06:37
*** IlyaE has quit IRC06:39
*** marun has joined #openstack-meeting-alt06:43
*** arnaud has quit IRC06:44
*** marun has quit IRC06:45
*** yamahata has joined #openstack-meeting-alt06:45
*** nacim has quit IRC06:50
*** GheRivero_ is now known as GheRivero06:50
*** flaper87|afk is now known as flaper8706:54
*** ramishra has joined #openstack-meeting-alt06:55
*** michael-yu has joined #openstack-meeting-alt06:59
*** michael-yu has quit IRC07:02
*** nati_ueno has joined #openstack-meeting-alt07:05
*** mspreitz has joined #openstack-meeting-alt07:10
*** michael-yu has joined #openstack-meeting-alt07:13
*** michael-yu has quit IRC07:15
*** michael-yu has joined #openstack-meeting-alt07:19
*** michael-yu has joined #openstack-meeting-alt07:20
*** jcoufal has joined #openstack-meeting-alt07:22
*** nati_ueno has quit IRC07:39
*** matrohon has quit IRC07:40
*** matrohon has joined #openstack-meeting-alt07:45
*** denis_makogon has quit IRC07:49
*** denis_makogon has joined #openstack-meeting-alt07:50
*** mspreitz has quit IRC07:51
*** nati_ueno has joined #openstack-meeting-alt07:51
*** jgallard has joined #openstack-meeting-alt07:57
*** nati_ueno has quit IRC08:01
*** ramishra has quit IRC08:03
*** nati_uen_ has joined #openstack-meeting-alt08:04
*** nacim has joined #openstack-meeting-alt08:05
*** denis_makogon has quit IRC08:05
*** julienve_ has joined #openstack-meeting-alt08:06
*** zhiyan is now known as zhiyan_08:10
*** zhiyan_ is now known as zhiyan08:10
*** nati_uen_ has quit IRC08:14
*** dguitarbite has quit IRC08:14
*** nati_ueno has joined #openstack-meeting-alt08:14
*** zhiyan is now known as zhiyan_08:14
*** zhiyan_ is now known as zhiyan08:15
*** yamahata has quit IRC08:18
*** eguz has joined #openstack-meeting-alt08:26
*** alex_didenko has quit IRC08:28
*** derekh has joined #openstack-meeting-alt08:29
*** alex_didenko has joined #openstack-meeting-alt08:29
*** eghobo has quit IRC08:30
*** bogdando has quit IRC08:30
*** dshulyak has quit IRC08:30
*** bogdando has joined #openstack-meeting-alt08:30
*** ramishra has joined #openstack-meeting-alt08:36
*** yamamoto_ has quit IRC08:42
*** eguz has quit IRC08:42
*** julienvey has left #openstack-meeting-alt08:44
*** dshulyak has joined #openstack-meeting-alt08:44
*** julienvey has joined #openstack-meeting-alt08:45
*** jtomasek has joined #openstack-meeting-alt08:48
*** akuznetsov has joined #openstack-meeting-alt08:54
*** noslzzp has joined #openstack-meeting-alt08:55
*** julienve_ has quit IRC08:56
*** sergmelikyan has quit IRC08:59
*** noslzzp has quit IRC08:59
*** sergmelikyan has joined #openstack-meeting-alt08:59
*** nati_ueno has quit IRC09:12
*** oomichi has joined #openstack-meeting-alt09:12
*** zhiyan is now known as zhiyan_09:13
*** ujuc has quit IRC09:14
*** zhiyan_ is now known as zhiyan09:15
*** mozawa has quit IRC09:32
*** akuznetsov has quit IRC09:34
*** chandan_kumar has quit IRC09:38
*** andreaf has joined #openstack-meeting-alt09:55
*** chandan_kumar has joined #openstack-meeting-alt09:55
*** irenab has joined #openstack-meeting-alt09:59
*** xuhanp has quit IRC10:07
*** ujuc has joined #openstack-meeting-alt10:08
*** yamamoto has joined #openstack-meeting-alt10:10
*** yamamoto has quit IRC10:12
*** ujuc has quit IRC10:16
*** jgallard has quit IRC10:21
*** chandan_kumar has quit IRC10:23
*** nosnos has quit IRC10:27
*** chandan_kumar has joined #openstack-meeting-alt10:37
*** Adri2000 has quit IRC10:38
*** Adri2000 has joined #openstack-meeting-alt10:39
*** Adri2000 has quit IRC10:39
*** Adri2000 has joined #openstack-meeting-alt10:39
*** irenab has quit IRC10:41
*** eanxgeek|log is now known as eanxgeek10:54
*** akuznetsov has joined #openstack-meeting-alt10:54
*** coolsvap is now known as coolsvap|afk10:56
*** ramishra has quit IRC11:09
*** ramishra has joined #openstack-meeting-alt11:10
*** oomichi has quit IRC11:17
*** tedross has joined #openstack-meeting-alt11:19
*** david-lyle has quit IRC11:20
*** PeterSchwaller has joined #openstack-meeting-alt11:25
*** PeterSchwaller_ has quit IRC11:27
*** mattgriffin has joined #openstack-meeting-alt11:35
*** chandan_kumar has quit IRC11:42
*** mattgriffin has quit IRC11:53
*** jgallard has joined #openstack-meeting-alt11:56
*** zz_gondoi is now known as gondoi11:56
*** gondoi is now known as zz_gondoi11:57
*** chandan_kumar has joined #openstack-meeting-alt11:58
*** mwagner_lap has quit IRC12:02
*** jgallard has quit IRC12:08
*** jgallard has joined #openstack-meeting-alt12:09
*** pdmars has joined #openstack-meeting-alt12:14
*** baoli has quit IRC12:18
*** amytron has quit IRC12:23
*** xuhanp has joined #openstack-meeting-alt12:23
*** chandan_kumar has quit IRC12:26
*** meow-nofer_ is now known as meow-nofer12:27
*** jdob has joined #openstack-meeting-alt12:29
*** akuznetsov has quit IRC12:35
*** jjmb has quit IRC12:35
*** Haiying has joined #openstack-meeting-alt12:37
*** baoli has joined #openstack-meeting-alt12:37
*** chandan_kumar has joined #openstack-meeting-alt12:41
*** akuznetsov has joined #openstack-meeting-alt12:43
*** matrohon has quit IRC12:44
*** Guest3914 has joined #openstack-meeting-alt12:48
*** demorris has joined #openstack-meeting-alt12:49
*** heyongli has joined #openstack-meeting-alt12:57
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Tue Apr 15 13:00:51 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
baoliHi there13:01
heyonglihi13:01
*** BrianB_ has joined #openstack-meeting-alt13:01
*** Guest3914 is now known as beagles13:01
beagleshi13:01
*** beagles is now known as Guest8474313:01
*** rkukura has joined #openstack-meeting-alt13:01
baoliIrenab is not going to be here today13:01
baoliLet's wait to see if John and Rkukura are going to join13:02
Guest84743(nick has gone crazy, Guest84743 is beagles)13:02
rkukuraI’m lurking, but am not caught up on current sr-iov goings on13:02
baoliI think that we should get started.13:04
* russellb lurking13:05
baolihttps://review.openstack.org/#/c/86606/13:05
*** ramishra has quit IRC13:06
baoliFor networking, my simplistic view of how tenant is going to use it: 1) want a sr-iov port (with macvtap or not), 2) the port is connected to a particular network.13:07
heyonglibaoli, agree, also picture this way13:08
baoliSo basically a compute host needs to provide the number of sr-iov ports per network it's connected with13:09
*** sadasu has joined #openstack-meeting-alt13:09
*** MarkAtwood has joined #openstack-meeting-alt13:09
heyonglidon't get you point, but this is sound good,13:10
baoliheyongli, I'm talking about the information required from a compute host for sr-iov networking13:11
*** eankutse has joined #openstack-meeting-alt13:12
heyongligot, does this bring something new?13:12
Guest84743baoli, to clarify, when you write "(macvtap or not)" above, do you mean the tenant specifies the type of connection (direct/macvtap) or is this implicit in the sr-iov/network spec?13:13
*** eankutse has quit IRC13:13
*** eankutse has joined #openstack-meeting-alt13:13
*** amytron has joined #openstack-meeting-alt13:13
baoliguest84743, two variants with sr-iov ports13:13
Guest84743right okay13:14
Guest84743so the have a degree of control over how it is connected?13:14
*** zz_gondoi is now known as gondoi13:14
baoliheyongli, not really. We have gone over it several times.13:14
heyonglii suppose the port type could be specified by user or not, both should be a valid use case13:14
baoliGuest84743, yea, with macvtap, less performance, but with live migration support13:15
* Guest84743 nods13:15
baoliheyongli, on top of the basic use cases, you brought it up that a tenant may want to use a sr-iov port that resides on a particular vendor's card.13:16
baoliWould everyone agree that the cloud should provide this support to the tenant?13:17
Guest84743has there ever been a discussion about using classifiers instead of direct "specification" that would mean something like 'passthru-to-net-foo-direct' instead of lower level details, or is this type of generalization/indirection seen as being part of a flavor mechanism13:17
russellbthis feels like flavor driven stuff to me13:17
heyongliguest84743, i agree13:17
russellbGuest84743: /nick beagles :-)13:17
baolibeagles, yes, we talked about that.13:18
sadasuGuest84743: good point13:18
Guest84743russellb, wouldn't let me change.. or kept changing it back13:18
russellbGuest84743: may need to identify with nickserv13:18
rkukuraI’m no expert on this area, but do we need to think about how the tenant ensures the VM has the right driver for whatever device they are asking for?13:18
Guest84743yeah, I've read the backlog of emails but in the end I couldn't get a strong handle on the general consensus13:18
*** Guest84743 is now known as b3nt_pin13:18
heyonglii also think the vendor,  vnic type should be hide in flaovr, but user also should can choose it if user does want it13:18
sadasurkukura: yes...that is very critical for the feature to work13:19
b3nt_pinheh, b3nt_pin will have to do for now.. won't let me (b3nt_pin is beagles)13:19
baolirkukura, do you mean the kernel device driver?13:20
rkukurabaoli: yes13:20
rkukurain the VM13:20
b3nt_pinrkukura, that wouldn't suck :)13:20
sadasuwhen the tenant picks the vendor and product ids, this indirectly takes care of the tenant driver criteria13:20
russellbyou can so something for that between flavor metadata and image metadata13:20
russellbcapabilities / requirements matching13:20
russellbif you want13:20
*** dteselkin_ has quit IRC13:21
b3nt_pinrussellb, is there a good example of this in use that you would recommend?13:21
rkukuraIf the tenant needs to ensure the VM has the correct driver, I don’t think we should be obfuscating how the tenant specifies/sees the vNIC type too much13:21
russellbrkukura: that's a fair point13:22
sadasurkukura: the same driver usually supports both vnic_types generally13:22
heyonglithe drive should directly depend on the device it use, not the nic type it use,  i think13:24
sadasudriver decides which host the VM can run on and the vnic_type decides the mode in which the sr-iov port can be used13:24
rkukuraAgain, I’m far from an expert on this area, but does the VM need a driver specific to the SR-IOV card’s vendor/type?13:25
*** dprince has joined #openstack-meeting-alt13:25
sadasuvnic_type is not useful in the placement of a VM on a host but the driver info is13:25
sadasurkukura: correct13:25
baolirkukura, would an image be built with all the device drivers the cloud would support?13:26
rkukuraSo vnic_type is more of a mode of operation than a device type?13:26
*** demorris has quit IRC13:26
sadasurkukura: correct ...again :-)13:27
rkukurabaoli: I guess if the image is supplied by the cloud provider, that would be reasonable.13:27
sadasuand only neutron cares about the vnic_type...nova can be blind to it13:27
*** dteselkin_ has joined #openstack-meeting-alt13:27
sadasuwe just want to include it in a single API, so the user can launch a VM with all these specification via one command13:27
heyonglito get a device driver properly setup, we may setup the meta data after get the actually device, but i'm not sure at that point, is there a way to do so,  for a tenant image.13:28
sadasurkukura: by image do you mean kernel driver for the sr-iov ports?13:29
b3nt_pinsadasu, rkukura: to clarify, are we saying that a VM needs a device specific driver? If yes, does it still need that if the vnic type is macvtap (doesn't sound right)?13:29
heyongliand this is common issue for all pci passthrough not only for sriov13:29
rkukurab3nt_pin: I don’t know the answers13:29
*** amytron has quit IRC13:30
b3nt_pinrkukura, :) okay... I'll poke around and see if I can find out what the deal with libvirt is at least.13:30
sadasub3nt_pin: host needs a device specific driver13:30
b3nt_pinsadasu, host, but not VM, right?13:30
rkukurasadasu: Yes, I meant the image that is booted, with its kernel, drivers, …13:30
sadasub3nt_pin: correct13:30
*** alex_didenko has quit IRC13:31
b3nt_pinsadasu, aahhh okay... that makes sense :)13:31
b3nt_pinsadasu, I'm curious how VFs are presented to a VM but I suppose that is a virtualization detail.13:32
sadasurkukura: atleast with the pci passthru devices that I am exposed to so far...the driver resides in the kernel of the host OS and not the guest OS13:32
sadasunot sure if any devices out there break that model13:32
b3nt_pinsadasu, I'm happy to "hear" that as it is consistent with my admittedly "academic" view (awaiting hardware to get hands-on)13:33
sadasubut I am guessing there will dfntlt be a host OS level driver...there might be an additional guest os lever driver13:33
sadasulevel*13:33
heyonglisadasu, any device? don't thinks so, some driver must in the guest os also,for some device13:33
*** balajiiyer has joined #openstack-meeting-alt13:33
b3nt_pinheyongli, yeah.. that would make sense especially for not networking SR-IOV13:33
sadasuheyongli: yes...mentioned that..13:34
* b3nt_pin wonders if anybody has a crypto board13:34
sadasuthe point I am trying to make is that ..there is a host kernel dependency also...13:34
heyonglib3nt_pin, i had one13:34
heyonglisadasu, seems a deploy problem13:34
russellbi think even if we only pulled of sr-iov NICs for Juno, that'd be a huge step forward :)13:35
b3nt_pinsadasu, yeah.. so this has to be presented as part of the info, basically. Whether configured or discovered.13:35
sadasuif the dependency is only on the VM image, then I think it is pretty simple because the cloud provider can provide the correct image ...end of story13:35
*** balajiiyer has left #openstack-meeting-alt13:35
b3nt_pinrussellb, +10013:35
baoliI think that we are talking about a different issue: how to select a host that meets the requirement that comes from a tenant built image.13:35
russellb"only"13:35
*** spzala has joined #openstack-meeting-alt13:35
*** mfer has joined #openstack-meeting-alt13:35
* b3nt_pin didn't meant to "dilute"13:35
russellbnah i said that13:36
*** dteselkin_ has quit IRC13:36
rkukuraMy concern was purely with the tenant VM having the correct driver for the virtual device that shows up in the VM, not with the hosts’ drivers.13:36
heyonglirkukura, the metadata service might be a answer for this, fix me13:37
sadasurkukura: in that case, the tenant has to supply nova with the correct image id, correct?13:37
baoliSay the tenant built image supports mlnx driver only.13:38
heyonglibaoli, then we need vendor information here, in the flavor13:38
*** venkatesh has joined #openstack-meeting-alt13:39
baoliHow to extract the requirement from the image?13:39
heyonglisadasu, for any image, provide some information to VM is a possible solution13:39
sadasubaoli: thought we covered that...13:40
heyonglibaoli, this is another story, i try to make image can append pci device information specs or flavor something13:40
sadasuheyongli: yes, that where the vendor_id, product_id come into play13:40
baolisadasu, can you enlighten me again?13:41
sadasubaoli: :-)13:41
*** MarkAtwood has quit IRC13:41
sadasuu are the expert..13:41
sadasuok...so I think this is where we are:13:42
b3nt_pincan we not simply assign that info to the image via metadata?13:42
sadasuPCI device needs      1. driver in host OS 2. driver in guest OS 3. Both13:42
heyonglib3nt_pin, we must had facility to extrat that from image.13:43
sadasuveryone on same page so far?13:43
heyonglisure, host driver is deploy scope i think,, guest image is a problem, we might should split that to another topic , it's common for all pci device. fix me13:44
sadasuspecifying vendor_id, product_id will help nova place VM of type 1 on correct host13:44
*** dteselkin_ has joined #openstack-meeting-alt13:44
*** mozawa has joined #openstack-meeting-alt13:44
baolib3nt_pin: do we have an API to associate the meta-data with the image, which then can be used for host scheduling?13:45
sadasubased on driver inside the VM image, once again giving vendor_id, product_id to nova should let us place it on the Host having the correct HW13:45
heyonglisadasu, i don't think vm need this in a type one request,  where am i wrong?13:45
sadasucase 3: is same as above13:45
*** jcoufal has quit IRC13:45
b3nt_pinbaoli, http://docs.openstack.org/grizzly/openstack-compute/admin/content/image-metadata.html13:46
baolib3nt_pin, thanks13:46
*** jcoufal has joined #openstack-meeting-alt13:46
sadasufor case 1: we will use vendor_id product_id just to determine if pci passthrro devices exist13:46
sadasub3nt_pin: thanks will take a look13:47
heyonglisadasu, no , whitelist should  does this, in a deploy stage.13:47
*** mwagner_lap has joined #openstack-meeting-alt13:47
sadasuagreed...whitelist contains the same info..13:47
sadasuit would deftly help to associate meta data with the VM instead of expecting the tenant to assign the correct image to the VM13:48
heyongliany thing related to host, should be a deploy problem, at least deploy involved in13:48
sadasuyes...even at deploy you are providing vendo_id, product_id13:49
*** gondoi is now known as zz_gondoi13:49
heyonglisadasu, sure, it help, current image meta data could not address vm's driver problem if we don't check that in PCI pass-through scope13:51
*** ameade has joined #openstack-meeting-alt13:51
b3nt_pinI'm kind of struggling with the "extract from vm" idea... what do we mean by that?13:52
heyonglib3nt_pin,where is the extract form vm idea? i'm lost here13:53
* b3nt_pin goes back ...13:53
b3nt_pinsorry.. heyongli I misinterpreted your previous statement13:53
b3nt_pinyou said, "extract from image" not from VM13:53
b3nt_pinmy bad13:53
sadasuI am a little worried if we are making the configuration very difficult13:54
b3nt_pincan you elaborate at which points you feel might be increasing the difficulty?13:54
*** balajiiyer has joined #openstack-meeting-alt13:54
heyonglisadasu, not really difficult, which point difficult do you mean?13:55
*** balajiiyer has left #openstack-meeting-alt13:55
* b3nt_pin is telepathically linked to heyongli apparently13:55
sadasuwhitelist, image meta-data, sr-iov port modes, picking the correct ml2 driver on the neutron side :-)13:55
sadasuI get what is going on..I am looking at it from a tenant perspective13:55
* b3nt_pin nods... 13:56
b3nt_pinare all of these essential for basic SR-IOV usage, or only required for finer and finer control?13:56
heyongliall of this could be done automatically, except the image meta-data, that's might be confuse now, but not very bad13:56
*** Haiying has quit IRC13:56
heyonglii thinks it's finer control13:56
b3nt_pinyeah13:57
sadasub3nt_pin: hard to say what is basic SR-IOV usage anymore :-)..every device/vendor is doing things slightly differently13:57
b3nt_pinlol13:57
heyonglicause OS admin could say, we had all these device, please pre install driver for your image... this is a simple solution here13:57
baoliheyongli, thinking about the same.13:59
baoliok, we have to wrap it up today14:00
heyongliif we provide image constrain, it's also a good feature,14:00
sadasuok...so my action item is to understand the image metadata feature better to see if that better suits the VM image driver dependency issue14:00
baolithanks everyone14:00
b3nt_pincheers all!14:00
baoli#endmeeting14:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:00
openstackMeeting ended Tue Apr 15 14:00:37 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:00
heyonglibye14:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-04-15-13.00.html14:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-04-15-13.00.txt14:00
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-04-15-13.00.log.html14:00
rkukuraheyongli: I agree the usual solution will be for the cloud provide to include the necessary drivers in the images. But there will be the chance that some old images won’t have specific drivers, or possibly no driver is available for some OS14:00
*** dane_leblanc has joined #openstack-meeting-alt14:01
sadasurkukura : +114:01
heyonglirkukura, sure, i like to have a image feature to pci, it's in my todo list already14:01
heyongliand, rkukura, thanks bring this up, i take it as a import use case to get image problem solution14:02
*** gokrokve has joined #openstack-meeting-alt14:02
heyonglilet me got a bp there capture the ideas for further enhancement14:03
*** heyongli has quit IRC14:05
*** Shixiong has joined #openstack-meeting-alt14:06
*** demorris has joined #openstack-meeting-alt14:11
*** kevinconway has joined #openstack-meeting-alt14:11
*** sadasu has quit IRC14:13
*** rueb7363 has joined #openstack-meeting-alt14:13
*** chandan_kumar has quit IRC14:13
*** amytron has joined #openstack-meeting-alt14:14
*** atiwari has joined #openstack-meeting-alt14:17
*** Barker has joined #openstack-meeting-alt14:18
*** nati_ueno has joined #openstack-meeting-alt14:18
*** nati_ueno has quit IRC14:19
*** jmontemayor has quit IRC14:20
*** cjellick has quit IRC14:21
*** venkatesh has quit IRC14:22
*** nwidell has joined #openstack-meeting-alt14:22
*** venkatesh has joined #openstack-meeting-alt14:24
*** IlyaE has joined #openstack-meeting-alt14:30
*** eankutse has quit IRC14:32
*** eankutse has joined #openstack-meeting-alt14:32
*** mattgriffin has joined #openstack-meeting-alt14:33
*** AlanClark has joined #openstack-meeting-alt14:35
*** julienve_ has joined #openstack-meeting-alt14:38
*** jtomasek has quit IRC14:38
*** julienve_ has quit IRC14:41
*** agordeev has quit IRC14:43
*** jcoufal has quit IRC14:43
*** julienvey has left #openstack-meeting-alt14:44
*** eankutse has quit IRC14:44
*** bcrochet has quit IRC14:44
*** eankutse has joined #openstack-meeting-alt14:44
*** sriram has joined #openstack-meeting-alt14:46
*** venkatesh has quit IRC14:46
*** eankutse1 has joined #openstack-meeting-alt14:47
*** eankutse has quit IRC14:48
*** julienvey has joined #openstack-meeting-alt14:49
*** julienvey has left #openstack-meeting-alt14:49
*** bcrochet has joined #openstack-meeting-alt14:51
*** akuznets_ has joined #openstack-meeting-alt14:51
*** alcabrera has joined #openstack-meeting-alt14:53
*** vkmc has joined #openstack-meeting-alt14:53
*** vkmc has joined #openstack-meeting-alt14:53
*** jtomasek has joined #openstack-meeting-alt14:53
*** david-lyle has joined #openstack-meeting-alt14:54
*** akuznetsov has quit IRC14:54
*** malini has joined #openstack-meeting-alt14:54
*** mpanetta has joined #openstack-meeting-alt14:57
*** mspreitz has joined #openstack-meeting-alt14:59
malini#startmeeting Marconi15:00
openstackMeeting started Tue Apr 15 15:00:02 2014 UTC and is due to finish in 60 minutes.  The chair is malini. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
alcabrerao/15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: Marconi)"15:00
openstackThe meeting name has been set to 'marconi'15:00
flaper87o/15:00
*** demorris has quit IRC15:00
mpanettao/15:00
alcabreraI thought I'd forget15:00
*** jchai has joined #openstack-meeting-alt15:00
alcabreraThis dependent types paper is *too* good15:00
*** balajiiyer has joined #openstack-meeting-alt15:00
alcabreraanywho15:00
vkmco/15:00
alcabrerawelcome, all!15:00
sriram>—o->15:00
malinihello jchai! thanks for joining15:00
* sriram jumps right in15:00
vkmcHi hi :)15:00
maliniothers get no gratitude :D15:00
jchaiHello15:00
malinihello vkmc15:00
malinianybody else here for Marconi?15:01
alcabrerajchai: hey! glad to have you join us. :D15:01
alcabreravkmc: w00t! good to see you!15:01
malinijchai is working on adding tests in Tempest for Marconi15:01
maliniThank You jchai for your behind the scenes effort :)15:02
alcabreraawesome15:02
*** amitgandhi has joined #openstack-meeting-alt15:02
vkmcGood to see you all :)15:02
*** eankutse1 has quit IRC15:02
malinihttps://wiki.openstack.org/wiki/Meetings/Marconi#Agenda  get to the agenda15:02
flaper87yo yo yo15:02
amitgandhio/15:02
flaper87#link https://wiki.openstack.org/wiki/Meetings/Marconi#Agenda15:02
*** jcoufal has joined #openstack-meeting-alt15:03
malinihello amitgandhi15:03
maliniFirst action items from last time15:03
*** Obulpathi has joined #openstack-meeting-alt15:03
Obulpathihi15:03
maliniObulpathi: hello15:03
maliniACTION: balajiiyer to get report on queue metadata usage by Rackspace customers15:03
*** Leonr has joined #openstack-meeting-alt15:03
malinibalajiiyer: did you see a lot of queue metadata usage ?15:04
*** flwang has joined #openstack-meeting-alt15:04
balajiiyermalini: no, not really. it was less than 1% in all datacenters15:04
malinihello flwang!15:04
flwangmalini: Hey :D15:04
flaper87flwang: 'sup buddy ?15:04
flaper87balajiiyer: that's interesting15:04
flwangflaper87: good, you?15:04
*** sbalukoff has joined #openstack-meeting-alt15:05
malinibalajiiyer: do you have any insights on how customers use the metadata?15:05
alcabrera#info queue metadata usage is < 1% @ Rackspace15:05
balajiiyermalini: I looked at some of them, didnt make much sense to me, probably test data. But I can send you a dump of metadata we have for analysis15:06
Obulpathiso, its <1% users or <1% queues?15:06
*** xuhanp has quit IRC15:06
flwangbalajiiyer: did you mean most of the metadata are test/fake data?15:06
flwangObulpathi: good question15:06
Obulpathi:)15:07
alcabrerayup15:07
alcabrerabalajiiyer: can you clarify wrt to Obulpathi's question?15:07
balajiiyerflwang: the first set of data I poured my eyes on were test data. I can get you the dump for analysis15:07
balajiiyerObulpathi: 1% of queues15:07
flaper87I think what we need to figure out is: Would they freak out if the next version of the API doesn't have support for metadata?15:07
*** Shixiong has quit IRC15:07
flwangbalajiiyer: cool, thanks15:07
Obulpathiok15:08
*** tri_hoang_vo has joined #openstack-meeting-alt15:08
flaper87I'm not sure what 1% is in numbers but it's probably already worth an upgrade plan15:08
Obulpathican we email the customers using them metadata?15:08
balajiiyerflaper87: got it. it might mean that we need to reach out to some of the customers to understand how they are using it and how it will impact them15:08
alcabrera#info clarification: 1% of all queues created @ Rackspace contain metadata15:09
maliniyeap..the key question is will we break existing users15:09
flaper87balajiiyer: that would be awesome15:09
Obulpathibalaji: yep .. thet would be great15:09
amitgandhimegan_w: can help with reaching out to those customers15:09
*** tedross has left #openstack-meeting-alt15:09
malinimegan_w: can you take care of that plz?15:09
flaper87also, FWIW, if in doubt, we can just provide the upgrade plan we talked last week15:09
balajiiyercreate an action item, but megan_w told me once earlier that customers aren't really responsive, so we have to see how it goes15:10
maliniwe need more followup on this15:10
flaper87it's not hard to do, it's very conservative and plays nice with user data15:10
flaper87the feature will go away for sure, lets just make sure we don't blow user's data15:10
*** xuhanp has joined #openstack-meeting-alt15:10
*** xuhanp has quit IRC15:10
*** jmontemayor has joined #openstack-meeting-alt15:10
malini#action: balajiiyer, megan_w to investigate customer impact when queue metadata support is removed15:11
*** cjellick has joined #openstack-meeting-alt15:11
maliniany more questions on this?15:11
alcabreranone from me15:11
flaper87nope15:11
Obulpathinone from my side15:11
maliniok..moving on15:11
maliniWe dont have any other action items listed15:12
*** zhangleiqiang has joined #openstack-meeting-alt15:12
maliniBut we need to track where we are on FAQ updates, ask15:12
maliniAnybody has the FAQ etherpad link handy?15:12
Obulpathialso, any update on the status of the POP?15:12
malini#link https://etherpad.openstack.org/p/draft-marconi-faq15:13
*** rmoe has quit IRC15:13
maliniI have not started on the test wiki, but will do tht this week15:13
malini#action: Malini to build a test wiki for Marconi15:14
alcabrerathanks, malini15:14
alcabrerare: the faq15:14
flaper87Please, guys, lets finish that FAQ15:14
alcabreraI haven't investigated oslo.messaging yet15:14
flaper87I think the sooner we start the discussion on the ML the better15:14
malinialcabrera: can you do it this week?15:14
alcabrerayup15:14
alcabreraactionize me! :)15:14
flaper87that will give us enough time to iterate over the FAQ several times15:15
alcabreraflaper87: agreed15:15
malini#action: alcabrera to compare marconi with oslo.messaging15:15
alcabreracool15:15
maliniflaper87, flwang: do you have pending tasks for the FAQ?15:16
flaper87malini: there are several open questions there15:16
flaper87I tackled some of them today, I'll go through the remaining before the enxt week15:16
maliniCan we assign folks to the open questions now?15:16
*** eankutse has joined #openstack-meeting-alt15:16
flwangmalini: nothing from me, but I'm available to be assigned something15:16
Obulpathiplease assign one to me15:17
flaper87I'd prefer folks to go there and add their names right next to the question15:17
maliniflaper87: +115:17
Obulpathi+115:17
flaper87Obulpathi: feel free to pick whatever question you want to work on15:17
maliniLets do it before the end of meeting , so we can actionize them15:17
maliniWe'll come back to this towards the end of meeting, to add more actions15:17
maliniLets tackle the FAQ this week & create a similar plan for ask next week15:18
maliniAnything else on this?15:18
malinimoving on..15:19
malini#topic: Split graduation list to smaller actionable chunks for each week15:19
*** openstack changes topic to ": Split graduation list to smaller actionable chunks for each week (Meeting topic: Marconi)"15:19
alcabreraI'm a favorable towards this proposal15:19
alcabreraerr15:19
alcabrera* I am15:19
malinithe idea behind this is to make progress on our pending tasks at a steady pace15:19
maliniwe dont want to make a scramble towards the end15:19
alcabrera+115:20
maliniideally I would like the tempest/ gating tasks done before the summit15:20
Obulpathi+1 to malinis proposal15:20
alcabrerathat would be lovely15:20
alcabreraand I think we can do it15:20
flaper87malini: I agree. However, I think we are still not 100% sure what those tasks are. I mean, we know some of them for sure15:20
malini#link https://etherpad.openstack.org/p/marconi-graduation-chunks15:20
flaper87I think the summit is the best moment for us to brainstorm about this15:20
maliniflaper87: good point..we still have a lot of cloudy areas15:20
flaper87it's perfect because we'll *all* be there15:21
maliniBut we have some tasks we need to get done for sure15:21
flaper87(Don't worry, I'll convince flwang to be there)15:21
mpanettapun intended malini?15:21
maliniyou are the only one who got it mpanetta ;)15:21
* flaper87 still doesn't get how the pun stuff work15:21
* amitgandhi i just sighed15:21
alcabreracloudy, cloudy15:21
flwangflaper87: haha15:21
alcabreraI can see the silver-lining, at least15:21
malini:D15:21
alcabrera:)15:22
flwangI'm still reviewing the list to pick one :D15:22
flaper87ahhh, "cloudy areas"15:22
flaper87got it15:22
* flaper87 is so fucking slow15:22
alcabrera:P15:22
maliniflaper87: Can we start tackling the areas we know for sure?15:22
malinitht will leave us free to tackle any new stuff tht comes up15:22
flaper87malini: absolutely, I was just about to say that15:22
alcabreragetting mongo up and running in the gate with Trusty out would be great15:22
maliniawesome15:22
alcabrerasince15:22
flaper87so, pretty much everything related to new features is still "cloudy"15:22
alcabrerathat's like15:22
flaper87:P15:22
alcabrera3 days away15:22
alcabreraI think15:22
mpanettahah15:23
flaper87but things like tempest15:23
malinialcabrera: I dont know when infra will have Trusty, but I'll foloow up15:23
alcabreramalini: thanks!15:23
*** nwidell has quit IRC15:23
flaper87gate, devstack, etc have to be done15:23
malini#action: Malini to follow up on Trusty with openstack-infra15:23
maliniflaper87: exactly15:23
maliniCurrently our biggest blocker is we still dont have marconi running on devstack15:23
maliniThis blocks horizon, tempest & making the jobs voting15:24
maliniWe have two bugs tht need to be fixed, to get around this15:24
malini(In addition to Trusty, which is not a blocker)15:24
*** rkukura has left #openstack-meeting-alt15:24
flaper87well, marconi running on the gate15:24
flaper87I think15:24
flaper87mmg15:24
flaper87ok, I kinda lost track there15:25
maliniflaper87: thanks for the correction15:25
* flaper87 trusts malini15:25
mpanettammg the merciless15:25
amitgandhithis bug is fixed right: https://bugs.launchpad.net/marconi/+bug/128749015:25
malini#info Marconi runs on devstack, but not on gate in devstack15:25
*** eankutse has quit IRC15:25
maliniamitgandhi: It came back15:25
alcabrerampanetta: heh. :P15:25
maliniamitgandhi: with this one https://bugs.launchpad.net/marconi/+bug/130126815:26
amitgandhiugh hate it when bugs dont squish right15:26
*** eankutse has joined #openstack-meeting-alt15:26
*** tomblank has joined #openstack-meeting-alt15:26
*** richm has joined #openstack-meeting-alt15:26
maliniamitgandhi: the original fix  changed the server behavior, making it hard for devs15:26
amitgandhiyeh =/15:26
* flaper87 should really pay attention to what's going on in LP15:27
malinianyways Can I get someone to volunteer on https://bugs.launchpad.net/marconi/+bug/1287490 ?15:27
*** betsy has joined #openstack-meeting-alt15:27
maliniWe really need this fixed this week15:27
malinisince it blocks a lot of upstream integration15:27
flaper87now that malini has the powerz, I see more bugs assigned to me. NOt sure if it's related to that, though15:27
flaper87:P15:27
alcabreraIt's low-hanging fruit, imo. This is a great one for new-comers.15:27
alcabrera:)15:27
ObulpathiI can do it15:27
alcabreracool!15:27
ObulpathiLet me assing to myself15:27
maliniObulpathi: awesome..Let me assign tht to you15:28
maliniObulpathi: even better15:28
Obulpathi:)15:28
malini#action: Obulpathi to work on https://bugs.launchpad.net/marconi/+bug/128749015:28
maliniLets get this fixed this week..Nag everybody on openstack-marconi if you need help ;)15:28
malinithe next one is https://bugs.launchpad.net/devstack/+bug/129406815:29
maliniI am not so sure we want to fix this..but want to hear everybody's thoughts15:29
malini#link https://bugs.launchpad.net/devstack/+bug/129406815:29
amitgandhii vote no if we arent going to support mysql15:29
*** khyati has joined #openstack-meeting-alt15:29
amitgandhiwould rather focus energy around mongo and X15:29
mpanettaamitgandhi: +115:29
amitgandhiwhere X is redis or whatever15:30
*** baoli has quit IRC15:30
flaper87malini: Is it *just* a mysql issue?15:30
flaper87I know the bug report says mysql but I want to make sure15:30
maliniflaper87: yes..sqlite runs fine15:30
malinion gate i.e15:30
flaper87I'd say, lets not worry (prio low) about it now15:30
flwangmalini: maybe we missed some mysql specific config15:30
maliniI dont know why mysql does not work at the gate, but does outside15:30
alcabreraflaper87: +115:30
Obulpathi+115:30
flaper87but saying we won't fix it sounds bad15:30
alcabreraI propose we drop sqla as a core platform once we have redis|amqp available15:31
maliniflwang: do you want to take a look at this one?15:31
amitgandhiare we deprecation mysql?15:31
flaper87especially because, although not recommended, we have support for it15:31
*** rueb7363 has quit IRC15:31
flaper87amitgandhi: not now, for sure15:31
*** baoli has joined #openstack-meeting-alt15:31
*** rueb7363 has joined #openstack-meeting-alt15:31
flaper87probably in the not so far future15:31
maliniflaper87: how far? before our next grad review?15:31
flwangmalini: I can if it's targeted in Juno15:31
alcabreradropping sqla, in particular, leads to easier installs (no longer require mysql_config to be installed)15:31
amitgandhiif its a low hanging fruit then just do it15:31
flaper87malini: after, I'd say15:31
amitgandhiif its time and energy, then dont bother (my opinion)15:32
flaper87alcabrera: does sqlalchemy require mysql_config?15:32
mpanettaalcabrera: +115:32
flaper87that's weird15:32
maliniflaper87: In that case, we need this fixed - since we'll be asked what backends are used in the gate15:32
flaper87I mean, we *HAVE* to remove python-mysql form the requirements *before* the graduation15:32
alcabrerathat's been my experience so far, flaper87. :/15:32
alcabreraor15:32
alcabrerahmm15:32
flaper87which is the dep requiring mysql_config15:32
alcabreramaybe it's python-mysql15:32
alcabrerayes, that15:32
flaper87ok15:32
flaper87#action flaper87 remove python-mysql dependency15:33
alcabrera+7.2515:33
flaper87alcabrera: waaa??? Why so low ?15:33
Obulpathi+2.515:33
flaper87Obulpathi: <315:33
*** hockeynut1 has joined #openstack-meeting-alt15:33
Obulpathi:)15:33
flaper87who gives me the remaining .25 ?15:33
alcabreratriple core, 1 regular, and a quarter to go15:33
malini#action: flwang to work on https://bugs.launchpad.net/devstack/+bug/1294068 for Juno15:33
*** hockeynut1 has quit IRC15:33
mpanetta+0.25 :P15:33
flaper87mpanetta: <3  <315:33
ObulpathiI din't do my math right :(15:34
flaper87ok15:34
maliniOther items in https://etherpad.openstack.org/p/marconi-graduation-chunks15:34
flaper87Obulpathi: still <315:34
maliniItem # 2 is blocked by #115:34
maliniSo lets get 1.1 fixed this week15:34
alcabreraso devstack really needs a fix15:34
malinialcabrera: yes15:34
Obulpathigot it15:34
maliniTempest Updates15:35
Obulpathiwill push it to my top priority15:35
malinijchai: want to update on API tempest tests?15:35
jchaiJust getting started15:35
jchaiI should be able to submit something later in the week15:36
malinijchai: do you think you can get the queues API tests patch submitted this week?15:36
maliniTht will be poistive tests for 5 more APIs15:36
jchaiI think so, yes15:36
malini#action: jchai to work on Queues API +ve tests15:37
malini#action: Malini to work on adding CLI tests15:37
maliniok..moving on15:37
*** muralia has joined #openstack-meeting-alt15:37
malini#topic: Meeting with TC to discuss graduation15:37
*** openstack changes topic to ": Meeting with TC to discuss graduation (Meeting topic: Marconi)"15:37
maliniWe need to get into the TC schedule again15:38
flaper87+115:38
flaper87couple of thoughts there15:38
maliniflaper87: sure..this is all yours15:38
flaper871) We need to have the FAQ ready and more marketing-like docs written15:38
flaper872) We should probably do it after the summit and participate in the cross-project sessions15:39
flaper873) I think we should also have the tasks sorted out15:39
flaper87with that plan, we can request a TC meeting to discuss what's expected from us15:39
*** IlyaE has quit IRC15:39
alcabrera+1; +1; +1;15:39
flaper87also, we need more than 1 meeting15:39
alcabreraagreed15:39
maliniflaper87: what are specific actions that we need to do between now & the summit?15:39
flaper87for instance, we need to discuss the whole falcon + pecan thing, one more time15:39
alcabrerawe need to be regulars to have our voices heard15:39
flaper87malini: FAQ and docs15:40
maliniwe addressed the FAQ15:40
maliniWhat do we need for the docs?15:40
flaper87also, gather more info about our take on pecan, benefits and downsides15:40
flaper87balajiiyer: did an amazing work15:40
flwangflaper87: what's the mean of "participate in the cross-project sessions"15:40
flaper87but again, the summit is *THE* right moment to reach to the community15:40
amitgandhiwe need to be more active on ask (post questions as well as answers)15:40
maliniflwang: http://summit.openstack.org/ has cross project sessions15:41
flaper87we need to talk to the guys working on pecan, we need to talk to the TC members again and to everyone in the community15:41
maliniflaper87: +115:41
flaper87we need to ask for feedback on our current, high-level plan15:41
flaper87etc15:41
maliniI think we are in the right direction & have the right ideas15:41
*** rmoe has joined #openstack-meeting-alt15:41
flaper87so, between now and the summit, I think we should focus on building the missing FAQ and doc foundations for Marconi15:41
*** aostapenko has quit IRC15:41
flaper87malini: +115:42
maliniBut we are still missing a solid list of stuff that we will do to accomplish these15:42
maliniflaper87: Can you detail the doc foundations? what can we do to get it done?15:42
flaper87sure15:42
flaper87so, besides the FAQ15:42
maliniIt will be ideal if it ends with #actions ;)15:42
flaper87I think we need to document our architecture a bit better15:43
Obulpathi+115:43
flaper87it's not clear for people what marconi looks like15:43
mpanettaA series of cheese laden tubes?15:43
flaper87we need to document what we mean with scaling marconi horizontally and what *sharding* means in MArconi's context15:43
amitgandhimaybe obul can do that while he learns it?15:43
Obulpathisure .. I can document that15:44
flaper87we need to document better what transports are or simply *stop* talking about them until we add another transport15:44
flaper87etc15:44
flaper87all this besides the FAQ15:44
malini#action: Obulpathi to document Marconi architecture15:44
flaper87Once that's done, we should then invite folks to read them15:44
flaper87and then chase them down at the summit15:44
malinimpanetta: Can you or oz do the 'document what we mean with scaling marconi horizontally and what *sharding* means in MArconi's context' ?15:44
alcabrerasounds like a problem tackled in multiple directions -- e.g., defining marconi15:44
flaper87to get feedback15:44
alcabreradocs, blogs, articles15:44
flaper87alcabrera: yeah15:45
mpanettamalini: Hmm, didn't Oz already do a doc, does it not include that?15:45
flaper87Our biggest problem in our graduation attempt was that basically no one knew what marconi looks like15:45
flaper87not even the TC15:45
*** khyati has quit IRC15:46
mpanettaI almost wish it was not called sharding, I always get confused between marconi and mongodb 'sharding'15:46
malinimpanetta: I dont think we talked with the focus on scaling15:46
flaper87not until after we withdrew our graduation request15:46
amitgandhior what marconi was ;-)15:46
flaper87mpanetta: it is sharding after all :P15:46
malinihmm..even if we create all the docs, will anybody outside of us read that?15:46
*** sbalukoff has quit IRC15:46
flaper87mpanetta: but I agree15:46
*** rmoe has quit IRC15:46
maliniIf creating awareness is our goal...15:46
flaper87malini: we don't know that but that doesn't mean we shouldn't have them15:46
maliniI think we can tie this in with our next topic15:46
flaper87malini: our goal is to clear all those points among ourselves too15:46
maliniflaper87: good point15:47
Obulpathi+115:47
flaper87for isntance, we know we want to graduate but we don't have a detailed list of how we benefit from graduating15:47
*** jtomasek has quit IRC15:47
flaper87we need to have that too15:47
malinidoes everybody agree on stopping the talk about transport, till we have something other than http?15:47
flaper87this will help the project and the community15:47
alcabreramalini: agreed15:47
amitgandhimalini: +115:47
flaper87(note I meant stop talking about it, not stop working on it)15:48
malinitht is easier than creating a new document ;)15:48
flaper87there's some work Cindy is doing that is worth moving forward15:48
*** jaypipes has quit IRC15:48
flaper87that said, I agree15:48
amitgandhiif the focus is on another storage then we dont need to keep talking about transports15:48
flaper87yeah15:48
flaper87we're 2 weeks away from the summit15:48
flaper87(maybe 3)15:48
malinicool.Lets have a new transport that really works, & then lets start talking abt it15:48
sriram+115:48
flaper87so, I think it is worth dedicating the upcoming weeks to writing docs instead of code15:49
maliniGuess its time to move on to the next topic15:49
maliniflaper87: +115:49
* amitgandhi dusts of microsoft word15:49
mpanettaargh 2 weeks...  If we are going to do the marconi cluster thing I need to find something else to run it on...15:49
mpanettaSomeone bought all the wandboards heh15:49
malinican we move on to the next topic?15:49
* flaper87 STFU15:49
alcabreramalini: yes15:49
mpanettayes15:49
malini#topic ATL summit15:49
*** openstack changes topic to "ATL summit (Meeting topic: Marconi)"15:49
malinimpanetta is eager to talk abt wandboards15:50
maliniSo lets hear that first :)15:50
* amitgandhi 10 minute warning15:50
flaper87amitgandhi: +115:50
malinithanks amitgandhi15:50
flwangcan we add these docs into source code under /doc?15:50
mpanettaWell, someone purchased them all and they have a 6 week lead time, so we have to find another platform.15:50
maliniflwang: +115:50
mpanettaIf we really want to do this (I think it would be a way to get people looking at it anyway)15:51
malinimpanetta: its your territory, you get to choose - unless somebody else has other ideas15:51
malinimpanetta: I hope you are still typing :)15:52
*** gyee has joined #openstack-meeting-alt15:52
mpanettaI'm looking15:52
mpanettabut nothing is as cheap :(15:52
mpanettaI am always open to suggestions :)15:52
malini#action: mpanetta to investigate wandboard cluster alternatives15:52
mpanettaCool :)15:53
malini#topic •'Marconi-Meet the team' dinner15:53
*** openstack changes topic to "•'Marconi-Meet the team' dinner (Meeting topic: Marconi)"15:53
*** james_li has joined #openstack-meeting-alt15:53
malinithis was kgriffs|afk idea15:53
amitgandhinote - atl hack day in next thur/fri ( flaper87, flwang are free to join us )15:53
alcabreraw00t15:53
*** roshanagr1 has joined #openstack-meeting-alt15:53
maliniamitgandhi: good point..tht wud be awesome15:53
flwangamitgandhi: how to join?15:54
flwangamitgandhi: is it f2f? or online? or....15:54
maliniflwang, amitgandhi: Lets discuss this in #openstack-marconi15:54
*** aratim has joined #openstack-meeting-alt15:54
flwangmalini: sure15:54
maliniWe are almost out of time15:54
amitgandhiphysically you can fly to the Rackspace Atlanta office ;-) else we can hangout in the #marconi channel15:54
alcabrera+1 for continuing discussion on hackday in #marconi15:55
malinikgriffs|afk had the idea of a Meet the team dinner during the summit15:55
*** tzumainn has joined #openstack-meeting-alt15:55
* amitgandhi stfu15:55
*** tzumainn has left #openstack-meeting-alt15:55
flwangamitgandhi: send me the air tickets, please15:55
maliniIt'll be cool if we can get some of the interested parties from other projects there15:55
alcabrerameet the team dinner would be lovely15:55
*** IlyaE has joined #openstack-meeting-alt15:55
* flaper87 wants to meet everyone on saturday15:55
alcabrerayes!15:55
malinihmm..15:55
flwangmalini: yep, it's targeted on 10 IIRC15:55
flaper87that is May 10th15:55
alcabreraI'll mark my calendat15:56
maliniI believe this is going to be us + everybody else in openstack15:56
alcabrera*calendar15:56
alcabreraso I *might* remember, :P15:56
flwangflaper87: I'm not sure if I can make it :(15:56
flaper87flwang: :(15:56
*** julienve_ has joined #openstack-meeting-alt15:56
flwangflaper87: given the moving, you know15:56
ObulpathiI wil join on saturday15:56
maliniI believe we are talking abt diff dinners :D15:56
alcabreraflwang: dang, that's right. you'll be missed. :(15:57
maliniWe probably need a hanging out internally + hanging out with prospective Marconi users15:57
*** datsun180b has joined #openstack-meeting-alt15:57
*** devkulkarni has joined #openstack-meeting-alt15:57
mpanettayes15:57
alcabreramalini: increasing inclusivity is always a plus15:57
flaper87alcabrera: +115:57
*** devkulkarni has left #openstack-meeting-alt15:57
flwangalcabrera: yep, bad15:57
alcabreraI'll see if GSoC students can make it out as well15:57
*** colinmcnamara has joined #openstack-meeting-alt15:57
flaper87I don't mind if other people join as long as you all are there <315:58
alcabrera*GSoC/OPW15:58
flaper87<3 <3 <#15:58
maliniawesome15:58
alcabrera<315:58
*** paulmo has joined #openstack-meeting-alt15:58
maliniIf there are folks you can reach out personally to invite, please do15:58
*** devkulkarni has joined #openstack-meeting-alt15:58
maliniremember we are looking for prospective customers too :)15:58
*** devkulkarni has quit IRC15:58
*** julienv__ has joined #openstack-meeting-alt15:58
alcabrera1m -- final thoughts?15:59
malini#action: everybody to create a list of prospective dinner invitees15:59
*** julienv__ is now known as julienvey_15:59
maliniI guess tht ends our meeting15:59
* flaper87 invites the marconi team15:59
*** devkulkarni has joined #openstack-meeting-alt15:59
flaper87w000t15:59
alcabrerahaha15:59
amitgandhiwe have to do this at marconi grill15:59
*** adrian_otto has joined #openstack-meeting-alt15:59
maliniLets continue on #openstack-marconi15:59
flaper87is there a marconi grill ?15:59
maliniThanks everyone!!15:59
flaper87O.O15:59
flaper87malini: thank you15:59
malini#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Tue Apr 15 15:59:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-15-15.00.html15:59
alcabreraI'll gather minutes15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-15-15.00.txt15:59
*** coolsvap|afk is now known as coolsvap15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2014/marconi.2014-04-15-15.00.log.html15:59
adrian_otto#startmeeting Solum Team Meeting16:00
openstackMeeting started Tue Apr 15 16:00:02 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
*** alcabrera has left #openstack-meeting-alt16:00
*** paulczar has joined #openstack-meeting-alt16:00
*** mpanetta has left #openstack-meeting-alt16:00
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum#Agenda_for_2014-04-15_1600_UTC Our Agenda16:00
*** Obulpathi has left #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
roshanagr1Roshan Agrawal16:00
tomblanktom blankenship16:00
devkulkarniDevdatta Kulkarni16:00
julienvey_Julien Vey16:00
*** eghobo has joined #openstack-meeting-alt16:00
*** julienve_ has quit IRC16:00
stanniePierre Padrixe16:00
coolsvapSwapnil16:00
*** jchai has left #openstack-meeting-alt16:00
paulmoPaul Montgomery16:01
muraliamurali16:01
aratimArati Mahimane16:01
paulczarPaul Czarkowski!16:01
*** CristianF has joined #openstack-meeting-alt16:01
*** baoli has quit IRC16:01
*** IlyaE has quit IRC16:01
*** eghobo has quit IRC16:01
datsun180bEd Cranford16:02
adrian_ottoWelcome everyone. Anyone else is welcome to chime in at any time to be recorded in the meeting attendance.16:03
adrian_otto#topic Announcements16:03
*** openstack changes topic to "Announcements (Meeting topic: Solum Team Meeting)"16:03
adrian_ottoNew Alternating Meeting Time Vote - Vote Pending16:03
adrian_otto#link https://wiki.openstack.org/wiki/Meetings/Solum#Proposed_Alternate_Meeting_Time16:03
*** Barker has quit IRC16:03
adrian_otto#link http://doodle.com/yma2pppk2nhwwgc8 Vote Here16:03
adrian_ottoplease take a moment to visit the doodle poll, and register your input16:04
adrian_ottoyou can use the (Yes) voting option to indicate that you could attend at the indicated time, but that you would rather not16:04
*** rajdeep has joined #openstack-meeting-alt16:04
adrian_ottokeep in mind that the whole point in alternating the meeting time is to make it possible for others to attend who are alseep at this time16:04
adrian_ottohi rajdeep16:04
rajdeephi adrian16:05
*** julienvey_ is now known as julienvey16:05
james_liJames Li16:05
devkulkarniwelcome james_li16:05
adrian_ottohi james_li16:05
gokrokveGeorgy Okrokvertskhov o/16:05
*** baoli has joined #openstack-meeting-alt16:06
*** mspreitz has left #openstack-meeting-alt16:06
devkulkarniadrian_otto: when does the vote close?16:06
adrian_ottodevkulkarni: as soon as I have heard from all known contributors who reside outside the US16:07
adrian_ottoI plan to consider input from core contributors highest16:07
devkulkarniadrian_otto: got it16:07
adrian_ottoI should say core reviewers16:07
rajdeepcan you share the voting link again?16:07
adrian_ottoirc://irc.freenode.net:6667/#link http://doodle.com/yma2pppk2nhwwgc8 Vote Here16:08
devkulkarnilooks like there is not a time that is convenient for all three (Banglore, Brisbane, Paris)16:08
*** amotoki_ has joined #openstack-meeting-alt16:08
adrian_ottothat was a funny cut/paste16:08
*** baoli has quit IRC16:08
adrian_ottodevkulkarni: exactly16:08
devkulkarniI am looking here: https://wiki.openstack.org/wiki/Meetings/Solum16:08
adrian_ottoon the Meetings wiki page I put smileys16:08
datsun180bI'm still not clear about what my vote means for this poll16:09
devkulkarniyep!! thanks for that. it helped16:09
adrian_ottobut as discussed before there is no time that will work for everyone16:09
julienveyit's OK for us if we can attend at least one out of 2 meetings16:09
*** IlyaE has joined #openstack-meeting-alt16:09
adrian_ottojulienvey: also I recognize that you and Pierre are pretty reachable in #solum during the US business day16:09
*** jaypipes has joined #openstack-meeting-alt16:09
adrian_ottoso we can probably keep you updated on those alternating weeks of key items of interest16:10
stannieyes that will be fine for us to assist at least to one of the meeting16:10
adrian_ottoplus we will have the meeting logs16:10
*** rmoe has joined #openstack-meeting-alt16:10
julienveyit would be great to have Angus participate in the other one :)16:11
*** eghobo has joined #openstack-meeting-alt16:11
*** baoli has joined #openstack-meeting-alt16:11
adrian_ottoexactly16:11
devkulkarnidatsun180b: all our votes can help in deciding the times that is convenient to those who cannot attend this one. if you plan to attend meeting other than this one then you can vote the time that is convenient for you..16:11
*** nwidell has joined #openstack-meeting-alt16:12
adrian_otto#action adrian_otto to close the voting on the New Alternating Meeting Time Vote, and send the results to the ML16:12
*** zhiyan is now known as zhiyan_16:12
*** nacim has quit IRC16:13
*** aostapenko has joined #openstack-meeting-alt16:13
adrian_ottoso, if you reside in the US, and you will NOT attend the alternating week meeting time regularly, then please vote No on the proposed meeting itme16:13
adrian_ottoI will take that into consideration when selecting16:13
*** Barker has joined #openstack-meeting-alt16:13
adrian_ottook, next topic16:14
datsun180bUnderstood16:14
adrian_otto#topic Review Action Items16:14
*** openstack changes topic to "Review Action Items (Meeting topic: Solum Team Meeting)"16:14
*** baoli_ has joined #openstack-meeting-alt16:14
adrian_ottoadrian_otto to propose a vote for a new meeting time for our ever-other-meeting schedule. [complete]16:14
adrian_ottoadrian_otto to follow up with paulmo to determine if https://blueprints.launchpad.net/solum/+spec/logging should be marked as Implemented [complete]16:15
*** baoli has quit IRC16:15
*** markwash has joined #openstack-meeting-alt16:15
adrian_ottowe will be re-scoping the remaining items in new bug/BP to be carried forward, and closing this blueprint16:15
*** derekh has quit IRC16:15
adrian_ottoooh, I forgot one thing about announcments16:16
*** balajiiyer has left #openstack-meeting-alt16:16
*** eghobo has quit IRC16:16
*** MarkAtwood has joined #openstack-meeting-alt16:16
adrian_ottodo any team members have other announcements they would like to share?16:16
adrian_ottook, next...16:16
*** balajiiyer has joined #openstack-meeting-alt16:17
adrian_otto#topic Environments16:17
*** openstack changes topic to "Environments (Meeting topic: Solum Team Meeting)"16:17
adrian_ottoat our meeting in Raleigh, NC we discussed the concept of Environments16:17
adrian_ottothese are abstract resources that can carry certain attributes that control how a deployment will happen16:17
adrian_ottofor example, who has access to the environment, which networks it contains, etc.16:18
*** balajiiyer has left #openstack-meeting-alt16:18
adrian_ottothose attributes can be inherited by the resources that become associated with the Environment resource16:18
*** aostapenko has quit IRC16:18
devkulkarniI saw roshanagr's email and julien_vey"s comments on it. I have few comments/questions16:18
adrian_ottothis concept may be useful within Solum, but may be more widely useful beyond Solum simply as a generic OpenStack resource16:19
roshanagr1I documented an inital set of use cases to frame the discussion: https://wiki.openstack.org/wiki/Solum/Environments16:19
adrian_ottoroshanagr1: excellent!16:19
roshanagr1Not intending for us to review and ratify the use cases, instead to have enough shared context so that we can start discussing with the following 2 goals in mind:16:19
*** eghobo has joined #openstack-meeting-alt16:19
roshanagr11. Identify the openstack projects the Environment feature is dependent on, and surface that dependency with the corresponding project teams in the Atlanta summit16:19
devkulkarniroshanagr1: in the email you mentioned something about 'who should own this piece'. could you elaborate more on it?16:19
roshanagr12. Develop a POV on which program the Environments feature should live under [Solum, Heat, or elsewhere]16:19
*** amitgandhi has left #openstack-meeting-alt16:19
roshanagr1@devkulkarni: that is goal 216:20
roshanagr1should it live within Solum. or Heat, or elsewhere16:20
*** markwash has quit IRC16:20
rajdeepi had one question on policy16:21
devkulkarnithat assumes the view that an environment is a heat stack16:21
devkulkarniwhich I don't think we have really agreed to16:21
rajdeepwhere does the policy related to publishing to different environment lives?16:21
adrian_ottodevkulkarni: I do not view an Environment as a feature of a stack16:21
roshanagr1@devkulkarni: we haven't agreed to anything yet16:21
julienveydevkulkarni: there is a wiki page with a more technical point of view about what is an environment https://wiki.openstack.org/wiki/Solum/ApiModel16:21
roshanagr1@rajdeep: don't know, TBD, probably keystone?16:22
adrian_ottorajdeep: excellent question. For policies to work, each service within OpenStack wold need to be extended to support Environments.16:22
rajdeephmm -- i am not sure keystone supports that16:22
tomblankroshanagr1: regarding goal 2.  Is it to create our program POV on what features are needed in existing OpenStack projects in order to support our program vision of enabling application developers and operators to easily support enviornments?16:22
paulczarto me an environment is a logical construct that provides hints/rules to Solum on where stacks can be placed16:22
adrian_ottoso even if there is a nice clean way to express, store, and list policies, each service will need to respect them16:22
rajdeepwe are working on a policy framework called16:22
rajdeepopenstack congress16:23
roshanagr1@tomblank:  yes16:23
rajdeephttps://wiki.openstack.org/wiki/Congress16:23
tomblankroshanagr1: thanks...16:24
rajdeepthere is a DSL being written to define policies16:24
julienveyrajdeep: good to know :)16:24
adrian_ottorajdeep: thanks for sharing that with us. We should look at each concept to see where Stackers could work together.16:24
roshanagr1@rajdeep: seems very relevant to this discussion. thanks!16:24
devkulkarnirajdeep: who enforces these policies?16:25
roshanagr1Environments feature will have a sependency on Keystone16:25
julienveyI tend to agree with paulczar's vision, which is kind of what Angus described in his wiki16:25
rajdeepthanks --16:25
*** jaypipes has quit IRC16:25
roshanagr1And Horizon16:26
roshanagr1Probably Heat16:26
rajdeepthis policy can be enforced reactively or proactively16:26
rajdeepdepending on the use case16:26
rajdeepin this case it could be proactive enforcement that flags voilations upfront16:26
*** dshulyak has quit IRC16:27
stanniein the wiki, does "lifecycle" means that we will use Environment as "promoted build" ?16:27
roshanagr1lifecycle means an app can progress from Dev- >Test- >Prod16:27
roshanagr1and a set of policy to manage that16:27
julienveystannie: That's how I see it16:28
stanniewhen you push your app, it will be first available in Dev environment, then if we choose to promote the build, then it will be in Test, Staging, Prod etc16:28
stannieyep16:28
devkulkarniyes16:28
roshanagr1stannie: yes16:28
stanniehowever there should be a way to deploy in production, in case if you fix a security bug or whatever16:28
roshanagr1stannie: good point.16:28
roshanagr1So there would be a default policy16:28
roshanagr1and a way to override it16:29
paulczarstannie: would we not allow the developer to have their own workflow policy?16:29
adrian_ottostannie: I imagine we can have an attribute in the Plan file that determines the target environment for a given assembly16:29
paulczarsome of us enjoy doing dev/test in production :D16:29
devkulkarnistannie: yes, we should have a way to do manual deploys/promotes as well. In https://wiki.openstack.org/wiki/Solum/ApiModel we have identified it16:29
stannieok16:29
*** BrianB_ has quit IRC16:30
devkulkarniadrian_otto: about that .. how do you envision plan file concept evolving to support environments?16:30
paulczarI would imagine that will all become part of the workflow stuff … once we determin if that belongs in Solum or somewhere else in the Program16:30
julienveystannie: there is some discussion here also about lifecycles, artifacts, and DU https://review.openstack.org/#/c/84434/16:31
stannieow, thank you julienvey16:31
adrian_ottodevkulkarni: a single plan refers to one environment. A workflow could just use that one, or could be configured to advance over a number of Environments in the coarse of following a flow.16:31
paulczardevkulkarni: for a simple app … you might have a plan that matches all your environments,  for a complex app you'd probably have a plan for each environment.16:32
adrian_ottoplans will *not* express workflows16:32
*** xenolog has joined #openstack-meeting-alt16:32
adrian_ottowe will have another approach for defining them16:32
adrian_ottoto begin with, we will have a few default workflows, and you can just ask for one by name16:33
adrian_ottoand later we can determine the best way to allow for detailed control to redefine custom flows.16:33
devkulkarniso plan would essentially define: code/artificat and required resources, and we would have a separate thing to define workflows16:33
adrian_ottoyes16:33
adrian_ottoas both don't really belong in the same artifact16:34
adrian_ottowe tried that and it got exceedingly comlex16:34
adrian_ottocomplex16:34
roshanagr1adrian_otto: should we consider decoupling environment from the plan file itself, so that the same plan file can be used to deploy to multiple environments?16:34
rajdeepi think trying to get into workflows will deviate us from the core use case16:34
rajdeepwe should just add hooks for workflow engines to be plugged in16:35
devkulkarniyep, makes sense. then the question would be what could be used to define the workflows. some thoughts that asalkeld and I had discussed were zuul, mistral, jenkins.16:35
adrian_ottoroshanagr1: perhaps. Are you thinking that it would be cast as a parameter?16:35
*** venkatesh has joined #openstack-meeting-alt16:35
roshanagr1@adrian_otto: possibly16:35
roshanagr1if I push my code+plan file from branch 1, deploy to dev16:35
adrian_ottoI suppose we could sue a parameter, with a default value16:36
roshanagr1if push from branch 2, deploy to test16:36
roshanagr1yes16:36
adrian_ottos/sue/use/ my fingers are not working well this morning16:36
julienveydevkulkarni: Jenkins has its own "Promotion" plugin. I think mistral would be a good option but we should investigate16:36
adrian_ottook, so let's determine what we will do next with Environments16:37
adrian_ottoshould we form a working group for it?16:37
julienveyroshanagr1: that's not a very common git workflow16:37
adrian_ottodoes it make sense to do that now, or start in Atlanta?16:37
tomblankadrian_otto: +1 on working group16:37
*** devkulkarni1 has joined #openstack-meeting-alt16:37
julienvey+1, we can start now I think16:38
tomblanki would suggest we start now16:38
roshanagr1+1 for working group.16:38
roshanagr1we need to have a POV before going to the Atlanta summit16:38
adrian_ottook, do we have a volunteer to chair the working group?16:38
roshanagr1I can do that16:38
adrian_ottoroshanagr1: thanks16:38
adrian_ottoI will assign you an AI to schedule a series of meetings to get further input from contributors16:39
adrian_ottosound ok?16:39
roshanagr1yes16:39
*** devkulkarni has quit IRC16:39
julienveyroshanagr1: agree that a POV would be good to have16:40
adrian_otto#action roshanagr1 to propose a working group, and schedule a recurring series to get input from contributors, and iterate on a plan for adding Environments as a feature to Solum and/or OpenStack16:40
roshanagr1please let me know who all would want to be part of the working group and  I will setup a doodle poll16:40
devkulkarni1roshanagr1: count me in16:40
*** amcrn has joined #openstack-meeting-alt16:40
julienveyroshanagr1: count me in too16:40
tomblankme too...16:40
adrian_ottoroshanagr1: I will attend16:40
rajdeepcount me in too16:40
roshanagr1thanks, will do.16:40
rajdeepif time is suitable16:41
tomblankand while i don't want to speak for him, i believe Angus will want to attend16:41
roshanagr1tomblank: yes16:41
*** sriram has left #openstack-meeting-alt16:41
devkulkarni1yep. I would say lets speak for him and count him in too :D16:41
adrian_ottolooks like a healthy number of Stackers, I suggest a doodle poll to schedule it, as we did with previous working groups.16:41
roshanagr1@adrian_otto: I will setup the doodle poll16:41
adrian_ottook, I want to only spend a few minutes on the next tipic16:41
*** btully has joined #openstack-meeting-alt16:41
adrian_otto#topic Mission Statement Review16:42
*** openstack changes topic to "Mission Statement Review (Meeting topic: Solum Team Meeting)"16:42
adrian_ottohas everyone had a chance to submit their thoughts in the etherpad?16:42
adrian_otto#link https://etherpad.openstack.org/p/solum-mission Mission Drafts16:42
*** btully has left #openstack-meeting-alt16:42
adrian_ottoif not, please take some time to get your thoughts in there16:42
adrian_ottoI'd like to focus us into a vote for next meeting16:42
adrian_ottoanyone think we need more discussion sessions?16:43
devkulkarni1minor clarification/point16:43
adrian_ottoIt's time to move from etherpad to wiki16:43
devkulkarni1the etherpad link says 'solum-mission' but we are discussing program mission16:43
devkulkarni1right?16:43
adrian_ottowe will have two missions16:43
*** zhangleiqiang has quit IRC16:44
adrian_ottoone for a program that covers an overall goal that may touch numerous projects16:44
adrian_ottoand another that focuses on project Solum to fit a more narrow set of ambitions16:44
roshanagr1We also need to choose a name for the Program16:44
adrian_ottoanother way to think of it is a Vision statement (for a Program)16:44
devkulkarni1when do we draw the line? do we go to Atlanta with both the statements?16:45
adrian_ottoand a Mission Statement (for a Project)16:45
*** eguz has joined #openstack-meeting-alt16:45
adrian_ottoI expect in Atlanta we will decide when it makes sense to propose an OpenStack program16:45
devkulkarni1ok16:46
adrian_ottoone possibility is I can take our mission, and complete an applciation16:46
adrian_ottoand we can iterate on that when we regroup in Atlanta in May16:46
devkulkarni1application for program you mean?16:46
adrian_ottoanother possibility is we can start looking at this each week until then, refining it further16:46
adrian_ottodevananda: yes, for a program16:46
adrian_ottothat's the more important initiative, I think16:47
adrian_ottoas multiple projects may form under that16:47
*** mat-lowery has left #openstack-meeting-alt16:47
adrian_ottothere is also a chance that some existing efforts that don't fit nicely under any existing program might prefer this one to being out in the ether16:47
devkulkarni1my vote will be to complete the application with what we have (which has shaped up great, I feel)16:47
*** eghobo has quit IRC16:49
adrian_ottook16:50
adrian_otto#topic Review Blueprints: https://launchpad.net/solum/+milestone/milestone-116:50
*** openstack changes topic to "Review Blueprints: https://launchpad.net/solum/+milestone/milestone-1 (Meeting topic: Solum Team Meeting)"16:50
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/deploy-workflow Workflow outlining deployment of a DU (asalkeld/devdatta-kulkarni)16:50
adrian_ottoshould this be marked as Implemented?16:50
julienveyadrian_otto: yes16:51
*** Obulpathi has joined #openstack-meeting-alt16:51
devkulkarni1yes. datsun180b has the latest.16:51
*** Obulpathi has quit IRC16:51
datsun180bconsidering we've been successfully deploying our ghost and ex1 apps for a while i say stick a fork in it16:51
adrian_ottoit's already marked accordingly16:51
*** Obulpathi has joined #openstack-meeting-alt16:51
datsun180bwell there you go16:52
adrian_otto#action adrian_otto to drop https://blueprints.launchpad.net/solum/+spec/deploy-workflow from the weekly agenda16:52
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/solum-git-pull Pull integration of Solum from an external Git repo (kraman)16:52
paulczarit's nonfunctional in master …  but the workflow is complete16:52
aratimThis one is nearing completion. Code is in place and functional tests are working. I am just doing the end to end testing now.16:52
devkulkarni1+1 aratim16:52
adrian_ottoThis one is marked as Implemented16:53
adrian_ottoshould we keep it on the weekly agenda?16:53
devkulkarni1I would say, yes. at least for next week16:53
aratimI think so. We can remove it next week16:53
adrian_ottook, next...16:53
adrian_otto#link https://blueprints.launchpad.net/solum/+spec/logging Logging Architecture (paulmo)16:53
*** zhangleiqiang has joined #openstack-meeting-alt16:54
adrian_ottopaulmo: as we mentioned earlier there are items in there that are out of scope16:54
adrian_ottoso I'd like to identify each and move them to tasks (wishlist bug), defects (bug) or another BP16:54
adrian_ottowe can work together on that, right?16:54
paulmoOk16:54
adrian_ottoanything you'd like input on from the team?16:55
*** akuznetsova_ has joined #openstack-meeting-alt16:55
paulmoNope, I'm good.16:55
adrian_ottothanks!16:55
adrian_otto#topic Open Discussion16:55
*** openstack changes topic to "Open Discussion (Meeting topic: Solum Team Meeting)"16:55
devkulkarni1btw, in launchpad is there a way to filter bugs based on tags? how do we find all bugs which are for m1?16:55
devkulkarni1or m2, etc.16:56
adrian_ottodevkulkarni1: I am working on that16:56
devkulkarni1okay.16:56
*** ankurrr has joined #openstack-meeting-alt16:56
adrian_ottothere is a way to view bugs in LP that belong to a milestone16:56
julienveydevkulkarni1: for tags, you have a clickable list on the right side of the bug list16:56
devkulkarni1yeah, that will help16:56
adrian_ottoand I am in the process of iterating the list, and getting each assigned to a milestone, or leaving them in the wishlist backlog.16:56
adrian_ottoyou can click on them on the right column, just like tags work16:57
devkulkarni1julienvey: okay. will try it.16:57
adrian_ottoand see a view by milestone16:57
adrian_ottoso that should start to get much more clear over the next couple of days16:57
*** jgallard has quit IRC16:57
devkulkarni1+116:57
*** harlowja_away is now known as harlowja_16:58
adrian_ottofor those seeking work in the mean time, look for bugs marked as "High" or "Medium"16:58
adrian_ottoand work through those.16:58
*** btully has joined #openstack-meeting-alt16:58
adrian_ottotop priority is to solve defects16:58
paulczarjust want to touch on how important we place on using docker driver.     It's currently not functional in master due to some recent merges and I have a few reviews up to get it working again … but there's some conficts with other features …  for example Neutron vs Docker16:58
*** coolsvap is now known as coolsvap|afk16:58
devkulkarni1did we manage to get a  presentation slot in Atlanta?16:59
paulczarso want to know if I should drop those reviews … or keep working on them16:59
adrian_ottodevkulkarni1: not yet, but we applied for this: https://www.openstack.org/blog/2014/03/call-for-proposals-open-source-openstack-summit/16:59
adrian_ottowe are awaiting a reply.16:59
*** sjmc7 has joined #openstack-meeting-alt16:59
*** tsufiev has joined #openstack-meeting-alt16:59
adrian_ottoI will also propose a vbrownbag session for a demo17:00
devkulkarni1paulczar: Nuetron client code merged in solum you mean?17:00
julienveypaulczar: for the heat template, I think you should create a new template, and use this one when solum is configured with docker17:00
julienveypaulczar: and stick with the actual one when using qcow217:00
*** katyafervent2 has joined #openstack-meeting-alt17:00
devkulkarni1adrian_otto: thanks for the link17:00
paulczarjulienvey: that's what I did with the review …  I reverted basic heat template and added a neutron one with the neutron features17:00
paulczargiven the strong backing for making docker default method at the summit … I thought it made most sense for doing it that way17:01
*** drupalmonkey has joined #openstack-meeting-alt17:01
adrian_ottothakns everyone17:02
devkulkarni1so we keep it then is what you are suggesting.. +117:02
adrian_otto#endmeeting17:02
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:02
openstackMeeting ended Tue Apr 15 17:02:07 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-04-15-16.00.html17:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-04-15-16.00.txt17:02
openstackLog:            http://eavesdrop.openstack.org/meetings/solum_team_meeting/2014/solum_team_meeting.2014-04-15-16.00.log.html17:02
*** paulmo has left #openstack-meeting-alt17:02
*** tomblank has left #openstack-meeting-alt17:02
*** rajdeep has quit IRC17:02
*** devkulkarni1 has left #openstack-meeting-alt17:02
*** muralia has left #openstack-meeting-alt17:02
*** paulczar has left #openstack-meeting-alt17:02
*** james_li has left #openstack-meeting-alt17:03
ruheit's time for Murano meeting17:03
*** EmilienM has quit IRC17:03
ruhe#startmeeting murano17:03
openstackMeeting started Tue Apr 15 17:03:39 2014 UTC and is due to finish in 60 minutes.  The chair is ruhe. 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
tsufievhi there17:03
ruhei'll copy the first topic from Solum meeting :)17:04
ruhe#topic Roll Call17:04
*** openstack changes topic to "Roll Call (Meeting topic: murano)"17:04
sjmc7hi guys17:04
* ruhe is ruslan kamaldinov17:04
btullyhowdy17:04
* btully is NOT a cowboy ;)17:04
katyafervent2Hi!17:05
akuznetsova_hello)17:05
tsufievi see a lot of new people this time :)17:05
ruheall right. i hope the rest of murano folk will join soon17:05
ruhe#topic Action Items Review17:05
*** openstack changes topic to "Action Items Review (Meeting topic: murano)"17:05
*** zhangleiqiang has quit IRC17:05
*** xenolog has quit IRC17:06
ruhe#link http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-04-08-17.02.txt17:06
ruhefirst AI is: gokrokve update status on https://blueprints.launchpad.net/murano/+spec/api-request-stats17:06
gokrokveHeh. I did not do this.17:07
ruhegokrokve: it's a good time to do it right now ;)17:07
*** eankutse1 has joined #openstack-meeting-alt17:07
gokrokveWill do this. Sure.17:07
ruhegokrokve: thanks17:07
ruhethe next AI is: ruhe to move events BPs to the next release17:07
*** EmilienM has joined #openstack-meeting-alt17:07
ruheand i did that17:07
*** eankutse has quit IRC17:07
ruhe#info moved events BPs to the next release17:08
ruhethe next one is:  sergmelikyan don't forget about and schedule a bug scrub day17:08
ruhelooks like sergmelikyan and me didn't do it. but we really wanted to17:08
ruheit's the release time and a lot of work, you know17:08
*** nati_ueno has joined #openstack-meeting-alt17:08
ruhesergmelikyan: you here?17:09
ruheok. i promise we will run bug scrub ASAP17:09
ruhe#action sergmelikyan don't forget about and schedule a bug scrub day17:10
ruhethe next AI is: tsufiev mark all UI-related BPs targeted on 0.5 as complete17:10
ruhetsufiev: some of your BPs are still "good progress"17:10
tsufievhm...17:10
ruhetsufiev: i would expect them to be "beta available" or "implemented"17:10
ruhe#link https://launchpad.net/murano/+milestone/0.517:10
*** datsun180b has left #openstack-meeting-alt17:11
*** adrian_otto has left #openstack-meeting-alt17:11
tsufievwe still have categories in 2 places - can it be considered completed?17:11
tsufievmarking them as beta...17:11
*** SumitNaiksatam has quit IRC17:11
akuznetsova_btw, i started to work with our bugs today, but there are a lot of bugs those are unassaigned and don't have a milestone17:11
ruhetsufiev: yes, beta is more appropriate for the current status of Murano UI17:11
tsufievruhe: done17:12
ruhetsufiev: thank you17:12
tsufievall is 'Implemented' or 'Beta...'17:12
katyafervent2because I have no rights to assign milestones anymore. Is it ok?) who should do it?17:12
ruheakuznetsova_: i guess it relates to our plan to run bug scrub day. but meanwhile you can process the bug list and use #murano to collect feedback on the bugs, wether they should be targeted for 0.5 or not17:13
dteselkinHi17:13
ruhekatyafervent2: core team should manage milestones17:13
akuznetsova_ruhe: ok, i'll do it tomorrow17:13
ruhekatyafervent2: you can always force them to take care of important bugs and BPs17:13
ruhe:)17:14
*** roshanagr1 has left #openstack-meeting-alt17:14
ruheok17:14
ruhenext AI is: xwizard_ add more tests for catalog API17:14
ruheakuznetsova_: i guess you can give us an update on tests for catalog API17:14
*** laurelm has quit IRC17:14
ruhebtw17:14
katyafervent2Sergey M did extend tests but I'm not sure if his commit was merged or no17:15
ruhe#info all UI-related BPs targeted on 0.5 are in "implemented" or "beta available" state17:15
*** laurelm has joined #openstack-meeting-alt17:15
katyafervent2let's say we did that for a smoke tests17:15
ruhekatyafervent2: do we need more test coverage in tempest?17:15
tsufievkatyafervent2: Me or Mu :)?17:15
katyafervent2Mu :)17:15
*** eankutse1 has quit IRC17:15
*** eankutse has joined #openstack-meeting-alt17:15
akuznetsova_yes, Sergey Mu wrote more tests for application catalog ang work with package17:16
ruhe#info sergey murashov added smoke tests for catalog API. we expect more tests to arrive17:16
ruhethat's all about action items17:17
tsufievakuznetsova_: what's about writing more tests for CentOS & Django 1.4?17:17
akuznetsova_tsufiev: do we need more special tests for that?17:17
ruhebefore we jump to the next topic "Release Status" i'd like folks to give a chance to propose additional topics17:17
tsufievakuznetsova_: we need to run the same tests as for ubuntu & django 1.5 - because they can behave differently17:18
*** eankutse has quit IRC17:18
*** b3nt_pin is now known as beagles17:18
*** eankutse has joined #openstack-meeting-alt17:19
tsufievruhe: i'd like to ask gokrokve about UI... is it right time now?17:19
gokrokveWhat is the question?17:19
ruhetsufiev: go ahead17:19
akuznetsova_tsufiev: ok, we will create new Jenkins Jobs with Centos as soon as our 'new' murano-ci will be done17:20
ruhesjmc7: btully: JFYI you can propose a topic for the weekly meeting if you have something major to discuss. there are two options - update https://wiki.openstack.org/wiki/Meetings/MuranoAgenda#Agenda before the meeting or propose topic when the meeting starts17:20
tsufievgokrokve: current UI have 2 category selectors: first as drop-down list, second in right sliding side-bar. will it remain in release?17:20
tsufievi found this a bit confusing17:20
sjmc7thanks ruhe - just lurking for now17:20
*** nati_ueno has quit IRC17:21
tsufievgokrokve: are you with us?17:23
*** tri_hoang_vo has quit IRC17:23
*** nati_ueno has joined #openstack-meeting-alt17:23
ruhetsufiev: i suggest to move on and continue your discussion when gokrokve gets back online17:24
gokrokveI think we can keep both. We can extend later the right panel.17:24
ruheoh, here is the man :)17:24
tsufievgokrokve: ok, if our UI man thinks it's ok, then it's ok :)17:24
ruhetsufiev: gokrokve: can we move the next topic?17:25
ruhe* to the next topic17:26
tsufievruhe: yes17:26
ruhe#topic Release status17:26
*** openstack changes topic to "Release status (Meeting topic: murano)"17:26
ruhein previous meetings we discussed each component in detail17:26
*** SumitNaiksatam has joined #openstack-meeting-alt17:27
ruhetoday i'd like to have an open discussion about items we think are important for this release, but not yet merged or implemented17:27
*** eankutse1 has joined #openstack-meeting-alt17:28
*** eankutse has quit IRC17:28
ruhegokrokve: you're the one who always cares about features :) what's missing from your point of view?17:28
tsufievruhe: advanced networking, of course :)17:28
gokrokveYes. Networking part should be in 0.5 as it was suported on 0.4 version.17:29
*** nati_ueno has quit IRC17:29
gokrokveother stuff can be added later in 0.5.1 release17:29
ruhe#info advanced networking is a must have for 0.517:29
*** michael-yu has joined #openstack-meeting-alt17:30
ruhei don't see stan_lagun here. correct me if i'm wrong, but i think that he's working on this feature17:30
*** nati_uen_ has joined #openstack-meeting-alt17:30
*** betsy has quit IRC17:30
ruhetsufiev: do we have a bug for it?17:31
ruheor BP17:31
*** slagun has joined #openstack-meeting-alt17:31
tsufievruhe: don't know of any17:32
tsufievruhe: fortunately you can ask slagun himself :)17:32
ruheslagun: ping17:32
*** sbalukoff has joined #openstack-meeting-alt17:32
slagunhi17:32
slagunsorry for being late. What is the question?17:32
ruheslagun: are you working on advanced networking?17:32
slagunnot yet17:33
*** dane_leblanc has quit IRC17:33
ruheslagun: but you will, right?17:33
slagunhopefully17:33
ruheslagun: can i ask you to file a bug related to this missing feature?17:33
slagunnp17:33
slagunsure17:34
ruhe#action slagun file a bug about missing "advanced networking"17:34
ruhe#action slagun implement "advanced networking" in 0.517:34
ruheanything else critical we would like to land in 0.5?17:35
ruhekatyafervent2: is our API in a good shape now?17:35
gokrokveI think we need to convert all existing apps to new DSL.17:35
*** dane_leblanc has joined #openstack-meeting-alt17:35
katyafervent2I think so)17:35
ruhegokrokve: agree17:36
*** eankutse1 has quit IRC17:36
*** eankutse has joined #openstack-meeting-alt17:36
ruhekatyafervent2: good to hear17:36
katyafervent2But need more investigation17:36
ruhegokrokve: i suggest to file a BP to track each existing app conversion to the new DSL17:36
ruhe#action ruhe file a BP to track conversion of existing apps to the new DSL17:37
*** IlyaE has quit IRC17:37
*** mozawa has quit IRC17:37
ruhekatyafervent2: btw, what's your progress with the telnet service?17:37
katyafervent2I can't check the deploy due to blocking issues17:38
*** khyati has joined #openstack-meeting-alt17:38
*** stannie has quit IRC17:38
katyafervent2Hope tomorrow I'll do it, because telnet package is ready17:38
sergmelikyanI will publish fixes for all found bugs tomorrow, I was able today finish deployemnt of Tomcat - Postgresql17:39
ruhesergmelikyan: woohoo!17:39
*** _nadya_ has joined #openstack-meeting-alt17:39
ruhe#info sergmelikyan successfully ran deployment of Tomcat/Postgres example17:40
*** aratim has quit IRC17:40
*** mozawa_ has joined #openstack-meeting-alt17:40
*** mozawa_ is now known as mozawa17:40
ruheso far we identified three critical items for 0.5:17:40
ruhe1. advanced networking17:41
ruhe2. convert existing apps the new DSL17:41
ruhe3. i need to work on my math17:41
*** overlayer has joined #openstack-meeting-alt17:41
tsufiev:)17:42
*** michael-yu has quit IRC17:42
ruheanything else?17:42
ruheall right, we're open for open discussion17:42
ruhe#topic Open Discussion17:42
*** openstack changes topic to "Open Discussion (Meeting topic: murano)"17:42
ruhei can give an update on the config generation/checking17:43
ruhehere is the patch:17:43
ruhe#link https://review.openstack.org/#/c/85855/17:43
*** balajiiyer has joined #openstack-meeting-alt17:43
ruheit'll allow us to generate sample config from the code17:43
ruheand always make sure that the sample config is synced with configs declared in the code17:44
*** sarob has joined #openstack-meeting-alt17:44
tsufievspeaking of the reviews...17:44
ruheand i'd like to remove SSL configs from heat,keystone,neutron block and keep is in a single [ssl] block17:44
tsufievguys, don't forget to review regularly, patches are not going to merge themselves :)17:44
sjmc7i can help with reviews for 0.5. our team is getting up to speed, should be starting to look at low hanging fruit bugs end of this week or beginning of next17:45
*** amotoki_ has quit IRC17:45
ruhesjmc7: thank you. we're constantly behind desired pace in dashboard reviews17:45
tsufievsjmc7: it would be great! btw, we already have plenty of low-hanging-fruits for dashboard17:45
*** IlyaE has joined #openstack-meeting-alt17:46
sjmc7tsufiev - splendid. if they're tagged, we'll pick them up17:46
ruhesergmelikyan: what do you think about moving all the SSL-related configs to a single block [ssl] ?17:46
sergmelikyanruhe, negative17:46
*** eankutse1 has joined #openstack-meeting-alt17:46
ruhesergmelikyan: you can find it in the bottom of https://review.openstack.org/#/c/85855/6/etc/murano/murano-api.conf.sample17:46
tsufievsjmc7: https://bugs.launchpad.net/murano/+bugs?field.tag=low-hanging-fruit17:46
*** michael-yu has joined #openstack-meeting-alt17:46
sergmelikyanruhe they are different settings for different services, I don't quite get how do you plan to combine them17:47
sjmc7tsufiev - yep. still getting dev environments set up, but we'll start on them asap17:47
ruhesergmelikyan: i would expect all the openstack services to use the same SSL keys within the same installation17:47
sergmelikyanO.o17:48
tsufievsjmc7: do you have any difficulties with setting dev envs up? we could help17:48
sjmc7tsufiev - a couple, but we've worked around/filed bugs. we'll ask if we need help. people are still learning the language and environment, taking some time17:49
*** beyounn has joined #openstack-meeting-alt17:49
tsufievsjmc7: ok, feel free to ask :)17:49
*** eankutse has quit IRC17:49
ruhetsufiev: that's something i'd like to improve before the relase. we don't have much developer docs atm. i'd like to add as much as possible and publish them to http://murano-api.readthedocs.org/en/latest/17:49
ruhesergmelikyan: seems i said something stupid, let's discuss in #murano :)17:50
sergmelikyanruhe, I am not sure that this is right thing to do, since different services may have been accessible from different endpoint types with different configurations. Why are trying to restrict them to use only same settings? This will mean that cloud where each service has own certificated will not be supported (murano would not work)17:50
*** colinmcnamara has quit IRC17:50
sergmelikyanok :)17:50
*** mfer has quit IRC17:51
*** bcrochet has left #openstack-meeting-alt17:51
tsufievsjmc7: yes, we're working on that. katyafervent2 is currently adding some docs to wiki: https://wiki.openstack.org/wiki/Murano/Documentation/How_to_create_application_package17:51
sjmc7ruhe - +1 for developer docs, there're lots of bits out of date17:51
ruhesergmelikyan: i guess we need to speak with folks who run production clouds17:51
sjmc7ok, great. i'll keep an eye out17:51
*** _nadya_ has quit IRC17:51
*** eankutse1 has quit IRC17:51
sjmc7ruhe - i can ask our public cloud folks?17:51
*** mfer has joined #openstack-meeting-alt17:52
*** eankutse has joined #openstack-meeting-alt17:52
tsufievruhe: oops, i confused your message with sjmc7's one :)17:52
tsufievruhe: anyway, we should move docs from wiki to readthedocs asap17:52
katyafervent2and from docbook too?17:53
ruhekatyafervent2: docbook is for user docs17:53
katyafervent2ok, so user guide will live there17:53
ruhesjmc7: that would be great17:53
*** yogesh has joined #openstack-meeting-alt17:53
*** arnaud has joined #openstack-meeting-alt17:53
sjmc7ruhe - maybe let me know after this exactly what the question is17:54
ruhesjmc7: sure17:54
sergmelikyanruhe, we had same settings for all services for one of the customers, but not on public cloud, since on public cloud they planned to not have wildcard certificates and disable insecure option17:54
ruhekatyafervent2: right. i'd like to move user docs from murano-docs to murano-api (which will be renamed to murano). but i need to convince sergmelikyan first :)17:54
akuznetsova_katyafervent2: i can help with user giude updating17:54
katyafervent2akuznetsova_: it would be great17:55
slagunsjmc7,you can take Heat's approach to clients' setting configuration as a reference17:55
sergmelikyanruhe, you don't need to convince me :) I think developers docs should be for developers (in murano-api repo in ReST), but manuals and guides in docbook and in different repo. Just as Openstack itself does.17:55
*** malini is now known as malini_afk17:56
sergmelikyanWe don't want to rewrite them to docbook once we integrated, are we? )17:56
ruhesergmelikyan: i want to keep user docs in docbook, but move them under murano-api to simplify the release process17:56
ruhethe same way we're moving tests and deployment scripts under murano-api17:57
sergmelikyanruhe, no objections here, but I don't think that moving all staff to single repo, where root of the python package is located is a good thing to do. We need to make sure that murano-api will not turn to mess.17:58
*** jprovazn has joined #openstack-meeting-alt17:58
akuznetsova_ruhe: do you want to move all tests to murano-api repo?17:58
ruheakuznetsova_: yes17:58
tsufievone repo to rule them all :)17:58
ruhespeaking of the developer docs, i will take an action item to setup everything necessary for  docs: a job to build them and to push to to readthedocs17:59
*** pbelanyi_ has joined #openstack-meeting-alt17:59
ruhe#action ruhe setup infrastructure for dev-docs building and publishing17:59
ruhelast minute17:59
ruheanything worth mentioning?17:59
*** matty_dubs has joined #openstack-meeting-alt18:00
*** marun has joined #openstack-meeting-alt18:00
ruhethanks everyone!18:00
ruhe#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Tue Apr 15 18:00:40 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-04-15-17.03.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-04-15-17.03.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/murano/2014/murano.2014-04-15-17.03.log.html18:00
*** sjmc7 has left #openstack-meeting-alt18:00
katyafervent2Bye!18:01
*** malini_afk is now known as malini18:01
*** akuznetsova_ has quit IRC18:01
*** bcrochet has joined #openstack-meeting-alt18:03
*** btully has left #openstack-meeting-alt18:03
*** eguz has quit IRC18:03
*** eghobo has joined #openstack-meeting-alt18:04
*** gokrokve_ has joined #openstack-meeting-alt18:08
*** bcrochet has left #openstack-meeting-alt18:08
*** jswarren_ has quit IRC18:09
*** rpodolyaka1 has joined #openstack-meeting-alt18:10
*** mozawa has quit IRC18:11
*** gokrokve has quit IRC18:12
*** ankurrr has left #openstack-meeting-alt18:14
*** CristianF has quit IRC18:17
*** sarob has quit IRC18:17
*** sarob has joined #openstack-meeting-alt18:17
*** dane_leblanc has quit IRC18:18
*** demorris has joined #openstack-meeting-alt18:19
*** pbelanyi_ has quit IRC18:22
*** sarob has quit IRC18:22
*** _nadya_ has joined #openstack-meeting-alt18:25
*** balajiiyer has quit IRC18:26
*** mat-lowery has joined #openstack-meeting-alt18:26
*** gokrokve_ has quit IRC18:30
*** sarob has joined #openstack-meeting-alt18:30
*** balajiiyer has joined #openstack-meeting-alt18:32
*** nati_uen_ has quit IRC18:32
*** balajiiyer has quit IRC18:32
*** balajiiyer has joined #openstack-meeting-alt18:32
*** nati_ueno has joined #openstack-meeting-alt18:33
*** gokrokve has joined #openstack-meeting-alt18:35
*** jdob_ has joined #openstack-meeting-alt18:35
*** nati_ueno has quit IRC18:35
*** aratim has joined #openstack-meeting-alt18:36
*** aratim has left #openstack-meeting-alt18:36
*** nati_ueno has joined #openstack-meeting-alt18:36
*** mozawa has joined #openstack-meeting-alt18:37
*** nati_ueno has quit IRC18:39
*** gokrokve has quit IRC18:39
*** Sukhdev has joined #openstack-meeting-alt18:40
*** michael-yu has quit IRC18:40
*** mozawa has quit IRC18:41
*** katyafervent2 has quit IRC18:43
*** michael-yu has joined #openstack-meeting-alt18:46
*** _nadya_ has quit IRC18:47
*** denis_makogon has joined #openstack-meeting-alt18:48
*** lsmola2 has joined #openstack-meeting-alt18:48
*** julienvey has quit IRC18:51
*** morazi has joined #openstack-meeting-alt18:52
*** julienve_ has joined #openstack-meeting-alt18:54
*** julienve_ has quit IRC18:54
*** nwidell has joined #openstack-meeting-alt18:55
*** nwidell has quit IRC18:55
*** overlayer has quit IRC18:57
*** tzumainn has joined #openstack-meeting-alt18:57
*** mozawa has joined #openstack-meeting-alt18:58
*** baoli_ has quit IRC18:59
*** tchaypo has joined #openstack-meeting-alt19:00
*** Ng has joined #openstack-meeting-alt19:00
*** ccrouch has joined #openstack-meeting-alt19:00
*** gokrokve has joined #openstack-meeting-alt19:01
jdobo/19:02
matty_dubs\o19:02
shadowerhola19:02
* shadower is such a rebel19:02
jdobthat's like a high five that we missed matty_dubs19:02
GheRiverohi19:02
rpodolyaka1o/19:02
matty_dubslol19:02
jomara\/\/o/\/\19:02
matty_dubsIs this where I get me some tripleos?19:02
jomara yes19:02
bnemecFor anyone who didn't see it, lifeless is looking for someone to run the meeting.19:03
*** nati_ueno has joined #openstack-meeting-alt19:03
shadoweroh19:03
* bnemec looks at SpamapS, slagle, and derekh19:03
tzumainnHI!19:03
bnemecExcept no derekh. :-)19:03
*** mat-lowery has left #openstack-meeting-alt19:04
tzumainnanyone have a pokeball with a core trapped inside?19:04
jdobtzumainn: perhaps a Endpoing?19:04
*** baoli has joined #openstack-meeting-alt19:04
tzumainnlol19:04
slagle#startmeeting tripleo19:05
openstackMeeting started Tue Apr 15 19:05:19 2014 UTC and is due to finish in 60 minutes.  The chair is slagle. Information about MeetBot at http://wiki.debian.org/MeetBot.19:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:05
tchaypoYou're all so witty. Clearly you've had time to pre-caffeinate.19:05
*** openstack changes topic to " (Meeting topic: tripleo)"19:05
openstackThe meeting name has been set to 'tripleo'19:05
slagleHi everyone!19:05
Ngo./19:05
jdobo/19:05
bnemeco/19:05
*** sarob has quit IRC19:05
dprincehello19:05
jomaraahoy19:05
GheRiveroo/19:05
slagle#topic agenda19:06
*** openstack changes topic to "agenda (Meeting topic: tripleo)"19:06
SpamapShalf here19:06
*** sarob has joined #openstack-meeting-alt19:06
slagle*  bugs19:06
slagle* reviews19:06
slagle*  Projects needing releases19:06
SpamapSon vacation.. but vacation w/ excellent wifi.. :-P19:06
slagle*  CD Cloud status19:06
*** greghaynes has joined #openstack-meeting-alt19:06
slagle*  CI19:06
slagle*   Insert one-off agenda items here19:06
jcoufalo/19:06
slaglegood grief19:06
marioso/ sorry a bit late19:06
slaglei am incapable of copy/pasting the agenda apparently19:06
greghaynesO\19:07
bnemec:-)19:07
slagle#topic bugs19:07
*** openstack changes topic to "bugs (Meeting topic: tripleo)"19:07
slagle#link https://bugs.launchpad.net/tripleo/19:07
slagle#link https://bugs.launchpad.net/diskimage-builder/19:07
slagle#link https://bugs.launchpad.net/os-refresh-config19:07
slagle#link https://bugs.launchpad.net/os-apply-config19:07
slagle#link https://bugs.launchpad.net/os-collect-config19:07
slagle#link https://bugs.launchpad.net/tuskar19:07
slagle#link https://bugs.launchpad.net/python-tuskarclient19:07
slaglewe have some untriaged bugs...19:08
slagle4 in tripleo19:08
*** mozawa has quit IRC19:09
tchaypoI see 4 incomplete, but only one new19:09
slaglecan someone pick those up and triage?19:09
*** sreshetnyak has quit IRC19:09
slaglenone appear critical to me19:09
tchaypoI thought the incomplete ones are considered triaged?19:10
*** sarob has quit IRC19:10
slaglenot sure what the stance on that is19:10
lsmola2hello19:10
slaglei like to see an Importance on there19:10
slaglealthough, if incomplete, that can be hard to determine19:11
*** jdob_ has quit IRC19:11
slaglei don't see any other untriaged in the other projects19:12
tchaypoThat seems reasonable - we should at least be able to figure out what the priority would be if we get the data to support the reported bug19:12
slagletchaypo: indeed, i'm just thinking...if it's not something that reproduces, thus we need more info, etc, it's not likely critical19:13
slaglei don't see any unassigned critical bugs19:13
slagleanyone have anything to discuss about those?19:14
slagleor other bug business for that matter?19:14
slagleexcellent! everyone agrees to fix all open bugs19:14
slaglemoving on19:14
slagle#topic reviews19:14
*** openstack changes topic to "reviews (Meeting topic: tripleo)"19:14
slagle#link http://www.russellbryant.net/openstack-stats/tripleo-openreviews.txt19:15
slaglethis was a big topic last week19:15
slaglearound the backlog of reviews related to exposing configuration19:15
slaglei did not see the proposed patches for a configuration pass through?19:15
slagledid i miss it?19:16
dprinceslagle: I volunteered to help but was told Steve K was working on it19:16
dprincelifeless: can you confirm someone is working on a pass through option?19:16
slaglecould be worth following up on the ML about the status on that19:16
dprincelifeless: not trying to point any fingers... but would like to not duplicate effort as well19:16
bnemeclifeless is out for the beginning of the meeting.  Maybe ask him when he gets here.19:17
slaglesince he's gone, i'll action him19:17
*** nati_ueno has quit IRC19:17
slagle#action lifeless provide status update on config pass though19:17
dprinceslagle: that was the last I heard anyways, we (someone) needs to implement a pass through option19:17
slagleright, i thought it was coming "today or tomorrow" last tuesday19:17
tchaypoI've been poking at the problem; it's interesting as a learning exercise19:17
slaglei did see the patch for the os-apply-config override templates19:18
slaglemaybe that was it? dunno for sure19:18
* bnemec thinks we should wait for lifeless and revisit this19:18
tchaypoBut I have no objection to someone who already understands the space jumping in19:18
slaglebnemec: indeed19:18
tchaypoI'm fairly sure stevenk hasn't had time to look at it19:19
slagleso, we continue to slip on reviews, but i think this is directly related to everyone agreeing not really to review the outstanding config changes last week19:19
*** betsy has joined #openstack-meeting-alt19:19
slagle--> Stats since the last revision without -1 or -2 :19:19
slagle----> Average wait time: 6 days, 8 hours, 19 minutes19:19
mariosworth noting that the tht reviews are blocked waiting for the software config worke19:19
bnemecYeah, it's hard to tell.  At least half of the longest waiting reviews are config options.19:19
*** mozawa has joined #openstack-meeting-alt19:19
slaglemarios: yes, and SpamapS is on vacation19:19
slaglei do think the software-config support is really high priority for the templates19:20
slagleany volunteers to help tests SpamapS's patches that are out there?19:20
shadowerhere19:20
jprovaznyes19:20
jprovaznI was trying them today19:20
shadowerbeen loo,king into it anyway19:20
slaglecool, i saw you guys were looking at it :)19:20
jprovaznseemed to work fine for me19:20
slaglethe more folks that jump in and test, the faster that will go19:20
greghaynesYep, are all the os-c-c patches needed for it now merged?19:21
shadowerthe occ patches blocking this just landed19:21
shadowerwe need a release19:21
greghaynesw00t19:21
jprovaznbut I still didn't finish reading through them to the end and understand it completely :)19:21
lsmola2I will test it too19:21
slaglelsmola2: thanks!19:21
slagleany other review business?19:21
jprovaznjust a nit19:22
slagleif you're waiting on reviews...don't be shy about pinging cores in #tripleo19:22
shadoweryeah19:22
slagledon't want to see folks blocked given the backlog19:22
jprovaznreview stats might be also worse because bunch of reviews are still waiting on success gating tests19:22
shadowerjprovazn: shouldn't that just affect approvals?19:22
jprovaznshadower, yes19:23
slaglejprovazn: true, but that doesn't affect all the stats about feedback19:23
jprovaznah, right19:23
*** sarob has joined #openstack-meeting-alt19:23
slagleany other review business?19:23
slagle#topic releases19:24
*** openstack changes topic to "releases (Meeting topic: tripleo)"19:24
slaglei don't mind releasing again this week19:24
rpodolyaka1slagle feel free to give this to me, if you are busy :)19:24
slagleon a related topic, we are still waiting on some acl overrides in gerrit for commit access to the stable branches19:24
lifelesso/ am here now :). not taking over but just able to participate :)19:24
slaglerpodolyaka1: i can handle for now :). thx though!19:25
*** Barker has quit IRC19:25
slagle#topic CD Cloud Status19:26
*** openstack changes topic to "CD Cloud Status (Meeting topic: tripleo)"19:26
shadowerslagle: so the software config t-h-t patch depends on os-*-config changes that just landed. Would you let me know once the release is out?19:26
slagleshadower: yes, will do19:26
*** Barker has joined #openstack-meeting-alt19:26
shadowerthanks19:26
slagleshadower: will aim to do that one this afternoon19:26
shadowercool, I'll pikc it up in EU morning then19:26
slaglei'm not actually sure what the status of the CD cloud is. i suspect unchanged from last week19:26
*** Barker has quit IRC19:27
slagle#topic CI19:27
*** openstack changes topic to "CI (Meeting topic: tripleo)"19:27
slaglei think stuff is passing now19:27
slagleafter the nova fixes from yesterday19:28
slaglei'm not sure of the details on that19:28
slaglei don't think derekh is here19:28
lifelesshe's not19:28
lifelessI think we should be able to remove his bandaid too19:28
slaglei've seen successful runs from this afternoon19:29
slagleif you have patches that need to be rechecked, plz do so19:29
lifelessdansmith landed a patch that broke bare use of the metadata server without nova-network; its been reverted19:29
*** julienvey has joined #openstack-meeting-alt19:30
slaglelifeless: i already see a revert for the bandaid https://review.openstack.org/#/c/87354/19:30
slaglealthough...it failed CI :/19:31
slaglelikely unrelated19:31
slagleanywho, that is in flight19:31
dprinceslagle: I plan on looking at it..19:31
slagledprince: thx!19:31
slagleother CI business?19:31
*** Barker has joined #openstack-meeting-alt19:31
slagledprince: how goes the reliability of the f20 job?19:32
dprinceslagle: seems like it is doing better to me. although still slowish on resources19:32
slaglei know derek was looking into an issue with nodepool not spinning up fedora nodes19:32
dprinceslagle: yes19:32
*** colinmcnamara has joined #openstack-meeting-alt19:32
slaglek19:33
slagle#topic open discussion19:33
*** openstack changes topic to "open discussion (Meeting topic: tripleo)"19:33
slaglelifeless: do you have an update on the config pass through proposal from last week?19:33
lifelesssomewhat19:33
lifelesstchaypo has been poking at it19:33
lifelessand I've now cleared my plate - I'll be doing that and only that today19:33
slaglek, cool19:34
lifelesshttp://lists.openstack.org/pipermail/openstack-dev/2014-April/032768.html <- would like thoughts on this19:34
greghaynesIs the plan to then pick some subset of the config change reviews as things we want to expose? Curious if therse some criteria for what we want to do as passthrough and what we dont19:35
greghaynesmakes it hard to give any review on those otherwise19:35
lifelessgreghaynes: indeed, so I think we need a layer cake doc19:35
lifelesswe describe in the overall design the different tools etc19:36
lifelessbut we don't talk about what not to expose, because there has until now never been a choice19:36
greghaynesdoc sounds good. Do we err on the side of accepting those reviews as well (if they are fine otherwise)?19:37
tchaypolifeless: I'll talk to you after the meeting about where I'm at.19:37
lifelesstchaypo: cool, thanks!19:37
lifelessgreghaynes: I think not. Like spamaps big patchset, this is going to be hugely hard if lots of little dribs and drabs are landing19:37
greghaynesah, right.. and theres more of that incoming19:38
SpamapSI think the things to expose are the things that would be hard to do with the manual injection.19:39
lifelessor anything that involves a derivation process19:39
slaglelifeless: so the gist of the nova spec proposal is: you submit a review with a spec/design doc. people review the commit as usual, provide feedback etc. then spec gets committed ?19:39
lifelessbut there are two layers19:39
lifelessat the TIE layer, we'll be making things more generic19:39
*** chandan_kumar has joined #openstack-meeting-alt19:39
lifelessat the THT layer we'll be modelling the conf files and then exposing is choosing to make it a parameter vs part of the passthrough json19:39
lifelessslagle: yes, and blueprints are created at the end of that process19:40
slagleok, i think it could work and like the idea19:40
*** malini is now known as malini_afk19:40
lifelessso for instance, for the passthrough stuff; we'd write a doc in incubator/doc/source/designs/passthough_config.rst19:40
bnemecI'm +1 on spec reviews, but last I heard they were still iterating on the nova process and wanted to finish that before applying it to other projects.19:41
lifelessthere's no reason we can't start ourselves19:41
bnemecAlthough if we put our spec reviews directly in incubator that might help.  Part of it was they didn't want a bunch of infra churn if things changed.19:41
slagleyea, let's be trendsetters19:41
lifelessthey aren't in a position to say 'this is what everyone should do' yet is all19:42
lifelesswhich really, thats a TC call19:42
ccrouchdo they have some sort of folder/naming convention so we dont end up with a sea of notstarted/completed/inprogress/abandoned designs ?19:42
ccrouchmaybe we just want a folder per cycle?19:42
lifelessGood question; perhaps wait and see?19:43
slagleyea, and more real time status will be tracked in the blueprint i suspect19:43
*** mozawa has quit IRC19:43
*** gyee has quit IRC19:43
ccrouchtrue19:43
slagleoh, before i forget, everyone please submit your design session proposals for Atlanta before Friday19:44
slagle#link http://summit.openstack.org/19:44
slagleany other business or shall we end early?19:45
*** venkatesh has quit IRC19:45
slagleguess not! bye folks! c ya in #tripleo19:45
slagle#endmeeting19:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:45
openstackMeeting ended Tue Apr 15 19:45:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-04-15-19.05.html19:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-04-15-19.05.txt19:45
openstackLog:            http://eavesdrop.openstack.org/meetings/tripleo/2014/tripleo.2014-04-15-19.05.log.html19:45
*** greghaynes has left #openstack-meeting-alt19:46
*** tzumainn has left #openstack-meeting-alt19:46
lsmola2thanks, have a great week19:46
*** jprovazn has left #openstack-meeting-alt19:46
jomaralater guys19:46
*** Ng has left #openstack-meeting-alt19:47
*** matty_dubs has left #openstack-meeting-alt19:47
*** chandan_kumar has quit IRC19:48
*** morazi has left #openstack-meeting-alt19:49
*** colinmcnamara has quit IRC19:51
*** _nadya_ has joined #openstack-meeting-alt19:51
*** eanxgeek is now known as eanxgeek|log19:55
*** ameade has quit IRC19:55
*** chandan_kumar has joined #openstack-meeting-alt19:55
*** marun has quit IRC19:55
*** marun has joined #openstack-meeting-alt19:58
*** mozawa has joined #openstack-meeting-alt20:00
*** rpodolyaka1 has quit IRC20:00
*** markmcclain has joined #openstack-meeting-alt20:01
*** swat30 has quit IRC20:04
*** thurloat has quit IRC20:07
*** nati_ueno has joined #openstack-meeting-alt20:08
*** michael-yu has quit IRC20:09
*** swat30 has joined #openstack-meeting-alt20:09
*** thurloat has joined #openstack-meeting-alt20:11
*** sarob has quit IRC20:12
*** sarob has joined #openstack-meeting-alt20:12
*** nati_ueno has quit IRC20:13
*** sarob has quit IRC20:17
*** chandan_kumar has quit IRC20:18
*** mozawa has quit IRC20:23
*** michael-yu has joined #openstack-meeting-alt20:25
*** nati_ueno has joined #openstack-meeting-alt20:25
*** mozawa has joined #openstack-meeting-alt20:25
*** colinmcnamara has joined #openstack-meeting-alt20:26
*** IlyaE has quit IRC20:33
*** baoli has quit IRC20:33
*** mozawa has quit IRC20:34
*** IlyaE has joined #openstack-meeting-alt20:34
*** betsy_ has joined #openstack-meeting-alt20:35
*** betsy has quit IRC20:36
*** betsy_ is now known as betsy20:36
*** colinmcnamara has quit IRC20:36
*** PeterSchwaller_ has joined #openstack-meeting-alt20:39
*** Sukhdev has quit IRC20:40
*** _nadya_ has quit IRC20:40
*** mozawa has joined #openstack-meeting-alt20:41
*** andreaf has quit IRC20:41
*** PeterSchwaller has quit IRC20:41
*** jcoufal has quit IRC20:44
*** dprince has quit IRC20:48
*** nati_ueno has quit IRC20:48
*** lsmola2 has quit IRC20:48
*** nati_ueno has joined #openstack-meeting-alt20:49
*** mwagner_lap has quit IRC20:50
*** IlyaE has quit IRC20:51
*** sarob has joined #openstack-meeting-alt20:51
*** sarob has quit IRC20:51
*** sarob has joined #openstack-meeting-alt20:51
*** pdmars_ has joined #openstack-meeting-alt20:53
*** pdmars_ has quit IRC20:54
*** pdmars_ has joined #openstack-meeting-alt20:54
*** pdmars has quit IRC20:57
*** gyee has joined #openstack-meeting-alt20:57
*** jdob has quit IRC20:58
*** harlowja_ has quit IRC20:58
*** tchaypo has left #openstack-meeting-alt21:01
*** harlowja has joined #openstack-meeting-alt21:03
*** demorris has quit IRC21:03
*** demorris has joined #openstack-meeting-alt21:03
*** edleafe has left #openstack-meeting-alt21:04
*** julienvey has quit IRC21:09
*** marun has quit IRC21:09
*** eankutse has quit IRC21:10
*** julienvey has joined #openstack-meeting-alt21:16
*** julienvey has quit IRC21:18
*** sarob has quit IRC21:19
*** coolsvap|afk has quit IRC21:25
*** hemanth has quit IRC21:26
*** coolsvap|afk has joined #openstack-meeting-alt21:26
*** nati_ueno has quit IRC21:26
*** hemanth has joined #openstack-meeting-alt21:27
*** IlyaE has joined #openstack-meeting-alt21:29
*** julienvey has joined #openstack-meeting-alt21:31
*** khyati has quit IRC21:34
*** balajiiyer has left #openstack-meeting-alt21:35
*** Obulpathi has quit IRC21:35
*** nati_ueno has joined #openstack-meeting-alt21:36
*** sbalukoff has quit IRC21:36
*** sbalukoff has joined #openstack-meeting-alt21:40
*** julienvey has quit IRC21:43
*** mfer has quit IRC21:46
*** garyduan has quit IRC21:46
*** Barker has quit IRC21:47
*** khyati has joined #openstack-meeting-alt21:49
*** sarob has joined #openstack-meeting-alt21:50
*** noslzzp has joined #openstack-meeting-alt21:51
*** marun has joined #openstack-meeting-alt21:53
*** mozawa has quit IRC21:57
*** arnaud has quit IRC21:57
*** nati_ueno has quit IRC21:58
*** nati_ueno has joined #openstack-meeting-alt21:58
*** kevinconway has quit IRC22:02
*** harlowja has quit IRC22:03
*** denis_makogon has quit IRC22:04
*** david_lyle_ has joined #openstack-meeting-alt22:04
*** harlowja has joined #openstack-meeting-alt22:05
*** nati_ueno has quit IRC22:05
*** david-lyle has quit IRC22:07
*** yogesh has quit IRC22:10
*** arnaud has joined #openstack-meeting-alt22:11
*** AlanClark has quit IRC22:12
*** nati_ueno has joined #openstack-meeting-alt22:23
*** noslzzp has quit IRC22:25
*** overlayer has joined #openstack-meeting-alt22:25
*** flaper87 is now known as flaper87|afk22:29
*** markmcclain has quit IRC22:32
*** betsy has quit IRC22:33
*** Haiying has joined #openstack-meeting-alt22:34
*** noslzzp has joined #openstack-meeting-alt22:36
*** spzala has quit IRC22:36
*** sarob has quit IRC22:37
*** sarob has joined #openstack-meeting-alt22:37
*** yogesh has joined #openstack-meeting-alt22:39
*** MarkAtwood has quit IRC22:40
*** amytron has quit IRC22:41
*** sarob has quit IRC22:42
*** amytron has joined #openstack-meeting-alt22:42
*** amytron has quit IRC22:47
*** demorris has quit IRC22:55
*** Haiying has quit IRC22:56
*** mozawa has joined #openstack-meeting-alt22:56
*** david_lyle_ has quit IRC22:57
*** mozawa has quit IRC22:59
*** marun has quit IRC22:59
*** Haiying has joined #openstack-meeting-alt23:02
*** yogesh has quit IRC23:03
*** khyati has quit IRC23:03
*** mwagner_lap has joined #openstack-meeting-alt23:04
*** noslzzp has quit IRC23:05
*** Leonr has quit IRC23:08
*** marun has joined #openstack-meeting-alt23:10
*** rueb7363 has quit IRC23:10
*** eankutse has joined #openstack-meeting-alt23:10
*** IlyaE has quit IRC23:15
*** nati_ueno has quit IRC23:15
*** eguz has joined #openstack-meeting-alt23:16
*** eguz has quit IRC23:16
*** eguz has joined #openstack-meeting-alt23:16
*** pdmars_ has quit IRC23:19
*** nati_uen_ has joined #openstack-meeting-alt23:20
*** eghobo has quit IRC23:20
*** demorris has joined #openstack-meeting-alt23:20
*** sarob has joined #openstack-meeting-alt23:21
*** gokrokve has quit IRC23:24
*** eguz has quit IRC23:24
*** sarob has quit IRC23:26
*** eghobo has joined #openstack-meeting-alt23:28
*** vkmc has quit IRC23:29
*** openstackstatus has quit IRC23:32
*** openstackstatus has joined #openstack-meeting-alt23:33
*** IlyaE has joined #openstack-meeting-alt23:33
*** eguz has joined #openstack-meeting-alt23:39
*** nosnos has joined #openstack-meeting-alt23:39
*** demorris has quit IRC23:41
*** demorris has joined #openstack-meeting-alt23:42
*** eghobo has quit IRC23:43
*** overlayer has quit IRC23:50
*** jmontemayor has quit IRC23:51
*** sarob has joined #openstack-meeting-alt23:51
*** gokrokve has joined #openstack-meeting-alt23:51
*** gokrokve has quit IRC23:54
*** sarob has quit IRC23:56
*** sarob has joined #openstack-meeting-alt23:57
*** Haiying has quit IRC23:57
*** hemanth has quit IRC23:57
*** mordred has quit IRC23:58
*** mordred has joined #openstack-meeting-alt23:58
*** pdmars has joined #openstack-meeting-alt23:59
*** ChanServ changes topic to "Restarting gerrit really quick to fix replication issue"23:59

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