Re: Cinder-Ceph Multi-Backend Example

2018-04-17 Thread James Beedy 
Alex,

Thanks for the response, and nice work on the write up.

~James

On Mon, Apr 16, 2018 at 5:28 AM, alex barchiesi 
wrote:

> Hi James,
> at GARR we recently tested the cinder multi backend with the following
> idea in mind:
> support 3 different backends:
>
>- a default one, for general-purpose disks like virtual machine boot
>disks: replicated pool with replica factor equal to 3
>- a reduced redundancy one: replicated pool with replica factor 2,
>which should slightly improve latency
>- a large capacity one: erasure-coded (possibly with a small frontend
>replicated pool)
>
> Premise: we have a juju deployed O~S (spanning 3 geographical data
> centers).
>
> We configured Cinder such that it allows selection between multiple
> “Volume Types”, where each Volume Type points to a distinct Ceph pool
> within the same Ceph cluster.
>
> This is the simplest configuration, as it involves Cinder configuration
> alone. Volumes which are created can be later attached to running
> instances, but all instances will have their boot disk on the default pool
> cinder-ceph.
>
> We faced some issues as reported in details here: https://docs.google.com/
> document/d/1VSS28cvZBIOEzTOmVMWZ0o9FiVFkVLvu__ZOLxneMqQ/edit#
>
> Would be interesting to find a way to be able to select the pool also for
> the boot disk of a VM
>
> Any comment, idea, "whatever" (also on the doc) is very much appreciated
>
> best Alex
>
>
>
> Dr. Alex Barchiesi
> 
> Senior cloud architect
> Art -Science relationships responsible
>
> GARR CSD department
>
> Rome GARR: +39 06 4962 2302
> Lausanne EPFL: +41 (0) 774215266
>
> linkedin: alex barchiesi
> 
> _
> I started with nothing and I still have most of it.
>
>
>
> On Sat, Apr 14, 2018 at 3:25 AM, James Beedy  wrote:
>
>> Looking for examples that describe how to consume multiple ceph backends
>> using the cinder-ceph charm.
>>
>> Thanks
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: bridge activation error: yaml: unmarshal errors:, line 7: field bonds not found in struct netplan

2018-04-17 Thread Vidmantas Rinkevičius 

Submitted

https://bugs.launchpad.net/juju/+bug/1764735


