← Back to team overview

cf-charmers team mailing list archive

Re: Deploing CF inside one machine

 

My steps:

1. deploy using deployer
2. push an app
go to directory with an app
get ip address of router using juju status router. e.g. 192.168.200.6
cf api http://api.192.168.200.6.xip.io
cf login (admin/admin)
cf create-space myspace
cf target -s myspace
cf push myapp
3. check if application up and running using a browser e.g. w3m
http://myapp.192.168.200.6.xip.io

-Alex Prismakov


On Wed, Apr 16, 2014 at 2:47 AM, Kapil Thangavelu <
kapil.thangavelu@xxxxxxxxxxxxx> wrote:

> fwiw using trunk revisions of the charms, i don't get this error when
> deploying. but i'm still at a loss on the login.. ie what are the steps to
> deploy an app after cf is running.
>
> cheers,
>
> Kapil
>
>
> On Tue, Apr 15, 2014 at 6:52 PM, Benjamin Saller <
> benjamin.saller@xxxxxxxxxxxxx> wrote:
>
>>
>> but all relations set and I able to deploy an app!
>>> checked on 2 machines (on home and office's PC)
>>>
>>> used bundle file -
>>> http://bazaar.launchpad.net/~cf-charmers/charms/bundles/cloudfoundry/bundle/revision/29/bundle_v001_local.yaml
>>>
>>>
>> I've been unable to replicate this. Using this deployment
>> cloud-controller goes into a respawn loop leaving this in the logs::
>>
>> Deprecated: Use -s or --insert-seed flag
>> /var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:94:in
>> `<class:App>': undefined method `kill_after_multiple_restarts' for class
>> `VCAP::CloudController::App' (NameError)
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:5:in
>> `<module:CloudController>'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:4:in
>> `<top (required)>'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/db.rb:56:in
>> `require'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/db.rb:56:in
>> `load_models'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:90:in
>> `setup_db'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:161:in
>> `start_cloud_controller'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:111:in
>> `block in run!'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
>> `call'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
>> `run_machine'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
>> `run'
>>         from
>> /var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:104:in
>> `run!'
>>         from bin/cloud_controller:12:in `<main>'
>>
>>
>> juju status can't tell the service isn't functioning.
>>
>> environment: local
>> machines:
>>   "1":
>>     agent-state: started
>>     agent-version: 1.18.1.1
>>     dns-name: 10.0.3.196
>>     instance-id: bcsaller-local-machine-1
>>     series: trusty
>>     hardware: arch=amd64
>> services:
>>   cc:
>>     charm: local:trusty/cf-cloud-controller-3
>>     exposed: false
>>     relations:
>>       nats:
>>       - nats
>>       router:
>>       - router
>>     units:
>>       cc/0:
>>         agent-state: started
>>         agent-version: 1.18.1.1
>>         machine: "1"
>>         public-address: 10.0.3.196
>>
>>
>> Any ideas?
>>
>>
>>
>>> -Alex Prismakov
>>>
>>> --
>>> Mailing list: https://launchpad.net/~cf-charmers
>>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~cf-charmers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>

References