Date   

Re: Did anybody deploy a wiki as app to CF?

James Bayer
 

this shows how to use drupal which is a cms with wiki functions
http://blog.pivotal.io/pivotal-cloud-foundry/products/how-to-deploy-drupal-to-pivotal-cf-within-seconds

if you're in a private deployment, the services shown for drupal are both
available as oss and listed on bosh.io.

mediawiki is a php app with mysql as an option:
https://www.mediawiki.org

but i'm not aware of install instructions for that. there are other options
here: https://en.wikipedia.org/wiki/List_of_wiki_software

On Fri, Jul 10, 2015 at 3:09 PM, jtuchscherer(a)pivotal.io <
jtuchscherer(a)pivotal.io> wrote:

Hi Stephan,

I managed to get an instiki(instiki.org) instance up and running on PWS. I
had to change a few things to get it to work and even with those changes,
it
isn't great yet. For example, uploaded files are stored locally in the
Warden container. Therefore, they get lost when the app is restarted. But
it
wouldn't be to hard to change the code to use an S3 bucket as a storage
solution, I just didn't bother yet.

I will clean up my local changes and document them, then I'll push them up
to github.

P.S.: I also looked for some other open source wiki engines. I didn't find
a
single one that could be deployed to CF (or any other PaaS) without major
changes.



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-Did-anybody-deploy-a-wiki-as-app-to-CF-tp643p680.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer


Re: 3 etcd nodes don't work well in single zone

Tony
 

Hi James,

Thank you for reply.

I think I didn't describe it clearly. Sorry about that.

The CentOS 6.5 is the OS underlying our OpenStack.

And we are using Ubuntu Trusty stemcell.
(bosh-openstack-kvm-ubuntu-trusty-go_agent)

Regards,
Tony



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p760.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: 3 etcd nodes don't work well in single zone

James Bayer
 

cf project does not support or test cf-release with centos6.5, only ubuntu
14.04.

etcd nodes should not necessarily be aware of which AZs they are in. the
only difference might be in the bosh manifests if they are in different
zones they likely have different job names and you'd need to ensure that
despite the different job names that they were configured to find each
other correctly.

On Thu, Jul 16, 2015 at 6:51 PM, Tony <Tonyl(a)fast.au.fujitsu.com> wrote:

Hi Amit,

Let me explain the error I got in details.

My env info:
CentOS 6.5,
Openstack Icehouse,
Single-AZ
2 hm9000 instances,
3 etcd instances,


Manifest:
- name: etcd_z1
instances: 3
networks:
- name: cf1
static_ips:
- 100.64.1.21
- 100.64.1.22
- 100.64.1.23
persistent_disk: 10024
properties:
metron_agent:
deployment: metron_agent.deployment
zone: z1
networks:
apps: cf1
etcd:
election_timeout_in_milliseconds: 1000
heartbeat_interval_in_milliseconds: 50
log_sync_timeout_in_seconds: 30
resource_pool: medium_z1
templates:
- name: etcd
release: cf
- name: etcd_metrics_server
release: cf
- name: metron_agent
release: cf
update: {}

properties:
etcd:
machines:
- 100.64.1.21
- 100.64.1.22
- 100.64.1.23
etcd_metrics_server:
nats:
machines:
- 100.64.1.11
- 100.64.1.12
...


I cf push dora app with 2 instances
(
https://github.com/cloudfoundry/cf-acceptance-tests/tree/master/assets/dora
)

And I can always get response from it. (curl dora.runmyapp.io --> "Hi,
I'm
Dora")
The app runs well.

Then I "cf app dora" and got
...
requested state: started
instances: ?/2
...

Then I "cf app dora" again after about 1 minute, and got
...
requested state: started
instances: 2/2
...

The instances' number varies between ?/2 and 2/2 after that.

I also wrote a small script to send "cf app dora" every second and check
the
instances' number.
if the number changed, then record it.

Wed Jul 15 06:50:57 UTC 2015 instances: ?/2 (32s)

Wed Jul 15 06:51:29 UTC 2015 instances: 2/2 (6s)

Wed Jul 15 06:51:35 UTC 2015 instances: ?/2 (1m30s)

Wed Jul 15 06:53:05 UTC 2015 instances: 2/2 (17s)

Wed Jul 15 06:53:22 UTC 2015 instances: ?/2 (3m40s)

Wed Jul 15 06:57:02 UTC 2015 instances: 2/2 (21s)

Wed Jul 15 06:57:23 UTC 2015 instances: ?/2 (2m4s)

Wed Jul 15 06:59:27 UTC 2015 instances: 2/2
...


From above we can see that:
1. instance number varies between ?/2 and 2/2
2. "?/2" can be got more often than "2/2"


The app instances' number is always "2/2" when there is only one etcd
instance.
So I reckon the problem is in multi etcd instances.


Other things I tried, but none of them works:

1. Stop etcd service on one etcd vm(monit stop etcd).

2. restart 3 etcd services one by one

3. restart all 3 etcd vms(terminate vms and let them restart
automatically.)

4. Restart two hm9000 vms

5. Restart haproxy(because I don’t know whether the “for HA” means
haproxy)
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210
Upgrade etcd server to 2.0.1 details
Should be run as 1 node (for small deployments) or 3 nodes spread across
zones (for HA)

6. Add these properties according to

http://bosh.io/jobs/etcd?source=github.com/cloudfoundry/cf-release&version=210
election_timeout_in_milliseconds: 1000
heartbeat_interval_in_milliseconds: 50
log_sync_timeout_in_seconds: 30


Anyway, it doesn't work when "- three instances in a one-zone deployment,
will all three instances in the same zone " as you mentioned.

Do you have any suggestion about it? Or is there any mistake in my
manifest?

Thanks,
Tony



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p756.html
Sent from the CF Dev mailing list archive at Nabble.com.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev
--
Thank you,

James Bayer


Re: Introducing OSS Release Integration Team

Amit Kumar Gupta
 

Ah, copy-paste fail! Zak is a Pivotal engineer, not IBM.

On Thu, Jul 16, 2015 at 7:33 PM, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi all,

As some of you may already be aware, the Runtime team has recently been
refactored:

- The "CAPI" team will be responsible for the Cloud Controller and
Services API
- The Routing team will be responsible for work on routing, including the
existing Gorouter component and new work on TCP routing
- The OSS Release Integration team (MEGA) will be primarily responsible
for the integration of all components

There is a little more to that last one, so I'd like to share our mandate
document and open it up to questions, comments, and clarifications. A
rough draft had been previously shared with the community. We have since
gathered feedback and held a team Inception to socialize our goals and
refine our mandate:


https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#

I'd also like to introduce the members of the new OSS Release Integration
team, so our names don't look unfamiliar when we respond to your issues,
pull requests, and mailing list messages.

Joseph Palermo, Technical Lead, Pivotal
Dan Lavine, Software Engineer, IBM
Zak Auerbach, Software Engineer, IBM
Duncan Winn, Solutions Engineer, Pivotal
Amit Gupta, PM, Pivotal

Thanks,
Amit


Introducing OSS Release Integration Team

Amit Kumar Gupta
 

Hi all,

As some of you may already be aware, the Runtime team has recently been
refactored:

- The "CAPI" team will be responsible for the Cloud Controller and Services
API
- The Routing team will be responsible for work on routing, including the
existing Gorouter component and new work on TCP routing
- The OSS Release Integration team (MEGA) will be primarily responsible for
the integration of all components

There is a little more to that last one, so I'd like to share our mandate
document and open it up to questions, comments, and clarifications. A
rough draft had been previously shared with the community. We have since
gathered feedback and held a team Inception to socialize our goals and
refine our mandate:

https://docs.google.com/document/d/1WmA174FR6p2G0WJqUQ336wzWaYWgBEwBtFJz7uKFSdo/edit#

I'd also like to introduce the members of the new OSS Release Integration
team, so our names don't look unfamiliar when we respond to your issues,
pull requests, and mailing list messages.

Joseph Palermo, Technical Lead, Pivotal
Dan Lavine, Software Engineer, IBM
Zak Auerbach, Software Engineer, IBM
Duncan Winn, Solutions Engineer, Pivotal
Amit Gupta, PM, Pivotal

Thanks,
Amit


Re: 3 etcd nodes don't work well in single zone

Tony
 

Hi Amit,

Let me explain the error I got in details.

My env info:
CentOS 6.5,
Openstack Icehouse,
Single-AZ
2 hm9000 instances,
3 etcd instances,


Manifest:
- name: etcd_z1
instances: 3
networks:
- name: cf1
static_ips:
- 100.64.1.21
- 100.64.1.22
- 100.64.1.23
persistent_disk: 10024
properties:
metron_agent:
deployment: metron_agent.deployment
zone: z1
networks:
apps: cf1
etcd:
election_timeout_in_milliseconds: 1000
heartbeat_interval_in_milliseconds: 50
log_sync_timeout_in_seconds: 30
resource_pool: medium_z1
templates:
- name: etcd
release: cf
- name: etcd_metrics_server
release: cf
- name: metron_agent
release: cf
update: {}

properties:
etcd:
machines:
- 100.64.1.21
- 100.64.1.22
- 100.64.1.23
etcd_metrics_server:
nats:
machines:
- 100.64.1.11
- 100.64.1.12
...


I cf push dora app with 2 instances
(https://github.com/cloudfoundry/cf-acceptance-tests/tree/master/assets/dora)

And I can always get response from it. (curl dora.runmyapp.io --> "Hi, I'm
Dora")
The app runs well.

Then I "cf app dora" and got
...
requested state: started
instances: ?/2
...

Then I "cf app dora" again after about 1 minute, and got
...
requested state: started
instances: 2/2
...

The instances' number varies between ?/2 and 2/2 after that.

I also wrote a small script to send "cf app dora" every second and check the
instances' number.
if the number changed, then record it.

Wed Jul 15 06:50:57 UTC 2015 instances: ?/2 (32s)

Wed Jul 15 06:51:29 UTC 2015 instances: 2/2 (6s)

Wed Jul 15 06:51:35 UTC 2015 instances: ?/2 (1m30s)

Wed Jul 15 06:53:05 UTC 2015 instances: 2/2 (17s)

Wed Jul 15 06:53:22 UTC 2015 instances: ?/2 (3m40s)

Wed Jul 15 06:57:02 UTC 2015 instances: 2/2 (21s)

Wed Jul 15 06:57:23 UTC 2015 instances: ?/2 (2m4s)

Wed Jul 15 06:59:27 UTC 2015 instances: 2/2
...


From above we can see that:
1. instance number varies between ?/2 and 2/2
2. "?/2" can be got more often than "2/2"


The app instances' number is always "2/2" when there is only one etcd
instance.
So I reckon the problem is in multi etcd instances.


Other things I tried, but none of them works:

1. Stop etcd service on one etcd vm(monit stop etcd).

2. restart 3 etcd services one by one

3. restart all 3 etcd vms(terminate vms and let them restart
automatically.)

4. Restart two hm9000 vms

5. Restart haproxy(because I don’t know whether the “for HA” means haproxy)
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210
Upgrade etcd server to 2.0.1 details
Should be run as 1 node (for small deployments) or 3 nodes spread across
zones (for HA)

6. Add these properties according to
http://bosh.io/jobs/etcd?source=github.com/cloudfoundry/cf-release&version=210
election_timeout_in_milliseconds: 1000
heartbeat_interval_in_milliseconds: 50
log_sync_timeout_in_seconds: 30


Anyway, it doesn't work when "- three instances in a one-zone deployment,
will all three instances in the same zone " as you mentioned.

Do you have any suggestion about it? Or is there any mistake in my manifest?

Thanks,
Tony



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p756.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: 3 etcd nodes don't work well in single zone

Tony
 

Hi Amit,

Thank you very much for your clear explanation.

I got the release info(I called it "release Note") from CF release 210,
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210

In the "NOTES" part, there is "Upgrade etcd server to 2.0.1" where you can
see
"Should be run as 1 node (for small deployments) or 3 nodes spread across
zones (for HA)"


I will do more test about the third one:
- three instances in a one-zone deployment, will all three instances in the
same zone

Thanks.

Tony




--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p755.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: 3 etcd nodes don't work well in single zone

Amit Kumar Gupta
 

Hi Gwenn,

Can you elaborate? Are you saying you've actually deployed 3 etcd nodes to
1 zone and you're currently experiencing problems? If so, can you give some
details on the problems?

Thanks,
Amit, CF OSS Release Integration PM
Pivotal Software, Inc.



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p754.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: 3 etcd nodes don't work well in single zone

Amit Kumar Gupta
 

Hi Tony,

All options are possible. You can run:

- one instance in a one-zone deployment
- one instance in one zone of a multi-zone deployment
- three instances in a one-zone deployment, will all three instances in the
same zone
- three instances in a multi-zone deployment, spreading out the instances
across zones
- three instances in a multi-zone deployment, where you still cram all
instances into one of the many zones

Running multiple instances improves availability in case one node dies, is
temporarily out of commission, being updated, etc. Multiple instances
incurs a performance cost though, since the data needs to be replicated
across nodes in the etcd cluster.

Running across multiple zones further improves availability and
fault-tolerance, since you're now resilient to even a whole zone (e.g.
hardware cluster) going down. This again incurs an additional performance
penalty, as network traffic between zones often suffers higher latency, as
well as a higher risk for network partitions.

I'm not sure where you found "Should be run as 1 node (but can NOT be run as
3 nodes) in environment with only one zone." I do not see it in the release
notes, but perhaps they were edited after you posted this question.

Best,
Amit, CF OSS Release Integration PM
Pivotal Software, Inc.



--
View this message in context: http://cf-dev.70369.x6.nabble.com/cf-dev-3-etcd-nodes-don-t-work-well-in-single-zone-tp746p753.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: cf push fails (goroutine errors)

James Bayer
 

i believe this could be related to this:
https://github.com/cloudfoundry/cli/issues/509
tracked it this story:
https://www.pivotaltracker.com/story/show/98672332

On Thu, Jul 16, 2015 at 6:42 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:



On 16 July 2015 at 13:06, Alexander Lomov <alexander.lomov(a)altoros.com>
wrote:

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.
You are right, I forget to activate the trace. Here
<https://drive.google.com/open?id=0B8Z5KYzSwwx3TURrbUtfMnNCa2c> is the
log, but I do not really understand the 'goroutine' problem. Do you have
any idea?


- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry
I will try to run the Acceptance Tests.



Best wishes,
Alex L.
Best and thank you,



------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and
the applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
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


--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer


Re: cf push fails (goroutine errors)

Michele Santuari <michele.santuari@...>
 

On 16 July 2015 at 13:06, Alexander Lomov <alexander.lomov(a)altoros.com>
wrote:

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.
You are right, I forget to activate the trace. Here
<https://drive.google.com/open?id=0B8Z5KYzSwwx3TURrbUtfMnNCa2c> is the log,
but I do not really understand the 'goroutine' problem. Do you have any
idea?


- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry
I will try to run the Acceptance Tests.



Best wishes,
Alex L.
Best and thank you,



------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
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


--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.


Re: CF client library

Noburou TANIGUCHI
 

Thank you James, for telling about the ActiveStates' library and proposing to
publish the information about client libraries on docs.cloudfoundry.org.

I think the information on this thread is helpful not only for me but other
Cloud Foundry users / developers. So it seems very good idea to publish and
maintain it on the official site.





--
View this message in context: http://cf-dev.70369.x6.nabble.com/CF-client-library-tp712p750.html
Sent from the CF Dev mailing list archive at Nabble.com.


Re: cf push fails (goroutine errors)

Alexander Lomov <alexander.lomov@...>
 

Looks like your CF CLI client fails to make a connection to CC API. Here
are some points about your case:

- you can run `cf push` with `CF_TRACE=true` environment variable to get
more verbose output: like this `CF_TRACE=true cf push`.

- you can try to run CATs (Cloud Foundry Acceptance Tests) to find out
possible root of the problem. Here is a link to CATs for cf-release v212
[1] and here is folder where you can find a link to it [2]

[1]
https://github.com/cloudfoundry/cf-acceptance-tests/tree/cdced815f585ef4661b2182799d1d6a7119489b0
[2]
https://github.com/cloudfoundry/cf-release/tree/v212/src/github.com/cloudfoundry

Best wishes,
Alex L.

------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Thu, Jul 16, 2015 at 11:11 AM, Michele Santuari <
michele.santuari(a)create-net.org> wrote:

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


cf push fails (goroutine errors)

Michele Santuari <michele.santuari@...>
 

Hi,
we have installed CF v212 on top of Openstack 6.0. Cloudfoundry has been
installed with bosh-init. All the VMs are up and running and bosh
cloudcheck reports 0 errors.
The problem is that when we push applications, we get a lot of errors
related to goroutine (see log file
<https://drive.google.com/open?id=0B8Z5KYzSwwx3WTdmT3hOQWk4eVU>) and the
applications are not started.
Could you help me identify the problem?
Thanks,

--
Michele Santuari
CREATE-NET
Junior Research Engineer
Via alla Cascata 56/D - 38123 Povo Trento (Italy)
e-mail: michele.santuari(a)create-net.org
Tel: (+39) 0461312443
Hangout: michele.santuari(a)create-net.org
Skype: s4nto.m
www.create-net.org
--------------------------------------------------------
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited according to the
Italian Law 196/2003 of the Legislature. If you received this in error,
please contact the sender and delete the material from any computer.


Re: 3 etcd nodes don't work well in single zone

Gwenn Etourneau
 

I guess ,
It can run with 3 nodes but it seems it not doing well with the 3 nodes on
the same zone.



On Thu, Jul 16, 2015 at 10:18 AM, Li, Tony <Tonyl(a)fast.au.fujitsu.com>
wrote:

Hi,



We installed CF210 recently (in single AZ).

Single etcd instance(instance number is 1) runs very well.

But multi etcd instances(instance number is 3) don't work well in single
AZ.



And from the release Notes on
http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210,
there is one term I’m confused about:



“Upgrade etcd server to 2.0.1 details
<https://www.pivotaltracker.com/story/show/91070214>

Should be run as 1 node (for small deployments) or 3 nodes spread across
zones (for HA)”



May I ask it means:



“1. Should be run as 1 node (but can NOT be run as 3 nodes) in
environment with only one zone.

2. Should be run as 3 nodes in environment with more than one zones.
should spread them across zones.”



Or means:

“1. can be run as 1 node, (and can also be run as 3 nodes) in
environment with only one zone.

2. Should be run as 3 nodes in environment with more than one zones.
should spread them across zones.”



Thanks,



*Tony*
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


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


3 etcd nodes don't work well in single zone

Tony
 

Hi,

We installed CF210 recently (in single AZ).
Single etcd instance(instance number is 1) runs very well.
But multi etcd instances(instance number is 3) don't work well in single AZ.

And from the release Notes on http://bosh.io/releases/github.com/cloudfoundry/cf-release?version=210, there is one term I’m confused about:

“Upgrade etcd server to 2.0.1 details<https://www.pivotaltracker.com/story/show/91070214>
Should be run as 1 node (for small deployments) or 3 nodes spread across zones (for HA)”

May I ask it means:

“1. Should be run as 1 node (but can NOT be run as 3 nodes) in environment with only one zone.
2. Should be run as 3 nodes in environment with more than one zones. should spread them across zones.”

Or means:
“1. can be run as 1 node, (and can also be run as 3 nodes) in environment with only one zone.
2. Should be run as 3 nodes in environment with more than one zones. should spread them across zones.”

Thanks,

Tony
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: Incubation Proposal: Project CF-Abacus

Chris Sterling
 

This looks like a useful service. Thanks for the contribution!

Chris Sterling
chris.sterling(a)gmail.com
twitter: @csterwa
linkedin: http://www.linkedin.com/in/chrissterling

On Wed, Jul 15, 2015 at 8:37 AM, Duncan Johnston Watt <
duncan.johnstonwatt(a)cloudsoftcorp.com> wrote:

+1 this looks incredibly useful.

Best

Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

On 15 July 2015 at 15:07, James Bayer <jbayer(a)pivotal.io> wrote:

thanks to ibm for this proposal! we're excited to review this in more
depth.

what this means for service authors is that they would have a standard
system component and format for to track custom billing metrics for service
usage other than "how long was this service deployed". consider an email
service, you could track usage for every email sent or for a data service
you could track the amount of disk usage for data storage. it opens up a
lot of flexibility for how to do chargeback and showback.

for operators, in addition to apps, if the services provided on the
platform use this approach or are translated to this, it provides a
standard way to roll-up usage for a tenant across all of their platform
usage and present it nicely aggregated.

looking forward to the feedback,

james

On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim(a)us.ibm.com>
wrote:

Hi,

This email is to introduce and propose project Abacus to the CF
community for incubation.

*What?*

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and
metering component such that users can project and drill down on the costs
they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use
to provide usage data, but also, how to aggregate that information, as well
as a component to expose the aggregated data into a format (JSON) that can
be subsequently consumed by users — this is done via a drill down UI in
Bluemix.

Project Abacus is an extracted Open Source Software version (under
Apache 2.0 license) of the APIs, usage metering, and aggregation components
from the Bluemix feature.

Finally, it’s important to state that project Abacus uses a
micro-services architecture and is written in Node.js with CouchDB
compatible DBs as datastore and for map/reduce aggregations. Also, all
components can actually run as CF apps or be externalized. In Bluemix they
run as apps.

In other words, this is a bit different from other CF components,
however, we have reviewed Abacus with our colleagues from Pivotal and they
also believe it warrants incubation.

*When?*

Now.

Find the first self-contained release here:
https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README
<https://github.com/jsdelfino/cf-abacus/blob/master/README.md>that can
help you setup and try this first release. The team has included a fake
broker that can be used to generate usage data so you can try the whole
thing out of the box.

*How?*

We plan to introduce this as part of the CAB call discussion tomorrow
07/15 and field any questions.

The next step will be to get approval and become an incubation project.
Once this is done we will be staffing the project with a team (many from
the Bluemix engineers that created it) as well as a PM, and follow the CFF
guidelines for new projects.

We are ready to move on this with no delays and we welcome all
interested parties to try out the first release and to help us refine the
APIs and subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: Incubation Proposal: Project CF-Abacus

Duncan Johnston-Watt <duncan.johnstonwatt@...>
 

+1 this looks incredibly useful.

Best

Duncan Johnston-Watt
CEO | Cloudsoft Corporation

Twitter | @duncanjw
Mobile | +44 777 190 2653
Skype | duncan_johnstonwatt
Linkedin | www.linkedin.com/in/duncanjohnstonwatt

On 15 July 2015 at 15:07, James Bayer <jbayer(a)pivotal.io> wrote:

thanks to ibm for this proposal! we're excited to review this in more
depth.

what this means for service authors is that they would have a standard
system component and format for to track custom billing metrics for service
usage other than "how long was this service deployed". consider an email
service, you could track usage for every email sent or for a data service
you could track the amount of disk usage for data storage. it opens up a
lot of flexibility for how to do chargeback and showback.

for operators, in addition to apps, if the services provided on the
platform use this approach or are translated to this, it provides a
standard way to roll-up usage for a tenant across all of their platform
usage and present it nicely aggregated.

looking forward to the feedback,

james

On Tue, Jul 14, 2015 at 8:30 PM, Michael Maximilien <maxim(a)us.ibm.com>
wrote:

Hi,

This email is to introduce and propose project Abacus to the CF community
for incubation.

*What?*

The IBM Bluemix PaaS (based on CloudFoundry) includes a billing and
metering component such that users can project and drill down on the costs
they have incurred or will incur as they use the system.

Part of this component includes not only APIs that service brokers use to
provide usage data, but also, how to aggregate that information, as well as
a component to expose the aggregated data into a format (JSON) that can be
subsequently consumed by users — this is done via a drill down UI in
Bluemix.

Project Abacus is an extracted Open Source Software version (under Apache
2.0 license) of the APIs, usage metering, and aggregation components from
the Bluemix feature.

Finally, it’s important to state that project Abacus uses a
micro-services architecture and is written in Node.js with CouchDB
compatible DBs as datastore and for map/reduce aggregations. Also, all
components can actually run as CF apps or be externalized. In Bluemix they
run as apps.

In other words, this is a bit different from other CF components,
however, we have reviewed Abacus with our colleagues from Pivotal and they
also believe it warrants incubation.

*When?*

Now.

Find the first self-contained release here:
https://github.com/jsdelfino/cf-abacus/archive/v0.0.1.tar.gz

There is a comprehensive README
<https://github.com/jsdelfino/cf-abacus/blob/master/README.md>that can
help you setup and try this first release. The team has included a fake
broker that can be used to generate usage data so you can try the whole
thing out of the box.

*How?*

We plan to introduce this as part of the CAB call discussion tomorrow
07/15 and field any questions.

The next step will be to get approval and become an incubation project.
Once this is done we will be staffing the project with a team (many from
the Bluemix engineers that created it) as well as a PM, and follow the CFF
guidelines for new projects.

We are ready to move on this with no delays and we welcome all interested
parties to try out the first release and to help us refine the APIs and
subsequent releases.

------
Best,

IBM CF team

dr.max
ibm cloud labs
silicon valley, ca

Sent from my iPhone

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Thank you,

James Bayer

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Cloudsoft Corporation Limited, Registered in Scotland No: SC349230.
Registered Office: 13 Dryden Place, Edinburgh, EH9 1RP

This e-mail message is confidential and for use by the addressee only. If
the message is received by anyone other than the addressee, please return
the message to the sender by replying to it and then delete the message
from your computer. Internet e-mails are not necessarily secure. Cloudsoft
Corporation Limited does not accept responsibility for changes made to this
message after it was sent.

Whilst all reasonable care has been taken to avoid the transmission of
viruses, it is the responsibility of the recipient to ensure that the
onward transmission, opening or use of this message and any attachments
will not adversely affect its systems or data. No responsibility is
accepted by Cloudsoft Corporation Limited in this regard and the recipient
should carry out such virus and other checks as it considers appropriate.


Re: R: Cant login from cf CLI, "Missing grant type"

Filip Hanik
 

Make sure you use the latest version of the CLI, that could be an issue too

On Wed, Jul 15, 2015 at 9:25 AM, Filip Hanik <fhanik(a)pivotal.io> wrote:

You shouldn't have to add the client to the manifest, as it is
automatically added here:

https://github.com/cf-identity/cf-release/blob/identity-latest/jobs/uaa/templates/uaa.yml.erb#L128-L137

If you wish to add it, it would look like:

properties:
uaa:
clients:
cf:
authorities: "uaa.none"
authorized-grant-types: "implicit,password,refresh_token"
scope:
"cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write,doppler.firehose"
secret: ""




On Wed, Jul 15, 2015 at 7:35 AM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Minimal update, I attach the new manifest, cf login trace and uaa.log
relevant part.

I am thinking that is related to the uaa->clients part of the manifest

thank you.
Michael

Il 15/07/15 08:57, *Michael Grifalconi * <
michael.grifalconi(a)studenti.unimi.it> ha scritto:

Hello all,

I can login using the web interface (login.mydomain.com) but when I try
on the cf CLI, I get:

Server error, status code 400, error code: invalid_request, message:
Missing grant type

Am I missing something in the (attached)manifest?

Thank you!

Michael

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

_______________________________________________
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


Re: R: Cant login from cf CLI, "Missing grant type"

Filip Hanik
 

You shouldn't have to add the client to the manifest, as it is
automatically added here:
https://github.com/cf-identity/cf-release/blob/identity-latest/jobs/uaa/templates/uaa.yml.erb#L128-L137

If you wish to add it, it would look like:

properties:
uaa:
clients:
cf:
authorities: "uaa.none"
authorized-grant-types: "implicit,password,refresh_token"
scope:
"cloud_controller.read,cloud_controller.write,openid,password.write,cloud_controller.admin,scim.read,scim.write,doppler.firehose"
secret: ""




On Wed, Jul 15, 2015 at 7:35 AM, Michael Grifalconi <
michael.grifalconi(a)studenti.unimi.it> wrote:

Minimal update, I attach the new manifest, cf login trace and uaa.log
relevant part.

I am thinking that is related to the uaa->clients part of the manifest

thank you.
Michael

Il 15/07/15 08:57, *Michael Grifalconi * <
michael.grifalconi(a)studenti.unimi.it> ha scritto:

Hello all,

I can login using the web interface (login.mydomain.com) but when I try
on the cf CLI, I get:

Server error, status code 400, error code: invalid_request, message:
Missing grant type

Am I missing something in the (attached)manifest?

Thank you!

Michael

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

_______________________________________________
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

8581 - 8600 of 9374