@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
I will get a spec out for review by end of day tomorrow.
Thanks,
Brad Jones
On 4 Jun 2015, at 22:30, Adrian Otto
adrian.o...@rackspace.commailto:adrian.o...@rackspace.com wrote:
Team,
I have published a top level blueprint for a magnum-horizon-plugin:
Jason,
I will definitely weigh all feedback on this. I’m interested in guidance from
anyone taking an interest in this subject.
Thanks,
Adrian
On Jun 4, 2015, at 1:55 PM, Jason Rist jr...@redhat.com wrote:
On 06/04/2015 11:58 AM, Steven Dake (stdake) wrote:
Hey folks,
I think it is
@lists.openstack.org
Date: Thursday, June 4, 2015 at 12:59 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum -
need a vote from the core
: [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...@cisco.com]
Sent: June
:30 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@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
I’m really keen to take on this effort, to echo what Steve said I think adding
a dashboard component to Magnum is critical in adoption and delivering good
usability to all.
Thanks,
Brad Jones
On 4 Jun 2015, at 18:58, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
Hey
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
nt Mailing List (not for usage questions)" openstack-dev@lists.openstack.orgFrom: "Steven Dake (stdake)" std...@cisco.comDate: 06/04/2015 11:03AMSubject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team
Hey folks,
I think it is critical
@lists.openstack.org
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum -
need a vote from the core team
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
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum -
need a vote from the core team
I am interested but not sure how much time I have this release cycle. I can
take on a more hands-off approach and help review
@lists.openstack.org
Subject: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need
a vote from the core team
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
: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need
a vote from the core team
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
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should
be a required option when creating a Bay/Baymodel
Thanks Adrian, imho making name as required can bring more
convenient to end users because UUID is difficult
\)
openstack-dev@lists.openstack.org
Date: 06/04/2015 02:20 PM
Subject:Re: [openstack-dev] [magnum][horizon] Making a dashboard
for Magnum - need a vote from the core team
I am interested but not sure how much time I have this release cycle. I
can take on a more hands-off approach and help
On 06/04/2015 11:58 AM, Steven Dake (stdake) 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 team has no
experience in UI development, but I have found atleast one volunteer Bradley
Jones to
I'm happy to provide reviews from the Horizon standpoint.
David
On Thu, Jun 4, 2015 at 12:55 PM, Jason Rist jr...@redhat.com wrote:
On 06/04/2015 11:58 AM, Steven Dake (stdake) wrote:
Hey folks,
I think it is critical for self-service needs that we have a Horizon
dashboard to represent
@lists.openstack.org
Date:06/04/2015 02:20 PM
Subject:Re: [openstack-dev] [magnum][horizon] Making a dashboard
for Magnum - need a vote from the core team
--
I am interested but not sure how much time I have this release cycle. I
can take on a more hands
\)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date:06/04/2015 02:20 PM
Subject:Re: [openstack-dev] [magnum][horizon] Making a dashboard for
Magnum - need a vote from the core team
I am interested but not sure how much
Some comments and questions in line. Thanks.
2015-06-03 11:27 GMT+08:00 Adrian Otto adrian.o...@rackspace.com:
Eric,
On Jun 2, 2015, at 10:07 PM, Eric Windisch e...@windisch.us wrote:
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.com
wrote:
I have reflected on
--
*From:* Jay Lau [jay.lau@gmail.com]
*Sent:* Tuesday, June 02, 2015 12:33 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be
a required option when creating a Bay/Baymodel
Thanks Adrian, imho making
+1
On May 31, 2015, at 12:56 AM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
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
questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Thanks Adrian, imho making name as required can bring more convenient to end
users because UUID is difficult to use. Without name, the end user need to
retrieve the UUID
Thanks Adrian, imho making name as required can bring more convenient to
end users because UUID is difficult to use. Without name, the end user need
to retrieve the UUID of the bay/baymodel first before he did some
operations for the bay/baymodel, its really time consuming. We can discuss
more in
questions)
openstack-dev@lists.openstack.org
Date: 06/02/2015 06:15 AM
Subject:Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint
Hi Jay,
For your question “what is the mesos object that we want to manage”, the
short answer is it depends. There are two options I can
Eric,
On Jun 2, 2015, at 10:07 PM, Eric Windisch
e...@windisch.usmailto:e...@windisch.us wrote:
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto
adrian.o...@rackspace.commailto:adrian.o...@rackspace.com wrote:
I have reflected on this further and offer this suggestion:
1) Add a feature to
Subject: Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint
--
Hi Jay,
For your question “what is the mesos object that we want to manage”, the
short answer is it depends. There are two options I can think of:
1. Don’t manage any object from
: [openstack-dev] [Magnum] Does Bay/Baymodel name should be
a required option when creating a Bay/Baymodel
Thanks Adrian, imho making name as required can bring more convenient
to end users because UUID is difficult to use. Without name, the end user
need to retrieve the UUID of the bay
On Tue, Jun 2, 2015 at 10:29 PM, Adrian Otto adrian.o...@rackspace.com
wrote:
I have reflected on this further and offer this suggestion:
1) Add a feature to Magnum to auto-generate human readable names, like
Docker does for un-named containers, and ElasticSearch does for naming
cluster
Lau [jay.lau@gmail.commailto:jay.lau@gmail.com]
Sent: Tuesday, June 02, 2015 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Thanks Adrian, imho
at 6:11 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
+1 about Jay option.
BTW
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, June 1, 2015 at 11:08 PM
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when
that with a UUID
since it is different on every cloud.
Thanks,
Kevin
From: Jay Lau [jay.lau@gmail.com]
Sent: Tuesday, June 02, 2015 12:33 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name
: Steven Dake (stdake) [std...@cisco.com]
Sent: Tuesday, June 02, 2015 4:52 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Kennan,
Agree on no requirement
-1. I disagree.
I am not convinced that requiring names is a good idea. I've asked several
times why there is a desire to require names, and I'm not seeing any persuasive
arguments that are not already addressed by UUIDs. We have UUID values to allow
for acting upon an individual resource.
Subject: Re: [openstack-dev] [Magnum] Magnum installation problem with
devstack kilo
--
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
) std...@cisco.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 06/01/2015 01:37 PM
Subject: Re: [openstack-dev] [Magnum] Magnum installation problem with
devstack kilo
--
I have this same problem
:37 PM
Subject:Re: [openstack-dev] [Magnum] Magnum installation problem with
devstack kilo
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
2015-06-01 21:54 GMT+08:00 Jay Pipes jaypi...@gmail.com:
On 05/31/2015 05:38 PM, Jay Lau wrote:
Just want to use ML to trigger more discussion here. There are now
bugs/patches tracing this, but seems more discussions are needed before
we come to a conclusion.
On 05/31/2015 05:38 PM, Jay Lau wrote:
Just want to use ML to trigger more discussion here. There are now
bugs/patches tracing this, but seems more discussions are needed before
we come to a conclusion.
https://bugs.launchpad.net/magnum/+bug/1453732
https://review.openstack.org/#/c/181839/
have for
existing k8s objects: pod/service/rc).
Thoughts?
Thanks
Hongbin
From: Jay Lau [mailto:jay.lau@gmail.com]
Sent: May-29-15 1:35 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint
I want to mention
Follow your heart. You are miracle!
From: Jay Lau jay.lau@gmail.com
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.org
Date: 06/01/2015 11:17 PM
Subject:Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should
+1!
2015-05-31 23:30 GMT+08:00 Hongbin Lu hongbin...@huawei.com:
+1!
*From:* Steven Dake (stdake) [mailto:std...@cisco.com]
*Sent:* May-31-15 1:56 AM
*To:* OpenStack Development Mailing List (not for usage questions)
*Subject:* [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a required
option when creating a Bay/Baymodel
Just want to use ML to trigger more discussion here. There are now bugs
: Sunday, May 31, 2015 at 2:38 PM
To: OpenStack Development Mailing List openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required option when creating a Bay/Baymodel
Just want to use ML to trigger more discussion here. There are now
bugs
+1 for Jay's suggestion.
xuhaiwei
-Original Message-
From: Davanum Srinivas [mailto:dava...@gmail.com]
Sent: Monday, June 01, 2015 8:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] Does Bay/Baymodel name should be a
required
Just want to use ML to trigger more discussion here. There are now
bugs/patches tracing this, but seems more discussions are needed before we
come to a conclusion.
https://bugs.launchpad.net/magnum/+bug/1453732
https://review.openstack.org/#/c/181839/
https://review.openstack.org/#/c/181837/
Hi, all
I am following
http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/dev-quickstart.rst
to
install magnum with openstack kilo version.
At the end, there are error messages like
python update.py /opt/stack/magnum
...
Syncing /opt/stack/magnum/requirements.txt
+1!
From: Steven Dake (stdake) [mailto:std...@cisco.com]
Sent: May-31-15 1:56 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for Core for
Magnum
Hi core team,
Kennan (Kai Qiang Wu's nickname) has really done
To: OpenStack Development Mailing List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Magnum] Magnum installation problem with devstack kilo
Hi, all
I am following
http://git.openstack.org/cgit/openstack/magnum/tree/doc/source/dev/dev
+1 for Kennan.
Thanks Regards
Madhuri Kumari
From: Steven Dake (stdake) [std...@cisco.com]
Sent: Sunday, May 31, 2015 11:26 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan
+1 from me!
On Sun, May 31, 2015 at 1:56 AM, Steven Dake (stdake) std...@cisco.com wrote:
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
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
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
I’m moving this whiteboard to the ML so we can have some discussion to refine
it, and then go back and update the whiteboard.
Source: https://blueprints.launchpad.net/magnum/+spec/mesos-bay-type
My comments in-line below.
Begin forwarded message:
From: hongbin
I want to mention that there is another mesos framework named as chronos:
https://github.com/mesos/chronos , it is used for job orchestration.
For others, please refer to my comments in line.
2015-05-29 7:45 GMT+08:00 Adrian Otto adrian.o...@rackspace.com:
I’m moving this whiteboard to the ML
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)
Cool!
2015-05-22 8:37 GMT-07:00 Adrian Otto adrian.o...@rackspace.com:
Team,
In response to excitement about the demo of magnum I showed during our
Tuesday keynote at the OpenStack Summit in Vancouver, I have made a
screencast of that same demo, and published it on the Magnum project
Hello All Magnum Developers, Users, and Fans:
Please take a few moments to complete our OpenStack / Magnum survey.
Your feedback is appreciated!:
http://goo.gl/forms/W6ggrLiYFv
Thank you,
-Perry Rivera
OpenStack / Magnum
questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: fredag 3 april 2015 13:17
To: OpenStack Development Mailing List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Magnum
Hi All,
Thank you for adding me to this team.
It will be my pleasure to work with you all together.
Till now, everyone has helped me in many or some way.
Thank you for all the support and this honor.
Looking forward for contributing more.
Thanks Regards
Madhuri Kumari
On Fri, May 1, 2015
+1!
On Apr 28, 2015, at 11:14 PM, Steven Dake (stdake) std...@cisco.com wrote:
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?
She
+1, welcome Madhuri!
2015-04-29 0:00 GMT+08:00 Adrian Otto adrian.o...@rackspace.com:
+1
On Apr 28, 2015, at 8:14 AM, Steven Dake (stdake) std...@cisco.com
wrote:
Hi folks,
I would like to nominate Madhuri Kumari to the core team for Magnum.
Please remember a +1 vote indicates your
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
+1 from me. welcome Madhuri!
On Tue, Apr 28, 2015 at 11:14 AM, Steven Dake (stdake) std...@cisco.com wrote:
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
+1
On Apr 28, 2015, at 8:14 AM, Steven Dake (stdake)
std...@cisco.commailto:std...@cisco.com wrote:
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?
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 the Atomic upstream produces which allows a simple
repeatable
On 04/26/2015 02:21 PM, Gregory Haynes 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 the Atomic upstream
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 the
Hi Madhuri,
I can’t also boot a vm with new image from.
But I can boot a vm using compressed image (fedora-21-atomic-3.qcow2.xz
(https://fedorapeople.org/groups/magnum/fedora-21-atomic-3.qcow2.xz))
when decompress it by hand.
Regards,
-yuanying
--
OTSUKA, Motohiro
Sent with Sparrow
Hi Steve,
I tried to boot a vm with the new image from. But it doesn't work.
The vm state was ACTIVE but I can't ping or ssh to the vm.
If anyone has tested it, please let me know.
Also I would request folks to test the image so that we can pass it as we
need this image for Kubernetes Client.
List (not for usage questions)
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [magnum] New fedora 21 Atomic images available for
testing
Hi Madhuri,
I can’t also boot a vm with new image from.
But I can boot a vm using compressed image
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
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.com
wrote:
Hi folks,
I have spent the last couple of days trying to bring some sanity to
Subject: [openstack-dev] [magnum] swagger-codegen generated code for
python-k8sclient
Hi All,
This is to have a discussion on the blueprint for implementing
python-k8client for magnum.
https://blueprints.launchpad.net/magnum/+spec/python-k8sclient
I have committed the code generated
PM
Subject:Re: [openstack-dev] [magnum] swagger-codegen generated code for
python-k8sclient
Hi All,
As we are using fedora-21-atomic-2 image and that has Kubernetes v0.11.0, I
tried to run v1beta3 APIs on it. Some of the APIs failed.
The Kubernetes developer said v1beta3
Fang,
One possibility we have been thinking about is using our Docker-Swarm bay type
to leverage Swarm’s Mesos integration feature as that takes form.
https://github.com/docker/swarm/blob/191b2b5fd4cef01eef0ae2a7e86f600d91b55ec1/ROADMAP.md
Adrian
I see, for different tools building different customer bay is not good choice.
Thanks,
Fang
From: adrian.o...@rackspace.com
To: openstack-dev@lists.openstack.org
Date: Thu, 16 Apr 2015 06:29:30 +
Subject: Re: [openstack-dev] [magnum]
Fang,
One possibility we have been
Andrew,
For clustered services that require generation of a discovery token, and access
to a discovery service, we need to keep in mind a few things:
1) Cloud operators have their own preferences for what defaults should be use.
Some may want to run their own discovery services, and others
Hi Devs,
I'd like to get some discussion going for possible improvements to the
discovery mechanism used in Magnum's Swarm bay.
The method of the existing review[1] is to use the public swarm discovery
endpoint, and let the user pass a token in on the bay-create call. This is
definitely not
a
docker-daemon.
We can create container in it.
--
From: andrew.mel...@rackspace.com
To: openstack-dev@lists.openstack.org
Date: Wed, 15 Apr 2015 14:53:39 +
Subject: Re: [openstack-dev] [magnum] How to use docker-swarm bay in magnum
Hi Jay,
Magnum Bays do
FRI
From: fang_feng...@hotmail.com
To: openstack-dev@lists.openstack.org
Date: Wed, 15 Apr 2015 14:29:27 +
Subject: [openstack-dev] [magnum]
Apache Mesos maybe is a choice as a Magnum's Container backend.Now it native
support Docker contanier . I thinks magnum have aMesos bay is very
From: Jay Lau jay.lau@gmail.com
Sent: Tuesday, April 14, 2015 5:33 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [magnum] How to use docker-swarm bay in magnum
Greetings,
Currently, there is a docker-swarm bay in magnum, but the problem is after this
swarm
For docker-swam bay,I think the bay looks like a big machine have a
docker-daemon.We can create container in it.
From: andrew.mel...@rackspace.com
To: openstack-dev@lists.openstack.org
Date: Wed, 15 Apr 2015 14:53:39 +
Subject: Re: [openstack-dev] [magnum] How to use docker-swarm bay
Maybe we can add a object mapping to docker-compose.
Date: Wed, 15 Apr 2015 23:32:01 +0800
From: jay.lau@gmail.com
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [magnum] How to use docker-swarm bay in magnum
Thanks Andrew and Fenghua. I see. The current docker-swarm
Apache Mesos maybe is a choice as a Magnum's Container backend.Now it native
support Docker contanier . I thinks magnum have aMesos bay is very Cool.
__
OpenStack Development
From: =?gb18030?B?NDQ5MTcxMzQy?= 449171...@qq.com
To: =?gb18030?B?b3BlbnN0YWNrLWRldg==?=
openstack-dev@lists.openstack.org
Subject: [openstack-dev] ?magnum?About clean none use container imag
Message-ID: tencent_1b594e50513691b07d1b8...@qq.com
Content-Type: text/plain; charset=gb18030
From now
Greetings,
Currently, there is a docker-swarm bay in magnum, but the problem is after
this swarm bay was created, how to let user use this bay? Still using swarm
CLI? The magnum do not have API/CLI to interact with swarm bay now.
--
Thanks,
Jay Lau (Guangya Liu)
2015 14:51:05 +0800
From: =?gb18030?B?NDQ5MTcxMzQy?= 449171...@qq.commailto:449171...@qq.com
To: =?gb18030?B?b3BlbnN0YWNrLWRldg==?=
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] ?magnum?About clean none use container imag
Message-ID
From now on magnum had container create and delete api .The container create
api will pull docker image from docker-registry.But the container delete api
didn't delete image.It will let the image remain even though didn't had
container use it.Is it much better we can clear the image in
Interesting topic, pulling image is time consuming, so someone might not
want to delete the container; But for some cases, if the image was not
used, then it is better to remove them from disk to release space. You may
want to send out an email to [openstack][magnum] ML to get more feedback ;-)
This puts me in mind of a previous proposal, from the Neutron side of
things. Specifically, I would look at Erik Moe's proposal for VM ports
attached to multiple networks:
https://blueprints.launchpad.net/neutron/+spec/vlan-aware-vms .
I believe that you want logical ports hiding behind a
confirmed
On 04/02/2015 12:36 PM, Adrian Otto wrote:
I respectfully respect your support to continue as your Magnum PTL.
Here are are my achievements and OpenStack experience and that make me the
best choice for this role:
* Founder of the OpenStack Containers Team
* Established vision
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 this proposal:
I respectfully respect your support to continue as your Magnum PTL.
Here are are my achievements and OpenStack experience and that make me the best
choice for this role:
* Founder of the OpenStack Containers Team
* Established vision and specification for Magnum
* Served as PTL for Magnum since
On 04/02/2015 01:45 PM, Kevin Benton wrote:
+1. I added a suggestion for a container networking suggestion to the
etherpad for neutron. It would be sad if the container solution built
yet another overlay on top of the Neutron networks with yet another
network management workflow. By the time
Russell,
On Apr 2, 2015, at 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
+1. I added a suggestion for a container networking suggestion to the
etherpad for neutron. It would be sad if the container solution built yet
another overlay on top of the Neutron networks with yet another network
management workflow. By the time the packets are traveling across the
wires, it
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
1301 - 1400 of 1499 matches
Mail list logo
