Re: Need info for deploying Mariadb as xenial

[Daniel Bartholomew]

On Mon, Jun 27, 2016, 7:40 AM Rajith P Venkata  wrote:
>
> Hi
>
> I am deploying mariadb5.5 on juju 2.0, I am getting error . Mariadb charm
> supports only trusty , is there a way we can have Mariadb charm deployed
> with series  xenial

MariaDB 5.5 is entirely unsupported on Ubuntu Xenial. The Ubuntu
repository for Xenial only has MariaDB 10.0 in it and the MariaDB
repositories for Xenial only have MariaDB 10.0 and higher in them. The
MariaDB Ubuntu repository for MariaDB 5.5 only supports Ubuntu Trusty
and Precise. My guess is that that is why the charm is failing, the
packages you are trying to install don't exist.

-- 
Daniel Bartholomew, MariaDB Release Manager
MariaDB | http://mariadb.com

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

Nasty MongoDB upsert behaviour

[Menno Smits]

Christian and I have just learned about an unfortunate property of upserts
in MongoDB. It's documented, but unexpected, and I doubt many people know
about it. From the docs:

With a unique index, if multiple applications issue the same update with
> upsert: true, exactly one update() would successfully insert a new document.
>


The remaining operations would either:
> * update the newly inserted document, or

** fail when they attempted to insert a duplicate.*



If the operation fails because of a duplicate index key error, *applications
> may retry the operation* which will succeed as an update operation.


 (
https://docs.mongodb.com/v3.2/reference/method/db.collection.update/#use-unique-indexes
)

This means that an upsert may result in either a new document being
inserted, an existing document being updated, or a duplicate key error
being returned. If the duplicate key error happens it's up to the client to
retry. Yuck!

These semantics exist in all versions of MongoDB that we use with Juju but
under 3.2 with WiredTiger duplicate key violations with upserts seem to be
happening a lot more often. We've been seeing them occasionally with
upserts into txns.stash that mgo/txn does.

Christian and I are about to propose a PR for mgo/txn which deals with this
issue but a check of the Juju state package shows a number of other uses of
upserts which also need to be changed. The most important of these is
probably the upserts for the sequence collection. Christian and I will look
at these next.

Please keep this in mind when interacting with MongoDB.

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

Re: Fwd: nfs kernel server installation failed in lxd container

[Shilpa Kaul]

Thanks Tycho,

I was able to install the nfs-kernel-server on the LXD container. I ran 
the steps for setting the default lxc profile and making the container as 
privileged on the host machine.
After this I deployed my charm and it worked fine.

Thanks and Regards,
Shilpa Kaul



From:   Tycho Andersen 
To: John Meinel , Shilpa Kaul/India/IBM@IBMIN, 
juju@lists.ubuntu.com
Date:   06/22/2016 08:01 PM
Subject:Re: Fwd: nfs kernel server installation failed in lxd 
container



Hi Shilpa,

[apologies, I wasn't subscribed to this list, so I can't reply to the
original message]

On Wed, Jun 22, 2016 at 05:49:35PM +0400, John Meinel wrote:
> -- Forwarded message --
> From: "Shilpa Kaul" 
> Date: Jun 20, 2016 19:32
> Subject: nfs kernel server installation failed in lxd container
> To: 
> Cc:
>
> Hi,
> 
> I am using NFS for file sharing in my charm. To install 
nfs-kernel-server
> on LXC container(Juju 1.25), I had done the below steps on my host 
machine :
> *apt-get install nfs-common*
> 
> *modprobe nfsdmount -t nfsd nfsd /proc/fs/nfsd*
> Then edit /etc/apparmor.d/lxc/lxc-default and added the following lines 
to
> it and restart the apparmor
> 
> *mount fstype=nfs,*
> *mount fstype=nfs4,*
> *mount fstype=nfsd,*
> *mount fstype=rpc_pipefs,*

