<div dir="ltr">Hi Sean,<div><br></div><div>Regarding your concerns about color support for osbash, we could keep it as a spec. What we plan to cover in this would be having different colors for different type to messages that are seen while running osbash so it enhances the readability of the scripts. We would try to make this color variation compatible with most operating systems. I will add this description to the etherpad too. As of now, I would be experimenting a bit on this feature so we don't know yet what the final outcome would look like and how far we would be interested in expanding it but I guess it could be added as a spec.</div><div><br></div><div>Regards,</div><div>Sayali. </div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 5, 2014 at 12:14 PM, sean roberts <span dir="ltr"><<a href="mailto:seanroberts66@gmail.com" target="_blank">seanroberts66@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">I have updated the etherpad <a href="https://etherpad.openstack.org/p/training-guides-kilo-summit" target="_blank">https://etherpad.openstack.org/p/training-guides-kilo-summit</a> with sum total of the blueprints we have discussed. I also went through and created the blueprints for the ones that still needed one. <div><br></div><div>Two exceptions. </div><div>1. Once we branch juno, we should mark <a href="https://blueprints.launchpad.net/openstack-training-guides/+spec/openstack-training-labs" target="_blank">https://blueprints.launchpad.net/openstack-training-guides/+spec/openstack-training-labs</a> completed. </div><div><br></div><div>2. Line 186 in the etherpad <ul style="margin:0px 0px 0px 1.5em;padding:0px;color:rgb(0,0,0);font-family:Arial,sans-serif;font-size:12px;line-height:16px"><li style="margin:0px;padding:0px"><span style="margin:0px;padding:1px 0px;background-color:rgb(188,236,236)">Color support for osbash (Labs) (Needs more discussion -- Can it be more like spec for UI)</span><span style="margin:0px;padding:1px 0px;background-color:rgb(98,233,182)"> </span></li></ul></div><div class="gmail_extra">I wasn't sure what to do with this. Help me out and explain.</div><div class="gmail_extra"><br></div><div class="gmail_extra">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.</div><div class="gmail_extra"><span class=""><br><div class="gmail_quote">On Mon, Dec 1, 2014 at 1:26 AM, Roger Luethi <span dir="ltr"><<a href="mailto:rl@patchworkscience.org" target="_blank">rl@patchworkscience.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Sun, 30 Nov 2014 23:10:19 -0800, sean roberts wrote:<br>
> - public infra version of the trainer cluster<br>
<br>
</span>We have already identified a number of issues that will likely limit the<br>
usefulness of such a version. The proposed spec has more information:<br>
<br>
<a href="https://review.openstack.org/#/c/137299/" target="_blank">https://review.openstack.org/#/c/137299/</a><br>
<br>
Before embarking on such an adventure, we would need good answers to at<br>
least these questions:<br>
<br>
a) Is there a need for this? How many trainees have access to hardware<br>
that cannot run the training-cluster itself but can interact with a<br>
node VM in a public cloud?<br>
<br>
b) Which features of the training cluster need to work in the public<br>
infra version? Are the trainees just going to play with the dashboard,<br>
or will they have a shell in the node VM and expect to find the<br>
exact environement of the training cluster?<br>
<span><br>
> - integration of the trainer cluster into other docs<br>
<br>
</span>I don't understand what that means. Can you elaborate?<br>
<span><font color="#888888"><br>
Roger<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div></span><span class="HOEnZb"><font color="#888888">-- <br><div><div dir="ltr"><br><div>~ sean</div></div></div>
</font></span></div></div>
<br>_______________________________________________<br>
OpenStack-docs mailing list<br>
<a href="mailto:OpenStack-docs@lists.openstack.org">OpenStack-docs@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs</a><br>
<br></blockquote></div><br></div>