On 2/4/15, 10:24 AM, Daniel P. Berrange berra...@redhat.com wrote:
On Wed, Feb 04, 2015 at 09:10:06AM -0800, James E. Blair wrote:
Thierry Carrez thie...@openstack.org writes:
You make a good point when you mention traditional distro here. I
would argue that containers are slightly
From: Eric Windisch e...@windisch.usmailto:e...@windisch.us
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Saturday, February 7, 2015 at 10:09 AM
To: OpenStack Development Mailing List (not
taking anything away from this fine and sensible direction, where
_would_ be a good place to discuss more radical container-based deployments?
(I'm fine if the answer is use ad-hoc communication channels for now)
On Fri Feb 06 2015 at 7:24:12 AM Steven Dake (stdake)
std...@cisco.commailto:std
Hey folks,
I wanted to provide a brief update on where we are headed with Kolla.
Initially Kolla began as a POC to show that containers could be used to deploy
OpenStack with the long term plan of integrating that functionality into
TripleO. That goal has not changed.
The tripleo community
Hey folks,
A few weeks ago I sent the mailing list a broad outline [1] for our new
approach to deploying OpenStack using container technology. Between then and
now, the Kolla core team has approved a new technical direction [2].
In summary, our new approach is to use fig [3] to provide
That is 3 votes. Welcome to kolla-core Andre!
Regards
-steve
On 2/17/15, 10:59 AM, Jeff Peeler jpee...@redhat.com wrote:
On Tue, Feb 17, 2015 at 03:07:31AM +, Steven Dake (stdake) wrote:
Hi folks,
I¹d am proposing Andre Martin to join the kolla-core team. Andre has
been providing mostly
Hey folks,
I’d like to invite the broader OpenStack community to participate in developing
milestone #3 of Kolla – a Project to Containerize the deployment of OpenStack.
This is a major refactoring of Kolla to make it viable for use by projects such
as TripleO or Fuel.
We have an aggressive
Hi folks,
I’d am proposing Andre Martin to join the kolla-core team. Andre has been
providing mostly code implementation, but as he contributes heavily, has
indicated he will get more involved in our peer reviewing process.
He has contributed 30% of the commits for the Kilo development cycle,
The initial magnum core team was founded at a meeting where several people
committed to being active in reviews and writing code for Magnum. Nearly all
of the folks that made that initial commitment have been active in IRC, on the
mailing lists, or participating in code reviews or code
+1 \o/ yay
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, February 16, 2015 at 8:07 PM
To: OpenStack Development Mailing List
-1
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, February 16, 2015 at 8:20 PM
To: OpenStack Development Mailing List (not for
.
But yup, I understand your point.
Thanks!
2015-02-10 12:32 GMT+08:00 Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com:
From: Joe Gordon joe.gord...@gmail.commailto:joe.gord...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev
discussions here
https://blueprints.launchpad.net/magnum/+spec/magnum-scheduler-for-docker
Thanks!
2015-02-09 16:22 GMT+08:00 Sylvain Bauza
sba...@redhat.commailto:sba...@redhat.com:
Hi Magnum team,
Le 07/02/2015 19:24, Steven Dake (stdake) a écrit :
From: Eric Windisch e...@windisch.usmailto:e
Dan,
One of the technical guys here at Cisco asked me a really good technical
question about libvirt upgrades in containers which I was unable to answer. My
suspicion is the linux VM system just sorts it out, but I wanted to get your
input.
Assume libvirt version 1 is running in a container.
On 2/9/15, 3:02 AM, Thierry Carrez thie...@openstack.org wrote:
Adrian Otto wrote:
[...]
We have multiple options for solving this challenge. Here are a few:
1) Cherry pick scheduler code from Nova, which already has a working a
filter scheduler design.
2) Integrate swarmd to leverage its
Hongbin Lars,
I spoke with Steve Hardy from Heat, who has been deep into improving resource
groups. He indicated the problem Hongbin saw, where the resource group kills
all Vms and then restarts them on a stack update to the count in a resource
group is fixed in master and stable/juno.
See
(not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Scheduling for Magnum
On Mon, Feb 9, 2015 at 6:00 AM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
On 2/9/15, 3:02 AM, Thierry Carrez
://launchpad.net/kolla
We use the openstack-dev mailing list with the tag [kolla]
Regards,
-steve
On 05/02/15 17:25, Steven Dake (stdake) wrote:
Hey folks,
I wanted to provide a brief update on where we are headed with Kolla.
Initially Kolla began as a POC to show that containers could be used
FenghuaFeng,
Ccing openstack-dev
1. Kubernetes doesn’t offer a control or integration point. We have that now
with docker-compose.
2. Kubernetes doesn’t offer super privileged containers. We need that in order
to operate an OpenStack environment.
Regards
-steve
From: 449171342
Hey folks,
I have manually updated the Fedora 21 Atomic image via rpm-ostree upgrade.
This image includes kubernetes 0.11 which some people have said is required to
use kubectl with current Magnum master. I don’t have time for the next week to
heavily test, but if someone could run this
On 3/10/15, 12:22 AM, Bohai (ricky) bo...@huawei.com wrote:
Hi, stackers
I try to use the Kolla Images and pull them down from docker hub.
I found the size of the image is bigger than what I thought(for example,
the images of docker conductor service is about 1.4GB).
Is it possible to get a
I am running for PTL for the Kolla project. I have been executing in an
unofficial PTL capacity for the project for the Kilo cycle, but I feel it is
important for our community to have an elected PTL and have asked Angus
Salkeld, who has no outcome in the election, to officiate the election
Hello,
The Kolla community is pleased to announce the release of Kilo #3 of the Kolla
project. It is available for immediate download from:
https://github.com/stackforge/kolla/archive/k3.tar.gz
This version removes Kubernetes entirely as a development environment. We
found we needed
-steve
Cheers,
Chmouel
On Sun, Mar 22, 2015 at 4:50 PM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
FenghuaFeng,
Ccing openstack-dev
1. Kubernetes doesn’t offer a control or integration point. We have that now
with docker-compose.
2. Kubernetes doesn’t offer super
in the community have discussed creating a
deployment tool as well to deploy Kolla containers if there is little community
uptake on our work.
Regards
-steve
---原始邮件---
发件人: Steven Dake (stdake)std...@cisco.commailto:std...@cisco.com
发送时间: 2015年03月22日 23:50:17
收件人: 449171342449171...@qq.commailto:449171
Michal,
All great questions. I have copied the OpenStack mailing list since these
technical questions can benefit everyone.
From: Stachowski, Michal
michal.stachow...@intel.commailto:michal.stachow...@intel.com
Date: Monday, March 30, 2015 at 6:21 AM
To: Steven Dake
: Questions about kolla
On Mon, Mar 30, 2015 at 3:42 PM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
We plan to dockerize any service needed to deploy OpenStack. We haven’t
decided if that includes ceph, since ceph may already be dockerized by someone
else. But it does
Hey folks,
We got a lot of complaints for folks trying to run Kolla on Ubuntu 14.04 with
3.13 kernel. Most of the problems were related to kernel bugs or docker bugs.
We have worked around them, and now Kolla launches like a champ for me on 14.04.
Regards
-steve
On 4/1/15, 5:12 AM, Monty Taylor mord...@inaugust.com wrote:
On 03/31/2015 03:30 PM, Steven Dake (stdake) wrote:
Hey folks,
One of our community members submitted a review to add optional Ansible
support to deploy OpenStack using Ansible and the containers within
Kolla. Our main objective
On 4/1/15, 5:32 AM, Chmouel Boudjnah chmo...@chmouel.com wrote:
On 03/31/2015 03:30 PM, Steven Dake (stdake) wrote:
Hey folks,
One of our community members submitted a review to add optional Ansible
support to deploy OpenStack using Ansible and the containers within
Kolla.
Our main
Hey folks,
One of our community members submitted a review to add optional Ansible support
to deploy OpenStack using Ansible and the containers within Kolla. Our main
objective remains: for third party deployment tools to use Kolla as a building
block for container content and management.
, 2015, at 8:33 AM, Steven Dake (stdake) std...@cisco.com
wrote:
Hey folks,
I have manually updated the Fedora 21 Atomic image via rpm-ostree
upgrade. This image includes kubernetes 0.11 which some people have
said is required to use kubectl with current Magnum master. I don¹t
have time
From: Madhuri Rai madhuri.ra...@gmail.commailto:madhuri.ra...@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, March 23, 2015 at 1:53 AM
To:
issue with submitting changes to swagger is swagger is written in
erlang – groan.
Regards,
-steve
Thanks,
Hongbin
On Mon, Mar 23, 2015 at 10:11 AM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
From: Madhuri Rai madhuri.ra...@gmail.commailto:madhuri.ra...@gmail.com
Reply
For those folks that weren’t aware of the scheduled outage today in gerrit to
handle the renames, the magnum repository has moved to the openstack namespace
\o/ :)
I pull from
git pull http://github.com/openstack/magnum
But you can also pull from the openstack git server
Regards
-steve
, at 8:33 AM, Steven Dake (stdake) std...@cisco.com
wrote:
Hey folks,
I have manually updated the Fedora 21 Atomic image via rpm-ostree
upgrade. This image includes kubernetes 0.11 which some people have
said is required to use kubectl with current Magnum master. I don¹t
have time for the next
Madhuri,
Copying openstack-dev mailing list – hope you don’t mind.
Folks, we are talking about the images here:
https://fedorapeople.org/groups/magnum/
Specifically the images with “15” in the filename.
Feel free to test these images as your leisure.
From: Madhuri Rai
On 4/17/15, 10:25 AM, Matthew Miller mat...@mattdm.org wrote:
On Fri, Apr 17, 2015 at 04:29:36PM +, Steven Dake (stdake) wrote:
Fedora 21 only has kubernetes 0.13 although I see in koji k8s 0.15
has been built for f23. Is there any possibility of getting
kubernetes 0.15 in fedora atomic
Hi folks,
I have spent the last couple of days trying to bring some sanity to the image
building process for Magnum.
I have found a tool which the Atomic upstream produces which allows a simple
repeatable building process for Fedora Atomic images using any upstream repos
of our choosing.
I
On 4/26/15, 11:21 AM, Gregory Haynes g...@greghaynes.net wrote:
Excerpts from Steven Dake (stdake)'s message of 2015-04-23 23:27:00 +:
Hi folks,
I have spent the last couple of days trying to bring some sanity to the
image building process for Magnum.
I have found a tool which
...@gmail.commailto:madhuri.ra...@gmail.com wrote:
Hi Steve,
Thank you for working on this.
It will be really good for us to remove dependency on external projects.
Regards,
Madhuri
On Fri, Apr 24, 2015 at 8:27 AM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
Hi folks,
I have spent
From: FangFenghua fang_feng...@hotmail.commailto:fang_feng...@hotmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, April 28, 2015 at 7:02 AM
To:
Hi folks,
I would like to nominate Madhuri Kumari to the core team for Magnum. Please
remember a +1 vote indicates your acceptance. A –1 vote acts as a complete
veto.
Why Madhuri for core?
1. She participates on IRC heavily
2. She has been heavily involved in a really difficult
Hi,
We would like to expand the core team and developers that can participate. Our
current 2000 UTC meeting time is not ideal for APAC participants.
I am considering moving the meeting to alternating schedules of 1600 UTC and
200 UTC. If you would like to attend the Kolla IRC meeting please
I have closed the doodle poll for our new meeting times. We will be meeting in
#openstack-meeting-3 (yes there is that much contention for our time slots –
must be a reason ;).
The times are:
Weekly Wednesday 1600 UTC (even weeks)
Weekly Wednesday 2200 UTC (odd weeks)
To determine if it is an
On 5/10/15, 5:06 PM, Tony Breeds t...@bakeyournoodle.com wrote:
On Sun, May 10, 2015 at 08:49:11PM +, Steven Dake (stdake) wrote:
I have closed the doodle poll for our new meeting times. We will be
meeting
in #openstack-meeting-3 (yes there is that much contention for our time
slots
The Kolla IRC team meeting at 2200 UTC is cancelled because nearly all the team
will be at OpenStack Developer Summit.
See ya there =)
Regards
-steve
__
OpenStack Development Mailing List (not for usage questions)
Kevin,
This is a great idea that would make a solid extension to the software.
If I read the wiki page correctly, the real goal is for operators and
tenants to be able to be notified via querying the ReST API so they could
write their own email/pager-duty app.
Regards
-steve
On 5/12/15, 11:16
Hey Stackers,
The Kolla community is pleased to announce the release of Kolla 2015.1.0. This
release includes the following features:
Kolla includes a complete container build system and all in one deployment tool.
We also have implemented completely functional containers for:
* Glance
From: David Kranz dkr...@redhat.commailto:dkr...@redhat.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Wednesday, May 13, 2015 at 6:27 AM
To: OpenStack Development Mailing List (not for
On 5/12/15, 1:28 PM, Julien Danjou jul...@danjou.info wrote:
On Tue, May 12 2015, Steven Dake (stdake) wrote:
This is a great idea that would make a solid extension to the software.
If I read the wiki page correctly, the real goal is for operators and
tenants to be able to be notified via
On 4/2/15, 9:51 AM, Russell Bryant rbry...@redhat.com wrote:
On 04/02/2015 12:36 PM, Adrian Otto wrote:
What to expect in the Liberty release cycle:
...
* Overlay networking
...
This is totally unrelated to your PTL email, but on this point, I'd be
curious what the Magnum team thinks of
On 4/1/15, 10:52 AM, Steven Hardy sha...@redhat.com wrote:
Hi all,
I've had various discussions about $subject, which have been re-started
lately due to some excellent work going on in the Heat community (Rabi
Mishra's work integrating SoftwareDeployments with various container
launching tools
@lists.openstack.org
Subject: Re: [openstack-dev] [magnum][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
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
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 std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack
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
Kennan,
Welcome to the magnum-core team!
Regards
-steve
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Saturday, May 30, 2015 at
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
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
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
-specs/tree/specs/liberty-template.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)
std...@cisco.commailto:std
On 6/1/15, 7:38 AM, Jeff Peeler jpee...@redhat.com 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.
http://logs.openstack.org/75/186475/1/check
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
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 tom.camm...@hp.commailto:tom.camm...@hp.com
Reply-To: OpenStack
Its unanimous! Welcome to the core reviewer team Harm!
Regards
-steve
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Sunday, June
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
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:
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
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
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)
std...@cisco.commailto: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
Steve,
There is no need for a second LP project at all.
Adrian
Original message
From: Steven Dake (stdake) std...@cisco.commailto:std...@cisco.com
Date: 06/12/2015 7:41 AM (GMT-08:00)
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev
] Proposal for changing 1600UTC
meeting to 1700 UTC
On Mon, Jun 08, 2015 at 05:15:54PM +, Steven Dake (stdake) wrote:
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
together with you 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)
std...@cisco.commailto:std
Reminder voting ends June 17th.
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Tuesday, June 9, 2015 at 12:02 PM
To: OpenStack
: Steven Dake (stdake) std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, May 25, 2015 at 11:59 AM
To: OpenStack Development Mailing List (not for usage
Jay 513
+1 on mandatory name requirement.
From: Jay Lau jay.lau@gmail.commailto:jay.lau@gmail.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Sunday, May 31, 2015 at 2:38 PM
To:
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:
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
On 5/26/15, 2:16 PM, jpee...@redhat.com 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 source as an option and build
from
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
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.
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
Kennan,
Agree on no requirement for unique name.
Regards
-steve
From: Kai Qiang Wu wk...@cn.ibm.commailto:wk...@cn.ibm.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, June 1, 2015
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
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
. Hope our 10
day eval analysis helps improve OSAD.
Regards
-steve
On Tue, Jun 30, 2015 at 2:28 PM, Ian Cordasco
ian.corda...@rackspace.com wrote:
On 6/29/15, 23:59, Steven Dake (stdake) std...@cisco.com wrote:
The Kolla community
is pleased to announce the
release of the
Kolla Liberty 1
On 7/1/15, 1:22 AM, Thierry Carrez thie...@openstack.org 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 water both days
- pretty amazing amount of work in a short 5 week cycle. Plan
to see same level of focus to meet our Liberty-2 milestone goals and
deliver on our complete mission.
Regards
-steve
--
Kevin Carter
IRC: cloudnull
From: Steven Dake (stdake) std
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,
Please note a correction, the dinner is the night of July 28th at 7pm, not July
27th.
My apologies.
Regards
-steve
From: Steven Dake std...@cisco.commailto:std...@cisco.com
Reply-To: OpenStack Development Mailing List (not for usage questions)
don’t permit 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
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
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
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
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
are miracle!
[Inactive hide details for Steven Dake (stdake) ---07/02/2015 02:06:58
AM---Apologies for double post – left off [magnum] pri]Steven Dake (stdake)
---07/02/2015 02:06:58 AM---Apologies for double post – left off [magnum] prior
by error. Ton Ngo of IBM Silicon Valley Research
From: Steven
Hey folks,
Just a quick reminder, we have a team meeting tomorrow at 1600 UTC on
#openstack-meeting-alt.
Look forward to seeing the team there.
Regards
-steve
__
OpenStack Development Mailing List (not for usage questions)
Hey fellow Kolla devs,
With Sam’s recent change to add build from source as an option and build from
Debuntian binaries as an option, we will end up in a situation where our gate
will take 4+ hours to build all of the images and run the functional tests. I
would like to separate each major
Hi folks,
I propose Sam Yaple for core approver for the Kolla team. Sam has a lot of
great ideas and has done some really cool work lately. Sam is active in IRC
and is starting to pick up more reviews. Of particular interest to me his his
idea of merging the work he has done on YAODU into
1 - 100 of 737 matches
Mail list logo
