|
Re: How to access the IP of my other instance inside my app
Ushani Balasooriya
Hi Daniel,
I'm trying create a cluster setup which is configurable for n number of instances. So, How can I access the IP set for a particular IP dynamically? Or is there a way where I can access them using a pre defined host which it can resolve the IP by itself? Appreciate your help |
|
|
|
Re: How to access the IP of my other instance inside my app
Daniel Mikusa <dmikusa@...>
I think you want Bosh links, but more specifically a self link ->
https://bosh.io/docs/links.html#self Dan On Wed, Sep 20, 2017 at 5:48 AM, Ushani Balasooriya <ushanib(a)gmail.com> wrote: Hi there, |
|
|
|
How to access the IP of my other instance inside my app
Ushani Balasooriya
Hi there,
Im going to deploy my application in BOSH and cluster it with n number of nodes. E.g., 2 So in my app, when I deploy the app in my manifest.yml I have defined below. So it starts at 10.244.15.21 and next node starts in 10.244.15.22 when give instances : 2 in my manifest.yml static: - 10.244.15.2 - 10.244.15.20 So in my each app I need to access each other nodes' IPs inside a XML file. How can i do this dynamically in a xml file. Please advice. Thanks E.g., <parameter name="localMemberHost">127.0.0.1</parameter> <members> <member> <hostName>10.244.15.21</hostName> <port>4000</port> </member> <member> <hostName>10.244.15.22</hostName> <port>4000</port> </member> </members> |
|
|
|
Re: not running after update. Review logs for failed jobs - deploy fails
Ushani Balasooriya
Could not figure out any solution. Created the same project from scratch with same configs and it started working
|
|
|
|
not running after update. Review logs for failed jobs - deploy fails
Ushani Balasooriya
bosh -e vbox -d wso2is deploy wso2is-manifest.yml.
This is what I get, Task 29 | 13:24:38 | Deprecation: Ignoring cloud config. Manifest contains 'networks' section. Task 29 | 13:24:38 | Preparing deployment: Preparing deployment (00:00:00) Task 29 | 13:24:38 | Preparing package compilation: Finding packages to compile (00:00:00) Task 29 | 13:24:38 | Updating instance wso2is: wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0) (canary) (00:03:16) Error: 'wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0)' is not running after update. Review logs for failed jobs: wso2is Task 29 | 13:27:54 | Error: 'wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0)' is not running after update. Review logs for failed jobs: wso2is =========== After spending sometime learnt to check debug logs and When I checked the debug logs it shows only this, Mon Sep 18 13:27:29 UTC 2017 Kicking off ctl script as root with start Mon Sep 18 13:27:32 UTC 2017 JAVA_HOME: /var/vcap/packages/oraclejdk/jdk1.8.0_144/ Mon Sep 18 13:27:32 UTC 2017 JAVA_BINARY: /var/vcap/packages/oraclejdk/jdk1.8.0_144//bin/java I googled and found to increase the canary_watch_time and update_watch_time as a solution. But still it didnt work I see 2 // in JAVA_BINARY: /var/vcap/packages/oraclejdk/jdk1.8.0_144//bin/java and cannot figure out how it comes. can it be the reason? I removed 1 / from the ctl.erb as well. But no luck. |
|
|
|
Re: /config/blobs.yml: no such file or directory
Ushani Balasooriya
Executing bosh init-release command created it for me.
|
|
|
|
/config/blobs.yml: no such file or directory
Ushani Balasooriya
It seems the config/blolbs.yml is not available. How can I resolve this?
bosh -e vbox add-blob /home/wso2/Downloads/jdk-8u144-linux-x64.tar.gz oraclejdk/jdk-8u144-linux-x64.tar.gz Tracking blob: Reading blobs index: Opening file /home/wso2/newBOSH/config/blobs.yml: open /home/wso2/newBOSH/config/blobs.yml: no such file or directory |
|
|
|
Re: Unknown disk type '5GB' in consul instance group when
Dmitriy Kalinin
you might have to update your cloud config with one that cf-deployment
toggle quoted message
Show quoted text
wants: bosh -e 192.168.50.6 ucc <(wget -O- https://raw.githubusercontent.com/cloudfoundry/cf-deployment/master/bosh-lite/cloud-config.yml ) On Sun, Sep 17, 2017 at 10:39 PM, Karan Shukla <shuklak13(a)gmail.com> wrote:
I've been trying to deploy Cloud Foundry on a local machine using Bosh |
|
|
|
Unknown disk type '5GB' in consul instance group when
Karan Shukla
I've been trying to deploy Cloud Foundry on a local machine using Bosh Lite on a VM via cf-deployment.
According to the documentation, the following command should build Cloud Foundry bosh -e 192.168.50.6 -d cf deploy cf-deployment.yml \ -o operations/bosh-lite.yml \ --vars-store deployment-vars.yml \ -v system_domain=bosh-lite.com The process successfully completes the first thirty tasks or so, and then I run into the following error. Error: Instance group 'consul' references an unknown disk type '5GB' Anyone have some insight on what 'consul' is and how I can fix it? Seems to be related to cloud-config.yml but I'm not sure which one in particular I should be looking into (there's one for both cf-deployment and bosh-deployment). |
|
|
|
Re: When I try to save the environment with the alias vbox it gives Missing PEM block
Ushani Balasooriya
Pls ignoe prvious comment
Issue was a space before the ( bracer. Correct command is as below. bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) Using environment '192.168.50.6' as anonymous user Name Bosh Lite Director UUID 575074fe-09db-4c88-8aae-eb8284b3d702 Version 263.2.0 (00000000) CPI warden_cpi Features compiled_package_cache: disabled config_server: disabled dns: disabled snapshots: disabled User (not logged in) Succeeded |
|
|
|
Re: When I try to save the environment with the alias vbox it gives Missing PEM block
Ushani Balasooriya
Issue was I had extra ) at the end of the command.
bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) should be bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca |
|
|
|
When I try to save the environment with the alias vbox it gives Missing PEM block
Ushani Balasooriya
bosh -e 192.168.50.6 alias-env vbox --ca-cert vbox/creds.yml
Validating Director connection config: Parsing certificate 1: Missing PEM block Exit code 1 Please explain me the below command. What is the --path parameter? I do not have a director_ssl folder. Also Is my above command correct? I have a folder called vox and creds.yml inside it. bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) |
|
|
|
Re: No progress can be seen with bosh create-env
Ushani Balasooriya
I found the reason. I had CF DEV VM running on my machine. When I had quit it showed me progress of downloading being done.
Finished (00:02:20) Validating release 'bosh'... Finished (00:00:00) Downloading release 'bosh-virtualbox-cpi'... Finished (00:02:39) Validating release 'bosh-virtualbox-cpi'... Finished (00:00:01) Downloading release 'bosh-warden-cpi'... .... |
|
|
|
Re: No progress can be seen with bosh create-env
Ushani Balasooriya
Below is what I get for past few hours.
bosh create-env bosh-deployment/bosh.yml \ --state vbox/state.json \Deployment manifest: '/home/wso2/BOSH/bosh-deployment/bosh.yml' Deployment state: 'vbox/state.json' Started validating Downloading release 'bosh'... |
|
|
|
No progress can be seen with bosh create-env
Ushani Balasooriya
When I tried to install Bosh Lite and executed the below step [2], it does not show any progress except the below [1] for few hours right now. Is it because of a network delay or anything wrong in my command? How can I know it is downloading correctly.
[1] Started validating Downloading release 'bosh'... [2] $ bosh create-env ~/workspace/bosh-deployment/bosh.yml \ --state state.json \ --vars-store ./creds.yml \ -o ~/workspace/bosh-deployment/virtualbox/cpi.yml \ -o ~/workspace/bosh-deployment/virtualbox/outbound-network.yml \ -o ~/workspace/bosh-deployment/bosh-lite.yml \ -o ~/workspace/bosh-deployment/jumpbox-user.yml \ -v director_name=vbox \ -v internal_ip=192.168.56.6 \ -v internal_gw=192.168.56.1 \ -v internal_cidr=192.168.56.0/24 \ -v network_name=vboxnet0 \ -v outbound_network_name=NatNetwork |
|
|
|
Bosh Director/CredHub API question
Michael Stancampiano
In CredHub documentation there are manifest identifiers defined with dot notation that seem to conform to the JSON objects for certificates (and other types) that can be specified in CredHub API calls. For example:
tls: ca: ((database-tls.ca)) certificate: ((database-tls.certificate)) private_key: ((database-tls.private_key)) Does the CredHub API support the usage of the dot notation to retrieve a specific value (such as a private_key)? For example: curl "https://example.com/api/v1/data?name=/database-tls.private_key" Does the Bosh Director when processing this manifest sample make one call to CredHub and retrieve all 3 values, using ?name=/database-tls ? |
|
|
|
CF Summit EU Unconference - Registration Open; Talks & Sponsors Requested
Daniel Jones
Hi all,
You can now register for the (free!) Unconference <https://www.eventbrite.co.uk/e/cf-summit-europe-2017-unconference-tickets-37837803890> at CF Summit Europe 2017. It'll take place between 1800-2200 on Tuesday 10th October, in the same venue as the Summit, and will feature food, drink, lightning talks, open space, and a pub quiz. If you think you may attend, *please* register, so we can make sure we have enough space, beer and food for everyone. Would you like to *talk at the Unconference*? We're looking for lightning talks (<= 10 minutes) to go along with the open space sessions. If you'd like to talk then please fill in our Google Form: https://goo.gl/forms/xB0beLDZ4Tk8AZjR2 We're open to novel talks, or cut-down versions of talks that didn't make the cut for the Summit itself. I expect that a fair few engineering folks will be in attendance, so excruciatingly technical talks are welcome! We're also *looking for sponsors* - if your organisation is interested, please contact Sara Lenz (slenz(a)anynines.com) for more information. Sponsor benefits include top-of-agenda lightning talks, signage, and online promotion. Regards, Daniel Jones - CTO +44 (0)79 8000 9153 @DanielJonesEB <https://twitter.com/DanielJonesEB> *EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry Specialists |
|
|
|
Re: Bosh - creating an aws instance - merge two calls into one
Dmitriy Kalinin
hey,
toggle quoted message
Show quoted text
we currently have two separate cpi methods for creating vms (create_vm) and setting metadata on the vms (set_vm_metadata). create_vm call does not receive necessary metadata to apply tags to the vm at creation time. potentially such functionality could be added in future. i would recommend adding an issue to https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release. dmitriy On Thu, Aug 31, 2017 at 4:02 PM, ram sajja <s_vrk(a)outlook.com> wrote:
Hello Every one, |
|
|
|
Problem with Azure Internal Load Balancer
Jonathan Stockley
Hi,
We have deployed BOSH 261.4 with Azure-CPI 260.5 with stemcell bosh-azure-hyperv-ubuntu-trusty-go_agent version 3363.27. I have deployed a BOSH release of our own application that uses two VMs and an Azure Internal Load Balancer. Everything works great for about an hour and then the ILB stops responding. The two VMs that are in the backend pool are still working fine and the health check probe URL is still responsive in both VMs. However after the ILB stops responding, there is no sign that it is sending the health check probe. I have been working with Microsoft Azure Support but so far we have not discovered any cause for this. It doesn’t help that there are no logs or diagnostics in Azure for an Internal LB, only for External LB. As a comparison, I manually deployed two Ubuntu Trusty (14.04) VMs using the Azure marketplace and setup an ILB in front of them and it has been working for the past 3 days without a problem. Has anyone else tried to use Azure Internal LB with BOSH? Could it be that the Azure stemcell we are using has a problem? Any help or suggestions would be most welcome. Thanks, Jo |
|
|
|
Bosh - creating an aws instance - merge two calls into one
ram sajja
Hello Every one,
we are currently using bosh version 262.3. The question I have is on how bosh provisions ec2 instances in AWS through bosh-aws-cpi. To give a little context on how provisioning on AWS used to happen In March, AWS Blog announced two new features we’re implementing: Ability to enforce required tags on RunInstances with IAM policy Ability to include tags on RunInstances with API and CLI Which means, before this date all provisioning was done in two steps: ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro --subnet-id <subnet-id> ec2-create-tags <instanceid> --tag "Name=<name_value>" --tag "App=<app_value>" --tag "AppOwner=<app_owner_value>" --tag "Environment=<env_value>" The new workflow assured that instance creation and tag management can be done in a single call. ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro --subnet-id <subnet-id> --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=<name_value>},{Key=App,Value=<app_value>},{Key=AppOwner,Value=<app_owner_value>},{Key=Environment,Value=<env_value>}]' Bosh ( tested with version 262.3 ) still seem to be provisioning instances in multiple calls instead of a single one. Bosh is issuing 1 api call just to create the instance, and then following that up with a 2nd api call to create-tags. Does anyone know if this is addressed in newer versions of bosh ? I looked at the code but did not seem like it and am not sure if this can be easily done ? any thoughts ? Thanks, Ram |
|
|