Re: [openstack-dev] [tc][election] Question for the candidates

[Swapnil Kulkarni (coolsvap)]

On Fri, Oct 13, 2017 at 1:12 AM, Clay Gerrard  wrote:
> I like a representative democracy.  It mostly means I get a say in which
> other people I have to trust to think deeply about issues which effect me
> and make decisions which I agree (more or less) are of benefit to the social
> groups in which I participate.  When I vote IRL I like to consider voting
> records.  Actions speak louder blah blah.
>
> To candidates:
>
> Would you please self select a change (or changes) from
> https://github.com/openstack/governance/ in the past ~12 mo or so where they
> thought the outcome or the discussion/process was particular good and
> explain why you think so?
>
> It'd be super helpful to me, thanks!
>
> -Clay
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

I have few of them on my mind.

Setting up guidelines for managing releases of binary artifacts [1]
was very important in and key to the hearts of most OpenStack
operators and everyone who's looking at the next big leap with
containerized deployment.

Embracing new languages in OpenStack which are required as dependency
for certain projects [2] [3] is a very important decision and I would
really like to see it through. While there is a lot of work to be done
to get something fully operational in current infrastructure but as we
will have more contributors who feel the need, we have the background
work ready for it.

And of course setting up the vision and mission for TC [4] was one of
the important things done. There will still be updates to it, but the
current draft is a piece of work with a diverse community like ours.

[1] https://review.openstack.org/#/c/469265/
[2] https://review.openstack.org/#/c/451524/
[3] https://review.openstack.org/#/c/398875/
[4] https://review.openstack.org/#/c/453262/

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap
me at coolsvap dot net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [tc] [kolla] [PTL] who can start the official meeting?

[Swapnil Kulkarni (coolsvap)]

I was attending the weekly requirements meeting when I noticed someone
started the kolla meeting [1] on openstack-meeting-4 channel. I thought we
had the restrictions on the chairs, but apparently there's not. Can we
think about having one such restriction?

[1]
http://eavesdrop.openstack.org/meetings/kolla/2017/kolla.2017-10-11-10.31.html

Best Regards,
Swapnil
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [election][tc] TC Candidacy - Swapnil Kulkarni (coolsvap)

[Swapnil Kulkarni (coolsvap)]

OpenStackers,

I am Swapnil Kulkarni(coolsvap), I have been a ATC since Icehouse and I wish
take this opportunity to throw my hat for election to the OpenStack Technical
Committee this election cycle. I started contributing to OpenStack with
introduction at a community event and since then I have always utilized every
opportunity I had to contribute to OpenStack. I am a core reviewer at kolla
and requirements groups. I have also been active in activities to improve the
overall participation in OpenStack, through meetups, mentorship, outreach to
educational institions to name a few.

My focus of work during TC would be to make it easier for people to get
involved in, participate, and contribute to OpenStack, to build the community.
I have had a few hickups in the recent past for community engagement and
contribution activities but my current employment gives me the flexibilty
every ATC needs and I would like to take full advantage of it and increse
the level of contribution.

Please consider this my application and thank you for your consideration.

[1] https://www.openstack.org/community/members/profile/7314/swapnil-kulkarni
[2] http://stackalytics.com/report/users/coolsvap
[3] https://review.openstack.org/510402

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap
me at coolsvap dot net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] Pycharm professional for OpenStack developers

[Swapnil Kulkarni (coolsvap)]

Greetings,

As many of you are aware, OpenStack community developers get access to
PyCharm professional edition licence to contribute to OpenStack. I am
maintaining the licence allocation. We have limited number of licences
to allocate and it is essential that people who are contributing to
OpenStack should get it. To do this we have a filtering criteria for
revoking licences from non-active users.

If you wake one fine day and realise you do not have an active Pycharm
licence, it may be due to two reasons,
1) you are not contributing actively to OpenStack or
2) you are no longer using PyCharm for contributing to OpenStack.

In either case you are considered not active user of PyCharm and your
licence will be revoked.

I do not mind people reaching out to me personally to request the
licence but I do not actively track requests on mail. I request
everyone to please refer to [1] for requesting new licence.

[1] https://wiki.openstack.org/wiki/Pycharm

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap
me at coolsvap dot net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tricircle]

