Thierry,
I personally prefer the meeting rooms as they are; however, we do need more of
them. I am often pinged in various other meetings in the common meeting
channels and find the group communication that happens in this way preferable
to joining each specific project channel. Joining each
Hey folks,
Jeffrey delegated to me to determine the tagging structure for
kolla-kubernetes. I was under the mistaken impression we need to tag 1.0.0
with the milestone tags (such as 1.0.0.0b2/1.0.0.0b3) for kolla-kubernetes.
That is not the case. We will be tagging 0.4.0 next, then 0.5.0, th
Jeffrey,
I think a better balance among the core reviewer teams for the 3 core
reviewer teams we have for our 3 deliverables is warranted as you stated.
To clarify my position, I am happy to train individuals on how to manage
Launchpad, even one on one for our core reviewers that don’t know h
The issue raised is they violate the 4 opens.
From: Michał Jastrzębski
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, December 12, 2016 at 8:09 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [kolla][t
ecember 14, 2016 at 3:22 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [kolla][tc] Video Meetings - input requested
On Wed, Dec 14, 2016 at 3:33 PM, Thierry Carrez
wrote:
> Ed Leafe wrote:
>> On Dec 12, 2016, at
portdirect +1
srwilkers +1
Doing a fantastic job reviewing and writing code and participating in team
meetings/irc conversations.
Regards
-steve
-Original Message-
From: Michał Jastrzębski
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, Dece
Folks,
I am in favor of using a new tag called [rdo] such that RDO (or its transitive
dependencies) can be discussed and filtered by email clients as it relates to
development topics that affect the broader OpenStack ecosystem. As RDO is a
community driven project which is very much related to
M, Erno Kuvaja wrote:
> On Mon, Dec 19, 2016 at 2:21 PM, Steven Dake (stdake)
wrote:
>> Folks,
>>
>>
>>
>> I am in favor of using a new tag called [rdo] such that RDO (or its
>> transitive dependencies) can be discussed and filtere
Hey peeps,
David Wang asked that we remove him from the kolla-kubernetes-core team because
he is involved in other activities and he isn’t sure if or when he will be able
to begin reviewing again.
In our earlier cleanup of the kolla-kubernetes-core review team, the core
reviewer team was on th
Derek,
I think Serverless is a great idea. I had considered starting a new project in
October around Serverless. During my analysis I of course saw iron.io’s work
and OpenWhisk. I thought OpenWhisk would be a better community to join as it
was open. Iron.io and OpenWhisk should join forces!
Hello folks,
In our team meeting today, I took an action to begin a mailing list discussion
around what to call our k8s objects in the kolla-kubernetes deliverable. At
present, we are calling them “pods”. The general consensus on the team meeting
is this is a hard concept for people new to th
Hey folks,
I have seen many reviews hitting the queue without reno release notes.
Its very simple and straightforward to create a reno release note. Simply run:
reno –n blurb
This creates a file in the releasenotes directory with a hash. Releasenotes
should be committed with the commit in qu
Michal,
I was thinking about kolla-salt and our Wednesday team meeting and the
declaration you made about how it should be done. I personally feel it is
mandatory we hold a vote of the core review teams to add a new deliverable. We
have voted on the addition of every deliverable we have ever
Hey folks,
Brandon Jozsa was kind enough to get some collaboration going between the
OpenStack Kolla community and the Helm community within CNCF. My hope out of
this effort is to build bridges between the OpenStack foundation and CNCF
hosted by the Linux Foundation. We are starting small, by
chal
On 23 December 2016 at 05:34, Steven Dake (stdake) wrote:
> Michal,
>
>
>
> I was thinking about kolla-salt and our Wednesday team meeting and the
> declaration you made about how it should be done. I personally feel it is
> mandatory we h
il fast to run kolla with
whatever. We need this kind of flexibility for people to innovate.
Thoughts?
Michal
On 23 December 2016 at 13:11, Steven Dake (stdake) wrote:
> Michal,
>
> Really what I was getting at was placing in the governance repository
-
From: "Steven Dake (stdake)"
Date: Friday, December 23, 2016 at 3:53 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [tc] Re: [kolla] A new kolla-salt deliverable
WFM – I’d be partly in favor of such an approach althou
Jeffrey,
Have you detected any pattern to any specific cloud provider in the logs?
Regards
-steve
From: Jeffrey Zhang
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Friday, December 30, 2016 at 12:41 AM
To: OpenStack Development Mailing List
Subject: Re: [ope
"OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [kolla][rdo] libvirt 2.0 process is failed during
launching qemu progress
I checked more than ten error gates, all of them happened in rax-iad.
On Sat, Dec 31, 2016 at 12:06 PM, Steven Dake
I think optimally we should check if we are running in rax-iad, and if so, set
libvirt virtualization to qemu. I was pretty sure the gate script that sets up
the system sets the libvirt type to qemu. After inspection of the gate
scripts, this is not the case. Perhaps it was setup this way pre
Michal,
Another option is 2 individuals from each core review team + PTL. That is
lighter weight then 3 and 4, yet more constrained then 1 and 2 and would be my
preferred choice (or alternatively 3 or 4). Adding a deliverable is serious
business ☺
FWIW I don’t’ think we are at an impasse, it
Thierry,
I am not a big fan of the separate gerrit teams we have instituted inside the
Kolla project. I always believed we should have one core reviewer team
responsible for all deliverables to avoid not just the appearance but the
reality that each team would fragment the overall community of
.
Regards
-steve
-Original Message-
From: Doug Hellmann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Wednesday, January 11, 2017 at 10:59 AM
To: openstack-dev
Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables
Excerpts from S
best interest should take priority.
Cheers,
Michal
On 11 January 2017 at 09:59, Doug Hellmann wrote:
> Excerpts from Steven Dake (stdake)'s message of 2017-01-11 14:50:31 +:
>> Thierry,
>>
>> I am not a big fan of the separate gerrit teams we have instituted in
Jozsa"
Date: Wednesday, January 11, 2017 at 1:01 PM
To: "Britt Houser (bhouser)" , "Steven Dake (stdake)"
, "OpenStack Development Mailing List (not for usage
questions)"
Subject: Re: [openstack-dev] [tc][kolla] Adding new deliverables
I’m not entirely sure h
Thierry,
Cool thanks for the leeway here ☺
I agree wholeheartedly with your last sentiment. If an existing Kolla sub-team
or an existing project (e.g. the Puppet team) in OpenStack or a new project
wants to use Kolla images and feels they would operate more effectively without
the structure K
We are busily releasing 0.4.0 of the Kolla deliverable kolla-kubernetes and
have determined we can’t release the kolla-kubernetes milestone without the
release liaison for Kolla being on the core reviewer sub-team to make last
minute fine tuning adjustments to the release and approve other peopl
Doug,
Thanks for your leadership and your consistent help with helping Kolla solve
how to use the release team’s tooling.
I have to say that manually tagging as we did previously as PTLs (when I was a
PTL) was pure madness. I really like what the releases team has done for
OpenStack!
Regards,
Hey folks,
The release team released kolla-kubernetes 0.4.0 Sunday January 15th. Now we
are in 0.5.0 development which lasts one month.
The general architecture of OpenStack based deployments with a Kubernetes
underlay is taking form. There are 5 blueprints in 0.5.0 which we expect
should la
My vote is for option 2 to deprecate Debian as there has been very little
activity and operators seem uninterested in Debian as a platform.
We could always add it back in at a later date if operators were to request it
and the Debian team were interested in maintaining it.
Regards
-steve
Kris,
Thanks for adding the kolla tag. As we reach milestone 3, every kolla dev is
knee deep in development and probably not reading mails not directly tagged
with [kolla].
IOutlook 2016 has a bug where I cannot respond inline. I am replying here so
my gmail account picks up the email so tha
Gema,
Yes team meeting sounds good.
I am changing my vote from choice 2 to abstain until this is sorted out.
Regards
-steve
-Original Message-
From: Gema Gomez
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Tuesday, January 24, 2017 at 7:42 AM
To: "op
Thanks peeps for responding to Kris. Kris, I had offered a response – do you
need further information answered? It looks to me like all the questions have
been answered by others in the community. If not, feel free to respond and
I’ll answer the remainders.
Sean when your around and I am ple
Hey folks,
Toby Cardone has kindly organized a local (to me) community meetup hosted by
the Red Hat Software User Group at Insight’s facilities in Tempe, AZ with the
topic of Kolla on February 15th, 2017 at 21:00 UTC. Several folks in the Kolla
IRC channel have asked if remote participation is
Hey folks,
Pip install kolla-ansible is busted. I’d take ownership of this bug myself,
however, I am personally swamped. This is a DOA deliverable issue and as such
is higher priority than “critical”. Can someone in the community take a look?
https://bugs.launchpad.net/kolla-ansible/+bug/166
Jay,
I don’t see a reference to the wiki page in your email and don’t immediately
see the LCOO working group wiki. From what you describe this working group is
not working within the framework of the 4 opens which is one of OpenStack’s
fundamental philosophies.
Thanks for bringing up your que
Flavio,
I think Michal (inc0) was planning to reach out to the TripleO team to at least
get one or more design sessions in Wednesday. Kolla’s PTG schedule for Monday
and Tuesday is packed with a wait list of topics. I depart IIRC Wednesday at
11AM – I had asked inc0 if we do these we do them
Marcin,
I think this work is fantastic!
The Ocata feature deadline has passed. Reference:
https://releases.openstack.org/ocata/schedule.html
The feature freeze deadline was January 25th 2017. What this means is that
this work will need to go into Pike instead of Ocata. One of the reasons you
7:16 PM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [kolla] unblocking the gate
On Mon, Feb 29, 2016, at 01:38 PM, Sam Yaple wrote:
> On Mon, Feb 29, 2016 at 6:42 PM, Clark Boylan
> wrote:
>
> > On Mon, Feb 29, 2016, at 0
Flavio,
Somehow the fuel project and openstack-ansible project got left off the
taglines. I’m not sure if the fuel peeps saw this thread, but I know the
openstack-ansible peeps didn’t see the thread. As a result, I’ve added those
taglines. Hopefully we can include the broader deployment tool
The mascot is absolutely fantastic! Nice work to all involved!
Regards
-steve
-Original Message-
From: Michał Jastrzębski
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Monday, February 13, 2017 at 7:53 PM
To: "OpenStack Development Mailing List (not fo
. The rest of the
information is correct.
Hope to see you for the live stream or if your in the greater Phoenix area, in
person!
Regards
-steve
From: "Steven Dake (stdake)"
Date: Tuesday, January 31, 2017 at 5:56 PM
To: "OpenStack Development Mailing List (not for usage questio
Dake
Reply-To: "Steven Dake (stdake)"
Date: Saturday, February 18, 2017 at 12:02 AM
To: "Steven Dake (stdake)"
Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #1
You can forward this invitation to others.
Hello,
Steven Dake invites you to join this WebEx
Reply-To: "Steven Dake (stdake)"
Date: Saturday, February 18, 2017 at 12:07 AM
To: "Steven Dake (stdake)"
Subject: (Forward to others) WebEx meeting invitation: Kolla PTG Day #2
You can forward this invitation to others.
Hello,
Steven Dake invites you to join this WebEx
e at the PTG
sessions.
--
Brandon B. Jozsa
________
From: Steven Dake (stdake)
Sent: Saturday, February 18, 2017 2:16:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [kolla] PTG Day #1 Webex remote participation
Hey f
(not for usage questions)"
Subject: Re: [openstack-dev] [kolla] PTG Day #1 Webex remote participation
________
From: Steven Dake (stdake)
Sent: Saturday, February 18, 2017 10:46 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [ope
0000 (+), Steven Dake (stdake) wrote:
[...]
> In the past the foundation has been wary of enabling remote
> participation.
[...]
Only wary because of prior experience: Cisco donated Webex service
and dedicated remote production staff for us throughout the H
Jeremy,
I understood your original message that it was a logistical nightmare to sort
out scaling remote participation across the entire ODS or (now the new PTGs)
and it is not a software tools problem but rather a logistics problem
independent of whatever software platform is used. I agree, e
?Jeffrey,
Thanks for your excellent service as Kolla PTL. You have served the Kolla
community well.
Regards,
-steve
From: Jeffrey Zhang
Sent: Tuesday, July 24, 2018 8:48 PM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [kolla] ptl non cand
Kollians,
Many of you that know me well know my feelings towards participating as a core
reviewer in a project. Folks with the ability to +2/+W gerrit changes can
sometimes unintentionally harm a codebase if they are not consistently
reviewing and maintaining codebase context. I also believe
leadership, guidance and commitment to make
> kolla the great project it is now.
>
> Best luck on your new projects and board of directors.
>
> Regards
>
>
>
>
>
> 2018-08-07 16:28 GMT+02:00 Steven Dake (stdake)
> mailto:std...@cisco.com>
> <
Thierry,
Kolla likely belongs in the packaging recipes in the map. Kolla-Ansible
belongs in the lifecycle tools.
FWIW, I'm agree with Jean on the location of OpenStack-Ansible in the map.
This is a deployment tool, not really a set of recipes. I think the name
"openstack-ansible" as a proje
?Shyam,
Our policy, decided long ago, is that we would work with third party components
(such as plugins) for nova, cinder, neutron, horizon, etc that were proprietary
as long as the code that merges into Kolla specifically is ASL2.
What is your plugin for? if its for nova, cinder, neutron,
Chris,
Thanks for all the hard work you have put into this. FWIW I found value in
your reports, but perhaps because I am not involved in the daily activities of
the TC.
Cheers
-steve
On 10/2/18, 8:25 AM, "Chris Dent" wrote:
HTML: https://anticdent.org/tc-report-18-40.html
Swapnil,
Pleasure working with you - hope to see you around the computerverse.
Cheers
-steve
On 10/16/18, 5:34 AM, "ʂʍɒρƞįł Ҟưȴķɒʁʉɨ" wrote:
Dear OpenStackers,
For a few months now, I am not able to contribute to code or reviewing
Kolla and Requirements actively given my cur
Hey folks,
The quickstart guide was modified as a result of a lot of painful debugging
over the last cycle approximately a month ago. The only solution available to
us was to split the workflow into an operator workflow (working on stable
branches) and a developer workflow (working on master).
rg/developer/kolla/quickstart.html#installing-kolla-and-dependencies-for-development
On Tue, Sep 13, 2016 at 4:33 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Hey folks,
The quickstart guide was modified as a result of a lot of painful debugging
over the last cycle approximately a
Hey folks,
I removed several folks which appeared inactive for the Newton cycle from the
kolla-drivers team on launchpad. As a reminder, the reason we add people to
the kolla-drivers team is to do bug triage, move blueprint states around, and
distribute the process of handling the release. If
Forgot kolla tag. See message inside.
From: Steven Dake
Date: Tuesday, September 13, 2016 at 8:34 PM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Removal of folks from kolla-drivers
Hey folks,
I removed several folks which appeared inactive for the Newton cycle
m Hosakote (vhosakot)
wrote:
> Thanks a lot Steve for being a great PTL, leader and a mentor!
>
> Regards,
> Vikram Hosakote
> IRC: vhosakot
>
> From: "Steven Dake (stdake)"
> Reply-To: "OpenStack Development Mailing
Core Reviewers:
The facts:
We have roughly 250 bugs in rc2. Of those, I suspect over half can just be
closed out as dupes, fixed, wontfix, or the like.
The core reviewer team has had various discussions around splitting the
repository at various times but has not come to a concrete conclusion v
We have far exceeded a majority for choice C (which is my preferred choice as
well). So once 3.0.0 tags, it is all hands on deck to make the repo split
happen as well as get started on the osic documentation which we owe the OSIC
team. There were no other votes for other choices. While not ev
Christian,
While the vote was not unanimous, a strong majority of core reviewers were in
favor of our nomination with no veto in the voting period. I know the two core
reviewers that did not vote are travelling so perhaps they missed the vote.
Welcome to the core review team! I attempted to m
Release team,
At one point Doug had indicated all projects would automatically branch on
tagging of rc1. I notice in git no Kolla stable/newton branch exists. Fwiw
this is actually a good thing, because 33 patches have merged since rc1
relating to things that need to go into Newton, dramatical
Hui,
Change is what you will see as I am not running for PTL for Ocata.
Reference:
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103499.html
Regards
-steve
On 9/14/16, 4:32 PM, "Hui Kang" wrote:
+1 for Jeffrey Zhang
- Jeffrey is full time on Kolla
- St
Thierry,
Cool wfm.
Thanks
-steve
On 9/18/16, 7:08 AM, "Thierry Carrez" wrote:
Steven Dake (stdake) wrote:
> Release team,
>
> At one point Doug had indicated all projects would automatically branch
> on tagging of rc1. I notice in git no Koll
+1 for option 2, unless some good Fedora folk appear in Kolla to maintain it in
the future. In that case, we can always undo a deprecation within a cycle.
Note the deprecation policy states that we do not remove functionality for 1
cycle after having released it for stable deliverables. Even t
+1 for option #2 with same commentary as prior relating to fedora.
Regards
-steve
On 9/19/16, 10:44 AM, "Jeffrey Zhang" wrote:
Kolla core reviewer team,
Kolla supports multiple Linux distros now, including
* Ubuntu
* CentOS
* RHEL
* Fedora
* Debian
* O
I disagree. Oracle Linux is well implemented and very well maintained by Paul
Bourke and many other fine folks from Oracle. CentOS is derived from RHEL
(changing trademarks and marketing fluff, not code).
Regards
-steve
From: Dave Walker
Reply-To: "OpenStack Development Mailing List (not for
Fwiw Swapnil, I think having a solid fedora implementation would be fantastic
to help manage the transition to centos8 whenever that happens. At this point
nobody has stepped up to do the work. We can always revisit any policy or vote
in the future if the environment changes (i.e. you are free
Consider this a reversal of my vote for Debian deprecation.
Swapnil, thanks for bringing this fact to our attention. It was missing from
the original vote. I don’t know why I didn’t bring up Benedikt’s contributions
(which were substantial) just as Paul’s were substantial for Oracle Linux. I
ot;
Date: Tuesday, September 20, 2016 at 7:25 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [vote][kolla] deprecation for debian distro support
Option 2
2016-09-20 16:07 GMT+02:00 Steven Dake (stdake)
mailto:std...@cisco.co
Sam,
Can this meeting instead be held in the normal openstack-meeting-1 -> 4
channels? Having one-off meetings in #openstack-networking-cisco is totally
fine. Having standing team meetings there is atypical of OpenStack projects.
The main value of using the opentack-meeting-1-4 channels is t
: Tuesday, September 20, 2016 at 7:25 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [vote][kolla] deprecation for debian distro support
Option 2
2016-09-20 16:07 GMT+02:00 Steven Dake (stdake)
mailto:std...@cisco.com>>:
Con
On 9/20/16, 11:18 AM, "Haïkel" wrote:
2016-09-19 19:40 GMT+02:00 Jeffrey Zhang :
> Kolla core reviewer team,
>
> Kolla supports multiple Linux distros now, including
>
> * Ubuntu
> * CentOS
> * RHEL
> * Fedora
> * Debian
> * OracleLinux
>
> B
One note in this poll. Repo-split has already reached a consensus decision via
ml vote, and the activity around that will happen prior to summit, so it is
probably worth ignoring entirely.
Regards
-steve
On 9/21/16, 10:14 AM, "Michał Jastrzębski" wrote:
Hello,
Now, when we have
other policies (i.e. project maturity
tags) in OpenStack because of this decision, that information would be helpful
as well.
Thanks!
-steve
On 9/19/16, 6:51 AM, "Doug Hellmann" wrote:
Excerpts from Thierry Carrez's message of 2016-09-18 16:08:04 +0200:
> Steven D
em. Let see how priorities will
look like after couple days:)
Also, please vote!
On 21 September 2016 at 12:54, Swapnil Kulkarni wrote:
> On Wed, Sep 21, 2016 at 11:16 PM, Steven Dake (stdake)
wrote:
>> One note in this poll. Repo-split has already reached a co
Folks,
We want to be inviting to new contributors even if they are green. New
contributors reflect on OpenStack’s growth in a positive way. The fact that a
new-to-openstack contributor would make such and error doesn’t warrant such a
negative response even if it a hassle for the various PTLs
OpenStack summit planning team,
We have been planning summit for approximately 2-3 months here:
https://etherpad.openstack.org/p/kolla-O-summit-planning
We further codified this into a vote via civs:
http://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_8368e1e74f8a0049
As you can see from the prel
>> decision making process.
>>
>>
>>
>> Regards
>>
>> -steve
>>
>>
>>
>>
>>
>> From: Mathias Ewald
>> Reply-To: "OpenStack Development Mailing List (not
Flavio,
Apologies for delay in response – my backlog is large.
Forgive me if I parsed your message incorrectly. It came across to me as “How
do I blaze a trail for OpenStack on Kubernetes?”. That was asked of me
personally 3 years ago which led to the formation of the Kolla project inside
Re
Lu,
The kolla documentation specifically states Newton has a pin on ansible <
2.0.0.0
From: "lu.yao...@zte.com.cn"
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Thursday, September 22, 2016 at 5:41 AM
To: "openstack-dev@lists.openstack.org"
Subject: [openstac
Dims,
This isn’t any of my particular business except it could affect emerging
technology projects (which I find important to OpenStack’s future) negatively –
so I thought I’d chime in.
A lack of activity in a specs repo doesn’t mean much to me. For example, as
Kolla was an emerging project w
Bogdan,
I recognize English isn’t your first language, so forgive me if I have
mis-parsed your message. I think the question you are asking is “Can we have
cooperation to standardize on how best to do OpenStack on Kubernetes”. We
tried an analog of that with Mirantis around Mesos, and that re
ct: Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to
deploy OpenStack on k8s
On 22/09/16 20:55 +, Steven Dake (stdake) wrote:
Flavio,
Apologies for delay in response – my backlog is large.
Forgive me if I parsed your message incorrectly.
It's probably me failing to
Stack Development Mailing List (not for usage questions)"
Date: Friday, September 23, 2016 at 11:43 AM
To: "openstack-dev@lists.openstack.org"
Subject: Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to
deploy OpenStack on k8s
On 09/23/2016 01:04 PM, Steven Dake (s
4:23 AM, Davanum Srinivas
mailto:dava...@gmail.com>> wrote:
> Steven,
>
> Fair point.
>
> Thanks,
> Dims
>
> On Thu, Sep 22, 2016 at 11:04 PM, Steven Dake (stdake)
> mailto:std...@cisco.com>>
> wrote:
> > Dims,
> >
> > This isn’t any of my pa
Sam is correct here. This is the why behind the how ☺
Regards
-steve
From: Sam Yaple
Reply-To: "s...@yaple.net" , "OpenStack Development Mailing
List (not for usage questions)"
Date: Monday, September 26, 2016 at 7:43 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Sub
ack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] [kolla][fuel][tripleo] Reference architecture to
deploy OpenStack on k8s
On 23/09/16 17:47 +, Steven Dake (stdake) wrote:
Flavio,
Forgive the top post and lack of responding inline – I am dealing with
Dane,
I’ve heard Yolanda has done good work on making disk image builder build fedora
atomic properly consistently. This may work better than the current image
building tools available with atomic if you need to roll your own. Might try
pinging her on irc for advice if you get jammed up here.
e been stable. Dane and I have resolved the problems
with the load balancer at least for the LBaaS v1. For LBaaS v2, we need to
build a new image with Kubernetes 1.3 and we just got one built today.
Ton,
[nactive hide details for "Steven Dake (stdake)" ---09/27/2016 10:18:07
PM]"S
First off, apologies for missing most of the team meeting today. I have read
through the logs and saw a discussion about deprecating heka. We need to
ensure that we follow the deprecation policy. My understanding of the
deprecation policy is as follows (in a nutshell):
1. We must mail
re...@betacloud-solutions.de>> wrote:
> On 29 Sep 2016, at 06:26, Steven Dake (stdake)
> mailto:std...@cisco.com>> 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 p
My Peers,
I am self-nominating for serving you as your technical committee
representative.
I won't bore you with my professional accomplishments. If you want to
see such information to judge if I'm qualified for serving you on the
technical committee team, that information is available in my
fou
Also impacts Kolla (as in our gates are blocked). At present we are using the
proposed workaround until the pycparser 2.14 wheel and package are synced up.
Regards
-steve
From: Matt Riedemann
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
Date: Sunday, October 2, 2
Emilen,
You say "the previous *PTL* of an OpenStack installation automation project" as
if there were only one previous PTL :) There are many previous PTLs of
OpenStack automation projects. I feel the question was directed at me, so I'll
answer.
From:
e: Tuesday, October 4, 2016 at 4:46 AM
To: "OpenStack Development Mailing List (not for usage questions)"
Subject: Re: [openstack-dev] TC candidacy
On Tue, Oct 4, 2016 at 4:01 AM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Emilen,
You say "the previous *PTL* of an Op
Hey folks,
Several people have asked for archives of the OSIC work we did. Those files
can be found here:
https://drive.google.com/drive/folders/0B8q6xDPETSkHc05fR21qeElpc2M?usp=sharing
Regards,
-steve
__
OpenStack Develop
Doug,
We have already tagged rc1 long ago, but ack on rc2 (we are targeting 12th at
present) and ack on 20th for retag of final rc. We expect our rc2 to be final.
If there are critical bugs that make the release doa in some way (such as
upgrades, reconfigure etc), we will obviously have to ta
601 - 700 of 748 matches
Mail list logo
