Re: Juju Openstack - Blocked

2018-02-15 Thread James Page 
Hi James

On Wed, 14 Feb 2018 at 20:22 James Beedy  wrote:

> Hello,
>
> I am experiencing some issues with a base-openstack deploy.
>
> I can get a base-openstack to deploy legitimately using MAAS with no
> apparent errors from Juju's perspective. Following some init ops and the
> launching of an instance, I find myself stuck with errors I'm unsure how to
> diagnose. I upload an image, create my networks, flavors, and launch an
> instance, and see the instance erring out with a "host not found" error
> when I try to launch them.
>
> My nova/ceph node and neutron node interface configuration [0] all have a
> single flat 1G mgmt-net interface configured via MAAS, and vlans trunked in
> on enp4s0f0 (untracked by maas).
>
>
> Looking to the nova logs, I find [1] [2]
>

You can ignore most of those errors - prior to the charm being fully
configured the daemons will log some error messages about broken db/rmq
etc...  newer reactive charms tend to disable services until config is
complete, older classic ones do not.

The compute node is not recording and error which would indicate some sort
of scheduler problem - /var/log/nova/nova-scheduler.log from the
nova-cloud-controller would tell us more.

The bundle I'm using [3] is lightly modified version of the openstack base
> bundle [4] with modifications to match my machine tags and mac addresses
> for my machines.
>

Seems reasonable - bundles are meant as a start point after all!

I've gone back and forth with network and charm config trying different
> combinations in hope this error is caused by some misconfiguration on my
> end, but I am now convinced this is something outside of my scope as an
> operator, and am hoping for some insight from the greater community.
>
> I seem to be able to reproduce this consistently (using both Juju < 2.3.2
> and 2.3.2).
>
> Not even sure if I should create a bug somewhere as I'm not 100% sure this
> isn't my fault. Let me know if additional info is needed.
>

 Lets dig into the scheduler log and see.

Cheers

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

Application names starting with digits

2016-12-02 Thread James Page 
Hi All

Is there a specific rationale for application names being limited to not
starting with a digit?  I get why they can't end with one but I don't see
why juju should place the same restriction on the start of an app name?
Example (where we tripped over this):

   juju deploy ubuntu 6wind-virtual-accelerator

(and ubuntu just to test the name out of a proposed charm where we had
testing problems due to this limitation)

Thoughts?

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

Re: Charmers application - David Ames

2016-03-21 Thread James Page 
+1

On Mon, 21 Mar 2016 at 15:37 Chris Glass 
wrote:

> Big +1 for thedac here as well.
>
> I'm actually surprised he's not a charmer already!
>
> On Sun, Mar 20, 2016 at 3:11 PM, Liam Young 
> wrote:
> > tl;dr +1 for thedac
> >
> > I've worked on charms with David since the ol' pyjuju days. He has made
> > numerous excellent contributions to the Openstack charms, charmhelpers
> and
> > charms from the wider community. He is also an excellent reviewer and
> can be
> > depended on to give a merge proposal a thorough dissection and offer
> helpful
> > suggestions.
> >
> > On Sat, Mar 19, 2016 at 11:38 PM, David Britton
> >  wrote:
> >>
> >> Big +1 for thedac
> >>
> >>
> >> On Saturday, March 19, 2016, James Beedy  wrote:
> >>>
> >>> Team -
> >>>
> >>> David played a monumental role in resolving a handful of issues I was
> >>> hitting my head on while trying to solidify my HA Openstack, also with
> DVR
> >>> issues which I was experiencing prior. The issues I was experiencing
> were
> >>> rather in depth and complex. David went a great deal out of his way to
> >>> identify where the bugs were in the charms that were at the root of my
> >>> issues, and ensured the issues I was experiencing were exploited and
> >>> resolved in the respective charms. By doing this, I feel David has
> >>> subsequently played a large role in solidifying the core functionality
> of
> >>> the charms. It is evident that David cares a great deal about the Juju
> >>> ecosystem, producing quality artifacts, and the community in general.
> It has
> >>> been a pleasure working with David, and I look forward to working with
> him
> >>> in the future!
> >>>
> >>> Thanks David!
> >>>
> >>> ~James
> >>>
> >>
> >>
> >> --
> >> David Britton 
> >>
> >>
> >> --
> >> Juju mailing list
> >> j...@lists.ubuntu.com
> >> Modify settings or unsubscribe at:
> >> https://lists.ubuntu.com/mailman/listinfo/juju
> >>
> >
> >
> > --
> > Juju mailing list
> > j...@lists.ubuntu.com
> > Modify settings or unsubscribe at:
> > https://lists.ubuntu.com/mailman/listinfo/juju
> >
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju-dev
>
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: Automatic retries of hooks