[Swapnil Kulkarni (coolsvap)]

Glad to see you here sir :)

Best Regards,
Swapnil

On Fri, Sep 30, 2016 at 6:17 PM, Chandrakant Bagade
 wrote:
> Hello ,
>
>
>
> Myself Chandrakant Bagade , working at Persistent System Ltd.
>
> I was trying Tricircle with devstack and found it , a very helpful  idea to
> datacenter management.
>
>
>
> I can see feature like provisioning , image/vm/volume management therein.
>
> I was wondering if features like monitoring/inventory management is also
> available there or planned for coming released. I read the docs but couldn’t
> find the information.
>
>
>
> Can someone from Tricircle team , help me with my query. If these are
> available , then pointer/documents to those would be much appreciated.
>
>
>
> Thanks,
>
> Chandrakant
>
> DISCLAIMER == This e-mail may contain privileged and confidential
> information which is the property of Persistent Systems Ltd. It is intended
> only for the use of the individual or entity to which it is addressed. If
> you are not the intended recipient, you are not authorized to read, retain,
> copy, print, distribute or use this message. If you have received this
> communication in error, please notify the sender and delete all copies of
> this message. Persistent Systems Ltd. does not accept any liability for
> virus infected mails.
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Kolla] Deprecation Policies (related to Heka)

[Swapnil Kulkarni (coolsvap)]

On Sep 29, 2016 3:06 PM, "Christian Berendt" 
wrote:
>
> > On 29 Sep 2016, at 06:26, Steven Dake (stdake)  wrote:
> >
> > If you have a different parsing of the deprecation policy, feel free to
chime in.
>
> Heka is only used as an internal component of Kolla and is not provided
as a service for the operators. It should be sufficient to replace Heka by
something else without deprecating it.
>
> Christian.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

Kolla is an operator tool and there are multiple tools only internal to
deployment. This does not mean we can deprecate tools without operator
being notified about it.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Release] [FFE] two xstatic packages to be bumped in upper-constraints, please

[Swapnil Kulkarni (coolsvap)]

On Tue, Sep 13, 2016 at 6:09 AM, 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
> upper-constraints in line with what they'll be packaging.
>
> The reviews are:
>
> update constraint for XStatic-Bootstrap-SCSS to new release 3.3.7.1
> https://review.openstack.org/#/c/368970/
>
> update constraint for XStatic-smart-table to new release 1.4.13.2
> https://review.openstack.org/#/c/366194/
>
>
> Thanks,
>
> Richard
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


+1

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][FFE] block graphviz 0.5.0

[Swapnil Kulkarni (coolsvap)]

On Fri, Sep 9, 2016 at 3:46 PM, Dirk Müller  wrote:
> Hi Tony,
>
> 2016-09-09 9:42 GMT+02:00 Tony Breeds :
>
>> Has some impact on  octavia (doc-requirements) and rpm-packaging (internal
>> global-requirements.txt)
>
> Yeah, rpm-packaging shouldn't be a blocker on this, since we're just
> trying to keep a snapshot of g-r that we have tested against (this
> isn't fully functional yet).
>
> so +2, workflow+1.
>
> Greetings,
> Dirk
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Thank you all for your responses and getting it merged.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements][FFE] block graphviz 0.5.0

[Swapnil Kulkarni (coolsvap)]

Currently kolla gate jobs are failing due to issues in graphviz 0.5.0. [1]

We need to unblock the gates by blocking graphviz===0.5.0.

[1] https://review.openstack.org/#/c/367416/

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [PyCharm] Renewal of Licence

[Swapnil Kulkarni (coolsvap)]

The annual renewal process of pycharm licences has been completed. As
part of this, the licences ar now renewed till Sep 4, 2017.

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla][documentation] Docimpact bugs

[Swapnil Kulkarni (coolsvap)]

Hello,

We have around 13 doc bugs [1] created for features which required
documentation. Most of the bugs are not attended after the feature got
merged. I have moved all the bugs to o-1. If you think any of this can
be completed within rc1 timeframe, feel free to move it back to the
current milestone or submit a change.


[1] https://bugs.launchpad.net/kolla/+bugs?field.tag=doc

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [tc] persistently single-vendor projects

[Swapnil Kulkarni (coolsvap)]

On Mon, Aug 1, 2016 at 1:09 PM, Thierry Carrez  wrote:
> Steven Dake (stdake) wrote:
>> On 7/31/16, 11:29 AM, "Doug Hellmann"  wrote:
>>> [...]
>>> To be clear, I'm suggesting that projects with team:single-vendor be
>>> given enough time to lose that tag. That does not require them to grow
>>> diverse enough to get team:diverse-affiliation.
>>
>> That makes sense and doesn't send the wrong message.  I wasn't trying to
>> suggest that either; was just pointing out Kevin's numbers are more in
>> line with diverse-affiliation than single vendor.  My personal thoughts
>> are single vendor projects are ok in OpenStack if they are undertaking
>> community-building activities to increase their diversity of contributors.
>
> Basically my position on this is: OpenStack is about providing open
> collaboration spaces so that multiple organizations and individuals can
> collaborate (on a level playing ground) to solve a set of issues. It's
> difficult to have a requirement of a project having a diversity of
> affiliation before it can join, because of the chicken-and-egg issue
> between visibility and affiliation-diversity. So we totally accept
> single-vendor projects as official OpenStack projects.
>
> But if a project is persistently single-vendor after some time and
> nobody seems interested to join it, the technical value of that project
> being "in" OpenStack rather than a separate project in the OpenStack
> ecosystem of projects is limited. It's limited for OpenStack (why
> provide resources to support a project that is obviously only beneficial
> to one organization ?), and it's limited to the organization itself (why
> go through the OpenStack-specific open processes when you could shortcut
> it with internal tools and meetings ? why accept the oversight of the
> Technical Committee ?).

+1 to track this.

>
> So the idea is to find a way for projects who realize that they won't
> attract a significant share of external contributions to move to an
> externally-governed project. I'm not sure we can use a strict deadline
> -- some projects might still be single-vendor after a year but without
> structurally resisting contributions. But being able to trigger a review
> after some time, to assess if we have reasons to think it will improve
> in the future (or not), sounds like a good idea.
>
> --
> Thierry Carrez (ttx)
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


The idea of externally-governed projects is very good since there are
and will be projects which want the status of being part of
"OpenStack" community but cannot have diverse-affiliation due to
inherent nature of development/testing/ci or whatsoever requirements.
If it remains or is known to remain a single vendor project in its
future, it does not need to be dependent on any of the community
resources, be it contributors/infrastructure.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [ptl][requirements] nomination period started

[Swapnil Kulkarni (coolsvap)]

On Wed, Jul 27, 2016 at 7:11 PM, Matthew Thode
 wrote:
> We've started a period of self nomination in preparation for the
> requirements project fully moving into project (as it's still under Doug
> Hellmann).
>
> We are gathering the self nominations here before we vote next week.
> https://etherpad.openstack.org/p/requirements-ptl-newton
>
> Nominees should also send an email to the openstack-dev list.
>
> --
> -- Matthew Thode (prometheanfire)
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

I would like to nominate for the PTL of newly formed requirements team.

I joined release engineering discussion during Austin Summit as an
enthusiast to see and volunteer for contribution. From the bootstrap
meeting of the requirement group [1] I have contributed with both code
and reviews[2]. I constantly review the requirements queue and always
help people to accelerate the merge of failing/required libraries. I
would like to do better management of requirements project. I have
started with the formulating team meeting agenda on wiki.

I wish to work on the requirements in the same intent going forward.

Thank you,
coolsvap

[1] 
http://eavesdrop.openstack.org/meetings/requirements/2016/requirements.2016-05-18-12.00.html
[2] http://stackalytics.com/report/contribution/requirements/75

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla] Binary containers with pip install?

[Swapnil Kulkarni (coolsvap)]

Dear Kollagues,

There has been a detailed conversation between me and Prithiv related
to [1] and allowing pip install in binary containers.

Till now we have simply skipped the binary containers till we have
official packages in respective distro repositories. I strongly feel
we should be following that.

If someone wishes to have a functionality without a package in the
base distro, there is always an option to build source containers and
use it with Kolla.

Thoughs welcome?

[1] https://review.openstack.org/#/c/344930/

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [requirements] Project Mascot

[Swapnil Kulkarni (coolsvap)]

Hello,

We had a discussion about project mascot for requirements team today
at the team meeting. Some of the options mentioned are added to [1].
If you have any option, please add to the list.
Also do not forget to provide preference. We will finalize the mascot
on Monday July 25.

[1] https://etherpad.openstack.org/p/requirements-team-mascot

--
Best Regards,
Swapnil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [PyCharm] [all] Revoking pycharm licences for non-active users

[Swapnil Kulkarni (coolsvap)]

On Tue, May 17, 2016 at 4:22 PM, Swapnil Kulkarni  wrote:
> Hello All,
>
> As part of the JetBrains Community support OpenStack (active)
> developers get access to community edition of PyCharm tool. From the
> management perspective I am facing issue to allocate licences to new
> requests. With some review, I have found more than 70 licences which
> are allocated and never used.
>
> I am revoking the PyCharm licences for this list of users. If you are
> among the users and you still think you need PyCharm licence, feel
> free to request a licence.
>
> Note: This exercise will be done every month for users who are not
> actively using PyCharm for 3 months or more.
>
> Best Regards,
> Swapnil

In order to make it easier for active contributors to obtain PyCharm
licence, I have created [1] to submit the information.

[1] 
https://docs.google.com/forms/d/1dQnWgvs9Aanf0Jx2OyZhVewDi2q8r5c905BdWBdXwvA/viewform

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][vote] Applying for stable-follows tag

[Swapnil Kulkarni (coolsvap)]

On Mon, Jul 18, 2016 at 6:23 PM, Paul Bourke  wrote:
> Hi Steve,
>
> +1 to applying. I'll volunteer for the backport team also.
>
> -Paul
>
>
> On 18/07/16 13:07, Steven Dake (stdake) wrote:
>>
>> Hey Koalians,
>>
>> I'd like us to consider applying  for the stable follows policy tag.
>>   Full details are here:
>>
>>
>> http://github.com/openstack/governance/blob/master/reference/tags/stable_follows-policy.rst
>>
>> Because of the magic work we did to make liberty functional, it is
>> possible that we may not be able to apply for this tag until Liberty
>> falls into EOL.  Still I personally believe intent matters most, and our
>> intent has always been for these to be stable low-rate-of-change
>> no-feature-backport branches.  There are some exceptions I think we
>> would fit under for the Liberty case, so I think it is worth a shot.
>>
>> I'd need 2-4 people to commit to joining the stable backport team for
>> Kolla reviews specifically.  These folks would be the only folks that
>> could ACK patches in the stable branch maintenance queue.  Anyone could
>> continue to submit backport patches as they desire.
>>
>> I'll leave voting open for 1 week or until there I a majority (6 core
>> reviewers) or until there is a unanimous vote.  If there is not, then we
>> won't apply.  The deadline for this vote is July 25th.
>>
>> Thanks!
>> -steve
>>
>>
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

+1 to apply for stable follows policy.
I would like to volunteer for the backport team.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] our mascot - input needed

[Swapnil Kulkarni (coolsvap)]

On Fri, Jul 15, 2016 at 1:38 AM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> The OpenStack foundation is putting together mascots for every project with
> a proper artist doing the work.  The cool thing about this is we a) get
> stickers b) have consistent look and feel among mascots in OpenStack.
>
> The downside is we have to make a decision.  The foundation wants 3-5
> choices.
>
> The mascot must be an animal and it can't involve glue or other inc007
> inspired ideas :)
>
> Obviously Koala bear is probably everyone's first choice since we have sort
> of been using that as a mascot since day one.  Anyone else have anything
> else for me to provide the foundation with a choices 2-5?
>
> Please respond quickly, the foundation needs the information shortly.  I'd
> like to offer up two alternatives just in case.
>
> Regards
> -steve
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

Koala bear

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][nova][infra] Voting gates

[Swapnil Kulkarni (coolsvap)]

