|
Re: Is Bosh is compatible with Openstack Ocata Version?
Hi Ultragtx,
I have successfully installed bosh director on openstack ocata but I am unable to deploy cloudfoundry due to some other reason. Still I am working on it. I will update you once I will install it. |
|
|
|
Re: Is Bosh is compatible with Openstack Ocata Version?
ultragtx <ultragtx@...>
Hi Arpit,
I’m also interested in deploying cf on ocata, was your installation successful? |
|
|
|
Re: Cloud Foundry Deployment using bosh
Hey David!
I have updated cloud-config as follows: bosh -e bosh-1 cloud-config Using environment '10.100.10.18' as client 'admin' azs: - cloud_properties: availability_zone: nova name: z1 compilation: az: z1 network: default reuse_compilation_vms: true vm_type: default workers: 5 disk_types: - disk_size: 3000 name: default - disk_size: 50000 name: large networks: - name: default subnets: - az: z1 cloud_properties: net_id: 6274c624-e262-4ba1-845f-7548c91a813f dns: - 8.8.8.8 gateway: 192.168.1.1 range: 192.168.1.0/24 type: manual - name: vip type: vip vm_types: - cloud_properties: instance_type: default name: default but now I am getting below mentioned error 14:02:48 | Preparing deployment: Preparing deployment (00:00:00) L Error: Instance group 'smoke-tests' references an unknown vm type 'm1.tiny' 14:02:48 | Error: Instance group 'smoke-tests' references an unknown vm type 'm1.tiny' Started Wed Aug 9 14:02:48 UTC 2017 Finished Wed Aug 9 14:02:48 UTC 2017 Duration 00:00:00 Task 117 error Updating deployment: Expected task '117' to succeed but state is 'error' Exit code 1 can you help with this? I have not uploaded cpi config till now. Do you think that cpi config is required? |
|
|
|
Re: Cloud Foundry Deployment using bosh
Hi David,
Thanks for your response. Yes.. I am using Openstack for cloud. If possible send me sample file for cloud config. |
|
|
|
Re: [cf-dev] Re: bosh lite v2
David Sabeti
Hi cf-dev,
toggle quoted message
Show quoted text
To add to this, I wanted to clarify what the Release Integration team is currently validating, and what we will plan to validate, in our pipelines. *Currently* We validate cf-release against the deprecated Vagrant workflow, and cf-deployment against the new bosh-lite workflow that uses bosh-deployment as described on bosh.io. *In the near future -- about two weeks* We're going to switch to using the bosh-deployment workflow for cf-release, and support that for the remainder of cf-release's lifetime. cf-deployment will continue to be validated on the bosh-deployment workflow as well. *tl;dr - The Release Integration team will stop validating the Vagrant workflow for bosh-lite in two weeks, so please switch to using the workflow described on bosh.io <http://bosh.io>* Thanks, David Sabeti CF Release Integration Project Lead On Fri, Aug 4, 2017 at 3:05 PM Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:
+cf-dev |
|
|
|
Re: Cloud Foundry Deployment using bosh
David Sabeti
Hi Arpit,
It looks like you're missing a cloud-config <http://bosh.io/docs/cloud-config.html>. You'll need to write a cloud-config and upload it to your bosh director. Which IaaS are you using? I may be able to help you find an example cloud-config to use. David On Tue, Aug 8, 2017 at 1:16 AM Arpit Sharma <arpitvipulsharma(a)gmail.com> wrote: Dear Team, |
|
|
|
Cloud Foundry Deployment using bosh
Dear Team,
I am getting below mentioned error, when I am trying to deploy cloudfoundry using cf-deployment. 07:35:43 | Preparing deployment: Preparing deployment (00:00:00) L Error: Required property 'networks' was not specified in object ({}) 07:35:44 | Error: Required property 'networks' was not specified in object ({}) Started Tue Aug 8 07:35:43 UTC 2017 Finished Tue Aug 8 07:35:44 UTC 2017 Duration 00:00:01 Task 101 error Updating deployment: Expected task '101' to succeed but state is 'error' Exit code 1 Anybody can help me with this? |
|
|
|
Re: How to avoid job restart while scaling bosh deployment?
Ronak Banka
Hemant,
toggle quoted message
Show quoted text
Unless there is a shared configuration which changes when you add a new instance, Bosh will not trigger deploy on your remaining instances. Can you paste your manifest here (masking secrets)? Thanks Ronak ᐧ On Mon, Aug 7, 2017 at 12:41 PM, hemant patre <hbpatre(a)gmail.com> wrote:
I am using bosh to deploy one database cluster on n instances. After that |
|
|
|
How to avoid job restart while scaling bosh deployment?
hemant patre
I am using bosh to deploy one database cluster on n instances. After that while scaling cluster I want to add one more instance to this cluster (so new cluster size will be n+1). I am changing manifest file to have instances value as n+1. When I am executing deploy command with modified manifest file, it is creating cluster of n+1 instances (n old instances and 1 new VM started). It is as per expectation. But in this process, job (database service) on all instances got restarted. I just want to add new instance without disturbing running jobs (services) on already running VMs. How to achieve this?
|
|
|
|
Adding a new blobstore provider (foo) in bosh
PARTHASARATHI KUNDU
Hi,
How can I add a new blobstore provider foo in bosh ? I have implemented fog-foo for the storage service and modified the configurations(private.yml and final.yml) as per http://bosh.io/docs/reference/blobs.html for the foo storage provider. Looks it recognizes only Cannot initialize blobstore: Unknown client provider 'OracleBM', available providers are: ["dav", "simple", "s3", "local", "s3cli"] So that means somewhere I have to inject the fog-foo in bosh . I can do that in cloudfoundry by modifying https://github.com/cloudfoundry/cloud_controller_ng/blob/e42d61adb9335ac18690456e1ae0997432b4f390/lib/cloud_controller/blobstore/fog/providers.rb Can you please suggest me how can i inject this for bosh. -- Regards Partha |
|
|
|
Re: bosh lite v2
Dmitriy Kalinin
+cf-dev
toggle quoted message
Show quoted text
On Fri, Aug 4, 2017 at 2:49 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote:
hey all, |
|
|
|
bosh lite v2
Dmitriy Kalinin
hey all,
as some of you may know, we have been recently recommending to install bosh lite via cli v2 instead of vagrant. we haven't found any serious drawbacks to the new approach so i would like to recommend new approach to everyone. i've updated cloudfoundry/bosh-lite repo to point to new bosh.io docs about bosh-lite. here are some advantages to the new approach: - uses cli v2 standard create-env - uses official vsphere stemcell as a host image for vbox - allows to configure director with uaa and credhub - "bosh lite" can be installed on any supported iaas (not just vbox) we are happy to answer any questions on cloudfoundry #bosh slack. cheers, dmitriy |
|
|
|
how can we make emphasize to recognize a new blobstore provider
PARTHASARATHI KUNDU
I have modified the config/final.yml and config/private.yml as per the new blobstore provider(foo) as per http://bosh.io/docs/reference/blobs.html. But I am not sure how to inject the new blobstore in bosh.
Obviously I get the error as below when I am trying to upload blobs using bosh cli Cannot initialize blobstore: Unknown client provider 'OracleBM', available providers are: ["dav", "simple", "s3", "local", "s3cli"] How can I make bosh to recognize "foo" ? |
|
|
|
Re: Bosh Director/CredHub question
Dmitriy Kalinin
director does not support interpolation within interpolation. this example seems to be very specific. are you trying to do cred rotation?
toggle quoted message
Show quoted text
Sent from my iPhone On Aug 2, 2017, at 10:55 AM, Michael Stancampiano <mstancamp(a)gmail.com> wrote: |
|
|
|
Bosh Director/CredHub question
Michael Stancampiano
Can the Bosh Director process a manifest file identifier that contains within it another identifier? For example:
Stored in CredHub would be the secrets /consul_cert/V1 and /cert_version In the manifest file the following would be specified: consul_cert: (( /consul_cert/(( /cert_version )) )) This would result in the outer identifier having the form: (( /consul_cert/V1 )) Thanks. |
|
|
|
Re: bosh director via http proxy
Daniel Hermans <daniel.hermans@...>
Thanks Dmitry!
For anyone else looking i added: -o bosh-deployment/misc/proxy.yml -v http_proxy=${http_proxy} -v https_proxy=${https_proxy} -v no_proxy=${no_proxy} to the end of my create-env command! |
|
|
|
Re: bosh director via http proxy
Dmitriy Kalinin
i think adding this ops file will help:
toggle quoted message
Show quoted text
https://github.com/cloudfoundry/bosh-deployment/blob/master/misc/proxy.yml Sent from my iPhone On Aug 1, 2017, at 6:32 PM, Daniel Hermans <daniel.hermans(a)gmail.com> wrote: |
|
|
|
bosh director via http proxy
Daniel Hermans <daniel.hermans@...>
Hi,
attempting to start a bosh deployment. My work machine uses a http proxy for internet access. I have set http_proxy and https_proxy variables in the shell but getting stuck. Am i missing something? I can see bosh attempting to do direct network connections to AWS rather than use the proxy: $ netstat -tn Active Internet connections (w/o servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 1 10.39.224.104:36468 54.240.195.243:443 SYN_SENT Error message from bosh create-env: $ bosh create-env bosh-deployment/bosh.yml --state=state.json --vars-store=creds.yml -o bosh-deployment/aws/cpi.yml -v director_name=bosh-1 ........... Started validating Downloading release 'bosh'... Skipped [Found in local cache] (00:00:00) Validating release 'bosh'... Finished (00:00:01) Downloading release 'bosh-aws-cpi'... Skipped [Found in local cache] (00:00:00) Validating release 'bosh-aws-cpi'... Finished (00:00:00) Validating cpi release... Finished (00:00:00) Validating deployment manifest... Finished (00:00:00) Downloading stemcell... Skipped [Found in local cache] (00:00:00) Validating stemcell... Finished (00:00:00) Finished validating (00:00:01) Started installing CPI Compiling package 'ruby_aws_cpi/c6ba8a1e1b53b94ee9caf13d2d749c40cecfa038'... Finished (00:00:00) Compiling package 'bosh_aws_cpi/137cfc70652337ff1d3fca795e6d9ddd6e7e68dd'... Finished (00:00:00) Installing packages... Finished (00:00:00) Rendering job templates... Finished (00:00:00) Installing job 'aws_cpi'... Finished (00:00:00) Finished installing CPI (00:00:00) Starting registry... Finished (00:00:00) Uploading stemcell 'bosh-aws-xen-hvm-ubuntu-trusty-go_agent/3421.9'... Failed (00:03:36) Stopping registry... Finished (00:00:00) Cleaning up rendered CPI jobs... Finished (00:00:00) creating stemcell (bosh-aws-xen-hvm-ubuntu-trusty-go_agent 3421.9): CPI 'create_stemcell' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Unable to create a connection to AWS. Please check your provided settings: Region 'ap-southeast-2', Endpoint 'Not provided'.\nIaaS Error: #\u003cSeahorse::Client::NetworkingError: execution expired\u003e","ok_to_retry":false} Exit code 1 Any help appreciated... Thanks! |
|
|
|
Re: bosh resurrection question
강경원 <atplus12345 at gmail.com...>
Our scenario is 4vms down and how long it wil take to recover. Test result
toggle quoted message
Show quoted text
was bsoh resurrects vm one by one. So it took about 20 minutes for just 4 vms. On Jul 29, 2017 11:29 AM, "강경원" <atplus12345(a)gmail.com> wrote:
|
|
|
|
Re: Not able to upload stemcell
Thanks Ronak,
Done... There was no internet on director. I have done mannually. |
|
|