Open Stack

Once we have some more discussions on self-healing, it would be a good idea to put together an architecture framework and then see which of the current OpenStack projects can fill in the gaps. Also, I hope the discussions results in a set of requirements that can be communicated to all projects and determine what features or capabilities will help us to meet the self-healing objectives.

Nemat 

-----Original Message-----
From: Tim Bell [mailto:Tim.Bell at cern.ch] 
Sent: Tuesday, November 28, 2017 1:05 PM
To: openstack-sigs at lists.openstack.org
Subject: Re: [Openstack-sigs] [self-healing] Storyboard for tracking SIG actions?


While Storyboard may not give us all we need immediately, there seemed to be a general interest to get it to a point where it could meet the communities’ needs. So, if we encounter areas for improvement, we have a chance to get those done. Sometimes, the requests for enhancement when we’re using the ‘community open source’ version of other software can be more difficult.

I’m tempted to give storyboard a go.. at minimum, we’ll get some new requirements they may like to consider for future effort which would help other SIGs following similar paths to self-healing in future.

Tim

-----Original Message-----
From: Adam Spiers <aspiers at suse.com>
Reply-To: "openstack-sigs at lists.openstack.org" <openstack-sigs at lists.openstack.org>
Date: Tuesday, 28 November 2017 at 21:43
To: "openstack-sigs at lists.openstack.org" <openstack-sigs at lists.openstack.org>
Subject: Re: [Openstack-sigs] [self-healing] Storyboard for tracking SIG actions?

    Tim Bell <Tim.Bell at cern.ch> wrote:
    >One of the benefits I would see of using Storyboard is that the
    >self-healing SIG will be working with many, many OpenStack projects
    >(since the main work is integrating the functionalities).
    >
    >As some of these will be using Storyboard (either in the short or
    >long term), this would improve our chances of building up appropriate
    >epics without duplicating the action items across multiple systems.
    >
    >Choosing the tools completely independently could risk that we end up
    >having to learn all of them.
    
    Very good point, Tim.  My main hesitation with Storyboard was simply
    ignorance over whether it is ready for serious use yet (and that's
    despite a vague memory of Thierry answering that question recently
    when I asked it ...)
    
    But Storyboard seems to have come on hugely since I last looked at it,
    so most likely my knowledge was simply out of date.  If it is indeed
    ready, I'm more than happy to give it a go.
    
    That said, it seems to be based on the assumption that all work is
    associated with at least one project (i.e. git repo).  Is there a way
    to make it work for a SIG which has no corresponding git repo?
    
    _______________________________________________
    openstack-sigs mailing list
    openstack-sigs at lists.openstack.org
    http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs
    

_______________________________________________
openstack-sigs mailing list
openstack-sigs at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-sigs