On Thu, Jul 14, 2016 at 7:51 PM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> At the midcycle, we had a session on gating.
>
> Out of that session came the decision to make the build gates voting as soon
> as the mirroring is finished for ubuntu first (because that is closer for us
> to get mirroring sorted out) followed by CentOS/Oracle Linux.  I am taking
> this work on (mirroring specifically) and expect it to finish in the next
> 1-2 weeks (ubuntu only).  After that I will sort out the centos mirroring.
> I'm not sure who got the mirroring work kicked off in infrastructure – I
> think it was Jessie Pretorious – if the credit is wrong apologies, but
> whoever it was, - huge thanks from me personally :)
>
> We are not making the deploy gates voting at this time, although the plan is
> to do so once we stablize the last of the gate issues.  I think we are just
> down to one issue now, and that is that ubuntu source fails with an error
> about VIR MIGRATE AUTO CONVERGE.  This looks to be a nova bug.  If the nova
> community has any bones to throw us on how to fix this, it would be
> appreciated.  I'd cut and paste the log, but for some reason C isn't
> working in my email client at present.
>
> If folks know of other consistent deploy gate failures, can you please
> respond on this thread with either a bug link or a link to a log of the
> failure in question.
>
> The review where it fails is 339776.
>
> Regards
> -steve
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>


+1 I think its good idea to finally move towards voting build jobs.

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] New specs process - a dicussion

[Swapnil Kulkarni (coolsvap)]

On Jul 12, 2016 8:04 PM, "Michał Jastrzębski"  wrote:
>
> Hey guys,
>
> Since our project matured, we decided that we should have a discussion
> regarding our spec process.
>
> https://etherpad.openstack.org/p/kolla-N-midcycle-specs
>
> Currently we do specs for most critical things, and they require majority
vote.
>
> We want to introduce another way, to enable non-nuclear specs.
> To summarize our discussion so far:
>
> 1. Specs will require only 2 * +2 by default
> 2. Specs sit at minimum 2 weeks in gerrit before first +2 arrives, so
> other people will have time to look at it
> 3. Any core can require a rollcall vote - then it becomes rollcall vote
> 4. If nobody calls for rollcall vote, after 2 weeks spec can be merged
> with normal 2 * +2
>
> Thoughts?
> Michal
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

+1 I agree.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla][vote] Apply for release:managed tag

[Swapnil Kulkarni (coolsvap)]

On Fri, Jul 1, 2016 at 6:26 AM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> I'd like the release management team to take on releases of Kolla.  This
> means applying for the release:managed[1] tag.  Please vote +1 if you wish
> to proceed, or –1 if you don’t wish to proceed.  The most complex part of
> this change will be that when feature freeze happens, we must actually
> freeze all feature development.  We as a team haven't been super good at
> this in the past, but I am confident we could hold to that set of rules if
> the core team is in agreement on this vote.
>
> I will leave voting open or 1 week until July 8th.  If a majority is reached
> prior to that date, I will close voting early and submit governance changes.
>
> Note the release team would have  to accept our application, so even though
> we may decide to vote to be release:managed, it is ultimately up to the
> discretion of the release management team whether we meet the criteria and
> if they have the bandwidth to work with our release liason.
>
> [1]
> https://github.com/openstack/governance/blob/master/reference/tags/release_managed.rst
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

+1 to apply for release:managed tag.

Swapnil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

[Swapnil Kulkarni (coolsvap)]

On Wed, Jun 29, 2016 at 4:57 PM, Swapnil Kulkarni (coolsvap)
<m...@coolsvap.net> wrote:
> On Wed, Jun 29, 2016 at 3:30 AM, James Slagle <james.sla...@gmail.com> wrote:
>> We've got some new contributors around TripleO recently, and I'd like
>> to offer up a "TripleO deep dive hour".
>>
>> The idea is to spend 1 hour a week in a high bandwidth environment
>> (Google Hangouts / Bluejeans / ???) to deep dive on a TripleO related
>> topic. The topic could be anything TripleO related, such as general
>> onboarding, CI, networking, new features, etc.
>>
>> I'm by no means an expert on all those things, but I'd like to
>> facilitate the conversation and I'm happy to lead the first few
>> "dives" and share what I know. If it proves to be a popular format,
>> hopefully I can convince some other folks to lead discussions on
>> various topics.
>>
>> I think it'd be appropriate to record these sessions so that what is
>> discussed is available to all. However, I don't intend these to be a
>> presentation format, and instead more of a q discussion. If I don't
>> get any ideas for topics though, I may choose to prepare something to
>> present :).
>>
>> Our current meeting time of day at 1400 UTC seems to suit a lot of
>> folks, so how about 1400 UTC on Thursdays? If folks think this is
>> something that would be valuable and want to do it, we could start
>> next Thursday, July 7th.
>>
>>
>> --
>> -- James Slagle
>> --
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> +1

