Open Stack

On Mon, Jun 3, 2019, at 8:15 AM, Mohammed Naser wrote:
> On Mon, Jun 3, 2019 at 11:05 AM Clark Boylan <cboylan at sapwetik.org> wrote:
> > On Sat, Jun 1, 2019, at 5:36 AM, Mohammed Naser wrote:

snip

> > > I will try to pick up sometime to POC a simple service being deployed
> > > by an OSA role instead of Bash, placement which seems like a very
> > > simple one and share that eventually.
> > >
> > > Thoughts? :)
> >
> > For me there are two major items to consider that haven't been brought up yet. The first is devstack's (lack of) speed. Any replacement should be at least as quick as the current tooling because the current tooling is slow enough already. The other is logging. I spend a lot of time helping people to debug CI job runs and devstack has grown a fairly effective set of logging that just about any time I have to help debug another deployment tool's CI jobs I miss (because they tend to log only a tiny fraction of what devstack logs).
> 
> The idea is *not* to use OpenStack Ansible to deploy DevStack, it's to
> use the roles
> to deploy the specific services.  Therefore, the log collection stuff
> should all still
> be the same, as long as it pulls down the correct systemd unit (which should
> be matching).

I know. I'm saying the logging that these other systems produce is typically lacking compared to devstack. So any change needs to address that.

> 
> The idea that it should be 100% transparent to the user at the end of
> the day, there
> should be no functional changes in how DevStack runs or what it logs
> in the gate.

If this is the plan then the logging concerns should be addressed as part of the "don't make it noticeable change" work.

Clark