<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Ian,<div class=""><br class=""></div><div class="">Thanks for sharing your availability.</div><div class=""><br class=""></div><div class="">I created a Doodle poll with dates: <a href="http://doodle.com/poll/geaq6fdsg749nsnc" class="">http://doodle.com/poll/geaq6fdsg749nsnc</a> Anyone who’s interested, please add your availability if you’re interested to participate.</div><div class=""><br class=""></div><div class="">I think we can aim for multiple shorter periods rather than one long one as we have multiple areas to improve. I would like to have well defined areas like:</div><div class=""><br class=""></div><div class="">* Updating the common content</div><div class="">* Work on the exercises for the code contribution block</div><div class="">* Work on content and exercises for the Documentation contribution block</div><div class="">* Finalise and test the Dev env.</div><div class="">* Etc.</div><div class=""><br class=""></div><div class="">If possible it would be great to have drivers for each of these blocks. We can then decide based on people’s availability to what to work on in a more focused way and when and we also need to define goals to see what progress we made.</div><div class=""><br class=""></div><div class="">What do you think?</div><div class=""><br class=""></div><div class="">Thanks,</div><div class="">Ildikó</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 31 Aug 2016, at 05:56, Ian Y. Choi <<a href="mailto:ianyrchoi@gmail.com" class="">ianyrchoi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello Ildiko,<br class=""><br class="">Great!<br class=""><br class="">But unfortunately, due to my personal schedule, approximately, Sep 7 12:00 UTC - 9 12:00 UTC will not be available for me.<br class=""><br class="">Would it be okay to have a sprint on around Sep 10-15?<br class=""><br class=""><br class="">With many thanks,<br class=""><br class="">/Ian<br class=""><br class="">Ildiko Vancsa wrote on 8/31/2016 2:38 AM:<br class=""><blockquote type="cite" class="">Hi Ian,<br class=""><br class="">Thanks for the link for the sprint.<br class=""><br class="">I think we can make it 100% official and post on the wiki page as well. The idea is to have dedicated time, when we focus on content, exercises, environment, etc. We need to decide the scope and define goals for the sprint and work on to achieve those.<br class=""><br class="">After talking to a few people mid- or second half of next week seems like a good target, e.g. Sept 6-8 or 7-9. I think that gives us enough time to figure out the sprint goals and it’s still in time from the Summit/training perspective, so we can either have another round of this if needed or work more offline on remaining items.<br class=""><br class="">What do you think?<br class=""><br class="">Best Regards,<br class="">Ildikó<br class=""><br class=""><blockquote type="cite" class="">On 30 Aug 2016, at 17:05, Ian Y. Choi <<a href="mailto:ianyrchoi@gmail.com" class="">ianyrchoi@gmail.com</a>> wrote:<br class=""><br class="">Hello,<br class=""><br class="">@Mark,<br class=""><br class="">For a newcomer, a desktop screen with basic explanation on the environment<br class="">(e.g., default user ID, default password, "/opt/stack" directory + upstream training logo if it is okay)<br class="">like <a href="http://www.flickr.com/photos/31838982@N08/7798881316/" class="">http://www.flickr.com/photos/31838982@N08/7798881316/</a> (I searched on Google) would be nice I think.<br class=""><br class="">For network connectivity on OpenStack instances, I usually used the following command. I am sure it will work well<br class="">: $ sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE<br class=""><br class="">@Ildiko,<br class=""><br class="">IMO testing virtual machine environment is also a good topic for our sprint, so I updated on Etherpad.<br class="">And will our sprint be a kind virtual sprint, like <a href="https://wiki.openstack.org/wiki/VirtualSprints" class="">https://wiki.openstack.org/wiki/VirtualSprints</a> ?<br class=""><br class=""><br class="">With many thanks,<br class=""><br class="">/Ian<br class=""><br class="">Mark Korondi1 wrote on 8/26/2016 4:13 AM:<br class=""><blockquote type="cite" class="">Thanks Ian for the constructive critique!<br class="">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!<br class=""><br class="">- I would recommend to enable "Reinitialize the MAC address of all<br class="">network cards" option when importing the virtual appliance using VirtualBox.<br class="">OK, TBD<br class="">- There is a warning: "The shared folder 'vagrant' could not be set up:<br class="">Shared folder path<br class="">'/home/oro/projects/_<a href="http://github.com/kmARC/openstack-training-virtual-environment'" class="">github.com/kmARC/openstack-training-virtual-environment'</a><br class="">is not absolute."<br class="">Yeah, I realized this, will remove<br class=""><br class="">- It seems that DevStack source is already stored in the OVA file. We<br class="">might need to guide users to execute 'git pull' to retrieve the latest<br class="">DevStack source.<br class="">I'll build the image one or two days before the actual course, so it won't be a problem.<br class=""><br class="">- No port forwarding and additional host-only network interface prevent<br class="">users from accessing Horizon on users' host OS environment.<br class=""> (e.g., the connection from Internet Explorer (out of VirtualBox) to<br class="">Horizon (executing in the virtual machine) is not supported.)<br class="">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<br class=""><br class="">- If we might use old OVA images during upstream training (as fresh as<br class="">possible would be nice but freshest DevStack environment would be so<br class="">ideal), then making DevStack offline (using 'OFFLINE=True' option in<br class="">local.conf) would be also nice to less use network bandwidth.<br class="">Oh, I didn't know about this. We will definitely use it then, thanks!<br class="">I try to fix these over the weekend, stay tuned for the next "release" :-)<br class="">Mark<br class=""><br class=""></blockquote></blockquote></blockquote><br class=""></div></div></blockquote></div><br class=""></div></body></html>