<div dir="ltr"><div><div><div><div><div><div>Hi, all<br><br></div>Thanks for your attention and proposals for this hackathon. With full understanding that optimization of deployment is on-going effort and should not be started and finished in these 2 days only, we still want to get focus on these issues in the sprint. Even if we don't solve immediately all problems, more people will be exposed to this field, additional tasks/bugs could be opened and scheduled, and maybe additional tests, process improvements and other insights will be introduced.<br></div>If we don't reduce ci job time to 1 hour in Thursday it doesn't mean we failed the mission, please remember.<br></div>The main goal of this sprint is to find problems and their work scope, and to find as many as possible solutions for them, using inter-team and team members collaboration and sharing knowledge. Ideally this collaboration and on-going effort will go further with such momentum. :)<br><br></div>I suggest to do it in 21 - 22 Jun 2017 (Wednesday - Thursday). All other details are provided in etherpad: <a href="https://etherpad.openstack.org/p/tripleo-deploy-time-hack">https://etherpad.openstack.org/p/tripleo-deploy-time-hack</a> and in wiki as well: <a href="https://wiki.openstack.org/wiki/VirtualSprints">https://wiki.openstack.org/wiki/VirtualSprints</a><br></div><div>We have a "deployment-time" tag for bugs:<span class="gmail-"> </span><span class="gmail-url"><a href="https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time">https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time</a> Please use it for bugs that affect deployment time or CI job run time. It will be easier to handle them in the sprint.<br></span></div><div><br></div>Please provide your comments and suggestions.<br><br></div>Thanks<br><div><div><div><br><div><div><br></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman <span dir="ltr"><<a href="mailto:sshnaidm@redhat.com" target="_blank">sshnaidm@redhat.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"><div><div><div><div><div>Hi, all<br><br></div>I'd like to propose an idea to make one or two days hackathon in TripleO project with main goal - to reduce deployment time of TripleO.<br><br></div>- How could it be arranged?<br><br>We can arrange a separate IRC channel and Bluejeans video conference session for hackathon in these days to create a "presence" feeling.<br><br><div>- How to participate and contribute?<br></div><div><br></div>We'll
have a few responsibility fields like tripleo-quickstart, containers, storage, HA,
baremetal, etc - the exact list should be ready before the hackathon so
that everybody could assign to one of these "teams". It's good to have
somebody in team to be stakeholder and responsible for organization and tasks.<br><br></div>- What is the goal?<br><br></div><div>The goal of this hackathon to reduce deployment time of TripleO as much as possible.<br><br><div>For example part of CI team takes a task to reduce quickstart tasks
time. It includes statistics collection, profiling and detection of
places to optimize. After this tasks are created, patches are tested and submitted.<br></div><div><br></div></div></div><div>The prizes will be presented to teams which saved most of time :)<br></div><div><div><div><div><div><div><div><br clear="all"><div><div>What do you think?<br><br></div><div>Thanks<span class="HOEnZb"><font color="#888888"><br></font></span></div><span class="HOEnZb"><font color="#888888"><div>-- <br><div class="m_6351451213497434415m_966914930401610820gmail_signature"><div dir="ltr"><div>Best regards<br></div>Sagi Shnaidman<br></div></div>
</div></font></span></div></div></div></div></div></div></div></div></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Best regards<br></div>Sagi Shnaidman<br></div></div>
</div>