I agree except I though the preference was for
instance_uuid = instance['uuid']
not
instance_uuid = instance.uuid
(use dict's and don't assume sqlalchemy)
On Wed, Dec 14, 2011 at 11:19 PM, Devin Carlen devin.car...@gmail.com wrote:
Yes, we should absolutely push to make this more
2011/12/15 Jesse Andrews anotherje...@gmail.com:
I agree except I though the preference was for
instance_uuid = instance['uuid']
not
instance_uuid = instance.uuid
(use dict's and don't assume sqlalchemy)
Yes... That's what Chris is saying, isn't it?
--
Soren Hansen |
++ on moving to a consistent dict-style syntax.
We could attempt to rip the Band-Aid off here by:
1. Rejecting any new patches which use the dot-notation
2. Trying to switch out to using dot-notation access all at once in one big
'fix-it-up' patch.
I'm not convinced 2) is possible. Separating
Great question.
Right now there are 3 approaches to metadata/runtime config:
* ec2 metadata service - http://169.254.169.254/ (used by ubuntu's
cloud-init for example)
* config drive - added in diablo
* xenstore via openstack agent - https://launchpad.net/openstack-guest-agents
* injecting
Yes, that was what I was saying. :)
On Dec 15, 2011, at 12:06 AM, Soren Hansen wrote:
2011/12/15 Jesse Andrews anotherje...@gmail.com:
I agree except I though the preference was for
instance_uuid = instance['uuid']
not
instance_uuid = instance.uuid
(use dict's and don't assume
Agree with both #1s as a start. And I wouldn't try to 'rip off the band-aid'
either.
I was bringing this up initially as I want to enforce *something* when
reviewing, but if we want to start 'fixing' things, we can start hitting small
sections of code to limit conflicts. The 'enforce_model'
I was bringing this up initially as I want to enforce *something* when
reviewing,
Yeah, I was just thinking that it could be a point of confusion if, for an
extended period, we're in a state where new code has to use dict-style instance
access, while nearby, older code still uses
Hi,
While searching for the swift performance tuning tips I came across this
post: http://adrianotto.com/2010/09/openstack-os-is-great-for/
In the comments, some users mention that it's better to keep max. number
of objects per container less than 1M. As far as I understood, this is
mainly
Thanks for the responses guys.
Jesse I can see how there might be concerns around using file injection but it
seems as if that was chosen as a method of inserting user-specified metadata
into an instance which is why I was wondering why it wasn't expanded to use the
same process to insert
Hi All,
I am testing acl support in swift-1.4.5. According to the document
http://swift.openstack.org/misc.html#module-swift.common.middleware.acl the
syntax to allow all non-admin users read access to the container except for
one is as following.
Executing the curl following curl command from
Hi,all,
Glance version i am running is 2012.1-dev. But glance-api can't be
started(maybe this version is just unstable for now?).Here is some details:
*#sudo glance-api glance-api.conf --debug -v *
*[1]27173*
*Error trying to load config /etc/glance/glance-api.conf:module
'glance.api.v1' from
How about adding the following two flags in nova.conf file?
We are running flat dhcp without problem.
You need to customize the values of the flags.
--flat_network_dhcp_start=10.99.1.2
--flat_interface=eth0
David.
--
Dr. Dong-In David Kang
Computer Scientist
USC/ISI
Dear Jeff ,
Could u check ur conf file for app_factory section! I think ur conf file is
out of date to match latest glance code. Compare with the new sample will
figure it out.
Hope it help
Hugo's iPhone
jeffrey coho jeffreycohob...@gmail.com 於 2011/12/15 21:28 寫道：
Hi,all,
Glance
Just for reference, question was answered here:
https://answers.launchpad.net/swift/+question/181977
On 15/12/2011 10:02, Rustam Aliyev wrote:
Hi,
While searching for the swift performance tuning tips I came across
this post: http://adrianotto.com/2010/09/openstack-os-is-great-for/
In the
On Thu, Dec 15, 2011 at 3:29 AM, Rick Harris rick.har...@rackspace.com wrote:
++ on moving to a consistent dict-style syntax.
+1 from me, too.
-jay
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Hello all. We've recently upgraded our cactus system to more recent
code. In the process of doing this, we've started logging whenever we
get tracebacks out of any of the openstack components we are running.
Some of these are clearly bugs, while others correspond to normal
operational conditions
I don't know if there's an official project policy, but personally I don't
think an end-user should ever see a Python traceback in a logfile under normal
operations (i.e., the user has configured all of the services correctly).
Lorin
--
Lorin Hochstein, Computer Scientist
USC Information
Yeah, I was worried we would run into these kinds of problems with a
recent commit...
Basically, do what Hugo suggested. We recently overhauled the
configuration and paste deploy factories in Glance to align with the
common cfg work being done in Nova and Glance. This means that the
On Thu, Dec 15 2011, Narayan Desai wrote:
Hello all. We've recently upgraded our cactus system to more recent
code. In the process of doing this, we've started logging whenever we
get tracebacks out of any of the openstack components we are running.
Some of these are clearly bugs, while
On Thu, 2011-12-15 at 07:10 +, Chris Behrens wrote:
There's a mix of usage throughout the code, and I know some people are
just matching the surrounding code. But, in a number of cases, I've
asked for these to be corrected to the latter, on assumption that the
DB layer will be returning
-1
By using the dict style access to these records we are tying ourselves to the
internal implementation of those records. If we want to be able to move the
'data model' logic out of the 'process' logic we will need to access the models
as attributes and not dict items.
We should confine the
On Dec 15, 2011, at 1:10 AM, Chris Behrens wrote:
I've seen a number of patches lately that have code like this:
instance = db.instance_get(...)
instance_uuid = instance.uuid
instead of:
instance_uuid = instance['uuid']
There's a mix of usage throughout the code, and I know some
On Thu, 15 Dec 2011, McNally, Dave wrote:
Thanks for the responses guys.
Jesse I can see how there might be concerns around using file injection
but it seems as if that was chosen as a method of inserting
user-specified metadata into an instance which is why I was wondering
why it wasn't
On Thu, 15 Dec 2011, Jesse Andrews wrote:
Great question.
Right now there are 3 approaches to metadata/runtime config:
* ec2 metadata service - http://169.254.169.254/ (used by ubuntu's
cloud-init for example)
* config drive - added in diablo
* xenstore via openstack agent -
On Wed, Dec 14, 2011 at 5:38 PM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
Or static disk image files!
Only if you've got enough RAM on the storage worker node to cache the entire
disk image. Otherwise it's just going to get evicted straight away.
The case where you've got so few,
On Thu, Dec 15, 2011, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote:
2. However, I violently disagree with the idea that the DB layer
must return dicts. It does not, even if you start talking about
allowing use of other kinds of databases. We can, and should,
Definitely we should be filing bugs.
Jesse
On Thu, Dec 15, 2011 at 8:00 AM, Julien Danjou
julien.dan...@enovance.com wrote:
On Thu, Dec 15 2011, Narayan Desai wrote:
Hello all. We've recently upgraded our cactus system to more recent
code. In the process of doing this, we've started logging
On Thu, Dec 15, 2011 at 8:43 AM, Scott Moser smo...@ubuntu.com wrote:
I'm just curious, what are the motivations behind inventing something
other than the EC2 Metadata service? It is generally functional, and
quite a lot can (and has) built atop this simple service.
I should clarify - the
On Thu, 15 Dec 2011, Jesse Andrews wrote:
On Thu, Dec 15, 2011 at 8:43 AM, Scott Moser smo...@ubuntu.com wrote:
I'm just curious, what are the motivations behind inventing something
other than the EC2 Metadata service? It is generally functional, and
quite a lot can (and has) built atop
Hi!
I'm testing a new installation (virtual environment) as following:
(1) I've installed Openstack using the Devstack Script (with some
modification to work here), so, all in one installation.
(2) Then, I started to install Openstack from a clean Ubuntu Oneiric
instalation, but using packages
On Dec 15, 2011, at 10:54 AM, Johannes Erdfelt wrote:
What kinds of things?
I'm just trying to better understand what is object-oriented about the
data returned from a database? What methods would we want to use?
JE
Any direct access to the data within a record should be encapsulated within
The script asks you for the password ... or you put it in a file called
localrc
Here is my localrc
MYSQL_PASSWORD=nova
RABBIT_PASSWORD=nova
SERVICE_TOKEN=nova
ADMIN_PASSWORD=nova
ENABLED_SERVICES=g-api,g-reg,key,n-api,n-cpu,n-net,n-sch,n-vnc,horizon,m
reading the script..
you either have it in localrc file as *ADMIN_PASSWORD, *or you were
prompted during install to type it in.
*
*
On Thu, Dec 15, 2011 at 1:38 PM, sn alaya...@gmail.com wrote:
and also the default username of openstack that has been installed using
devstack script...
On
Your simulation is of the one case that I said would work: when you have enough
RAM to cache the entire image.
When you _don't_ have enough RAM, then the images will just immediately be
evicted, and the performance with the cache will be worse, not better. This
break point is going to be when
On Dec 15, 2011, at 8:21 AM, Monsyne Dragon wrote:
Actually, what we should be working to is using plain python model
objects, and having the sqlalchemy layer use it's mapper
functionality (separated from the models) to map db rows to those
models. THis will allow any persistence layer to
For me, it's not one particular notation versus the other, I'd be happy with
either--it's having both. It just needlessly complicates things.
Now we're complaining that the ORM we likely aren't using
correctly isn't working for us
I don't think anyone is complaining that the *ORM* is at fault
This should have been asked to you when running the stack.sh script
and this should be stored in localrc file.
Chmouel.
On Thu, Dec 15, 2011 at 6:28 PM, sn alaya...@gmail.com wrote:
hi experts...
i have just now installed successfully openstack without any errors.with
the scripts mention
Johannes Erdfelt johan...@erdfelt.com said:
On Thu, Dec 15, 2011, Kevin L. Mitchell kevin.mitch...@rackspace.com wrote:
2. However, I violently disagree with the idea that the DB layer
must return dicts. It does not, even if you start talking about
allowing use of other
Hm. I've just been going off of this doc string in db/api.py:
Functions in this module are imported into the nova.db namespace. Call these
functions from nova.db namespace, not the nova.db.api namespace.
All functions in this module return objects that implement a dictionary-like
interface.
I think all are bugs.
Even if you understand some of them and considers them to be logical,
you should not see ugly backtraces. You should see nice log lines any
system administrator can read and understand clearly.
I agree. There are some other practical reasons for it too:
- Exceptions
On Dec 15, 2011, at 1:27 PM, Devin Carlen wrote:
Matt, that answer is simple: so we can use things other than sqlalchemy.
Except that we don't need to do that to use other things that sqlalchemy.
We can have sqlalchemy map to plain python objects, and use those.
And any other persistence
On Thu, Dec 15, 2011 at 2:55 PM, Ewan Mellor ewan.mel...@eu.citrix.com wrote:
Your simulation is of the one case that I said would work: when you have
enough RAM to cache the entire image.
When you _don't_ have enough RAM, then the images will just immediately be
evicted, and the
On Thu, Dec 15, 2011 at 2:29 PM, Dong-In David Kang dk...@isi.edu wrote:
I'm trying to make novaclient work with keystone.
It looks like authentication is working, but actual interaction between
novaclient and nova does not work.
Here is what I get (with added debugging messages I added in
On Dec 15, 2011, at 10:37 AM, Scott Moser wrote:
On Thu, 15 Dec 2011, Jesse Andrews wrote:
On Thu, Dec 15, 2011 at 8:43 AM, Scott Moser smo...@ubuntu.com wrote:
I'm just curious, what are the motivations behind inventing something
other than the EC2 Metadata service? It is generally
Hmm, looks like you are using an old version of python-novaclient. You might
try grabbing from source. The packages from launchpad are not supported in any
way. We try to provide relatively current packages, but we don't really have
the resources to maintain and support them at this point.
Hum, ok, I'll try some versions tomorrow and post the results!
Thanks Vish!
:)
On Dec 15, 2011, at 8:53 PM, Vishvananda Ishaya wrote:
Hmm, looks like you are using an old version of python-novaclient. You might
try grabbing from source. The packages from launchpad are not supported in
On Thu, Dec 15, 2011 at 2:29 PM, Dong-In David Kang dk...@isi.edu
wrote:
I'm trying to make novaclient work with keystone.
It looks like authentication is working, but actual interaction
between novaclient and nova does not work.
Here is what I get (with added debugging messages I
On Thu, Dec 15, 2011, Mark Washenberger mark.washenber...@rackspace.com wrote:
1. regular objects (which is what I thought Kevin was talking about. . .
maybe?)
I think this has been poorly defined so far. I've seen some quick
proposals that include moving instance actions to an Instance class,
I use nova on KVM.
I create Windows 2008 R2 image and upload to glance.
$ glance index
ID Name Disk Format
Container Format Size
--
--
9
Hi,
I'm testing swift 1.4.4 setup with 4 nodes/zones on RHEL 5.7. I ran into
the problem of slow writes. Using swift-bench we generated load, writing
hundreds of 4K files. Results:
- Writes - ~3 PUTs/sec (very slow)
- Reads - ~25 GETs/sec (ok)
It's clear that writes are not limited by I/O.
+1
On 12/15/11 3:19 PM, Johannes Erdfelt johan...@erdfelt.com wrote:
On Thu, Dec 15, 2011, Mark Washenberger mark.washenber...@rackspace.com wrote:
1. regular objects (which is what I thought Kevin was talking about. . .
maybe?)
I think this has been poorly defined so far. I've seen some
In my case, I want to set access permissions to all the users except for
this user tester3 and according to the documentation - is to be
prefixed to deny access to the user. But even after setting the - for the
user tester3, read access is granted to it. Can anyone who has used it
provide some
hello,
please Unsubscribe my account from open stack...
On Fri, Dec 16, 2011 at 8:02 AM, Mohammed Junaid mohdjunaid...@gmail.comwrote:
In my case, I want to set access permissions to all the users except for
this user tester3 and according to the documentation - is to be
thanks you everyone the default user name was admin and yes i have
configured the password as password during installation. thanks for
helping and replying all
[DevStack] script is the best way to test Openstack.
#devstack #openstack #ubuntu
___
Hi,
For my company, I'd like to set-up a nova-compute All-In-One node, to
replace a eucalyptus cluster which is showing age.
Unfortunately I'm not well versed in networking, and have trouble
grasping the difference between the multiple network managers, but I
think I would need a Flat mode in my
55 matches
Mail list logo
