Re: [openstack-dev] [magnum] Mesos Conductor
> > > > @hongin, @adrian I agree with you. So can we go ahead with magnum > container-create(delete) ... for mesos bay (which actually create > mesos(marathon) app internally)? > > @jay, yes we multiple frameworks which are using mesos lib. But the mesos > bay we are creating uses marathon. And we had discussion in irc on this > topic, and I was asked to implement initial version for marathon. And agree > with you to have unified client interface for creating pod,app. > > Regards > Bharath T > > > Date: Thu, 19 Nov 2015 10:01:35 +0800 > From: jay.lau@gmail.com<mailto:jay.lau@gmail.com> > To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [magnum] Mesos Conductor > > +1. > > One problem I want to mention is that for mesos integration, we cannot > limited to Marathon + Mesos as there are many frameworks can run on top of > Mesos, such as Chronos, Kubernetes etc, we may need to consider more for > Mesos integration as there is a huge eco-system build on top of Mesos. > > On Thu, Nov 19, 2015 at 8:26 AM, Adrian Otto <adrian.o...@rackspace.com > <mailto:adrian.o...@rackspace.com>> wrote: > > Bharath, > > I agree with Hongbin on this. Let’s not expand magnum to deal with apps or > appgroups in the near term. If there is a strong desire to add these > things, we could allow it by having a plugin/extensions interface for the > Magnum API to allow additional COE specific features. Honestly, it’s just > going to be a nuisance to keep up with the various upstreams until they > become completely 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, and have it interact with the > marathon API directly rather than trying to represent those resources in > Magnum. If that tool became popular, then we could revisit this topic for > further consideration. > > Adrian > > > On Nov 18, 2015, at 3:21 PM, Hongbin Lu <hongbin...@huawei.com hongbin...@huawei.com>> wrote: > > > > 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 > implement a wrapper API to offer what native tool already offers. However, > if you can point out a valid use case to wrap the API, I will give it more > thoughts. > > > > Best regards, > > Hongbin > > > > [1] https://docs.mesosphere.com/using/cli/marathonsyntax/ > > > > From: bharath thiruveedula [mailto:bharath_...@hotmail.com bharath_...@hotmail.com>] > > Sent: November-18-15 1:20 PM > > To: openstack-dev@lists.openstack.org openstack-dev@lists.openstack.org> > > Subject: [openstack-dev] [magnum] Mesos Conductor > > > > Hi all, > > > > I am working on the blueprint [1]. As per my understanding, we have two > resources/objects in mesos+marathon: > > > > 1)Apps: combination of instances/containers running on multiple hosts > representing a service.[2] > > 2)Application Groups: Group of apps, for example we can have database > application group which consists mongoDB app and MySQL App.[3] > > > > So I think we need to have two resources 'apps' and 'appgroups' in mesos > conductor like we have pod and rc for k8s. And regarding 'magnum container' > command, we can create, delete and retrieve container details as part of > mesos app itself(container = app with 1 instance). Though I think in mesos > case 'magnum app-create ..." and 'magnum container-create ...' will use the > same REST API for both cases. > > > > Let me know your opinion/comments on this and correct me if I am wrong > > > > [1]https://blueprints.launchpad.net/magnum/+spec/mesos-conductor. > > [2]https://mesosphere.github.io/marathon/docs/application-basics.html > > [3]https://mesosphere.github.io/marathon/docs/application-groups.html > > > > > > Regards > > Bharath T > > > __ > > OpenStack Development Mailing List (not for usage questions) > > Unsubscribe: > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe< > http://lists.openstack.org/?subject:unsubscribe> > > http://lists.openstack.org/cgi-bin/m
[openstack-dev] [Murano] Does Murano support version management?
Hi, I have a question for Murano: Suppose I want to manage two different version Spark packages, does Murano can enable me create one Application in application catalog but can enable me select different version spark packages to install? -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Magnum] New Core Reviewers
Welcome Ton and Egor!! On Wed, Feb 3, 2016 at 12:04 AM, Adrian Otto <adrian.o...@rackspace.com> wrote: > Thanks everyone for your votes. Welcome Ton and Egor to the core team! > > Regards, > > Adrian > > > On Feb 1, 2016, at 7:58 AM, Adrian Otto <adrian.o...@rackspace.com> > wrote: > > > > Magnum Core Team, > > > > I propose Ton Ngo (Tango) and Egor Guz (eghobo) as new Magnum Core > Reviewers. Please respond with your votes. > > > > Thanks, > > > > Adrian Otto > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay
Hi Magnum, The current mesos bay only include mesos and marathon, it is better to enhance the mesos bay have more components and finally enhance it to a DCOS which focus on container service based on mesos. For more detail, please refer to https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/ The mesosphere now has a template on AWS which can help customer deploy a DCOS on AWS, it would be great if Magnum can also support it based on OpenStack. I filed a bp here https://blueprints.launchpad.net/magnum/+spec/mesos-dcos , please show your comments if any. -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Enhance Mesos bay to a DCOS bay
Yes, that's exactly what I want to do, adding dcos cli and also add Chronos to Mesos Bay to make it can handle both long running services and batch jobs. Thanks, On Fri, Mar 25, 2016 at 5:25 PM, Michal Rostecki <michal.roste...@gmail.com> wrote: > On 03/25/2016 07:57 AM, Jay Lau wrote: > >> Hi Magnum, >> >> The current mesos bay only include mesos and marathon, it is better to >> enhance the mesos bay have more components and finally enhance it to a >> DCOS which focus on container service based on mesos. >> >> For more detail, please refer to >> >> https://docs.mesosphere.com/getting-started/installing/installing-enterprise-edition/ >> >> The mesosphere now has a template on AWS which can help customer deploy >> a DCOS on AWS, it would be great if Magnum can also support it based on >> OpenStack. >> >> I filed a bp here >> https://blueprints.launchpad.net/magnum/+spec/mesos-dcos , please show >> your comments if any. >> >> -- >> Thanks, >> >> Jay Lau (Guangya Liu) >> >> > Sorry if I'm missing something, but isn't DCOS a closed source software? > > However, the "DCOS cli"[1] seems to be working perfectly with Marathon and > Mesos installed by any way if you configure it well. I think that the thing > which can be done in Magnum is to make the experience with "DOCS" tools as > easy as possible by using open source components from Mesosphere. > > Cheers, > Michal > > [1] https://github.com/mesosphere/dcos-cli > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum-ui] Proposed Core addition, and removal notice
+1, thanks for the great work on magnum UI, Shu Muto! On Sun, Mar 6, 2016 at 12:52 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > +1 > > BTW, I am magnum core, not magnum-ui core. Not sure if my vote is counted. > > Best regards, > Hongbin > > -Original Message- > From: Adrian Otto [mailto:adrian.o...@rackspace.com] > Sent: March-04-16 7:29 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: [openstack-dev] [magnum-ui] Proposed Core addition, and removal > notice > > Magnum UI Cores, > > I propose the following changes to the magnum-ui core group [1]: > > + Shu Muto > - Dims (Davanum Srinivas), by request - justified by reduced activity > level. > > Please respond with your +1 votes to approve this change or -1 votes to > oppose. > > Thanks, > > Adrian > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Seek advices for a licence issue
Yes, I will contribute to this project. Thanks On Sat, Apr 23, 2016 at 8:44 PM, Hongbin Lu <hongbin...@huawei.com> wrote: > Jay, > > > > I will discuss the proposal [1] in the design summit. Do you plan to > contribute on this efforts or someone from DCOS community interest to > contribute? > > > > [1] https://blueprints.launchpad.net/magnum/+spec/mesos-dcos > > > > Best regards, > > Hongbin > > > > *From:* Jay Lau [mailto:jay.lau@gmail.com] > *Sent:* April-22-16 12:12 AM > *To:* OpenStack Development Mailing List (not for usage questions) > *Subject:* Re: [openstack-dev] [magnum] Seek advices for a licence issue > > > > I got confirmation from Mesosphere that we can use the open source DC/OS > in Magnum now, it is a good time to enhance the Mesos Bay to Open Source > DCOS. > > From Mesosphere > > DC/OS software is licensed under the Apache License, so you should feel > free to use it within the terms of that license. > --- > > Thanks. > > > > On Thu, Apr 21, 2016 at 5:35 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > > Hi Mark, > > > > I have went though the announcement in details, From my point of view, it > seems to resolve the license issue that was blocking us in before. I have > included the Magnum team in ML to see if our team members have any comment. > > > > Thanks for the support from foundation. > > > > Best regards, > > Hongbin > > > > *From:* Mark Collier [mailto:m...@openstack.org] > *Sent:* April-19-16 12:36 PM > *To:* Hongbin Lu > *Cc:* foundat...@lists.openstack.org; Guang Ya GY Liu > *Subject:* Re: [OpenStack Foundation] [magnum] Seek advices for a licence > issue > > > > Hopefully today’s news that Mesosphere is open major sourcing components > of DCOS under an Apache 2.0 license will make things easier: > > > > https://mesosphere.com/blog/2016/04/19/open-source-dcos/ > > > > I’ll be interested to hear your take after you have time to look at it in > more detail, Hongbin. > > > > Mark > > > > > > > > On Apr 9, 2016, at 10:02 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > > > > Hi all, > > > > A brief introduction to myself. I am the Magnum Project Team Lead (PTL). > Magnum is the OpenStack container service. I wrote this email because the > Magnum team is seeking clarification for a licence issue for shipping > third-party software (DCOS [1] in particular) and I was advised to consult > OpenStack Board of Directors in this regards. > > > > Before getting into the question, I think it is better to provide some > backgroup information. A feature provided by Magnum is to provision > container management tool on top of a set of Nova instances. One of the > container management tool Magnum supports is Apache Mesos [2]. Generally > speaking, Magnum ships Mesos by providing a custom cloud image with the > necessary packages pre-installed. So far, all the shipped components are > open source with appropriate license, so we are good so far. > > > > Recently, one of our contributors suggested to extend the Mesos support to > DCOS [3]. The Magnum team is unclear if there is a license issue for > shipping DCOS, which looks like a close-source product but has community > version in Amazon Web Services [4]. I want to know what are the appropriate > actions Magnum team should take in this pursuit, or we should stop pursuing > this direction further? Advices are greatly appreciated. Please let us know > if we need to provide further information. Thanks. > > > > [1] https://docs.mesosphere.com/ > > [2] http://mesos.apache.org/ > > [3] https://blueprints.launchpad.net/magnum/+spec/mesos-dcos > > [4] > https://docs.mesosphere.com/administration/installing/installing-community-edition/ > > > > Best regards, > > Hongbin > > > > > > > > _______ > Foundation mailing list > foundat...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > > -- > > Thanks, > > Jay Lau (Guangya Liu) > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [magnum] Seek advices for a licence issue
I got confirmation from Mesosphere that we can use the open source DC/OS in Magnum now, it is a good time to enhance the Mesos Bay to Open Source DCOS. From Mesosphere DC/OS software is licensed under the Apache License, so you should feel free to use it within the terms of that license. --- Thanks. On Thu, Apr 21, 2016 at 5:35 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > Hi Mark, > > > > I have went though the announcement in details, From my point of view, it > seems to resolve the license issue that was blocking us in before. I have > included the Magnum team in ML to see if our team members have any comment. > > > > Thanks for the support from foundation. > > > > Best regards, > > Hongbin > > > > *From:* Mark Collier [mailto:m...@openstack.org] > *Sent:* April-19-16 12:36 PM > *To:* Hongbin Lu > *Cc:* foundat...@lists.openstack.org; Guang Ya GY Liu > *Subject:* Re: [OpenStack Foundation] [magnum] Seek advices for a licence > issue > > > > Hopefully today’s news that Mesosphere is open major sourcing components > of DCOS under an Apache 2.0 license will make things easier: > > > > https://mesosphere.com/blog/2016/04/19/open-source-dcos/ > > > > I’ll be interested to hear your take after you have time to look at it in > more detail, Hongbin. > > > > Mark > > > > > > > > On Apr 9, 2016, at 10:02 AM, Hongbin Lu <hongbin...@huawei.com> wrote: > > > > Hi all, > > > > A brief introduction to myself. I am the Magnum Project Team Lead (PTL). > Magnum is the OpenStack container service. I wrote this email because the > Magnum team is seeking clarification for a licence issue for shipping > third-party software (DCOS [1] in particular) and I was advised to consult > OpenStack Board of Directors in this regards. > > > > Before getting into the question, I think it is better to provide some > backgroup information. A feature provided by Magnum is to provision > container management tool on top of a set of Nova instances. One of the > container management tool Magnum supports is Apache Mesos [2]. Generally > speaking, Magnum ships Mesos by providing a custom cloud image with the > necessary packages pre-installed. So far, all the shipped components are > open source with appropriate license, so we are good so far. > > > > Recently, one of our contributors suggested to extend the Mesos support to > DCOS [3]. The Magnum team is unclear if there is a license issue for > shipping DCOS, which looks like a close-source product but has community > version in Amazon Web Services [4]. I want to know what are the appropriate > actions Magnum team should take in this pursuit, or we should stop pursuing > this direction further? Advices are greatly appreciated. Please let us know > if we need to provide further information. Thanks. > > > > [1] https://docs.mesosphere.com/ > > [2] http://mesos.apache.org/ > > [3] https://blueprints.launchpad.net/magnum/+spec/mesos-dcos > > [4] > https://docs.mesosphere.com/administration/installing/installing-community-edition/ > > > > Best regards, > > Hongbin > > > > > > > > ___ > Foundation mailing list > foundat...@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/foundation > > > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [keystone] Can anyone share some experience for how to configure keystone work with https
Hi, Does anyone have some experience or some document for how to configure keystone work with https? If so, can you please help share with me or show some links that can help? -- Thanks, Jay Lau (Guangya Liu) __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
