Hi,
There was also talk of having neutron as the default network setting. Do we
still want to move towards this in devstack? I know that Yong is working on a
solution for having the multi node support for the floating IP's.
At the last summit I was going to look into the option of doing a live
Hi,
There are a number of ways of going about this:
1. You can run devstack (www.devstack.orghttp://www.devstack.org). This
is from the sources.
2. You can do installation via the manuals
3. RDO also has a very nice and easy way of going about things - it make
use of
On 06/19/2013 07:13 PM, Mark McClain wrote:
All-
The OpenStack Networking team is happy to announce that the Quantum project
will be changing its name to Neutron. You'll soon see Neutron in lots of places
as we work to implement the name change within OpenStack.
I hope that Nickelodeon does
On 05/21/2013 07:04 AM, Qinglong.Meng wrote:
Hi all,
Here is output of cmd 'ovs-vsctl show'. But how to explain it. Can
anybody help me?
Please look at the following diagram to see how the VM connects to the
OVS when using the Hybrid driver:
On 05/21/2013 06:34 AM, Qinglong.Meng wrote:
Hi friends,
the nova-compute log say 'brctl addif qbr876fed87-40
qvb876fed87-40' error, when I reboot the server by 'init 6', and the
nova-compute service
Can you please clarify which server you reboot?
Please loot at
On 04/27/2013 12:44 PM, Michaël Van de Borne wrote:
Anybody has an idea about why the nova metadata server rejects the VM
requests?
Hi,
Just a few questions:-
1. Can you please check /etc/quantum/metadata_agent.ini to see that you
have the correct quantum keystone credential configured?
2.
On 04/11/2013 01:59 PM, Arindam Choudhury wrote:
Hi,
I am trying to install openstack folsom on fedora 18. while installing
quantum I am having this problem:
# cat dhcp-agent.log
2013-04-11 12:53:31 INFO [quantum.common.config] Logging enabled!
2013-04-11 12:55:39ERROR
this option will include in Grizzly. We get
now (since the switch to Quantum) network I/O bottlenecks without
using all NIC's of our nodes.
So I'm looking forward to Grizzly
Greetings
Heiko
Am 12.12.2012 17:11, schrieb Gary Kotton:
On 12/12/2012 05:58 PM, Xin Zhao wrote:
Hello,
If I
On 03/20/2013 06:16 PM, Sylvain Bauza wrote:
Hi,
As per https://bugs.launchpad.net/quantum/+bug/1155050 and also other
litterature, I do see doc alerts saying that Quantum L3 and DHCP
agents must be on different hosts.
Let me be honest, I successfully installed and configured both on the
On 03/18/2013 05:14 AM, tommy(??) wrote:
more:
means we can not command : quantum component-list
This command was replaced by quantum agent-list. Please note that you
need to an admin user to be able to invoke this.
Thanks
Gary
Thanks,
Tommy Bao
2013/3/18 tommy(??) bychya...@gmail.com
Hi,
I'd like to run for the Technical Committee in the up and coming elections.
I am a Principle Software Engineer at Red Hat. I have been actively
developing OpenStack since the Essex release. I am currently a Quantum
core developer. In addition to this I am also core on the Stable
On 03/12/2013 12:13 AM, Greg Chavez wrote:
So I'm setting up Folsom on Ubuntu 12.10, using the Github Folsom
Install Guide:
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
After following the steps to instantiate the
? Thanks!
Yes, that is correct. Even the first time that it starts it is out of
sync :)
On Tue, Mar 12, 2013 at 3:18 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
On 03/12/2013 12:13 AM, Greg Chavez wrote:
So I'm setting up Folsom on Ubuntu 12.10, using
On 03/04/2013 05:45 PM, Guilherme Russi wrote:
Found the problem, when I did the step: ovs-vsctl add-port br-ex eth2,
it stopped my lan communication.
The l3 agent makes changes to the routing table. This may cause a
conflict with the default gateway. I would suggest having a static route
Hi Greg,
Sorry to hear you woes. I agree with you that setting things up is
challeniging and sometimes problematic. I would suggest a number of things:
1. Give devstack a bash. This is very helpful and useful to try and
understand how everything fits and works together. www.devstack.org
2. A
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following Provided Router/single tenancy setup.
So, at reboot, my tap/qg/qr network interfaces were down :
7: qg-c39e5df4-7f: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN
On 02/19/2013 03:47 PM, Sylvain Bauza wrote:
Le 19/02/2013 13:31, Gary Kotton a écrit :
On 02/19/2013 01:57 PM, Sylvain Bauza wrote:
Hi,
I progressed in investigating the bug. I forgot to mention I was
following Provided Router/single tenancy setup.
So, at reboot, my tap/qg/qr network
On 02/11/2013 06:58 PM, Pádraig Brady wrote:
A quick search suggests that kernel has CONFIG_BRIDGE=n set.
So I presume there another method is possible through config.
Gary any ideas?
Please look at https://bugzilla.redhat.com/show_bug.cgi?id=877704. For
some reason the the bridge module is
On 02/11/2013 07:26 PM, Greg Chavez wrote:
Solution:
[root@kvm-cs-sn-10i nova]# modprobe -r brcompat
[root@kvm-cs-sn-10i nova]# modprobe bridge
[root@kvm-cs-sn-10i nova]# brctl show
bridge namebridge idSTP enabledinterfaces
Still can't boot a VM... looking into the reasons now.
Could this be
+1
On 01/23/2013 05:51 PM, Joe Gordon wrote:
+1
On Wed, Jan 23, 2013 at 7:58 AM, Chris Behrens cbehr...@codestud.com
mailto:cbehr...@codestud.com wrote:
+1
On Jan 22, 2013, at 5:38 PM, Matt Dietz matt.di...@rackspace.com
mailto:matt.di...@rackspace.com wrote:
All,
in
the stable version.
Thanks,
Gabriel
*From:* Gary Kotton gkot...@redhat.com
*To:* jian@canonical.com
*Cc:* openstack@lists.launchpad.net
*Sent:* Wednesday, January 23, 2013 10:08 AM
*Subject:* Re: [Openstack] Is the Quantum
On 01/22/2013 07:02 PM, Jian Wen wrote:
On 2013?01?22? 10:56, Balamurugan V G wrote:
Hi,
In an Openstack deployment using Quantum, the compute nodes access
the public/external network via the network node (as per the diagram
On 01/24/2013 12:02 AM, mohammad kashif wrote:
Hi
I have a running Essex OpenStack cluster on Ubuntu with multi host
network set up. Floating IP etc is working. I am planning to install
same kind of setup with Folsom on RHEL 6.3 and quantum. I have some
questions
Most of the documents
Hi,
In order to be able to help can you please provide the following
information:
1. Which plugin are you using? I assume that it is OpenvSwitch from the
link :)
2. Are all of the Quantum services running:
- quantum-server
- quantum-openvswitch-agent
- quantum-dhcp-agent
3. Can you
you!
Thiago
On 3 January 2013 06:38, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
In order to be able to help can you please provide the following
information:
1. Which plugin are you using? I assume that it is OpenvSwitch
from the link :)
2
On 12/29/2012 06:16 AM, Dennis Jacobfeuerborn wrote:
Hi,
I've successfully setup a single machine openstack environment including
quantum with a provider router configuration (openvswitch). The Problem is
that I cannot reach the internet from the VMs.
The reason apparently is that the default
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
On 12/13/2012 12:07 PM, ZhiQiang Fan wrote:
i can ping and ssh into instance with private ip and floating ip
instance can ping the control node ip, but cannot ping the compute
node and any external network
In order to be able to help would it be possible that you provide IP
addresses and
On 12/12/2012 05:58 PM, Xin Zhao wrote:
Hello,
If I understand it correctly, multi-host network mode is not supported
(yet) in quantum in Folsom.
I wonder what's the recommended way of running multiple network nodes
(for load balancing and
bandwidth concerns) in quantum? Any documentation
On 12/11/2012 09:50 AM, Trinath Somanchi wrote:
Hi-
I have the following first set of doubts regarding the Folsom Quantum
[1] With regard of Quantum Plug-in, How does the RPC communication
take place between the Agent and the plug-n ? In the source code,
ovs_quantum_plugin.py, I find the
to the methods then
the base classes methods will be invoked.
Thanks
Gary
Will ovs plugin will not consider the implementation of port and
subnet? If it considers, where these are happening?
Kindly help me understand the same.
Thanks in advance
-
Trinath
On Sun, Dec 9, 2012 at 5:19 PM, Gary Kotton
On 12/11/2012 11:38 AM, Trinath Somanchi wrote:
Hi-
Thanks for the reply. I still have some more doubts ... please find
then inline.
Kindly help me understand these...
On Tue, Dec 11, 2012 at 2:59 PM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
On 12/11/2012 09
Hi Trina,
I am not really sure that I understand your question. The Quantum
service marshals the API's to a plugin. The plugin is responsible for
providing the virtual network service. In the case of the OVS plugin the
ovs_quantum_plugin.py will treat the API calls. That means that it will
On 11/25/2012 07:24 PM, Lance Haig wrote:
Hi,
I want to build an OpenStack all in one server with devstack or by
hand I don't mind.
I want to host some VM's with persistant storage and some without.
I also can only get ipv6 /64 address range for my server so need to
know if OpenStack
On 11/23/2012 05:15 PM, Jian Hua Geng wrote:
Hi,
I am using the Quantum on Folsom release, does it still support auto
assign floating ip to a vm just list the nova-network did?
If the answer is yes, how to implement it?
Hi,
I am not familiar with the auto assign feature. At the moment the
On 11/21/2012 10:28 PM, Paras pradhan wrote:
Hi all
I am following this tutorial
https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst
When I start the instance, it starts well but it doesnot get the IP
however I can see the ip
Hi,
A considerable effort has been made to close a number of problems in
the Folsom release.
The list of issues addressed can be seen at
https://review.openstack.org/#/q/status:merged+project:openstack/quantum+branch:stable/folsom,n,z
There are still a few bug fixes in
On 11/15/2012 04:30 PM, Samuel Winchenbach wrote:
Hi All,
I am looking for a good guide to help me get started with Folsom and
Quantum for either 12.04 or 12.10.
Please look at
http://docs.openstack.org/trunk/openstack-network/admin/content/index.html.
There is a demo section.
You can
On 11/15/2012 05:22 PM, Skible OpenStack wrote:
Can you please tell me what type of networking are you using ? VLAN or
GRE ?
In the examples we are using VLAN.
Le 15/11/2012 16:16, Gary Kotton a écrit :
On 11/15/2012 04:30 PM, Samuel Winchenbach wrote:
Hi All,
I am looking for a good
Does anyone have an idea about the date ?
I am not sure if anyone is working on this. You are welome to add
the support. It would be great.
Le 15/11/2012 16:14, Gary Kotton a crit:
Hi
On 11/07/2012 11:47 AM, Aniruddha Khadkikar wrote:
Hi Stackers,
We have a small Openstack lab using three servers. The components are
distributed as:
1. Network controller - Quantum L3 DHCP, L2 agent, Nova, Openvswitch
2. Cloud controller - Quantum server, L2 agent, Nova, Openvswitch,
Hi,
The bug has been fixed upstream and is merged into the stable folsom
branch. Please note that this may not have been packaged by the various
linux distributions.
If you need to fix this locally then please look at
It would also be nice if one could change configuration settings at run
time instead of having to restart a process.
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
On 11/04/2012 04:45 PM, Nah, Zhongyue wrote:
https://blueprints.launchpad.net/nova/+spec/deployer-friendly-confs
This blueprint seems to be planning to implement what is being discussed for
Nova.
Great.
I assume that this will be done in OpenStack Common so that all of the
users of the
On 10/29/2012 02:59 AM, Asher Newcomer wrote:
+1
On Sun, Oct 28, 2012 at 8:39 PM, Russell Bryant rbry...@redhat.com
mailto:rbry...@redhat.com wrote:
On 10/28/2012 08:19 PM, David Kang wrote:
I agree that subject prefix is a way.
There are pros and cons of either approach.
On 10/26/2012 03:56 PM, Gurjar, Unmesh wrote:
Hi,
I can think of two alternative solutions for maintaining uniqueness:
1.DB look up: After generating a new MAC address, checking uniqueness
by doing a DB look up.
The Quantum code ensure that the MAC address generated is unqiue. This
is
Hi,
In addition to Dan's comments you can also take a look at the following
link http://wiki.openstack.org/ConfigureOpenvswitch.
Thanks
Gary
On 10/24/2012 08:21 AM, livemoon wrote:
Thanks Dan
On Wed, Oct 24, 2012 at 2:15 PM, Dan Wendlandt d...@nicira.com
mailto:d...@nicira.com wrote:
On 10/18/2012 05:42 PM, Lars Kellogg-Stedman wrote:
The good news is that since replacing qpid with rabbitmq our
environment seems to have stabilized to the point that it's *almost*
useful.
Can you please explain the problems that you had with qpid?
The last remaining issue is that dnsmasq
On 10/12/2012 03:37 PM, Srikanth Kumar Lingala wrote:
*/overlaps with another subnet/*
HI,
There is a configuration variable that allows you to do this:
allow_overlapping_ips. By default this is False. Can you please try
setting it to True.
Thanks
Gary
On 10/20/2012 07:23 PM, Tim Bell wrote:
If we purchase an OUI, is there a mechanism within Quantum to only
allocate Mac addresses with that prefix ?
At the moment Quantum enables the user to define a base MAC address.
That is the user can update the configuration file. The user selects a
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Hi,
I am writing to announce my candidacy for the PTL for Quantum for the
Grizzly release. A quantum leap has been made with the up and coming
Folsom release. Dan and the guys have done a tremendous job. More
challenges await us in Grizzly. I started working on Quantum towards the
end of
On 09/03/2012 08:47 PM, rob_hirschf...@dell.com wrote:
Dan,
The challenge here is how to wean off one code base (Nova Net) and into another
(Quantum).
My thinking was that we'd be able to have more shared components and possibly
shared code. This could ease the transition by having
On 09/04/2012 12:03 PM, Takaaki Suzuki wrote:
Hi
Currently, I see that DHCP instance is created per network, at least
from looking at the Dnsmasq implementation.
I'm curious to know how a DHCP instance can provide services to a VM
attached to a port on a network that has multiple subnets.
It
On 09/04/2012 12:48 PM, Takaaki Suzuki wrote:
Hi Gary
Thank you for your support.
I share with you information.
Can you also please provide sudo ovs-vsctl show?
Thanks
Gary
1. can you please do quantum port-list?
quantum --os_token f095d7163a564456b60bf47b078537a7 --os_url
On 09/04/2012 12:56 PM, Takaaki Suzuki wrote:
Can you also please provide sudo ovs-vsctl show?
sure.
It looks like a bug. I'll investigate further and let you know.
Thanks
Gary
midokura16:~/devstack# ovs-vsctl show
d699f1f2-792c-4eb9-8306-32a622316389
Bridge br-tun
Port
Hi,
Just a few more questions:
1. Can you send me the results of ps aux |grep dnsmasq
2. Can you also please send the ifconfig. The tap devices for also ip
address. Can you please send me ip addr. (my gut feeling is that we do
not configure 192.168.30.2 but rather 192.168.10.2.
Thanks
Gary
On
Hi,
I have managed to find the problem :). I have spent the whole day on
this :(.
I was running devstack and the code executes ovs_quantum_agent.py.
Whilst going through the mailing mails I came upon this mail and saw
that you are calling quantum-openvswitch-agent.
I'll post a fix soon.
On 08/23/2012 10:16 AM, Trinath Somanchi wrote:
Hi -
Rather than using this installation for every different package can I
use devstack's stack.sh script to install the Openstack latest
milestone release?
devstack does not use the installation packages. This uses the git
repositories. By
On 08/13/2012 08:42 AM, balaji patnala wrote:
Hello Thierry,
Can we download Folsom branch codebase for understanding Quantum and
other changes in Folsom release?
You can get the code at git://github.com/openstack/quantum.git.
If you would like to see the status of things regarding F-3 then
On 07/23/2012 11:02 AM, Dan Wendlandt wrote:
On Sun, Jul 22, 2012 at 5:51 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
This is an interesting idea. In addition to the creation we will
also need the update. I would prefer that the agents would have
one
On 07/19/2012 07:11 PM, Dan Wendlandt wrote:
On Wed, Jul 18, 2012 at 5:17 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
On 07/18/2012 04:23 AM, Dan Wendlandt wrote:
Hi Gary,
Removing much of the thread history, as I think we agree on the
high-level goals
On 07/18/2012 04:23 AM, Dan Wendlandt wrote:
On Mon, Jul 16, 2012 at 3:30 AM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
The patch https://review.openstack.org/#/c/9591/ contains the
initial support for the scalable agents (this is currently
16, 2012 at 10:05 PM, Gary Kotton gkot...@redhat.com
mailto:gkot...@redhat.com wrote:
Hi,
If the name is intended to be a description then how about the
idea of calling the field description instead. This is far
more descriptive and does not lend the user
Hi,
The patch https://review.openstack.org/#/c/9591/ contains the initial
support for the scalable agents (this is currently implemented on the
linux bridge). At the moment this does not support a network or port
update, that is, the user can set 'admin_status_up' to 0. This means
that either
Hi,
If the name is intended to be a description then how about the idea of
calling the field description instead. This is far more descriptive
and does not lend the user to think that this should be unique.
Thanks
Gary
___
Mailing list:
or not ? Why do you need --public True ?
That just adds confusion...
Endre.
2012/7/12 Gary Kotton gkot...@redhat.com mailto:gkot...@redhat.com
Hi,
1. Is this also applicable to the agents? Say for example a
user wants to ensure that a public network is attached
Hi,
1. Is this also applicable to the agents? Say for example a user wants
to ensure that a public network is attached to network interface em1 and
the private network attached to em2. Is this something that will be
addressed by the blueprint?
2. I prefer option #3. This seems to be a cleaner
--public True ? That just
adds confusion...
Endre.
2012/7/12 Gary Kotton gkot...@redhat.com mailto:gkot...@redhat.com
Hi,
1. Is this also applicable to the agents? Say for example a user
wants to ensure that a public network is attached to network
interface em1 and the private network
Hi,
Anyone having problems with gerrit?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Hi,
Following the Quantum IRC meeting last night below is an update of the
stable essex additions:
Cherry picks approved and integrated:
https://github.com/openstack/quantum/commit/b226e0c7e91e7089286e0977f7e0f185afe2964f
Hi,
I am in the process of integrating the RPC code from OpenStack common
into Quantum. I initially started working with qpid as the backend
implementation. I ran into problems due to the fact that
control_exchange is defined as 'nova'. This is in
quantum/openstack/common/rpc/__init__.py
On 07/10/2012 06:29 PM, Eric Windisch wrote:
In addition to this I have a few additional questions and or concerns:
1. When we import code from openstack common the test cases for the
modules are not imported (maybe I missed something with running setup).
When the code is copied the imports are
Hi,
In Quantum we make use of a number of different configuration files. A
quantum plugin may have one or more configuration files. An example of
the configuration files is below.
/etc/quantum/quantum.conf
/etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
When the quantum service
Hi,
Does anyone know what can cause the failure below:
Started by userOpenStack Hudson
https://jenkins.openstack.org/user/hudson-openstack
[EnvInject] - Preparing an environment for the build.
Building remotely onprecise6 https://jenkins.openstack.org/computer/precise6
in workspace
Hi,
Anyone encountered any problems. When I try to access the server
(https://review.openstack.org/) I get:
Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request /GET /
https://review.openstack.org//.
Reason:
Hi,
It seems that this has stopped working today. Any ideas?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help :
Hi,
Is anyone aware of a problem with Jenkins?
Thanks
Gary
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Hi,
Quantum has moved to openstack common configuration (the plugin.ini file
no longer exists). Support has been added to devstack to ensure that
quantum and devstack will work irrespective of the version running.
Would it be possible to review this so that we can move forward with the
On 06/07/2012 11:39 AM, Neelakantam Gaddam wrote:
Hi All,
Currently, I don't see any Quantum UI in Horizon in Essex. Does the
Horizon support Quantum UI in the current release? If so, please share
the configuration steps. If not, When can I expect the Quantum UI
integration with Horizon ?
Hi Monty and Dan,
Background: A short while ago I started to port bug fixes for Quantum
from Folsom-1 to Stable Essex. Jenkins did not accept the patches due to
the fact that the automatic tests did not pass. The failures are due to
2 reasons:
1. pep8 checks (addressed in the tox.ini)
2.
On 06/05/2012 04:29 PM, Monty Taylor wrote:
On 06/05/2012 07:54 AM, Gary Kotton wrote:
Hi Monty and Dan,
Background: A short while ago I started to port bug fixes for Quantum
from Folsom-1 to Stable Essex. Jenkins did not accept the patches due to
the fact that the automatic tests did not pass
On 06/01/2012 12:47 AM, Russell Bryant wrote:
On 05/31/2012 04:21 PM, Mark McLoughlin wrote:
I expect to do a pretty detailed review of the patch to add rpc to
openstack-common and make some API design recommendations. But I think
we'll have to balance some of those design ideas between stuff
On 05/16/2012 12:24 AM, Salman Malik wrote:
Hi Guys,
I am having trouble with launching instances. The launch fails on
networking task with status error. Here is the output (at nova-compute
screen session) on launching instance :
2012-05-02 06:41:52 TRACE nova.rpc.amqp RemoteError: Remote
Hi,
This morning I encountered a problem (which did not happen a few days
ago :)). When devstack is launched, with quantum configured, the gateway
and bridge devices are created. This causes problems with quantum.
For example when devstack is up and running prior to deploying an
instance we
-Original Message-
From: openstack-bounces+eperdomo=cisco@lists.launchpad.net
[mailto:openstack-bounces+eperdomo=cisco@lists.launchpad.net] On
Behalf Of Gary Kotton
Sent: Monday, May 14, 2012 11:01 PM
To: openstack@lists.launchpad.net
Subject: [Openstack] [devstack/quantum] Configuration
Hi,
https://review.openstack.org/#/c/7169/ ensures that all of the open
source agents have uniform database access. This requires a minor change
to the devstack code.
In addition to this I have added in some minor chnages which ensure that
the devstack user is able to run Quantum Plugins and
Hi,
Great document. Would it be possible to add in other flavours of Linux
that support Open Stack?
Thanks
Gary
On 05/07/2012 03:23 PM, Eric Dodemont wrote:
I have written a 50 pages document: Install Your Own OpenStack Cloud
- Essex Edition.
The PDF file can be downloaded here:
Brilliant!
From: openstack-bounces+garyk=radware@lists.launchpad.net
[mailto:openstack-bounces+garyk=radware@lists.launchpad.net] On
Behalf Of Joshua Harlow
Sent: Wednesday, January 18, 2012 9:21 PM
To: Mark McLoughlin
Cc: Andy Smith; openstack
Subject: Re: [Openstack] Proposal for new
Hi,
When I connect to the dashboard after a devstack installation I get the
following error:
Unable to get service info: This error may be caused by a misconfigured
Nova url in keystone's service catalog, or by missing openstackx
extensions in Nova. See the Horizon README.
A little
Hi,
I too have encountered the problem in the past. Maybe the attached mail
may help.
Thanks
Gary
From: openstack-bounces+garyk=radware@lists.launchpad.net
[mailto:openstack-bounces+garyk=radware@lists.launchpad.net] On
Behalf Of Leander Bessa
Sent: Tuesday, January 10, 2012 6:22 PM
Hi,
Will this module sync the configurations between the different nodes in
the system? That is, if the cloud has a number of Compute modules
running. Will the updated configuration on one of them be replicated to
the additional nodes? If so then this is great, if not, would it be
possible to
93 matches
Mail list logo
