Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Emilien Macchi]

Reminder: the sprint is starting today:

- /join #openstack-sprint
- tag relevant bugs in Launchpad to be found on
https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time
- 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,

Thanks!

On Mon, Jun 19, 2017 at 5:30 PM, Emilien Macchi  wrote:
> Reminder: the sprint will start on Wednesday of this week.
>
> Actions required:
>
> - /join #openstack-sprint
> - tag relevant bugs in Launchpad to be found on
> https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time
> - 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,
>
> Thanks!
>
> On Thu, Jun 8, 2017 at 10:44 AM, Emilien Macchi  wrote:
>> On Thu, Jun 8, 2017 at 4:19 PM, Sagi Shnaidman  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-2
>> 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,
>>
>> Thanks!
>>
>>> Thanks
>>>
>>>
>>>
>>> On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman  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
 possible.

 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?

 Thanks
 --
 Best regards
 Sagi Shnaidman
>>>
>>>
>>>
>>>
>>> --
>>> Best regards
>>> Sagi Shnaidman
>>
>>
>>
>> --
>> Emilien Macchi
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage 

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Emilien Macchi]

Reminder: the sprint will start on Wednesday of this week.

Actions required:

- /join #openstack-sprint
- tag relevant bugs in Launchpad to be found on
https://bugs.launchpad.net/tripleo/+bugs?field.tag=deployment-time
- 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,

Thanks!

On Thu, Jun 8, 2017 at 10:44 AM, Emilien Macchi  wrote:
> On Thu, Jun 8, 2017 at 4:19 PM, Sagi Shnaidman  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-2
> 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,
>
> Thanks!
>
>> Thanks
>>
>>
>>
>> On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman  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
>>> possible.
>>>
>>> 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?
>>>
>>> Thanks
>>> --
>>> Best regards
>>> Sagi Shnaidman
>>
>>
>>
>>
>> --
>> Best regards
>> Sagi Shnaidman
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Emilien Macchi]

On Thu, Jun 8, 2017 at 4:19 PM, Sagi Shnaidman  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-2
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,

Thanks!

> Thanks
>
>
>
> On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman  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
>> possible.
>>
>> 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?
>>
>> Thanks
>> --
>> Best regards
>> Sagi Shnaidman
>
>
>
>
> --
> Best regards
> Sagi Shnaidman



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Sagi Shnaidman]

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



On Tue, May 23, 2017 at 1:47 PM, Sagi Shnaidman  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
> possible.
>
> 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?
>
> Thanks
> --
> Best regards
> Sagi Shnaidman
>



-- 
Best regards
Sagi Shnaidman
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Bogdan Dobrelya]

On 25.05.2017 0:08, Jeremy Stanley wrote:
> On 2017-05-24 16:27:18 -0500 (-0500), Ben Nemec wrote:
> [...]
>> I spent a _lot_ of time tracking down performance issues and
>> optimizing things where I could, and in the end pretty much every
>> gain I made was regressed somewhere else within a few weeks,
>> leaving us where we are now with jobs timing out all over the
>> place.
> [...]
> 
> The uneasy truth (in many places, not just TripleO) is that if
> people only try to improve speed or memory footprint or what have
> you when jobs are constantly hitting those thresholds, then the
> gains will usually only be very temporary. I agree it has to be an
> all-the-time effort to work on minimization across these axes or
> else we'll end up with near constant job failures from them. Under
> development, software will (often rapidly) grow to fill the resource
> constraints placed around it. There's some sort of natural law at
> work there.
> 

Great topic, and a huge effort #deployment-time! Thank you for raising
this. Few more inputs and random thoughts:
[0] - Lightening undercloud MAV to save Mark Watney once again
[1] - There is a strange nerdish joy with (never ending) adjusting of
tests matrix and chaining builds promotion pipelines.

[0] https://bugs.launchpad.net/tripleo/+bug/1693448
[1] https://bugs.launchpad.net/tripleo/+bug/1693435

-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Jeremy Stanley]