I have done some bootstrapping in the ehterpad [1]. Hoping to see some
action there :)

[1] https://etherpad.openstack.org/p/tripleo-deep-dive-topics

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [TripleO] TripleO deep dive hour?

[Swapnil Kulkarni (coolsvap)]

On Wed, Jun 29, 2016 at 3:30 AM, James Slagle  wrote:
> We've got some new contributors around TripleO recently, and I'd like
> to offer up a "TripleO deep dive hour".
>
> The idea is to spend 1 hour a week in a high bandwidth environment
> (Google Hangouts / Bluejeans / ???) to deep dive on a TripleO related
> topic. The topic could be anything TripleO related, such as general
> onboarding, CI, networking, new features, etc.
>
> I'm by no means an expert on all those things, but I'd like to
> facilitate the conversation and I'm happy to lead the first few
> "dives" and share what I know. If it proves to be a popular format,
> hopefully I can convince some other folks to lead discussions on
> various topics.
>
> I think it'd be appropriate to record these sessions so that what is
> discussed is available to all. However, I don't intend these to be a
> presentation format, and instead more of a q discussion. If I don't
> get any ideas for topics though, I may choose to prepare something to
> present :).
>
> Our current meeting time of day at 1400 UTC seems to suit a lot of
> folks, so how about 1400 UTC on Thursdays? If folks think this is
> something that would be valuable and want to do it, we could start
> next Thursday, July 7th.
>
>
> --
> -- James Slagle
> --
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

+1

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][packaging] Normalizing requirements file

[Swapnil Kulkarni (coolsvap)]

On Wed, Jun 22, 2016 at 10:15 AM, Haïkel  wrote:
> Hi,
>
> as a packager, I spend a lot of time to scrutinize the requirements
> repo, and I find it easier to read if specifiers are ordered.
> So in a quick glance, you can check which is the min version required
> and max one without trying to search them among other specifiers.
> I scripted a basic linter to do that (which also normalize comments to
> PEP8 standards)
>
> Initial review is here:
> https://review.openstack.org/#/c/332623/
>
> script is available here;
> https://gist.github.com/hguemar/7a17bf93f6c8bd8ae5ec34bf9ab311a1
>
> Your thoughts?
>
> Regards,
> H.
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Haikel,

This looks good and the global-requirements.txt now looks much cleaner.

Can you add the linter to the tools directory in requirements. We can
use it in our gates.

Swapnil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [requirements][all] VOTE to expand the Requirements Team

[Swapnil Kulkarni (coolsvap)]

Thank you all.

On Mon, Jun 20, 2016 at 6:39 PM, Davanum Srinivas <dava...@gmail.com> wrote:
> Thanks for the VOTE everyone.
>
> Matthew, Dirk, Swapnil, Tony, Thomas,
> With this VOTE the training wheels come off :) Please be cautious with
> your new super powers!

Dims, yes of course :)

>
> And thanks a Ton to Thierry as well.
>
> Thanks,
> Dims
>
> On Fri, Jun 17, 2016 at 3:59 PM, Robert Collins
> <robe...@robertcollins.net> wrote:
>> Sure. +1
>>
>> On 17 June 2016 at 02:44, Davanum Srinivas <dava...@gmail.com> wrote:
>>> Folks,
>>>
>>> At Austin the Release Management team reached a consensus to spin off
>>> with some new volunteers to take care of the requirements process and
>>> repository [1]. The following folks showed up and worked with me on
>>> getting familiar with the issues/problems/tasks (see [1] and [2]) and
>>> help with the day to day work.
>>>
>>> Matthew Thode (prometheanfire)
>>> Dirk Mueller (dirk)
>>> Swapnil Kulkarni (coolsvap)
>>> Tony Breeds (tonyb)
>>> Thomas Bechtold (tbechtold)
>>>
>>> So, please cast your VOTE to grant them +2/core rights on the
>>> requirements repository and keep up the good work w.r.t speeding up
>>> reviews, making sure new requirements don't break etc.
>>>
>>> Also, please note that Thierry has been happy enough with our work to
>>> step down from core responsibilities :) Many thanks Thierry for
>>> helping with this effort and guidance. I'll make all the add/remove to
>>> the requirements-core team when this VOTE passes.
>>>
>>> Thanks,
>>> Dims
>>>
>>> [1] https://etherpad.openstack.org/p/newton-relmgt-plan
>>> [2] https://etherpad.openstack.org/p/requirements-tasks
>>> [3] https://etherpad.openstack.org/p/requirements-cruft
>>>
>>> --
>>> Davanum Srinivas :: https://twitter.com/dims
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> --
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap
me at coolsvap dot net
+91-87960 10622(c)
http://in.linkedin.com/in/coolsvap
"It's better to SHARE"

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] stepping down from core

