I have bosh micro deploying a stem cell to vSphere server however the vm once provisioned doesn't seem to have an ip address assigned to it in vSphere client. I also cannot performa simple ping to the ip address that I have assigned to bosh director in my bosh yaml file. This is leading to connection timeouts whilst waiting for the agent. The vm is powered up by the bosh micro deploy process,
Here is a snippet from the deployment log...
I, [2012-11-12T02:05:39.819121 #8151] [create_vm(bm-ac986c50-ec83-424b-8752-3ede19c76f31, ...)] INFO -- : Cloning vm: <[Vim.VirtualMachine] vm-1253> to vm-689766f4-834d-44b5-9ab6-36e961390c72 I, [2012-11-12T02:06:01.560344 #8151] [create_vm(bm-ac986c50-ec83-424b-8752-3ede19c76f31, ...)] INFO -- : Setting VM env: {"vm"=>{"name"=>"vm-689766f4-834d-44b5-9ab6-36e961390c72", "id"=>"vm-1255"}, "agent_id"=>"bm-ac986c50-ec83-424b-8752-3ede19c76f31", "networks"=> {"bosh"=> {"cloud_properties"=>{"name"=>"VM Network"}, "netmask"=>"255.255.255.0", "gateway"=>"172.16.19.2", "ip"=>"172.16.4.999", "dns"=>[], "type"=>nil, "default"=>["dns", "gateway"], "mac"=>"00:50:56:93:99:fb"}}, "disks"=>{"system"=>0, "ephemeral"=>1, "persistent"=>{}}, "ntp"=>["bosh.ntp.comain.com"], "blobstore"=> {"plugin"=>"local", "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}}, "mbus"=>"http://vcap:b00tst...@0.0.0.0:6868", "env"=>{"bosh"=>{"password"=>"mypassword"}}}
It may also be worth pointing out that I cannot log into the director vm with the credentials logged in the snippet "env"=>{"bosh"=>{"password"=>"mypassword"}}}. Are these the correct credentials to use?
The ip address was due to the fact I was using an out of range ip address for the bosh director. Although any help on the login credentials issue is welcome.
On Monday, November 12, 2012 10:43:52 AM UTC, chris....@opencredo.com wrote:
> Hi
> I have bosh micro deploying a stem cell to vSphere server however the vm > once provisioned doesn't seem to have an ip address assigned to it in > vSphere client. I also cannot performa simple ping to the ip address that I > have assigned to bosh director in my bosh yaml file. This is leading to > connection timeouts whilst waiting for the agent. The vm is powered up by > the bosh micro deploy process,
> It may also be worth pointing out that I cannot log into the director vm > with the credentials logged in the > snippet "env"=>{"bosh"=>{"password"=>"mypassword"}}}. Are these the > correct credentials to use?
the passform you use, did you generate it with "mkpasswd -m sha-512"?
cheers,
/Martin
--
Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
"The question is not if you are paranoid, it is if you are paranoid enough."
On Nov 12, 2012, at 3:19, chris.hed...@opencredo.com wrote:
> The ip address was due to the fact I was using an out of range ip address for the bosh director. Although any help on the login credentials issue is welcome.
> On Monday, November 12, 2012 10:43:52 AM UTC, chris....@opencredo.com wrote:
>> Hi
>> I have bosh micro deploying a stem cell to vSphere server however the vm once provisioned doesn't seem to have an ip address assigned to it in vSphere client. I also cannot performa simple ping to the ip address that I have assigned to bosh director in my bosh yaml file. This is leading to connection timeouts whilst waiting for the agent. The vm is powered up by the bosh micro deploy process,
>> It may also be worth pointing out that I cannot log into the director vm with the credentials logged in the snippet "env"=>{"bosh"=>{"password"=>"mypassword"}}}. Are these the correct credentials to use?
On Monday, November 12, 2012 4:52:09 PM UTC, Martin Englund wrote:
> Chris,
> the passform you use, did you generate it with "mkpasswd -m sha-512"?
> cheers, > /Martin > -- > Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. > "The question is not if you are paranoid, it is if you are paranoid > enough."
> On Nov 12, 2012, at 3:19, chris....@opencredo.com <javascript:> wrote:
> The ip address was due to the fact I was using an out of range ip address > for the bosh director. Although any help on the login credentials issue is > welcome.
> On Monday, November 12, 2012 10:43:52 AM UTC, chris....@opencredo.comwrote:
>> Hi
>> I have bosh micro deploying a stem cell to vSphere server however the vm >> once provisioned doesn't seem to have an ip address assigned to it in >> vSphere client. I also cannot performa simple ping to the ip address that I >> have assigned to bosh director in my bosh yaml file. This is leading to >> connection timeouts whilst waiting for the agent. The vm is powered up by >> the bosh micro deploy process,
>> It may also be worth pointing out that I cannot log into the director vm >> with the credentials logged in the >> snippet "env"=>{"bosh"=>{"password"=>"mypassword"}}}. Are these the >> correct credentials to use?
Thanks for the pointer, I've generated the password with mkpasswd and now I can access the director vm. Out of interest is there a default password if I don't specify env->bosh->password or is this property mandatory?
On Tuesday, November 13, 2012 12:13:17 PM UTC, chris....@opencredo.com wrote:
> No I've not generated a passform, For now I just use a raw string as > defined in the micro yaml file. Have I missed an obvious step here?
> On Monday, November 12, 2012 4:52:09 PM UTC, Martin Englund wrote:
>> Chris,
>> the passform you use, did you generate it with "mkpasswd -m sha-512"?
>> cheers, >> /Martin >> -- >> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc. >> "The question is not if you are paranoid, it is if you are paranoid >> enough."
>> On Nov 12, 2012, at 3:19, chris....@opencredo.com wrote:
>> The ip address was due to the fact I was using an out of range ip address >> for the bosh director. Although any help on the login credentials issue is >> welcome.
>> On Monday, November 12, 2012 10:43:52 AM UTC, chris....@opencredo.comwrote:
>>> Hi
>>> I have bosh micro deploying a stem cell to vSphere server however the vm >>> once provisioned doesn't seem to have an ip address assigned to it in >>> vSphere client. I also cannot performa simple ping to the ip address that I >>> have assigned to bosh director in my bosh yaml file. This is leading to >>> connection timeouts whilst waiting for the agent. The vm is powered up by >>> the bosh micro deploy process,
>>> It may also be worth pointing out that I cannot log into the director vm >>> with the credentials logged in the >>> snippet "env"=>{"bosh"=>{"password"=>"mypassword"}}}. Are these the >>> correct credentials to use?
> Thanks for the pointer, I've generated the password with mkpasswd and now
> I can access the director vm. Out of interest is there a default password
> if I don't specify env->bosh->password or is this property mandatory?
> On Tuesday, November 13, 2012 12:13:17 PM UTC, chris....@opencredo.comwrote:
>> No I've not generated a passform, For now I just use a raw string as
>> defined in the micro yaml file. Have I missed an obvious step here?
>> On Monday, November 12, 2012 4:52:09 PM UTC, Martin Englund wrote:
>>> Chris,
>>> the passform you use, did you generate it with "mkpasswd -m sha-512"?
>>> cheers,
>>> /Martin
>>> --
>>> Martin Englund, Staff Engineer, Cloud Foundry, VMware Inc.
>>> "The question is not if you are paranoid, it is if you are paranoid
>>> enough."
>>> On Nov 12, 2012, at 3:19, chris....@opencredo.com wrote:
>>> The ip address was due to the fact I was using an out of range ip
>>> address for the bosh director. Although any help on the login credentials
>>> issue is welcome.
>>> On Monday, November 12, 2012 10:43:52 AM UTC, chris....@opencredo.comwrote:
>>>> Hi
>>>> I have bosh micro deploying a stem cell to vSphere server however the
>>>> vm once provisioned doesn't seem to have an ip address assigned to it in
>>>> vSphere client. I also cannot performa simple ping to the ip address that I
>>>> have assigned to bosh director in my bosh yaml file. This is leading to
>>>> connection timeouts whilst waiting for the agent. The vm is powered up by
>>>> the bosh micro deploy process,
>>>> It may also be worth pointing out that I cannot log into the director
>>>> vm with the credentials logged in the snippet "env"=>{"bosh"=>{"**password"=>"mypassword"}}}.
>>>> Are these the correct credentials to use?
