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?

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 ​

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.

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 ​

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?
Chef outputs the elapsed time at the end of the run, so if those times are similar, then it’s probably something to do with bootstrapping or openstack. If the chef runs account for the time difference, then use a profiler as Julian suggested (more on that below) to help pinpoint why Chef is running slower.

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.

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 ​

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?
Chef outputs the elapsed time at the end of the run, so if those times are similar, then it’s probably something to do with bootstrapping or openstack. If the chef runs account for the time difference, then use a profiler as Julian suggested (more on that below) to help pinpoint why Chef is running slower.

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.