15:01:25 <DinaBelova> #startmeeting climate
15:01:26 <openstack> Meeting started Fri Jan 24 15:01:25 2014 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:01:27 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:01:29 <openstack> The meeting name has been set to 'climate'
15:01:32 <DinaBelova> o/
15:01:40 <DinaBelova> hello everyone :)
15:01:44 <DinaBelova> who's here?
15:02:04 <DinaBelova> bauzas, joel_c f_rossigneux, scroiset?
15:02:12 <bauzas> o/
15:02:22 <bauzas> scroiset is off today
15:02:29 <bauzas> and f_rossigneux too
15:02:41 <DinaBelova> when I've got days off I always go to meetings :D
15:02:43 <bauzas> feelink like a lone soul :)
15:02:53 <DinaBelova> ok, Nick is afk now I see
15:03:01 <DinaBelova> we'll be alone today :D
15:03:36 <DinaBelova> joel_c, you here?
15:03:41 <JoelC> yes
15:03:44 <JoelC> hi
15:03:46 <DinaBelova> wow :)
15:03:52 <bauzas> we're not alone in the dark \o/
15:04:04 <DinaBelova> ok, let's start
15:04:13 <DinaBelova> our agenda is https://wiki.openstack.org/wiki/Meetings/Climate
15:04:30 <DinaBelova> #topic Action items from the last meeting + reviews queries
15:04:41 <DinaBelova> #link http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-01-17-15.00.html
15:04:51 <DinaBelova> last meeting ended with 3 action items
15:05:08 <bauzas> yup
15:05:17 <DinaBelova> I suppose I almost close to oslo.messaging
15:05:28 <bauzas> yep agreed
15:05:30 <DinaBelova> cause soon change helping me with that will be merged
15:05:43 <DinaBelova> and after that we may add it to 0.1.1
15:06:07 <DinaBelova> bauzas, what's with your action items?
15:06:19 <bauzas> well, I got the incubation checklist item
15:06:28 <bauzas> https://review.openstack.org/#/c/59454/2/reference/incubation-integration-requirements
15:06:35 <DinaBelova> thx
15:07:10 <DinaBelova> ok, as for current code status
15:07:22 <bauzas> for the second action : https://bugs.launchpad.net/climate/+bug/1272371
15:07:27 <bauzas> (just created it)
15:07:33 <DinaBelova> I understood that :)
15:07:36 <DinaBelova> ok
15:07:49 <DinaBelova> we have two important changes to be merged
15:07:57 <DinaBelova> that are stoppers for 0.1 now
15:07:57 <Nikolay_St> I'm here
15:08:04 <DinaBelova> Nikolay_St, o/
15:08:13 <DinaBelova> 1/ VM plugin
15:08:18 <DinaBelova> 2/ Nova API extensions
15:08:26 <bauzas> 1/ is still under test
15:08:34 <bauzas> and still bugging
15:08:51 <bauzas> about unshelve action which is not part of v1_1 novaclient
15:09:02 <DinaBelova> bauzas, although last your trace seems to be quite strange to me
15:09:15 <bauzas> ok, let's discuss that off this meeting
15:09:33 <bauzas> 2/ will test it once 1/ is validated :D
15:09:46 <DinaBelova> bauzas, I see problem here
15:09:46 <bauzas> running out of people now for helping me
15:09:54 <DinaBelova> unshelving seems to be supported
15:09:58 <DinaBelova> in current master
15:10:07 <DinaBelova> but not for tag 2.15.0
15:10:15 <bauzas> exactly
15:10:43 <bauzas> I don't want to discuss about resolution, but how can it have been working before ?
15:10:50 <DinaBelova> that's for master https://github.com/openstack/python-novaclient/blob/master/novaclient/v1_1/servers.py#L625
15:10:52 <Nikolay_St> simple.
15:11:00 <Nikolay_St> we use devstack
15:11:16 <Nikolay_St> and it uses latest master branch
15:11:16 <DinaBelova> I suppose that's because Nick had lab with master branch
15:11:31 <DinaBelova> problem here is that we NEED this change
15:11:36 <bauzas> although I'm testing climate on a venv
15:12:04 <bauzas> DinaBelova: +1
15:12:08 <bauzas> that's a huge issue
15:12:16 <bauzas> we can't use the client
15:12:25 <bauzas> for unshelving
15:12:36 <bauzas> or at lease until it's released
15:13:04 <DinaBelova> bauzas, but using some direct requests to Nova also seems bad to me
15:13:46 <DinaBelova> http://pypi.openstack.org/openstack/python-novaclient/
15:13:53 <DinaBelova> 2.15.0 is really old
15:14:08 <Nikolay_St> yeap, another time
15:14:10 <bauzas> DinaBelova: yep
15:14:33 <Nikolay_St> DinaBelova: may be it'll be better to push a letter to the mailing list?
15:14:40 <DinaBelova> I suppose, Nick, you may try to ask Nova guys about the same you did for keystoneclient
15:14:41 <DinaBelova> yep
15:14:46 <DinaBelova> Nikolay_St, exactly
15:14:57 <bauzas> that's something we need to prevent for the next times
15:14:58 <DinaBelova> because Sep 2013 seems to be really weird for me
15:15:12 <bauzas> hold on
15:15:17 <Nikolay_St> ?
15:15:22 <bauzas> I can shelve/unshelve with the client
15:15:27 <DinaBelova> 0_0
15:15:34 <bauzas> by the shell I mean
15:15:41 <DinaBelova> em
15:15:45 <DinaBelova> how?
15:15:50 <bauzas> lemme check
15:15:50 <Nikolay_St> wow
15:16:07 <DinaBelova> ok, let's spend a minute
15:16:35 <bauzas> but still, we need to make sure we don't test against master ;)
15:16:48 <bauzas> for the reqs I mean
15:16:55 <DinaBelova> I got it
15:17:15 <DinaBelova> still
15:17:27 <DinaBelova> Nick, will you write letter to ML anyway?
15:17:37 <Nikolay_St> yeap
15:17:39 <DinaBelova> #action Nikolay_St write to ML about novaclient
15:18:36 <DinaBelova> ok, shall we move to next topic?
15:18:58 <DinaBelova> #topic Current status for the Climate 0.1.0 (testing, possible release postponing till Jan 27)
15:19:11 <DinaBelova> we now have problems to solve
15:19:46 <DinaBelova> but I believe we have good chances on having release Jan 27 (evening CET)
15:19:49 <DinaBelova> smth like that
15:20:26 <DinaBelova> when we'll fix VM plugin and test it - we're almost there
15:20:40 <DinaBelova> bauzas, Nikolay_St, any objections?
15:20:50 <bauzas> +1
15:20:51 <Nikolay_St> no, I don't think so
15:20:56 <DinaBelova> ok
15:20:57 <DinaBelova> great
15:21:09 <DinaBelova> so now we'll have two really interesting topics :)
15:21:18 <DinaBelova> #topic Future plans for 0.1.1 (bug fixing, small features, etc.)
15:21:51 <DinaBelova> for now I already see something we decided to scope fro 0.1.1
15:21:57 <DinaBelova> #link https://launchpad.net/climate/+milestone/0.1.1
15:22:27 <DinaBelova> Also I should move to that BP list writing documentation for climate
15:22:30 <DinaBelova> moment
15:22:42 <bauzas> agree
15:23:08 <DinaBelova> #link https://blueprints.launchpad.net/climate/+spec/wiki-pages
15:23:11 <DinaBelova> here it is
15:23:50 <DinaBelova> I suppose if we'll have noncritical bugs/whatever found while 0.1 testing
15:23:58 <DinaBelova> we'll also scope them for 0.1
15:24:21 <DinaBelova> I think that's not so interesting
15:24:37 <DinaBelova> the most nice topic for today is the next one
15:24:48 <Nikolay_St> for 0.1.1, yeah?
15:24:48 <bauzas> sure
15:25:06 <DinaBelova> ok. i'll move on it
15:25:11 <DinaBelova> #topic Future plans for 0.2 (https://etherpad.openstack.org/p/climate-0.2)
15:25:20 <DinaBelova> #link https://etherpad.openstack.org/p/climate-0.2
15:25:38 <DinaBelova> here is small Etherpad page
15:25:47 <DinaBelova> where I propose to share ideas about 0.2
15:26:21 <DinaBelova> Sylvain & I have written there something already
15:26:39 <Nikolay_St> yeap, I have no time today to write my thoughts
15:26:43 <bauzas> that's open to your  comments
15:26:48 <DinaBelova> JoelC, I suppose you might have some ideas there too
15:26:50 <DinaBelova> :)
15:27:02 <Nikolay_St> but, also I think about Neutron reservations
15:27:17 <DinaBelova> Nikolay_St, please add this point there
15:27:31 <DinaBelova> JoelC, you are welcome to share your ideas
15:28:08 <DinaBelova> JoelC, we saw your comments on https://blueprints.launchpad.net/climate/+spec/notifications
15:28:13 <Nikolay_St> DinaBelova: I'do it on weekend
15:28:19 <DinaBelova> Nikolay_St, tnx
15:28:29 <JoelC> yes.  i am reviewing the climate-.2 etherpad.  looks interesting..  ultimately we are looking to drive our life cycle management needs from climate.  climate being the source of many of the events.
15:28:47 <JoelC> we anticipate having workflows that will be triggered by these events
15:29:12 <DinaBelova> JoelC, are you speaking about notifications here as events?
15:29:16 <bauzas> the Ceilometer integration should match your needs
15:29:16 <JoelC> based on what BP around hooks/notifications and the direction you are headed I think we will have the integration points to make this a reality
15:29:31 <JoelC> not really
15:29:51 <bauzas> so I guess you want to do actions on an event ?
15:30:22 <JoelC> correct
15:30:39 <DinaBelova> like "lease has started" -> "do smth"
15:30:40 <DinaBelova> ?
15:30:51 <JoelC> when a user is entitled today we have custom code that integrates with openstack and creates the project, etc.
15:31:25 <JoelC> in the future we will enhance this to store more meta detail within openstack ... hopefully in the generic meta repository in glance but we will see how that plays out
15:31:42 <JoelC> that meta data will drive business logic we hope to exist as workflows in mistral
15:32:01 <DinaBelova> JoelC, great idea
15:32:46 <bauzas> JoelC: why aren't you using Heat for this ?
15:32:49 <JoelC> most of our projects will be using leases so we are hoping we can get climate to send events (lease started, lease about to expire, lease expired, etc..)
15:33:01 <JoelC> we do use heat for complex collections
15:33:17 <JoelC> projects are associated to our business units
15:33:21 <bauzas> because Ceilometer can send events to Heat
15:33:32 <JoelC> each team / BU will have several projects
15:33:55 <DinaBelova> bauzas, I suppose there is one thing here - Climate should a source of events
15:34:04 <DinaBelova> because these events are Climate specific
15:34:17 <JoelC> those that are not "production" will be forced to get a lease.... this concept is part of our integrated service management and resource management
15:34:18 <bauzas> yup, I'm thinking of the workflow Climate -> Ceilo -> Heat
15:34:41 <bauzas> for providing actions upon events
15:35:08 <bauzas> but still, we can define some custom hooks, I agree
15:35:18 <DinaBelova> bauzas, I'm not sure JoelC is speaking about actions that Heat might be processing
15:35:25 <JoelC> one of the workflows that we would like to realize this year would be to send notification on expiration, backup the vm and delete it.
15:35:28 <bauzas> where you map extra actions that you need to do
15:36:10 <bauzas> JoelC: okay, gotcha
15:36:24 <DinaBelova> JoelC, i think that's more than implementable
15:36:25 <DinaBelova> :)
15:37:15 <DinaBelova> ok
15:37:16 <bauzas> ok, anything left to discuss for 0.2 ?
15:37:36 <DinaBelova> I think no
15:37:58 <DinaBelova> ok
15:38:02 <DinaBelova> #topic Open discussion
15:38:23 <DinaBelova> something to discuss?
15:38:24 <DinaBelova> :)
15:38:39 <DinaBelova> I suppose we just should have 0.1 asap
15:38:51 <DinaBelova> and then continue working on everything else
15:39:20 <DinaBelova> JoelC, please don't mind to describe your use cases and ideas in https://etherpad.openstack.org/p/climate-0.2
15:39:43 <DinaBelova> JoelC, am I right you want to participate in Climate implementing with your team?
15:39:56 <JoelC> will do.  we look forward to pulling down .1 and getting more involved in realizing .2.  thanks.
15:40:17 <JoelC> correct.. we need to get more involved.
15:40:38 <DinaBelova> JoelC, it's really good news :)
15:40:51 <DinaBelova> Because speaking about 0.2 scope
15:41:08 <DinaBelova> there are much to do :)
15:41:13 <DinaBelova> And it'll be interesting :)
15:41:23 <DinaBelova> bauzas, anything to add?
15:41:23 <bauzas> DinaBelova: I also have some people wanting to join us
15:41:29 <DinaBelova> bauzas, wow
15:41:30 <DinaBelova> :)
15:41:34 <DinaBelova> It's X-mas for me :)
15:41:36 <bauzas> DinaBelova: that's still to discuss
15:41:53 <DinaBelova> bauzas, let me know about results of this discussion
15:42:02 <bauzas> DinaBelova: of course ;)
15:42:07 <DinaBelova> nice
15:42:18 <DinaBelova> ok, let's return to 0.1 :)
15:42:28 <DinaBelova> and test/fix it asap :)
15:42:31 <DinaBelova> bye
15:42:32 <bauzas> :)
15:42:34 <bauzas> bye
15:42:47 <DinaBelova> #endmeeting