> At the very least it is always possible to describe what area of the code is
> being changed, so that you alert the reviewers you are familiar with that
> area.
Yes, Makes sense.
-Mandar
__
Disclaimer:This email and any att
> I particularly hate the single-line "Fixes bug 1234566"-type commit messages.
I assume your concern was regarding commits where "Fixes bug 1234566" is the
first and ONLY line.
"Fixes bug 1234566" comes from Wiki.
Plus there is restriction on how long the first line of the commit message can
so my guess given below -
which may be incorrect and/or confusing - sorry about that)
Re "What I can't figure out is what changed in the last couple days" - I am not
sure :(
-Mandar
From: Gabriel Hurley [mailto:gabriel.hur...@nebula.com]
Sent: Friday, June 29, 2012 2:02 AM
To: Ke
May be related to https://bugs.launchpad.net/keystone/+bug/995976
Check last comment at https://bugs.launchpad.net/keystone/+bug/995811
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of
Try "nova --debug image-list" - It should give you more information/stack trace.
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Trinath Somanchi
Sent: Tuesday, June 26, 2012 3:24 P
http://lmgtfy.com/?q=openstack+command+line+tools
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Trinath Somanchi
Sent: Tuesday, June 26, 2012 10:49 AM
To: openstack@lists.launchpad.
See https://lists.launchpad.net/openstack/msg12548.html to get debug
information on the webpage
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Trinath Somanchi
Sent: Monday, June 2
Based on the error, I think the machine where you are running "nova" client is
unable to connect to nova-api server.
You can try "nova --debug list", This might give you some clue/help
troubleshoot further.
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@list
andar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Vaze, Mandar
Sent: Friday, June 22, 2012 9:41 AM
To: Vishvananda Ishaya
Cc: openstack@lists.launchpad.net
Subject: Re: [Openstack] AttributeError: "virDomain instance has no attribute
'reset'"
Vish,
I'm running
stall ?
Thanks,
-Mandar
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Friday, June 22, 2012 12:13 AM
To: Vaze, Mandar
Subject: Re: AttributeError: "virDomain instance has no attribute 'reset'"
the reset command was only recently added to libvirt, so your version is
This may not be related to host flag.
See similar problem being discussed in this thread :
https://lists.launchpad.net/openstack/msg13314.html
(Same symptoms as yours, error in allocate_for_instance, rpc timeouts)
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[ma
Default password for cirros is "cubswin:)" - including the smiley
I hope you entered correct password (It is easy to ignore the last two
characters thinking it is a smiley)
Other options is to use password less ssh login using keypair.
See
http://docs.openstack.org/essex/openstack-compute/starte
Ø Does this Controller machine requires Hardware virtualization support for
KVM libvirt ?
Yes. To be accurate nova-compute needs hardware virtualization support .
Otherwise you can use “libvirt_type=qemu”
Check
http://docs.openstack.org/trunk/openstack-compute/admin/content/kvm.html#checking-kv
"public_port" is configurable via keystone.conf - so if port 5000 is blocked in
specific setup, it is trivial to change it to some other port.
why make so many changes (REST docs, XML docs, devstack, and the code) for a
parameter that can be easily tweaked ?
-Mandar
-Original Message-
When I tried this on post-essex release code, I got :
error: unrecognized arguments: --force_hosts=
Try --hint force_hosts= instead
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@li
Udit,
What setup are you using ? devstack ?
Did you start this getting error recently ? Did anything change on your system?
This (https://lists.launchpad.net/openstack/msg11123.html) thread suggests code
was updated without updating api-paste.ini (Not sure if it applies to you since
you haven't
> Here is my question:
> 1. Is the stop operation of vm instance means to delete the vm and keep
>nothing except keep
> this record in databases ?
> 2. Is the start operation of vm means to creat a new vm instance according
>to the
> recorde in databases ?
While some hyperv
> ... so it makes sense to go through each daemon at a time using pdb.
Not sure what you mean, but you can easily put set_trace() in multiple daemons
at the simultaneously, in fact it is useful to trace the flow across various
openstack services.
-Mandar
_
Salman,
I haven't used UI tools like Pydev and/or eclipse. I have a devstack
installation running on linux box where I use ssh for all my development.
TL;DR Version : I use pdb (aka Python Debugger) It is very easy to use if you
have used gdb - (Refer to
http://docs.python.org/library/pdb.htm
I think glance uses keystone for authentication (default setup)
See https://lists.launchpad.net/openstack/msg12661.html and
http://docs.openstack.org/api/openstack-compute/programmer/content/using-python-to-obtain-the-authentication-token.html
for "how to get auth token"
Once you use authentica
Ø The Image is moving from the states Scheduling, Networking and to Spawning.
In the Spawning phase, a Error is returned.
What error do you see ? If you haven’t enabled logging, please do and see if
there are any errors – especially in nova-compute log.
Which hypervisor are you using ? (Since t
_create_image method supports two types of images - image_snapshot and
image_backup
These two are mostly identical except for few places (like checking for
rotation etc.)
Neither Dashboard (Horizon UI) nor "nova" command line tool have option to
perform "image_backup"
Both these only invoke "im
Hi,
Related to instance being stuck in "image_snapshot" for extended period of
time, it is easy to "recover" the instance (script uses pre-defined timeout
to "guess" that snapshot has hung and will never complete) and bring it back to
"usable" state, I also the *inform the user that their sna
> But the pickle is the case where a user initiates a shutdown
> inside the VM. What's the expected behavior after it's detected?
> Should it respect the shutdown_terminate flag or work more like an OS
> API? Right now when a shutdown in a VM is detected, the vm state is
> updated to SHUTOFF and t
Sharing with the community, so that it would be useful for others as reference.
From: Raghuram Bondalapati [mailto:raghuram.bondalap...@gmail.com]
Sent: Thursday, May 31, 2012 11:16 AM
To: Vaze, Mandar
Subject: Re: [Openstack] Cannot access nova instances from dashboard
I have enabled Debug and
Can you try setting DEBUG=True (For troubleshooting only) in
openstack_dashboard/settings.py ? (and then restart Horizon/Dashboard)
Then you may get more information when you run into the following error.
-Mandar
P.S: I assume that you have ":" between $my_ip and 5000 in
OPENSTACK_KEYSTONE_URL
> I'm a bit disappointed that the request even went through to the compute node
> to build the instance, as the scheduler *should* already know the memory
> exceeds the available memory on the box.
FilterScheduler (and chanceScheduler?) checks this condition before sending to
Compute, SimpleSc
> I want to know if there is a timeout for a fixed ip to be reused, how long
> this time is
Parameter you are looking for is fixed_ip_disassociate_timeout. Set it to low
value like "1" (This is number of seconds)
Default value is 600 i.e. 10 minutes.
-Mandar
__
Which IPAM ?
This behavior is fixed for mélange IPAM . Please look at
https://bugs.launchpad.net/melange/+bug/971504
Also see this : https://bugs.launchpad.net/nova/+bug/973442
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nt
Sorry for responding to old thread, I later realized that Yun had already
responded to Gabe's query.
-Original Message-
From: Vaze, Mandar
Sent: Friday, May 25, 2012 6:10 PM
To: 'Gabe Westmaas'; Mark Washenberger; openstack@lists.launchpad.net;
yun...@gmail.com
Subject:
> I'd like to understand the difference between a soft and hard delete.
soft_delete is invoked when "reclaim_instance_interval" flag is set to non-zero.
In this case, when delete command is fired, only the VM is powered off, and
vm_state is set to SOFT_DELETE
Other resources (like network, volume
. from /opt/stack)
"cd /opt/stack ; for d in `ls -1`; do echo "updating $d"; cd $d; git pull; cd
/opt/stack; done"
-Mandar
From: Salman Malik [mailto:salma...@live.com]
Sent: Thursday, May 24, 2012 7:47 PM
To: dolph.math...@gmail.com; Vaze, Mandar
Cc: openstack@lists.launc
Last time when I ran into this error, I had updated (git pull) only nova, but
forgot to update keystone.
Once I updated (git pull) all the other projects, including keystone, the error
went away.
Few things you can use for troubleshooting :
1. Run this command from terminal - See if the
Ø Is there any way to find out if image is exists with the help of glance
command?
"glance image-list"
See my other email for your original problem
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest con
Ø But, from inside dashboard, I couldn't find where to get a similar
information.
>From Dashboard, Click "Edit Instance" button on far right, and click on "View
>Log"
Scroll at the end, you'll see the password.
-Mandar
__
D
Milind,
Nova boot command takes Image and Flavor IDs, not names
Can you try "nova boot -image 057f5695-7af5-4d42-ab17-2f0f36f99ee2 " instead ?
Similarly, you may need to use -flavor 2 instead of --flavor m1.small
If you are interested in looking at code, see "def do_boot" in
novaclient/v1_1/she
lf Of Christoph Thiel
Sent: Wednesday, May 09, 2012 4:04 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] Pending review
On Wed, May 09, 2012 at 05:38:44AM +0000, Vaze, Mandar wrote:
> https://review.openstack.org/#/c/6829/
>
> Kevin Mitchell has reviewed as "Looks good
https://review.openstack.org/#/c/6829/
Kevin Mitchell has reviewed as "Looks good to me"
Additional reviews and approval required
Thanks,
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest confidence for
Of
Eric Luo
Sent: Tuesday, May 08, 2012 7:04 AM
To: Vaze, Mandar
Subject: Re: [Openstack] Instance unreachable
Hi , Mandar .
I did have such problems before ,and I got things work at last . So ,I think my
experience may have a little help.
If you can ping (or ssh) to the VM on your HOST ,but
Forwarding to ML so that others can suggest further troubleshooting points.
From: ghassen ben hamida [mailto:ghassen.ben.ham...@gmail.com]
Sent: Monday, May 07, 2012 5:36 PM
To: Vaze, Mandar
Subject: Re: [Openstack] Instance unreachable
Hi,
It is a single machine setup.
There is nothing what
Check if using sql based service catalog instead of file based helps.
[catalog]
driver = keystone.catalog.backends.sql.Catalog
See http://keystone.openstack.org/configuration.html
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.
1. Have you enabled logging ? Do you see any errors in nova-network logs ?
2. Which network manager are you using ?
3. Some details about your setup will also help (Is it Single machine
setup ?)
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mai
Please also see this : https://review.openstack.org/#/c/6829/
When nova-network is on remote host, dhcp requests need to go to remote
server. I’ve proposed a fix above.
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata...
Emilien,
Please see https://answers.launchpad.net/quantum/+question/194111
Nova-compute and nova-network on two different machines seems to be the key
here.
Solution is proposed in the above thread.
Hope that helps.
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
This is really useful.
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Bernhard M. Wiedemann
Sent: Wednesday, May 02, 2012 5:56 PM
To: openstack@lists.launchpad.net
Thanks !!
-Mandar
-Original Message-
From: Alan Pevec [mailto:ape...@gmail.com]
Sent: Monday, April 30, 2012 1:19 PM
To: Vaze, Mandar
Cc: d...@nicira.com; openstack@lists.launchpad.net
Subject: Re: [Openstack] Backporting to Essex-Stable
On Mon, Apr 30, 2012 at 8:14 AM, Vaze, Mandar
> did the nova user /already/ have root access?
nova-rootwrap uses "sudo" to execute certain commands that require root access.
So yes, nova user already has root access via sudo. You can check /etc/sudoers
file.
stack.sh script from devstack adds the entry in sudoers list for the user
runnin
We've recently fixed some bugs that did not make it in time for Essex, so they
are in master branch now.
We would like these to be back-ported to Essex-stable branch.
https://bugs.launchpad.net/nova/+bug/973194
https://bugs.launchpad.net/nova/+bug/977759
https://bugs.launchpad.net/nova/+bug/97787
Dan,
I've updated the question (few more queries)
> Also, you didn't say exactly how you were running devstack. Can you send
> your config?
I've described my two-machine setup in the original question itself.
I didn't know how to add an attachment to the question, so here is my nova.conf
for
Dan,
Can you help with this ?
https://answers.launchpad.net/nova/+question/194111
Thanks,
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain
Dan,
Can you help with this ?
https://answers.launchpad.net/nova/+question/194111
Thanks,
-Mandar
__
Disclaimer:This email and any attachments are sent in strictest confidence for
the sole use of the addressee and may contain
n favor of data integrity :)
-Mandar
-Original Message-
From: Vishvananda Ishaya [mailto:vishvana...@gmail.com]
Sent: Friday, April 20, 2012 11:47 AM
To: Vaze, Mandar
Cc: Philipp Wollermann; J. Daniel Schmidt; openstack
Subject: Re: [Openstack] Using Foreign Keys
On Apr 19, 2012, at 8:59 P
+1 for data integrity ...
Here is an example that could use data integrity check :
tenant information is managed in keystone DB
ovs_quantum DB has tenant_id column for networks table.
When I use stack.sh - it puts a string "default" in tenant_id column - when it
creates network via "nova-manage
Hi,
I understand that most of you must be busy and enjoying the Design Summit in
progress this week.
It would be great if someone can spare some time to have a look at these :
* https://review.openstack.org/#/c/6262/ : Both Vish and Padraig have
said "Looks good to me" but the review
I have also seen this when I execute run_tests.sh
Since I haven't yet made changes related to these parts of code, I generally
skip this test using @unit.skip decorator
I've already clicked "This bug also affects me" on LP
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze
asq locally ?
Thanks !!
-Mandar
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Thursday, April 12, 2012 9:44 PM
To: Vaze, Mandar
Cc: openstack@lists.launchpad.net; netst...@lists.launchpad.net
Subject: Re: [Netstack] Role of "nova-manage network" commands when using
QuantumManager
H
asq locally ?
Thanks !!
-Mandar
From: Dan Wendlandt [mailto:d...@nicira.com]
Sent: Thursday, April 12, 2012 9:44 PM
To: Vaze, Mandar
Cc: openst...@lists.launchpad.net; netstack@lists.launchpad.net
Subject: Re: [Netstack] Role of "nova-manage network" commands when using
QuantumManager
H
You may have his this bug : https://bugs.launchpad.net/nova/+bug/965826
Says : this occurs "When auth_host (in api-paste.ini) has the wrong IP address"
Something to check ...
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdat
It is my understanding that in multi-node setup :
* nova-manage can be executed from any machine which may not be running
nova-network process. (Or should nova-manage always be run on nova-network
node ?)
* nova-manage does DB operations and delegates the actual networking
cal
It is my understanding that in multi-node setup :
* nova-manage can be executed from any machine which may not be running
nova-network process. (Or should nova-manage always be run on nova-network
node ?)
* nova-manage does DB operations and delegates the actual networking
cal
@nicira.com]
Sent: Wednesday, April 11, 2012 11:07 PM
To: Vaze, Mandar
Cc: Nicolas de BONFILS; openstack@lists.launchpad.net
Subject: Re: [Openstack] Instance can't reach dhcp or metadata
On Wed, Apr 11, 2012 at 5:24 AM, Vaze, Mandar
mailto:mandar.v...@nttdata.com>> wrote:
I have neve
I have never been able to get to ssh to an instance with Quantum+mélange
https://lists.launchpad.net/openstack/msg09206.html
-Mandar
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Nicolas de
Would http://devstack.org/guides/single-machine.html work for you ? (Or does it
need to be installed from packages)
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
B
https://review.openstack.org/#change,6076 has been open since Apr 2nd.
I understand everyone must have been busy with Essex release up to 5th.
Can someone please take a look and approve ? (It is a trivial change)
Thanks,
-Mandar
___
Copying /opt/stack/mélange/etc/mélange/mélange.conf to /etc resolved the
problem i.e. test cases started executing.
But that seems like BAD idea since running test cases trashed my DB ( I have
single box devstack installation)
-Mandar
-Original Message-
From: Vaze, Mandar
Sent
e any configuration file. Cannot load application
mélange
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On
Behalf Of Jason Kölker
Sent: Friday, April 06, 2012 8:21 PM
I tried to run ./run_tests.sh (without virtualenv) I kept on getting error
related to "unable to find config file"
I ran the tests from /opt/stack/mélange
Same errors when I run "python run_tests.py"
/opt/stack/mélange/etc/mélange/mélange.conf is present and valid.
How do I pass the config file t
!!!
Thanks Rohit !!!
Thanks Vish !!
-Mandar
From: Vaze, Mandar
Sent: Wednesday, April 04, 2012 4:41 PM
To: openstack@lists.launchpad.net
Cc: 'vishvana...@gmail.com'
Subject: RE: [Openstack] Instance fails to spawn when instance_path is nfs
mounted
All,
On the link given below vish
Jason/Troy/Dan :
I've marked the bug from invalid to new.
See my updates at : https://bugs.launchpad.net/melange/+bug/971504/comments/3
If indeed you agree to periodic_task suggestion - where should that go (code
wise) ? mélange-server ? Please guide me.
Thanks,
-Mandar
From: Vaze, M
All,
On the link given below vish asked if I could “chown” the files in that folder
– turns out I couldn’t.
I’ve answered his query on the link below – but repeating the updates here for
larger audience (Unfortunately, I have revived a question that is marked as
“solved” – so not many people m
Ø Check if not only root can write on the nfs share (specially libvirt user).
It doesn’t look like permissions issue to me. Just to be doubly sure, I
“touched” a file, in that folder, edited and deleted the file. All operations
worked w/o error.
As I have listed below, several files got created
> I had a problem like this when the umask was locked down. Setting the umask
> to 022 in the init script for nova-compute solved my problem.
I'm running from devstack setup - so I don't have an init-script. All the
processes run in a "screen" session.
Here is what I did :
1. Stopped nova-comp
72 matches
Mail list logo
