Skip to content
This repository has been archived by the owner on Nov 29, 2017. It is now read-only.

some notes while going through the new tutorial. #20

Open
wants to merge 1 commit into
base: create-user
Choose a base branch
from

Conversation

hmalphettes
Copy link
Contributor

Hi Drc Nic,
Here are my notes while going through this revised version of the tutorial.
Really just details that will go away and might not be useful to pull.
I hope it helps.

@@ -166,7 +168,20 @@ ruby ../chef_deployer/bin/chef_deployer deploy ~/.chefbosh --default-password=''
...lots of chef...
```

Now apply patches to BOSH CLI:
If there is a problem with read_pipe.expect(/password /)
See http://reviews.cloudfoundry.org/#/c/6935/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternately to "make these changes" is we either:

  • say "run this cherry pick command", or
  • we manage a fork of bosh that contains all the patches we need to make bosh work

Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wish we could convince the bosh guys to take my very innocent change?
I rewrote it to minimize the changes to the behavior they currently have.

Any advice on what I could do to make them comfortable with it?
I am sure they are busy with everything else already.

Avoiding the fork would be nice unless there are tweaks you have in mind?

Otherwise:

  • cherry pick would be my favorite.
  • a small script to patch things up

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

Bonus, there is also this pull request in progress for simplifying the instructions for using chef_deployer. Let me know if you have time to have a look at them. #21

@hmalphettes
Copy link
Contributor Author

I'll run through that new version based on pull-21: my motivation is that this time I need to figure out why my chef created bosh VM refuses to reboot.

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

I'm trying this:

cd ~/.chefbosh/bosh/releases
git checkout -b patches
git fetch ssh://$(whoami)@reviews.cloudfoundry.org:29418/bosh refs/changes/87/7387/2 && git cherry-pick FETCH_HEAD


rm -rf /tmp/repos
ruby ../chef_deployer/bin/chef_deployer deploy ~/.chefbosh --default-password='' --local

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

Still got this error:

==> DIRECTLY CONNECTING TO ec2-23-21-73-121.compute-1.amazonaws.com
:::deploy_sudo_passwd:::
password for: ec2-23-21-73-121.compute-1.amazonaws.com@vcap:{:config=>false, :port=>22, :password=>nil, :auth_methods=>["publickey", "hostbased"], :user=>"vcap"}? 

Checking that vcap user is correct.

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

I can ssh [email protected] successfully.

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

Now trying the first patch of @hmalphettes's

git checkout master
git checkout -b p6935
git fetch ssh://$(whoami)@reviews.cloudfoundry.org:29418/bosh refs/changes/35/6935/1 && git cherry-pick FETCH_HEAD

rm -rf /tmp/repos
ruby ../chef_deployer/bin/chef_deployer deploy ~/.chefbosh --default-password='' --local

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

That is, I'm trying http://reviews.cloudfoundry.org/#/c/6935/

Initially I tried http://reviews.cloudfoundry.org/#/c/7387/

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

Current attempt, as it did once before if I recollect, seems to block here:

...
       repos  uploading bosh to ec2-23-21-73-121.compute-1.amazonaws.com
==> EXECUTING SSH LOGIN git push -q ssh://[email protected]:22/var/vcap/deploy/repos/bosh master

@drnic
Copy link
Contributor

drnic commented Jul 23, 2012

Suggestions on debugging what is happening?

@hmalphettes
Copy link
Contributor Author

humf. I'll try this again then. In my experience it crashes loudly with the stack trace I reported in gerrit and that Ruslan also mentionned on the mailing list today.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants