Date   

Re: Incubation request: App Auto-Scaling service

Marco Voelz
 

Thanks Dies for driving this proposal. We're looking forward to contributing with two of our engineers in full-time!

Warm regards
Marco

On 21/03/16 21:54, "Koper, Dies" <diesk(a)fast.au.fujitsu.com<mailto:diesk(a)fast.au.fujitsu.com>> wrote:

Hi Shannon,

Our App Auto-Scaling proposal has received overwhelming support from the community, and we have received and addressed various feedback.

Now, Fujitsu and IBM would like to put the proposal forward to the Services PMC as an incubation project.

Project name: App Auto-Scaling
Project proposal: https://docs.google.com/document/d/1HHhj9ZK-trI_VVDR34bwOnWem83UAq5_Pjr9imRTazY/edit?usp=sharing
Proposed Project Lead: Michael Fraenkel (IBM)
Proposed Scope: Please refer to the Goals and Non-goals sections in the proposal
Development Operating Model: Distributed Committer Model
Technical Approach: Please refer to the Deliverables section in the proposal
Initial team committed: 7 engineers: 2 from Fujitsu, 2 from SAP, 3 from IBM (not including the Lead)

As functionally IBM’s recently open sourced app auto-scaling solution (see https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/QRBQKDDG7PWS6EMEBWI4ARFQ3OGSSSWB) seems a good match to our proposal, the team will look at using that code.
Michael can be contacted to answer any IP concerns about this code.

Please let me know if you have any questions.

Regards,
Dies Koper
Fujitsu


From: Koper, Dies [mailto:diesk(a)fast.au.fujitsu.com]
Sent: Friday, February 19, 2016 11:53 AM
To: cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>
Subject: [cf-dev] Proposal: App Auto-Scaling service

Dear community,

We have relaunched this initiative and put together a proposal for an App Auto-Scaling service, ready for your review:

https://docs.google.com/document/d/1HHhj9ZK-trI_VVDR34bwOnWem83UAq5_Pjr9imRTazY/edit?usp=sharing

The proposal includes feedback from SAP, as well as some of the suggestions you have shared with me.

The intent is to start with a MVP, really a minimal yet useful solution, that can serve as a foundation to build upon to address the various problems raised.

We welcome your feedback, as well as your participation in this exciting project!

Regards,
Dies Koper
Fujitsu


Sourcey buildpack not working on Diego

Aaron Huber
 

I've got a few customers using the Sourcey buildpack along with
Perl/Mojolicious and we've found that it is non-functional when used on
Diego cells. It continues to work fine on DEA. Has anyone been successful
at deploying with this buildpack on Diego, or does anyone have any
suggestions on what might be different that's causing it to break?

I've posted on an issue in the buildpack repo but the developer could use
some help with documentation or some tips on what might be different.

https://github.com/oetiker/sourcey-buildpack/issues/1

Aaron Huber
Intel Corporation




--
View this message in context: http://cf-dev.70369.x6.nabble.com/Sourcey-buildpack-not-working-on-Diego-tp4275.html
Sent from the CF Dev mailing list archive at Nabble.com.


Incubation request: App Auto-Scaling service

Koper, Dies <diesk@...>
 

Hi Shannon,

Our App Auto-Scaling proposal has received overwhelming support from the community, and we have received and addressed various feedback.

Now, Fujitsu and IBM would like to put the proposal forward to the Services PMC as an incubation project.

Project name: App Auto-Scaling
Project proposal: https://docs.google.com/document/d/1HHhj9ZK-trI_VVDR34bwOnWem83UAq5_Pjr9imRTazY/edit?usp=sharing
Proposed Project Lead: Michael Fraenkel (IBM)
Proposed Scope: Please refer to the Goals and Non-goals sections in the proposal
Development Operating Model: Distributed Committer Model
Technical Approach: Please refer to the Deliverables section in the proposal
Initial team committed: 7 engineers: 2 from Fujitsu, 2 from SAP, 3 from IBM (not including the Lead)

As functionally IBM's recently open sourced app auto-scaling solution (see https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/message/QRBQKDDG7PWS6EMEBWI4ARFQ3OGSSSWB) seems a good match to our proposal, the team will look at using that code.
Michael can be contacted to answer any IP concerns about this code.

Please let me know if you have any questions.

Regards,
Dies Koper
Fujitsu


From: Koper, Dies [mailto:diesk(a)fast.au.fujitsu.com]
Sent: Friday, February 19, 2016 11:53 AM
To: cf-dev(a)lists.cloudfoundry.org
Subject: [cf-dev] Proposal: App Auto-Scaling service

Dear community,

We have relaunched this initiative and put together a proposal for an App Auto-Scaling service, ready for your review:

https://docs.google.com/document/d/1HHhj9ZK-trI_VVDR34bwOnWem83UAq5_Pjr9imRTazY/edit?usp=sharing

The proposal includes feedback from SAP, as well as some of the suggestions you have shared with me.

