A couple of points
1) I dug up the code and 1.22.8 has the same code for listening on
":17070", so I can't see why it wouldn't be listening on both addresses.
2) Is there any reason you're still on 1.22.* ? Its been out of support for
a while, and we do strongly encourage you to upgrade to the
Hi John,
I'm using version 1.22.8. I did check the order of the interfaces and they
all start before juju runs. Even after restarting the API service with the
interfaces up it's still doesn't listen on 10.38.250.0/24.
Thanks,
Wayne
On Mon, Nov 7, 2016 at 6:34 AM, John Meinel
Hi James
What's the use case your using them for? Elastic IPs in aws are a very
limited commodity you get like 5 per region per account by default. IMO
it's generally not a recommended practice to depend on them as effectively
they represent public endpoints mapping to a single instance in aws.
Hi James
What's the use case your using them for? Elastic IPs in aws are a very
limited commodity you get like 5 per region per account by default. IMO
it's generally not a recommended practice to depend on them as effectively
they represent public endpoints mapping to a single instance in aws.
What version of Juju are you running? Is it possible the devices didn't
come up before Juju was up and running? Right now we are doing:
endpoint := net.JoinHostPort("", strconv.Itoa(info.APIPort))
listener, err := net.Listen("tcp", endpoint)
Which means we listen to ":17070". That should
Hi,
We had an Issue with Juju Charm store user accounts.
We developed a Cinder storage driver charm for "Kaminario-flash based
storage arrays".
In order to interact with Juju charm store, we need to create an Ubuntu SSO
account. Followed https://jujucharms.com/docs/2.0/authors-charm-store.
