Regarding Terms

[Shruthima Almavar]

Hi,
We have sent a request for terms creation through the terms link ( 
https://docs.google.com/forms/d/1sOfp0a6KLY9kqnpPeGwHv_YQJv7LEbXH1CAV-xBaMjU/viewform?edit_requested=true
)
for the following charms:

ibm-http-server
ibm-http-plg
ibm-http-wct
ibm-mobilefirstserver
ibm-spectrum-scale 


Could you please create terms as soon as possible.

Thank you..!!!

Regards,
Shruthima



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

Re: Regarding Terms

[Matthew Williams]

Just replying publicly to confirm that this was done earlier this morning

Thanks

Matty

On Thu, Aug 11, 2016 at 10:30 AM, Shruthima Almavar 
wrote:

> Hi,
> We have sent a request for terms creation through the terms link (
> https://docs.google.com/forms/d/1sOfp0a6KLY9kqnpPeGwHv_
> YQJv7LEbXH1CAV-xBaMjU/viewform?edit_requested=true
> 
> )
> for the following charms:
>
> ibm-http-server
> ibm-http-plg
> ibm-http-wct
> ibm-mobilefirstserver
> ibm-spectrum-scale
>
>
> Could you please create terms as soon as possible.
>
> Thank you..!!!
>
> Regards,
> Shruthima
>
>
>
> --
> 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

Point people to ubuntu-on-windows instead of the broken juju-on-windows?

[Merlijn Sebrechts]

Hi all


Juju-on-windows is pretty broken and it doesn't seem that bugs are being
fixed anymore. Wouldn't it be better to point people to Juju on "Ubuntu on
windows" instead? One of my colleagues started using it and it seems to
work just fine.

Some show-stopping bugs in Juju-on-windows:

   - `juju ssh` is not translating newlines correctly
   .
   - windows users can't create layered charms because the Charm tools for
   windows is still at 1.2.9.
   




What do you guys think?

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

Re: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

[Marco Ceppi]

On Thu, Aug 11, 2016 at 11:27 AM Merlijn Sebrechts <
merlijn.sebrec...@gmail.com> wrote:

> Hi all
>
>
> Juju-on-windows is pretty broken and it doesn't seem that bugs are being
> fixed anymore. Wouldn't it be better to point people to Juju on "Ubuntu on
> windows" instead? One of my colleagues started using it and it seems to
> work just fine.
>
> Some show-stopping bugs in Juju-on-windows:
>
>- `juju ssh` is not translating newlines correctly
>.
>- windows users can't create layered charms because the Charm tools
>for windows is still at 1.2.9.
>
>
> This is a doc mistake, I'll have an updated charm-tools msi before the end
of the week in the docs.

What do you guys think?
>

I think you've got a good point, however, not everyone is on Windows 10.
Pointing people who are on Windows 10 to WSL instead would be fruitful for
a good native experience.
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

[Nate Finch]

Just FYI - running the juju client on Windows is 100% supported and we
actively fix bugs on it all the time.   I hadn't seen the particular bug
you referenced about juju ssh, but that definitely seems like something we
should prioritize higher.  The linux ssh works so much better because we
can simply run the OS's ssh and everything Just Works, but that's not
possible on Windows, so it's much more involved to make it work (we
basically have to write an entire ssh client).

