yahoo-eng-team team mailing list archive

[Scott Moser <smoser@xxxxxxxxxx>]

Public bug reported:

When looking into bug 1604962 I investigated cloud-init and curtin logs and looked at timestamps.
In Adams scenario shown at 
  https://bugs.launchpad.net/maas/+bug/1604962/comments/16
posting a message back to maas was taking up to 7 seconds.

cloud-init and curtin during an installation can be expected to post
dozens of messages.  if each of those took just 5 seconds the group of
only 12 would make an installation take 60 seconds longer than it needed
to.

This can be considered a "client" problem (curtin and cloud-init) in
some respects. These clients could definitely background their posting
of data so that they can go on.  However, if they do that at some point
they probably should verify that all messages were correctly posted, so
its possible that backgrounding the posting wouldn't actually help.

Adam's system I think was a "orange box", with 10 clients all
installing.  That does not seem like enough load to account for 5+
second posts.

Related bugs:
  * bug 1604962: node set to "failed deployment" for no visible reason

** Affects: cloud-init
     Importance: Undecided
         Status: New

** Affects: curtin
     Importance: Undecided
         Status: New

** Affects: maas
     Importance: Undecided
         Status: New

** Also affects: cloud-init
   Importance: Undecided
       Status: New

** Also affects: curtin
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1606999

Title:
  reporting messages can slow down operations greatly

Status in cloud-init:
  New
Status in curtin:
  New
Status in MAAS:
  New

Bug description:
  When looking into bug 1604962 I investigated cloud-init and curtin logs and looked at timestamps.
  In Adams scenario shown at 
    https://bugs.launchpad.net/maas/+bug/1604962/comments/16
  posting a message back to maas was taking up to 7 seconds.

  cloud-init and curtin during an installation can be expected to post
  dozens of messages.  if each of those took just 5 seconds the group of
  only 12 would make an installation take 60 seconds longer than it
  needed to.

  This can be considered a "client" problem (curtin and cloud-init) in
  some respects. These clients could definitely background their posting
  of data so that they can go on.  However, if they do that at some
  point they probably should verify that all messages were correctly
  posted, so its possible that backgrounding the posting wouldn't
  actually help.

  Adam's system I think was a "orange box", with 10 clients all
  installing.  That does not seem like enough load to account for 5+
  second posts.

  Related bugs:
    * bug 1604962: node set to "failed deployment" for no visible reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1606999/+subscriptions