LXD doesn't use the `lxc-default` profile, but generates a separate
profile for each container for security reasons. IIRC juju uses the
default profile for LXD, so you could do something like:

lxc profile set default raw.apparmor "mount fstype=nfs,
mount fstype=nfs4,
mount fstype=nfsd,
mount fstype=rpc_pipefs,"

You'll also need to make sure the container is privileged, as
unprivileged mounting of nfs is not supported by the kernel right now:

lxc profile set default security.privileged true

Tycho

> By doing this and further steps of installing nfs server and nfs client, 
I
> was able to share files between the LXC containers.
> 
> Now when I run the same charm on Juju 2.0(LXD containers), my charm 
fails
> as the nfs-kernel-server installation fails. In the logs I see the below
> messages
> 
> 
> 
> 
> *A dependency job for nfs-server.service failed. See 'journalctl -xe' 
for
> details.invoke-rc.d: initscript nfs-kernel-server, action "start"
> failed.dpkg: error processing package nfs-kernel-server
> (--configure): subprocess installed post-installation script returned 
error
> exit status 1 *
> 
> On doing journalctl -xe, I see lots of *"Operation not permitted*" 
messages
> and *"Failed to mount NFSD configuration filesystem"*error messages.
> 
> Can anyone please help me in resolving the above issue and configuring 
NFS
> Server on LXD containers.
> 
> 
> Thanks and Regards,
> Shilpa Kaul
> 
> 
> --
> 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

Post resource error

[Tom Barber]

I have no idea what this means and when I try and submit it again it tells
me the resource exists but:

bugg@tomsdevbox:~/charms/wily/dcos-master$ charm push .
cs:~spicule/wily/dcos-master --resource
software=~/Projects/dcos-master/bootstrap.tar.gz
ERROR cannot post archive: cannot unmarshal error response "http://www.w3.org/TR/html4/strict.dtd\;>\n\n\nERROR: The requested URL could not be
retrieved\n\n\n\nERROR\nThe
requested URL could not be retrieved\n\n\n\n\nThe following error was encountered while trying to
retrieve the URL: http://api.jujucharms.com/v5/~spicule/wily/dcos-master/archive?\;>
http://api.jujucharms.com/v5/~spicule/wily/dcos-master/archive?\n\n\nZero Sized Reply\n\n\nSquid
did not receive any data for this request.\n\nYour cache
administrator is mailto:webmaster?subject=Ca ... [3524 bytes
omitted]": invalid character '<' looking for beginning of value

Tom
--

Director Meteorite.bi - Saiku Analytics Founder
Tel: +44(0)5603641316

(Thanks to the Saiku community we reached our Kickstart

goal, but you can always help by sponsoring the project
)
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

New functional-ha-recovery-maas-1-9 is non-voting

[Curtis Hovey-Canonical]

We added a test specific to xenial maas 1.9 to help engineers
investigate HA issues in Maas 1.9: functional-ha-recovery-maas-1-9.

This test is current'y using xenial. There is also a test for trusty
that QA staff can run on demand to gather logs.

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

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

functional-charm-resource-charmstore now votes

[Curtis Hovey-Canonical]

The functional-charm-resource-charmstore job that tests user
permission in juju via grant and revoke commands now votes.

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

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

functional-unregister test now votes

[Curtis Hovey-Canonical]

The test of the unregister  command is now voting.

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

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

Re: Need info for deploying Mariadb as xenial

[Nate Finch]

You can use --series xenial --force  I don't know if there's anything in
the charm that might fail, though.

On Mon, Jun 27, 2016, 7:40 AM Rajith P Venkata  wrote:

> Hi
>
> I am deploying mariadb5.5 on juju 2.0, I am getting error . Mariadb charm
> supports only trusty , is there a way we can have Mariadb charm deployed
> with series  xenial
>
> Rajith
>
> IBM AIX Certified, OCPCertified
> 
>
> Email: rajith...@in.ibm.com
>
> --
> 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