[OpenStack-docs] [training-guides] Team meeting reminder
Matjaz.Pancur at fri.uni-lj.si
Fri Sep 2 09:30:59 UTC 2016
On 01 Sep 2016, at 23:58, Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>> wrote:
We have four potential days to run mini virtual sprints according to the current state of the poll, which are:
* Sept. 6 / Tuesday
* Sept. 12-13 / Monday-Tuesday
* Sept. 16. / Friday
The poll is still open if anyone would like to join us: http://doodle.com/poll/geaq6fdsg749nsnc
I won’t be available for the whole day, but I will join as much as I can. I’ll look at the review queue regularly, though.
I think if we choose a content block and goals wisely we can have great progress in these intervals, I will add proposals to the etherpad (https://etherpad.openstack.org/p/upstream-university-improvements).
@Ian, Matjaz: I’ve lost track a little bit on the Training Guides meetings. It would be great if we could use the slot on Monday for planning regardless we have an actual meeting scheduled or not. Do you think it would be possible?
Yes, absolutely. You can even add specific topics to the official meeting agenda at https://etherpad.openstack.org/p/training-guides-meeting-agenda
I was also thinking to run the meetings weekly in September and first half of October or maybe even until the Summit to check progress and ensure we are coordinated. What do you think?
We switched to biweekly schedule because the attendance at the meetings was low and we wanted to see if biweekly schedule is enough. Fortunately, we still have a reservation for weekly meetings so I see no problems with this.
What do others think? We switch bask to weekly meetings until the Summit?
Thanks and Best Regards,
On 31 Aug 2016, at 19:55, Ildiko Vancsa <ildiko.vancsa at gmail.com<mailto:ildiko.vancsa at gmail.com>> wrote:
Thanks for sharing your availability.
I created a Doodle poll with dates: http://doodle.com/poll/geaq6fdsg749nsnc Anyone who’s interested, please add your availability if you’re interested to participate.
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:
* Updating the common content
* Work on the exercises for the code contribution block
* Work on content and exercises for the Documentation contribution block
* Finalise and test the Dev env.
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.
What do you think?
On 31 Aug 2016, at 05:56, Ian Y. Choi <ianyrchoi at gmail.com<mailto:ianyrchoi at gmail.com>> wrote:
But unfortunately, due to my personal schedule, approximately, Sep 7 12:00 UTC - 9 12:00 UTC will not be available for me.
Would it be okay to have a sprint on around Sep 10-15?
With many thanks,
Ildiko Vancsa wrote on 8/31/2016 2:38 AM:
Thanks for the link for the sprint.
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.
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.
What do you think?
On 30 Aug 2016, at 17:05, Ian Y. Choi <ianyrchoi at gmail.com<mailto:ianyrchoi at gmail.com>> wrote:
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
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,
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.
- There is a warning: "The shared folder 'vagrant' could not be set up:
Shared folder path
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
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" :-)
OpenStack-docs mailing list
OpenStack-docs at lists.openstack.org<mailto:OpenStack-docs at lists.openstack.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-docs