Re: [Openstack] Handling of adminPass is arguably broken (essex)

On 11/1/12 9:36 AM, "Lars Kellogg-Stedman" wrote: >> Honestly I think the entire idea of passing a password in to the >>instance at boot >> time is insecure and flawed. > >I think that the use of a configuration drive is a reasonably way to >provide configuration information to an instance, and

Re: [Openstack] [openstack-dev] Openstack NOVA and Metadata.

Its in the instance_metadata table in the nova db. From: Trinath Somanchi [mailto:trinath.soman...@gmail.com] Sent: Friday, August 31, 2012 9:15 PM To: Anne Gentle Cc: OpenStack Development Mailing List; openstack@lists.launchpad.net Subject: Re: [openstack-dev] [Openstack] Openstack NOVA and Meta

Re: [Openstack] HELP: All instances automatically rebooted.

Hey Sam, Is it possible your hypervisors restarted? I see this entry in the logs: 2012-08-23 06:35:02 INFO nova.compute.manager [req-f1598257-3f35-40e6-b5aa-d47a0e93bfba None None] [instance: ce00ff1d-cf46-44de-9557-c5a0f91c8d67] Rebooting instance after nova-compute restart. Gabe From: ope

Re: [Openstack] [openstack-dev] [Glance] Implementing Common Image Properties

It would definitely be great to see these as generally accepted properties. In general, I would hope that anything that is accepted by the community eventually makes it into core API, and shipping with them on by default is a great first step. Mostly, I'd like to see us able to turn off the "

Re: [Openstack] [nova] Call for Help -- OpenStack API XML Support

> -Original Message- > From: openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net > [mailto:openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of > Gabe Westmaas > Sent: Friday, August 10, 2012 9:15 AM > To: Daniel

Re: [Openstack] [nova] Call for Help -- OpenStack API XML Support

> -Original Message- > From: openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net > [mailto:openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of > Daniel P. Berrange > Sent: Friday, August 10, 2012 8:48 AM > To: Vishvananda Ishaya > Cc: OpenSt

Re: [Openstack] Improving logging

> -Original Message- > From: openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net > [mailto:openstack- > bounces+gabe.westmaas=rackspace@lists.launchpad.net] On Behalf Of > Michael Still > Sent: Wednesday, July 18, 2012 10:51 PM > To: Eugene Kirpichov > Cc: openstack@lis

Re: [Openstack] glance_api_servers vs. glance_host vs. keystone?

Hey Lars, Sadly I don't have much in the way of a solution for you, but I do have some suggestions. Comments inline. On 6/15/12 4:17 PM, "Lars Kellogg-Stedman" wrote: >Howdy all, > >I've spent the past few days slogging through the initial steps of >getting OpenStack and running and I seem to

Re: [Openstack] request and transaction IDs across all projects

[mailto:salv.orla...@gmail.com] Sent: Thursday, June 14, 2012 7:15 PM To: Jay Pipes Cc: Gabe Westmaas; openstack@lists.launchpad.net Subject: Re: [Openstack] request and transaction IDs across all projects +111 from me.  This would make a lot easier extracting info from logs and correlating events

Re: [Openstack] request and transaction IDs across all projects

On 6/12/12 12:32 PM, "Jay Pipes" wrote: >On 06/12/2012 01:27 AM, Gabe Westmaas wrote: >> In nova we use a request ID to to help in finding all logs associated >>with >> a particular request, and this has proven to be extremely useful when >> debuggin

[Openstack] request and transaction IDs across all projects

In nova we use a request ID to to help in finding all logs associated with a particular request, and this has proven to be extremely useful when debugging issues. This should be taken a bit further, in two different directions. First, I'd like to see the request ID stored along with the any fau

Re: [Openstack] [nova][glance] making nova api more asynchronous

t;this kind of information... > >-- >Duncan Thomas >HP Cloud Services, Galway > > >> -Original Message- >> From: openstack-bounces+duncan.thomas=hp@lists.launchpad.net >> [mailto:openstack-bounces+duncan.thomas=hp@lists.launchpad.net] On >>

[Openstack] [nova][glance] making nova api more asynchronous

Hey all, I was looking through some of the api calls, in particular creating a server on the openstack api. I'm not too excited by how long it takes, and was wondering what people think about making it more asynchronous. Basically, wondering if making it so that the POST to the nova API doesn't a

Re: [Openstack] Lossage in nova test suite?

Should we revert this change till we get it cleared up? On 6/4/12 8:29 PM, "James E. Blair" wrote: >On 06/04/2012 04:00 PM, Kevin L. Mitchell wrote: >> Today I've noticed some significant problems with nova's test suite >> leaving literally hundreds of python processes out. I'm guessing that >>

Re: [Openstack] Quotas... 1 of 1 instances? What's the deal?

And I opened one 3 weeks ago! :) Just marked the one you did as a duplicate – happy to have it go either way though, no worries. https://bugs.launchpad.net/nova/+bug/998199 The error message is confusing, largely because the variable names are confusing, I suspect. Anyway, there should be so

Re: [Openstack] nova state machine simplification and clarification

l.com] > Sent: Friday, May 18, 2012 2:33 PM > To: Gabe Westmaas > Cc: openstack@lists.launchpad.net > Subject: Re: [Openstack] nova state machine simplification and clarification > > Gabe, > > There is a flag reclaim_instance_interval on API. If it's set to 0 (by &