However, as a workaround, it would be pretty trivial to write a juju plugin
to launch putty with the right parameters.  Then you'd just do `juju putty
0` rather than juju ssh 0.  Obviously, it would open putty, not a CLI ssh
terminal, but the overall experience is probably a lot better than what we
could provide.

On Thu, Aug 11, 2016 at 11:41 AM Marco Ceppi 
wrote:

> On Thu, Aug 11, 2016 at 11:27 AM Merlijn Sebrechts <
> merlijn.sebrec...@gmail.com> wrote:
>
>> Hi all
>>
>>
>> Juju-on-windows is pretty broken and it doesn't seem that bugs are being
>> fixed anymore. Wouldn't it be better to point people to Juju on "Ubuntu on
>> windows" instead? One of my colleagues started using it and it seems to
>> work just fine.
>>
>> Some show-stopping bugs in Juju-on-windows:
>>
>>- `juju ssh` is not translating newlines correctly
>>.
>>- windows users can't create layered charms because the Charm tools
>>for windows is still at 1.2.9.
>>
>>
>> This is a doc mistake, I'll have an updated charm-tools msi before the
> end of the week in the docs.
>
> What do you guys think?
>>
>
> I think you've got a good point, however, not everyone is on Windows 10.
> Pointing people who are on Windows 10 to WSL instead would be fruitful for
> a good native experience.
> --
> 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: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

[Merlijn Sebrechts]

Hi Nate


Thanks for your quick reply! My colleagues will just 'upgrade' to windows
10 so this doesn't really apply to us anymore but wouldn't it be easier to
package putty with the windows juju client and use that as default? Writing
an entire ssh client seems a bit overkill.. or is there an advantage to
having a CLI ssh terminal?



Kind regards
Merlijn

2016-08-11 20:02 GMT+02:00 Nate Finch :

> Just FYI - running the juju client on Windows is 100% supported and we
> actively fix bugs on it all the time.   I hadn't seen the particular bug
> you referenced about juju ssh, but that definitely seems like something we
> should prioritize higher.  The linux ssh works so much better because we
> can simply run the OS's ssh and everything Just Works, but that's not
> possible on Windows, so it's much more involved to make it work (we
> basically have to write an entire ssh client).
>
> However, as a workaround, it would be pretty trivial to write a juju
> plugin to launch putty with the right parameters.  Then you'd just do `juju
> putty 0` rather than juju ssh 0.  Obviously, it would open putty, not a CLI
> ssh terminal, but the overall experience is probably a lot better than what
> we could provide.
>
> On Thu, Aug 11, 2016 at 11:41 AM Marco Ceppi 
> wrote:
>
>> On Thu, Aug 11, 2016 at 11:27 AM Merlijn Sebrechts <
>> merlijn.sebrec...@gmail.com> wrote:
>>
>>> Hi all
>>>
>>>
>>> Juju-on-windows is pretty broken and it doesn't seem that bugs are being
>>> fixed anymore. Wouldn't it be better to point people to Juju on "Ubuntu on
>>> windows" instead? One of my colleagues started using it and it seems to
>>> work just fine.
>>>
>>> Some show-stopping bugs in Juju-on-windows:
>>>
>>>- `juju ssh` is not translating newlines correctly
>>>.
>>>- windows users can't create layered charms because the Charm tools
>>>for windows is still at 1.2.9.
>>>
>>>
>>> This is a doc mistake, I'll have an updated charm-tools msi before the
>> end of the week in the docs.
>>
>> What do you guys think?
>>>
>>
>> I think you've got a good point, however, not everyone is on Windows 10.
>> Pointing people who are on Windows 10 to WSL instead would be fruitful for
>> a good native experience.
>> --
>> 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: Point people to ubuntu-on-windows instead of the broken juju-on-windows?

[Jorge O. Castro]

On Thu, Aug 11, 2016 at 2:02 PM, Nate Finch  wrote:
> The linux ssh works so much better because we can simply run the OS's ssh
> and everything Just Works, but that's not possible on Windows, so it's much
> more involved to make it work (we basically have to write an entire ssh
> client).

Microsoft announced that OpenSSH will be coming to Powershell at some
point, so that's probably the client we should use when it lands.

We can track progress here since they OSSed Powershell:

https://github.com/PowerShell/Win32-OpenSSH/wiki/Win32-OpenSSH-RoadMap

Sounds like it should be ready for us to at least play with soon?

-- 
Jorge Castro
Canonical Ltd.
http://jujucharms.com/ - The fastest way to model your service

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

Re: maas in a container

[Jason Hobbs]

Daniel,

Can you show the full dump of your profile and container configs?

Here's what my 'maas' profile looks like:

ubuntu@beartic:~$ lxc profile show maas
name: maas
config:
  raw.lxc: |-
lxc.cgroup.devices.allow = c 10:237 rwm
lxc.aa_profile = unconfined
lxc.cgroup.devices.allow = b 7:* rwm
  security.privileged: "true"
description: ""
devices:
  eth0:
name: eth0
nictype: bridged
parent: br1
type: nic
  loop0:
path: /dev/loop0
type: unix-block
  loop1:
path: /dev/loop1
type: unix-block
  loop2:
path: /dev/loop2
type: unix-block
  loop3:
path: /dev/loop3
type: unix-block
  loop4:
path: /dev/loop4
type: unix-block
  loop5:
path: /dev/loop5
type: unix-block
  loop6:
path: /dev/loop6
type: unix-block
  loop7:
path: /dev/loop7
type: unix-block

Here's the config for the container maas is running in:
ubuntu@beartic:~$ lxc config show maas-server
name: maas-server
profiles:
- maas
config:
  volatile.base_image:
d23ee1f4fd284aeaba6adeb67cccf7b871e96178d637fec96320aab7cc9634b1
  volatile.eth0.hwaddr: 00:16:3e:ca:9e:31
  volatile.last_state.idmap: '[]'
devices:
  root:
path: /
type: disk
ephemeral: false

Thanks,
Jason

On Wed, Aug 10, 2016 at 8:09 AM, Daniel Bidwell  wrote:

> I have followed the steps below, but still no luck.  Here is what I
> have:
>
> /var/log/syslog on my container, maastest, shows:
>
> Aug 10 12:51:05 maastest kernel: [210439.259086] audit: type=1400
> audit(14708334
> 65.435:829): apparmor="DENIED" operation="mount" info="failed flags match"
> error
> =-13 profile="lxd-maastest_" name="/tmp/maas-9bYBDZ/"
> pid=13267 co
> mm="mount" fstype="ext4" srcname="/dev/loop0" flags="ro"
>
> From the machine holding the container a "lxc profile show maastest"
> returns:
>
> lxc profile show maastest
> name: maastest
> config:
>   raw.lxc: lxc.cgroup.devices.allow = c 10:237 rwm
> lxc.cgroup.devices.allow = b 7:*
> rwm lxc.aa_profile = unconfined
>   security.privileged: "true"
> description: ""
> devices:
> ...
>
> The maastest profile has been applied to the maastest container.
>
> /etc/apparmor.d/lxc-custom-default contains:
>
> profile lxc-container-extx-mounts
> flags=(attach_disconnected,mediate_deleted) {
>   #include 
>   mount fstype=ext4 -> /**,
>   mount fstype=ext3 -> /**,
>   mount fstype=ext2 -> /**,
> }
>
> Any suggestions as to what I am missing?
>
> On Sat, 2016-08-06 at 22:50 -0500, Jason Hobbs wrote:
> > Hi Daniel,
> >
> > There is some documentation for installing MAAS in a container here:
> >
> > https://maas.ubuntu.com/docs/install.html#container-install
> >
> > It's focused on 2.0 but the same steps should work for 1.9.3 too. It
> > covers setting up the loop devices.
> >
> > Hope this helps,
> > Jason
> >
> > On Sat, Aug 6, 2016 at 10:11 PM, Daniel Bidwell 
> > wrote:
> > > I have a lxd container running on 16.04 with maas 1.9.3 running in
> > > it.
> > >
> > > The pxe boot doesn't work because the container doesn't have any
> > > /dev/loop* devices and will not allow me to create any.
> > >
> > > How do I go about creating /dev/loop* devices and allowing them to
> > > work
> > > in a container?
> > > --
> > > Daniel Bidwell 
> > >
> > >
> > > --
> > > Juju mailing list
> > > Juju@lists.ubuntu.com
> > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman
> > > /listinfo/juju
> > >
> --
> Daniel Bidwell 
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Default bootstrap machine sizes on public clouds

[Mark Shuttleworth]

It's been a while since we discussed the default machine sizes to use
when bootstrapping on public clouds. Now that we have multi-model
controllers I'm seeing folks stress the controller a lot harder (which
is good :)) and I wonder if we shouldn't up the defaults?


Mark

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

A new development release of Juju, 2.0-beta15, is here!

[Nicholas Skaggs]

A new development release of Juju, 2.0-beta15, is here!


## What's new?


This releases addresses stability and performance issues including 29 bugs
from b14 last week. Some notable ones include:


* lxd containers not using configured proxy for downloading images

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

* juju2 beta11 unable to parse PORT during a maas bootstrap

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

* LXD no longer activates all interfaces on initial deploy when using
MAAS2rc3 and JUJU Beta13

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

* It is not possible to refer to multiple models with the same name from
the CLI

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


## How do I get it?


If you are running Ubuntu, you can get it from the Juju devel PPA:


sudo apt-add-repository ppa:juju/devel

sudo apt-get update; sudo apt-get install juju-2.0


Or install it from the snap store


snap install juju --beta --devmode


Windows, Centos, and OS X users can get a corresponding installer at:


https://launchpad.net/juju-core/+milestone/2.0-beta15



## Feedback Appreciated!


We encourage everyone to subscribe the mailing list at

juju@lists.ubuntu.com and join us on #juju on freenode. We would love to

hear your feedback and usage of juju.



## Anything else?


You can read more information about what's in this release by viewing

the release notes here:


https://jujucharms.com/docs/devel/temp-release-notes
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju