Date   

Reg cant find template : metron_agent

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

Hi

I am working on cloud foundry and I could create a development bosh release of cloud foundry using the following source:
git clone https://github.com/cloudfoundry/cf-release.git (added some rules in haproxy.conf file)

When I tried to deploy with the dev release of cloud-foundry, I get the following error:

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done (00:00:00)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Failed: Can't find template `metron_agent' (00:00:00)

Error 190012: Can't find template `metron_agent'

Kindly help me figure out the issue of the error, as this is a show-stopper for us..

Regards
Nithiaysri


Re: Is there any mechanism for restoring the Cloud Foundry state with Diego after rebooting the machine

Nanduni Nimalsiri
 

Hi Hristo,

Thank you so much for the information. Where should I use this command? Is it at workspace/cf-release and workspace/diego-release and then enable Docker support in Cloud Foundry?

Best regards,
Nanduni.


Re: Is there any mechanism for restoring the Cloud Foundry state with Diego after rebooting the machine

Gwenn Etourneau
 

Btw, if you are just looking to use CF and Diego you can use microPCF

https://github.com/pivotal-cf/micropcf

On Tue, Feb 16, 2016 at 3:24 PM, Hristo Iliev <hsiliev(a)gmail.com> wrote:

Hi,

You can use bosh cloudcheck command to restore the VM state. That saves
you the time-consuming part of build/upload/deploy cycle, since it will
just restore the processes on the containers/VMs.

If you need more help with bosh, cf-bosh list is the right place to ask.

HTH
Hristo Iliev

2016-02-16 6:57 GMT+02:00 Nanduni Nimalsiri <nandunibw(a)gmail.com>:

I have successfully deployed Diego in BOSH-Lite. But this process takes
me a long time, nearly an hour. So whenever I shut down and restart my
machine, I have to follow this process again and again. This wastes lots of
time to enable Docker support in Diego. Sometimes I have to rerun the steps
several times when I get errors.
Starting the Bosh-Lite director does not take a long time, so keeping
that Bosh-Lite director VM in suspended/paused state does not help me a lot.
Deploying the Diego release and CF release takes me a lot of time. I want
to know if there is any mechanism to start this process quickly when I
restart my machine. Is there any mechanism to restore the states after
rebooting the machine. Please help.

Best regards,
Nanduni


Re: Is there any mechanism for restoring the Cloud Foundry state with Diego after rebooting the machine

Hristo Iliev
 

Hi,

You can use bosh cloudcheck command to restore the VM state. That saves you
the time-consuming part of build/upload/deploy cycle, since it will just
restore the processes on the containers/VMs.

If you need more help with bosh, cf-bosh list is the right place to ask.

HTH
Hristo Iliev

2016-02-16 6:57 GMT+02:00 Nanduni Nimalsiri <nandunibw(a)gmail.com>:

I have successfully deployed Diego in BOSH-Lite. But this process takes me
a long time, nearly an hour. So whenever I shut down and restart my
machine, I have to follow this process again and again. This wastes lots of
time to enable Docker support in Diego. Sometimes I have to rerun the steps
several times when I get errors.
Starting the Bosh-Lite director does not take a long time, so keeping that
Bosh-Lite director VM in suspended/paused state does not help me a lot.
Deploying the Diego release and CF release takes me a lot of time. I want
to know if there is any mechanism to start this process quickly when I
restart my machine. Is there any mechanism to restore the states after
rebooting the machine. Please help.

Best regards,
Nanduni


Is there any mechanism for restoring the Cloud Foundry state with Diego after rebooting the machine

Nanduni Nimalsiri
 

I have successfully deployed Diego in BOSH-Lite. But this process takes me a long time, nearly an hour. So whenever I shut down and restart my machine, I have to follow this process again and again. This wastes lots of time to enable Docker support in Diego. Sometimes I have to rerun the steps several times when I get errors.
Starting the Bosh-Lite director does not take a long time, so keeping that Bosh-Lite director VM in suspended/paused state does not help me a lot.
Deploying the Diego release and CF release takes me a lot of time. I want to know if there is any mechanism to start this process quickly when I restart my machine. Is there any mechanism to restore the states after rebooting the machine. Please help.

Best regards,
Nanduni


database migration

Jeff Weber <jweber@...>
 

I've got a monolithic CF deployment that has become quite a burden to
upgraded because of it's all releases in one manifest nature. I'm currently
working on a plan to cleanup and disaggregate and the first step is to
migrate my core database into its own separate deployment.

After putting my plan together I wanted to confirm it's as simple as it
seems:

1) Deploy new database cluster
2) Stop CF services
3) Perform backup of databases on old cluster
4) Restore backups to new cluster
5) Reconfigure manifest to point to new database cluster
6) Redeploy / Start CF services with new manifest
7) Validate
8) Remove old database instance from the manifest

