Re: BOSH CPI for Alibaba
Gwenn Etourneau
No as far as I know, I don't think there is a CPI for Alibaba.
toggle quoted message
Show quoted text
But it's a good chance for you to contribute to the community. Thanks On Mon, May 29, 2017 at 6:17 PM, Gunakar Rao <gunakarp(a)gmail.com> wrote:
Hello Team, |
|
BOSH CPI for Alibaba
Gunakar Rao
Hello Team,
Any pointers , if BOSH CPI available for Alibaba cloud !! From official doc[https://bosh.io/docs/build-cpi.html], I can see AWS ,Azure ,OpenStack ,vSphere ,vCloud CPI release . In terms of development , SDK from alibaba is also available. There is a ref here, not much progress since 2 years. Thanks Gunakar |
|
BOSH CPI for Alibaba !!
Gunakar Rao
Hello Team,
From the official docs : https://bosh.io/docs/build-cpi.html , i am see the CPI for AWS , Azure , OpenStack , vSphere , vCloud . Wondering if any CPI available for Alibaba Cloud ?? |
|
Re: Proposal: Rename disk_types.cloud_properties.type
Danny Berger
I agree this could be a bit confusing to both newcomers and others. I'm not
toggle quoted message
Show quoted text
sure renaming the `disk_types.cloud_properties.type` is the correct solution though. The values in `cloud_properties` should be values which make sense and are native to the IaaS, so they'll all follow slightly different conventions and should probably be more consistent to the IaaS context than a BOSH context. VM types could have a similar discussion. The persistent_disk_type/disk_types/disk_pool confusion should hopefully pass with time as everyone consolidates on cloud-config-type manifests. As a compromise to at least help give the user a better hint, I wonder if director could say something like `Persistent disk "default" not found (expected "small", "large", "large_gp2")`. On Thu, May 18, 2017 at 12:12 PM, Evan Farrar <evanfarrar(a)gmail.com> wrote:
After helping a BOSH Bootloader user today with deploying a BOSH release --
Danny Berger |
|
Why does the ConfigDrive settings require a MetaData file?
Krishnan Ramanathan
Hello,
I am just trying to understand why the ConfigDrive settings require a MetaData file? I can see that for the CDROM settings, we simply skip the PublicSSHKeyForUsername, however when using a ConfigDrive, if the MetaData file is not present then the bosh agent returns an error. Could the bosh-agent simply skip and not error out if the MetaData file is not defined? If someone can explain this with some actual use case examples, then I would appreciate it. Thanks Krishnan |
|
Re: Building stemcell on ESX/vSphere
Krishnan Ramanathan
Thanks Danny!
|
|
Re: Insert system cacert from bosh-init or create-env?
Tom Sherrod <tom.sherrod@...>
Yes, that worked.
toggle quoted message
Show quoted text
Thank you. On Mon, May 22, 2017 at 2:31 PM, Amit Gupta <agupta(a)pivotal.io> wrote:
I haven't tried it myself, but I think colocated the ca_certs job from the |
|
Re: Insert system cacert from bosh-init or create-env?
Amit Kumar Gupta
I haven't tried it myself, but I think colocated the ca_certs job from the
toggle quoted message
Show quoted text
os-conf-release might work: https://github.com/cloudfoundry/os-conf-release/tree/master/jobs/ca_certs Amit On Mon, May 22, 2017 at 11:15 AM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:
Hi, |
|
Insert system cacert from bosh-init or create-env?
Tom Sherrod <tom.sherrod@...>
Hi,
Is there a way to get a private ca cert into the microbosh instance with bosh-init or create-env? We are trying to upload releases from an https site that has a private cert. Trusted certs works fine for bosh deployed instances. I'm now trying to determine a way to get the microbosh director itself to work with it. Thanks, Tom |
|
Re: Cloud Foundry Support for Canaries
Stephen Peggs
Have you read about blue green deploys?
toggle quoted message
Show quoted text
https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html. I think it covers the same sort of space, ensuring the development version is good before rolling production users in to it. On Fri, 19 May 2017 at 21:37, Sean Keery <skeery(a)pivotal.io> wrote:
A simple timed canary strategy could use something like |
|
Re: Cloud Foundry Support for Canaries
Sean Keery <skeery@...>
A simple timed canary strategy could use something like
https://github.com/krujos/scaleover-plugin. More complex application canary scenarios have been created with CD systems such as Jenkins or Concourse. Finally, you could use a third party tool such as Spinnaker, which specializes in complex application deployments. Sean On Fri, May 19, 2017 at 4:42 AM Christian Brinker <cbrinker(a)evoila.de> wrote: Hi Shane,-- *Sean Keery | Minister of Chaos | Pivotal Cloud Foundry Solutions* Mobile: 970.274.1285 | skeery(a)pivotal.io LinkedIn: @zgrinch <http://www.linkedin.com/in/zgrinch> | Twitter: @zgrinch <https://twitter.com/zgrinch> | Github: @skibum55 <https://github.com/skibum55> Adopt the Silicon Valley state of mind |
|
BOSH service deploy throwing CPI error
subin alex
Hi Experts,
I am trying to deploy an enterprise application on Openstack instance jumpbox.I have BOSH and CloudFoundry already setup and is working fine.However ,while i am deploying my application services to BOSH,I am getting below error, Failed: CPI error 'Bosh::Clouds::VMCreationFailed' with message 'VM creation with name 'ZZZZ' failed. Following network IDs are not existing or not accessible from this project: 'XXXX'. Make sure you do not use subnet IDs' in 'create_vm' CPI method (00:00:02) From the error message,it looks likean issue wherein BOSH is prevented from creating VMs on configured floating IPs on the instance(with id 'XXXX'). But I am unable to narrow down as to where is the exact problem lying. Can you guys please help me out on this? Thanks & Regards, Subin |
|
Re: Cloud Foundry Support for Canaries
Christian Brinker
Hi Shane,
toggle quoted message
Show quoted text
please do not mix up BOSH with CF. With BOSH you deploy virtual machines. It is used for example to deploy Cloud Foundry. The canaries support here is for example used for changing the Cloud Foundry platform deployment. Your apps pushed to Cloud Foundry have no direct connection to it. https://github.com/cloudfoundry-incubator/cf_canaries#instances-canary would be more the canary solution you need. I am not that involved with that project. So I am not sure it works. This should be answered by one other here out of the community. But there are also exist other approaches like https://github.com/cloudfoundry/diegocanaryapp and a discussion about zero-downtime deployments was there some time ago. But I did not follow the actual outcome. If you want a more active influence to the routing, you can use routing services. See https://docs.cloudfoundry.org/services/route-services.html for it. There is also an example limiting the rate of traffic to an application. It is not exactly your problem, but may present you some hints for your problem. Greets Christian On Fri, 19 May 2017 at 12:10 Shane Gannon <sgannon200(a)gmail.com> wrote:
I've evaluating Cloud Foundry to determine whether it supports Canary --
E-Mail: cbrinker(a)evoila.de evoila GmbH Wilhelm-Theodor-Römheld-Str. 34 55130 Mainz Germany Geschäftsführer: Johannes Hiemer Amtsgericht Mainz HRB 42719 Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If You are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. |
|
Cloud Foundry Support for Canaries
Shane Gannon
I've evaluating Cloud Foundry to determine whether it supports Canary Releases for my apps.
https://martinfowler.com/bliki/CanaryRelease.html So far I've found references to BOSH supporting canaries. But this appears to be an internal mechanism that cloud foundry uses when re-deploying its own servers. I've also had a look at https://github.com/cloudfoundry-incubator/cf_canaries but this appears to be for testing the infrastructure / overall system. e.g. Canaries to warn about memory/cpu/disk/network etc usage. Are there any common approaches to supporting Canary Deploys with Cloud Foundry? I imagine it would need to relate to the GoRouter somehow. The closest I've come to finding a solution is the documentation from Cloud Foundry on Blue-Green Deployments. https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html But this technic would not let me control the percentage of, or which, traffic is routed to the Canary. |
|
bosh-gen for bosh 2.0
Dr Nic Williams
https://github.com/cloudfoundry-community/bosh-gen/pull/97
With bosh2 <https://github.com/cloudfoundry/bosh-cli/> now GA, we've been migrating all community releases to assume bosh2 usage. There are some subtle required changes, and some stylistic changes. bosh-gen is being upgraded so that new BOSH releases look and feel like this new style. The first release is now available via the PR above. git clone https://github.com/cloudfoundry-community/bosh-gen -b bosh2 cd bosh-gen bundle rake install:local bosh-gen will also try to help generate releases that produce no bosh-lint linting errors (read introduction <http://www.starkandwayne.com/blog/using-bosh-lint-gives-us-consistent-conventions-for-bosh-releases-and-manifests/> ) Perhaps some features of bosh-gen can be removed due to overlapping inclusion in bosh2, so we'll figure that out as we go. Feedback in the PR appreciated! Cheers Dr Nic & maintainers of bosh-gen -- Dr Nic Williams Stark & Wayne LLC http://starkandwayne.com +61 437 276 076 twitter @drnic |
|
Proposal: Rename disk_types.cloud_properties.type
Evan Farrar <evanfarrar@...>
After helping a BOSH Bootloader user today with deploying a BOSH release
I've realized that there is a small pain point in the BOSH cloud-config schema that could be resolved. I suggest we disambiguate the schema and terminology used within BOSH regarding disk types. There are three closely related things that all re-use the term “type”: persistent_disk_type, disk_types, and disk_types.cloud_properties.type. This is a recent issue, because previously disk_pool was renamed to disk_type to clarify the relationship between persistent_disk_type and disk_pool. Problem: A user receives an error message like “Persistent disk “default” not found.” She must consult her cloud-config for an acceptable disk type to substitute and may be led to believe that “S4” or “gp2” would be an acceptable value when in fact the persistent_disk_type field requires a value from disk_types.name. Solution: Renaming disk_types.cloud_properties.type to disk_types.cloud_properties.storage. I have based this on the terminology used on IaaS pricing documentation, where most use the term “volume type” or “volume storage” for this piece of information. I'm curious what others think of this proposal. Please add comments and suggestions on this document <https://docs.google.com/document/d/1VpWLtVWOF38Y65WY7Zpqd2qLKYfzE4CkdlufsqbLBbA/edit?usp=sharing>[1] or via mailing list. [1] https://docs.google.com/document/d/1VpWLtVWOF38Y65WY7Zpqd2qLKYfzE4CkdlufsqbLBbA/edit?usp=sharing |
|
Bosh task would not finish but hang indefinitely
Kamen Tomov
The following script hangs on upload stemcell. If I replace upload stemcell with upload release it hangs as well.
bosh -n target https://${bd_ip}:25555/ bosh login admin admin bosh update cloud-config bosh/cloud-config.yml bosh upload stemcell https://s3.amazonaws.com/bosh-core-stemcells/aws/bosh-stemcell-3312.20-aws-xen-ubuntu-trusty-go_agent.tgz --skip-if-exists bosh upload release https://bosh.io/d/github.com/cloudfoundry/syslog-release?v=11 Here is what output I get: + bosh -n target https://10.111.2.6:25555/ Target set to 'my-bosh' + bosh login admin admin Logged in as 'admin' + bosh update cloud-config bosh/cloud-config.yml Acting as user 'admin' on 'my-bosh' Successfully updated cloud config + bosh upload stemcell https://s3.amazonaws.com/bosh-core-stemcells/aws/bosh-stemcell-3312.20-aws-xen-ubuntu-trusty-go_agent.tgz --skip-if-exists Acting as user 'admin' on 'my-bosh' Using remote stemcell 'https://s3.amazonaws.com/bosh-core-stemcells/aws/bosh-stemcell-3312.20-aws-xen-ubuntu-trusty-go_agent.tgz' It just waits afterwards. Here is some additional info: bosh tasks Acting as user 'admin' on 'my-bosh' +---+--------+---------+-------------------------+-------+------------+-----------------+--------+ | # | State | Started | Last Activity | User | Deployment | Description | Result | +---+--------+---------+-------------------------+-------+------------+-----------------+--------+ | 7 | queued | - | 2017-05-15 15:37:25 UTC | admin | | create stemcell | | +---+--------+---------+-------------------------+-------+------------+-----------------+--------+ Total tasks running now: 1 ***************************************************************** bosh task 7 --debug Acting as user 'admin' on 'my-bosh' Director task 7 I, [2017-05-15T15:37:25.066320 #7252] [0x2ad04fd3f118] INFO -- TaskHelper: Director Version: 261.4.0 I, [2017-05-15T15:37:25.066360 #7252] [0x2ad04fd3f118] INFO -- TaskHelper: Enqueuing task: 7 ***************************************************************** bosh --version BOSH 1.3262.26.0 I would appreciate your help. |
|
Re: Certificates management
Sylvain Goulmy <sygoulmy@...>
Wrong mailing list, i start a new thread on cf-dev.
|
|
Certificates management
Sylvain Goulmy <sygoulmy@...>
Hi all,
I see in the security configuration for consul that there is a specific procedure to change existing certificates if you want to rotate to a new set. I was wondering if that also applies for the other cf component (cc, etcd, loggregator) or if this is only specific for the consul component ? If this is consul specific, does it mean that for the other components you just have to change the certs in your stub and deploy ? Thanks in advance for your feedback. Sylvain |
|
Re: Building stemcell on ESX/vSphere
Danny Berger
Hi Krishnan - the stemcell-related code was split off into a separate repo,
https://github.com/cloudfoundry/bosh-linux-stemcell-builder. It has an updated README.md should contain all the files you're interested in. Danny On Mon, May 8, 2017 at 7:48 PM, Krishnan Ramanathan <krishnan(a)brkt.com> wrote: Hello, -- Danny Berger |
|