Thursday, 2014-01-30

*** nati_ueno has quit IRC00:00
*** igor has joined #openstack-meeting-alt00:02
*** nati_ueno has joined #openstack-meeting-alt00:02
*** nati_ueno has quit IRC00:02
*** nati_ueno has joined #openstack-meeting-alt00:03
*** igor has quit IRC00:06
*** IlyaE has joined #openstack-meeting-alt00:13
*** banix has quit IRC00:15
*** colinmcnamara has joined #openstack-meeting-alt00:20
*** gokrokve_ has quit IRC00:36
*** colinmcnamara has quit IRC00:36
*** gokrokve has joined #openstack-meeting-alt00:37
*** colinmcnamara has joined #openstack-meeting-alt00:37
*** sarob has quit IRC00:38
*** sarob has joined #openstack-meeting-alt00:38
*** gokrokve has quit IRC00:41
*** colinmcnamara has quit IRC00:42
*** Sukhdev has joined #openstack-meeting-alt00:46
*** jecarey has quit IRC00:51
*** nati_uen_ has joined #openstack-meeting-alt00:51
*** richm has quit IRC00:52
*** sarob has quit IRC00:54
*** nati_ueno has quit IRC00:54
*** ijw has quit IRC00:55
*** david-lyle has quit IRC00:55
*** flaper87 is now known as flaper87|afk01:00
*** igor has joined #openstack-meeting-alt01:02
*** julim has joined #openstack-meeting-alt01:04
*** nati_uen_ has quit IRC01:07
*** igor has quit IRC01:07
*** nati_ueno has joined #openstack-meeting-alt01:07
*** michael-yu has quit IRC01:10
*** krtaylor has joined #openstack-meeting-alt01:19
*** gokrokve has joined #openstack-meeting-alt01:21
*** michael-yu has joined #openstack-meeting-alt01:25
*** krtaylor has quit IRC01:26
*** lblanchard has joined #openstack-meeting-alt01:26
*** gokrokve has quit IRC01:33
*** gokrokve has joined #openstack-meeting-alt01:33
*** colinmcnamara has joined #openstack-meeting-alt01:35
*** mozawa has joined #openstack-meeting-alt01:36
*** gokrokve has quit IRC01:38
*** lblanchard has quit IRC01:38
*** nosnos has joined #openstack-meeting-alt01:38
*** yamahata has joined #openstack-meeting-alt01:40
*** banix has joined #openstack-meeting-alt01:42
*** mestery_ has joined #openstack-meeting-alt01:45
*** markwash has joined #openstack-meeting-alt01:48
*** michael-yu has quit IRC01:48
*** mestery has quit IRC01:48
*** kraman has quit IRC01:54
*** malini_afk has quit IRC01:57
*** malini_afk has joined #openstack-meeting-alt01:59
*** malini_afk is now known as malini01:59
*** gokrokve has joined #openstack-meeting-alt02:01
*** igor has joined #openstack-meeting-alt02:03
*** igor has quit IRC02:08
*** sbalukoff has quit IRC02:11
*** gokrokve has quit IRC02:13
*** colinmcnamara has quit IRC02:25
*** markvoelker has quit IRC02:28
*** yamahata has quit IRC02:32
*** yamahata has joined #openstack-meeting-alt02:37
*** markwash has quit IRC02:45
*** nati_uen_ has joined #openstack-meeting-alt02:45
*** Sukhdev has quit IRC02:46
*** jcooley_ has quit IRC02:47
*** nati_ueno has quit IRC02:48
*** nati_uen_ has quit IRC02:50
*** colinmcnamara has joined #openstack-meeting-alt02:53
*** sarob has joined #openstack-meeting-alt02:57
*** gokrokve has joined #openstack-meeting-alt03:01
*** colinmcnamara has quit IRC03:03
*** sarob has quit IRC03:04
*** igor has joined #openstack-meeting-alt03:04
*** igor has quit IRC03:09
*** krtaylor has joined #openstack-meeting-alt03:12
*** amcrn has quit IRC03:14
*** markwash has joined #openstack-meeting-alt03:19
*** mestery_ is now known as mestery03:21
*** david-lyle has joined #openstack-meeting-alt03:23
*** coolsvap_away has quit IRC03:27
*** jcooley_ has joined #openstack-meeting-alt03:27
*** jcooley_ has quit IRC03:34
*** jcooley_ has joined #openstack-meeting-alt03:35
*** chandankumar_ has joined #openstack-meeting-alt03:36
*** colinmcnamara has joined #openstack-meeting-alt03:38
*** markwash has quit IRC03:38
*** chandankumar_ has quit IRC03:40
*** jcooley_ has quit IRC03:40
*** chandankumar_ has joined #openstack-meeting-alt03:41
*** leizhang has joined #openstack-meeting-alt03:44
*** markwash has joined #openstack-meeting-alt03:45
*** chandankumar_ has quit IRC03:46
*** chandankumar__ has joined #openstack-meeting-alt03:47
*** chandankumar__ has left #openstack-meeting-alt03:50
*** sarob has joined #openstack-meeting-alt04:01
*** leizhang has quit IRC04:01
*** markwash has quit IRC04:02
*** colinmcnamara has quit IRC04:03
*** aignatov_ is now known as aignatov04:04
*** igor has joined #openstack-meeting-alt04:05
*** sarob has quit IRC04:06
*** michael-yu has joined #openstack-meeting-alt04:07
*** igor has quit IRC04:09
*** jcooley_ has joined #openstack-meeting-alt04:10
*** jcooley_ has quit IRC04:16
*** jcooley_ has joined #openstack-meeting-alt04:17
*** jcooley_ has quit IRC04:21
*** jcooley_ has joined #openstack-meeting-alt04:22
*** kraman has joined #openstack-meeting-alt04:22
*** akuznetsov has joined #openstack-meeting-alt04:26
*** jjmb has joined #openstack-meeting-alt04:35
*** bdpayne has joined #openstack-meeting-alt04:36
*** arnaud has quit IRC04:44
*** arnaud__ has quit IRC04:44
*** aignatov is now known as aignatov_04:50
*** mattgriffin has quit IRC04:59
*** sarob has joined #openstack-meeting-alt05:04
*** igor has joined #openstack-meeting-alt05:05
*** igor has quit IRC05:10
*** sarob has quit IRC05:11
*** akuznetsov has quit IRC05:13
*** SergeyLukjanov_ is now known as SergeyLukjanov05:15
*** gokrokve has quit IRC05:16
*** gokrokve has joined #openstack-meeting-alt05:17
*** coolsvap has joined #openstack-meeting-alt05:19
*** banix has quit IRC05:19
*** Ranjitha has quit IRC05:20
*** michael-yu has quit IRC05:21
*** gokrokve has quit IRC05:21
*** Leon has joined #openstack-meeting-alt05:24
*** Leonr has quit IRC05:25
*** Leon is now known as Guest4506605:25
*** akuznetsov has joined #openstack-meeting-alt05:26
*** rwsu has quit IRC05:27
*** mahipal has joined #openstack-meeting-alt05:31
*** arborism has joined #openstack-meeting-alt05:32
*** arborism is now known as amcrn05:34
*** akuznetsov has quit IRC05:37
*** irenab has joined #openstack-meeting-alt05:38
*** michael-yu has joined #openstack-meeting-alt05:38
*** jtomasek has quit IRC05:42
*** itzikb has joined #openstack-meeting-alt05:44
*** Guest45066 has quit IRC05:56
*** Leonr has joined #openstack-meeting-alt05:57
*** DinaBelova_ is now known as DinaBelova06:01
*** DinaBelova is now known as DinaBelova_06:04
*** Leonr has quit IRC06:05
*** igor has joined #openstack-meeting-alt06:06
*** sarob has joined #openstack-meeting-alt06:07
*** igor has quit IRC06:11
*** denis_makogon_ has joined #openstack-meeting-alt06:11
*** sarob has quit IRC06:11
*** mattgriffin has joined #openstack-meeting-alt06:12
*** bdpayne has quit IRC06:14
*** akuznetsov has joined #openstack-meeting-alt06:15
*** akuznets_ has joined #openstack-meeting-alt06:18
*** bdpayne has joined #openstack-meeting-alt06:19
*** akuznetsov has quit IRC06:20
*** yjiang5 has joined #openstack-meeting-alt06:27
*** cloudpie has joined #openstack-meeting-alt06:27
*** gokrokve has joined #openstack-meeting-alt06:27
*** yjiang5_1 has quit IRC06:29
*** gokrokve has quit IRC06:31
*** cloudpie has quit IRC06:37
*** DinaBelova_ is now known as DinaBelova06:40
*** nati_ueno has joined #openstack-meeting-alt06:43
*** kraman has quit IRC06:45
*** Sukhdev has joined #openstack-meeting-alt06:47
*** SushilKM has joined #openstack-meeting-alt06:48
*** nati_ueno has quit IRC06:48
*** SergeyLukjanov is now known as SergeyLukjanov_06:52
*** jcooley_ has quit IRC06:59
*** DinaBelova is now known as DinaBelova_06:59
*** jcooley_ has joined #openstack-meeting-alt07:00
*** yogesh has joined #openstack-meeting-alt07:04
*** igor has joined #openstack-meeting-alt07:07
*** sarob has joined #openstack-meeting-alt07:08
*** mattgriffin has quit IRC07:10
*** yogesh has quit IRC07:11
*** igor has quit IRC07:12
*** IlyaE has quit IRC07:14
*** sarob has quit IRC07:15
*** Sukhdev has quit IRC07:15
*** nati_ueno has joined #openstack-meeting-alt07:15
*** jcooley_ has quit IRC07:16
*** igor has joined #openstack-meeting-alt07:17
*** igor has quit IRC07:20
*** khyati_ has quit IRC07:22
*** michael-yu has quit IRC07:23
*** bdpayne has quit IRC07:24
*** kiall has quit IRC07:25
*** GheRivero has quit IRC07:25
*** nati_ueno has quit IRC07:26
*** michael-yu has joined #openstack-meeting-alt07:29
*** michael-yu has quit IRC07:33
*** ijw has joined #openstack-meeting-alt07:37
*** yogesh has joined #openstack-meeting-alt07:39
*** ijw has quit IRC07:41
*** sbalukoff has joined #openstack-meeting-alt07:47
*** flaper87|afk is now known as flaper8707:49
*** jcooley_ has joined #openstack-meeting-alt07:51
*** catheri3 has joined #openstack-meeting-alt07:59
*** catheri3 has left #openstack-meeting-alt08:00
*** NikitaKonovalov_ is now known as NikitaKonovalov08:02
*** jcooley_ has quit IRC08:05
*** sarob has joined #openstack-meeting-alt08:11
*** ttx has quit IRC08:12
*** igor has joined #openstack-meeting-alt08:12
*** igormarnat_ has joined #openstack-meeting-alt08:15
*** julienvey_ has joined #openstack-meeting-alt08:15
*** sarob has quit IRC08:15
*** harlowja is now known as harlowja_away08:18
*** michael-yu has joined #openstack-meeting-alt08:21
*** mattoliverau has quit IRC08:27
*** david-lyle_ has quit IRC08:29
*** lyle has joined #openstack-meeting-alt08:29
*** michael-yu has quit IRC08:32
*** SushilKM has quit IRC08:36
*** SushilKM has joined #openstack-meeting-alt08:37
*** nosnos has quit IRC08:39
*** nosnos has joined #openstack-meeting-alt08:39
*** ijw has joined #openstack-meeting-alt08:40
*** jcooley_ has joined #openstack-meeting-alt08:46
*** nacim has joined #openstack-meeting-alt08:46
*** ttx has joined #openstack-meeting-alt08:47
*** ttx has quit IRC08:47
*** ttx has joined #openstack-meeting-alt08:47
*** ttx has quit IRC08:50
*** ttx has joined #openstack-meeting-alt08:50
*** ttx has quit IRC08:50
*** ttx has joined #openstack-meeting-alt08:50
*** SushilKM has quit IRC08:51
*** ttx has quit IRC08:51
*** ttx has joined #openstack-meeting-alt08:51
*** ttx has quit IRC08:51
*** ttx has joined #openstack-meeting-alt08:51
*** ijw has quit IRC08:52
*** d0ugal has joined #openstack-meeting-alt08:53
*** d0ugal has quit IRC08:53
*** d0ugal has joined #openstack-meeting-alt08:53
*** ijw has joined #openstack-meeting-alt08:53
*** ttx has quit IRC08:56
*** aignatov_ is now known as aignatov08:56
*** ttx has joined #openstack-meeting-alt08:56
*** ttx has quit IRC08:56
*** ttx has joined #openstack-meeting-alt08:56
*** SushilKM has joined #openstack-meeting-alt08:57
*** urvika has joined #openstack-meeting-alt08:59
*** d0ugal has quit IRC09:00
*** jtomasek has joined #openstack-meeting-alt09:01
*** urvika has quit IRC09:04
*** denis_makogon_ has quit IRC09:09
*** safchain has joined #openstack-meeting-alt09:09
*** johnthetubaguy has joined #openstack-meeting-alt09:11
*** johnthetubaguy has quit IRC09:13
*** GheRiver1 has joined #openstack-meeting-alt09:14
*** johnthetubaguy has joined #openstack-meeting-alt09:14
*** GheRiver1 is now known as GheRivero09:16
*** jcooley_ has quit IRC09:16
*** jtomasek has quit IRC09:21
*** derekh has joined #openstack-meeting-alt09:26
*** rsblendido has joined #openstack-meeting-alt09:28
*** rossella_s has joined #openstack-meeting-alt09:28
*** SergeyLukjanov_ is now known as SergeyLukjanov09:36
*** yogesh has quit IRC09:37
*** DinaBelova_ is now known as DinaBelova09:40
*** yamahata has quit IRC09:40
*** NikitaKonovalov is now known as NikitaKonovalov_09:40
*** SergeyLukjanov is now known as SergeyLukjanov_09:40
*** SushilKM has quit IRC09:45
*** DinaBelova is now known as DinaBelova_09:46
*** nosnos has quit IRC09:46
*** nosnos has joined #openstack-meeting-alt09:46
*** nosnos has quit IRC09:47
*** kiall has joined #openstack-meeting-alt10:03
*** jcooley_ has joined #openstack-meeting-alt10:09
*** sarob has joined #openstack-meeting-alt10:12
*** jcooley_ has quit IRC10:14
*** SushilKM has joined #openstack-meeting-alt10:15
*** aignatov is now known as aignatov_10:15
*** aignatov_ is now known as aignatov10:15
*** DinaBelova_ is now known as DinaBelova10:15
*** sarob has quit IRC10:16
*** ijw has quit IRC10:17
*** SergeyLukjanov_ is now known as SergeyLukjanov10:19
*** GheRivero has quit IRC10:20
*** kiall has quit IRC10:21
*** ijw has joined #openstack-meeting-alt10:23
*** d0ugal has joined #openstack-meeting-alt10:28
*** coolsvap has quit IRC10:28
*** aignatov is now known as aignatov_10:31
*** mozawa has quit IRC10:35
*** rohit404 has joined #openstack-meeting-alt10:39
*** yamahata has joined #openstack-meeting-alt10:41
*** DinaBelova is now known as DinaBelova_10:42
*** boris-42 has quit IRC10:54
*** derekh has quit IRC10:58
*** igormarnat_ has quit IRC11:01
*** jcooley_ has joined #openstack-meeting-alt11:02
*** aignatov_ is now known as aignatov11:04
*** igormarnat_ has joined #openstack-meeting-alt11:05
*** sarob has joined #openstack-meeting-alt11:13
*** jcooley_ has quit IRC11:16
*** DinaBelova_ is now known as DinaBelova11:17
*** sarob has quit IRC11:20
*** coolsvap has joined #openstack-meeting-alt11:31
*** jmaron has joined #openstack-meeting-alt11:38
*** HenryG has quit IRC11:48
*** jmaron has quit IRC11:53
*** jtomasek has joined #openstack-meeting-alt11:54
*** nacim has quit IRC12:10
*** sarob has joined #openstack-meeting-alt12:16
*** rohit404 has quit IRC12:17
*** rohit404 has joined #openstack-meeting-alt12:19
*** coolsvap has quit IRC12:20
*** sarob has quit IRC12:22
*** SergeyLukjanov is now known as SergeyLukjanov_12:22
*** david-lyle has quit IRC12:22
*** DinaBelova is now known as DinaBelova_12:24
*** ijw has quit IRC12:25
*** igormarnat_ has quit IRC12:33
*** igormarnat_ has joined #openstack-meeting-alt12:37
*** nacim has joined #openstack-meeting-alt12:43
*** mozawa has joined #openstack-meeting-alt12:46
*** jcooley_ has joined #openstack-meeting-alt12:51
*** katyafervent_awa is now known as katyafervent12:52
*** baoli has joined #openstack-meeting-alt12:55
*** pdmars has joined #openstack-meeting-alt12:57
*** BrianB_ has joined #openstack-meeting-alt12:58
*** d0ugal has quit IRC12:59
baoli#startmeeting PCI Passthrough13:00
openstackMeeting started Thu Jan 30 13:00:29 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
baoliHi13:00
BrianB_Hi13:01
irenabhi13:01
rkukurahi13:01
*** d0ugal has joined #openstack-meeting-alt13:01
baoli#topic neutron BPs for SRIOV13:01
*** d0ugal has quit IRC13:01
*** d0ugal has joined #openstack-meeting-alt13:01
*** openstack changes topic to "neutron BPs for SRIOV (Meeting topic: PCI Passthrough)"13:01
irenablets refine the neutron part first?13:02
baoli#topic vnic_type13:02
*** openstack changes topic to "vnic_type (Meeting topic: PCI Passthrough)"13:02
baoliirenab, go ahead13:02
irenabso for vnic_type we have a bp, and discussion on mailing list where to define it13:02
*** sadasu has joined #openstack-meeting-alt13:03
*** HenryG has joined #openstack-meeting-alt13:03
irenabI think it fit the port binding space13:03
baoliI second it.13:03
*** SushilKM has left #openstack-meeting-alt13:03
rkukuralets resolve top-level vs. binding:profile 1st, then if former, decide which extension13:03
baoliGiven it's functionality, it fits well as binding:vnic_type13:04
irenabbaoli: I also think so, it just require change to CLI/API13:05
rkukuraIs there consensus it needs to be top-level,  and is this due to needing use access?13:05
rkukuras/use/user/13:05
irenabrkukura: do not think so13:05
rkukurairenab: No consensus?13:05
irenabNo for user access, as I said in the mail, he user will set something much more abstract13:06
irenab'high performance ...' NIC13:06
rkukuraI'd be happiest if this we admin-only (in binding:profile) and the user passed something in --nic to nova that resulted in nova setting up binding:profile as admin.13:06
rkukuras/this we/this was/13:07
irenabrkukura: exactly what I have in mind13:07
irenabmay it be admin or network owner?13:07
rkukuraI apologize that I'm not even trying to keep up with the nova side of these discussions13:07
irenabrkukura: I think we should be able to decouple nova and neutron13:08
rkukuraNormally, network owners are normal users, and don't know/see anything internal to the deployment13:08
irenabrkukura: so they won't create neutron port?13:08
rkukuraPlus, we need to make sure its works for normal user whether they are the owner of the network, or someone else owns the network and sets --shared True13:09
baoliif we call it nic_type (instead of vnic_type): virtio/direct/macvtap? would it be less confusing?13:09
*** GheRivero has joined #openstack-meeting-alt13:09
irenabbaoli: do you think user should be able to set it?13:10
*** eggmaster has quit IRC13:10
*** DinaBelova_ is now known as DinaBelova13:10
baoliThe question is that should the user be allowed to choose a virtio port versus sriov port?13:11
rkukuraDo we have a plan in place on the nova side for nova code to set things in binding:profile, or is the idea that users do this manually, and later nova automates it?13:11
irenabyes, or it should be admin choice13:11
sadasuwe were designing for "nova code to set things in binding:profile"13:12
baolirkukura, we did. But due to the discussions we had so far, we changed the course, and decided to work on the neutron port-create first13:12
sadasuand then what baoli said happened13:12
rkukurabaoli: That's what I thought, but we need to know whether we can assume the neutron port-create/port-update is done by nova as admin13:12
irenabrkukura: for vnic_type it will be user choice translated by nova to vnic_type and set on neutron port13:12
baolithat's right, irenab13:13
rkukurairenab: Sounds good, just want to make sure the nova code will make icehouse13:13
*** markvoelker has joined #openstack-meeting-alt13:14
irenabfor icehouse, we do not need nova for vnic_type, we set it on neutron port via port-create13:14
baolirkukura, we are not going to change the nova code/CLI in the initial release13:14
irenaband then use --nic port_id = xxx for novaboot13:14
rkukurairenab: Normal users are not admin13:14
rkukuraDoes this same thing apply to other details like PCI slot, ...?13:15
baolirkukura, so normal users can not choose a virtio port versus a sriov port?13:15
rkukurathe VNIC that the user's VM sees is really a nova concept, not a neutron concept.13:15
irenabPCI slot is not user or admin choice directly, nova allocates it13:15
baolirkukura, nova boot can be used by normal users13:16
rkukurairenab: So in icehouse, will nova store pci_slot in binding:profile (as admin)?13:16
*** yamahata has quit IRC13:16
irenabdepends on baoli's work :-)13:17
rkukurabaoli: I'm not arguing that normal users should not be able to specify the VNIC type, just that they should do this through nova API so that nova does all the right stuff, including what's needed on the neutron port13:17
irenabrkukura: I think we all agree13:18
baolirkukura, following the existing work flow in nova, binding:profile will be set and neutron port-update is called13:18
rkukuraIf we can count on having some nova code in icehouse that creates/updates the neuton port with binding:profile as admin, then I think we just stick with using binding:profile for all this.13:18
*** sarob has joined #openstack-meeting-alt13:19
rkukuraSo my issue with users needing to directly set vnic-type on the neutron port was misguided, right? I was hoping for that answer!13:19
baolirkukura, if a normal user can choose the nic_type from nova boot, why it can't do so in the neutron port-create command?13:20
*** yamahata has joined #openstack-meeting-alt13:20
irenabrkukura: initialy we for icehouse we start with setting vnc_type on neutron port and then run nova-boot13:20
rkukurairenab: Does that same thing apply to the other items (pci slot, ...) that we want to put in binding:profile?13:21
irenabrkukura: only vnic_type13:21
rkukuraSo who sets the others?13:21
irenabrkukura: nova13:21
rkukuraSo if nova sets the others, why can't it also set vnic_type?13:22
rkukuraIs the issue that this would require extending the nova API somehow, and we won't get that in icehouse?13:23
irenabrkukura: to make long story short, currently lack of agreement and time to implement13:23
irenabrkukura: correct13:23
baolirkukura, to use sriov, we need to do this initially: nova boot --flavor m1.large --image <i-uuid> --nic port-id=<port-uuid>13:23
baoliso we have to create a sriov port first13:23
*** d0ugal has quit IRC13:23
rkukuraOk, so normal users need to be able to set vnic_type, so best way forward seems to be to make it top-level13:24
baoliCool, so we'll proceed with that?13:25
rkukuraThen the only question is whether its in the portbindings extension or a different extension13:25
*** jcooley_ has quit IRC13:25
irenabrkukura: I think that normal user will get some abstract definition of nic flavors that precreated by admin, and this will imply vnic_type13:25
*** sarob has quit IRC13:25
rkukurairenab: For icehouse, or later?13:25
irenabrkukura: later13:25
rkukuraAnd where does this "abstract definition" live? In nova eventually?13:26
irenabController13:26
rkukura?13:26
irenablike VM Flavors13:26
rkukuraOh, nova controller?13:26
rkukuraMake sense I think13:26
*** demorris has joined #openstack-meeting-alt13:27
baoliok, back to rkukura's question on the extension13:27
irenabI think the port binding seems the right place to land this13:27
rkukuraSo eventually users won't need to deal with binding:vnic_type directly, so hiding it in portbindings extension is fine with me13:27
irenabrkukura: Cool13:27
baoliok, so the conclusion is that user can now specify vnic_type and it will be stored as binding:vmic_type13:28
irenabso top-level or part of profile on binding, actually depends on how do you plan to deal with profile as part of generic support for ML213:28
irenabsince vnic_type should be checked and stored not on Mech Driver level but on the level on top of it13:29
rkukuraI think baoli is correct because normal users needing access to vnic_type cannot easily be done within binding:profile13:29
irenabso top-lvel on binding extension?13:30
baoliagree13:30
rkukuraI think irenab's BP should cover making the ml2 plugin persist binding:vnic_type13:30
irenabrkukura: agree.13:30
baoliagree13:30
rkukurawith default of virtio13:30
irenabits exactly the code change I shared with you few days13:31
rkukuraand all binding-capable MechanismDrivers should check the value when trying to bind, and act appropriately13:31
irenabso, if we are OK with it, I can complete it and push next week13:31
rkukuraSounds good to me!13:31
rkukuraI'll submit the BP to implement binding:profile in ML2 today, and also push next week13:32
baoliOne question, where vmci_type is persisted?13:32
irenabrkukura: great!13:32
baolis/vmci_type/vnic_type13:32
rkukuraIf vmci_type is in bindng:profile, the ml2 plugin will persist it with my BP13:32
rkukuraI think binding:vnic type would be persisted by ml2 plugin in its port binding table13:33
irenabso the only left on neutron is if we add common utils/driver for SRIOV generic parts to be used by Cisco/Mellanox Mech. Drivers13:33
irenabrkukura: exactly what I had in mind13:33
rkukuraThere's also the binding:vif_details output parameter I'm working with Nachi on, right?13:33
sadasushould vnic_type be part of the vif_details?13:35
*** mestery_ has joined #openstack-meeting-alt13:35
baoliOne more question, would ovs agent be able to see this binding:vmic_type?13:35
irenabsadasu: not, it will be reflected in vif_type13:35
irenabbaoli: agent should not see it13:36
rkukurasadasu: My understanding is that binding:vnic_type is an input param, while binding:vif_details is output13:36
baoliirenab, we talked about running multiple agents in the same time, right?13:36
sadasuwho does the translation from binding_vnic_type to vif_type in vif_details, generic ML2 plugin or specific mech drivers?13:36
irenabbaoli: we can take it offline, I 'll explain how it is resolved in case we have more on agenda13:37
sadasurkukura: but vif_type in vif_details depends on input vnic_type13:37
*** mestery has quit IRC13:37
rkukurabaoli: There is a separate effort to let the bound MD control what gets returned to the agent in the get_device_details RPC13:37
irenabsadasu: I think Mech. Driver13:37
baoliirenab, sure.13:37
rkukurasadasu: Yes, the binding:vif_type attribute is output by the bound MD13:37
sadasuok...13:38
baolifor sriov, do we need anything from binding:vif_details?13:38
irenabrkukura: for PCI details sent via profile, should it be pushed back via vif_details?13:39
rkukuraIsn't this where nova's GenericVIFDriver might get the VLAN to tag the PF with?13:39
sadasuI don't think we need to send the pci address info back via vif_details13:39
rkukurairenab: binding:profile is input to neutron, binding:vif_details is output from neutron13:39
irenabsadasu: it should be available to VIFDriver13:40
baoliSo what would be inside this binding:vif_details for SRIOV?13:40
baoliwould get_port() return binding:profile?13:40
sadasuirenab: agreed. But, since it is already an inout via binding_profile, why do we send it back out ?13:41
rkukuraIn my view each binding:vif_type value will determine what nova's GenericVIFDriver looks for in binding:vif_details. The GenericVIFDriver and the MD that bindings need to agree on how this works.13:41
irenabfor SRIOV MD we have some common part and part that specific for solution. Cisco has profile_id, right?13:42
*** d0ugal has joined #openstack-meeting-alt13:42
rkukuraThe dictionary returned by port-create, port-update, and port-show will contain binding:vnic_type for all users, and for admins will contain binding:vif_type, binding:profile, and binding:vif_details13:42
baolirkukura, I think that it can be done that way. It's just that we need to figure out how much it will impact the existing code, and what would be inside binding:vif_details for SRIOV13:42
sadasurkukura: Ideally, we would need the pci address details and "profile_id" (here profile is a libvirt term) to be part of vif_details13:43
irenabwe may want vlan_id to be there too, since libvirt can set it13:43
sadasuirenab: for me its part of profile_id...but yes...depending on MD functionality13:44
sadasubut the only part I am not clear about is, should pci address be part of vif_details...13:44
baoliOk, sure so we'll set vif_details to includes things like profileid and/or vlan_id13:45
irenabsadasu: agree, but any SRIOV Mech Driver require pci address to be present13:45
rkukuraSeems we need to be working on a concrete proposal regarding what the MDs put in binding:vif_details and how nova's GenericVIFDriver uses binding:vif_type and binding:vif_details13:45
sadasuwe know GebericVIFDriver needs it13:45
irenabrkukura: do you say the binding:profile won't be propagated to VIFDriver?13:45
sadasuwill be able to get it directly from Nova, or should it be part of vif_details?13:46
*** yamahata has quit IRC13:46
baolirkukura, it's something called VIF dictionary13:46
sadasuI don't know implementation of GenericVIFDriver well enough to answer that question myself13:46
baolinova invokes neutron get_port which will return everything13:46
*** yamahata has joined #openstack-meeting-alt13:47
rkukuraI think GenericVIFDriver has admin access to the port, so it should see binding:vif_type, binding:vif_details, and binding:profile13:47
irenabbaoli: not everything is propagated to VIFDriver13:47
baoliirenab, the VIF object13:47
irenabGenericVIFDriver does not call into neutron, it receives what is on VIF object, but not all attributes of port present there13:48
rkukuraWould probably make sense for nova to propagate all the portbindings attributes to the VIF driver13:48
rkukuraincluding the new ones13:48
irenabrkukura: is there a work on nova to support your neutron bp?13:48
baoliWe can take a look at the area13:48
baoli10 more minutes. I'd like to talk about the neutron port-create syntax13:49
rkukuraWe need to look at Nachi's nova patch for binding:vif_security, which I've proposed to rename binding:vif_details, and see if its getting propagated to the VIF driver13:49
irenaband if we need info from profile, need to see that it is availabe to VIF Driver too13:50
baoliirenab, rkukura, how would it look like?13:50
irenabbaoli: to icehouse we need vnic_type and profile_if for port-create, right?13:51
rkukuraI think "neutron port-create --binding:vnic_type sriov ..." would work13:51
baoliirenab, right13:51
irenabso vnic_type is like rkukura said13:51
baolihow about the profileid?13:51
rkukuraIsn't profile_id a key in binding:profile?13:52
irenaband profileid in via --binding:profile type=dict profileid=xxx13:52
rkukuraBut only admins can set binding:profile13:52
baolibefore that, a question is should we make them explicit arguments, rather than unknown arguments? doing a neutron port-create help should display those arguments, right?13:53
*** jdob has joined #openstack-meeting-alt13:54
irenabbaoli: sounds like Juno feature....13:54
rkukurabaoli: I think that is a general question that applies equally to other extensions13:54
sadasuI think it is fine for now to have --binding:profile type=dict profileid=xxx set only by admin users13:54
*** markwash has joined #openstack-meeting-alt13:55
baoliok, we can postpone that to juno13:55
rkukuraIs the profile_id something that the nova code in icehouse could infer from the flavor and set on binding:profile?13:55
baolisadasu, then the port can only be created by an admin?13:55
*** Barker has joined #openstack-meeting-alt13:56
sadasurkukura: no13:56
irenabgreat, so having vnic_type and binding:profile bp, do we need bp for common SRIOV on neutron side?13:56
rkukuraI'm not clear on where a normal user would get values for profile_id?13:56
sadasubaoli: for non admin users a profile_is can be created with the vlian_id borrowed from the network that the port would be attached to13:56
rkukuraNormal users do not know about VLANs13:57
*** zhiyan has joined #openstack-meeting-alt13:57
irenabsadasu: so it won't be set on port-create?13:57
sadasuyes, it won't be set during port create for non-admin userrs13:57
rkukuraWhat is the purpose of this profile_id?13:57
irenabwe have 3 mins left?13:57
baoliI think that we have to take it offline. I'll send out some minutes.13:58
sadasurkukura: profile_id would point to a set of config that can be applied to the port13:58
irenabI still not sure on the syntax for PCI slot info exchange13:58
sadasulike qos, acls etc13:58
irenabhaving further discussion on Mon?13:59
baoliThat sounds good13:59
rkukuraIF the profile_id is needed by the GenericVIFDriver, if the bound MD could figure out what it should be and put it in binding:vif_details13:59
irenabI'll send an email to the group once push the change for vnic_type. rkukura: can you approve it?13:59
sadasuyes, yes13:59
rkukurairenab: Are you going to update the BP to match current agreement?14:00
sadasurkukura: yes. but will have to think about it some more14:00
irenabrkukura: shure14:00
irenabwill try to make it today, most late on Sunday14:00
sadasuirenab: thanks14:00
rkukurairenab: Let me know when the BP is ready to approve and I'll take care of it14:00
*** hdd_ has joined #openstack-meeting-alt14:00
irenabrkukura: thanks14:01
baoliI'll send out some minutes, and the questions we had during this meeting14:01
baoli#endmeeting14:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:01
openstackMeeting ended Thu Jan 30 14:01:25 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-30-13.00.html14:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-30-13.00.txt14:01
irenaband agreements14:01
sadasubaoli: gr8. thanks14:01
openstackLog:            http://eavesdrop.openstack.org/meetings/pci_passthrough/2014/pci_passthrough.2014-01-30-13.00.log.html14:01
*** arnaud__ has joined #openstack-meeting-alt14:01
baoliYep!14:01
irenabthanks all14:01
markwash#startmeeting glance14:02
openstackMeeting started Thu Jan 30 14:02:14 2014 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.14:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:02
*** openstack changes topic to " (Meeting topic: glance)"14:02
openstackThe meeting name has been set to 'glance'14:02
markwashgreetings14:02
arnaud__hi markwash14:02
rosmaitao/14:02
icchahey14:02
*** jbernard has joined #openstack-meeting-alt14:03
markwashI'm a little slow this morning14:03
zhiyanhello14:03
markwashI think I overcame my jetlag on the trip back almost immediately14:03
markwashI scratched out a bit of an agenda for today here14:04
markwash#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:04
markwashI can't actually remember all of the items we pushed off to this meeting vs the next at the mini summit14:04
*** kiall has joined #openstack-meeting-alt14:05
markwash#topic summit post-processing14:05
*** openstack changes topic to "summit post-processing (Meeting topic: glance)"14:05
markwash#link https://wiki.openstack.org/wiki/Glance/IcehouseCycleMeetup14:05
*** BrianB_ has quit IRC14:05
rosmaitai think today is just the drivers14:05
markwashin case folks haven't seen that already, its got a lot of the etherpad notes from the summit, not all of the slides14:06
rosmaitaglance.store is next time14:06
zhiyanrosmaita: +114:06
arnaud__ok sounds good14:06
zhiyanarnaud__: thanks14:06
*** rkukura has left #openstack-meeting-alt14:06
markwashsince it was first in the list, let's just do a quick reminder about what we want to have prepped for next week on glance.store14:06
arnaud__I think it would be nice it flavio could be around to discuss it14:07
zhiyan(a little distracted, tonight is China New Year eve)14:07
arnaud__since he was the initiator14:07
markwashmakes sense14:07
*** balajiiyer has joined #openstack-meeting-alt14:07
markwashzhiyan: happy chinese new year!14:07
zhiyanmarkwash: thanks!14:07
arnaud__+1 :)14:08
zhiyanhappy new year!14:08
zhiyanarnaud__: thanks14:08
rosmaitazhiyan: happy new year from virginia, too14:08
arnaud__I will ping him this week to make sure he will be there next meeting14:08
zhiyanrosmaita: thanks14:08
*** balajiiyer has left #openstack-meeting-alt14:08
*** yamahata has quit IRC14:09
*** yamahata has joined #openstack-meeting-alt14:09
zhiyanarnaud__: if you ok, pls involve me, thanks.14:09
markwashOkay so I'll add glance store to the planned schedule for next meeting14:09
markwashand here's the link to that topic so folks can prepare as well14:09
markwash#link https://etherpad.openstack.org/p/right_place_for_glance.store_modules14:09
*** yamahata has quit IRC14:10
markwashokay14:10
*** yamahata has joined #openstack-meeting-alt14:10
arnaud__ok zhiyan14:10
markwashnow onto drivers14:11
markwashI cleaned up glance-drivers in launchpad, and made the first appointment14:11
markwashfirst I added rosmaita14:11
rosmaitathank you!14:11
markwashwe'll see how well we can define the team duties and figure out the workload and then see about adding more folks14:12
markwashso all that's left is to set up a coordination meeting14:12
markwashrosmaita: would next tuesday sometime work for you?14:13
zhiyanmarkwash: sorry, may i know what's "glance driver"? give a quick sync-up?14:13
markwashoh sure, sorry I'm going too fast14:13
rosmaitai will check date while you fill in zhiyan14:14
zhiyanmarkwash: thanks! (streaming delay killed me, seems)14:14
markwashin iccha 's session about blueprint triage, one of the proposals was to adopt a nova-style drivers group to perform blueprint triage14:14
markwashwe weren't sure we needed to go to the level of sponsorship14:14
*** eankutse has joined #openstack-meeting-alt14:14
zhiyanmarkwash: ok. make sense.14:15
flaper87o/14:15
* flaper87 is late14:15
markwashso the initial goals are to just figure out the workflow and to try to clean up the existing blueprints14:15
arnaud__markwash: any idea how many people in the team?14:16
markwasharnaud__: not sure yet14:16
* flaper87 is working on the virtual-size and glance.store bps14:16
markwasharnaud__: two feels a little small but I think is right just for bootstrapping14:16
arnaud__flaper87: we will talk about the glance.store next week, hope that's ok for you :)14:17
*** ashwini has joined #openstack-meeting-alt14:17
rosmaitamarkwash: tuesday is wide open for me right now14:17
flaper87arnaud__: I'm already working on that14:17
flaper87next weeks meeting is late for me. I'll try to make it anyway14:17
*** akuznets_ has quit IRC14:17
markwashrosmaita: okay cool I'll follow up with you to pick a time14:18
*** bill_az has joined #openstack-meeting-alt14:18
*** akuznetsov has joined #openstack-meeting-alt14:18
*** jcooley_ has joined #openstack-meeting-alt14:18
zhiyanflaper87: btw, i saw your initial code with your personal trunk. it's a good start, but tbh i think it need more wrap14:18
flaper87zhiyan: it's not finished14:19
flaper87I'm working on it14:19
flaper87and I ned to submit patches in both glance and glance.store to make the transition easier14:19
flaper87need*14:19
markwashflaper87: one thing we were talking about a bit is the timeline14:19
*** yamahata has quit IRC14:19
*** lblanchard has joined #openstack-meeting-alt14:19
zhiyanflaper87: np. actually i'm interested in it14:19
flaper87and I would target a huge / perfect wrapper to begin with, TBH. I'd prefer transitioning to glance.stores w/ backwards compatibility and few changes. Then we can improve the wrapper.14:20
flaper87that's what we planned with olso.messaging to14:20
markwashflaper87: I think it met with pretty broad consensus about being a good idea to break out the stores, but there were two hangups. . one we want to make sure this improves the testing story rather than hurts it, which I think is doable14:20
* flaper87 doesn't want to hijack the meeting14:20
icchaespecially if we are waiting for changes on the scrubbing locations to get in?14:20
markwashflaper87: the other concern was more about how we might use it in the client14:20
markwashand I think that's really important but not necessarily so blocking14:20
flaper87markwash: re testing. I fully agree! I'm actually spending more time there now14:21
flaper87cleaning up things that shouldn't have been inside the store package14:21
flaper87markwash: yeah, that's a good question14:21
flaper87I think that relates a lot w/ direct_url access being enabled14:21
flaper87but I admit I still need to think more about that particular bit14:21
arnaud__I think what we said it that the lib could be ready by I-3 but integrated later with glance/glance-client. what do you think flaper87?14:21
*** yamahata has joined #openstack-meeting-alt14:22
flaper87arnaud__: I'd agree w/ integrating it after I-3 in the client but I think glance would benefit from a non-breaking transition to glance.store during I-314:22
*** sarob has joined #openstack-meeting-alt14:22
*** ivoks has quit IRC14:23
markwashflaper87: stuart had some concerns that raised red flags for that general plan of integrating with the client, mostly around having to have such a high privilege / trust level for clients. . but I think we just need to be sure we have a clear strategy for less trusted clients that still makes sense14:23
markwashokay, moving on, we can cover this more next meeting I think14:23
*** ivoks has joined #openstack-meeting-alt14:23
markwash#topic glance summit post-processing: glance mission14:23
*** openstack changes topic to "glance summit post-processing: glance mission (Meeting topic: glance)"14:24
flaper87markwash: agreed14:24
* iccha needs to step away for a bit14:24
markwashduring the summit we had a lot of fun chatting with jbernard and georgy and other mirantis folks about how glance might work for other projects14:24
markwashand the general idea was that glance's mission is a bit broader and different than "image store"14:25
* flaper87 is so happy to hear that!14:25
markwashand randallburt also14:25
markwashthere are some steps we need to follow to build momentum for this in Atlanta14:26
zhiyansounds good14:26
markwashI think we should have a statement of this mission, actually it can be the the Images Program mission in the governance repo or wherever14:26
*** mahipal has quit IRC14:26
*** baoli has quit IRC14:26
markwashand we need to have some proposals for how we can follow that mission14:26
jbernardmarkwash: im happy to help in this regard14:27
flaper87this is going to be interesting14:27
flaper87because an Image program for a broarder mission doesn't seem to be a god fit, we'd have to rename the program14:27
markwashI wanna give a little preview of that mission here14:27
flaper87so establish a way to deprecate an existing program and create a new one14:27
flaper87anyway, TC discussion14:27
markwashflaper87: yeah good point, which might make things a bit awkward14:27
*** jcooley_ has quit IRC14:27
flaper87s/god/good/14:28
* flaper87 is still hungry and there are no gummy bears left14:28
*** sarob has quit IRC14:28
markwashthe preview is, Glance's role is to store and track the "starting points" or templates for other openstack services14:28
*** akuznetsov has quit IRC14:28
*** kraman has joined #openstack-meeting-alt14:29
markwashand to make those "starting points" discoverable, shareable, and to provide some gating and validation to make the interoperability story work in general14:29
flaper87I wish we could find a better term other than template14:30
markwashyeah14:30
*** jmaron has joined #openstack-meeting-alt14:30
markwashalso better than "starting points" :-)14:30
flaper87LOL, you said that14:30
flaper87:P14:30
markwashoh I fully admit this is definitely a work in progress14:30
markwashthat's why I bring it up here14:30
flaper87but the overall idea sounds really good, IMHO14:30
rosmaita+114:30
markwashI'd really like for us to have some good language around it before throwing it out as troll bait14:31
arnaud__+114:31
rosmaitamarkwash: good idea!14:31
markwashbecause I think the next step in the process is the ML and any related TC discussions14:31
rosmaitathere will be strong but not necessarily helpful opinions on this14:31
markwash(in parallel to the code process we can talk about, which shouldn't feel blocked by the mission imo)14:31
*** csaba|afk is now known as csaba14:32
*** itzikb has quit IRC14:32
markwashit might actually be good to just be ready with a mission and then wait a bit until we are adding some of the code14:32
*** demorris has quit IRC14:32
flaper87markwash: fully agree14:32
markwashthat can sometimes ease the confusion for folks14:33
*** bill_az_ has joined #openstack-meeting-alt14:33
*** bill_az has quit IRC14:33
flaper87and it sounds like for this transition we'll need an API v3 :)14:33
markwashflaper87: yeah we aren't quite clear on that14:33
markwashit might be able to be bolted onto v2, which could ease the transition a bit14:33
markwashI think that's the current code plan14:34
flaper87I'm not sure about that. What worries me the most is that we don't have a client release with support for v214:34
markwashfolks are just going to submit patches against v2 that sort of do their own thing14:34
flaper87My concern is that doing that could end up in corner cases that we won't be able to see14:34
flaper87becase we are going to change the existing API instead of working on a new API thought for this transition14:35
markwashflaper87: I'm not sure I follow about the client release14:35
markwashI've been using v2 with the current glanceclient14:36
markwashat least, I thought so! :-)14:36
flaper87markwash: yeah but the API is not fully supported, right? I mean, we don't have support for multi-locaitons in the client, for example14:36
flaper87AFAIK14:36
arnaud__flaper87: that's correct14:37
zhiyanflaper87: are you talking PATCH api?14:37
flaper87zhiyan: I'm talking about multi-location in general.14:37
flaper87but lets stay in-topic14:37
markwashI guess, are you concerned that the v2.x series is continuing to advance, ahead of the client, while we would be doing yet more stuff?14:38
flaper87what I wanted to say is that implementing a v3 API w/o having full support for v2 would be weird14:38
*** yamahata has quit IRC14:38
*** demorris has joined #openstack-meeting-alt14:38
flaper87markwash: yeah, pretty much that14:38
markwashoh14:38
markwashyeah14:38
markwashthat's my concern about v3 as well14:38
rosmaitaflaper87: what multi-location support is missing in client?14:38
markwashrevving major version is really disruptive for downstream14:38
flaper87so, I'm there are som good points about working on a v3 but also things that make me think that v2.X would be better14:38
markwashso I think we should only do it if we have to14:38
flaper87rosmaita: adding new locations for an image. AFAIK, that hasn't been implemented. I could be wrong, though14:39
*** kraman has quit IRC14:39
flaper87I admit I've been heads down in the server myself14:39
markwashmy current thinking is that we have a broad strategy of adding new, more generic resource types to v2 to deal with all the14:39
markwashdarnit14:39
markwashformatting14:39
markwashbroad strategy of:14:40
zhiyanrosmaita: imo, except receive multi-locations, others are all miss currently14:40
markwash1) add new, more generic-ish resource types to v2 to deal with instances, heat templates, murano packages, etc14:40
*** yamahata has joined #openstack-meeting-alt14:40
arnaud__markwash: artifacts? :)14:40
markwash2) try to shrink v2/images to *just block devices* none of this multi-disk stuff14:40
markwasharnaud__: yeah artifacts14:40
markwashthats what I think they were calling it, right?14:41
arnaud__yep14:41
markwashokay cool14:41
markwashand 3) have the new artifacts stuff maintain references to v2/images where appropriate in their hierarchy14:41
*** boris-42 has joined #openstack-meeting-alt14:41
markwasharnaud__: artifacts might be the word to solve our previous mission terminology problem as well14:41
arnaud__yes, that's what I was thinking too14:42
rosmaitazhiyan: you can also set the multi-locations, the json pointer code was enhanced so PATCH would work for that14:42
arnaud__btw, markwash: I would be interested to work on the instance templates14:42
zhiyanrosmaita: from glanceclient?14:43
*** aignatov is now known as aignatov_14:43
markwasharnaud__: cool, I think jbernard is sort of "carrying the torch" on instance templates for now but I know we're going to need a broad front in order to get buyin across the projects, there is probably a place you can fit into those efforts14:43
zhiyanrosmaita: i added location patch api support on server side.14:44
arnaud__ok sounds good14:44
rosmaitazhiyan: probably not14:44
jbernardmarkwash, arnaud__: yes, all help is appreciated14:44
markwashjbernard: great, thanks14:44
markwashI know a lot of folks here will be interested in helping, there's always the additional challenge of keeping focus if we end up with too many cooks :-)14:45
markwashnot saying we'll end up there but its a good thing to be aware of14:46
markwashokay, I think I sidetracked myself14:46
markwashjust a quick announcement, I'll be providing some more summary material from the summit soon14:46
markwashand ashwini can post videos as appropriate (?)14:47
markwashno promises on the quality, we weren't checking or talking directly into the mic or anything14:47
rosmaitashe will not post inappropriate videos14:47
markwashhaha14:47
markwashmoving on14:47
markwash#topic icehouse 314:47
*** openstack changes topic to "icehouse 3 (Meeting topic: glance)"14:47
ashwinimarkwash: yes i will look into sorting those soon14:48
markwashfirst thing to note, we're trying to coordinate a cross-project code proposal deadline14:48
markwashI'm not sure if the date has been announced yet, but it was looking like february 18 which is quite soon14:48
markwashcode proposal meaning the review needs to be up in gerrit by then14:48
rosmaitaso, would glanceclient stuff be excluded from the freeze?14:49
*** vponomaryov has joined #openstack-meeting-alt14:49
markwashlook to the ML for more details, either already there or coming soon14:49
markwashglanceclient I think is generally excluded from the feature freeze, so I expect this wouldn't really affect it either14:49
rosmaitaok, could give us time to get the client up to icehouse API before icehouse release14:50
markwashin terms of review priorities, I think folks should be focusing on stuff in https://launchpad.net/glance/+milestone/icehouse-314:50
*** banix has joined #openstack-meeting-alt14:50
markwashthere are a bunch of things there that are already proposed and done essentially14:50
*** bswartz has joined #openstack-meeting-alt14:50
markwashcarryover from icehouse 214:50
markwashthe more of those we can land early the better14:51
*** caitlin56 has joined #openstack-meeting-alt14:51
markwashthe gate is a real blocker and I'm worried we'll be in for sad times as we approach the Feature Freeze window14:51
*** rraja has joined #openstack-meeting-alt14:51
markwashokay, that's all I have, I'm going to kick it over to open discussion but feel free to discuss this more if you have questions14:52
markwash#topic open discussion14:52
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:52
*** japplewhite has joined #openstack-meeting-alt14:52
zhiyanmarkwash: actually i have three review request for the testing14:52
*** aignatov_ is now known as aignatov14:53
markwashzhiyan: cool, links?14:53
zhiyanone is testrepository migration, flaper87 just mentioned in team room, i think it can help gate14:53
zhiyanhttps://review.openstack.org/#/c/59699/14:53
zhiyansecond is https://bugs.launchpad.net/glance/+bug/127436514:53
flaper87please, lets merge the testr one14:53
*** mpolanco has joined #openstack-meeting-alt14:53
markwashsounds like the testrepository one can fix my virtualenv/pip problems too?14:54
zhiyanthird is https://bugs.launchpad.net/glance/+bug/127213614:54
zhiyantestr can't, but #59699 could :)14:54
zhiyanactually it can fix two issues14:54
zhiyanat last, it can make "run_tests.sh" real work14:54
*** shamail has joined #openstack-meeting-alt14:56
markwashI'm running the testrepository one now locally btw14:56
*** mestery_ is now known as mestery14:56
*** ozstacker has joined #openstack-meeting-alt14:56
zhiyanmarkwash: yes, doublecheck will be better14:56
*** demorris has quit IRC14:57
zhiyanthat's all for me.14:57
hdd_hello, I have been working on cross-service request ID, which will log the request ID mapping between services14:57
*** aostapenko has joined #openstack-meeting-alt14:57
hdd_this would require updates to all the python clients14:57
hdd_I was wonder what the procedure is for cutting a new release of glanceclient, once I have the code done14:58
*** aostapenko has quit IRC14:58
zhiyanhdd_: it can be used to help log analysis?14:58
*** aostapenko has joined #openstack-meeting-alt14:58
markwashhdd_: I just cut the release14:58
*** aostapenko has quit IRC14:58
markwashI mean14:58
markwashthe process is "markwash does it"14:58
hdd_zhiyan: yes, that's the idea14:58
hdd_(-:14:58
*** aostapenko has joined #openstack-meeting-alt14:58
markwashhdd_ I push a git tag to openstack or gerrit or whatever, a tarball is built by jenkins, and then jenkins uploads stuff to pypi14:59
hdd_ok, so I'll just contact you when the change is merged?14:59
markwashyeah14:59
hdd_cool15:00
markwashit never hurts to pester me about releasing the client15:00
markwashsad but true15:00
markwashokay I guess we'll make way, in case there is another meeting right after15:00
*** gregsfortytwo1 has joined #openstack-meeting-alt15:00
markwashthanks everybody!15:00
rosmaitabye!15:00
*** kevinconway has joined #openstack-meeting-alt15:00
arnaud__bye15:00
markwash#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:00
openstackMeeting ended Thu Jan 30 15:00:44 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-30-14.02.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-30-14.02.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2014/glance.2014-01-30-14.02.log.html15:00
*** hdd_ has quit IRC15:00
*** ashwini has left #openstack-meeting-alt15:01
bswartz#startmeeting manila15:01
openstackMeeting started Thu Jan 30 15:01:16 2014 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:01
*** openstack changes topic to " (Meeting topic: manila)"15:01
openstackThe meeting name has been set to 'manila'15:01
bswartzhello folks15:01
*** zhiyan has left #openstack-meeting-alt15:01
aostapenkohello, everyone15:01
yportnovahi15:01
caitlin56hello15:01
vponomaryovHello15:01
scottdaHi15:01
gregsfortytwo1hi15:01
bswartz#link https://wiki.openstack.org/wiki/ManilaMeetings15:01
shamailHi15:01
rrajahi15:01
csabahello15:01
*** vbellur has joined #openstack-meeting-alt15:02
bswartzsome of us were having a discussion earlier this week that I think the whole group would find interesting15:02
bswartz(also I'm hoping someone has a genius idea that will solve the problem)15:02
bill_az_Hi everyone15:02
bswartzso the issue is in the generic driver design, with how it connects to the tenant network15:03
*** ndn9797 has joined #openstack-meeting-alt15:03
*** jbernard has left #openstack-meeting-alt15:03
bswartzOur initial hope was that we could simply create a network port on the tenant's network and assign that to the service VM15:03
bswartzhowever we don't want to make the service VM owned by the tenant for a variety of reasons15:04
ndn9797Hi, I'm Nagesh, from Bangalore, joining manila meeting for first time..15:04
bswartz1) We don't want it to count against the tenant's quotas15:04
bswartz2) We don't want the tenant to accidentally delete it15:04
yportnovandn9797: Hi15:05
bswartz3) We want to hide manila backend details from the tenant to the extent possible15:05
*** AlanClark has joined #openstack-meeting-alt15:05
bswartzndn9797: hello and welcome!15:05
bswartzso it's preferrable for the service VMs created by the generic driver to be owned by some special service tenant15:06
*** balajiiyer has joined #openstack-meeting-alt15:06
bswartzhowever it seems that either nova or neutron or both won't let us connect a VM owned by one tenant to a network owned by another tenant15:06
bswartzone potential workaround is to allow the service VMs to have their own separate network and to simply provide routing between that network and tenant networks15:07
bswartzI find that workaround to be complex and error prone15:07
gregsfortytwo1there isn't an infrastructure for "admin" nodes or whatever to be connected to anybody they want?15:07
bswartzbut without making changes to nova or neutron or both, it seems to be the only option15:08
*** demorris has joined #openstack-meeting-alt15:08
vponomaryovgregsfortytwo1: problem in assigning user tenant port to service tenant vm15:08
bswartzoops I forgot to set the topic15:08
bswartz#topic Generic Driver Networking15:08
*** openstack changes topic to "Generic Driver Networking (Meeting topic: manila)"15:09
shamailWould assigning a static IP to the service VM bypass the separate tenant/network issue?  Assuming there's a way for us to do this.15:09
bswartzokay so hopefully most of you understand the problem15:09
aostapenkoI have news since yesterday, it's quite easy to configure routers, so we will not need any additional route rules in vm in our private network15:09
bswartzshamail: the IP will end up getting assigned by neutron and will be effectively static15:10
ndn9797I understand the problem now. Thanks <bswartz>15:10
shamailThe issue is with floating IPs and being assigned cross-tenants, no?  Might be completely mistaken since I wasn't in the discussions earlier.15:10
bswartzbut it will be an IP from a separate network15:10
gregsfortytwo1has anybody talked to people in the other groups yet? I'm surprised there's not an accepted model already15:10
bswartzgregsfortytwo1: I think that nobody is doing anything that requires what we want15:10
bswartzsince you always have the option of setting up virtual routes between tenants15:10
shamailBut the assignment mechanism (e.g. Neutron) is the issue, not the address space itself so couldn't we find an alternative way to assign?15:10
gregsfortytwo1everybody else is still just doing things through the hypervisor? really?15:11
bswartzno it's not actually an IP issue15:11
shamailOkay.15:11
bswartzwe can allocate a port on the tenants network, we just can't assign it to our VM through nova15:11
bswartzwe could still fake it and use the IP within the VM -- but without actual bridging of the packets thats useless15:11
*** mattgriffin has joined #openstack-meeting-alt15:12
*** demorris has quit IRC15:12
bswartzgregsfortytwo1: I'm not sure what you mean15:12
aostapenkowe'd like to share docs about how generic driver is implemented now15:12
bswartzgregsfortytwo1: I think people are using their own tenant networks currently, and when they need connectivity they're setting it up through neutron routes15:13
aostapenkohttps://docs.google.com/a/mirantis.com/drawings/d/1sDPO9ExTb3zn-GkPwbl1jiCZVl_3wTGVy6G8GcWifcc/edit15:13
aostapenkohttps://docs.google.com/a/mirantis.com/drawings/d/1Fw9RPUxUCh42VNk0smQiyCW2HGOGwxeWtdVHBB5J1Rw/edit15:13
aostapenkohttps://docs.google.com/a/mirantis.com/document/d/1WBjOq0GiejCcM1XKo7EmRBkOdfe4f5IU_Hw1ImPmDRU/edit15:13
bswartzthe ideal case for me is that we can create a VM that right on the tenant's network but the VM is hidden from them and doesn't count against their quotas15:13
caitlin56Could we do this the opposite way? Rather than giving each machine in each tenant network access to the management network, could we give the management machine a floating IP on each tenant network?15:14
*** demorris has joined #openstack-meeting-alt15:14
bswartzcaitlin56: yes that's an option, but it has some problems15:14
bswartzin particular, the security services that the storage server needs to communicate with will be inside the tenant network15:15
*** jecarey has joined #openstack-meeting-alt15:15
bswartzso the "service VM" will need routes back into the tenant network15:15
caitlin56There is an even better option, but I do not think neutron supports it, you place the management computer in a "DMZ VLAN" and allow routing to the DMZ from any tenant network.15:15
bswartzwe may be able to get that to work by just setting up the routes15:15
*** gokrokve has joined #openstack-meeting-alt15:15
*** wmichel has left #openstack-meeting-alt15:16
bswartzcaitlin56: we need 2-way routing though15:16
caitlin56The gotcha is that all tenant networks have to be NATtted to a unique address on the tenant network.15:16
*** codekobe has left #openstack-meeting-alt15:16
gregsfortytwo1I'm not a network engineer so this is all a bit beyond me, but what's error-prone about setting up the routes?15:16
aostapenkobswartz: yes, we can do so, and it's not difficult15:16
caitlin56gregsfortytwo: the problem is that the tenant networks can all think they are 10.0.0.0/815:16
bswartzgregsfortytwo1: perhaps error-prone was the wrong phrase -- what I meant was that there's a lot of complexity with network routes and testing all the corner cases seems like a huge problem15:17
bswartzaostapenko thinks he can make it work so it's what we're going to try15:17
*** mattgriffin has quit IRC15:17
gregsfortytwo1isn't that Somebody Else's Problem? (where Somebody Else is neutron)15:17
*** balajiiyer has left #openstack-meeting-alt15:17
scottdaIf the ideal solution involves work from Neutron (and perhaps Nova), it might be worth trying to get a blueprint together for those team. Neutron doesn't seem to be too locked down for new features.15:17
*** mattgriffin has joined #openstack-meeting-alt15:18
bswartzI just wanted to throw this problem out to the larger group to see if we could find a better way15:18
gregsfortytwo1we don't just say "connect this IP and this network" or similar?15:18
*** mattgriffin has quit IRC15:19
bswartzgregsfortytwo1: it's a question of the routing rules -- which packets go to which gateways15:19
caitlin56The trick is that you need very specific firewall and NAT rules to be set up properly. You want to allow each tenant network to use the same addresses, and you doi not want to allow general traffic from the tenant networks.15:19
*** mattgriffin has joined #openstack-meeting-alt15:19
bswartzconsider this: the service network will have sime CIDR range, and that range will need to be mapped into every tenant's routing tables15:20
caitlin56The setup I have seen, each tenant is NATted to the DMZ, and routing is limited to the DMZ subnet (i.e. no packets transit the DMZ).15:20
bswartzif any tenant is using those same addresses for something (perhaps a VPN connectiong to a corporate network) we will get an address collision15:20
*** DinaBelova is now known as DinaBelova_15:20
bswartzconnection*15:20
caitlin56bswartz: it's ont he15:20
caitlin56DMZ thaty we need to do the routing.15:21
*** kraman has joined #openstack-meeting-alt15:21
*** rohit404 has left #openstack-meeting-alt15:21
shamailWouldn't that still require something to maintain the NAT entries and provision the addresses?  How would this be from a maintenance perspective?15:21
caitlin56The assumption is that the DMZ has a public IPV4 or ipv6 subnet - something a tenant should not be using.15:21
bswartzcaitlin56: you're proposing that service VMs be given public addresses?15:22
caitlin56You allow a route from each tenant network to that specific public subnet,  and you NAT tranlate every packet when routed.15:22
bswartzcaitlin56: how do the service VMs tunnel back into the tenant networks?15:22
caitlin56It can be PNAT or block NAT translation, but here PNAT seems more appropriate.15:23
aostapenkowe'd like to avoid using NAT at all because of nfs limitations15:23
caitlin56That's where you need NAT rather than PNAT.15:23
bswartzyeah the whole idea is to deliver a driver that works similarly to a VLAN-based mutlitenancy solution which requires full 2-way network connectivity15:24
bswartzNAT causes problems15:24
caitlin56The only way to avoid NAT is to have the management server run lots of network namespaces and essentially "route" to the correct process before doing IP routing.15:24
bswartzif NAT is going to be required then I'm inclined to use the gateway-mediated multitenancy model15:24
*** rwsu has joined #openstack-meeting-alt15:24
*** sarob has joined #openstack-meeting-alt15:25
scottdaSorry I may have missed this, but why not a Neutron admin subnet?15:25
*** caitlin_56 has joined #openstack-meeting-alt15:25
bswartzscottda: you may need to explain what that is...15:26
aostapenkoWe're using 1 service network and multiple subnets in it with different cidrs15:26
*** ndn9797_ has joined #openstack-meeting-alt15:26
*** japplewhite has quit IRC15:26
scottdaSome feature, yet to be implemented, that allows an admin to setup neutron networking across tenants.15:26
*** ndn9797 has quit IRC15:26
*** japplewhite has joined #openstack-meeting-alt15:27
scottdaand subnets15:27
*** akerr has joined #openstack-meeting-alt15:27
caitlin_56Sorry about the drop. Anyway there is ultimately only two choices: you create a set of unique IP addresses visisble tot he manager (via NAT or PNAT), or you create slave processes which have uniwuenetwork namespaces and hence can join the tenant network without reservation.15:27
*** mattgriffin has quit IRC15:27
*** david-lyle has joined #openstack-meeting-alt15:27
*** mattgriffin has joined #openstack-meeting-alt15:27
bswartzscottda: that sounds like exactly what we need15:27
bswartzscottda: if it's not implemented though then we're still left without a solution15:28
csababswartz: as of gateway mediated, in the original concept gateway was equal to hypervisor, but for sake of network separation we thought we'd need service vm-s for gateway role so as long as this view held, I don't see how is that simpler as of network plumbing15:28
scottdaWell, if the ideal place for this is in Neutron, we could attempt to get it in Neutron.15:28
*** arnaud__ has quit IRC15:28
scottdaIt might take a bit more time, but we will be living with this solution for a long time. Years.15:29
caitlin_56But if our plan is to get Neutron improved first we will need an interim workaround.15:29
bswartzI do think the ideal place is in neutron15:29
*** dkliban has joined #openstack-meeting-alt15:29
bswartzOr nova15:29
*** markwash has quit IRC15:29
bswartzsome way to create special vms that span tenants15:29
*** caitlin56 has quit IRC15:29
bswartzscottda: are in a position to get something like that implemented?15:30
scottdaI'm not certain, but my instinct is that it will be easier to get a change through Neutron than Nova. Just from a standpoint that Neutron is newer, and changing faster.15:30
scottdaI have teammates who work on Neutron. I can certainly fly the idea past them to get some feedback.15:30
caitlin_56Linux namespaces provides the tools needed. Trying to bypass neutron to use them will be very tricky.15:30
*** sarob has quit IRC15:31
scottdaThey might have already discussed such a thing, or have a quick answer like "sure, sounds doable" or "no way, already thought of that" I really don't know.15:31
*** amytron has joined #openstack-meeting-alt15:31
bswartzcaitlin_56: there's nothing technically complicated about allowing a service VM to be directly on a tenant's network15:31
bswartzit's an administrative limitation that prevents us from doing what we want15:31
*** david-lyle has quit IRC15:32
bswartzpossibly there are security implications15:32
caitlin_56How do you know which tenant you are talking to?15:32
bswartzthere's one VM per tenant15:32
aostapenkoactually one vm per share-network15:33
bswartzso you have a 1-to-1 mapping and you can track that15:33
caitlin_56How do you talk with tenant X? You have to select the  namespace before the IP address is any good.15:33
bswartzwell yeah, thanks aostapenko15:33
*** japplewhite has quit IRC15:33
bswartzcaitlin_56: it's no different than if tenant X had created a new VM himself15:33
bswartzhowever the owner of that VM needs to be us15:34
bswartzor the "service tenant" as we've been saying15:34
*** mattgriffin has quit IRC15:34
bswartzthere is the issue of how the manila-share service talks to these special VMs, but that's also a solvable problem15:34
*** mattgriffin has joined #openstack-meeting-alt15:35
scottdaI'll start a dialogue with some Neutron devs about feasibility of an admin network. There's still the issue of the service VM.15:35
*** DinaBelova_ is now known as DinaBelova15:35
bswartzscottda: thx -- I'll follow up w/ you after this meeting because I'm very interested in that approach15:36
caitlin_56scottda: this is a general problem, not unique to NFS. So neutron should be willing to listen.15:36
scottdaYes, I'll need to get some more info as I'm not as up to speed on Manila as I'd liket to be15:36
bswartzokay enough on that15:36
scottdacaitlin_56: agreed. I think I can sell it :)15:36
bswartzlet's jump to dev status15:37
bswartz#topic dev status15:37
*** openstack changes topic to "dev status (Meeting topic: manila)"15:37
vponomaryovi will update about it15:37
*** shamail has quit IRC15:37
bswartzvponomaryov: ty15:37
vponomaryovDev status:15:37
vponomaryov1) Generic driver - https://review.openstack.org/#/c/67182/15:37
vponomaryovLion part of work is done15:37
vponomaryovTODO:15:37
vponomaryova) Finalize work of routers and routes between Vm in service tenant and vm in user tenant15:37
vponomaryovb) Write unittest15:37
vponomaryovInfo, mentioned before:15:38
vponomaryovhttps://docs.google.com/a/mirantis.com/drawings/d/1sDPO9ExTb3zn-GkPwbl1jiCZVl_3wTGVy6G8GcWifcc/edit15:38
vponomaryovhttps://docs.google.com/a/mirantis.com/drawings/d/1Fw9RPUxUCh42VNk0smQiyCW2HGOGwxeWtdVHBB5J1Rw/edit15:38
vponomaryovhttps://docs.google.com/a/mirantis.com/document/d/1WBjOq0GiejCcM1XKo7EmRBkOdfe4f5IU_Hw1ImPmDRU/edit15:38
vponomaryov2) NetApp Cmode driver - https://review.openstack.org/#/c/59100/15:38
vponomaryovTODO: bugfixing and retesting15:38
vponomaryov3) We have open item about share-networks, that should be disscussed and if accepted will take some time for implementation.15:39
bswartzvponomaryov:  what open issue?15:39
vponomaryovShould I begin with open item?15:39
*** mpolanco has quit IRC15:39
bswartzvponomaryov: yes pls15:39
vponomaryovOpen item: With current code, Vserver (VM) will be created (with data from share-network) only on first share creation call.15:39
vponomaryovits true for both drivers15:40
vponomaryovProblem:15:40
vponomaryovCurrent realisation assumes creation share and Vserve for itr. And it can be failed due to improper share-network data. So, user would like to use already activated share-networks, and wait much less time.15:40
vponomaryovAlso, due to mechanism of mapping security service to share network, we shouldn't try create Vserver (VM) on share network creation.15:40
vponomaryovProposal:15:40
vponomaryovWe can have command for share-network like "initialize" or "run", to make it, when we (admin) are ready.15:40
*** kraman has left #openstack-meeting-alt15:40
bswartzvponomaryov: you're saying we don't error check the parameters used for share-network-create until long after the API call succeeds?15:41
vponomaryovwe are checking this data on creation of Vserver, and we do this on first share creation call15:41
bswartzwell here's the thing15:42
bswartzeven if we create a vserver before we need to, we may need to create another one at some point in the future15:42
bswartzany share-create call can result in a new vserver getting created15:42
*** mpolanco has joined #openstack-meeting-alt15:42
vponomaryovyes, use r will have a choise between active share-networks15:43
vponomaryovwhich one to use15:43
bswartznow I agree that its probably worthwhile to at least validate the params passed in 1 time at the beginning15:43
bswartzbut that won't prevent us from having issues if something changes behind our back15:43
vponomaryovso, we should not only check, we should create Vserver15:44
vponomaryovif its creation is successfull, we have active share-network15:44
bswartzanyone else have an opinion here?15:44
caitlin_56bswartz: that is an unsolvable problem. The fact that you cannot launch a VM right now does not mean that the configuration is incorrect - only that it probably is.15:44
bswartzI think I can live with creating an empty vserver, just to validate the parameters passed in15:44
*** mpolanco has quit IRC15:45
vponomaryovcaitlin_56: +1, a lot of issues won't be caused by improper data itself15:45
vponomaryovwe should know, we have a Vserver15:46
vponomaryovand can crete share15:46
caitlin_56You either allow "speculative" networks or you prevent some legitimate configuration from being accepted due to a temporary network glitch.15:46
bswartzcaitlin_56: are you against the proposal?15:47
bswartzI think it's fine to do it -- the biggest downside is wasted resources15:47
bswartzokay if noone opposed then I say go ahead with it vponomaryov15:48
bswartz#topic open discussion15:49
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:49
vponomaryovok15:49
caitlin_56bswartz: I'd raise a error, but allow an operator to override - "no this config is correct even if you can't do it right now."15:49
bswartzany other topics for this week?15:49
bswartzcaitlin_56: if it won't work right now the tenant can try agian later when it will work15:49
vponomaryovA couple with launchpad BPs15:49
bswartzcaitlin_56: there's little value it setting something up early if that thing is useless until a later time15:50
*** aignatov is now known as aignatov_15:50
vponomaryovbswartz: BP https://blueprints.launchpad.net/manila/+spec/join-tenant-network can be marked as implemented,15:51
vponomaryovbugs left according to its changes. + approved change for share-networks15:51
bswartzvponomaryov: I'm here15:51
bswartzI'm there rather15:51
vponomaryovand second15:52
vponomaryovIf we drop xml support, BP https://blueprints.launchpad.net/manila/+spec/xml-support-to-client should be marked as invalid.15:52
vponomaryovDo we drop XML support?15:52
bswartzack my browser is crashing15:52
bswartzoh yes15:53
bswartzit came to my attention this week that the Nova project is dropping support for XML in their v3 API15:53
bswartzso I see no reason to support XML in any version of our API15:53
*** sadasu has quit IRC15:53
ndn9797_fine with XML drop..15:54
*** caitlin_56 has quit IRC15:54
*** caitlin_56 has joined #openstack-meeting-alt15:54
*** IlyaE has joined #openstack-meeting-alt15:54
vponomaryovI have no questions15:55
vponomaryovthanks15:55
bswartzokay15:55
bswartzthanks everyone15:55
aostapenkothanks, bye15:55
*** akerr has left #openstack-meeting-alt15:55
bswartz#endmeeting15:55
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:55
openstackMeeting ended Thu Jan 30 15:55:54 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:55
*** gregsfortytwo1 has left #openstack-meeting-alt15:55
*** jmontemayor has joined #openstack-meeting-alt15:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-30-15.01.html15:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-30-15.01.txt15:55
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2014/manila.2014-01-30-15.01.log.html15:56
vbellurthanks15:56
*** vbellur has left #openstack-meeting-alt15:56
*** aostapenko has quit IRC15:56
*** caitlin_56 has quit IRC15:56
*** ozstacker has quit IRC15:56
*** ozstacker has joined #openstack-meeting-alt15:56
*** jmontemayor has quit IRC15:57
*** jmontemayor has joined #openstack-meeting-alt15:57
*** henrynash has joined #openstack-meeting-alt16:00
*** matrohon has quit IRC16:00
*** bswartz has left #openstack-meeting-alt16:02
*** mpolanco has joined #openstack-meeting-alt16:02
*** thinrichs has joined #openstack-meeting-alt16:02
*** ndn9797_ has quit IRC16:03
*** boris-42 has quit IRC16:05
thinrichsAre we having the Neutron policy meeting today?16:06
*** csaba is now known as csaba|afk16:07
thinrichsNevermind--I just found Kyle's note canceling it.16:07
*** thinrichs has quit IRC16:07
*** d0ugal has quit IRC16:08
*** irenab has quit IRC16:09
*** betsy has joined #openstack-meeting-alt16:10
*** alagalah has joined #openstack-meeting-alt16:10
alagalahSorry I'm late16:10
*** jcooley_ has joined #openstack-meeting-alt16:12
*** ramashri has joined #openstack-meeting-alt16:13
*** japplewhite has joined #openstack-meeting-alt16:14
marunalagalah: it's cancelled16:14
alagalahmarun:  Thanks!16:16
*** DinaBelova is now known as DinaBelova_16:18
*** gokrokve has quit IRC16:21
*** japplewhite has left #openstack-meeting-alt16:22
*** david-lyle has joined #openstack-meeting-alt16:24
*** Barker has quit IRC16:24
*** michael-yu has joined #openstack-meeting-alt16:29
*** jprovazn has joined #openstack-meeting-alt16:31
*** malini is now known as malini_afk16:31
*** DinaBelova_ is now known as DinaBelova16:31
*** Barker has joined #openstack-meeting-alt16:33
*** aostapenko has joined #openstack-meeting-alt16:34
*** lsmola_ has quit IRC16:34
*** jcooley_ has quit IRC16:35
*** rnirmal has joined #openstack-meeting-alt16:35
*** SushilKM has joined #openstack-meeting-alt16:38
*** SushilKM has left #openstack-meeting-alt16:38
*** michael-yu has quit IRC16:39
*** malini_afk is now known as malini16:42
*** Leonr has joined #openstack-meeting-alt16:43
*** rraja has quit IRC16:52
*** d0ugal has joined #openstack-meeting-alt16:58
*** Barker has quit IRC16:59
*** demorris has quit IRC17:01
*** igormarnat_ has quit IRC17:01
*** Barker has joined #openstack-meeting-alt17:02
*** igormarnat_ has joined #openstack-meeting-alt17:04
*** igormarnat_ has quit IRC17:05
*** michael-yu has joined #openstack-meeting-alt17:06
*** rnirmal has quit IRC17:10
*** michael-yu has quit IRC17:10
*** michael-yu has joined #openstack-meeting-alt17:13
*** boris-42 has joined #openstack-meeting-alt17:14
*** gokrokve has joined #openstack-meeting-alt17:15
*** mozawa has quit IRC17:20
*** julim has quit IRC17:23
*** jcooley_ has joined #openstack-meeting-alt17:25
*** _nadya_ has joined #openstack-meeting-alt17:25
*** jcooley_ has quit IRC17:28
*** mat-lowery has left #openstack-meeting-alt17:29
*** sarob has joined #openstack-meeting-alt17:29
*** demorris has joined #openstack-meeting-alt17:31
*** aignatov_ is now known as aignatov17:31
*** _nadya_ has quit IRC17:33
*** jcooley_ has joined #openstack-meeting-alt17:34
*** sarob has quit IRC17:34
*** bdpayne has joined #openstack-meeting-alt17:37
*** mpolanco has quit IRC17:37
*** coolsvap has joined #openstack-meeting-alt17:38
*** Praveen_ has joined #openstack-meeting-alt17:53
*** sss has joined #openstack-meeting-alt17:54
*** dmitryme has joined #openstack-meeting-alt17:54
*** krtaylor has quit IRC17:56
*** arnaud__ has joined #openstack-meeting-alt17:56
*** arnaud___ has joined #openstack-meeting-alt17:56
*** jspeidel1 has joined #openstack-meeting-alt17:56
*** bob_nettleton has joined #openstack-meeting-alt17:56
*** ramashri has quit IRC17:59
*** sreshetniak has joined #openstack-meeting-alt18:00
*** jcooley_ has quit IRC18:00
*** crobertsrh has joined #openstack-meeting-alt18:01
*** jcooley_ has joined #openstack-meeting-alt18:01
*** ErikB has joined #openstack-meeting-alt18:01
aignatovhello savanna folks!18:03
*** _nadya_ has joined #openstack-meeting-alt18:03
aignatovwho's around?18:03
ErikBHi Alex18:04
jspeidel1here18:04
dmitrymeme there18:04
crobertsrhI'm here18:04
bob_nettletonhere18:04
*** jspeidel1 has left #openstack-meeting-alt18:04
*** markwash has joined #openstack-meeting-alt18:05
*** jspeidel has joined #openstack-meeting-alt18:05
aignatovlooks like  a quorum, let's start :)18:05
aignatov#startmeeting savanna18:05
openstackMeeting started Thu Jan 30 18:05:52 2014 UTC and is due to finish in 60 minutes.  The chair is aignatov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
*** ramashri has joined #openstack-meeting-alt18:05
*** openstack changes topic to " (Meeting topic: savanna)"18:05
openstackThe meeting name has been set to 'savanna'18:05
aignatov#topic Agenda18:06
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:06
aignatov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_January.2C_3018:06
*** dmitryme has quit IRC18:06
*** Ranjitha has joined #openstack-meeting-alt18:06
*** dmitryme has joined #openstack-meeting-alt18:06
*** ramashri has quit IRC18:06
*** alazarev has joined #openstack-meeting-alt18:07
aignatovi'm running this meeting today because SergeyLukjanov_ is on the flight to the FOSDEM summit in brusseil18:07
aignatovit looks like there are no action items from the previous meeting so lets move to the next topic18:07
aignatov#topic News / updates18:08
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:08
aignatovfolks, please18:08
crobertsrhFor me on the UI it has been a few bug fixes along with implementing many of the changes that tmckay has been working on (java action, streaming, etc).18:09
aignatovupdate from me, I'm filed blueprint in the heat to implement Savanna plugin and started working on this18:09
aignatov#link https://blueprints.launchpad.net/heat/+spec/savanna-as-heat-resource18:10
dmitrymeI'am woking on the agent, made a couple of preparational CRs during last week18:10
aignatovcrobertsrh: great progress!18:10
*** igormarnat_ has joined #openstack-meeting-alt18:10
bob_nettletonI'm working on wrapping up a few remaining issues with the HDP images for diskimage-builder, and hope to submit a patch over the next few days (if testing goes well).18:11
aignatovbob_nettleton: some troubles with testing now?18:11
*** kebray_ has joined #openstack-meeting-alt18:12
*** _nadya_ has quit IRC18:12
aignatovif you have any question about DIB and how it works you can ask IvanBereezovskiy and mattf directly or via openstack-dev18:12
aignatovthey are our experts in DIB :)18:12
*** igor has quit IRC18:12
jspeidelI have been working on blueprint support in ambari which will allow ambari to export a blueprint  for a running cluster which is then imported into savanna when using the HDP plugin.18:13
*** igor has joined #openstack-meeting-alt18:13
bob_nettletonaignatov: ok, thanks.  I've found a few issues related to package installs.  I have a few questions about DIB that I've run into this week, so I'll ask Ivan and Matt or post to the list.  thanks!18:13
aignatovjspeidel: do we have Launchpad blueprint for blueprint support in Ambari? :)18:14
*** igormarnat_ has quit IRC18:14
aignatovbob_nettleton: cool!18:14
jspeidelaignatov, working on that ;)18:14
dmitrymebob_nettleton: there are people who currently working on the same thing for Spark and CDH: https://review.openstack.org/#/c/69865/18:14
dmitrymeit makes sense to look at what they do, share you opinion, etc.18:15
aignatovany others updates, guys?18:15
bob_nettletondmitryme: ok, thanks.  I'll check out this link.18:15
*** rsblendido has quit IRC18:15
aignatovyep, one more update Spark plugin is in progress, thanks dmitryme for pointing this out :)18:16
aignatov#link https://review.openstack.org/#/c/69865/18:16
aignatovlets move on18:16
*** vponomaryov is now known as vponomaryov|afk18:16
*** igor__ has joined #openstack-meeting-alt18:17
aignatov#topic Roadmap update / cleanup18:17
*** openstack changes topic to "Roadmap update / cleanup (Meeting topic: savanna)"18:17
*** igor__ has quit IRC18:17
aignatovlets skip this... no updates in this area18:17
aignatov#topic Project naming collision18:17
*** openstack changes topic to "Project naming collision (Meeting topic: savanna)"18:17
*** nati_ueno has joined #openstack-meeting-alt18:17
*** rossella_s has quit IRC18:17
*** igor__ has joined #openstack-meeting-alt18:18
aignatovbad news confirmed, we have to rename Savanna :(18:18
*** igor has quit IRC18:18
*** igor__ has quit IRC18:18
*** igor has joined #openstack-meeting-alt18:18
aignatovall you saw the mail from Sergey about this, I think18:19
aignatovand he prepared etherpad18:19
aignatov#link https://etherpad.openstack.org/p/savanna-renaming18:19
*** igor__ has joined #openstack-meeting-alt18:20
aignatovdo you have thoughts about new name guys?18:20
*** eankutse has quit IRC18:20
aignatovif yes, please share it in the etherpad above18:20
*** eankutse has joined #openstack-meeting-alt18:20
jmaronsavahanah...18:21
aignatovsavanna, but without one 'n' :)18:21
aignatovSAVANA18:21
*** julim has joined #openstack-meeting-alt18:22
aignatovjmaron: didm;t you mistaken? savaHanaH?18:22
*** igor has quit IRC18:23
*** henrynash has quit IRC18:23
*** khyati has joined #openstack-meeting-alt18:23
dmitrymeI don't have a name to propose in mind, but I have an idea to share. I think we don't really need to find synonym for "Savanna", I mean we can pick name from completely different topic18:23
alazarevI like savannah, all new people call us in such kind anyway18:23
*** khyati has left #openstack-meeting-alt18:23
*** IvanBerezovskiy1 has joined #openstack-meeting-alt18:24
dmitrymealazarev: I am not sure we will be able to register trademark which is that close to 'Savanna'18:25
aignatovdmitryme: agree, I liked savanna before because it has the same meaning and spelling in russsian as well as in english, so I'd like to have the similar new name18:25
aignatovlike 'cosmos'18:25
aignatovit's just thoughts :)18:25
alazarevwill need to check with lawyers18:25
dmitrymefrom the top of my head, there is a distributed FS with 'Cosmos' name18:26
aignatovdmitryme: it was just an example, I didn't propose that name18:26
dmitrymebesides, I am not sure if english speakers are accustomed to that word18:26
*** igor__ has quit IRC18:27
alazarevdmitryme: agree, space is everywhere18:27
aignatovwhat is the Zotzozis18:27
aignatovI see this in the etherpad :)18:27
dmitrymeit does not google :-)18:28
*** Ranjitha has quit IRC18:28
*** harlowja_away is now known as harlowja18:28
aignatovSaratov? ;)18:29
*** nacim has quit IRC18:30
dmitrymeaignatov: though I like it as its my home city name, I am afraid it does not sound18:30
aignatovbut it rhymes with Savanna18:30
*** HenryG has quit IRC18:30
dmitrymeaignatov: I like it that you don't write poetry...18:31
dmitryme:-)18:31
aignatovlol18:31
aignatovok, any more thoughts, ideas?18:32
jmaronrhymes: santana, bandana, banana ;)18:33
*** HenryG has joined #openstack-meeting-alt18:33
jmaronatlanta (sight of next summit)18:34
aignatovjmaron: atlanta will start and over, but the name is forever :)18:34
dmitrymeatlantis :-)18:34
aignatovdmitryme: I like it18:34
dmitrymeaignatov: I think the city will persist :-)18:35
aignatovplease write it to the doc:)18:35
aignatovdmitryme: I hope :)18:35
jmaronariadne - She is mostly associated with mazes and labyrinths, due to her involvement in the myths of the Minotaur and Theseus.18:36
jmaronGet it?  we allow you to more easily navigate the maze of big data deployments…18:36
*** Praveen_ has quit IRC18:37
aignatovalso I see 'Centillion' as name, I like it as well, may be just 'Cent'? ;)18:37
aignatovjmaron: good candidate as well, please document your thoughts in the doc, all ideas...18:38
alazarevcent is not too valuable :)18:38
aignatovalazarev: may be, but short and clear18:40
alazarevI believe it is too early for discussion, let's put options to etherpad18:40
*** sarob has joined #openstack-meeting-alt18:40
*** safchain has quit IRC18:40
alazarevgeneral discussion?18:41
aignatovalazarev: right, but don't forget that about two weeks left before we get a decision to the community and lawyers about new name18:41
aignatovlets move on18:41
aignatov#topic General discussion18:41
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:41
*** sbalukoff has quit IRC18:42
jmaronsorry I was late, so I'll just mention I've started integrating support for HDP 2.0. Hope to have something for review next week18:42
*** michael-yu has quit IRC18:42
alazarevI have a question about https://bugs.launchpad.net/savanna/+bug/1232075 . Does anyone knows ground for it?18:43
alazarevI like idea to have all hostnames in lowercase. But it seems that real causes are needed.18:43
*** mpolanco has joined #openstack-meeting-alt18:43
*** ramashri has joined #openstack-meeting-alt18:44
jspeidelalazarev, I remember that when capital letters were used for resources that ended up in the hostname, this caused failures in savanna18:44
jspeidelthe hosts were not resolved properly18:44
aignatovjmaron: great to hear that, will you plan HDP 2.0 with all supported functionality like EDP, cinder volumes etc...?18:45
jspeidelwe also had the same issue with special characters in the host name like underscores18:45
alazarevjspeidel: don't you muss with underscores?18:45
jmaroncorrect.  host name is assembled from cluster name, some template names, etc and upper cases caused issues18:45
jmaronaignatov:  that's my hope, but I may be forced to take an iterative approach (smaller commits providing incremental support)18:46
jspeidelalazarec, not sure what you mean by muss with underscores18:46
alazarevjspeidel: sent phrase before reading your second line :)18:46
jspeidelif an underscore ends up in the host name, it will cause failures18:46
aignatovalazarev: yes, that's was the reason for -2 from me because I don't know any cause18:46
aignatovand bug description is also unclear about that18:47
jspeidelaignatov, I can update the bug if that would help.  But this is needed18:47
aignatovjspeidel: please update :)18:48
jmaronI wonder if we could have some UI based validation of entries to prevent such issues?18:48
jspeidelunfortunately, ambari forces the useage of hostnames so we can't just use ip's18:48
jmaronor at least minimize the risk18:48
jspeidelaignatov, will update18:48
*** michael-yu has joined #openstack-meeting-alt18:49
alazarevjspeidel: apache hadoop also requires use of hostnames18:49
jspeidelalazarev, yep18:49
*** codekobe has joined #openstack-meeting-alt18:51
*** Ranjitha has joined #openstack-meeting-alt18:51
*** eankutse has quit IRC18:52
aignatovjmaron:looking forward for HDP 2.0 on the review ;)18:52
aignatovguys, anything to discuss?18:53
alazarevjmaron: will HDP 2.0 support include EDP?18:53
jmaronalazarev:  I'd like it to ;)18:54
*** dmitryme has quit IRC18:54
jmaronmy goal is to use EDP as the measure of whether the integration is, in fact, working18:54
alazarevjmaron: great!18:54
*** johnthetubaguy has quit IRC18:55
*** sss has quit IRC18:55
*** eankutse has joined #openstack-meeting-alt18:55
aignatovwhy not? it seems easy to implement edp support for Hadoop 2.0, ooze 4.0 works with it, and we use this version with oozie18:55
aignatovshould work :)18:55
jmaronthat's my hope :)18:56
aignatovwith oozie -> of oozie18:56
*** jcooley_ has quit IRC18:56
alazarevyarn need to be supported, now we have jobtracker hardcoded18:57
*** dmitryme has joined #openstack-meeting-alt18:57
aignatovalazarev: I see18:58
jmaronah…true.  I'll need to see if I can add code to address yarn18:58
*** jcooley_ has joined #openstack-meeting-alt18:59
aignatov1 minutes left, lets finish this meeting18:59
aignatovthanks every one who's joined18:59
aignatovGuys, think about new name for Savanna!19:00
*** jspeidel has left #openstack-meeting-alt19:00
*** alagalah has left #openstack-meeting-alt19:00
aignatovshare your thoughts in etherpad19:00
*** nati_uen_ has joined #openstack-meeting-alt19:00
*** sarob has quit IRC19:00
aignatov#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Thu Jan 30 19:00:32 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-30-18.05.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-30-18.05.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2014/savanna.2014-01-30-18.05.log.html19:00
*** jmaron has left #openstack-meeting-alt19:00
*** sarob has joined #openstack-meeting-alt19:01
*** bob_nettleton has left #openstack-meeting-alt19:01
*** eankutse1 has joined #openstack-meeting-alt19:02
*** eankutse has quit IRC19:02
*** david-lyle has quit IRC19:03
*** nati_ueno has quit IRC19:03
*** nati_uen_ has quit IRC19:03
*** nati_ueno has joined #openstack-meeting-alt19:04
*** nati_ueno has quit IRC19:07
*** IvanBerezovskiy1 has left #openstack-meeting-alt19:07
*** Ranjitha has quit IRC19:08
*** bdpayne has quit IRC19:09
*** doug_shelley66 has quit IRC19:10
*** bdpayne has joined #openstack-meeting-alt19:10
*** Ranjitha has joined #openstack-meeting-alt19:10
*** igormarnat_ has joined #openstack-meeting-alt19:11
*** doug_shelley66 has joined #openstack-meeting-alt19:11
*** kebray_ has quit IRC19:13
*** igormarnat_ has quit IRC19:16
*** nati_ueno has joined #openstack-meeting-alt19:19
*** nati_ueno has quit IRC19:19
*** ramashri has quit IRC19:19
*** demorris has quit IRC19:19
*** nati_ueno has joined #openstack-meeting-alt19:20
*** ramashri has joined #openstack-meeting-alt19:21
*** ramashri has quit IRC19:23
*** demorris has joined #openstack-meeting-alt19:24
*** ErikB has quit IRC19:24
*** crobertsrh has left #openstack-meeting-alt19:26
*** amcrn has quit IRC19:30
*** ErikB has joined #openstack-meeting-alt19:31
*** dkliban has left #openstack-meeting-alt19:34
*** sbalukoff has joined #openstack-meeting-alt19:34
*** songole has joined #openstack-meeting-alt19:38
*** songole has quit IRC19:41
*** rohit404 has joined #openstack-meeting-alt19:47
*** IlyaE has quit IRC19:48
*** irenab has joined #openstack-meeting-alt19:49
*** nati_ueno has quit IRC20:02
*** d0ugal has quit IRC20:03
*** demorris_ has joined #openstack-meeting-alt20:03
*** amcrn has joined #openstack-meeting-alt20:04
*** aignatov is now known as aignatov_20:04
*** mpolanco has quit IRC20:05
*** demorris has quit IRC20:06
*** demorris_ is now known as demorris20:06
*** Duane_ has joined #openstack-meeting-alt20:06
*** IlyaE has joined #openstack-meeting-alt20:09
*** aignatov_ is now known as aignatov20:10
*** RajeshMohan has quit IRC20:10
*** ErikB has quit IRC20:11
*** ozstacker has quit IRC20:12
*** ozstacker has joined #openstack-meeting-alt20:12
*** RajeshMohan has joined #openstack-meeting-alt20:12
*** RajeshMohan has quit IRC20:14
*** nati_ueno has joined #openstack-meeting-alt20:15
*** RajeshMohan has joined #openstack-meeting-alt20:16
*** mpolanco has joined #openstack-meeting-alt20:21
*** Barker has quit IRC20:26
*** Barker has joined #openstack-meeting-alt20:27
*** michael-yu has quit IRC20:27
*** alazarev has quit IRC20:28
*** michael-yu has joined #openstack-meeting-alt20:29
*** Duane_ has quit IRC20:30
*** DinaBelova is now known as DinaBelova_20:30
*** Duane_ has joined #openstack-meeting-alt20:30
*** alazarev has joined #openstack-meeting-alt20:30
*** jcooley_ has quit IRC20:31
*** jcooley_ has joined #openstack-meeting-alt20:32
*** Duane_ has quit IRC20:34
*** rocky2 has joined #openstack-meeting-alt20:40
*** _nadya_ has joined #openstack-meeting-alt20:45
*** denis_makogon_ has joined #openstack-meeting-alt20:50
*** khyati has joined #openstack-meeting-alt20:51
*** demorris has quit IRC20:58
*** aignatov is now known as aignatov_20:58
*** michael-yu has quit IRC21:00
*** dkliban has joined #openstack-meeting-alt21:01
*** sreshetniak has quit IRC21:01
*** FallenPegasus has joined #openstack-meeting-alt21:01
*** denis_makogon has quit IRC21:02
*** denis_makogon_ is now known as denis_makogon21:02
*** dmakogon_ has joined #openstack-meeting-alt21:02
*** rocky2 has quit IRC21:03
*** rocky2 has joined #openstack-meeting-alt21:03
*** michael-yu has joined #openstack-meeting-alt21:04
*** alazarev has quit IRC21:04
*** HenryG has quit IRC21:06
*** Duane_ has joined #openstack-meeting-alt21:06
*** alazarev has joined #openstack-meeting-alt21:09
*** Ranjitha has quit IRC21:09
*** coolsvap is now known as coolsvap_away21:10
*** ErikB has joined #openstack-meeting-alt21:10
*** richm has joined #openstack-meeting-alt21:12
*** n0ano has quit IRC21:14
*** n0ano has joined #openstack-meeting-alt21:14
*** rocky2 has quit IRC21:18
*** mpolanco has quit IRC21:18
*** rocky2 has joined #openstack-meeting-alt21:18
*** Duane__ has joined #openstack-meeting-alt21:19
*** eankutse1 has quit IRC21:21
*** eankutse has joined #openstack-meeting-alt21:22
*** Duane_ has quit IRC21:22
*** irenab has quit IRC21:22
*** lblanchard has quit IRC21:22
*** mpolanco has joined #openstack-meeting-alt21:23
*** markwash has quit IRC21:24
*** Duane_ has joined #openstack-meeting-alt21:25
*** julim has quit IRC21:26
*** haleyb has quit IRC21:26
*** haleyb has joined #openstack-meeting-alt21:27
*** rnirmal has joined #openstack-meeting-alt21:28
*** Duane__ has quit IRC21:29
*** Ranjitha has joined #openstack-meeting-alt21:31
*** jcooley_ has quit IRC21:32
*** jcooley_ has joined #openstack-meeting-alt21:32
*** betsy has quit IRC21:33
*** ErikB has quit IRC21:34
*** nati_uen_ has joined #openstack-meeting-alt21:39
*** nati_ueno has quit IRC21:42
*** rocky2 has quit IRC21:42
*** catherineD has joined #openstack-meeting-alt21:44
*** Duane_ has quit IRC21:45
*** Duane_ has joined #openstack-meeting-alt21:46
*** yogesh has joined #openstack-meeting-alt21:46
*** rocky2 has joined #openstack-meeting-alt21:50
*** markwash has joined #openstack-meeting-alt21:50
*** Duane_ has quit IRC21:51
*** mpolanco has quit IRC21:51
*** alazarev has quit IRC21:53
*** mpolanco has joined #openstack-meeting-alt21:53
*** Sukhdev has joined #openstack-meeting-alt21:53
*** alazarev has joined #openstack-meeting-alt21:55
*** krtaylor has joined #openstack-meeting-alt21:56
*** DrRay|2 has joined #openstack-meeting-alt21:58
*** DrRay|2 has left #openstack-meeting-alt21:58
*** jcooley_ has quit IRC21:58
*** drray810 has joined #openstack-meeting-alt21:59
*** rohit404 has quit IRC21:59
*** Kileroy has joined #openstack-meeting-alt22:01
*** drray810 has quit IRC22:01
*** Kileroy has quit IRC22:01
*** drray028 has joined #openstack-meeting-alt22:01
*** _nadya_ has quit IRC22:01
*** jprovazn is now known as jprovazn_afk22:02
*** yogesh has quit IRC22:03
*** Alex_H has joined #openstack-meeting-alt22:04
*** jdob has quit IRC22:04
rocky2anybody out there for Refstack?22:05
catherineDYes.  This is Catherine Diep from IBM is here for RefStack22:05
drray028and Raymond Wong, also from IBM.22:06
rocky2Hey!  Rocky Grober from Huawei.22:06
*** henrynash has joined #openstack-meeting-alt22:07
*** zehicle_ has joined #openstack-meeting-alt22:08
*** Duane_ has joined #openstack-meeting-alt22:09
*** dmitryme has quit IRC22:09
*** Duane__ has joined #openstack-meeting-alt22:09
*** pdmars has quit IRC22:10
*** joshuamckenty has joined #openstack-meeting-alt22:11
*** nati_uen_ has quit IRC22:11
rocky2 Hmm.  Should we start anyway???22:12
joshuamckentyyes22:12
joshuamckentyRefStack meeting?22:12
*** nati_ueno has joined #openstack-meeting-alt22:12
joshuamckentySorry, we were all in #refstack22:12
zehicle_hello22:12
*** Barker has quit IRC22:12
rocky2Oh.  Lemme see if I can get there22:12
joshuamckentywe can meet here instead22:12
*** Barker has joined #openstack-meeting-alt22:13
zehicle_https://wiki.openstack.org/wiki/Meetings/DefCore22:13
*** Barker has quit IRC22:13
*** Duane_ has quit IRC22:13
zehicle_Agenda22:14
zehicle_review the use-cases22:14
zehicle_identify immediate work items & owners (added below)22:14
zehicle_deal with logistics and code sharing/access issues22:14
zehicle_talk over general objectives and timelines22:14
*** Barker has joined #openstack-meeting-alt22:14
*** sparkycollier has joined #openstack-meeting-alt22:14
*** Barker has quit IRC22:14
zehicle_can I get a roll call?22:15
* zehicle_ rusty w/ IRC meeting governance22:15
joshuamckentyhere22:15
catherineDCatherine Diep and Raymond Wong from IBM22:15
rocky2o/22:15
sparkycollierhere22:15
drray028hi22:15
Alex_Hhey22:16
joshuamckentyso use cases are https://docs.google.com/document/d/1O1KH3RcPR2ZshlV3LS1qPBaywBCyXlzuFdinmYZNAM8/edit?pli=122:16
zehicle_hey!  ok, and I'm putting up an etherpad so we can edit the ones that we choose to work on22:16
zehicle_https://etherpad.openstack.org/p/DefCoreRefStackUseCases22:16
*** Duane_ has joined #openstack-meeting-alt22:17
joshuamckentyCan we force-rank them as well?22:18
zehicle_yes, that's what I was thinking22:18
zehicle_we would pick the top 5 and force rank22:18
zehicle_leave the rest for later22:18
zehicle_on that doc, we highlighted the top set in yellow22:18
*** Haiying has joined #openstack-meeting-alt22:18
zehicle_I'd like to limit our top 5 as being from that list22:19
joshuamckentyagreed22:19
joshuamckentyI'm tweaking some words, though22:20
joshuamckentyfoundation(2) -22:20
*** davidlenwell has joined #openstack-meeting-alt22:20
zehicle_let's get the top 5 onto the etherpad22:20
joshuamckentycommunity needs to indicate important "capabiltivies"22:20
joshuamckentynot tests22:20
zehicle_then add some details22:20
zehicle_I'd like to limit the time spent on this to x:40 at the latest22:20
*** eankutse has quit IRC22:20
zehicle_so we can move on22:20
*** Duane__ has quit IRC22:20
zehicle_ah, can we pick this by blocking work first?22:21
zehicle_e.g.: was thinking that we need a way to upload the resuilts22:21
joshuamckentyI thought that's what I was doing22:21
zehicle_user.322:21
*** yogesh has joined #openstack-meeting-alt22:22
davidlenwellSo the api needs to be planned out and then executed ..  restful api will be needed to upload remote results22:22
joshuamckentyand ops722:22
rocky2So, these are use cases for refstack, not for the defcore capabilities that refstack validates, correct?22:23
zehicle_added22:23
joshuamckentydavidlenwell: is it overwhelming to take "upload", "tag", and "sign" as the top three features?22:23
zehicle_yes, this is refstack22:23
joshuamckentye.g., I'd like to jump straight to a signed upload22:23
davidlenwelljoshuamckenty: I don't think so22:23
*** yogesh has quit IRC22:23
zehicle_joshuamckenty, +122:23
joshuamckentyit deals with vendor.4 as well22:24
zehicle_except that we need to have a target for people working on t-cup22:24
joshuamckentyand vendor.322:24
davidlenwellif the user has an ssh key in a keychain that is assosiated with a launch pad account  then signing it will be easier22:24
zehicle_I'd like to be able to have the collect results work run in parallel22:24
joshuamckentyzehicle_: I think that's the capabilities bucketing22:24
zehicle_so, I think that signing the results is not as critical right now22:24
davidlenwellSo the t-cup uploader doesn't need to think about anything .. it will just post the results with a pub key and refstack will deal with validating it22:25
fungijust to be clear, signing is only to avoid someone spoofing results as if they came from a particular provider when they did not?22:25
joshuamckentyfungi: correct22:25
fungiso avoiding impersonation. got it22:25
joshuamckentyor to prevent getting a bunch of anonymous reports22:25
joshuamckentye.g., 500 uploads of the same test results22:26
zehicle_I think that's a critical feature22:26
joshuamckentyto skew community input22:26
joshuamckentyzehicle_: that's what I mean by signed upload22:26
*** mattgriffin has quit IRC22:26
zehicle_I want to make sure that we're unblocked22:26
joshuamckentynot actual result signing, just a validated user22:26
zehicle_> does everyone know what I mean by t-cup?22:26
fungiwell, signatures don't necessarily prevent anonymity if each is submitted with a different throwaway key, but that can be gotten into later22:26
davidlenwellzehicle_: I don't see any reason why this would block anyone22:26
joshuamckentyfungi - if they have to be in launchpad they do22:27
zehicle_if it does not block, then I'm fine22:27
joshuamckentyzehicle_: do you think tagging needs to be in t-cup?22:27
rocky2No idea on t-cup except from the context.22:27
zehicle_joshuamckenty, no22:27
joshuamckentyrunning tempest in docker22:27
davidlenwellno docker22:27
joshuamckentyand then uploading the results to refstack22:27
joshuamckentyoh, just container?22:27
joshuamckentyor just the refstack cli22:27
joshuamckentyrefstack-local22:27
*** sparkycollier has quit IRC22:27
davidlenwella container22:27
zehicle_joshuamckenty, I think that tagging should be a server thing so that they are shared22:27
rocky2tnx22:27
zehicle_IMHO, we could limited tagging to just admins for now22:27
joshuamckentyno22:27
davidlenwellfungi:  it will work a lot like infra in the end because in the end infra will run this22:28
joshuamckentyb/c we want the community to tag the capabilities that they think are imporant22:28
fungitying new official openstack activities to launchpad is a bit problematic. we'd (community at large) really like to get away from lp al together22:28
zehicle_having infra running it is not a requirement for now22:28
davidlenwellSo t-cup is just a script that runs tests22:28
joshuamckentyfungi: is there an API against the openstack member DB yet?22:28
zehicle_I'm not sure they are the same use case22:28
davidlenwelljoshuamckenty: I was just typing that22:28
zehicle_since we want the t-cup people to be able to run from generic systems22:28
davidlenwellzehicle_: I think we can accept both signed and unsigned results from anywere ..22:29
zehicle_ok22:29
davidlenwellwe want the data no matter what22:29
fungijoshuamckenty: not that i've been told. would be nice. would be nice to let members submit openpgp (or x.509 or whatever) ids to the foundation member database too, though we don't collect those from anyone today22:29
joshuamckentydavidlenwell: as far as capturing "config" info from the tested environment, any ideas?22:29
zehicle_davidlenwell, can we accept unsigned first22:29
zehicle_and then allow signed later22:29
joshuamckentynumber of nodes, hypervisor, etc22:29
davidlenwellI don't see why we can't just do both .. its not a complicated thing22:30
zehicle_BTW, I'm expecting that we'll purge data on a regular basis during Feb22:30
joshuamckentyyes22:30
zehicle_and then start keeping it after we work out the process22:30
joshuamckentyokay, that makes sense then22:30
zehicle_yes, let's do both22:30
davidlenwellSo next topic ?22:30
rocky2can't we get the config info from the target db?22:30
davidlenwellif the admin running the tests has an admin account on the cloud we should be able to collect a lot of info22:31
zehicle_we've got a workable set of top use-cases22:31
zehicle_everyone ok to move to the next part of the discussion?22:31
joshuamckentyzehicle_: the first two are dupes22:31
zehicle_cool!22:32
zehicle_fewer is better for us right now22:32
zehicle_I'd like to have us focus on knocking down a small set22:32
joshuamckentyagreed22:32
*** mattgriffin has joined #openstack-meeting-alt22:33
joshuamckentyOh, sorry22:33
davidlenwellso tagging22:33
*** Alex_H has quit IRC22:33
joshuamckentystep 1 is fix some stuff22:33
joshuamckentyso that what we've got works :)22:33
zehicle_do we have a working base RefStack website?22:33
joshuamckentystep 2 is upload and tagging22:33
davidlenwellmostly22:33
joshuamckentyhence, step 122:33
joshuamckentyso davidlenwell22:33
joshuamckentywe could probably subdivide here22:34
davidlenwellSo what do we have now.. and what is missing ..22:34
zehicle_we need everyone to be able to use RefStack UI/API locally22:34
zehicle_I think that should be a goal for the sprint22:34
davidlenwellagreed ..22:34
joshuamckentywe need to take the updated capabilities22:34
joshuamckentyand update the refstack scorecard22:34
joshuamckentyand we REALLY need to make sure we're all running the havana-tagged tempest branch22:34
joshuamckentyand not trunk22:35
zehicle_yy22:35
zehicle_some of this sprint is going to be just able getting people up to speed w/ code22:35
zehicle_and docs/etc22:35
joshuamckentynot that according to https://github.com/openstack-ops/refstack/network we should probably pull current code back to the main branch22:35
davidlenwellokay .. so about the current code ..22:35
davidlenwellwe've decided to throw away the current cli..22:36
davidlenwelltermie and I came up with a pretty slick way of just making it an extension of the website .. using a restful api22:37
joshuamckentynice22:37
davidlenwellso .. what is mainly missing right now to call this a  working beta is ...22:37
zehicle_:)22:37
joshuamckentyhow long is this sprint?22:37
zehicle_I was thinking weekly22:37
davidlenwellweekly works for me22:37
joshuamckentysquirrel cage22:37
zehicle_small chunks22:37
davidlenwelltwo weeks might be better22:37
joshuamckentytwo weeks, please22:37
zehicle_I'm ok w/222:37
rocky2two weeks22:38
davidlenwelldecided..22:38
joshuamckentyit matches to our internal sprint schedules22:38
joshuamckenty:)22:38
*** Alex_H has joined #openstack-meeting-alt22:38
davidlenwellso .. back to what is missing22:38
zehicle_weekly meetings tho?22:38
joshuamckentyand can we agree that we're going to stick to our *informal* process for another month or two?22:38
davidlenwellthe restful api needs to be designed and built .. I can handle that with ease22:38
joshuamckentyyes22:38
joshuamckentye.g., no stack forge port, dual +1, core team stuff for now22:38
zehicle_davidlenwell, you also have a DB design completed?22:39
davidlenwellzehicle_:  was getting to tht22:39
zehicle_ok22:39
davidlenwellwe need to move the database out of sqlite and use mysql or a cloud db22:39
davidlenwellbecause one of the main hurdles I am running into is sqlite mangles the raw subunit output of the tester22:39
*** alazarev has quit IRC22:39
joshuamckentyokay22:40
davidlenwellwhich makes it imposible to generate a score card from it22:40
zehicle_makes sense22:40
joshuamckentywell, on a local machine22:40
davidlenwellthen we just have t-cup22:40
joshuamckentywe run mysql in the container?22:40
davidlenwellsure22:40
davidlenwellno22:40
* fungi just noticed that the chair never did a #startmeeting refstack, so it's not being recorded as a discrete meeting with minutes/notes22:40
davidlenwellmysql runs someplace were refstack can use it .. on another server22:40
zehicle_sorry22:40
zehicle_#startmeeting22:41
openstackzehicle_: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'22:41
joshuamckenty#startmeeting refstack22:41
openstackMeeting started Thu Jan 30 22:41:04 2014 UTC and is due to finish in 60 minutes.  The chair is joshuamckenty. Information about MeetBot at http://wiki.debian.org/MeetBot.22:41
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:41
*** openstack changes topic to " (Meeting topic: refstack)"22:41
openstackThe meeting name has been set to 'refstack'22:41
fungiawesome22:41
* zehicle_ no meeting karma for me tonight22:41
joshuamckenty#agreed Use Cases are as of in https://etherpad.openstack.org/p/DefCoreRefStackUseCases22:41
joshuamckenty#topic database22:41
davidlenwellAlex_H: was working on tempest in container .. and I still don't have a status of that22:41
*** openstack changes topic to "database (Meeting topic: refstack)"22:41
zehicle_#link https://etherpad.openstack.org/p/DefCoreRefStackUseCases22:41
joshuamckenty#agreed Sprints will be two weeks22:41
joshuamckenty#agreed meetings will continue to be weekly22:42
zehicle_also updating the meeting page on wiki22:42
joshuamckenty#agreed development will continue to be "informal" for a couple more months (no stackforge process)22:42
davidlenwellI don't know if I agree with that one22:42
davidlenwellbut we can discuss it22:42
joshuamckentyokay, let's finish db first22:42
davidlenwellokay22:42
joshuamckentyso we need to get off sqlite22:43
joshuamckentybut we need to support running locally22:43
davidlenwelldatabase .. the local version needs no database.. it just uses the restful api on refstack ..22:43
davidlenwellit can run locally all day long22:43
joshuamckentyand streams the results while tempest is running?22:43
davidlenwelltests are stored in a test-r repo22:43
davidlenwelllocally22:43
joshuamckentyoh, right22:43
joshuamckentytest-r is cray-cray22:43
davidlenwellno .. when the test is done .. the results are pulled and uploaded throught he api22:43
joshuamckentyah, k22:44
*** mpolanco1 has joined #openstack-meeting-alt22:44
davidlenwelljoshuamckenty: agreed .. test-r is cray cray .. but we have all the support we need on it .. robert colins wrote it and is very helpful when asked22:44
joshuamckentytotally agree22:44
joshuamckentyokay, so I can take switching prod refstack to mysql or postgres22:44
catherineDSo all local run will have data upload.  What if we are in private network and can not access RefStack.22:44
joshuamckentyany preference?22:44
joshuamckentycatherineD: you don't *have* to upload22:45
davidlenwell++ correct ..22:45
davidlenwellbut you should22:45
joshuamckentybut it won't influence defcore or prove certification if you don't22:45
davidlenwell.. yeah that22:45
davidlenwellstop typing faster than me joshuamckenty.. ;)22:45
joshuamckenty:)22:45
*** mpolanco has quit IRC22:45
joshuamckentyit's how I win arguments22:45
zehicle_the upload process should be just a webpost22:46
davidlenwellmost networks can get out .. but you won't be able to get back in ..22:46
zehicle_so, if you can access both your cloud and the refstack site then tcup can report for you22:46
davidlenwellusually there is a proxy or something22:46
zehicle_effectively, tcup is a bridge22:46
catherineDI was thinking of in the case of private cloud.  We can run the test locally and then export the result and up load via a RefStack accesible network server22:46
*** RajeshMohan has quit IRC22:46
davidlenwellprivate clouds need internet access too22:46
zehicle_catherineD, yes, that's the idea22:46
davidlenwellusually they can call out .. but don't have routes back in unless specifically opened22:47
rocky2Some private clouds don't need the internet22:47
rocky2or rather don't want it22:47
zehicle_rocky2, but the clients are not isolated22:47
davidlenwellI would suggest using a proxy server while certifying and then shutting it off22:47
joshuamckenty#action pull dlenwell's branch back into the openstack-ops branch22:47
*** RajeshMohan has joined #openstack-meeting-alt22:47
davidlenwelljoshuamckenty: pull request ?22:47
catherineDrocky2.  Yest, not all private cloud hav network22:47
joshuamckentyyeah22:48
rocky2proxy might work.  Need a "batch" or "ship when I say" capability for reporting22:48
zehicle_let's slow down a little22:48
davidlenwellcatherineD: I don't know how we'll be able to solve that problem just yet ..22:48
joshuamckentydid you have a preference on mysql vs. postgres, david?22:48
zehicle_I'd prefer postgresql but can adapt22:48
davidlenwellI defualt to mysql because I hate psql ..but I can also adapt22:48
zehicle_rocky2 & catherineD - we've broken the problem into two parts22:49
davidlenwellalso .. infra has to run this22:49
joshuamckentywell, I like running refstack on top of cloud foundry on top of AWS (because it's ironic)22:49
davidlenwellthey usually use mysql ..22:49
joshuamckentythere's no evidence that infra has to run it22:49
joshuamckentyalthough I don't object to them doing it22:49
davidlenwellI don't want to long term22:49
zehicle_I think that adds compelxity22:49
joshuamckentyeventually22:49
zehicle_we should focus on making it easy to run tempest against clouds where the user does not have other infrastructure22:50
davidlenwellI'd rather not have to rebuilld it to pass it along22:50
rocky2zehicle_  agreed on the complexity22:50
zehicle_so, I should be able to run it from my laptop against my internal clouds22:50
joshuamckentyzehicle_: we should focus on being able to gather and collate tempest runs from many clouds22:50
davidlenwelljoshuamckenty: I don't think we should base engineering decisions on how ironic they are .. but thats just me22:50
zehicle_those clouds would have have external access, but I can reach them internally22:50
rocky2zehicle_ +122:50
joshuamckentydavidlenwell: that's the entire history of OpenStack, though22:50
zehicle_when I run the tests, I can tehn upload the results to refstack22:50
zehicle_because my laptop is connected to the internet (even if the cloud I tested is now)22:51
zehicle_not22:51
joshuamckentyanyway, I'm going mysql22:51
zehicle_+1 on mysql22:51
joshuamckentyb/c it's supported by -infra and cloud foundry22:51
joshuamckentyand farmboy22:51
zehicle_#agree mysql22:51
zehicle_already on the etherpad22:51
davidlenwellyeah .. and termie already did a lot of the work for refstack to use mysql in farm boy22:51
joshuamckentyyup22:51
davidlenwellso done .. next topic22:51
joshuamckentyokay - do you want to talk about stackforge process now?22:52
davidlenwellyes22:52
joshuamckentymy concern is just that it will slow us down in the short term22:52
zehicle_for this sprint, I think willing participants need to get your refstack working on their local envuronements22:52
joshuamckentyand we're under a lot of time pressure22:52
rocky2How about changing the topic officially?22:52
joshuamckenty#topic stackforge22:52
*** openstack changes topic to "stackforge (Meeting topic: refstack)"22:52
davidlenwellyes ..22:52
*** _0x44 has joined #openstack-meeting-alt22:52
davidlenwellstackforge process I think is important for two reasons22:52
davidlenwell1. people contributing will be elegable for coupon codes to attend the summit in atlanta22:53
davidlenwellright now they wouldn't be22:53
rocky2Somebody reviews the code before checkin22:53
davidlenwellit would require a plus two from a core dev22:53
joshuamckentyrocky2: we do that now, it doesn't require stack forge. (Although it is a side effect)22:53
joshuamckentydavidlenwell: is that a bonus?22:54
rocky2Can we do it with a +1?  loosen the rules for the project?22:54
zehicle_would make it easier to me to engage my team if they would show up as ATCs22:54
joshuamckentydefine refstack core right now: me, you, and termie?22:54
joshuamckentyrocky2: +122:54
*** mpolanco1 has quit IRC22:54
zehicle_would help attract people22:54
davidlenwellI don't want to be all power hungry .. but I don't want 10 conflicting pull requests to deal with merging manually22:55
fungiwell, being a stackforge project contributor won't get anyone free summit passes. being an openstack{,-dev,-infra} contributor will. but by "stackforge" i assume you really mean "openstack"22:55
*** jecarey has quit IRC22:55
davidlenwellzehicle_: thats my other point .. being in gerrit review process is a known thing in the comminity and a work flow these guys are used to22:55
fungijust need to figure out what official program the project belongs within, in that case22:55
davidlenwellI don't want to be seen as different or special22:55
joshuamckentyI do22:55
zehicle_I'm in favor22:55
joshuamckenty:)22:56
*** konetzed has quit IRC22:56
zehicle_I think that we're solving problems that we don't have - not that many contributors22:56
rocky2joshuamckenty:  +122:56
joshuamckentyIf you suggest making this an official openstack project, you'll immediately lose two of the three core devs22:56
davidlenwellbefore atlanta I want to be in gerrit review22:56
joshuamckentybecause neither termie nor I will keep contributing22:56
joshuamckentybut the ATC temptation may mitigate that22:57
joshuamckentye.g., you might get enough new devs to make it a good trade22:57
davidlenwelltermie would be a loss .. but you are too busy to be that active on this anyways22:57
davidlenwelloutside of planning22:57
zehicle_lets plan a transition and move on.  really, I would not expect you to remain a maintainer22:57
joshuamckentyalso true22:57
joshuamckentyso once we have PRs from two other devs, I think we should pull the trigger22:58
zehicle_can we talk about work items for the sprint?22:58
davidlenwelllets put planning the transition on the agenda for next week22:58
joshuamckentya reasonable compromise?22:58
zehicle_+122:58
davidlenwellagreed22:58
rocky2+022:58
zehicle_adding to the wiki page22:58
joshuamckenty#topic sprint work items22:59
*** openstack changes topic to "sprint work items (Meeting topic: refstack)"22:59
davidlenwellitem one .. t-cup22:59
davidlenwella few weeks ago .. Alex_H and I were planning to make tempest in a docker container22:59
zehicle_# agenda: Transition of RefStack into OpenStack management22:59
davidlenwellafter much deliberation I decided that docker wasn't the right move .. docker is still very imature23:00
*** nati_uen_ has joined #openstack-meeting-alt23:00
zehicle_Alex_H had it working23:00
zehicle_for what we're doing, it's a reasonable and fast way to get it distributed23:00
davidlenwellI've been trying to sync with him for a few days .. we keep missing each other23:00
zehicle_he's not available until after 2 your time23:00
davidlenwellI'll try to chat with him today ..23:01
*** nati_uen_ has quit IRC23:01
zehicle_he's on the IRC23:01
joshuamckentylet's focus on the upload API23:01
davidlenwellSo lets table the tcup talk for now23:01
davidlenwellthe api23:01
joshuamckentysince that's agnostic to what was used to run the code23:01
davidlenwellis dependant on the database23:01
zehicle_#topic API23:01
joshuamckentyI'll do the DB right away23:01
zehicle_we do need a way for users to run the tests locally23:01
*** nati_uen_ has joined #openstack-meeting-alt23:01
joshuamckentydavidlenwell: we've been putting the work items into https://etherpad.openstack.org/p/DefCoreRefStackUseCases23:01
*** jprovazn_afk has quit IRC23:01
joshuamckentyzehicle_: we have that23:01
joshuamckentythere's a refstack CLI already23:01
davidlenwellyes ..23:02
joshuamckenty(which davidlenwell and termie want to rewrite)23:02
zehicle_ok, let's get the documented23:02
joshuamckenty:)23:02
joshuamckentyhttps://github.com/dlenwell/refstack/tree/master/refstack/cli23:02
davidlenwellwell right now it lets you add clouds and generate configs adn then execute tests ..23:02
davidlenwelltthe testing part I want to replace with tcup as what is there is a hack job23:03
davidlenwellthe config generation is pretty strong23:03
*** nati_ueno has quit IRC23:03
joshuamckentyhttps://github.com/dlenwell/refstack/blob/master/refstack/cli/refstack#L11423:03
davidlenwellthe store the results thing doesn't work with sqlite23:04
davidlenwellwhich this version of the cli is dependant on23:04
joshuamckentyhttps://github.com/dlenwell/refstack/blob/master/refstack/common/tester.py#L95 ?23:04
catherineDSo have we decided to replace CLI with Restful API.  CLI is what we have been focused on for local test.23:04
joshuamckentyno, there will still be a CLI23:04
davidlenwellno .. let me clearify23:04
joshuamckentywe're going to add an API for upload23:04
joshuamckentyto refstack.org23:04
davidlenwellthere will be a cli .. it will just work a lot differently23:04
catherineDThat is great.23:05
davidlenwellthe cli .. will generate the config .. trigger tcup .. capture the results from tcup and upload them through the api to refstack23:05
*** kevinconway has quit IRC23:05
rocky2Wanna capture that in the etherpad?23:06
davidlenwellI want to make a flow chart explaining the behavior23:06
rocky2cool23:06
davidlenwellone thing that is seriously lacking in this project is a propper high level design document23:06
davidlenwellthat takes the use cases into account23:07
joshuamckenty#chair zehicle_23:07
openstackCurrent chairs: joshuamckenty zehicle_23:07
joshuamckenty#chair davidlenwell23:07
openstackCurrent chairs: davidlenwell joshuamckenty zehicle_23:07
joshuamckentyguys, I have to run, I'm sorry23:07
joshuamckentylate for another meeting23:07
zehicle_I'm pulled into my next thing too23:07
davidlenwellso until next time ?23:07
joshuamckentydavidlenwell: can you keep going with technical bits?23:07
davidlenwellsure23:07
joshuamckentymake sure every dev has work :)23:07
davidlenwell:)23:07
joshuamckentyand keep the etherpad updated23:07
rocky2davidlenwell:  +1 for high level design doc.  I'll help anyway I can.23:07
joshuamckentythanks everyone!!!23:07
*** joshuamckenty has quit IRC23:08
catherineDDavid could we meet at #refStack?23:08
davidlenwellsure .. lets move there and gree up this room23:08
catherineDOK thanks a lot!23:08
davidlenwellfungi: how do we end this thing ?23:08
fungidavidlenwell: please #endmeeting23:08
davidlenwell#endmeeting23:09
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:09
openstackMeeting ended Thu Jan 30 23:09:05 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-01-30-22.41.html23:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-01-30-22.41.txt23:09
openstackLog:            http://eavesdrop.openstack.org/meetings/refstack/2014/refstack.2014-01-30-22.41.log.html23:09
fungithanks!23:09
zehicle_I'd like people to have an idea of work to get done23:09
davidlenwellzehicle_: sync with me after your next thing23:09
zehicle_kk - will be tomorrow23:10
*** Haiying has quit IRC23:13
*** Alex_H has quit IRC23:15
*** konetzed has joined #openstack-meeting-alt23:18
*** Haiying has joined #openstack-meeting-alt23:18
*** david-lyle has joined #openstack-meeting-alt23:21
*** Leonr has quit IRC23:22
*** mattoliverau has joined #openstack-meeting-alt23:23
*** sarob has quit IRC23:23
*** Haiying has quit IRC23:25
*** henrynash has quit IRC23:30
*** Ranjitha has quit IRC23:30
*** david-lyle has quit IRC23:31
*** nati_uen_ has quit IRC23:32
*** AlanClark has quit IRC23:32
*** nati_ueno has joined #openstack-meeting-alt23:36
*** denis_makogon has quit IRC23:37
*** FallenPegasus has quit IRC23:46
*** cody-somerville has joined #openstack-meeting-alt23:47
*** flaper87 is now known as flaper87|afk23:51
*** michael-yu has quit IRC23:51
*** yogesh has joined #openstack-meeting-alt23:52
*** rocky2 has quit IRC23:53
*** michael-yu has joined #openstack-meeting-alt23:53
*** SergeyLukjanov_ is now known as SergeyLukjanov23:53
*** Sukhdev has quit IRC23:53
*** NikitaKonovalov_ is now known as NikitaKonovalov23:55

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