I'll bet I am not the only developer who is not highly competent with
bridges and tunnels, Open VSwitch, Neutron configuration, and how DevStack
transmutes all those. My bet is that you would have more developers using
Neutron if there were an easy-to-find and easy-to-follow recipe to use, to
"CARVER, PAUL" wrote on 08/14/2014 09:35:17 AM:
> Mike Spreitzer [mailto:mspre...@us.ibm.com] wrote:
>
> >I'll bet I am not the only developer who is not highly competent with
> >bridges and tunnels, Open VSwitch, Neutron configuration, and how
DevStack
> &g
"CARVER, PAUL" wrote on 08/14/2014 09:35:17 AM:
> Mike Spreitzer [mailto:mspre...@us.ibm.com] wrote:
>
> >I'll bet I am not the only developer who is not highly competent with
> >bridges and tunnels, Open VSwitch, Neutron configuration, and how
DevStack
> &g
Anita Kuno wrote on 08/15/2014 10:38:20 AM:
> OpenStack is OpenStack. The use of openstack is also acceptable in our
> development conversations.
>
> OS or os is operating system. I am starting to see some people us OS or
> os to mean OpenStack. This is confusing and also incorrect[0].
>
> ...
Anita Kuno wrote on 08/15/2014 01:08:44 PM:
> ...
> I think you hit the nail on the head here, Russell, "it's fine in the
> right context".
>
> The definition of the right context however is somewhat elusive. I have
> chosen (it is my own fault) to place myself in the area where the folks
> I de
Russell Bryant wrote on 08/15/2014 01:49:40 PM:
> ...
> but surely when it comes to learning OpenStack itself, the OpenStack
> community, dev processes, tools, etc this has got to be extremely
> far down the list of barriers to entry.
No argument there. I am spending decimal orders of magn
In particular, I tried to run DevStack inside an LXC a few months ago. I
discovered that DevStack (presumably for the sake of cinder-volume)
pre-reqs a system package named tgt, and tgt does not succeed to install
inside an LXC (the install script launches the daemon, but the daemon
launch fai
Jay Lau wrote on 08/14/2014 08:54:56 AM:
> I see a few mentions of OpenStack services themselves being
> containerized in Docker. Is this a serious trend in the community?
>
>
http://allthingsopen.com/2014/02/12/why-containers-for-openstack-services/
>
It looks to me like the problem addresse
There has been a lot of discussion around these issues, let me see if I
can break it down into pieces, hopefully in a way that allows some
progress on one of them first.
I continue to focus on the timeless version of the problem, in which the
placement question is simply where can we put some g
This is primarily an issue for Nova.
Mike Spreitzer/Watson/IBM@IBMUS wrote on 08/20/2014 01:21:24 AM:
> From: Mike Spreitzer/Watson/IBM@IBMUS
> To: "OpenStack Development Mailing List"
,
> Date: 08/20/2014 01:24 AM
> Subject: [openstack-dev] Separating the issues around s
committed? BTW, I am doing
the following admittedly risky thing: I run DevStack, and make my changes
in /opt/stack/heat/.
Thanks,
Mike
- Forwarded by Mike Spreitzer/Watson/IBM on 08/24/2014 03:03 AM -
From: ubuntu@mjs-dstk-821a (Ubuntu)
To: Mike Spreitzer/Watson/IBM@IBMUS,
Date: 08/24
ommitted? BTW, I am
doing
> > the following admittedly risky thing: I run DevStack, and make my
changes
> > in /opt/stack/heat/.
> >
> > Thanks,
> > Mike
> >
> > - Forwarded by Mike Spreitzer/Watson/IBM on 08/24/2014 03:03 AM
-
> >
&
Morgan Fainberg wrote on 08/24/2014 12:01:37
PM:
> ...
>
> Keystone saw an oddity with the new sample config generator
> (changing how options are sorted and therefore changing the way the
> sample config is rendered). This could be a similar / related issue.
>
> Most of the projects stoppe
t;
> On Sun, Aug 24, 2014 at 11:10 AM, Mike Spreitzer
wrote:
> > What I really need to know is what to do when committing a change that
> > really does require a change in the sample configuration file. Of
course I
> > tried running generate_sample.sh, but `tox -epep8`
You offered to share ideas about a different way to approach spanning AZs
for OS::Heat::AutoScalingGroup. I am interested. Can we discuss it here?
Thanks,
Mike___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/
Steven Hardy wrote on 09/11/2014 04:21:18 AM:
> On Wed, Sep 10, 2014 at 04:44:01PM -0500, Jason Greathouse wrote:
> >I'm trying to find a way to create a set of servers and attach a
new
> >volume to each server.
> >...
>
> Basically creating lots of resource groups for related thin
Background: Health maintenance is very important to users, and I have
users who want to do it now and into the future. Today a Heat user can
write a template that maintains the health of a resource R. The detection
of a health problem can be done by anything that hits a webhook. That
general
Angus Salkeld wrote on 09/18/2014 09:33:56 PM:
> Hi
> I am trying to add some docs to openstack-manuals hot_guide about
> using provider templates : https://review.openstack.org/#/c/121741/
> Mike has suggested we use a different term, he thinks "provider" is
> confusing.
> I agree that at th
Zane Bitter wrote on 11/15/2013 05:59:06 PM:
> On 15/11/13 22:17, Keith Bray wrote:
> > The way I view 2 vs. 4 is that 2 is more complicated and you don't
gain
> > any benefit of availability. If, in 2, your global heat endpoint is
down,
> > you can't update the whole stack. You have to work a
Steve Baker wrote on 11/19/2013 03:40:54 PM:
...
> How to define and deliver this agent is the challenge. Some options are:
> 1) install it as part of the image customization/bootstrapping (golden
> images or cloud-init)
> 2) define a (mustache?) template in the SoftwareConfig which
> os-collect-
Clint Byrum wrote on 11/19/2013 04:28:31 PM:
> From: Clint Byrum
> To: openstack-dev ,
> Date: 11/19/2013 04:30 PM
> Subject: Re: [openstack-dev] [Heat] HOT software configuration
> refined after design summit discussions
>
> Excerpts from Steve Baker's message of 2013-11-19 13:06:21 -0800:
>
Regarding my previous email:
> Steve Baker wrote on 11/19/2013 03:40:54 PM:
> ...
> > How to define and deliver this agent is the challenge. Some options
are:
> > 1) install it as part of the image customization/bootstrapping (golden
> > images or cloud-init)
>
> > 2) define a (mustache?) temp
Steve Baker wrote on 11/20/2013 06:00:47 PM:
...
> > What I meant to convey is "let's give this piece of the interface a
lot of
> > thought". Not "this is wrong to even have." Given a couple of days
now,
> > I think we do need "apply" and "remove". We should also provide really
> > solid example
Clint Byrum wrote on 11/20/2013 05:41:16 PM:
> Autoscaling doesn't really fly with stateful services IMO.
I presume you're concerned about the "auto" part, not the "scaling". Even
a stateful group is something you may want to scale; it just takes a more
complex set of operations to accomplish
Thomas Spatzier wrote on 11/21/2013 02:48:14
AM:
> ...
> Now thinking more about update scenarios (which we can leave for an
> iteration after the initial deployment is working),
I recommend thinking about UPDATE from the start. We should have an
implementation in which CREATE and UPDATE share
I'm still a newbie here, so can not claim my Nova skills are even
"modest". But I'd like to track this, if nothing more.
Thanks,
Mike___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/op
"Daniel P. Berrange" wrote on 11/22/2013 11:32:59
AM:
> > A good example is the current discussion around a new scheduling
> > service. There have been lots of big ideas around this. Robert
Collins
> > just started a thread about a proposal to start this project but with
a
> > very strict sc
I am sorry I missed that session, but am interested in the topic. This is
very relevant to Heat, where we are working on software configuration in
general. I desire that Heat's ability to configure software will meet the
needs of Trove, Savanna, and Murano.
At IBM we worked several Hadoop exa
I am suffering from bug 1266513, when trying to work on nova. For
example, on MacOS 10.8.5, I clone nova and then (following the
instructions at https://wiki.openstack.org/wiki/DependsOnOSX) run `cd
nova; python tools/install_venv.py`. It fails due to PyPI lacking a
sufficiently advanced neta
I am trying to become a bit less of a newbie, and having a bit of
difficulty with basics. Following are some questions, and reviews of the
relevant documentation that I have been able to find (I am trying to
contribute to documentation as well as solve my setup problems). My
driving question
Brant Knudson wrote on 01/09/2014 10:07:27 AM:
> When I was starting out, I ran devstack ( http://devstack.org/ ) on
> an Ubuntu VM. You wind up with a system where you've got a basic
> running OpenStack so you can try things out with the command-line
> utilities, and also do development becau
I want to explore the linkage between the proposed exclusive use filter
and scheduling a little more. At the Icehouse summit I heard the concern
that without advance preparation, there may well be zero hosts that are
acceptable. Why is that not a concern now?
What does the Nova scheduler do n
> From: Sylvain Bauza
>
> Le 22/01/2014 02:50, Jay Pipes a écrit :
> >
> > Yup, agreed. It's difficult to guess what the capacity implications
> > would be without having solid numbers on customer demands for this
> > functionality, including hard data on how long such instances would
> > typical
Jay Pipes wrote on 01/21/2014 08:50:36 PM:
...
> On Tue, 2014-01-21 at 14:28 +, Day, Phil wrote:
> > > >
> > > > I think there is clear water between this and the existing
> aggregate based
> > > isolation. I also think this is a different use case from
> reservations. It's
> > > *mostly*
> From: Khanh-Toan Tran
...
> There is an unexpected line break in the middle of the link, so I post
it
> again:
>
>
https://docs.google.com/document/d/1RfP7jRsw1mXMjd7in72ARjK0fTrsQv1bqolOri
> IQB2Y
The mailing list software keeps inserting that line break. I
re-constructed the URL and look
> From: Steven Dake
...
> The crux of the problem is how do you obtain critical mass for
> custom one-off solutions? Lets assume two possible solutions to
> this problem that these vendors could take. If there are more,
> please feel free to explain them:
>
> 1) Implement a ReST server which
> From: Prasad Vellanki
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 01/21/2014 02:16 AM
> Subject: Re: [openstack-dev] [heat] Sofware Config progress
>
> Steve & Clint
>
> That should work. We will look at implementing a resource that spins
> up a shortlive
Thanks to work by several colleagues, I can share a non-trivial Heat
template for a system that we have been using as an example to work. It
is in the TAR archive here:
https://drive.google.com/file/d/0BypF9OutGsW3Z2JqVTcxaW1BeXc/edit?usp=sharing
Start at connections.yaml. Also in the archive
> From: Georgy Okrokvertskhov
> ...
> Thank you for sharing this. It looks pretty impressive. Could you,
> please some details about DSL syntax, if it is possible?
I will respond briefly, and pass your request along to the people working
on that.
In the Weaver language there are distinct conce
> From: Sean Dague
...
> Realistically, the biggest issue I see with on-boarding is mentoring
> time. Especially with folks completely new to our structure, there is a
> lot of confusing things going on. And OpenStack is a ton to absorb. I
> get pinged a lot on IRC, answer when I can, and sometime
Robert Collins wrote on 02/16/2014 05:26:50
PM:
> I would have expected run_tests.sh to tox which creates a venv, but
> heat seems different. So you'll need to install testrepository via
> your system tox, not one from a venv.
I don't think I have a system tox. `pip list | grep -i tox` comes up
I am trying to figure out how I should be doing unit testing, and
documenting it in https://wiki.openstack.org/wiki/Gerrit_Workflow
Oddly, the situation for Nova seems reversed: run_tests.sh works and tox
does not. See http://paste.openstack.org/show/66969/ for my experiences
with each. Am I
Boris Pavlovic wrote on 02/18/2014 12:55:26 PM:
> What version of tox do you use?
That was using version 1.6.1 (as a workaround to
https://bugs.launchpad.net/openstack-ci/+bug/1274135).
Also, this was a fresh DevStack install (done about an hour or two before
I posted to the list), with a pre
Mike Spreitzer/Watson/IBM@IBMUS wrote on 02/18/2014 01:22:33 PM:
> That was using version 1.6.1 (as a workaround to https://
> bugs.launchpad.net/openstack-ci/+bug/1274135).
>
> Also, this was a fresh DevStack install (done about an hour or two
> before I posted to the list)
"Dean Troyer (Code Review)" wrote on 02/18/2014
05:53:03 PM:
> I'm curious why we haven't seen this before now? I've run on bare
> raring and saucy systems a number of times...need to try again I
suppose...
Yes, I have previously done lots of DevStack installs on post-precise
releases of Ub
I just installed DevStack into raring, and that appeared to work. So I
went on to try `tox` in /opt/stack/nova. My invocation of tox created a
virtual environment using /usr/lib/python2.7/dist-packages/virtualenv.py.
In raring the latest virtualenv is version 1.9.1, which installs pip
version
Zane Bitter wrote on 02/21/2014 12:23:05 PM:
> Yeah, we are overloading the term 'developer' here, since that section
> contains both information that is only useful to developers working on
> Heat itself, and information useful to users developing templates.
At the highest levels of the OpenS
https://bugs.launchpad.net/devstack/+bug/1203680 is literally about Glance
but Nova has the same problem. There is a fix released, but just merging
that fix accomplishes nothing --- we need people who run DevStack to set
the new variable (INSTALL_TESTONLY_PACKAGES). This is something that
nee
Sean Dague wrote on 02/20/2014 02:45:03 PM:
> ...
> That being said, we also need to be a little bit careful about taking
> such a hard line about "supported vs. not" based on only what's in the
> gate. Because if we did the following things would be listed as
> unsupported (in increasing level of
Sean Dague wrote on 02/21/2014 06:09:18 PM:
> On 02/21/2014 05:28 PM, Clark Boylan wrote:
> > ...
> > I would be wary of relying on devstack to configure your unittest
> > environments. Just like it takes over the node you run it on, devstack
> > takes full ownership of the repos it clones and wil
(I added some tags in the subject line, probably should have been there
from the start.)
Thanks guys, for an informative discussion. I have updated
https://wiki.openstack.org/wiki/Gerrit_Workflow and
https://wiki.openstack.org/wiki/Testing to incorporate what I have
learned.
Like Ben I know
Dean Troyer wrote on 02/26/2014 12:53:31 PM:
> Thanks for the updates, but I've massaged the project bits and
> restored/expanded the reasons to consider one or the other option.
Thanks for the further updates. I have just one question about those. One
way to do both unit testing and system (
Dean Troyer wrote on 02/26/2014 03:28:04 PM:
> On Wed, Feb 26, 2014 at 1:09 PM, Mike Spreitzer
wrote:
>> Thanks for the further updates. I have just one question about
>> those. One way to do both unit testing and system (integration)
>> testing is to: git clone you
So far I have found three different sources, and they all say different
things.
http://techs.enovance.com/5991/autoscaling-with-heat-and-ceilometer
http://devstack.org/lib/ceilometer.html
http://docs.openstack.org/developer/ceilometer/install/development.html
Thanks,
Mike
Swapnil Kulkarni wrote on 03/01/2014
12:36:49 AM:
> I am able to configure devstack with ceilometer adding following to
localrc
>
> enable_service ceilometer-acompute ceilometer-acentral ceilometer-
> collector ceilometer-api
> enable_service ceilometer-alarm-notifier ceilometer-alarm-evaluat
Chris Friesen wrote on 04/25/2014 12:23:00
PM:
> I'm looking to add support for server groups to heat. I've got working
> code, but I thought I'd post the overall design here in case people had
> objections.
>
> Basically, what I propose is to add a "class NovaServerGroup" resource.
> Cur
Zane Bitter wrote on 04/25/2014 12:36:00 PM:
> On 25/04/14 12:23, Chris Friesen wrote:
> ...
> > The "LaunchConfiguration" and "Instance" classes would be extended
with
> > an optional "ServerGroup" property. In the "Instance" class if the
> > "ServerGroup" property is set then the group name i
Jay Pipes wrote on 04/25/2014 06:28:38 PM:
> On Fri, 2014-04-25 at 22:00 +, Day, Phil wrote:
> > Hi Jay,
> >
> > I'm going to disagree with you on this one, because:
>
> No worries, Phil, I expected some dissention and I completely appreciate
> your feedback and perspective :)
I myself sit
FYI, here is an example of using those new features in a system of
non-trivial size and complexity. It is similar to an example I exhibited
earler, see
http://lists.openstack.org/pipermail/openstack-dev/2014-February/026606.html
Today's example is simpler in one major way: each of the four "cl
Jay Lau wrote on 04/26/2014 11:41:25 PM:
> Just noticed this email, I have already filed a blueprint related to
> this topic https://blueprints.launchpad.net/heat/+spec/vm-instance-
> group-support
> My idea is that can we add a new field such as "PlacemenetPolicy" to
> AutoScalingGroup? If the
Jay Lau wrote on 04/27/2014 12:31:01 AM:
> I think server group is an important feature especially when working
> with heat auto scaling group, there is already some discussion for this
> http://markmail.org/message/jl5wlx3nr3g53ko5
> The current server group feature does support add/delete a V
Steve Gordon wrote on 04/28/2014 08:58:35 AM:
> - Original Message -
> > Hi Stackers,
> > Proposal
> >
> > Create two new options to nova boot:
> >
> > --near-tag
> > and
> > --not-near-tag
> >
> > The first would tell the scheduler to place the new VM near other VMs
> > having a p
Chris Friesen wrote on 04/28/2014 10:44:46
AM:
> On 04/26/2014 09:41 PM, Jay Lau wrote:
> ...
> > My idea is that can we add a new field such as "PlacemenetPolicy" to
> > AutoScalingGroup? If the value is affinity, then when heat engine
create
> > the AutoScalingGroup, it will first create a se
Chris Friesen wrote on 04/30/2014 06:07:49
PM:
> If we go with what Zane suggested (using the already-exposed
> scheduler_hints) then by implementing a single "server group" resource
> we basically get support for server groups "for free" in any resource
> that exposes scheduler hints.
>
> T
Joe Gordon wrote on 05/27/2014 07:31:16 PM:
> From: Joe Gordon
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/27/2014 07:32 PM
> Subject: Re: [openstack-dev] [neutron] Supporting retries in
neutronclient
>
>
> On Tue, May 27, 2014 at 1:51 PM, Eugene Nik
"Armando M." wrote on 05/28/2014 07:35:52 PM:
> From: "Armando M."
> To: "OpenStack Development Mailing List (not for usage questions)"
> ,
> Date: 05/28/2014 07:37 PM
> Subject: Re: [openstack-dev] [neutron][L3] VM Scheduling v/s Network
> as input any consideration ?
>
> Hi Keshava,
>
> To
Devananda van der Veen wrote on 05/29/2014
01:26:12 PM:
> Hi Jaromir,
>
> I agree that the midcycle meetup with TripleO and Ironic was very
> beneficial last cycle, but this cycle, Ironic is co-locating its
> sprint with Nova. Our focus needs to be working with them to merge
> the nova.virt.
Clint Byrum wrote on 05/29/2014 07:52:07 PM:
> I am writing to get some brainstorming started on how we might mitigate
> some of the issues we've seen while deploying large stacks on Heat. I am
> sending this to the dev list because it may involve landing fixes rather
> than just using different
Clint Byrum wrote on 05/29/2014 09:09:18 PM:
> > > update-failure-recovery
> > > ===
> > >
> > > This is a blueprint I believe Zane is working on to land in Juno.
...
>
> It's not just the observed state that you need in the database to
resume.
>
> You also need the param
Steve Baker wrote on 06/02/2014 05:37:25 PM:
> > BTW You missed off another strategy that we have discussed in the
> > past, and which I think Steve Baker might(?) be working on: retrying
> > failed calls at the client level.
> >
> As part of the client-plugins blueprint I'm planning on implement
John Garbutt wrote on 06/04/2014 04:29:36 AM:
> On 3 June 2014 14:29, Jay Pipes wrote:
> > tl;dr
> > =
> >
> > Move CPU and RAM allocation ratio definition out of the Nova scheduler
and
> > into the resource tracker. Remove the calculations for overcommit out
of the
> > core_filter and ram
I am not even sure what is the intent, but some of the behavior looks like
it is clearly unintended and not useful (a more precise formulation of
"buggy" that is not defeated by the lack of documentation).
IMHO, the API and CLI documentation should explain these calls/commands in
enough detail
I am not even sure what is the intent, but some of the behavior looks like
it is clearly unintended and not useful (i.e., buggy).
IMHO, the API and CLI documentation should explain these calls/commands in
enough detail that the reader can tell the difference. And the difference
should be us
https://wiki.openstack.org/wiki/Meetings/HeatAgenda
http://www.timeanddate.com/worldclock/fixedtime.html?msg=Heat+Chat&iso=20140618T20&p1=211&ah=1
Agenda (2014-06-18 2000 UTC)
Review last meeting's actions
Adding items to the agenda
Mid-cycle meetup
Critical issues sync
Regards,
Mike_
I have noticed that lately DevStack has been hacking requirements.txt in
most projects and test-requirements.txt in many. Why is this being done?
Thanks,
Mike___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cg
Suppose I have just used DevStack to install and startup OpenStack, and I
want to use tempest to check that my shiny new OpenStack is copacetic.
Should I use testr directly, or use tox or run_tempest.sh to wrap it in a
virtual environment? I see that tempest's README.rst says that I *can*,
but
I want to use DevStack to install and configure OpenStack with Neutron,
into a VM in an OpenStack undercloud. I looked at
https://wiki.openstack.org/wiki/NeutronDevstack and tried that, and
failed. Looking deeper, I see there are very important additional details
to pay attention to: flat net
Has anybody exercised the case of OS::Heat::AutoScalingGroup scaling a
nested stack that includes a OS::Neutron::PoolMember? Should I expect
this to work?
Thanks,
Mike___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openst
I can tell.
I think its only a few days of work, but the OpenStack CLA is preventing
me from contributing. :/
Thanks,
Kevin
From: Mike Spreitzer [mspre...@us.ibm.com]
Sent: Wednesday, March 12, 2014 11:34 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [heat][neutron] OS:
Zane Bitter wrote on 03/17/2014 07:03:25 PM:
> On 17/03/14 17:03, Ton Ngo wrote:
> > - How to handle resources with timer, e.g. wait condition:
pause/resume
> > timer value
>
> Handle it by only allowing pauses before and after. In most cases I'm
> not sure what it would mean to pause _during
I run into trouble in Ubuntu VMs when avahi-autoipd is installed. This is
when I install OpenStack using DevStack with a fairly plain local.conf.
For example, make an instance of Ubuntu Server 12.04. You can reboot it,
and all is well. Cloud-init continues to be able to read its metadata
fro
Lars Kellogg-Stedman wrote on 03/31/2014 01:31:57 PM:
> ... you could add an explicit route to the metadata
> address via your default gateway
Yes, and there are other work-arounds possible too. I posted here because
I was concerned there may be a bug that needs fixing.
> Why are you inst
I would like to suggest that a metadata section be allowed at the top
level of a HOT. Note that while resources in a stack can have metadata,
there is no way to put metadata on a stack itself. What do you think?
Thanks,
Mike___
OpenStack-dev mailing
Zane Bitter wrote on 04/02/2014 05:36:43 PM:
> I think that if you're going to propose a new feature, you should at
> least give us a clue who you think is going to use it and what for ;)
I was not eager to do that yet because I have not found a fully
satisfactory answer yet, at this point I a
Clint Byrum wrote on 04/03/2014 01:10:30 PM:
> Things that affect the stack as a whole really belong in the stack
> API. That would also put them in the OS::Heat::Stack resource, so the
> template language already supports that.
The OS::Heat::Stack resource is one of several that create nested s
Keith Bray wrote on 04/03/2014 01:50:28 PM:
> We proposed another specific piece of template data [3] which I
> can't remember whether it was met with resistance or we just didn't
> get to implementing it since we knew we would have to store other
> data specific to our uses cases in other fil
Clint Byrum wrote on 04/03/2014 07:01:16 PM:
> ... The whole question raises many more
> questions, and I wonder if there's just something you haven't told us
> about this use case. :-P
Yes, I seem to have made a muddle of things by starting in one corner of a
design space. Let me try to reset
"Kekane, Abhishek" wrote on 04/04/2014
06:26:58 AM:
> This is regarding implementation of blueprint https://
> blueprints.launchpad.net/tempest/+spec/testcases-expansion-icehouse.
>
> As per mentioned in etherpads for this blueprint, please add your
> name if you are working on any of the item
Let me add one more thing:
> Now let us consider how to evolve the Nova API so that a server-
> group can be scheduled holistically. That is, we want to enable the
> scheduler to look at both the group's policies and its membership,
> all at once, and make a joint decision about how to place all
It appears that in Fedora 19 and 20 the Wordpress examples need to install
different packages than in every other release (see my debugging in
https://review.openstack.org/#/c/87065/). I just got a complaint from
Heat validation that I can't do this:
"AWS::CloudFormation::Init" : {
Zane Bitter wrote on 04/15/2014 03:29:03 PM:
> On 15/04/14 14:31, Mike Spreitzer wrote:
> > It appears that in Fedora 19 and 20 the Wordpress examples need to
> > install different packages than in every other release (see my
debugging
> > in https://review.openstack.org
Clint Byrum wrote on 04/15/2014 05:17:21 PM:
> Excerpts from Zane Bitter's message of 2014-04-15 13:32:30 -0700:
> > Yes, that _kind_ of thing. But I don't see much point in having an
> > AWS::CloudFormation::Init section that isn't compatible with
> > CloudFormation's definition of it. We al
Mike Spreitzer/Watson/IBM@IBMUS wrote on 04/15/2014 05:59:50 PM:
> Yes, I can see how OS::Heat::Init makes sense. But is this just the
> first thing on a long list? Would it be better to have a static
> intrinsic that is like Python's dict(iterable of
> iterable)->
Many of the templates in the heat-templates project have built-in
expectations of image names; here is an example excerpt:
F18: {'32': F18-i386-cfntools, '64': F18-x86_64-cfntools}
F17: {'32': F17-i386-cfntools, '64': F17-x86_64-cfntools}
U10: {'32': U10-i386-cfntools, '64': U10-x86_6
Zane Bitter wrote on 04/16/2014 11:39:56 AM:
> In any event, though, my impression is that we are trying to get out of
> the cfn-init business as much as possible and leave the task to some
> combination of custom images, software config and configuration
> management. Hopefully someone will c
Steven Hardy wrote answers to most of my questions.
To clarify, my concern about URLs and image names is not so much for the
sake of a person browsing/writing but rather because I want programs,
scripts, templates, and config files (e.g., localrc for DevStack) to all
play nice together (e.g.,
Steven Hardy wrote on 04/16/2014 01:05:14 PM:
> On Wed, Apr 16, 2014 at 11:39:59AM -0400, Mike Spreitzer wrote:
> > http://fedorapeople.org/groups/heat/prebuilt-jeos-images/F19-
> x86_64-cfntools.qcow2
> > seems to be broken; I get failures every time I try to use it. Ha
Steven Dake wrote on 04/16/2014 03:31:16 PM:
> ...
> Fedora 19 shipped in the Fedora cloud images does *NOT* include
> heat-cfntools. The heat-cfntools package was added only in Fedora
> 20 qcow2 images. Fedora 19 must be custom made which those
> prebuilt-jeos-images are. They worked for m
Gouzongmei wrote on 04/19/2014 10:37:02 PM:
> We can supply APIs for getting, putting, adding and deleting current
> templates in the system, then when creating heat stacks, we just
> need to specify the name of the template.
Look for past discussion of Heat Template Repository (Heater). Here
On further thought, I noticed that "template-based resource" also
describes an AWS::CloudFormation::Stack; and since those are
template-based, you could well describe them as "custom" too.
Would you consider "nested stack" to also describe resources of other
types that are implemented by Python
1 - 100 of 301 matches
Mail list logo
