If the subnets have logical differences, then they should be in different spaces.
Examples for and against: 1) 2 network switches, one is 1GB for admin traffic, other is 10GB for storage traffic, these should be different spaces 2) 2 racks, each configured identically. each rack has 2 switches as described in (1). You would want to put the 2 subnets from the admin on each rack into the same space, and the 2 switches for the data traffic in another space. I can see that you have 10.0.[20-29].0/24 configured, but I have no idea how you're planning on carving out those subnets. It may be that they are intended to all be identical (one space), or it may be that they are to be carved into different types of traffic (each type of traffic would then be a different space). Spaces are a grouping mechanism. All subnets in a spaces are considered logically similar. John =:-> On Tue, Mar 15, 2016 at 10:33 PM, James Beedy <jamesbe...@gmail.com> wrote: > Hello Everyone, > > Thought I would take 2.0 for a test drive, I seem to of hit a wall trying > to bind service interfaces to subnet in a space. > > I see spaces can be assigned like so --> > > juju deploy mysql --bind "server=database cluster=internal" > > Does this indicate that I should have an affinity between subnets and > spaces? > > See here, my `space-0` has multiple subnets --> > http://paste.ubuntu.com/15393950/ > > Is there a way I can `bind` a service to a specific subnet in a space? > .... Is this a thing yet? > > > Thanks, > > James > > > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > >
-- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
