- From: "Julian C. Dunn" <
>
- To:
- Subject: [chef] Re: Strange delay between bootstrapping hosts
- Date: Wed, 21 Jan 2015 10:36:34 -0500
On Jan 20, 2015, at 7:08 PM, Justin Franks
<
>
wrote:
>
>
Strange delay between bootstrapping hosts.
>
Want to know where to look. Any ideas?
>
Here is the problem:
>
We have two Openstack deployments/builds. OpenstackX and OpenstackY
>
>
If I do this on OpenstackX it completes the bootstrap and chef run ~1 min
>
43 seconds:
>
time knife openstack server create -N justinblahblah -f
>
958e7841-a90d-45ff-acf8-8a9c946bc5fe -S justin-openstack -G justin
>
--network-ids c60e802c-516d-42f8-8b01-d9b120f245a9 --bootstrap-network
>
dev-1-private-1a -i ~/.ssh/justin-openstack.pem -r <insert runlistA>
>
>
If I do the same thing on OpenstackY it completes the bootstrap and chef
>
run in ~5min 30 seconds
>
time knife openstack server create -N justinblahblah -f
>
958e7841-a90d-45ff-acf8-8a9c946bc5fe -S justin-openstack -G justin
>
--network-ids c60e802c-516d-42f8-8b01-d9b120f245a9 --bootstrap-network
>
dev-1-private-1a -i ~/.ssh/justin-openstack.pem -r <insert runlistA>
>
>
Yes, the Openstack environments are a bit different. But data transfer
>
testing in both environments to same Chef server reveals fast performance.
>
Any ideas on where to look to find where the delays are coming?
I would probably write a report handler to do this. You can iterate over
run_status.all_resources or run_status.updated_resources; for each resource,
there is an elapsed_time accessor that hangs off it that you can do something
with.
- Julian
[ Julian C. Dunn
<
>
* Sorry, I'm ]
[ WWW:
http://www.aquezada.com/staff/julian * only Web 1.0 ]
[
gopher://sdf.org/1/users/keymaker/ * compliant! ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
Archive powered by MHonArc 2.6.16.