Re: [Openstack] nova state machine simplification and clarification

Also, with this proposal I'd be a lot more interested in exposing task state as a part of the API eventually. This is helpful to communicate whether or not other actions would be allowed in certain states. For example, right now we don't allow other actions when a server is snapshotting, but whil

Re: [Openstack] nova state machine simplification and clarification

I agree, this looks much more clear compared to where we are now. I'd like to understand the difference between a soft and hard delete. Does an API user have to specify that in some way? I definitely agree that you should be able to delete in any state, I would rather it not be a requirement that

Re: [Openstack] [Glance] Replication implementations

This actually sounds like it covers most of the first run needs in this etherpad: http://etherpad.openstack.org/FolsomGlanceImageReplication Definitely excited to see the tool, and then I wonder if we can just add a few things to it to get metadata and filtering support. Sounds like ec2 stuff i

Re: [Openstack] Caching strategies in Nova ...

On 3/23/12 8:56 AM, "Sandy Walsh" wrote: > > >On 03/23/2012 09:44 AM, Gabe Westmaas wrote: >> I'd prefer to just set a different expectation for the user. Rather >>than worrying about state change and invalidation, lets just set the >>expectatio

Re: [Openstack] Caching strategies in Nova ...

I'd prefer to just set a different expectation for the user. Rather than worrying about state change and invalidation, lets just set the expectation that the system as a whole is eventually consistent. I would love to prevent any cache busting strategies or expectations as well as anything tha

Re: [Openstack] Can't delete instances with "error" status.

...@gmail.com] Sent: Thursday, March 22, 2012 2:20 AM To: Gabe Westmaas Cc: Yong Sheng Gong; Openstack Mail List Subject: Re: [Openstack] Can't delete instances with "error" status. My understanding is that you would not always want a user to delete an instance in an error state. So an op

Re: [Openstack] Can't delete instances with "error" status.

Instances in deleted status can normally be deleted, but there is definitely a bug to file here somewhere – possibly more than one. A common reason I have seen is that the node the instance lives on is no longer operating correctly, so the compute manager never gets the delete request, so it do

Re: [Openstack] Gerrit minimum review time frame

> there have been occasions where it's frustrated me that something I > objected to got merged without my seeing it or while I was trying to > comment. I've heard of this several times in the past as well - some merge prop is mid-review, and then it merges. Is there an easy mechanism to flag a r

Re: [Openstack] eventlet weirdness

> Beyond refactoring the way we add in data for response extensions, I think > the right way to get this database performance is make the compute-cells > approach the "normal". In this approach, there are at least two nova > databases, one which lives along with the nova-api nodes, and one that liv

Re: [Openstack] Remove Zones code - FFE

On 2/15/12 9:48 AM, "Armando Migliaccio" wrote: >I am a bit lost...what has size got to do with relationship? > >> -Original Message- >> From: Jay Pipes [mailto:jaypi...@gmail.com] >> Sent: 15 February 2012 14:36 >> To: Gabe Westmaas >> C

Re: [Openstack] Remove Zones code - FFE

I think this thing we call zones is fundamentally different from an Availability Zone or a Host Aggregate. An Availability Zone is about redundancy, a Host Aggregate is about capabilities, and a Zone is about infrastructure performance. I could easily imagine an Availability Zone larger than

Re: [Openstack] Remove Zones code - FFE

