Hi there,
we raised a bug https://bugs.launchpad.net/devstack/+bug/1193112 where the
default configuration of swift in devstack interacts badly with keystone. We
end up with the following exception iwth swift-proxy-server:
$ cd /opt/stack/swift /opt/stack/swift/bin/swift-proxy-server
Mark Washenberger wrote:
* There are efforts that span multiple projects but work directly on the
project code repositories, like integrated release, or stable
maintenance, or vulnerability management (collectively called for the
convenience of this thread horizontal efforts).
Greetings Stackers!
This is the Monday update. Looks like we had a few rebases that failed. The
developers involved are working on them as you read this and will be posting
new versions as soon as they can. This kind of thing happens when a patch takes
too long to review and the code base
On 25 June 2013 20:19, Thierry Carrez thie...@openstack.org wrote:
without a code repo today, so it's a moot point : I suggest saying
that until it is revisited, there cannot be a Program w/o a code repo.
What we have today is a number of efforts that are pretty central to
OpenStack (like
Today in the Project release status meeting we'll be looking into
Swift 1.9.0 release, Neutron renaming plan and havana-2 milestone progress.
Feel free to add extra topics to the agenda:
[1] http://wiki.openstack.org/Meetings/ProjectMeeting
All Project Technical Leads should be present (if you
On Mon, Jun 24, 2013 at 10:50:18PM +0100, Mark McLoughlin wrote:
Hey,
Pulling this out of gerrit for discussion.
Background is one of my patches to diskimage-builder was -1ed because I
terminated the title line of the commit message with a period:
https://review.openstack.org/33262
Robert Collins wrote:
So, doing [the 6 monthly] releases and stable branches seem like the
same thing to me : it's packaging up the project output for
consumption by redistributors (and low-resource risk-averse orgs).
That totally makes sense to me as a program - but I think calling it
Don't like dragging up old threads, but I spoke to Navneet on IRC, and
I missed this thread first time.
The Disk_Config setting is used by XenAPI to decide when it should
resize the server's partition and filesystem, but nova currently only
does this root disks that have a single partition where
On 25/06/13 10:52, Rahul Sharma wrote:
Hi All,
I have setup multi-node openstack setup using grizzly release and ubuntu
12.04 distribution. Since there is no support for individual user to
change his/her password, someone has provided a patch for the same.
Ref:-
the patch use keystone v3 , in grizzly horizon use keystone v2.
On Tue, Jun 25, 2013 at 4:52 PM, Rahul Sharma rahulsharma...@gmail.comwrote:
Hi All,
I have setup multi-node openstack setup using grizzly release and ubuntu
12.04 distribution. Since there is no support for individual user to
Sean Dague s...@dague.net writes:
Cool proposed change coming in from the Heat folks -
https://review.openstack.org/#/c/34278/ to use dib to build their base
images in devstack. From a development perspective, will make
experimenting with Heat a lot easier.
However, this raises an issue as
Hi Shake,
As per the patch, it seems that they have added check for v2_0.
def tenant_create(request, name, description=None, enabled=None,
domain=None):
manager = VERSIONS.get_project_manager(request, admin=True)
*if VERSIONS.active 3:*
return manager.create(name, description,
On Tue, Jun 25, 2013 at 6:21 PM, Gary Kotton gkot...@redhat.com wrote:
On 06/25/2013 06:03 AM, Zhongyue Luo wrote:
Hi team
I'm currently trying to move the generate_sample.sh script in nova to
oslo.
Before pushing the patch to gerrit, I wanted to give the output
directory a default
Hey,
On Mon, 2013-06-24 at 11:50 +0200, Thierry Carrez wrote:
The TC would bless the *mission statement* of the program rather than
the specific set of projects implemented to reach that goal.
This is a really nice way of putting it and you've captured a bunch of
other stuff very well too.
Close, the agent doesn't actually do the resizing, but many people use
Sysprep (indiscriminately) for this purpose.
I'm more familiar with Glance metadata, but it certainly seems to me that
having the server metadata available to instances (via MDS and config
drive) makes a ton of sense.
Richard
On Mon, 2013-06-24 at 13:14 -0400, Monty Taylor wrote:
* Where would openstack/requirements fall ?
I think openstack/requirements sits under oslo - although right now
it's a joint-venture between oslo and infra.
If you look at the Oslo mission statement(s):
Hi everyone,
Just a quick meeting to sync up today. No real agenda.
p
Peter J. Pouliot, CISSP
Senior SDET, OpenStack
Microsoft
New England Research Development Center
One Memorial Drive,Cambridge, MA 02142
ppoul...@microsoft.commailto:ppoul...@microsoft.com | Tel: +1(857) 453 6436
I think the allure of labeling this as 'orchestration' comes from the reliance
on multiple services to make this feature work.
Heck, booting an instance is something that should be handled by
'orchestration'. Booting an instance requires the cooperation of many services
-- and while I won't go
It is not entirely clear to me what your desired behavior is, but I won't let
that stop me from hazarding a guess.
Horizon now supports keystone API versions 2.0 and 3. By default, if the
keystoneclient that is installed supports v3, then that is what Horizon will
use. However, you can
Meeting ended Tue Jun 25 16:18:14 2013 UTC. Information about MeetBot at
http://wiki.debian.org/MeetBot . (v 0.1.4)
Minutes:
http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-06-25-16.00.html
Minutes (text):
On Tue, Jun 25, 2013 at 7:22 AM, Andrew Laski andrew.la...@rackspace.comwrote:
I have a couple of reviews up to introduce the concept of shelving an
instance into Nova. The question has been raised as to whether or not this
belongs in Nova, or more rightly belongs in Heat. The blueprint for
Anne Gentle wrote:
Dare I ask, what about TryStack? Infra seems to get a ton under it but
that's where I'd place it if I had to state a preference.
I'd see TryStack as a separate program, with the goal of maintaining an
infrastructure that lets users play with OpenStack. That goal sounds a
bit
Mark McLoughlin wrote:
[1] - ok, some caveats on what I mean by integrated release ...
We're producing software for people who want to build clouds. A software
product, for want of a better term.
Right now, we say the official service projects (definition: a project
which exposes a REST
On 06/25/2013 12:42 PM, Thierry Carrez wrote:
Anne Gentle wrote:
Dare I ask, what about TryStack? Infra seems to get a ton under it but
that's where I'd place it if I had to state a preference.
I'd see TryStack as a separate program, with the goal of maintaining an
infrastructure that
In this case, the exception is just hard to debug, and not something we
expected in our design. The thorough solution would be to debug further to see
the root cause, and deal with it as I suggested in the code review.
However, If it is time consuming to debug, we can put the patch in there
On 06/25/13 at 09:42am, Joe Gordon wrote:
On Tue, Jun 25, 2013 at 7:22 AM, Andrew Laski andrew.la...@rackspace.comwrote:
I have a couple of reviews up to introduce the concept of shelving an
instance into Nova. The question has been raised as to whether or not this
belongs in Nova, or more
Hi folks,
Recently I've faced strange problem with devstack on Ubuntu LTS 12.04.
./stack.sh script stalls on network creation, quantum net-create never
returns response.
More detailed investigation showed that quantum-server is stuck on
connecting to amqp queue.
Moreover, any other quantum agent
I like the programs idea and the direction this thread is going.
As we reconsider the relationship of repos and programs to the OpenStack
project, I think we should include one more aspect of taxonomy.
We have several orgs on github related to openstack:
openstack/
openstack-infra/
On Mon, Jun 24, 2013 at 11:53 PM, John Griffith john.griff...@solidfire.com
wrote:
All,
I wanted to loop the larger community in on some discussions that have
been taking place on #openstack-cinder.
During the Summit we talked about switching to Pecan for our API/Web
framework. Since
James E. Blair wrote:
I propose that in the future, we adopt the following strategy:
* Any repo associated with an official OpenStack program is entitled to
use the openstack org.
* Programs may request an org for their program, with justification,
but in general we should limit the
On 06/25/2013 03:15 PM, Ray Pekowski wrote:
On Jun 25, 2013 1:09 PM, Qing He qing...@radisys.com
mailto:qing...@radisys.com wrote:
Basically, when 'unexpected' happens, someone (e.g., operator) needs
to know about it and look into it to see if it is something benign or
fatal. If it is
I think this discussion could potential shape a new business model for
how contributors are supported as they work with OpenStack.
One difficulty I foresee with Jesus' model is the potential for the
Contributed for: line playing a role in the decision to approve a
patch vs recommending it
On Mon, Jun 24, 2013 at 7:48 AM, Elizabeth Krumbach Joseph
l...@princessleia.com wrote:
The OpenStack Infrastructure (Infra) team is hosting our weekly
meeting tomorrow, Tuesday June 25th, at 19:00 UTC in
#openstack-meeting
Meeting minutes+logs now available here:
Minutes:
Agree! Let someone know and keep going unless someone wants to interrupt it or
do something. (Does there exist a mechanism already to do this?)
-Original Message-
From: Russell Bryant [mailto:rbry...@redhat.com]
Sent: Tuesday, June 25, 2013 12:21 PM
To: openstack-dev@lists.openstack.org
Does the log alert operator? Something like SNMP trap?
From: Ray Pekowski [mailto:pekow...@gmail.com]
Sent: Tuesday, June 25, 2013 12:16 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] Should RPC consume_in_thread() be more fault
tolerant?
On Jun 25, 2013 1:09 PM, Qing
On 06/25/2013 04:08 PM, Qing He wrote:
Does the log alert operator? Something like SNMP trap?
You can turn on a mode where it will emit a notification, and
notifications can be published via AMQP.
--
Russell Bryant
___
OpenStack-dev mailing list
Clarify, operator does not have to go through a long log to find the issue.
Instead, he/she needs to be notified that something severe/unexpected just
happened and he/she needs to check it out.
From: Qing He
Sent: Tuesday, June 25, 2013 1:09 PM
To: 'OpenStack Development Mailing List'
Subject:
On 26 June 2013 10:54, Steve Baker sba...@redhat.com wrote:
What elements are you using, that you're dragging in these two
components for your tempest test image?
tie heat-cfntools depends on os-apply-config and os-refresh-config,
which seems inverted to me. This whole area may change soon
Hopefully I've gotten the attention of networking folk with that
subject. We have an odd routing problem in our devtest environment,
which I haven't figured out the cause of - but I'm wondering if anyone
has some insight before I start climbing through the linuxbridge
kernel code :)
In the
39 matches
Mail list logo
