In addition to the other questions below, I was wondering if you could
explain why you included all those integer IDs; aren't the UUIDs
sufficient?
Thanks,
Mike
From: Mike Spreitzer/Watson/IBM@IBMUS
To: "Yathiraj Udupi (yudupi)" ,
Cc: OpenStack Development Mail
See the picture at
https://docs.google.com/drawings/d/1nridrUUwNaDrHQoGwSJ_KXYC7ik09wUuV3vXw1MyvlY
and the writeup at
https://docs.google.com/document/d/1Ecr1zXpU4zMvEySmbD-wwxLPfinndb0eaKgMuALOb2I
This is not as small as possible, but not terribly large; there are only 8
VM instances. I want
On second thought, I should revise and extend my remarks. This message
supersedes my previous two replies.
Thanks. I have a few questions. First, I am a bit stymied by the style
of API documentation used in that document and many others: it shows the
first line of an HTTP request but says no
Yes, that helps. Please, guys, do not interpret my questions as
hostility, I really am just trying to understand. I think there is some
overlap between your concerns and mine, and I hope we can work together.
Sticking to the physical reservations for the moment, let me ask for a
little more e
Sylvain: please do not interpret my questions as hostility. I am only
trying to understand your proposal, but I am still confused. Can you
please walk through a scenario involving Climate reservations on virtual
resources? I mean from start to finish, outlining which party makes which
decisi
Thanks for the clue about where the request/response bodies are
documented. Is there any convenient way to view built documentation for
Havana right now?
You speak repeatedly of the desire for "clean" interfaces, and nobody
could disagree with such words. I characterize my desire that way too
Thanks, that helps a lot. At what point in the process is it decided (and
by what) which host will run the VM instance? Is that host picked from
the same pool as is used for non-reserved instances? How does the outline
go if there is not enough capacity for the reserved instance?
Thanks,
Mik
I favor separation of concerns. I think (4), at least, has got nothing to
do with infrastructure orchestration, the primary concern of today's heat
engine. I advocate (4), but as separate functionality.
Regards,
Mike
Alex Rudenko wrote on 10/09/2013 12:59:22 PM:
> From: Alex Rudenko
> To:
Yes, there is more than the northbound API to discuss. Gary started us
there in the Scheduler chat on Oct 1, when he broke the issues down like
this:
11:12:22 AM garyk: 1. a user facing API
11:12:41 AM garyk: 2. understanding which resources need to be tracked
11:12:48 AM garyk: 3. backend impl
Debojyoti Dutta wrote on 10/09/2013 02:48:26 AM:
>
> Mike, I agree we could have a cleaner API but I am not sure how
> cleanly it will integrate with current nova which IMO should be test
> we should pass (assuming we do cross services later)
I think the cleaner APIs integrate with Nova as well a
Regarding Alex's question of which component does holistic infrastructure
scheduling, I hesitate to simply answer "heat". Heat is about
orchestration, and infrastructure scheduling is another matter. I have
attempted to draw pictures to sort this out, see
https://docs.google.com/drawings/d/1Y
I'll be at the summit too. Available Nov 4 if we want to do some prep
then. It will be my first summit, I am not sure how overbooked my summit
time will be.
Regards,
Mike
From: Sylvain Bauza
To: OpenStack Development Mailing List
,
Cc: Mike Spreitzer/Watson/IBM@IBMUS
Could we agree on the following small changes to the model you posted last
week?
1. Rename InstanceGroupPolicy to InstanceGroupPolicyUse
2. In InstanceGroupPolicy[Use], rename the "policy" field to
"policy_type"
3. Add an InstanceGroupPolicyUseProperty table, holding key/value pairs
(two s
inline into the InstanceGroupPolicy[Use] class.
Regards,
Mike
From: "Yathiraj Udupi (yudupi)"
To: Mike Spreitzer/Watson/IBM@IBMUS,
Cc: OpenStack Development Mailing List
Date: 10/14/2013 01:38 PM
Subject:Re: [scheduler] Policy Model
Mike,
Like I proposed in m
That came through beautifully formatted to me, but it looks much worse in
the archive. I'm going to use crude email tech here, so that I know it
won't lose anything in handling.
"Yathiraj Udupi (yudupi)" wrote on 10/14/2013 01:17:47
PM:
> I read your email where you expressed concerns regard
Yes, Rethinking Scheduler Design
http://summit.openstack.org/cfp/details/34 is not the same as the
performance issue that Boris raised. I think the former would be a
natural consequence of moving to an optimization-based joint
decision-making framework, because such a thing necessarily takes
"Yathiraj Udupi (yudupi)" wrote on 10/14/2013 11:43:34
PM:
> ...
>
> For the policy model, you can expect rows in the DB each
> representing different policy instances something like-
> {id: , uuid: "SOME-UUID-1", name: "anti-colocation-1", type:
> "anti-colocation", properties: {lev
Steve Baker wrote on 10/15/2013 06:48:53 PM:
> From: Steve Baker
> To: openstack-dev@lists.openstack.org,
> Date: 10/15/2013 06:51 PM
> Subject: [openstack-dev] [Heat] HOT Software configuration proposal
>
> I've just written some proposals to address Heat's HOT software
> configuration needs
The threading in the archive includes this discussion under the "HOT
Software orchestration proposal for workflows" heading, and the overall
ordering in the archive looks very mixed up to me. I am going to reply
here, hoping that the new subject line will be subject to less strange
ordering in
Steven Hardy wrote on 10/16/2013 04:11:40 AM:
> ...
> IMO we should be abstracting the software configuration complexity
behind a
> Heat resource interface, not pushing it up to a pre-processor (which
> implies some horribly complex interfaces at the heat template level)
I am not sure I follow.
Zane Bitter wrote on 10/16/2013 08:25:38 AM:
> To answer your question, the key thing that Heat does is take in two
> declarative models and generate a workflow to transform one into the
> other. (The general case of this is a stack update, where the two models
> are defined in the previous a
Zane Bitter wrote on 10/16/2013 10:30:44 AM:
> On 16/10/13 15:58, Mike Spreitzer wrote:
> ...
> > Thanks for a great short sharp answer. In that light, I see a
concern.
> > Once a workflow has been generated, the system has lost the ability
to
> > adapt to change
Mike Wilson wrote on 10/16/2013 07:13:17 PM:
> I need to understand better what "holistic scheduling" means, ...
By "holistic" I simply mean making a joint decision all at once about a
bunch of related resources of a variety of types. For example, making a
joint decision about where to place
What is the rationale for this new feature? Since there is already an
autoscaling group implemented by Heat, what is the added benefit here? And
why is it being done as another heat-native thing rather than as an
independent service (e.g., as outlined in
https://wiki.openstack.org/wiki/Heat/Au
Clint Byrum wrote on 10/17/2013 09:16:12 PM:
> Excerpts from Mike Spreitzer's message of 2013-10-17 17:19:58 -0700:
> > What is the rationale for this new feature? Since there is already an
> > autoscaling group implemented by Heat, what is the added benefit here?
And
> > why is it being don
(I really do not understand how the archive is ordered. In the by-thread
view, in which all messages with this subject are equally indented, the
last message listed is not the chronologically last.)
I see that components have parameters. In some uses (invocations) of
components, parameters ar
Steve Baker wrote on 10/15/2013 06:48:53 PM:
> I've just written some proposals to address Heat's HOT software
> configuration needs, and I'd like to use this thread to get some
feedback:
> https://wiki.openstack.org/wiki/Heat/Blueprints/hot-software-config
>
https://wiki.openstack.org/wiki/He
"Yathiraj Udupi (yudupi)" wrote on 10/15/2013 03:08:32
AM:
> I have made some edits to the document: https://docs.google.com/
> document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?pli=1#
> ...
One other minor thing to discuss in the modeling is metadata. I am not
eager to totally go
Zane Bitter wrote on 10/28/2013 06:47:50 AM:
> On 27/10/13 16:37, Edgar Magana wrote:
> > Heat Developers,
> >
> > I am one of the core developers for Neutron who is lately working on
the
> > concept of "Network Topologies". I want to discuss with you if the
> > following blueprint will make sens
Steve Baker wrote on 10/28/2013 04:24:30 PM:
> On 10/29/2013 02:53 AM, Steven Hardy wrote:
> > ...
> > Can anyone provide me with a clear argument for what the "fundamental
> > differences" actually are?
> ...
> Since writing those proposals my thinking has evolved too. I'm currently
> thinking i
"Yathiraj Udupi (yudupi)" wrote on 10/29/2013 02:46:30
AM:
> The Instance Group API document is now updated with a simple example
> request payload of a nested group, and some description of how the
> API implementation should handle the registration of the components
> of a nested instance gr
Alex Glikson wrote on 10/29/2013 03:37:41 AM:
> 1. I assume that the motivation for rack-level anti-affinity is to
> survive a rack failure. Is this indeed the case?
> This is a very interesting and important scenario, but I am curious
> about your assumptions regarding all the other OpenStack
Khanh-Toan Tran wrote on 10/29/2013
09:10:00 AM:
> ...
> 1) Member of a group is recursive. A member can be group or an
> instance. In this case there are two different declaration formats
> for members, as with http-server-group-1 ("name, "policy", "edge")
> and Http-Server-1 ("name", "reques
John Garbutt wrote on 10/29/2013 07:29:19 AM:
> ...
> Its looking good, but I was thinking about a slightly different
approach:
>
> * I would like to see instance groups be used to describe all
> scheduler hints (including, please run on cell X, or please run on
> hypervisor Y)
I think Yathi's
I should clarify my comment about invoking Heat to do the orchestration. I
think we have a choice between designing a 1-stage API vs a 2-stage API.
The 2-stage API goes like this: first the client defines the top-level
group and everything inside it, then the client makes more calls to create
t
Following is my reaction to the last few hours of discussion.
Russell Bryant wrote "Nova calling heat to orchestrate Nova seems
fundamentally wrong". I am not totally happy about this either, but would
you be OK with Nova orchestrating Nova? To me, that seems worse ---
duplicating functionali
Swapnil Kulkarni wrote on 10/30/2013
02:36:37 AM:
> I had a discussion with russellb regarding this for yesterday, I
> would like to discuss this with the team regarding the blueprint
> mentioned in subject.
>
>
https://blueprints.launchpad.net/nova/+spec/auto-vm-discovery-on-hypervisor
>
"Daniel P. Berrange" wrote on 10/30/2013 12:38:21
PM:
> ... This avoids any need to deal with the hard problems of adopting
> arbitrary VMs.
Sorry, my writing was unclear. I did not mean another use case for
adopting VMs; I mean another use case for VM discovery.
Regards,
Mike
Alex Glikson wrote on 10/30/2013 02:26:08 AM:
> Mike Spreitzer wrote on 30/10/2013 06:11:04 AM:
> > Date: 30/10/2013 06:12 AM
> >
> > Alex also wrote:
> > ``I wonder whether it is possible to find an approach that takes
> > into account cross-resource p
Clint Byrum wrote on 10/30/2013 01:42:53 PM:
> ...
>
> The engine should store _all_ of its state in a distributed data store
> of some kind. Any engine should be aware of what is already happening
> with the stack from this state and act accordingly. That includes the
> engine currently working
Lakshminaraya Renganarayana/Watson/IBM@IBMUS wrote on 10/30/2013 03:35:32
PM:
> Zane Bitter wrote on 10/29/2013 08:46:21 AM:
> ...
> In this method
> > (i.e. option (2) above) shouldn't we be building the dependency graph
in
> > Heat rather than running through them sequentially as specified
Zane Bitter wrote on 11/12/2013 12:06:14 PM:
> ... However, if
> for any reason you have a dict key starting with "$" and we interpret
> that specially, then you are basically hosed since you almost certainly
> _needed_ it to actually start with "$" for a reason. So -1.
>
> cheers,
> Zane.
Y
This is a follow-up to the design summit discussion about DB migrations.
There was concern about the undo-ability of some migrations. The specific
example cited was removal of a column. Could that be done with the
following three migrations, each undo-able? First, change the code to
keep wri
It seems to me we have been discussing a proposal whose write-up
intertwines two ideas: (1) making software components look like resources,
and (2) using nested stacks and environments to achieve the pattern of
definitions and uses. The ideas are separable, and I think the discussion
has sort
Michael Still wrote on 11/13/2013 04:27:17 PM:
> ...
> This was actually discussed in the session as an example of how other
> projects handle these problems. Our concerns (IIRC) were that it would
> take even more patches to land, and each of those patches is quite
> hard to land in nova these da
Zane Bitter wrote on 11/14/2013 12:56:22 PM:
> ...
> My 2c: the way I designed the Heat API was such that extant stacks can
> be addressed uniquely by name. Humans are pretty good with names, not so
> much with 128 bit numbers. The consequences of this for the design were:
> - names must be
There were some concerns expressed at the summit about scheduler
scalability in Nova, and a little recollection of Boris' proposal to keep
the needed state in memory. I also heard one guy say that he thinks Nova
does not really need a general SQL database, that a NOSQL database with a
bit of d
For the case of an item that has no significant doc of its own but is
related to an extensive blueprint, how about linking to that extensive
blueprint?
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/m
Joshua, I do not think such a strict and coarse scheduling is a practical
way to manage developers, who have highly individualized talents,
backgrounds, and interests.
Regards,
Mike
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
Robert Collins wrote on 09/06/2013 05:31:14
PM:
> From: Robert Collins
> To: OpenStack Development Mailing List
,
> Date: 09/06/2013 05:36 PM
> Subject: Re: [openstack-dev] [tripleo] Scaling of TripleO
>
> ...
> My vision for TripleO/undercloud and scale in the long term is:
> - A fully redu
A quick dictionary lookup of "data processing" yields the following. I
wonder if you mean something more specific.
data processing |ˈˌdædə ˈprɑsɛsɪŋ|
noun
a series of operations on data, esp. by a computer, to retrieve,
transform, or classify information.
From: Matthew Farrellee
To: O
First, I'm a newbie here, wondering: is this the right place for
comments/questions on blueprints? Supposing it is...
I am referring to
https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension
In my own research group we have experience with a few systems that do
something lik
Jon Maron wrote on 09/10/2013 08:50:23 PM:
> From: Jon Maron
> To: OpenStack Development Mailing List
,
> Cc: OpenStack Development Mailing List
> Date: 09/10/2013 08:55 PM
> Subject: Re: [openstack-dev] [savanna] Program name and Mission
statement
>
> Openstack Big Data Platform
Let's se
> To provide a simple, reliable and repeatable mechanism by which to
> deploy Hadoop and related Big Data projects, including management,
> monitoring and processing mechanisms driving further adoption of
OpenStack.
That sounds like it is at about the right level of specificity.
___
First let me make sure I understand what this section (
http://docs.openstack.org/developer/devstack/guides/neutron.html#neutron-networking-with-open-vswitch-and-provider-networks
) is trying to say. The second paragraph is saying that some
infrastructure provider has allocated a VLAN tag (and th
> From: Henry Gessau
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 12/04/2015 02:23 PM
> Subject: Re: [openstack-dev] [neutron] Multiple locations for
> documentation of features
>
> Sean M. Collins wrote:
> > I've noticed that a lot of features are now being
What about pinging? BTW, from where would the pings come?
In the Docker/Swarm API today there is no way to disable ping. However,
once Kuryr's libnetwork plugin is updated so that `docker network connect
--ip=W.X.Y.Z ...` will latch onto a matching pre-existing Neutron Port, if
it exists, the
Antoni Segura Puimedon wrote on 06/11/2016
07:39:41 PM:
> Well, with a label you can make the Neutron Port have an SG that
> forbids pinging.
Wait, what? Labels on what can do what?
Thanks,
Mike
__
OpenStack Developmen
I like this, for a reason not mentioned. I am not a Neutron dev or
operator and have never learned how to deploy Neutron; I have always
driven it through DevStack. The documentation for that has never been
adequate, and I have concluded it will never be adequate. With inadequate
documentatio
I am looking at
https://www.openstack.org/videos/video/project-kuryr-docker-delivered-kubernetes-next
, around 28:00. You have said that overlay networks are involved, and are
now talking about load balancers. Is this Neutron LBaaS? As far as I
know, a Neutron LBaaS instance is "one-armed"
I just read
http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.html and,
unless I missed something, it seems to be describing something that is not
multi-tenant. I am focused on FQDNs for Neutron Ports. For those, only
the "hostname" part (the first label, in official DNS jargon
Neutron's DNS integration
>
> On 09/05/2016 19:21, Mike Spreitzer wrote:
> > I just read
> >
http://docs.openstack.org/mitaka/networking-guide/adv-config-dns.htmland
> , unless
> > I missed something, it seems to be describing something that is not
> > multi
"Hayes, Graham" wrote on 05/09/2016 04:08:07 PM:
> ...
> On 09/05/2016 20:55, Mike Spreitzer wrote:
> ...
> > Oh, right, the network gets to specify the rest of the FQDN. In my
case
> > I am interested in Neutron Ports on tenant networks. So with a
per-port
&
"Hayes, Graham" wrote on 05/10/2016 09:30:26 AM:
> ...
> > Ah, that may be what I want. BTW, I am not planning to use Nova. I
am
> > planning to use Swarm and Kubernetes to create containers attached to
> > Neutron private tenant networks. What DNS server would I configure
> > those container
> On Tue, May 10, 2016 at 11:28 AM, Kevin Benton wrote:
> neutron subnet-show with the UUID of the subnet they have a port on
> will tell you.
>
> On Tue, May 10, 2016 at 6:40 AM, Mike Spreitzer
wrote:
> "Hayes, Graham" wrote on 05/10/2016 09:30:26 AM:
>
>
I would like to back-port https://review.openstack.org/#/c/242721/ ---
which fixed https://bugs.launchpad.net/devstack/+bug/1469596 --- to
stable/liberty. I have contributed to main line development before, but
not stable branches. I see that
http://docs.openstack.org/infra/manual/developers.
in DevStack?
>
> On Sun, Jan 3, 2016 at 4:01 PM, Mike Spreitzer
wrote:
> I would like to back-port https://review.openstack.org/#/c/242721/
> --- which fixed https://bugs.launchpad.net/devstack/+bug/1469596---
> to stable/liberty. I have contributed to main line development
>
in DevStack?
>
> On Sun, Jan 3, 2016 at 4:01 PM, Mike Spreitzer
wrote:
> I would like to back-port https://review.openstack.org/#/c/242721/
> --- which fixed https://bugs.launchpad.net/devstack/+bug/1469596---
> to stable/liberty. I have contributed to main line development
>
I have been trying to get
http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface
working on Ubuntu 14.04 (updated to the latest, which includes kernel
3.19). With the latest sources and a sufficiently recent OVS, the
one-node install pretty much
Adam Lawson wrote on 01/23/2016 02:27:46 PM:
> For the sake of over-simplification, is there ever a reason to NOT
> enable jumbo frames in a cloud/SDN context where most of the traffic
> is between virtual elements that all support it? I understand that
> some switches do not support it and tra
BTW, regarding devstack: See
https://bugs.launchpad.net/devstack/+bug/1532924. I have been trying to
get the current code to work, following the ideas in
https://specs.openstack.org/openstack/fuel-specs/specs/7.0/jumbo-frames-between-instances.html#proposed-change
. It fails only at the last s
Monty Taylor wrote on 09/15/2015 11:04:07 AM:
> a) an update to python-novaclient to allow a named network to be passed
> to satisfy the "you have more than one network" - the nics argument is
> still useful for more complex things
I am not using the latest, but rather Juno. I find that in ma
Clark Boylan wrote on 09/15/2015 04:06:26 PM:
> > I also strongly recommend to users to put vms on a private network and
> > use floating ip's/load balancers. For many reasons. Such as, if you
> > don't, the ip that gets assigned to the vm helps it become a pet. you
> > can't replace the vm and g
"Armando M." wrote on 09/15/2015 03:50:24 PM:
> On 15 September 2015 at 10:02, Doug Hellmann
wrote:
> Excerpts from Armando M.'s message of 2015-09-15 09:30:35 -0700:
...
> As with the Glance image upload API discussion, this is an example
> of an extremely common use case that is either comple
Is there a way to configure devstack to install Neutron such that there is
just one network and that is an external network and Nova can create
Compute Instances on it, using projects of Kilo vintage?
Thanks,
Mike
__
Open
> From: Monty Taylor
> To: Sylvain Bauza , "OpenStack Development
> Mailing List (not for usage questions)"
> Date: 09/28/2015 09:54 AM
> Subject: Re: [openstack-dev] Compute API (Was Re: [nova][cinder] how
> to handle AZ bug 1496235?)
>
> ...
> Specifically, I want "nova boot" to get me a VM w
> From: 王华
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 09/28/2015 11:34 PM
> Subject: [openstack-dev] [magnum]swarm + compose = k8s?
>
> Hi folks,
>
> Magnum now exposes service, pod, etc to users in kubernetes coe, but
> exposes container in swarm coe. As I
> From: Gorka Eguileor
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 09/29/2015 07:34 AM
> Subject: Re: [openstack-dev] [all] -1 due to line length violation
> in commit messages
...
> Since we are not all native speakers expecting everyone to realize that
> dif
I have been looking at
http://docs.openstack.org/developer/devstack/guides/neutron.html and
wonder about a few things.
In the section
http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface
there is a helpful display of localrc contents. It says
[Apologies for re-posting, but I botched the subject line the first time
and know that people use filters.]
I have been looking at
http://docs.openstack.org/developer/devstack/guides/neutron.html and
wonder about a few things.
In the section
http://docs.openstack.org/developer/devstack/guides
[Sorry, but I do not know if the thundering silence is because these
questions are too hard, too easy, grossly off-topic, or simply because
nobody cares.]
I have been looking at
http://docs.openstack.org/developer/devstack/guides/neutron.htmland wonder
about a few things.
In the section
http
> From: "Sean M. Collins"
...
>
> On Tue, Oct 06, 2015 at 11:25:03AM EDT, Mike Spreitzer wrote:
> > [Sorry, but I do not know if the thundering silence is because these
> > questions are too hard, too easy, grossly off-topic, or simply because
> > nobo
Thierry Carrez wrote on 10/09/2015 05:42:49 AM:
...
> So whenever you feel like you made progress, or had a little success in
> your OpenStack adventures, or have some joyful moment to share, just
> throw the following message on your local IRC channel:
>
> #success [Your message here]
>
> The
---
From:"Sean M. Collins" To:"OpenStack Development
Mailing List (not for usage questions)"
Date:Mon, Oct 12, 2015 11:34Subject:Re:
[openstack-dev] [devstack] [neutron] A larger batch of questions about
configuring DevStack to use Neutron
On Thu, Oct 08, 2015 at 01:47:31PM
> On Thu, Oct 08, 2015 at 01:47:31PM EDT, Mike Spreitzer wrote:
> > ..
> > > > In the section
> > > > http://docs.openstack.org/developer/devstack/guides/
> > > neutron.html#using-neutron-with-a-single-interface
> > &
Matt Riedemann wrote on 10/08/2015 09:48:33
PM:
> On 10/8/2015 11:38 AM, Sean M. Collins wrote:
> > Please see my response here:
> >
> >
http://lists.openstack.org/pipermail/openstack-dev/2015-October/076251.html
> >
> > In the future, do not create multiple threads since responses will get
>
> From: Mike Spreitzer/Watson/IBM@IBMUS
> To: "OpenStack Development Mailing List \(not for usage questions\)"
>
> Date: 10/13/2015 03:39 AM
> Subject: Re: [openstack-dev] [devstack] [neutron] A larger batch of
> questions about configuring DevStack to use Neutron
&
> questions about configuring DevStack to use Neutron
>
> On Fri, Oct 16, 2015 at 02:02:57AM EDT, Mike Spreitzer wrote:
> > Now I have tested the first section (taking the latest of both
changes)
> > using stable/liberty, and it failed because br-ex was not created
>
> From: Rukhsana Ansari
> To: openstack-dev@lists.openstack.org
> Date: 06/02/2015 01:59 PM
> Subject: [openstack-dev] [neutron] [fwaas] -IPv6 support in Kilo
>
> Hi,
>
> I was browsing the code to understand IPv6 support For FWaaS in Kilo.
>
> I don't see a restriction in the db code or in r
How would I modify the recipe at
http://docs.openstack.org/developer/devstack/guides/neutron.html#using-neutron-with-a-single-interface
to get linuxbridge instead of openvswitch?
Thanks,
Mike
__
OpenStack Development Mai
"Sean M. Collins" wrote on 03/02/2016 12:38:29 PM:
> I think that the default security group should be left as is - and users
> should be trained that they should bring/create security groups with the
> appropriate rules for their need.
Could we at least make it less difficult to figure out whic
"Sean M. Collins" wrote on 03/02/2016 01:16:52 PM:
> Meaning your users are creating new security groups and naming them
> "default" - so you have the "default" default (heh) and then the one
> that they created named default?
>
> Are security group names in Nova-Net unqiue? I seem to recall tha
Kevin Benton wrote on 03/02/2016 01:27:27 PM:
> Does it at least also include the UUID, or is there no way to tell
> from 'nova show'?
No direct way to tell, as far as I can see.
__
OpenStack Development Mailing List (not
On Feb 5 I was given a tarchive of kuryr with an install script that
configures the docker daemon to use consul as its cluster store. If I
modify the config of docker to use etcd instead then do I need to change
anything in Kuryr?
Thanks,
Mike
___
> From: Weidong Shao
> To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: 02/28/2015 02:12 PM
> Subject: [openstack-dev] Heat: autoscaling across availability zones
>
> From the heat template reference doc, it seems that auto-scaling
> across AZs is not supported.
Are you looking at scaling the numbers of tenants, Neutron routers, and
tenant networks as you scale hosts and guests? I think this is a
plausible way to grow. The compartmentalizations that comes with growing
those things may make a difference in results.
Thanks,
Mike
From: Neil Jerram
As an operator, is there a way I can create two external networks from
Neutron's point of view, where both of those networks are accessed through
the same host NIC? Obviously those networks would be using different
subnets. I need this sort of thing because the two subnets are treated
differe
Does Neutron support any of the 4/6 interoperation/transition techniques?
I wear an operator's hat nowadays, and want to make IPv6 as useful and
easy to use as possible for my tenants. I think the
interoperation/transition techniques will play a big role in this.
Thanks,
Mike__
"Robert Li (baoli)" wrote on 05/05/2015 09:02:08 AM:
> Currently dual stack is supported. Can you be specific on what
> interoperation/transition techniques you are interested in? We’ve
> been thinking about NAT64 (stateless or stateful).
>
> thanks,
> Robert
&g
Joshua Harlow wrote on 02/10/2017 12:21:08 PM:
> Knowing where this is at and the issues. It makes me wonder if it is
> worthwhile to start thinking about how we can start to look at 'outside
> the openstack' projects for DNS. I believe there is a few that are
> similar enough to designate (th
201 - 300 of 301 matches
Mail list logo
