[openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO
emilien at redhat.com
Mon Jun 19 21:30:08 UTC 2017
Reminder: the sprint will start on Wednesday of this week.
- /join #openstack-sprint
- tag relevant bugs in Launchpad to be found on
- create new bugs related to performances and tag them.
Anyone is welcome to join the sprint, feel free to ping me or Sagi if
any question or feedback,
On Thu, Jun 8, 2017 at 10:44 AM, Emilien Macchi <emilien at redhat.com> wrote:
> On Thu, Jun 8, 2017 at 4:19 PM, Sagi Shnaidman <sshnaidm at redhat.com> wrote:
>> Hi, all
>> 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.
>> If we don't reduce ci job time to 1 hour in Thursday it doesn't mean we
>> failed the mission, please remember.
>> 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. :)
>> I suggest to do it in 21 - 22 Jun 2017 (Wednesday - Thursday). All other
>> details are provided in etherpad:
>> https://etherpad.openstack.org/p/tripleo-deploy-time-hack and in wiki as
>> well: https://wiki.openstack.org/wiki/VirtualSprints
>> We have a "deployment-time" tag for bugs:
>> https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time Please
>> use it for bugs that affect deployment time or CI job run time. It will be
>> easier to handle them in the sprint.
>> Please provide your comments and suggestions.
> Thanks Sagi for bringing this up, this is really awesome.
> One thing we could do to make this sprint productive is to report /
> triage Launchpad bugs related to $topic so we have a list of things we
> can work on during these 2 days.
> Maybe we could go through:
> https://launchpad.net/tripleo/+milestone/pike-3 and add
> deployment-time to all the bugs we think it's related to performances.
> Once we have the list, we'll work on them by priority and by area of knowledge.
> Also, folks like face to face interactions. We'll take care of
> preparing an open Bluejeans where folks can easily join and ask
> questions. We'll probably be connected all day, so anyone can join
> anytime. No schedule constraint here.
> Any feedback is welcome,
>> On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman <sshnaidm at redhat.com> wrote:
>>> Hi, all
>>> 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.
>>> - How could it be arranged?
>>> We can arrange a separate IRC channel and Bluejeans video conference
>>> session for hackathon in these days to create a "presence" feeling.
>>> - How to participate and contribute?
>>> 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.
>>> - What is the goal?
>>> The goal of this hackathon to reduce deployment time of TripleO as much as
>>> 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.
>>> The prizes will be presented to teams which saved most of time :)
>>> What do you think?
>>> Best regards
>>> Sagi Shnaidman
>> Best regards
>> Sagi Shnaidman
> Emilien Macchi
More information about the OpenStack-dev