Bug 1577837 Comment 2 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
lol they already approved it! that was fast

results for 100 instances: spun up ok, registered ok, check status also worked (I stopped 1 instance)(tested mainly provisioning loop and registering)
Provisioning:  :44:32 to :44:32 (less than 1s). Registering: :45:47 to :46:13 (~30s)

results for 1000 instances: `Error calling AWS API: RequestLimitExceeded: Request limit exceeded.` in provisioning loop
Revision 1 by
on 
lol they already approved it! that was fast

results for 100 instances: spun up ok, registered ok, check status also worked (I stopped 1 instance)(tested mainly provisioning loop and registering)
Provisioning:  :44:32 to :44:32 (less than 1s). Registering: :45:47 to :46:13 (~1/2 s)

results for 1000 instances: `Error calling AWS API: RequestLimitExceeded: Request limit exceeded.` in provisioning loop
Revision 2 by
on 
lol they already approved it! that was fast

results for 100 instances: spun up ok, registered ok, check status also worked (I stopped 1 instance)(tested mainly provisioning loop and registering)
Provisioning:  :44:32 to :44:32 (less than 1s). Registering: :45:47 to :46:13 (less than 1s)

results for 1000 instances: `Error calling AWS API: RequestLimitExceeded: Request limit exceeded.` in provisioning loop
Revision 3 by
on 
lol they already approved it! that was fast

results for 100 instances: spun up ok, registered ok, check status also worked (I stopped 1 instance)(tested mainly provisioning loop and registering)
Provisioning:  :44:32 to :44:32 (less than 1s). Registering: :45:47 to :46:13 (~30s)

results for 1000 instances: `Error calling AWS API: RequestLimitExceeded: Request limit exceeded.` in provisioning loop

Back to Bug 1577837 Comment 2