Partitions maybe? On 2/14/12 4:01 PM, "Gabe Westmaas" wrote: >This really is more of about sharding than grouping though. The specific >goal of this implementation is to shard your nova database (on a capacity >basis, not on a special key) and allow you to split (or shard

Re: [Openstack] Remove Zones code - FFE

This really is more of about sharding than grouping though. The specific goal of this implementation is to shard your nova database (on a capacity basis, not on a special key) and allow you to split (or shard :) connections to your rabbit server. This implementation should be used for performance

Re: [Openstack-qa-team] Tempest and functional test success definition

I think the discussion about whether SSHing crossed that line was more about sshing to control nodes to do setup. SSHing is pretty useful, you just need to be able to tweak it some when you are doing it. I'd suggest adding in the ability to ssh as a configuration option, along with options for ho

Re: [Openstack] Nova trunk completely broken on Python 2.6

Was filed and fixed last night (https://bugs.launchpad.net/nova/+bug/917398 and https://review.openstack.org/#change,3086 before the email was sent - let me know if its still broken!) though I'm not sure we are entirely good yet. Right now we seem to be hanging on xenserver, though I think its unr

Re: [Openstack] Unique key is case-sensitive or *in*sensitive?

Maybe a good topic for next design summit is to define our next set of goals with migrations as the projects get larger and the usage of the projects increases in scale. Are migrations intended for all environments? Dev, initial rollouts, small clouds, "enterprise" clouds? Should data and sc

Re: [Openstack] API specifications

Hi Nachi, The reason for excluding those from being required in the create response is to allow us to make those creates as asynchronous as possible. Gabe On 12/2/11 12:01 PM, "Nachi Ueno" wrote: >Hi Brian > >Thank you for your response. >How about params which is missing in docs? > >accessIPv

Re: [Openstack] reviewday

Sure! Sorry about that :) Torpedo is just the set of ruby tests that we have been using for a while to smoketest the API, separated into a project outside of VPC - the project that was running for a while on the jenkins server. Source is here: https://github.com/dprince/torpedo When one is hit

[Openstack] reviewday

Hey all, Just thought I'd let you know of a tool many of the guys here on ozone have found useful: http://reviewday.ohthree.com/ Basically it takes the review ordering work that Thierry did and makes it work with gerrit and then adds test results from smokestack to let you know whether unit t

Re: [Openstack-qa-team] test suite name

with Jim to get the github rename done. Gabe From: Gabe Westmaas mailto:gabe.westm...@rackspace.com>> Date: Thu, 17 Nov 2011 10:15:59 -0500 To: openstack qa team mailto:openstack-qa-team@lists.launchpad.net>> Subject: Re: [Openstack-qa-team] test suite name Let's try this agai

Re: [Openstack-qa-team] test suite name

Let's try this again! I actually checked these in launchpad this time, so we should be good. This closes in 3 days. https://launchpad.net/~openstack-qa-team/+poll/real-suite-name/+vote Gabe From: Gabe Westmaas mailto:gabe.westm...@rackspace.com>> Date: Tue, 8 Nov 2011 14:36:

[Openstack-qa-team] storm doesn't work!

Hey everyone, Bad news – I didn't actually check to make sure that storm was available on launchpad prior to the poll, sorry guys. Jim Blair was kind enough to point that out before we went too far, and we are unfortunately going to have to go back to the drawing board. I personally would lik

Re: [Openstack-qa-team] test suite name

Thanks to everyone who voted! Storm has been approved as the name for the new test suite, big thanks to Donald Ngo for suggesting the name. https://launchpad.net/~openstack-qa-team/+poll/name-functional-tests I will work with James Blair to get the name changed shortly. Gabe From: Gabe

[Openstack-qa-team] test suite name

Hey guys, Here is the poll I created on Wednesday (it took a while to become active). https://launchpad.net/~openstack-qa-team/+poll/name-functional-tests/+vote This is going to determine the project name in openstack and Jim Blair will be less than happy if we need to change again, so its impo

Re: [Openstack-qa-team] Python wrappers for OpenStack APIs

Here's a full spec in xml, I believe: https://github.com/openstack/compute-api/tree/master/openstack-compute-api- 1.1/src Gabe On 10/17/11 1:19 PM, "David Kranz" wrote: >On 10/17/2011 1:02 PM, Ngo, Donald (HP Cloud Services : QA) wrote: >> Is this what you are looking for?: http://docs.openst

Re: [Openstack] OpenStack API v1.0 Removal from Nova

On 10/12/11 9:22 AM, "Jay Pipes" wrote: >On Wed, Oct 12, 2011 at 8:13 AM, Gabe Westmaas > wrote: >> I definitely get why developers working on the code base are in favor of >> this, especially for reasons 3 and 4 below. However, there are a couple >> of reason

Re: [Openstack] OpenStack API v1.0 Removal from Nova

I definitely get why developers working on the code base are in favor of this, especially for reasons 3 and 4 below. However, there are a couple of reasons that it might make sense to keep it, and I'd really like to hear from a different demographic, if at all possible. First, I'd like to hear fr

Re: [Openstack] [Nova] MySQL drivers in DB

+1 on modifying it in your environment, this seems outside the scope of migrations, though perhaps listed as a "best practice" for the deployment process. Similarly, I have been trying to decide what makes sense for indexes. Right now it would be a bad idea to run nova without adding some indexes

[Openstack] [QA] openstack-integration-tests

I'd like to try to summarize and propose at least one next step for the content of the openstack-integration-tests git repository. Note that this is only about the actual tests themselves, and says absolutely nothing about any gating decisions made in other sessions. First, there was widesprea

Re: [Openstack] Image Create in API version 1.1

Hi Phil, That functionality moved to a server action in 1.1: http://docs.openstack.org/api/openstack-compute/1.1/content/Create_Image-d1e4655.html Gabe From: "Day, Phil" mailto:philip@hp.com>> Date: Fri, 23 Sep 2011 18:38:58 +0100 To: "openstack@lists.launchpad.net

Re: [Openstack] Integration tests

On 9/12/11 2:54 PM, "Tim Simpson" wrote: >It would be advantageous for the tests to only use one client, whatever >it turns out to be. I think it would be most practical to use a bleeding >edge version of Nova client and add any features necessary to it in its >own repo directly or by somehow mi

Re: [Openstack] Status of OpenStack 1.1 API

Most of these issues (and a few more) are now tagged osapi-v1.1 (thanks waldon). If you do work on them please claim them first! Thanks for the help. Gabe On 9/8/11 9:32 AM, "Gabe Westmaas" wrote: >Hey Thierry, > >Here is a list the team compiled on the known gaps in the

Re: [Openstack] Status of OpenStack 1.1 API

Hey Thierry, Here is a list the team compiled on the known gaps in the 1.1 implementation. I haven't had a chance to file any bugs on these yet, but wanted to at least answer this email with the list. I split them roughly based on complexity. Most complex: resource uuids - there is a mixture of

Re: [Openstack] python-novaclient vs. python-openstack.compute

Hey Sandy, We hadn't shifted our focus over to the client yet - our assumption had been that the best course would be to version the existing library and move forward. However, that was definitely an assumption and if people have experience that says maybe we should explore a new client tied m

Re: [Openstack] Problem with "values" in JSON responses

Team titan will be implementing this, and the "values" array was one of the discussion points at the conference that didn't come to an immediate resolution. We will try to put together a reasonable approach that balances the goals of the "values" attributes as well as the goals of "jsonic" json

Re: [Openstack] Proposal to defer existing OS API v1.1 to Diablo, for greater stability in Cactus

Thanks Justin, appreciate the input! Answers inline. On Thursday, March 31, 2011 5:31pm, "Justin Santa Barbara" said: > I think there are a few distinct issues: > > 1) XML support. I was thinking that most XML issues would also be issues in > the JSON, so validating the XML will also serve a

Re: [Openstack] Proposal to defer existing OS API v1.1 to Diablo, for greater stability in Cactus

On Wednesday, March 30, 2011 6:16pm, "Rick Clark" said: > ___ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/Li

Re: [Openstack] server affinity

gt; Nova, but suggest all projects use the same locality zone names/tags > to ensure cross-project locality. > > So, "yes", and don't make it nova-specific. :) > > -Eric > > On Mon, Feb 28, 2011 at 04:48:25PM -0500, Gabe Westmaas wrote: >> Hey All, &g

[Openstack] server affinity

Hey All, For various reasons, Rackspace has a need to allow customers to request placement in the same zone as another server. I am trying to figure out if this is generically useful, or something that should be outside of core. The idea is that if you don't specify an affinity ID one will ge

Re: [Openstack] OpenStack Compute API 1.1

e and usable OpenStack Compute API. This means that using only >> the API and tools that interact with the OpenStack Compute API Nova can be >> installed and configured; once running all of the Nova features and >> functions for VM, Network, and Volume provisioning and management are &g

[Openstack] OpenStack API 1.1

A blueprint and proposed spec for OpenStack API 1.1 has been posted and I would love to get feedback on the specification. Blueprint: https://blueprints.launchpad.net/nova/+spec/openstack-api-1-1 Spec wiki: http://wiki.openstack.org/OpenStackAPI_1-1 Detailed Spec: http://wiki.openstack.org/Open

