Open Stack

It's great to have this available!  I think it'll help people understand
what's going on MUCH more quickly.

Some thoughts.
- The image is 3GB, which took me 30 minutes to download.  Are all VMs this
big?  I think we should finish this as a VM but then look into doing it
with containers to make it EVEN easier for people to get started.

- It gave me an error about a missing shared directory when I started up.

- I expected devstack to be running when I launched the VM.  devstack
startup time is substantial, and if there's a problem, it's good to assume
the user won't know how to fix it.  Is it possible to have devstack up and
running when we start the VM?  That said, it started up fine for me.

- It'd be good to have a README to explain how to use the use-case
structure. It wasn't obvious to me.

- The top-level dir of the Congress_Usecases folder has a Congress_Usecases
folder within it.  I assume the inner one shouldn't be there?

- When I ran the 10_install_policy.sh, it gave me a bunch of authorization
problems.

But otherwise I think the setup looks reasonable.  Will there be an undo
script so that we can run the use cases one after another without worrying
about interactions?

Tim


On Fri, Sep 18, 2015 at 11:03 AM Shiv Haris <sharis at brocade.com> wrote:

> Hi Congress folks,
>
>
>
> BTW the login/password for the VM is vagrant/vagrant
>
>
>
> -Shiv
>
>
>
>
>
> *From:* Shiv Haris [mailto:sharis at Brocade.com]
> *Sent:* Thursday, September 17, 2015 5:03 PM
> *To:* openstack-dev at lists.openstack.org
> *Subject:* [openstack-dev] [Congress] Congress Usecases VM
>
>
>
> Hi All,
>
>
>
> I have put my VM (virtualbox) at:
>
>
>
> http://paloaltan.net/Congress/Congress_Usecases_SEPT_17_2015.ova
>
>
>
> I usually run this on a macbook air – but it should work on other
> platfroms as well. I chose virtualbox since it is free.
>
>
>
> Please send me your usecases – I can incorporate in the VM and send you an
> updated image. Please take a look at the structure I have in place for the
> first usecase; would prefer it be the same for other usecases. (However I
> am still open to suggestions for changes)
>
>
>
> Thanks,
>
>
>
> -Shiv
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150919/e9a8f096/attachment.html>