Can you check the kubelet log on your minions? Seems the container failed
to start, there might be something wrong for your minions node. Thanks.
2015-02-22 15:08 GMT+08:00 Hongbin Lu hongbin...@gmail.com:
Hi all,
I tried to go through the new redis example at the quickstart guide [1],
but
On Sun Feb 22 2015 at 6:27:16 AM Michael Bayer mba...@redhat.com wrote:
On Feb 21, 2015, at 9:49 PM, Joshua Harlow harlo...@outlook.com wrote:
Some comments/questions inline...
Mike Bayer wrote:
Yuriy Taradayyorik@gmail.com wrote:
On Fri Feb 20 2015 at 9:14:30 PM Joshua
Thanks Jay,
I checked the kubelet log. There are a lot of Watch closed error like
below. Here is the full log http://fpaste.org/188964/46261561/ .
*Status:Failure, Message:unexpected end of JSON input, Reason:*
*Status:Failure, Message:501: All the given peers are not reachable*
Please note
Please see inline
On Thu, Feb 19, 2015 at 4:43 PM, Steve Gordon sgor...@redhat.com wrote:
- Original Message -
From: Irena Berezovsky irenab@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org,
On Thu, Feb 5, 2015 at
It's really a great feature for HEAT which can accelerate the speed for
HEAT to production, wish you good luck! Thanks!
2015-02-21 2:21 GMT+08:00 Aggarwal, Nikunj nikunj.aggar...@hp.com:
Hi,
I have submitted presentations for Openstack L summit :
The Heat Orchestration Template
How can I having a device owner value to match it vs. the compute node?
--
Regards,
Leo
-
I enjoy the massacre of ads. This sentence will slaughter ads without a
messy bloodbath
On Sat, Feb 21, 2015 at 4:21 AM, Aggarwal, Nikunj nikunj.aggar...@hp.com
wrote:
Hi,
I have submitted presentations for Openstack L summit :
The Heat Orchestration Template Builder: A demonstration
On 17/02/15 23:32, Chris Friesen wrote:
Hi all,
Just thought I'd highlight here that Ubuntu 14.10 is using qemu 2.1, but
they're not currently enabling NUMA support.
I've reported it as a bug and it's been fixed for 15.04, but there is
some pushback about fixing it in 14.10 on the
Once the gate settles down this week I’ll be sending up a major
“big bang” patch to Tempest that will tag all of the tests with unique
identifiers, implementing this spec:
https://github.com/openstack/qa-specs/blob/master/specs/meta-data-and-uuid-for-tests.rst
The work in progress is here, and
On 02/23/2015 06:17 AM, Tom Fifield wrote:
Also, we currently assume that qemu can pin to NUMA nodes. This is an
invalid assumption since this was only added as of qemu 2.1, and there
only if it's compiled with NUMA support. At the very least we should
have a version check, but if Ubuntu
Hi Jay,
I tried the native k8s commands (in a fresh bay):
*kubectl create -s http://192.168.1.249:8080 http://192.168.1.249:8080 -f
./redis-master.yaml*
*kubectl create -s http://192.168.1.249:8080 http://192.168.1.249:8080 -f
./redis-sentinel-service.yaml*
*kubectl create -s
Hi Doug,
I can't find above error when using the latest codes (2015-02-22), but
new error occur ( see [1] ). I feel it has no concern with the
code(ConfigOpts.import_opt), the same code can be run in both bash and
pycharm, it just didn't work in eclipse+pydev. It looks like there are some
I suspect that there are some error after the pod/services parsed, can you
please use the native k8s command have a try first then debug k8s api part
to check the difference of the original json file and the parsed json file?
Thanks!
kubectl create -f .json xxx
2015-02-23 1:40 GMT+08:00
On Feb 22, 2015, at 10:20 AM, Yuriy Taraday yorik@gmail.com wrote:
On Sun Feb 22 2015 at 6:27:16 AM Michael Bayer mba...@redhat.com wrote:
On Feb 21, 2015, at 9:49 PM, Joshua Harlow harlo...@outlook.com wrote:
Some comments/questions inline...
Mike Bayer wrote:
On 02/18/2015 06:37 PM, Brian Rosmaita wrote:
Thanks for your comment, Miguel. Your suggestion is indeed very close
to the RESTful ideal.
However, I have a question for the entire API-WG. Our (proposed)
mission is To improve the developer experience of API users by
converging the OpenStack
15 matches
Mail list logo