2016-01-21 Thread James Page 
On Wed, 20 Jan 2016 at 20:31 William Reade 
wrote:

> On Wed, Jan 20, 2016 at 8:01 PM, Dean Henrichsmeyer 
> wrote:
>>
>> You realize James was complaining and not celebrating the "success" ? The
>> fact that we can have a discussion trying to determine whether something is
>> a bug or a feature indicates a problem.
>>
>
> Sorry, I didn't intend to disparage his experience; I took it as
> legitimate and reasonable surprise at a change we evidently didn't
> communicate adequately. But I don't think it's a misfeature; I think it's a
> necessary approach, in service of global reliability in challenging
> environments.
>

You didn't - don't worry!


> But: if there are times it's inconvenient and not just surprising, we
> should surely be able to disable it. Gabriel/Bogdan, would you be able to
> address this?
>

I Agree with David's +1 on this feature with the condition that it can be
disabled so that charm authors actually understand the behaviour of the
software they are deploying.

Please lets also ensure the retry limit is sensible - otherwise we might
end up with end-users waiting a loong time to understand that something
is not recoverable which could be equally as damaging.
-- 
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju-dev

Re: 1.17.6

2014-03-19 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 17/03/14 16:16, Curtis Hovey-Canonical wrote:
 Curtis- Is it possible to do a 1.17.6 in the middle of the week
 rather
 than waiting until Thurs/Friday? That would still let us get a
 1.18.0 out at the end of the week with a bit of focus.
 I can do a development release every day of the week if we exclude 
 ppc64el and arm64 (because they are built by Ubuntu. James May be 
 willing to do a 1.17.6 release for Ubuntu in the middle of the week
 if it supports juju-mongodb. Ubuntu wont be getting 1.17.5 because
 it breaks ppc64el and arm64.

Yes please! If .6 restores the juju-mongodb support I'm happy to push
for the FFe I'll need to upload.

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJTKYhAAAoJEL/srsug59jDDKMP/0zOPecZWScX54zgALuhIAvz
fpSDh7f2AwJenM3lMqwbxKz7Lrlcf/EP519DKVhJvvdXYvmSl4/2F5xLf1RJdbII
IPJ9sziUPjVQAdqDJBcg3x5cZkj5gd7P6PiDqg6r4OtiLH4bvucZDNPM/DOTkIih
pQ0scdn2/ClYQ5XqOviF0Q8dgP8tTNh2gWz4p6gZL8MayY6vZ9xsKGE7vyEmFGIp
cbX3X0HY/7KLpL7TJKUnNy4o1T+600+nicPPVuDy6/9Zj6zgmLamWCjONmWspJTE
zGZeyhTDFjq9QSo4S73dFXPckPRqbJAgzQpfjj+59gfj5ty4poZjABgc0/P4M+LJ
cNY6BWDB3x0Os8VoUIkgMvOngoNn4/KoyHM0RwV/PfuuU5KF8iEOisH9oTs5p2B9
f3L5JkoXk44evDJztrirUXrXto8e5YgTnA5sgT1w5Pqc5+v6y484akHpMgmA7W/o
AYwc+3zoiT89MoE1W/sH8zgppCOdm0yM0eaFEtFUbNGn9OGltnqZEex8+SXDoCuB
tIFcmWe7yTk7x4olZmYqQX8aLyogKLc8cGHonHE9qFxulbAzUSvgiXYsykzctEce
CO4yIIrXbKrNMHleujfOk3eoCWxDk8rnPdqowHxeafwwlCq0S956eRmzZ7+Bj6Z5
WggcJQ71Z0GK9Y0mbMxP
=XXJp
-END PGP SIGNATURE-

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

Re: Juju 1.17.0 on trusty means no production work

2014-01-24 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Curtis

On 23/01/14 19:53, Curtis Hovey-Canonical wrote:
[...]
 I am happy to run trusty and test the new packaging of stable 
 software. Juju 1.17.0 is not stable, it is not compatible with
 1.16.x, and was not given a choice, nor informed that I could be
 risking someone's assets. I don't think ubuntu devel series should
 be getting devel juju, at least not until we have full devel to
 stable compatibility testing.

FWIW I did raise this at the cross-team meeting on the 16th of January
so people should have been aware that this work was happening; the
rationale for the 1.17.0 release upload was:

1) its the first release to support gccgo - and we need to be testing
with juju built using this toolchain.
2) its closer to the stable release we will be releasing with.

