[openstack-dev] [vitrage] Normalized Resource State
Weyl, Alexey (Nokia - IL)
alexey.weyl at nokia.com
Mon May 16 15:34:25 UTC 2016
Sounds good Ifat and Eylon.
Maybe we only need to think of a more general name for TERMINATING state (something that will include all end transient states).
> -----Original Message-----
> From: Afek, Ifat (Nokia - IL) [mailto:ifat.afek at nokia.com]
> Sent: Monday, May 16, 2016 6:29 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: Amir, Tomer (Nokia - IL)
> Subject: Re: [openstack-dev] [vitrage] Normalized Resource State
> > -----Original Message-----
> > From: EXT Malin, Eylon (Nokia - IL) [mailto:eylon.malin at nokia.com]
> > Sent: Monday, May 16, 2016 6:09 PM
> > Hi all,
> > Aggregated_state can has only values from NormalizedResourceState
> > which is constant enum.
> > Currently the NormalizedResourceState has these values : TERMINATED,
> > ERROR, UNRECOGNIZED , SUSPENDED , RESCUED , RESIZED , TRANSIENT
> > SUBOPTIMAL, RUNNING , UNDEFINED.
> > I think that 2 states are missing :
> > 1. IN_MAINTENANCE - which represent that this resource is under
> > maintenance 2. TERMINATING - which represent transient state that
> > terminating the resource.
> MAINTENANCE state is relevant also for OPNFV Doctor workflow (which is
> currently in discussion), so I think we should add it. We can add
> TERMINATING as well.
> > And regards RUNNING state maybe ACTIVE is more appropriate. Horizon
> > also show active state for instance, networks and ports.
> Fine with me to replace RUNNING with ACTIVE.
> > What do you think ?
> > Eylon Malin
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-
> request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev