On 03/16/2015 03:24 PM, Doug Hellmann wrote:
Excerpts from Adam Young's message of 2015-03-16 14:17:16 -0400:
On 03/16/2015 01:45 PM, Doug Hellmann wrote:
All of these are reasons we have so far resisted building a service to
deploy updates to oslo.config's input files, and rely on
Emilien Macchi [mailto:emil...@redhat.com] on Monday, March 16, 2015 09:00
wrote:
On 03/16/2015 11:13 AM, Colleen Murphy wrote:
This thread is to follow up on our IRC discussion today. In today's
meeting we started discussing whether we want to pursue applying to
move under the OpenStack
- Original Message -
From: Adam Young ayo...@redhat.com
To: openstack-dev@lists.openstack.org
Sent: Tuesday, March 17, 2015 8:59:17 AM
Subject: Re: [openstack-dev] [keystone][congress][group-policy] Fetching
policy from a remote source
On 03/16/2015 03:24 PM, Doug Hellmann
While working to remove deps on /root/openrc [1][2], I found that we have a
package for fule-utils to provide a tool called fdb-cleaner. It looks like
the source is [3] and its built at [4]
I see that there are no tests, or CI to test integrity of the code there. I
propose that we move this to
Robert,
Thanks for sharing this!
Now I know how to speed up start of Rally ;)
Best regards,
Boris Pavlovic
On Tue, Mar 17, 2015 at 2:23 AM, Robert Collins robe...@robertcollins.net
wrote:
So, one of the things that we sometimes do in an __init__.py is this:
all = [submodule]
import
Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300:
I've raised this in reviews 157135 and 153966, but I think it deserves
a thread of its own.
I think universal wheels are useful - they are simple to build and
publish - we don't need to do one wheel per Python version.
On 01:15 Thu 12 Mar , Fox, Kevin M wrote:
Also, can
https://review.openstack.org/#/c/163647https://review.openstack.org/#/c/163647/2
be considered. all it does is move code from the accepted nfs.py to posix.py
as described in the approved spec. This enables all posix complient file
On 03/16/2015 05:52 PM, Bryan D. Payne wrote:
I have about one more week working with OpenStack full time. After
that, I am still planning on coming to the summit in May, and would be
happy to help with any final transition pieces at that time. And I'll
continue being available at this email
On 17 March 2015 at 13:22, Doug Hellmann d...@doughellmann.com wrote:
Excerpts from Robert Collins's message of 2015-03-17 12:54:00 +1300:
I've raised this in reviews 157135 and 153966, but I think it deserves
a thread of its own.
I think universal wheels are useful - they are simple to build
Hi Sean,
2015-03-16 23:15 GMT+09:00 Sean Dague s...@dague.net:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1:
Hi Tim,
I am interest in it. But I am UTC+8 time, so the 8a Pacific is not
convenient. No matter, I can read the minutes if it has.
I am sorry for not contribute the inter-domain text to delegation draft ,
I think this IRTF draft mentioned some
On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote:
I am worried about SDKs making requests that have additional JSON
attributes that were previously ignored by v2, but will be considered
invalid by the v2.1 validation code. If we were to just strip out the
extra items,
+1 Rob. Warning could carry/indicate all the attributes ignored.
-Original Message-
From: Robert Collins [mailto:robe...@robertcollins.net]
Sent: Monday, March 16, 2015 7:56 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova] what is
The last couple of meetings have been visibly low on participation. Most
notably anyone not involved with the planned schedule is not participating.
Often I find that the discussion leeds to wanting to talk with more of the
devs, but they are frequently not available.
Is there any reason for the
Hi,
I will not be available tomorrow morning for the meeting. Please feel free to
go ahead without me.
Cheers,
Robert
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
On Mon, Mar 16, 2015 at 4:35 PM, Andrew Woodward xar...@gmail.com wrote:
While working to remove deps on /root/openrc [1][2], I found that we have
a package for fule-utils to provide a tool called fdb-cleaner. It looks
like the source is [3] and its built at [4]
I see that there are no
I've raised this in reviews 157135 and 153966, but I think it deserves
a thread of its own.
I think universal wheels are useful - they are simple to build and
publish - we don't need to do one wheel per Python version.
However, right now I'm fairly sure that we're not exporting the
requirements
2015-03-17 0:08 GMT+09:00 John Garbutt j...@johngarbutt.com:
On 16 March 2015 at 14:15, Sean Dague s...@dague.net wrote:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use =
2015-03-17 11:56 GMT+09:00 Robert Collins robe...@robertcollins.net:
On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com wrote:
I am worried about SDKs making requests that have additional JSON
attributes that were previously ignored by v2, but will be considered
invalid by the
Meeting on #openstack-meeting at 1500 UTC (9:00AM MDT)
1) Patch status -
https://etherpad.openstack.org/p/kilo-nova-priorities-tracking
--
Don Dugger
Censeo Toto nos in Kansa esse decisse. - D. Gale
Ph: 303/443-3786
So I've successfully done a deployment to a QuintupleO environment. \o/
I don't have a nice polished demo video yet or anything, but I did go
ahead and write up some general thoughts about the process I followed
here: http://blog.nemebean.com/content/quintupleo-success
I realize it's not super
From: Sean Dague s...@dague.net
Sent: Thursday, March 12, 2015 9:09 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [stacktach] [oslo] stachtach - kombu - pika ??
On 03/10/2015 12:56 PM, Joshua Harlow wrote:
I saw the following on
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1: openstack_compute_api_v2
/v2: openstack_compute_api_v2
/v2.1:
We had the following exchange on the Fedora Cloud list, but I think it
now more properly belongs here;
On 03/12/2015 12:37 PM, Daniel P. Berrange wrote:
On Thu, Mar 12, 2015 at 12:17:06PM -0400, Adam Young wrote:
So, it looks like xz is not supported by OpenStack.
So what you say OpenStack
Hi Mike,
The points was, there is no real need or real use case for archiving the db
as the nova-mange does.
What is the exact use case ? Auditing ? Accounting ?
* Keystone allows permanent delete, if you need to do auditing probably
the user accounts would the primary target for saving.
*
Excerpts from Akihiro Motoki's message of 2015-03-16 11:53:07 +0900:
Thanks Doug,
It is a good direction to have the stable branches for all libraries.
It seems better that I wait for adopting oslo.policy in django-openstack-auth.
In the current infra, a library specified in LIBS_FROM_GIT
- Original Message -
Dear Neutron developers,
I have been playing with OpenStack Neutron since Grizzly but never
committed a bug upstream. I want to fix a neutron bug and do not see
any unassigned low-hanging-fruit starter bug in
Looks great and it is really helpful) I've already started to play with it
and test it.
Regards,
Anastasia Kuznetsova
On Mon, Mar 16, 2015 at 1:19 PM, Renat Akhmerov rakhme...@mirantis.com
wrote:
Thank you so much! I’m excited and looking forward to play with it )
How about moving (or
Oops, thanks, I abandoned my one.
2015-03-16 17:09 GMT+08:00 Chen CH Ji jiche...@cn.ibm.com:
oops, duplication ... I submitted changes to spec after got this info
since it make sense to me ...
https://review.openstack.org/#/c/164229/
https://review.openstack.org/#/c/164234/
Best Regards!
2015-03-16 12:26 GMT+08:00 Christopher Yeoh cbky...@gmail.com:
So ultimately I think this is a style issue rather than a technical one. I
think there
are situations where one way looks clearer than another the other way
does. Sorry I can't get around to putting up a couple of examples,
ATM
Hi,
This is a reminder about weekly team meeting that we’ll have today. Please note
that today (and possibly next several times) we’ll start at 16.20 UTC instead
of 16.00 UTC due to schedule issues within the team.
Agenda:
Kilo-3 progress
Engine refactoring
Next plans
Renat Akhmerov
@
Hi,
I could find some tests in tempest are still not tagged with services as
per blueprint
https://blueprints.launchpad.net/tempest/+spec/add-service-tags
eg: .tempest.api.compute.test_live_block_migration:test_iscsi_volume
(should have volume tag)
I have started adding tags where appropriate
On 03/15/2015 03:23 AM, Christopher Yeoh wrote:
On Sat, 28 Feb 2015 09:51:27 -0700
Jay Pipes jaypi...@gmail.com wrote:
On 02/26/2015 04:27 AM, Sean Dague wrote:
In trying to move the flavor manage negative tests out of Tempest
and into the Nova functional tree, I ran into one set of tests
On 03/15/2015 10:26 AM, Lingxian Kong wrote:
2015-03-11 15:57 GMT+08:00 Qiao, Liyong liyong.q...@intel.com:
Hi all
will instance action deprecate in feature since we have notify mechanism now?
Currently, nova have instance action and instance event action to record
specify actions performed
Based on the results of https://doodle.com/wuhsuafq5tibzugg we have two
contenders, in 1st place is 1500 on Tuesdays and in 2nd is 1600 on
Thursdays. 1500 Tuesdays has an opening in #openstack-meeting-4 and 1600
Thursdays has openings in #openstack-meeting and #openstack-meeting-3.
Since 1500 on
On Mon, Mar 16, 2015 at 10:10 AM, Adam Young ayo...@redhat.com wrote:
Oslo policy has been released as a stand alone library. This is great, in
that the rules engine is relatively non-applicaition specific, and I assume
that all of the policy based project are planning to migrate over to
Hi folks,
due to some technical issues we were unable to merge Cliff integration patches
to keep ISO build jobs alive.
Since now the problem is fixed and we are unblocked, I’d like to ask for a FFE
in order to merge that all.
- romcheg
signature.asc
Description: Message signed with OpenPGP
On 03/16/2015 11:13 AM, Colleen Murphy wrote:
This thread is to follow up on our IRC discussion today. In today's
meeting we started discussing whether we want to pursue applying to move
under the OpenStack namespace and what pros and cons are. One concern
that was brought up was that our
On 16 March 2015 at 14:15, Sean Dague s...@dague.net wrote:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1:
Oslo policy has been released as a stand alone library. This is great,
in that the rules engine is relatively non-applicaition specific, and I
assume that all of the policy based project are planning to migrate over
to using the policy library instead of the incubated version.
Part of the
On Mar 16, 2015, at 10:08 AM, John Garbutt j...@johngarbutt.com wrote:
Drop of /v1.1 ?
---
Only new deploys are really going to base off of our in tree
config. I'm not convinced that we want to encourage people setting up
new /v1.1 endpoint in tree.
I'm not convinced there
On 03/16/2015 11:22 AM, Russell Bryant wrote:
On 03/16/2015 11:08 AM, John Garbutt wrote:
While its not under Nova's control, I think we need to consider the
keystone catalog here.
It feels nice to have an explicit entry for v2.1, that people start
using once the client is updated to support
On 03/16/2015 05:33 AM, joehuang wrote:
[Topic]: Huge token size
Hello,
As you may or may not be aware of, a requirement project proposal
Multisite[1] was started in OPNFV in order to identify gaps in
implementing OpenStack across multiple sites.
Although the proposal has not been
- Original Message -
From: Rohan Kanade openst...@rohankanade.com
To: openstack-dev@lists.openstack.org
Sent: Monday, March 16, 2015 1:13:12 PM
Subject: [openstack-dev] [qa][tempest] Service tag blueprint incomplete
Hi,
I could find some tests in tempest are still not tagged
On 03/16/2015 11:08 AM, John Garbutt wrote:
While its not under Nova's control, I think we need to consider the
keystone catalog here.
It feels nice to have an explicit entry for v2.1, that people start
using once the client is updated to support microversions. DefCore
would eventually
Hello Nova!
I'd like to ask community to help me with some unclear things. I'm
currently working on adding persistent storage support into a parallels
driver.
I'm trying to start VM.
nova boot test-vm --flavor m1.medium --image centos-vm-32 --nic
net-id=c3f40e33-d535-4217-916b-1450b8cd3987
It is perhaps worth mentioning that there is an effort to implement a
generic synchronization mechanism (between Neutron and backend
controllers/devices) in the ML2 plugin [1]. A possible framework for its
eventual implementation is in an early discussion/proof-of-concept WIP
state [2].
PTL Election details: https://wiki.openstack.org/wiki/PTL_Elections_April_2015
TC Election details: https://wiki.openstack.org/wiki/TC_Elections_April_2015
Please read the stipulations and timelines for candidates and electorate
contained in these wikipages.
There will be an announcement email
Hi all,
The feedback on the POC delegation proposal has been mostly positive. Several
people have asked for a meeting to discuss further. Given time zone
constraints, it will likely be 8a or 9a Pacific. Let me know in the next 2
days if you want to participate, and we will try to find a day
On Mon, Mar 16, 2015 at 8:10 AM, Adam Young ayo...@redhat.com wrote:
Oslo policy has been released as a stand alone library. This is great, in
that the rules engine is relatively non-applicaition specific, and I assume
that all of the policy based project are planning to migrate over to using
On Mar 10, 2015, at 6:00 PM, Devananda van der Veen devananda@gmail.com
wrote:
On Tue, Mar 10, 2015 at 12:12 PM Lauren Sell lau...@openstack.org
mailto:lau...@openstack.org wrote:
- Operators don’t want the wild west. They are nervous about dissolving the
integrated release,
Excerpts from Adam Young's message of 2015-03-16 11:10:01 -0400:
Oslo policy has been released as a stand alone library. This is great,
in that the rules engine is relatively non-applicaition specific, and I
assume that all of the policy based project are planning to migrate over
to using
On 03/16/2015 11:22 AM, Russell Bryant wrote:
On 03/16/2015 11:08 AM, John Garbutt wrote:
While its not under Nova's control, I think we need to consider the
keystone catalog here.
It feels nice to have an explicit entry for v2.1, that people start
using once the client is updated to support
On Mon, 16 Mar 2015 11:22:12 -0400
Russell Bryant rbry...@redhat.com wrote:
On 03/16/2015 11:08 AM, John Garbutt wrote:
While its not under Nova's control, I think we need to consider the
keystone catalog here.
It feels nice to have an explicit entry for v2.1, that people start
using
On Mon, 16 Mar 2015 10:15:50 -0400
Sean Dague s...@dague.net wrote:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
/v1.1:
Hey Everyone,
Thought I'd reach out to the ML to see if somebody might have some insight
or suggestions to a problem I've been trying to solve.
The short summary is:
During a dsvm-full run in the gate there are times when /dev/sdX devices on
the system may be created/deleted. The trick here
Hi.
My name is Luke and I am UX designer willing to contribute to OpenStack
user experience. I am currently digging through wiki trying to find out how
to contribute.
So far I kindly ask you to add me to OpenStack InVision account.
I am also wondering if there is any test instance with Horizon
Hi Sean-
On Mon, Mar 16, 2015 at 11:15 PM, Sean Dague s...@dague.net wrote:
Our current top level shipped example paste.ini for Nova includes the
following set of endpoint definitions:
[composite:osapi_compute]
use = call:nova.api.openstack.urlmap:urlmap_factory
/: oscomputeversions
I like proposal 1 better, but only because I am already familiar with how
plugins interact with keystoneclient. The websso work is (i think) pretty
close to getting merged, and could easily be tweaked to use a token plugin
(when it's ready). I think the same can be said for our k2k issue, but
On 02:22 Sat 07 Mar , Chen, Wei D wrote:
Hi,
I thought the feature should be approved as long as the SPEC[1] is merged,
but it seems I am wrong from the beginning[2], both of
them (SPEC merged and BP approval[4][5]) is necessary and mandatory for
getting some effective reviews, right?
On Tue, 17 Mar 2015 15:56:27 +1300
Robert Collins robe...@robertcollins.net wrote:
On 17 March 2015 at 14:27, Ken'ichi Ohmichi ken1ohmi...@gmail.com
wrote:
I am worried about SDKs making requests that have additional JSON
attributes that were previously ignored by v2, but will be
2015-03-17 13:25 GMT+08:00 Christopher Yeoh cbky...@gmail.com:
On Mon, 16 Mar 2015 11:22:12 -0400
Russell Bryant rbry...@redhat.com wrote:
On 03/16/2015 11:08 AM, John Garbutt wrote:
While its not under Nova's control, I think we need to consider the
keystone catalog here.
It
On 17 March 2015 at 09:30, Ben Nemec openst...@nemebean.com wrote:
So I've successfully done a deployment to a QuintupleO environment. \o/
\o/
--
Robert Collins rbtcoll...@hp.com
Distinguished Technologist
HP Converged Cloud
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on St. Patrick's Day[0], Tuesday March 17th, at 19:00 UTC in
#openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is
welcome to to add agenda
On 03/13/2015 05:53 AM, Jan Provaznik wrote:
On 03/10/2015 05:53 PM, James Slagle wrote:
On Mon, Mar 9, 2015 at 4:35 PM, Jan Provazník jprov...@redhat.com wrote:
Hi,
it would make sense to have a library for the code shared by Tuskar UI and
CLI (I mean TripleO CLI - whatever it will be, not
Hi,
Is there any process we follow to create the release notes (ex:
https://wiki.openstack.org/wiki/ReleaseNotes/Juno) for each release of
OpenStack, by collection details across different projects in OpenStack.?
Regards
Kanagaraj M
Hi All,
Lastly , I would like to know whether the predefined secret names
private_key”,
“public_key”, and “private_key_passphrase” in RSA containers has any
logical relation with the secret reference.
For ex : If the name of the secret is private_key , should the secret_ref
be necessarily a
HI Asha,
It looks like your curl command is malformed, which is why you’re getting all
the curl errors. You need to quote the entirety of the payload, like so:
curl -X POST -H 'content-type:application/json' -H 'X-Project-Id: 12345' -d '{
name: container1 ,type: rsa,secret_refs: [ { name:
I have recently accepted a new position with a company that does not work
with OpenStack. As a result, I'll be transitioning away from this
community. As such, I wanted to offer a few quick notes:
* OpenStack Security Guide -- I have transitioned leadership of this
security documentation effort
Hello again Asha,
Yes, the predefined secret names in an RSA container should match up with
secret refs for those actual things. “private_key” should point to the private
key of the RSA pair, “public_key” should point to the matching public key.
private_key_passphrase is optional, and it is
Hi All,
Could any one help me out with the execution of the command for creating
the container .
Please find the command and the response below :
root@barbican:~# curl -X POST -H 'content-type:application/json' -H
'X-Project-Id: 12345' -d { name: container1 ,type:
rsa,secret_refs: [ { name:
Hi All,
Could any one help me out with the execution of the command for creating
the container .
Please find the command and the response below :
root@barbican:~# curl -X POST -H 'content-type:application/json' -H
'X-Project-Id: 12345' -d { name: container1 ,type:
rsa,secret_refs: [ { name:
So, one of the things that we sometimes do in an __init__.py is this:
all = [submodule]
import submodule
This means users can do
import mymodule
mymodule.submodule
and it works.
This is actually a bit of an anti-pattern in the Python space, because
to import mymodule.othersubmodule we'll
Hi,
It looks like your patch ran with no problems. The only fail is a non voting
test which means that it's not reliable. You should be good on the CI side,
just need to wait to get reviews for your patch.
Thanks
Mohammed
Sent from my iPhone
On Mar 16, 2015, at 1:05 AM, kwon-ho lee
Hi Adam,
For the most part we've been looking at Congress policy as complementary to
Oslo policy, so we haven’t yet tried to incorporate Oslo policy into Congress
(though I did some experiments with that a while back). But looking forward,
it would definitely be convenient if there were some
Excerpts from Adam Young's message of 2015-03-16 14:17:16 -0400:
On 03/16/2015 01:45 PM, Doug Hellmann wrote:
All of these are reasons we have so far resisted building a service to
deploy updates to oslo.config's input files, and rely on provisioning
tools to update them.
Have we
On 03/16/2015 02:59 PM, Tim Hinrichs wrote:
Hi Adam,
For the most part we've been looking at Congress policy as complementary to
Oslo policy, so we haven’t yet tried to incorporate Oslo policy into Congress
(though I did some experiments with that a while back). But looking forward,
it
On 03/16/2015 01:45 PM, Doug Hellmann wrote:
All of these are reasons we have so far resisted building a service to
deploy updates to oslo.config's input files, and rely on provisioning
tools to update them.
Have we consider using normal provisioning tools for pushing out
changes to policy
I am trying to understand which projects support a previous link for
pagination and how that support is implemented.
I believe that supporting a next link is quite common and is implemented
as:
1. Caller includes a marker query string parameter which represents the
ID of the last item in the
Hi all,
Please consider this announcement as an added awareness note for the status of
Kilo (k-3) development. [1] shows the lists of features that we intend to land
into Kilo-3.
The candidates for FFE are:
* Artifacts [2]
* Catalog Index Service [3]
* Policy Enforcer
Hello,
I read blueprint which You send but I don't know how it should solve for
example problems like can be in l2pop mechanism. It send message to fanout
cast and forget about it. There is no any exception in port_update_postcommit
operation but message can be not consumed by some agents (or
interested
Thx
Uri (Oo-Ree)
C: 949-378-7568
From: Tim Hinrichs [mailto:thinri...@vmware.com]
Sent: Monday, March 16, 2015 11:05 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Congress] [Delegation] Meeting scheduling
Hi all,
The feedback on the
Hello,
Thanks. I didn't find it before.
When we will upgrade our infra we will see if this problem will still present.
I hope that this was due to that bug maybe and will be fixed then :)
--
Pozdrawiam / Best regards
Sławek Kapłoński
sla...@kaplonski.pl
Dnia poniedziałek, 16 marca 2015
On Sun, Mar 15, 2015 at 22:37:59, Sławek Kapłoński wrote:
Maybe good idea for the beginning could be to implement some periodic
task
called from agent to check db config and compare it with real state on
host?
What do You think? Or maybe I'm competly wrong with such idea and it
should be
oops, duplication ... I submitted changes to spec after got this info since
it make sense to me ...
https://review.openstack.org/#/c/164229/
https://review.openstack.org/#/c/164234/
Best Regards!
Kevin (Chen) Ji 纪 晨
Engineer, zVM Development, CSTL
Notes: Chen CH Ji/China/IBM@IBMCN Internet:
Thank you so much! I’m excited and looking forward to play with it )
How about moving (or copying) this code into one of our official repos?
“mistral-extra” seems to be the right place since from the very beginning it
was intended to be used for various tools and examples.
Renat Akhmerov
@
Le 14/03/2015 01:13, Chris Friesen a écrit :
Hi,
I've recently submitted some code for review at
https://review.openstack.org/163060;.
The change involves adding a new reported_at field to the Service
object class, and I'd like some feedback on the object-versioning
aspects of that:
1)
87 matches
Mail list logo
