Excerpts from Boris Pavlovic's message of 2015-06-02 16:36:20 -0700:
> Jeremy,
>
> > the Infrastructure Project is now past 120 repos with more
> > than 70 core reviewers among those.
>
>
> I dislike the idea of having 120 repos for single tool. It makes things
> complicated for everybody:
> do
On 06/03/2015 12:16 AM, Jens Rosenboom wrote:
I'm wondering though whether the current API behaviour here should be
changed more generally. Is there a plausible reason to silently
discard options that are not allowed for non-admins? For me it would
make more sense to return an error in that case
Guys,
I will try to summarize all questions and reply on them:
*- Why not splitting repo/plugins?*
I don't want to make "architectural" decisions based on "social" or
"not enough good tool for review" issues.
If we take a look at OpenStack that was splited many times: Glance,
Cinder, ...
2015-06-01 13:40 GMT+02:00 John Garbutt :
> On 31 May 2015 at 14:15, Xu, Hejie wrote:
>> Replied in line with prefix [alex]
>>
>> -Original Message-
...
>> 2)
>> We also agreed that all micro version bumps need a spec, to help avoid is
>> adding more "bad" things to the API as we try and
I'm not sure if you can test this behaviour on your own because it requires
the VMware plugin and the eventlet handling of backend response.
But the issue was manifesting and had to be fixed with this mega-hack [1].
The issue was not about several workers executing the same code - the
loopingcall
[Updated with additional information.]
Hello,
I'm pleased to announce the development of a new project called Mercador
(Portuguese for “merchant”). Mercador will provide a mechanism for integrating
OpenStack cloud services from one cloud service provider (CSP) into the set of
services publish
Colleen Murphy wrote:
>
> 3) Manually abandon after N months/weeks changes that have a -1 that was
> never responded to
>
> ```
> If a change is submitted and given a -1, and subsequently the author
> becomes unresponsive for a few weeks, reviewers should leave reminder
> comments on the review
On 3 June 2015 at 07:12, John Griffith wrote:
>
>
> On Tue, Jun 2, 2015 at 7:19 PM, Ian Wienand wrote:
>
>> On 06/03/2015 07:24 AM, Boris Pavlovic wrote:
>>
>>> Really it's hard to find cores that understand whole project, but
>>> it's quite simple to find people that can maintain subsystems of
On Tue, Jun 2, 2015 at 7:19 PM, Ian Wienand wrote:
> On 06/03/2015 07:24 AM, Boris Pavlovic wrote:
>
>> Really it's hard to find cores that understand whole project, but
>> it's quite simple to find people that can maintain subsystems of
>> project.
>>
>
> We are made wise not by the recollecti
Eric,
On Jun 2, 2015, at 10:07 PM, Eric Windisch
mailto:e...@windisch.us>> wrote:
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto
mailto:adrian.o...@rackspace.com>> wrote:
I have reflected on this further and offer this suggestion:
1) Add a feature to Magnum to auto-generate human readable name
When you update an environment in Murano it will update underlying stack.
You should not see a new stack for the same environment. If you have a
PostgresDB deployed and then add a Tomcat application you will see that
stack was updated with new resources. There is no dependency between Tomcat
and Po
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto
wrote:
> I have reflected on this further and offer this suggestion:
>
> 1) Add a feature to Magnum to auto-generate human readable names, like
> Docker does for un-named containers, and ElasticSearch does for naming
> cluster nodes. Use this feature
On 06/02/2015 05:41 PM, James E. Blair wrote:
> Hi,
>
> This came up at the TC meeting today, and I volunteered to provide an
> update from the discussion.
>
> In general, I think there is a lot of support for a packaging effort in
> OpenStack. The discussion here has been great; we need to answ
I have reflected on this further and offer this suggestion:
1) Add a feature to Magnum to auto-generate human readable names, like Docker
does for un-named containers, and ElasticSearch does for naming cluster nodes.
Use this feature if no name is specified upon the creation of a Bay or Baymodel
On 06/02/2015 07:48 PM, Jay Pipes wrote:
On 06/02/2015 07:25 PM, Chris Friesen wrote:
In many cases only nova-compute can resolve races (resource tracking of
specific CPU cores, specific PCI devices, etc. in the face of parallel
scheduling) so unless we're going to guarantee no races then I th
On 06/02/2015 07:25 PM, Chris Friesen wrote:
On 06/02/2015 02:36 PM, Andrew Laski wrote:
There used to be a project that I think was looking for an API like
this to
provide a reservation system, Climate or Blazar or something. There
was brief
talk of providing something like it for that use cas
I think that we did not come to a conclusion in today's IRC meeting.
Adrian proposed that Magnum generate a unique name just like what docker is
doing for "docker run", the problem mentioned by Andrew Melton is that
Magnum support multi tenant, we should support the case that bay/baymodel
under di
In today's IRC meeting, the conclusion for now is that create a
Marathon+Mesos bay without exposing any object to Magnum but enable end
user operate Marathon directly. Thanks.
2015-06-03 9:19 GMT+08:00 Kai Qiang Wu :
> Hi All,
>
> For mesos bay, I think what we should implement depends on user-ca
Hi All,
For mesos bay, I think what we should implement depends on user-cases.
If users use magnum to create mesos-bay, what would they do with mesos in
following steps ?
1. If they go to mesos (framework or anything) directly, we'd better not
involve any new mesos objects, but use container if
On 06/03/2015 07:24 AM, Boris Pavlovic wrote:
Really it's hard to find cores that understand whole project, but
it's quite simple to find people that can maintain subsystems of
project.
We are made wise not by the recollection of our past, but by the
responsibility for our future.
- Geor
In other words, can a new component that is being to an environment have
dependency on the existing ones?
If so, how does that defined?
For example, going back to your example of a multi-tier application, if I
initially have PostgreDB in my environment, and later add Tomcat, how do I tell
Tomca
Thanks Rochelle, looking forward to your next version
On Wed, Jun 3, 2015 at 6:27 AM, Rochelle Grober
wrote:
> Spec is in the works but needs to be reworked a bit more. It’s under
> Openstack-specs. I’m revamping it, but I’m taking vacation until Monday,
> so you won’t see the new patch until
Hi,
Ok, so you just need a noop driver, which you can find in the review link I
posted a few emails back.
Thanks,
doug
> On Jun 2, 2015, at 6:23 PM, Wanjing Xu wrote:
>
> Doug
>
> Our current event consumer is listening to the queue with the topic specified
> in neutron.conf as notificatio
Hi Horizon devs,
The following test patches are a high priority, blocking further new work
in Liberty until they're landed. Please consider helping review them to get
the landed ASAP:
https://review.openstack.org/#/c/170554/
https://review.openstack.org/#/c/167738/
https://review.openstack.org/#/
Doug
Our current event consumer is listening to the queue with the topic specified
in neutron.conf as notification_topics = x. neutron will generate all
create/update/delete events(from api) to this queue including vip/member/pool
events. So we don't need to write a driver to generate the
Sorry about the long delay.
>Even the LOG.error("KEVIN PID=%s network response: %s" % (os.getpid(),
r.text)) line? Surely the server would have forked before that line was
executed - so what could prevent it from executing once in each forked
process, and hence generating multiple logs?
Yes, jus
Hi Gosha,
Thank you very much for your message.
Before I can answer your question I would need to better understand how
Murano handles life-cycle operations that you mentioned.
I hope you can bear with me with these questions or point me to documents
that I need to read.
When I deploy an envir
On 02/06/15 01:51, Jay Pipes wrote:
> On 06/01/2015 08:30 AM, John Garbutt wrote:
>> On 1 June 2015 at 13:10, Flavio Percoco wrote:
>>> On 01/06/15 11:57 +0100, John Garbutt wrote:
> On 26/05/15 13:54 -0400, Nikhil Komawar wrote:
FWIW, moving Nova from glance v1 to glance v2, without bre
On 2015-06-03 02:36:20 +0300 (+0300), Boris Pavlovic wrote:
> I dislike the idea of having 120 repos for single tool. It makes things
> complicated for everybody:
> documentation stuff, installation, maintaing, work that touches multiple
> repos and so on..
>
> So I would prefer to have single rep
On Tue, Jun 2, 2015 at 4:12 PM, Robert Collins
wrote:
> On 3 June 2015 at 10:34, Jeremy Stanley wrote:
> > On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote:
> >> I like this very much. I recall there was a session at the summit
> >> about this that Thierry and Kyle led. If I recall corre
Jeremy,
> the Infrastructure Project is now past 120 repos with more
> than 70 core reviewers among those.
I dislike the idea of having 120 repos for single tool. It makes things
complicated for everybody:
documentation stuff, installation, maintaing, work that touches multiple
repos and so on
On 06/02/2015 02:36 PM, Andrew Laski wrote:
There used to be a project that I think was looking for an API like this to
provide a reservation system, Climate or Blazar or something. There was brief
talk of providing something like it for that use case, but the idea was put on
the backburner to w
Hi Rukhsana, When you say "IPv6 support for FWaaS in Kilo" can you
indicate exactly what you are looking for?
The FWaaS rules in the resource model support both formats (which I
recall has always been the case). A particular implementation/driver
may not support ipv6 (and which is what you are see
We are content to announce the release of:
oslo.messaging 1.13.0: Oslo Messaging API
This release is part of the liberty release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.messaging
For more details, please see the git log history below and:
http://
On 3 June 2015 at 10:34, Jeremy Stanley wrote:
> On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote:
>> I like this very much. I recall there was a session at the summit
>> about this that Thierry and Kyle led. If I recall correctly, the
>> discussion mentioned that it wasn't (at this point
Hi,
If you have an existing event consumer that you want to stick with, you could
write a driver that just generates events. There are some error status warts
that you’d either have to live with or handle, but you could do that later.
Thanks,
doug
> On Jun 2, 2015, at 1:05 PM, Wanjing Xu wrot
On Tue, 2015-06-02 at 16:16 -0600, David Lyle wrote:
> The Horizon project also uses the nova policy.json file to do role
> based access control (RBAC) on the actions a user can perform. If the
> defaults are hidden in the code, that makes those checks a lot more
> difficult to perform. Horizon wil
Hi Kunal
Is it OK if you tell us how this agentless controller is done? Or at least
give me the pointer to the installation guide? I wonder if using an noop
driver is the way.
RegardsWanjingFrom: kunalhgan...@gmail.com
Date: Mon, 1 Jun 2015 19:02:29 -0700
To: openstack-dev@lists.openstack.or
Hi,
This came up at the TC meeting today, and I volunteered to provide an
update from the discussion.
In general, I think there is a lot of support for a packaging effort in
OpenStack. The discussion here has been great; we need to answer a few
questions, get some decisions written down, and mak
On 2015-06-02 21:59:34 + (+), Ian Cordasco wrote:
> I like this very much. I recall there was a session at the summit
> about this that Thierry and Kyle led. If I recall correctly, the
> discussion mentioned that it wasn't (at this point in time)
> possible to use gerrit the way you describ
Hi Henrique,
I don't think we need to specifically call out that we want a domain, we
should always reference the namespace as we do today. Basically, if we ask
for a project name we need to also provide it's namespace (your option #1).
This clearly lines up with how we handle projects in domains
On Tue, Jun 2, 2015 at 12:09 PM, Adam Young wrote:
> Since this a cross project concern, sending it out to the wider mailing
> list:
>
> We have a sub-effort in Keystone to do better access control policy (not
> the Neutron or Congress based policy efforts).
>
> I presented on this at the summi
Spec is in the works but needs to be reworked a bit more. It’s under
Openstack-specs. I’m revamping it, but I’m taking vacation until Monday, so
you won’t see the new patch until at least next week. You are welcome to
comment on the current version, though:
https://review.openstack.org/#/c/
The Horizon project also uses the nova policy.json file to do role based
access control (RBAC) on the actions a user can perform. If the defaults
are hidden in the code, that makes those checks a lot more difficult to
perform. Horizon will then get to duplicate all the hard coded defaults in
our co
On 2 June 2015 at 23:59, Ian Cordasco wrote:
>
>
> On 6/2/15, 16:24, "Boris Pavlovic" wrote:
>
> >Hi stackers,
> >
> >
> >Issue
> >---
> >
> >
> >Projects are becoming bigger and bigger overtime.
> >More and more people would like to contribute code and usually core
> >reviewers
> >team can'
On 6/2/15, 16:24, "Boris Pavlovic" wrote:
>Hi stackers,
>
>
>Issue
>---
>
>
>Projects are becoming bigger and bigger overtime.
>More and more people would like to contribute code and usually core
>reviewers
>team can't scale enough. It's very hard to find people that understand
>full proje
Hi Vahid,
Thank you for sharing your thoughts.
I have a questions about application life-cycle if we use TOSCA translator.
In Murano the main advantage of using HOT format is that we can update Het
stack with resources as soon as we need to deploy additional application.
We can dynamically create
Hello everyone,
We currently see 6 bugs as main HCF dependencies [1]. We'll try to close
all of them overnight. If we don't succeed, we'll need another day.
We'll take decision whether we do/do not declare HCF based on the
results tomorrow morning PDT.
[1] Key HCF dependencies:
https://bugs.
Hey everyone!
The CORS spec has been under review for about a month now, and the TC has
put it on the agenda next week for final approval. I plan on doing one
final revision of the document - if it is warranted - so get your comments
in now!
https://review.openstack.org/#/c/179866/
Michael
_
I'm thinking that the current approach is probably how we want to keep
things. I can't imagine many other projects being okay with multiple
create calls with the same name.
Though if you're really adamant about including that support, we could
include a new flag (--or-update) that performs the u
I like this idea. I agree, as things grow it is probably easier to find
folks that know certain areas a project rather than the full scope.
This could be a good way to handle the load and delegate some pieces
(such as driver reviews) to a different set of people.
On 06/02/2015 04:24 PM, Boris
Hi stackers,
*Issue*
*---*
Projects are becoming bigger and bigger overtime.
More and more people would like to contribute code and usually core
reviewers
team can't scale enough. It's very hard to find people that understand full
project and have enough time to do code reviews. As a result t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
The current meeting time of 1500 UTC on Tuesday is presenting some
conflicts, so we're trying to come up with an alternative. I've
created a Doodle for anyone who is interested in attending these
meetings to indicate what times work and which do
Thanks all!
Someone should now say «With great power comes great responsibility»
And I should respond with something like «Night gathers, and now my watch
begins», should I?
I kind of like this kind of symbolism =) Isn’t there a Core Developer Oath or
Vow? Shouldn’t we think of one?
--
Ki
On 06/02/15 at 11:28am, Alexis Lee wrote:
Andrew Laski said on Mon, Jun 01, 2015 at 09:26:33AM -0400:
However what these parameters give users, versus orchestrating
outside of Nova, is the ability to have the instances all scheduled
as a single block.
We should seek to provide this via persist
Samuel,
VXLAN was moved to 7.0, as you noted it won't make 6.1. Mirantis has
identified this as a high priority for 7.0 so it should get more attention
this time. However any assistance in CR / Testing is always appreciated.
On Thu, May 28, 2015 at 1:38 PM Samuel Bartel
wrote:
> Hi Sean,
>
> I
The verify_tempest_config script has an option to write a new conf file.
I noticed that when you do this, the items in DEFAULT are duplicated in
every section that is written. Looking at the source I can see why this
happens. I guess it is not harmful but is this considered a bug in the
write m
Hello,
I am seeing some weird behavior in my setup and would really appreciate if
someone could clarify a few things below:
Setup: Simple two node. One with control+compute (Node1) and another a compute
(Node2). Since, Node2 is running low in HW, I create a AvlZone putting only
Node2 so that I
Since this a cross project concern, sending it out to the wider mailing
list:
We have a sub-effort in Keystone to do better access control policy (not
the Neutron or Congress based policy efforts).
I presented on this at the summit, and the effort is under full swing.
We are going to set
Thanks everybody. While I am trying to digest all the responses, I am here to
reply why we are not considering a driver. We already have an application
which listens to neutron events to do some other stuff, it might just be easier
for us if we reuse this framework and program the LBaasS from
Updated
Sean, I see that there is no spec linked in gerrit or the BP do we have one?
On Tue, Jun 2, 2015 at 11:07 AM Sean M. Collins wrote:
> Can we update the vxlan bp to target it to 7.0? The series goal is still
> set to 6.1.x
>
> https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-su
Also in favor of #2 and thought it was how it was running. #4 sounds bad
and may hide good code.
How do we want to account for drive-by authors who are going to be unable
to work on future revisions. We talked a while back that we wanted to be
able to account for this as some operators are unable
In today's meeting we discussed implementing a policy for whether and when
core reviewers should abandon old patches whose author's were inactive.
(This doesn't apply to authors that want to abandon their own changes, only
for core reviewers to abandon other people's changes.) There are a few
thing
Hi Serg,
As I mentioned in my earlier email to you I am interested in participating
in this effort.
I am a Heat-Translator contributor and have started looking at how the
integration may work (at a higher level for now).
I'll send my thoughts on that shortly.
Thanks.
Regards,
-
Please note the change in time (and day of the week) and channel:
Meeting on #openstack-meeting at 1600 UTC (9:00am PDT)
Agenda can be found here (feel free to add yours):
https://wiki.openstack.org/wiki/Meetings/Tacker#Meeting_June_4.2C_2015
Thanks,
- Stephen
___
Can we update the vxlan bp to target it to 7.0? The series goal is still
set to 6.1.x
https://blueprints.launchpad.net/fuel/+spec/neutron-vxlan-support
Thanks
--
Sean M. Collins
__
OpenStack Development Mailing List (not f
> From: Rukhsana Ansari
> To: openstack-dev@lists.openstack.org
> Date: 06/02/2015 01:59 PM
> Subject: [openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo
>
> Hi,
>
> I was browsing the code to understand IPv6 support For FWaaS in Kilo.
>
> I don't see a restriction in the db code or in r
Hey everyone!
It's time to pick a name for the M release.
If you have a name you'd like us to vote on, please add it here:
https://wiki.openstack.org/wiki/Release_Naming/M_Proposals
The nominations will be open until 2015-06-07 23:59:59 UTC.
If you don't remember the rules, they're here:
http
Hi,
I was browsing the code to understand IPv6 support For FWaaS in Kilo.
I don't see a restriction in the db code or in reference fwaas_plugin.py
However, from this:
https://github.com/openstack/neutron-fwaas/blob/stable/kilo/neutron_fwaas/services/firewall/drivers/vyatta/vyatta_fwaas.py#L126
I suspect a "BaaS" (Bridge-as-a-service) proposal is lurking in this thread.
While the idea of yet-another-aas is probably not desirable at this time,
it might be worth trying and understand - from an exclusively logical
perspective (ie: the API consumer point of view) - what would be the
differen
Hi Michal,
Apart from reviewing your changes, few more efforts done from TaskFlow side
that I find useful for Cinder's case (and in general).
https://review.openstack.org/#/c/186524/
https://review.openstack.org/#/c/184814/
-Vilobh
On Tue, Jun 2, 2015 at 2:45 AM, Dulko, Michal
wrote:
> Righ
+1 from me, long overdue!
> On May 28, 2015, at 9:42 AM, Kyle Mestery wrote:
>
> Folks, I'd like to propose Assaf Muller to be a member of the Neutron core
> reviewer team. Assaf has been a long time contributor in Neutron, and he's
> also recently become my testing Lieutenant. His influence
+1
From: Stan Lagun mailto:sla...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, June 2, 2015 at 9:32 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@list
+1
From: Ekaterina Chernova mailto:efedor...@mirantis.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, June 2, 2015 at 2:42 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:opensta
On 02/06/15 16:33, Evgeny Fedoruk wrote:
> Hi All,
>
> Does anyone know on which IRC channel the GSLB API meeting is happening?
>
> Thanks,
>
> Evg
>
It was held in #openstack-meeting-4
The logs are here: http://eavesdrop.openstack.org/meetings/gslb/2015/
We are meeting next week, same time, sam
On Mon, Jun 1, 2015 at 12:16 PM, Colleen Murphy wrote:
> Hi everyone,
>
> Here's an initial agenda for our weekly meeting tomorrow at 1500 UTC in
> #openstack-meeting-4:
>
> https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20150602
>
> Please add a
On 2015-06-02 12:41 PM, Yanis Guenane wrote:
>
> The openstacklib::db::sync[2] is currently only a wrapper around an exec
> that does the actual db sync, this allow to make any modification to the
> exec into a single place. The main advantage IMO is that a contributor
> is provided with the same
Great!
A correction here: RBAC proposal does address some of the use cases on
interconnecting tenants.
Fawad Khaliq
On Tue, Jun 2, 2015 at 9:41 PM, Anik wrote:
> That's exactly what I was asking for. Thanks Fawad.
>
> Regards,
> Anik
> 201-245-1569
>
> --
> *From
Hello! I think it's a good time to discuss implementation of trusts in
Glance v2 and v3 api.
Currently we have two different situations during image creation where our
token may expire, which leads to unsuccessful operation.
First is connection between glance-api and glance-registry. In this case
> On Jun 1, 2015, at 12:32 PM, JJ Asghar wrote:
>
> Please answer select the best time for you asap, and tomorrow at 1600UTC i’ll
> send out the time that has been decided.
Ok, so it seems we’re going to have the hack session 1900UTC Wednesday. I’ll
see y’all in the IRC channel!
-J
_
Hi all,
The initial meeting logs can be found at
http://eavesdrop.openstack.org/meetings/gslb/2015/ , and we will be having
another meeting next week, same time, same channel.
Thanks,
doug
> On May 31, 2015, at 1:27 AM, Samuel Bercovici wrote:
>
> Good for me - Tuesday at 1600UTC
>
>
> --
That's exactly what I was asking for. Thanks Fawad. Regards, Anik 201-245-1569
From: Fawad Khaliq
To: OpenStack Development Mailing List (not for usage questions)
Cc: Anik
Sent: Tuesday, June 2, 2015 9:29 AM
Subject: Re: [openstack-dev] Interconnecting projects
On Tue, Jun 2, 20
Hello list,
In order to standardize the way sync_db is done across modules, I would
like to offer a suite of patch[1] that enforces a common pattern.
Pattern is :
if $sync_db {
include COMPONENT::db::sync
}
class COMPONENT::db::sync {
openstacklib::db::sync {
[
On 06/02/2015 12:32 AM, Ian Wells wrote:
The fix should work fine. It is technically a workaround for the way
checksums work in virtualised systems, and the unfortunate fact that
some DHCP clients check checksums on packets where the hardware has
checksum offload enabled. (This doesn't work due
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 06/02/2015 06:22 PM, Sean Dague wrote:
> Nova has a very large API, and during the last release cycle a lot
> of work was done to move all the API checking properly into policy,
> and not do admin context checks at the database level. The result
>
On Tue, Jun 2, 2015 at 9:14 PM, Assaf Muller wrote:
> Check out:
>
> http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html
If I understand correctly, what Anik is probably asking for is way to
connect two OpenStack projects together from a network point of view, whe
Nova has a very large API, and during the last release cycle a lot of
work was done to move all the API checking properly into policy, and not
do admin context checks at the database level. The result is a very
large policy file -
https://github.com/openstack/nova/blob/master/etc/nova/policy.json
Check out:
http://specs.openstack.org/openstack/neutron-specs/specs/liberty/rbac-networks.html
Kevin is trying to solve exactly this problem. We're really hoping to land it in
time for Liberty.
- Original Message -
> Hi,
>
> Trying to understand if somebody has come across the following
+1. Most of the other openstack api's allow for non unique names. The api's
that take in a name just break in that case. Its up to the user to decide if
they want uniqueness and api's to work by name, or non-uniqueness and have to
use uuids.
Thanks,
Kevin
From:
On 6/2/15, 04:45, "Boris Bobrov" wrote:
>On Tuesday 02 June 2015 09:32:45 Chenhong Liu wrote:
>> There is keystone/exception.py which contains Exceptions defined and
>>used
>> inside keystone provide 4xx and 5xx status code. And we can use it like:
>> exception.Forbidden.code, exception.for
Hi,
Trying to understand if somebody has come across the following scenario:
I have a two projects: Project 1 and Project 2
I have a neutron private network in Project 1, that I want to connect that
private network to a neutron port in Project 2.
This does not seem to be possible without using adm
Names can make writing generic orchestration templates that would go in the
applications catalog easier. Humans are much better at inputting a name rather
then a uuid. You can even default a name in the text box and if they don't
change any of the defaults, it will just work. You can't do that w
Hi All,
Does anyone know on which IRC channel the GSLB API meeting is happening?
Thanks,
Evg
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
On 06/02/2015 02:39 PM, Jeremy Stanley wrote:
> On 2015-06-02 09:02:42 +0200 (+0200), Thomas Goirand wrote:
> [...]
>> That will be the little bit more tricky part. Some libraries are very
>> small, and probably caching will not be useful (too much work when
>> building the VM image). However, for
I've spent some time trying to eliminate the number of deprecation warnings
we have in preparation for our upgrade to Kilo. One of the ones that I got
stuck on is the nova::rabbitmq::rabbitmq_class parameter.
If this parameter is specified, and it is by default, then the class will
include the ra
Hi All,
Some of us are still returning from post summit activities. We will resume
meetings next week.
p
Peter J. Pouliot CISSP
Microsoft Enterprise Cloud Solutions
C:\OpenStack
New England Research & Development Center
1 Memorial Drive
Cambridge, MA 02142
P: 1.(857).4536436
E: ppoul...@micros
Filip, my congratulations! Welcome!
On Tue, Jun 2, 2015 at 5:34 PM, Stan Lagun wrote:
> +1
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
> On Tue, Jun 2, 2015 at 9:25 AM, Serg Melikyan
> wrote:
>
>> Folks, I'd like to propose Filip Blaha to core members of Mu
Kirill, welcome!
On Tue, Jun 2, 2015 at 5:32 PM, Stan Lagun wrote:
> +1 without any doubt
>
> Sincerely yours,
> Stan Lagun
> Principal Software Engineer @ Mirantis
>
>
>
> On Tue, Jun 2, 2015 at 10:43 AM, Ekaterina Chernova <
> efedor...@mirantis.com> wrote:
>
>> +1
>>
>> Regards,
>> Kate.
>>
We are glad to announce the release of:
pycadf 1.0.0: CADF Library
This release is part of the liberty release series.
With source available at:
https://git.openstack.org/cgit/openstack/pycadf
For more details, please see the git log history below and:
https://launchpad.net/pycadf/+mi
We are pumped to announce the release of:
oslo.db 1.10.0: Oslo Database library
This release is part of the liberty release series.
With source available at:
http://git.openstack.org/cgit/openstack/oslo.db
For more details, please see the git log history below and:
http://launchpad.ne
1 - 100 of 165 matches
Mail list logo