We really need to kickoff the Main Inclusion Review process now if
juju is to be in main for 14.04; asking the MIR team to review the
previous stable release of juju seems pretty pointless when its going
to be using a different toolchain and work in different ways for release.

[...]
 For the time being, I am going to create a stable trusty juju and 
 place it in the stable ppa so that some people have a choice to 
 respond to production situations.

If the situation is that bad, then I can revert the 1.17.0 upload to
trusty and switch back to 1.16.5.

Regards

James

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJS4iKaAAoJEL/srsug59jDnfkP/0NYpEGX9AHF3LRheMTquZo3
8CmO75HUfobucNLEctm0nnUI95krzxIlQBUlbny4qPwKN3mDDkv7Efpnl8upV4oi
NJUs1JKgRmyYxKwHJC7i2C+NnQ+4M1G3ChcaIxZjzHINJk9gZy1FG1e99i3X18Fs
lgp0rjQmqlt9eJ/q/HBRrezfosQXtEgSnM/Yst6p/eKMyr9hiXI+Y4NiZhlJB835
ylqy5n2tboPxkI7UUqhTY26XKrME9VV7UBZlhL1nNtIdWlzvUi8pYvsBS+n1+IiM
Bz0Ue9XjbNjWxOZUFDzpa9wmxb+odmZe57C86/M2PNQ7bixiCH4IeVu7h9v/Zgir
JOThndTRvfnrpWL/6MfSnx5tIuyI8zxZb9GYEJpo56290YOlNiO6l8aeX/5umUWu
fMHiyzVSWPrArNNaxMAfAaNAuahTJrLFvyMqi0GCtfk3jeCx7CD+XoSRxanZM6Ln
fOzs8kGK9ChgOs8hqP5b0vQBGMb/a8+dBex9kzFupUrvSgYe40tr6/GKPBA13qfi
JfXWAt6nYukdjrHuDr8vTxwC0xWZDIWZsFyHpVpUg01CIlD2WmKOXUKcJoNgb/Mk
sL0PMgdPd/hF/riNcRJscKKSf+myGIa9PW1hW3ZWzrdk9JHrVbZVyrqK7QJxfsLg
YTWnKF8k75a6QUqa7gwM
=jeui
-END PGP SIGNATURE-

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

Re: KVM provisioning now in trunk

2013-12-04 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Tim
On 04/12/13 04:44, Tim Penhey wrote:
 For those who like living on the edge, we now have KVM container
 support in trunk.

Nice work!

 It is kinda hard to confirm it fully works right now. I need to
 actually test it on a MAAS install that is KVM capable.
 
 Constraints aren't yet supported, that should be coming tomorrow 
 (fingers crossed).
 
 Also landed recently is a KVM option for the local provider.  For
 the truly trivial, add container: kvm to the local
 configuration.

Is it possible to mix LXC and KVM containers under the local provider?

I can think of one use case where this would be useful.

Cheers

James

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSnwkvAAoJEL/srsug59jD0VUP/iVA6WQbTjzutedojJTSnLzY
cnOOaovo3cZFEmLp1jeeOO0X8cLBMGbyXiquYm51iDZakARqaqmgJjDUqqRkpHvd
4dGdMGSBjmTtiySOnhkjcOZrJYXlPdj3E1IPLBQR692TvbCqaniLt96U8ax5E6pE
ZtZ770WCXPbOFQdscQgoHHd+SOfeNjCTorkbbgURREwNKKmcZKUv79xtCZO46YOE
YxQ9eYdl52P/VpogIWy8OSSycILCvlLLHSl5iQLXAkrengug0X3O0k3ZsnDmmDHS
wvjKb49YfCiQ0VIoFZQqcYvKtm866cWIkzQqDkpA/heiv6Yzsv4DC0CZHHQYheYd
FBjQcG17LV/SeoK2b8wHWU8Ivk+CG+gfzISMXd0hW+it7tpkMD4c31i0kjbxiEAK
3bwU/p4vK+1aFdK2u7r6UNNEyaO0J70ROpPpuagMeizgf+HZc5crSIlaQ9LrbtHf
0byFcSEu2Rivw5Y9VourWSEeLrKZujZA1Cj0UYt1jSxyw9iKw4qe+SzskciF9EbJ
tIEuw4UZCH1Heu986PlLWz8y1a48Ihz/MUmkTk2WZn9Pwxg9MsUQ3JSHkURxutk/
LkpXqZHYSDvDnikcAK1rNQJYtEWYLQOggwWdoEkt5l0VdHoNAxjph126oO6BDHpl
hDY5YaiwL/QIBb7t/eDH
=L9pw
-END PGP SIGNATURE-

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

