robably since we
started this project.
> What is the community's level of interest in exploring that?
The session on adding a backend using a non-SQL datastore was pretty
well attended.
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu
> For the rest of the data, perhaps it could be persisted using some alternate
> backend.
What would that solve?
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer |
I'd very much like to take part in the discussions. Depending on the
outcome of said discussion, I may or may not want to participate in
the implementation :)
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer |
s of
nova-network who are probably already nervous that the rug will be
pulled out from under them? I'm about a -1,000,000 on that one.
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | http://www
I've not read the blueprint yet, but I think we'll need another name
for it. I'm sure lots of us are running this Sentry in prduction:
https://github.com/getsentry/sentry
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
Open
+1. Thanks for all your hard work.
Den 16/01/2014 19.17 skrev "Anita Kuno" :
> Thank you, fungi.
>
> You have kept openstack-infra running for that last 2 weeks as the sole
> plate-spinner whilst the rest of us were conferencing, working on the
> gerrit upgrade or getting our laptop stolen.
>
> Y
2100 UTC is 1 PM Pacific. :-)
Den 29/01/2014 17.01 skrev "Vishvananda Ishaya" :
> I apologize for the confusion. The Wiki time of 2100 UTC is the correct
> time (Noon Pacific time). We can move tne next meeting to a different
> day/time that is more convienient for Europe.
>
> Vish
>
>
> On Jan 29
s is a
bigger problem than the credentials for separate registration service
that performs the exact same operations?
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/
2014-02-01 18:24 GMT+01:00 Saju M :
&g
2014-02-10 17:03 GMT+01:00 Kieran Spear :
> On 10 February 2014 08:27, Soren Hansen wrote:
>> I agree that putting admin credentials on a public web server is a
>> security risk, but I'm not sure why a set of restricted admin
>> credentials that only allow you to cre
Den 15/02/2014 00.19 skrev "Adam Young" :
>> Could you please spend 5 minutes on the blueprint
https://blueprints.launchpad.net/horizon/+spec/user-registration and add
your suggestions in the white board.
> Does it make sense for this to be in Keystone first, and then Horizon
just consumes it? I w
ore appropriate time.
> If the user is pulling the devstack plugin from a 3rd party location,
> then it's clear where the support needs to come from. If it's coming
> from devstack, people are going to be private message pinging me on
> IRC when it doesn't work (which
2014-09-12 1:05 GMT+02:00 Jay Pipes :
> If Nova was to take Soren's advice and implement its data-access layer on
> top of Cassandra or Riak, we would just end up re-inventing SQL Joins in
> Python-land. I've said it before, and I'll say it again. In Nova at least,
> the SQL schema is complex becau
2014-09-26 17:11 GMT+02:00 Jay Pipes :
> On 09/26/2014 06:45 AM, Soren Hansen wrote:
>> Define "best".
> best == most appropriate.
#copout
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | ht
qualification than "Nova's data model is
really complex" reads *exactly* like a snarky comment implying everyone
else "has it wrong".
[1]: http://aphyr.com/posts/288-the-network-is-reliable
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer
I'm sorry about my slow responses. For some reason, gmail didn't think
this was an important e-mail :(
2014-09-30 18:41 GMT+02:00 Jay Pipes :
> On 09/30/2014 08:03 AM, Soren Hansen wrote:
>> 2014-09-12 1:05 GMT+02:00 Jay Pipes :
> How would I go about getting the asso
2014-10-03 9:00 GMT+02:00 Michael Chapman :
> On Fri, Oct 3, 2014 at 4:05 AM, Soren Hansen
> wrote:
>> That said, there will certainly be situations where there'll be a
>> need for some sort of anti-entropy mechanism. It just so happens that
>> those situations alre
int is just that there's plenty of alternatives to the
omniscient schedulers that we've been used to for 3 years now.
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/
_
but simply making them simple to disable and
thus enable the O(1) scheduler.
--
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | http://www.openstack.org/
___
OpenStack-dev ma
Putting release notes in the git repo so that they simply will get
merged along with the corresponding code seems like a no-brainer. What
am I missing?
Soren Hansen | http://linux2go.dk/
Ubuntu Developer | http://www.ubuntu.com/
OpenStack Developer | http
2015-07-08 18:45 GMT+02:00 Thierry Carrez :
> Soren Hansen wrote:
>> Putting release notes in the git repo so that they simply will get
>> merged along with the corresponding code seems like a no-brainer. What
>> am I missing?
> For stable branches it prevents us from
like to ask
one more chance to resucitate it in its current home.
I could be open to a discussion about putting it into a separate
repository, but having it functionally remain in its current place, if
that's somehow easier to swallow.
Soren Hansen | http://linux2go.dk/
Ubuntu Develo
21 matches
Mail list logo
