FAQ
Hi,
Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
We got it running with nova-network,. and are now upgading the environment
to use Quantum

Any extra settings in manifest files if Quantum is enabled ?

Search Discussions

  • Ferran Rodenas at Apr 3, 2013 at 10:12 pm
    Yes, it works with Quantum, both using DHCP or static IP's. If you're using
    DHCP, you don't need anything else. But if you plan to use static IP's,
    then you need to create new stemcells, install new gems using the latest
    codebase (or wait until we publish them, very soon hopefully), and then
    some hackery with the fog gem (as the latest public fog gem doesn't contain
    the quantum stuff):

    On a Ubuntu 12.10 box:

    1) cd ~/
    2) git clone git://github.com/fog/fog.git
    3) cd ~/fog
    4) bundle install
    5) bundle exec rake build
    6) cd ~/
    7) git clone git://github.com/cloudfoundry/bosh.git
    8) cd ~/bosh
    9) cp ~/fog/pkg/fog-1.10.0.gem vendor/cache # We're going to replace the
    bundled fog gem
    10) bundle install --local --binstubs
    11) bundle exec rake stemcell:micro[openstack] # To create a microBosh
    stemcell
    12) bundle exec rake stemcell:basci[openstack] # To create a Bosh stemcell

    Once you got all the new stuff installed, you'll need to modify the network
    section of the micro_bosh.yml:

    network:
       type: manual
       label: bosh-net # Name of your Quantum network
       vip: 172.24.4.227 # Floating IP to assign to your microBosh
       ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one of
    the subnets IP range)
       cloud_properties:
         net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network

    If you want later to deploy a full bosh or wordpress, see this manifest
    examples:
    1) Full Bosh:
    https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-static.yml
    2) Wordpress:
    https://github.com/cloudfoundry/bosh-sample-release/blob/master/examples/wordpress-openstack-static.yml

    Let us know if you find any problem.

    - Ferdy


    2013/4/3 Animesh Singh <animation2007@gmail.com>
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment
    to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Kalonji Bankole at Jun 28, 2013 at 4:37 am
    Hello,

    I have been able to execute steps 1-10 without error, but I have been stuck
    on step 11 for quite a while. Attempting to create a basic BOSH stemcell
    yields the following exception:

    "Incorrect YAML structure in
    `/home/k/Documents/bosh/release/config/final.yml': undefined method `root'
    for #<Psych::Nodes::Mapping:0x000000024b24e8>
    rake aborted!
    Command failed with status (1): [bosh create release --force
    --with-tarball...]"

    This error results while executing Step 12, as bundle raises an exception
    from the following line
    "bosh create release --force --with-tarball"

    I'm not too sure where to look to debug this issue. The final.yml file
    doesn't seem to contatin any reference to 'root' either. Do you know of any
    documentation I could review to obtain a deeper understanding of these
    error messages?

    Thanks,
    Kalonji
    On Wednesday, April 3, 2013 3:12:06 PM UTC-7, ferdy wrote:

    Yes, it works with Quantum, both using DHCP or static IP's. If you're
    using DHCP, you don't need anything else. But if you plan to use static
    IP's, then you need to create new stemcells, install new gems using the
    latest codebase (or wait until we publish them, very soon hopefully), and
    then some hackery with the fog gem (as the latest public fog gem doesn't
    contain the quantum stuff):

    On a Ubuntu 12.10 box:

    1) cd ~/
    2) git clone git://github.com/fog/fog.git
    3) cd ~/fog
    4) bundle install
    5) bundle exec rake build
    6) cd ~/
    7) git clone git://github.com/cloudfoundry/bosh.git
    8) cd ~/bosh
    9) cp ~/fog/pkg/fog-1.10.0.gem vendor/cache # We're going to replace the
    bundled fog gem
    10) bundle install --local --binstubs
    11) bundle exec rake stemcell:micro[openstack] # To create a microBosh
    stemcell
    12) bundle exec rake stemcell:basci[openstack] # To create a Bosh stemcell

    Once you got all the new stuff installed, you'll need to modify the
    network section of the micro_bosh.yml:

    network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one
    of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network

    If you want later to deploy a full bosh or wordpress, see this manifest
    examples:
    1) Full Bosh:
    https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-static.yml
    2) Wordpress:
    https://github.com/cloudfoundry/bosh-sample-release/blob/master/examples/wordpress-openstack-static.yml

    Let us know if you find any problem.

    - Ferdy


    2013/4/3 Animesh Singh <animat...@gmail.com <javascript:>>
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Dr Nic Williams at Jun 28, 2013 at 4:46 am
    What do you get when you run the following?

    $ ruby -v
    $ gem env
    $ gem list bosh

    I am sure we've seen that "undefined method `root' " issue before but not
    for months afaik.

    Nic
  • Ruben Koster at Jun 28, 2013 at 9:22 am
    Are the above steps still necessary? Since we now have CI build stemcells?
    On Friday, June 28, 2013 6:45:53 AM UTC+2, Dr Nic Williams wrote:

    What do you get when you run the following?

    $ ruby -v
    $ gem env
    $ gem list bosh

    I am sure we've seen that "undefined method `root' " issue before but not
    for months afaik.

    Nic

    --

    ------------------------------

    Have an innovative day

    *Innovation Factory *De Lairessestraat 180* *1075 HM Amsterdam* *+31
    20 7787008 www.innovationfactory.eu

    *
    Disclaimer*
    *The information transmitted is intended only for the person or entity to
    which it is addressed and may contain confidential and/or privileged
    material. Any use of, or taking of any action in reliance upon, this
    information by persons or entities other than the intended recipient is
    prohibited. If you received this in error, please contact the sender and
    delete the material from any computer. Innovation Factory does not accept
    liability for any errors, viruses or omissions in the contents of this
    message, which may arise as a result of e-mail transmission. No employee or
    agent is authorized to conclude any binding agreement on behalf of
    Innovation Factory with another party by email.*
  • Kalonji Bankole at Jun 28, 2013 at 4:39 pm
    I get the following results.

    $ruby -v

    "ruby 1.9.3p448 (2013-06-27 revision 41675) [x86_64-linux]"

    $ gem env

    "RubyGems Environment:
       - RUBYGEMS VERSION: 1.8.25
       - RUBY VERSION: 1.9.3 (2013-06-27 patchlevel 448) [x86_64-linux]
       - INSTALLATION DIRECTORY: /home/k/.rvm/gems/ruby-1.9.3-p448
       - RUBY EXECUTABLE: /home/k/.rvm/rubies/ruby-1.9.3-p448/bin/ruby
       - EXECUTABLE DIRECTORY: /home/k/.rvm/gems/ruby-1.9.3-p448/bin
       - RUBYGEMS PLATFORMS:
         - ruby
         - x86_64-linux
       - GEM PATHS:
          - /home/k/.rvm/gems/ruby-1.9.3-p448
          - /home/k/.rvm/gems/ruby-1.9.3-p448@global
       - GEM CONFIGURATION:
          - :update_sources => true
          - :verbose => true
          - :benchmark => false
          - :backtrace => false
          - :bulk_threshold => 1000
       - REMOTE SOURCES:
          - http://rubygems.org/"

    $ gem list bosh

    *** LOCAL GEMS ***

    Kalonji
    On Thursday, June 27, 2013 9:45:53 PM UTC-7, Dr Nic Williams wrote:

    What do you get when you run the following?

    $ ruby -v
    $ gem env
    $ gem list bosh

    I am sure we've seen that "undefined method `root' " issue before but not
    for months afaik.

    Nic

  • Dr Nic Williams at Jun 28, 2013 at 4:41 pm
    Thanks. What commands were you running that reproduce the issue?

    Nic
  • Kalonji Bankole at Jun 28, 2013 at 5:00 pm
    I receive this error each time I run

    $sudo bundle exec rake stemcell:micro[openstack]
    On Friday, June 28, 2013 9:40:46 AM UTC-7, Dr Nic Williams wrote:

    Thanks. What commands were you running that reproduce the issue?

    Nic
  • Kalonji Bankole at Jul 19, 2013 at 5:24 am
    Hello,

    At this point I am able to generate a basic stemcell of version 1.5.0.pre.3
    using the steps above. I am able to successfully upload the stemcell as
    well, but when attempting to deploy bosh, a time-out occurs during the
    "Compiling packages" stage. Slightly older stemcells obtained from the
    public repository (version 1.5.0.pre2) allow for a successful deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in the
    public openstack stemcell repository, so I was wondering if there is is a
    possibility that version 1.5.0.pre.3 stemcells are not fully supported yet?
    If so, what do I need to alter to create a 1.5.0.pre2 stemcell using the
    rake build? And where can I find a valid 1.5.0.pre.3 stemcell to attempt a
    deployment with?

    My issue appears to be identical to the thread Dhruv's thread here<https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking through
    the debug log. Do you have any suggestions of where I might continue from
    here?

    Thanks
    Kalonji Bankole
  • Heiko Krämer at Jul 19, 2013 at 8:56 am
    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env is working
    correctly.

    cd /var/vcap/stemcells/ && wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz
    && wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz


    Cheers
    Heiko
    On 19.07.2013 07:24, Kalonji Bankole wrote:
    Hello,

    At this point I am able to generate a basic stemcell of version
    1.5.0.pre.3 using the steps above. I am able to successfully upload
    the stemcell as well, but when attempting to deploy bosh, a time-out
    occurs during the "Compiling packages" stage. Slightly older stemcells
    obtained from the public repository (version 1.5.0.pre2) allow for a
    successful deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in
    the public openstack stemcell repository, so I was wondering if there
    is is a possibility that version 1.5.0.pre.3 stemcells are not fully
    supported yet? If so, what do I need to alter to create a 1.5.0.pre2
    stemcell using the rake build? And where can I find a valid
    1.5.0.pre.3 stemcell to attempt a deployment with?

    My issue appears to be identical to the thread Dhruv's thread here
    <https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking
    through the debug log. Do you have any suggestions of where I might
    continue from here?

    Thanks
    Kalonji Bankole

    --
    anynines.com
  • Kalonji Bankole at Jul 22, 2013 at 3:04 pm
    Hello

    The stemcells acquired from the public repository work fine, but my primary
    focus is to get my custom stemcell working. It seems that the custom
    stemcell seems to fail at deploying the VMs, which are all unresponsive,
    and then hangs at the compiling packages stage. I cannot SSH into the VMs
    either. I've built the stemcell using the instructions above, is there
    perhaps an alternative procedure I could possibly use?

    Thanks,
    Kalonji Bankole
    On Friday, July 19, 2013 1:56:00 AM UTC-7, Heiko Krämer wrote:

    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env is working
    correctly.

    cd /var/vcap/stemcells/ && wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz&& wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz


    Cheers
    Heiko

    On 19.07.2013 07:24, Kalonji Bankole wrote:

    Hello,

    At this point I am able to generate a basic stemcell of version
    1.5.0.pre.3 using the steps above. I am able to successfully upload the
    stemcell as well, but when attempting to deploy bosh, a time-out occurs
    during the "Compiling packages" stage. Slightly older stemcells obtained
    from the public repository (version 1.5.0.pre2) allow for a successful
    deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in the
    public openstack stemcell repository, so I was wondering if there is is a
    possibility that version 1.5.0.pre.3 stemcells are not fully supported yet?
    If so, what do I need to alter to create a 1.5.0.pre2 stemcell using the
    rake build? And where can I find a valid 1.5.0.pre.3 stemcell to attempt a
    deployment with?

    My issue appears to be identical to the thread Dhruv's thread here<https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking through
    the debug log. Do you have any suggestions of where I might continue from
    here?

    Thanks
    Kalonji Bankole



    -- anynines.com
  • Ferran Rodenas at Jul 22, 2013 at 4:36 pm
    Some things you should check:

    - The vm console log to see if the vm started up properly.
    - The vm key-pair. You should be able to ssh to the vm using the private
    key. If there's a permission denied, that means that the vm cannot get the
    private key from the openstack metadata server.
    - The security group used for the vm has all ports opened (or at least the
    ones that appears at the openstack
    guide)<http://docs.cloudfoundry.com/docs/running/deploying-cf/openstack/deploying_microbosh.html#openstack_security_groups>
    .

    Another approach is to delete the 'bosh_harden' and 'bosh_harden_ssh' from
    your spec file<https://github.com/cloudfoundry/bosh/blob/master/stemcell_builder/spec/stemcell-openstack.spec#L34>
    before
    building the stemcell. This will allow you to ssh as root and check inside
    the vm if the bosh agent is running properly.

    - Ferdy


    2013/7/22 Kalonji Bankole <kalonb91@gmail.com>
    Hello

    The stemcells acquired from the public repository work fine, but my
    primary focus is to get my custom stemcell working. It seems that the
    custom stemcell seems to fail at deploying the VMs, which are all
    unresponsive, and then hangs at the compiling packages stage. I cannot SSH
    into the VMs either. I've built the stemcell using the instructions above,
    is there perhaps an alternative procedure I could possibly use?

    Thanks,
    Kalonji Bankole
    On Friday, July 19, 2013 1:56:00 AM UTC-7, Heiko Krämer wrote:

    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env is working
    correctly.

    cd /var/vcap/stemcells/ && wget http://bosh-jenkins-artifacts.**
    s3.amazonaws.com/micro-bosh-**stemcell/openstack/latest-**
    micro-bosh-stemcell-openstack.**tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz>&& wget
    http://bosh-jenkins-artifacts.**s3.amazonaws.com/bosh-**
    stemcell/openstack/latest-**bosh-stemcell-openstack.tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz>


    Cheers
    Heiko

    On 19.07.2013 07:24, Kalonji Bankole wrote:

    Hello,

    At this point I am able to generate a basic stemcell of version
    1.5.0.pre.3 using the steps above. I am able to successfully upload the
    stemcell as well, but when attempting to deploy bosh, a time-out occurs
    during the "Compiling packages" stage. Slightly older stemcells obtained
    from the public repository (version 1.5.0.pre2) allow for a successful
    deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in the
    public openstack stemcell repository, so I was wondering if there is is a
    possibility that version 1.5.0.pre.3 stemcells are not fully supported yet?
    If so, what do I need to alter to create a 1.5.0.pre2 stemcell using the
    rake build? And where can I find a valid 1.5.0.pre.3 stemcell to attempt a
    deployment with?

    My issue appears to be identical to the thread Dhruv's thread here<https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking through
    the debug log. Do you have any suggestions of where I might continue from
    here?

    Thanks
    Kalonji Bankole



    -- anynines.com
  • Kalonji Bankole at Jul 22, 2013 at 5:21 pm
    Thank you for the response. I am using the same manifest file for deploying
    both the public stemcell and the custom stemcell. The only change made to
    the manifest file when switching between these stemcells is the stemcell
    version number (1.5.0.pre2 vs 1.5.0.pre.3, respectively). Does it matter
    that I'm attempting to deploy a 1.5.0pre.3 stemcell with a 1.5.0.pre.2
    agent?

    The specified security group ensures that all necessary ports are open, and
    the path to the key is correct as well. Since the public stemcell's
    deployment is relatively fine, and both stemcells are using the same
    manifest file, I'm not sure if the key, networking, and security groups are
    an issue.

    Running the bosh vms commands shows that the VMs are not starting up
    properly.

    [image: Inline image 1]

    Here is the end of the of the log of the micro bosh instance I'm deploying
    from, which shows that there are issues with monit and disk partitioning.

    2013-07-22_01:34:23.84378 #[1812] INFO: loaded new infrastructure settings:
    {"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb", "persistent"=>{}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"}
    2013-07-22_01:34:23.84380 #[1812] INFO: Loaded settings:
    #<Bosh::Agent::Settings:0x000000027c5748
    @settings={"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb", "persistent"=>{}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"},
    @cache_file="/var/vcap/bosh/settings.json">
    2013-07-22_01:34:23.84604 #[1812] WARN: no ntp-servers configured
    2013-07-22_01:34:23.84604 #[1812] INFO: Found unformatted drive
    2013-07-22_01:34:23.84605 #[1812] INFO: Partition /dev/vdb
    2013-07-22_01:34:23.85290 Checking that no-one is using this disk right now
    ...
    2013-07-22_01:34:23.85431 OK
    2013-07-22_01:34:23.85439
    2013-07-22_01:34:23.85439 sfdisk: ERROR: sector 0 does not have an msdos
    signature
    2013-07-22_01:34:23.85441 /dev/vdb: unrecognized partition table type
    2013-07-22_01:34:23.85443 No partitions found
    2013-07-22_01:34:23.85448 Warning: no primary partition is marked bootable
    (active)
    2013-07-22_01:34:23.85449 This does not matter for LILO, but the DOS MBR
    will not boot this disk.
    2013-07-22_01:34:24.03905 If you created or changed a DOS partition,
    /dev/foo7, say, then use dd(1)
    2013-07-22_01:34:24.03907 to zero the first 512 bytes: dd if=/dev/zero
    of=/dev/foo7 bs=512 count=1
    2013-07-22_01:34:24.03907 (See fdisk(8).)
    2013-07-22_01:34:24.08760 #[1812] INFO: Create swap and data partitions
    2013-07-22_01:34:24.09544 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:25.91381 #[1812] INFO: Swapon partition /dev/vdb1
    2013-07-22_01:34:25.91916 #[1812] INFO: Mount data partition /dev/vdb2 to
    /var/vcap/data
    2013-07-22_01:34:25.95949 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:26.12007 chmod: cannot access `/dev/sr0': No such file or
    directory
    2013-07-22_01:34:26.12192 chown: cannot access `/dev/sr0': No such file or
    directory
    2013-07-22_01:34:26.14647 #[1812] INFO: Monit:
    /var/vcap/bosh/etc/monitrc:8: Warning: include files not found
    '/var/vcap/monit/job/*.monitrc'
    2013-07-22_01:34:26.14666 #[1812] INFO: Monit: monit: generated unique
    Monit id 1cb26a82de087daf2f4ba346660c533b and stored to '/root/.monit.id'
    2013-07-22_01:34:26.14682 #[1812] INFO: Monit: Starting monit daemon with
    http interface at [127.0.0.1:2822]
    2013-07-22_01:34:26.14700 #[1812] INFO: Monit:
    2013-07-22_01:34:26.14707 #[1812] INFO: Monit:
    2013-07-22_01:34:27.14039 #[1812] INFO: Monit Service Connection Refused:
    retrying
    2013-07-22_01:34:27.24160 #[1812] INFO: Message processors:
    {"migrate_disk"=>Bosh::Agent::Message::MigrateDisk,
    "list_disk"=>Bosh::Agent::Message::ListDisk,
    "mount_disk"=>Bosh::Agent::Message::MountDisk,
    "unmount_disk"=>Bosh::Agent::Message::UnmountDisk,
    "state"=>Bosh::Agent::Message::State, "drain"=>Bosh::Agent::Message::Drain,
    "apply"=>Bosh::Agent::Message::Apply,
    "compile_package"=>Bosh::Agent::Message::CompilePackage,
    "fetch_logs"=>Bosh::Agent::Message::FetchLogs,
    "ssh"=>Bosh::Agent::Message::Ssh, "ping"=>Bosh::Agent::Message::Ping,
    "noop"=>Bosh::Agent::Message::Noop, "start"=>Bosh::Agent::Message::Start,
    "stop"=>Bosh::Agent::Message::Stop,
    "prepare_network_change"=>Bosh::Agent::Message::PrepareNetworkChange,
    "release_apply_spec"=>Bosh::Agent::Message::ReleaseApplySpec}
    2013-07-22_01:34:27.29674 >> Thin web server (v1.5.0 codename Knife)
    2013-07-22_01:34:27.29679 >> Maximum connections set to 1024
    2013-07-22_01:34:27.29681 >> Listening on 0.0.0.0:6868, CTRL+C to stop
    2013-07-22_01:34:27.30573 10.31.0.20 - - [22/Jul/2013 01:34:27] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:27.30774 #[1812] INFO: Message: {"method"=>"ping",
    "arguments"=>[], "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:27.31998 10.31.0.20 - vcap [22/Jul/2013 01:34:27] "POST
    /agent HTTP/1.1" 200 17 0.0126
    2013-07-22_01:34:33.51347 10.31.0.20 - - [22/Jul/2013 01:34:33] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:33.51559 #[1812] INFO: Message: {"method"=>"mount_disk",
    "arguments"=>["4bf04d59-bf90-4fc2-b532-2438c6042cfb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:33.51767 10.31.0.20 - vcap [22/Jul/2013 01:34:33] "POST
    /agent HTTP/1.1" 200 85 0.0025
    2013-07-22_01:34:34.19121 #[1812] INFO: loaded new infrastructure settings:
    {"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"}
    2013-07-22_01:34:34.19227 #[1812] INFO: MountDisk:
    4bf04d59-bf90-4fc2-b532-2438c6042cfb - {"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}}
    da", "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}}
    2013-07-22_01:34:34.19254 #[1812] INFO: setup disk settings:
    #<Bosh::Agent::Settings:0x00000003725058
    @settings={"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"},
    @cache_file="/var/vcap/bosh/settings.json">
    2013-07-22_01:34:34.19380 #[1812] INFO: Found blank disk /dev/vdc
    2013-07-22_01:34:34.19867
    2013-07-22_01:34:34.19869 sfdisk: ERROR: sector 0 does not have an msdos
    signature
    2013-07-22_01:34:34.19874 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:34.19877 No partitions found
    2013-07-22_01:34:34.52146 10.31.0.20 - - [22/Jul/2013 01:34:34] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:34.52392 #[1812] INFO: Message: {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:34.52393 10.31.0.20 - vcap [22/Jul/2013 01:34:34] "POST
    /agent HTTP/1.1" 200 85 0.0008
    2013-07-22_01:34:35.20387
    2013-07-22_01:34:35.20389 sfdisk: ERROR: sector 0 does not have an msdos
    signature
    2013-07-22_01:34:35.20392 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:35.20393 No partitions found
    2013-07-22_01:34:35.52776 10.31.0.20 - - [22/Jul/2013 01:34:35] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:35.53024 #[1812] INFO: Message: {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:35.53025 10.31.0.20 - vcap [22/Jul/2013 01:34:35] "POST
    /agent HTTP/1.1" 200 85 0.0008
    2013-07-22_01:34:36.20448 #[1812] INFO: Partitioning /dev/vdc
    2013-07-22_01:34:36.20680 Checking that no-one is using this disk right now
    ...
    2013-07-22_01:34:36.20873 OK
    2013-07-22_01:34:36.20882
    2013-07-22_01:34:36.20883 sfdisk: ERROR: sector 0 does not have an msdos
    signature
    2013-07-22_01:34:36.20885 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:36.20889 No partitions found
    2013-07-22_01:34:36.20900 Warning: no primary partition is marked bootable
    (active)
    2013-07-22_01:34:36.20900 This does not matter for LILO, but the DOS MBR
    will not boot this disk.
    2013-07-22_01:34:36.33275 If you created or changed a DOS partition,
    /dev/foo7, say, then use dd(1)
    2013-07-22_01:34:36.33277 to zero the first 512 bytes: dd if=/dev/zero
    of=/dev/foo7 bs=512 count=1
    2013-07-22_01:34:36.33277 (See fdisk(8).)
    2013-07-22_01:34:36.34209 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:36.53399 10.31.0.20 - - [22/Jul/2013 01:34:36] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:36.53615 #[1812] INFO: Message: {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:36.53616 10.31.0.20 - vcap [22/Jul/2013 01:34:36] "POST
    /agent HTTP/1.1" 200 85 0.0009
    2013-07-22_01:34:37.53983 10.31.0.20 - - [22/Jul/2013 01:34:37] "POST
    /agent HTTP/1.1" 401 - 0.0001
    2013-07-22_01:34:37.54213 #[1812] INFO: Message: {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:37.54214 10.31.0.20 - vcap [22/Jul/2013 01:34:37] "POST
    /agent HTTP/1.1" 200 85 0.0007
    2013-07-22_01:34:38.39558 #[1812] INFO: Mounting persistent disk store
    2013-07-22_01:34:38.39569 #[1812] INFO: Mount /dev/vdc1 /var/vcap/store


    On Mon, Jul 22, 2013 at 9:20 AM, Ferran Rodenas wrote:

    Some things you should check:

    - The vm console log to see if the vm started up properly.
    - The vm key-pair. You should be able to ssh to the vm using the private
    key. If there's a permission denied, that means that the vm cannot get the
    private key from the openstack metadata server.
    - The security group used for the vm has all ports opened (or at least the
    ones that appears at the openstack guide)<http://docs.cloudfoundry.com/docs/running/deploying-cf/openstack/deploying_microbosh.html#openstack_security_groups>
    .

    Another approach is to delete the 'bosh_harden' and 'bosh_harden_ssh' from
    your spec file<https://github.com/cloudfoundry/bosh/blob/master/stemcell_builder/spec/stemcell-openstack.spec#L34> before
    building the stemcell. This will allow you to ssh as root and check inside
    the vm if the bosh agent is running properly.

    - Ferdy


    2013/7/22 Kalonji Bankole <kalonb91@gmail.com>
    Hello

    The stemcells acquired from the public repository work fine, but my
    primary focus is to get my custom stemcell working. It seems that the
    custom stemcell seems to fail at deploying the VMs, which are all
    unresponsive, and then hangs at the compiling packages stage. I cannot SSH
    into the VMs either. I've built the stemcell using the instructions above,
    is there perhaps an alternative procedure I could possibly use?

    Thanks,
    Kalonji Bankole
    On Friday, July 19, 2013 1:56:00 AM UTC-7, Heiko Krämer wrote:

    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env is working
    correctly.

    cd /var/vcap/stemcells/ && wget http://bosh-jenkins-artifacts.**
    s3.amazonaws.com/micro-bosh-**stemcell/openstack/latest-**
    micro-bosh-stemcell-openstack.**tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz>&& wget
    http://bosh-jenkins-artifacts.**s3.amazonaws.com/bosh-**
    stemcell/openstack/latest-**bosh-stemcell-openstack.tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz>


    Cheers
    Heiko

    On 19.07.2013 07:24, Kalonji Bankole wrote:

    Hello,

    At this point I am able to generate a basic stemcell of version
    1.5.0.pre.3 using the steps above. I am able to successfully upload the
    stemcell as well, but when attempting to deploy bosh, a time-out occurs
    during the "Compiling packages" stage. Slightly older stemcells obtained
    from the public repository (version 1.5.0.pre2) allow for a successful
    deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in
    the public openstack stemcell repository, so I was wondering if there is is
    a possibility that version 1.5.0.pre.3 stemcells are not fully supported
    yet? If so, what do I need to alter to create a 1.5.0.pre2 stemcell using
    the rake build? And where can I find a valid 1.5.0.pre.3 stemcell to
    attempt a deployment with?

    My issue appears to be identical to the thread Dhruv's thread here<https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking through
    the debug log. Do you have any suggestions of where I might continue from
    here?

    Thanks
    Kalonji Bankole



    -- anynines.com
  • Heiko Krämer at Jul 23, 2013 at 8:24 am
    Hi Kalonji,

    that looks good so far. You don't have any issues that's normal, bosh
    will create a new ephemeral and volume. This disks don't have any
    partions or filesystems and it will be created on boot.

    Just try the follow command if you instance have finished with the boot
    process:

    nmap <IP> -sS -p 22

    and check if the port is filtered. If yes Ferdy are right you don't have
    the correct security groups.


    In addition you should check you nova-compute.log on you compute server
    if you see any errors or something weird stuff.




    Cheers
    Heiko
    On 22.07.2013 19:21, Kalonji Bankole wrote:
    Thank you for the response. I am using the same manifest file for
    deploying both the public stemcell and the custom stemcell. The only
    change made to the manifest file when switching between these
    stemcells is the stemcell version number (1.5.0.pre2 vs 1.5.0.pre.3,
    respectively). Does it matter that I'm attempting to deploy a
    1.5.0pre.3 stemcell with a 1.5.0.pre.2 agent?

    The specified security group ensures that all necessary ports are
    open, and the path to the key is correct as well. Since the public
    stemcell's deployment is relatively fine, and both stemcells are using
    the same manifest file, I'm not sure if the key, networking, and
    security groups are an issue.

    Running the bosh vms commands shows that the VMs are not starting up
    properly.

    Inline image 1

    Here is the end of the of the log of the micro bosh instance I'm
    deploying from, which shows that there are issues with monit and disk
    partitioning.

    2013-07-22_01:34:23.84378 #[1812] INFO: loaded new infrastructure
    settings: {"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb", "persistent"=>{}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"}
    2013-07-22_01:34:23.84380 #[1812] INFO: Loaded settings:
    #<Bosh::Agent::Settings:0x000000027c5748
    @settings={"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb", "persistent"=>{}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"},
    @cache_file="/var/vcap/bosh/settings.json">
    2013-07-22_01:34:23.84604 #[1812] WARN: no ntp-servers configured
    2013-07-22_01:34:23.84604 #[1812] INFO: Found unformatted drive
    2013-07-22_01:34:23.84605 #[1812] INFO: Partition /dev/vdb
    2013-07-22_01:34:23.85290 Checking that no-one is using this disk
    right now ...
    2013-07-22_01:34:23.85431 OK
    2013-07-22_01:34:23.85439
    2013-07-22_01:34:23.85439 sfdisk: ERROR: sector 0 does not have an
    msdos signature
    2013-07-22_01:34:23.85441 /dev/vdb: unrecognized partition table type
    2013-07-22_01:34:23.85443 No partitions found
    2013-07-22_01:34:23.85448 Warning: no primary partition is marked
    bootable (active)
    2013-07-22_01:34:23.85449 This does not matter for LILO, but the DOS
    MBR will not boot this disk.
    2013-07-22_01:34:24.03905 If you created or changed a DOS partition,
    /dev/foo7, say, then use dd(1)
    2013-07-22_01:34:24.03907 to zero the first 512 bytes: dd
    if=/dev/zero of=/dev/foo7 bs=512 count=1
    2013-07-22_01:34:24.03907 (See fdisk(8).)
    2013-07-22_01:34:24.08760 #[1812] INFO: Create swap and data partitions
    2013-07-22_01:34:24.09544 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:25.91381 #[1812] INFO: Swapon partition /dev/vdb1
    2013-07-22_01:34:25.91916 #[1812] INFO: Mount data partition /dev/vdb2
    to /var/vcap/data
    2013-07-22_01:34:25.95949 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:26.12007 chmod: cannot access `/dev/sr0': No such
    file or directory
    2013-07-22_01:34:26.12192 chown: cannot access `/dev/sr0': No such
    file or directory
    2013-07-22_01:34:26.14647 #[1812] INFO: Monit:
    /var/vcap/bosh/etc/monitrc:8: Warning: include files not found
    '/var/vcap/monit/job/*.monitrc'
    2013-07-22_01:34:26.14666 #[1812] INFO: Monit: monit: generated unique
    Monit id 1cb26a82de087daf2f4ba346660c533b and stored to
    '/root/.monit.id <http://monit.id>'
    2013-07-22_01:34:26.14682 #[1812] INFO: Monit: Starting monit daemon
    with http interface at [127.0.0.1:2822 <http://127.0.0.1:2822>]
    2013-07-22_01:34:26.14700 #[1812] INFO: Monit:
    2013-07-22_01:34:26.14707 #[1812] INFO: Monit:
    2013-07-22_01:34:27.14039 #[1812] INFO: Monit Service Connection
    Refused: retrying
    2013-07-22_01:34:27.24160 #[1812] INFO: Message processors:
    {"migrate_disk"=>Bosh::Agent::Message::MigrateDisk,
    "list_disk"=>Bosh::Agent::Message::ListDisk,
    "mount_disk"=>Bosh::Agent::Message::MountDisk,
    "unmount_disk"=>Bosh::Agent::Message::UnmountDisk,
    "state"=>Bosh::Agent::Message::State,
    "drain"=>Bosh::Agent::Message::Drain,
    "apply"=>Bosh::Agent::Message::Apply,
    "compile_package"=>Bosh::Agent::Message::CompilePackage,
    "fetch_logs"=>Bosh::Agent::Message::FetchLogs,
    "ssh"=>Bosh::Agent::Message::Ssh, "ping"=>Bosh::Agent::Message::Ping,
    "noop"=>Bosh::Agent::Message::Noop,
    "start"=>Bosh::Agent::Message::Start,
    "stop"=>Bosh::Agent::Message::Stop,
    "prepare_network_change"=>Bosh::Agent::Message::PrepareNetworkChange,
    "release_apply_spec"=>Bosh::Agent::Message::ReleaseApplySpec}
    2013-07-22_01:34:27.29674 >> Thin web server (v1.5.0 codename Knife)
    2013-07-22_01:34:27.29679 >> Maximum connections set to 1024
    2013-07-22_01:34:27.29681 >> Listening on 0.0.0.0:6868
    <http://0.0.0.0:6868>, CTRL+C to stop
    2013-07-22_01:34:27.30573 10.31.0.20 - - [22/Jul/2013 01:34:27] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:27.30774 #[1812] INFO: Message: {"method"=>"ping",
    "arguments"=>[], "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:27.31998 10.31.0.20 - vcap [22/Jul/2013 01:34:27]
    "POST /agent HTTP/1.1" 200 17 0.0126
    2013-07-22_01:34:33.51347 10.31.0.20 - - [22/Jul/2013 01:34:33] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:33.51559 #[1812] INFO: Message:
    {"method"=>"mount_disk",
    "arguments"=>["4bf04d59-bf90-4fc2-b532-2438c6042cfb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:33.51767 10.31.0.20 - vcap [22/Jul/2013 01:34:33]
    "POST /agent HTTP/1.1" 200 85 0.0025
    2013-07-22_01:34:34.19121 #[1812] INFO: loaded new infrastructure
    settings: {"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"}
    2013-07-22_01:34:34.19227 #[1812] INFO: MountDisk:
    4bf04d59-bf90-4fc2-b532-2438c6042cfb - {"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}}
    da", "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}}
    2013-07-22_01:34:34.19254 #[1812] INFO: setup disk settings:
    #<Bosh::Agent::Settings:0x00000003725058
    @settings={"vm"=>{"name"=>"vm-80b762d6-a96b-44a4-b10d-b7f5ad7e9757"},
    "agent_id"=>"bm-0167772d-99e1-4a45-b135-14505552d300",
    "networks"=>{"bosh"=>{"cloud_properties"=>{}, "netmask"=>nil,
    "gateway"=>nil, "ip"=>nil, "dns"=>nil, "type"=>"dynamic",
    "default"=>["dns", "gateway"]}}, "disks"=>{"system"=>"/dev/vda",
    "ephemeral"=>"/dev/vdb",
    "persistent"=>{"4bf04d59-bf90-4fc2-b532-2438c6042cfb"=>"/dev/vdc"}},
    "env"=>{"bosh"=>{"password"=>nil}}, "ntp"=>[],
    "blobstore"=>{"plugin"=>"local",
    "properties"=>{"blobstore_path"=>"/var/vcap/micro_bosh/data/cache"}},
    "mbus"=>"http://vcap:b00tstrap@0.0.0.0:6868"},
    @cache_file="/var/vcap/bosh/settings.json">
    2013-07-22_01:34:34.19380 #[1812] INFO: Found blank disk /dev/vdc
    2013-07-22_01:34:34.19867
    2013-07-22_01:34:34.19869 sfdisk: ERROR: sector 0 does not have an
    msdos signature
    2013-07-22_01:34:34.19874 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:34.19877 No partitions found
    2013-07-22_01:34:34.52146 10.31.0.20 - - [22/Jul/2013 01:34:34] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:34.52392 #[1812] INFO: Message:
    {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:34.52393 10.31.0.20 - vcap [22/Jul/2013 01:34:34]
    "POST /agent HTTP/1.1" 200 85 0.0008
    2013-07-22_01:34:35.20387
    2013-07-22_01:34:35.20389 sfdisk: ERROR: sector 0 does not have an
    msdos signature
    2013-07-22_01:34:35.20392 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:35.20393 No partitions found
    2013-07-22_01:34:35.52776 10.31.0.20 - - [22/Jul/2013 01:34:35] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:35.53024 #[1812] INFO: Message:
    {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:35.53025 10.31.0.20 - vcap [22/Jul/2013 01:34:35]
    "POST /agent HTTP/1.1" 200 85 0.0008
    2013-07-22_01:34:36.20448 #[1812] INFO: Partitioning /dev/vdc
    2013-07-22_01:34:36.20680 Checking that no-one is using this disk
    right now ...
    2013-07-22_01:34:36.20873 OK
    2013-07-22_01:34:36.20882
    2013-07-22_01:34:36.20883 sfdisk: ERROR: sector 0 does not have an
    msdos signature
    2013-07-22_01:34:36.20885 /dev/vdc: unrecognized partition table type
    2013-07-22_01:34:36.20889 No partitions found
    2013-07-22_01:34:36.20900 Warning: no primary partition is marked
    bootable (active)
    2013-07-22_01:34:36.20900 This does not matter for LILO, but the DOS
    MBR will not boot this disk.
    2013-07-22_01:34:36.33275 If you created or changed a DOS partition,
    /dev/foo7, say, then use dd(1)
    2013-07-22_01:34:36.33277 to zero the first 512 bytes: dd
    if=/dev/zero of=/dev/foo7 bs=512 count=1
    2013-07-22_01:34:36.33277 (See fdisk(8).)
    2013-07-22_01:34:36.34209 mke2fs 1.41.11 (14-Mar-2010)
    2013-07-22_01:34:36.53399 10.31.0.20 - - [22/Jul/2013 01:34:36] "POST
    /agent HTTP/1.1" 401 - 0.0002
    2013-07-22_01:34:36.53615 #[1812] INFO: Message:
    {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:36.53616 10.31.0.20 - vcap [22/Jul/2013 01:34:36]
    "POST /agent HTTP/1.1" 200 85 0.0009
    2013-07-22_01:34:37.53983 10.31.0.20 - - [22/Jul/2013 01:34:37] "POST
    /agent HTTP/1.1" 401 - 0.0001
    2013-07-22_01:34:37.54213 #[1812] INFO: Message:
    {"method"=>"get_task",
    "arguments"=>["ba128df4-3615-472d-b878-3191393f3ddb"],
    "reply_to"=>"bm-0167772d-99e1-4a45-b135-14505552d300"}
    2013-07-22_01:34:37.54214 10.31.0.20 - vcap [22/Jul/2013 01:34:37]
    "POST /agent HTTP/1.1" 200 85 0.0007
    2013-07-22_01:34:38.39558 #[1812] INFO: Mounting persistent disk store
    2013-07-22_01:34:38.39569 #[1812] INFO: Mount /dev/vdc1 /var/vcap/store



    On Mon, Jul 22, 2013 at 9:20 AM, Ferran Rodenas wrote:

    Some things you should check:

    - The vm console log to see if the vm started up properly.
    - The vm key-pair. You should be able to ssh to the vm using the
    private key. If there's a permission denied, that means that the
    vm cannot get the private key from the openstack metadata server.
    - The security group used for the vm has all ports opened (or at
    least the ones that appears at the openstack guide)
    <http://docs.cloudfoundry.com/docs/running/deploying-cf/openstack/deploying_microbosh.html#openstack_security_groups>.

    Another approach is to delete the 'bosh_harden' and
    'bosh_harden_ssh' from your spec file
    <https://github.com/cloudfoundry/bosh/blob/master/stemcell_builder/spec/stemcell-openstack.spec#L34> before
    building the stemcell. This will allow you to ssh as root and
    check inside the vm if the bosh agent is running properly.

    - Ferdy


    2013/7/22 Kalonji Bankole <kalonb91@gmail.com

    Hello

    The stemcells acquired from the public repository work fine,
    but my primary focus is to get my custom stemcell working. It
    seems that the custom stemcell seems to fail at deploying the
    VMs, which are all unresponsive, and then hangs at the
    compiling packages stage. I cannot SSH into the VMs either.
    I've built the stemcell using the instructions above, is there
    perhaps an alternative procedure I could possibly use?

    Thanks,
    Kalonji Bankole

    On Friday, July 19, 2013 1:56:00 AM UTC-7, Heiko Krämer wrote:

    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env
    is working correctly.

    cd /var/vcap/stemcells/ && wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz
    && wget
    http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz


    Cheers
    Heiko
    On 19.07.2013 07:24, Kalonji Bankole wrote:
    Hello,

    At this point I am able to generate a basic stemcell of
    version 1.5.0.pre.3 using the steps above. I am able to
    successfully upload the stemcell as well, but when
    attempting to deploy bosh, a time-out occurs during the
    "Compiling packages" stage. Slightly older stemcells
    obtained from the public repository (version 1.5.0.pre2)
    allow for a successful deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet
    available in the public openstack stemcell repository, so
    I was wondering if there is is a possibility that version
    1.5.0.pre.3 stemcells are not fully supported yet? If so,
    what do I need to alter to create a 1.5.0.pre2 stemcell
    using the rake build? And where can I find a valid
    1.5.0.pre.3 stemcell to attempt a deployment with?

    My issue appears to be identical to the thread Dhruv's
    thread here
    <https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than
    looking through the debug log. Do you have any
    suggestions of where I might continue from here?

    Thanks
    Kalonji Bankole

    --
    anynines.com <http://anynines.com>


    --
    --
    anynines.com
  • Dr Nic Williams at Jul 22, 2013 at 4:36 pm
    Quick question - have you eliminated all external possible causes -
    networking issues, security groups, etc?

    On Mon, Jul 22, 2013 at 9:04 AM, Kalonji Bankole wrote:

    Hello

    The stemcells acquired from the public repository work fine, but my
    primary focus is to get my custom stemcell working. It seems that the
    custom stemcell seems to fail at deploying the VMs, which are all
    unresponsive, and then hangs at the compiling packages stage. I cannot SSH
    into the VMs either. I've built the stemcell using the instructions above,
    is there perhaps an alternative procedure I could possibly use?

    Thanks,
    Kalonji Bankole
    On Friday, July 19, 2013 1:56:00 AM UTC-7, Heiko Krämer wrote:

    Hi Kalonji,

    you can use for testing the latest openstack stemcell builds.
    They are working perfectly and you can test if your OS env is working
    correctly.

    cd /var/vcap/stemcells/ && wget http://bosh-jenkins-artifacts.**
    s3.amazonaws.com/micro-bosh-**stemcell/openstack/latest-**
    micro-bosh-stemcell-openstack.**tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/micro-bosh-stemcell/openstack/latest-micro-bosh-stemcell-openstack.tgz>&& wget
    http://bosh-jenkins-artifacts.**s3.amazonaws.com/bosh-**
    stemcell/openstack/latest-**bosh-stemcell-openstack.tgz<http://bosh-jenkins-artifacts.s3.amazonaws.com/bosh-stemcell/openstack/latest-bosh-stemcell-openstack.tgz>


    Cheers
    Heiko

    On 19.07.2013 07:24, Kalonji Bankole wrote:

    Hello,

    At this point I am able to generate a basic stemcell of version
    1.5.0.pre.3 using the steps above. I am able to successfully upload the
    stemcell as well, but when attempting to deploy bosh, a time-out occurs
    during the "Compiling packages" stage. Slightly older stemcells obtained
    from the public repository (version 1.5.0.pre2) allow for a successful
    deployment.

    I've also noticed that 1.5.0.pre.3 stemcells are not yet available in the
    public openstack stemcell repository, so I was wondering if there is is a
    possibility that version 1.5.0.pre.3 stemcells are not fully supported yet?
    If so, what do I need to alter to create a 1.5.0.pre2 stemcell using the
    rake build? And where can I find a valid 1.5.0.pre.3 stemcell to attempt a
    deployment with?

    My issue appears to be identical to the thread Dhruv's thread here<https://groups.google.com/a/cloudfoundry.org/d/msg/bosh-dev/jXd7l-qI__Y/0vBHnI3UDgwJ>,
    but I did not see any resolution to the issue, other than looking through
    the debug log. Do you have any suggestions of where I might continue from
    here?

    Thanks
    Kalonji Bankole



    -- anynines.com

    --
    Dr Nic Williams
    Stark & Wayne LLC - consultancy for Cloud Foundry users
    http://drnicwilliams.com
    http://starkandwayne.com
    cell +1 (415) 860-2185
    twitter @drnic
  • Animesh Singh at Apr 4, 2013 at 6:55 pm
    Ferdy, Thanks.

    I did see the examples. There is *no* one example which is purely DHCP. I
    do see either floating / or static ips in all the manifest files.
    Is that something we will have to deal with ? If yes, then the quantum
    commands for assigning floating ips should be taken care of by CPI ?

    Also any particular version of BOSH and CF we have to have for it to work
    with Quantum
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment
    to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 4, 2013 at 8:12 pm
    You can delete floating IP's, but then you should guess what IP address is
    assigned, i.e. for director.

    See my previous message for what version of bosh you should use, depends on
    what type of network conf are you going to use (dhcp vs static).

    - Ferdy


    2013/4/4 Animesh Singh <animation2007@gmail.com>
    Ferdy, Thanks.

    I did see the examples. There is *no* one example which is purely DHCP. I
    do see either floating / or static ips in all the manifest files.
    Is that something we will have to deal with ? If yes, then the quantum
    commands for assigning floating ips should be taken care of by CPI ?

    Also any particular version of BOSH and CF we have to have for it to work
    with Quantum
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Anderson L Jason at Apr 5, 2013 at 12:32 am
    Hi Ferdy,

    I am also trying to get Cloud Foundry deployed onto OpenStack w/ Quantum
    using BOSH. I would like to use DHCP but not sure which of these three
    examples I should use.

        -
        https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-dns.yml
        -
        https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-static.yml
        -
        https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-vip.yml

    The Openstack-DNS one looks the cleanest but seems to rely on PowerDNS
    which I know had some issues but maybe are now fixed? Assuming I delete
    the director and powerdns static IPs parts in the OpenStack-DNS example,
    would I just use the bosh vms command to determine the director IP?
    Finally if I do use the DNS example, will I need to edit the stemcells and
    update my microbosh manifest as you mentioned in your first post?
    Appreciate your help,

      - Jason Anderson
    On Thursday, April 4, 2013 1:12:40 PM UTC-7, ferdy wrote:

    You can delete floating IP's, but then you should guess what IP address is
    assigned, i.e. for director.

    See my previous message for what version of bosh you should use, depends
    on what type of network conf are you going to use (dhcp vs static).

    - Ferdy


    2013/4/4 Animesh Singh <animat...@gmail.com <javascript:>>
    Ferdy, Thanks.

    I did see the examples. There is *no* one example which is purely DHCP.
    I do see either floating / or static ips in all the manifest files.
    Is that something we will have to deal with ? If yes, then the quantum
    commands for assigning floating ips should be taken care of by CPI ?

    Also any particular version of BOSH and CF we have to have for it to work
    with Quantum
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 5, 2013 at 8:21 am
    Yes, you can use the DNS example and delete the Floating IP's. You'll need
    to build new stemcells and gems and deploy a new version on microBosh. You
    don't need to modify the microBosh manifest, the ip and net_id options are
    only used when using static IP's.

    - Ferdy


    2013/4/5 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I am also trying to get Cloud Foundry deployed onto OpenStack w/ Quantum
    using BOSH. I would like to use DHCP but not sure which of these three
    examples I should use.

    -
    https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-dns.yml
    -
    https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-static.yml
    -
    https://github.com/cloudfoundry/bosh/blob/master/release/examples/bosh-openstack-vip.yml

    The Openstack-DNS one looks the cleanest but seems to rely on PowerDNS
    which I know had some issues but maybe are now fixed? Assuming I delete
    the director and powerdns static IPs parts in the OpenStack-DNS example,
    would I just use the bosh vms command to determine the director IP?
    Finally if I do use the DNS example, will I need to edit the stemcells and
    update my microbosh manifest as you mentioned in your first post?
    Appreciate your help,

    - Jason Anderson

    On Thursday, April 4, 2013 1:12:40 PM UTC-7, ferdy wrote:

    You can delete floating IP's, but then you should guess what IP address
    is assigned, i.e. for director.

    See my previous message for what version of bosh you should use, depends
    on what type of network conf are you going to use (dhcp vs static).

    - Ferdy


    2013/4/4 Animesh Singh <animat...@gmail.com>

    Ferdy, Thanks.
    I did see the examples. There is *no* one example which is purely DHCP.
    I do see either floating / or static ips in all the manifest files.
    Is that something we will have to deal with ? If yes, then the quantum
    commands for assigning floating ips should be taken care of by CPI ?

    Also any particular version of BOSH and CF we have to have for it to
    work with Quantum
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum
    ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 8, 2013 at 6:32 pm
    Hi Ferdy
    We were looking at your examples, and tried with network type set to
    "manual"
    It came back with an error saying
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment
    to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 8, 2013 at 6:43 pm
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
       type: manual
       label: bosh-net # Name of your Quantum network
       vip: 172.24.4.227 # Floating IP to assign to your microBosh
       ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one of
    the subnets IP range)
       cloud_properties:
         net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network"


    It came with the error that "manual" type is not supported. Are we back
    level for this ? Also the net_id is the UUID of the private network, not
    the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment
    to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 8, 2013 at 7:42 pm
    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animation2007@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one
    of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network"


    It came with the error that "manual" type is not supported. Are we back
    level for this ? Also the net_id is the UUID of the private network, not
    the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 8, 2013 at 11:35 pm
    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a custom
    stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com <javascript:>>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one
    of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network"


    It came with the error that "manual" type is not supported. Are we back
    level for this ? Also the net_id is the UUID of the private network, not
    the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 9, 2013 at 12:55 am
    Also one thing I am noticing is the version of fog I am getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one
    of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum
    network"


    It came with the error that "manual" type is not supported. Are we back
    level for this ? Also the net_id is the UUID of the private network, not
    the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum
    ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 9, 2013 at 8:36 am
    Can you provide more details about what's failing with eventmachine? Can
    you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    Also one thing I am noticing is the version of fog I am getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in
    one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da773fdd # UUID of your
    Quantum network"


    It came with the error that "manual" type is not supported. Are we back
    level for this ? Also the net_id is the UUID of the private network, not
    the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 9, 2013 at 8:46 am
    I was able to go beyong by using eventmachine 1.0.1 version, and created
    microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_builder
    /var/tmp/bosh/bosh_agent-1.5.0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work...
    sudo env
      /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/build/bin/build_from_spec.s
            h /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0
      .pre.3-28522/build/spec/stemcell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.0.p
      re.3-28522/build/etc/settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the
    stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine? Can
    you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    Also one thing I am noticing is the version of fog I am getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in
    one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da773fdd # UUID of your
    Quantum network"


    It came with the error that "manual" type is not supported. Are we
    back level for this ? Also the net_id is the UUID of the private network,
    not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 9, 2013 at 8:50 am
    There're some missing packages, be sure to install (via apt-get
    install): build-essential
    libsqlite3-dev rsync libmysqlclient-dev libxml2-dev libxslt-dev
    libpq-dev genisoimage
    debootstrap kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and created
    microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_builder
    /var/tmp/bosh/bosh_agent-1.5.0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work...
    sudo env
    /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/build/bin/build_from_spec.s
    h /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0
    .pre.3-28522/build/spec/stemcell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.0.p
    re.3-28522/build/etc/settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the
    stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine? Can
    you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in
    one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da773fdd # UUID of your
    Quantum network"


    It came with the error that "manual" type is not supported. Are we
    back level for this ? Also the net_id is the UUID of the private network,
    not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 9, 2013 at 7:31 pm
    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?
    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get install): build-essential
    libsqlite3-dev rsync libmysqlclient-dev libxml2-dev libxslt-dev libpq-dev genisoimage
    debootstrap kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com <javascript:>>
    I was able to go beyong by using eventmachine 1.0.1 version, and created
    microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_builder
    /var/tmp/bosh/bosh_agent-1.5.0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work...
    sudo env
    /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/build/bin/build_from_spec.s
    h /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0
    .pre.3-28522/build/spec/stemcell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.0.p
    re.3-28522/build/etc/settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the
    stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <frod...@gmail.com<javascript:>
    wrote:
    Can you provide more details about what's failing with eventmachine? Can
    you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com <javascript:>>
    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in
    one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da773fdd # UUID of your
    Quantum network"


    It came with the error that "manual" type is not supported. Are we
    back level for this ? Also the net_id is the UUID of the private network,
    not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 9, 2013 at 7:41 pm
    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get install): build-essential
    libsqlite3-dev rsync libmysqlclient-dev libxml2-dev libxslt-dev
    libpq-dev genisoimage debootstrap kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and created
    microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**builder
    /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/build/bin/build_*
    *from_spec.s h /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**stemcell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.**0.p re.3-28522/build/etc/**
    settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the
    stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine?
    Can you install the gem as a standalone (gem install eventmachine -v
    0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be
    in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da**773fdd # UUID of
    your Quantum network"


    It came with the error that "manual" type is not supported. Are we
    back level for this ? Also the net_id is the UUID of the private network,
    not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh at Apr 10, 2013 at 8:37 am
    Thanks . I will keep inquiring , though if you can post on this thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10 couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a dependency on it it seems

    Sent from my iPhone
    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animation2007@gmail.com>
    Seems I am running into lot of issues with eventmachine dependencies on 0.12.1 version etc. It maybe wise to wait for official stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:
    There're some missing packages, be sure to install (via apt-get install): build-essential libsqlite3-dev rsync libmysqlclient-dev libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_builder /var/tmp/bosh/bosh_agent-1.5.0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/build/bin/build_from_spec.s h /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/stemcell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.0.p re.3-28522/build/etc/settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:
    Can you provide more details about what's failing with eventmachine? Can you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    Also one thing I am noticing is the version of fog I am getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum network"


    It came with the error that "manual" type is not supported. Are we back level for this ? Also the net_id is the UUID of the private network, not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Anderson L Jason at Apr 10, 2013 at 5:16 pm
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

        1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI.
        2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
        3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

      - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com <javascript:>>
    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**builder
    /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/build/bin/build_
    **from_spec.s h /var/tmp/bosh/bosh_agent-1.5.**0.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**stemcell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.**0.p re.3-28522/build/etc/**
    settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create
    the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine?
    Can you install the gem as a standalone (gem install eventmachine -v
    0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a
    custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be
    in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da**773fdd # UUID of
    your Quantum network"


    It came with the error that "manual" type is not supported. Are we
    back level for this ? Also the net_id is the UUID of the private network,
    not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 10, 2013 at 11:06 pm
    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells and
    ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells. When
    does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the manually
    created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**
    stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create
    the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine?
    Can you install the gem as a standalone (gem install eventmachine -v
    0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating
    a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual
    networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be
    in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID of
    your Quantum network"


    It came with the error that "manual" type is not supported. Are
    we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:

    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh at Apr 11, 2013 at 12:21 am
    Ferdy on the same node , is the event machine 0.12.10 issue only on Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone
    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells and ones I'd make using you're previously defined process? I kept getting "Error 100: Floating IP <IP Address> not allocated" even though I allocated the IP through Quantum. Looks like it is using nova-network instead so perhaps a limitation with the CPI. <- Umm, should work with the new stemcells. When does this happens? When deploying a microBosh or when deploying other deployments? Can you please paste the micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but requires creating new stemcells? <- Yes, old stemcells doesn't support manual networks

    3. Dynamic IPs are supported with Quantum in both the old and the manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old stemcells and ones I'd make using you're previously defined process? I kept getting "Error 100: Floating IP <IP Address> not allocated" even though I allocated the IP through Quantum. Looks like it is using nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:
    Thanks . I will keep inquiring , though if you can post on this thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10 couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a dependency on it it seems

    Sent from my iPhone
    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    Seems I am running into lot of issues with eventmachine dependencies on 0.12.1 version etc. It maybe wise to wait for official stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:
    There're some missing packages, be sure to install (via apt-get install): build-essential libsqlite3-dev rsync libmysqlclient-dev libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/release/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_builder /var/tmp/bosh/bosh_agent-1.5.0.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/build/bin/build_from_spec.s h /var/tmp/bosh/bosh_agent-1.5.0.pre.3-28522/work /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/stemcell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.0.p re.3-28522/build/etc/settings.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:
    Can you provide more details about what's failing with eventmachine? Can you install the gem as a standalone (gem install eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    Also one thing I am noticing is the version of fog I am getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating a custom stemcell is failing with a dependency on eventmachine ((0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-2099da773fdd # UUID of your Quantum network"


    It came with the error that "manual" type is not supported. Are we back level for this ? Also the net_id is the UUID of the private network, not the network from where we pull floating ips I would guess ?
    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with Quantum ?
    We got it running with nova-network,. and are now upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 11, 2013 at 12:39 pm
    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on Ubuntu
    12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells and
    ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells. When
    does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the manually
    created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**
    stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create
    the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with eventmachine?
    Can you install the gem as a standalone (gem install eventmachine -v
    0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for creating
    a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should
    be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID
    of your Quantum network"


    It came with the error that "manual" type is not supported. Are
    we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested with
    Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 11, 2013 at 5:23 pm
    Its ruby 1.9.3 - Unless you have other version. Also the install is fine
    with eveyrthing else - and goes all along -except for eventmachine. I am
    trying again on 12-10, and will post you the logs when eventmachine fails

    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated" even
    though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**
    stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create
    the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should
    be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID
    of your Quantum network"


    It came with the error that "manual" type is not supported. Are
    we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 11, 2013 at 5:46 pm
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
             ERROR: Failed to build gem native extension.

             /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int
    ConnectionDescriptor::SendOutboundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid
    ConnectionDescriptor::_WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce()â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToServer(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToUnixServer(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateTcpServer(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::OpenDatagramSocket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateUnixDomainServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int, const
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE, VALUE,
    VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated" even
    though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies on
    0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/**
    stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it create
    the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should
    be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID
    of your Quantum network"


    It came with the error that "manual" type is not supported. Are
    we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading the
    environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 12, 2013 at 12:06 pm
    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native
    -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animation2007@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int
    ConnectionDescriptor::SendOutboundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid
    ConnectionDescriptor::_WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce()â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToServer(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToUnixServer(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateTcpServer(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::OpenDatagramSocket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateUnixDomainServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int, const
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated" even
    though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies
    on 0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/*
    *stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should
    be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID
    of your Quantum network"


    It came with the error that "manual" type is not supported.
    Are we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading
    the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Animesh Singh at Apr 12, 2013 at 3:57 pm
    Thanks. Tried it few days ago , and it got me past the issue for bundle
    install commands , but the rake commands for stemcell were still failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I was
    able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum errors
    while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native
    -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animation2007@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int
    ConnectionDescriptor::SendOutboundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid
    ConnectionDescriptor::_WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce()â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToServer(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToUnixServer(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateTcpServer(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::OpenDatagramSocket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateUnixDomainServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned intâ
    from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int, const
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated" even
    though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this thread
    once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies
    on 0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/*
    *stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh (should
    be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd # UUID
    of your Quantum network"


    It came with the error that "manual" type is not supported.
    Are we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading
    the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 12, 2013 at 5:21 pm
    Download these prebuilt stemcells. It have been tested with dynamic and
    manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz
    microBosh stemcell:
    http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz



    - Ferdy



    2013/4/12 Animesh Singh <animation2007@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for bundle
    install commands , but the rake commands for stemcell were still failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I was
    able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum errors
    while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2 -pipe -march=native
    -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animation2007@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int
    ConnectionDescriptor::SendOutboundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid
    ConnectionDescriptor::_WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce()â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToServer(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToUnixServer(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateTcpServer(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::OpenDatagramSocket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateUnixDomainServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int, void*,
    size_t)â, declared with attribute warn_unused_result [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animation2007@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated" even
    though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies
    on 0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?



    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas wrote:

    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd #
    UUID of your Quantum network"


    It came with the error that "manual" type is not supported.
    Are we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading
    the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Anderson L Jason at Apr 13, 2013 at 3:37 pm
    Hi Ferdy,

    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/bosh_agent/infrastructure/openstack/registry.rb)
    but maybe I'm missing something. Much appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json
    (Bosh::Agent::LoadSettingsError)
    2013-04-13_15:31:20.76536 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:25:in
    `load'
    2013-04-13_15:31:20.76542 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:14:in
    `load'
    2013-04-13_15:31:20.76544 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:97:in
    `start'
    2013-04-13_15:31:20.76549 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:76:in
    `run'
    2013-04-13_15:31:20.76551 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/bin/bosh_agent:96:in
    `<top (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:23:in
    `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:23:in
    `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic and
    manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz
    microBosh stemcell: http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz



    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com <javascript:>>
    Thanks. Tried it few days ago , and it got me past the issue for bundle
    install commands , but the rake commands for stemcell were still failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I
    was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum errors
    while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas <frod...@gmail.com<javascript:>>
    wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2 -pipe -march=native
    -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com <javascript:>>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int
    ConnectionDescriptor::SendOutboundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid
    ConnectionDescriptor::_WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce()â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToServer(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::ConnectToUnixServer(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateTcpServer(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::OpenDatagramSocket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::CreateUnixDomainServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors



    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas <frod...@gmail.com<javascript:>
    wrote:
    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com <javascript:>>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com<javascript:>>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old stemcells
    and ones I'd make using you're previously defined process? I kept getting "Error
    100: Floating IP <IP Address> not allocated" even though I allocated the IP
    through Quantum. Looks like it is using nova-network instead so perhaps a
    limitation with the CPI. <- Umm, should work with the new stemcells.
    When does this happens? When deploying a microBosh or when deploying other
    deployments? Can you please paste the micro_bosh or task log so I can see
    what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com <javascript:>>
    Hi Ferdy,

    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.7.0.tgz) and while looking back at your posts
    I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine dependencies
    on 0.12.1 version etc. It maybe wise to wait for official stemcell to be
    published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas**e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui**lder
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-2 8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0**
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.****
    0.pre.3-28522/build/bin/build_****from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0**.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc**ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**.p
    re.3-28522/build/etc/**settings**.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <frod...@gmail.com
    wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da****773fdd #
    UUID of your Quantum network"


    It came with the error that "manual" type is not supported.
    Are we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading
    the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled ?
  • Ferran Rodenas at Apr 14, 2013 at 5:22 pm
    At this point, the registry should be running on you local machine (where
    you executed bosh micro deploy ...), not in the microBosh VM. You would see
    a bosh_registry.log in your deployments directory. Can you check if that
    file exists and which are the contents?

    - Ferdy


    2013/4/13 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/bosh_agent/infrastructure/openstack/registry.rb)
    but maybe I'm missing something. Much appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json
    (Bosh::Agent::LoadSettingsError)
    2013-04-13_15:31:20.76536 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:25:in
    `load'
    2013-04-13_15:31:20.76542 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:14:in
    `load'
    2013-04-13_15:31:20.76544 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:97:in
    `start'
    2013-04-13_15:31:20.76549 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:76:in
    `run'
    2013-04-13_15:31:20.76551 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/bin/bosh_agent:96:in
    `<top (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:23:in
    `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:23:in
    `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic and
    manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.**s3.amazonaws.com/last_**successful_bosh-stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz>
    microBosh stemcell: http://bosh-jenkins-artifacts.**s3.amazonaws.com/last_**successful_micro-bosh-**stemcell-openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz>



    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for bundle
    install commands , but the rake commands for stemcell were still failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I
    was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum errors
    while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2 -pipe -march=native
    -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int ConnectionDescriptor::**SendOutboundData(const
    char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid ConnectionDescriptor::_**
    WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce(**)â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_**RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**ConnectToServer(const
    char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**ConnectToUnixServer(const
    char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**CreateTcpServer(const
    char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**OpenDatagramSocket(const
    char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::_**OpenFileForWriting(const
    char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**CreateUnixDomainServer(const
    char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(**char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::**
    SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE, VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI. <- Umm,
    should work with the new stemcells. When does this happens? When deploying
    a microBosh or when deploying other deployments? Can you please paste the
    micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com>

    Hi Ferdy,
    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-**openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.**7.0.tgz) and while looking back at
    your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine
    dependencies on 0.12.1 version etc. It maybe wise to wait for official
    stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap kpartx
    qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version, and
    created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas****e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui****lder
    /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-2
    8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0****
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.******
    0.pre.3-28522/build/bin/build_******from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc****ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0**
    **.p re.3-28522/build/etc/**settings****.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <
    frod...@gmail.com> wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am getting
    fog-1.10.1
    Not sure if that is causing the eventmachine issue ?
    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh wrote:

    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your
    microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da******773fdd #
    UUID of your Quantum network"


    It came with the error that "manual" type is not supported.
    Are we back level for this ? Also the net_id is the UUID of the private
    network, not the network from where we pull floating ips I would guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh Singh
    wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been tested
    with Quantum ?
    We got it running with nova-network,. and are now upgading
    the environment to use Quantum

    Any extra settings in manifest files if Quantum is enabled
    ?
  • Anderson L Jason at Apr 15, 2013 at 5:42 am
    Hi Ferdy,

    That would explain why I'm not seeing the OpenStack Registry on the
    MicroBOSH VM. Two questions though:

    1) Looking through the OpenStack Registry log on my local BOSH-CLI VM, I
    see the following errors at the end of this post. They basically state
    that Sinatra is not found even though 'gem list Sinatra' shows the local
    gem sinatra (1.4.2) is installed. Any thoughts?

    2) Why does the BOSH agent log state "got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}". Any
    particular reason why it say localhost instead of the machine in which I
    started the BOSH deploy? Thanks,


    *Openstack_Registry.log When Deploying MicroBOSH*
    I, [2013-04-14T19:39:12.009076 #2382] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:39:12.009575 #2382] INFO -- : HTTP server is starting on
    port 25889...
    E, [2013-04-14T19:39:14.664625 #2382] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:41:23.084842 #2382] DEBUG -- : (0.000250s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:41:23.084975 #2382] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:41:23.085412 #2382] DEBUG -- : (0.000356s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:41:23.086353 #2382] DEBUG -- : (0.000114s) SELECT * FROM
    `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087151 #2382] DEBUG -- : (0.000104s) SELECT
    COUNT(*) AS 'count' FROM `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087472 #2382] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:41:23.087594 #2382] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:41:23.088101 #2382] DEBUG -- : (0.000197s) INSERT INTO
    `openstack_servers` (`server_id`, `settings`) VALUES ('vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb',
    '{"vm":{"name":"vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb"},"agent_id":"bm-7303a2a0-2998-4204-ac31-
    ab129e08c6bf","networks":{"bosh":{"cloud_properties":{"net_id":"348f3609-3ad2-4b2c-a945-4074a023bcb5","security_groups":
    ["default"]},"netmask":null,"gateway":null,"ip":null,"dns":null,"type":"dynamic","default":["dns","gateway"]}},"disks":
    {"system":"/dev/vda","ephemeral":"/dev/vdb","persistent":{}},"env":{"bosh":{"password":null}},"ntp":[],"blobstore":
    {"plugin":"local","properties":{"blobstore_path":"/var/vcap/micro_bosh/data/cache"}},"mbus":"http://vcap:b00tstrap@0.0.0.0:6868"}')
    D, [2013-04-14T19:41:23.088404 #2382] DEBUG -- : (0.000121s) SELECT * FROM
    `openstack_servers` WHERE (`id` = 1) LIMIT 1
    D, [2013-04-14T19:41:23.257119 #2382] DEBUG -- : (0.168538s) COMMIT
    E, [2013-04-14T19:43:55.954641 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:57.392378 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:58.885495 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:44:00.375715 #2382] ERROR -- : Sinatra::NotFound
    ...
    ...
    ...
    E, [2013-04-14T19:48:47.007029 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:48.500271 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:50.262314 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:51.687800 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.112593 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.570218 #2382] ERROR -- : Sinatra::NotFound
    I, [2013-04-14T19:48:55.231005 #2382] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Openstack_Registry.log When Deleting Partial MicroBOSH Deployment*
    I, [2013-04-14T19:32:51.345886 #14148] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:32:51.346132 #14148] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:32:53.894723 #14148] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:32:57.091895 #14148] DEBUG -- : (0.000266s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:32:57.092011 #14148] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:32:57.092366 #14148] DEBUG -- : (0.000274s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:32:57.093282 #14148] DEBUG -- : (0.000183s) SELECT * FROM
    `openstack_servers` WHERE (`server_id` =
    'vm-9e14d78d-8392-4ff4-bbbd-19e003abdbb3') LIMIT 1
    D, [2013-04-14T19:32:57.093565 #14148] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:32:57.093673 #14148] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:32:57.093935 #14148] DEBUG -- : (0.000156s) DELETE FROM
    `openstack_servers` WHERE `id` = 1
    D, [2013-04-14T19:32:57.216922 #14148] DEBUG -- : (0.122866s) COMMIT
    I, [2013-04-14T19:32:57.899244 #14148] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Ports Open When Deploying on BOSH CLI VM*
    tcp 0 0 0.0.0.0:25889 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN

    On Sunday, April 14, 2013 10:22:18 AM UTC-7, ferdy wrote:

    At this point, the registry should be running on you local machine (where
    you executed bosh micro deploy ...), not in the microBosh VM. You would see
    a bosh_registry.log in your deployments directory. Can you check if that
    file exists and which are the contents?

    - Ferdy


    2013/4/13 <anderson...@gmail.com <javascript:>>
    Hi Ferdy,

    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/bosh_agent/infrastructure/openstack/registry.rb)
    but maybe I'm missing something. Much appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json
    (Bosh::Agent::LoadSettingsError)
    2013-04-13_15:31:20.76536 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:25:in
    `load'
    2013-04-13_15:31:20.76542 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/settings.rb:14:in
    `load'
    2013-04-13_15:31:20.76544 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent/bootstrap.rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:97:in
    `start'
    2013-04-13_15:31:20.76549 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/lib/bosh_agent.rb:76:in
    `run'
    2013-04-13_15:31:20.76551 from
    /var/vcap/bosh/lib/ruby/gems/1.9.1/gems/bosh_agent-1.5.0.pre.3/bin/bosh_agent:96:in
    `<top (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:23:in
    `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:23:in
    `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic and
    manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.**s3.amazonaws.com/last_**successful_bosh-stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz>
    microBosh stemcell: http://bosh-jenkins-artifacts.**s3.amazonaws.com/last_**successful_micro-bosh-**stemcell-openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz>



    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for bundle
    install commands , but the rake commands for stemcell were still failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I
    was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum
    errors while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int ConnectionDescriptor::**SendOutboundData(const
    char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    ed.cpp: In member function âvoid ConnectionDescriptor::_**
    WriteOutboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce(**)â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned integer
    expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_**RunSelectOnce()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **intern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_**
    ReadLoopBreaker()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**ConnectToServer(const
    char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**ConnectToUnixServer(const
    char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**CreateTcpServer(const
    char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**OpenDatagramSocket(const
    char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::_*
    *OpenFileForWriting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::**CreateUnixDomainServer(const
    char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(**char* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_**
    ReadLoopBreaker()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::**
    SignalLoopBreaker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE,
    VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI. <- Umm,
    should work with the new stemcells. When does this happens? When deploying
    a microBosh or when deploying other deployments? Can you please paste the
    micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but requires
    creating new stemcells? <- Yes, old stemcells doesn't support manual
    networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com>

    Hi Ferdy,
    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-**openstack-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.**7.0.tgz) and while looking back at
    your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and
    the manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine 0.12.10
    couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh code has a
    dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine
    dependencies on 0.12.1 version etc. It maybe wise to wait for official
    stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap
    kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version,
    and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas****e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui****lder
    /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-2
    8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0****
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.******
    0.pre.3-28522/build/bin/build_******from_spec.s h
    /var/tmp/bosh/bosh_agent-1.5.**0****.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc****ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.**0*
    ***.p re.3-28522/build/etc/**settings****.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <
    frod...@gmail.com> wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am
    getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?

    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh
    wrote:
    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a qoekaround
    documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to use
    manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your
    microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da******773fdd
    # UUID of your Quantum network"


    It came with the error that "manual" type is not
    supported. Are we back level for this ? Also the net_id is the UUID of the
    private network, not the network from where we pull floating ips I would
    guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh
    Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been
    tested with Quantum ?
    We got it running with nova-network,. and are now
    upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is
    enabled ?
  • Ferran Rodenas at Apr 16, 2013 at 6:44 pm
    1) The Sinatra::NotFound error doesn't mean that it cannot find Sinatra. It
    means that the bosh registry has received a request and it returned a 404
    http code (not found).

    2) This happens on the microBosh. When deployer starts, it creates an SSL
    tunnel between your local machine and the microBosh VM on port 25889, so
    localhost is your local machine.

    Looking at your logs, it seems you're using the new stemcells but the old
    gems, that are incompatible. What version of bosh deployer are you using?
    "bosh -v"

    - Ferdy


    2013/4/14 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    That would explain why I'm not seeing the OpenStack Registry on the
    MicroBOSH VM. Two questions though:

    1) Looking through the OpenStack Registry log on my local BOSH-CLI VM, I
    see the following errors at the end of this post. They basically state
    that Sinatra is not found even though 'gem list Sinatra' shows the local
    gem sinatra (1.4.2) is installed. Any thoughts?

    2) Why does the BOSH agent log state "got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}". Any
    particular reason why it say localhost instead of the machine in which I
    started the BOSH deploy? Thanks,


    *Openstack_Registry.log When Deploying MicroBOSH*
    I, [2013-04-14T19:39:12.009076 #2382] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:39:12.009575 #2382] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:39:14.664625 #2382] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:41:23.084842 #2382] DEBUG -- : (0.000250s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:41:23.084975 #2382] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:41:23.085412 #2382] DEBUG -- : (0.000356s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:41:23.086353 #2382] DEBUG -- : (0.000114s) SELECT * FROM
    `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087151 #2382] DEBUG -- : (0.000104s) SELECT
    COUNT(*) AS 'count' FROM `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087472 #2382] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:41:23.087594 #2382] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:41:23.088101 #2382] DEBUG -- : (0.000197s) INSERT INTO
    `openstack_servers` (`server_id`, `settings`) VALUES ('vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb',
    '{"vm":{"name":"vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb"},"agent_id":"bm-7303a2a0-2998-4204-ac31-
    ab129e08c6bf","networks":{"bosh":{"cloud_properties":{"net_id":"348f3609-3ad2-4b2c-a945-4074a023bcb5","security_groups":
    ["default"]},"netmask":null,"gateway":null,"ip":null,"dns":null,"type":"dynamic","default":["dns","gateway"]}},"disks":
    {"system":"/dev/vda","ephemeral":"/dev/vdb","persistent":{}},"env":{"bosh":{"password":null}},"ntp":[],"blobstore":
    {"plugin":"local","properties":{"blobstore_path":"/var/vcap/micro_bosh/data/cache"}},"mbus":"
    http://vcap:b00tstrap@0.0.0.0:6868"}')
    D, [2013-04-14T19:41:23.088404 #2382] DEBUG -- : (0.000121s) SELECT * FROM
    `openstack_servers` WHERE (`id` = 1) LIMIT 1
    D, [2013-04-14T19:41:23.257119 #2382] DEBUG -- : (0.168538s) COMMIT
    E, [2013-04-14T19:43:55.954641 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:57.392378 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:58.885495 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:44:00.375715 #2382] ERROR -- : Sinatra::NotFound
    ...
    ...
    ...
    E, [2013-04-14T19:48:47.007029 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:48.500271 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:50.262314 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:51.687800 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.112593 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.570218 #2382] ERROR -- : Sinatra::NotFound
    I, [2013-04-14T19:48:55.231005 #2382] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Openstack_Registry.log When Deleting Partial MicroBOSH Deployment*
    I, [2013-04-14T19:32:51.345886 #14148] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:32:51.346132 #14148] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:32:53.894723 #14148] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:32:57.091895 #14148] DEBUG -- : (0.000266s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:32:57.092011 #14148] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:32:57.092366 #14148] DEBUG -- : (0.000274s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:32:57.093282 #14148] DEBUG -- : (0.000183s) SELECT *
    FROM `openstack_servers` WHERE (`server_id` =
    'vm-9e14d78d-8392-4ff4-bbbd-19e003abdbb3') LIMIT 1
    D, [2013-04-14T19:32:57.093565 #14148] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:32:57.093673 #14148] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:32:57.093935 #14148] DEBUG -- : (0.000156s) DELETE FROM
    `openstack_servers` WHERE `id` = 1
    D, [2013-04-14T19:32:57.216922 #14148] DEBUG -- : (0.122866s) COMMIT
    I, [2013-04-14T19:32:57.899244 #14148] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Ports Open When Deploying on BOSH CLI VM*
    tcp 0 0 0.0.0.0:25889 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN

    On Sunday, April 14, 2013 10:22:18 AM UTC-7, ferdy wrote:

    At this point, the registry should be running on you local machine (where
    you executed bosh micro deploy ...), not in the microBosh VM. You would see
    a bosh_registry.log in your deployments directory. Can you check if that
    file exists and which are the contents?

    - Ferdy


    2013/4/13 <anderson...@gmail.com>

    Hi Ferdy,
    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/**bosh_agent/infrastructure/**
    openstack/registry.rb) but maybe I'm missing something. Much
    appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"**http://admin:admin@localhost:**25889"},
    "server"=>{"name"=>"vm-**f3af9c4c-4e10-44c4-8703-**8f03091adf38"}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528 /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json (Bosh::Agent::**
    LoadSettingsError)
    2013-04-13_15:31:20.76536 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:25:in
    `load'
    2013-04-13_15:31:20.76542 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:14:in
    `load'
    2013-04-13_15:31:20.76544 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/**bootstrap.rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/**bootstrap.rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent.rb:97:in `start'
    2013-04-13_15:31:20.76549 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent.rb:76:in `run'
    2013-04-13_15:31:20.76551 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/bin/bosh_agent:96:in `<top
    (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:**23:in
    `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:**23:in
    `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic and
    manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.****s3.amazonaws.com/last_**successf**ul_bosh-stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz>
    microBosh stemcell: http://bosh-jenkins-artifacts.****s3.amazonaws.com/last_**successf**ul_micro-bosh-**stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz>



    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for
    bundle install commands , but the rake commands for stemcell were still
    failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and I
    was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum
    errors while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int ConnectionDescriptor::**
    SendOutb**oundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    ed.cpp: In member function âvoid ConnectionDescriptor::_**WriteOu**
    tboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce(****
    )â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_**RunSelectOnce**
    ()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    er()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::*
    *ConnectToServe**r(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::*
    *ConnectToUnixS**erver(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::*
    *CreateTcpServe**r(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::*
    *OpenDatagramSo**cket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::_
    **OpenFileForWr**iting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::*
    *CreateUnixDoma**inServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong unsigned
    intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(**cha**r* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    er()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::**SignalLoopBrea**
    ker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE,
    VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no format
    arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with eventmachine
    0.12.10 What version of ruby are you using? How do you installed (apt-get,
    rvm, rbenb)? Anyway, you can try on 12.04 (the only requirement is kpartx
    0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only on
    Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI. <- Umm,
    should work with the new stemcells. When does this happens? When deploying
    a microBosh or when deploying other deployments? Can you please paste the
    micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells? <- Yes, old stemcells doesn't support
    manual networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com>

    Hi Ferdy,
    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-**openstack**-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.****7.0.tgz) and while looking back
    at your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and
    the manually created stemcells?

    Thanks for the help!

    - Jason Anderson
    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh wrote:

    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine
    0.12.10 couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh
    code has a dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine
    dependencies on 0.12.1 version etc. It maybe wise to wait for official
    stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via apt-get
    install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap
    kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version,
    and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas******e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui******lder
    /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-2
    8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0******
    .pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0******
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.********
    0.pre.3-28522/build/bin/build_********from_spec.s
    h /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc******ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.*
    *0******.p re.3-28522/build/etc/**settings******
    .bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <
    frod...@gmail.com> wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am
    getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?

    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh
    wrote:
    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a
    qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to
    use manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with these
    versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your
    microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da********773fdd
    # UUID of your Quantum network"


    It came with the error that "manual" type is not
    supported. Are we back level for this ? Also the net_id is the UUID of the
    private network, not the network from where we pull floating ips I would
    guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh
    Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been
    tested with Quantum ?
    We got it running with nova-network,. and are now
    upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is
    enabled ?
  • Anderson L Jason at Apr 17, 2013 at 10:00 pm
    Hi Ferdy,

    I'm currently using the gems which are available on rubygems.orgs (see the
    following list). These are pretty old so how would I go about getting the
    new bosh_deployer and bosh_cli gems? Thanks,

        - bosh_aws_cpi (0.7.0)
        - bosh_aws_registry (0.2.3)
        - bosh_cli (1.0.3)
        - bosh_common (0.5.4)
        - bosh_cpi (0.5.1)
        - bosh_deployer (1.4.1)
        - bosh_openstack_cpi (0.0.7)
        - bosh_openstack_registry (0.0.5)
        - bosh_vcloud_cpi (0.4.9)
        - bosh_vsphere_cpi (0.6.0)

      - Jason
    On Tuesday, April 16, 2013 11:44:35 AM UTC-7, ferdy wrote:

    1) The Sinatra::NotFound error doesn't mean that it cannot find Sinatra.
    It means that the bosh registry has received a request and it returned a
    404 http code (not found).

    2) This happens on the microBosh. When deployer starts, it creates an SSL
    tunnel between your local machine and the microBosh VM on port 25889, so
    localhost is your local machine.

    Looking at your logs, it seems you're using the new stemcells but the old
    gems, that are incompatible. What version of bosh deployer are you using?
    "bosh -v"

    - Ferdy


    2013/4/14 <anderson...@gmail.com <javascript:>>
    Hi Ferdy,

    That would explain why I'm not seeing the OpenStack Registry on the
    MicroBOSH VM. Two questions though:

    1) Looking through the OpenStack Registry log on my local BOSH-CLI VM, I
    see the following errors at the end of this post. They basically state
    that Sinatra is not found even though 'gem list Sinatra' shows the local
    gem sinatra (1.4.2) is installed. Any thoughts?

    2) Why does the BOSH agent log state "got user_data:
    {"registry"=>{"endpoint"=>"http://admin:admin@localhost:25889"},
    "server"=>{"name"=>"vm-f3af9c4c-4e10-44c4-8703-8f03091adf38"}}". Any
    particular reason why it say localhost instead of the machine in which I
    started the BOSH deploy? Thanks,


    *Openstack_Registry.log When Deploying MicroBOSH*
    I, [2013-04-14T19:39:12.009076 #2382] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:39:12.009575 #2382] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:39:14.664625 #2382] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:41:23.084842 #2382] DEBUG -- : (0.000250s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:41:23.084975 #2382] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:41:23.085412 #2382] DEBUG -- : (0.000356s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:41:23.086353 #2382] DEBUG -- : (0.000114s) SELECT *
    FROM `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087151 #2382] DEBUG -- : (0.000104s) SELECT
    COUNT(*) AS 'count' FROM `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb')
    LIMIT 1
    D, [2013-04-14T19:41:23.087472 #2382] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:41:23.087594 #2382] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:41:23.088101 #2382] DEBUG -- : (0.000197s) INSERT INTO
    `openstack_servers` (`server_id`, `settings`) VALUES ('vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb',
    '{"vm":{"name":"vm-2c6c5677-42fc-4399-bb9f-286ea1c687bb"},"agent_id":"bm-7303a2a0-2998-4204-ac31-
    ab129e08c6bf","networks":{"bosh":{"cloud_properties":{"net_id":"348f3609-3ad2-4b2c-a945-4074a023bcb5","security_groups":
    ["default"]},"netmask":null,"gateway":null,"ip":null,"dns":null,"type":"dynamic","default":["dns","gateway"]}},"disks":
    {"system":"/dev/vda","ephemeral":"/dev/vdb","persistent":{}},"env":{"bosh":{"password":null}},"ntp":[],"blobstore":
    {"plugin":"local","properties":{"blobstore_path":"/var/vcap/micro_bosh/data/cache"}},"mbus":"
    http://vcap:b00tstrap@0.0.0.0:6868"}')
    D, [2013-04-14T19:41:23.088404 #2382] DEBUG -- : (0.000121s) SELECT *
    FROM `openstack_servers` WHERE (`id` = 1) LIMIT 1
    D, [2013-04-14T19:41:23.257119 #2382] DEBUG -- : (0.168538s) COMMIT
    E, [2013-04-14T19:43:55.954641 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:57.392378 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:58.885495 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:44:00.375715 #2382] ERROR -- : Sinatra::NotFound
    ...
    ...
    ...
    E, [2013-04-14T19:48:47.007029 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:48.500271 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:50.262314 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:51.687800 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.112593 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.570218 #2382] ERROR -- : Sinatra::NotFound
    I, [2013-04-14T19:48:55.231005 #2382] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Openstack_Registry.log When Deleting Partial MicroBOSH Deployment*
    I, [2013-04-14T19:32:51.345886 #14148] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:32:51.346132 #14148] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:32:53.894723 #14148] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:32:57.091895 #14148] DEBUG -- : (0.000266s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:32:57.092011 #14148] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:32:57.092366 #14148] DEBUG -- : (0.000274s) PRAGMA
    table_info('openstack_servers')
    D, [2013-04-14T19:32:57.093282 #14148] DEBUG -- : (0.000183s) SELECT *
    FROM `openstack_servers` WHERE (`server_id` =
    'vm-9e14d78d-8392-4ff4-bbbd-19e003abdbb3') LIMIT 1
    D, [2013-04-14T19:32:57.093565 #14148] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:32:57.093673 #14148] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:32:57.093935 #14148] DEBUG -- : (0.000156s) DELETE FROM
    `openstack_servers` WHERE `id` = 1
    D, [2013-04-14T19:32:57.216922 #14148] DEBUG -- : (0.122866s) COMMIT
    I, [2013-04-14T19:32:57.899244 #14148] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Ports Open When Deploying on BOSH CLI VM*
    tcp 0 0 0.0.0.0:25889 0.0.0.0:*
    LISTEN
    tcp 0 0 0.0.0.0:80 0.0.0.0:*
    LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:*
    LISTEN

    On Sunday, April 14, 2013 10:22:18 AM UTC-7, ferdy wrote:

    At this point, the registry should be running on you local machine
    (where you executed bosh micro deploy ...), not in the microBosh VM. You
    would see a bosh_registry.log in your deployments directory. Can you check
    if that file exists and which are the contents?

    - Ferdy


    2013/4/13 <anderson...@gmail.com>

    Hi Ferdy,
    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/**bosh_agent/infrastructure/**
    openstack/registry.rb) but maybe I'm missing something. Much
    appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"**http://admin:admin@localhost:**25889"},
    "server"=>{"name"=>"vm-**f3af9c4c-4e10-44c4-8703-**8f03091adf38"}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528 /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json (Bosh::Agent::**
    LoadSettingsError)
    2013-04-13_15:31:20.76536 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:25:in
    `load'
    2013-04-13_15:31:20.76542 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/settings.**rb:14:in
    `load'
    2013-04-13_15:31:20.76544 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/**bootstrap.rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent/**bootstrap.rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent.rb:97:in `start'
    2013-04-13_15:31:20.76549 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/lib/bosh_agent.rb:76:in `run'
    2013-04-13_15:31:20.76551 from /var/vcap/bosh/lib/ruby/gems/**
    1.9.1/gems/bosh_agent-1.5.0.**pre.3/bin/bosh_agent:96:in `<top
    (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:**23:in
    `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:**23:in
    `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic
    and manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.****s3.amazonaws.com/last_**successf**ul_bosh-stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz>
    microBosh stemcell: http://bosh-jenkins-artifacts.****s3.amazonaws.com/last_**successf**ul_micro-bosh-**stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz>




    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for
    bundle install commands , but the rake commands for stemcell were still
    failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and
    I was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum
    errors while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int ConnectionDescriptor::**
    SendOutb**oundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    ed.cpp: In member function âvoid ConnectionDescriptor::_**WriteOu**
    tboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce(****
    )â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_**RunSelectOnce**
    ()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i**ntern.h:379) [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    er()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **ConnectToServe**r(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **ConnectToUnixS**erver(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **CreateTcpServe**r(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **OpenDatagramSo**cket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::_
    **OpenFileForWr**iting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **CreateUnixDoma**inServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(**cha**r* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    er()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::**SignalLoopBrea**
    ker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t write(int,
    const void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE,
    VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no
    format arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE, VALUE,
    VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no
    format arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with
    eventmachine 0.12.10 What version of ruby are you using? How do you
    installed (apt-get, rvm, rbenb)? Anyway, you can try on 12.04 (the only
    requirement is kpartx 0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only
    on Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI. <-
    Umm, should work with the new stemcells. When does this happens? When
    deploying a microBosh or when deploying other deployments? Can you please
    paste the micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells? <- Yes, old stemcells doesn't support
    manual networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com>

    Hi Ferdy,
    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-**openstack**-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.****7.0.tgz) and while looking
    back at your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and
    the manually created stemcells?

    Thanks for the help!

    - Jason Anderson

    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh
    wrote:
    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine
    0.12.10 couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh
    code has a dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine
    dependencies on 0.12.1 version etc. It maybe wise to wait for official
    stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via
    apt-get install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap
    kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version,
    and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas******e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui******lder
    /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-2
    8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0******
    .pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0******
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.********
    0.pre.3-28522/build/bin/build_********from_spec.s
    h /var/tmp/bosh/bosh_agent-1.5.**0******.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc******ell-openstack.spec /var/tmp/bosh/bosh_agent-1.5.
    **0******.p re.3-28522/build/etc/**settings******
    .bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did it
    create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <
    frod...@gmail.com> wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am
    getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?

    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh
    wrote:
    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a
    qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to
    use manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with
    these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your
    microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da********773fdd
    # UUID of your Quantum network"


    It came with the error that "manual" type is not
    supported. Are we back level for this ? Also the net_id is the UUID of the
    private network, not the network from where we pull floating ips I would
    guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh
    Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been
    tested with Quantum ?
    We got it running with nova-network,. and are now
    upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is
    enabled ?
  • Ferran Rodenas at Apr 18, 2013 at 4:44 am
    To install gems from the latest codebase:

    1) git clone git://github.com/cloudfoundry/bosh.git
    2) cd ~/bosh
    3) bundle install --local --binstubs
    4) bundle exec rake all:install

    - Ferdy


    2013/4/17 <anderson.l.jason@gmail.com>
    Hi Ferdy,

    I'm currently using the gems which are available on rubygems.orgs (see the
    following list). These are pretty old so how would I go about getting the
    new bosh_deployer and bosh_cli gems? Thanks,

    - bosh_aws_cpi (0.7.0)
    - bosh_aws_registry (0.2.3)
    - bosh_cli (1.0.3)
    - bosh_common (0.5.4)
    - bosh_cpi (0.5.1)
    - bosh_deployer (1.4.1)
    - bosh_openstack_cpi (0.0.7)
    - bosh_openstack_registry (0.0.5)
    - bosh_vcloud_cpi (0.4.9)
    - bosh_vsphere_cpi (0.6.0)

    - Jason
    On Tuesday, April 16, 2013 11:44:35 AM UTC-7, ferdy wrote:

    1) The Sinatra::NotFound error doesn't mean that it cannot find Sinatra.
    It means that the bosh registry has received a request and it returned a
    404 http code (not found).

    2) This happens on the microBosh. When deployer starts, it creates an SSL
    tunnel between your local machine and the microBosh VM on port 25889, so
    localhost is your local machine.

    Looking at your logs, it seems you're using the new stemcells but the old
    gems, that are incompatible. What version of bosh deployer are you using?
    "bosh -v"

    - Ferdy


    2013/4/14 <anderson...@gmail.com>

    Hi Ferdy,
    That would explain why I'm not seeing the OpenStack Registry on the
    MicroBOSH VM. Two questions though:

    1) Looking through the OpenStack Registry log on my local BOSH-CLI VM, I
    see the following errors at the end of this post. They basically state
    that Sinatra is not found even though 'gem list Sinatra' shows the local
    gem sinatra (1.4.2) is installed. Any thoughts?

    2) Why does the BOSH agent log state "got user_data:
    {"registry"=>{"endpoint"=>"**http://admin:admin@localhost:**25889"},
    "server"=>{"name"=>"vm-**f3af9c4c-4e10-44c4-8703-**8f03091adf38"}}".
    Any particular reason why it say localhost instead of the machine in which
    I started the BOSH deploy? Thanks,


    *Openstack_Registry.log When Deploying MicroBOSH*
    I, [2013-04-14T19:39:12.009076 #2382] INFO -- : BOSH OpenStack Registry
    starting...
    I, [2013-04-14T19:39:12.009575 #2382] INFO -- : HTTP server is starting
    on port 25889...
    E, [2013-04-14T19:39:14.664625 #2382] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:41:23.084842 #2382] DEBUG -- : (0.000250s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:41:23.084975 #2382] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:41:23.085412 #2382] DEBUG -- : (0.000356s) PRAGMA
    table_info('openstack_servers'**)
    D, [2013-04-14T19:41:23.086353 #2382] DEBUG -- : (0.000114s) SELECT *
    FROM `openstack_servers` WHERE (`server_id` = 'vm-2c6c5677-42fc-4399-
    bb9f-**286ea1c687bb') LIMIT 1
    D, [2013-04-14T19:41:23.087151 #2382] DEBUG -- : (0.000104s) SELECT
    COUNT(*) AS 'count' FROM `openstack_servers` WHERE (`server_id` = 'vm-
    2c6c5677-42fc-4399-bb9f-**286ea1c687bb') LIMIT 1
    D, [2013-04-14T19:41:23.087472 #2382] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:41:23.087594 #2382] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:41:23.088101 #2382] DEBUG -- : (0.000197s) INSERT INTO
    `openstack_servers` (`server_id`, `settings`) VALUES ('vm-2c6c5677-
    42fc-4399-bb9f-**286ea1c687bb', '{"vm":{"name":"vm-2c6c5677-**
    42fc-4399-bb9f-286ea1c687bb"},**"agent_id":"bm-7303a2a0-2998-**
    4204-ac31-ab129e08c6bf","**networks":{"bosh":{"cloud_**
    properties":{"net_id":"**348f3609-3ad2-4b2c-a945-**
    4074a023bcb5","security_**groups":["default"]},"netmask"**
    :null,"gateway":null,"ip":**null,"dns":null,"type":"**
    dynamic","default":["dns","**gateway"]}},"disks":{"system":**
    "/dev/vda","ephemeral":"/dev/**vdb","persistent":{}},"env":{"**
    bosh":{"password":null}},"ntp"**:[],"blobstore":{"plugin":"**
    local","properties":{"**blobstore_path":"/var/vcap/**
    micro_bosh/data/cache"}},"**mbus":"http://vcap:b00tstrap@**0.0.0.0:6868<http://vcap:b00tstrap@0.0.0.0:6868>
    "}')
    D, [2013-04-14T19:41:23.088404 #2382] DEBUG -- : (0.000121s) SELECT *
    FROM `openstack_servers` WHERE (`id` = 1) LIMIT 1
    D, [2013-04-14T19:41:23.257119 #2382] DEBUG -- : (0.168538s) COMMIT
    E, [2013-04-14T19:43:55.954641 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:57.392378 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:43:58.885495 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:44:00.375715 #2382] ERROR -- : Sinatra::NotFound
    ...
    ...
    ...
    E, [2013-04-14T19:48:47.007029 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:48.500271 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:50.262314 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:51.687800 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.112593 #2382] ERROR -- : Sinatra::NotFound
    E, [2013-04-14T19:48:54.570218 #2382] ERROR -- : Sinatra::NotFound
    I, [2013-04-14T19:48:55.231005 #2382] INFO -- : BOSH OpenStack Registry
    shutting down...


    *Openstack_Registry.log When Deleting Partial MicroBOSH Deployment*
    I, [2013-04-14T19:32:51.345886 #14148] INFO -- : BOSH OpenStack
    Registry starting...
    I, [2013-04-14T19:32:51.346132 #14148] INFO -- : HTTP server is
    starting on port 25889...
    E, [2013-04-14T19:32:53.894723 #14148] ERROR -- : Sinatra::NotFound
    D, [2013-04-14T19:32:57.091895 #14148] DEBUG -- : (0.000266s) PRAGMA
    foreign_keys = 1
    D, [2013-04-14T19:32:57.092011 #14148] DEBUG -- : (0.000028s) PRAGMA
    case_sensitive_like = 1
    D, [2013-04-14T19:32:57.092366 #14148] DEBUG -- : (0.000274s) PRAGMA
    table_info('openstack_servers'**)
    D, [2013-04-14T19:32:57.093282 #14148] DEBUG -- : (0.000183s) SELECT *
    FROM `openstack_servers` WHERE (`server_id` = 'vm-9e14d78d-8392-4ff4-bbbd-
    **19e003abdbb3') LIMIT 1
    D, [2013-04-14T19:32:57.093565 #14148] DEBUG -- : (0.000061s) SELECT
    sqlite_version() LIMIT 1
    D, [2013-04-14T19:32:57.093673 #14148] DEBUG -- : (0.000035s) BEGIN
    D, [2013-04-14T19:32:57.093935 #14148] DEBUG -- : (0.000156s) DELETE
    FROM `openstack_servers` WHERE `id` = 1
    D, [2013-04-14T19:32:57.216922 #14148] DEBUG -- : (0.122866s) COMMIT
    I, [2013-04-14T19:32:57.899244 #14148] INFO -- : BOSH OpenStack
    Registry shutting down...


    *Ports Open When Deploying on BOSH CLI VM*
    tcp 0 0 0.0.0.0:25889 0.0.0.0:*
    LISTEN
    tcp 0 0 0.0.0.0:80 0.0.0.0:*
    LISTEN
    tcp 0 0 0.0.0.0:22 0.0.0.0:*
    LISTEN

    On Sunday, April 14, 2013 10:22:18 AM UTC-7, ferdy wrote:

    At this point, the registry should be running on you local machine
    (where you executed bosh micro deploy ...), not in the microBosh VM. You
    would see a bosh_registry.log in your deployments directory. Can you check
    if that file exists and which are the contents?

    - Ferdy


    2013/4/13 <anderson...@gmail.com>

    Hi Ferdy,
    Gave these new stemcells a shot but ran into the following error with
    the MicroBOSH stemcell agent not coming up. From reading one of your
    previous posts, it seems like the problem is that the bosh agent cannot
    access the OpenStack registry service which should be running on the
    MicroBOSH VM. I can confirm that no registry service is running on port
    25889 but cannot find a OpenStack registry log to view or binary which I
    can start. It looks like the registry code file is there (@
    bosh_agent-1.5.0.pre.3/lib/****bosh_agent/infrastructure/**open**
    stack/registry.rb) but maybe I'm missing something. Much appreciated,

    2013-04-13_15:31:20.71802 #[3192] INFO: Starting agent 1.5.0.pre.3...
    2013-04-13_15:31:20.71807 #[3192] INFO: Configuring agent...
    2013-04-13_15:31:20.73291 #[3192] INFO: Configuring instance
    2013-04-13_15:31:20.75951 #[3192] INFO: got user_data:
    {"registry"=>{"endpoint"=>"**htt**p://admin:admin@localhost:**2588**9"},
    "server"=>{"name"=>"vm-**f3af9c4**c-4e10-44c4-8703-**8f03091adf38"**}}
    2013-04-13_15:31:20.76451 #[3192] INFO: failed to load infrastructure
    settings: Error requesting registry information #<Errno::ECONNREFUSED:
    Connection refused - connect(2) (http://localhost:25889)>
    2013-04-13_15:31:20.76528 /var/vcap/bosh/lib/ruby/gems/**1**
    .9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/settings.**rb:**52:in
    `rescue in load_from_cache': could neither load infrastructure settings nor
    cached settings from: /var/vcap/bosh/settings.json (Bosh::Agent::**
    LoadSettingsErro**r)
    2013-04-13_15:31:20.76536 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/settings.**rb:**47:in
    `load_from_cache'
    2013-04-13_15:31:20.76538 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/settings.**rb:**29:in
    `rescue in load'
    2013-04-13_15:31:20.76540 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/settings.**rb:**25:in
    `load'
    2013-04-13_15:31:20.76542 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/settings.**rb:**14:in
    `load'
    2013-04-13_15:31:20.76544 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/**bootstrap.**rb:61:in
    `load_settings'
    2013-04-13_15:31:20.76546 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent/**bootstrap.**rb:35:in
    `configure'
    2013-04-13_15:31:20.76548 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent.rb:97:in `start'
    2013-04-13_15:31:20.76549 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/lib/bosh_agent.rb:76:in `run'
    2013-04-13_15:31:20.76551 from /var/vcap/bosh/lib/ruby/gems/**1*
    *.9.1/gems/bosh_agent-1.5.0.**pre**.3/bin/bosh_agent:96:in `<top
    (required)>'
    2013-04-13_15:31:20.76553 from /var/vcap/bosh/bin/bosh_agent:***
    *23:in `load'
    2013-04-13_15:31:20.76554 from /var/vcap/bosh/bin/bosh_agent:***
    *23:in `<main>'

    On Friday, April 12, 2013 10:21:15 AM UTC-7, ferdy wrote:

    Download these prebuilt stemcells. It have been tested with dynamic
    and manual networks:

    Bosh stemcell: http://bosh-jenkins-artifacts.******s3.amazonaws.com/last_**successf****ul_bosh-stemcell-**openstack.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_bosh-stemcell-openstack.tgz>
    microBosh stemcell: http://bosh-jenkins-artifacts.******s3.amazonaws.com/last_**successf****ul_micro-bosh-**stemcell-**opensta**ck.tgz <http://bosh-jenkins-artifacts.s3.amazonaws.com/last_successful_micro-bosh-stemcell-openstack.tgz>




    - Ferdy



    2013/4/12 Animesh Singh <animat...@gmail.com>
    Thanks. Tried it few days ago , and it got me past the issue for
    bundle install commands , but the rake commands for stemcell were still
    failing

    Yesterday I tried with ruby 2.0 0 and bundler 1.3.5 which helped and
    I was able to create BOSH stemcell !!!

    Though Microbosh stemcell creation is still failing with checksum
    errors while syncing blobs at this point . Any idea ?

    bosh create release --force --with-tarball
    Syncing blobs...
    nginx/pcre-8.12.tar.gz downloaded
    Checksum mismatch for downloaded blob `nginx/pcre-8.12.tar.gz'




    On Apr 12, 2013, at 5:00 AM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Try: gem install eventmachine -v '0.12.10' -- --with-cflags=\"-O2
    -pipe -march=native -w\"
    Another option (inside bosh dir): bundle config build.eventmachine
    --with-cflags=\"-O2 -pipe -march=native -w\" && bundle install --local
    --binstubs

    - Ferdy


    2013/4/11 Animesh Singh <animat...@gmail.com>
    So this is the error I get while installing sudo sudo gem install
    eventmachine -v '0.12.10'


    Fetching: eventmachine-0.12.10.gem (100%)
    Building native extensions. This could take a while...
    ERROR: Error installing eventmachine:
    ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb
    checking for rb_trap_immediate in ruby.h,rubysig.h... no
    checking for rb_thread_blocking_region()... yes
    checking for inotify_init() in sys/inotify.h... yes
    checking for writev() in sys/uio.h... yes
    checking for rb_thread_check_ints()... yes
    checking for rb_time_new()... yes
    checking for sys/event.h... no
    checking for epoll_create() in sys/epoll.h... yes
    checking for main() in -lcrypto... yes
    checking for main() in -lssl... yes
    checking for main() in -lcrypto... yes
    checking for openssl/ssl.h... yes
    checking for openssl/err.h... yes
    creating Makefile

    make
    compiling sigs.cpp
    compiling files.cpp
    compiling cplusplus.cpp
    compiling emwin.cpp
    compiling page.cpp
    compiling epoll.cpp
    compiling ed.cpp
    ed.cpp: In member function âvirtual int ConnectionDescriptor::**
    SendOutb****oundData(const char*, int)â:
    ed.cpp:503:76: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    ed.cpp: In member function âvoid ConnectionDescriptor::_**WriteOu**
    **tboundData()â:
    ed.cpp:956:67: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    compiling em.cpp
    em.cpp: In member function âbool EventMachine_t::_RunEpollOnce(****
    **)â:
    em.cpp:501:3: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i****ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:501:37: warning: âint rb_thread_select(int, fd_set*,
    fd_set*, fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/**i****ntern.h:379)
    [-Wdeprecated-declarations]
    em.cpp:556:39: warning: comparison between signed and unsigned
    integer expressions [-Wsign-compare]
    em.cpp: In member function âbool EventMachine_t::_**RunSelectOnce**
    **()â:
    em.cpp:873:4: warning: âint rb_thread_select(int, fd_set*, fd_set*,
    fd_set*, timeval*)â is deprecated (declared at /usr/include/ruby-1.9.1/ruby/
    **i****ntern.h:379) [-Wdeprecated-declarations]
    em.cpp:873:38: warning: âint rb_thread_select(int, fd_set*,
    fd_set*, fd_set*, timeval*)â is deprecated (declared at
    /usr/include/ruby-1.9.1/ruby/**i****ntern.h:379)
    [-Wdeprecated-declarations]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    **er()â:
    em.cpp:924:52: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âbool EventMachine_t::_RunTimers()â:
    em.cpp:948:72: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **ConnectToServe****r(const char*, int, const char*, int)â:
    em.cpp:1089:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **ConnectToUnixS****erver(const char*)â:
    em.cpp:1218:22: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1221:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1237:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1243:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1249:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **CreateTcpServe****r(const char*, int)â:
    em.cpp:1453:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1455:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1535:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **OpenDatagramSo****cket(const char*, int)â:
    em.cpp:1545:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1596:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::_**OpenFileForWr****iting(const char*)â:
    em.cpp:1773:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int EventMachine_t::
    **CreateUnixDoma****inServer(const char*)â:
    em.cpp:1805:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1866:9: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âconst long unsigned int
    EventMachine_t::Socketpair(**cha****r* const*)â:
    em.cpp:1927:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1932:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1934:33: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1938:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp:1948:10: warning: converting to non-pointer type âlong
    unsigned intâ from NULL [-Wconversion-null]
    em.cpp: In member function âvoid EventMachine_t::_**ReadLoopBreak**
    **er()â:
    em.cpp:922:50: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    em.cpp: In member function âvoid EventMachine_t::**SignalLoopBrea**
    **ker()â:
    em.cpp:294:34: warning: ignoring return value of âssize_t
    write(int, const void*, size_t)â, declared with attribute
    warn_unused_result [-Wunused-result]
    compiling cmain.cpp
    compiling binder.cpp
    compiling pipe.cpp
    compiling kb.cpp
    kb.cpp: In member function âvirtual void
    KeyboardDescriptor::Read()â:
    kb.cpp:79:27: warning: ignoring return value of âssize_t read(int,
    void*, size_t)â, declared with attribute warn_unused_result
    [-Wunused-result]
    compiling ssl.cpp
    compiling rubymain.cpp
    rubymain.cpp: In function âVALUE t_connect_server(VALUE, VALUE,
    VALUE)â:
    rubymain.cpp:468:42: error: format not a string literal and no
    format arguments [-Werror=format-security]
    rubymain.cpp: In function âVALUE t_bind_connect_server(VALUE,
    VALUE, VALUE, VALUE, VALUE)â:
    rubymain.cpp:488:42: error: format not a string literal and no
    format arguments [-Werror=format-security]
    cc1plus: some warnings being treated as errors


    On Thu, Apr 11, 2013 at 5:39 AM, Ferran Rodenas wrote:

    I'm using Ubuntu 12.10 and don't have any problems with
    eventmachine 0.12.10 What version of ruby are you using? How do you
    installed (apt-get, rvm, rbenb)? Anyway, you can try on 12.04 (the only
    requirement is kpartx 0.4.9).

    - Ferdy


    2013/4/11 Animesh <animat...@gmail.com>
    Ferdy on the same node , is the event machine 0.12.10 issue only
    on Ubuntu 12.10? Can I try ur instructions on 12.04 ?

    Sent from my iPhone

    On Apr 10, 2013, at 4:06 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    Jason,

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not allocated"
    even though I allocated the IP through Quantum. Looks like it is using
    nova-network instead so perhaps a limitation with the CPI. <-
    Umm, should work with the new stemcells. When does this happens? When
    deploying a microBosh or when deploying other deployments? Can you please
    paste the micro_bosh or task log so I can see what's happening?

    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells? <- Yes, old stemcells doesn't support
    manual networks

    3. Dynamic IPs are supported with Quantum in both the old and the
    manually created stemcells? <- Yes

    - Ferdy


    2013/4/10 <anderson...@gmail.com>

    Hi Ferdy,
    I was able to deploy MicroBOSH using the old stemcells
    (micro-bosh-stemcell-**openstack****-kvm-0.8.1.tgz and
    bosh-stemcell-openstack-kvm-0.******7.0.tgz) and while looking
    back at your posts I had the following questions:

    1. Floating IPs do NOT work at all with Quantum for both old
    stemcells and ones I'd make using you're previously defined process? I
    kept getting "Error 100: Floating IP <IP Address> not
    allocated" even though I allocated the IP through Quantum. Looks like it
    is using nova-network instead so perhaps a limitation with the
    CPI.
    2. Static IPs work with Quantum using the manual option but
    requires creating new stemcells?
    3. Dynamic IPs are supported with Quantum in both the old and
    the manually created stemcells?

    Thanks for the help!

    - Jason Anderson

    On Wednesday, April 10, 2013 1:37:51 AM UTC-7, Animesh Singh
    wrote:
    Thanks . I will keep inquiring , though if you can post on this
    thread once it's ready , would be grt

    I had to abandon the custom stem cell because eventmachine
    0.12.10 couldn't be installed on Ubuntu 12.10 ( known issue) , and Bosh
    code has a dependency on it it seems

    Sent from my iPhone

    On Apr 9, 2013, at 12:41 PM, Ferran Rodenas <frod...@gmail.com>
    wrote:

    We don't have an exact date, but it'll be soon.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Seems I am running into lot of issues with eventmachine
    dependencies on 0.12.1 version etc. It maybe wise to wait for official
    stemcell to be published
    Do you have a timeline for it ?

    On Tuesday, April 9, 2013 1:50:14 AM UTC-7, ferdy wrote:

    There're some missing packages, be sure to install (via
    apt-get install): build-essential libsqlite3-dev rsync libmysqlclient-dev
    libxml2-dev libxslt-dev libpq-dev genisoimage debootstrap
    kpartx qemu-kvm

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>
    I was able to go beyong by using eventmachine 1.0.1 version,
    and created microbosh stemcell, and I could see the stemcell in dev_releases

    ubuntu@testu1210:~/bosh/**releas********e/dev_releases$ ls
    index.yml micro-bosh-13.1-dev.tgz micro-bosh-13.1-dev.yml


    Now the command to create BOSH stemcell

    bundle exec rake stemcell:basic[openstack]

    ends with

    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0********
    .pre.3-28522
    MADE ROOT: /var/tmp/bosh/bosh_agent-1.5.**0********
    .pre.3-28522
    PWD: /home/ubuntu/bosh
    cp -rp /home/ubuntu/bosh/stemcell_**bui********lder
    /var/tmp/bosh/bosh_agent-1.5.**0********.pre.3-2
    8522/build
    mkdir -p /var/tmp/bosh/bosh_agent-1.5.**0********
    .pre.3-28522/work
    building in /var/tmp/bosh/bosh_agent-1.5.**0********
    .pre.3-28522/work...
    sudo env /var/tmp/bosh/bosh_agent-1.5.**********
    0.pre.3-28522/build/bin/build_**********from_spec.s
    h /var/tmp/bosh/bosh_agent-1.5.**0********.pre.3-28522/work
    /var/tmp/bosh/bosh_agent-1.5.0 .pre.3-28522/build/spec/
    **stemc********ell-openstack.spec
    /var/tmp/bosh/bosh_agent-1.5.**0********.p
    re.3-28522/build/etc/**settings********.bash
    === Configuring 'base_debootstrap' stage ===
    debootstrap is not available


    Not sure whether it succeeded or not and if yes, where did
    it create the stemcell ?




    On Tue, Apr 9, 2013 at 1:36 AM, Ferran Rodenas <
    frod...@gmail.com> wrote:
    Can you provide more details about what's failing with
    eventmachine? Can you install the gem as a standalone (gem install
    eventmachine -v 0.12.10?

    The fog gem has been update, but it shouldn't be the
    problem.

    - Ferdy


    2013/4/9 Animesh Singh <animat...@gmail.com>

    Also one thing I am noticing is the version of fog I am
    getting fog-1.10.1
    Not sure if that is causing the eventmachine issue ?

    On Monday, April 8, 2013 4:34:58 PM UTC-7, Animesh Singh
    wrote:
    Ferdy
    On the latest Ubuntu 12-10 image., this step of yours for
    creating a custom stemcell is failing with a dependency on eventmachine (
    (0.12.10)

    bundle install --local --binstubs

    Not sure if you have seen this before, and have a
    qoekaround documented
    On Monday, April 8, 2013 12:42:29 PM UTC-7, ferdy wrote:

    You need to use newer gems and stemcells if you want to
    use manual networks. See my previous message on how to do that.

    - Ferdy


    2013/4/8 Animesh Singh <animat...@gmail.com>
    Sorry for the half a post there :) So we tried with
    these versions

    bosh_cli gem version 1.0.3
    bosh_deployer version 1.4.1
    bosh_cpi (0.5.1)
    bosh_deployer (1.4.1)
    bosh_openstack_cpi (0.0.7)
    bosh_openstack_registry (0.0.5)

    and trying to use the manual type in microbosh.yml file

    "network:
    type: manual
    label: bosh-net # Name of your Quantum network
    vip: 172.24.4.227 # Floating IP to assign to your
    microBosh
    ip: 10.0.1.5 # Static IP to assign to your microBosh
    (should be in one of the subnets IP range)
    cloud_properties:
    net_id: 4ef0b0ec-58c9-4478-8382-**2099da**********773fdd
    # UUID of your Quantum network"


    It came with the error that "manual" type is not
    supported. Are we back level for this ? Also the net_id is the UUID of the
    private network, not the network from where we pull floating ips I would
    guess ?

    On Wednesday, April 3, 2013 2:48:15 PM UTC-7, Animesh
    Singh wrote:
    Hi,
    Wanted to verify if BOSH CPI for OpenStack has been
    tested with Quantum ?
    We got it running with nova-network,. and are now
    upgading the environment to use Quantum

    Any extra settings in manifest files if Quantum is
    enabled ?

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupbosh-dev @
postedApr 3, '13 at 9:48p
activeJul 23, '13 at 8:24a
posts45
users7

People

Translate

site design / logo © 2021 Grokbase