| openstackgerrit | Lin Yang proposed openstack/valence-specs master: Add scheduler to support multiple PODM https://review.openstack.org/474053 | 04:38 |
|---|---|---|
| openstackgerrit | Raghavendra proposed openstack/valence master: [WIP] Task Manager and task queue https://review.openstack.org/474068 | 06:01 |
| openstackgerrit | Lin Yang proposed openstack/valence-specs master: Add scheduler to support multiple PODM https://review.openstack.org/474053 | 06:16 |
| openstackgerrit | Raghavendra proposed openstack/valence master: [WIP] Task Manager and task queue updated api part to support RPC mechanism Change-Id: I5bc741575e153b16c98fe7351facec3a3b5f87f7 https://review.openstack.org/474068 | 06:37 |
| openstackgerrit | Raghavendra proposed openstack/valence master: [WIP] Task Manager and task queue updated api part to support RPC mechanism Change-Id: I5bc741575e153b16c98fe7351facec3a3b5f87f7 https://review.openstack.org/474068 | 06:42 |
| openstackgerrit | Ananth Narayan S proposed openstack/valence-specs master: [WIP] Add task queueing to address scalability https://review.openstack.org/474099 | 08:03 |
| openstackgerrit | Raghavendra proposed openstack/valence master: [WIP] Task Manager and task queue updated api part to support RPC mechanism Change-Id: I5bc741575e153b16c98fe7351facec3a3b5f87f7 https://review.openstack.org/474068 | 09:29 |
| openstackgerrit | Raghavendra proposed openstack/valence master: [WIP] Task Manager and task queue updated api part to support RPC mechanism Change-Id: I5bc741575e153b16c98fe7351facec3a3b5f87f7 https://review.openstack.org/474068 | 12:52 |
| *** openstackgerrit has quit IRC | 13:18 | |
| *** ramineni_ has joined #openstack-valence | 14:22 | |
| *** ananth_n has joined #openstack-valence | 14:25 | |
| *** ntpttr_laptop has joined #openstack-valence | 14:26 | |
| ananth_n | hi nate | 14:28 |
| ananth_n | hi ntpttr_laptop | 14:29 |
| ntpttr_laptop | hey ananth_n | 14:29 |
| ananth_n | could you cair the meeting today | 14:29 |
| ananth_n | i am in and out with a couple of things | 14:29 |
| ananth_n | will be online | 14:29 |
| ananth_n | but might be sloe | 14:29 |
| ananth_n | slow | 14:29 |
| mkrai | Hi | 14:29 |
| ntpttr_laptop | sure np | 14:30 |
| ntpttr_laptop | hi mkrai | 14:30 |
| ramineni_ | hi | 14:30 |
| ananth_n | hello | 14:30 |
| lin_yang | Hello everyone | 14:31 |
| ntpttr_laptop | hi all, does anyone have agenda items today that they'd like discussed? | 14:31 |
| *** shuquan has joined #openstack-valence | 14:31 | |
| ananth_n | one announcement: RSD 2.1 is released on https://github.com/01org/IntelRSD contains the PSME simulator under the “Simulators” folder. | 14:31 |
| shuquan | hi guys | 14:32 |
| ntpttr_laptop | hi shuquan | 14:32 |
| shuquan | sorry, i'm late | 14:33 |
| ntpttr_laptop | no problem! do you have any agenda items you'd like discussed today? | 14:33 |
| shuquan | due to some network issue | 14:33 |
| shuquan | no from me | 14:33 |
| shuquan | :) | 14:33 |
| ananth_n | so, for folks who joined after i posted the message, let me repeat: one announcement: RSD 2.1 is released on https://github.com/01org/IntelRSD contains the PSME simulator under the “Simulators” folder. | 14:34 |
| mkrai | I have one | 14:34 |
| ananth_n | the PODM reference code will work with the PSME simulator. | 14:34 |
| lin_yang | ananth_n: Thanks for the update | 14:35 |
| ntpttr_laptop | thanks ananth_n | 14:35 |
| ntpttr_laptop | mkrai: sure what would you like to talk about? | 14:35 |
| mkrai | This is the new patch for redesigning architecture: https://review.openstack.org/#/c/474068/ | 14:35 |
| mkrai | This is WIP | 14:35 |
| mkrai | So wanted to tell you guys so that you can have a look | 14:35 |
| ntpttr_laptop | ah cool thanks for the link, | 14:36 |
| ntpttr_laptop | I'll give that a look today | 14:36 |
| lin_yang | sure, will do it today, thanks | 14:36 |
| mkrai | Bdw this is not posted by me :) | 14:36 |
| ntpttr_laptop | yes, has raghavendra been at any of these meetings? I'm not sure we've met | 14:37 |
| mkrai | No I think | 14:38 |
| ananth_n | raghavendra hasn't been to the meetings. | 14:38 |
| ntpttr_laptop | okay well I'll give the patch a look and pull it down to test it when it's ready for that | 14:38 |
| ananth_n | also, madhuri & I are working on the spec : https://review.openstack.org/#/c/474099/ . This is also WIP. In a day or two, I'll submit the non-WIP first draft | 14:39 |
| ntpttr_laptop | ananth_n: hey, do you know if there's an API spec document for the 2.X pod manager somewhere public? | 14:39 |
| ntpttr_laptop | ananth_n: awesome, I'll leave that open in a tab as well | 14:39 |
| ramineni_ | does anyone had a look at device orchestration part? ntpttr_laptop, i have updated your comments on that spec, plz have look again | 14:40 |
| ananth_n | ntpttrr_laptop: there should be, i will look for it | 14:40 |
| ntpttr_laptop | ramineni_: thanks, will do | 14:40 |
| ramineni_ | ananth_n: again same question, does valence has plan for pike release? | 14:41 |
| ntpttr_laptop | I've been looking into that, and that's why I want to look at the API spec for 2.X | 14:41 |
| lin_yang | I am working on new scheduler service, here is the spec: https://review.openstack.org/#/c/474053/2 | 14:41 |
| ramineni_ | ntpttr_laptop: great , thanks | 14:41 |
| ramineni_ | ananth_n: or first release planned would be Q? | 14:42 |
| ntpttr_laptop | I think it might be too late for pike, is that right ananth_n? | 14:44 |
| lin_yang | ramineni_: anyone are waiting the valence release? | 14:44 |
| ananth_n | sorry folks, am in between things. | 14:44 |
| ntpttr_laptop | np | 14:44 |
| ramineni_ | lin_yang: no, just need to report which release would be planned for valence | 14:45 |
| ntpttr_laptop | I'd venture to say Q at this point | 14:45 |
| ramineni_ | ntpttr_laptop: ok, thanks for the update | 14:46 |
| *** mrittika has joined #openstack-valence | 14:47 | |
| ananth_n | +1 ntpttr_laptop | 14:47 |
| *** akhil_jain has joined #openstack-valence | 14:47 | |
| ntpttr_laptop | do we have any work being done on the client side? shuquan did your company have a working implementation of a python-valenceclient that was demoed at the openstack summit? | 14:47 |
| lin_yang | +1 for Q release | 14:47 |
| ananth_n | the q release will be the meaty one | 14:47 |
| mrittika | hi | 14:48 |
| shuquan | yes, i think jinxing has submit some patches about client | 14:49 |
| mrittika | did we discuss the agenda item | 14:49 |
| ntpttr_laptop | hi mrittika | 14:49 |
| lin_yang | hey mrittika | 14:49 |
| ntpttr_laptop | shuquan: yes, but none that implement the CLI itself | 14:49 |
| ntpttr_laptop | mrittika: which item would you like to discuss? we've talked about a couple things | 14:49 |
| mrittika | sorry got late.. can eat or type :) | 14:50 |
| shuquan | I see. Let me check with jinxing internally tomorrow. | 14:50 |
| ntpttr_laptop | shuquan: the one that is submitted upstream right now is getting -1s from jenkins at the moment | 14:50 |
| ntpttr_laptop | no problem, just wondering since I saw the video with a working demo of it :) | 14:51 |
| mrittika | i anyone from lenovo joined? | 14:51 |
| lin_yang | shuquan: thanks, it would be better that jinxing can submit all code base to gerrit for reviewing | 14:51 |
| ntpttr_laptop | mrittika: looks like maybe now | 14:52 |
| lin_yang | hubian is not online today | 14:52 |
| ntpttr_laptop | not* | 14:52 |
| mrittika | ok. you guys discussed something for Q release | 14:53 |
| shuquan | sure. jinxing has submit 6 patches for client already. | 14:53 |
| ntpttr_laptop | mrittika: well we discussed how it would likely be the first major one | 14:54 |
| ntpttr_laptop | mrittika: is there something in particular you wanted to talk about then? | 14:54 |
| mrittika | hubian wanted to discuss other cloudstacks we would support | 14:55 |
| *** HuBian has joined #openstack-valence | 14:56 | |
| ananth_n | he joined just now | 14:56 |
| ntpttr_laptop | ah and here's HuBian now! | 14:56 |
| ananth_n | maybe he missed that today onwards is 30 minutes earlier | 14:56 |
| mrittika | wow! there is a Indian saying that if someone is discussing about you and you appear you live for 100 yrs! | 14:57 |
| mrittika | 100 yrs to @HuBian | 14:57 |
| shuquan | :) | 14:58 |
| lin_yang | awesome :) congrats HuBian | 14:58 |
| mkrai | mrittika: haha good one )=:) | 14:58 |
| mrittika | @HuBian what other stack stacks would you like to support | 14:59 |
| mrittika | has anyone started any work on other stacks | 14:59 |
| HuBian | :) | 14:59 |
| ntpttr_laptop | so you mentioned wanting to discuss what other cloud stacks to support? | 14:59 |
| HuBian | thank you all guys | 14:59 |
| ntpttr_laptop | ah I think my connection might be lagging here | 14:59 |
| mrittika | mine too. | 15:00 |
| HuBian | Yeah ~ this is intreast that what rsd would be engaged with | 15:01 |
| mrittika | @ananth do you want to share our investigation with Openshift | 15:01 |
| HuBian | We'd like to go with | 15:01 |
| ntpttr_laptop | mrittika: if you start typing someone's IRC nick and press tab it'll autocomplete and ping them :) | 15:01 |
| mrittika | oh cool! | 15:02 |
| shuquan | regarding openshift, we're also working on it. | 15:02 |
| mrittika | shuquan: did you start with ansible scripts | 15:02 |
| shuquan | we integrate openshift with openstack by heat and ansible. | 15:02 |
| shuquan | we're going to deploy openshift in composed node in RSD. | 15:03 |
| HuBian | :) | 15:04 |
| ntpttr_laptop | shuquan: cool :) is there any way that valence can be used to make the process easier do you think? | 15:04 |
| shuquan | currently, we deploy openshift with heat. and heat will call nova, neturon, etc. and ironic with redfish is integrated with nova, neutron. | 15:06 |
| mrittika | is ironic integrated with neutron now? | 15:07 |
| shuquan | sure. the multi-tenancy features in ironic | 15:07 |
| mkrai | Yes ironic uses neutron | 15:07 |
| shuquan | another feature we can do in valence is to design how to integrate psme networking with ironic multi tenancy feature | 15:08 |
| mrittika | shuquan: exactly.. i was typing that | 15:09 |
| shuquan | any one like to work on that? :) | 15:09 |
| mrittika | should we start a valence branch in Openshift? | 15:10 |
| mrittika | shuquan: there is a blueprint being written on that as we meet here | 15:10 |
| shuquan | maybe we can start with a workflow design first. | 15:11 |
| ntpttr_laptop | mrittika: what would need to change on the openshift side of things? | 15:11 |
| mrittika | ntpttr_laptop: i don't know. i haven't investigated.. however if we want to support containers like K8 instead on OPenstack VMs | 15:12 |
| HuBian | So , it seems that valence has already descieded to support OpenShift as its next cloudstack ? @Mrittika | 15:12 |
| HuBian | Or still in "Open" status ? | 15:13 |
| mrittika | HuBian: it is the other way round..Openshift should be able to use Valence | 15:13 |
| mrittika | if it is only ansible scripts, then not much | 15:13 |
| ntpttr_laptop | mrittika: wasn't that one piece of software that when we had the conversation with michal he said that there wouldn't be much use for RSD? | 15:14 |
| mrittika | Openshift is PAAS. so application characteristics translated to system requirements is the main work | 15:14 |
| HuBian | ok ~ | 15:14 |
| mrittika | ntpttr_laptop: yes.. that's what i meant in my comment | 15:15 |
| shuquan | the problem is openshift, k8s use valence directly or customers still use openstack to deploy them. | 15:15 |
| mrittika | shuquan: what is usage in the industry? | 15:15 |
| shuquan | for the customers we met in China, we built openstack for over all data center management. | 15:16 |
| shuquan | and if they want paas, we use openstack to orchestrate a openshift for them. | 15:17 |
| mrittika | ok. as ntpttr_laptop was saying there is no mapping of K8s to redfish/RSD usage | 15:17 |
| shuquan | and use magnum to build k8s for them | 15:17 |
| mrittika | ok. that seems reasonable.. | 15:18 |
| shuquan | so integrating ironic with rsd well will help customers build openshift/k8s on RSD | 15:18 |
| shuquan | in openstack, magnum -> heat -> nova -> ironic -> PODM | 15:19 |
| shuquan | so ironic is the key. | 15:20 |
| mrittika | has anyone looked at Redfish network proposal | 15:20 |
| lin_yang | shuquan: you mean ironic dynamic compose node through PODM here? | 15:20 |
| mkrai | shuquan: But ironic using valence is possible, do you think? | 15:20 |
| ntpttr_laptop | mrittika: do you have a link? or do you mean what was talked about in your slides? | 15:20 |
| ananth_n | mrittika : not sure if everyone here has a DMTF membership. can anyone view the proposal? | 15:21 |
| shuquan | I hope we can find a good reason to persuade the ironic community on dynamic composition. :) | 15:21 |
| mrittika | https://www.dmtf.org/sites/default/files/Managing_Network_Infrastructure_via_Redfish_v2.pdf | 15:22 |
| HuBian | @shuquan +1 | 15:22 |
| mrittika | i believe you can access it | 15:22 |
| ntpttr_laptop | thanks yes I can access it | 15:22 |
| mrittika | please review that at leisure | 15:22 |
| mkrai | magnum->heat->nova->valence->ironic is simpler | 15:23 |
| shuquan | but as we discussed with the ironic community, they don't want to add the compose part into the exsiting logic | 15:23 |
| shuquan | we have do some testing on the psme networking. :) | 15:24 |
| lin_yang | shuquan: I believe so, both nova and ironic community | 15:24 |
| mrittika | shuquan: that is why we have valence | 15:24 |
| mkrai | In this case we have new virt-driver in Nova that uses valence to do the dynamic composition. | 15:24 |
| mrittika | mkrai: that is not a good use case | 15:24 |
| mkrai | mrittika: Could you please explain why? | 15:25 |
| mrittika | using mechanisms like nova tags or flavors to trigger compose is better that making nova wait a few minutes for the system to compose and boot up | 15:26 |
| mrittika | and then schedule a VM or container | 15:26 |
| ntpttr_laptop | mrittika: wouldn't it have to wait that time anyways if it's using a tag of some kind? | 15:26 |
| mrittika | in a dynamic dc telemetry should be used to identify if new systems need to be composed or new resource needs to be added to a composed node | 15:27 |
| ananth_n | mrittika: if we have telemetry of some kind, then someone could proactively compose a node | 15:28 |
| ananth_n | i believe we had discussed that as one of the things valence could do | 15:28 |
| ntpttr_laptop | time check :) | 15:28 |
| mrittika | yes. Heat and ansible scripts would have policies..too | 15:28 |
| mrittika | yes. we need to jump to a voice meeting.. | 15:29 |
| ananth_n | but that would mean we provoide cloud orchestrator specific support in valence | 15:29 |
| mrittika | ananth_n: yes | 15:29 |
| shuquan | voice meeting +1 | 15:29 |
| ananth_n | ok - need to switch to another meeting. catch you next week folks. | 15:30 |
| mrittika | yes. me too.. bye everyone | 15:30 |
| shuquan | 88 | 15:30 |
| ntpttr_laptop | yep thanks all. Voice meeting for all of us here would be great | 15:30 |
| *** shuquan has quit IRC | 15:30 | |
| ntpttr_laptop | I thik that could help a lot | 15:30 |
| HuBian | voice meeting +1 | 15:30 |
| lin_yang | thanks all, bye | 15:30 |
| ramineni_ | bye all | 15:31 |
| *** ramineni_ has left #openstack-valence | 15:31 | |
| HuBian | bye ~ :) | 15:31 |
| *** HuBian has quit IRC | 15:31 | |
| *** ananth_n has quit IRC | 15:31 | |
| *** mrittika has quit IRC | 16:03 | |
| *** ntpttr_laptop has quit IRC | 16:26 | |
| *** ntpttr_laptop has joined #openstack-valence | 16:30 | |
| *** ntpttr_laptop has quit IRC | 18:31 | |
| *** ntpttr_laptop has joined #openstack-valence | 19:13 | |
| *** ntpttr_laptop__ has joined #openstack-valence | 19:53 | |
| *** ntpttr_laptop has quit IRC | 19:53 | |
| *** ntpttr_laptop__ has quit IRC | 19:58 | |
| *** ntpttr_laptop has joined #openstack-valence | 21:14 | |
| *** ramineni_ has joined #openstack-valence | 23:56 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!