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
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
te?
>
>
>
> [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)
ere.com/administration/installing/installing-community-edition/
>
>
>
> Best regards,
>
> Hongbin
>
>
>
>
>
>
>
> ___
> Foundation mailing list
> foundat...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/found
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
wrote:
> On 03/25/2016 07:57 AM, Jay Lau wrote:
>
>> Hi Magnum,
.
--
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 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 (Gua
Stack 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)
| NULL| auto_increment |
>> > >>
>> > >> | created_at | datetime | YES | | NULL||
>> > >>
>> > >> | updated_at | datetime | YES | | NULL||
>> > >>
>> > >> | deleted_at | datetime
he case we could check the maximum
>> allowed number of (or access rate of) whatever lower level resource before
>> requesting it, and raising an understandable error. I see that as an
>> enhancement rather than a must-have. In all honesty that feature is
>> probably more c
uestions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org
> ?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
> __
> OpenStack Development Mailing
honesty that feature is
> probably more complicated than it's worth in terms of value.
>
> --
>
> Adrian
>
>
> On Dec 20, 2015, at 6:36 AM, Jay Lau wrote:
>
> I also have the same concern with Lee, as Magnum depend on HEAT and HEAT
> need call nova, cind
t; 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: opensta
me 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://mesosph
ely containerize
> some COE daemons, but we don’t have to containerize **all** COE daemons.
>
>
>
> [1] https://blueprints.launchpad.net/magnum/+spec/mesos-bay-with-coreos
>
>
>
> Best regards,
>
> Hongbin
>
>
>
> *From:* Jay Lau [mailto:jay.lau@gm
No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193
>
> ----
> Follow your heart. You are miracle!
>
> [image: Inactive hide details for Jay Lau ---26/11/2015 07:15:59 am---Hi,
> It is becoming more and more popular to use docker conta
want to upgrade, just update the dockerfile is enough. Comments?
--
Thanks,
Jay Lau (Guangya Liu)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org
-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 q
t; >
> > [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
> &
Cool, thanks Ton!
On Thu, Nov 19, 2015 at 7:07 AM, Ton Ngo wrote:
> The slides for the Tokyo talk is available on slideshare:
>
> http://www.slideshare.net/huengo965921/exploring-magnum-and-senlin-integration-for-autoscaling-containers
>
> Ton,
>
>
> [image: Inactive
signal for Magnum and the Magmum can leverage those features
to unify the client interface for different COEs. i.e we can use "magnum
app create" to create pod, rc, service, pv, pvc even marathon service etc.
Just some early thinking from my side...
Thanks!
On Thu, Nov 19, 2015 at 10:01 AM, J
gt; >
> >
> > Regards
> > Bharath T
> >
> __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://l
t; --
> Thanks,
>
> Ryan Rossiter (rlrossit)
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org openstack-dev-requ...@lists.openstack.org>?subject:unsubscri
gt;
>> As one of the core reviewers who couldn't make the summit, this sounds
>> like a very exciting direction to go in. I'd love to see more docs (I
>> realize it's still early) on how mesos will be utilized and what
>> additional frameworks may be us
gt; Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>>
>> --
>> Best wishes!
>> Baohua
>>
p://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
>
> --
>
> Davanum Srinivas :: https://twitter.com/dims
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Uns
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.o
be shared by
multi-tenants, the reason is that sometimes, creating a bay maybe time
consuming, and enabling the bay shared by multi-tenant can save some time
for some users.
Any comments on this?
--
Thanks,
Jay Lau (Guangya Liu
Anyone who have some comments/suggestions on this? Thanks!
On Mon, Sep 14, 2015 at 3:57 PM, Jay Lau wrote:
> Hi Vikas,
>
> Thanks for starting this thread. Here just show some of my comments here.
>
> The reason that Magnum want to get k8s resource via k8s API including two
_
> 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)
___
Hi,
I see that we already have a magnum ui team, just wondering what is the
current status of this project? I'm planning a PoC and want to see if there
are some current magnum ui work that I can leverage.
--
Thanks,
Jay Lau (Guangy
trict Beijing P.R.China
> 100193
>
> ------------
> Follow your heart. You are miracle!
>
> [image: Inactive hide details for Jay Lau ---08/04/2015 05:51:33 AM---Hi
> Suro, Yes, I did not see a strong reason for ad
stone.
>
> Now in magnum, we may choose to model it after nova, but nova really has a
> bunch of backend services, viz. nova-conductor, nova-cert, nova-scheduler,
> nova-consoleauth, nova-compute[x N], whereas magnum not.
>
> For magnum, at this point creating 'service-list&#
Hi Suro and others, comments on this? Thanks.
2015-07-30 5:40 GMT-04:00 Jay Lau :
> Hi Suro,
>
> In my understanding, even other CoE might have service/pod/rc concepts in
> future, we may still want to distinguish the "magnum service-list" with
> "magnum coe-serv
e 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
> COE, adding prefix to COE-specific command is unavoidable.
>
>
>
> Best regards,
>
> Hongbi
015-07-28 UTC 2200 Tuesday
>
> On 7/21/15 4:54 PM, SURO wrote:
>
> Hi all, [special attention: Jay Lau] The bp[1] registered, asks for the
> following implementation -
>
>- 'magnum service-list' should be similar to 'nova service-list'
>- '
Thanks Adrian, we can talk later in the IRC meeting.
2015-07-28 4:07 GMT-04:00 Adrian Otto :
> Jay,
>
> Yes, it is on the agenda.
>
> Thanks,
>
> Adrian
>
> On Jul 27, 2015, at 8:32 AM, Jay Lau wrote:
>
> Adrian,
>
> Can we put hyper as a topic for
___
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe: openstack-dev-requ...@lists.openstack.org
>>> <mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
>>> http://lists.open
?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> ______
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@list
nal message
> From: Peng Zhao
> Date: 07/19/2015 5:36 AM (GMT-08:00)
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [magnum][bp] Power Magnum to run on metal
&
ut produce bays that use Hyper instead of a Docker host. Everywhere
> we currently offer CoreOS as an option we could also offer Hyper as an
> alternative, with some caveats.
>
>
>
> There may be some caveats/drawbacks to consider before committing to a
> Hyper integration. I’ll be asking
e Hyper instead of a Docker host. Everywhere
> we currently offer CoreOS as an option we could also offer Hyper as an
> alternative, with some caveats.
>
> There may be some caveats/drawbacks to consider before committing to a
> Hyper integration. I’ll be asking those of Peng also
th K8S. Mesos takes a bit more efforts, but still
>> straightforward.
>>
>> We expect to finish both integration in v0.4 early August.
>>
>> Best,
>> Peng
>>
>> -
>> Hyper - Make VM run like Co
August.
>
> Best,
> Peng
>
> -
> Hyper - Make VM run like Container
>
>
>
> On Thu, Jul 16, 2015 at 3:47 PM, Jay Lau wrote:
>
>> Hi Peng,
>>
>>
>> Just want to get more for Hyper. If we create a hyper bay, then can I set
>> up multipl
gt;>
>>
>> __________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@lists.openstack.org
>> ?subject:unsubscribe
>> http://lists.openstack
s: Building 28(Ring Building), ZhongGuanCun Software Park,
> No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China
>100193
>
>
>
>Follow your heart. You are miracle
penstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
> OpenStack Developme
Hi Sahara Team,
Just notice that the CloudBreak (https://github.com/sequenceiq/cloudbreak)
also support running on top of OpenStack, can anyone show me some
difference between Sahara and CloudBreak when both of them using OpenStack
as Infrastructure Manager?
--
Thanks,
Jay Lau (Guangya Liu
>
> Follow your heart. You are miracle!
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.ope
ot;bay_uuid": "$BAY_UUID",
> "name": "test-container",
> "image_id": "cirros",
> "command": "ping -c 4 8.8.8.8"
> }
> END
> $ magnum container-create < ~/container.json
>
>
> The key difference in this example,
I have filed a bp for this
https://blueprints.launchpad.net/magnum/+spec/auto-generate-name Thanks
2015-06-04 14:14 GMT+08:00 Jay Lau :
> Thanks Adrian, I see. Clear now.
>
> 2015-06-04 11:17 GMT+08:00 Adrian Otto :
>
>> Jay,
>>
>> On Jun 3, 2015, at 6:42 PM,
y.
>
> Thanks
> Alex Xu
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-req
Thanks Adrian, I see. Clear now.
2015-06-04 11:17 GMT+08:00 Adrian Otto :
> Jay,
>
> On Jun 3, 2015, at 6:42 PM, Jay Lau wrote:
>
> Thanks Adrian, some questions and comments in-line.
>
> 2015-06-03 10:29 GMT+08:00 Adrian Otto :
>
>> I have reflected on this fur
Windisch
>
> __
> 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
>
>
>
>
gt;
Just curious why do we need this feature? Different Magnum clusters might
using different CoE engine. So you are mentioning the case all of the
Magnum clusters are using same CoE engine? If so, yes, this should be made
clear in configuration file.
Adrian
>
> On Jun 2, 2015, at 8:44 PM, J
ny of the defaults, it will just work. You can't do 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 Devel
APIs (it looks the Marathon’s object ‘app’ can be leveraged
>to operate a docker container). The effect is that Magnum will have a set
>of common abstractions that is implemented differently by different bay
>type.
>2. Do manage a few Marathon objects (i.e. app
me way you use Nova if you want, by adding names to all
> resources. I don't see the wisdom in forcing that style of use without a
> technical reason for it.
>
> Thanks,
>
> Adrian
>
> On May 31, 2015, at 4:43 PM, Jay Lau wrote:
>
>
> Just want to use ML to tr
2015-06-01 21:54 GMT+08:00 Jay Pipes :
> 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.
>>
>&g
rxtx-factor ] [--is-public ]
Please show your comments if any.
--
Thanks,
Jay Lau (Guangya Liu)
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-r
t;
> -steve
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/li
-vs-aurora-and-their-purposes
> [6] https://github.com/mesosphere/kubernetes-mesos
>
> --
> Add support for mesos bay type
> https://blueprints.launchpad.net/magnum/+spec/mesos-bay-type
>
>
>
> __
&
/05/video-vancouver-openstack-keynote-with-magnum-and-kubrnetes/
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/
> 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)
estions)
> 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 Develop
l use the container endpoints of our API to
> interact with the bay.
>
>
>
> --Andrew
>
> --
> *From:* Jay Lau
> *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 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
ts.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)
Un
>> 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
>>
4a71-8d9c-580d88fd4797", "ip_address":
"192.168.0.62"} |
+--+--+---+---------+
--
Thanks,
Jay Lau (Guangya Liu)
ch other. Any further
> suggestion?
>
> Thanks,
> Hongbin
>
>
> On Sun, Feb 22, 2015 at 3:58 AM, Jay Lau 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
orth for presentation.
>
>
>
> Thanks & Regards,
>
> Nikunj
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> htt
a bug.
>
> Thanks,
> Hongbin
>
> [1]
> https://github.com/stackforge/magnum/blob/master/doc/source/dev/dev-quickstart.rst#exercising-the-services-using-devstack
>
> __
> OpenStack Development Mailing List (not for usage q
enstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe
r at a later point. I’m willing to accept
> that tradeoff for a quick delivery of a Docker specific scheduler that we
> can learn from and iterate.
>
> Cheers,
>
> Adrian
>
> On Feb 9, 2015, at 10:57 PM, Jay Lau wrote:
>
> Thanks Steve, just want to discuss more f
Thanks Steve, just want to discuss more for this. Then per Andrew's
comments, we need a generic scheduling interface, but if our focus is
native docker, then does this still needed? Thanks!
2015-02-10 14:52 GMT+08:00 Steven Dake (stdake) :
>
>
> From: Jay Lau
> Rep
nstack.org?subject:unsubscribe
>> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> __________
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
&g
> Unsubscribe:
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
> __
> OpenStack Development Mailing List (not for
m, but I’m sure the swarm upstream is
> busy with requests and this may be difficult to achieve.
>
> Regards
> -steve
>
>
> __________
>
/F17/Neutron.template
I will try to file a bp to see if we can introduce a new source such as
OS::Heat::PortPool etc to heat.
Thanks!
2015-01-27 13:30 GMT+08:00 Qiming Teng :
> On Tue, Jan 27, 2015 at 10:34:47AM +0800, Jay Lau wrote:
> > 2015-01-27 10:28 GMT+08:00 Qiming Teng :
> >
&
>>
>
> __
> 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/openstac
2015-01-27 10:28 GMT+08:00 Qiming Teng :
> On Tue, Jan 27, 2015 at 10:13:59AM +0800, Jay Lau wrote:
> > Greetings,
> >
> > I have a question related to MAC and IP binding, I know that we can
> create
> > a port to bind a private IP and MAC together then create VM us
t find a
solution for this, does anyone can give some suggestions for how to
configure this in heat template to achieve this goal?
--
Thanks,
Jay Lau (Guangya Liu)
__
OpenStack Development Mailing List (not for usage q
want to discuss is still network, currently, magnum only support
neutron, what about nova-network support?
2015-01-19 0:39 GMT+08:00 Steven Dake :
> On 01/18/2015 09:23 AM, Jay Lau wrote:
>
> Thanks Steven, more questions/comments in line.
>
> 2015-01-19 0:11 GMT+08:00 Steven Dak
Thanks Steven, more questions/comments in line.
2015-01-19 0:11 GMT+08:00 Steven Dake :
> On 01/18/2015 06:39 AM, Jay Lau wrote:
>
> Thanks Steven, just some questions/comments here:
>
> 1) For native docker support, do we have some project to handle the
> network? The cur
ad.net/magnum/milestone-1
>
> Regards,
> -steve
>
>
> [1] https://review.openstack.org/#/admin/groups/473,members
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lis
s when host was
added to compute_nodes table.
2014-12-30 14:52 GMT+08:00 Lingxian Kong :
> Thanks, Jay Pipes and Jay Lau, for your reply!
>
> Just as what Jay Lau said, 'nova hypervisor-show '
> indeed returns host ip address, and there are more other information
> included
Does "nova hypervisor-show" help? It already include the host ip address.
2014-12-29 21:26 GMT+08:00 Jay Pipes :
> On 12/29/2014 06:51 AM, Lingxian Kong wrote:
>
>> Hi Stackers:
>>
>> As for now, we can get the 'host name', 'service' and 'availability
>> zone' of a host through the CLI command 'n
There is no problem for your cluster, it is working well. With nova docker
driver, you need to use namespace to check the network as you did:
2014-12-29 13:15 GMT+08:00 Iván Chavero :
> Hello,
>
> I've installed OpenStack with Docker as hypervisor on a cubietruck,
> everything
> seems to work ok
So you are using heat docker driver but not nova docker driver, right?
If you are using nova docker driver, then the container was treated as VM
and you can do monitoring and auto scaling with heat.
But with heat docker driver, it talk to docker host directly which you need
to define in HEAT tem
Cool, Thierry! I see. This is really what I want ;-)
Thanks!
2014-12-01 16:51 GMT+08:00 Thierry Carrez :
> Jay Lau wrote:
> >
> > When I review a patch for OpenStack, after review finished, I want to
> > check more patches for this project and then after click the "Pro
I'm OK if all reviewers agree on this proposal, I may need to bookmark the
projects that I want to review. ;-)
2014-12-01 14:35 GMT+08:00 OpenStack Dev :
> Jay this has been informed & discussed, pre & post the gerrit upgrade :)
>
>
> On Mon Dec 01 2014 at 12:00:02 PM Ja
t: jiche...@cn.ibm.com
> > Phone: +86-10-82454158
> > Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
> > District, Beijing 100193, PRC
> >
> > [image removed] Jay Lau ---12/01/2014 01:56:48 PM---When I review a
> > patch for OpenStack, after review fi
When I review a patch for OpenStack, after review finished, I want to check
more patches for this project and then after click the "Project" content
for this patch, it will **not** jump to all patches but project
description. I think it is not convenient for a reviewer if s/he wants to
review more
The current behavior is not flexible to customer, I see that we have a
blueprint want to enhance this behavior.
https://blueprints.launchpad.net/heat/+spec/autoscaling-api-resources
https://wiki.openstack.org/wiki/Heat/AutoScaling
In Use Case section, we have the following:
=
Hi Alex,
You can continue the work https://review.openstack.org/#/c/88983/ from here
;-)
2014-10-29 13:42 GMT+08:00 Chen CH Ji :
> Yes, I remember that spec might talk about local storage (in local db?)
> and it can be the root cause
>
> And I think we need persistent storage otherwise the sched
This is also a use case for Congress, please check use case 3 in the
following link.
https://docs.google.com/document/d/1ExDmT06vDZjzOPePYBqojMRfXodvsk0R8nRkX-zrkSw/edit#
2014-10-14 5:59 GMT+08:00 Russell Bryant :
> Nice timing. I was working on a blog post on this topic.
>
> On 10/13/2014 05:4
Hi Jay,
There was actually a discussion about file a blueprint for object
notification http://markmail.org/message/ztehzx2wc6dacnk2
But for patch https://review.openstack.org/#/c/107954/ , I'd like we keep
it as it is now to resolve the requirement of server group notifications
for 3rd party clie
Just go through the tutorial, it is very clear, thanks Tim and the Congress
team.
In the README.rst, the link http://docs.openstack.org/developer/congress
cannot be opened.
One minor comments, I noticed that you are using Neutron for the example,
can you please add another case without neutron? N
;
> On Aug 21, 2014, at 7:54 AM, Jay Lau wrote:
>
> I know that Congress is still under development, but it is better that
> it can provide some info for "How to use it" just like docker
> https://wiki.openstack.org/wiki/Docker , this might attract more people
> contrib
1 - 100 of 222 matches
Mail list logo
