| zhenguo | hi guys, does valence client work now? is there some document to show how to use it? | 02:48 |
|---|---|---|
| ramineni | mkrai: curl -v -H "Content-Type: application/json" -X POST -d '{"name":"small", "properties":{"memory":{"capacity_mib":"1000", "type":"DDR2"},"processor":{"total_cores":"2","model":"Intel"}}}' http://localhost:8181/v1/flavors | 03:12 |
| ramineni | this works | 03:12 |
| ramineni | zhenguo: valence client is not usable as of now, work is going on the same | 03:14 |
| zhenguo | ramineni: got it, thanks! | 03:15 |
| zhenguo | ramineni: I'm considering the integration of mogan and valence, but unfortunately the client it's still not usable now :( | 03:16 |
| zhenguo | ramineni: do you have a plan for the first release of client? | 03:16 |
| ramineni | zhenguo: oh ok, not sure , hopefully should be done by pike-3 , ill check with the other team members and let you know | 03:18 |
| zhenguo | ramineni: thanks very much! | 03:18 |
| ramineni | zhenguo: no problem :) | 03:18 |
| *** ChanServ changes topic to "#openstack-valence" | 04:09 | |
| -openstackstatus- NOTICE: Sufficient free space has been reclaimed that jobs are passing again; any POST_FAILURE results can now be rechecked. | 04:09 | |
| openstackgerrit | Anusha Ramineni proposed openstack/python-valenceclient master: Add pep8 check for import order style https://review.openstack.org/467481 | 04:49 |
| *** lin_yang has joined #openstack-valence | 14:23 | |
| *** ramineni_ has joined #openstack-valence | 14:47 | |
| ramineni_ | lin_yang: ntpttr : hi | 14:51 |
| lin_yang | Hi | 14:52 |
| ramineni_ | lin_yang: have a small question , what is the difference between systems and nodes in terms of rackscale | 14:52 |
| ramineni_ | lin_yang: is it that nodes are composed from systems resources? | 14:53 |
| lin_yang | ramineni_: nate and I will attend another meeting today, maybe cannot attend irc meeting | 14:54 |
| lin_yang | Yes your understanding is correct | 14:55 |
| *** ananth_n has joined #openstack-valence | 14:55 | |
| ramineni_ | lin_yang: oohk, thanks | 14:55 |
| *** hubian has joined #openstack-valence | 14:58 | |
| ananth_n | hello everyone | 14:59 |
| ramineni_ | ananth_n: hi | 14:59 |
| hubian | hello ananth | 14:59 |
| ananth_n | let'a | 15:00 |
| ananth_n | let's wait a min to see | 15:00 |
| ananth_n | if anyone else joins | 15:00 |
| lin_yang | Hello ananth | 15:00 |
| ananth_n | hi lin_yang | 15:00 |
| mkrai | Hi | 15:01 |
| ananth_n | i realise things have been a tad slow over the past couple of weeks | 15:02 |
| ananth_n | but let's resume at full speed now :) | 15:03 |
| ramineni_ | ananth_n: are we expecting pike-2 release for valence? | 15:03 |
| *** jfding has joined #openstack-valence | 15:03 | |
| *** ntpttr_laptop has joined #openstack-valence | 15:03 | |
| ntpttr_laptop | hi | 15:04 |
| jfding | hi | 15:04 |
| ananth_n | we didn't have one such in the plan | 15:04 |
| ramineni_ | ananth_n: but Projects must participate in at least two milestones in order to be considered part of the release | 15:04 |
| ananth_n | ntpttr_mobile jfding hello | 15:04 |
| ramineni_ | ananth_n: https://releases.openstack.org/pike/schedule.html#p-mf | 15:04 |
| ntpttr_laptop | sorry for being a couple minutes late, but what is being discussed right now? | 15:05 |
| *** Mrittika_ has joined #openstack-valence | 15:06 | |
| *** praveen__ has joined #openstack-valence | 15:06 | |
| ntpttr_laptop | hi Mrittika_ | 15:06 |
| ananth_n | in order to meet the pike2 timeline, which is in 2 weeks, we will have to revisit what's pending & what can be closed in the 2 weeks | 15:06 |
| Mrittika_ | Hi | 15:06 |
| ramineni_ | ananth_n: yes | 15:06 |
| ananth_n | @ntpttr_mobile ramineni was asking if we will partivcipate in pike2 release | 15:07 |
| ntpttr_laptop | ah sure, but have we participated in the milestones like ramineni_ said? I know there was a while where activity was low, did we miss them then or can we still make the timeline? | 15:07 |
| Mrittika_ | I will be adding/modifying a blueprint on task scheduling | 15:07 |
| Mrittika_ | Let's review that offline and decide if that is possible | 15:08 |
| ntpttr_laptop | sounds good Mrittika_ I'll take a look when it's up | 15:08 |
| ramineni_ | ntpttr_laptop: pike 2 is june5 -9 , so it should be possible :) | 15:08 |
| ananth_n | we haven't participated in earlier release, & pike-2 is in 2 weeks | 15:08 |
| ntpttr_laptop | sounds good! | 15:09 |
| Mrittika_ | @ramineni which blueprints are of interest to you | 15:09 |
| ananth_n | so, to meet the pike-2 timeline, i suggest we look at all pending patches & freeze on what would be included/excluded | 15:10 |
| Mrittika_ | Yes | 15:10 |
| ntpttr_laptop | will do | 15:10 |
| ntpttr_laptop | we can have those discussions on gerrit | 15:10 |
| lin_yang | If we donot add new feature we can close current pending patches and make a release | 15:10 |
| ramineni_ | Mrittika_: im interested in vendor drivers in valence and manage disaggreate resource not of rack scale, but the proposal is still in draft phase | 15:10 |
| Mrittika_ | When you say release is this for official release? | 15:11 |
| mkrai | I will complete the ironic integration BP. Sorry have been busy with some other stuffs. | 15:11 |
| ramineni_ | Mrittika_: final release will be around first week of Aug | 15:11 |
| Mrittika_ | Ok. Need to know who wants the release | 15:12 |
| ntpttr_laptop | ramineni_, do you have a spec up for vendor drivers or is it in BP phase now? | 15:13 |
| Mrittika_ | Essentially, based on a couple of requests we need a task scheduler in | 15:13 |
| ramineni_ | BP :( , hoping to keep the spec soon | 15:13 |
| ntpttr_laptop | ramineni_, when you have a spec ready I'm happy to review it | 15:14 |
| mkrai | Mrittika_: What is this task scheduler ? | 15:14 |
| Mrittika_ | And then test simultaneous connections by ironic and nova to show scalability | 15:14 |
| ntpttr_laptop | I'll try to keep an eye open but feel free to ping/email | 15:14 |
| ananth_n | @ramineni let us know when you have the spec ready | 15:14 |
| ramineni_ | ananth_n: ntpttr_laptop: sure will do , thanks | 15:15 |
| Mrittika_ | @mkrai I will add the bp and all will get a notification | 15:15 |
| Mrittika_ | Need to know requirement from Lenovo | 15:15 |
| mkrai | Mrittika_: Ok thanks | 15:15 |
| ananth_n | @Mrittika the release that ramineni is refering in order to intercept the pike release. we should align a release of valence so it will be made part of OpenStack release in Aug. @ramineni please chip in | 15:15 |
| ananth_n | @hubian ? | 15:16 |
| ananth_n | does Lenovo have any requirements? | 15:16 |
| ramineni_ | ananth_n: yes, Mrittika_: more info in https://releases.openstack.org/pike/schedule.html#p-mf | 15:16 |
| hubian | from lenovo side we would ensure the valence could.stable running on lenovo's podm | 15:17 |
| Mrittika_ | @ramineni is your team planning a release with pike +valence | 15:17 |
| ntpttr_laptop | hubian: lenovo's podm uses redfish right, or are you also interested in vendor driver's like ramineni_? | 15:18 |
| ramineni_ | Mrittika_: no | 15:18 |
| hubian | we would fix the gap between lenovo's podm and valence | 15:19 |
| hubian | yeah lenovo podm uses redfish | 15:19 |
| ntpttr_laptop | cool that sounds good | 15:19 |
| lin_yang | hubian: any difference between Lenovo podm and reference one? | 15:19 |
| mkrai | ramineni_: Do you have link for your vendor driver ? | 15:20 |
| hubian | some extended api's spec | 15:20 |
| hubian | and the api spec version has a difference | 15:21 |
| Mrittika_ | We need someone to update the redfish driver | 15:21 |
| lin_yang | Is there a api spec we can take a look hubian? | 15:22 |
| Mrittika_ | Not a pike activity but something to target for q3 | 15:22 |
| lin_yang | Mrittika_: you mean sushy? | 15:22 |
| ramineni_ | mkrai: no as of now, hoping to keep spec soon | 15:22 |
| Mrittika_ | Yes | 15:22 |
| Mrittika_ | lin_yang why do you need the spec | 15:23 |
| lin_yang | I would like to do that, what kind of update? | 15:23 |
| Mrittika_ | I will add a bp for that too | 15:23 |
| lin_yang | Want to figure out the difference for Lenovo podm if we will support it | 15:24 |
| Mrittika_ | We only build for redfish | 15:24 |
| lin_yang | Mrittika_: sounds good | 15:24 |
| hubian | eh,there is but i thought lenovo podm is extended api as the rsd allowed , so maybe this won't effect valence too much | 15:24 |
| Mrittika_ | Yes hubian is correct | 15:25 |
| lin_yang | Okay got it | 15:25 |
| hubian | :) | 15:26 |
| Mrittika_ | Ananth_n any other area to consider? | 15:27 |
| ntpttr_laptop | ananth_n | 15:28 |
| ntpttr_laptop | doesn't ping unless you get capitalization of letters :) | 15:28 |
| ananth_n | valence storage/networking pieces are not yet developed | 15:28 |
| hubian | @ramineni, i.got you email about the mutil podmanager , i will reply you asap ～ | 15:28 |
| ananth_n | rather, we're lagging on those fronts. | 15:29 |
| ramineni_ | hubian: thanks :) | 15:29 |
| Mrittika_ | Multi poem is something we want to do this year | 15:29 |
| ntpttr_laptop | ananth_n: I can talk to my manager about using cycles for doing some valence work again to work on storage | 15:29 |
| ntpttr_laptop | I haven't been lately but I think that I could swing it again | 15:29 |
| ananth_n | multi-podm: we have a patch submitted by hubian. | 15:29 |
| Mrittika_ | Does anyone have a bp? | 15:29 |
| Mrittika_ | Oh | 15:30 |
| ananth_n | multi-cloud is not yet in | 15:30 |
| Mrittika_ | Is there a flow diag | 15:30 |
| ananth_n | hubian : could you share any diagram | 15:30 |
| ananth_n | coz the spec was text-only | 15:30 |
| hubian | yeah ～ i could continue making it for mutli pod manager | 15:30 |
| ramineni_ | ntpttr_laptop: would like to discuss on pooled resources api , about the storage patch whihc you submitted, may be ill drop mail later | 15:31 |
| ananth_n | we need a "scheduler" of sorts for multi-podm support. that is pending IIRC | 15:31 |
| mkrai | I think its better to create a etherpad page for all the task that are pending and which patches/bp we want in this release | 15:31 |
| Mrittika_ | Good to see lot of things to be done 😊 | 15:31 |
| ananth_n | we do hvae a lot of things to develop:) | 15:32 |
| mkrai | For keeping a centralized source of data | 15:32 |
| ananth_n | Mrittika yes! :) | 15:32 |
| ntpttr_laptop | ramineni_: sure that sounds good, been a while since I pushed that patch so it likely could use an update | 15:32 |
| Mrittika_ | Need more folks to join | 15:32 |
| ntpttr_laptop | ramineni_, send me an email and I'll get back to you :) | 15:32 |
| ananth_n | we've had more folks from NEC submit patches recently. that's good. they aren't in today's meeting though | 15:33 |
| ramineni_ | ntpttr_laptop: sure , thanks | 15:33 |
| Mrittika_ | Ok. Let's review and update bps | 15:33 |
| Mrittika_ | And call it a day today | 15:34 |
| ntpttr_laptop | sounds good! | 15:34 |
| hubian | +1 | 15:34 |
| ananth_n | the day is starting for nttpttr_laptop and lin_yang :D | 15:34 |
| Mrittika_ | Bye! | 15:35 |
| ntpttr_laptop | bye all | 15:35 |
| ananth_n | bye folks ! | 15:35 |
| hubian | very nice to see valence returns powerful hah～ | 15:35 |
| hubian | thanks | 15:35 |
| lin_yang | Thanks bye | 15:35 |
| *** ananth_n has quit IRC | 15:35 | |
| hubian | bye ～ | 15:35 |
| jfding | bye~ | 15:35 |
| *** ramineni_ has left #openstack-valence | 15:35 | |
| *** hubian has quit IRC | 15:36 | |
| *** praveen__ has quit IRC | 15:37 | |
| *** Mrittika_ has quit IRC | 15:39 | |
| *** ntpttr_laptop has quit IRC | 15:56 | |
| *** ntpttr_laptop has joined #openstack-valence | 16:07 | |
| *** ntpttr_laptop has quit IRC | 16:12 | |
| *** ntpttr_laptop has joined #openstack-valence | 17:00 | |
| *** ntpttr_laptop has quit IRC | 17:04 | |
| *** jfding has quit IRC | 17:43 | |
| *** openstackgerrit has quit IRC | 19:48 | |
| *** ntpttr_laptop has joined #openstack-valence | 20:12 | |
| *** ntpttr_laptop has quit IRC | 20:26 | |
| *** ramineni_ has joined #openstack-valence | 23:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!