Open Stack

On Thu, Dec 6, 2018 at 4:56 PM Matt Riedemann <mriedemos at gmail.com> wrote:

> On 12/6/2018 12:10 PM, Melvin Hillsman wrote:
> > After many discussions it seems SDK validation essentially should be
> > about confirming cloud state pre/post SDK interaction rather than API
> > support. An example is that when I use pkgcloud and ask that a VM be
> > created, does the VM exist, in the way I asked it exist, rather than are
> > there specific API calls that are being hit along the way to creating my
> VM.
> >
> > I am putting this email out to keep the community informed of what has
> > been discussed in this space but also and most importantly to get
> > feedback and support for this work. It would be great to get a set of
> > official and community SDKs, get them setup with CI testing for
> > validation (not changing their current CI for unit/functional/acceptance
> > testing; unless asked to help do this), and connect the results to the
> > updated project navigator SDK section. A list of scenarios has been
> > provided as a good starting point for cloud state checks.[2]
> >
> > Essentially the proposal is to deploy OpenStack from upstream (devstack
> > or other), stand up a VM within the cloud, grab all the SDKs, run
> > acceptance tests, report pass/fail results, update project navigator. Of
> > course there are details to be worked out and I do have a few questions
> > that I hope would help get everyone interested on the same page via this
> > thread.
> >
> >  1. Does this make sense?
>
> Makes sense to me. Validating the end result of some workflow makes
> sense to me. One thing I'm wondering about is what you'd start with for
> basic scenarios. It might make sense to start with some of the very
> basic kinds of things that openstack interoperability certification
> requires, like create a VM, attach a volume and port, and then delete it
> all. Then I guess you'd build from there?
>

Yes sir the scenarios you mention are exactly what we have in the
spreadsheet and want to add more. I did not think about it but maybe this
ethercalc is better for everyone to collaborate on -
https://ethercalc.org/q4nklltf21nz


>
> >
> >  2. Would folks be interested in a SDK SIG or does it make more sense to
> >     request an item on the API SIG's agenda?
>
> No opinion.
>
> >
> >  3. Bi-weekly discussions a good cadence?
>
> Again no opinion but I wanted to say thanks for communicating this for
> others less involved in this space - it's good to know *something* is
> going on.
>
> >
> >  4. Who is interested in tackling this together?
>
> Again, no real opinion from me. :) Hopefully that other person that I
> just saw run away over there...
>
> --
>
> Thanks,
>
> Matt
>
>

-- 
Kind regards,

Melvin Hillsman
mrhillsman at gmail.com
mobile: (832) 264-2646
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20181206/58c0f824/attachment.html>