Re: New juju-mongodb package

2013-12-02 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Morning folks

so far I have requests for:

mongo (default shell)

mongoexport (used in new juju backup plugin)

mongodump/mongorestore (useful)

I'm keen we don't bloat out the 'server' package to much - the
binaries are quite large due to the requirement to statically link v8.

Which of these is core to the function of juju, and which are useful
for debugging?  Please also that the mongodb-clients package will
still be available in universe so you will always be able to get any
of the client tools that way as well (I'll probably keep those
packages maintained to the latest point release for the released series).



On 28/11/13 20:10, Ian Booth wrote:
 Also mongoexport (used in the new juju backup plugin)
 
 On Fri 29 Nov 2013 03:53:06 EST, William Reade wrote:
 The mongodump and mongorestore binaries would also be extremely
 useful.
 
 Cheers William
 
 
 On Thu, Nov 28, 2013 at 3:38 PM, James Page
 james.p...@canonical.comwrote:
 
 
 
 * *BEGIN ENCRYPTED or SIGNED PART* *
 
 On 28/11/13 14:18, Gustavo Niemeyer wrote:
 It would be good to have the mongo binary available and
 working as well, also under that juju-specific namespace. This
 is the console client, and will be useful to connect to the
 local juju database when debugging issues.
 
 Makes sense - added.
 
 -- James Page Technical Lead Ubuntu Server Team 
 james.p...@canonical.com
 
 
 ** *END ENCRYPTED or SIGNED PART* **
 
 
 -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify
 settings or unsubscribe at: 
 https://lists.ubuntu.com/mailman/listinfo/juju-dev
 
 
 -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify
 settings or unsubscribe at:
 https://lists.ubuntu.com/mailman/listinfo/juju-dev
 
 
 
 


- -- 
James Page
Technical Lead
Ubuntu Server Team
james.p...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSnEx9AAoJEL/srsug59jDtMoQAJIV0V8mfvhuu3bkXRyG1uF2
UBh1IHgULMzK6n59qxbpk5foHa+ilMbpSmRXec8ynNLXpV5fxYch4kv3IPzTvBty
y6vNsaHEgTb8cay61IHIZtOwPd99tUQddMllT7hurB88fJ7zfL409xXJCOdIRJ+c
Qpj1WUfH64J/DtZLQ5ZSaVTtYxgM8G4DWo9CCpe+KdKWw/QkyxKSVt6ych5yXNzb
2sGZm5Ub2jHaz/ynK8H4bLPvTYj+0cg0k9v3gcmv8ctMvXZmujKgcqLp0iGD2krA
H3ZHmuw9lnKZDqJFZQAgUSEdQIirVE2WwNcnT7YWUJbbw8wXuIUJnNu7AkE4UdNb
9q4hwGVphrTsW8hWsrpsHFsi92IMuU+Y6IvLzwnCbde06rNJitt4UdulV435bOg3
UbKmOzndomS0OPZON+ya0AOfbZ1iwfgVP8vSGbDdr06CyOc+okiuewvb2+RrXXdP
N7zqIdNJ5bVUo5iM1EjDg7FJDNdlACYZkiol9eDHo1AnXBgObyPxOmdshPvknHkf
kf2Ia8oPjrcgolxMJnjh88RfaLLnbsyVujGujVYJ7RqrQjgvIlM9BaLnKHITWUPr
OA3A9S5VF+8gbNVmLxMatBHN3MDITWgVsgOMDzMscRW5SGzJ86gfhuFdudDyBlZN
HFDb9O5tqE7mP60KQBDa
=7rS2
-END PGP SIGNATURE-

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

Re: New juju-mongodb package

