+1 for Eli. Great addition to team.
Regards,
Madhuri
-Original Message-
From: Davanum Srinivas [mailto:dava...@gmail.com]
Sent: Wednesday, June 1, 2016 8:11 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Hi Hongbin,
I also liked the idea of having heterogeneous set of nodes but IMO such
features should not be implemented in Magnum, thus deviating Magnum again from
its roadmap. Whereas we should leverage Heat(or may be Senlin) APIs for the
same.
I vote +1 for this feature.
Regards,
Madhuri
Thanks Shu for providing suggestions.
I wanted the new name to be related to containers as Magnum is also synonym for
containers. So I have few options here.
1. Casket
2. Canister
3. Cistern
4. Hutch
All above options are free to be taken on pypi and Launchpad.
Thoughts?
Regards
Madhuri
Hi Ricardo,
Thanks for sharing it. Result seems great and we will surely try to fix the
issue.
Cheers!
Regards,
Madhuri
-Original Message-
From: Ricardo Rocha [mailto:rocha.po...@gmail.com]
Sent: Friday, June 17, 2016 8:44 PM
To: OpenStack Development Mailing List (not for usage
vivek.jain.openst...@gmail.com>;
flw...@catalyst.net.nz<mailto:flw...@catalyst.net.nz>; Shuu Mutou; Davanum
Srinivas; OpenStack Development Mailing List (not for usage questions); Chandan
Kumar; hai...@xr.jp.nec.com<mailto:hai...@xr.jp.nec.com>; Qi Ming Teng;
sitlani.namr...@yah
+1 for both. Welcome!
From: 大塚元央 [mailto:yuany...@oeilvert.org]
Sent: Tuesday, February 2, 2016 9:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Magnum] New Core Reviewers
+1 welcome!!
2016年2月2日(火) 10:14
Corey the one you are talking about has changed to coe-service-*.
Eli, IMO we should display proper error message. M-api service should only have
read permission.
Regards,
Madhuri
From: Corey O'Brien [mailto:coreypobr...@gmail.com]
Sent: Wednesday, February 3, 2016 6:50 PM
To: OpenStack
+1 from me. Thanks Eli for your contribution.
Regards,
Madhuri
From: Yuanying OTSUKA [mailto:yuany...@oeilvert.org]
Sent: Friday, April 1, 2016 8:13 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum]
Hi,
+1 for option #2. Its ok to fetch help message from API server but a drawback
is help message is supposed to work generally even if the actual services are
not running.
Thoughts?
Regards,
Madhuri
-Original Message-
From: taget [mailto:qiaoliy...@gmail.com]
Sent: Thursday, May 12,
+1 for Sypros.
Regards,
Madhuri
From: Hongbin Lu [mailto:hongbin...@huawei.com]
Sent: Saturday, July 23, 2016 1:57 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [magnum] Proposing Spyros Trigazis for Magnum core
+1 from me for both.
From: Hongbin Lu [mailto:hongbin...@gmail.com]
Sent: Wednesday, August 10, 2016 8:40 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Zun][Higgins] Proposing Sudipta Biswas and Wenzhi Yu
for
Hi Greg,
Now it is not mandatory to have lbaas in Magnum. Here is blueprint in Magnum
that aims to decouple lbaas from Magnum
https://blueprints.launchpad.net/magnum/+spec/decouple-lbaas.
You can use flag –master-lb-enabled in baymodel to specify whether you want
lbaas or not. However it just
Hi Greg,
Yes we do have document that explains the steps to configure your docker client
to to be able to interact to bays.
Please follow this link
https://github.com/openstack/magnum/blob/master/doc/source/dev/quickstart.rst#building-and-using-a-swarm-bay
Regards,
Madhuri
From: Waines, Greg
+1 for both.
-Original Message-
From: Wenzhi Yu [mailto:wenzhi...@163.com]
Sent: Tuesday, January 24, 2017 7:02 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Zun] Propose a change of the Zun core
+1 for both.
-Original Message-
From: Adrian Otto [mailto:adrian.o...@rackspace.com]
Sent: Tuesday, November 8, 2016 12:36 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Magnum] New Core Reviewers
Magnum
+1 for both. Shubham will be a great addition to team.
Thanks!
Madhuri
From: Hongbin Lu [mailto:hongbin...@huawei.com]
Sent: Thursday, October 20, 2016 2:49 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Zun]
It seems the term COE is a valid term now. I am in favor of having “openstack
coe cluster” or “openstack container cluster”.
Using the command “infra” is too generic and doesn’t relate to what Magnum is
doing exactly.
Regards,
Madhuri
From: Spyros Trigazis [mailto:strig...@gmail.com]
Sent:
is, Sandbox is the outer container and the real
user container is nested inside the sandbox. I am trying to figure out how
this is going to play out
when we have clear containers.
[Kumari, Madhuri] The sandbox container is just an infra container that manage
IaaS resources associated with a container
+1 from me as well.
Thanks Dims and Yanyan for you contribution to Zun ☺
Regards,
Madhuri
From: Kevin Zhao [mailto:kevin.z...@linaro.org]
Sent: Wednesday, June 21, 2017 6:37 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re:
Hi All,
I am working on a bug [1] in Ironic which talks exposing the state of conductor
service running in OpenStack environment.
There are two ways to do this:
1) create a new API endpoint e.g. 'v1/service' that can report which conductor
is managing given node. Additionally it can also
+1 for both.
Well deserved Feng!
Thanks,
Madhuri
From: Hongbin Lu [mailto:hongbin...@huawei.com]
Sent: Saturday, April 29, 2017 9:35 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Zun] Proposal a change of Zun
+1 for both. Thanks Kien for all your work in Zun, especially multi-node CI.
Regards,
Madhuri
From: Pradeep Singh [mailto:ps4openst...@gmail.com]
Sent: Sunday, September 17, 2017 8:35 PM
To: OpenStack Development Mailing List (not for usage questions)
Hi,
nova-docker was discontinued because the lifecycle of containers and VMs are
different and the Nova APIs doesn't satisfy it.
Zun is an independent project of Nova which has its own set of APIs for
managing containers on top of OpenStack.
For more information, you can read the FAQ section
(not for usage questions)
<openstack-dev@lists.openstack.org>
Cc: Kumari, Madhuri <madhuri.kum...@intel.com>
Subject: [Zun] PTL on vacation for 3 weeks
Hi team,
I will be on vacation during Dec 11 - Jan 2. Madhuri Kumari (cc-ed) kindly
agreed to serve the PTL role while I am away. Wish e
Welcome to the team, Deepak!
Regards,
Madhuri
From: Hongbin Lu [mailto:hongbin...@gmail.com]
Sent: Monday, May 14, 2018 10:00 AM
To: OpenStack Development Mailing List (not for usage questions)
; deepak.mou...@nectechnologies.in
Subject: [openstack-dev] [Zun]
Welcome to the team, Ji Wei ☺
Regards,
Madhuri
From: Hongbin Lu [mailto:hongbin...@gmail.com]
Sent: Thursday, May 3, 2018 2:10 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Zun] Announce change of Zun core
Thank you Hongbin. The article is very helpful.
Regards,
Madhuri
From: Hongbin Lu [mailto:hongbin...@gmail.com]
Sent: Sunday, April 29, 2018 5:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Zun][k8s] AWS
Hi Nova Developers,
I am working on adding a service management API in Ironic [1][2]. This spec
adds a new API /conductors to list, enable/disable an ironic-conductor service.
I am struggling to understand the difference between shutting down a service
manually and disabling it.
So my question
28 matches
Mail list logo