Adam Spiers

[**@aspiers**](https://github.com/aspiers) commented on [March 31, 2019 1:26 PM](https://github.com/crowbar/crowbar-openstack/pull/2063#issuecomment-478365873 "2019-03-31T18:26:29Z - Replied by Github Reply Comments"): > But the main problem seems to be that the CI is currently failing: [snipped]...

Just realised the main part of this change was totally unnecessary - dropped.

@rsalevsky I would prefer the opposite, because they have no goals or code in common.

> We save the duplicated code for the gem definition. I agree that's a benefit, but only a very small one which is outweighed by the other considerations below: >...

Rebased

This is **not** ready for merging due to the breakage referenced above.

Still WIP, but marked by a label now.

@nicolasbock Removed my -1. I can't give +1 because I don't even understand why autoyast would need to self-update :-) If there's newer autoyast code then why wouldn't it be...

Two more thoughts: 1. The answer given to "Why is this change necessary?" was "Speed up the chef-client execution", but IIUC that's not precisely what's happening; it's actually *reducing* the...

And another: 3. Orchestration is [hard](https://etherpad.nue.suse.com/p/cloud-orchestration) ;-/