2013-12-02 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/12/13 09:10, John Arbash Meinel wrote:
 On 2013-12-02 13:01, James Page wrote:
 Morning folks
 
 so far I have requests for:
 
 mongo (default shell)
 
 mongoexport (used in new juju backup plugin)
 
 mongodump/mongorestore (useful)
 
 I'm keen we don't bloat out the 'server' package to much - the 
 binaries are quite large due to the requirement to statically
 link v8.
 
 Which of these is core to the function of juju, and which are 
 useful for debugging?  Please also that the mongodb-clients
 package will still be available in universe so you will always be
 able to get any of the client tools that way as well (I'll
 probably keep those packages maintained to the latest point
 release for the released series).
 
 Is mongodump/mongorestore going to be in the mongodb-client or 
 mongodb-server?

Currently I was just planning a juju-mongodb package; however we could
split things that need to be on the client end of juju into a
juju-mongodb-clients package.

 How is this going to relate if we have to release a custom version
 of MongoDB (2.6 instead of 2.4).

Yeah - that is tricky; that's why I was asking what do we need, rather
than what is nice to have; I would suspect that mongo shell is
probably forward compatible for example but that would not be nice if
it wasn't.

 The only thing we actively use on a regular basis (AFAIK) is
 mongos and mongod. However, if we set up regular backup process,
 then we'll need one of mongodump or mongoexport (I don't know what
 the difference is between them). And obviously dump isn't very
 useful if you can't restore, though at the point you are restoring
 is a reasonable time to create new tools.
 
 I don't fully understand the difference from mongoexport vs
 mongodump (it looks like dump generates a binary snapshot
 compatible with restore, while export/import generate text
 representations of the data.)
 
 I'd *really* like us to stick with *one* of them as the
 recommended method for backing up the content.

+1 - we can add them all but it bloats out a bit.

 At which point, mongos, monogod and mongoexport/mongodump become 
 critical for the regular operation of the system (assuming we set
 up backups as a regular process), and then mongo, 
 mongoimport/mongorestore become tools that you install when you
 want to inspect/restore/probe/etc.
 
 If you're happier splitting them, I'm personally fine with that. I 
 *am* a bit concerned about them being split and then we bump the 
 version of juju-mongodb and then we end up without the
 corresponding tools available.

Installed sizes (taken from saucy which has the same v8 embedding):

- -rwxr-xr-x 1 root root 7.2M Sep  5 15:30 /usr/bin/mongo
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongodump
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongoexport
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongoimport
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongorestore

Expect about ~50% compression;

- -- 
James Page
Technical Lead
Ubuntu Server Team
james.p...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSnGGZAAoJEL/srsug59jDjBcP+gNXfsVb29GqxlK9iICokbRO
8+zUueVR7BNf9CP10+p0xDcPRQPsiUZ7WTkqqvdXXtu/Mu3Y1OWIxLTidwz5DlBm
Mi+oTebFDfd4oKiJHCC1GGoXs0wUioumjE++qfIafl1cV1YkbmxClewS6OczDf9I
IsdzadFrArhmEwcyNUtDuAk4d2jJDy7s0ijYutFqNihWpGYE0aqG268Hk8lS6Ik3
+OftTOa7rDfH6F8Dd7/YACRPH6iYmwbyaNJrIzWmobWIkVvSp4RRVpsSQAUR3EMi
Vu2oT0ipg+ySYL7ZsCYtqHkZbKh+Ft/p4ZBi03TzHj4aHBmmehgXxTKEglX+MRN5
7nOnLmNd5VSqu8Ur85P/E+FWB01eUUh8FL4nA4j1SXwwlf10YE4iFf/MVRBJBK5k
LC7XZ0KqPjO3dcahCWfzg1fcRtXiEOBOXtiXsZu6WwyjRQq5UoHsh44yDeP5U4Kl
g8xIYK0t1qmgYFzQPQnzoR4fGYPnVECgdfDA0kuC/1lxZJ4XEsK+Wis7rWFU6Ny7
rKj0S+6QHseg49WVYIpwRU98/2YWvG/clrCXVSv1cJQx0OevRLImN42GFJldZMLk
PxRzsOzSommTng6jgXmLb89JCk4yegnRX8OrOLxVljWhaYPbiI1DfDhjIcukz6Vl
gSGKQdNUoS5jgHH7LF6X
=0AjE
-END PGP SIGNATURE-

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

Re: New juju-mongodb package

