Thursday, 2013-10-31

*** yamahata has joined #openstack-meeting-alt00:03
*** SumitNaiksatam has quit IRC00:05
*** alazarev has joined #openstack-meeting-alt00:05
*** sacharya has joined #openstack-meeting-alt00:08
*** IlyaE has quit IRC00:19
*** yogeshmehra has joined #openstack-meeting-alt00:19
*** kgriffs is now known as kgriffs_afk00:19
*** betsy has joined #openstack-meeting-alt00:21
*** yogeshme_ has joined #openstack-meeting-alt00:22
*** yogeshmehra has quit IRC00:23
*** sarob has quit IRC00:23
*** sarob has joined #openstack-meeting-alt00:24
*** vkmc has joined #openstack-meeting-alt00:26
*** vkmc has joined #openstack-meeting-alt00:26
*** sarob has quit IRC00:28
*** alazarev has quit IRC00:29
*** yidclare has quit IRC00:31
*** julim has quit IRC00:35
*** yogeshme_ has quit IRC00:45
*** SumitNaiksatam has joined #openstack-meeting-alt00:46
*** SumitNaiksatam has quit IRC00:47
*** saurabhs has quit IRC00:49
*** SumitNaiksatam has joined #openstack-meeting-alt00:49
*** julim has joined #openstack-meeting-alt00:50
*** julim has quit IRC00:50
*** amytron has joined #openstack-meeting-alt00:55
*** rakhmerov has joined #openstack-meeting-alt00:57
*** rakhmerov has quit IRC01:01
*** amytron has quit IRC01:01
*** nosnos has joined #openstack-meeting-alt01:05
*** amytron has joined #openstack-meeting-alt01:12
*** vkmc has quit IRC01:17
*** vkmc has joined #openstack-meeting-alt01:18
*** twoputt has quit IRC01:23
*** twoputt_ has quit IRC01:24
*** colinmcnamara has quit IRC01:26
*** julim has joined #openstack-meeting-alt01:29
*** julim has quit IRC01:29
*** Barker has quit IRC01:49
*** esker has joined #openstack-meeting-alt01:49
*** vkmc has quit IRC01:52
*** rakhmerov has joined #openstack-meeting-alt01:58
*** coolsvap has quit IRC01:58
*** sarob has joined #openstack-meeting-alt02:25
*** gokrokve has joined #openstack-meeting-alt02:30
*** rakhmerov has quit IRC02:31
*** sacharya has quit IRC02:32
*** gokrokve_ has quit IRC02:34
*** colinmcnamara has joined #openstack-meeting-alt02:42
*** rakhmerov has joined #openstack-meeting-alt02:47
*** sacharya has joined #openstack-meeting-alt03:11
*** IlyaE has joined #openstack-meeting-alt03:16
*** sacharya1 has joined #openstack-meeting-alt03:18
*** sacharya has quit IRC03:18
*** tanisdl has quit IRC03:26
*** esker has quit IRC03:35
*** esker has joined #openstack-meeting-alt03:36
*** sarob has quit IRC03:36
*** sarob has joined #openstack-meeting-alt03:36
*** cody-somerville has quit IRC03:39
*** sarob has quit IRC03:41
*** vipul is now known as vipul-away03:45
*** cody-somerville has joined #openstack-meeting-alt03:48
*** nati_ueno has joined #openstack-meeting-alt03:56
*** amcrn has quit IRC03:56
*** sarob has joined #openstack-meeting-alt04:03
*** sarob has quit IRC04:05
*** sarob has joined #openstack-meeting-alt04:05
*** IlyaE has quit IRC04:08
*** sarob has quit IRC04:10
*** nosnos has quit IRC04:17
*** nosnos_ has joined #openstack-meeting-alt04:17
*** nosnos_ has quit IRC04:22
*** nosnos has joined #openstack-meeting-alt04:23
*** eankutse has joined #openstack-meeting-alt04:24
*** nosnos has quit IRC04:26
*** fungi has quit IRC04:26
*** cody-somerville has quit IRC04:27
*** nosnos has joined #openstack-meeting-alt04:29
*** fungi has joined #openstack-meeting-alt04:33
*** nosnos_ has joined #openstack-meeting-alt04:33
*** nosnos has quit IRC04:37
*** cody-somerville has joined #openstack-meeting-alt04:40
*** sacharya1 has quit IRC04:41
*** colinmcnamara has quit IRC04:43
*** colinmcnamara has joined #openstack-meeting-alt04:44
*** colinmcnamara has quit IRC04:48
*** yogeshmehra has joined #openstack-meeting-alt04:53
*** rpodolyaka1 has joined #openstack-meeting-alt04:55
*** eankutse has quit IRC05:04
*** HenryG has quit IRC05:13
*** sarob has joined #openstack-meeting-alt05:16
*** yogeshmehra has quit IRC05:18
*** sarob_ has joined #openstack-meeting-alt05:18
*** sarob has quit IRC05:21
*** nosnos_ has quit IRC05:28
*** nosnos has joined #openstack-meeting-alt05:28
*** yamahata has quit IRC05:37
*** SergeyLukjanov has joined #openstack-meeting-alt05:53
*** akuznetsov has joined #openstack-meeting-alt05:54
*** nosnos_ has joined #openstack-meeting-alt06:06
*** nosnos has quit IRC06:08
*** SergeyLukjanov has quit IRC06:08
*** sdague has quit IRC06:08
*** sarob_ has quit IRC06:12
*** sarob has joined #openstack-meeting-alt06:12
*** sdague has joined #openstack-meeting-alt06:13
*** _ozstacker_ has joined #openstack-meeting-alt06:15
*** SergeyLukjanov has joined #openstack-meeting-alt06:16
*** ozstacker has quit IRC06:17
*** sarob has quit IRC06:17
*** gokrokve has quit IRC06:18
*** gokrokve has joined #openstack-meeting-alt06:19
*** gokrokve has quit IRC06:23
*** denis_makogon has joined #openstack-meeting-alt06:27
*** yogeshmehra has joined #openstack-meeting-alt06:27
*** rpodolyaka1 has quit IRC06:35
*** SergeyLukjanov has quit IRC06:37
*** akuznetsov has quit IRC06:44
*** akuznetsov has joined #openstack-meeting-alt06:45
*** SergeyLukjanov has joined #openstack-meeting-alt06:48
*** yogeshmehra has quit IRC06:50
*** yogeshmehra has joined #openstack-meeting-alt06:59
*** akuznetsov has quit IRC07:04
*** coolsvap has joined #openstack-meeting-alt07:13
*** nosnos_ has quit IRC07:22
*** nosnos has joined #openstack-meeting-alt07:22
*** sarob has joined #openstack-meeting-alt07:23
*** sarob has quit IRC07:28
*** jcoufal has joined #openstack-meeting-alt07:32
*** yamahata has joined #openstack-meeting-alt07:39
*** rushiagr has joined #openstack-meeting-alt07:45
*** flaper87|afk is now known as flaper8708:03
*** akuznetsov has joined #openstack-meeting-alt08:19
*** SergeyLukjanov has quit IRC08:19
*** denis_makogon has quit IRC08:31
*** lsmola_ has joined #openstack-meeting-alt08:41
*** vponomaryov has joined #openstack-meeting-alt08:44
*** yamahata has quit IRC08:59
*** yogeshmehra has quit IRC09:01
*** rushiagr has quit IRC09:02
*** rushiagr has joined #openstack-meeting-alt09:03
*** rushiagr has left #openstack-meeting-alt09:11
*** yamahata has joined #openstack-meeting-alt09:13
*** derekh has joined #openstack-meeting-alt09:30
*** flwang has quit IRC09:33
*** flwang has joined #openstack-meeting-alt09:47
*** jtomasek has joined #openstack-meeting-alt09:54
*** yamahata has quit IRC09:57
*** derekh has quit IRC10:20
*** jcoufal is now known as jcoufal_afk10:22
*** jog0 has left #openstack-meeting-alt10:33
*** derekh has joined #openstack-meeting-alt10:35
*** akuznetsov has quit IRC10:47
*** nosnos has quit IRC10:51
*** coolsvap has quit IRC10:59
*** jprovazn has joined #openstack-meeting-alt11:03
*** flaper87 is now known as flaper87|afk11:30
*** vkmc has joined #openstack-meeting-alt11:30
*** vkmc has joined #openstack-meeting-alt11:30
*** tedross has joined #openstack-meeting-alt11:35
*** tedross has left #openstack-meeting-alt11:36
*** akuznetsov has joined #openstack-meeting-alt11:37
*** pcm_ has joined #openstack-meeting-alt11:44
*** yamahata has joined #openstack-meeting-alt12:00
*** pdmars has joined #openstack-meeting-alt12:03
*** amytron has quit IRC12:04
*** venkatesh has joined #openstack-meeting-alt12:06
*** esker has quit IRC12:10
*** esker has joined #openstack-meeting-alt12:10
*** esker has quit IRC12:14
*** venkatesh has quit IRC12:23
*** venkatesh has joined #openstack-meeting-alt12:27
*** flaper87|afk is now known as flaper8712:41
*** kevinconway has quit IRC12:49
*** kevinconway has joined #openstack-meeting-alt12:56
*** dprince has joined #openstack-meeting-alt13:02
*** lblanchard has joined #openstack-meeting-alt13:05
*** aignatov has joined #openstack-meeting-alt13:27
*** esker has joined #openstack-meeting-alt13:34
*** imsplitbit has left #openstack-meeting-alt13:37
*** Barker has joined #openstack-meeting-alt13:42
*** eankutse has joined #openstack-meeting-alt13:46
*** eankutse has quit IRC13:47
*** eankutse has joined #openstack-meeting-alt13:47
*** Barker_ has joined #openstack-meeting-alt13:48
*** Barker has quit IRC13:49
*** coolsvap has joined #openstack-meeting-alt13:52
*** kgriffs_afk is now known as kgriffs13:55
*** HenryG has joined #openstack-meeting-alt14:01
*** venkatesh has quit IRC14:01
*** lsmola_ has quit IRC14:02
*** esker has quit IRC14:12
*** gokrokve has joined #openstack-meeting-alt14:14
*** jergerber has joined #openstack-meeting-alt14:15
*** mayfield has joined #openstack-meeting-alt14:19
*** sacharya has joined #openstack-meeting-alt14:20
*** coolsvap has quit IRC14:32
*** sacharya has quit IRC14:36
*** jmontemayor has joined #openstack-meeting-alt14:46
*** caitlin56 has joined #openstack-meeting-alt14:52
*** aostapenko has joined #openstack-meeting-alt14:52
*** dhellmann-afk is now known as dhellmann14:54
*** eharney has joined #openstack-meeting-alt14:55
*** shamail has joined #openstack-meeting-alt14:56
*** betsy has quit IRC14:57
*** ruhe has joined #openstack-meeting-alt14:57
*** betsy has joined #openstack-meeting-alt14:58
*** glenng1 has joined #openstack-meeting-alt14:59
*** gregsfortytwo1 has joined #openstack-meeting-alt14:59
*** jcorbin has joined #openstack-meeting-alt14:59
*** lpabon has joined #openstack-meeting-alt15:00
*** bswartz has joined #openstack-meeting-alt15:01
bswartz#startmeeting manila15:01
openstackMeeting started Thu Oct 31 15:01:06 2013 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
bswartzhey guys15:01
vponomaryovhi15:01
bswartzlast meeting before HK15:01
aostapenkohi15:01
*** yidclare has joined #openstack-meeting-alt15:01
shamailHello15:01
*** bill_az has joined #openstack-meeting-alt15:02
glenng1Whaa Hoo15:02
bswartz#link https://wiki.openstack.org/wiki/ManilaMeetings15:02
*** glenng1 is now known as glenng15:02
*** amytron has joined #openstack-meeting-alt15:02
bswartzso the main thing is the conference15:02
bswartz#topic conference15:02
*** openstack changes topic to "conference (Meeting topic: manila)"15:02
bswartzfor those of you attending the conference, we've settled on 5:30 tuesday for our meetup15:03
*** ni291187 has joined #openstack-meeting-alt15:03
bswartzI still need you to RSVP if you haven't already: bswartz@netapp.com15:03
*** IlyaE has joined #openstack-meeting-alt15:03
*** ni291187 is now known as alexpecoraro15:04
bswartzThe location is not set yet, but we will find a nice corner of the hotel bar and reserve it for 90 minutes or so15:04
shamailGreat, look forward to it.15:04
bswartzI'll get drinks for anyone who's been coming to these meetings15:05
*** bvandehey has joined #openstack-meeting-alt15:05
bswartzadditionally, I'll try to fit in an unconference sessions15:05
bswartzsession*15:05
*** kiall has quit IRC15:05
bswartzI still need to go over the schedule and find a timeslot that doesnt' conflict15:06
*** lsmola has joined #openstack-meeting-alt15:06
shamailbswartz: What will be the method of sending out additional sessions? Email?15:06
bswartzoverall I'm excited about hte conference -- many of the summit sessions look interesting15:06
bswartzwell for the tuesday get together I'll be sending out the location to people who've RSVPd15:07
bswartzJeff Oneal will get to HK early and reserve a place15:07
bswartzfor the unconference session it will be posed on the whiteboard near the unconference rooms15:07
shamailbswartz: Okay, thanks!15:08
bswartzI'll do that first thing tuesday so if it isn't posted tuesday morning then it means I probably couldn't find a time that works15:08
*** kiall has joined #openstack-meeting-alt15:08
bswartzanyone have any other questions about our plans for HK?15:09
bswartzthey're very modest this time around -- expect more for the J-release conference15:10
bswartzokay15:10
bswartz#topic dev status15:10
*** openstack changes topic to "dev status (Meeting topic: manila)"15:10
*** jcoufal_afk is now known as jcoufal15:10
*** sacharya has joined #openstack-meeting-alt15:10
*** aignatov has quit IRC15:10
bswartzso I've learned a few things about linux containers15:10
bswartz(1) they need their own filesystem root, they cannot share the filesystem root with the parent OS15:11
*** nwidell has joined #openstack-meeting-alt15:11
bswartz(2) LXC is actually a fairly immature linux container implementation -- OpenVZ is another implementation that uses the same kernel feature (containers) and is much more production ready15:12
vponomaryovActually, NFSkernel server does not work in OpenVZ too15:12
bswartzIf we do go down the linux containers path, I think we'll lean towards OpenVZ over LXC -- they're both supported by libvirt btw15:12
bswartzoh that's a third thing15:13
caitlin56A key test of these containers is whether you can do per tenant DNS and DHCP.15:13
bswartz(3) You can't use the Kernel NFS server with linux containers, because you only get 1 kernel15:13
*** caitlin56 has quit IRC15:13
*** caitlin56 has joined #openstack-meeting-alt15:13
bswartzthanks vponomaryov15:13
bswartzcaitlin56: I'm fairly certain that won't be an issue, but it's worth confirming15:13
bswartzthere is a user-space NFS server that allows us to overcome the 3rd issue15:14
bswartzbut the first issue is the one that concerns me most15:14
caitlin56bswartz: my research says that it is possible, but not the default configuration with most of them.15:14
aostapenkoand user nfs server supports only nfs315:14
gregsfortytwo1bswartz: you're looking at Ganeti?15:15
*** ruhe has quit IRC15:15
bswartzif the LVM driver for Manila is going to rely on a specially-crafted root filesystem, then we're going to have to maintain a little "distribution" of sorts including all the binaries needed to run the container15:15
caitlin56aosstapenko: this is a solution for testing, right? nfs3 is good enough.15:15
*** navneet has joined #openstack-meeting-alt15:15
*** colinmcnamara has joined #openstack-meeting-alt15:16
bswartzif we end up having to maintain a distro, it's probably better to go with something off the shelf and fully virtualize it15:16
gregsfortytwo1err, Ganesha I mean15:16
*** vipul-away is now known as vipul15:16
bswartzthe point of the LVM driver is to provide full functionality in a software-only mode -- to be a reference implementation15:17
bswartzfull virtualization is less efficient than containers but it seems that containers don't buy us much other than efficiency15:17
bswartzand with all the limitations, I think people would be happier with full virtualization and access to the kernel NFS server, etc15:18
vponomaryovbswartz: maybe we should do containers support as more flexibility, fot those, who will use Samba, etc ?15:18
bswartzWe could, for example, find a really stripped-down version of Debian, add some scripts to it, and use that as our NFS/CIFS server15:19
*** SergeyLukjanov has joined #openstack-meeting-alt15:19
*** SergeyLukjanov is now known as _SergeyLukjanov15:19
bswartzif we write the scripts right, then perhaps we could even leave it up to the admin to find his own distro (for people who prefer redhat, for example)15:19
*** alexpecoraro has quit IRC15:19
*** _SergeyLukjanov is now known as SergeyLukjanov15:20
*** ruhe has joined #openstack-meeting-alt15:20
*** yamahata has quit IRC15:20
bswartzvponomaryov: containers may still be a valid backend, but I think from the manila side we want to limit the complexity15:20
bswartzgregsfortytwo1: sorry I'm not familiar with ganesha15:20
*** vipul is now known as vipul-away15:20
gregsfortytwo1oh, you said user-space nfs server, it's the only one of those I'm familiar with15:21
bswartzgregsfortytwo1: is that the same as unfs3?15:22
aostapenkoactually it is unfs315:22
gregsfortytwo1don't think so…looks like https://github.com/nfs-ganesha/nfs-ganesha/wiki is the homepage?15:22
bswartzhmm15:22
bswartzI wonder what you get when you apt-get install nfs-user-server15:23
aostapenkonothing15:23
vponomaryovbswartz: nfs-user-server is absent in repos15:23
aostapenkowe need to get the source15:23
vponomaryovand it is different from uns315:23
bswartzvponomaryov: it existed back in 8.0415:23
bswartzperhaps it got removed15:23
gregsfortytwo1yeah, looks like removed from Debian in 200915:24
gregsfortytwo1http://packages.qa.debian.org/n/nfs-user-server.html15:24
bswartzin any case, my feeling is that the nfs-kernel-server is more feature rich and better maintained15:24
gregsfortytwo1anyway, Ganesha is interesting to me because it has a pluggable interface to its backing filesystem, but I don't know anything else about it15:24
*** alexpecoraro has joined #openstack-meeting-alt15:25
caitlin56So the real tradeoff is NFS-kernel under a VM versus userland NFS with containers. Given the goals of the project, I suspect that VMs make more sense. But either would work.15:25
bswartzbut more important than that, full virtualization will probably be easier to implement and easier to maintain15:26
caitlin56agreed VMs simpler than containers, nfs-kernel simpler than user-mode kernel.15:27
bswartzif we write the LVM driver to assume a fully virtualized server (under nova) then all we need to do is define the software that must exist inside the VM, and define the management interface between manila and that15:27
bswartzI'm undecided on whether we should specify a Linux distro or remain agnostic about that15:28
vponomaryovbswartz: I think, it will be customer friendly to have image in glance special for that15:29
bswartzvponomaryov: well customers (end users) probably will never see the VMs directly15:30
bswartzthese real customer of manila is the administrator15:30
*** aignatov has joined #openstack-meeting-alt15:30
caitlin56bswartz: I think you want to spec a Linux distro with at least these versions of these packages.15:30
bswartzand the administrator may want freedom to use a different image15:30
*** alazarev has joined #openstack-meeting-alt15:30
bswartzsome people have strong feelings -- I can't imagine redhat running an debian-derivative, and I can't imagine canonical running a redhat-derivative15:31
bswartzI don't want to get in the middle of that15:31
jcorbinbswartz: are you suggesting that the reference implementation of the Manila server would be running on a VM provisioned by Nova?15:31
bswartzjcorbin: that seems to be the path of least resistence15:32
bswartzjcorbin: and it always fits very nicely within the design of openstack15:32
bswartzs/always/actually/15:32
jcorbinbswarz: I like that because then the network will be provisioned for you. Agree with path of least resistence15:32
*** ruhe has quit IRC15:33
bswartzokay so that's a nice segue into talking about the network stuff again15:33
bswartzyportnova: you here?15:33
vponomaryovno, she is absent15:33
bswartzvponomaryov: do you have an update15:33
bswartzhow is the prototype for the neutron API calling code15:34
vponomaryovActually, we had an update with containers, which are already discussed, and one another thing is that15:34
vponomaryovnetwork code for quantum is blocked by driver with/out containers or full virtualisation15:34
vponomaryov*of15:35
bswartzvponomaryov: I'd like to model the network configuration code around what's most likely to work with real hardware backends15:35
bswartzbecause those are going to be less flexible than the software backend15:35
bswartzWe need to prove that the design works for both software and multiple hardware backends to have confidence, of course15:36
caitlin56I'm trying to gather a set of requirements from our field engineers about what real customers need to do for "network" configuration to support NFS and CIFS.15:36
caitlin56I'll post once I have gathered, but I am concerned that the neutron dhcp-agent does not look to be adequate for this use. It only assigns IP addresses.15:37
caitlin56and gateway.15:37
*** ruhe has joined #openstack-meeting-alt15:37
bswartzcaitlin56: netapp devices don't use DHCP at all -- it's all static configuration15:37
*** jaypipes has joined #openstack-meeting-alt15:37
shamailsame.15:37
bswartzmanila will need to have the capability to statically configure backends15:37
caitlin56But what about your clients?15:37
bswartzthe client is the one giving us the information15:38
bswartzthe client supplies the DNS server IP, the AD domain name, the AD credentials, etc15:38
caitlin56You don't have clients that are getting the AD or LDAP server from the DHCP server?15:38
bswartzin most cases OpenStack won't even have that information15:38
bswartztypically clients get teh DNS server from DHCP and find everything else through DNS15:39
caitlin56That might be good enough.15:39
bswartzif there are backends that can't work without DHCP then we'll need to look into how to support those15:40
bswartzbut right now I'm under the impression that DHCP not a critical piece of intrastructure, outside of assigning IPs/netmasks/gateway/DNS15:40
shamailThis part of the networking discussion is discussing services, we assume base connectivity to the tenant's network is established?  Sorry, missed last week.15:41
*** nwidell has quit IRC15:41
bswartzshamail: yes15:41
bswartzwe're prototyping the code that manila will use to call neutron and wire in a storage controller directly to a tenant VLAN15:41
*** caitlin56 has quit IRC15:42
*** caitlin56 has joined #openstack-meeting-alt15:42
bswartzvponomaryov: it may make sense to base the prototype on a netapp backend rather than the LVM backend, so the 2 projects can proceed in parallel15:42
caitlin56Telling tenants that a) they need a static IP for their openstack launched clients and b) that they find other services on their tenant network via DNS is probably acceptable.15:43
bswartzcaitlin56: My intent is that neutron will still own the IP assigning, but the backend will be statically configured15:44
bswartzthe clients shouldn't need to do anything different15:44
jcorbinbswartz: With the reference port, with LVM and no HW storage controller,I would think that the VM is already wired into the tenant network when it is created. You just specify the networks you want to configure the Manila VM to. Is that correct?15:45
bswartzunless perhaps they're running an AD server inside the cloud -- that would need a static IP beacuse AD servers changing IPs seems like bad news15:45
caitlin56As I understand neutron, you can't just fire off a VM that has no IP address before the tenant DHCP gives it to them.15:45
bswartzjcorbin: yeah15:46
caitlin56THe VM might not *know* its IP address until it asks for it via DHCP, but it was determined before the VM launched.15:46
*** shamail_ has joined #openstack-meeting-alt15:46
*** dprince has quit IRC15:47
*** shamail has quit IRC15:47
*** shamail_ is now known as shamail15:47
bswartzokay I'm getting confused here15:47
bswartzwe have 2 topics going on I think15:47
bswartzthe LVM backend and the network config15:47
shamailsorry, disconnected.15:48
jcorbincaitlin56: I see the problem. I will see if there is a way to statically allocate a VM to a tenant network.15:48
caitlin56Difference is very technical. DHCP has rules on how quickly an IP address can be reassigned. Neutron does not.15:48
bswartzfor the purposes of network config, let's assume a hardware based backend with static configuraiton15:48
caitlin56It's a minor distinction that no customer should object to, but one that they should be warned about.15:48
shamailbswartz: that will probably provide the most flexibility in accommodating numerous options.15:49
bswartzis neutron not able to give permanent leases out?15:49
bswartzif it isn't then I can see how that presents a problem15:49
caitlin56Neutron leases can be changed by admin at any time. Not exactlythe same rules as for DHCP dynamic leases.15:50
*** twoputt has joined #openstack-meeting-alt15:50
caitlin56But the admin can choose to follow those rules.15:50
*** twoputt_ has joined #openstack-meeting-alt15:50
jcorbinbswartz: I can look into that. I would think that the Ironic project would want static IPs for dedicated instances.15:51
bswartzvponomaryov: have you looked at obtaining an IP address from neutron on a permanent basis?15:51
bswartzjcorbin: thanks, I agree15:51
vponomaryovbswartz: I haven't info about this15:51
bswartzokay15:51
bswartzsome more stuff to look into15:52
bswartzso I will be busy next week, as will many of you I imagine15:52
caitlin56It's more an issue for anyone who was *relying* on dynamic addresses. But those are pretty rare.15:52
bswartzwe'll cancel next week's meeting right now15:52
bswartzand plan to meet again on 14 Nov15:52
bswartz#topic open discussion15:53
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:53
caitlin56The 14 Nov meeting, what time will that be for those of us on the west coast?15:53
bswartzanything else to talk about before we head off to HK?15:53
vponomaryovbswartz: we have several slides for, we will send it in email15:54
icchahey the qonos nodes in prod have 75 workers, would be great if we could merge these prs to reflect state in prdocution:15:54
icchahttps://github.rackspace.com/O3Eng/region-ord/pull/10215:54
bswartzcaitlin56: thanks for the reminder15:54
icchahttps://github.rackspace.com/O3Eng/region-ord/pull/6815:54
bswartzso because DST ends for those of us who are US-based, this meeting remains at 1500 UTC15:55
icchahttps://github.rackspace.com/O3Eng/region-dfw/pull/7715:55
icchahttps://github.rackspace.com/O3Eng/region-dfw/pull/4815:55
bswartzthat means it will be 1 hour earlier on your calendar if you're US-based, until DST kicks in again on 2014 March 1015:55
icchasorry wrong window15:55
caitlin56bswart: not a problem for me. But most west coast based engineers are more likely to *still* be up at 7:00 AM than to have woken up.15:56
caitlin56You might want to see if you can get a better time slot.15:56
bswartzcaitlin56: I knew about this issue when I scheduled the meeting -- it's an unavoidable problem when trying to schedule these worldwide meetings15:57
bswartzI would have chosen a later timeslot but they're all taken15:57
*** alexpecoraro has left #openstack-meeting-alt15:57
*** aignatov has quit IRC15:57
caitlin56ok, might not be a problem. Everyone willing to do irc at 8:00 AM might be able to do 7:00.15:58
bswartzunfortunately our west coast friends will need to wake up early for a couple of months15:58
bswartzvponomaryov: I saw the set of slides you sent out this morning15:58
bswartzvponomaryov: if you have more I'd love to see them15:59
bswartzI don't have anything else for today15:59
bswartzand somehow we used the whole hour15:59
vponomaryovbswartz: ok15:59
bswartzthanks everyone15:59
*** navneet has quit IRC15:59
bswartzsee you in 2 weeks if I don't see you in HK15:59
aostapenkothank you, bye15:59
shamailThanks.  Take care everyone.15:59
*** ruhe has quit IRC16:00
bswartzremembe to RSVP to bswartz@netapp.com if you're coming to our meeting 5:30PM on tuesday16:00
*** caitlin56 has quit IRC16:00
vponomaryovbye16:00
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack meetings (alternate)"16:00
openstackMeeting ended Thu Oct 31 16:00:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-10-31-15.01.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-10-31-15.01.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-10-31-15.01.log.html16:00
*** jcorbin has left #openstack-meeting-alt16:00
*** glenng has left #openstack-meeting-alt16:00
*** gregsfortytwo1 has left #openstack-meeting-alt16:01
*** tanisdl has joined #openstack-meeting-alt16:04
*** shamail has quit IRC16:04
*** bswartz has left #openstack-meeting-alt16:05
*** sarob has joined #openstack-meeting-alt16:05
*** ben_duyujie has joined #openstack-meeting-alt16:06
*** jtomasek has quit IRC16:06
*** aignatov has joined #openstack-meeting-alt16:07
*** akuznetsov has quit IRC16:08
*** bvandehey has quit IRC16:11
*** derekh has quit IRC16:14
*** markwash has joined #openstack-meeting-alt16:26
*** twoputt has quit IRC16:30
*** twoputt_ has quit IRC16:30
*** twoputt has joined #openstack-meeting-alt16:32
*** aignatov has quit IRC16:32
*** twoputt_ has joined #openstack-meeting-alt16:32
*** esker has joined #openstack-meeting-alt16:42
*** sarob has quit IRC16:42
*** sarob has joined #openstack-meeting-alt16:43
*** alazarev has quit IRC16:45
*** alazarev has joined #openstack-meeting-alt16:47
*** SumitNaiksatam has quit IRC16:48
*** eankutse has quit IRC16:50
*** aignatov has joined #openstack-meeting-alt16:55
*** sarob has quit IRC16:56
*** sarob_ has joined #openstack-meeting-alt16:56
*** coolsvap has joined #openstack-meeting-alt17:01
*** enikanorov has quit IRC17:01
*** enikanorov has joined #openstack-meeting-alt17:01
*** demorris has joined #openstack-meeting-alt17:03
*** akuznetsov has joined #openstack-meeting-alt17:03
*** lblanchard has quit IRC17:07
*** SumitNaiksatam has joined #openstack-meeting-alt17:09
*** IlyaE has quit IRC17:13
*** sarob_ has quit IRC17:13
*** sarob has joined #openstack-meeting-alt17:17
*** yogeshmehra has joined #openstack-meeting-alt17:21
*** vipul-away is now known as vipul17:23
*** vipul is now known as vipul-away17:24
*** yidclare has quit IRC17:28
*** sarob has quit IRC17:30
*** flwang has quit IRC17:31
*** twoputt has quit IRC17:32
*** twoputt_ has quit IRC17:32
*** sarob has joined #openstack-meeting-alt17:33
*** crobertsrh has joined #openstack-meeting-alt17:36
*** alazarev has quit IRC17:37
*** ben_duyujie has quit IRC17:43
*** alazarev has joined #openstack-meeting-alt17:46
*** sarob has quit IRC17:47
*** SlickNik has left #openstack-meeting-alt17:53
*** ruhe has joined #openstack-meeting-alt17:53
*** eankutse has joined #openstack-meeting-alt17:54
*** eankutse has quit IRC17:55
*** tanisdl has quit IRC17:55
*** eankutse has joined #openstack-meeting-alt17:55
SergeyLukjanovsavanna team meeting will be here in 10 mins17:55
*** SumitNaiksatam has quit IRC17:59
*** jspeidel has joined #openstack-meeting-alt18:01
*** NikitaKonovalov has joined #openstack-meeting-alt18:02
*** mattf has joined #openstack-meeting-alt18:04
*** IlyaE has joined #openstack-meeting-alt18:04
SergeyLukjanovsavanna folks, are you around?18:05
ruhei'm around18:05
aignatovo/18:05
alazarevo/18:06
mattfo/18:06
jspeidelo/18:06
SergeyLukjanovok, let's start the meeting18:07
*** bill_az has left #openstack-meeting-alt18:07
SergeyLukjanov#startmeeting savanna18:07
openstackMeeting started Thu Oct 31 18:07:38 2013 UTC and is due to finish in 60 minutes.  The chair is SergeyLukjanov. Information about MeetBot at http://wiki.debian.org/MeetBot.18:07
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:07
*** openstack changes topic to " (Meeting topic: savanna)"18:07
openstackThe meeting name has been set to 'savanna'18:07
SergeyLukjanov#topic Agenda18:07
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:07
SergeyLukjanov#link https://wiki.openstack.org/wiki/Meetings/SavannaAgenda#Agenda_for_October.2C_3118:08
SergeyLukjanov#topic Action items from the last meeting18:08
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:08
*** yidclare has joined #openstack-meeting-alt18:08
SergeyLukjanovhm18:09
SergeyLukjanovlet's discuss here design summit proposals that wasn't accepted18:10
*** flaper87 is now known as flaper87|afk18:10
SergeyLukjanovany updates?18:10
aignatovI've just sent the letter about retrospective results18:11
aignatov#link https://wiki.openstack.org/wiki/Savanna/Release_0.3_Retrospective18:11
crobertsrhI've started a pad for post 0.3 dashboard enhancements.18:11
crobertsrh#link https://etherpad.openstack.org/p/EDP_dashboard_post_0.318:11
aignatovif someone wants to add more thoughts please edit this page about retro18:11
*** nadya has joined #openstack-meeting-alt18:12
*** nadya is now known as Guest7002318:12
*** kgriffs is now known as kgriffs_afk18:12
*** briancline has quit IRC18:12
SergeyLukjanovTrevor's requirements doc is on review18:13
*** SumitNaiksatam has joined #openstack-meeting-alt18:13
mattfSergeyLukjanov, update from me re drafting actions, still tbd. i should have some initial goals out to collaborators today.18:13
*** SumitNaiksatam has quit IRC18:13
SergeyLukjanovmattf, ok, great18:13
SergeyLukjanovok, let's move on18:14
SergeyLukjanov#topic Design summit update18:15
*** openstack changes topic to "Design summit update (Meeting topic: savanna)"18:15
SergeyLukjanov#link http://icehousedesignsummit.sched.org/overview/type/savanna18:15
SergeyLukjanov#link https://wiki.openstack.org/wiki/Summit/Icehouse/Etherpads#Savanna18:15
SergeyLukjanovany questions about the design summit?18:16
SergeyLukjanovok18:16
SergeyLukjanov#topic News / updates18:17
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:17
SergeyLukjanovfolks, please18:17
SergeyLukjanovupdate from me - we start working on moving integration tests to CI18:17
SergeyLukjanovI mean jenkins.o.o18:18
mattfsavanna got a lot of play during strata & hadoop world this week. i did an unconference session and discussed it quite a bit. there's a good amount of interest. there was also the rax + hwx preso and plans.18:18
ruhei'd like to hear more about rax + hwx18:18
ruhein regards to savanna18:18
SergeyLukjanovmattf, interesting, could you, please, share some minutes and slides from strata for savanna-related stuff?18:18
mattfme too actually. it was in the last slot yesterday. i had to leave 5 min into it. i just got to talk to rnirmal et al before it.18:19
mattfi'm going to find the video and see if there were questions as they went through the presentation.18:19
mattfSergeyLukjanov, i'll pull some notes together after summit and share points of interest18:20
SergeyLukjanovmattf, thank you18:20
SergeyLukjanov#info Reminder: The Nov 7 meeting is canceled. We’ll resume meetings on Nov 14.18:21
SergeyLukjanovanything else?18:21
mattfwhat are the next steps for the retrospective?18:22
*** SumitNaiksatam has joined #openstack-meeting-alt18:22
aignatovhmm, good question, page is done, need to think how to turn ideas for improvements into the real life :)18:23
mattfdefinitely18:23
aignatovmost thoughts were about review process18:23
SergeyLukjanovyep :)18:23
jspeidelquestion - the patch that provides oozie support in hdp plugin was just merged.  For EDP, how does savanna controller know where oozie is running to execute jobs?18:23
*** gokrokve has quit IRC18:24
SergeyLukjanovI think that we can discuss retrospective at the next team meeting18:24
mattfaignatov, the way we've run them, folks rank the items, we pick 1 or 2 and create a plan to address for the next release18:24
*** gokrokve has joined #openstack-meeting-alt18:24
*** yidclare has quit IRC18:25
*** alazarev has quit IRC18:25
*** jaypipes has quit IRC18:25
*** jergerber has quit IRC18:25
*** jcoufal has quit IRC18:25
*** fungi has quit IRC18:25
*** slagle has quit IRC18:25
*** crobertsrh has quit IRC18:25
*** katyafervent has quit IRC18:25
aignatovjspeidel, edp controller knows about running uzi by looking at cluster info18:25
aignatovafaik your pathc includes ooze url to cluster info18:26
*** NikitaKonovalov has quit IRC18:26
jspeidelaignatov, are you looking for specific node process names?18:26
jspeidelin cluster info?18:26
aignatovmattf, good idea18:26
aignatovjspiedel, yes, we are looking for http://host:11000/oozie in cluster info18:27
aignatovafter that edp goes to ooze through rest18:27
jspeidelok18:28
*** alazarev has joined #openstack-meeting-alt18:28
SergeyLukjanovI think that there are no updates in "Roadmap cleanup / update"18:28
SergeyLukjanovand we're already in "General discussion"18:28
*** gokrokve has quit IRC18:29
*** crobertsrh has joined #openstack-meeting-alt18:29
SergeyLukjanov#topic General discussion18:29
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:29
*** NikitaKonovalov has joined #openstack-meeting-alt18:29
Guest70023jspeidel, client = o.OozieClient(cluster['info']['JobFlow']['Oozie'] + "/oozie")18:30
*** Guest70023 is now known as nprivalova18:30
aignatovmattf, you wanna run the votes to rank the items in retro?18:30
nprivalovaguest is me :)18:30
aignatovnprivalova, thx, I meant the same exactly :)18:31
ruheaignatov, i don't think we need votes18:31
mattfaignatov, i'd rather not. i'm short on time atm.18:31
ruheall the items are important18:31
*** nati_ueno has quit IRC18:31
mattfaignatov, you could just try to pull out 3-4 themes, send them out a day or two before the next meeting, then we discuss which we should do at the next meeting18:32
SergeyLukjanovruhe, agreed18:32
mattfi see 3 themes right off -- reviews, collaboration and process/housekeeping18:32
*** kgriffs_afk is now known as kgriffs18:32
SergeyLukjanovin fact there are 3-4 major themes at all18:32
aignatovmattf, agreed, will do18:32
aignatovSergeyLukjanov, please add AI on me18:33
SergeyLukjanov#action aignatov to start retrospective discussion18:34
mattfit also looks like few people responded to the poll18:34
aignatovbtw, only 5 contributors are answered , I waited for more answers;)18:34
ruhei'd let PTL to decide and convert retrospective results into action items18:34
aignatovrune, we need just to start discussions about items in retro18:35
aignatovrune -> ruhe, sorry18:35
mattfi wish i had thought of it myself - the comment on 100x line commits is really insightful18:35
mattfthere was a thread on os-dev about patch set sizes recently too18:35
mattfproper review of some of the reviews we have in process are a good day+ of work18:36
*** NikitaKonovalov has quit IRC18:36
SergeyLukjanovyeah, big CRs are very painful to review18:36
*** dmitryme has joined #openstack-meeting-alt18:36
mattfi'm about to launch the discussion on that one, but i'll hold off til our next meeting18:37
* mattf zips lips18:37
SergeyLukjanovin addition we can discuss it at summit18:37
* mattf nods18:37
jspeidelagreed18:37
alazarevusually it is possible to split big commit into several smaller. May be we need some guidance?18:38
*** NikitaKonovalov has joined #openstack-meeting-alt18:38
mattf+1018:38
SergeyLukjanovI think that there could not be the common guidance for splitting code18:38
mattfthat guidance can come from well defined purpose of change etc18:38
* mattf rezips18:38
ruhehmm18:39
ruhethat should be already covered somewhere on openstack wiki18:39
aignatovthe main problem of big patches I saw sometime on the review, that the certain patch contains not only certain fix but some unrelated code impovements18:40
SergeyLukjanovyeah, there are some recommendations to not create large CRs18:40
mattfthere's also an issue w/ the number of iterations on reviews. not that 1 is a desirable number, but >12 raises a flag for me18:41
mattfespecially when only 4 people are reviewing18:42
*** SumitNaiksatam has quit IRC18:42
mattfbut...we should discuss later18:42
alazarevwith the official doc, reviewers could request to split big commit into smallers18:42
SergeyLukjanovat most it relates to CR size18:42
jspeidelyes, will be good do discuss in person18:42
nprivalovabtw, recently in mail I saw the statement 'if you send cr you should review someone's code'18:43
mattf^^ is something we should facilitate imho18:43
SergeyLukjanovagreed18:43
mattfit's something a strong community supports18:43
SergeyLukjanovbtw http://russellbryant.net/openstack-stats/savanna-reviewers-30.txt looks not very good18:44
ruhefor alazarev it looks very good :)18:44
mattfwe should kick off this discussion next week18:44
*** SumitNaiksatam has joined #openstack-meeting-alt18:45
aignatovafter next week, mattf18:45
SergeyLukjanovand next week (on summit) too18:45
mattftime is compressed for me atm18:45
alazarevreview is a good way to get inside the project :)18:45
aignatovalazarev, +218:45
*** twoputt_ has joined #openstack-meeting-alt18:46
*** twoputt has joined #openstack-meeting-alt18:46
*** lblanchard has joined #openstack-meeting-alt18:46
SergeyLukjanovare there anything more to discuss?18:47
mattfnothing from me18:47
ruhejspeidel, could you shed some light on hwx + rax? is it savanna spinning up HDP clusters?18:48
jspeidelruhe, I really don't have any info at the moment.  I will try to have some answers for next week18:49
ruheok, thanks18:49
jspeidelyep18:49
SergeyLukjanovlooks like that's all for today18:50
SergeyLukjanovthank you all18:50
SergeyLukjanov#info JFYI you can always use openstack-dev@lists.openstack.org mailing lists and #savanna irc channel to find us and ask your questions18:50
SergeyLukjanov#endmeeting18:50
*** openstack changes topic to "OpenStack meetings (alternate)"18:50
openstackMeeting ended Thu Oct 31 18:50:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-31-18.07.html18:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-31-18.07.txt18:50
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-10-31-18.07.log.html18:50
*** mattf has left #openstack-meeting-alt18:51
*** ruhe has quit IRC18:53
*** briancline has joined #openstack-meeting-alt18:59
*** bryansd1 has joined #openstack-meeting-alt19:00
*** NikitaKonovalov has quit IRC19:04
*** NikitaKonovalov has joined #openstack-meeting-alt19:05
*** nati_ueno has joined #openstack-meeting-alt19:05
*** jspeidel has left #openstack-meeting-alt19:06
*** akuznetsov has quit IRC19:06
*** gokrokve has joined #openstack-meeting-alt19:09
*** akuznetsov has joined #openstack-meeting-alt19:11
*** vipul-away is now known as vipul19:14
*** akuznetsov has quit IRC19:14
*** jaypipes has joined #openstack-meeting-alt19:18
*** jergerber has joined #openstack-meeting-alt19:18
*** jcoufal has joined #openstack-meeting-alt19:18
*** fungi has joined #openstack-meeting-alt19:18
*** slagle has joined #openstack-meeting-alt19:18
*** katyafervent has joined #openstack-meeting-alt19:18
*** hobana.freenode.net changes topic to "Action items from the last meeting (Meeting topic: savanna)"19:18
*** gokrokve has quit IRC19:18
*** gokrokve has joined #openstack-meeting-alt19:18
*** dmitryme has quit IRC19:20
*** gokrokve has quit IRC19:23
*** rushiagr has joined #openstack-meeting-alt19:24
*** vipul is now known as vipul-away19:29
*** jspeidel has joined #openstack-meeting-alt19:39
*** SergeyLukjanov is now known as _SergeyLukjanov19:40
*** _SergeyLukjanov has quit IRC19:40
*** NikitaKonovalov has quit IRC19:43
*** jspeidel has left #openstack-meeting-alt19:43
*** SergeyLukjanov has joined #openstack-meeting-alt19:44
*** gokrokve has joined #openstack-meeting-alt19:48
*** bryansd1 has left #openstack-meeting-alt19:52
*** davlaps has joined #openstack-meeting-alt19:54
*** NikitaKonovalov has joined #openstack-meeting-alt19:55
*** __nikhil__ is now known as nikhil_19:55
*** lsmola has quit IRC19:55
*** nikhil_ is now known as Guest1363819:55
*** SergeyLukjanov has quit IRC19:58
*** gokrokve has quit IRC19:59
*** SergeyLukjanov has joined #openstack-meeting-alt20:00
*** gokrokve has joined #openstack-meeting-alt20:00
*** HenryG has quit IRC20:01
*** dprince has joined #openstack-meeting-alt20:01
markwashglance o'clock methinks20:01
*** gokrokve_ has joined #openstack-meeting-alt20:01
*** crobertsrh has left #openstack-meeting-alt20:02
*** zhiyan has joined #openstack-meeting-alt20:02
esheffieldo/20:02
markwasho/20:02
markwash#startmeeting glance20:02
openstackMeeting started Thu Oct 31 20:02:40 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: glance)"20:02
openstackThe meeting name has been set to 'glance'20:02
esheffieldwe have little monsters wandering through the office pilfering sweets :-)20:02
Guest13638o/20:02
*** sarob has joined #openstack-meeting-alt20:03
*** Guest13638 is now known as nikhil___20:03
markwashhehe20:03
markwashspecial "halloween" episode of the glance meeting20:03
nikhil___markwash: did you get a chance to look at eddie's pic20:03
markwashand here I haven't gorged myself on candy yet20:03
nikhil___markwash: haha yeah :)20:03
markwashnikhil___: no I think I must have missed that20:04
nikhil___here it comes20:04
nikhil___https://drive.google.com/file/d/0B9Ycgkgf21YCcHJDR0c2MDhPZTQ/edit?usp=sharing20:04
zhiyanhi20:04
*** gokrokve has quit IRC20:05
markwashagenda here: https://etherpad.openstack.org/p/glance-team-meeting-agenda20:05
*** jergerber has quit IRC20:05
*** jergerbe_ has joined #openstack-meeting-alt20:05
markwashonly real items on there are: 1) glanceclient cross-version api and 2) worker checkin20:05
markwashlet's talk about glanceclient first20:06
markwash#topic glanceclient v1/v2 cross version api20:06
*** openstack changes topic to "glanceclient v1/v2 cross version api (Meeting topic: glance)"20:06
*** demorris_ has joined #openstack-meeting-alt20:06
markwashbackground in the following thread20:06
*** nati_ueno has quit IRC20:06
markwash#link http://lists.openstack.org/pipermail/openstack-dev/2013-October/016875.html20:06
esheffieldoh boy20:06
esheffield:-)20:06
*** demorris has quit IRC20:07
*** demorris_ is now known as demorris20:07
*** nati_ueno has joined #openstack-meeting-alt20:07
markwashsome more background here as well20:07
markwash#link https://review.openstack.org/#/c/33327/20:07
markwashan old patch we discussed before20:07
markwashI think the key question in my mind is, does it really make sense to publish client libs that 100% follow the versioning scheme of the server library?20:08
*** pcm_ has quit IRC20:09
esheffieldyeah, I've wrestled with this a bit in my mind as well20:09
markwashor should library api versioning be independent?20:09
esheffieldon the one hand, I like the idea of having the api version differences hidden behind a unified interface20:09
esheffieldbut what do you do with functional differences?20:10
markwashyeah20:10
esheffieldI have not reached a satisfactory conclusion in my thinking :-(20:11
markwashI think that might help define the times when you want to make a major version change in the client library as well20:11
markwashso in that scheme, we could have done things this way20:12
markwashhad v1 of the glancelient keep pretty close functionality with the v1 api20:12
markwashbut it could be portable to the v2 api to a certain extent, if that's feasible?20:12
markwashand then when there was v2 functionality that we could not possibly make work with the client v1 interface, we'd have to publish a v2 client as a separate major version of python-glanceclient20:13
markwashone thing I'm not sure about is how easy / acceptable it is for us to simultaneously maintain the 1.x "Head" and the 2.x "Head" of the client library20:13
esheffieldyeah, that could get messy20:14
markwashthat might be a good question to punt up to the list20:15
esheffieldtho it might be the "least bad" thing20:15
markwashit might be a problem for packagers as well20:15
esheffieldI would hope that very soon the v1 client could be frozen with no more updates20:15
esheffieldso might be less of an issue, at least until we hit the flux of a v2 / v3 transition20:16
markwashheh20:16
markwashhow could we freeze it? just not accept more updates to the code in that directory in the client repo?20:17
esheffieldI guess what I'm thinking is at some point we have a released 1.x client and there are no more updates to that release after some point20:19
markwashgotcha, I think that makes sense20:19
esheffieldless about freezing the code and more of "you want to use glance v1, you have to use glanceclient v1.x"20:19
*** SumitNaiksatam has quit IRC20:19
*** nprivalova has quit IRC20:19
*** NikitaKonovalov has quit IRC20:20
markwashI kinda like the idea of glanceclient v2 being able to work with v1 as well, in some forms. . not sure if such an api is possible20:20
*** NikitaKonovalov has joined #openstack-meeting-alt20:20
*** vipul-away is now known as vipul20:21
markwashesheffield: do you think there are any strategic moves we could take soon to help improve this situation?20:21
esheffieldpossibly something like ghe's patch from earlier20:22
markwashand are there any other folks who feel like they have spare bandwidth to work on this v1 v2 compatibility for nova?20:22
esheffieldan interface that supports the most common functionality between the two at first20:23
markwashhow close is Ghe's patch to that?20:23
twoputtI would be interested to know how to deal with the "location" with the v1 api?20:23
*** jcoufal has quit IRC20:23
esheffieldwell, ghe's patch was mostly the imageservice pulled from nova20:24
esheffieldso it was still just v1, but basically represented that common functionality20:24
esheffieldthe patch I have up for nova essentially allows switching v1 / v2 behind that interface20:25
twoputtand not have both of them, that's correct?20:25
nikhil___what is the location issue?20:26
nikhil___sorry, I'm not super familiar with this20:26
twoputtmy understanding is that you can get the location(s) of the image with the v2 api20:27
zhiyantwoputt: glance only show direct url/location to client in v2 api, if admin enable it.20:27
markwashhmm, but its definitely something we'd like nova to use20:27
markwashon the consumer side its easy, nova can use the location IF its present20:28
zhiyantwoputt: yes, v1 always not expose location to client.20:28
markwashon the producer side (nova uploading an image directly to a store, and then passing the location off to glance) there might be some compatibility as well20:28
markwashso maybe that just works20:29
twoputtso for example, in the future the vmware driver in nova will need to get this location. consequently, nova should be able to talk v1/v2 at the same time20:29
markwashof course, v1 won't show multiple locations20:29
zhiyanv1 won't show any locations20:30
markwashzhiyan: right, sorry20:30
twoputtok20:30
markwashI meant to say, v1 can accept a *single* location as a register action20:30
markwashbut does not have semantics for adding a location20:30
markwashso if we wanted to nova to do cool stuff like upload to multiple stores on snapshot, for example to save to cinder and swift, the common client could not support that20:31
esheffieldsounds that way to me20:32
markwashwell, I'm having a hard time wrapping my head around this now :-(20:33
markwashmaybe we should revisit the issue later?20:33
esheffieldheh, welcome to my world of the last couple months! :-)20:34
nikhil___say 5 for tasks and we'r game :)20:34
markwash#topic tasks20:35
*** openstack changes topic to "tasks (Meeting topic: glance)"20:35
zhiyanmarkwash: so from Ghe's patch, you prefer we move the nova/cinder 's consuming code to glanceclient? but i'm confulsed is that for nova/cinder it still need choice using v1/image_service.py or v2/image_service.py , since they are just different essentially ...20:35
markwashwhoops, switched too soon!20:35
*** demorris has quit IRC20:35
zhiyanmarkwash: :)20:36
markwashzhiyan: I think that's a reasonable confusion20:36
*** demorris has joined #openstack-meeting-alt20:36
zhiyanmarkwash: i'm ok, we can talk this later.20:36
esheffieldzhiyan: right now the glance functionality that nova needs is common to v1 and v2, so a single image service could work with swappable "drivers" for v1 / v2 behind it20:36
markwashone sec, I think your comment is a bit of clarity for me20:36
esheffieldbut if nova starts to require say multiple locations, that's a v2 only thing so that becomes more problematic20:37
twoputtyes20:37
twoputtand I think this might come soon20:37
zhiyanesheffield: but IMO only some special function, like locations, can help nova do sush cool things...20:38
markwashif that's the case, then we just need to figure out how to get everyone useing v220:38
zhiyanmarkwash: so the migration cost is high, 1->2, 2->3..20:38
markwashso, if we could make a client API that makes the helpful parts of v2 discoverable20:39
zhiyanseems the cost probably can not be saved.20:39
markwashlike, say if the library tells you something useful like "can we add locations?"20:40
markwashthen its possible nova could be using this client API with both v1 and v2 glance20:40
esheffieldduck typing ftw!20:40
*** NikitaKonovalov has quit IRC20:40
markwashand only try to do these new features if the library says they're available20:41
*** rushiagr has quit IRC20:41
esheffieldthat does mean client users have to be ready with a fallback20:41
esheffieldif an expected feature isn't there20:41
markwashesheffield: yeah, true. . there may be graceful fallbacks though. . I'm not sure20:42
zhiyani'm thinking how it work if glance server disable one api version20:42
zhiyanif so, we need have a function list, allow consumer do the function-availibitly query20:42
* markwash falls back into a bit of confusion20:43
zhiyannext topic? time is short, and nikhil___ i waiting :)20:43
markwashI guess let's keep stewing on this and see if we have any clearer ideas in the future20:44
markwash#topic tasks for real20:44
*** openstack changes topic to "tasks for real (Meeting topic: glance)"20:44
markwashtasks!20:44
nikhil___yay!20:44
markwashwhat's the latest update?20:44
nikhil___thanks all for all the prompt reviews when we needed it most :)20:44
nikhil___really really appreciate it!!20:44
nikhil___markwash: I updated the latest executor interface patch up20:45
nikhil___https://review.openstack.org/#/c/44355/20:45
nikhil___and this completes the chain for all that has been discussed and is waiting for reviews20:45
nikhil___wanted to ask if we had (at least some level) of agreement of the executor interface supported atm ?20:46
markwashnikhil___: is it basically just the "run(task_details)"  that I see?20:47
nikhil___markwash: general outline of the factory/pattern proposed atm20:48
nikhil___yeah and now I see that it mostly relates to run task part20:48
zhiyannikhil___: not sure you noticed, i have put some comments in https://review.openstack.org/#/c/46117/20:49
nikhil___would folks be available to review during the summit ? :)20:49
zhiyani think they are applicable for #4435520:49
markwashnikhil___: I see a little difference there in the executor factory20:49
markwashthe way it is used makes a lot of sense20:49
markwashbut the way its defined, it looks like you pass in the task itself20:50
* markwash might be wrong20:50
zhiyannikhil___: i think/like do it in my night (really night, this time)20:50
markwashI'll definitely be able to review today and during the summit somewhat20:51
nikhil___markwash: def run(self, task_id, task_status, task_type, task_input): has this signature proposed20:51
nikhil___this would be kind of a contract, I'm guessing20:51
*** jergerbe_ has quit IRC20:51
markwashokay cool, i'll focus on that in my review in the next few hours20:52
nikhil___between the scripts and glance code supporting them20:52
nikhil___thanks markwash zhiyan20:52
markwashdoes that cover tasks for now?20:52
nikhil___zhiyan: did not quite get your earlier comment though20:52
zhiyannp nikhil20:52
*** jprovazn has quit IRC20:53
nikhil___markwash: yeah, mostly. I wanted to see how the position was of community20:53
nikhil___on this MP20:53
markwashokay cool20:53
markwashI think generally positive20:53
markwashfrom me at least20:53
nikhil___https://review.openstack.org/#/c/54198/620:53
markwashlast few minutes for open discussion?20:53
nikhil___that has some comments and will address that20:53
nikhil___some discussion was around the status transition checks and wanted to ensure everyone was on the same page about how status is being viewed in general20:54
zhiyannikhil___: thanks20:54
nikhil___seems to be like status and state of tasks is kinda intermingled so that's that20:54
nikhil___that was the last bit, promise. markwash  :)20:54
markwashno worries20:55
markwash#topic open discussion20:55
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:55
twoputtis it the good time to ask for reviews? :) that's my first glance meeting *halloween*20:56
markwashas I suspected :-)20:56
zhiyanquick asking, can someone tell me what "atm" mean? thanks20:56
markwashtwoputt: sure, any time is good for review requests!20:56
markwashzhiyan: "at the moment" I believe20:56
*** alazarev has quit IRC20:57
zhiyanaha, got it20:57
twoputtI have this small patch https://review.openstack.org/#/c/52998/ -- any feedback would be nice ;)20:57
*** alazarev has joined #openstack-meeting-alt20:58
markwashcool20:59
*** nati_uen_ has joined #openstack-meeting-alt20:59
markwashall right, thanks folks, happy halloween!21:00
markwash#endmeeting21:00
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"21:00
nikhil___you too21:00
openstackMeeting ended Thu Oct 31 21:00:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-10-31-20.02.html21:00
nikhil___:)21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-10-31-20.02.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-10-31-20.02.log.html21:00
twoputtnikhil___: once you merge https://review.openstack.org/#/c/46117/ and https://review.openstack.org/#/c/44355/, is there still a lot of this to do before we can use the tasks?21:00
zhiyanthank you guys21:00
nikhil___twoputt: let's switch to glance channel21:00
*** jergerber has joined #openstack-meeting-alt21:00
*** nati_ueno has quit IRC21:03
*** pdmars has quit IRC21:04
*** demorris has quit IRC21:04
*** demorris has joined #openstack-meeting-alt21:04
*** jergerber has quit IRC21:05
*** lblanchard has quit IRC21:07
*** bdpayne has joined #openstack-meeting-alt21:08
*** Barker_ has quit IRC21:08
*** gokrokve_ has quit IRC21:09
*** SumitNaiksatam has joined #openstack-meeting-alt21:10
*** dprince has quit IRC21:11
*** gokrokve_ has joined #openstack-meeting-alt21:12
*** esker has quit IRC21:13
*** SumitNaiksatam has quit IRC21:14
*** sarob has quit IRC21:22
*** kgriffs has left #openstack-meeting-alt21:23
*** enikanorov__ has joined #openstack-meeting-alt21:24
*** gokrokve_ has quit IRC21:24
*** ilyashakhat has joined #openstack-meeting-alt21:25
*** gokrokve has joined #openstack-meeting-alt21:25
*** enikanorov has quit IRC21:25
*** ilyashakhat_ has quit IRC21:26
*** sarob has joined #openstack-meeting-alt21:26
*** gokrokve has quit IRC21:30
*** zhiyan1 has joined #openstack-meeting-alt21:37
*** eankutse1 has joined #openstack-meeting-alt21:38
*** eankutse1 has quit IRC21:38
*** zhiyan has quit IRC21:38
*** eankutse has quit IRC21:41
*** jmontemayor has quit IRC21:52
*** demorris has quit IRC21:58
*** ruhe has joined #openstack-meeting-alt22:00
*** nati_ueno has joined #openstack-meeting-alt22:00
*** colinmcnamara has quit IRC22:01
*** lblanchard has joined #openstack-meeting-alt22:02
*** nati_uen_ has quit IRC22:03
*** aignatov has quit IRC22:05
*** aignatov has joined #openstack-meeting-alt22:05
*** SergeyLukjanov has quit IRC22:07
*** IlyaE has quit IRC22:08
*** ruhe has quit IRC22:11
*** aignatov has quit IRC22:15
*** alazarev has quit IRC22:18
*** yogeshmehra has quit IRC22:19
*** sacharya has quit IRC22:24
*** markmcclain has joined #openstack-meeting-alt22:32
*** bdpayne has quit IRC22:40
*** gokrokve has joined #openstack-meeting-alt22:56
*** amytron has quit IRC22:57
*** nati_ueno has quit IRC22:57
*** markmcclain has quit IRC22:58
*** davlaps has quit IRC23:01
*** nati_ueno has joined #openstack-meeting-alt23:04
*** eharney has quit IRC23:06
*** bdpayne has joined #openstack-meeting-alt23:06
*** amytron has joined #openstack-meeting-alt23:09
*** bdpayne has quit IRC23:12
*** gokrokve has quit IRC23:13
*** gokrokve has joined #openstack-meeting-alt23:13
*** gokrokve_ has joined #openstack-meeting-alt23:16
*** gokrokve has quit IRC23:17
*** sacharya has joined #openstack-meeting-alt23:18
*** bdpayne has joined #openstack-meeting-alt23:20
*** amytron has quit IRC23:30
*** amytron has joined #openstack-meeting-alt23:36
*** SergeyLukjanov has joined #openstack-meeting-alt23:38
*** gokrokve_ has quit IRC23:49
*** gokrokve has joined #openstack-meeting-alt23:50
*** alazarev has joined #openstack-meeting-alt23:54
*** gokrokve has quit IRC23:55
*** harlowja has quit IRC23:55
*** harlowja has joined #openstack-meeting-alt23:56
*** nati_ueno has quit IRC23:56
*** alazarev has quit IRC23:57
*** nati_ueno has joined #openstack-meeting-alt23:57
*** nati_uen_ has joined #openstack-meeting-alt23:59

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