Hi,
Do any of you know if there is anybody working on a Quantum plugin for
VMWare ESXi? And if yes, when it may be available?
Regards,
Balu
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe :
Hi all:
I have some issue about nova-volume network(public eth0 change to private eth1).
I use openstack essex version.
My Environment :
Muti-host network
Public ip : 192.168.1.0/24
Private ip : 192.168.2.0/24
Controller has nova-volume partition.
public: 192.168.1.50 private:192.168.2.2
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
Anybody has any pointers on this regard ?
Thank you,
On Fri, Mar 8, 2013 at 10:09 PM, Ashutosh Narayan
aashutoshnara...@gmail.com wrote:
Hi folks,
I am following these
instructionshttp://docs.openstack.org/trunk/openstack-compute/install/yum/content/compute-verifying-install.html
but
Only changing the VM MTU to 1454 does the trick ('ifconfig eth0 mtu 1454').
I think this is the same issue:
https://bugs.launchpad.net/quantum/+bug/1075336
So instead of decreasing the MTU on the physical interface you could also
increase it on the openvswitch port.
Cheers,
Robert
hi.
I'm sorry can not reply to the original letter.
openvswitch and brctl can run normal together in RHEL6.3.
error message:
ProcessExecutionError: Unexpected error while running command.
Command: sudo nova-rootwrap /etc/nova/rootwrap.conf brctl addbr
qbr2218b8c4-7d
Exit code: 1
Stdout: ''
There may be some mistake exist. Just know, the vlan works as expected.
On Tue, Mar 12, 2013 at 12:02 PM, Lei Zhang zhang.lei@gmail.com wrote:
Hi all,
I am testing the nova-network + vlan + multi_host. But I found that the
ip_forward is enable automatically when launch new instances.
Hi folks,
I am trying to install dashboard as per instructions mentioned
herehttp://docs.openstack.org/trunk/openstack-compute/install/yum/content/installing-openstack-dashboard.html
.
First of all /etc/openstack-dashboard/local_settings.py file doesn't
exist instead
North America entered DST last Sunday (Europe will do the same on March
31), so we are entering DST / UTC time confusion again.
Remember that all our OpenStack online meetings are expressed in UTC
time (which does not have DST nonsense), and doublecheck what that means
for you using tools like:
On 03/12/2013 11:20 AM, Ashutosh Narayan wrote:
Hi folks,
I am trying to install dashboard as per instructions mentionedhere
http://docs.openstack.org/trunk/openstack-compute/install/yum/content/installing-openstack-dashboard.html.
First of all |/etc/openstack-dashboard/local_settings.py
Le 12/03/2013 09:20, Robert van Leeuwen a écrit :
Only changing the VM MTU to 1454 does the trick ('ifconfig eth0 mtu 1454').
I think this is the same issue:
https://bugs.launchpad.net/quantum/+bug/1075336
So instead of decreasing the MTU on the physical interface you could also
increase it
Hi,
I am trying to configuring openstack with one controller and one network
and two compute nodes.
I am not able to understand how the communication of the VM's happens which
are for the same tenant with same ip range but on the different compute
hosts.
Please help me to understand how GRE
On 03/12/2013 11:46 AM, Ashutosh Narayan wrote:
Hi Matthias,
Thanks for pointing that out. I now get a login page.
But it doesn't logs me with admin credentials,
Here is a snippet of error_log
== /var/log/httpd/error_log ==
[Tue Mar 12 10:40:16 2013] [error] unable to retrieve service
On Tue, Mar 12, 2013 at 11:24 AM, Thierry Carrez thie...@openstack.org wrote:
Remember that all our OpenStack online meetings are expressed in UTC
time (which does not have DST nonsense), and doublecheck what that means
for you using tools like:
Or for the lazy ones (i.e: most of us) who
On 03/12/2013 12:02 PM, Ashutosh Narayan wrote:
The web page keeps on waiting and error_logs shows me
what I posted earlier.
Are you taking the credentials from your keystone?
Yes, I am taking credentials from keystone
Please verify your keystone settings in
Logan, thanks for your reply. I've been very conscientious of NTP, so I'm
very confident that that is not an issue.
Gary: so in this case the agent = quantum-plugin-openvswitch-agent, and
plugin = quantum-server. That's confusing. And what you're saying is
that the ovs plugin/agent - whatever
On Tue, Mar 12, 2013 at 4:46 PM, Matthias Runge mru...@redhat.com wrote:
On 03/12/2013 12:02 PM, Ashutosh Narayan wrote:
The web page keeps on waiting and error_logs shows me
what I posted earlier.
Are you taking the credentials from your keystone?
Yes, I am taking
I thought about it, but yet not tried. Which OVS port would you
recommend to increase MTU ?
On the network node (br-ex or qg-) , or on the compute node (br-int) ?
You need to set it on the compute nodes ( int-br-ethX ) and possibly the an
extra port on the routing node.
(we use a
I'm having trouble with Swift, using Keystone auth, on Folsom.
When I try something simple like 'swift stat', there are two errors:
Firstly a logging error:
147proxy-server STDOUT: No handlers could be found for logger
keystone.middleware.auth_token
More importantly, the authorization fails:
For Quantum GRE tunneling, the network node and compute nodes need a NIC on
your data network. You assign each of those NIC's an IP (for instance,
192.168.1.1-3). Then (assuming you are using openvswitch with GRE
tunneling) you set up your quantum configs. Look at the Quantum
administration guide
Hi all,
I use openstack (folsom release) + XCP + ubuntu 12.04.
I tried to create a snapshot of an ubuntu instance.
Unfortunately, I get this error. Any ideas how to deal with this error?
-
2013-03-12 12:54:02 AUDIT nova.compute.manager
[req-39dc25ff-686d-46b8-98ac-29b3b08dbe94 admin demo]
It seems as though the plugin is waiting for a coalesce to happen after the
snapshot - and timing out.
Could you confirm if the coalesce actually happened on the XenServer host, or
if there were errors when attempting to coalesce? (probably from /var/log/SMlog)
It might be worth checking the
We'd hope that there was something output to one of the log files in this case.
Is there anything that seems suspicious?
Also, is this through a manual setup, or are you running devstack?
From: openstack-bounces+bob.ball=citrix@lists.launchpad.net
Hi,
While studying keystone v3 and domains feature, I realized that current
policy.json file has no domain_admin role as I was expecting. I wonder if this
role will be defined in Grizzly timeframe or how do you envision domain_admin
role enforcement.
Thanks in advance!
Glaucimar Aguiar
Hi All,
I am using https://github.com/openstack/tempest/tree/stable/folsom release
of Tempest.
I ran tests under /tempest-stable-folsom/tempest/ using : nosetests tests/
It worked fine for most of the test cases.
After this I tried to ran : *nosetests tests/network/*
*It is giving me an error
Hi Bob,
No, it was through a manual step and I was following the instructions
mentioned
herehttp://docs.openstack.org/trunk/openstack-compute/install/yum/content/compute-verifying-install.html
.
I am running all the services on single hosts which is actually a virtual
machine
running on a Xen
Please note that I know one can edit policy.json to define domain-admin role
permissions but with the implementation of domains, it seems that domain-admin
role permissions should be defined as admin role permissions are.
Thanks in advance,
Glaucimar Aguiar
-Original Message-
From:
On 03/12/2013 01:35 PM, Greg Chavez wrote:
Logan, thanks for your reply. I've been very conscientious of NTP, so
I'm very confident that that is not an issue.
Gary: so in this case the agent= quantum-plugin-openvswitch-agent
agent== quantum-plugin-openvswitch-agent - yes
, and plugin =
Le 12/03/2013 13:12, Robert van Leeuwen a écrit :
I thought about it, but yet not tried. Which OVS port would you
recommend to increase MTU ?
On the network node (br-ex or qg-) , or on the compute node (br-int) ?
You need to set it on the compute nodes ( int-br-ethX ) and possibly the an
Hi all,
You all did great with DocImpact, but now that we're less than a month from
release, the tiny doc team is facing a long list of doc bugs that won't be
done by April 4th, many generated by DocImpact flags.
We typically do a release of the docs about a month after the actual
release date,
On Tue, Mar 12, 2013 at 8:01 PM, Jay Pipes jaypi...@gmail.com wrote:
On 03/12/2013 12:55 AM, Girija Sharan wrote:
Hi Masayuki,
Thanks a lot for your early response.
I am using Openstack Folsom and not Devstack.
I am not getting how to integrate Tempest for Folsom. As you mentioned
Doc bug logged https://bugs.launchpad.net/openstack-manuals/+bug/1154141about
the Dashboard (Horizon) outdated instructions. Feel free to pick it
up and fix.
Anne
On Tue, Mar 12, 2013 at 7:01 AM, Ashutosh Narayan
aashutoshnara...@gmail.com wrote:
On Tue, Mar 12, 2013 at 4:46 PM, Matthias
On 03/12/2013 11:14 AM, Girija Sharan wrote:
But the tests in *tempest-stable-folsom/tempest/tests/network *are not
running in Folsom with Quantum. All other tests are running fine.
Someone said that this stable-folsom release of tempest is not for
testing Quantum in Folsom.
Is it true ? If
Hi,
Thanks again.
I am getting this error whenever I
ran *tempest-stable-folsom/tempest/tests/network tests.
==
ERROR: test suite for class
'tempest.tests.network.test_networks.NetworksTest'
Give your whole proxy.conf here.
On Tue, Mar 12, 2013 at 8:54 PM, Adam Huffman adam.huff...@gmail.comwrote:
I'm having trouble with Swift, using Keystone auth, on Folsom.
When I try something simple like 'swift stat', there are two errors:
Firstly a logging error:
147proxy-server STDOUT:
[DEFAULT]
bind_port = 8080
bind_ip = ip
workers = 24
user = swift
set log_level = DEBUG
log_facility = LOG_LOCAL2
[pipeline:main]
pipeline = healthcheck cache authtoken keystone proxy-server
[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true
account_autocreate = true
An information system is asking and i do not know how to enable it
- API Key
OK with other information:
-Username
-Project ID
- Auth URL
- Region Name
Alex Vitola
@ alexvitola
___
Mailing list: https://launchpad.net/~openstack
Post to :
Can someone point me to docs describing how to add/modify/delete permissions
for a horizon panel?
I want a non-admin user to be able to access the Swift object-store containers
panel in horizon. Currently, the containers panel.py has the permissions set
to:
permissions =
Logan,
Thank you for the response!
The high availability configuration documentation will be useful. The immediate
problem is less with high availability than performance enhancement.
Using the nova-controller and -compute model, I have one cinder node running
the api, scheduler, and volume
On 03/12/2013 05:26 PM, Girija Sharan wrote:
Hi,
Thanks again.
I am getting this error whenever I
ran *tempest-stable-folsom/tempest/tests/network tests.
==
ERROR: test suite for class
Hi Wyllys,
On 13 March 2013 04:19, Wyllys Ingersoll wyllys.ingers...@evault.com wrote:
Can someone point me to docs describing how to add/modify/delete permissions
for a horizon panel?
I want a non-admin user to be able to access the Swift object-store
containers panel in horizon.
If anybody from the forums is on here, or can forward this message to the
forum admins, I have been trying for weeks to register. This is from
multiple IP address ranges-- work, home, and cellular. I keep getting the
following error:
Your IP 96.60.255.159 has been blocked because it is
Hi!
Sorry about the double posting... I need help! :-P
I'm trying, without any kind of success, to deploy OpenStack with Quantum
on its simplest scenario, I think, which is `Single Flat' with `Linux
Bridge' plugin.
My topology is:
1 firewall with 2 ethX (eth0 public, eth1 10.32.14.1
Hi,
When booting up a UEC image on our cloud cloud-init writes the apt sources file
with:
http://availability-zone.clouds.archive.ubuntu.com/ubuntu
Today all of a sudden this doesn't resolve to anything.
I note that http://availability-zone.cloud.archive.ubuntu.com does (cloud not
clouds)
Make sure the quantum-dhcp and l3 agents are running and properly configured.
It sounds like either the q-dhcp agent is not functioning or connectivity
between the dhcp agent and vm is not functioning. If using GRE tunnels, test
connectivity between the tunnel endpoints. You should also see
Daneyon,
Thank you for your time! I'll check it!
I read that guide from Cisto once... Too complex.
I also, tried the following guides too, appears to be like the one from
Cisco:
Hi,
Is the MySQL adapter for python isntalled in your machine. Because the error
corresponds to th unavailability of the MySQLdb adapter.
Kindly have a look into that.
Regards,
Avinash
From: openstack-bounces+avinash.prasad=nttdata@lists.launchpad.net
On Wed, Mar 13, 2013 at 2:14 AM, Rami Vaknin rvak...@redhat.com wrote:
On 03/12/2013 05:26 PM, Girija Sharan wrote:
Hi,
Thanks again.
I am getting this error whenever I
ran *tempest-stable-folsom/tempest/tests/network tests.
at 20130312
Title: precise_grizzly_ceilometer_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/133/Project:precise_grizzly_ceilometer_trunkDate of build:Tue, 12 Mar 2013 05:10:40 -0400Build duration:2 min 35 secBuild cause:Started by user James
Title: precise_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_horizon_trunk/100/Project:precise_grizzly_horizon_trunkDate of build:Tue, 12 Mar 2013 12:31:39 -0400Build duration:2 min 44 secBuild cause:Started by an SCM changeBuilt
Title: raring_grizzly_horizon_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_horizon_trunk/98/Project:raring_grizzly_horizon_trunkDate of build:Tue, 12 Mar 2013 12:31:39 -0400Build duration:3 min 31 secBuild cause:Started by an SCM changeBuilt
at 20130312
Title: precise_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_nova_trunk/800/Project:precise_grizzly_nova_trunkDate of build:Tue, 12 Mar 2013 15:48:22 -0400Build duration:11 minBuild cause:Started by user Adam GandelmanBuilt
Title: precise_grizzly_deploy
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_deploy/210/Project:precise_grizzly_deployDate of build:Tue, 12 Mar 2013 15:59:27 -0400Build duration:2 min 10 secBuild cause:Started by command line by jenkinsBuilt
Title: raring_grizzly_nova_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_nova_trunk/895/Project:raring_grizzly_nova_trunkDate of build:Tue, 12 Mar 2013 17:33:38 -0400Build duration:32 secBuild cause:Started by user Adam GandelmanBuilt
Title: raring_grizzly_swift_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_swift_trunk/152/Project:raring_grizzly_swift_trunkDate of build:Tue, 12 Mar 2013 18:00:48 -0400Build duration:2 min 30 secBuild cause:Started by an SCM changeBuilt
Title: test_devstack_exercises
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_devstack_exercises/1/Project:test_devstack_exercisesDate of build:Tue, 12 Mar 2013 18:16:00 -0400Build duration:1.2 secBuild cause:Started by command line by jenkinsBuilt
Title: test_devstack_exercises
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/test_devstack_exercises/2/Project:test_devstack_exercisesDate of build:Tue, 12 Mar 2013 18:16:08 -0400Build duration:0.6 secBuild cause:Started by command line by jenkinsBuilt
Title: precise_essex_quantum_stable
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_essex_quantum_stable/11/Project:precise_essex_quantum_stableDate of build:Tue, 12 Mar 2013 18:31:38 -0400Build duration:8 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/450/Project:raring_grizzly_quantum_trunkDate of build:Tue, 12 Mar 2013 20:42:25 -0400Build duration:2 min 1 secBuild cause:Started by an SCM changeBuilt
Title: precise_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/precise_grizzly_ceilometer_trunk/139/Project:precise_grizzly_ceilometer_trunkDate of build:Tue, 12 Mar 2013 22:31:41 -0400Build duration:1 min 21 secBuild cause:Started by an SCM
Title: raring_grizzly_ceilometer_trunk
General InformationBUILD FAILUREBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_ceilometer_trunk/140/Project:raring_grizzly_ceilometer_trunkDate of build:Tue, 12 Mar 2013 22:31:41 -0400Build duration:2 min 28 secBuild cause:Started by an SCM
Title: raring_grizzly_quantum_trunk
General InformationBUILD SUCCESSBuild URL:https://jenkins.qa.ubuntu.com/job/raring_grizzly_quantum_trunk/451/Project:raring_grizzly_quantum_trunkDate of build:Wed, 13 Mar 2013 00:31:41 -0400Build duration:19 minBuild cause:Started by an SCM changeBuilt
64 matches
Mail list logo