On 2017-05-24 16:27:18 -0500 (-0500), Ben Nemec wrote:
[...]
> I spent a _lot_ of time tracking down performance issues and
> optimizing things where I could, and in the end pretty much every
> gain I made was regressed somewhere else within a few weeks,
> leaving us where we are now with jobs timing out all over the
> place.
[...]

The uneasy truth (in many places, not just TripleO) is that if
people only try to improve speed or memory footprint or what have
you when jobs are constantly hitting those thresholds, then the
gains will usually only be very temporary. I agree it has to be an
all-the-time effort to work on minimization across these axes or
else we'll end up with near constant job failures from them. Under
development, software will (often rapidly) grow to fill the resource
constraints placed around it. There's some sort of natural law at
work there.
-- 
Jeremy Stanley

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Ben Nemec]

On 05/23/2017 05:47 AM, Sagi Shnaidman 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 possible.

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?


I'm happy to see this get more attention, and I will take this 
opportunity to point out 
http://blog.nemebean.com/content/improving-tripleo-ci-throughput which 
discusses the work I did a few months ago to decrease the ci wall time. 
Some of that was ci-specific, some of it was general bugs in TripleO 
performance.


However, the important thing to note is the last couple of paragraphs. 
I spent a _lot_ of time tracking down performance issues and optimizing 
things where I could, and in the end pretty much every gain I made was 
regressed somewhere else within a few weeks, leaving us where we are now 
with jobs timing out all over the place.


I guess my point is two-fold: 1) I'm not sure a day or two sprint is 
going to be sufficient to dig into and fix the performance of TripleO. 
Maybe if there's some low-hanging fruit.  2) It's certainly not going to 
be sufficient to keep TripleO performance at an acceptable level 
long-term.  This will have to be an ongoing effort, and we badly need 
the tracking previously provided by our graphite metrics.  Without hard 
numbers on what is regressing we don't know what to look at.  Related: 
https://review.openstack.org/#/c/462980


-Ben

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Marios Andreou]

On Tue, May 23, 2017 at 4:40 PM, Emilien Macchi  wrote:

> On Tue, May 23, 2017 at 6:47 AM, Sagi Shnaidman 
> 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.
>
> +1 for IRC. We already have #openstack-sprint, that we could re-use.
> Also +1 for video conference, to get face to face interactions,
> promptly and unscheduled.
>
> > - 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.
>
> Before running the sprint, we should first track bugs / blueprints
> related to deployment speed.
> Not everyone in our team understands why some parts of deployments
> take time, so we need to make it visible so everyone can know how they
> can help during the sprint.
>
> Maybe we could create a Launchpad tag "deployment-time" to track bugs
> related to it. We should also make prioritization so we can work on
> the most critical ones first.
>
> I like the idea of breaking down the skills into small groups:
>
> - High Availability: deployment & runtime of Pacemaker optimization
> - Puppet: anything related to the steps (a bit more general but only a
> few of us have expertise on it, we could improve it).
> - Heat: work with the Heat team if we have some pending bugs about
> slowness.
> - Baremetal: ironic / workflows
> - tripleo-quickstart: tasks that can be improved / optimized
>
> This is a proposal ^ feel free to (comment,add|remove) anything.
>
>
> > - What is the goal?
> >
> > The goal of this hackathon to reduce deployment time of TripleO as much
> as
> > possible.
> >
> > 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?
>
>
o/ Sagi - fwiw I really like the idea - like a remote project gathering...
especially having an open bluejeans session (I'd still do that even if an
irc chan is the preferred medium for the hackathon in the end) and I also
like the topic.

Personally I will find it hard to block-book a day (for example) to work on
this particular thing - depending on where we are in the cycle/current BZ
or customer cases etc etc and that is the main reason I wouldn't be able to
participate - at least not for the whole thing, but would at least try to
track it  (Even if I could block book a day it would probably be hard to
match the day that other folks can do it). I guess if you've gone to the
trouble of filing the bugs/blueprints and the 'deployment-time' tag as
suggested by Emilien then in in the worst case this effort can proceed in
the 'usual' way (gerrit,mailing list etc).

thanks


