Re: - CC configuration in deployment manifest


Kinjal Doshi
 

Thanks a lot Dieu, that answers my question.

I have another question about creating a deployment manifest using the
following as guidelines: http://do
<http://docs.cloudfoundry.org/deploying/aws/cf-stub.html#editing>
cs.cloudfoundry.org/deploying/aws/cf-stub.html#editing
<http://docs.cloudfoundry.org/deploying/aws/cf-stub.html#editing>

The stud mentions that it requires 2 networks cf1 and cf2. I have created a
VPC with CIDR as 10.10.0.0/16 and am creating two public subnets cf1 and
cf2 with CIDR as 10.10.160/20 and 10.10.80.0/20. Is that the correct
approach? Or are these required to be private subnets.

In case of the minimal-aws deployment one private and one public subnet was
required but here since they are used for different zones, I am not sure if
both should be private or public or 1 each. Would be great if you could
please help me understand.

Thanks,
Kinjal

On Wed, Feb 3, 2016 at 1:05 AM, Dieu Cao <dcao(a)pivotal.io> wrote:

Hi Kinjal,

We generally recommend naming it with a specific identifiable folder name
that is not the bucket root.

This might look like:
...
buildpack_directory_key: buildpacks
....
droplet_directory_key: droplets
...

or
...
buildpack_directory_key: dev-cc-buildpacks
...
droplet_directory_key: dev-cc-droplets
...

Hope that helps.
Similarly for app_package_directory_key and resource_directory_key

-Dieu
CF CAPI PM

On Tue, Feb 2, 2016 at 7:29 AM, Kinjal Doshi <kindoshi(a)gmail.com> wrote:

Hi,

I have a question regarding the configuration of cloud controller.

It is described at
http://docs.cloudfoundry.org/deploying/aws/cf-stub.html#editing that
DROPLET_DIRECTORY_KEY should be replaced with the directory/bucket used to
store the droplets and BUILDPACK_DIRECTORY_KEY should be replaced with the
directory/bucket used to store buildpacks

Please help me understand if there should be specific values for these
two parameters or it could be just any random directory name which is
created later?

Thanks,
Kinjal





Join {cf-dev@lists.cloudfoundry.org to automatically receive all group messages.