FAQ
Sorry if this is a silly question, and I vaguely remember reading the
proper way to determine this, but it's slipping my mind at the moment. I'm
attempting to deploy Cloud Foundry to vSphere, and when I run "bosh
deploy", I get the following error:

$ bosh deploy
Getting deployment properties from director...
Compiling deployment manifest...
Please review all changes carefully
Deploying `cloudfoundry.yml' to `micro' (type 'yes' to continue): yes

Director task 44

Preparing deployment
binding deployment (00:00:00)

binding release (00:00:00)

binding existing deployment (00:00:00)

binding resource pools: `infrastructure/3' asked for a dynamic IP but
there were no more available (00:00:00)
Error 4/8 00:00:00


Task 44 error

Obviously, it's an error in my manifest YAML with whatever job is in the infrastructure
pool that has the index of 3, however, how do I know which job '
infrastructure/3' is? Is this the 3rd job in my manifest? The 4th if this
index is 0-based? Or does my Micro BOSH index the jobs in a different order?

Thanks!

Brian McClain
@brianmmcclain

Search Discussions

  • Brian McClain at Jul 14, 2012 at 6:03 pm
    Forgot to mention, all of the jobs in my manifest are required a static IP
    on the network I'm deploying to, however I looked through all of my jobs
    and they are all assigned static IPs.

    Thanks

    Brian McClain
    @brianmmcclain
    On Saturday, July 14, 2012 2:02:13 PM UTC-4, Brian McClain wrote:

    Sorry if this is a silly question, and I vaguely remember reading the
    proper way to determine this, but it's slipping my mind at the moment. I'm
    attempting to deploy Cloud Foundry to vSphere, and when I run "bosh
    deploy", I get the following error:

    $ bosh deploy
    Getting deployment properties from director...
    Compiling deployment manifest...
    Please review all changes carefully
    Deploying `cloudfoundry.yml' to `micro' (type 'yes' to continue): yes

    Director task 44

    Preparing deployment
    binding deployment (00:00:00)

    binding release (00:00:00)

    binding existing deployment (00:00:00)

    binding resource pools: `infrastructure/3' asked for a dynamic IP but
    there were no more available (00:00:00)
    Error 4/8 00:00:00


    Task 44 error

    Obviously, it's an error in my manifest YAML with whatever job is in the infrastructure
    pool that has the index of 3, however, how do I know which job '
    infrastructure/3' is? Is this the 3rd job in my manifest? The 4th if this
    index is 0-based? Or does my Micro BOSH index the jobs in a different order?

    Thanks!

    Brian McClain
    @brianmmcclain
  • Vadim Spivak at Jul 14, 2012 at 6:20 pm
    Not all VMs are used for jobs, compilation VMs and other idle resource pool
    VMs will get a dynamic IP.

    -Vadim
    On Sat, Jul 14, 2012 at 11:03 AM, Brian McClain wrote:

    Forgot to mention, all of the jobs in my manifest are required a static IP
    on the network I'm deploying to, however I looked through all of my jobs
    and they are all assigned static IPs.

    Thanks

    Brian McClain
    @brianmmcclain

    On Saturday, July 14, 2012 2:02:13 PM UTC-4, Brian McClain wrote:

    Sorry if this is a silly question, and I vaguely remember reading the
    proper way to determine this, but it's slipping my mind at the moment. I'm
    attempting to deploy Cloud Foundry to vSphere, and when I run "bosh
    deploy", I get the following error:

    $ bosh deploy
    Getting deployment properties from director...
    Compiling deployment manifest...
    Please review all changes carefully
    Deploying `cloudfoundry.yml' to `micro' (type 'yes' to continue): yes

    Director task 44

    Preparing deployment
    binding deployment (00:00:00)

    binding release (00:00:00)

    binding existing deployment (00:00:00)

    binding resource pools: `infrastructure/3' asked for a dynamic IP but
    there were no more available (00:00:00)
    Error 4/8 00:00:00


    Task 44 error

    Obviously, it's an error in my manifest YAML with whatever job is in the infrastructure
    pool that has the index of 3, however, how do I know which job '
    infrastructure/3' is? Is this the 3rd job in my manifest? The 4th if
    this index is 0-based? Or does my Micro BOSH index the jobs in a different
    order?

    Thanks!

    Brian McClain
    @brianmmcclain
  • Brian McClain at Jul 14, 2012 at 8:41 pm
    Ah, that makes sense. Not around the computer to check, but would the
    solution be to scale down the resource pool to only the total number of
    instances for the jobs, and set up a seperate, DHCP-enabled network for
    compilation?

    Thanks

    Brian McClain
    @brianmmcclain

    On Jul 14, 2012, at 2:20 PM, Vadim Spivak wrote:

    Not all VMs are used for jobs, compilation VMs and other idle resource pool
    VMs will get a dynamic IP.

    -Vadim
    On Sat, Jul 14, 2012 at 11:03 AM, Brian McClain wrote:

    Forgot to mention, all of the jobs in my manifest are required a static IP
    on the network I'm deploying to, however I looked through all of my jobs
    and they are all assigned static IPs.

    Thanks

    Brian McClain
    @brianmmcclain

    On Saturday, July 14, 2012 2:02:13 PM UTC-4, Brian McClain wrote:

    Sorry if this is a silly question, and I vaguely remember reading the
    proper way to determine this, but it's slipping my mind at the moment. I'm
    attempting to deploy Cloud Foundry to vSphere, and when I run "bosh
    deploy", I get the following error:

    $ bosh deploy
    Getting deployment properties from director...
    Compiling deployment manifest...
    Please review all changes carefully
    Deploying `cloudfoundry.yml' to `micro' (type 'yes' to continue): yes

    Director task 44

    Preparing deployment
    binding deployment (00:00:00)

    binding release (00:00:00)

    binding existing deployment (00:00:00)

    binding resource pools: `infrastructure/3' asked for a dynamic IP but
    there were no more available (00:00:00)
    Error 4/8 00:00:00


    Task 44 error

    Obviously, it's an error in my manifest YAML with whatever job is in the infrastructure
    pool that has the index of 3, however, how do I know which job '
    infrastructure/3' is? Is this the 3rd job in my manifest? The 4th if
    this index is 0-based? Or does my Micro BOSH index the jobs in a different
    order?

    Thanks!

    Brian McClain
    @brianmmcclain
  • Vadim Spivak at Jul 14, 2012 at 9:29 pm
    Yep, exactly

    On Jul 14, 2012, at 1:41 PM, Brian McClain wrote:

    Ah, that makes sense. Not around the computer to check, but would the
    solution be to scale down the resource pool to only the total number of
    instances for the jobs, and set up a seperate, DHCP-enabled network for
    compilation?

    Thanks

    Brian McClain
    @brianmmcclain

    On Jul 14, 2012, at 2:20 PM, Vadim Spivak wrote:

    Not all VMs are used for jobs, compilation VMs and other idle resource pool
    VMs will get a dynamic IP.

    -Vadim
    On Sat, Jul 14, 2012 at 11:03 AM, Brian McClain wrote:

    Forgot to mention, all of the jobs in my manifest are required a static IP
    on the network I'm deploying to, however I looked through all of my jobs
    and they are all assigned static IPs.

    Thanks

    Brian McClain
    @brianmmcclain

    On Saturday, July 14, 2012 2:02:13 PM UTC-4, Brian McClain wrote:

    Sorry if this is a silly question, and I vaguely remember reading the
    proper way to determine this, but it's slipping my mind at the moment. I'm
    attempting to deploy Cloud Foundry to vSphere, and when I run "bosh
    deploy", I get the following error:

    $ bosh deploy
    Getting deployment properties from director...
    Compiling deployment manifest...
    Please review all changes carefully
    Deploying `cloudfoundry.yml' to `micro' (type 'yes' to continue): yes

    Director task 44

    Preparing deployment
    binding deployment (00:00:00)

    binding release (00:00:00)

    binding existing deployment (00:00:00)

    binding resource pools: `infrastructure/3' asked for a dynamic IP but
    there were no more available (00:00:00)
    Error 4/8 00:00:00


    Task 44 error

    Obviously, it's an error in my manifest YAML with whatever job is in the infrastructure
    pool that has the index of 3, however, how do I know which job '
    infrastructure/3' is? Is this the 3rd job in my manifest? The 4th if
    this index is 0-based? Or does my Micro BOSH index the jobs in a different
    order?

    Thanks!

    Brian McClain
    @brianmmcclain
  • Brian McClain at Jul 15, 2012 at 6:20 am
    Just as a reference for anyone else that missed this in the documentation
    like I did, I also had to set the resource pool's network to the dynamic
    network, instead of the static one that I intend the VMs to run on.
    Referenced here:

    network [String, required] References a network name (see [network_spec]
    for details). Idle resource pool VMs will use this network configuration.
    Later, when the job is being applied to these resource pool VMs, networks
    might be reconfigured to meet job's needs.

    I created a third network to that in the cloudfoundry.yml example manifest
    in the OSS-Docs, put it on a DHCP-enabled VLAN, and used this as the
    network configuration in both the "compilation" and all pools in the
    "resource_pools" sections.

    Thanks again Vadim!

    Brian McClain
    @brianmmcclain

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-users @
postedJul 14, '12 at 6:02p
activeJul 15, '12 at 6:20a
posts6
users3

People

Translate

site design / logo © 2022 Grokbase