Is there anything outside of these basic steps to watch out for as gotchas
or should this be a straight forward set of tasks?


Scaling Down etcd

Suren R
 

Hi Cloud Foundry!
We are trying to split the cloud foundry deployment in to multiple
deployments. Each CF component will have its own deployment manifest.
We are doing this activity in an existing CF. We moved all components
except nats and etcd, into the new deployments. The original single
deployment is now having just these two jobs.

Of which, existing deployment is having 3 etcd machines. The migration idea
is to bring 4 new etcd machines in the cluster through new deployment.
Point all other components to these four etcd machines and delete the
existing 3 nodes.

However, if we delete the existing 3 nodes and do an update to form a 4
node cluster, the cluster breaks and as a result all running apps are going
down. (Because the canary job brings one node down for the update, as a
result tolerance is breached.)

We also tried to remove these three nodes from the cluster using etcdctl
command and tried to update deletion to the new deployment through bosh.
This also makes the bosh deployment to fail (etcd job is failing saying
"unequal number of nodes").

In this situation, what would be the best way to reduce the nodes in the
etcd cluster?

regards,
Surendhar


Re: Downloading Buildpack Bits from Cloud Foundry

Matthew Sykes <matthew.sykes@...>
 

Try these:

https://github.com/cloudfoundry/cf-release/blob/master/jobs/cloud_controller_ng/spec#L220-L225



On Mon, Feb 15, 2016 at 6:44 AM, Rafal Radecki <radecki.rafal(a)gmail.com>
wrote:

Hi.

I tried both solutions and have some questions:
1) when I invoke on the host with cc mentioned wget I get:
===
# wget --server-response --http-user=user --http-password=pass
http://127.0.0.1:9022/v2/buildpacks/03ab7576-a181-4c46-9a0a-c4d61d262c2e/download
--2016-02-15 11:42:06--
http://127.0.0.1:9022/v2/buildpacks/03ab7576-a181-4c46-9a0a-c4d61d262c2e/download
Connecting to 127.0.0.1:9022... connected.
HTTP request sent, awaiting response...
HTTP/1.1 401 Unauthorized
Server: nginx
Date: Mon, 15 Feb 2016 11:42:06 GMT
Content-Type: application/json;charset=utf-8
Content-Length: 100
Connection: keep-alive
Keep-Alive: timeout=20
X-VCAP-Request-ID: 48256908-2be7-472c-8606-84e110a754d8
X-Content-Type-Options: nosniff
Unknown authentication scheme.

Username/Password Authentication Failed.
===

What user/password should be used? I tried admin user and all other
options from my deployment manifest with no luck.

2) I found mentioned identifier of the buildpack in ccdb in table
buildpacks as guid_hash but what to do with this next? How to download the
blob?

BR,
Rafal.


--
Matthew Sykes
matthew.sykes(a)gmail.com


Binding an App to the controller hostname

Tim Lawrence
 

Hi all,

We have been testing one of our CF deployments and have found that we can deploy an app bound to the "api" hostname. eg "api.domain.com".
It appears that the router then forwards traffic to this app rather than the CF API. Clearly this is a fairly big problem for us.
This deployment is not currently completely up to date so wondered if anyone else has seen this and if it has patched this in a subsequent release?


Re: Downloading Buildpack Bits from Cloud Foundry

Rafal Radecki
 

Hi.

I tried both solutions and have some questions:
1) when I invoke on the host with cc mentioned wget I get:
===
# wget --server-response --http-user=user --http-password=pass http://127.0.0.1:9022/v2/buildpacks/03ab7576-a181-4c46-9a0a-c4d61d262c2e/download
--2016-02-15 11:42:06-- http://127.0.0.1:9022/v2/buildpacks/03ab7576-a181-4c46-9a0a-c4d61d262c2e/download
Connecting to 127.0.0.1:9022... connected.
HTTP request sent, awaiting response...
HTTP/1.1 401 Unauthorized
Server: nginx
Date: Mon, 15 Feb 2016 11:42:06 GMT
Content-Type: application/json;charset=utf-8
Content-Length: 100
Connection: keep-alive
Keep-Alive: timeout=20
X-VCAP-Request-ID: 48256908-2be7-472c-8606-84e110a754d8
X-Content-Type-Options: nosniff
Unknown authentication scheme.

Username/Password Authentication Failed.
===

What user/password should be used? I tried admin user and all other options from my deployment manifest with no luck.

2) I found mentioned identifier of the buildpack in ccdb in table buildpacks as guid_hash but what to do with this next? How to download the blob?

BR,
Rafal.


Support for multiple externalId in UAA

Paul Bakare
 

Hi,