[Swapnil Kulkarni (coolsvap)]

On Tue, Jun 7, 2016 at 1:06 AM, Jeff Peeler  wrote:
> Hi all,
>
> This is my official announcement to leave core on Kolla /
> Kolla-Kubernetes. I've enjoyed working with all of you and hopefully
> we'll cross paths again!
>
> Jeff
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


All the best Jeff for the next big thing you are going to do :)

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

[Swapnil Kulkarni (coolsvap)]

On Fri, Jun 10, 2016 at 6:44 AM, Steven Dake (stdake) <std...@cisco.com> wrote:
> Swapnil,
>
> Thanks for triggering this community vote.  It was sorely overdue :).  I
> counted 8 votes before I voted (I am all for moving everything to 1600UTC)
> which is a majority of the CR team.  Note in the future I think we may
> need to consider having split meetings again, if our community makeup
> changes.

Steve, yes I understand.

>
> I have submitted a review to make the change official:
> https://review.openstack.org/#/c/327845/1
>
>
> Regards
> -steve
>
>
> On 6/8/16, 5:54 AM, "Swapnil Kulkarni (coolsvap)" <m...@coolsvap.net> wrote:
>
>>Dear Kollagues,
>>
>>Some time ago we discussed the requirement of alternating meeting
>>times for Kolla weekly meeting due to major contributors from
>>kolla-mesos were not able to attend weekly meeting at UTC 1600 and we
>>implemented alternate US/APAC meeting times.
>>
>>With kolla-mesos not active anymore and looking at the current active
>>contributors, I wish to reinstate the UTC 1600 time for all Kolla
>>Weekly meetings.
>>
>>Please let me know your views.
>>
>>--
>>Best Regards,
>>Swapnil Kulkarni
>>irc : coolsvap
>>
>>__
>>OpenStack Development Mailing List (not for usage questions)
>>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Thank you all for your vote!

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [kolla] Request for changing the meeting time to 1600 UTC for all meetings

[Swapnil Kulkarni (coolsvap)]

Dear Kollagues,

Some time ago we discussed the requirement of alternating meeting
times for Kolla weekly meeting due to major contributors from
kolla-mesos were not able to attend weekly meeting at UTC 1600 and we
implemented alternate US/APAC meeting times.

With kolla-mesos not active anymore and looking at the current active
contributors, I wish to reinstate the UTC 1600 time for all Kolla
Weekly meetings.

Please let me know your views.

-- 
Best Regards,
Swapnil Kulkarni
irc : coolsvap

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] prototype of a DSL for generating Dockerfiles

[Swapnil Kulkarni (coolsvap)]

