you can do export OS_NO_CACHE=1 in your script before using a nova Client
object. to avoid input keyring
2012/11/9 Trinath Somanchi trinath.soman...@gmail.com
Hi-
I have written an resource extension in nova-api. and the test script runs
in the compute-host. When the Keystone credentials
I am sorry, i believe i am having a hardware problem because i have done
apt-get install -y openvswitch-switch openvswitch-datapath-dkms
on other nodes and tunneling just got back to work fine ! my mistake !
thank you for your kind help, i appreciate that !
Le 09/11/2012 03:33, Dan Wendlandt
Hi fellows,
Today I just updated my devstack to setup a new openstack dev environment with
RECLONE set to yes in localrc. The stack.sh failed at the very end in
glance image-create with the error of Invalid OpenStack Identify credential.
I then tried to run glance image-list in the command
as you know.
I already setup my environment with below
- controller: all the things except nova-compute, quantum-l3,dhcp-agent
- network: quantum-l3-agent, quantum-dhcp-agent
- compute*2: nova-compute
and the chef installation was already opened in my github.
please refer
currently.
l3_agent designed as serve all tenant's traffic or
per router per l3_agent by specify router_id in l3_agent.ini
so in current architecture. if you want deploy as production scale.
I think l3_agent must be dedicated to one router
or the another solution is needed(nvp, midonet, cisco
My system is Ubuntu 12.04 64bit.
My nova list also failed with a HTTP 401 status error, with the following
output on nova-api:
2012-11-09 18:30:09 ERROR keystone.common.cms [-] Verify error: Verification
failure
139967656924832:error:04091077:rsa routines:INT_RSA_VERIFY:wrong signature
Hello all,
I would like to know the available solutions that are used regarding to
backing up and/or snapshotting running
instances on compute nodes. Documentation does not mention anything related
to this. With snapshots I don't mean
the current snapshot mechanism, that imports image of the
Hi,
Sorry I missed this, I am still behind on my email.
In the current model every XCP node gets a VM with nova-compute running on it,
and it must be a linux PV VM.
That node does several management tasks. For example, with raw images, it will
stream the image into a VDI attached to that VM.
Sorry for the late response.
What you really want to do is export the OVF through XenCenter, inside there
you will find the VHD file, which is what you really want to be uploading to
Glance (I think there are instructions there for VHD files).
Mate has a nice blog post on quicker ways to
Cinder is the way forward to look at exposing multiple volume types.
The Cinder guys should be able to help you with how to get that working:
https://blueprints.launchpad.net/cinder/+spec/volume-type-scheduler
XCP NFS support should be in there soon too:
Sounds like a bug worth reporting.
What flavor where you selecting, and what image were you using?
There is some code in XenAPI driver that tries to resize the partition of the
disk, and the file system on it, if I remember correctly. Can you see that in
the logs? Maybe it fails because your
My bad, I noticed you have some IBM arrays. What SR type are you using to
connect to those?
I think Cinder has some code of some IBM arrays. If that connects with iSCSI,
it should work with XCP.
Cheers,
John
From: John Garbutt
Sent: 09 November 2012 12:08
To: 'Egoitz Aurrekoetxea Aurre';
Hi Skible,
I followed the install guide
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
I am able to bring up guest, but unable to get ip to guest vm from network
node.
Also attached respective configuraion files .
Please
Hi Skible,
I followed the install guide
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
I am able to bring up guest, but unable to get ip to guest vm from network
node.
Also attached respective configuraion files .
Please
Hello. Anyone?
2012/11/7 Daniel Oliveira dvalbr...@gmail.com
My bad. This is the
tutorialhttp://www.hastexo.com/resources/docs/installing-openstack-essex-20121-ubuntu-1204-precise-pangolinI
talked about.
2012/11/7 Daniel Oliveira dvalbr...@gmail.com
Hello,
I've been following this
Hello,
After initial installs I had seen 404 several times, but most of the times
was not due dashboard itself.
The dashboard refuses to open when you have some critical errors such as
the nova-api not starting.
Also, when glance does not work, the Images panel on the dashboard will
throw an
First. Ping to your metadata_ip in network router namespace.
2012년 11월 9일 금요일에 Veera Reddy님이 작성:
Hi Skible,
I followed the install guide
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
I am able to bring up guest, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OpenStack Security Advisory: 2012-017 (ERRATA 1)
CVE: CVE-2012-4573, CVE-2012-5482
Date: November 9, 2012
Title: Authentication bypass for image deletion
Impact: High
Reporter: Gabe Westmaas (Rackspace)
Products: Glance
Affects: Essex, Folsom, Grizzly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greetings,
Over the last few days there has been some unwelcome activity around
the release of OSSA-2012-017. The Essex patch wasn't ready when the
advisory was published. After that we discovered that the patches for
Folsom and Grizzly were
Hello,
I have just installed the Folsom package of Nova API and am unable to get
it to start.
Here's the error log:
2012-11-09 14:28:40 DEBUG nova.wsgi [-] Loading app metadata from
/etc/nova/api-paste.ini from (pid=25593) load_app
/usr/lib/python2.7/dist-packages/nova/wsgi.py:371
2012-11-09
Hello all,
I'm unable to start glance. I upgraded it from Essex to Folsom on ubuntu
12.04. It produces the following output:
2012-11-09 14:51:27 29928 DEBUG glance.common.config [-] Loading
glance-api-keystone from /etc/glance/glance-api-paste.ini load_paste_app
You may try with option –insecure –no-cache
Regards,
Ravi
From: openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net
[mailto:openstack-bounces+ravikumar.venkatesan=hp@lists.launchpad.net] On
Behalf Of Trinath Somanchi
Sent: Thursday, November 08, 2012 8:39 PM
To:
Highlights of the week
The future of Incubation and Core
http://markmail.org/message/hmc2cmf3wycrqhpe
Incubation is currently an OpenStack project status that grants a
promising project more access to OpenStack shared resources, especially
in the CI, release management and QA
[addendum]
Call For Presentations at Linux.Conf Australia - OpenStack
MiniConf day http://firedaemon.wufoo.com/forms/z7x2p1/
Being held in January in Canberra, Australia, linux.conf.au is one of
the foremost open source conferences in the world, and is considered the
most
Hi all,
I've managed to get Openstack pretty much up and running as I wanted it. I
do have, however, a rather strange networking issue.
I created the network with
nova-manage network create --fixed_range_v4=10.0.41.0/24 --num_networks=1
--bridge=br41 --bridge_interface=eth0 --label=development
I've managed to fix the problem by replacing my old paste.ini files for
glance-api and glance-registry with the ones provided with the packages.
On Fri, Nov 9, 2012 at 2:55 PM, Leander Bessa Beernaert leande...@gmail.com
wrote:
Hello all,
I'm unable to start glance. I upgraded it from Essex
For anyone with the same problem, I've managed to fix my problem by
updating my old api-paste.ini with the one provided with the
Folsom package.
Regards,
Leander
On Fri, Nov 9, 2012 at 2:42 PM, Leander Bessa Beernaert leande...@gmail.com
wrote:
Hello,
I have just installed the Folsom
Hi everyone,
I've some doubts regarding the usage/working of libvirt-lxc with openstack.
I'm doing a project titled Low density virtualization for Storage cloud
1. Can i use libvirt for lxc with Openstack swift alone (excluding nova,
glance and keystone)? If no what other openstack components
Good day everyone,
I am doing a Folsom install following this guide:
https://github.com/EmilienM/openstack-folsom-guide
I only have set up the internal network and I can swpan instances but it
doesn't seem like I can connect to them at all, and they cannot find the
metadata host.
I have 3
On 11/09/2012 09:14 AM, Joe Warren-Meeks wrote:
What I am seeing in Tcpdump is a lot of incorrect cksums. This happens
with all Tcp connections.
17:12:38.539784 IP (tos 0x0, ttl 64, id 53611, offset 0, flags [DF],
proto TCP (6), length 60)
10.0.0.240.56791 10.0.41.3.22: Flags [S], cksum
The libvirt driver has actually gotten quite good at rebuilding all of the data
for instances. This only thing it can't do right now is redownload base images
from glance. With current state if you simply back up the instances directory
(usually /var/lib/nova/instances) then you can recover by
I have two nic cards, I want eth0 to always be connected to network1
and eth1 to always be connected to network2.
In the essex, I can do this by arrange the order of --nic options in
the nova boot command. But in the folsom,it does not seem to work
anymore, the following commands connect eth0 to
What is the ip address of your workstation? You may be running into something
similar to this issue:
http://lists.openstack.org/pipermail/openstack-dev/2012-September/001212.html
I suspect either:
a) Traffic not getting snatted when it should. This is usually due to
overlapping ranges between
The api doesn't support any way to order these, so they are being returned in
db order. In essex we retrieved each network individually, but now they are
retrieved together. I believe the following will fix your issue:
diff --git a/nova/network/manager.py b/nova/network/manager.py
index
Hi again,
I won't have access again to the system till Monday so I will test it then,
but a colleague of mine just told me (he is just trying the same set up
with similar issues):
when virtual machine is booting on the compute node, on the controller node
i can see the following:
Hi all -
We plan to have a Folsom branch release of the documentation in the
next few days. The CI Team is doing the work to cut a stable/folsom
branch for openstack-manuals.
To make it, I followed the steps in
http://wiki.openstack.org/Documentation/Release.
So from now on, the master branch is
Thanks, will these changes ever be added back to the later releases?
Yi
On Fri, Nov 9, 2012 at 1:02 PM, Vishvananda Ishaya
vishvana...@gmail.com wrote:
The api doesn't support any way to order these, so they are being returned in
db order. In essex we retrieved each network individually, but
Pardon me, the bottom line should have said, propose it into trunk and backport
it (into folsom/stable). So the answer to your question is yes.
Vish
On Nov 9, 2012, at 3:22 PM, Yi Sun beyo...@gmail.com wrote:
Thanks, will these changes ever be added back to the later releases?
Yi
Hey Everyone,
So, I was trying to run only a single test from Tempest, and I
naively tried the usual nosetest syntax of;
nosetests -v
tempest.tests.compute.servers.test_server_actions:ServerActionsTestBase.test_resize_server_confirm
No dice, so, I then tried the slightly more bulky but
To run a single test from Tempest:
~/openstack_projects/tempest$ nosetests -sv
tempest/tests/compute/flavors/test_flavors.py
The expected flavor details should be returned ... ok
Ensure 404 returned for non-existant flavor ID ... ok
flavor details are not returned for non existant flavors ... ok
Test_server_actions.py
~/openstack_projects/tempest$ nosetests -sv
tempest/tests/compute/servers/test_server_actions.py
The server's password should be set to the provided password ... SKIP: Change
password not available.
Negative Test: The server reboot on non existent server should return ...
Hey Ravi,
Cool, and how do you run (say) only test_reboot_server_hard from
ServerActionsTestBase ?
Whenever I try, I get;
stack@DevStack:~/tempest$ nosetests -sv
tempest.tests.compute.servers.test_server_actions.py:ServerActionsTestBase.test_reboot_server_hard
The server should be power
Hi,
In my setup metadata_ip is controller ip.
I am able to ping to controller from network node.
Regards,
Veera.
On Fri, Nov 9, 2012 at 7:02 PM, Choe, Cheng-Dae white...@gmail.com wrote:
First. Ping to your metadata_ip in network router namespace.
2012년 11월 9일 금요일에 Veera Reddy님이 작성:
Hi
at 20121109
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/24/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 08:04:19 -0500Build duration:2 min 43 secBuild cause:Started by an SCM changeBuilt
at 20121109
Title: precise_grizzly_python-keystoneclient_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_python-keystoneclient_trunk/7/Project:precise_grizzly_python-keystoneclient_trunkDate of build:Fri, 09 Nov 2012 08:07:02 -0500Build duration:3 min 34
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/7/Project:precise_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 08:10:37 -0500Build duration:2 min 51 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_horizon_trunk/9/Project:precise_grizzly_horizon_trunkDate of build:Fri, 09 Nov 2012 08:11:54 -0500Build duration:3 min 4 secBuild cause:Started by an SCM changeBuilt
at 20121109-0824Build needed 00:03:30, 11280k disc spaceERROR:root:Error occurred during package creation/build: Command
Title: raring_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/8/Project:raring_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 08:14:58 -0500Build duration:11 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/55/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 08:17:57 -0500Build duration:19 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/57/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 08:24:29 -0500Build duration:29 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/56/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 10:31:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/25/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 12:01:21 -0500Build duration:1 min 57 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/57/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:01:24 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/59/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:01:25 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/58/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:31:29 -0500Build duration:14 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/60/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 12:31:24 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt
at 20121109
at 20121109-1309Build needed 00:03:56, 11288k disc spaceERROR:root:Error occurred during package creation/build
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/59/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 13:01:24 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/61/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 13:01:27 -0500Build duration:17 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/8/Project:precise_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 14:01:22 -0500Build duration:1 min 49 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_glance_trunk/9/Project:raring_grizzly_glance_trunkDate of build:Fri, 09 Nov 2012 14:01:22 -0500Build duration:10 minBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_quantum_trunk/27/Project:precise_grizzly_quantum_trunkDate of build:Fri, 09 Nov 2012 14:31:22 -0500Build duration:2 min 20 secBuild cause:Started by an SCM changeBuilt
at 20121109
at 20121109-1534Build needed 00:01:49
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/62/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 16:01:28 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/64/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 16:01:28 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/65/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 18:01:24 -0500Build duration:16 minBuild cause:Started by an SCM changeBuilt
at 20121109
Title: precise_folsom_python-keystoneclient_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_folsom_python-keystoneclient_trunk/68/Project:precise_folsom_python-keystoneclient_trunkDate of build:Fri, 09 Nov 2012 22:31:21 -0500Build duration:3 min 18
at 20121109-2236Build
on:pkg-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRewrite initial migrationby dolph.mathewseditkeystone/common/sql/migrate_repo/versions/001_add_initial_tables.pyConsole Output[...truncated 44420 lines...]Finished at 20121109-2241Build needed 00:02:55
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/64/Project:precise_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 23:01:23 -0500Build duration:13 minBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/66/Project:raring_grizzly_nova_trunkDate of build:Fri, 09 Nov 2012 23:01:25 -0500Build duration:15 minBuild cause:Started by an SCM changeBuilt
77 matches
Mail list logo