Seems SCIM does not support multiple externalId for a User resource.

How can one achieve this in UAA? Does this feature exist in UAA or would it
be catered for in
the future?

Many thanks


Increase CAB meeting to 1.5 or 2 hours?

Dr Nic Williams
 

Since we started the CAB calls in late 2013 the size of Cloud Foundry
community, the number of engineering teams, and the number of code bases
(both core & community) has grown.

There was a time when community projects might get to be introduced once
during a CAB meeting; and shared discussion of what was going on amongst
the community.

Recently, due to the hard limit of 1 hour - there is only just time for
core team projects to discuss their status.

With increased number of CF office locations, the tread will continue to
create more teams, which in turn will create more repositories & tracker
roadmaps, and will create more demand on the limited CAB call time slot.

I like the name "Community Advisory Board meeting". It seems like a good
goal for the meeting.

Could we increase the CAB meeting to 1.5 or 2 hours?

Or could the summaries by PMs be delivered before the meeting (I have the
feeling many of them are organized and have notes that they are reading).
This might give us more time to discuss the projects, and discuss
non-core/community projects and ambitions.

It might also allow time for the community to chat with itself and bond as
a community.

with valentine's love
Dr Nic


--
Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
http://drnicwilliams.com
http://starkandwayne.com
cell +1 (415) 860-2185
twitter @drnic


Re: Deploying Diego to BOSH-Lite

Eric Malm <emalm@...>
 

Hi, Nanduni,

If the other Docker images you are pushing don't declare ports to expose,
or the processes they run don't listen for TCP connections on the ports
they expose, then they will fail the default 'port' health check when
pushed as a CF app. If you turn that port-based health-check off by
changing it to 'none', though, the image may run successfully. For example,
I was able to get the busybox image to start as a CF app by running `cf
push busybox -o busybox -u none`. I did encounter a problem with the
'hello-world' image, as it appeared not to start the '/hello' command
correctly in garden-linux, and I've filed a bug in the Garden team's
tracker about it at https://www.pivotaltracker.com/story/show/113694139.
Someone from that team may be able to provide more insight into why that
image doesn't execute correctly, or whether it's too minimal to be
supported.

Thanks,
Eric

On Sat, Feb 13, 2016 at 4:47 PM, Nanduni Nimalsiri <nandunibw(a)gmail.com>
wrote:

Hi Eric,

Thank you very much. I could deploy Diego in Bosh-Lite with the versions
you have mentioned. Thank you again for your very clear instructions.

I came up with another issue. It seems that only cloudfoundry/lattice-app
docker image works for me. When I push any other image from Docker Hub, the
application fails to start ( 0 of 1 instances running, 1 starting ..... 0
of 1 instances running, 1 crashed).

I tried with several images. eg: busybox, hello-world etc. I can't find
any reason. Can you please help me?

Best Regards,
Nanduni



Re: Deploying Diego to BOSH-Lite

Nanduni Nimalsiri
 

Hi Eric,

Thank you very much. I could deploy Diego in Bosh-Lite with the versions you have mentioned. Thank you again for your very clear instructions.

I came up with another issue. It seems that only cloudfoundry/lattice-app docker image works for me. When I push any other image from Docker Hub, the application fails to start ( 0 of 1 instances running, 1 starting ..... 0 of 1 instances running, 1 crashed).

I tried with several images. eg: busybox, hello-world etc. I can't find any reason. Can you please help me?

Best Regards,
Nanduni


Re: Future of CAB calls - short survey

Michael Maximilien
 

Quick update:

We have 30 submitted responses to survey and 5 who have started but not completed. This is close to normal average participants in CAB lately but I am sure we still could get many more responses. Please take a 5 minutes to complete: https://goo.gl/83F726

Finally, at the last CAB call (Feb) we had 28 totals participants: 1 (Canada) + 2 (UK) + 2 (Germany) + 2 (Switzerland) + 21 (USA)

Of course that does not count places, like the conference room at Pivotal, where we had 8 participants but one caller (me).

Anyhow, I'll submit results to survey on Th and close it Wed night. If you have not already, take a minute to complete.

Thanks for your time. Best,

dr.max
ibm cloud labs
sillicon valley, ca

Sent from my iPhone

On Feb 10, 2016, at 12:22 PM, Michael Maximilien <maxim(a)us.ibm.com> wrote:

Hi, all,

Based on recent low attendance and engagement, it's time we perhaps tweak the call.

After briefly discussing with Colin, Chip, Sam, Chris, Stormy, and a few others, here is a short anonymous survey (5 minutes max) that I'd encourage you to take to help shape the future of the CAB call.

https://goo.gl/83F726

I'll leave this open for one week. I'll send a reminder end of this week with an idea of how many responses we have and again next week before closing it on Wednesday 17th @ midnight.

