[OpenStack-docs] [training-guides] Team meeting reminder

Ian Y. Choi ianyrchoi at gmail.com
Tue Aug 30 16:03:24 UTC 2016


Mark Korondi1 wrote on 8/31/2016 12:53 AM:
> Hi,
> good idea for the wallpaper!
Yes, wallpaper! That's exactly what I thought. Thanks for expressing 
with a nice word.
> Yeah, a simple iptables rule should be sufficient, however I think the 
> Virtualbox VM settings also need to be tuned for this.
I thought two network interfaces (one: NAT - Internet, the other: 
Host-only - VM access from the host)
and a simple iptable rule would be sufficient. Would this environment 
not be sufficient?


With many thanks,

/Ian
>
>     ----- Original message -----
>     From: "Ian Y. Choi" <ianyrchoi at gmail.com>
>     To: Mark Korondi1 <ORO at zurich.ibm.com>, ildiko.vancsa at gmail.com
>     Cc: openstack-docs at lists.openstack.org,
>     women-of-openstack at lists.openstack.org
>     Subject: Re: [OpenStack-docs] [training-guides] Team meeting reminder
>     Date: Tue, Aug 30, 2016 5:05 PM
>     Hello,
>
>     @Mark,
>
>     For a newcomer, a desktop screen with basic explanation on the
>     environment
>     (e.g., default user ID, default password, "/opt/stack" directory +
>     upstream training logo if it is okay)
>     like http://www.flickr.com/photos/31838982@N08/7798881316/ (I searched
>     on Google) would be nice I think.
>
>     For network connectivity on OpenStack instances, I usually used the
>     following command. I am sure it will work well
>     : $ sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
>
>     @Ildiko,
>
>     IMO testing virtual machine environment is also a good topic for our
>     sprint, so I updated on Etherpad.
>     And will our sprint be a kind virtual sprint, like
>     https://wiki.openstack.org/wiki/VirtualSprints ?
>
>
>     With many thanks,
>
>     /Ian
>
>     Mark Korondi1 wrote on 8/26/2016 4:13 AM:
>     > Thanks Ian for the constructive critique!
>     > Before addressing the issues, I want to ask the others too, if
>     you try
>     > out the image, please think of what *you* as a newcomer would be
>     happy
>     > to start with (firefox bookmarks, editor settings, missing tools
>     which
>     > are not installed, etc.) Especially if there's windows/osx people
>     > here, I'd be happy to hear what would you miss from the VM what you
>     > use on the host machine. Thanks guys!
>     >
>     > - I would recommend to enable "Reinitialize the MAC address of all
>     > network cards" option when importing the virtual appliance using
>     > VirtualBox.
>     > OK, TBD
>     > - There is a warning: "The shared folder 'vagrant' could not be
>     set up:
>     > Shared folder path
>     >
>     '/home/oro/projects/_github.com/kmARC/openstack-training-virtual-environment'
>     > is not absolute."
>     > Yeah, I realized this, will remove
>     >
>     > - It seems that DevStack source is already stored in the OVA
>     file. We
>     > might need to guide users to execute 'git pull' to retrieve the
>     latest
>     > DevStack source.
>     > I'll build the image one or two days before the actual course, so it
>     > won't be a problem.
>     >
>     > - No port forwarding and additional host-only network interface
>     prevent
>     > users from accessing Horizon on users' host OS environment.
>     >   (e.g., the connection from Internet Explorer (out of
>     VirtualBox) to
>     > Horizon (executing in the virtual machine) is not supported.)
>     > On the network side I'll do some more improvements. Now it's not
>     even
>     > possible to start a VM and get networking in it, IIRC
>     >
>     > - If we might use old OVA images during upstream training (as
>     fresh as
>     > possible would be nice but freshest DevStack environment would be so
>     > ideal), then making DevStack offline (using 'OFFLINE=True' option in
>     > local.conf) would be also nice to less use network bandwidth.
>     > Oh, I didn't know about this. We will definitely use it then,
>     thanks!
>     > I try to fix these over the weekend, stay tuned for the next
>     "release" :-)
>     > Mark
>     >
>
>




More information about the OpenStack-docs mailing list