Monday, 2014-03-31

*** matsuhashi has joined #openstack-trove00:23
*** mayfield_ has joined #openstack-trove01:08
*** hub_cap_ has joined #openstack-trove01:08
*** esmute_ has joined #openstack-trove01:12
*** dmakogon_ has quit IRC01:13
*** mayfield has quit IRC01:13
*** esmute has quit IRC01:13
*** hub_cap has quit IRC01:13
*** esmute_ is now known as esmute01:13
*** dmakogon_ has joined #openstack-trove01:20
*** matsuhashi has quit IRC01:24
*** matsuhashi has joined #openstack-trove01:26
*** jasonb365 has joined #openstack-trove01:31
*** nosnos has joined #openstack-trove01:31
*** jasonb365 has quit IRC01:39
*** jasonb365 has joined #openstack-trove01:40
*** yidclare has quit IRC01:45
*** hub_cap_ is now known as hub_cap01:49
hub_capman looks like i dc'd... a netsplit maybe? /me shrugs01:55
*** eghobo has quit IRC02:19
*** khyati has joined #openstack-trove02:59
*** khyati has quit IRC03:02
*** eghobo has joined #openstack-trove03:07
*** haomaiwang has joined #openstack-trove03:17
*** matsuhashi has quit IRC03:19
*** jasonb365 has quit IRC03:19
*** nosnos has quit IRC03:34
*** sbfox has joined #openstack-trove03:54
*** haomaiw__ has joined #openstack-trove03:56
*** matsuhashi has joined #openstack-trove03:57
*** haomaiwang has quit IRC03:58
*** nosnos has joined #openstack-trove04:02
*** michael-yu has joined #openstack-trove04:03
*** michael-yu has quit IRC04:04
*** michael-yu has joined #openstack-trove04:06
*** matsuhashi has quit IRC04:39
*** matsuhashi has joined #openstack-trove04:43
*** jasonb365 has joined #openstack-trove04:53
*** SushilKM has joined #openstack-trove05:37
*** jasonb365 has quit IRC05:37
*** nosnos_ has joined #openstack-trove05:53
*** nosnos has quit IRC05:53
*** matsuhashi has quit IRC05:54
*** matsuhashi has joined #openstack-trove05:55
openstackgerritJenkins proposed a change to openstack/trove: Imported Translations from Transifex  https://review.openstack.org/8272106:24
*** flaper87|afk is now known as flaper8707:02
*** matsuhashi has quit IRC07:08
*** matsuhashi has joined #openstack-trove07:08
*** nosnos_ has quit IRC07:09
*** nosnos has joined #openstack-trove07:10
*** matsuhashi has quit IRC07:22
*** yogesh has joined #openstack-trove07:26
*** matsuhashi has joined #openstack-trove07:28
*** michael-yu has quit IRC07:30
*** sbfox has quit IRC07:32
*** michael-yu has joined #openstack-trove07:36
*** michael-yu has quit IRC07:37
*** matsuhashi has quit IRC07:46
*** matsuhashi has joined #openstack-trove07:47
*** timfreund has quit IRC07:53
*** yogesh has quit IRC07:55
*** eghobo has quit IRC08:29
*** yogesh has joined #openstack-trove08:43
*** yogesh has quit IRC08:44
*** RockKuo_TW_PC has joined #openstack-trove08:48
*** RockKuo_TW has quit IRC08:52
*** haomaiw__ has quit IRC09:13
*** haomaiwa_ has joined #openstack-trove09:13
*** haomaiw__ has joined #openstack-trove09:32
*** haomaiwa_ has quit IRC09:35
*** timfreund has joined #openstack-trove09:42
*** matsuhashi has quit IRC11:26
*** nosnos has quit IRC11:27
*** demorris has joined #openstack-trove11:50
*** saju_m has joined #openstack-trove11:51
*** saju_m has quit IRC12:00
*** saju_m has joined #openstack-trove12:06
*** saju_m has quit IRC12:08
openstackgerritDenis M. proposed a change to openstack/trove: Fix create call for security group rules  https://review.openstack.org/8376812:17
openstackgerritDenis M. proposed a change to openstack/python-troveclient: Fix create call for security group rules  https://review.openstack.org/8411512:18
openstackgerritDenis M. proposed a change to openstack/trove: Add stack_id for future usage  https://review.openstack.org/6787312:20
openstackgerritDenis M. proposed a change to openstack/trove: Support floating IP association at provisioning  https://review.openstack.org/4507512:20
openstackgerritDenis M. proposed a change to openstack/trove: Allow db instance conditional logging  https://review.openstack.org/6378912:20
openstackgerritDenis M. proposed a change to openstack/trove: Allow log files audit  https://review.openstack.org/6430212:21
openstackgerritDenis M. proposed a change to openstack/python-troveclient: Allow log files audit  https://review.openstack.org/6430312:21
openstackgerritDenis M. proposed a change to openstack/trove: Track security group provisioned by heat  https://review.openstack.org/7104012:21
openstackgerritDenis M. proposed a change to openstack/trove: Add heat.template for Percona datastore  https://review.openstack.org/7653612:21
openstackgerritDenis M. proposed a change to openstack/trove: Add heat.template for Redis datastore  https://review.openstack.org/7653812:21
openstackgerritDenis M. proposed a change to openstack/trove: Add point in time recovery  https://review.openstack.org/7722212:21
openstackgerritDenis M. proposed a change to openstack/python-troveclient: Add point in time recovery  https://review.openstack.org/7722312:21
openstackgerritDenis M. proposed a change to openstack/trove: Support full backup/restore for Cassandra  https://review.openstack.org/7755112:21
*** pdmars has joined #openstack-trove12:23
openstackgerritDenis M. proposed a change to openstack/trove: Refactoring strategies implementation  https://review.openstack.org/7789912:26
openstackgerritDenis M. proposed a change to openstack/trove: Refactor mysql and redis apps  https://review.openstack.org/8002012:26
*** pdmars has quit IRC12:26
*** pdmars has joined #openstack-trove12:30
*** demorris has quit IRC12:30
*** mrsnivvel has joined #openstack-trove12:36
*** Barker has joined #openstack-trove12:44
*** radez_g0n3 is now known as radez12:48
tenagliaDo you know what is the status of RHEL-like support for Trove?12:51
*** Barker has quit IRC12:54
*** dmakogon_ is now known as denis_makogon12:55
denis_makogontenaglia, please elaborate your question12:56
tenagliadenis_makogon: I understand it was not very clear. The last time we've checked the only platform on which Trove was able to run was Ubuntu. We'd like to use RHEL-like distros so I was wondering what is the current state.12:57
tenagliapython-troveclient had some Ubuntu-specific dependencies.12:58
*** grapex has joined #openstack-trove13:03
denis_makogontenaglia, which deps. are ubuntu-specific ?13:04
tenagliadon't remember now.13:05
tenagliamaybe I should just give it a second shot and report later.13:05
tenagliait was just a preliminary check.13:05
denis_makogonfrom my perspective, trove could work on fedora, i don't see so much difference between RHEL and fedora13:10
*** grapex has quit IRC13:11
*** mrsnivvel has quit IRC13:20
*** blueyes has joined #openstack-trove13:44
*** blueyes has quit IRC13:46
*** blueyes has joined #openstack-trove13:46
*** zigo has quit IRC13:50
*** grapex has joined #openstack-trove13:57
*** robertmy_ has joined #openstack-trove13:58
*** zigo has joined #openstack-trove13:58
tenagliadenis_makogon: indeed not much difference13:59
tenagliathanks it's enough to re-start working at it.13:59
denis_makogontenaglia, you're welcome14:02
*** blueyes has quit IRC14:05
*** blueyes has joined #openstack-trove14:06
*** rwsu has joined #openstack-trove14:06
*** jasonb365 has joined #openstack-trove14:15
*** demorris has joined #openstack-trove14:15
*** blueyes has quit IRC14:18
*** michael-yu has joined #openstack-trove14:19
*** jcru has joined #openstack-trove14:23
*** amytron has joined #openstack-trove14:24
*** michael-yu has quit IRC14:26
*** tanisdl has joined #openstack-trove14:29
*** jmontemayor has joined #openstack-trove14:34
*** kevinconway has joined #openstack-trove14:37
*** kevinconway has quit IRC14:38
*** kevinconway has joined #openstack-trove14:38
*** freyes has joined #openstack-trove14:54
*** SushilKM has quit IRC14:56
*** Barker has joined #openstack-trove14:57
*** sbfox has joined #openstack-trove14:59
imsplitbitI have sent out links to the instance metadata blueprint and spec15:01
imsplitbitcore reviews blueprints on Mondays yes?15:01
*** Barker has quit IRC15:01
*** jasonb365 has quit IRC15:02
*** Barker has joined #openstack-trove15:04
denis_makogonimsplitbit, saw your email, we can talk about it today15:05
*** demorris has quit IRC15:18
*** demorris has joined #openstack-trove15:18
hub_capdenis_makogon: imsplitbit core will decide what bps to look at in the morning meeting15:20
denis_makogonhub_cap, i thought we're reviewing scheduled BPs, isn't it ?15:22
hub_capit depends15:23
hub_capif any random person puts a bp on then not necessarily15:23
hub_capand the cor ewill choose what, based on what people put15:23
hub_capthere will still be a priority15:23
denis_makogonget it, i thought that core are going review what they want, independently from the long-term schedule15:25
hub_capim not sure what that means15:27
denis_makogonlet me elaborate abit, contributors have one week (from Mon. to Mon, legal time range) to schedule discussion (one or more BP) and all scheduled BPs would be discussed within 1h, and almost nothing can't change this order15:30
hub_capno i said the opposite15:32
hub_capput your bp up, we will choose which ones to look at15:32
*** sbfox has quit IRC15:32
hub_capand you have as much time as you want to file a blueprint15:32
hub_capthere is no legal time range for that15:32
hub_capim not sure what that means either15:32
hub_capif it takes u 6 wks to finish your blueprint, then thas fine15:32
denis_makogoni mean legal time range - its the time when you should schedule your BP for discussion, if you schedule it like one or 2h ago, it'll be hard to review it15:36
*** sbfox has joined #openstack-trove15:39
denis_makogonwhen do we plan to start BP meeting ?15:44
*** freyes has quit IRC15:45
*** khyati has joined #openstack-trove15:47
*** eghobo has joined #openstack-trove15:59
*** ViswaV has joined #openstack-trove16:02
*** jmontemayor_ has joined #openstack-trove16:03
*** jmontemayor has quit IRC16:06
denis_makogonhub_cap, saw you're email16:23
denis_makogonhub_cap, is it true =( ?16:23
hub_capheh, i did, in fact, send that email denis_makogon :)16:24
hub_capi think 3 or 4 ptls are stepping down too16:24
hub_capits a painful, relentless job16:24
denis_makogoni see16:25
*** SushilKM has joined #openstack-trove16:28
*** jmontemayor_ has quit IRC16:29
*** jmontemayor has joined #openstack-trove16:31
denis_makogonhub_cap, when do we plan to start meeting ?16:37
hub_capim pretty sure it was at 11pt16:38
denis_makogon11 pst ?16:42
hub_capi think so denis_makogon16:45
hub_capas in, 1hr15m from now16:45
*** RockKuo_TW_PC has quit IRC16:46
denis_makogonprobably, i'll go home, will try not to be late16:46
denis_makogonhub_cap, thanks for converting the actual time =)16:46
hub_capnpnp16:47
*** harlowja_away is now known as harlowja16:48
*** demorris has quit IRC16:52
amrithhub_cap: how many minutes from now is "one hour from now" in PST ;)17:07
*** michael-yu has joined #openstack-trove17:09
*** rwsu has quit IRC17:11
*** demorris has joined #openstack-trove17:13
hub_caplol17:14
*** shivamshukla has joined #openstack-trove17:17
*** eghobo has quit IRC17:27
*** eghobo has joined #openstack-trove17:28
ViswaVhub_cap: Hat tip for a job well done so far as the Trove PTL. Hope the baton passes on to equally capable hands.17:29
*** khyati has quit IRC17:29
amrith+117:29
*** yidclare has joined #openstack-trove17:29
*** michael-yu has quit IRC17:29
hub_capthx guys17:30
hub_capill still be around to give whomever that is hell17:31
hub_capand all of you17:31
hub_capmy -2 is still strong :)17:31
ViswaV:)17:31
hub_capin reality i just want to be invited to the HP core contributor dinners in the OS conf's17:31
*** mattgriffin has joined #openstack-trove17:41
* juice is tearing up17:44
juicecore reviewers - here is a blueprint that I would like to discuss today if there are open slots https://blueprints.launchpad.net/trove/+spec/trove-guest-private-network17:46
*** amcrn has joined #openstack-trove17:46
*** rustlebee is now known as russellb17:47
*** SushilKM has quit IRC17:47
*** tanisdl has quit IRC17:47
vipulhub_cap, SlickNik: are there BPs that we have on the docket to review17:49
SlickNikvipul: the agenda is here: https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_Mar._31_.28blueprint_meeting.2917:51
*** mattgriffin has quit IRC17:52
*** mattgriffin has joined #openstack-trove17:54
*** yogesh has joined #openstack-trove17:56
*** denis_makogon_ has joined #openstack-trove17:58
amrithfor the BP review meeting are we using meeting-alt? or do we stay here?17:59
*** denis_makogon has quit IRC17:59
*** denis_makogon_ is now known as denis_makogon17:59
*** dmakogon_ has joined #openstack-trove17:59
denis_makogonamrith, we're here17:59
hub_capdenis_makogon: plz make your blueprints look more like juice's18:00
SlickNikI think we're planning on staying here.18:00
amrithok, thx18:00
hub_capwe talked about the format already, and im not sure we can move forward w/ yours until you fix the way they look :)18:00
denis_makogonhub_cap, which one ?18:00
hub_capboth18:00
amrithI'll pour myself a stiff drink ;)18:00
hub_caplets start w/ juices18:00
hub_capits nice18:01
juiceready when you are18:01
amrithyes, I have the juice of a potato, the juice of a grape, juice of barley seed, ...18:01
hub_caplol amrith18:01
hub_capnice18:01
juicemaking me thirsty18:01
hub_capim pretty sure thats all alcohol ;)18:01
amrithcome on over and we can enjoy together. speaking of which, are you coming to attend today18:02
amrithalcohol, shiver the thought18:02
amrithI wouldn't touch the devils brew18:02
hub_capnaw i cant, im stuck in berkley till wed morn18:02
juicedid the gun go off?18:02
SlickNikYeah, go for it18:02
amrithok, will miss you. others who are here please let me know ... percona live in Hyatt at Santa Clara is where its all happening18:02
juiceI'll give you all a few minutes to skim the content18:02
SlickNikAgenda: https://wiki.openstack.org/wiki/Meetings/TroveMeeting#Agenda_for_Mar._31_.28blueprint_meeting.2918:03
amrithwho's driving?18:03
juicebasically the premise here is to leverage neutron functionality in a way that we can create isolated trove instances18:03
SlickNikRight now we're talking about "Trove Managed Instances on Private Network"18:03
juiceisolated in the sense that there are nearly inaccessible to intrusion with the exception of their db port18:03
amriththx18:04
juiceand they have no exposure to fiddling with from a nova stand point18:04
juicethere is a behind the scenes tenant owned by the provider which owns all trove nova instances18:04
*** khyati_ has joined #openstack-trove18:04
juicefrom Trove's perspective, the accounting of which tenant owns which node is still being handled18:04
juicethere is also a behind the scenes network which connects the Trove instances with the RabbitMQ server18:05
hub_capyea so my beef here18:06
juicethe user provides a network preferably their private network to the Trove Intance Create which allows them to access the Trove Instance from their App Server or if public from the internet18:06
hub_capis that we are defining _how_ trove is installed18:06
juiceyou're from texas so I am expecting a lot of beef18:06
hub_capim not sure that other projects are doing that18:06
hub_caplol juice18:06
juiceI think in this case we are providing the option to run trove in this fashion18:06
hub_capdo other projects lke nova make this the case?18:06
hub_capwell your bp says "by default"18:07
juicethe idea is that it will support this use case but also allows for the default situation18:07
amrithjuice, do I undrestand correctly that this means that we will no longer be able to address a trove instance as an underlying "nova instance"18:07
hub_capok the default is the dev env w/ 1 network18:07
juicehub_cap: yes the default will be the same as it is now18:07
hub_capwoah thsi is not cool juice , the complete trove mgmt18:07
denis_makogonhub_cap, even now we can assign more than one nics for the instance on provisioning18:08
hub_capthats going too far18:08
juicebut then through configuration and some plugin like code you can run the setup in this way18:08
hub_capcan u explain juice what "system-based tenatn will own all trove guest instances"?18:08
hub_capis this just for the network?18:08
juicenope it's for the instances as well18:08
hub_capi disagree completely on this18:09
hub_capits not up to us to decide that18:09
juicehowever the billing/usage will still report the end user tenant id18:09
hub_capthis feels like the "hp" way is dictated into trove OS :)18:09
ViswaV+1 hub_cap18:09
juicehub_cap: even if it is just a configurable deployment18:10
amrithjuice: how does one get access to things like query log, mysql general log, etc? if we can't access the underlying server?18:10
vipulI think this is simply proposing another remote.py impl that doesn't re-use the original token18:10
hub_capvipul: we can make it an option18:10
hub_capim fine w/ that18:10
vipuland giving you the option via cfg to choose that over the delegated auth method18:10
juicechoice usually does not suggest dictate18:10
hub_capbut none o fthis can be default18:10
hub_capid recommend updating the bp to define that none of this will be default. but options18:10
juicehub_cap: it will not be the default configuration18:10
hub_capheh it doesnt appear as such based on the bp.. so jus tadd some verbiage and im cool w it18:11
vipulthe benefit of this is also for those running Trove on a 'shared' nova -- it allows the instances to be hidden from the Nova CLI18:11
juicehub_cap: sorry if I suggested that somewhere.  it certainly wasn't the intention18:11
hub_capit makes sense to have this if u want18:11
hub_capvipul: but we also talked w/ nova coutnless times about managed vms18:11
SlickNikYeah, sounds to me like these can be deployment options, but shouldn't be the default trove config.18:11
hub_capthere is more than one way to solv ethis18:11
hub_capw/o mucking w/ trove18:11
hub_capjust dont let people do things "managed" by trove18:11
vipulhub_cap: sure, but that's a long pole :)18:11
hub_capor savanna or any other things18:11
hub_capsure but itll help everyone18:11
hub_capand it wont add extra code to trove18:11
grapexjuice: I feel like I'm still wrapping my head around it, but I wonder if this could be two blueprints. One is the ability to configure Trove to allow another tenant to control server creation in Nova on a users behalf18:12
ViswaValso juice: the diagram https://wiki.openstack.org/wiki/File:Trove-private-network-overview.jpg  does not show swift service as part of the trove management customer net. Don't we need that for backups/restore?18:12
grapexI wonder if that should be split out into it's own bp?18:12
juicegrapex: I suppose it could be split into two18:13
denis_makogonone for the multi-tenancy, another for the networking, i guess18:13
* grapex fist pumps18:13
juicegrapex: however, you can't do the networking one without the management user18:13
juicegrapex: easy now easy18:14
grapexjuice: Maybe it's dependent on it then?18:14
hub_capexactly18:14
amrithin that case tehre has to be at least a third BP18:14
juiceviswav: for backups, the swift account will still be tied to the end user18:14
juiceamrith: what? :) tell me you're kidding18:15
denis_makogonjuice, agreed, containers it's the actual user quota18:15
amrithfor how you will allow multiple guests to share a VM and how you'll allow users access to files (like logs)18:15
vipulSo one thing to keep in mind is.. there is an issue today where the instances will not have access to the control plane (unless you poke a hole) -- and when we go to Neutron, and the end user dictates the network to attach, we will lose control over whether that instance also has a management network18:15
amrithso if I understand this correctly, you want to lock down the instance18:15
amrithand not allow the user to access the underlyign Nova18:15
amrithand you want to also have >1 guest on a VM18:15
amrithif there's already a plan for how you get access to stuff like logs from the machine, then it should be part of this effort18:16
amrithno?18:16
juiceamrith: correct, correct, wrong18:16
amrithok18:16
juicethe logging issue still exists here. whatever denis_makagon is working on should work here18:16
amrithfine, so long as it's been thought through18:16
ViswaVjuice: I meant doesn't the swift service need to be accessible via the trove management net interface on the guest VM? Or is it expected to be accessible via the customer specified net during creation?18:16
vipuljuice: if we don't go with a 'trove tenant' approach, how will we attach a management network to the instance18:16
juiceviswav: I will look into the backup/swift issue18:16
SlickNikamrith: I don't think the bp proposes > 1 guest on a VM.18:17
*** konetzed has quit IRC18:17
amrithisn't that what shared Nova means (from what was said above)18:17
grapexvipul: You're saying that if Trove doesn't own the Nova server, attaching the network is impossible?18:17
amrithyes, I don't see that in the bp but that was being said above?18:17
amrithcalled multi-tenancy etc.,18:17
juicevipul: we can still attach the instance to the management network behind the scenes.  the issue is that the customer since they own the instance can go into nova and detach the port18:17
vipulamrith: Shared nova means you have a public nova endpoint.. that Trove deploys on top of18:17
juice:(18:17
*** mattgriffin has quit IRC18:17
amrithhmm18:18
vipulamrith: it means folks are doing a nova boot as well as trove create on the same nova18:18
hub_capid like us to talk to nova before we go much further here tho18:18
hub_capcan u do some diligence here vipul/juice to discuss w/ nova core18:18
hub_capevery time ive brought htis up they like the idea18:18
grapexI also don't think, strictly speaking, you have to make Trove "own" the instances for this to be useful18:18
hub_capof a "managed" vm18:18
vipuljuice: Since we're using the Tenant's token, there will be lack of privileges for that tenant to know about mgmt network18:19
grapexfor example, if no one has access to the Nova API you're talking to it it won't matter.18:19
grapexJust to name a highly theoretical example. :)18:19
hub_capi think we _should_ keep everything in the tenant personally18:19
SlickNikvipul / amrith: Yeah, I think a more apt description would be "public nova" rather than "shared nova"18:19
ViswaV'trove owned instances  (single system tenant)" may also limit the freedom of an org to apply different QOS criteria based on tenant info  (provision project1's  trove instances on a cheaper set of Hyps or a different datacenter etc)18:19
denis_makogonhub_cap, agreed, multi-tenancy is the complicated part with spread services18:20
juicevipul: let me try to see if that is an issue.  I think you can still provide a port from another network and attach it to the instance18:20
*** shivamshukla has quit IRC18:20
amrithLAGCHECK18:20
*** tanisdl has joined #openstack-trove18:20
amrithoops18:20
vipulgrapex: Yes, it's not impossible. assuming you make the mgmt network public or give Neutron Admin to end users18:20
amrithneed new password, sorry18:20
juicevipul: you may not be able to provide a net-id but I think you can provide a port that was created by the owner of that network18:21
vipulthe issue is a end user wants a Private DB -- how do we also manage that private DB that lives in a private network18:21
denis_makogonjuice, yes18:21
hub_capamrith: yes yer lagging lol18:21
amrith* need barley juice18:22
hub_capvipul: we can have a mgmt user to do _that_18:22
hub_capthe validation on neuttron18:22
vipulhub_cap: Yea, so if we attach the mgmt network as a separate step in the boot process, via admin user that owuld work18:22
hub_capbut i dont think that alone justifies making everything in trove talk over a single user18:23
juicethe end issue being that there is a lot of control in the users hands when they have access to nova18:23
vipulhub_cap: agreed i think it's two BPs..18:23
hub_capfor sure, discrete issue ju18:23
juiceputting the "managed" feature in Nova would be great18:23
hub_caplol18:23
hub_capmy latency is terible........18:23
denis_makogonmine too18:23
juiceI think the latency is in my head18:23
vipullet's forget about the Trove tenant / ownership issue.. that can come later18:24
hub_capjuice: hehe you arent on a remote machine irc'ing18:24
grapexI think everyone could get behind having an option for Trove to manage the Nova servers.18:24
juicesummary: i will split this up in two, talk to nova core to see if this is a feature they can provide.18:24
vipulgrapex: yea that could come as an optional impl of remote.py later18:24
juiceif this is not a feature they can provide, what next?18:24
denis_makogonjuice, first in nova, then in heat, do not forget about it18:25
juicegrapex: vipul: we do something to this effect today with the technique vipul mentioned above18:25
juicedenis_makagon: heat?! seriously?18:25
denis_makogonjuice, and only =)18:25
grapexjuice: The heat is on.18:25
juicegrapex: it's on the street18:26
hub_cap++ i like this now18:26
hub_capsry to ruin yoru world juice but arent u glad we talked ;)18:26
denis_makogonif nova/heat would be able to assign resources on given tenant it'll be fantastic18:27
hub_capthis is the whole point of these18:27
juicehub_cap: yeah this is all good18:27
juicebetter now than later18:27
juiceearly feedback is what this is all about so I think it's working18:28
hub_cap++18:28
hub_capwe have a late addition to th elist to fyi18:28
vipulOk looks like we've beat this thing dead lol18:28
vipulnext one?18:28
denis_makogonprobably yes18:29
hub_capvipul: lol18:29
hub_capeveryone refersh their page18:29
juiceyeah I can't take anymore - Next!18:29
SlickNikI think so, we've got clear next steps for this bp.18:29
juicekinda fun though - I feel like I just ran through a gauntlet with you guys and your padded batons - "American Gladiator" style18:30
SlickNik*an instance metadata bp shows up*18:30
hub_capdenis_makogon: where are teh blueprints for your "other" things?18:30
hub_capjuice: dibs on the tenis ball gun18:31
denis_makogonhub_cap, https://blueprints.launchpad.net/trove/+spec/point-in-tyme-recovery18:31
hub_capi just see your wiki links18:31
hub_capplz fix18:31
denis_makogonhub_cap, https://blueprints.launchpad.net/trove/+spec/volume-snapshot18:31
juicehub_cap: oh man I forgot about that.  good one18:31
hub_capalso imsplitbit plz fix yers18:31
vipulare we doing in order?18:31
hub_capwe can go w/ network attr mgmt now sure18:31
hub_capthis one is not in the proper format18:32
SlickNikActually, the other 2 networking bps are both not in the proper format.18:32
denis_makogonhub_cap, done, page fixed18:32
hub_capthx denis_makogon18:32
hub_capyea SlickNik niether is18:32
hub_capi thought they were both denis_makogon but one is annashen_ 's18:32
SlickNikThey also talk about very similar things.18:33
denis_makogonmine for networks is only one18:33
hub_capdenis_makogon: plz remove the wiki page from there18:33
hub_capthe wiki page _should_ be linked from the bp18:33
hub_capagain18:33
hub_capplz see juices18:33
hub_capif its alreayd linked there is no reason to put it on the wiki page18:33
vipulwhich one are you guys looking at? https://blueprints.launchpad.net/trove/+spec/network-manager-spec ?18:34
hub_capi wnat to kick them both to next wk18:34
hub_capand let annashen_ and denis_makogon work out the differences18:34
hub_capand fix their bp styleing18:34
annashen_hub_cap, sure18:34
SlickNikdmakogon_ / annashen_ : Can you please update your bps to follow https://wiki.openstack.org/wiki/TroveBlueprint?18:34
hub_cap++18:34
hub_capany blueprint not in that style will be immed kicked18:34
* hub_cap is mean18:35
denis_makogonbtw, first BP also was with the bad style18:35
annashen_SlickNick, hub_cap, i heard you both18:35
hub_capannashen_: thank you18:35
hub_capok moving on?18:35
SlickNikannashen_: Thanks!18:35
SlickNikyup.18:35
vipuldenis_makogon: first one we reviewed was perfect :)18:35
hub_capyup18:36
SlickNikdmakogon_: take a look at https://wiki.openstack.org/wiki/Trove/trove-managed-instances (linked from the bp)18:36
hub_capit was exactly what we are looking for18:36
hub_capif they are not like thta, we will kick them18:36
denis_makogonSlickNik, bp isn't wiki page18:36
hub_capweve already asked for them to be in thsi format18:36
denis_makogonlet's move on18:36
hub_capno denis_makogon18:36
hub_caplets discuss this18:36
vipulBP should link to a wiki page18:36
hub_capcuz youre wrong18:36
hub_capthe bp linksto the wiki18:36
hub_capjust like weve been doing forever18:36
*** mattgriffin has joined #openstack-trove18:36
hub_capSet the url for this specification18:37
hub_capthat has always been there18:37
hub_capand we have always use dit18:37
hub_caplets do this one https://blueprints.launchpad.net/trove/+spec/trove-metadata18:37
hub_capsince its also in the correct format18:37
hub_capany objections18:38
hub_cap?18:38
vipul+1 let's do it18:38
hub_capfrck imsplitbit this is nice mang18:39
hub_cap*frack18:39
cp16netahh damn PATCH?18:39
cp16netlolz18:39
hub_capcp16net: yes18:39
* SlickNik is reading the bp18:39
hub_capPATCH ftw!18:39
dougshelley66so question18:40
dougshelley66on the spec18:40
dougshelley66is the intention that the key is generated on create?18:40
juiceimsplitbit: does the metadata provide any direct functional impact18:40
juice'or for now is it just metadata?18:40
imsplitbitjust metadata atm18:40
amrithimplisitbit: +N for a very clear specification18:41
imsplitbitbut there is some use for us internal in testing and such18:41
imsplitbitCI18:41
juicedo we have any services that will use this and if so does it then imply there needs to be specific metadata in there18:41
imsplitbitjuice: not at the moment18:41
cp16nethub_cap: that was the death of me... :-P18:41
cp16netbut i think moving forward it will be better :)18:41
vipulright, besides adding labels, what's the use case18:41
denis_makogonglance will have metadata service soon18:41
imsplitbitcp16net and I were talking about using in CI environments to keep track of ci job instances18:41
juiceimsplitbit: ok just asking.  thanks and a very thorough bp it is18:41
imsplitbitwhat created them18:41
imsplitbitetc18:41
hub_capgod we need a single metadata svc for openstack hahahah18:41
imsplitbitthanks18:41
cp16netusing it as a place for a description or something on an instance18:42
imsplitbityeah so the entry point in the instance is very small18:42
denis_makogonhub_cap, it's already in process18:42
cp16netor like what tests actually started the job18:42
juiceimsplitbit: can you search across instance18:42
amrithtwo questions. 1. can metadata be specified on instance create and 2. is any metadata stored with an instance snapshot / image that will be automatically instantiated on launch.18:42
imsplitbitonce there is an openstack service there's a very clear path to migrate to it18:42
juiceimpsplitbit: without specifying the instance_id? e.g. show me instances where metadata Key = Value?18:42
imsplitbit1. not yet, I didn't want to have too much in the inital pr18:42
hub_capdenis_makogon: got a link? is it a mirantis thing?18:43
imsplitbit2. I don't know that the instance snapshot would store that but we can find a way to hook it in18:43
imsplitbitjuice: no18:43
hub_capi like #1 for a follow on18:43
denis_makogonhub_cap, i'll link you as soon as i reach skype18:43
amrithimplisitbit: thanks18:43
imsplitbitinstance id is required ATM18:43
hub_capdenis_makogon: npnp18:43
juiceimsplitbit: ok just asking18:43
juice:)18:43
imsplitbitnp18:44
hub_capimsplitbit: i approve this bp, personally. i think we need it18:44
vipulimsplitbit: so this doesn't directly relate to the Replication API anymore correct?18:44
imsplitbitI wanted to keep iteration 1 as small as possible18:44
imsplitbitvipul: no it doesn'18:44
hub_capi also think we need the create stuff too18:44
imsplitbitt18:44
hub_capbut it shoudl be a follow up18:44
imsplitbitalthough I'm borrowing heavily from it for topology api18:44
hub_capdemorris: will be happy18:44
hub_capso any issues w/ this?18:46
SlickNikI like the idea; but I'm still trying to wrap my head around the use cases.18:47
hub_capk18:47
hub_caplets give some more time18:47
hub_capto read18:47
vipulSlickNik: +1 I can't really say i don't like it.. i just want to know how metadata would be useful in vNext18:47
dougshelley66i had a question regarding the name of the key on create18:47
dougshelley66it looks like it is generated?18:47
vipullike is there certain metadata that will trigger behavior18:47
SlickNikimsplitbit: Can you explain where / how this would be useful for trove?18:48
hub_capSlickNik: i can give u a use case that isint related to replication18:48
imsplitbitthis is less useful to trove and more useful to users of trove18:48
hub_captagging for a UI18:48
imsplitbitexactly18:48
imsplitbitusers can make use of it's free form to store data that is critical to them to live with the instance that goes beyond the hostname18:49
imsplitbit'business_purpose': 'this is our super cool reporting box'18:49
imsplitbitor asset tagging for their internal business tracking18:49
imsplitbitit's for the users more than us18:49
hub_capsame reason that say, nova, has it18:49
imsplitbitbut we can use it for things liek CI18:49
imsplitbitlike18:49
*** michael-yu has joined #openstack-trove18:49
hub_capman u type liek me18:50
hub_cap;)18:50
vipulfair enough... you've convinced me18:50
imsplitbitI'm dealing with a pinched nerve18:50
SlickNikAh, okay. Now that makes a bit more sense to me.18:50
kevinconwayso quick quesiton. most of those cases seem like use cases for deployers of trove not developers consuming trove18:50
kevinconwayor did i catch that wrong?18:50
imsplitbitour UI team has been requesting it for some time18:50
kevinconwayok not really question.18:50
hub_capim pretty sure thats the opposite of what we said18:50
hub_cap18:49 < imsplitbit> 'business_purpose': 'this is our super cool reporting box'18:51
hub_caphow is that deployers?18:51
hub_capi bought an instance, i need to add biz_purpose to it18:51
hub_caprax doesnt care18:51
abramleyIf Nova already has metadata - and Trove deploys on Nova - why couldn't you just put your metadata in the nova instance? How / when do you choose to use Trove metadata vs Nova metadata ?18:51
kevinconwayso asset tagging, for example, would need to be enforced by a deployer other wise its just a freeform api call18:51
kevinconwayso any developer consuming could NOT add the asset tag18:51
imsplitbitbecause nova could possibly be obscured from the users depending on how it's deployed18:52
hub_capif your biz requires asset tagging kevinconway , then you can enforce that w/ your instances you buy18:52
juiceLike in my Bp :)18:52
hub_capbut deployers dont care18:52
hub_capcuz its freeform18:52
kevinconwayyeah my brain wires got crossed18:52
kevinconwayapp devs would use the feature18:52
hub_capyuppers18:52
imsplitbityes18:52
kevinconwayglad i could help18:52
vipula trove 'instance' could also be >1 nova instance18:53
kevinconwaythank you for your time18:53
hub_capthey have an operation for that.. have u seen pi?18:53
imsplitbitvipul: +118:53
vgnbkrAlso, if the feature was to be used both by devs and users, wouldn't there need to be some mechanism to determine if the k/v pairs should be shown to users?18:54
imsplitbitvgnbkr: I've put some thought into that18:54
hub_capvgnbkr: and not deleted ;)18:54
imsplitbitnova solves this by having 3 metadata services18:54
imsplitbit1 for users18:54
hub_capLOL srsly?!18:54
imsplitbit1 for instance internal18:54
imsplitbitand 1 called system_metadata for drivers18:54
imsplitbittotally serious18:54
*** jcru has quit IRC18:55
imsplitbitI don't feel like we need to take it to that leve18:55
imsplitbitl18:55
imsplitbitI thought about adding a .protected method for internal stuff to use and anything protected would not be displayed18:55
imsplitbitbut we then take the risk of taking up namespace for keys18:55
vgnbkrThat's fine, but then we should clarify that it is only for end user use, no?18:55
imsplitbitthis services use is for end user ATM yes18:55
SlickNikSo for v1, we (trove) are just going to have 1 right?18:56
imsplitbityes18:56
SlickNikFor the tagging use case for eg, you would need just 1 visible to the end user.18:56
SlickNikOkay, I'm good with it. Nice work on the bp imsplitbit.18:56
imsplitbitthanks!18:56
imsplitbitworked hard on it over the weekend18:56
hub_caphorray, so we all in agreement?18:56
vipulwe're not really building a metadata service really.. just a metadata store18:56
kevinconwayimsplitbit: can we get a spanish translation of the BP?18:56
imsplitbitcorrect18:56
imsplitbitmetadata store18:56
imsplitbitlol18:56
imsplitbitkevinconway: ^^^18:56
imsplitbitI had to try to 1 up esp18:57
imsplitbitwithout doing graphics :)18:57
hub_capkevinconway: feel free to put up the translations on transifex18:57
* imsplitbit is no good with visio18:57
SlickNikvipul: agreed. I don't think we need to broadcast this to newly booted instances like a metadata "service".18:57
hub_capoh and kevinconway u had to add a troll remark eh? ;)18:57
hub_capTROLLLLLLL18:57
hub_capTROVETROLLLLLL18:57
hub_capsomeone bring hiim his crown18:57
imsplitbitsky = blue, kevinconway = trolllllllllllllllllllllll18:57
vipulthis was great imsplitbit good job18:58
imsplitbitthese are just constants in life18:58
hub_capimsplitbit: ++18:58
imsplitbitthanks vipul18:58
*** jcru has joined #openstack-trove18:58
hub_capkevinconway: hows yer bridgehouse treating ya?18:58
hub_capTROVETROLLLLLLLLLLL18:58
hub_capok so we are done i thikn18:58
imsplitbitI'm working on fixing up some of the feedback from denis and I'll resubmit18:59
SlickNikThat's it then, I think we're through with the bp's we had.18:59
hub_capwe def need to clean up the rest of the bps18:59
imsplitbitthere is 100% unittest coverage tho18:59
hub_capannashen_: denis_makogon we will get to your snext wk when they are cleaned up18:59
espimsplitbit: nice work!18:59
denis_makogonhub_cap, cool18:59
SlickNikYes, denis_makogon and annashen_ please re-add your bps to the list for the next meeting once they're cleaned up. Thanks!18:59
*** kevinconway_ has joined #openstack-trove18:59
denis_makogonthere're still two BPs19:00
hub_capdenis_makogon: none of your sare in the proper format19:00
hub_capformat odes not just mean putting the link19:00
hub_capplz view the other blueprints19:00
hub_capand make yours like theirs19:00
denis_makogonpoint in time recovery and volume data is in proper format19:00
SlickNikdenis_makogon: Here is the template: https://wiki.openstack.org/wiki/TroveBlueprint19:01
*** kevinconway has quit IRC19:01
*** kevinconway_ is now known as kevinconway19:01
hub_capno its not, the blueprint says "point in time recovery"19:01
hub_capand thats it19:01
hub_capthats not valid19:01
hub_capand your other blueprint has a ton of junk in it19:01
hub_capalso19:01
hub_capnot valid19:01
grapexI've got a meeting. Talk to you all later!19:02
denis_makogonfine19:02
SlickNiklater grapex19:02
denis_makogoni need some clarification about my BPs now19:03
denis_makogonhub_cap, what do you call "junk" ?19:04
*** robertmy_ has quit IRC19:05
*** robertmyers has joined #openstack-trove19:05
denis_makogonhub_cap, SlickNik, please show me the difference between BP template and https://blueprints.launchpad.net/trove/+spec/point-in-time-recovery, https://blueprints.launchpad.net/trove/+spec/volume-snapshot19:05
*** eguz has joined #openstack-trove19:06
denis_makogonwaiting for the response from cores19:10
*** eghobo has quit IRC19:10
SlickNikhi denis_makogon: If you take a look at https://wiki.openstack.org/wiki/Trove/PointInTimeRecovery, it doesn't follow Blueprint template guidelines. I don't see a Justification or impacts section for example.19:12
*** demorris has quit IRC19:14
denis_makogonSlickNik, impacts should be mentioned even if there're none of them ?19:14
*** Barker has quit IRC19:14
hub_capthank you for handling SlickNik19:15
SlickNikdenis_makogon: If a bp has no impact, why chose to do it? :)19:15
denis_makogonSlickNik, for me "impact" mean that this thing ruins/breaks something19:16
denis_makogonSlickNik, and the features are chosen because of the actual use cases and approaches19:17
SlickNikdenis_makogon: Ah that's probably a language issue then. "Impact" means what does it affect in *any* way. Not just break / ruin.19:17
*** mattgriffin has quit IRC19:18
denis_makogonSlickNik, and now explain, why did this one skipped https://wiki.openstack.org/wiki/Trove/volume-data-snapshot-design ? It has all sections19:21
SlickNikdenis_makogon: BP's are chosen for a wide variety of reasons, most of which are enumerated in the Blueprint template. Which is one of the main reasons why we're asked to submit bps that follow the template guidelines.19:22
*** konetzed has joined #openstack-trove19:22
denis_makogonSlickNik, i get this, but i didn't get the answer why the third BP was skipped19:23
denis_makogonSlickNik, it has __all__ sections from the template19:24
denis_makogonSlickNik, please explain19:24
hub_capdenis_makogon: plz link it19:25
hub_capid like to see the blueprint, cuz last i checked19:25
hub_capit had too much junk in the blueprint19:25
hub_capinstead of a nice little pararaph explaining its intent19:25
*** mattgriffin has joined #openstack-trove19:27
*** mattgriffin has quit IRC19:28
hub_capwe want 3 to 5 sentence explainign why, thats it19:29
hub_capin the blueprint19:29
SlickNikdenis_makogon:  A couple of things that stand out to me are:19:29
SlickNik1. It's missing the whole point of _why_ this is needed. If you look at the Justification section, it talks about _HOW_ this can be done, which is not a justification of _WHY_ this should be done.19:29
SlickNik2. There are essention sections that are needed by the template (eg. Impacts) that have a heading but no text under them.19:29
hub_cap++19:29
SlickNikAlso, I believe that hub_cap is talking about the actual bp on launchpad (not the wiki-page) i.e. https://blueprints.launchpad.net/trove/+spec/volume-snapshot . This should not be a wall of text. It should just be a few lines regarding the justification, and should link to the wiki page which has the rest of the bp outlined using the template guildelines.19:32
*** denis_makogon has quit IRC19:33
openstackgerritA change was merged to openstack/python-troveclient: Fix database-list via CLI for large # of dbs  https://review.openstack.org/8292319:34
*** rramirez has joined #openstack-trove19:37
*** SnowDust has joined #openstack-trove19:39
*** khyati_ has quit IRC19:43
*** mattgriffin has joined #openstack-trove19:44
hub_capyuuuup SlickNik19:45
*** radez is now known as radez_g0n319:49
*** pdmars has quit IRC19:51
*** pdmars has joined #openstack-trove19:51
ViswaV"god we need a single metadata svc for openstack hahahah"  hub_cap:  +4219:57
hub_capLOL ViswaV19:57
hub_capamcrn: dude is the rain comin down in teh wasteland?19:58
amcrnnot at the moment19:58
hub_capman.. its started up here19:58
hub_caplike crazy thunder, lightning, stormy19:58
*** mattgriffin has quit IRC19:59
amcrnyeah, it's supposed to hit down here a little bit later today20:01
cp16nethub_cap: amcrn watch out for the mud slides20:02
*** mattgriffin has joined #openstack-trove20:12
*** kevinconway_ has joined #openstack-trove20:14
*** kevinconway has quit IRC20:15
*** kevinconway_ is now known as kevinconway20:15
*** mattgriffin has quit IRC20:16
*** ashestakov has quit IRC20:18
*** mattgriffin has joined #openstack-trove20:19
*** rwsu has joined #openstack-trove20:22
*** kevinconway has quit IRC20:24
*** mattgriffin has quit IRC20:27
*** mattgriffin has joined #openstack-trove20:27
*** khyati_ has joined #openstack-trove20:28
*** michael-yu has quit IRC20:30
*** sbfox has quit IRC20:30
openstackgerritAndreas Jaeger proposed a change to openstack/trove: Check that all po/pot files are valid  https://review.openstack.org/8423920:35
*** eguz has quit IRC20:36
*** michael-yu has joined #openstack-trove20:36
*** sbfox has joined #openstack-trove20:42
*** tanisdl_ has joined #openstack-trove20:46
*** tanisdl has quit IRC20:49
*** tanisdl_ is now known as tanisdl20:49
*** mattgriffin has quit IRC20:49
*** kevinconway has joined #openstack-trove20:50
*** mattgriffin has joined #openstack-trove20:55
openstackgerritAndreas Jaeger proposed a change to openstack/trove: Check that all po/pot files are valid  https://review.openstack.org/8423920:56
*** mattgriffin has quit IRC20:57
*** harlowja is now known as harlowja_away21:00
*** mattgriffin has joined #openstack-trove21:01
*** eghobo has joined #openstack-trove21:03
*** mattgriffin has quit IRC21:03
*** pdmars has quit IRC21:09
*** harlowja_away is now known as harlowja21:19
*** robertmyers has quit IRC21:30
*** SnowDust has quit IRC21:30
esphey, any core folks in the mood to review? :) https://review.openstack.org/#/c/81682/, https://review.openstack.org/#/c/81557/, https://review.openstack.org/#/c/81410/21:31
espor non-core ^21:31
*** esp has left #openstack-trove21:31
*** sbfox has quit IRC21:33
*** grapex has quit IRC21:35
*** sbfox has joined #openstack-trove21:38
*** esp has joined #openstack-trove21:39
*** michael-yu has quit IRC21:46
*** ViswaV has quit IRC21:51
*** michael-yu has joined #openstack-trove21:52
*** ViswaV has joined #openstack-trove21:53
*** flaper87 is now known as flaper87|afk21:57
*** michael-yu has quit IRC22:12
*** michael-yu has joined #openstack-trove22:16
*** jasonb365 has joined #openstack-trove22:23
*** kevinconway has quit IRC22:26
*** jcru has quit IRC22:27
*** yogesh has quit IRC22:28
*** jasonb365 has quit IRC22:31
*** amytron has quit IRC22:31
*** esp2 has joined #openstack-trove22:40
*** esp2 has quit IRC22:45
*** grapex has joined #openstack-trove23:03
*** jmontemayor has quit IRC23:13
openstackgerritNikhil Manchanda proposed a change to openstack/trove: Remove mockito, and replace with mock  https://review.openstack.org/8288823:23
*** khyati_ has quit IRC23:25
*** yidclare has quit IRC23:26
*** rramirez has quit IRC23:32
*** tanisdl has quit IRC23:41

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