2013-12-02 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 02/12/13 09:15, John Arbash Meinel wrote:
 Which of these is core to the function of juju, and which are 
 useful for debugging?  Please also that the mongodb-clients
 package will still be available in universe so you will always
 be able to get any of the client tools that way as well (I'll
 probably keep those packages maintained to the latest point
 release for the released series).
 Looking at the juju-backup script, it is intended to use both dump
 and export. The export is so that we end up with JSON format for
 our settings table so we can extract content from there as part
 of restore (what credentials were you using, etc).
 
 Are they both really big? If so, we can probably use: mongo --eval 
 STUFF instead of mongoexport, but that would again presume that
 we have a 'mongo' binary available.
 
 I *believe* the data in the mongo dump is just BSON encoded, so it 
 would be possible to post-filter it with a bson aware tool to get
 it into human-consumable form (rather than using mongoexport at
 backup time).
 
 I guess the question is, how expensive is it to include it? For
 Juju core folks the cost of including it is all externality so *we*
 aren't particularly motivated to keep our toolset minimal. But if
 there is a use case we want to support, we're willing to help.

Installed sizes:

- -rwxr-xr-x 1 root root 7.2M Sep  5 15:30 /usr/bin/mongo
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongodump
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongoexport
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongoimport
- -rwxr-xr-x 1 root root  13M Sep  5 15:30 /usr/bin/mongorestore

Expect ~50% ish compression for the package itself.

Lets think about download sizes/times for end-users in this context
please :-).  It costs time for every server that's provisioned.

- -- 
James Page
Technical Lead
Ubuntu Server Team
james.p...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSnGKXAAoJEL/srsug59jD5nAP/1/y5gMfvrof1HaR85rIASuF
IsfrAHpPUzLcaRlPhReuhjfHaOCm2iEoKu91C6tJHp5moYfTuwKmdJAWSkaNVVoZ
dHyijS92G6socnKFL1uT1hWb48Eaf/glEIPo2zwsyIphnCRxQGrwJOXywYgyQlRd
c2Sac2PdW1Bukyrc5DNpv62bai+7RL//stwLuWPrYb29+gq5IgiWSW/FGLGZPy/1
+hiID7vC2CfnkKCOiYryfCd/ZfThEZQzAFs2Vazgq8vVSb6vDJKbInp4KlXwcI3Y
SHYBXv6duIFxfQZNYNRFiUJ2cHwVtSviiK7nZPFpzrCfJjoahSpoG05fnvHqU/eC
d1P2JGuvIhxwSJzOY12W5278kHko4udC8j02vdrmJEJeQj23V3dDmWe747Dx9V2a
faTq6qmQ3PY+WUgAp9R5GRv41fi+UIuzHjL39DylCZzZjR/G3w1weZjRIy3ykg11
6SDhFIeGklZ1LxSSWQi/0MDxrr0IpMm+YXKKZ8v1C47MQs1Ot6qLaNL3+wXULmHZ
SQzFUyZL/99xd+0OH3+AK2i/2GF77x1euUPu2ze9m2rcBtUYw7udm5R0m+MkuJaT
ETxL1ZQ5gi1kjS3hA+syxF/pCi2EcGl49NPJEzRT18taoN6ArVgXIKtCme40qFoE
4oOoAeOdnkP4IosaEYSB
=VrGq
-END PGP SIGNATURE-

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

New juju-mongodb package

2013-11-28 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi Folks

I've started working on the new, stripped down, juju specific MongoDB
package that we have been discussing over the last few weeks.

I'm proposing a package structure like this:

  ./usr/lib/juju/bin/mongos
  ./usr/lib/juju/bin/mongod

No users will be created; its just the binaries; upstart and general
system configuration such as creating users will be the responsibility
of juju.

The mongod and mongos binaries will be provided in a juju namespaced
location to avoid conflicting with the standard mongodb package; v8
will be linked statically using the embedded copy of v8 in the mongodb
source code - this avoids exposing v8 generally in main and allows the
security team to manage mongodb/v8 in the context of its use with
juju, rather than in more broad general use.

The plan is that we will apply for a minor release exception for this
package, and that if need be we can update to a new major release (2.6
for example) at some point in the future without impacting the rest of
the distro by bumping the standard mongodb package.

The total compressed package size is about 7MB - expanding to about
23MB on disk.

I still need todo some work on getting the embedded v8 copy to build
for armhf (MongoDB upstream strip this out) - arm64 has been discussed
but that's going to need some work upstream to enable v8 for this
architecture.