On 2018-04-17 15:29, John Meinel wrote:
btw, including a copy of your /etc/netplan/*.yaml files once you've 
bootstrapped would probably be useful to make sure we're addressing 
the issues that you're seeing.


John
=:->


On Tue, Apr 17, 2018 at 4:18 PM, John Meinel > wrote:


We should get a bug following this. But essentially Bionic changed
how networking configuration is being done, from
/etc/network/interfaces to /etc/netplan/*.yaml files.

When we started implementing support for netplan, they hadn't
finished support for bonds, so we didn't implement support for
reading bonds and configuring them.

They have since finished supporting bonds in netplan, and we need
to update our support for netplan to include bonds.

While we *could* just not past "strict" to the yaml library, I
think the net result of that would not be positive, because we
might try to create configurations not being aware of part of your
network.


On Tue, Apr 17, 2018 at 10:46 AM, Vidmantas Rinkevičius
> wrote:

Hi,

During openstack deployment juju gives error on all lxd
containers.

Example:

sudo juju status

3/lxd/0  down pending  bionic bridge
activation error: yaml: unmarshal errors:
  line 7: field bonds not found in struct netplan.

yaml:

openstack-dashboard:
    annotations:
  gui-x: '500'
  gui-y: '-250'
    charm: cs:~openstack-charmers-next/bionic/openstack-dashboard
    num_units: 1
    bindings:
  website: web
    options:
  openstack-origin: distro-proposed
    to:
    - lxd:3


I am deploying 18.04 and I use network spaces.

Any ideas why this error occurs?






-- 
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

Re: bridge activation error: yaml: unmarshal errors:, line 7: field bonds not found in struct netplan

2018-04-17 Thread John Meinel 
btw, including a copy of your /etc/netplan/*.yaml files once you've
bootstrapped would probably be useful to make sure we're addressing the
issues that you're seeing.

John
=:->


On Tue, Apr 17, 2018 at 4:18 PM, John Meinel  wrote:

> We should get a bug following this. But essentially Bionic changed how
> networking configuration is being done, from /etc/network/interfaces to
> /etc/netplan/*.yaml files.
>
> When we started implementing support for netplan, they hadn't finished
> support for bonds, so we didn't implement support for reading bonds and
> configuring them.
>
> They have since finished supporting bonds in netplan, and we need to
> update our support for netplan to include bonds.
>
> While we *could* just not past "strict" to the yaml library, I think the
> net result of that would not be positive, because we might try to create
> configurations not being aware of part of your network.
>
>
> On Tue, Apr 17, 2018 at 10:46 AM, Vidmantas Rinkevičius <
> vidmantas.rinkevic...@vgtu.lt> wrote:
>
>> Hi,
>>
>> During openstack deployment juju gives error on all lxd containers.
>>
>> Example:
>>
>> sudo juju status
>>
>> 3/lxd/0  down pending  bionic bridge activation
>> error: yaml: unmarshal errors:
>>   line 7: field bonds not found in struct netplan.
>>
>> yaml:
>>
>> openstack-dashboard:
>> annotations:
>>   gui-x: '500'
>>   gui-y: '-250'
>> charm: cs:~openstack-charmers-next/bionic/openstack-dashboard
>> num_units: 1
>> bindings:
>>   website: web
>> options:
>>   openstack-origin: distro-proposed
>> to:
>> - lxd:3
>>
>>
>> I am deploying 18.04 and I use network spaces.
>>
>> Any ideas why this error occurs?
>>
>>
>>
>>
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/juju
>>
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: bridge activation error: yaml: unmarshal errors:, line 7: field bonds not found in struct netplan

2018-04-17 Thread John Meinel 
We should get a bug following this. But essentially Bionic changed how
networking configuration is being done, from /etc/network/interfaces to
/etc/netplan/*.yaml files.

When we started implementing support for netplan, they hadn't finished
support for bonds, so we didn't implement support for reading bonds and
configuring them.

They have since finished supporting bonds in netplan, and we need to update
our support for netplan to include bonds.

While we *could* just not past "strict" to the yaml library, I think the
net result of that would not be positive, because we might try to create
configurations not being aware of part of your network.


On Tue, Apr 17, 2018 at 10:46 AM, Vidmantas Rinkevičius <
vidmantas.rinkevic...@vgtu.lt> wrote:

> Hi,
>
> During openstack deployment juju gives error on all lxd containers.
>
> Example:
>
> sudo juju status
>
> 3/lxd/0  down pending  bionic bridge activation error:
> yaml: unmarshal errors:
>   line 7: field bonds not found in struct netplan.
>
> yaml:
>
> openstack-dashboard:
> annotations:
>   gui-x: '500'
>   gui-y: '-250'
> charm: cs:~openstack-charmers-next/bionic/openstack-dashboard
> num_units: 1
> bindings:
>   website: web
> options:
>   openstack-origin: distro-proposed
> to:
> - lxd:3
>
>
> I am deploying 18.04 and I use network spaces.
>
> Any ideas why this error occurs?
>
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/juju
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

bridge activation error: yaml: unmarshal errors:, line 7: field bonds not found in struct netplan

2018-04-17 Thread Vidmantas Rinkevičius 

Hi,

During openstack deployment juju gives error on all lxd containers.

Example:

sudo juju status

3/lxd/0  down pending  bionic bridge activation 
error: yaml: unmarshal errors:

  line 7: field bonds not found in struct netplan.

yaml:

openstack-dashboard:
    annotations:
  gui-x: '500'
  gui-y: '-250'
    charm: cs:~openstack-charmers-next/bionic/openstack-dashboard
    num_units: 1
    bindings:
  website: web
    options:
  openstack-origin: distro-proposed
    to:
    - lxd:3


I am deploying 18.04 and I use network spaces.

Any ideas why this error occurs?






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