Open Stack

On Fri, May 10, 2019 at 11:55 AM Chris Dent <cdent+os at anticdent.org> wrote:
> > * Nate Johnston asked about supporting bulk create APIs, such as
> > Neutron's bulk port create.  After kicking around a couple of options
> > the rough consensus is around using a YAML file (or JSON or both?) to
> > define the resources to be created and giving it to a new top-level
> > 'create' command (yes, verb only, the resource names will be in the
> > YAML file).
>
> +∞
>
> There are presumably some error handling issues with that, but
> overall something like this would be very useful.

I should admit that during this conversation I was well down the path
of re-creating Ansible before I realized it... that is part of the
reason we want to start with a simplistic equivalent to shell's 'set
-e' and let the user sort it out.

Note that the delete command pattern is different in that it attempts
them all once and returns a list of failures if any.  I am certainly
open to discussion on the preferred way to address errors without
inventing complicated retry mechanisms; my feeling is if you need
those use Ansible and the SDK directly.

dt

-- 
Dean Troyer
dtroyer at gmail.com