The intent is to start with a MVP, really a minimal yet useful solution, that can serve as a foundation to build upon to address the various problems raised.

We welcome your feedback, as well as your participation in this exciting project!

Regards,
Dies Koper
Fujitsu


Re: Connection refused - api.10.244.0.22.xip.io:443

Amit Kumar Gupta
 

I'm not sure what you mean by "adding changes which uses
api.10.244.0.22.xip.io". Why not use api.bosh-lite.com?

Also, I don't know anything ever used api.10.244.0.22.xip.io. The previous
domain was api.10.244.0.34.xip.io (34, not 22).

Best,
Amit

On Sat, Mar 19, 2016 at 9:06 PM, Wayne Ha <wayne.h.ha(a)gmail.com> wrote:

Amit,

You are right, if I use the default bosh-lite-v231.yml which uses
api.bosh-lite.com then the cf domains command works.

But now I am adding the changes for v231 into boshlite-devbox.yml based on
v226 which uses api.10.244.0.22.xip.io then the cf domains command fails.

Can I continue using api.10.244.0.22.xip.io?

Thanks,


Re: Reg the upgrade from cf-205 to cf-231

Amit Kumar Gupta
 

Awesome!

On Mon, Mar 21, 2016 at 3:12 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Thank you Gwenn and Amit

The fix works.



Regards

Nitiyasri