On Fri, May 27, 2016 at 8:35 AM, Steven Dake (stdake)  wrote:
> Hey folks,
>
> While Swapnil has been busy churning the dockerfile.j2 files to all match
> the same style, and we also had summit where we declared we would solve the
> plugin problem, I have decided to begin work on a DSL prototype.
>
> Here are the problems I want to solve in order of importance by this work:
>
> Build CentOS, Ubuntu, Oracle Linux, Debian, Fedora containers
> Provide a programmatic way to manage Dockerfile construction rather then a
> manual (with vi or emacs or the like) mechanism
> Allow complete overrides of every facet of Dockerfile construction, most
> especially repositories per container (rather than in the base container) to
> permit the use case of dependencies from one version with dependencies in
> another version of a different service
> Get out of the business of maintaining 100+ dockerfiles but instead maintain
> one master file which defines the data that needs to be used to construct
> Dockerfiles
> Permit different types of optimizations or Dockerfile building by changing
> around the parser implementation – to allow layering of each operation, or
> alternatively to merge layers as we do today
>
> I don't believe we can proceed with both binary and source plugins given our
> current implementation of Dockerfiles in any sane way.
>
> I further don't believe it is possible to customize repositories & installed
> files per container, which I receive increasing requests for offline.
>
> To that end, I've created a very very rough prototype which builds the base
> container as well as a mariadb container.  The mariadb container builds and
> I suspect would work.
>
> An example of the DSL usage is here:
> https://review.openstack.org/#/c/321468/4/dockerdsl/dsl.yml
>
> A very poorly written parser is here:
> https://review.openstack.org/#/c/321468/4/dockerdsl/load.py
>
> I played around with INI as a format, to take advantage of oslo.config and
> kolla-build.conf, but that didn't work out.  YML is the way to go.
>
> I'd appreciate reviews on the YML implementation especially.
>
> How I see this work progressing is as follows:
>
> A yml file describing all docker containers for all distros is placed in
> kolla/docker
> The build tool adds an option —use-yml which uses the YML file
> A parser (such as load.py above) is integrated into build.py to lay down he
> Dockerfiles
> Wait 4-6 weeks for people to find bugs and complain
> Make the —use-yml the default for 4-6 weeks
> Once we feel confident in the yml implementation, remove all Dockerfile.j2
> files
> Remove —use-yml option
> Remove all jinja2-isms from build.py
>
> This is similar to the work that took place to convert from raw Dockerfiles
> to Dockerfile.j2 files.  We are just reusing that pattern.  Hopefully this
> will be the last major refactor of the dockerfiles unless someone has some
> significant complaints about the approach.
>
> Regards
> -steve
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

The DSL template to generate the Dockerfile seems way better than the
jinja templates in terms of extension which is currently a major
bottleneck in the plugin implementation. I am +2+W on this plan of
action to test it for next 4-6 weeks and see thereon.

Swapnil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [kolla] Cross project spec liason

[Swapnil Kulkarni (coolsvap)]

On Thu, May 26, 2016 at 8:28 AM, Steven Dake (stdake)  wrote:
> Fellow core reviewers,
>
> I have a lot of liasing to do as a PTL and would like to offload some of
> it so I can get some actual sleep :)  Are there any takers on Mike's
> requirement for a cross-project liason for Kolla?  The job involves
> reviewing all specs in the cross project spec repository and understanding
> their technical impact on Kolla.  It is important in this role to take
> care of ensuring Kolla's objectives are met by the specs and raise any red
> flags to the PTL and provide an update to the core team during our weekly
> team meeting.  This responsibility comes with +2/-2 voting rights on all
> cross project specifications.
>
> The individual must be a core reviewer.
>
> Regards,
> -steve
>
> On 5/17/16, 6:41 AM, "Mike Perez"  wrote:
>
>>Hi PTL's,
>>
>>Please make sure your cross-project spec liaisons are up-to-date [1].
>>This role
>>defaults to the PTL if no liaison is selected. See list of
>>reponsibilities [2].
>>
>>As agreed by the TC, the cross-project spec liaison team will have voting
>>rights on the openstack/openstack-spec repo [3]. Next week I will be
>>adding
>>people from the cross-project spec liaison list to the gerrit group with
>>the
>>appropriate ACLs.
>>
>>
>>[1] -
>>https://wiki.openstack.org/wiki/CrossProjectLiaisons#Cross-Project_Spec_Li
>>aisons
>>[2] -
>>http://docs.openstack.org/project-team-guide/cross-project.html#cross-proj
>>ect-specification-liaisons
>>[3] -
>>http://governance.openstack.org/resolutions/20160414-grant-cross-project-s
>>pec-team-voting.html
>>
>>--
>>Mike Perez
>>
>>__
>>OpenStack Development Mailing List (not for usage questions)
>>Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


Steve,

I would like to take the responsibility to be cross-project liaison for Kolla.

Swapnil

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev