Hi manila, I would like to broach the subject of share load balancing.
Currently the share server for an (in this case) NFS share that is newly
created is determined at share creation time. In this proposal, the share
server is determined "late binding style" at mount-time instead.
For the sake o
On 2015年02月10日 11:34, yuntong wrote:
On 2015年02月10日 05:12, gordon chung wrote:
> In nova api, a nova api.fault notification will be send out when the when
there
> is en error.
>http://git.openstack.org/cgit/openstack/nova/tree/nova/api/openstack/__init__.py#n119
> but i couldn't find where th
Ok, cool. Looking forward to it.
Best regards,
Alex Levine
On 2/10/15 5:25 AM, M Ranga Swami Reddy wrote:
Hi Alex Levine (you can address me 'Swami'),
Thank you. I have been working on this EC2 APIs quite some time. We
will work closely together on this project for reviews, code cleanup,
bug
I updated the lib/swift file and the devstack build failded with the same error
when uploading image.
I commented the script in stack.sh to disable the uploading image procedure,
but the build still failed when running "cinder type-create default ", the
error is still " Unauthorized ":
2015-02
Hi Stacker,
A question about oslo.config, maybe a very silly question. but pls tell
me if you know, thanks in advance.
I know oslo has removed 'olso' namespace, oslo.config has been changed
to oslo_config, it also retains backwards compat.
I found I can run openstack successfully, but as
Hi all,
After OpenStack Juno, floating ip is handled by dvr, but SNAT is still
handled by l3agent on network node. The distributed SNAT is in future plans
for DVR. In my opinion, SNAT can move to DVR as well as floating ip. I have
searched in blueprint, there is little about distributed SNAT. Is
Dear PTLs, cross-project liaisons and anyone else interested,
We'll have a cross-project meeting today at 21:00 UTC, with the
following agenda:
* Status update on novanet2neutron
* API_Working_Group[1] update (etoews)
* EOL stable/icehouse [2]
* openstack-specs discussion
* CLI Sorting Argument
Hi,
I would like to request a FFE for
https://review.openstack.org/#/c/134134/
It is a change that allows a driver to use type "file" instead of "block"
for local volumes.
It was blocked because at that time there was no use for it.
Now, we have a driver merged which currently returns "loca" for
On Tue, Feb 10, 2015 at 11:55:54AM +0200, Eduard Matei wrote:
> Hi,
>
> I would like to request a FFE for
> https://review.openstack.org/#/c/134134/
>
> It is a change that allows a driver to use type "file" instead of "block"
> for local volumes.
> It was blocked because at that time there was n
On Fri, Feb 06, 2015 at 10:47:29AM -0500, Solly Ross wrote:
> Hi,
>
> I would like to request a feature freeze exception for the
> "Websockify security proxy framework" blueprint [1].
>
> The blueprint introduces a framework for defining "security drivers" for the
> connections between the websoc
On Fri, Feb 06, 2015 at 10:20:04PM +, Tomoki Sekiyama wrote:
> Hello,
>
> I'd like to request a feature freeze exception for the change
> https://review.openstack.org/#/c/138795/ .
>
> This patch makes live volume-boot instance snapshots consistent by
> quiescing instances before snapshotti
Joe, Matt & Matthew:
I hear your frustration with broken stable branches. With my
vulnerability management team member hat, responsible for landing
patches there with a strict deadline, I can certainly relate with the
frustration of having to dive in to unbork the branch in the first
place, rather
On Fri, Feb 06, 2015 at 05:29:33PM -0500, Solly Ross wrote:
> Hi,
>
> I would like to request a non-priority feature freeze exception for the
> "Use libvirt storage pools" blueprint [1].
>
> The blueprint introduces a new image backed type that uses libvirt storage
> pools,
> and is designed to
On 02/10/2015 11:12 AM, Daniel P. Berrange wrote:
> On Fri, Feb 06, 2015 at 10:20:04PM +, Tomoki Sekiyama wrote:
>> Hello,
>>
>> I'd like to request a feature freeze exception for the change
>> https://review.openstack.org/#/c/138795/ .
>>
>> This patch makes live volume-boot instance snapsho
On Mon, Feb 09, 2015 at 05:15:26PM +0100, Andreas Maier wrote:
>
> Hello,
> I would like to ask for the following feature freeze exceptions in Nova.
>
> The patch sets below are all part of this blueprint:
> https://review.openstack.org/#/q/status:open+project:openstack/nova
> +branch:master+topi
Hi,
I'd like to request a feature freeze exception for the change:
https://review.openstack.org/140733/
It's a small, self-contained driver for attaching StorPool-backed
Cinder volumes to existing Nova virtual machines. It does not touch
anything outside its own bailiwick (adds a new class to
On Tue, Feb 10, 2015 at 12:28:27PM +0200, Peter Penchev wrote:
> Hi,
>
> I'd like to request a feature freeze exception for the change:
> https://review.openstack.org/140733/
>
> It's a small, self-contained driver for attaching StorPool-backed
> Cinder volumes to existing Nova virtual machines
- Original Message -
> From: "Jay Pipes"
> To: [email protected]
> Sent: Monday, February 9, 2015 9:36:45 PM
> Subject: Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody
> should know about Galera
>
> On 02/09/2015 03:10 PM, Clint Byrum wrote:
> > Excer
Hi,
In Kilo the cinder driver is requested to be merged before K-1, I want to ask
that in L does the driver will be requested to be merged before L-1?
Thanks and regards,
Liu
__
OpenStack Development Mailing List (not for us
On Tue, Feb 10, 2015 at 12:34 PM, Daniel P. Berrange
wrote:
> On Tue, Feb 10, 2015 at 12:28:27PM +0200, Peter Penchev wrote:
>> Hi,
>>
>> I'd like to request a feature freeze exception for the change:
>> https://review.openstack.org/140733/
>>
>> It's a small, self-contained driver for attaching
On Tue, Feb 10, 2015 at 12:52:38PM +0200, Peter Penchev wrote:
> On Tue, Feb 10, 2015 at 12:34 PM, Daniel P. Berrange
> wrote:
> > On Tue, Feb 10, 2015 at 12:28:27PM +0200, Peter Penchev wrote:
> >> Hi,
> >>
> >> I'd like to request a feature freeze exception for the change:
> >> https://review.
Folks,
We are collecting OpenStack workloads stats. For authentication in the
keystone we are using admin user credentials from Nailgun. Credentials can
be changed directly in the OpenStack and we will loose possibility of
fetching information.
This issue can be fixed by creation additional user
Hi all,
During the analysis of the following bug:
https://bugs.launchpad.net/heat/+bug/1418878
i figured out that orchestration engine doesn't work properly in some cases.
The case is the following:
trying to delete the same stack with resources n times in series.
It might happen if the stack delet
Hello Jason,
On Tue, Feb 10, 2015 at 10:07 AM, Jason Bishop
wrote:
>
> When a share is created (from scratch), the manila scheduler identifies a
> share server from its list of backends and makes an api call to
> create_share method in the appropriate driver. The driver executes the
> required s
- Original Message -
> From: "Jay Pipes"
> To: "Attila Fazekas" , "OpenStack Development Mailing
> List (not for usage questions)"
>
> Cc: "Pavel Kholkin"
> Sent: Monday, February 9, 2015 7:15:10 PM
> Subject: Re: [openstack-dev] [all][oslo.db][nova] TL; DR Things everybody
> shoul
Sorry for flood,
i forgot p4:
Prohibit stack deletion if the current stack state, status = (DELETE, IN
PROGRESS).
Raise not supported exception in heat engine. It is possible because stack
state
will be updated before deleting.
On Tue, Feb 10, 2015 at 2:04 PM, Kairat Kushaev
wrote:
> Hi all,
> D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
my name was called out here, so I think I need to present my thoughts
on the matter. :) And sorry for writing too many words below.
===
As a disclaimer, I was not the one to support long support term for
stable branches. On the previous summit,
Hi,
General info
Detailed documentation is available in the latest spec [1] (see [2] for
HTML format). You can also check blue-print [3] and etherpad how-to [4]
for more info.
Fuel-library granularization status
As you may know, we're using granular task based deployment in master
branch already.
On 02/09/2015 10:55 PM, Michael Still wrote:
> The previous policy is that we do a release "when requested" or when a
> critical bug fix merges. I don't see any critical fixes awaiting
> release, but I am not opposed to a release.
>
> The reason I didn't do this yesterday is that Joe wanted some t
>There seemed to be two ways to create a VM via cli:
>
>1) use neutron command to create a port first and then use nova command to
>attach the vm to that port(neutron port-create.. >followed by nova boot --nic
>port-id=)
>2)Just use nova command and a port will implicitly be created for you(nova
Hi,
Recently we've had discussions in the ML [1] and on weekly IRC
meeting [2] about specs and whether they should be merged before
or after the patches for feature get merged.
Lets continue the discussion in this thread.
[1]
http://lists.openstack.org/pipermail/openstack-dev/2015-January/055528
On Feb 9, 2015, at 9:28 PM, Jay Pipes
mailto:[email protected]>> wrote:
On 02/02/2015 02:51 PM, Stefano Maffulli wrote:
On Fri, 2015-01-30 at 23:05 +, Everett Toews wrote:
To converge the OpenStack APIs to a consistent and pragmatic RESTful
design by creating guidelines that the projects sho
On Tue, Feb 10, 2015 at 03:04:39PM +0400, Kairat Kushaev wrote:
>Hi all,
>During the analysis of the following bug:
>https://bugs.launchpad.net/heat/+bug/1418878
>i figured out that orchestration engine doesn't work properly in some
>cases.
>The case is the following:A
>
Hi Swami,
I"ve some exposure to Amazon API for S3, I'm willing to work on EC2 API.
Pls let me know how to contribute in to this.
-Viswanath
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstac
Thank you very much for joining with us in EC2 API sub team. Will
share the To Do details soon.
Thanks
Swami
On Tue, Feb 10, 2015 at 6:57 PM, Jayachandragupta Kasiviswa
wrote:
> Hi Swami,
>
> I"ve some exposure to Amazon API for S3, I'm willing to work on EC2 API.
> Pls let me know how to contri
Thanks for explanation, Steven.
Will try to figure out why it is not working in nova.
On Tue, Feb 10, 2015 at 4:04 PM, Steven Hardy wrote:
> On Tue, Feb 10, 2015 at 03:04:39PM +0400, Kairat Kushaev wrote:
> >Hi all,
> >During the analysis of the following bug:
> >https://bugs.launchp
Hi there,
Swami Reddy ([email protected]) invites you to participate in the
Doodle poll "EC2 API Sub Team Weekly Meeting."
Participate now
https://doodle.com/8a6fnv6yxp7tgiw9?tmail=poll_invitecontact_participant_invitation&tlink=pollbtn
What is Doodle? Doodle is a web service that helps Swami
Fuelers,
I see no problems here. I think it's ok if some parts of feature were
merged before the spec, because it means the feature is under
development. Moreover, if we merge specs asap there's a chance that
we'll miss something. Therefore, the chance that it will be found and
discussed at the de
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need some cache system for packages on master node. It should
work for deb and rpm packages, and be able to serve up to 200 nodes.
I know we had bad experience in the past, can you guys share your though
I definitely don't expect any change of the existing port in the case with
two nics. However in the case of single nic a question like 'what is impact
of security-groups parameter' arises.
Also a similar question arises out of '--nic port-id=xxx,v4-fixed-ip=yyy'
combination.
Moreover, if we assume
On Tue, Feb 10, 2015, at 04:29 AM, Joshua Zhang wrote:
> Hi Stacker,
>A question about oslo.config, maybe a very silly question. but pls
>tell
> me if you know, thanks in advance.
>
>I know oslo has removed 'olso' namespace, oslo.config has been changed
> to oslo_config, it also reta
On 09/02/15 18:15, Jay Pipes wrote:
> On 02/09/2015 01:02 PM, Attila Fazekas wrote:
>> I do not see why not to use `FOR UPDATE` even with multi-writer or
>> Is the retry/swap way really solves anything here.
>
>> Am I missed something ?
>
> Yes. Galera does not replicate the (internal to InnnoDB)
Hello Tomasz,
In a previous life, I used squid to speed up packages downloads and it
worked just fine...
Simon
On Tue, Feb 10, 2015 at 3:24 PM, Tomasz Napierala
wrote:
> Hi,
>
> We are currently redesigning our apporach to upstream distributions and
> obviusly we will need some cache system for
Hi All,
Due to multiple conflicts today we need to postpone the Hyper-v discussion
until next week.
Peter J. Pouliot CISSP
Microsoft Cloud+Enterprise Solutions
C:\OpenStack
New England Research & Development Center
1 Memorial Drive
Cambridge, MA 02142
P: 1.(857).4536436
E: [email protected]
On Tue, Feb 10, 2015, at 05:19 AM, Thierry Carrez wrote:
> Joe, Matt & Matthew:
>
> I hear your frustration with broken stable branches. With my
> vulnerability management team member hat, responsible for landing
> patches there with a strict deadline, I can certainly relate with the
> frustrati
On Tue, Feb 10, 2015, at 07:25 AM, Sean Dague wrote:
> On 02/09/2015 10:55 PM, Michael Still wrote:
> > The previous policy is that we do a release "when requested" or when a
> > critical bug fix merges. I don't see any critical fixes awaiting
> > release, but I am not opposed to a release.
> >
On Tue, 2015-02-10 at 15:24 +0100, Tomasz Napierala wrote:
Hi,
We are currently redesigning our apporach to upstream distributions and
obviusly we will need some cache system for packages on master node. It should
work for deb and rpm packages, and be able to serve up to 200 nodes.
I know we h
Since this is sort of a topic change, I opted to start a new thread. I was
reading over the "Juno is Fubar at the Gate" thread, and this bit stood out to
me:
> > So I think it's time we called the icehouse branch and marked it EOL. We
> > originally conditioned the longer support window on extra
Hi folks,
One of the key features that we are adding to Glance with the
introduction of Artifacts is the ability to have multiple versions of
the same object in the repository: this gives us the possibility to
query for the latest version of something, keep track on the changes
history, and build
On Tue, Feb 10, 2015 at 11:19:20AM +0100, Thierry Carrez wrote:
> Joe, Matt & Matthew:
>
> I hear your frustration with broken stable branches. With my
> vulnerability management team member hat, responsible for landing
> patches there with a strict deadline, I can certainly relate with the
> frus
On 02/10/2015 10:28 AM, Alexander Tivelkov wrote:
> Hi folks,
>
> One of the key features that we are adding to Glance with the
> introduction of Artifacts is the ability to have multiple versions of
> the same object in the repository: this gives us the possibility to
> query for the latest versi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The sentiment that Kevin is expressing here has come up informally at past
Operator’s meetups as well, which makes sense given that relatively few
operators are chasing trunk vs using a stable rele
Yes, assume NEW drivers have to land in before the L-1 milestone. This
also includes getting a CI system up and running.
Walt
Hi,
In Kilo the cinder driver is requested to be merged before K-1, I want
to ask that in L does the driver will be requested to be merged before
L-1?
Thanks and
On Tue, Feb 10, 2015 at 9:20 AM, Kevin Bringard (kevinbri) <
[email protected]> wrote:
> ATC is only being given to folks committing to the current branch (
> https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstack-summit/
> ).
> Secondly, it's difficult to get stack-analytics c
Thanks Monty!
Yup, probably I've missed that. I was looking at pbr and its version
implementation, but didn't realize that this is actually a fusion of
semver and pep440.
So, we have this as an extra alternative to choose from.
It would be an obvious choice if we were just looking for some commo
On 2015-02-10 15:20:46 + (+), Kevin Bringard (kevinbri) wrote:
[...]
> I've been talking with a few people about this very thing lately,
> and I think much of it is caused by what appears to be our
> actively discouraging people from working on it. Most notably, ATC
> is only being given to
Thierry Carrez writes:
> I also disagree with the proposed solution. We announced a support
> timeframe for Icehouse, our downstream users made plans around it, so we
> should stick to it as much as we can.
To be fair, if we did that, we did not communicate accurately the
sentiment of the room a
On 02/10/2015 10:35 AM, Matthew Treinish wrote:
On Tue, Feb 10, 2015 at 11:19:20AM +0100, Thierry Carrez wrote:
Joe, Matt & Matthew:
I hear your frustration with broken stable branches. With my
vulnerability management team member hat, responsible for landing
patches there with a strict deadlin
>
> > Secondly, it's difficult to get stack-analytics credit for back
> > ports, as the preferred method is to cherry pick the code, and
> > that keeps the original author's name. I've personally gotten a
> > few commits into stable, but have nothing to show for it in
> > stack-analytics (if I'm do
On Tue, 2015-02-10 at 15:20 +, Kevin Bringard (kevinbri) wrote:
> I've been talking with a few people about this very thing lately, and
> I think much of it is caused by what appears to be our actively
> discouraging people from working on it. Most notably, ATC is only
> being given to folks co
Hi Alex,
That's great. I think we should start the work without delay.
I have just created the ec2 api sub team wiki page in nova active
sub-teams list.
https://wiki.openstack.org/wiki/Nova#Active_Sub-teams:
https://wiki.openstack.org/wiki/Meetings/EC2API
For the ec2 api weekly meeting, I have al
On 2/10/15, 10:35, "Alexander Tivelkov" wrote:
>Thanks Monty!
>
>Yup, probably I've missed that. I was looking at pbr and its version
>implementation, but didn't realize that this is actually a fusion of
>semver and pep440.
>
>So, we have this as an extra alternative to choose from.
>
>It would
On 2015-02-10 11:50:28 -0500 (-0500), David Kranz wrote:
[...]
> I would rather give up branchless tempest than the ability for
> real distributors/deployers/operators to collaborate on stable
> branches.
[...]
Keep in mind that branchless tempest came about in part due to
downstream use cases as
James E. Blair wrote:
> Thierry Carrez writes:
>
>> I also disagree with the proposed solution. We announced a support
>> timeframe for Icehouse, our downstream users made plans around it, so we
>> should stick to it as much as we can.
>
> To be fair, if we did that, we did not communicate accur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The voice of operators/users/deployers in this conversation should be reflected
through the entity that they are paying to provide operational cloud services.
Let’s be careful here: I hope you didn’t mean to say that
operators/users/deployers vo
On 02/10/2015 12:20 PM, Jeremy Stanley wrote:
On 2015-02-10 11:50:28 -0500 (-0500), David Kranz wrote:
[...]
I would rather give up branchless tempest than the ability for
real distributors/deployers/operators to collaborate on stable
branches.
[...]
Keep in mind that branchless tempest came a
On 2015-02-10 10:21:58 -0600 (-0600), Dean Troyer wrote:
[...]
> ATC credit should be given, stable branch maintenance is a
> contribution to the project, no question.
[...]
Just to keep this particular misconception from spinning out of
control, as I mentioned elsewhere in this thread they absolu
On Tue, Feb 10, 2015 at 11:50:28AM -0500, David Kranz wrote:
> On 02/10/2015 10:35 AM, Matthew Treinish wrote:
> >On Tue, Feb 10, 2015 at 11:19:20AM +0100, Thierry Carrez wrote:
> >>Joe, Matt & Matthew:
> >>
> >>I hear your frustration with broken stable branches. With my
> >>vulnerability manageme
Hi everyone!
I wanted to propose Marek Denis (marekd on IRC) as a new member of the Keystone
Core team. Marek has been instrumental in the implementation of Federated
Identity. His work on Keystone and first hand knowledge of the issues with
extremely large OpenStack deployments has been a sign
This doesn't look flexible for me. Glance and keystone could use different
settings for SSL. I like current way to use session and config section for
each separate client (like [1]).
[1] https://review.openstack.org/#/c/131098/
Thanks,
Andrew.
On Mon, Feb 9, 2015 at 6:19 PM, Matt Riedemann
wrot
Hi Ian,
Automatic version generation is not the only and not the primary
reason for the version concept. In fact, the implementation which is
planned to land in this cycle does not contain this feature at all:
currently we also leave the version assignment up to uploader (version
is a regular immu
> On Feb 10, 2015, at 9:21 AM, Dean Troyer wrote:
>
> On Tue, Feb 10, 2015 at 9:20 AM, Kevin Bringard (kevinbri)
> wrote:
> ATC is only being given to folks committing to the current branch
> (https://ask.openstack.org/en/question/45531/atc-pass-for-the-openstack-summit/).
>
> Secondly, it'
+1
On Tue, Feb 10, 2015 at 11:56 AM, David Stanek wrote:
> +1
>
> On Tue, Feb 10, 2015 at 12:51 PM, Morgan Fainberg <
> [email protected]> wrote:
>
>> Hi everyone!
>>
>> I wanted to propose Marek Denis (marekd on IRC) as a new member of the
>> Keystone Core team. Marek has been instrumen
+1
On Tue, Feb 10, 2015 at 11:51 AM, Morgan Fainberg wrote:
> Hi everyone!
>
> I wanted to propose Marek Denis (marekd on IRC) as a new member of the
> Keystone Core team. Marek has been instrumental in the implementation of
> Federated Identity. His work on Keystone and first hand knowledge of
+1
On Tue, Feb 10, 2015 at 11:51 AM, Morgan Fainberg wrote:
> Hi everyone!
>
> I wanted to propose Marek Denis (marekd on IRC) as a new member of the
> Keystone Core team. Marek has been instrumental in the implementation of
> Federated Identity. His work on Keystone and first hand knowledge of
+1
On Tue, Feb 10, 2015 at 12:51 PM, Morgan Fainberg wrote:
> Hi everyone!
>
> I wanted to propose Marek Denis (marekd on IRC) as a new member of the
> Keystone Core team. Marek has been instrumental in the implementation of
> Federated Identity. His work on Keystone and first hand knowledge of
+1 !!
On Tue, Feb 10, 2015 at 11:51 AM, Morgan Fainberg
mailto:[email protected]>> wrote:
Hi everyone!
I wanted to propose Marek Denis (marekd on IRC) as a new member of the Keystone
Core team. Marek has been instrumental in the implementation of Federated
Identity. His work on Keyston
On 02/10/2015 12:51 PM, Morgan Fainberg wrote:
Hi everyone!
I wanted to propose Marek Denis (marekd on IRC) as a new member of the
Keystone Core team. Marek has been instrumental in the implementation
of Federated Identity. His work on Keystone and first hand knowledge
of the issues with extr
On 02/10/2015 09:47 AM, Matthew Booth wrote:
On 09/02/15 18:15, Jay Pipes wrote:
On 02/09/2015 01:02 PM, Attila Fazekas wrote:
I do not see why not to use `FOR UPDATE` even with multi-writer or
Is the retry/swap way really solves anything here.
Am I missed something ?
Yes. Galera does not
On 02/10/2015 06:28 AM, Attila Fazekas wrote:
- Original Message -
From: "Jay Pipes"
To: "Attila Fazekas" , "OpenStack Development Mailing List (not
for usage questions)"
Cc: "Pavel Kholkin"
Sent: Monday, February 9, 2015 7:15:10 PM
Subject: Re: [openstack-dev] [all][oslo.db][nova] T
[email protected] (James E. Blair) writes:
> Hi,
>
> The Infrastructure program has a unique three-tier team structure:
> contributors (that's all of us!), core members (people with +2 ability
> on infra projects in Gerrit) and root members (people with
> administrative access). Read all about
+1
or +1, in this case.
Steve
Joe Savak wrote on 02/10/2015 01:06:51 PM:
> From: Joe Savak
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 02/10/2015 01:17 PM
> Subject: Re: [openstack-dev] [Keystone] Proposing Marek Denis for
> the Keystone Core Team
>
On 2015-02-10 10:59:57 -0800 (-0800), James E. Blair wrote:
> And she is now a member of infra-core! Thanks again!
Excellent--I have a list of stuff that... er, I mean welcome aboard!
--
Jeremy Stanley
__
OpenStack Developm
+1! Marek has been an outstanding Keystone contributor and reviewer!
--Brad
Brad Topol, Ph.D.
IBM Distinguished Engineer
OpenStack
(919) 543-0646
Internet: [email protected]
Assistant: Kendra Witherspoon (919) 254-0680
From: David Stanek
To: "OpenStack Development Mailing List (not f
On 8/17/2014 7:58 PM, Osanai, Hisashi wrote:
On Friday, August 15, 2014 8:48 PM, Ihar Hrachyshka wrote:
There was an issue with jenkins running py33 checks for stable
ceilometer branches, which is wrong. Should be fixed now.
Thank you for your response.
I couldn't solve this by myself but D
On 2/10/2015 1:08 PM, Matt Riedemann wrote:
On 8/17/2014 7:58 PM, Osanai, Hisashi wrote:
On Friday, August 15, 2014 8:48 PM, Ihar Hrachyshka wrote:
There was an issue with jenkins running py33 checks for stable
ceilometer branches, which is wrong. Should be fixed now.
Thank you for your
On Tue, Feb 10, 2015 at 10:59 AM, James E. Blair wrote:
> [email protected] (James E. Blair) writes:
>
>> Hi,
>>
>> The Infrastructure program has a unique three-tier team structure:
>> contributors (that's all of us!), core members (people with +2 ability
>> on infra projects in Gerrit) and roo
+1
Cheers
Priti
From: Brad Topol mailto:[email protected]>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:[email protected]>>
Date: Tuesday, February 10, 2015 at 11:04 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:
On 02/10/2015 12:15 PM, Ian Cordasco wrote:
So Semantic Versioning, as I’ve already mentioned in the past, isn’t
really a de facto standard in any language community but it is a language
agnostic proposal. That said, just because it’s language agnostic does not
mean it won’t conflict with other l
Folks, I cleaned up the Solum roadmap page to reflect the current areas of
focus for the team. Please refer to "Milestone:kilo" at the roadmap page below
https://wiki.openstack.org/wiki/Solum/HighLevelRoadmap
I also registered a new blueprint for the CLI revamping being done right now -
https://b
I think most people would agree documentation is a good thing, and
consistency is generally a good thing… is there an accepted standard on
layout and minimum required fields?
If not, should there be?
For example
- Heading (short description)
- Description
- Inputs
- Input name + description
Hi all,
There's recently been quite a bit of discussion in Oslo about what
Eventlet use cases we want to support, and this led to the conclusion
that an eventlet best practices document would be helpful. Because of
the broad applicability of this information, the thought was that a
cross-project
> but how do we do with other priority message like "WARN" ?
we can add support for the other levels as well... are there WARN, CRITICAL,
priority messages?
cheers,gord
Date: Tue, 10 Feb 2015 16:11:23 +0800
From: [email protected]
To: [email protected]; [email protected]; jul...@d
I agree with Alexander on this. We should certainly learn what we can from
existing software. That said, the Solum team really wants this feature in
Glance so we can leverage that instead of having our own repository for Heat
templates we generate when building apps. We want to keep our requirem
On 2/10/15, 13:55, "Jay Pipes" wrote:
>On 02/10/2015 12:15 PM, Ian Cordasco wrote:
>> So Semantic Versioning, as I’ve already mentioned in the past, isn’t
>> really a de facto standard in any language community but it is a
>>language
>> agnostic proposal. That said, just because it’s language agn
On 2/10/15, 12:01, "Alexander Tivelkov" wrote:
>Hi Ian,
>
>Automatic version generation is not the only and not the primary
>reason for the version concept. In fact, the implementation which is
>planned to land in this cycle does not contain this feature at all:
>currently we also leave the versi
> On Feb 10, 2015, at 3:17 PM, Ian Cordasco wrote:
>
>>
>> And of course, the chosen solution should be mappable to database, so
>> we may do sorting and filtering on the DB-side.
>> So, having it as a simple string and letting the user to decide what
>> it means is not an option.
>
> Except f
Excerpts from Alexander Tivelkov's message of 2015-02-10 07:28:55 -0800:
> Hi folks,
>
> One of the key features that we are adding to Glance with the
> introduction of Artifacts is the ability to have multiple versions of
> the same object in the repository: this gives us the possibility to
> que
It's that time again... on Saturday, March 21, 2015, the OpenStack
Project Infrastructure team is upgrading the operating system on
which review.openstack.org runs, and that means a new virtual
machine instance with new IP addresses assigned by our service
provider. The new IP addresses will be as
As pointed out by the examples in the other replies, you would essentially
have to support every possible parameter to "neutron port-create" in "nova
boot". That's creating unnecessary knowledge of neutron in nova. If you had
to eliminate one of the two, the second workflow should actually be the o
1 - 100 of 135 matches
Mail list logo
