, would not know if they
> > would remain suitable tomorrow).
> >
> > --
> > Stuart Bishop <stuart.bis...@canonical.com
> > <mailto:stuart.bis...@canonical.com>>
> >
> > --
>
I'm sorted. Thanks to those that replied.
On Thu, Dec 15, 2016, 18:33 Reed O'Brien <reed.obr...@canonical.com> wrote:
> Is there anyone around tomorrow North American time or sometime (any
> timezone) next week who can guide me through getting kvm running on lxd
> local
, but I'm not sure if he's around.
Cheers,
Reed
--
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
t;- May make future integration of tools which work with Github into our
> >process more difficult (e.g. static analysis or automated review
> tools)
> >
> > There has been talk of evaluating other review tools such as Gerrit and
> > that may still happen. For now, let'
t;>> > > I made a little test review on one PR here, and the UX was
>>>> > almost
>>>> > > exactly like working in reviewboard:
>>>> > > https://github.com/juju/juju/pull/6234
>>>> > >
>>>> > > There may be important edge cases I'm missing, but I think it's
>>>> > worth
>>>> > > looking into.
>>>> > >
>>>> > > -Nate
>>>>
>>>> --
>>>> 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
>>>
>>>
>> --
>> 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
>
>
--
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
On Mon, Aug 15, 2016 at 10:30 PM John Meinel wrote:
> ...
>>
>
>
>> +### tuple ### allow any 8000 0.0.0.0/0 any 0.0.0.0/0 in
>> +-A ufw-user-input -p tcp --dport 8000 -j ACCEPT
>> +-A ufw-user-input -p udp --dport 8000 -j ACCEPT
>> +
>>
>>
> If I'm reading this one
Yes thanks for doing the work to share this menn0. It is much appreciated.
I also needed to change the following in squid-deb-proxy (even though I
added a bunch of domains to
/etc/squid-deb-proxy/mirror-dstdomain.acl.d/10-default):
--- a/squid-deb-proxy/squid-deb-proxy.conf
+++
the read-write one, g...@github.com/...
Either would help prevent accidental writes to upstream.
--
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
.
>
> According to Github, this is the normal, expected practice:
> https://help.github.com/articles/fork-a-repo/#keep-your-fork-synced
>
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/juju-de
Unmarshal function, and seems to be recommending
> > using a Schema instead.
> >
> > I'm not completely sold either way, though I do find the YAML format
> > for the schema description to be far more human readable than the JSON
> > format.
> >
> > Thoughts?
> >
obviously have to handle this error specially.
>
Barring handling it via mgo session this seems obvious and practical.
~ro
--
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
evelopment.| |
|
+---+---+---+-+----+
--
Reed O'Brien
✉ reed.obr...@canonical.com
✆ 415-562-6797
+---+---+---+-++
| Level | Audience | Purpose | Example |
np
On Thu, Apr 7, 2016 at 10:31 AM, roger peppe <roger.pe...@canonical.com>
wrote:
> On 7 April 2016 at 17:34, Reed O'Brien <reed.obr...@canonical.com> wrote:
> >> Do you want to NAT the IPv4 traffic? n
> >
> > You do want to NAT the traffic, unless you h
about an hour now. I should probably have
> bootstrapped
> with debug enabled, I guess. It may be a related issue if I mucked
> up the lxd bridge configuration somehow again.
>
>
> On 7 April 2016 at 16:25, Reed O'Brien <reed.obr...@canonical.com> wrote:
> > I thin
1 INFO juju.cmd supercommand.go:60 running juju
> >> [2.0-beta3
> >> gc go1.6]
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 cloud "lxd" not found, trying
> as a
> >> provider name
> >> 2016-04-07 03:51:01 INFO cmd cmd.go:141 no credentials foun
fy 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:
16 matches
Mail list logo