Earlier  
Posted Nick Remark
#openstack-nova - 2018-09-18
20:58:11 openstackgerrit Matt Riedemann proposed openstack/nova master: Return a minimal construct for nova list when a cell is down https://review.openstack.org/567785
20:58:39 mriedem tssurya: can we abandon https://review.openstack.org/#/c/594947/ ? i don't think anything is using it now
20:59:11 tssurya mriedem: originally it was created for https://review.openstack.org/#/c/591658/
20:59:21 tssurya so let's keep it (see the comments from dan there)
20:59:27 mriedem oh, ok
20:59:31 tssurya I am currently updating the test cases for this one
20:59:37 tssurya it will come on top
21:15:33 mriedem dansmith: so if i want to kick the tires on your db migration script in a devstack env, i should be able to just create an empty placement db (but with schema) and then just create some instances and do the migration?
21:16:21 dansmith mriedem: if you have a devstack, easiest thing is to just create some instances, then create an empty placement db and then point it at the server with root/$pass
21:16:40 dansmith if not, you
21:16:50 dansmith will need a nova db with all the right tables, plus something in inventories
21:17:51 mriedem yeah i was thinking of creating a stable/rocky devstack, creating some instances so there is data (allocations), and then create a placement db and run the script
21:18:05 mriedem essentially what grenade is going to have to do
21:18:45 dansmith yup
21:19:06 dansmith run --mkconfig and then put root and the DATABASE_PASSWORD from your localrc in there
21:19:53 dansmith I should probably have mkconfig assume placement and nova_api as db names.. dunno why I didn't
21:26:00 dansmith done
21:29:15 openstackgerrit Ben Nemec proposed openstack/nova master: WIP: Migrade upgrade checks to oslo.upgradecheck https://review.openstack.org/603499
21:34:56 openstackgerrit Ben Nemec proposed openstack/nova master: WIP: Migrade upgrade checks to oslo.upgradecheck https://review.openstack.org/603499
21:35:55 mriedem bnemec: fancy
21:36:12 mriedem is that library in the openstack/requirements repo yet?
21:36:27 mriedem nope https://github.com/openstack/requirements/blob/master/upper-constraints.txt
21:36:29 bnemec No, the repo just got created.
21:36:41 bnemec There is a release on pypi from when I reserved the name though.
21:37:15 bnemec I'm also wondering if we want to rename the UpgradeCheck* classes to just Code and Result for the sake of brevity.
21:37:30 bnemec When used from the lib they'll be upgradecheck.Code and upgradecheck.Result anyway.
21:37:43 dansmith gdi, mriedem already got my -1
21:38:05 bnemec lol
21:39:36 mriedem i didn't -1 b/c i'm too nice
21:40:08 mriedem bnemec: that works for me - i named them that way in nova b/c we have the whole subcommand thing
21:40:13 bnemec dansmith: If you want, you could -1 for the flagrant pep8 violations. ;-)
21:40:18 mriedem so theoretically we could have nova-status foo bar
21:40:24 mriedem nova-status upgrade baz
21:40:28 dansmith nah, now I'm demotivated
21:41:35 bnemec mriedem: Yeah, makes sense. Since the library is specialized we should be able to use the more generic names.
21:41:44 bnemec I'll get that proposed and update the Nova patch.
21:56:23 openstackgerrit Matt Riedemann proposed openstack/nova master: Resource retrieving: add changes-before filter https://review.openstack.org/599276
22:05:35 mriedem wah wah https://etherpad.openstack.org/p/nova-forum-stein
22:05:45 mriedem we have 8 days to submit forum sessions
22:18:58 dansmith this always confuses me,
22:19:07 dansmith but you mean non-presentation forum sessions I guess?
22:19:20 dansmith like projecty design summity topics
22:19:22 dansmith right?
22:23:02 mriedem i guess so yeah,
22:23:04 openstackgerrit Matt Riedemann proposed openstack/nova master: Resource retrieving: add changes-before filter https://review.openstack.org/599276
22:23:12 mriedem although they changed to not use the old forum submission tool,
22:23:25 mriedem and instead use something that looks like the normal call for presentations thing for the big recorded rooms
22:23:40 mriedem https://www.openstack.org/summit/berlin-2018/call-for-presentations
22:24:01 dansmith yeah, which .. seems weird, since those are all picked already, AFAIK
22:24:36 mriedem right, and the one thing i did submit as a presentation has somehow carried over to the forum review i think,
22:24:38 mriedem which is not what i wanted
22:25:11 dansmith meaning, didn't get accepted as a presentation so they made it a forum session instead?
22:25:12 mriedem because i'm pretty sure you all don't want to hear me talking about nfv at the edge in fusionsphere during the forum...
22:25:35 dansmith I think jaypipes would
22:25:41 dansmith he <3's edge
22:25:49 mriedem it would be on jay's top 4 watch list
22:25:51 mriedem or whatever
22:25:58 dansmith Pipes' Picks
22:26:50 mriedem so my thing wasn't accepted as a forum session,
22:26:55 mriedem but i don't want it to be a candidate i guess
22:30:08 mriedem asking for clarification
22:38:14 mriedem dansmith: maybe you want to do a session on oschown
22:38:25 mriedem s/want/should/
22:38:41 dansmith I'd like someone to have ever tried it ever first
22:38:58 dansmith but I could lie
22:39:25 mriedem dude, it's already in production in starlingx
22:39:30 dansmith haha
22:42:08 mriedem kablam http://logs.openstack.org/24/602124/4/experimental/grenade-postgresql/c27d517/
22:42:10 mriedem passing
22:42:23 dansmith I don't know why, but.. congrats :)
22:49:51 openstackgerrit Merged openstack/nova master: Revert "libvirt: add method to configure migration speed" https://review.openstack.org/590814
22:49:58 openstackgerrit Merged openstack/nova master: Add missing backticks in nova-manage docs https://review.openstack.org/603370
#openstack-nova - 2018-09-19
00:02:30 openstackgerrit Tetsuro Nakamura proposed openstack/nova-specs master: Spec: Support filtering by forbidden aggregate https://review.openstack.org/603352
00:39:32 openstack Launchpad bug 1792674 in OpenStack Compute (nova) "[Rocky] fail to get VNC console" [Undecided,Confirmed]
00:39:32 new-comer https://bugs.launchpad.net/nova/+bug/1792674
01:43:06 openstackgerrit Chen proposed openstack/nova master: doc trivial: additional info to admin-password-injection https://review.openstack.org/603414
02:38:27 openstackgerrit Matt Riedemann proposed openstack/nova master: DNM: test resize reschedule up-calls https://review.openstack.org/603389
03:18:17 openstackgerrit Brin Zhang proposed openstack/python-novaclient master: Add support changes-before for microversion 2.66 https://review.openstack.org/603549
03:32:39 openstackgerrit Merged openstack/nova stable/rocky: Handle binding_failed vif plug errors on compute restart https://review.openstack.org/595317
03:32:46 openstackgerrit Merged openstack/nova stable/rocky: Restart scheduler in TestNovaManagePlacementHealAllocations https://review.openstack.org/598152
04:57:32 gmann alex_xu: i will skip today API office hour due to fever. we will continue from next week.
05:06:39 alex_xu gmann: ok, no problem
06:53:49 openstackgerrit OpenStack Proposal Bot proposed openstack/nova master: Imported Translations from Zanata https://review.openstack.org/601047
07:11:32 dpawlik_ is someone using cellv2 but not as "simple" cell but multiple cells?
07:22:24 sorrison dpawlik_: I know CERN are
07:22:39 dpawlik_ sorrison: thx
07:23:04 dpawlik_ sorrison: I got a feeling when I read documentation and the code on github, that all uses simple cell setup xD
07:23:54 sorrison We (Nectar) have some cellsv2 stuff running in testing, still cellsv1 in production
07:23:57 dpawlik_ there are no starts scripts for RDO/Debian Salsa/Ubuntu cloud archive to start super conductor and also conductor that take configuration from different file
07:25:22 sorrison I'm *think* that the super conductor is just a normal conductor but it listens on the api level rabbit queue
07:26:01 sorrison If you were running multiple cells then you'd have lots of different controllers running different conductors
07:26:50 bauzas good morning stackers
07:27:16 bauzas sorrison: this is correct
07:27:57 bauzas dpawlik_: a super conductor is just a normal conductor with a specific configuration
07:30:24 dpawlik_ bauzas: but its reading amqps queue from vhost / and its also talking with nova_cell0 db yes?
07:31:01 dpawlik_ and the second conductor e.g. cell1 is reading from another vhost e.g. nova_cell1 and its also puting data to nova_cell1 db
07:31:26 dpawlik_ I just describe my point of knowledge how it should be configured, is it true?
07:32:01 dpawlik_ I just take it from devstack
07:32:33 dpawlik_ and Im wondering why after executing the same commands like it is done on devstack, on my controller I have duplicated nova services
07:40:20 bauzas dpawlik_: sorry, I was on mute so I missed your ping

Earlier   Later