Re: Simplestreams and juju 2.x on openstack

[Curtis Hovey-Canonical]

On Fri, Feb 10, 2017 at 8:04 PM, Tom Barber  wrote:

> If I want to bootstrap openstack how do I deal with simple streams?
>
> The docs point to https://jujucharms.com/docs/stable/howto-privatecloud
> but in 2.1RC1 `juju metadata` isn't valid.
>

Are you using a deb package, a snap, the MacOS client, the window's
installer?

The windows installer does not provide the metadata plugin. All other
packages/snaps/downloads do.

The juju metadata works for me using either the snap or the deb on a
pristine host. The juju-metadata plugin is included in the osx download and
it gives me the same results as the Ubuntu metadata plugins.


-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Simplestreams and juju 2.x on openstack

[Tom Barber]

If I want to bootstrap openstack how do I deal with simple streams?

The docs point to https://jujucharms.com/docs/stable/howto-privatecloud but
in 2.1RC1 `juju metadata` isn't valid.

Thanks

Tom

-- 
Tom Barber
CTO Spicule LTD
t...@spicule.co.uk

http://spicule.co.uk

@spiculeim 

Schedule a meeting with me 

GB: +44(0)5603641316
US: +18448141689


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: GCE controller and machine IP's are not static

[Antonio Rosales]

On Fri, Feb 10, 2017 at 7:12 AM, John Meinel  wrote:
> This is true on AWS as well, FWIW. But on AWS just a restart isn't enough. A
> full stop and start will change the addresses, though.

To make a stop in AWS I have to issue a AWS CLI command or take action
via the console.  In GCE however, I can and probably will reboot my
instance without any interaction from GCE CLI or console.  As a user I
would expect the default behavior to be to keep my same IP through
reboot.

Glad to see the bug is targeted for 2.2 I guess it missed 2.1 as that
went RC1 today. Of note Google Cloud Next conference is March 8-10
which would be nice to have a fix by then but may be behind other hot
bugs.

-thanks,
Antonio


> Note that if you're in HA as long as one of the controller addresses don't
> change we'll discover the others.
> However, if static addresses really are free on GCE we should certainly make
> use of them.
>
> John
> =:->
>
> On Feb 10, 2017 1:58 PM, "Merlijn Sebrechts" 
> wrote:
>>
>> Hi all
>>
>>
>> I want to bring some attention to a nasty bug on GCE. The external IP that
>> juju gives to instances is ephemiral. This means that the IP can be changed
>> after stopping and restarting the instance. This is obviously not what we
>> want.
>>
>> There is no cost advantage to an ephemiral IP so Juju should assign static
>> IPs by default.
>>
>> Bug on launchpad: https://bugs.launchpad.net/juju/+bug/1613823
>>
>>
>>
>> Kind regards
>> Merlijn
>>
>> --
>> 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
>



-- 
Antonio Rosales
Ecosystem Engineering
Canonical

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Juju 2.1-rc1 and Conjure-Up are here!

[Curtis Hovey-Canonical]

A new release of Juju, 2.1-rc1, and Conjure-up, are here!


## What's new?

[juju] Manual provisioning now supports CentOS machines. See
https://github.com/juju/docs/issues/1647 for instructions on how to
prepare a CentOS LXD container for manual provisioning.

[juju] Beta 5 changed the way LXD certificate credentials are handled
internally, which caused issues for some users connecting to a
"localhost" controller from remote machines. If you need to add models
to a LXD controller from a remote machine, you can now use

juju autoload-credentials

followed by

juju add-credential localhost

on the LXD host to generate a certificate credential, and then load that
credential into the Juju client on the remote host.

See https://github.com/juju/docs/issues/1636 for more details if this
applies to you.

[juju] Container networking refinements to explicitly specify which
spaces to deploy applications to. The most visible changes apply to
machines that have more than one network interface. Juju's network
spaces now gives operators greater control over the spaces into which
applications are deployed.