Other bugs pertinent MongoDB/juju usage would include:

  https://bugs.launchpad.net/juju-core/+bug/1208430

I'm pretty sure that running mongodb not as root will be part of the
security team signoff on the MIR review.

Cheers

James

- -- 
James Page
Technical Lead
Ubuntu Server Team
james.p...@canonical.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSl0lPAAoJEL/srsug59jDwrkQAKQuDJsm5I8YPeIwzTv+4/Gd
mcIQHcPer3EHaMB9/4zjWg8EoNuU0dj52PCjEEbI6zBZek1VqqxYLbsLxdzoo6x1
SAVulHOCG/oVcjL/XVQ7EYTodZrXOEAYKlAOOxI2pj9ea6XoQVI3i4SsZdMCNUyr
+CBUKrxH8YPcM3mXIyJBw0qbiHFLJQsywC1gZnsLTomox2Ob+eIk+n/CH2d0tMv3
DyD5c5GAypnHzmrsiteJuPu01OqMaYsiltRWaFFEzuV7C8eIVW4uRFowC+xX8a0i
UZ6FTUri4l9F4OahoJdVyjTofgQuis6pa/uKQWp7AUA+40JB/uMKApNV1xJ1772c
8YXVYNVYEc9r+x/LzuqFyHt1BEdqYgDt4ZG7mYR0AwW4p4eK7wAFRElH8JPVdEQ9
9iDFV/FFFCcWdVKRKSUuDCdv3bCNnEOLZU2qD0db9IPUNfGGeedkrSJAXGxBiCkg
9OBxp4xylrbU4gw9tJDmicctIXG6N+n/XMlsDj5FkWqmGAq3HqdXw6VCPJ48X7+m
ZHnXoQniR0eoh021xxFmb+f4eTG6U9YY8oyefMERLliVD/a26qQ6VQDa0M1mJig1
OQzbJoaXbuJulew7B+sFI0ltMtx6CVhtyXobKATEKMrzs5GcqT15B7+K5W0Uisca
Wp2ySVEZGOc3Sv3fobBC
=XBGC
-END PGP SIGNATURE-

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

Re: [ANN] juju-core 1.13.2 has been released

2013-08-26 Thread James Page 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 25/08/13 13:17, David Cheney wrote:
 Thanks John. James -- I have uploaded the release tarball now,
 sorry about the delay, I was in an airplane.

No problem; juju-core 1.13.2 also uploaded to Saucy.

Cheers

James

- -- 
James Page
Ubuntu and Debian Developer
james.p...@ubuntu.com
jamesp...@debian.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBCAAGBQJSGxsTAAoJEL/srsug59jDoYwQAMKovqEhdrY8BdrHNZZWjnXx
O/DH+SPpbIyyvdLqiuURpAjMXfTrUW9sOOYPmT0L/3KxokyDLvXsYJTau+v1S2m7
0yZIG8qWkMA5CBzgUoMd1tdxbJWIYEdpKvEaJaMypgB5KBZaJMSA5ZruyQwZXLM5
wgJXxRxGDXrJqfazrD+j6t+Mexd3PaFB2LWpla0HdqLXc2nAjn7ltGz7euWJNB3E
n56R9J3YoFPQwUnHUnW63iCIjiBzh02A2wS72rao/V/3rCRIrR5moPRf2Y8edr+g
wURt4jSD49h0KfNciz5FMTjms08txLXla/zfSP2T8Gb/Dbptf0zznuw5YCV1WeJG
5MGm9QD9SKi3kvd9hKMXLgHJxZOw0ilsorO/nLDP3wEMTM/x2O8gaOaB0YkAht2g
PaiJOfIXwpVZRuZmOYufvCutozO3s755zy99QRTvQMb2/SRTnRM2I9GHgkJWgNKX
Bw0l0mQjHNL9CNhcug/obrWFIgNlGUBcz6cQo2d5VH3qa3hK0PnYmiy1mzVvFz3/
HJxV6FEB8VUdjrsqpzYdkGXWpD0qXlodaTBrXKJyrY/6/Z+hgS7tsxjjfh/cOEnw
GH3564WvZYWMeFI2WKhXaVoyD/FC+Go5MtKR2Z1Y9nb3QQ/sR4vgeIBQlUuthyPs
KxwNytIEP+nDYg2YEr9x
=iqal
-END PGP SIGNATURE-

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