On 06/08/12 16:47, Trinath Somanchi wrote:
> Hi-
>
> Can any one guide me on understanding the process that updates the
> compute_nodes table in nova database.
nova-compute on each compute node sends a regular message to the
nova-scheduler on the scheduler node with an update of its status. These
thanks a lot for the guidance...
On Mon, Aug 6, 2012 at 12:57 PM, Michael Still
wrote:
> On 06/08/12 16:47, Trinath Somanchi wrote:
> > Hi-
> >
> > Can any one guide me on understanding the process that updates the
> > compute_nodes table in nova database.
>
> nova-compute on each compute node s
On 08/03/2012 09:37 AM, 王鹏 wrote:
Everyone:
Hi!
When I install keystone alone, find a error, that’s make me crazy !the
situation as follow:
This is my conf
[DEFAULT]
bind_host = 0.0.0.0
public_port = 5000
admin_port = 35357
admin_token = admin
compute_port = 8774
verbose = True
debu
Have you used keystone as auth server?
If yes, please share your glance and keystone logs to figure out the root cause.
Regards,
Willfu
发件人： 王鹏
收件人： openstack@lists.launchpad.net
发送日期： 2012年8月6日, 星期一, 上午 11:22
主题: [Openstack] glance error
hello,everyone:
Hi,
The interval can be managed via the periodic_interval flag in nova.conf,
which is by default 60 sec
Cheers!
On Mon, Aug 6, 2012 at 9:40 AM, Trinath Somanchi wrote:
> thanks a lot for the guidance...
>
>
>
> On Mon, Aug 6, 2012 at 12:57 PM, Michael Still <
> michael.st...@canonical.com> wr
Have you exported vars as the guide:
export SERVICE_ENDPOINT="http://localhost:35357/v2.0";
export SERVICE_TOKEN=admin
Best
Il giorno 03/ago/2012, alle ore 09:37, 王鹏 ha scritto:
> Everyone:
>
> Hi!
>
> When I install keystone alone, find a error, that’s make me crazy !the
> situation as fol
Hi,
Is there a way to change the default file system of the ephemeral disk attached
to an instance?
By default it's ext3.
Thanks,
Jerico
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https
Hi,
I think this only way is to edit the code like so:
- go to the line 66
of /usr/lib/python2.7/dist-packages/nova/virt/disk/api.py
- and change to 'default=mkfs.ext4 -L %(fs_label)s -F %(target)s',
Make sure to purge your /var/lib/nova/instances/_base
It worked for me :)
Let me know
Hi,
Are you using Essex or Folsom when it worked for you?
Regards,
Jerico
On 06/08/2012, at 8:48 PM, Sébastien Han wrote:
> Cool ;)
>
> On Mon, Aug 6, 2012 at 12:47 PM, Jerico Revote
> wrote:
> Thanks Sebastien, I'll give it a shot.
>
> Jerico
>
> On 06/08/2012, at 8:02 PM, Sébastien Han
I'm using Essex.
Where did you make the code change?
You must put the change on each nova-compute node.
Enable the --verbose flag in nova.conf on your compute nodes,
purge /var/lib/nova/instances/_base/'ephemeral_something', boot a new vm
and watch the log.
Grep for a line matching 'mkfs'
My l
Hi all,
KVM block migration support in OpenStack
(https://blueprints.launchpad.net/nova/+spec/kvm-block-migration)
seems to be somewhat of a secret - there's almost nothing in the
docs/guides (which to the contrary state that live migration is only
possible with shared storage) and only a couple o
Your glance-api server probably can't talk to your glance-registry server. Make
sure glance-registry is running and that glance-api is correctly configured
with its IP and port.
On Aug 5, 2012, at 8:22 PM, 王鹏 wrote:
> hello,everyone:
> when I over glance install and config ,and test glance ind
Hi everyone,
I remember that once in a Cinder IRC meeting, John mentioned the
implementation of CHAP. Is it related to this blueprint:
https://blueprints.launchpad.net/cinder/+spec/iscsi-chap ?
I am interested in this topic, and not sure whether someone is already
doing it.
If no one has taken
No need to edit code, there is a config option for this:
## (MultiStrOpt) mkfs commands for ephemeral device. The format is
=
Put the following in nova.conf:
virt_mkfs=default=mkfs.ext4 -L %(fs_label)s -F %(target)s
On Aug 6, 2012, at 3:02 AM, Sébastien Han wrote:
> Hi,
>
> I think thi
On 08/04/2012 07:48 AM, Heng Xu wrote:
> But I tried a few things in HostState class, I ran into error, because I
> could not monitor the stats in hoststates class as opposed to a database, is
> there a way to check the stats in HostState class as exists in memory?
cc'ing Sandy Walsh, who is vas
Oh I didn't know that one!
Thanks ;)
On Mon, Aug 6, 2012 at 6:07 PM, Vishvananda Ishaya wrote:
> No need to edit code, there is a config option for this:
>
> ## (MultiStrOpt) mkfs commands for ephemeral device. The format is
> =
>
> Put the following in nova.conf:
>
> virt_mkfs=default=mkfs.
Hi Nachi,
I've reviewed the code and added comments. I'd like to see at least a
basic spec describing the proposed approach (need only be a couple
paragraphs, perhaps with a diagram) linked to the blueprint so we can have
a design discussion around it. Thanks,
Dan
On Fri, Aug 3, 2012 at 1:03
On Fri, Aug 3, 2012 at 12:33 PM, Nati Ueno wrote:
> Hi folks
>
> I report this bug recently.
>
> device_id should not be updated twice
> https://bugs.launchpad.net/quantum/+bug/1031473
>
> Now, a user can update device_id which may cause problem.
>
Yeah, ideally this field could only be updated
Hi Dan
Thank you for pointing this.
Yusuke updated design spec.
https://blueprints.launchpad.net/quantum/+spec/quantum-multihost-dhcp
2012/8/6 Dan Wendlandt :
> Hi Nachi,
>
> I've reviewed the code and added comments. I'd like to see at least a basic
> spec describing the proposed approach (nee
I'm happy to announce that Swift 1.6.0 has been released. You can get the
tarball at https://launchpad.net/swift/folsom/1.6.0. As always, you can upgrade
your production Swift clusters to this new version with no downtime to your
clients.
The complete changelog for this release is at
https://g
https://answers.launchpad.net/nova/+question/204852
Can anyone help me? I'm banging my head against a brick wall. I can't ever get
an instance on anything but the control node to be accessible.
Thanks
Dave
Dave Pigott
Validation Engineer
T: +44 1223 40 00 63 | M +44 7940 45 93 44
Linaro.org │
Hi,
Below are the meeting notes from the IRC meeting about LBaaS which
took place on Aug 2.
The logs can be found at
http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-08-02-17.00.log.html
[19:18:27 .. 19:56:41]
=== Status on our side ===
https://github.com/Mir
Hi,
I just posted the following at
http://forums.openstack.org/viewtopic.php?f=15&t=1435, then realized this
mailing list might be a better place to ask the question.
In summary, I've cobbled together devstack-based nodes to exercise
quantum/openvswitch (when I say cobbled, I mean my result is
Hi Syd,
There should not be an additional gateway interface on the compute nodes,
only the node that has n-net in ENABLED_SERVICES. I'm assuming you want to
use the OVSQuantumPlugin? Can you also
attach /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini from your
two nodes? Also if you are i
Hi guys,
By porting our Essex code to Folsom, I noticed that the method
nova/image/glance.get_glance_client is missing. Any suggestion on what to use
as replacement in Folsom?
Here's the current Essex snippet.
(glance_client, image_id) = self._glance.get_glance_client(context,
nam
Hi,every:
That is my first install swift,I according to
objectstorage-adminguide-essex.pdf from www.openstack.org.
when I after install ,Verify the Installation,
use swift -V 2 -A http://:5000/v2.0 -U adminUser:admin -K
012345SECRET99TOKEN012345 stat
[Errno 111] ECONNREFUSED
why?
before this error
Replace "" with the IP/hostname & port of your keystone
server (e.g. 127.0.0.1:35357).
-Dolph
On Mon, Aug 6, 2012 at 9:15 PM, 王鹏 wrote:
> Hi,every:
> That is my first install swift,I according to
> objectstorage-adminguide-essex.pdf from www.openstack.org.
> when I after install ,Verify the Ins
Hi-
I'm seeing these errors in the COMPUTE-NODE nova-compute.log while bringing
up the virtual machines.
2012-08-07 04:45:46 DEBUG nova.rpc.amqp
[req-7e560f6e-0342-4799-83da-94e46d555d96 668f5d9ca716417fa16208828c5acea8
a17de6f647b14739acb33f09d246f72e] Pool creating new connection from
(pid=2770
Guys-
Its my config problem... Its troubleshooted... Now VMs are up and running...
On Tue, Aug 7, 2012 at 10:19 AM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:
> Hi-
>
> I'm seeing these errors in the COMPUTE-NODE nova-compute.log while
> bringing up the virtual machines.
>
> 2012-08-
Hi-'
I have been testing the openstack for past few days... and I have a doubt
here...
>From the Horizon in the CONTROLLER, VMs are created in the NODE machine.
Using the virsh console at the NODE machine, I have suspended the VM. But
the same VM-STATE is not populated in the HORIZON.
Does Nov
You are using virsh directly. Don't do that. Let openstack suspend
nodes. Otherwise yes openstack will not know that you have decided to play
with virsh.
On Mon, Aug 6, 2012 at 11:05 PM, Trinath Somanchi <
trinath.soman...@gmail.com> wrote:
> Hi-'
>
> I have been testing the openstack for past
point of clarity... it should figure out the vm is in a bad state
eventually and list it as not running.
On Mon, Aug 6, 2012 at 11:25 PM, Matt Joyce wrote:
> You are using virsh directly. Don't do that. Let openstack suspend
> nodes. Otherwise yes openstack will not know that you have decided
32 matches
Mail list logo