When deploying an application to a target with multiple spaces, the
operator must specify which to use. Ambiguous bindings will result in a
provisioning failure.

Juju creates bridges for containers when it knows the spaces the
applications require, and the container's bridge only connects to the
required network interfaces. Previously, Juju bridged all networks and
placed the network card in promiscuous mode when the machine was
provisioned.

Bindings are supported per-endpoint, allowing operators to configure
mysql so the 'admin' endpoint is accessed on a separate subnet from
'db'. Charms utilizing the existing "unit-get private-address" must be
updated to use "network-get --primary-address ".

Operators may specify bindings when deploying a charm:

juju deploy --bind "admin=admin-space db=internal-space" 

To specify everything in the same space:

juju deploy --bind space 

Bundles may specify bindings with a bindings stanza:

mysql:
  charm: "./xenial/percona-cluster"
  num_units: 1
  bindings:
access: internal-api
shared-db: internal-api

Bundles may place all bindings in the same space:

mysql:
  charm: "./xenial/percona-cluster"
  num_units: 1
  bindings:
"": internal-api


[conjure-up] Added several Big Data spells:

conjure-up bigdata


## Bugs Addressed

Check the milestones for a detailed breakdown of Juju and Conjure-Up
bugs corrected.

https://launchpad.net/juju/+milestone/2.1-rc1

https://github.com/conjure-up/conjure-up/milestone/14?closed=1


## How do I get it?

If you are running Ubuntu, you can get Juju from the juju devel ppa:

   sudo add-apt-repository ppa:juju/devel; sudo apt-get update

   sudo apt-get install juju

Or install Juju from the snap store:

   snap install juju --beta --devmode

Install conjure-up from the snap store:

   snap install conjure-up --classic --candidate

If you are on Trusty, you'll need to run a few extra commands:

   sudo apt-get install snapd
   sudo groupadd lxd && sudo usermod -a -G lxd $USER
   sudo reboot

Now you can install snaps, including conjure-up, as normal:

   snap install conjure-up --classic --candidate

Windows, CentOS, and MacOS users can get a corresponding Juju
installer at:

   https://launchpad.net/juju/+milestone/2.1-rc1


## Feedback Appreciated!

We encourage everyone to let us know how you're using Juju. Send us a
message on Twitter using #jujucharms, join us at #juju on freenode, and
subscribe to the mailing list at juju@lists.ubuntu.com.



-- 
Curtis Hovey
Canonical Cloud Development and Operations
http://launchpad.net/~sinzui

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: GCE controller and machine IP's are not static

[John Meinel]

This is true on AWS as well, FWIW. But on AWS just a restart isn't enough.
A full stop and start will change the addresses, though.
Note that if you're in HA as long as one of the controller addresses don't
change we'll discover the others.
However, if static addresses really are free on GCE we should certainly
make use of them.

John
=:->

On Feb 10, 2017 1:58 PM, "Merlijn Sebrechts" 
wrote:

> Hi all
>
>
> I want to bring some attention to a nasty bug on GCE. The external IP that
> juju gives to instances is ephemiral. This means that the IP can be changed
> after stopping and restarting the instance. This is obviously not what we
> want.
>
> There is no cost advantage to an ephemiral IP so Juju should assign static
> IPs by default.
>
> Bug on launchpad: https://bugs.launchpad.net/juju/+bug/1613823
>
>
>
> Kind regards
> Merlijn
>
> --
> 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

GCE controller and machine IP's are not static

[Merlijn Sebrechts]

Hi all


I want to bring some attention to a nasty bug on GCE. The external IP that
juju gives to instances is ephemiral. This means that the IP can be changed
after stopping and restarting the instance. This is obviously not what we
want.

There is no cost advantage to an ephemiral IP so Juju should assign static
IPs by default.

Bug on launchpad: https://bugs.launchpad.net/juju/+bug/1613823



Kind regards
Merlijn
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju