[openstack-dev] [Containers][Magnum] Questions on dbapi

2014-12-31 Thread Hongbin Lu
Hi all, I am writing tests for the Magnum dbapi. I have several questions about its implementation and appreciate if someone could comment on them. * Exceptions: The exceptions below were ported from Ironic but don't seem to make sense in Magnum. I think we should purge them from the code except

Re: [openstack-dev] [magnum] Propose removing Dmitry Guryanov from magnum-core

2015-02-17 Thread Hongbin Lu
-1 On Mon, Feb 16, 2015 at 10:20 PM, Steven Dake (stdake) std...@cisco.com wrote: 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

Re: [openstack-dev] [heat] multicloud support for ec2

2015-01-28 Thread Hongbin Lu
Hi, I would appreciate if someone replies the email below. Thanks. Best regards, Hongbin On Sun, Jan 25, 2015 at 12:03 AM, Hongbin Lu hongbin...@gmail.com wrote: Hi Heat team, I am looking for a solution to bridge between OpenStack and EC2. According to documents, it seems that Heat has

[openstack-dev] [heat] multicloud support for ec2

2015-01-24 Thread Hongbin Lu
Hi Heat team, I am looking for a solution to bridge between OpenStack and EC2. According to documents, it seems that Heat has multicloud support but the remote cloud(s) must be OpenStack. I wonder if Heat supports multicloud in the context of supporting remote EC2 cloud. For example, does Heat

Re: [openstack-dev] [magnum] Memory recommendation for running magnum with devstack

2015-03-19 Thread Hongbin Lu
Hi Surojit, I think 8G of RAM and 80G of disk should be considered the minimum. The guide will create 3 m1.small VMs (each with 2G of RAM and 20G of disk), and 2 volumes (5G each). In your case, I am not sure why you get the memory error. Probably, you could walk-around it by creating a flavor

Re: [openstack-dev] [Magnum][Heat] Expression of Bay Status

2015-03-10 Thread Hongbin Lu
Hi Adrian, On Mon, Mar 9, 2015 at 6:53 PM, Adrian Otto adrian.o...@rackspace.com wrote: Magnum Team, In the following review, we have the start of a discussion about how to tackle bay status: https://review.openstack.org/159546 I think a key issue here is that we are not subscribing to

Re: [openstack-dev] [magnum] swagger-codegen generated code for python-k8sclient

2015-03-23 Thread Hongbin Lu
Hi Madhuri, Amazing work! I wouldn't concern the code duplication and modularity issue since the codes are generated. However, there is another concern here: if we find a bug/improvement of the generated code, we probably need to modify the generator. The question is if the upstream will accept

Re: [openstack-dev] [magnum] Issue on going through the quickstart guide

2015-02-22 Thread Hongbin Lu
wrote: Can you check the kubelet log on your minions? Seems the container failed to start, there might be something wrong for your minions node. Thanks. 2015-02-22 15:08 GMT+08:00 Hongbin Lu hongbin...@gmail.com: Hi all, I tried to go through the new redis example at the quickstart guide [1

[openstack-dev] [magnum] Issue on going through the quickstart guide

2015-02-21 Thread Hongbin Lu
Hi all, I tried to go through the new redis example at the quickstart guide [1], but was not able to go through. I was blocked by connecting to the redis slave container: *$ docker exec -i -t $REDIS_ID redis-cli* *Could not connect to Redis at 127.0.0.1:6379 http://127.0.0.1:6379: Connection

Re: [openstack-dev] [magnum] Issue on going through the quickstart guide

2015-02-22 Thread Hongbin Lu
json file and the parsed json file? Thanks! kubectl create -f .json xxx 2015-02-23 1:40 GMT+08:00 Hongbin Lu hongbin...@gmail.com: Thanks Jay, I checked the kubelet log. There are a lot of Watch closed error like below. Here is the full log http://fpaste.org/188964/46261561

Re: [openstack-dev] [magnum] Proposal for Madhuri Kumari to join Core Team

2015-04-30 Thread Hongbin Lu
+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

Re: [openstack-dev] [magnum][horizon] Making a dashboard for Magnum - need a vote from the core team

2015-06-04 Thread Hongbin Lu
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: OpenStack Development Mailing List (not for usage questions) Subject:

[openstack-dev] [heat] Question about retrieving resource_list from ResourceGroup

2015-06-26 Thread Hongbin Lu
Hi team, I would like to start my question by using a sample template: heat_template_version: 2014-10-16 parameters: count: type: number default: 5 removal_list: type: comma_delimited_list default: [] resources: sample_group: type: OS::Heat::ResourceGroup

Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

2015-06-13 Thread Hongbin Lu
blueprint. This way we solve for the use case, and don't need a new attribute on the bay resource that requires users to concatenate multiple attribute values in order to get a native client tool working. Adrian On Jun 12, 2015, at 6:32 PM, Hongbin Lu hongbin...@huawei.commailto:hongbin...@huawei.com

Re: [openstack-dev] [Magnum] Discuss configurable-coe-api-port Blueprint

2015-06-12 Thread Hongbin Lu
A use case could be the cloud is behind a proxy and the API port is filtered. In this case, users have to start the service in an alternative port. Best regards, Hongbin From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: June-12-15 2:22 PM To: OpenStack Development Mailing List (not for

Re: [openstack-dev] [Magnum] Add periodic task threading for conductor server

2015-06-14 Thread Hongbin Lu
I think option #3 is the most desired choice in performance’s point of view, because magnum is going to support multiple conductors and all conductors share the same DB. However, if each conductor runs its own thread for periodic task, we will end up to have multiple instances of tasks for

Re: [openstack-dev] [magnum] Proposing Kai Qiang Wu (Kennan) for Core for Magnum

2015-05-31 Thread Hongbin Lu
+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

Re: [openstack-dev] [Magnum] Discuss mesos-bay-type Blueprint

2015-06-01 Thread Hongbin Lu
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 Marathon directly. Instead, we can focus on the existing Magnum objects (i.e. container), and implements them

Re: [openstack-dev] [openstackclient] [magnum] Review of object and actions for magnumclient implementation

2015-05-24 Thread Hongbin Lu
Hi Ronald, I think the “update” action is definitely appropriate to use, since it is not specific to magnum (Heat and Ironic use it as well). By looking through the existing list of actions [1], it looks the start/stop actions fits into the openstackclient resume/suspend actions. The “execute”

Re: [openstack-dev] [Magnum] Continuing with heat-coe-templates

2015-06-29 Thread Hongbin Lu
Agree. The motivation of pulling templates out of Magnum tree is hoping these templates can be leveraged by a larger community and get more feedback. However, it is unlikely to be the case in practise, because different people has their own version of templates for addressing different use

Re: [openstack-dev] [magnum][blueprint] magnum-service-list

2015-07-29 Thread Hongbin Lu
Suro, I think service/pod/rc are k8s-specific. +1 for Jay’s suggestion about renaming COE-specific command, since the new naming style looks consistent with other OpenStack projects. In addition, it will eliminate name collision of different COEs. Also, if we are going to support pluggable

Re: [openstack-dev] [Magnum]horizontal scalability

2015-08-03 Thread Hongbin Lu
Adrian, If the reason to avoid leader election is because it is complicated and error prone, this argument may not be true. Leader election is complicated in a pure distributed system in which there is no centralized storage. However, Magnum has a centralized database, so it is possible to

Re: [openstack-dev] [magnum]password for registry v2

2015-08-13 Thread Hongbin Lu
Hi Wanghua, For the question about how to pass user password to bay nodes, there are several options here: 1. Directly inject the password to bay nodes via cloud-init. This might be the simplest solution. I am not sure if it is OK in security aspect. 2. Inject a scoped Keystone

Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal withHyper

2015-07-21 Thread Hongbin Lu
and also have plan integrate with mesos for scheduling. Once mesos integration finished, we can treat mesos+hyper as another kind of bay. Thanks 2015-07-19 4:15 GMT+08:00 Hongbin Lu hongbin...@huawei.commailto:hongbin...@huawei.com: Peng, Several questions Here. You mentioned that HyperStack

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

2015-07-15 Thread Hongbin Lu
, Haidian District Beijing P.R.China 100193 Follow your heart. You are miracle! [Inactive hide details for Hongbin Lu ---07/16/2015 04:44:14 AM---+1 for the idea of using Nova flavor directly. Why we introduc]Hongbin Lu

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

2015-07-16 Thread Hongbin Lu
Follow your heart. You are miracle! graycol.gifHongbin Lu ---07/16/2015 11:47:30 AM---Kai, Sorry for the confusion. To clarify, I was thinking how to name the field you proposed in baymo From: Hongbin Lu hongbin...@huawei.commailto:hongbin...@huawei.com To: OpenStack Development Mailing List

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

2015-07-14 Thread Hongbin Lu
I am going to propose a third option: 3. virt_type I have concerns about option 1 and 2, because “instance_type” and flavor was used interchangeably before [1]. If we use “instance_type” to indicate “vm” or “baremetal”, it may cause confusions. [1]

Re: [openstack-dev] [magnum] Magnum template manage use platform VS others as a type?

2015-07-15 Thread Hongbin Lu
is a vm, and 'ironic' means a baremetal nova instance. Adrian Original message From: Hongbin Lu hongbin...@huawei.commailto:hongbin...@huawei.com Date: 07/14/2015 7:20 PM (GMT-08:00) To: OpenStack Development Mailing List (not for usage questions) openstack-dev

Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal with Hyper

2015-07-18 Thread Hongbin Lu
Peng, Several questions Here. You mentioned that HyperStack is a single big “bay”. Then, who is doing the multi-host scheduling, Hyper or something else? Were you suggesting to integrate Hyper with Magnum directly? Or you were suggesting to integrate Hyper with Magnum indirectly (i.e. through

[openstack-dev] [magnum][devstack] Request actions on a suspicious commit

2015-07-13 Thread Hongbin Lu
Hi, I sent this email to request investigations on a suspicious commit [1] from devstack, which possibly breaks magnum's functional gate test. The first breakage at Magnum side occurred at Jul 10 4:18 PM [2], which is about half an hour after the suspicious commit being merged. By dipping into

Re: [openstack-dev] [magnum][kolla] Stepping down as a Magnum core reviewer

2015-10-25 Thread Hongbin Lu
Hi Steve, Thanks for your contributions. Personally, I would like to think for your mentorship and guidance when I was new to Magnum. It helps me a lot to pick up everything. Best wish for your adventure in Kolla. Best regards, Hongbin From: Steven Dake (stdake) [mailto:std...@cisco.com]

Re: [openstack-dev] [Magnum][Testing] Reduce Functional testing ongate.

2015-11-13 Thread Hongbin Lu
I am going to share something that might be off the topic a bit. Yesterday, I was pulled to the #openstack-infra channel to participant a discussion, which is related to the atomic image download in Magnum. It looks the infra team is not satisfied with the large image size. In particular, they

Re: [openstack-dev] [magnum] Failed to create swarm bay with fedora-21-atomic-5-d181.qcow2

2015-10-16 Thread Hongbin Lu
Hi Mars, I cannot reproduce the error. My best guess is that your VMs don’t have external internet access (Could you verify it by ssh into one of your VM and type “curl openstack.org” ?). If not, please create a bug to report the error (https://bugs.launchpad.net/magnum). Thanks, Hongbin

Re: [openstack-dev] [magnum] Creating pods results in "EOF occurred in violation of protocol" exception

2015-10-14 Thread Hongbin Lu
Hi Bertrand, Thanks for reporting the error. I confirmed that this error was consistently reproducible. A bug ticket was created for that. https://bugs.launchpad.net/magnum/+bug/1506226 Best regards, Hongbin -Original Message- From: Bertrand NOEL [mailto:bertrand.n...@cern.ch] Sent:

[openstack-dev] [magnum] Document adding --memory option to create containers

2015-10-08 Thread Hongbin Lu
Hi team, I want to move the discussion in the review below to here, so that we can get more feedback https://review.openstack.org/#/c/232175/ In summary, magnum currently added support for specifying the memory size of containers. The specification of the memory size is optional, and the COE

Re: [openstack-dev] [magnum] Tom Cammann for core

2015-07-10 Thread Hongbin Lu
+1 Welcome Tom! -Original Message- From: Adrian Otto [mailto:adrian.o...@rackspace.com] Sent: July-09-15 10:21 PM To: OpenStack Development Mailing List Subject: [openstack-dev] [magnum] Tom Cammann for core Team, Tom Cammann (tcammann) has become a valued Magnum contributor, and

Re: [openstack-dev] [magnum] versioned objects changes

2015-08-27 Thread Hongbin Lu
-1 from me. IMHO, the rolling upgrade feature makes sense for a mature project (like Nova), but not for a young project like Magnum. It incurs overheads for contributors reviewers to check the object compatibility in each patch. As you mentioned, the key benefit of this feature is supporting

[openstack-dev] [magnum] Steps to upload magnum images

2015-09-06 Thread Hongbin Lu
Hi team, As you may know, magnum is tested with pre-built Fedora Atomic images. Basically, these images are standard atomic image with k8s packages pre-installed. The images can be downloaded from fedorapeople.org [1]. In most cases, you are able to test magnum by using images there. If you

[openstack-dev] [magnum] Vote for our weekly meeting schedule

2015-09-10 Thread Hongbin Lu
Hi team, Currently, magnum weekly team meeting is scheduled at Tuesday UTC1600 and UTC2200. As our team growing, contributors from different timezones joined and actively participated. I worried that our current meeting schedule (which was decided a long time ago) might not be update-to-date

Re: [openstack-dev] [magnum] Maintaining cluster API in upgrades

2015-09-14 Thread Hongbin Lu
Hi Ryan, I think pushing python k8sclient out of magnum tree (option 3) is the decision, which was made in Vancouver Summit (if I remembered correctly). It definitely helps for solving the k8s versioning problems. Best regards, Hongbin From: Ryan Rossiter [mailto:rlros...@linux.vnet.ibm.com]

[openstack-dev] [magnum][ptl] Magnum PTL Candidacy

2015-09-17 Thread Hongbin Lu
Hi all, I would like to announce my candidacy for the PTL position of Magnum. I involved in Magnum project starting from December 2014. At that time, Magnum's code base is much smaller than right now. Since then, I worked with a diverse set of team members to land features, discuss the

Re: [openstack-dev] [all][elections] PTL nomination period is now over

2015-09-17 Thread Hongbin Lu
Hi, I am fine to have an election with Adrian Otto, and potentially with other candidates who are also late. Best regards, Hongbin From: Kyle Mestery [mailto:mest...@mestery.com] Sent: September-17-15 4:24 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [magnum] New Core Reviewers

2015-09-30 Thread Hongbin Lu
+1 for both. Welcome! From: Davanum Srinivas [mailto:dava...@gmail.com] Sent: September-30-15 7:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum] New Core Reviewers +1 from me for both Vilobh and Hua. Thanks, Dims On Wed, Sep 30, 2015

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-01 Thread Hongbin Lu
Kris, I think the proposal of hierarchical projects is out of the scope of magnum, and you might need to bring it up at keystone or cross-project meeting. I am going to propose a walk-around that might work for you at existing tenancy model. Suppose there is a department (department A) with

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-10-01 Thread Hongbin Lu
, Kevin From: Hongbin Lu [hongbin...@huawei.com] Sent: Thursday, October 01, 2015 7:39 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [magnum]swarm + compose = k8s? Kris, I think the proposal of hierarchical projects

Re: [openstack-dev] [magnum]swarm + compose = k8s?

2015-09-30 Thread Hongbin Lu
+1 from me as well. I think what makes Magnum appealing is the promise to provide container-as-a-service. I see coe deployment as a helper to achieve the promise, instead of the main goal. Best regards, Hongbin From: Jay Lau [mailto:jay.lau@gmail.com] Sent: September-29-15 10:57 PM To:

Re: [openstack-dev] [magnum] Handling password for k8s

2015-09-20 Thread Hongbin Lu
Hi Ton, If I understand your proposal correctly, it means the inputted password will be exposed to users in the same tenant (since the password is passed as stack parameter, which is exposed within tenant). If users are not admin, they don't have privilege to create a temp user. As a result,

Re: [openstack-dev] [magnum] Associating patches with bugs/bps (Please don't hurt me)

2015-09-18 Thread Hongbin Lu
For the guidance, I saw the judgement is a bit subjective. It could happen that a contributor think his/her patch is trivial (or it is not fixing a function defect), but a reviewer think the opposite. For example, I find it hard to judge when I reviewed the following patches:

Re: [openstack-dev] [magnum] versioned objects changes

2015-08-28 Thread Hongbin Lu
, and it will also be a major savings later on if something like [1] pops up. [1]: https://bugs.launchpad.net/nova/+bug/1474074 [2]: https://review.openstack.org/#/c/217342/ On 8/27/2015 9:46 AM, Hongbin Lu wrote: -1 from me. IMHO, the rolling upgrade feature makes sense for a mature project (like Nova

Re: [openstack-dev] [magnum] Mesos Conductor

2015-12-07 Thread Hongbin Lu
pletely stable from an API perspective, and no additional changes are likely. All of our COE’s still have plenty of maturation ahead of them, so this is the wrong time to wrap them. If someone really wants apps and appgroups, (s)he could add that to an experimental branch of the magnum client, a

Re: [openstack-dev] Mesos Conductor using container-create operations

2015-12-09 Thread Hongbin Lu
As Bharath mentioned, I am +1 to extend the "container" object to Mesos bay. In addition, I propose to extend "container" to k8s as well (the details are described in this BP [1]). The goal is to promote this API resource to be technology-agnostic and make it portable across all COEs. I am

Re: [openstack-dev] [magnum] Magnum conductor async container operations

2015-12-17 Thread Hongbin Lu
Suro, FYI. In before, we tried a distributed lock implementation for bay operations (here are the patches [1,2,3,4,5]). However, after several discussions online and offline, we decided to drop the blocking implementation for bay operations, in favor of non-blocking implementation (which is

Re: [openstack-dev] [magnum] Removing pod, rcs and service APIs

2015-12-16 Thread Hongbin Lu
Hi Tom, If I remember correctly, the decision is to drop the COE-specific API (Pod, Service, Replication Controller) in the next API version. I think a good way to do that is to put a deprecated warning in current API version (v1) for the removed resources, and remove them in the next API

Re: [openstack-dev] Mesos Conductor using container-create operations

2015-12-10 Thread Hongbin Lu
and handle things appropriately. We should think through the scenarios carefully to come to agreement on how this would work. Ton Ngo, [Inactive hide details for Hongbin Lu ---12/09/2015 03:09:23 PM---As Bharath mentioned, I am +1 to extend the "container" object]Hongbin Lu ---12/09/2

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

2015-12-12 Thread Hongbin Lu
Hi, As Kai Qiang mentioned, magnum gate recently had a bunch of random failures, which occurred on creating a nova instance with 2G of RAM. According to the error message, it seems that the hypervisor tried to allocate memory to the nova instance but couldn’t find enough free memory in the

Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

2016-01-07 Thread Hongbin Lu
[mailto:cboy...@sapwetik.org] Sent: January-07-16 6:04 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate On Thu, Jan 7, 2016, at 02:59 PM, Hongbin Lu wrote: > Hi folks, > > It looks the swarm func test is

[openstack-dev] [magnum] Temporarily remove swarm func test from gate

2016-01-07 Thread Hongbin Lu
Hi folks, It looks the swarm func test is currently unstable, which negatively impacts the patch submission workflow. I proposed to remove it from Jenkins gate (but keep it in Jenkins check), until it becomes stable. Please find the details in the review

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

2015-12-21 Thread Hongbin Lu
If we decide to support quotas in CaaS layer (i.e. limit the # of bays), its implementation doesn't have to be redundant to IaaS layer (from Nova, Cinder, etc.). The implementation could be a layer on top of IaaS, in which requests need to pass two layers of quotas to succeed. There would be

Re: [openstack-dev] [openstack][magnum] Quota for Magnum Resources

2015-12-21 Thread Hongbin Lu
Jay, I think we should agree on a general direction before asking for a spec. It is bad to have contributors spend time working on something that might not be accepted. Best regards, Hongbin From: Jay Lau [mailto:jay.lau@gmail.com] Sent: December-20-15 6:17 PM To: OpenStack Development

Re: [openstack-dev] [openstack][magnum]a problem about trust

2015-12-23 Thread Hongbin Lu
+1 Thanks Steven for pointing out the pitfall. Best regards, Hongbin -Original Message- From: Steven Hardy [mailto:sha...@redhat.com] Sent: December-23-15 3:30 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [openstack][magnum]a problem

Re: [openstack-dev] [Infra][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

2015-12-21 Thread Hongbin Lu
Hi Jeremy, If you can make the swap size consistent, that would be terrific. Consistent settings across test nodes can improve the predictability of the test results. Thanks for the assistant from infra team to locate the cause of this error. We greatly appreciate it. Best regards, Hongbin

Re: [openstack-dev] [Infra][nova][magnum] Jenkins failed quite often for "Cannot set up guest memory 'pc.ram': Cannot allocate memory"

2015-12-20 Thread Hongbin Lu
t; On Sun, Dec 13, 2015, at 10:51 AM, Clark Boylan wrote: > On Sat, Dec 12, 2015, at 02:16 PM, Hongbin Lu wrote: > > Hi, > > > > As Kai Qiang mentioned, magnum gate recently had a bunch of random > > failures, which occurred on creating a nova instance with 2G of RA

Re: [openstack-dev] [magnum]storage for docker-bootstrap

2015-11-25 Thread Hongbin Lu
Here is a bit more context. Currently, at k8s and swarm bay, some required binaries (i.e. etcd and flannel) are built into image and run at host. We are exploring the possibility to containerize some of these system components. The rationales are (i) it is infeasible to build custom packages

Re: [openstack-dev] [magnum] Using docker container to run COE daemons

2015-11-26 Thread Hongbin Lu
Jay, Agree and disagree. Containerize some COE daemons will facilitate the version upgrade and maintenance. However, I don’t think it is correct to blindly containerize everything unless there is an investigation performed to understand the benefits and costs of doing that. Quoted from Egor,

Re: [openstack-dev] [magnum] Mesos Conductor

2015-11-18 Thread Hongbin Lu
Hi Bharath, I agree the "container" part. We can implement "magnum container-create .." for mesos bay in the way you mentioned. Personally, I don't like to introduce "apps" and "appgroups" resources to Magnum, because they are already provided by native tool [1]. I couldn't see the benefits to

[openstack-dev] [magnum] Issue on history of renamed file/folder

2015-11-18 Thread Hongbin Lu
Hi team, I would like to start this ML to discuss the git rename issue. Here is the problem. In Git, it is handy to retrieve commit history of a file/folder. There are several ways to do that. In CLI, you can run "git log ..." to show the history. In Github, you can click "History" bottom on

Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

2016-01-08 Thread Hongbin Lu
remove swarm func test from gate Hongbin, I’m not aware of any viable options besides using a nonvoting gate job. Are there other alternatives to consider? If not, let’s proceed with that approach. Adrian > On Jan 7, 2016, at 3:34 PM, Hongbin Lu <hongbin...@huawei.com> wrote: &

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

2016-06-03 Thread Hongbin Lu
ple > homogeneous bays, not a single heterogeneous one. That way you end up > with a composition of simple systems rather than a larger complex one. > > Adrian > > > > On Jun 1, 2016, at 3:02 PM, Hongbin Lu <hongbin...@huawei.com> wrote: > > > > Persona

[openstack-dev] Announcing Higgins -- Container management service for OpenStack

2016-06-03 Thread Hongbin Lu
Hi all, We would like to introduce you a new container project for OpenStack called Higgins (might be renamed later [1]). Higgins is a Container Management service for OpenStack. The key objective of the Higgins project is to enable tight integration between OpenStack and container

[openstack-dev] [Magnum] The Magnum Midcycle

2016-06-07 Thread Hongbin Lu
Hi all, Please find the Doodle pool below for selecting the Magnum midcycle date. Presumably, it will be a 2 days event. The location is undecided for now. The previous midcycles were hosted in bay area so I guess we will stay there at this time. http://doodle.com/poll/5tbcyc37yb7ckiec In

Re: [openstack-dev] [magnum][heat] spawn a group of nodes on different availability zones

2016-06-07 Thread Hongbin Lu
Hi Heat team, A question inline. Best regards, Hongbin > -Original Message- > From: Steven Hardy [mailto:sha...@redhat.com] > Sent: March-03-16 3:57 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [magnum][heat] spawn a group of nodes

Re: [openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

2016-06-07 Thread Hongbin Lu
Insaan > Cc: Hongbin Lu; adit...@nectechnologies.in; > vivek.jain.openst...@gmail.com; Shuu Mutou; Davanum Srinivas; hai- > x...@xr.jp.nec.com; Yuanying; Kumari, Madhuri; yanya...@cn.ibm.com; > flw...@catalyst.net.nz; OpenStack Development Mailing List (not for > usage questions);

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

2016-06-07 Thread Hongbin Lu
her project uses. >> >> https://en.wikipedia.org/wiki/Straddle_carrier >> https://en.wikipedia.org/wiki/Suezmax >> https://en.wikipedia.org/wiki/Twistlock >> >> These words are not used by other project on PYPI and Launchpad. >> >> ex.) >> https:

[openstack-dev] [Higgins][Zun] Project roadmap

2016-06-12 Thread Hongbin Lu
Hi team, During the team meetings these weeks, we collaborated the initial project roadmap. I summarized it as below. Please review. * Implement a common container abstraction for different container runtimes. The initial implementation will focus on supporting basic container operations

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

2016-06-10 Thread Hongbin Lu
://etherpad.openstack.org/p/containers-service-api * https://etherpad.openstack.org/p/openstack-containers-service-api 2016年6月1日(水) 12:09 Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>>: Sheel, Thanks for taking the responsibility. Assigned the BP to you. As discussed, please s

Re: [openstack-dev] [Magnum] The Magnum Midcycle

2016-06-09 Thread Hongbin Lu
t for usage questions)" <openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle Hi Hongbin. CERN's location: https://goo.gl/maps/DWbDVjnAvJJ2 Cheers, Spyros On 8 June 2016 at 16:01, Hongbin Lu <

Re: [openstack-dev] [kuryr][magnum]Installing kuryr for mutlinode openstack setup

2016-05-25 Thread Hongbin Lu
one running in one node, and then have N nodes with docker engine, kuryr/libnetwork and the neutron agents of the vendor of your choice. [Hongbin Lu] Yes, Magnum is optional if you prefer to install swarm/k8s/mesos manually or by other tools. What Magnum offers is basically an automation of de

Re: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, and removal notice

2016-06-10 Thread Hongbin Lu
+1 > -Original Message- > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] > Sent: June-10-16 5:33 AM > To: openstack-dev@lists.openstack.org > Cc: Haruhiko Katou > Subject: [openstack-dev] [magnum-ui][magnum] Proposed Core addition, > and removal notice > > Hi team, > > I propose the

Re: [openstack-dev] Quesion about Openstack Containers and Magnum

2016-06-11 Thread Hongbin Lu
Hi, It looks Spyros already answered your question: http://lists.openstack.org/pipermail/openstack-dev/2016-June/097083.html . Is anything else we can help, or you have further questions? Best regards, Hongbin From: zhihao wang [mailto:wangzhihao...@hotmail.com] Sent: June-11-16 1:03 PM To:

Re: [openstack-dev] [Higgins][Zun] Project roadmap

2016-06-13 Thread Hongbin Lu
Rana Insaan; Yuanying Subject: Re: [openstack-dev] [Higgins][Zun] Project roadmap On Mon, Jun 13, 2016 at 12:10 AM, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: Hi team, During the team meetings these weeks, we collaborated the initial project roadmap.

Re: [openstack-dev] [magnum] Notes for Magnum design summit

2016-06-13 Thread Hongbin Lu
ut need to elaborate the details further. The idea revolves around creating a heat stack for each node in the bay. This idea shows a lot of promise but needs more investigation and isn’t a current priority. Tom From: Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>&g

Re: [openstack-dev] [Higgins][Zun] Project roadmap

2016-06-14 Thread Hongbin Lu
> -Original Message- > From: Flavio Percoco [mailto:fla...@redhat.com] > Sent: June-14-16 3:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [Higgins][Zun] Project roadmap > > On 13/06/16 18:46 +0

Re: [openstack-dev] [Magnum] The Magnum Midcycle

2016-06-14 Thread Hongbin Lu
cation: https://goo.gl/maps/DWbDVjnAvJJ2 Cheers, Spyros On 8 June 2016 at 16:01, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: Ricardo, Thanks for the offer. Would I know where is the exact location? Best regards, Hongbin > -Original Message-

Re: [openstack-dev] [Magnum] The Magnum Midcycle

2016-06-14 Thread Hongbin Lu
, CA. -- Adrian On Jun 7, 2016, at 1:35 PM, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: Hi all, Please find the Doodle pool below for selecting the Magnum midcycle date. Presumably, it will be a 2 days event. The location is undecided for now. The previo

Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide

2016-06-14 Thread Hongbin Lu
t; > Call me ignorance, but I'm surprised at neutron-lbaas being a > > dependency of magnum. Why is this? Sorry if it has been asked > before > > and I've just missed that answer? > > > > Thanks, > > Brandon > > On Wed, 2016-06-01 at 14:39 +, Hongbin Lu wrote

Re: [openstack-dev] [magnum][lbaas][docs] Operator-facing installation guide

2016-06-14 Thread Hongbin Lu
at 3:54 PM, Hongbin Lu <hongbin...@huawei.com<mailto:hongbin...@huawei.com>> wrote: Hi neutron-lbaas team, Could anyone confirm if there is an operator-facing install guide for neutron-lbaas. So far, the closest one we could find is: https://wiki.openstack.org/wiki/Neutron/LBaaS/HowT

Re: [openstack-dev] [Higgins][Zun] Project roadmap

2016-06-13 Thread Hongbin Lu
Percoco wrote: > > On 12/06/16 22:10 +, Hongbin Lu wrote: > >> Hi team, > >> > >> During the team meetings these weeks, we collaborated the initial > >> project roadmap. I summarized it as below. Please review. > >> > >> * Impl

Re: [openstack-dev] [Magnum] The Magnum Midcycle

2016-06-08 Thread Hongbin Lu
gt; Subject: Re: [openstack-dev] [Magnum] The Magnum Midcycle > > Hi Hongbin. > > Not sure how this fits everyone, but we would be happy to host it at > CERN. How do people feel about it? We can add a nice tour of the place > as a bonus :) > > Let us know. > > Ricardo >

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

2016-05-28 Thread Hongbin Lu
n vs > one that has 'just do the basics' but thats just my 2 cents... > > Hongbin Lu wrote: > > I agree with you and Qiming. The Higgins project should start with > > basic functionalities and revisit advanced features later. > > > > Best regards, > > > &g

Re: [openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] Gap analysis: Heat as a k8s orchestrator

2016-05-28 Thread Hongbin Lu
> -Original Message- > From: Zane Bitter [mailto:zbit...@redhat.com] > Sent: May-27-16 6:31 PM > To: OpenStack Development Mailing List > Subject: [openstack-dev] [TripleO][Kolla][Heat][Higgins][Magnum][Kuryr] > Gap analysis: Heat as a k8s orchestrator > > I spent a bit of time

Re: [openstack-dev] [higgins] Docker-compose support

2016-05-31 Thread Hongbin Lu
I don’t think it is a good to re-invent docker-compose in Higgins. Instead, we should leverage existing libraries/tools if we can. Frankly, I don’t think Higgins should interpret any docker-compose like DSL in server, but maybe it is a good idea to have a CLI extension to interpret specific

[openstack-dev] [Higgins] Proposing Eli Qiao to be a Higgins core

2016-05-31 Thread Hongbin Lu
Hi team, I wrote this email to propose Eli Qiao (taget-9) to be a Higgins core. Normally, the requirement to join the core team is to consistently contribute to the project for a certain period of time. However, given the fact that the project is new and the initial core team was formed based

[openstack-dev] [Higgins] Call for contribution for Higgins API design

2016-05-31 Thread Hongbin Lu
Hi team, As discussed in the last team meeting, we agreed to define core use cases for the API design. I have created a blueprint for that. We need an owner of the blueprint and it requires a spec to clarify the API design. Please let me know if you interest in this work (it might require a

Re: [openstack-dev] [Higgins] Call for contribution for Higgins API design

2016-05-31 Thread Hongbin Lu
Sheel, Thanks for taking the responsibility. Assigned the BP to you. As discussed, please submit a spec for the API design. Feel free to let us know if you need any help. Best regards, Hongbin From: Sheel Rana Insaan [mailto:ranasheel2...@gmail.com] Sent: May-31-16 9:23 PM To: Hongbin Lu Cc

Re: [openstack-dev] [higgins] Should we rename "Higgins"?

2016-05-31 Thread Hongbin Lu
Shu, According to the feedback from the last team meeting, Gatling doesn't seem to be a suitable name. Are you able to find an alternative name? Best regards, Hongbin > -Original Message- > From: Shuu Mutou [mailto:shu-mu...@rf.jp.nec.com] > Sent: May-24-16 4:30 AM > To:

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

2016-06-02 Thread Hongbin Lu
ng 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 > > -Original Message- > From: Hongbin Lu [mailto:hongbin...@huawei.com] > Sent: Thursday,

Re: [openstack-dev] [higgins] Continued discussion from the last team meeting

2016-05-26 Thread Hongbin Lu
container hosts(baremetal and VM) automatically, but manual intervention could be necessary in many pratical use cases. But I suggest to hide these API interfaces from endusers since it's not their responsibility to manage those hosts. Thanks. 2016-05-25 4:55 GMT+08:00 Hongbin Lu <hong

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

2016-06-01 Thread Hongbin Lu
; From: Hongbin Lu > Sent: June-01-16 11:44 AM > To: OpenStack Development Mailing List (not for usage questions) > Subject: RE: [openstack-dev] [magnum] Discuss the idea of manually > managing the bay nodes > > Hi team, > > A blueprint was created for tracking this idea: >

[openstack-dev] [magnum][lbaas] Operator-facing installation guide

2016-06-01 Thread Hongbin Lu
Hi lbaas team, I wonder if there is an operator-facing installation guide for neutron-lbaas. I asked that because Magnum is working on an installation guide [1] and neutron-lbaas is a dependency of Magnum. We want to link to an official lbaas guide so that our users will have a completed

Re: [openstack-dev] [magnum] Discuss the idea of manually managing the bay nodes

2016-06-01 Thread Hongbin Lu
to specify the deleting node. > So we should manage “node” individually. > > For example: > $ magnum node-create —bay … > $ magnum node-list —bay > $ magnum node-delete $NODE_UUID > > Anyway, if magnum want to manage a lifecycle of container > infrastructure. > This

  1   2   3   4   5   >