*From:* Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
*Sent:* Saturday, March 19, 2016 4:38 AM
*To:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>
*Cc:* Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X
(ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
*Subject:* Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231



Hi,



What is the value of uaa.require_https in your manifest ? By default is
true, try to put to false





Thanks



On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com> wrote:

Hi Amit,



Thanks a lot for your support as always!



Please see the detailed logs you are looking for:-





root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy#
cf login

API endpoint: https://api.testinceptionjk.cisco.com



REQUEST: [2016-03-18T16:30:28Z]

GET /v2/info HTTP/1.1

Host: api.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux







RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 632

Content-Type: application/json;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Server: nginx

X-Content-Type-Options: nosniff

X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997

X-Vcap-Request-Id:
a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281



{"name":"","build":"","support":"http://support.cloudfoundry.com
","version":0,"description":"","authorization_endpoint":"
http://uaa.testinceptionjk.cisco.com","token_endpoint":"
http://uaa.testinceptionjk.cisco.com
","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"
ssh.testinceptionjk.cisco.com:2222
","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"
https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://
loggregator.testinceptionjk.cisco.com:80
","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443
"}



REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Content-Type: application/json

User-Agent: go-cli 6.12.2-24abed3 / linux







REQUEST: [2016-03-18T16:30:28Z]

GET /login HTTP/0.0

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Referer: http://uaa.testinceptionjk.cisco.com/login

User-Agent: go-cli 6.12.2-24abed3 / linux







RESPONSE: [2016-03-18T16:30:28Z]

HTTP/1.1 200 OK

Content-Length: 487

Cache-Control: no-cache, no-store, max-age=0, must-revalidate

Cache-Control: no-store

Content-Language: en-US

Content-Type: application/json;charset=UTF-8

Date: Fri, 18 Mar 2016 16:30:28 GMT

Expires: 0

Pragma: no-cache

Server: Apache-Coyote/1.1

Strict-Transport-Security: max-age=31536000 ; includeSubDomains

X-Content-Type-Options: nosniff

X-Frame-Options: DENY

X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b

X-Xss-Protection: 1; mode=block



{"app":{"version":"3.1.0"},"links":{"uaa":"
http://uaa.testinceptionjk.cisco.com","passwd":"
https://console.testinceptionjk.cisco.com/password_resets/new","login":"
http://login.testinceptionjk.cisco.com","register":"
https://console.testinceptionjk.cisco.com/register
"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com
","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}



Email> admin



Password>

Authenticating...



REQUEST: [2016-03-18T16:30:35Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux



grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin



RESPONSE: [2016-03-18T16:30:35Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:35 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f



<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:



Password>

Authenticating...



REQUEST: [2016-03-18T16:30:42Z]

POST /oauth/token HTTP/1.1

Host: uaa.testinceptionjk.cisco.com

Accept: application/json

Authorization: [PRIVATE DATA HIDDEN]

Content-Type: application/x-www-form-urlencoded

User-Agent: go-cli 6.12.2-24abed3 / linux



grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin



RESPONSE: [2016-03-18T16:30:42Z]

HTTP/1.1 400 Bad Request

Content-Length: 1086

Content-Language: en

Content-Type: text/html;charset=utf-8

Date: Fri, 18 Mar 2016 16:30:42 GMT

Server: Apache-Coyote/1.1

X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7



<html><head><title>Apache Tomcat/7.0.61 - Error
report</title><style><!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY
{font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P
{font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--></style>
</head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must
be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b>
Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request
must be over https&quot;}</u></p><p><b>description</b> <u>The request sent
by the client was syntactically incorrect.</u></p><HR size="1"
noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>

Server error, status code: 400, error code: , message:



Password>



Thanks

Jayaraj



*From: *Amit Gupta <agupta(a)pivotal.io>
*Date: *Friday, March 18, 2016 at 11:37 AM
*To: *"Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)" <ngnanase(a)cisco.com>
*Cc: *"Discussions about Cloud Foundry projects and the system overall." <
cf-dev(a)lists.cloudfoundry.org>, Jayarajan Ramapurath Kozhummal <
jayark(a)cisco.com>


*Subject: *Re: Reg the upgrade from cf-205 to cf-231



Can you do:



CF_TRACE=true cf login



so we can get more info about where that 400 response code is coming from.



Best,

Amit



On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



Bosh deployment has completed successfully. I could set the endpoint, but
I could not login to it with the credentials I have given in the
properties. Logs and properties below.



root(a)testdeploy:/deploy# cf login

API endpoint: https://api.testdeploy.cisco.com



Email> admin



Password>

Authenticating...

Server error, status code: 400, error code: , message:



Password>

Authenticating...

Server error, status code: 400, error code: , message:





PROPERTIES::



scim:

# external_groups: null

# groups: null

userids_enabled: true

users:

- admin|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write

- services|<%= $common_password
%>|scim.write,scim.read,openid,cloud_controller.admin

#spring_profiles: null



Regards

Nithiyasri



*From:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at
Cisco)
*Sent:* Friday, March 18, 2016 7:23 AM
*To:* 'Amit Gupta' <agupta(a)pivotal.io>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* RE: Reg the upgrade from cf-205 to cf-231



Hi Amit



Thanks for your quick reply. Pls let me know in which Vm , should I login
to see the compilation logs..



Previously when I did the upgrade, it dint compile the individual
packages. Logs below.

Kindly let me know why is it trying to compile individual package now.




---------------------------------------------------------------------------------------

Started preparing package compilation > Finding packages to compile. Done
(00:00:00)



Started preparing dns > Binding DNS. Done (00:00:00)







Regards

Nithiyasri



*From:* Amit Gupta [mailto:agupta(a)pivotal.io <agupta(a)pivotal.io>]
*Sent:* Friday, March 18, 2016 5:36 AM
*To:* Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <
ngnanase(a)cisco.com>
*Cc:* Discussions about Cloud Foundry projects and the system overall. <
cf-dev(a)lists.cloudfoundry.org>; Jayarajan Ramapurath Kozhummal (jayark) <
jayark(a)cisco.com>
*Subject:* Re: Reg the upgrade from cf-205 to cf-231



I'm not sure why it's taking >40 mins to compile some simple go binaries.
You may have network issues (compilation jobs taking a long time to
download dependencies from BOSH director blobstore, or upload compiled
resulting artifacts) or you may need more CPU on your compilation
machines. You can try to SSH into the compilation VMs while they're
running to see what they're doing over those 40 minutes.



On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase -
TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com> wrote:

Hi Amit



I was able to do an upgrade of deployment from cf-205 to cf-231 multiple
times.

But now, I am getting timeout errors while compiling buildpacks once in
rootfs or in buildpack_java or in nginx..

Could you pls help us resolve this error..



Following is the one:



Done compiling packages >
buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)

Done compiling packages >
rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)

Failed compiling packages >
rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out
waiting for Server `3c04cecc-1308-4da
f-8dc5-b9c1924004c3' to be active (00:41:23)

Failed compiling packages >
nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for
Server `fbbb8647-1415-46d9-92de-d030f 4164b6b'
to be active (00:43:31)







Failed compiling packages >
cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server
`223ec673-b66d-4362-8e27-0859805 2ebe5' to be
active (00:44:49)



Error 100: Timed out waiting for Server
`3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active





Regards

Nithiyasri







Re: Using swift as a blobstore in cloud foundry with keystone v3

Nicholas Calugar
 

We have a story in flight:
https://www.pivotaltracker.com/story/show/115793253

If upgrading fog doesn't work, we'll happily take a PR that resolves this.

On Thu, Mar 17, 2016 at 5:33 PM Gwenn Etourneau <getourneau(a)pivotal.io>
wrote:

This can be nice ! As Bosh support V3 it can be nice that the CC do the
same.
To be able to fully use v3.



On Thu, Mar 17, 2016 at 6:30 PM, Voelz, Marco <marco.voelz(a)sap.com> wrote:

Dear Nicholas,

if desired, we can also do a PR for allowing the CC to connect to Swift
using Keystone v3. A couple of months ago we did the same thing in the
OpenStack CPI. We also have some test envs available where we can validate
the change. What do you think?

Warm regards
Marco

On 16/03/16 18:13, "Nicholas Calugar" <ncalugar(a)pivotal.io> wrote:

Hi Muhammad,

Unfortunately, we don't have an environment using keystone v3. We are
passing the configuration to fog as-is. There are several fixes that have
been made in later releases of fog, for example:

https://github.com/fog/fog/pull/3806

I'll get a story prioritized to upgrade fog to v1.37.0

Thanks,

Nick

On Sun, Mar 13, 2016 at 11:58 PM Altaf, Muhammad <
Muhammada(a)fast.au.fujitsu.com> wrote:

Hi All,

I am trying to configure cloud foundry to use swift on OpenStack. I have
followed the instructions at
https://docs.cloudfoundry.org/deploying/openstack/using_swift_blobstore.html

When used keystone v2, I am able to start my apps on DEA which is good.
However when using keystone V3, I am not able to start my apps. The error I
am getting is:



“FAILED

Server error, status code: 400, error code: 170001, message: Staging
error: failed to stage application:

Error downloading: HTTP status: 401”



Tried to debug by adding some ‘puts’ statements in openstack/core.rb
file and it looks like tokens are being generated successfully so there is
no problem with the authentication. The generated response to auth request
shows that the user has “ResellerAdmin” role as well.



When I look into runner_z1/0 /var/vcap/data/dea_next/tmp/
app-package-download.tgz2016*, I find error saying: “401 Unauthorized:
Temp URL invalid xxxxx”



/var/vcap/sys/log/dea_next/dea_next.log shows some download URLs, and if
I curl those URLs, I get exact same error message. Below are the
fog_connection settings in cloud foundry manifest:



fog_connection: &fog_connection

provider: 'OpenStack'

openstack_username: 'cf-admin2'

openstack_tenant: 'cf2'

openstack_project_name: 'cf2'

openstack_api_key: 'passw0rd'

openstack_auth_url: 'http://<OPENSTACK_IP>:5000/v3/auth/tokens'

openstack_domain_name: 'cf_domain'

openstack_user_domain_name: 'cf_domain'

openstack_temp_url_key: 'b3968d0207b54ece87cccc06515a89d4'





Account has a valid temp_url_key configured. Please see below:

curl -v -X GET
http://SWIFT_IP:SWIFT_PORT/v2/Auth_b34a51e551ec4796a461168c886c734f -H
"X-Auth-Token: TOKEN"

* Hostname was NOT found in DNS cache

* Trying SWIFT_IP...

* Connected to SWIFT_IP (SWIFT_IP) port SWIFT_PORT (#0)

GET /v2/Auth_b34a51e551ec4796a461168c886c734f HTTP/1.1
User-Agent: curl/7.35.0
Host: SWIFT_IP:SWIFT_PORT
Accept: */*
X-Auth-Token: TOKEN
< HTTP/1.1 204 No Content

< Content-Length: 0

< X-Account-Object-Count: 0

< X-Timestamp: 1457918518.21777

< X-Account-Meta-Temp-Url-Key: *b3968d0207b54ece87cccc06515a89d4*

< X-Account-Bytes-Used: 0

< X-Account-Container-Count: 0

< Content-Type: text/plain; charset=utf-8

< Accept-Ranges: bytes

< X-Trans-Id: txfc362c27bdda4355a942a-0056e65d93

< Date: Mon, 14 Mar 2016 06:43:31 GMT

<

* Connection #0 to host SWIFT_IP left intact



Also, I can see that the containers are created on swift, so obviously
it is able to authenticate.

$ openstack container list

+---------------+

| Name |

+---------------+

| cc-buildpacks |

| cc-droplets |

| cc-packages |

| cc-resources |

+---------------+



I would appreciate if someone can help me fixing this issue.



Regards,




*Muhammad Altaf Software Development Engineer Fujitsu Australia Software
Technology Pty Ltd*
14 Rodborough Road, Frenchs Forest NSW 2086, Australia
*T* +61 2 9452 9067 *F* +61 2 9975 2899
Muhammada(a)fast.au.fujitsu.com
fastware.com.au

[image: image001.jpg]
[image: image002.jpg]

Disclaimer

The information in this e-mail is confidential and may contain content
that is subject to copyright and/or is commercial-in-confidence and is
intended only for the use of the above named addressee. If you are not the
intended recipient, you are hereby notified that dissemination, copying or
use of the information is strictly prohibited. If you have received this
e-mail in error, please telephone Fujitsu Australia Software Technology Pty
Ltd on + 61 2 9452 9000 or by reply e-mail to the sender and delete the
document and all copies thereof.

Whereas Fujitsu Australia Software Technology Pty Ltd would not
knowingly transmit a virus within an email communication, it is the
receiver’s responsibility to scan all communication and any files attached
for computer viruses and other defects. Fujitsu Australia Software
Technology Pty Ltd does not accept liability for any loss or damage
(whether direct, indirect, consequential or economic) however caused, and
whether by negligence or otherwise, which may result directly or indirectly
from this communication or any files attached.

If you do not wish to receive commercial and/or marketing email messages
from Fujitsu Australia Software Technology Pty Ltd, please email
unsubscribe(a)fast.au.fujitsu.com


Re: NFS

Amit Kumar Gupta
 

If you push a docker container via cf ((not directly to Diego API) it's
hard coded to run unprivileged.

Set this to true:

https://github.com/cloudfoundry-incubator/nsync/blob/master/recipebuilder/docker_recipe_builder.go#L134

Set the "url" for the Diego release in your manifest to
"file:///PATH-TO-DIEGO-REPO" and the version to "create", this will create,
upload, and use your local release next time you bosh deploy.

Cheers,
Amit

On Monday, March 21, 2016, Guillaume Berche <bercheg(a)gmail.com> wrote:

Hi Ted,

What's the procedure to enable privileged containers in a CF deployment ?
I could not yet find related properties in diego-release, or
garden-linux-release.

Do I understand correctly from [1] that applications pushed through
buildpack run in privileged containers by default and hence can use FUSE
clients, whereas docker-based CF apps run in non-priviledged containers [2]
?

Thanks in advance,

Guillaume.

[1]
https://github.com/cloudfoundry-incubator/nsync/blob/7902bea3fb2b028e05dfdcfd511b8368e14e460f/recipebuilder/buildpack_recipe_builder_test.go#L115
[2]
https://github.com/cloudfoundry-incubator/nsync/blob/5ea94c17eba4be1cd388f9fed57eaf6186932e34/recipebuilder/docker_recipe_builder_test.go#L151


Guillaume.

On Tue, Mar 15, 2016 at 10:29 PM, Ted Young <tyoung(a)pivotal.io
<javascript:_e(%7B%7D,'cvml','tyoung(a)pivotal.io');>> wrote:

Hi Raymond,

It is possible to use FUSE-based clients to connect to remote
filesystems, but only if your Cloud Foundry deployment has enabled
privileged containers.

We are currently working on adding volume management to Cloud Foundry.
NFS and other distributed filesystems will be available as services,
allowing access without the need for privileged containers or FUSE.

Thanks,
Ted

On Tue, Mar 15, 2016 at 1:21 PM, Raymond J Steele <
raymondsteele(a)gmail.com
<javascript:_e(%7B%7D,'cvml','raymondsteele(a)gmail.com');>> wrote:

Can a cloud foundry application make us of Network Filesystem share? If
so, would this scale?

Thanks,

Raymond


Re: NFS

Guillaume Berche
 

Hi Ted,

What's the procedure to enable privileged containers in a CF deployment ? I
could not yet find related properties in diego-release, or
garden-linux-release.

Do I understand correctly from [1] that applications pushed through
buildpack run in privileged containers by default and hence can use FUSE
clients, whereas docker-based CF apps run in non-priviledged containers [2]
?

Thanks in advance,

Guillaume.

[1]
https://github.com/cloudfoundry-incubator/nsync/blob/7902bea3fb2b028e05dfdcfd511b8368e14e460f/recipebuilder/buildpack_recipe_builder_test.go#L115
[2]
https://github.com/cloudfoundry-incubator/nsync/blob/5ea94c17eba4be1cd388f9fed57eaf6186932e34/recipebuilder/docker_recipe_builder_test.go#L151


Guillaume.

On Tue, Mar 15, 2016 at 10:29 PM, Ted Young <tyoung(a)pivotal.io> wrote:

Hi Raymond,

It is possible to use FUSE-based clients to connect to remote filesystems,
but only if your Cloud Foundry deployment has enabled privileged containers.

We are currently working on adding volume management to Cloud Foundry. NFS
and other distributed filesystems will be available as services, allowing
access without the need for privileged containers or FUSE.

Thanks,
Ted

On Tue, Mar 15, 2016 at 1:21 PM, Raymond J Steele <raymondsteele(a)gmail.com
wrote:
Can a cloud foundry application make us of Network Filesystem share? If
so, would this scale?

Thanks,

Raymond


Re: Database implementation as a cloud foundry app

Daniel Mikusa
 

On Mon, Mar 21, 2016 at 8:49 AM, Sundarajan Srinivasan <
sundarajan.s(a)gmail.com> wrote:

Thanks Dan.

What would be the advantage of deploying and maintaining database via bosh
and then normal method ?
Off the top of my head...

- you might be able to use an existing release, which would make the
amount of work to setup the database low
- you get all the advantages of bosh
http://bosh.io/docs/about.html
http://bosh.io/docs/problems.html

Other's maybe able to comment more.

Dan



Suggestions are appreciated!


Re: Does Diego support memory swap?

Sam Dai
 

And after I ssh to app container using command "cf ssh app", then execute command "cat /proc/meminfo", show the following information:
SwapTotal: 1048572 kB
SwapFree: 13180 kB
According to this information, memory swap works in diego, but where do I configure the value of SwapTotal?


Re: Database implementation as a cloud foundry app

Sundarajan Srinivasan
 

Thanks Dan.

What would be the advantage of deploying and maintaining database via bosh and then normal method ?

Suggestions are appreciated!


Does Diego support memory swap?

Sam Dai
 

Hi all,
I just saw this page
https://lists.cloudfoundry.org/archives/list/cf-dev(a)lists.cloudfoundry.org/thread/QUPLENMHRESTGAIQFTG6MXRU7V6YZ4SA/#U6QUJFZEXDKLM5PMVPZRQQN4YUXIKAOF,
it looks like when memory usage exceeds the limit, the kernel of diego
won't swap out any pages to avoid the oom killer. But when I executed the
command "bosh vms --vitals", found the value of Swap Usage for cell_z1/0 is
"100% (1021.5M)", It looks like there is memory swap in diego cell, so
want to confirm if there is memory swap in deigo cell?

Thanks,
Sam


Re: Database implementation as a cloud foundry app

Daniel Mikusa
 

On Sun, Mar 20, 2016 at 11:36 PM, Sundarajan Srinivasan <
sundarajan.s(a)gmail.com> wrote:

Dear People,

We have plans to host our application layer (node js) in the cloud
foundry as an app. I have a great doubt on the database implementation part
in cloud foundry.
If you don't want to use a service that you acquire through a service
broker & CF's marketplace, you can host your database somewhere else.
There's nothing that says your database and app must live in CF. The
easiest way to use an external service is to create a user provided
service. This contains the information to your service and works just like
a service you acquire through a service broker.



It looks like the database are usually kept outside of Cloud foundry and
consumed via the service broker.

Yes.


If this is the case they how come the scale in and scale out happens to
database.
At the moment, scaling the database is up to the database provider (i.e.
whomever runs the service & service broker). The service broker is just an
interface so that CF knows how to provision services automatically.
Everything else (running, managing, scaling) the service happens outside
and is the responsibility of the service provider, not CF.



Is there a way to push a database as an app into CF ?
Not at the moment. I believe there are some recent threads on this list
about this topic.



And I saw that each app has been restricted to a size of 2GB max and local
storage of an app is not persistent. Having said I am confused that
implementing a database as an app is not a correct architecture.
You're right the default max disk size (i.e. cf push -k) is 2GB. The local
file system is also ephemeral, meaning you should never write anything
important there because it will go away after the app is restarted /
restaged.



I came to know that the memory (RAM) can be increase to an organization
using the quota space. How to increase the storage size of an app ?
If you're an administrator, you can change the limit.

https://github.com/cloudfoundry/capi-release/blob/master/jobs/cloud_controller_ng/spec#L432-L437

Dan


Re: Reg the upgrade from cf-205 to cf-231

Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM@Cisco) <ngnanase at cisco.com...>
 

Thank you Gwenn and Amit
The fix works.

Regards
Nitiyasri

From: Gwenn Etourneau [mailto:getourneau(a)pivotal.io]
Sent: Saturday, March 19, 2016 4:38 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org>
Cc: Amit Gupta <agupta(a)pivotal.io>; Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com>
Subject: Re: [cf-dev] Re: Reg the upgrade from cf-205 to cf-231

Hi,

What is the value of uaa.require_https in your manifest ? By default is true, try to put to false


Thanks

On Sat, Mar 19, 2016 at 6:05 AM, Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>> wrote:
Hi Amit,

Thanks a lot for your support as always!

Please see the detailed logs you are looking for:-


root(a)testinceptionjk:/opt/cisco/vms-installer/tenant-testinceptionjk/cf-deploy# cf login
API endpoint: https://api.testinceptionjk.cisco.com<https://api.testinceptionjk.cisco.com/>

REQUEST: [2016-03-18T16:30:28Z]
GET /v2/info HTTP/1.1
Host: api.testinceptionjk.cisco.com<http://api.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 632
Content-Type: application/json;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Server: nginx
X-Content-Type-Options: nosniff
X-Vcap-Request-Id: 1cffe445-b169-426f-61fe-f421654bf997
X-Vcap-Request-Id: a4da6848-66c7-4375-6509-3688b69232a2::fbaf3999-67d2-4fd4-b35e-c02c2af15281

{"name":"","build":"","support":"http://support.cloudfoundry.com","version":0,"description":"","authorization_endpoint":"http://uaa.testinceptionjk.cisco.com","token_endpoint":"http://uaa.testinceptionjk.cisco.com","min_cli_version":null,"min_recommended_cli_version":null,"api_version":"2.51.0","app_ssh_endpoint":"ssh.testinceptionjk.cisco.com:2222","app_ssh_host_key_fingerprint":null,"app_ssh_oauth_client":"ssh-proxy","routing_endpoint":"https://api.testinceptionjk.cisco.com/routing","logging_endpoint":"wss://loggregator.testinceptionjk.cisco.com:80","doppler_logging_endpoint":"wss://doppler.testinceptionjk.cisco.com:4443"}

REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Content-Type: application/json
User-Agent: go-cli 6.12.2-24abed3 / linux



REQUEST: [2016-03-18T16:30:28Z]
GET /login HTTP/0.0
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Referer: http://uaa.testinceptionjk.cisco.com/login
User-Agent: go-cli 6.12.2-24abed3 / linux



RESPONSE: [2016-03-18T16:30:28Z]
HTTP/1.1 200 OK
Content-Length: 487
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Cache-Control: no-store
Content-Language: en-US
Content-Type: application/json;charset=UTF-8
Date: Fri, 18 Mar 2016 16:30:28 GMT
Expires: 0
Pragma: no-cache
Server: Apache-Coyote/1.1
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
X-Vcap-Request-Id: 7a845595-63f4-4c97-5397-52ffca0f2f4b
X-Xss-Protection: 1; mode=block

{"app":{"version":"3.1.0"},"links":{"uaa":"http://uaa.testinceptionjk.cisco.com","passwd":"https://console.testinceptionjk.cisco.com/password_resets/new","login":"http://login.testinceptionjk.cisco.com","register":"https://console.testinceptionjk.cisco.com/register"},"zone_name":"uaa","entityID":"login.testinceptionjk.cisco.com","commit_id":"9b5c13d","idpDefinitions":{},"prompts":{"username":["text","Email"],"password":["password","Password"]},"timestamp":"2016-02-05T14:27:13+0000"}

Email> admin

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:35Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:35Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:35 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: fbe5f151-ae1f-48fa-673d-f002dd3ab04f

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>
Authenticating...

REQUEST: [2016-03-18T16:30:42Z]
POST /oauth/token HTTP/1.1
Host: uaa.testinceptionjk.cisco.com<http://uaa.testinceptionjk.cisco.com>
Accept: application/json
Authorization: [PRIVATE DATA HIDDEN]
Content-Type: application/x-www-form-urlencoded
User-Agent: go-cli 6.12.2-24abed3 / linux

grant_type=password&password=[PRIVATE DATA HIDDEN]&scope=&username=admin

RESPONSE: [2016-03-18T16:30:42Z]
HTTP/1.1 400 Bad Request
Content-Length: 1086
Content-Language: en
Content-Type: text/html;charset=utf-8
Date: Fri, 18 Mar 2016 16:30:42 GMT
Server: Apache-Coyote/1.1
X-Vcap-Request-Id: bfa611f1-46bc-42de-4b81-37e40bab8fe7

<html><head><title>Apache Tomcat/7.0.61 - Error report</title><style><!--H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}HR {color : #525D76;}--></style> </head><body><h1>HTTP Status 400 - {&quot;error&quot;: &quot;request must be over https&quot;}</h1><HR size="1" noshade="noshade"><p><b>type</b> Status report</p><p><b>message</b> <u>{&quot;error&quot;: &quot;request must be over https&quot;}</u></p><p><b>description</b> <u>The request sent by the client was syntactically incorrect.</u></p><HR size="1" noshade="noshade"><h3>Apache Tomcat/7.0.61</h3></body></html>
Server error, status code: 400, error code: , message:

Password>

Thanks
Jayaraj

From: Amit Gupta <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Date: Friday, March 18, 2016 at 11:37 AM
To: "Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)" <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: "Discussions about Cloud Foundry projects and the system overall." <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>, Jayarajan Ramapurath Kozhummal <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>

Subject: Re: Reg the upgrade from cf-205 to cf-231

Can you do:

CF_TRACE=true cf login

so we can get more info about where that 400 response code is coming from.

Best,
Amit

On Fri, Mar 18, 2016 at 5:49 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

Bosh deployment has completed successfully. I could set the endpoint, but I could not login to it with the credentials I have given in the properties. Logs and properties below.

root(a)testdeploy:/deploy# cf login
API endpoint: https://api.testdeploy.cisco.com

Email> admin

Password>
Authenticating...
Server error, status code: 400, error code: , message:

Password>
Authenticating...
Server error, status code: 400, error code: , message:


PROPERTIES::

scim:
# external_groups: null
# groups: null
userids_enabled: true
users:
- admin|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin,uaa.admin,password.write
- services|<%= $common_password %>|scim.write,scim.read,openid,cloud_controller.admin
#spring_profiles: null

Regards
Nithiyasri

From: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco)
Sent: Friday, March 18, 2016 7:23 AM
To: 'Amit Gupta' <agupta(a)pivotal.io<mailto:agupta(a)pivotal.io>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: RE: Reg the upgrade from cf-205 to cf-231

Hi Amit

Thanks for your quick reply. Pls let me know in which Vm , should I login to see the compilation logs..

Previously when I did the upgrade, it dint compile the individual packages. Logs below.
Kindly let me know why is it trying to compile individual package now.

---------------------------------------------------------------------------------------
Started preparing package compilation > Finding packages to compile. Done (00:00:00)

Started preparing dns > Binding DNS. Done (00:00:00)



Regards
Nithiyasri

From: Amit Gupta [mailto:agupta(a)pivotal.io]
Sent: Friday, March 18, 2016 5:36 AM
To: Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>>
Cc: Discussions about Cloud Foundry projects and the system overall. <cf-dev(a)lists.cloudfoundry.org<mailto:cf-dev(a)lists.cloudfoundry.org>>; Jayarajan Ramapurath Kozhummal (jayark) <jayark(a)cisco.com<mailto:jayark(a)cisco.com>>
Subject: Re: Reg the upgrade from cf-205 to cf-231

I'm not sure why it's taking >40 mins to compile some simple go binaries. You may have network issues (compilation jobs taking a long time to download dependencies from BOSH director blobstore, or upload compiled resulting artifacts) or you may need more CPU on your compilation machines. You can try to SSH into the compilation VMs while they're running to see what they're doing over those 40 minutes.

On Thu, Mar 17, 2016 at 7:06 AM, Nithiyasri Gnanasekaran -X (ngnanase - TECH MAHINDRA LIM at Cisco) <ngnanase(a)cisco.com<mailto:ngnanase(a)cisco.com>> wrote:
Hi Amit

I was able to do an upgrade of deployment from cf-205 to cf-231 multiple times.
But now, I am getting timeout errors while compiling buildpacks once in rootfs or in buildpack_java or in nginx..
Could you pls help us resolve this error..

Following is the one:

Done compiling packages > buildpack_java/d65c2d20fc067c9995c18d195e0ff117ea9202c0 (00:24:23)
Done compiling packages > rtr/2d7de4f6fc25938c21c5be87174f95583feb14b5 (00:38:22)
Failed compiling packages > rootfs_cflinuxfs2/ac0ba35f1106af81cb735eb56360c6cc924af83a: Timed out waiting for Server `3c04cecc-1308-4da f-8dc5-b9c1924004c3' to be active (00:41:23)
Failed compiling packages > nginx/bf3af6163e13887aacd230bbbc5eff90213ac6af: Timed out waiting for Server `fbbb8647-1415-46d9-92de-d030f 4164b6b' to be active (00:43:31)



Failed compiling packages > cli/b61b75716312df9f4f7c81a17f3a7de456efce71: Timed out waiting for Server `223ec673-b66d-4362-8e27-0859805 2ebe5' to be active (00:44:49)

Error 100: Timed out waiting for Server `3c04cecc-1308-4daf-8dc5-b9c1924004c3' to be active


Regards
Nithiyasri


Re: cf marketplace: no services available

Giovanni Napoli
 

Hi,

thank you for your answer. I have another question: could i deploy more than one release using bosh? I don't understand if i can deploy only one release or n releases without changing my cf-232.dev deployment. Thank you, and sorry the stupid question.


Re: cf marketplace: no services available

sridhar vennela
 

Hi,

The PostgreSQL job is used by other jobs like CloudController, UAA, and other jobs. If you want to use services in the marketplace, You need to do bosh deploy for that particular service. Please follow below links to deploy MySQL services to the marketplace.

https://blog.starkandwayne.com/2014/07/02/adding-mysql-service-to-your-trycf-cloud-foundry/
https://github.com/cloudfoundry/cf-mysql-release

Hope that helps.


Database implementation as a cloud foundry app

Sundarajan Srinivasan
 

Dear People,

We have plans to host our application layer (node js) in the cloud foundry as an app. I have a great doubt on the database implementation part in cloud foundry.

It looks like the database are usually kept outside of Cloud foundry and consumed via the service broker. If this is the case they how come the scale in and scale out happens to database.

Is there a way to push a database as an app into CF ?

And I saw that each app has been restricted to a size of 2GB max and local storage of an app is not persistent. Having said I am confused that implementing a database as an app is not a correct architecture.

I came to know that the memory (RAM) can be increase to an organization using the quota space. How to increase the storage size of an app ?
Could you please clarify the queries?

Thanks
Sundar


Re: How to minimize VMs used in cf/diego

Benjamin Gandon
 

When I read "decrease the VM size" I guess you might be using BOSH-lite.
Then you could be interested in switching to microPCF which has a smaller memory footprint.

/Benjamin

Le 17 mars 2016 à 04:33, Stanley Shen <meteorping(a)gmail.com> a écrit :

Hello, all

By default, there are about 20 VMs will be used in cf/diego installation.
I am trying to minimize the VM size.

I tried to follow https://github.com/cloudfoundry-community/cf-boshworkspace but got some problem.
I create an issue for it but got no response, is this still maintained?

If there are any other documentation about it, or any experience on it?


cf marketplace: no services available

Giovanni Napoli
 

Hi all, i've deployed Cloud Foundry v232 using BOSH-Lite on a local machine, but when i type:

cf marketplace

there are no services available. But in the VMs, for istance, ther's the "postgresql" job with its ip.
How can be possible? Thank you.


Re: Connection refused - api.10.244.0.22.xip.io:443

Wayne Ha <wayne.h.ha@...>
 

Amit,

You are right, if I use the default bosh-lite-v231.yml which uses api.bosh-lite.com then the cf domains command works.

But now I am adding the changes for v231 into boshlite-devbox.yml based on v226 which uses api.10.244.0.22.xip.io then the cf domains command fails.

Can I continue using api.10.244.0.22.xip.io?

Thanks,

5141 - 5160 of 9421