Hi,
I use spiff manifest templates included by cf-release and diego-release,
and generate manifests by spiff, but I usually use the manifests as
reference materials.
I finally adjust my own manifests by refering to spiff generated manifests,
job definitions of cf-release and/or diego-release, and do try-and-error...
Now, setting parameters of diego components are changing with every version,
so job definitions of diego-release are essential reference.
Regards,
Ken Ojiri
---
Ken Ojiri <ozzozz(a)gmail.com>
Mitaka, Tokyo Japan
toggle quoted message
Show quoted text
On Tue, May 12, 2015 at 5:56 PM, 王天青 <wang.tianqing.cn(a)gmail.com> wrote:
Hi Ken,
How do you generate the manifest file?
Thanks
Best Regards~!
Grissom
On Mon, May 11, 2015 at 9:17 PM OzzOzz <ozzozz(a)gmail.com> wrote:
Hi,
I have posted a sample BOSH deployment manifest to Gist.
https://gist.github.com/ozzozz/4c08c37863b703a75afc
I could deploy cf-release v207 and diego-release 0.1099.0 to AWS Tokyo
region by MicroBOSH.
I could also deploy cf-release and diego-release to OpenStack(Juno).
The manifests differs only in 'networks', 'cloud_properties' and
'stemcell'.
Regards,
Ken
---
<ozzozz(a)gmail.com>
Mitaka, Tokyo Japan
On Sat, May 9, 2015 at 8:57 PM, Tom Sherrod <tom.sherrod(a)gmail.com> wrote:
Hi,
Are there any examples or docs on installing Diego with bosh/microbosh?
Using the bosh-lite as a template, I'm tripping up on various parts. Is
this
even a valid direction in installing?
Either AWS or Openstack..
Thanks,
Tom
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
