hi @ChrisRohrer thanks for the quick sketch - this is very useful. I have lots of comments, so see below
I can't remember if we're going to have a "directional" training, or an open-ended training, for the hands on part.If we are going to jhave a direction, or an endpoint, we should make that clear in the introduction bit. This should include e.g. learning outcomes and skills acquired.
- You mean an X.509 cert or an ssh public key ? (I'm assuming public key) ?
- Ah - good point - which servers are we going to be using ? Is there going to be a ubuntunet cloud that we're going to use for the training ?
This is basically the git-novice lesson from Software Carpentry. I suggest we just have the attendees read the lesson before coming, then go through the steps that apply to us ? What do you think @ChrisRohrer ?
Also - what is the point of this github lesson ? I'm assuming that we're going to have the attendees use their repos for developing their playbooks and roles ?
I'm a little hesitant to do the "create org" bit - this is unnecessary overhead I think. In the interest of developing community, they could rather join an existing org like AAROC or UbuntuNet.
I start from a more general "what is DevOps" point, and then have two levels of Ansible nastiness in the previous course. The slides in there need to be updated for v2.1 onwards - things like debugging strategies, dynamic inventories, blocks, etc. The installation is also far smoother with pip, and the base containers for Ansible are available now.
We should discuss whether we want Docker to form an integral part of the training or not - ie, what kind of prerequisite knowledge should they have about how containers work. We probably won't have time to train people about Docker (that's a whole other bootcamp), so if they are by and large ignorant of it, we need to just do a demo or something.
So, I'm assuming I'm responsible for Day 1 then, right ?
And you are responsible for Day 2 ?
Are the projects described in the survey responses ? Do we have the possibility to suggest projects ?
I would try to stick to one kind of contextualisation. Either vagrant or Docker ... yes, they do slightly different things, etc, but we risk to confuse the daylights out of people if we mix and match things.
Ansible also provides a built-in means for orchestrating containers with playbooks - ansible-container. In my experience so far, it isn't trivial to use, you need to be a bit of an expert, but if you're using Docker Compose then things fit together nicely. This is also a good way to avoid the huge Dockerfile antipattern. There are many antipatterns which could be discussed if we decide to have containers included in the bootcamp.
IMHO they are really important for testing, and testing is part of the DevOps triangle, so we should explicitly include it.
Yes, yes yes. Let's just pick out the relevant bits of the Mozilla Working Open Workshop which does this kind of thing really well.
Lastly- do we have an indico page for the event yet ?