wrong message

Below is a slightly edited version of a tcp dump on the activemq side of a transaction between an NMS 1.2 client and ActiveMQ 5.3. MESSAGE message-id:ID:arch3.bmdc-35562-1269288301113-2:1918:-1:1:14 BEGIN transaction:ID:IAD2DEPLOY01-56247-634052078212143799-1:885:1 message-id:ID:arch3.bmdc-35562

Re: NMS / ActiveMQ 5.3 / "Unable to read beyond the end of the stream."

We see the same exception against a 5.1 broker, although we have not been able to pin down exactly when it happens, and it certainly isn't as frequently as every 60 seconds. Gabe -Original Message- From: "Timothy Bish" Sent: Monday, October 12, 2009 10:47am To: users@activemq.apache.or

RE: 1->N queue model for high volume traffic?

I have an application with similary requirements, and we considered this route as well. Whether or not there are problems with this really depends on how messages come in. For example, for us, we have the potential for hundreds of thousands of queues based on algorithm you described, and not o

Re: Horizontally scaling JMS listener/consumer application.....in Active MQ environment

Both queues and topics can have multiple consumers, however the purpose of a topic is so that each consumer gets a copy of the message, while the purpose of a queue is that each message is only delivered to one consumer. Gabe -Original Message- From: "G1" Sent: Wednesday, September 23,

consumer timeout for client_acknowledge or transac ted sessions

Hello, I am a little confused about something and am having a hard time finding the information in the documentation, although I definitely think its possible I just don't know how to read it. In either a transacted session or a client acknowledge mode session, if a consumer fails to commit or

RE: Why configure destinations in the broker?

So that is the intended use case keeping entities in the system from creating queues that you have not authorized, interesting. Thank you for the input, I appreciate it. Nick Gabe Westmaas wrote: > > You can disable the creation of queues if you want to limit usage of your > broker t

RE: Why configure destinations in the broker?

You can disable the creation of queues if you want to limit usage of your broker to specific, known queues. Gabe -Original Message- From: "yesnid" Sent: Friday, January 30, 2009 1:08pm To: users@activemq.apache.org Subject: Why configure destinations in the broker? Hello All, I am cu

NMS and non-responsive queue

Hey all, One of the developers in our company is writing an application that uses NMS and every once in a while the queue becomes unresponsive to consumers, although producers can continue to produce to it. Other times a message will get stuck at the top of the queue and producers and consumer

[jira] Commented: (AMQ-763) closing of Message Groups not working

[ https://issues.apache.org/activemq/browse/AMQ-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48329#action_48329 ] Gabe Westmaas commented on AMQ-763: --- I will be out of the office until December 27th

Re: Message is sendt more than once

mq.apache.org Subject: Re: Message is sendt more than once Hi i am using the following :session =con.createSession(true,Session.CLIENT_ACKNOWLEDGE); On Mon, Dec 1, 2008 at 2:42 PM, Gabe Westmaas <[EMAIL PROTECTED]>wrote: > Could be an acknowledgment issue, what type of acknowledge (client

RE: Message is sendt more than once

Could be an acknowledgment issue, what type of acknowledge (client, auto, dups ok, transaction) are you using? -Original Message- From: "Lars Eirik Rønning" <[EMAIL PROTECTED]> Sent: Monday, December 1, 2008 8:16am To: users@activemq.apache.org Subject: Message is sendt more than once Hi

RE: Question about Logging in ActiveMQ 5.1

Not by default, I don't believe. Our organization added logging to a few places to achieve just that, but frankly it seems like overkill and since I took over the project I have never actually had to use those logs. You can use camel inside the broker to log messages when they arrive, I don't

RE: Monitoring Queue Consumers

If that's the only queue, I think if you use activemq-admin you can see all clients connected to the broker. You have to sift through a little bit to see the information though. activemq-admin query or activemq-admin query | grep RemoteAddress to just see the ip and port numbers. Gabe

RE: Producer hanged when sending 6M ByteMessage

How are you persisting the message? MySQL has a default max packet size of 1M, and I'm sure other databases have similar limits. Also, if you aren't consuming the messages you may exceed memory limits on the broker, check the Home page on the web monitor and see if its at 99%. You can adjus

store and forward behavior

Hello all, We are using activemq 5.1.0 in a linux environment and 1.5.0 jvm with a network of brokers. Our activemq.xml file is attached, and it is mirrored on the other broker (we found that duplex=true didn't work for us, as it forwarded ALL queues, regardless of settings). Note that we also