Wednesday, 2017-02-08

openstackgerrithubian proposed openstack/valence master: implement simulator for valence  https://review.openstack.org/42245307:12
openstackgerrithubian proposed openstack/valence master: implement simulator for valence  https://review.openstack.org/42245307:25
openstackgerrithubian proposed openstack/valence master: implement simulator for valence  https://review.openstack.org/42245308:53
*** openstackgerrit has quit IRC09:34
*** ntpttr_ has joined #openstack-valence09:44
*** ntpttr has quit IRC09:45
*** yufei_ has quit IRC09:45
*** yufei_ has joined #openstack-valence10:01
*** hubian has joined #openstack-valence14:56
*** Jinxing has joined #openstack-valence14:58
Jinxinghi14:59
*** ramineni_ has joined #openstack-valence14:59
ntpttr_hi15:00
lin_yangHi15:01
mkraiHi Jinxing ntpttr_ lin_yang15:01
*** ananth_n has joined #openstack-valence15:01
mkraiIs there any official meeting now?15:01
ananth_nhello everyone15:02
ananth_nhello @mkrai15:02
ananth_nhaven't seen you earlier15:02
ntpttr_hi mkrai, yep now is the weekly meeting15:02
mkraihi ananth_n15:02
mkraiI am always logged in to this channel15:03
mkrai:)15:03
mkraiOk I think I should introduce myself. I am Madhuri Kumari working with Intel :)15:03
hubianwelcome15:04
ntpttr_welcome madhuri :)15:04
mkraiThank you hubian ntpttr_15:04
lin_yangmkrai: welcome to join valence15:04
ananth_n@mkrai, ah, now I know who you are :)15:04
mkraiThank you lin_yang :)15:04
ntpttr_so I put one quick thing on the agenda today I believe.. Would just like some eyes on my node-manage patch https://review.openstack.org/#/c/429119/315:05
ananth_n@ntpttr_ yes, I did go thru' the BP. i think it is a feature we'll need. haven't had time to go thru' the code patch15:05
ntpttr_basically what is does is allow the user to consume already existing nodes into the valence database, since if valence didn't create them in the first place it won't know how to access them15:05
hubianyeah~i have taken a sight on that patch15:06
ntpttr_cool thanks ananth. I think I need to add the api-ref changes to the patch15:06
*** ntpttr_ is now known as ntpttr15:06
ntpttrbut it really isn't all that complex15:07
ntpttranyways, I don't really have anything more to say about it here15:07
ananth_nso, i also wanted to figure out what we need to do within Valence given Mogan is here. some of the things Mogan is doing, we had planned to do in Valence15:08
ntpttrananth_n: which things are those ananth_n?15:08
ntpttrwith regards to bare metal use?15:08
ananth_nMogan is doing quota management, integrates with Ironic15:08
mkraintpttr_: Do you have link for the blueprint?15:08
ananth_nI haven't studied Mogan to know if its Ironic integration is different from what Valence's plans are15:09
mkraiI guess the commit message doesn't point to the bp15:09
ntpttrmkrai: https://blueprints.launchpad.net/openstack-valence/+spec/manage-node15:09
ananth_nbut my main concern is to not duplicate effort15:09
lin_yangananth_n: yep the first thing is quota15:10
lin_yangBut mogan seems to focus on openstack only15:10
ntpttrananth_n: definitely something to look into15:10
lin_yangValence should support other cloud15:11
lin_yangSo I would like to say valence somehow still need support quota15:11
ananth_n@lin_yang yes, good point. It might be that we continue to have the features. but just wanted to raise this concern.15:11
ananth_naside: Malini and I drafted an abstract and submitted it15:12
ananth_nplease vote :)15:12
ntpttrwill do :)15:12
hubian+115:13
mkraintpttr_: I have a quick question looking at the patch15:13
lin_yangAnd leave mogan do high level quota for all hardware resource15:13
ntpttrmkrai: sure15:13
mkraiI see that the API endpoint is /nodes/manage which registers the node to valence15:13
mkraiWhat would be the endpoint to delete/update etc?15:14
hubian@yanglin valence should support other cloud , could please say more about this?15:14
ntpttrmkrai: the same as any other node at that point15:14
lin_yanghubian: like k8s mesos15:15
ntpttrso you'd hit the API server with a delete request at /v1/nodes/<string:nodeid>15:15
ntpttrbecause when the node is managed it will be assigned a UUID15:16
Jinxing@lin_yang but the valence just compose node, is there any relation to what cloud?15:16
ananth_n@hubian the idea is that valence is not restricted to openstack but can support other s/w which wants to use pooled resources.15:17
ntpttrJinxing: there will hopefully be soon - I think that a pretty big priority now should be integrating with deployment tools to be able to deploy OpenStack on composed nodes15:17
ntpttrand then other technologies can follow as well15:17
ananth_n@Jinxing : Valence is more than compose node. :) The concepts of quota, telemetry etc can be applied to other clouds too.15:17
lin_yang+115:18
hubianok maybe i could get the point15:18
hubianthat valence would have a big picture15:19
JinxingI will look for some information about it. Perhaps I haven’t understand the valence completely.15:20
hubianafter hardware management, valence could do something on the up level15:20
ntpttryeah the idea is that once nodes have ben composed, valence knows enough information about them to use a tool to provision them and bring them up with an OS, and then we could write a plugin for a deployment tool like kolla or triple-o to deploy openstack on top of them15:21
Jinxingyeah15:21
lin_yangIt is more than precompose node then deploy cloud on it. Like cloud grow shrink on the fly when admin is aware it is short of something15:22
hubianok, get it !15:22
JinxingWe have dpeloyed openstack successfully by kolla after compose node by valence.15:23
ananth_nspeaking of which, @jinxing , any updates on client?15:23
Jinxingyeah15:23
JinxingI have implemented some functions about  the valence client, but haven't submit to the community and lack unittests. Now I am writing the unittest, so I will submit some patch, please take some times to review it, thanks.15:23
ntpttrJinxing: oh really? What tool did you use for bringing up an OS on the composed nodes before using kolla?15:23
ntpttrthat is really interesting to hear15:23
lin_yangI guess it is 99cloud owned production tool15:25
Jinxingyeah,through a driver wirten by yufei15:26
JinxingUse ironic deploy OS, then use kolla to deploy openstack15:26
ntpttrawesome - is your tool anything like bifrost?15:26
lin_yangJinxing: thanks for awesome work on client. If possible, please separate into small piece15:26
ntpttra standalone tool for ironic15:27
ntpttrhey guys sorry I have a hard stop here in 2 minutes15:27
ntpttranother meeting15:27
JinxingI will separate into small  piece15:27
lin_yangntpttr: bye15:27
ananth_nya, same here - another meeting in 2 minutes15:28
ntpttrJinxing: I definitely want to hear more about the process you guys had for deploying the cloud after composing nodes15:28
ntpttrmaybe in email would be good15:28
ntpttrthanks everyone :)15:28
lin_yangananth_n: please help to review my patches pending on gerrit when you get chance thanks15:29
ntpttrah yes I forgot! I've given them +2s I believe15:29
ntpttrjust need one more set of eyes15:29
lin_yangntpttr: thanks a lot Nate15:30
ananth_nsure. I will review15:30
lin_yangananth_n: thanks15:31
Jinxing@ntpttr we can comunicate by email15:31
ntpttrJinxing: sounds good15:31
*** ananth_n has left #openstack-valence15:54
*** Jinxing has quit IRC16:10
*** ramineni_ has quit IRC17:59
*** lin_yang has quit IRC18:35
*** dasanind has quit IRC18:35
*** sindhu has quit IRC18:35
*** lin_yang has joined #openstack-valence19:47
*** dasanind has joined #openstack-valence20:14
*** sindhu has joined #openstack-valence20:16
*** ramineni_ has joined #openstack-valence23:58

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