Hi,
I would like to subscribe to this mail list.
Best wishes.
Vincent Hou (侯胜博)
Software Engineer, Standards Growth Team, Emerging Technology Institute, IBM
China Software Development Lab
Notes ID: Sheng Bo Hou/China/IBM@IBMCN E-mail: sb...@cn.ibm.com
Address:3F, Ring, Building 28
HI Aniruddha,
If you don't find the documentation to be consistent with the behaviour,
you might want to wait for this to get into the trunk:
https://review.openstack.org/#change,5164
To get started, Devstack is my bet. Reading the devstack deployment
and excercise scripts will
be a lot helpful
Hi,
I am working on a cloud network resource provisioning service, which
will accomodate networking among virtual machines by configuring the
network hardware(switches) that lies between the hosts. The goal of
the service is 1) to undo the vlan clean requirement that you have
in Nova and
Hi,
I am working on a cloud network resource provisioning service, which
will accomodate networking among virtual machines by configuring the
network hardware(switches) that lies between the hosts. The goal of the
service is 1) to undo the vlan clean requirement that you have in
Nova and other
Hi Dimitris,
This sounds a lot like what the Quantum API and plugin interface is
intended to support. I'd check out: http://wiki.openstack.org/Quantum and
feel free to send email to the netstack list for details on integration new
functionality.
Dan
On Thu, Mar 15, 2012 at 7:19 AM, Dimitris
On 03/14/2012 11:42 AM, David Kranz wrote:
In case any one runs into this, there is a bug in the Precise upstart
package that causes a reboot after installing essex to result in a
kernel panic. I don't know exactly what in the openstack install process
triggers it but there is a PPA mentioned
Hello,I followed the quantum-admin-guide document to create the network by using:"nova-manage network create --label=tenant-private --fixed_range_v4=192.168.1.0/24 --project_id= --priority=1 --gateway=192.168.1.254"I got error caused
On 03/15/2012 10:17 AM, Robbie Williamson wrote:
On 03/14/2012 11:42 AM, David Kranz wrote:
In case any one runs into this, there is a bug in the Precise upstart
package that causes a reboot after installing essex to result in a
kernel panic. I don't know exactly what in the openstack install
Hi Vish All,
We would definitely prefer to leave the code in place and ready to fix any
issues related to it.
We found out that it is extremely hard to work with latest trunk version -
our QA was constantly complaining about different regression scenarios and
we decided to stick with released
On Mar 15, 2012, at 11:43 AM, Yapeng Wu wrote:
Hello,
I followed the quantum-admin-guide document to create the network by using:
nova-manage network create --label=tenant-private
--fixed_range_v4=192.168.1.0/24 --project_id= --priority=1
--gateway=192.168.1.254
I got error
Vladimir,
Are you sure the code in trunk is working? Investigation by one of the
community members showed that it was broken. If you are planning on merging
your new code in, perhaps it is better to do it all at once? FYI, nova-volume
is going to be split into its own service during folsom,
Hi Vish,
I was not aware of any issue with VSA code in diablo/stable (or at least
major issues).
Of course, we've done tons of changes to it lately and probably there were
some bugs that were fixed later, but I'm sure this particular code is
fully functional.
We will need to look closer on
I would like to add that the complete lack of documentation makes the VSA code
unusable. I have no idea where to get started with it. The following bug has
been open and assigned for the past 6+ months:
https://bugs.launchpad.net/nova/+bug/835099. The fact that you are maintaining
a fork of
On Thu, 2012-03-15 at 09:02 -0700, Vladimir Popovski wrote:
I was not aware of any issue with VSA code in diablo/stable (or at least
major issues).
I'll point out that the code we're concerned about is the code in trunk,
not the code in diablo/stable. There have been substantial changes to
the
Brian Waldon wrote:
I would like to add that the complete lack of documentation makes the
VSA code unusable. I have no idea where to get started with it. The
following bug has been open and assigned for the past 6+
months: https://bugs.launchpad.net/nova/+bug/835099. The fact that you
are
I think is time (after essex release) to rethink the way plugins are
integrated into mainline code. This problem, an outdated plugin, it's not
new (Hyper-V), and with the increasing numbers of them (storage like
Zadara, Nexenta... network with Nicira, BigSwitch, Citrix...) we need a
policy to
If there is anything broken in Essex due to this code, please let me know
and we will take a look/fix it.
The main reason why we would like to have it in place - to make developers
aware that there is somebody relying on particular functionality and/or
particular function/module. Otherwise we
Hi,
I have just upload the OpenStack UI code base, which implies few changes in
the openstack-java-sdk api.
You can view the video i uploaded 2 days ago here:
http://youtu.be/zGy4yC7r6w4
The source code is available at:
https://github.com/woorea/openstack-java-sdk/tree/master/openstack-ui
If
pip install xenapi
- Chris
On Mar 15, 2012, at 10:00 AM, Eduardo Nunes wrote:
got this error on log, 2012-03-15 16:52:33,809 ERROR nova.compute.manager
[-] Unable to load the virtualization driver: No module named XenAPI
my nova-compute version diablo 2011.3
check you have XenAPI installed on your system.
'sudo easy_install xenapi' should suffice.
On Thu, Mar 15, 2012 at 5:00 PM, Eduardo Nunes eduardo.ke...@gmail.com wrote:
got this error on log, 2012-03-15 16:52:33,809 ERROR nova.compute.manager
[-] Unable to load the virtualization driver: No
On Mar 15, 2012, at 10:08 AM, Ghe Rivero wrote:
I think is time (after essex release) to rethink the way plugins are
integrated into mainline code. This problem, an outdated plugin, it's not
new (Hyper-V), and with the increasing numbers of them (storage like Zadara,
Nexenta... network
On Mar 15, 2012, at 8:48 AM, Vladimir Popovski wrote:
Hi Vish All,
We would definitely prefer to leave the code in place and ready to fix any
issues related to it.
We found out that it is extremely hard to work with latest trunk version -
our QA was constantly complaining about
Yes, until we move to handling L3 in Quantum itself (Folsom), the L3
integration in QuantumManager is pretty simple.
Dan
On Thu, Mar 15, 2012 at 8:51 AM, David Lapsley dlaps...@nicira.com wrote:
On Mar 15, 2012, at 11:43 AM, Yapeng Wu wrote:
Hello,
I followed the quantum-admin-guide
Without install and config docs it is too difficult to ask testers to try it.
My docs request of this particular volume extension was in the diablo release
but is still needed in Essex. Let's start with a docs merge request before
asking people to test it.
Let me know if you need an
On a sort of side note, I was sort of surprised that given all the
discussion on volumes, VSA etc in IRC and on email lately that there
were ZERO attendees in the weekly meeting today.
So, maybe just a reminder, there is a weekly volume meeting in
openstack-meeting on Thursdays at 18:00 (UTC).
+1
I'd like to see a way for plugins to be able to modify the DB schema. There's
no easy way for a plugin to be able to add a column to a core nova table, for
instance.
In any case, I'm +1 on removing the vsa code for Essex.
On Mar 15, 2012, at 10:08 AM, Ghe Rivero wrote:
I think is time
On 03/15/2012 11:51 AM, David Lapsley wrote:
On Mar 15, 2012, at 11:43 AM, Yapeng Wu wrote:
Hello,
I followed the quantum-admin-guide document to create the network by using:
nova-manage network create --label=tenant-private
--fixed_range_v4=192.168.1.0/24 --project_id= --priority=1
Ghe Rivero wrote:
Ø I think is time (after essex release) to rethink the way plugins are
integrated into mainline code. This problem,
an outdated plugin, it's not new (Hyper-V), and with the increasing numbers of
them (storage like Zadara, Nexenta...
network with Nicira, BigSwitch,
I'm starting to get some of this stuff into the official manuals.
Eduardo, please take a look at https://review.openstack.org/#change,5419 and
see if that is useful.
Thanks,
Ewan.
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
https://review.openstack.org/#change,5419
Cheers,
Ewan.
-Original Message-
From: openstack-bounces+ewan.mellor=citrix@lists.launchpad.net
[mailto:openstack-bounces+ewan.mellor=citrix@lists.launchpad.net]
On Behalf Of Anne Gentle
Sent: 10 March 2012 06:15
To: Thomas Goirand
On Thu, 2012-03-15 at 15:14 -0400, Brian Haley wrote:
That is correct. We explicitly check in
nova.network.quantum.manager.QuantumManager
if gateway is not None and len(gateway) 0:
if gateway.split('.')[3] != '1':
Yeah, I think its fine to delete the check. Feel free to remove the check
in your environment and reply back if anything else breaks -- I'll also
submit a nova patch for it.
Thanks,
Brad
On Thu, Mar 15, 2012 at 12:14 PM, Brian Haley brian.ha...@hp.com wrote:
On 03/15/2012 11:51 AM, David
Hello,
I removed the check, the nova-manage command runs fine now.
But the gateway address was not pushing to dnsmasq.
In Nova code, how does the gateway option is pushed to dnsmasq?
Thanks,
Yapeng
On 2012-03-15, at 7:55 PM, Brad Hall wrote:
Yeah, I think its fine to delete the check.
33 matches
Mail list logo
