translation coordinators:
Tomoyuki Kato kato.dream.tomoy...@gmail.com
Masanori Itoh masanori.i...@gmail.com
Akira Yoshiyama akirayoshiy...@gmail.com
Best regards,
Masanori -- JOSUG / Japan OpenStack User Group
From: Ying Chun Guo guoyi...@cn.ibm.com
Subject: [Openstack] Recruiting - Translation
Hi Razique,
Did you synchronize clock of all the servers?
I saw similar issue when clock of nova servers were not synchronized well.
In this case, compute nodes are recognized as down and up (smiley) in turn
repeatedly.
Setting up an NTP server is a good idea, and please check using ntpq
Hi,
I was thinking about the exactly the same thing which Catlin pointed out.
Also, there is an implementation enabling RDMA handling from python:
https://github.com/jgunthorpe/python-rdma
Thus, I was wondring if I can do something more using the above.
BTW, I'm in Boston attending at
kbytes
total disk: 10485760 kbytes
Thanks,
--
Hisashi Ikari
2011-04-11 (月) の 16:50 +0900 に Masanori ITOH さんは書きました:
Hi,
We are considering if it's possible to support KVM block migration
as the next step of live migration.
Actually, our main issue at this moment
,
2011/4/12 Masanori ITOH itou...@nttdata.co.jpmailto:itou...@nttdata.co.jp
Hi,
Vish also mentioned that we should support the KVM block migration feature
instead of stability which I mentioned because it's very much useful.
I agree with Vish of course. :)
Actually, we discussed inclusion
you run nova.sh (or anyway nova-* services) by root user.
# Or, maybe someone set writable bit in the directory which lock_path points to.
Regards,
Masanori
--
Masanori ITOH itou...@nttdata.co.jp
From: Thomas Goirand tho...@goirand.fr
Subject: Re: [Openstack] Nova writing lock files in /usr/lib
Hi,
From: Jon Slenk jsl...@internap.com
Subject: Re: [Openstack] ec2 vs. openstack api question
Date: Mon, 25 Apr 2011 16:48:30 -0700
On Mon, Apr 25, 2011 at 4:34 PM, Joshua McKenty j...@pistoncc.com wrote:
Can you give us the actual command you're running?
curl localhost:8773/
works,
status: active
transferred ram: 48 kbytes
remaining ram: 147792 kbytes
total ram: 147840 kbytes
transferred disk: 206848 kbytes
remaining disk: 10278912 kbytes
total disk: 10485760 kbytes
Thanks,
--
Hisashi Ikari
2011-04-11 (月) の 16:50 +0900 に Masanori ITOH さんは書きました:
Hi
Hi Funasaki-san,
I think the following works.
# nova-manage floating create HOST_NAME FLOATING_IP(global/public IP)
and
# euca-associate-address -i INSTANCE_ID FLOATING_IP
Here, please note that Nova does not assign a public IP to an instance
on the launch time automatically like the case of
Hello,
We, NTT DATA, also agree with majority of folks.
It's realistic shooting for the the Diablo time frame to have
the new network service.
Here are my suggestions:
- I know that there were several documents on the new network service issue
that were locally exchanged so far.
Why not
OpenStack developers are on the list. :)
Regards,
Masanori
---
Masanori ITOH RD Headquarters, NTT DATA CORPORATION
e-mail: itou...@nttdata.co.jp
From: Kenji Funasaki kenji.funas...@gmail.com
Subject: [Openstack] Can ec2-api-tools maintain OpenStack Nova ?
Date: Thu, 20 Jan 2011 20:01
Hello,
I'm Masanori Itoh of NTT DATA, Japan.
I would like to share some issues on openstack from Japanese
enterprise system market.
I know that the requirements below do not fit for the austin release
scheduled in this Octorber, but I believe that still it's useful
sharing them with folks here
12 matches
Mail list logo
