Thanks Razique,
I still need to edit the official HA doc to give details about this
setup, I don't really have the time this week.
I hope I can save some time before the end of the year.
Cheers!
--
Regards,
Sébastien Han.
On Tue, Dec 18, 2012 at 12:13 AM, Razique Mahroua
Hi guys!
I'm not migrating from Essex to Folsom. I've just done a clear installation
of Folsom 2012.2 from EPEL 6.7.
Then, it could be a problem related to migration.
I requested catalog from keystone-cli and it worked. Hence, exception seems
to be around this extraction:
File
On 12/18/2012 09:35 AM, JuanFra Rodriguez Cardoso wrote:
Hi guys!
I'm not migrating from Essex to Folsom. I've just done a clear
installation of Folsom 2012.2 from EPEL 6.7.
Then, it could be a problem related to migration.
I requested catalog from keystone-cli and it worked. Hence, exception
Ok, Matthias. Sorry for confusion, I decided to re-install Folsom 2012.2 in
a parallel testbed. In this way, I avoided any incompatibility with
migration from Essex.
I continue researching and I will report us, ok?
Thanks! ;)
2012/12/18 Matthias Runge mru...@redhat.com
On 12/18/2012 09:35 AM,
Ryan Lane wrote:
I've just finished importing the content from the MoinMoin wiki into the
MediaWiki instance. Please check the content:
https://wiki-staging.openstack.org/wiki/Main_Page
[...]
Also note that the migration script doesn't map from MoinMoin to
MediaWiki perfectly and we'll
Hi guys!
No problem at all. It's just solved. It was an own mistake related to wrong
passwords (in YAML config file).
Sorry for any inconvenience.
Thanks a lot anyway!
JuanFra.
2012/12/18 Jian Wen wenj...@canonical.com
On 2012年12月18日 09:29, YuXingchao wrote:
Hi, JuanFra. This usually
Great articles/guides guys!
Appreciated and useful material for production deployments.
Thanks!
JuanFra.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More
One more thing I spotted around links.
In the migrated wiki:
[[XenServer/DevStack|XenServer and [[DevStack
Clearly it's a simple fix to this:
[[XenServer/DevStack|XenServer and DevStack]]
I guess this extra link (that is obviously not valid syntax, and wasn't in the
original page) got
Hi,
Thanks for looking into this.
I'll file a bug and fix.
Thank you
Gary
On 12/17/2012 10:38 AM, Liu Wenmao wrote:
the local vairable *physical_network* should be *alloc.physical_network*
I suggest to add some error output to the logger
root@controller:~# quantum-server --config-file
Hi Stackers,
For your information, a new documentation is now available [1] :
Installation and configuration for testing-sized systems.
The purpose of this work is to explain how to install a 3 nodes
(controller + network + compute) setup from Ubuntu Packages (Folsom),
and understand how to
Thanks for links Sébastien.
Is using pacemaker/corosync (as opposed to haproxy + keepalived) for the
opensource services the preferred method for making openstack HA? Also is
it possible with pacemaker to run the services in an Active/Active
configuration with load balancing? Pardon my
On 12/18/2012 12:17 AM, Thierry Carrez wrote:
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is nothing Ubuntu-specific
Thomas Goirand wrote:
On 12/18/2012 12:17 AM, Thierry Carrez wrote:
Thomas Goirand wrote:
[No pun intended, but it'd be nice if stackers had a bit more
consideration for our work in Debian, and stop thinking only with
Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, Ubuntu, ... in mind.]
There is
On 12/18/2012 05:29 PM, Sascha Peilicke wrote:
On 12/17/2012 04:47 PM, Thomas Goirand wrote:
This
means that absolutely all of our packages have to embed a patch in
debian/patches to fix the wrong MANIFEST.in.
We've spent quite some time on that. Or rather, should I say: it's a
real time
The most obvious issue is how ugly the new main page is :) The loss of
image inclusion and columns transformed an admittedly not perfect page
(disclaimer: I authored it) into something unreadable and very
unwelcoming. Note that it's probably the only page that uses column
layout, so maybe we
I'm relatively new to this group, but have a question that I believe may
already have been answered. Is there a matrix comparison between the elements
of Swift vs. Amazon's S3 interface? Specifically around: provisioning,
authentication, appending, etc. Anything that someone could point me
On Tue, Dec 18, 2012 at 2:21 AM, John Garbutt john.garb...@citrix.comwrote:
One more thing I spotted around links.
In the migrated wiki:
[[XenServer/DevStack|XenServer and [[DevStack
Clearly it's a simple fix to this:
[[XenServer/DevStack|XenServer and DevStack]]
I guess this extra
On Tue, Dec 18, 2012 at 10:41 AM, Joe Warren-Meeks
joe.warren.me...@gmail.com wrote:
Hi guys,
I've created a windows 2012 image and uploaded it ok. Pretty much
following this example:
http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-a-windows-image.html
When I go
Countless times I'm here trying to make my openstack runnig! So here we go
again!
My set up is a
nova-network-hahttp://docs.openstack.org/trunk/openstack-compute/admin/content/existing-ha-networking-options.html,
so each of my nodes run a nova-{api-metadata,network,compute,volume}, my
controller
Hey everybody,
We're trying very hard to build an Openstack cluster here, and I've been
running into some trouble with the Keystone LDAP identity backend. I have
every expectation that this is just something I have misconfigured, but
honestly the documentation seems somewhat lacking for this,
On 12/18/2012 01:41 PM, Joe Warren-Meeks wrote:
Hi guys,
I've created a windows 2012 image and uploaded it ok. Pretty much following
this
example:
http://docs.openstack.org/trunk/openstack-compute/admin/content/creating-a-windows-image.html
When I go to launch an instance, it works ok
I suspended instances and rebooted one of my compute nodes, but not compute
wont start up. Appears to be the checks of the machine images that fails.
Libvirt has found the instances and started them back up, and compute
checks them out and gets through 4 of 6 instances, then bombs:
From
Hi,
I've installed the Windows 2012 Datacenter Edition in our Testing Cloud
running Folsom and it's working very well : I can RDP the VM, and also
use VNC inside the dashboard.
I've created the image using VirtIO driver both for storage and network.
The Disk Format is RAW and the Container
Make sure you're specifying a tenant (e.g. OS_TENANT_NAME) in order to
receive authorization (e.g. the admin role) to perform nova list. You can
debug the authn/authz process using keystone token-get (this doc is for
folsom, but should work for essex, although the arguments may have changed,
check
On 12/18/2012 09:43 PM, Greg C wrote:
I suspended instances and rebooted one of my compute nodes, but not compute
wont start up.
From nova-compute.log:
2012-12-18 12:38:16 TRACE nova File
/usr/lib/python2.7/dist-packages/nova/virt/images.py, line 56, in
qemu_img_info
2012-12-18
Yes!, that was it. Had a failed snapshot (zero size, so I assume it
failed). Removed it with qemu-img, and now we are back online. Thanks.
On Tue, Dec 18, 2012 at 5:03 PM, Pádraig Brady p...@draigbrady.com wrote:
On 12/18/2012 09:43 PM, Greg C wrote:
I suspended instances and rebooted one
at 20121218
at 20121218-1011Build needed 00:06:22, 46672k disc spaceERROR:root:Error occurred during package creation/build
at 20121218
at 20121218
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/309/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 11:35:05 -0500Build duration:7 min 22 secBuild cause:Started by an SCM changeBuilt
-builderHealth ReportWDescriptionScoreBuild stability: All recent builds failed.0ChangesRemove the deprecated quantum v1 code and directory.by yaguang.tangdeletenova/network/quantum/nova_ipam_lib.pyConsole Output[...truncated 12047 lines...]Finished at 20121218-1146Build needed 00:04:26, 101484k disc
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/310/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 12:31:05 -0500Build duration:6 min 48 secBuild 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/313/Project:raring_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 12:31:05 -0500Build duration:8 min 50 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/311/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 13:31:03 -0500Build duration:7 min 18 secBuild 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/314/Project:raring_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 13:32:06 -0500Build duration:9 min 9 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/313/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 15:01:06 -0500Build duration:6 min 26 secBuild 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/317/Project:raring_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 15:31:03 -0500Build duration:8 min 16 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_glance_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_glance_trunk/61/Project:precise_grizzly_glance_trunkDate of build:Tue, 18 Dec 2012 16:31:02 -0500Build duration:10 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/316/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 17:01:15 -0500Build duration:6 min 40 secBuild 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/319/Project:raring_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 17:01:04 -0500Build duration:8 min 25 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/317/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 19:01:07 -0500Build duration:6 min 28 secBuild 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/320/Project:raring_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 19:01:07 -0500Build duration:8 min 50 secBuild cause:Started by an SCM changeBuilt
at 20121218
at 20121218
Title: precise_grizzly_nova_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/318/Project:precise_grizzly_nova_trunkDate of build:Tue, 18 Dec 2012 21:31:03 -0500Build duration:5 min 56 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_quantum_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/136/Project:raring_grizzly_quantum_trunkDate of build:Wed, 19 Dec 2012 02:31:01 -0500Build duration:7 min 51 secBuild cause:Started by an SCM changeBuilt
47 matches
Mail list logo
