Earlier  
Posted Nick Remark
#openstack-nova - 2018-02-09
09:21:26 bauzas French children will be on vacation by tonight
09:21:30 clang a X u e F e n g
09:21:30 clang j o l o a l o g
09:21:30 clang o b a s c o c g o
09:21:30 clang i r c o r v u s
09:21:34 clang h e J u l i a h o
09:21:34 clang h e s k e t h T
09:21:34 clang c a s - a f k j
09:21:34 clang S w a n s o n l u
09:21:34 clang r v i n d n 0 5
09:21:34 clang c l a y t o n a
09:21:38 clang j o h n 5 1 p
09:21:38 clang i v i v s o n i _
09:21:38 clang b e l a l a s k
09:21:38 clang a m e a d e r a
09:21:38 clang m e s k i i a n
09:21:42 clang t r a i g n a t
09:21:42 clang e g u s j i s
09:21:42 clang u m b S u b l i m
09:21:42 clang u r p l e r b o t
09:21:54 clang D e x s t e l u
09:21:54 clang a n d o B l a c k
09:21:54 clang e r l y c a t m
09:21:54 clang w o r k b e t h
09:21:54 clang s q u e o p e n
09:21:58 clang o g e t a 8 6 s
09:21:58 clang d s l e y d r _ g
09:21:58 clang i s i m o n d o
09:21:58 clang e i f z f u n g
09:21:58 clang t o a b c t l l
09:21:58 clang c z s z a h e r
09:22:02 clang r a r d j p s h
09:22:02 clang m x y a n g e v
09:22:02 clang N o b o d y C a
09:22:02 clang e m r o d d e n
09:22:02 clang e r v e r a s c o d
09:22:06 clang r i l i n e r i c
09:22:06 clang d g o n z a l e z
09:22:06 clang m a n j e e t s
09:22:18 clang a g a r t y a s
09:22:18 clang i c k l e r r h
09:22:18 clang s a u g g y f r
09:22:18 clang a p l e M a s t
09:22:18 clang e b b e x S a m Y
09:22:22 clang x t o m m y l i k
09:22:22 clang j a m i e c t t
09:22:22 clang h u a w t o m h a
09:22:22 clang b o y j i a n g
09:22:22 clang e t t l e d o s a
09:22:26 clang n k a i s e r s
09:22:26 clang r c f r i e s e
09:22:26 clang e d a n d y m c c
09:22:26 clang o o d m o r d r
09:22:26 clang e h u l y a r w
09:22:30 clang A n t i c i m e x
09:22:46 lyarwood aaaaaaaaaaaaaand back to normal
09:23:19 lyarwood bauzas: are you saying that stable/queens is the rc branch?
09:24:16 bauzas yup
09:24:32 bauzas the relmgmt team branches on the RC1 tag
09:24:55 bauzas we had some diagram in the past that explained the release thingy
09:25:00 bauzas in some wikipage
09:25:12 bauzas but I don't know if that got trampled somehow
09:25:26 lyarwood bauzas: right, I thought you were trying to say that there was another rc branch somewhere, that makes sense.
09:25:52 bauzas so, changes targeting RC2 (or more) requires both a master patch *and* a stable/queens patch
09:26:04 bauzas we don't branch when we GA
09:26:10 lyarwood kk
09:26:29 lyarwood thanks :)
09:26:59 bauzas lyarwood: cgit shows it nicely http://git.openstack.org/cgit/openstack/nova/
09:27:13 bauzas I mean http://git.openstack.org/cgit/openstack/nova/log/
09:27:51 lyarwood bauzas: right, I was looking at GH but wasn't sure what we could actually land in stable/queens at this point
09:28:04 lyarwood bauzas: I've pushed https://review.openstack.org/#/c/542738/ for now
09:33:02 bauzas lyarwood: yeah, that's the regular process for asking a RC candidate
09:33:14 bauzas the master change is merged, now you request for a RC2
09:33:53 bauzas the question stable core reviewers should wonder is whether we provide that in a new RC2 or if we wait for a stable point release
09:33:59 bauzas (just explaining the process)
09:34:12 bauzas (to anyone in the chan)
09:34:22 bauzas hence why we branch on RC1
09:34:46 bauzas in general, we keep RC patches for only regression bugfixes
09:35:33 openstackgerrit Marcin Juszkiewicz proposed openstack/nova master: Provide basic data for AArch64 support matrix/functionality https://review.openstack.org/541728
09:36:19 hrw another few entries to matrix
09:36:54 lyarwood bauzas: I don't think it's a stable/core issue that the moment as I don't have +2 on that branch until after GA iirc ;)
09:37:12 lyarwood at the moment*
09:37:42 bauzas lyarwood: yeah, RC branch (which is not yet a stable branch) is having different gerrit permissions
09:38:20 bauzas nova cores can +2 on RC branch by default but not on stable branches
09:38:35 bauzas and that's the opposity for stable cores
09:40:54 openstackgerrit Lajos Katona proposed openstack/osc-placement master: Random names for functional tests https://review.openstack.org/542745
09:44:02 openstackgerrit jichenjc proposed openstack/nova master: Avoid live mgirate to same host https://review.openstack.org/542689
09:52:24 openstackgerrit Lee Yarwood proposed openstack/nova stable/pike: Refine waiting for vif plug events during _hard_reboot https://review.openstack.org/542748
09:53:11 hrw bauzas: thx for info. had no idea about stable|master core split
10:28:12 openstackgerrit Lee Yarwood proposed openstack/nova stable/ocata: Refine waiting for vif plug events during _hard_reboot https://review.openstack.org/542767
10:29:26 hrw so, anyone knows how to get service up after 'nova service-force-down' call?
10:29:45 gibi mriedem, gmann_: I also have some patches on the project config regarding the tempest-full job https://review.openstack.org/#/c/538908/
10:41:16 gibi hrw: the API has a forced_down flag that you can set to false https://developer.openstack.org/api-ref/compute/#update-forced-down
10:41:29 hrw gibi: thx
10:41:57 gibi hrw: the nova client has a --unset flag to do that
10:42:32 hrw weird
10:43:00 hrw works ;D
10:43:09 gibi :)
10:43:45 hrw there should just be 'openstack service up' and 'openstack service down --force' ;D
10:46:33 gibi hrw: the service has an administrative state (enable/disable) and an operational state (up, down, forced_down)

Earlier   Later