Friday, 2017-02-03

*** mat128 is now known as mat128|mtg16:35
ntpttrlin_yang: have a moment?20:14
ntpttrI think I just found one possible reason we might want to at least be aware of the redfish assigned UUID for nodes20:15
ntpttrworking on the manage command, it's possible to run it on a node you already have saved in the database, which results in having the same node in the DB twice with two different valence-assigned UUIDs20:16
ntpttrlin_yang: *or* we could use the index value, with the caveat that we will need to be checking only against nodes managed by the same pod manager20:32
ntpttrI think it would be good to get that info stored in the DB for resources anyways - index, uuid, and which pod manager are they managed by20:32
ntpttrin the form of a UUID so that all pod manager IDs are unique20:32
lin_yangjust finished the lunch21:32
lin_yangyep, the podm uuid + index should be unique21:32
lin_yangand the corresponding podm uuid should be store in db also as you mentioned, I remember chester update this on api spec21:35
lin_yanghttps://review.openstack.org/#/c/410570/5/api-ref/source/valence-api-v1-nodes.inc21:37
lin_yangHow about we add podm uuid in another commit, combine with support compose node on multiply podm?21:40
openstackgerritLin Yang proposed openstack/valence master: Support post action to composed node  https://review.openstack.org/42840321:46
*** ramineni has quit IRC22:20
*** ramineni has joined #openstack-valence22:21
*** ramineni has quit IRC22:50
*** ramineni has joined #openstack-valence22:51
ntpttrlin_yang: Sounds good, a different commit would be best23:44
ntpttrrunning into a bit of an issue with my patch at the moment with node listing not showing index value23:45
lin_yangif need to any update for current node related function, please let me know23:48

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