I'll share the results soon after and hopefully we can use the feedback to improve where we go from here.

All the best,

dr.max
ibm cloud labs
sillicon valley, ca

Sent from my iPhone


Re: Error dialing loggregator server: unexpected EOF

Rohit Kumar
 

Hi Ramon,

Can you confirm if your installation has the 4443 port open for
loggregator? One quick way of finding out would be to issue a curl to the
traffic controller. Can you run the following command and tell us what you
see?

curl -kv https://loggregator.cf.dev.eden.klm.com:4443

If you can reach the traffic controller, you will get a 404 response.

Rohit

On Fri, Feb 12, 2016 at 4:24 AM, Ramon Makkelie <ramon.makkelie(a)klm.com>
wrote:

i just created a new cloudfoundry deployment for testing purposes
and i can push a application but the the following error

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration
(loggregator endpoint is wss://loggregator.cf.dev.eden.klm.com:4443).

cf logs trace http://pastebin.com/KkpAJ8x0

doppler/loggeragor logs http://pastebin.com/c8giCvua

deployment manifest http://pastebin.com/XQMfWqDJ

can maby someone point me in the right direction?
i think im missing something


Re: How to upgrade ruby version in application container to 2.2.0

Noburou TANIGUCHI
 

I think this thread

http://cf-dev.70369.x6.nabble.com/cf-dev-How-to-use-new-cf-ssh-with-Rails-apps-tp3497.html

may help.


Sam Dai wrote
I deployed a java application app1 to diego, then I ssh to the application
container using command " cf ssh app1", when I execute command "ruby -v"
in
this application container, the value is shown as below:

ruby 1.9.3p547 (2014-05-14 revision 45962) [x86_64-linux]

Because I also have some ruby script in my java application app1 and want
to use ruby 2.2.0, want to know how to upgrade ruby version in application
container to 2.2.0?

In my machine, the CF version is V227, Diego version is v.0.1445.0. Bosh
stemcell is bosh-stemcell-3147-warden-boshlite-ubuntu-trusty-go_agent.tgz

Thanks,

Sam




-----
I'm not a ...
noburou taniguchi
--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-How-to-upgrade-ruby-version-in-application-container-to-2-2-0-tp3745p3748.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: How to upgrade ruby version in application container to 2.2.0

Daniel Mikusa
 

On Fri, Feb 12, 2016 at 5:42 AM, Sam Dai <sam.dai(a)servicemax.com> wrote:

I deployed a java application app1 to diego, then I ssh to the application
container using command " cf ssh app1", when I execute command "ruby -v" in
this application container, the value is shown as below:

ruby 1.9.3p547 (2014-05-14 revision 45962) [x86_64-linux]
This is the version of ruby that comes with the cflinuxfs2 (i.e. Ubuntu
Trusty) stack. You can't upgrade it, but you can install a newer version
next to it.

Because I also have some ruby script in my java application app1 and want
to use ruby 2.2.0, want to know how to upgrade ruby version in application
container to 2.2.0?
You might look at the multi-buildpack. It would let you run both the Java
and Ruby build packs and then you'd end up with both installed.

https://github.com/ddollar/heroku-buildpack-multi

Dan



In my machine, the CF version is V227, Diego version is v.0.1445.0. Bosh
stemcell is bosh-stemcell-3147-warden-boshlite-ubuntu-trusty-go_agent.tgz

Thanks,

Sam




Error dialing loggregator server: unexpected EOF

ramonskie
 

i just created a new cloudfoundry deployment for testing purposes
and i can push a application but the the following error

Warning: error tailing logs
Error dialing loggregator server: unexpected EOF.
Please ask your Cloud Foundry Operator to check the platform configuration (loggregator endpoint is wss://loggregator.cf.dev.eden.klm.com:4443).

cf logs trace http://pastebin.com/KkpAJ8x0

doppler/loggeragor logs http://pastebin.com/c8giCvua

deployment manifest http://pastebin.com/XQMfWqDJ

can maby someone point me in the right direction?
i think im missing something


How to upgrade ruby version in application container to 2.2.0

Sam Dai
 

I deployed a java application app1 to diego, then I ssh to the application
container using command " cf ssh app1", when I execute command "ruby -v" in
this application container, the value is shown as below:

ruby 1.9.3p547 (2014-05-14 revision 45962) [x86_64-linux]

Because I also have some ruby script in my java application app1 and want
to use ruby 2.2.0, want to know how to upgrade ruby version in application
container to 2.2.0?

In my machine, the CF version is V227, Diego version is v.0.1445.0. Bosh
stemcell is bosh-stemcell-3147-warden-boshlite-ubuntu-trusty-go_agent.tgz

Thanks,

Sam

5561 - 5580 of 9330