[OpenStack-docs] [training-guides] getting down to basics
sean roberts
seanroberts66 at gmail.com
Fri Dec 5 06:44:18 UTC 2014
I have updated the etherpad
https://etherpad.openstack.org/p/training-guides-kilo-summit with sum total
of the blueprints we have discussed. I also went through and created the
blueprints for the ones that still needed one.
Two exceptions.
1. Once we branch juno, we should mark
https://blueprints.launchpad.net/openstack-training-guides/+spec/openstack-training-labs
completed.
2. Line 186 in the etherpad
- Color support for osbash (Labs) (Needs more discussion -- Can it be
more like spec for UI)
I wasn't sure what to do with this. Help me out and explain.
What's next. Volunteers! I have started by putting my name and milestone
objective next to a blueprint on the etherpad. We can have more than one
person sign up for a blueprint. Now your turn.
On Mon, Dec 1, 2014 at 1:26 AM, Roger Luethi <rl at patchworkscience.org>
wrote:
> On Sun, 30 Nov 2014 23:10:19 -0800, sean roberts wrote:
> > - public infra version of the trainer cluster
>
> We have already identified a number of issues that will likely limit the
> usefulness of such a version. The proposed spec has more information:
>
> https://review.openstack.org/#/c/137299/
>
> Before embarking on such an adventure, we would need good answers to at
> least these questions:
>
> a) Is there a need for this? How many trainees have access to hardware
> that cannot run the training-cluster itself but can interact with a
> node VM in a public cloud?
>
> b) Which features of the training cluster need to work in the public
> infra version? Are the trainees just going to play with the dashboard,
> or will they have a shell in the node VM and expect to find the
> exact environement of the training cluster?
>
> > - integration of the trainer cluster into other docs
>
> I don't understand what that means. Can you elaborate?
>
> Roger
>
--
~ sean
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20141204/3c966a9e/attachment.html>
More information about the OpenStack-docs
mailing list