Comment 14 for bug 1619812
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 1619812] Re: juju bootstrap node or deploy service with vSphere provider connects vm to wrong virtual switch | #14 |
we seem to be chasing rabbits that aren't actually allowing us to model
spaces on VMware and actually support per application networks.
What is the granularity of a network? Is it a list of subnets that can talk
to each other (like AWS VPC) or is it more like a subnet?
John
=:->
On Jul 19, 2017 10:27, "Andrew Wilkins" <email address hidden>
wrote:
> OK, so I think I've got a handle on what we need to do.
>
> The OVA/OVFs on cloud-images.
> Network" network. We're not validating that, and not enabling you to
> override that. Moreover, there's absolutely no way it would work with a
> distributed port group.
>
> So I'll look at doing the following:
> - introduce a "network" config, via which users will be able to specify
> the name of the primary network to which each VM will be attached the
> primary network name to attach to each VM
> - if "network" is unspecified, use "VM Network" if it exists; if it does
> not, but there is exactly one network available to the host/cluster, use
> that instead
> - if there's no "VM Network", and no single network, we'll probably just
> return an error and require the user to make a choice by setting the
> network config
>
> We'll need to check the type of network, and treat distributed port
> groups a little bit specially. I'm hoping to have this in a 2.2.3
> release soon.
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> juju bootstrap node or deploy service with vSphere provider connects
> vm to wrong virtual switch
>
> To manage notifications about this bug go to:
> https:/
>