Michal,
The vote was unanimous. Welcome to the Kolla Core Reviewer team. I have added
you to the appropriate gerrit group.
Regards
-steve
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mail
I am in favor of this work if it lands before Liberty.
Regards
-steve
On 9/30/15, 10:54 AM, "Jeff Peeler" wrote:
>The patch I just submitted[1] modifies the syntax of all.yml to use
>dictionaries, which changes how variables are referenced. The key
>point being in globals.yml, the overriding o
Hello Peers,
I would be pleased to serve on the Technical Committee with your vote. I have
a very relevant background to serving you in the Technical Committee in that I
have done the following during OpenStack development:
1. Led the development, incubation, and integration of Heat for t
Hi folks,
I am proposing Michal for core reviewer. Consider my proposal as a +1 vote.
Michal has done a fantastic job with rsyslog, has done a nice job overall
contributing to the project for the last cycle, and has really improved his
review quality and participation over the last several mo
Hongbin,
I believe the domain approach is the preferred approach for the solution long
term. It will require more R&D to execute then other options but also be
completely secure.
Regards
-steve
From: Hongbin Lu mailto:hongbin...@huawei.com>>
Reply-To: "OpenStack Development Mailing List (not
: +1
- harmw
Sam Yaple schreef op 2015-09-14 13:44:
On Mon, Sep 14, 2015 at 11:19 AM, Paul Bourke
mailto:paul.bou...@oracle.com>>
wrote:
On 13/09/15 18:34, Steven Dake (stdake) wrote:
Response inline.
From: Sam Yaple
mailto:sam...@yaple.net><mailto:sam...@yaple.net<mailto:sa
Response inline.
From: Sam Yaple mailto:sam...@yaple.net>>
Reply-To: "s...@yaple.net<mailto:s...@yaple.net>"
mailto:s...@yaple.net>>
Date: Sunday, September 13, 2015 at 1:35 AM
To: Steven Dake mailto:std...@cisco.com>>
Cc: "OpenStack Developmen
Response inline.
From: Sam Yaple mailto:sam...@yaple.net>>
Reply-To: "s...@yaple.net<mailto:s...@yaple.net>"
mailto:s...@yaple.net>>
Date: Saturday, September 12, 2015 at 11:34 PM
To: Steven Dake mailto:std...@cisco.com>>
Cc: "OpenStack Developmen
From: Sam Yaple mailto:sam...@yaple.net>>
Reply-To: "s...@yaple.net<mailto:s...@yaple.net>"
mailto:s...@yaple.net>>
Date: Saturday, September 12, 2015 at 11:01 PM
To: Steven Dake mailto:std...@cisco.com>>
Cc: "OpenStack Development Mailing List (not for
Hey folks,
Sam had asked a reasonable set of questions regarding a patchset:
https://review.openstack.org/#/c/222893/
The purpose of the patchset is to enable both RDO and RHOS as binary choices on
RHEL platforms. I suspect over time, from-source deployments have the
potential to become the no
My Peers,
Liberty for Kolla was fantastically successful! We held our first in person
mid-cycle and entered the Big Tent governance process. We successfully
released 3 milestone releases within 3 days of deadline with increasing
functionality. I believe our Kolla release of rc1 on September
Hi folks,
Kolla documentation is now published live to docs.openstack.org. Our
documentation still needs significant attention to be really high quality, but
what we have is a start. Every code change results in new published
documentation.
I’d like to invite folks interested in getting invo
The Kolla community is pleased to announce the release of the Kolla Liberty 3
milestone. This release fixes 90 bugs and implements 16 blueprints!
During Liberty 3, Kolla joined the big tent governance! Our project can be
found here:
http://governance.openstack.org/reference/projects/index.h
Hi folks,
Our 22:00 UTC meeting is very poorly attended resulting in the need to cancel
the 22:00 meeting several times over the last month. Also our core reviewer
team has communicated a desire to have the 16:00 UTC meeting 30 minutes later
to better fit in with EMEA workdays. Given that, I’
Kai,
This sounds like a good solution. The actual VM doesn’t need to be super large
given our present tests.
Regards
-steve
From: Kai Qiang Wu mailto:wk...@cn.ibm.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: F
On 8/13/15, 6:13 AM, "Jeremy Stanley" wrote:
>On 2015-08-13 19:38:07 +0800 (+0800), Kai Qiang Wu wrote:
>> I did talked to infra, which I think it is resource issue, But
>> they thought it is nova issue,
>[...]
>
>No, I said the error was being raised by Nova, so was not an error
>coming _from_
On 8/13/15, 4:58 PM, "Clark Boylan" wrote:
>On Thu, Aug 13, 2015, at 03:13 AM, Tom Cammann wrote:
>> Hi Team,
>>
>> Wanted to let you know why we are having consistent functional test
>> failures in the gate.
>>
>> This is being caused by Nova returning "No valid host" to heat:
>>
>> 2015-08
ewer team
On Fri, Aug 14, 2015 at 3:29 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Hi folks,
Swapnil has done a bunch of great technical work, participates heavily in IRC,
and has contributed enormously to the implementation of Kolla. I’d like to see
more reviews from
On 8/16/15, 11:58 AM, "Julien Danjou" wrote:
>On Sun, Aug 16 2015, Steven Dake (stdake) wrote:
>
>Hi Steven,
>
>> In Kolla we are packaging gnocchi in a container. It has a dependency on
>> pg_config as part of the build system. I¹d like to know from a gnoc
Hi,
In Kolla we are packaging gnocchi in a container. It has a dependency on
pg_config as part of the build system. I’d like to know from a gnocchi expert
if this build time dependency relies on postgresql configured in some way, or
does it just look for standard library paths?
The reason is
At the midcycle, we had only 1 session on upgrade, and we didn’t come to any
clear consensus on how it should be handled. I took a stab at writing what I
think are the requirements for upgrade in this blueprint:
https://blueprints.launchpad.net/kolla/+spec/upgrade-strategy
The blueprint can be
Hi folks,
Swapnil has done a bunch of great technical work, participates heavily in IRC,
and has contributed enormously to the implementation of Kolla. I’d like to see
more reviews from Swapnil, but he has committed to doing more reviews and
already has gone from something like 0 reviews to 90
Hi,
There has been a lot of debate in the Kolla community about how to handle data
containers but it has happened all over the place (irc, various reviews, etc).
I’d like to have one record of the various tribal knowledge on this subject.
The latest proposal is to create one data container whi
From: Akash Gangil mailto:akashg1...@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Wednesday, August 12, 2015 at 1:37 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-de
Hi,
Alicja has been heading up this blueprint:
https://blueprints.launchpad.net/kolla/+spec/dockerfile-template
Other projects like TripleO and downstreams depend on this change to happen as
soon as possible. It is a mountain of work – too much for one person to finish
in a sprint. I’d like t
Hi folks,
We had about 40 blueprints for Kolla marked for L3. Our community can
typically process about 20-25 blueprints in a 1 month period. As a result, I
pushed a bunch of blueprints to Mitaka, and got our blueprint count down to
about 24 blueprints. The Essential/High blueprints are what
Hey folks,
I just wanted to give a heads up to fellow new members to the big tent (and the
TC) that don’t have the correct repo listed today in the projects.yaml file in
the governance repo that according to fungi [1] those projects contributors
will not receive ATC passes. According to clark
On 8/7/15, 8:08 AM, "Dan Prince" wrote:
>On Fri, 2015-08-07 at 14:21 +, Steven Dake (stdake) wrote:
>> James and Dan,
>>
>> During the ansible-multi spec process that James Slagle reviewed,
>> there was a serious commitment by the Kolla core team t
James and Dan,
During the ansible-multi spec process that James Slagle reviewed, there was a
serious commitment by the Kolla core team to maintain config-internal, pretty
much for the tripleo use case. We didn’t want to leave our partner projects in
the lurch and at the time Ryan/Ian’s impleme
Apologies for top post, but I just wanted to point out in the
config-external examples I am aware /opt/kolla is the wrong directory to
configure from (it should be /var/lib/kolla or something similar) and we
will fix this during l3.
Regards
-steve
On 8/5/15, 6:53 PM, "Steven Dake (s
On 8/5/15, 11:33 AM, "Ryan Hallisey" wrote:
>Tagging kolla so the kolla community also sees it.
>Pardon the top posting.
>
>-Ryan
Ryan,
Super appreciated I may have missed this in my deluge of mail - please
keep doing that - or if it involves kolla please tag as kolla as I read
that folder oft
Hi folks,
the Kolla community is pleased to announce the release of the Kolla Liberty 2
milestone. This release fixes 77 bugs and implements 18 blueprints!
Our community developed the following notable features:
* Source building of containers
* Ansible Deployment for core services
* High
On 7/30/15, 4:26 PM, "Doug Hellmann" wrote:
>Excerpts from Steven Dake (stdake)'s message of 2015-07-30 15:27:15 +:
>>
>> On 7/29/15, 1:23 PM, "Doug Hellmann" wrote:
>>
>> >Excerpts from Steven Dake (stdake)'s message
Folks,
I will be at the Magnum midcycle August 5th and August 6th in SJC so I will be
unavailable to run the IRC meeting during this time. Ryan Hallisey has
graciously agreed to chair the meeting in my absence. Bmace has also offered
to act as a backup in the case that both I or Ryan are unav
Paul and all,
Thanks for the fantastic work leading this bueprint. If we can use this
same approach for new Ansible services, I think we would end up with a
development team that is trained in Ansible the same way the dev team is
trained in creating build from source code.
That etherpad is here:
On 7/29/15, 1:23 PM, "Doug Hellmann" wrote:
>Excerpts from Steven Dake (stdake)'s message of 2015-07-29 20:07:26 +:
>> Doug Hellman of the TC suggested we change the mission statement of
>>Kolla to be a little less specific. The new mission statement I
>&g
Doug Hellman of the TC suggested we change the mission statement of Kolla to be
a little less specific. The new mission statement I submitted in the review is
here Is basically cutting off the last part of the mission statement sentence:
https://review.openstack.org/#/c/206789/
If your a Kolla
TCers,
The Kolla development community jointly produced our commit message and commit
contents via Etherpad at the first day of our Midcycle this week during a 1
hour live editing session. The Kolla project humbly requests application to
the big tent. [1]
Thanks!
-steve
[1] https://review.op
Today at 10:00 AM PST our Kola-Palooza Midcycle event begins! Please join us
remotely if you are not able to make it on site if you have an interest in
deploying OpenStack using Ansible within Docker container technology. If you
are attending in person, please appear before 9:30 so we can get
Hi,
We are executing the Kolla midcycle Wednedsay July 28th and July 29th from 10AM
until 5PM PST. This conflicts with our normally scheduled IRC team meeting so
we are canceling the IRC team meeting for this coming week only. We do have
remote access available via WebEx for people to attend
Gal,
I’m not clear exactly what you plan to do with regards to building docker
containers for Neutron, but the Kolla project has developed both linuxbridge
and ovs agents as well as a complete running Neutron system inside container
technology. We can launch it AIO with docker-compose, or alte
Fellow Kolla developers,
Daneyon has been instrumental in getting Kolla rolling and keeping our project
alive. He even found me a new job that would pay my mortgage and Panamera
payment so I could continue performing as PTL for Kolla and get Magnum off the
ground. But Daneyon has conferred wi
From: Adrian Otto mailto:adrian.o...@rackspace.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Thursday, July 16, 2015 at 12:35 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-
Madhuri,
Alee is in EST timezone (gmt-5 IIRC). Alee will help you get barbican rolling.
Can you two folks set up a time to chat on irc on Monday or tuesday?
Thanks
-steve
__
OpenStack Development Mailing List (not for us
ev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla] image bloat
On 17 Jul 2015 12:30, "Steven Dake (stdake)"
mailto:std...@cisco.com>> wrote:
>
> Hey folks,
>
>
> The bloat on the from-source comes from the C toolchain. The bloat on the
>
I likely will not be making the team meetings the following week as I’m taking
a week of PTO.
Regards
-steve
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.
Hey folks,
Playing with from source builds and comparing them to from binary builds, I
noticed our binary images are much larger:
>From source:
kollaglue/centos-source-magnum-api latest
f822f446c882About a minute ago 510.8 MB
kollaglue/centos-sourc
estions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [magnum] The way magnum-conductor communicates
with k8s master
On Jul 13, 2015, at 8:40 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
From: "OTSUKA, Motohiro" mailto:yu
day, July 14, 2015 at 8:56 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla] Proposal for Paul Bourke for Kolla Core
+1
From: "Steven Dake (stdake)" mailto:std...@cisco.co
From: "OTSUKA, Motohiro" mailto:yuany...@oeilvert.org>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, July 13, 2015 at 8:11 PM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-
Hey folks,
I am proposing Paul Bourke for the Kolla core team. He did a fantastic job
getting Kolla into shape to support multiple distros and from source/from
binary installation. His statistics are fantastic including both code and
reviews. His reviews are not only voluminous, but consiste
+1 welcome aboard Tom!
Regards
-steve
On 7/9/15, 7:20 PM, "Adrian Otto" wrote:
>Team,
>
>Tom Cammann (tcammann) has become a valued Magnum contributor, and
>consistent reviewer helping us to shape the direction and quality of our
>new contributions. I nominate Tom to join the magnum-core team
pstream goodness.
I hope this helps and if you guys are interested in working on any these things
we'd love help in a collaborative effort.
--
Kevin Carter
IRC: cloudnull
[0]
https://github.com/stackforge/os-ansible-deployment/tree/master/playbooks/library
[1] https://review.ope
https://review.openstack.org/199463
Sam Yaple
864-901-0012
On Tue, Jul 7, 2015 at 9:21 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
On 7/7/15, 2:05 PM, "Robert Collins"
mailto:robe...@robertcollins.net>> wrote:
>On 4 July 2015 at 06:53, Steven Dake (stda
On 7/7/15, 2:05 PM, "Robert Collins" wrote:
>On 4 July 2015 at 06:53, Steven Dake (stdake) wrote:
>> Kolla Devs as well as the Technical Committee,
>>
>> I wanted to get the TC¹s thoughts on this plan of action as we intend to
>> apply for big ten
Tom,
Just to be clear on motive, it had nothing to do with reuse by others.
Lars had a repo he maintains. Magnum had a repo it maintained. We wanted one
source of truth. The deal was we would merge all the things into
heat-coe-templates, delete larsks/heat-kubernetes and delete the magnum
t
Please note a correction, the dinner is the night of July 28th at 7pm, not July
27th.
My apologies.
Regards
-steve
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org&
it bundled libraries.
Regards
-steve
Thanks,
Kevin
From: Steven Dake (stdake)
Sent: Friday, July 03, 2015 11:53:00 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Greg DeKoenigsberg
Subject: [openstack-dev] [kolla][tc] Plans for using Pre-2.0 Ansible modu
Kolla Devs as well as the Technical Committee,
I wanted to get the TC’s thoughts on this plan of action as we intend to apply
for big tent once our Ansible code has completed implementation. If the
approach outlined in this email seems like a blocker and we should just start
with #4 instead, i
Hey community folks!
The Kolla team is having a mid-cycle event in San Jose, CA. Coffee is provided
throughout the day (I believe, but not certain on this point), and lunch, soda,
water are provided at lunch time. An RSVP dinner is provided the night of July
27th at 7 PM so food costs should
el: 86-10-82451647
Address: Building 28(Ring Building), ZhongGuanCun Software Park,
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
Follow your heart. You are miracle!
[Inactive hide deta
rward to
>play with Kolla with these new bits sometime in the near future.
Kevin,
Thanks!
The development team did a fantastic job focusing in Liberty 1 - 14
blueprints - pretty amazing amount of work in a short 5 week cycle. Plan
to see same level of focus to meet our Liberty-2 milestone go
ment that OSAD could theoretically suffer.
This theoretical issue makes the deployment non-repeatable. Hope our 10
day eval analysis helps improve OSAD.
Regards
-steve
>
>>
>>On Tue, Jun 30, 2015 at 2:28 PM, Ian Cordasco
>> wrote:
>>
>>
>>
>>On 6/29
Apologies for double post – left off [magnum] prior by error.
Ton Ngo of IBM Silicon Valley Research has graciously offered to host the 2 day
Magnum midcycle event at IBM’s facilities.
The sessions will run from 9AM – 5PM and catered lunch and refreshments
(soda/water) will be provided.
The mi
On 7/1/15, 1:22 AM, "Thierry Carrez" wrote:
>Steven Dake (stdake) wrote:
>> The dates for the Kolla midcycle have been confirmed for July 28th and
>> July 29th. Coffee/Tea will be provided in the mornings, and catered
>> lunch will be provided with soda or wat
Hey folks,
The dates for the Kolla midcycle have been confirmed for July 28th and July
29th. Coffee/Tea will be provided in the mornings, and catered lunch will be
provided with soda or water both days. A dinner will be held July 28th. Since
budget is really tight for most folks because of a
Ton Ngo of IBM Silicon Valley Research has graciously offered to host the 2 day
Magnum midcycle event at IBM’s facilities.
The sessions will run from 9AM – 5PM and catered lunch and refreshments
(soda/water) will be provided.
The mid-cycle will be a standard mid-cycle with a 1 hour introduction
The Kolla community is pleased to announce the release of the Kolla Liberty 1
milestone. This release fixes 56 bugs and implements 14 blueprints!
Of significant note during this milestone, we defined our Mission statement for
our project which is:
Kolla provides production-ready containers and
Re python 3 sounds fantastic. Re changing around python client, lets hold off
on that until we have a concrete plan for getting a python client in an
operational state in the proper repository.
Regards
-steve
From: Tom Cammann mailto:tom.camm...@hp.com>>
Reply-To: "OpenStack Development Maili
Hey Kolla cats (and Magnum cats),
I have a tooth infection, which isn’t super serious, but the pain levels are
about a 8 out of 10 on the holy fuck scale. As a result, my work is a bit
impaired. I may be a bit MIA in the next week while I sort out the medical
problem and get my tooth into a m
Hey TCers,
In this thread, the Magnum community made a commitment to tackle horizon
support for our software:
http://lists.openstack.org/pipermail/openstack-dev/2015-June/066701.html
We would like to add magnum-ui to the list of repos in the openstack namespace.
The governance review change:
h
Clint,
Answering Clint’s question, yes there is a reason all nodes must expose a
floating IP address.
In a Kubernetes cluster, each minion has a port address space. When an
external service contacts the floating IP’s port, the request is routed over
the internal network to the correct contain
Its unanimous! Welcome to the core reviewer team Harm!
Regards
-steve
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, June 14, 2015 at 1
Reminder voting ends June 17th.
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, June 9, 2015 at 12:02 PM
To: "OpenStack Development Mailing Li
Hey folks,
I am proposing Harm Waites for the Kolla core team. He did a fantastic job
implementing Designate in a container[1] which I’m sure was incredibly
difficult and never gave up even though there were 13 separate patch reviews :)
Beyond Harm’s code contributions, he is responsible for
or a second LP project at all.
Adrian
Original message
From: "Steven Dake (stdake)" mailto:std...@cisco.com>>
Date: 06/12/2015 7:41 AM (GMT-08:00)
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subjec
us to
arrive at a well reasoned decision about how to approach this.
On Jun 4, 2015, at 10:58 AM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Hey folks,
I think it is critical for self-service needs that we have a Horizon dashboard
to represent Magnum. I know the entire Magnum t
u to make this into something we are all proud of.
Adrian
PS: Special thanks to sdake for initiating this conversation, and helping us to
arrive at a well reasoned decision about how to approach this.
On Jun 4, 2015, at 10:58 AM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Hey fo
The kolla-drivers team in launchpad is a restricted team because people can
damage the issue tracker and cause a bunch of work on my end to fix. That
said, I’m going to open up the kolla-drivers launchpad team to a wider group of
any individual involved in Kolla. This is different from the cor
r usage questions)"
>>
>> Sent: Tuesday, June 9, 2015 2:19:00 PM
>> Subject: Re: [openstack-dev] [kolla] Proposal for changing 1600UTC
>>meeting to 1700 UTC
>>
>> On Mon, Jun 08, 2015 at 05:15:54PM +, Steven Dake (stdake) wrote:
>>> Folks,
>>
This is an open invitation to Operators that have an interest in contributing
to the Kolla design around deployment to participate in a 2 day design focused
midcycle summit. The hours will run from 10:00 AM to 5:00 PM PST and the
location will be in San Jose, CA in the US. The two days will b
e.rst
Adapt it for magnum (I have not contributed a spec template of our own yet.
TODO.)
Contribute it here:
http://git.openstack.org/cgit/openstack/magnum/tree/specs
Thanks,
Adrian
On Jun 4, 2015, at 12:58 PM, Steven Dake (stdake)
mailto:std...@cisco.com>> wrote:
Hey folks,
I think it is cr
Folks,
Several people have messaged me from EMEA timezones that 1600UTC fits right
into the middle of their family life (ferrying kids from school and what-not)
and 1700UTC while not perfect, would be a better fit time-wise.
For all people that intend to attend the 1600 UTC, could I get your fe
Hi folks,
I will be presenting Magnum at the Cisco Live US event in San Diego and demoing
both Kolla and Magnum with Daneyon Hansen at CLUS in demo pods in the devnet
section. If you will be at Cisco Live, feel free to drop by the demo pods to
see demos of both Kolla and Magnum or attend our 3
On 6/1/15, 7:38 AM, "Jeff Peeler" wrote:
>On Sat, May 30, 2015 at 03:00:04AM +, Steven Dake (stdake) wrote:
>>Hey Folks,
>>
>>I noticed the Kolla functional gate is failing sporadically.
>>
>>It seems that sometimes an image doesn¹t build.
>&
Kennan,
Welcome to the magnum-core team!
Regards
-steve
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Saturday, May 30, 2015 at 10:56 PM
To: "Op
agnum][horizon] Making a dashboard for Magnum -
need a vote from the core team
Could we have a new group magnum-ui-core and include magnum-core as a subgroup,
like the heat-coe-tempalte-core group.
Thanks,
Hongbin
From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: June-04-15 1:58 PM
To: O
Kolla devs,
First off, the Kolla development team did a fantastic job of getting their
various thoughts into the Kolla Manfesto etherpad. It was really something
magical to watch and participate in and was a new experience for me :).
I have detected a pattern between different missions that so
My vote is +1 for a unified core team for all Magnum development which in the
future will include the magnum-ui repo, the python-magnumclient repo, the
magnum repo, and the python-k8sclient repo.
Regards
-steve
From: Steven Dake mailto:std...@cisco.com>>
Reply-To: "OpenStack
Hey folks,
I think it is critical for self-service needs that we have a Horizon dashboard
to represent Magnum. I know the entire Magnum team has no experience in UI
development, but I have found atleast one volunteer Bradley Jones to tackle the
work.
I am looking for more volunteers to tackle
I can see both points of view. Principle of least surprise applies here. A
list of bays without names would be surprising for a tenant imo :) I don’t
particularly have a strong opinion, but my inclination is to lean towards
non-unique names as a requirement for creating bays.
Again I am not
Kennan,
Agree on no requirement for unique name.
Regards
-steve
From: Kai Qiang Wu mailto:wk...@cn.ibm.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Monday, June 1, 2015 at 6:11 PM
To: "OpenStack Development Maili
I have this same problem with devstack master. I’m not sure what it is other
then it involves the requirements repo possibly not containing
oslo.versionedobjects on my system. Dims has a suggestion to do something
about it, but I didn’t get back to it. Try joining channel
#openstack-containe
Hey folks,
Since this is our first odd week meeting and the time is different from our
original time, I’d like to remind folks interested in Kolla to attend our IRC
meeting in openstack-meeting-4 at 2200 UTC on Wednesday, June 3rd.
Agenda is here:
https://wiki.openstack.org/wiki/Meetings/Kolla#
Jay 513
+1 on mandatory name requirement.
From: Jay Lau mailto:jay.lau@gmail.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Sunday, May 31, 2015 at 2:38 PM
To: OpenStack Development Mailing List
mailto:openstac
Hi core team,
Kennan (Kai Qiang Wu’s nickname) has really done a nice job in Magnum
contributions. I would like to propose Kennan for the core reviewer team. I
don’t think we necessarily need more core reviewers on Magnum, but Kennan has
demonstrated a big commitment to Magnum and is a welcom
If you are backporting heat templates for Kubernetes, please test each commit
with a bay create followed by a creation of a redis application. For an
example redis application, check out my demo at:
https://github.com/stackforge/kolla/tree/master/demos/magnum
Master is currently broken, I assu
Hey Folks,
I noticed the Kolla functional gate is failing sporadically.
It seems that sometimes an image doesn’t build.
http://logs.openstack.org/75/186475/1/check/check-kolla-functional-f21/8f23913/console.html
One thing that looks off there is barbican is not building a —release image
(I.e.
lists.openstack.org>>
Date: Thursday, May 28, 2015 at 11:50 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [kolla] Add core approver Sam Yaple
+1
From: "Steven Dake (st
On 5/26/15, 2:16 PM, "jpee...@redhat.com" wrote:
>(Trying to summarize discussions from earlier on IRC)
>
>On Mon, May 25, 2015 at 06:54:43PM +, Steven Dake (stdake) wrote:
>>Hey fellow Kolla devs,
>>
>>With Sam¹s recent change to add build from
601 - 700 of 875 matches
Mail list logo
