Open Stack

I like your idea Ifat. 

-----Original Message-----
From: Afek, Ifat (Nokia - IL) [mailto:ifat.afek at nokia.com] 
Sent: Wednesday, May 18, 2016 1:27 PM
To: OpenStack Development Mailing List (not for usage questions) <openstack-dev at lists.openstack.org>
Cc: Amir, Tomer (Nokia - IL) <tomer.amir at alcatel-lucent.com>
Subject: Re: [openstack-dev] [vitrage] Normalized Resource State

> -----Original Message-----
> From: EXT Weyl, Alexey (Nokia - IL) [mailto:alexey.weyl at nokia.com]
> 
> 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
> >
> > > -----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
> >
> > Ifat.

Thinking about it again, I'm not sure the normalized state is the right direction.
Today it makes sense to add "terminating" and "maintenance", tomorrow it will make sense to add two other states, and we will end up with a "unified state" that includes all states of all datasources.

If the main purpose of the normalized state is for visualization, then how about we have the following:
- AggregatedState, which is the aggregation of the different states. It can hold any value, depending on the datasource configuration file.
- SimplifiedState or StateCategory, which will be one of {error, warning, ok, unknown}, or in other words red/yellow/green/gray. 
- No normalized state

What do you say?
Ifat.









__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev