do you know why chef's detecting this as solo run? can you share the log.
Are you using chef-zero as standalone chef server or via chef-client local
mode. If you are using it in standalone mode, you have to upload some
fixture data to get going, so that the search results return some value.
I'm using Chef zero with Vagrant as explained in the Vagrant doc, I think
that it starts an in mem chef zero server before starting the VM.
I'm also using Berks to retreive my dependencies, so if I could avoid to
fetch and modify that recipe it should be better.
do you know why chef's detecting this as solo run? can you share the log.
Are you using chef-zero as standalone chef server or via chef-client local
mode. If you are using it in standalone mode, you have to upload some
fixture data to get going, so that the search results return some value.
you dont have to modify any recipe, but you have to find out if you can
upload the required data bags via vagrant plugin. I dont use vagrant, but i
think you can do something using the shell provisioner , and execute it
before the chef-solo run. Also change the chef-solo invocation to
chef-client, either in localmode (-z) or configure the client.rb with
chef-zero details (localhost, 8889.. might vary depending upon where
chef-zero is bound,can be in the bridge interface of virtualbox as well).
On Mon, Apr 20, 2015 at 12:45 AM, Charlie Mordant cmordant1@gmail.com
wrote:
Hi Ranjib,
I'm using Chef zero with Vagrant as explained in the Vagrant doc, I think
that it starts an in mem chef zero server before starting the VM.
I'm also using Berks to retreive my dependencies, so if I could avoid to
fetch and modify that recipe it should be better.
do you know why chef's detecting this as solo run? can you share the log.
Are you using chef-zero as standalone chef server or via chef-client local
mode. If you are using it in standalone mode, you have to upload some
fixture data to get going, so that the search results return some value.
you dont have to modify any recipe, but you have to find out if you can
upload the required data bags via vagrant plugin. I dont use vagrant, but i
think you can do something using the shell provisioner , and execute it
before the chef-solo run. Also change the chef-solo invocation to
chef-client, either in localmode (-z) or configure the client.rb with
chef-zero details (localhost, 8889.. might vary depending upon where
chef-zero is bound,can be in the bridge interface of virtualbox as well).
On Mon, Apr 20, 2015 at 12:45 AM, Charlie Mordant cmordant1@gmail.com
wrote:
Hi Ranjib,
I'm using Chef zero with Vagrant as explained in the Vagrant doc, I think
that it starts an in mem chef zero server before starting the VM.
I'm also using Berks to retreive my dependencies, so if I could avoid to
fetch and modify that recipe it should be better.
do you know why chef's detecting this as solo run? can you share the
log. Are you using chef-zero as standalone chef server or via chef-client
local mode. If you are using it in standalone mode, you have to upload some
fixture data to get going, so that the search results return some value.
I'm using Chef zero with Vagrant as explained in the Vagrant doc, I
think that it starts an in mem chef zero server before starting the VM.
I'm also using Berks to retreive my dependencies, so if I could avoid
to fetch and modify that recipe it should be better.
You're probably better off starting with test-kitchen which will handle
setting up the Vagrantfile for you, and with uploading data bags to the
virts, etc.
I ended up using the 'user' cookbook (also made by an OpsCode contributor),
that don't use search internally.
Yes, I really need to use test-kitchen, but as its an off-work project, I
don't have so much time to set this things up (for now), even if it's the
way to go in mid term.
I'm using Chef zero with Vagrant as explained in the Vagrant doc, I
think that it starts an in mem chef zero server before starting the VM.
I'm also using Berks to retreive my dependencies, so if I could avoid to
fetch and modify that recipe it should be better.
You're probably better off starting with test-kitchen which will handle
setting up the Vagrantfile for you, and with uploading data bags to the
virts, etc.