> Excellent idea, thanks Sagi for proposing it.
>
> Another thought: before doing the sprint, we might want to make sure
> our tripleo-ci is in stable shape (which is not the case right now, we
> have 4 alerts and one of them affects ovb-ha)...
>
> > Thanks
> > --
> > Best regards
> > Sagi Shnaidman
>
>
>
> --
> Emilien Macchi
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Emilien Macchi]

On Tue, May 23, 2017 at 9:40 AM, Emilien Macchi  wrote:
> On Tue, May 23, 2017 at 6:47 AM, Sagi Shnaidman  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.
>
> +1 for IRC. We already have #openstack-sprint, that we could re-use.
> Also +1 for video conference, to get face to face interactions,
> promptly and unscheduled.
>
>> - 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.
>
> Before running the sprint, we should first track bugs / blueprints
> related to deployment speed.
> Not everyone in our team understands why some parts of deployments
> take time, so we need to make it visible so everyone can know how they
> can help during the sprint.
>
> Maybe we could create a Launchpad tag "deployment-time" to track bugs
> related to it. We should also make prioritization so we can work on
> the most critical ones first.

Proposed here: https://review.openstack.org/467335
Discussion can happen in Gerrit for this one.

> I like the idea of breaking down the skills into small groups:
>
> - High Availability: deployment & runtime of Pacemaker optimization
> - Puppet: anything related to the steps (a bit more general but only a
> few of us have expertise on it, we could improve it).
> - Heat: work with the Heat team if we have some pending bugs about slowness.
> - Baremetal: ironic / workflows
> - tripleo-quickstart: tasks that can be improved / optimized
>
> This is a proposal ^ feel free to (comment,add|remove) anything.
>
>
>> - What is the goal?
>>
>> The goal of this hackathon to reduce deployment time of TripleO as much as
>> possible.
>>
>> 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?
>
> Excellent idea, thanks Sagi for proposing it.
>
> Another thought: before doing the sprint, we might want to make sure
> our tripleo-ci is in stable shape (which is not the case right now, we
> have 4 alerts and one of them affects ovb-ha)...
>
>> Thanks
>> --
>> Best regards
>> Sagi Shnaidman
>
>
>
> --
> Emilien Macchi



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Joe Talerico]

On Tue, May 23, 2017 at 6:47 AM, Sagi Shnaidman  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
> possible.
>
> 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?

Sounds like a great idea! Looking forward to contributing! Lets go
ahead and add this one :
https://bugs.launchpad.net/tripleo/+bug/1671859

;-)

>
> Thanks
> --
> Best regards
> Sagi Shnaidman
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] A proposal for hackathon to reduce deploy time of TripleO

[Emilien Macchi]

On Tue, May 23, 2017 at 6:47 AM, Sagi Shnaidman  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.

+1 for IRC. We already have #openstack-sprint, that we could re-use.
Also +1 for video conference, to get face to face interactions,
promptly and unscheduled.

> - 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.

Before running the sprint, we should first track bugs / blueprints
related to deployment speed.
Not everyone in our team understands why some parts of deployments
take time, so we need to make it visible so everyone can know how they
can help during the sprint.

Maybe we could create a Launchpad tag "deployment-time" to track bugs
related to it. We should also make prioritization so we can work on
the most critical ones first.

I like the idea of breaking down the skills into small groups:

- High Availability: deployment & runtime of Pacemaker optimization
- Puppet: anything related to the steps (a bit more general but only a
few of us have expertise on it, we could improve it).
- Heat: work with the Heat team if we have some pending bugs about slowness.
- Baremetal: ironic / workflows
- tripleo-quickstart: tasks that can be improved / optimized

This is a proposal ^ feel free to (comment,add|remove) anything.


> - What is the goal?
>
> The goal of this hackathon to reduce deployment time of TripleO as much as
> possible.
>
> 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?

Excellent idea, thanks Sagi for proposing it.

Another thought: before doing the sprint, we might want to make sure
our tripleo-ci is in stable shape (which is not the case right now, we
have 4 alerts and one of them affects ovb-ha)...

> Thanks
> --
> Best regards
> Sagi Shnaidman



-- 
Emilien Macchi

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev