Wednesday, 2015-12-09

*** yamamoto has joined #openstack-meeting-400:09
*** u_kozat has joined #openstack-meeting-400:13
*** Prithiv has joined #openstack-meeting-400:15
*** u_kozat has quit IRC00:17
*** salv-orl_ has joined #openstack-meeting-400:18
*** salv-orlando has quit IRC00:20
*** yamamoto has quit IRC00:21
*** sdake has quit IRC00:25
*** sridhar_ram has quit IRC00:25
*** Prithiv has quit IRC00:29
*** Prithiv has joined #openstack-meeting-400:30
*** FallenPegasus is now known as MarkAtwood00:30
*** belmoreira has quit IRC00:30
*** sridhar_ram has joined #openstack-meeting-400:32
*** mbound_ has quit IRC00:41
*** openstackstatus has quit IRC00:50
*** openstack has joined #openstack-meeting-400:53
*** ChanServ sets mode: +o openstack00:53
*** sridhar_ram has joined #openstack-meeting-401:01
*** pmesserli has quit IRC01:03
*** bpokorny_ has joined #openstack-meeting-401:06
*** Swami_ has quit IRC01:09
*** bpokorny has quit IRC01:09
*** bpokorny_ has quit IRC01:10
*** itisha has quit IRC01:16
*** Prithiv has quit IRC01:18
*** sridhar_ram has quit IRC01:22
*** krtaylor has quit IRC01:22
*** sridhar_ram1 has joined #openstack-meeting-401:24
*** sridhar_ram1 has quit IRC01:25
*** shuquan has joined #openstack-meeting-401:33
*** krtaylor has joined #openstack-meeting-401:36
*** sridhar_ram has joined #openstack-meeting-401:37
*** banix has joined #openstack-meeting-401:42
*** shuquan has quit IRC01:44
*** sridhar_ram has quit IRC01:45
*** tfukushima has joined #openstack-meeting-401:54
*** sridhar_ram has joined #openstack-meeting-401:59
*** sridhar_ram has quit IRC02:02
*** Swami has joined #openstack-meeting-402:02
*** armax has quit IRC02:02
*** yamamoto has joined #openstack-meeting-402:09
*** Swami has quit IRC02:09
*** yamamoto has quit IRC02:10
*** bharathm has quit IRC02:13
*** bobh has joined #openstack-meeting-402:17
*** tfukushima has quit IRC02:20
*** devananda has joined #openstack-meeting-402:27
*** s3wong has quit IRC02:43
*** prashantD has quit IRC02:46
*** baoli has joined #openstack-meeting-402:52
*** yamamoto has joined #openstack-meeting-402:59
*** yamahata has quit IRC03:01
*** baoli has quit IRC03:09
*** bobh has quit IRC03:10
*** MarkAtwood has quit IRC03:42
*** MarkAtwood has joined #openstack-meeting-403:43
*** fawadkhaliq has joined #openstack-meeting-403:53
*** MarkAtwood has quit IRC03:57
*** fawadkhaliq has quit IRC04:00
*** mattymo has quit IRC04:05
*** siwos_ has quit IRC04:06
*** siwos_ has joined #openstack-meeting-404:07
*** mattymo has joined #openstack-meeting-404:11
*** dims has joined #openstack-meeting-404:13
*** dims has quit IRC04:15
*** bobh has joined #openstack-meeting-404:18
*** dims has joined #openstack-meeting-404:18
*** banix has quit IRC04:28
*** dims has quit IRC04:29
*** bpokorny has joined #openstack-meeting-404:44
*** fawadkhaliq has joined #openstack-meeting-404:45
*** inteq has joined #openstack-meeting-404:46
*** fawadkhaliq has quit IRC04:47
*** kexiaodong has quit IRC04:50
*** bpokorny has quit IRC04:55
*** persia has quit IRC05:06
*** bobh has quit IRC05:07
*** persia has joined #openstack-meeting-405:09
*** sdake has joined #openstack-meeting-405:15
*** dims has joined #openstack-meeting-405:20
*** fawadkhaliq has joined #openstack-meeting-405:33
*** armax has joined #openstack-meeting-405:38
*** salv-orl_ has quit IRC06:00
*** salv-orlando has joined #openstack-meeting-406:00
*** MarkAtwood has joined #openstack-meeting-406:05
*** numans has joined #openstack-meeting-406:08
*** javeriak has joined #openstack-meeting-406:12
*** watanabe_isao has joined #openstack-meeting-406:17
*** salv-orl_ has joined #openstack-meeting-406:17
*** salv-orlando has quit IRC06:20
*** logan- has quit IRC06:24
*** javeriak has quit IRC06:25
*** javeriak has joined #openstack-meeting-406:25
*** irenab has joined #openstack-meeting-406:31
*** armax has quit IRC06:48
*** irenab has quit IRC06:51
*** EvgenyF has joined #openstack-meeting-406:55
*** [1]evgenyf has joined #openstack-meeting-406:55
*** nkrinner has joined #openstack-meeting-406:56
*** tfukushima has joined #openstack-meeting-406:59
*** javeriak has quit IRC07:02
*** javeriak has joined #openstack-meeting-407:02
*** chem has joined #openstack-meeting-407:04
*** javeriak_ has joined #openstack-meeting-407:06
*** javeriak has quit IRC07:07
*** May-meimei has quit IRC07:11
*** May-meimei has joined #openstack-meeting-407:14
*** MarkAtwood has quit IRC07:20
*** MarkAtwood has joined #openstack-meeting-407:20
*** dshakhray has joined #openstack-meeting-407:26
*** paul-carlton2 has joined #openstack-meeting-407:29
*** irenab has joined #openstack-meeting-407:30
*** chem has quit IRC07:42
*** sridhar_ram has joined #openstack-meeting-407:43
*** nkrinner has quit IRC07:46
*** nkrinner has joined #openstack-meeting-407:46
*** nkrinner has quit IRC07:54
*** nkrinner has joined #openstack-meeting-407:55
*** chem has joined #openstack-meeting-407:58
*** zeih has joined #openstack-meeting-408:01
*** matrohon has joined #openstack-meeting-408:03
*** MarkAtwood has quit IRC08:07
*** matrohon has quit IRC08:07
*** belmoreira has joined #openstack-meeting-408:15
*** paul-carlton2 has quit IRC08:17
*** paul-carlton2 has joined #openstack-meeting-408:19
*** amotoki has joined #openstack-meeting-408:22
*** chem has quit IRC08:23
*** fawadkhaliq has quit IRC08:32
*** chem has joined #openstack-meeting-408:34
*** chem has quit IRC08:36
*** chem has joined #openstack-meeting-408:40
*** matrohon has joined #openstack-meeting-408:46
*** fawadkhaliq has joined #openstack-meeting-408:48
*** fawadkhaliq has quit IRC08:49
*** javeriak_ has quit IRC08:49
*** dshakhray has quit IRC08:51
*** tfukushima has quit IRC08:51
*** tfukushima has joined #openstack-meeting-408:52
*** chem has left #openstack-meeting-408:53
*** salv-orl_ has quit IRC08:58
*** zeih has quit IRC08:58
*** paul-carlton2 has quit IRC08:59
*** yamahata has joined #openstack-meeting-409:01
*** _degorenko|afk is now known as degorenko09:04
*** openstackstatus has quit IRC09:05
*** openstack has joined #openstack-meeting-409:08
*** ChanServ sets mode: +o openstack09:08
*** javeriak has joined #openstack-meeting-409:13
*** yamahata has quit IRC09:15
*** javeriak has quit IRC09:18
*** zeih has joined #openstack-meeting-409:18
*** javeriak has joined #openstack-meeting-409:19
*** sridhar_ram has quit IRC09:29
*** javeriak has quit IRC09:32
*** fawadkhaliq has joined #openstack-meeting-409:34
*** javeriak has joined #openstack-meeting-409:35
*** mbound_ has joined #openstack-meeting-409:35
*** igordcard has joined #openstack-meeting-409:38
*** Kevin_Zheng has quit IRC09:40
*** matrohon has quit IRC09:41
*** dshakhray has joined #openstack-meeting-409:45
*** Prithiv has joined #openstack-meeting-409:50
*** tfukushima has quit IRC09:52
*** salv-orlando has joined #openstack-meeting-409:59
*** salv-orlando has quit IRC10:03
*** igordcard has quit IRC10:08
*** wojdev has joined #openstack-meeting-410:08
*** wojdev has quit IRC10:17
*** wojdev has joined #openstack-meeting-410:23
*** dims has quit IRC10:25
*** EvgenyF has quit IRC10:27
*** [1]evgenyf has quit IRC10:27
*** igordcard has joined #openstack-meeting-410:30
*** watanabe_isao has quit IRC10:37
*** May-meimei has quit IRC10:38
*** fawadkhaliq has quit IRC10:57
*** fawadkhaliq has joined #openstack-meeting-410:57
*** fawadkhaliq has quit IRC11:03
*** May-meimei has joined #openstack-meeting-411:05
*** salv-orlando has joined #openstack-meeting-411:10
*** igordcard has quit IRC11:19
*** wojdev has quit IRC11:20
*** paul-carlton2 has joined #openstack-meeting-411:31
*** EvgenyF has joined #openstack-meeting-411:34
*** [1]evgenyf has joined #openstack-meeting-411:34
*** dims has joined #openstack-meeting-411:37
*** kproskurin has joined #openstack-meeting-411:38
*** sambetts-afk is now known as sambetts11:38
*** igordcard_ has joined #openstack-meeting-411:54
*** igordcard_ has quit IRC11:55
*** javeriak has quit IRC11:56
*** javeriak has joined #openstack-meeting-412:01
*** yamamoto has quit IRC12:03
*** cdelatte has quit IRC12:05
*** yamamoto has joined #openstack-meeting-412:06
*** igordcard_ has joined #openstack-meeting-412:12
*** igordcard_ has quit IRC12:12
*** wojdev has joined #openstack-meeting-412:12
*** igordcard_ has joined #openstack-meeting-412:14
*** yamamoto has quit IRC12:15
*** salv-orl_ has joined #openstack-meeting-412:17
*** javeriak has quit IRC12:19
*** salv-orlando has quit IRC12:20
*** javeriak has joined #openstack-meeting-412:24
*** Steap has left #openstack-meeting-412:28
*** matrohon has joined #openstack-meeting-412:29
*** javeriak has quit IRC12:34
*** matrohon has quit IRC12:34
*** matrohon has joined #openstack-meeting-412:36
*** fawadkhaliq has joined #openstack-meeting-412:38
*** bobh has joined #openstack-meeting-412:44
*** salv-orl_ has quit IRC12:44
*** cdelatte has joined #openstack-meeting-412:48
*** salv-orlando has joined #openstack-meeting-412:49
*** amotoki_ has joined #openstack-meeting-412:56
*** amotoki__ has joined #openstack-meeting-412:59
*** amotoki has quit IRC12:59
*** amotoki__ is now known as amotoki___12:59
*** julim has joined #openstack-meeting-413:01
*** amotoki___ is now known as amotoki__13:02
*** amotoki_ has quit IRC13:02
*** amotoki__ is now known as amotoki13:02
*** paul-carlton2 has quit IRC13:03
*** jed56 has quit IRC13:03
*** javeriak has joined #openstack-meeting-413:09
*** klamath has joined #openstack-meeting-413:15
*** bobh has quit IRC13:17
*** fawadkhaliq has quit IRC13:27
*** baoli has joined #openstack-meeting-413:40
*** baoli_ has joined #openstack-meeting-413:41
*** yamamoto has joined #openstack-meeting-413:44
*** baoli has quit IRC13:45
*** bzhou has joined #openstack-meeting-413:46
*** woodard has joined #openstack-meeting-413:49
*** yamahata has joined #openstack-meeting-413:52
*** jed56 has joined #openstack-meeting-413:53
*** yamamoto has quit IRC13:53
*** vtech has joined #openstack-meeting-413:56
*** vincentfrancoise has joined #openstack-meeting-413:59
*** seanmurphy has joined #openstack-meeting-413:59
acabot#startmeeting watcher13:59
openstackMeeting started Wed Dec  9 13:59:54 2015 UTC and is due to finish in 60 minutes.  The chair is acabot. Information about MeetBot at http://wiki.debian.org/MeetBot.13:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:59
*** openstack changes topic to " (Meeting topic: watcher)"13:59
openstackThe meeting name has been set to 'watcher'13:59
*** gabor_antal has joined #openstack-meeting-413:59
acabothi14:00
vtecho/14:00
tpeopleso/14:00
jed56o/14:00
seanmurphyhi guys14:00
acabotour agenda for today #link https://wiki.openstack.org/wiki/Watcher_Meeting_Agenda#12.2F9.2F201514:00
sballeo/14:00
vincentfrancoiseo/14:00
bzhouhi14:00
*** javeriak_ has joined #openstack-meeting-414:00
acabotmore people every week for the roll call ;-)14:01
*** logan- has joined #openstack-meeting-414:01
acabot#topic Announcements14:01
*** openstack changes topic to "Announcements (Meeting topic: watcher)"14:01
*** cdupont has joined #openstack-meeting-414:01
*** dtardivel has joined #openstack-meeting-414:01
cduponthi all14:02
dtardivelhi14:02
*** sdake has quit IRC14:02
acabotour mid-cycle meetup will take place at IBM Austin february 2-514:02
sballe+114:02
*** yamahata has quit IRC14:02
*** javeriak has quit IRC14:02
*** vmahe_ has joined #openstack-meeting-414:02
acabotan eventbrite is available for registration14:02
acabotthx to jwcroppe for hosting it14:02
*** mehdi__ has joined #openstack-meeting-414:02
acabotsballe: I think we can start spreading the event around us14:03
sballeagreed14:03
acabotwe will provide details for accommodations through a wiki page next week14:04
acabotWatcher code as been tagged last friday as it was the mitaka-1 deadline14:04
*** pmesserli has joined #openstack-meeting-414:05
seanmurphyacabot: what specifically does this mean?14:05
seanmurphy(in one sentence)14:05
*** bruno has joined #openstack-meeting-414:05
*** bruno is now known as brunograz14:05
dtardivelseanmurphy: new pypi package are available (0.21.0 for watcher and 0.20.0 for python-watcherclient)14:06
acabotwe try to stick to the OpenStack release schedule so we release software every 2 months (3 releases between each summit)14:06
seanmurphygot it - thanks14:06
acabotit is not mandatory as we are not under the big tent but it is a good way to complete BP thanks to the deadline ;-)14:07
acabotdoc and packages are updated when we tag the software14:07
acabotas well14:07
acabotany other announcement ?14:07
acabot#topic Review Action Items14:08
*** openstack changes topic to "Review Action Items (Meeting topic: watcher)"14:08
* edleafe wanders in late14:08
*** javeriak has joined #openstack-meeting-414:09
acabota lot of code refactoring has been done after the glossary merge14:09
acabotplease review all related patches https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/glossary-related-refactoring,n,z14:09
tpeopleswill spend some time this week reviewing those14:10
*** javeriak_ has quit IRC14:10
acabot#action tpeoples review code refactoring https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/glossary-related-refactoring,n,z14:10
* sballe will do the same14:11
acabot#action sballe review code refactoring https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/glossary-related-refactoring,n,z14:11
bzhouI will review those too14:11
mehdi__will do the same14:11
sballe+114:11
acabottpeoples submitted a devstack plugin14:12
dtardivelI will test it14:12
acabotit needs to be tested and reviewed14:12
acabotot> #action mehdi__ review code refactoring https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/glossary-related-refactoring,n,z14:12
acabot#action mehdi__ review code refactoring https://review.openstack.org/#/q/status:open+project:openstack/watcher+branch:master+topic:bp/glossary-related-refactoring,n,z14:12
tpeoplesdtardivel: you'll need to get the commit into your local git repo and then use that local repo as the path with enable_plugin14:13
acabot#dtardivel review https://review.openstack.org/#/c/254584/14:13
acabot#action dtardivel review https://review.openstack.org/#/c/254584/14:13
cdupontI can also review :)14:13
*** hamza has quit IRC14:13
tpeoplesdtardivel: you'll also need to clone  python-watcher-client into the same directory as watcher due to some path lookup reasons14:13
acabotcdupont: devstack ?14:13
sballeall the more people who can review the better14:14
cdupontOK14:14
acabotsballe: +114:14
acabot#action cdupont review https://review.openstack.org/#/c/254584/14:14
dtardiveltpeoples: ok14:14
tpeoplesask me if you have questions14:14
*** javeriak has quit IRC14:15
acabotI'd like to thank Darren & Gábor who fixed many low hanging fruit bugs14:15
cduponttpeoples: how hard is it to install?14:15
acabotif you can give your IRC name it would be great ;-)14:15
*** javeriak has joined #openstack-meeting-414:16
tpeoplescdupont: not very, it's only hard now because you'll need to pull down my changes into your local git repo since they aren't merged yet, then use that repo instead to enable the plugin14:16
cdupontOK great14:17
acabotto find low hanging fruit bugs : https://bugs.launchpad.net/watcher/+bugs?field.tag=low-hanging-fruit14:17
acaboton watcher specs, there are 2 reviews in progress14:18
*** javeriak has quit IRC14:19
jed56https://review.openstack.org/#/q/status:open+watcher-specs,n,z14:19
acabotbzhou: it seems there is a problem on this one (the last PS) https://review.openstack.org/#/c/252268/14:19
acabotbzhou: could you fix it ?14:19
bzhouok. I will work with Junjie to fix it14:20
acabotok thx14:20
sballebzhou: +114:20
acabotthe other one is just a move into implemented folder for telemetry, sballe, can you +2 today ?14:20
*** dronshaw has joined #openstack-meeting-414:20
sballeyes14:21
acabotthx14:21
sballewhich spec?14:21
acabot#action sballe review https://review.openstack.org/#/c/254130/14:21
acabot#action bzhou fix review https://review.openstack.org/#/c/252268/ (last PS)14:21
*** jmckind has joined #openstack-meeting-414:22
acabot#topic Blueprint/Bug Review and Discussion14:22
*** openstack changes topic to "Blueprint/Bug Review and Discussion (Meeting topic: watcher)"14:22
*** banix has joined #openstack-meeting-414:22
*** jmckind has quit IRC14:23
acabottpeoples: you had to split the BP https://blueprints.launchpad.net/watcher/+spec/well-defined-interfaces14:23
*** srwilkers has joined #openstack-meeting-414:23
tpeoplesI spent a bit of time looking at our use cases to try and split this up and it seems like a lot of things already have well-defined interfaces, so I didn't want to create BPs that are useless.14:23
tpeoplesThe Strategy abstraction allows us to define different optimization algorithms already given the current state of the cloud; the cluster model collector allows us to define different ways to get the current state (metrics).14:23
tpeoplesThe one thing that I thought could use some work is how actions are defined, and I think we should try and use taskflow for these to get a well-defined interface as well as for other reasons.  See https://blueprints.launchpad.net/watcher/+spec/use-taskflow for more details.14:23
jed56tpeoples  I agree14:24
vmahe_I agree that we should have a look at taskflow project and see if it fits our needs14:24
jed56about taskflow I want to understand how we can implement our own planner strategy14:25
*** rbak has quit IRC14:25
acabot#action vmahe_  jed56 look at the taskflow project to see if it fits Watcher needs14:25
acabotdoes any one of you already experienced taskflow ?14:25
tpeoplesi have used it a bit14:25
acabotin which context ?14:26
tpeoplesrunning concurrent tests that had a bunch of dependencies.  we also use it for the nova-powervm driver14:26
acabotok14:26
acabotwe have a couple of new BPs these week14:27
tpeoplesi think we'll find it suits our needs :).  a lot of what we're doing in code we'd get out of the box with it.  let's discuss more next week14:27
acabottpeoples: ok14:27
tpeoplesacabot:  before we move on, what do we want to use with the well-defined-interfaces BP?14:28
tpeopleswant to do*14:28
tpeoplesmark as obsolete?14:29
acabottpeoples: we have things to change regarding interfaces between watcher components14:29
*** jmckind has joined #openstack-meeting-414:29
acabottpeoples: but I think its a big "spec" work14:29
tpeoplesok14:30
acabotI suggest to keep this BP in the list and update it with a more precise scope (like one component) and use it as a test14:31
acabotwe have 3 new BPs14:32
acabotthe first one is https://blueprints.launchpad.net/watcher/+spec/efficacy-indicator14:32
acabotany comment on this one ?14:32
acabotshould we have a spec for it ?14:33
tpeoples+1 to efficacy over efficiency.  yes, i think a spec is necessary to outline how it's going to be implemented14:33
dtardivel+114:33
jed56+214:34
*** yamamoto has joined #openstack-meeting-414:34
acabot#action acabot start a spec for  https://blueprints.launchpad.net/watcher/+spec/efficacy-indicator14:34
*** cdupont_ has joined #openstack-meeting-414:34
sballe+214:34
*** igordcard has joined #openstack-meeting-414:34
acabot2nd https://blueprints.launchpad.net/watcher/+spec/watcher-ui14:34
acabotintegration of Watcher in Horizon14:34
acabotwe already have a beta version on our side14:35
sballewe might need to talk to the horizon tea,14:35
sballes/team14:35
*** cdupont has quit IRC14:35
sballeacabot: maybe you could do a demo so we can see it14:35
*** brucet has joined #openstack-meeting-414:35
acabotsballe: sure I will provide a video for next meeting14:35
sballeacabot: +114:36
*** igordcard has quit IRC14:36
tpeopleswe'll want to integrate that into the devstack plugin as a horizon plugin at some point, jfyi14:36
acabot#action acabot record a video of Watcher UI before next meeting14:36
acabottpeoples: absolutely14:36
*** igordcard has joined #openstack-meeting-414:37
acabotand then the 3rd : https://blueprints.launchpad.net/watcher/+spec/basic-cloud-consolidation-integration14:37
acabotseanmurphy has submitted it14:37
seanmurphywe would like to see if we can implement our earlier work on watcher14:37
seanmurphyunderstand what is required to realize it on watcher14:38
seanmurphyand implement it14:38
seanmurphyacabot suggested doing it for the m-3 mar 3 date14:38
seanmurphywhich we can do14:38
seanmurphym-2 is a bit soon for us14:38
seanmurphyas we have commitments from now into early jan14:38
sballeseanmurphy: sounds good14:39
acabotseanmurphy: can we have reviewed specs on it by 21st jan ?14:39
sballe+114:39
seanmurphyyes - this should be possible i think14:39
acabotand then implem for mitaka-314:39
acabotok great14:39
seanmurphyright14:39
tpeoplesi think jwcroppe and i would probably be interested in helping with a CPU util-based algorithm14:39
seanmurphyi will need to look at some examples to make sure i structure them properly etc14:40
acabottpeoples: do you mean on the same BP ?14:40
seanmurphywe’d be happy work with anyone on it14:40
*** raofei_ is now known as raofei14:40
jed56:)14:40
tpeoplesacabot: yeah (even though this BP isn't "reactive")14:40
acabot#action seanmurphy start a spec for https://blueprints.launchpad.net/watcher/+spec/basic-cloud-consolidation-integration14:41
cdupont_related to the consolidation I have some questions14:41
*** Swami has joined #openstack-meeting-414:41
cdupont_shall I? :)14:42
seanmurphyshoot14:42
acabotcdupont_: sure14:42
cdupont_we also started two BPs on a consolidation language/grammar14:42
seanmurphyok14:43
cdupont_I rretro-engineered a bit Watcher code14:43
cdupont_at the moment there is a data model implemented14:43
cdupont_what I'm not sure is how it can be extended t suit our needs14:43
*** fawadkhaliq has joined #openstack-meeting-414:43
sballecdupont_: can you clarify?14:44
cdupont_how the data model of Watcher can be extended, i.e. what if I need more infos on a VM, for example it's last migration time14:45
jed56cdupont : this a good question14:45
jed56:)14:45
acabotcdupont_: we are still waiting for a spec regarding the grammar stuff14:45
*** neelashah has joined #openstack-meeting-414:45
acabotcdupont_: it would be easier to iterate on gerrit14:46
cdupont_the grammar for consolidation rules?14:46
jed56We need to write a BP about how to extend to data model depending the need14:46
acabotyes14:46
cdupont_+114:47
jed56we will never have a universal model14:47
*** eric__ has joined #openstack-meeting-414:47
cdupont_it's not trivial really :)14:48
jed56We can maybe provided like CloudSim some generic model14:48
acabotthis BP https://blueprints.launchpad.net/watcher/+spec/watcher-consolidation-grammar has been accepted but you need to write a spec to give us details about what you are planning to do14:48
cdupont_OK14:48
cdupont_this is about the grammar for consolidation rules14:49
acabotspecs are in watcher-specs repo, you will find templates available14:49
cdupont_i.e. "this VM must not move", "those two VMs must stay together", etc.14:49
sballe+1 on the spec14:49
acabotcdupont_: ok so seanmurphy will start a spec on consolidation algo and you will be able to ask questions regarding the data model through gerrit ok ?14:50
cdupont_it's OK14:50
seanmurphyworks for me14:50
acabotany update on https://blueprints.launchpad.net/watcher/+spec/watcher-consolidation-rules-api ?14:50
jed56if have question regarding data model you can use #openstack-watcher14:50
acabotMichele is set as assignee but I dont know who he is14:51
cdupont_acabot: It's Federico. I don't know of any update14:51
acabotok I will send a mail14:51
cdupont_OK14:52
acabotanyone from Servionica ? https://blueprints.launchpad.net/watcher/+spec/watcher-overload-underload14:52
acabot#topic Open Discussion14:53
*** openstack changes topic to "Open Discussion (Meeting topic: watcher)"14:53
seanmurphymeetings over holiday period?14:53
vmahe_we don't know what holiday means :-)14:53
vincentfrancoisevmahe_: lol14:54
seanmurphyhaha14:54
acabotdtardivel will handle the meeting next week and sballe will do it around christmas14:54
tpeoplesacabot: i want to work on https://blueprints.launchpad.net/watcher/+spec/tempest-basic-set-up if no one already has14:54
seanmurphyok14:54
seanmurphyso basically business as usual14:54
seanmurphymeeting will take place same bat time, same bat channel14:54
jed56vmahe : how to make a work a better place with so many holidays :)14:54
*** javeriak has joined #openstack-meeting-414:54
seanmurphythanks14:54
jed56word14:54
acabot#action tpeoples start working on https://blueprints.launchpad.net/watcher/+spec/tempest-basic-set-up14:55
tpeoplesthere's the translation BP too, but I think that's pretty low priority at this point14:55
acabotthere is also an open BP on translation, anyone interested ? ;-)14:55
acabottpeoples: +114:56
tpeoplesi'm interested in that but don't want to grab it at this point :)14:56
bzhouanyone want to work on https://blueprints.launchpad.net/watcher/+spec/optimization-threshold? Or I am going to take it.14:56
acabotbzhou: I think it is deeply related with your PoC, it would be great to have you on this one14:57
bzhouacabot: yeah14:57
jed56+114:57
*** Ng has joined #openstack-meeting-414:57
acabot#action bzhou start working on https://blueprints.launchpad.net/watcher/+spec/optimization-threshold?14:58
sballebzhou: +114:58
*** mbound_ has quit IRC14:58
*** rbak has joined #openstack-meeting-414:58
tpeopleswould anyone else like the openstackgerritbot to sit in our channel, or would it annoy people?  i'm not sure if it's even possible, might have to spin up our own bot for it, but i can find out14:58
sballeI am not sure what that means?14:59
acabottpeoples: I already did it ;-) https://review.openstack.org/#/c/254765/14:59
*** mhoppal has joined #openstack-meeting-414:59
acabotbut the CI failed so I'm waiting...14:59
sballelol14:59
tpeoplesawesome acabot14:59
tpeoplessballe: it's a bot that puts a message to the channel when someone submits a patchset14:59
acabotthanks for this great meeting15:00
jed56thanks :)15:00
tpeoplesttyl15:00
cdupont_tks15:00
acabotbye15:00
seanmurphybye guys!15:00
bzhouthanks15:00
cdupont_bye15:00
acabot#endmeeting15:00
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"15:00
vincentfrancoisebye15:00
jed56bye15:00
openstackMeeting ended Wed Dec  9 15:00:28 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-09-13.59.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-09-13.59.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/watcher/2015/watcher.2015-12-09-13.59.log.html15:00
mehdi__tnx bye15:00
sballebye15:00
*** brunograz has left #openstack-meeting-415:01
jasondotstar#startmeeting vahana15:01
openstackMeeting started Wed Dec  9 15:01:00 2015 UTC and is due to finish in 60 minutes.  The chair is jasondotstar. 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: vahana)"15:01
openstackThe meeting name has been set to 'vahana'15:01
Ng.o/15:01
jasondotstar#topic roll call15:01
*** openstack changes topic to "roll call (Meeting topic: vahana)"15:01
*** bobh has joined #openstack-meeting-415:01
jasondotstarhowdy Ng15:01
Nghey hey :)15:01
vtech\o/15:01
jasondotstarhey there15:01
*** igordcard__ has joined #openstack-meeting-415:02
jasondotstar#topic Introduction15:02
*** openstack changes topic to "Introduction (Meeting topic: vahana)"15:02
jasondotstareventually I'll drop this section of the meeting15:02
*** mhoppal has left #openstack-meeting-415:02
jasondotstarbut it's new, so I figure I should remind folks...15:02
*** igordcard has quit IRC15:02
jasondotstarfriendly reminder that the OpenStack Vahana project is an effort to build an iOS client for OpenStack, in the form of one or more frameworks for interacting with the OS API, and *possibly* front end app15:03
jasondotstar#link https://etherpad.openstack.org/p/openstack-mobile-ios-brainstorm15:03
jasondotstarInterested parties are encouraged to join the #openstack-vahana IRC channel15:03
jasondotstarwe'll keep the train moving here......15:04
jasondotstarI'm feeling like this might be another short meeting for us, but we'll see....15:04
jasondotstar#topic Action Items from Last Meeting15:04
*** openstack changes topic to "Action Items from Last Meeting (Meeting topic: vahana)"15:04
jasondotstarso for some reason15:04
jasondotstarthe meetbot didn't keep the meeting log from our last meeting :-(15:05
*** mehdi__ has quit IRC15:05
*** sigmavirus24_awa is now known as sigmavirus2415:05
Ngjasondotstar: I think it did, but last week the topic was set to "openstack-vahana"15:05
jasondotstarahhh15:05
jasondotstarso consistency is key15:05
jasondotstarso i think we'll go with starting meeting as just vahana15:06
jasondotstarthat's what we started out with :-)15:06
*** cdupont_ has quit IRC15:06
Ng+115:06
* jasondotstar wonders if we can find the agenda using openstack-vahana15:06
* jasondotstar looks15:06
jasondotstarhttp://eavesdrop.openstack.org/meetings/openstack-vahana/ 40415:07
Nghttp://eavesdrop.openstack.org/meetings/openstack_vahana/2015/openstack_vahana.2015-12-02-15.01.html15:07
*** bzhou has quit IRC15:07
*** irenab has quit IRC15:07
jasondotstar\o/15:07
jasondotstarunderstore15:07
jasondotstarunderscore*15:08
jasondotstarcool.15:08
Ngso I had one action item, and I need to carry it over because I haven't done it yet, sorry!15:08
jasondotstarno worries15:08
jasondotstarI did get a chance to chat with the horizon folks yesterday15:09
jasondotstarwe had a decent talk about native vs. cordova15:09
jasondotstarPiet from the UX team was actually there15:09
*** cdelatte has quit IRC15:09
jasondotstarso if you want to touch base w/ him15:09
Ngah nice15:09
Ngyeah15:09
Ngwhat was their feeling on native vs cordova?15:10
jasondotstarhe gave me some insight regarding going down this road before15:10
*** cdelatte has joined #openstack-meeting-415:10
jasondotstarwell, several of them seemed to agree with the platform agnostic play15:10
jasondotstarI gave them a few things to chew on regarding the benefits of going native15:11
jasondotstarending with a 'and i just dont want to do HTML/JS'15:11
Nghehe15:11
jasondotstartvOS dashboards15:11
jasondotstarwatchOS alerts15:12
*** delattec has joined #openstack-meeting-415:12
jasondotstarso trying to make a play for going native.... and there was one who jokingly spoke up and said 'oh so it's an excuse to play with the cool toys'15:12
jasondotstar:-)15:12
Ngmwaha15:12
jasondotstarPiet did mention that there are making use cases for mobile15:13
jasondotstarand *then* there are use cases for NATIVE iOS15:13
Ngnice15:13
jasondotstarthey were having trouble with the use cases for mobile in the past15:13
jasondotstarso it was suggested to do an operators survey15:14
jasondotstarwhere we put together something that asks them which actions would you take where15:14
*** brucet has quit IRC15:14
jasondotstarand have like a browser tablet phone matrix15:14
jasondotstaror something15:14
*** cdelatte has quit IRC15:15
Ngas in *we* do an operators survey? or is this something they are already working on that we can be part of?15:15
jasondotstargood qn.15:15
*** dandruta has joined #openstack-meeting-415:15
jasondotstarI was thinking he meant "we".15:15
jasondotstarat that point I asked our colleagues at HP about it15:15
jasondotstarand dhellmann spoke up and offered to do a warm intro to the user committee15:16
jasondotstarwho might help us set something up like this15:16
Ngwoot15:16
jasondotstarso if you want to continue working the UX angle15:17
jasondotstarwhile i work with dhellmann on getting somewhere with the survey15:17
* Ng nods15:17
jasondotstarthose could be a couple actions we take this week....15:17
jasondotstar#action Ng to continue chasing down support from the UX team15:18
jasondotstar#action jasondotstar to take up dhellmann on his offer to introduce him to the user committee in an effort to kickoff the op survey15:18
jasondotstarwe also talked about technology to support they survey, but to me that doesn't matter as much. CIVS or Google Forms15:19
jasondotstarwe'll find the right tool to support it15:19
jasondotstars/they/the15:19
*** akwasnie has joined #openstack-meeting-415:20
jasondotstarok so my other action item I'll have to roll fwd15:20
jasondotstarit was this one: to chat with -infra about public cloud API testing environment(s)15:21
jasondotstarI'll revisit that one this week15:21
jasondotstar#action jasondotstar to chat with -infra about public cloud API testing environment(s)15:21
jasondotstaralright the unassigned ones:15:21
*** zeih has quit IRC15:22
*** javeriak has quit IRC15:22
jasondotstarcome up with a list of short-term MVP goals15:22
jasondotstarwe *sorta* started this one15:22
jasondotstarbut I think we should add a couple more15:22
jasondotstarso far we've got:15:23
jasondotstarClass that authenticates with keystone and stores the resulting token15:23
jasondotstarand15:23
jasondotstarClass that bears basic Nova (Compute) functions15:23
jasondotstarthings like, listing compute resources15:24
NgI now have a ridiculously simplified class that can fetch a token from keystone15:24
jasondotstarNIIIIIIIIIICE15:24
*** vincentfrancoise has left #openstack-meeting-415:24
jasondotstar\o/15:24
Ngit needs a bunch of work to be anything close to production ready, but that work all requires us to start making infrastructure decisions15:25
* jasondotstar hears the brass ensemble playing a glorious fanfare15:25
Nglike logging, which variation of the observer pattern we're going to use, etc.15:25
jasondotstar+115:25
*** inteq has quit IRC15:25
jasondotstarthat brings me to our other unassigned task15:25
jasondotstargit repo15:25
jasondotstari didn't look into this one at all.....15:25
jasondotstarany thoughts here?15:26
jasondotstaras I stated before15:27
jasondotstarI jumped the gun a bit and created a couple15:27
jasondotstarbut with the concerted effort we should create a vahana git repo15:27
jasondotstarsomewhere.... esp now that we're making some progress developmentally15:27
Ngthe question is where15:28
jasondotstaryep15:28
jasondotstarbig question15:28
Nggithub is easy, infra would be better, but I'm not sure what happens if you want a git repo from infra without any testing15:28
jasondotstargithub?15:28
jasondotstaris it just a matter of asking -infra for it?15:28
NgI suspect it'll turn into a review adding it to infra's repos, but it's so long since I've done it, that I don't know :)15:29
jasondotstarok15:29
jasondotstarI'll take that one since I've already got to talk to them15:29
jasondotstar#action jasondotstar to chat with -infra about git repo hosting15:30
jasondotstarOK15:31
jasondotstaranything else on the action items?15:31
Ngnothing from me15:31
jasondotstarok15:31
jasondotstar#topic R&D15:32
*** openstack changes topic to "R&D (Meeting topic: vahana)"15:32
Ngso my R&D work was around getting the barest possible keystone authentication going, which I have done15:32
jasondotstaryou touched on what you've got working thus far15:32
jasondotstarawesome15:32
jasondotstarI'm behind on my R&D work15:33
jasondotstarbut I'd like to have a look at what you've got going15:33
NgI have a class that wraps AlamoFire, in case we need to change that, and an Identity class that at the moment just takes url/username/password as init parameters, and has a getToken()15:33
jasondotstarnice15:33
jasondotstarabout what I was going to try15:33
Nghttp://pastebin.com/Fz9vcbw7 is what I have in my playground right now15:33
* jasondotstar looks15:35
Ng(I arbitrarily picked "OSV" as the class prefix, for OpenStack Vahana :)15:35
jasondotstaryep15:35
jasondotstarjust peeped that15:35
jasondotstarOSVBase15:35
jasondotstarOSVRest, etc, etc.15:35
jasondotstarI like it.15:35
jasondotstarnice wrap15:36
jasondotstarall the funcs needed15:36
jasondotstarcool. I'll have to try this out with my devstack env15:37
jasondotstari honestly don't know much about keystone API15:38
Ngso I said just now that logging and observerpattern were the things I care about next. I just added OSVBase right after saying that and added the logging functions to it, so that is now abstracted and we can defer any decision about logging until later15:38
Ngbut the observer one is a really important decision15:38
jasondotstaris there much beyond grabbing the tokens and logging15:38
*** blahRus has joined #openstack-meeting-415:38
jasondotstar?15:38
*** blahRus has quit IRC15:38
Ngthat depends :)15:39
*** blahRus has joined #openstack-meeting-415:39
Ngthe keystone API has tons of stuff in it, and really it comes down to how a cloud/tenant is set up15:39
*** belmoreira has quit IRC15:39
jasondotstargotcha15:39
Nge.g. you can get a token that's restricted to specific things15:39
jasondotstarright15:39
Ngthe (very formal) API spec for keystone is http://developer.openstack.org/api-ref-identity-v3.html15:39
*** javeriak has joined #openstack-meeting-415:40
jasondotstardo we state up from this the amount of the keystone API that we're going to implement?15:40
jasondotstaror do we start small and work our way up?15:40
jasondotstars/from/front15:40
jasondotstars/this the/this is the/15:40
jasondotstartypos galore this morning15:41
* jasondotstar needs coffee15:41
Ngyeah I'm struggling with that one a bit. I worry that if we start dumb and try to get smarter, the architecture will be wrong. I also worry that if we try to start smart, we won't be understanding the problem space properly and will still get it wrong ;)15:41
jasondotstartrue stmt.15:41
NgI think the latter worry pretty much forces me to start dumb and try to get smarter15:42
jasondotstarthis is where the survey would help15:42
jasondotstarknowing what ppl might want to use mobile for15:42
Ngyeah, that will definitely help15:42
jasondotstarmight steer us in the direction of which portions of the API to expose15:42
jasondotstarmeanwhile, we can continue R&D15:43
jasondotstar(i guess)15:43
jasondotstarfiguring out what we can/can't should/shouldn't do15:43
Ngultimately though, the Identity class' main job is "here is some set of auth data and metadata, get me a token" and that should be reasonably possible to always entirely hide inside the class, so we can change/improve/expand it over time15:43
jasondotstaryep15:44
jasondotstaragreed15:44
*** dshakhray has quit IRC15:44
Ngand if people want it to be able to talk to the Policies part of keystone's API, that would just be more functions in OSVIdentity15:44
jasondotstar#agreed on the role of the Identity class in openstack-vahana. it's job is to fetch the API token15:45
jasondotstar+115:45
jasondotstars/it's/its15:45
* jasondotstar warms up the Keurig15:45
Nganother question is whether we should support older API versions15:46
jasondotstarhmmmmm15:46
jasondotstargood one15:46
NgI am somewhat tempted to avoid that decision by just renaming OSVIdentity to OSVIdentity315:47
Ngthen if people care for v2, it can be added15:47
jasondotstar+115:47
jasondotstar#agreed we should concern ourselves with API v3 and not worry about supporting older API versions atm15:48
jasondotstargood stuff.15:49
*** dshakhray has joined #openstack-meeting-415:49
jasondotstarok we're about 10 mins out15:49
jasondotstarany other R&D items?15:50
Ngobserver pattern, or as I rather suspect, pattern*s*15:50
Ngthis is a really tough one15:51
*** eric__ has quit IRC15:51
jasondotstarindeed15:51
*** eric__ has joined #openstack-meeting-415:51
Ngdelegates are 1:1, KVO isn't really native to swift, and NSNotificationCenter is awfully blunt15:51
*** igordcard has joined #openstack-meeting-415:52
NgI'm currently looking at https://github.com/slazyk/Observable-Swift15:52
jasondotstarhttps://developer.apple.com/library/mac/documentation/Swift/Conceptual/BuildingCocoaApps/AdoptingCocoaDesignPatterns.html#//apple_ref/doc/uid/TP40014216-CH7-XID_815:53
jasondotstarthere's some KVO stuff there15:53
jasondotstarbut I haven't read through it all15:53
*** igordcard__ has quit IRC15:53
jasondotstar#action evaluate how we are to implement Observer pattern(s)15:54
Ngso the KVO you can do with Swift is actually using the objc runtime and only works for classes that derive from NSObject (which, for no especially good reason, all of mine currently do)15:54
jasondotstaryep that's what i saw15:54
jasondotstarsubclassing NSObject should work15:55
jasondotstar#topic Open Discussion15:55
*** openstack changes topic to "Open Discussion (Meeting topic: vahana)"15:55
*** sdake has joined #openstack-meeting-415:55
jasondotstarlast five minutes15:55
NgI don't think I have anything else for this week :)15:56
jasondotstarnope, I didn't think we'd take up the whole hour15:56
jasondotstarbut good discussion15:56
Ng:)15:56
*** irenab has joined #openstack-meeting-415:56
jasondotstarI'm tapped out. :-)15:56
jasondotstarwell, thx again. until next week15:56
*** inc0 has joined #openstack-meeting-415:56
Ngthanks :)15:56
jasondotstarNg++15:56
jasondotstar#endmeeting15:56
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"15:56
openstackMeeting ended Wed Dec  9 15:56:55 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-09-15.01.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-09-15.01.txt15:57
openstackLog:            http://eavesdrop.openstack.org/meetings/vahana/2015/vahana.2015-12-09-15.01.log.html15:57
*** Ng has left #openstack-meeting-415:57
*** dronshaw has left #openstack-meeting-415:58
*** jose-falavinha has joined #openstack-meeting-416:00
*** gabor_antal has left #openstack-meeting-416:03
*** vishwanathj has quit IRC16:08
*** nkrinner has quit IRC16:08
*** vishwanathj has joined #openstack-meeting-416:08
*** wojdev has quit IRC16:09
*** vtech has quit IRC16:09
*** vtech has joined #openstack-meeting-416:10
*** wojdev has joined #openstack-meeting-416:10
*** sdake has quit IRC16:10
*** brucet has joined #openstack-meeting-416:15
*** ajmiller has joined #openstack-meeting-416:19
*** Swami has quit IRC16:23
*** bharathm has joined #openstack-meeting-416:24
*** numans has quit IRC16:26
*** javeriak has quit IRC16:27
*** akwasnie1 has joined #openstack-meeting-416:30
*** rhallisey has joined #openstack-meeting-416:30
*** akwasnie has quit IRC16:30
*** akwasnie1 has quit IRC16:31
*** akwasnie has joined #openstack-meeting-416:31
rhallisey#startmeeting kolla16:31
openstackMeeting started Wed Dec  9 16:31:58 2015 UTC and is due to finish in 60 minutes.  The chair is rhallisey. Information about MeetBot at http://wiki.debian.org/MeetBot.16:31
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:32
*** openstack changes topic to " (Meeting topic: kolla)"16:32
openstackThe meeting name has been set to 'kolla'16:32
rhallisey#topic rollcall16:32
*** mitchjameson has joined #openstack-meeting-416:32
*** openstack changes topic to "rollcall (Meeting topic: kolla)"16:32
*** javeriak has joined #openstack-meeting-416:32
rhalliseyhello16:32
akwasniehi16:32
pbourkehere16:32
nihiliferhi16:32
britthousero/16:32
rhalliseyinc0, around?16:32
* jpeeler is here16:32
rhalliseyjpeeler, oh hai!16:32
kproskurinhi16:33
inc0yeah16:33
rhallisey#topic Announcements16:33
*** openstack changes topic to "Announcements (Meeting topic: kolla)"16:33
rhalliseyI don't really any announcements, I figured this meeting will be focused on upgrades16:34
inc0yay16:34
rhalliseyI know we need to tag M-1 soon16:34
rhalliseylike yesterday ).016:34
rhalliseyO.o16:35
nihiliferlike 4 Dec?16:35
rhallisey#topic Upgrade playbook16:35
*** openstack changes topic to "Upgrade playbook (Meeting topic: kolla)"16:35
rhalliseyinc0, you added this, why don't you lead the discussion16:35
rhallisey:)16:35
rhallisey#link https://review.openstack.org/#/c/254395/16:36
inc0ok, so https://review.openstack.org/#/c/254395/16:36
inc0I started to make playbook for upgrades16:36
*** bpokorny has joined #openstack-meeting-416:37
inc0I took slightly different approach than we agreed on summit16:37
*** sean-k-mooney has joined #openstack-meeting-416:37
inc0it seems it makes more sense to break stuff per project16:37
inc0every project is different and procedure will be different16:38
britthouserThat seems to match what we had drawn on the whiteboard?16:38
inc0so to get any upgrades asap, I'll just ask community per project and do what they tell me to do16:38
inc0well  we won't have "kolla version" this way16:39
inc0it will be nova version and keystone version16:39
pbourkemy only concern is how will that fit in with current ops expectations16:39
pbourkeas most do not do rolling upgrades16:39
pbourkethey will want to go from kolla x to kolla y16:40
*** akwasnie has quit IRC16:40
britthouserSo the "kolla version" will just be a conglomerate of each project's versions?  that's kinda how I understood things were going to work in Tokyo16:40
inc0yeah, and it might be snowflake16:40
inc0I'm ok with ks liberty and rest mitaka, thats ok16:40
*** wojdev has quit IRC16:41
rhalliseyinc0, I got a question since I missed this meeting.  This would be upgrade from liberty to M16:42
pbourkewill other distrubutions such as rdo be moving to this mechanism I wonder?16:42
inc0kolla version will be just version of code you have, not version of deployed stuff16:42
inc0yeah, this will be L->M16:42
inc0or rather L->master16:42
inc0at any point16:42
inc0until we tag16:42
britthouserMaybe I'm missing the obvious, but this sounds like what we discussed in Tokyo.  At the point we tag, then that is when the "version" of kolla is defined.  and it will just be the sum of the versions of each project at that point in time?16:44
nihiliferi'm not aware what exactly you agreed about in tokio and how's your current idea different16:44
nihiliferbut the current idea makes sense IMO16:45
*** javeriak_ has joined #openstack-meeting-416:45
rhallisey#link https://etherpad.openstack.org/p/kolla-mitaka-upgrade16:46
rhalliseywe can take a minute to read here16:47
*** javeriak has quit IRC16:48
pbourkei think the key difference is the etherpad was to provide a monolithic playbook to move between atomic versions of kolla16:49
*** ajafo has joined #openstack-meeting-416:49
pbourkea "version" of kolla would be comprised of multiple versions of it's components16:50
rhallisey'    - Most likely will supply a playbook or script (last resort) for each upgrade'16:50
pbourkebut there would be no option to move indiviviual ones forward16:50
pbourkedoes that make sense based on what others remember?16:51
britthouserMaybe this is just micro/macro viewpoint.  Micro: each project will have its own playbook.  I remmeber we sketched this out on the white board.16:51
rhalliseyso in inc0's case can one upgrade just nova?16:51
inc0yeah16:51
rhalliseyok I like that16:51
britthousermacro: a set of playbooks tied together and tagged ?16:51
rhalliseyinc0, I like it, but we will need to doc our recommendation. Did you guys talk about the case someone upgrade only one service16:52
britthouseri.e. the two methods don't exclude each other.  One just makes up the other?16:52
rhalliseyand just leaves it that way16:52
rhalliseybritthouser, I think so16:53
rhalliseythat's the way I understand it at least16:53
*** paul-carlton2 has joined #openstack-meeting-416:53
*** javeriak_ has quit IRC16:53
*** javeriak has joined #openstack-meeting-416:54
britthouserok cool. Me too.16:54
britthouser@inc0 does that jive with your understanding too?16:54
rhalliseysince we have the ability to do a rolling update is there any concern for say running a mitaka nova and a liberty glance16:54
inc0yeah, so if you look at patchset16:54
inc0there is upgrade.yml master playbook16:54
*** srwilkers has quit IRC16:54
inc0this will call one upgrade after anothert16:54
*** sridhar_ram has joined #openstack-meeting-416:54
inc0but you can to -t nova to upgrade just nova16:55
jokke_rhallisey: that specific combo will hopefully have a problem :P16:55
rhalliseyjokke_, not necessary, I've done it16:56
*** pbourke has quit IRC16:56
*** sdake has joined #openstack-meeting-416:56
rhalliseyI did it wil kilo & liberty16:56
inc0hey sdake we're talking about upgrades so you might be interested16:56
jokke_rhallisey: we are currently working to get mitaka Nova consuming v2 Images API and we are doing some changes in Glance side to facilitate that16:56
*** pbourke has joined #openstack-meeting-416:56
*** prashantD has joined #openstack-meeting-416:56
*** javeriak_ has joined #openstack-meeting-416:56
britthouserto rhallisey' point, I could see operators wanting to pick and choose specific versions of each project.16:56
jokke_rhallisey: so as said we're hopefully in a state where we get that work done this cycle and it might have a problem16:57
inc0well jokke_ in this case upgrade of glance is straightforward enough to be done before you upgrade nova16:57
britthouserbut I think that's a diffrent discussion.  if the upgrades for each project are tehre, then that functionatliy could happen down the road.16:57
rhalliseyjokke_, I mean it may not work now, but that would be cool to have.  In the past it worked for me16:57
jokke_inc0: and that way it should work perfectly fine16:57
inc0I expect most of people will try to upgrade whole thing anyway16:57
*** Swami has joined #openstack-meeting-416:57
inc0this approach would let them do that in steps16:57
inc0which in my mind is valuable ability16:57
rhalliseyinc0, I expect there to be a decent amount of people who do a by service upgrade16:58
britthouseragreed inc016:58
inc0today glance, tomorrow  nova16:58
rhalliseyand keep some around that they don't want to touch16:58
rhallisey'mix and match'16:58
inc0upgrade glance -> validate if it's ok and only after that you do next step16:58
jokke_my point was to bring that up because I think these things might happen between project so you might not be able to count that every variation of upgrade order will work16:58
inc0and you can stop anywhere you want16:58
rhalliseyyou can do it properly if it's documented correctly16:58
*** javeriak has quit IRC16:58
rhalliseyjokke_, for sure. I've tried XD16:58
rhalliseyjokke_, some do though16:58
inc0jokke_, we'll need to carefuly create upgrade guide16:59
inc0and do order well16:59
inc0but that's part of this task anyway16:59
rhalliseyinc0, the docs for ordering/mix&match would need to be spot on16:59
inc0yup16:59
rhalliseyand they may not work from M->N16:59
rhalliseyyou never know16:59
inc0I intend to do lots of experiments with this, and I'd appreciate help16:59
rhalliseyso it's a tricky subject16:59
inc0as I'll probably focus on ubuntu16:59
inc0so our playbook might change each release17:00
rhalliseyinc0, I did a bunch of research in the past around this.  I'll try and help it along17:00
rhalliseyinc0, correct, the playbook and docs would change based on the intended upgrade17:00
inc0but general idea is it should always upgrade from last stable to current master17:00
inc0best case scenerio - doc will just need to explain what ansible-playbook upgrade.yml does17:01
inc0and all you need to do is to call this master playbook and it works17:01
inc0that would be my goal17:01
*** seanmurphy has quit IRC17:02
inc0and upgrade.yml always upgrades stable->master17:02
rhalliseycool17:02
inc0therefore when we tag out Mitaka it will upgrade liberty->mitaka17:02
britthouserSo each time a new stable is cut, the playbooks would be rewritten? or appended?17:02
inc0and change to be mitaka->master17:02
rhalliseybritthouser, Appended17:02
inc0so I don't expect upgrade procedure will be different per release really17:02
inc0there might be some differences, but we'll work on those case by case17:03
nihiliferbut if it will?17:03
inc0nova upgrade procedure hasn't changed since I17:03
nihiliferthen i'm +1 for idea od appendinf17:03
nihiliferappending*17:03
inc0we will adjust plays accordingly17:03
inc0maybe append, maybe not17:03
inc0there might be steps that needs to be deleted17:03
inc0or replaced17:03
rhalliseyfor sure17:04
inc0all I'm saying is these plays should always upgrade stable->master17:04
inc0and we need to keep working on these forever and ever17:04
inc0later on we should gate on this17:04
pbourkeit sounds good :)17:04
britthouserSo lets say I"m running liberty, in two years I decide to upgrade to N release.17:04
rhalliseybritthouser, O.o17:04
inc0britthouser, then you download mitaka17:04
britthouserwill the playbooks to upgrade L->M still be around?17:04
inc0upgrae to mitaka17:05
rhalliseyhehe17:05
inc0then you download N and upgrade to N17:05
inc0as long as code will be17:05
britthouserok...yeah that's what I'm getting at.  Will the N versions have the playbooks for L->M?17:05
rhalliseybritthouser, so I was thinking we have a playbook set per release17:05
britthousersounds like no?17:05
*** bharathm has quit IRC17:05
rhalliseymajor release17:05
inc0britthouser, no, they will not17:05
inc0you'll need to do step by step17:05
britthouserOk yeah that would be a pain to maintain.17:05
inc0but plays will be available on git17:05
britthouserright17:05
nihiliferso they will be in stable branches, right?17:05
rhalliseyyes17:06
nihiliferok, makes sense17:06
inc0so you can do that, it will be harder, but well...your fault really17:06
inc0so, my approach has one other advantage17:06
inc0if any of you want to pick a project and write upgrade play for it, I'll appreciate help;)17:06
rhalliseyinc0, are their BP's for each service?17:07
inc0we can do this in pararell and more project will get upgrade coverage17:07
britthouserSo we're basically telling operators not to get more than one release behind, or they'll upgrades will require multi-steps17:07
rhalliseydoesn't look like it17:07
pbourkedo work items17:07
inc0rhallisey, I made one for nova17:07
rhalliseyok I'll make BPs for the rest of the services17:07
*** jose-falavinha has quit IRC17:07
inc0work items also work, but each play will be big enough for a bp I think17:08
inc0and might require discussion on itself as projects differ and upgrade procedures differ17:08
rhalliseyI'd rather do BP's so we can track who has each one17:08
*** acabot has quit IRC17:08
inc0yeah, agree rhallisey17:09
rhalliseyok thanks inc0.  Any more points of emphasis on the topic of upgrades?17:09
*** akwasnie has joined #openstack-meeting-417:09
inc0if you agree with this approach, then let's just get to work I guess:)17:09
rhalliseyI like it17:10
rhallisey#topic kolla-mesos17:10
*** openstack changes topic to "kolla-mesos (Meeting topic: kolla)"17:10
rhalliseyJust wanted to give them a shotout17:10
rhalliseyand remind the cores that if you are interested in reviewing that work17:10
rhalliseybe sure to filter for it17:10
rhalliseybecause I noticed they were 1 core short on like 10 patches17:10
rhalliseyso if you are looking to do some reviews add kolla-mesos to your watchlist17:11
rhallisey#topic Open Discussion17:11
*** openstack changes topic to "Open Discussion (Meeting topic: kolla)"17:11
rhalliseywho's got some cool stuff they want to talk about?17:11
*** acabot has joined #openstack-meeting-417:12
britthouserI missed last week's meeting, but was there an update on mid-cycle?17:12
inc0britthouser, nope17:12
britthouserOk. =)17:12
nihiliferlast week freenode had splitbrain17:12
rhalliseysdake, ^ anything?17:12
rhalliseyI have something if I may17:12
rhalliseyhttps://blueprints.launchpad.net/kolla/+spec/kolla-kubernetes17:12
rhalliseyI saw kube now support the stuff we need to use it17:13
sdakeroot canal - on pto17:13
inc0no net=host in k8s right?17:13
rhalliseyfigured i'd just throw that out there17:13
*** jwarendt has joined #openstack-meeting-417:13
rhalliseyinc0, no it is17:13
nihiliferrhallisey: nice17:13
nihiliferbut one question17:13
nihiliferwhat about bootstrap tasks?17:13
nihiliferdoes k8s support them?17:13
rhalliseynet=host pid=host and --privileged are in v1.117:13
nihiliferthat's what we use chronos for in kolla-mesos17:13
rhalliseynihilifer, good question.  I'll get back to you on that17:13
inc0well, whoever would take on k8s will need to figure this out17:14
jpeelerrhallisey: glad you asked about those caps17:14
sdakeno bbootstrp tasks17:14
nihiliferrhallisey: i ask, because from what i know, it doesn't17:14
nihiliferbut my idea17:14
inc0we can do mixture ansible->k8s17:14
nihiliferis to use k8s as mesos framework then17:14
nihiliferso opposite mixture that inc0 proposes ;)17:14
sdakecomonguys lets just stick to what we have on our plates17:14
sdakewhih is massive17:14
sdakewe don't need to invent more work for no good reason17:14
rhalliseyI'm not saying this is happening or anything but that I"m just looking at it17:15
inc0yeah, upgrades will take lot of work17:15
rhallisey+1 focus on upgrades17:15
inc0let's wait for someone who needs k8s;)17:15
nihilifer+1 for postponing k8s17:15
nihiliferbut i;m just saying17:15
inc0if someone needs it, we'll help17:15
rhalliseyit's just show and tell :D17:15
nihiliferthat we may use it as mesos framweork along with chronos17:15
rhalliseynihilifer, kk noted17:16
inc0yeah once we have mesos there might be little value added by k8s...17:16
rhalliseyinc0, unless someone wanted to make it. I'm not opposed to that17:16
nihiliferk8s would be de facto alternative for marathon17:17
inc0yup, it's possible and it's job for the taking;)17:17
inc0we could do kolla-on-magnum17:17
inc0like tripleo but more;)17:17
rhalliseyO.O17:17
inc0kom17:17
nihiliferlol17:17
britthouserOCOO17:18
*** ajmiller_ has joined #openstack-meeting-417:18
inc0koalla with a magnum gun would be logo17:18
rhalliseyok well I think we're all set guys thanks for coming!17:18
britthouserthx!17:18
rhallisey#endmeeting kolla17:18
inc0yup, thanks for input on upgrades17:18
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"17:18
openstackMeeting ended Wed Dec  9 17:18:45 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:18
nihiliferthx17:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-09-16.31.html17:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-09-16.31.txt17:18
openstackLog:            http://eavesdrop.openstack.org/meetings/kolla/2015/kolla.2015-12-09-16.31.log.html17:18
*** akwasnie has left #openstack-meeting-417:18
*** rhallisey has left #openstack-meeting-417:19
*** ajmiller has quit IRC17:21
*** iyamahat has joined #openstack-meeting-417:23
*** barrett has joined #openstack-meeting-417:23
*** barrett has left #openstack-meeting-417:24
*** dims has quit IRC17:24
*** barrett has joined #openstack-meeting-417:25
*** sean-k-mooney has left #openstack-meeting-417:25
*** degorenko is now known as _degorenko|afk17:27
*** vtech_ has joined #openstack-meeting-417:28
*** vtech has quit IRC17:28
*** vtech_ has quit IRC17:30
*** salv-orlando has quit IRC17:30
*** igordcard has quit IRC17:33
*** armax_ has joined #openstack-meeting-417:38
*** matrohon has quit IRC17:39
*** javeriak_ has quit IRC17:40
*** javeriak_ has joined #openstack-meeting-417:40
*** kebray has joined #openstack-meeting-417:41
*** bharathm has joined #openstack-meeting-417:46
*** kproskurin has quit IRC17:49
*** salv-orlando has joined #openstack-meeting-417:49
*** salv-orlando has quit IRC17:52
*** jwarendt has quit IRC17:53
*** Prithiv has quit IRC17:56
*** numans has joined #openstack-meeting-417:56
*** vtech has joined #openstack-meeting-417:59
*** yamamoto has quit IRC18:05
*** sdake has quit IRC18:08
*** dandruta has quit IRC18:14
*** markvoelker has quit IRC18:18
*** sambetts is now known as sambetts-afk18:18
*** kebray has quit IRC18:19
*** markvoelker has joined #openstack-meeting-418:21
*** yamamoto has joined #openstack-meeting-418:22
*** brucet has quit IRC18:22
*** yamamoto has quit IRC18:23
*** mitchjameson has quit IRC18:25
*** javeriak has joined #openstack-meeting-418:26
*** javeriak_ has quit IRC18:30
*** trozet has quit IRC18:30
*** paul-carlton2 has quit IRC18:33
*** [1]evgenyf has quit IRC18:34
*** EvgenyF has quit IRC18:34
*** Swami has quit IRC18:35
*** Swami has joined #openstack-meeting-418:35
*** seanmurphy has joined #openstack-meeting-418:40
*** sridhar_ram has quit IRC18:42
*** neelashah has quit IRC18:42
*** sdake has joined #openstack-meeting-418:43
*** nishi has joined #openstack-meeting-418:50
*** dshakhray has quit IRC18:56
*** yamamoto has joined #openstack-meeting-419:00
*** brucet has joined #openstack-meeting-419:00
*** david-ly_ has joined #openstack-meeting-419:00
*** Bjoern_ has joined #openstack-meeting-419:02
*** bobh has quit IRC19:02
*** yamamoto has quit IRC19:02
*** bpokorny_ has joined #openstack-meeting-419:02
*** david-ly_ is now known as david-lyle_19:03
*** david-lyle has quit IRC19:03
*** bpokorny_ has quit IRC19:03
*** neelashah has joined #openstack-meeting-419:04
*** fawadkhaliq has quit IRC19:04
*** bpokorny_ has joined #openstack-meeting-419:04
*** david-lyle_ is now known as david-lyle19:04
*** salv-orlando has joined #openstack-meeting-419:05
*** Swami has quit IRC19:06
*** Swami has joined #openstack-meeting-419:06
*** bpokorny has quit IRC19:06
*** mbound_ has joined #openstack-meeting-419:09
*** bpokorny_ has quit IRC19:11
*** sridhar_ram has joined #openstack-meeting-419:12
*** bpokorny has joined #openstack-meeting-419:12
*** bobh has joined #openstack-meeting-419:14
*** bpokorny_ has joined #openstack-meeting-419:14
*** bpokorny has quit IRC19:17
*** wojdev has joined #openstack-meeting-419:21
*** devananda has quit IRC19:22
*** javeriak_ has joined #openstack-meeting-419:30
*** javeriak_ has quit IRC19:32
*** armax_ is now known as armax19:32
*** javeriak has quit IRC19:33
*** devananda has joined #openstack-meeting-419:34
*** salv-orlando has quit IRC19:36
*** iyamahat has quit IRC19:39
*** numans has quit IRC19:39
*** brucet has quit IRC19:46
*** briancurtin has quit IRC19:46
*** briancurtin has joined #openstack-meeting-419:46
*** seanmurphy_ has joined #openstack-meeting-419:48
*** bpokorny_ has quit IRC19:51
*** seanmurphy has quit IRC19:51
*** seanmurphy_ is now known as seanmurphy19:51
*** kevinbenton has quit IRC19:54
*** baoli_ has quit IRC19:54
*** u_kozat has joined #openstack-meeting-419:55
*** vtech has quit IRC19:57
*** dtardivel has quit IRC19:57
*** david-lyle has quit IRC19:58
*** david-lyle has joined #openstack-meeting-419:58
*** bpokorny has joined #openstack-meeting-420:00
jokke_hi, anyone here for Log WG meeting?20:00
*** Bjoern_ has left #openstack-meeting-420:02
*** neelashah has quit IRC20:03
*** sridhar_ram has quit IRC20:04
jokke_#startmeeting log wg20:05
openstackMeeting started Wed Dec  9 20:05:34 2015 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.20:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:05
*** openstack changes topic to " (Meeting topic: log wg)"20:05
openstackThe meeting name has been set to 'log_wg'20:05
jokke_#info meeting cancelled due to the lack of participation20:06
jokke_#endmeeting20:06
*** openstack changes topic to "Q&A (Meeting topic: openstack-vahana)"20:06
openstackMeeting ended Wed Dec  9 20:06:09 2015 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:06
openstackMinutes:        http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-12-09-20.05.html20:06
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-12-09-20.05.txt20:06
openstackLog:            http://eavesdrop.openstack.org/meetings/log_wg/2015/log_wg.2015-12-09-20.05.log.html20:06
*** salv-orlando has joined #openstack-meeting-420:10
*** iyamahat has joined #openstack-meeting-420:12
*** kevinbenton_ has joined #openstack-meeting-420:13
*** kevinbenton_ has quit IRC20:14
*** kevinbenton has joined #openstack-meeting-420:14
*** wojdev has quit IRC20:19
*** armax has quit IRC20:25
*** sridhar_ram has joined #openstack-meeting-420:34
*** neelashah has joined #openstack-meeting-420:37
*** belmoreira has joined #openstack-meeting-420:41
*** kebray has joined #openstack-meeting-420:43
*** mbound_ has quit IRC20:47
*** dims has joined #openstack-meeting-420:49
*** vtech has joined #openstack-meeting-420:51
*** baoli has joined #openstack-meeting-420:54
*** kebray has quit IRC20:55
*** krtaylor has quit IRC20:56
*** nishi has quit IRC20:57
*** bpokorny has quit IRC20:58
*** dims has quit IRC20:58
*** dims has joined #openstack-meeting-421:00
*** dims has quit IRC21:01
*** u_kozat has quit IRC21:04
*** baoli has quit IRC21:05
*** baoli has joined #openstack-meeting-421:06
*** seanmurphy has quit IRC21:09
*** seanmurphy has joined #openstack-meeting-421:10
*** meteorfox has quit IRC21:13
*** dshakhray has joined #openstack-meeting-421:13
*** meteorfox has joined #openstack-meeting-421:14
*** neelashah has quit IRC21:15
*** baoli has quit IRC21:17
*** baoli has joined #openstack-meeting-421:17
*** belmoreira has quit IRC21:26
*** neelashah has joined #openstack-meeting-421:27
*** baoli has quit IRC21:29
*** baoli has joined #openstack-meeting-421:30
*** armax has joined #openstack-meeting-421:35
*** neelashah1 has joined #openstack-meeting-421:38
*** neelashah has quit IRC21:38
*** baoli has quit IRC21:41
*** baoli has joined #openstack-meeting-421:42
*** seanmurphy has quit IRC21:46
*** baoli has quit IRC21:47
*** baoli has joined #openstack-meeting-421:48
*** jmckind has quit IRC21:51
*** sridhar_ram has quit IRC21:56
*** barrett has left #openstack-meeting-421:57
*** baoli has quit IRC21:59
*** baoli has joined #openstack-meeting-422:00
*** u_kozat has joined #openstack-meeting-422:02
*** jmckind has joined #openstack-meeting-422:03
*** inc0 has quit IRC22:04
*** sridhar_ram has joined #openstack-meeting-422:06
*** u_kozat has quit IRC22:06
*** baoli has quit IRC22:08
*** neelashah1 has quit IRC22:08
*** baoli has joined #openstack-meeting-422:08
*** baoli has quit IRC22:12
*** neelashah has joined #openstack-meeting-422:13
*** rbak has quit IRC22:15
*** baoli has joined #openstack-meeting-422:16
*** wojdev has joined #openstack-meeting-422:19
*** baoli has quit IRC22:23
*** baoli has joined #openstack-meeting-422:24
*** neelashah has quit IRC22:25
*** david-lyle has quit IRC22:34
*** baoli has quit IRC22:35
*** baoli has joined #openstack-meeting-422:36
*** meteorfox has quit IRC22:36
*** aglarendil has quit IRC22:36
*** iyamahat has quit IRC22:38
*** briancurtin has quit IRC22:38
*** s3wong has joined #openstack-meeting-422:39
*** david-ly_ has joined #openstack-meeting-422:39
*** patrickeast has quit IRC22:40
*** ashtokolov has quit IRC22:41
*** david-ly_ is now known as david-lyle22:45
*** jmckind has quit IRC22:47
*** baoli has quit IRC22:47
*** baoli has joined #openstack-meeting-422:48
*** sdake has quit IRC22:52
*** baoli has quit IRC22:59
*** baoli has joined #openstack-meeting-422:59
*** banix has quit IRC23:04
*** klamath has quit IRC23:08
*** baoli has quit IRC23:09
*** baoli_ has joined #openstack-meeting-423:10
*** blahRus has quit IRC23:12
*** baoli_ has quit IRC23:19
*** rbak has joined #openstack-meeting-423:19
*** wojdev has quit IRC23:23
*** baoli has joined #openstack-meeting-423:25
*** briancurtin has joined #openstack-meeting-423:28
*** u_kozat has joined #openstack-meeting-423:31
*** MarkAtwood has joined #openstack-meeting-423:32
*** meteorfox has joined #openstack-meeting-423:33
*** baoli has quit IRC23:35
*** baoli has joined #openstack-meeting-423:36
*** vtech has quit IRC23:37
*** aglarendil has joined #openstack-meeting-423:47
*** ashtokolov has joined #openstack-meeting-423:47
*** sigmavirus24 is now known as sigmavirus24_awa23:48
*** klamath has joined #openstack-meeting-423:48
*** kebray has joined #openstack-meeting-423:49
*** baoli has quit IRC23:50
*** patrickeast has joined #openstack-meeting-423:51
*** kebray has quit IRC23:51

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