Open Stack

I was able to make devstack run without a network connection by disabling tempest.  So, I think it uses the loopback IP address, and that does not change, so rejoin-stack.sh works without a network at all.


- Alex



________________________________
From: Zhou, Zhenzan <zhenzan.zhou at intel.com>
Sent: Thursday, September 24, 2015 4:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Congress Usecases VM

Rejoin-stack.sh works only if its IP was not changed. So using NAT network and fixed ip inside the VM can help.

BR
Zhou Zhenzan

From: Alex Yip [mailto:ayip at vmware.com]
Sent: Friday, September 25, 2015 01:37
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Congress Usecases VM


I have been using images, rather than snapshots.



It doesn't take that long to start up.  First, I boot the VM which takes a minute or so.  Then I run rejoin-stack.sh which takes just another minute or so.  It's really not that bad, and rejoin-stack.sh restores vms and openstack state that was running before.



- Alex





________________________________
From: Shiv Haris <sharis at Brocade.com<mailto:sharis at Brocade.com>>
Sent: Thursday, September 24, 2015 10:29 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Congress Usecases VM

Hi Congress folks,

I am looking for ideas. We want the Openstack to be running when the user instantiates the Usecase-VM. However creating a OVA file is possible only when the VM is halted which means Openstack is not running and the user will have to run devstack again (which is time consuming) when the VM is restarted.

The option is to take a snapshot. It appears that taking a snapshot of the VM and using it in another setup is not very straight forward. It involves modifying the .vbox file and seems that it is prone to user errors. I am leaning towards halting the machine and generating an OVA file.

I am looking for suggestions ….

Thanks,

-Shiv


From: Shiv Haris [mailto:sharis at Brocade.com]
Sent: Thursday, September 24, 2015 9:53 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Congress Usecases VM

First of all I apologize for not making it at the meeting yesterday, could not cut short another overlapping meeting.

Also, Tim thanks for the feedback. I have addressed some of the issues you posed however I am still working on some of the subtle issues raised. Once I have addressed all I will post another VM by end of the week.

-Shiv


From: Tim Hinrichs [mailto:tim at styra.com]
Sent: Friday, September 18, 2015 5:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Congress] Congress Usecases VM

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.

[shivharis] Yes, unfortunately that is the case. The disk size I set is 20GB – but the OVA compress the image and disk to 3 GB. I will looking at other options.


- It gave me an error about a missing shared directory when I started up.
[shivharis] will fix this

- 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.
[shivharis] OVA files can be created only when the VM is halted, so devstack will be down when you bring up  the VM. I agree a snapshot will be a better choice.

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

- 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?
[shivharis] my automation issues, fixed.

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

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?
[shivharis] tricky, will find some way out.

Tim

[shivharis] Thanks

On Fri, Sep 18, 2015 at 11:03 AM Shiv Haris <sharis at brocade.com<mailto: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<mailto:sharis at Brocade.com>]
Sent: Thursday, September 17, 2015 5:03 PM
To: openstack-dev at lists.openstack.org<mailto: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<https://urldefense.proofpoint.com/v2/url?u=http-3A__paloaltan.net_Congress_Congress-5FUsecases-5FSEPT-5F17-5F2015.ova&d=BQMGaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=djA1lFdIf0--GIJ_8gr44Q&m=3IP4igrLri-BaK8VbjbEq2l_AGknCI7-t3UbP5VwlU8&s=wVyys8I915mHTzrOp8f0KLqProw6ygNfaMSP0T-yqCg&e=>

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://OpenStack-dev-request@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/20150925/52adf968/attachment.html>