Hi Everyone,
I'm excited to announce my candidacy for PTL for Kolla team during the Ocata
cycle.
Kolla is a fantastic project. It brings fresh new blood to OpenStack Deployment
Management. Simplifying the lives of Operators when managing OpenStack is
essential to OpenStack’s success and I persona
Hi,
Probably going through [1] (and link to Admin guide made by Stephen in one of
activity - [2]) and maybe [3] will be helpful
BR,
Konstantin
[1] https://bugs.launchpad.net/nova/+bug/1614882
[2]
http://docs.openstack.org/admin-guide/compute-cpu-topologies.html#customizing-instance-numa-placemen
Hi
I tried installing manually following the guide you shared. I didnot face
any problem and the server started fine. Could you please share your
tacker.conf file and tacker.log file?
Thanks
Janki
On Mon, Sep 12, 2016 at 9:09 AM, zhi wrote:
> hi,
>
> I downloaded the code from the master bran
+1, thanks for taking care of that!
On 09/12/2016 03:35 AM, Huang Zhiteng wrote:
> +1 for this long-waited feature to land in Newton.
>
> On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant
> mailto:jsbry...@electronicjungle.net>>
> wrote:
>
> +1 from me. It is making good progress and is low risk
Hello all,
I would like to announce that i will not be running for projects Kuryr or
Dragonflow
PTL.
I believe that both projects shows great value and progress compared to the
time they exists
mostly thanks to the great communities actively working on both of them.
I also strongly believe that
It was a good pleasure to work with you, Gal.You did an awesome job
for Dragonflow.
Thanks for all your help and guide in this project. Hopefully we can
get-together
some time or cooperate in other projects in the future.
On Mon, Sep 12, 2016 at 4:31 PM, Gal Sagie wrote:
> Hello all,
>
> I would
Hi!
The Telemetry project continued improving this last cycle, and I'm really glad
of what the team achieve. We continued to reduce our technical debt a lot, and
improved various parts of our stack. We're still leading some parts of the
OpenStack development platform, and I think it's a great achi
On Mon, Sep 12, 2016 at 10:31 AM, Gal Sagie wrote:
> Hello all,
>
> I would like to announce that i will not be running for projects Kuryr or
> Dragonflow
> PTL.
>
> I believe that both projects shows great value and progress compared to the
> time they exists
> mostly thanks to the great communit
Hi
I would like to announce my candidacy for PTL of the OpenStack Charms
project (see [0]).
I'm the incumbent and first PTL of this project, which joined the OpenStack
project this year; Right now we have around 30 charms for deploying
various parts of OpenStack, with an active core team 100% po
Hi,
I'm trying to deploy a basic three nodes architecture to test Fuel 9: 1
controller, 1storage and 1 compute nodes. After some minutes, I got this error
message:
Deployment has failed. All nodes are finished. Failed tasks: Task[sync_time/1],
Task[sync_time/3], Task[sync_time/2] Stopping the
Hi Kuryrs!
Sorry I didn't get to post it earlier, here goes today's meeting
agenda. As always, feel free to add items or bring them up during the
open discussion, I'll be checking the agenda for updates just before
the meeting starts at 14utc.
See you in the meeting,
Toni
__
Overview
Kuryr proposes to address the issues of double encapsulation and exposure of
containers as neutron entities when containers are running within VMs.
As an alternative to the vlan-aware-vms and use of ovs within the VM, we
propose to:
- Use allowed-address-pairs configuration fo
Hi Kuryrs!
On September 5th's weekly IRC meeting Irena Berezovsky suggested that
we should take a decision regarding the location of specs and devrefs.
Currently we default to putting all the specs and devrefs for:
- Kuryr
- Kuryr-libnetwork
- Kuryr-kubernetes
to openstack/kuryr. Fuxi is still b
On Mon, Sep 12, 2016 at 1:29 PM, Coughlan, Ivan wrote:
>
>
> Overview
>
> Kuryr proposes to address the issues of double encapsulation and exposure of
> containers as neutron entities when containers are running within VMs.
>
> As an alternative to the vlan-aware-vms and use of ovs within the VM,
>
> I was wondering if the user/group should be (only) set in a common config,
> like neutron.conf, if it should be duplicated in dhcp and metadata config
> files, or if the metadata ini should be added to the list of ini files,
> when starting up the DHCP agent.
>
Previously, metadata_proxy_user/
On Sun, Sep 11, 2016 at 1:22 PM, Emilien Macchi wrote:
> Hopefully Heïkel was also online :-)
>
> Here's the short term workaround: https://review.rdoproject.org/r/#/c/2186/
> For long term, we need to backport what we want from master to
> tripleoclient, specially all the recent mistral changes.
On Friday, 9 September 2016 14:12:51 CEST Matt Riedemann wrote:
> On 9/9/2016 1:58 PM, Ben Swartzlander wrote:
> > On 09/08/2016 08:37 PM, Matt Riedemann wrote:
> >> On 9/8/2016 7:05 PM, Ravi, Goutham wrote:
> >>> Hi,
> >>>
> >>>
> >>>
> >>> I was looking for some clarity around backports of bug
On Mon, Sep 12, 2016 at 7:59 AM, Emilien Macchi wrote:
> On Sun, Sep 11, 2016 at 1:22 PM, Emilien Macchi wrote:
>> Hopefully Heïkel was also online :-)
>>
>> Here's the short term workaround: https://review.rdoproject.org/r/#/c/2186/
>> For long term, we need to backport what we want from master
Hi Heaters,
with great regret I announce my resignation from the heat-core team.
About a year ago I was reassigned to another project, and despite my best
efforts I came to conclusion that unfortunately I can not keep up with
duties expected from Heat core team member in appropriate capacity.
I
Nikhil,
Thank you for all your hard work as Glance PTL (3 times!). Glad to hear
that you will be continuing to work in OpenStack, and especially that you
plan to continue working with Glance.
cheers,
brian
On 9/12/16, 2:08 AM, "Nikhil Komawar" wrote:
>Hi team,
>
>
>Just wanted to share my dec
On Mon, Sep 12, 2016 at 10:24:23AM +0200, Michał Dulko wrote:
> +1, thanks for taking care of that!
>
> On 09/12/2016 03:35 AM, Huang Zhiteng wrote:
> > +1 for this long-waited feature to land in Newton.
> >
> > On Sun, Sep 11, 2016 at 1:09 AM, Jay S. Bryant
> > mailto:jsbry...@electronicjungle.ne
+1
On Mon, Sep 12, 2016 at 3:00 AM, Matthew Mosesohn
wrote:
> +1
>
> On Sun, Sep 11, 2016 at 10:20 PM, Alexey Shtokolov
> wrote:
> > +1
> >
> > Stanislaw made a great contribution!
> > I would like to mention SSL-support, YAQL expressions for data-driven
> > orchestration
> > and his awesome li
Hi Kuryrs!
First of all, I want to thank Gal for the hard work done in the past
two cycles as PTL for the project and to all of you who have
contributed in any and many ways, be it either in documentation, code,
bugs, design, discussion and usage.
I announce my candidacy to the Kuryr PTL position
Hi Pavlo,
It's really bad to hear such news. However as you said we all stay in
community and I believe, we will meet again! :)
See you in Barcelona, I hope ;)
On 12 September 2016 at 15:35, Pavlo Shchelokovskyy
wrote:
> Hi Heaters,
>
> with great regret I announce my resignation from the heat-c
Hi,
Vlad was the only one that was luke-warm in favour of 'ironic node-list
--chassis'. Since I haven't received any positive, enthusiastic comment about
wanting it, I don't think it is worth spending any more time pursuing it.
'openstack baremetal node list --chassis' does exist though (in 1.7
+1 on b) too.
On 12 September 2016 at 13:38, Antoni Segura Puimedon
wrote:
> Hi Kuryrs!
>
> On September 5th's weekly IRC meeting Irena Berezovsky suggested that
> we should take a decision regarding the location of specs and devrefs.
>
> Currently we default to putting all the specs and devrefs
Hello everyone,
I would like to announce my candidacy to continue as Cinder PTL for the Ocata
release.
>
> On Sep 8, 2016, at 3:11 PM, Sean Dague wrote:
>
> On 09/08/2016 09:04 AM, Andrew Laski wrote:
>>
>>
>> On Thu, Sep 8, 2016, at 07:18 AM, Sean Dague wrote:
>>> On 09/07/2016 07:34 PM, Andrew Laski wrote:
On Wed, Sep 7, 2016, at 06:54 PM, Martin Millnert wrote:
> On Thu,
On Mon, Sep 12, 2016 at 2:35 PM, Pavlo Shchelokovskyy
wrote:
> Hi Heaters,
>
> with great regret I announce my resignation from the heat-core team.
>
> About a year ago I was reassigned to another project, and despite my best
> efforts I came to conclusion that unfortunately I can not keep up with
Hi ,
I have below entries in my pipeline.yaml file:
sources:
- name: meter_source
interval: 600
meters:
- "*"
sinks:
- name: meter_sink
transformers:
publishers:
- notifier://
- kafka://localhost:9092?topic=ceilometer
The behaviour of
+1
On Wed, Sep 7, 2016 at 5:07 PM, Maksim Malchuk wrote:
> Hello,
>
> I would like to nominate Stanislaw Bogatkin to fuel-library core due to his
> significant contribution to the project [1] and [2]. He is one of the top
> reviewers and contributors in the project.
>
> [1]
> http://stackalytics.
Hi folks!
I'm looking into support for multiple overclouds with shared control
plane. I'm porting a downstream guide: https://review.openstack.org/368840.
However, this no longer works, probably because "internal_api" network
name is hardcoded in ServiceNetMapDefaults:
https://github.com/ope
+1.
Sean's services as Cinder PTL is really appreciable!!
Regards,
Sheel Rana
On Sep 12, 2016 7:11 PM, "Sean McGinnis" wrote:
Hello everyone,
I would like to announce my candidacy to continue as Cinder PTL for the
Ocata
release.
The Cinder project has made great strides over the last several
Hello,
You all hopefully know me as inc0 on IRC. I would like to submit my candidacy
for the PTL position in the following cycle.
I think we, as a team, did a tremendous job in last cycles, ensuring that Kolla
is and will be the great project to work on and to use. Opensource
project is only
as g
On Mon, Sep 12, 2016 at 1:42 PM, Antoni Segura Puimedon
wrote:
> On Mon, Sep 12, 2016 at 1:29 PM, Coughlan, Ivan
> wrote:
>>
>>
>> Overview
>>
>> Kuryr proposes to address the issues of double encapsulation and exposure of
>> containers as neutron entities when containers are running within VMs.
Hi Ivan,
The approach looks very interesting and seems to be reasonable effort to
make it work with kuryr as alternative to the 'VLAN aware VM' approach.
Having container presented as neutron entity has its value, especially for
visibility/monitoring (i.e mirroring) and security (i.e applying secu
I am fine with option (b) as well.
We can add option (d):
Specs in openstack/*kuryr-specs* but devrefs in each specific project,
i.e., the one that will end up with the implementation code.
On Mon, Sep 12, 2016 at 2:38 PM, Antoni Segura Puimedon
wrote:
> Hi Kuryrs!
>
> On September 5th's weekly
Hi all,
I've decided it's time to step down as PTL of Congress. Partly because I
have so many outside responsibilities, and partly because we have such a
strong team, the time is right for someone else to lead the project. We've
made so much progress over the past couple of years, and there's so
I am announcing my candidacy for PTL for the Release Management team
for the Ocata release cycle [1].
During Newton we successfully split out the Requirements Management
team, which now has enough active members to maintain a healthy review
rate for requirements changes. The team also made signif
On Tue, Sep 6, 2016 at 8:11 AM, Galyna Zholtkevych <
gzholtkev...@mirantis.com> wrote:
> Dear all,
>
> Ironic community needs a help to decide on the specification
>
> of the openstack client command that provide the same functionality as
>
> 'ironic driver-raid-logical-disk-properties' .
>
> Some
Team,
I’m travelling now and would like to skip the meeting. If you still would like
to have it then please take charge.
Renat Akhmerov
@Nokia
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: ope
Ivan,
Thanks for the proposal. From Magnum's point of view, this proposal doesn't
seem to require to store neutron/rabbitmq credentials in tenant VMs which
is more desirable. I am looking forward to the PoC.
Best regards,
Hongbin
On Mon, Sep 12, 2016 at 7:29 AM, Coughlan, Ivan
wrote:
>
>
> *Ov
On 8 September 2016 at 14:40, Corey Bryant
wrote:
> Hi All,
>
> The Ubuntu OpenStack team is pleased to announce the general availability
> of OpenStack Newton B3 milestone in Ubuntu 16.10 and for Ubuntu 16.04 LTS
> via the Ubuntu Cloud Archive.
>
> Ubuntu 16.04 LTS
>
> Y
Hi,
Tomorrow we'll have our weekly meeting:
https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160913
Feel free to add topics as usual,
Thanks!
On Thu, Sep 8, 2016 at 9:57 AM, Iury Gregory wrote:
> No topic/discussion in our agenda, we cancelled the meeting, see you next
> week!
Hello Everyone!
Think disaggregated hardware assembled to meet workload needs,
dynamically growing and shrinking your cloud, and more.
https://wiki.openstack.org/wiki/Rsc
Do come and join us for our very first IRC meeting on Sept 13, UTC 3:00 hrs.
Please forward to others you thin
On Mon, Sep 12, 2016 at 10:51 AM, Ruby Loo wrote:
> My preference is:
>
> * openstack baremetal driver show --raid-logical-disk-properties
>
Agreed here.
The process we encourage is always to first identify the resource you are
operating on. I would add that a 'property' is not a resource,
I am writing to submit my candidacy for re-election as the PTL for the
Trove project (Ocata cycle). I have been an active technical
contributor to the Trove project since just before the Icehouse
release when Trove was integrated into OpenStack. I have also
contributed code[1] and reviews[2] to som
Hi all,
Is there (or was there ever) any plans to implement in Glance a service
that would periodically check that the image files are still available on
the file system (or in whatever storage system being used) and have the
correct checksum?
We had a few issues where an image file was removed f
We are chuffed to announce the release of:
XStatic-Bootstrap-SCSS 3.3.7.1: Bootstrap-SCSS 3.3.7 (XStatic
packaging standard)
With package available at:
https://pypi.python.org/pypi/XStatic-Bootstrap-SCSS
For more details, please see below.
Changes in XStatic-Bootstrap-SCSS 3.3.7.0..3.3.7.1
To the OpenStack Community,
Consider this email my self non-nomination for PTL of Kolla for
the coming Ocata release. I let the team know in our IRC team meeting
several months ago I was passing the on baton at the conclusion of Newton,
but I thought the broader OpenStack community would apprecia
On Sun, Sep 11, 2016 at 11:53 PM, Thierry Carrez
wrote:
>
> FWIW I agree with Jay that the wording "a product" is definitely
> outdated and does not represent the current reality. "Product"
> presupposes a level of integration that we never achieved, and which is,
> in my opinion, not desirable at
On Sep 12, 2016, at 1:53 AM, Thierry Carrez wrote:
> FWIW I agree with Jay that the wording "a product" is definitely
> outdated and does not represent the current reality. "Product"
> presupposes a level of integration that we never achieved, and which is,
> in my opinion, not desirable at this
Hi all!
On Wednesday, Sep 14, 2016 we will try to clean up our bug list, triage,
separate RFEs from real bugs, etc. Then we'll find out which bugs must
be fixed for Newton, and, well, fix them :)
We are starting as soon as the first person joins and stop as soon as
the last person drops. We
Excerpts from Thierry Carrez's message of 2016-09-12 08:53:58 +0200:
> Doug Hellmann wrote:
> > Excerpts from Jay Pipes's message of 2016-09-09 14:30:29 -0400:
> >> > To me, this statement
> >>> about One OpenStack is about emphasizing those commonalities and
> >>> working together to increase the
> On Sep 12, 2016, at 2:17 PM, Doug Hellmann wrote:
>
> Excerpts from Thierry Carrez's message of 2016-09-12 08:53:58 +0200:
>> Doug Hellmann wrote:
>>> Excerpts from Jay Pipes's message of 2016-09-09 14:30:29 -0400:
> To me, this statement
> about One OpenStack is about emphasizing thos
Hi Sergio,
Thanks for reaching out. And this is an excellent question.
Firstly, I'd like to mention that Glance is built-in (and if deployed
correctly) is self-resilient in ensuring that you do NOT need an audit
of such files. In fact, if any operator (particularly large scale
operator) needs su
Hi,
Here is this week's subteam report for Ironic. As usual, this is pulled
directly from the Ironic whiteboard[0] and formatted.
Bugs (dtantsur)
===
- Stats (diff between 29 Aug 2016 and 12 Sep 2016)
- Ironic: 255 bugs (+21) + 213 wishlist items (-1). 41 new (+8), 181 in
progress (
Hello, everyone!
First of all, I would like to thanks all the previous Keystone PTLs,
core reviewers and contributors who have made OpenStack and Keystone
what they are today. It is been a pleasure for me to work in this team
and learn with you all. I would be honored to be your PTL during the
nex
I've just put up https://review.openstack.org/#/c/368995/, declaring my
candidacy for Glance PTL.
Here's the content of that patch for your convenience:
Hello everyone,
I would like to announce my candidacy for the role of PTL of Glance for
the Ocata cycle.
Current State of Glance
Just a gentle reminder, the bug days start Tuesday September 13th.
https://etherpad.openstack.org/p/newton-glance-sept-bug-days
P.S. In some parts of the world, this day has already started.
On 9/7/16 3:54 PM, Nikhil Komawar wrote:
> Hi all,
>
>
> I would like to propose bug days for Glance ne
I am writing to submit my candidacy for re-election as the PTL for the
packaging-deb project.
The idea sparked in Vancouver (spring 2015). The project joined the
big-tent about a year ago (in August 2015, it was approved by the TC)
But it then took about a year to have it bootstraped. This was lon
On 2016-09-12 21:10:04 +0200 (+0200), Thomas Goirand wrote:
[...]
> P.S: It maybe will be a bit hard to find out who can vote, because only
> the debian/newton branch should count, and currently Stackalytics is
> counting the master which contains upstream commits. Hopefully, we can
> solve the iss
Thanks everyone for the quick and positive responses.
I'm on PTO this week with limited internet access, so my replies may have
some delays. Next week it will go back to normal. :-)
Cheers,
Gorka.
On Mon, Sep 12, 2016 at 3:04 PM, Sean McGinnis
wrote:
> On Mon, Sep 12, 2016 at 10:24:23AM +0200
Hi Nikhil,
Thanks so much for you response.
1) No, this is a private cloud.
2) Glance v1 (this problem has manifested itself in one of our oldest
deployments, which is running Icehouse).
3) No, location is not exposed.
4) Glance is setup with the filesystem backend drive, using a Gluster
volume m
I wanted to share my responses to a set of questions from the Product
Working Group who is working with the OpenStack Foundation to collect
updated information on the Newton release for each project (along with
directional guidance on future release plans).
This is a follow up at the end of th
I am announcing my candidacy for Horizon PTL.
I've been contributing to Horizon since the Juno cycle and have
been a core reviewer for the last two cycles. We’ve got a great
culture in the Horizon team that I’d like to help continue and
thrive.
I feel we have made good progress in several areas o
On Mon, Sep 12, 2016 at 04:21:43PM +0200, Dmitry Tantsur wrote:
> Hi folks!
>
> I'm looking into support for multiple overclouds with shared control plane.
> I'm porting a downstream guide: https://review.openstack.org/368840.
>
> However, this no longer works, probably because "internal_api" net
Hello Steve.
Thank you very much for your great work on OAuth 1 authentication for
Keystone.
(1) I have configured Keystone for Federation by following the instructions
below.
Then I can log in to OpenStack through Shibboleth identity provider.
Configuring Keystone for Federation
http://docs.o
Hello everyone,
I would like to announce my candidacy to continue as OpenStack Chef
PTL for the Ocata release.[0]
= State of the Kitchen =
Over the Newton cycle, we said good bye to some contributors, and
hello to others. It slowed our overall output, but Stackalytics shows
that we still
>
> Would you please shed some light on how to configure Keystone for OAuth1?
> Thank you very much.
>
There is some documentation in the API but nothing formally written out:
http://developer.openstack.org/api-ref/identity/v3-ext/index.html
>
> I am trying to develop OAuth 2 client for Keysto
Steve - You did a great job leading the effort & appreciate your work on
building a leadership pipeline for the project.
Best wishes
Carol
Sent from my iPhone
On Sep 12, 2016, at 12:09 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
To the OpenStack Community,
Consider this email my
I'd like to know the latest status on the VMware NSX CI. It's not
automatically reporting on nova changes, I had to manually check it
several times on this change:
https://review.openstack.org/#/c/281134/
And then when it does report it fails every time, and the logs are not
available.
Is s
Thank you so much, Tim, for spearheading and guiding the project all this
time! I'm especially grateful for your emphasis on supporting the
development and the goals of the contributors. I hope we'll continue to
benefit from your vision and your thought-leadership in the future!
Eric
From: Tim
Hi everyone,
The OpenStack Infrastructure (Infra) team is having our next weekly
meeting on Tuesday September 13th, at 19:00 UTC in #openstack-meeting
Meeting agenda available here:
https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting
Anyone is welcome to to add agen
Hi all!
I¹m writing to announce my candidacy for Congress PTL (Ocata).
First, I¹d like to thank Tim for his outstanding leadership since the very
beginning of the project. Under his leadership, Congress has grown from an
interesting idea to a capable service. I would also like to thank everyone
Matt,
There was some cleanup done around 2.30pm (PST) and that's why the logs are
missing.
And the previous failures were due to lower value set for FIXED_NETWORK_SIZE in
devstack
configuration file. It has been increased to 126 now.
Thanks,
Giri
> On Sep 12, 2016, at 4:29 PM, Matt Riedemann
Hi Zhi,
Thanks for reporting this issue. This is caused due to a recent code
change, that shows up only during manual install. Please open a bug. Fix is
fairly straightforward.
- Sridhar
On Sun, Sep 11, 2016 at 8:39 PM, zhi wrote:
> hi,
>
> I downloaded the code from the master branch and inst
Hi folks,
We have two patches to upper-constraints up that we'd like to see merged
for Newton. The package updates in question only changed meta-data, but
they did so in a way that fixes issues for downstream, and it makes sense
to keep upper-constraints in line with what they'll be packaging.
Th
On 8 September 2016 at 11:29, Tony Breeds wrote:
> On Wed, Sep 07, 2016 at 08:10:45AM -0500, Matthew Thode wrote:
> > https://review.openstack.org/366631
> >
> > The combination of oslo.context 2.9.0 + positional 1.0.1 (which is the
> > current minimum requirement) results in various unit test fa
On 09/12/2016 07:39 PM, Richard Jones wrote:
> Hi folks,
>
> We have two patches to upper-constraints up that we'd like to see merged
> for Newton. The package updates in question only changed meta-data, but
> they did so in a way that fixes issues for downstream, and it makes
> sense to keep uppe
Hi all,
I want to get people¹s thoughts regarding what we should set as default
devstack deployment config for Ocata.
At the moment, it is set to deploy three processes: API, policy, and
datasource-drivers.
I see some potential arguments against that:
1. For most users installing via devstack, ru
I'd agree with a single process version of Congress for devstack. I'd say
we should even do that for Newton.
Tim
On Mon, Sep 12, 2016 at 6:34 PM Eric K wrote:
> Hi all,
>
> I want to get people’s thoughts regarding what we should set as default
> devstack deployment config for Ocata.
> At the
When using ansible template module, you may see the trailing newline
is stripped by blocks, like
# template.j2
a = {% if true %}1{% endfor %}
b = 2
the render will be like
a=1b=2
The newline character after `a=1` is stripped.
The root cause comes from jinja2's trim_blocks feature. Ansible
enab
On Tue, Sep 13, 2016 at 10:39:24AM +1000, Richard Jones wrote:
> Hi folks,
>
> We have two patches to upper-constraints up that we'd like to see merged
> for Newton. The package updates in question only changed meta-data, but
> they did so in a way that fixes issues for downstream, and it makes se
On Tue, Sep 13, 2016 at 09:03:52AM +0800, Jamie Lennox wrote:
> So the major difference between positional 1.0 and 1.1 is that we swapped
> from using a @functools.wrap decorator to a @wrapt decorator. The reason
> for this is that @functools.wraps basically screws up any inspection of the
> funct
On 09/09/2016 11:12 AM, Duncan Thomas wrote:
On 9 September 2016 at 17:22, Ben Swartzlander mailto:b...@swartzlander.org>> wrote:
On 09/08/2016 04:41 PM, Duncan Thomas wrote:
Despite the fact I've appeared to be slightly disagreeing with
John in
the IRC discussion
Thanks Brian. I'm glad to be associated with OpenStack and Glance.
On 9/12/16 8:46 AM, Brian Rosmaita wrote:
> Nikhil,
>
> Thank you for all your hard work as Glance PTL (3 times!). Glad to hear
> that you will be continuing to work in OpenStack, and especially that you
> plan to continue workin
Hey Sergio,
Glad to know that you're not having any feature related issues (to me
this is a good sign). Based on your answers, it makes sense to require a
reliability solution for backend data (or some sort of health monitoring
for the user data).
So, I wonder what your thoughts are for such an
Hi Nikhil,
Thank you for your support, guidance and hard work as Glance PTL.
I have enjoyed working with you and glad to know that you will be there to help
:)
Thank you,
Abhishek
-Original Message-
From: Nikhil Komawar [mailto:nik.koma...@gmail.com]
Sent: Monday, September 12, 2016 1
Thanks Abhishek! I'm glad to have been of assistance and happy to help
further.
On 9/13/16 12:27 AM, Kekane, Abhishek wrote:
> Hi Nikhil,
>
> Thank you for your support, guidance and hard work as Glance PTL.
> I have enjoyed working with you and glad to know that you will be there to
> help :)
>
On Tue, Sep 6, 2016 at 9:06 PM, Doug Hellmann wrote:
> Team,
>
> I would like to add Tony Breeds to the "Release Managers" team in
> gerrit. This would give him +2 permissions on openstack-infra/release-tools
> and on openstack/releases. I feel his reviews on both of those repos
> have already dem
Hi Nikhil,
Thanks for your hard work as Glance PTL, you did a great job. And happy
to know you will still work in OpenStack, see you around ;)
On 12/09/16 18:08, Nikhil Komawar wrote:
Hi team,
Just wanted to share my decision for not running for PTL for Glance.
It's been great serving the c
Hi everybody,
After an amazing ride that I believe has created a solid platform for a rich
and interactive search experience in OpenStack, I wanted to let everybody know
that I will not be nominating myself to be the Searchlight PTL for the Ocata
cycle. I will continue as a core reviewer and wi
Thank you Fei Long. It's always a pleasure working with you!
On 9/13/16 12:59 AM, Fei Long Wang wrote:
> Hi Nikhil,
>
> Thanks for your hard work as Glance PTL, you did a great job. And
> happy to know you will still work in OpenStack, see you around ;)
>
> On 12/09/16 18:08, Nikhil Komawar wrote
Hi Travis,
Firstly, I would like to congratulate you for such an amazing piece of
work that you've lead to create.
Even though not very hands on over the last few months, I've kept myself
updated with the new developments in the projects and seen the team
grow. So, I am glad to say that you've
On Mon, Sep 12, 2016 at 9:17 PM, Hongbin Lu wrote:
> Ivan,
>
> Thanks for the proposal. From Magnum's point of view, this proposal
> doesn't seem to require to store neutron/rabbitmq credentials in tenant VMs
> which is more desirable. I am looking forward to the PoC.
>
Hogbin, Can you please el
I like both, 'a' and 'b', options. Would give a slight preferance to 'a',
all documentation at one place.
-VikasC
On Mon, Sep 12, 2016 at 8:48 PM, Irena Berezovsky
wrote:
> I am fine with option (b) as well.
> We can add option (d):
> Specs in openstack/*kuryr-specs* but devrefs in each specifi
Hi Congress folks,
I'm in favor of single process for devstack default. It's easy to check
logs and tests its feature.
best regards,
Masahito
On 2016/09/13 11:00, Tim Hinrichs wrote:
I'd agree with a single process version of Congress for devstack. I'd
say we should even do that for Newton.
98 matches
Mail list logo
