ann to the novaclient release group now.
Michael
On Fri, Feb 20, 2015 at 2:12 AM, Matt Riedemann
wrote:
>
>
> On 2/12/2015 6:55 PM, Michael Still wrote:
>>
>> This was discussed in the nova meeting this morning. In that meeting
>> we declared ourselves unwedged and ready
I can do another release if needed once we've landed a fix, although
it sounds like this can be fixed in neutron?
Michael
On Fri, Feb 20, 2015 at 7:33 AM, melanie witt wrote:
> On Feb 19, 2015, at 11:52, Terry Wilson wrote:
>
>> Unfortunately, the new novaclient release ended up completely brea
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli wrote:
> Does it make sense to purge old stuff regularly so we have a better
> overview? Or maybe we should chart a distribution of age of proposed
> changesets, too in order to get a better understanding of where the
> outliers are?
Given the ab
Hi,
this is just a quick note to let you know that Liberty specs are now
open for Nova. By open I mean that it is possible to upload such a
spec, but I wouldn't expect to see much review effort on these until
Kilo is ready.
If authors of previously approved specs (Juno or Kilo) want to use the
"p
I'm not 100% sure if this would be trivial or not, but the process to
find out isn't scary. We should add this to a nova meeting agenda on
the wiki and talk through it during a meeting.
(Noting that we're not approving specs for liberty in any form until
the Kilo branch is cut, so we have some tim
Hi,
let's start tracking ideas for summit sessions in this etherpad:
https://etherpad.openstack.org/p/liberty-nova-summit-ideas
Have at it!
Cheers,
Michael
--
Rackspace Australia
__
OpenStack Development Mailing List
Hi,
I thought it would be a good idea to send out a status update for the
migration from nova-network to Neutron, as there hasn't been as much
progress as we'd hoped for in Kilo. There are a few issues which have
been slowing progress down.
First off, creating an all encompassing turn key upgrade
I apologise if there's already been an email about this, I can't see one.
Is the Hyper-V CI broken at the moment? It looks like there are a
number of tests failing for every change, including trivial typo
fixes. An example:
http://64.119.130.115/168500/4/results.html.gz
http://stackalytics.com/r
Hi!
As discussed in the nova meeting last week, now is the time for us to
be focusing on closing release critical bugs in Kilo. The nominal date
for RC1 is 9 April, but it will release sooner than that if we close
all of the bugs targetted to RC1 before then.
This calls for two actions:
- if yo
The blueprint for this work appears to be
https://blueprints.launchpad.net/nova/+spec/nested-quota-driver-api
which shows it didn't make it into Nova in Kilo.
Looking at the reviews, I agree they didn't get enough attention, but
there isn't a lot that we can do about that right now. We can revisit
On Thu, Apr 2, 2015 at 4:28 AM, Joe Gordon wrote:
> On Wed, Apr 1, 2015 at 6:59 AM, Sylvain Bauza wrote:
>> Le 01/04/2015 15:51, Sean Dague a écrit :
>>>
>>> I just spent a chunk of the morning purging out some really old
>>> Incomplete bugs because about 9 months ago we disabled the auto
>>> exp
This looks good to me, but it would be interesting to see what Sean or
Matt thought.
Michael
On Thu, Apr 2, 2015 at 3:25 AM, Joe Gordon wrote:
>
>
> On Wed, Apr 1, 2015 at 8:28 AM, Lenny Verkhovsky
> wrote:
>>
>>
>>
>> Hi all,
>>
>>
>>
>> We had some issues with presentation of the logs, now it
Thanks for the detailed email on this. How about we add this to the
agenda for this weeks nova meeting?
One option would be to add a fixture to some higher level test class,
but perhaps someone has a better idea than that.
Michael
On Wed, Apr 1, 2015 at 8:54 PM, Markus Zoeller wrote:
> Context:
Actually, for some projects the +1 is part of a public voting process and
therefore required.
Michael
On 2 Apr 2015 8:11 am, "Steve Martinelli" wrote:
> *puts mailing list police hat on*
>
> Refer to
> http://lists.openstack.org/pipermail/openstack-dev/2015-March/059642.html
>
> I know we're try
I'd like another term as Nova PTL, if you'll have me.
I feel Kilo has gone reasonably well for Nova -- our experiment with
priorities has meant that we’ve got a lot of important work done. We
have progressed well with cells v2, our continued objects transition,
scheduler refactoring, and the v2.1
On Fri, Apr 3, 2015 at 12:38 AM, Matthew Booth wrote:
> On 02/04/15 07:20, Michael Still wrote:
First off, sorry for the slow reply to this email. The reason that I
sent my candidacy email at the very start of the election window is
that Easter is a four day holiday in Australia, so I sent
I am ok with this change too, which now has two +2's. If someone
doesn't object in the next few hours I will merge the change.
Michael
On Wed, Apr 8, 2015 at 1:46 AM, Thierry Carrez wrote:
> Finucane, Stephen wrote:
>> Nova cores,
>>
>> I would like to request a SFE for the below fix:
>>
>>
How many users are likely to use live migration without the changes to
qemu you mention? How functional would the live migration be?
Thanks,
Michael
On Wed, Apr 8, 2015 at 2:45 AM, Markus Zoeller wrote:
> I'd like to request a string freeze exception for this review:
>
> https://review.opens
It is my sad duty to inform the community that Chris Yeoh passed away this
morning. Chris leaves behind a daughter Alyssa, aged 6, who I hope will
remember Chris as the clever and caring person that I will remember him as.
I haven’t had a chance to confirm with the family if they want flowers or a
I just wanted to send a note about John running in the PTL election for Nova.
I want to make it clear that I think having more than one candidate is
a good thing -- its a healthy part of a functional democracy, and it
also means regardless of the outcome we have at least one succession
planning op
There are a few bugs still outstanding for nova's RC1. Here's a quick
summary. For each of these we need to either merge the fix, or bump
the bug from being release blocking.
-
https://bugs.launchpad.net/nova/+bug/1427351
"cells: hypervisor API extension can't find compute_node services"
Thi
o fix this. There will be
charity envelopes available at the funeral, or you can choose your
preferred research to fund, should you wish to do so. You have our
thanks."
Michael
On Wed, Apr 8, 2015 at 2:49 PM, Michael Still wrote:
> It is my sad duty to inform the community that Chris Yeoh
Hi,
we need to make sure we continue to progress on bugs targeted as
likely to need backport to Kilo. The current list is here --
https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential .
Bugs on that list which have fixes merged and backports prepared will
stand a very good chance of g
On Wed, Apr 15, 2015 at 7:22 AM, Dan Smith wrote:
>> we need to make sure we continue to progress on bugs targeted as
>> likely to need backport to Kilo. The current list is here --
>> https://bugs.launchpad.net/nova/+bugs?field.tag=kilo-rc-potential .
>>
>> Bugs on that list which have fixes merg
Hey, turbo hipster already knows how to upgrade major releases, so
adding this should be possible.
That said, I've been travelling all day so haven't had a chance to
look at this. If Josh doesn't beat me to it, I will take a look when I
get to my hotel tonight.
(We should also note that we can ju
On Thu, Apr 23, 2015 at 1:31 AM, Dan Smith wrote:
>> Sure, but for people doing continuous deployment, they clearly haven't
>> ran the migrate_flavor_data (or if they have, they haven't filed any
>> bugs about it not working[0]).
>
> Hence the usefulness of T-H here, right? The point of the migrat
Hi,
I've served on the TC for a while now and enjoyed it. However, I feel
I've reached a point where I need to step back and take a break. I
will therefore not be running this time around. I'm sure I'll return
just as soon as my righteous anger builds up again.
Cheers,
Michael
--
Rackspace Aust
Excellent, and well done!
I think it would be a good idea to send this announcement to the
openstack-operators list as well, as some ops people might not notice
it here.
Cheers,
Michael
On Thu, Apr 23, 2015 at 10:33 PM, Alexandre Levine
wrote:
> Hello everyone,
>
> We've decided to cut our firs
+1 I think she'd be a valuable addition to the team.
Michael
On 30 Apr 2015 9:30 pm, "John Garbutt" wrote:
> Hi,
>
> I propose we add Melanie to nova-core.
>
> She has been consistently doing great quality code reviews[1],
> alongside a wide array of other really valuable contributions to the
>
Hi,
I just wanted to let people know that I am going through abandoning
old specs for Nova at the moment. The criteria I am using is:
- spec targets kilo
- no review comments or other activity since January or February
I think its worth reinforcing that an abandon isn't a -2... An upload
of a
Hi,
I noticed last night that there are 23 bugs currently filed in nova
tagged as ironic related. Whilst some of those are scheduler issues, a
lot of them seem like things in the ironic driver itself.
Does the ironic team have someone assigned to work on these bugs and
generally keep an eye on th
As discussed at the Nova meeting this morning, we'd like to gauge
interest in a mid-cycle meetup for the Liberty release.
To that end, I've created the following eventbrite event like we have
had for previous meetups. If you sign up, you're expressing interest
in the event and if we decide there's
I thought I should let people know that we've had 14 people sign up
for the mid-cycle so far.
Michael
On Fri, May 8, 2015 at 3:55 PM, Michael Still wrote:
> As discussed at the Nova meeting this morning, we'd like to gauge
> interest in a mid-cycle meetup for the Liberty rele
l
On Fri, May 8, 2015 at 4:49 PM, Michael Still wrote:
> I thought I should let people know that we've had 14 people sign up
> for the mid-cycle so far.
>
> Michael
>
> On Fri, May 8, 2015 at 3:55 PM, Michael Still wrote:
>> As discussed at the Nova meeting this morning,
It would be interesting for this to be built in a way where other endpoints
could be added to the list that have extra headers added to them.
For example, we could end up with something quite similar to EC2 IAMS if we
could add headers on the way through for requests to OpenStack endpoints.
Do yo
This sort of question comes up every six months or so it seems.
The issue is that for config drive users we don't have a way of rebuilding
all of the config drive (for example, the root password is gone). That's
probably an issue for rescue because its presumably one of the things you
might reset.
2014 at 08:26:44AM +1000, Michael Still wrote:
> > On Tue, Sep 23, 2014 at 8:58 PM, Daniel P. Berrange
> wrote:
> > > On Tue, Sep 23, 2014 at 02:27:52PM +0400, Roman Bogorodskiy wrote:
> > >> Michael Still wrote:
> > >>
> > >>
Hi,
I'm trying to explain this behaviour in stable/newton, which specifies
Routes==2.3.1 in upper-constraints:
$ pip install --no-binary :all: Routes==2.3.1
...
Could not find a version that satisfies the requirement Routes==2.3.1
(from versions: 1.5, 1.5.1, 1.5.2, 1.6, 1.6.1, 1.6.2, 1.6.3, 1.7
te:
> On 06/12/2017 04:29 AM, Michael Still wrote:
> > Hi,
> >
> > I'm trying to explain this behaviour in stable/newton, which specifies
> > Routes==2.3.1 in upper-constraints:
> >
> > $ pip install --no-binary :all: Routes==2.3.1
> > ...
> >
Certainly removing the "--no-binary :all:" results in a build that builds.
I'll test and see if it works todayish.
Michael
On Mon, Jun 12, 2017 at 9:56 PM, Chris Smart wrote:
> On Mon, 12 Jun 2017, at 21:36, Michael Still wrote:
> > The experimental buildroot based iron
Hi,
I'm cc'ing openstack-dev because your email is the same as the comment you
made on the relevant review, and I think getting visibility with the wider
Nova team is a good idea.
Unfortunately this is a risk of having an out of tree Nova driver, which
has never been the recommended path for impl
Hi.
I'm working through the process of converting the libvirt driver in Nova to
privsep with the assistance of Tony Breeds. For various reasons, I started
with removing all the calls to the chown binary and am replacing them with
privsep equivalents. You can see this work at:
https://review.o
Hi,
nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could
use shred to zero out volumes efficiently if we could assume that shred
8.22 was in all our downstream distros [1]. shred 8.22 shipped in 2013 [2].
Can we assume that thing now? xenial appears to ship with 8.25 for examp
Specifically we could do something like this:
https://review.openstack.org/#/c/495532
Michael
On Sun, Aug 20, 2017 at 3:43 PM, Michael Still wrote:
> Hi,
>
> nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could
> use shred to zero out volumes efficiently if we
I'm going to take the general silence on this as permission to remove the
idmapshift binary from nova. You're welcome.
Michael
On Sat, Jul 29, 2017 at 10:09 AM, Michael Still wrote:
> Hi.
>
> I'm working through the process of converting the libvirt driver in No
017 at 03:43:22PM +1000, Michael Still wrote:
> > Hi,
> >
> > nova.virt.libvirt.storage.lvm.clear_volume() has a comment that we could
> > use shred to zero out volumes efficiently if we could assume that shred
> > 8.22 was in all our downstream distros [1]. shred 8.22 sh
"Matt Riedemann" wrote:
> On 8/20/2017 1:11 AM, Michael Still wrote:
>
>> Specifically we could do something like this:
>> https://review.openstack.org/#/c/495532
>>
>
> Sounds like we're OK with doing this in Queens given the other discussion
> in this
Dims, I'm not sure that's actually possible though. Many of these files
have been through rewrites and developed over a large number of years.
Listing all authors isn't practical.
Given the horse has bolted on forking these files, I feel like a comment
acknowledging the original source file is pro
Hi,
this email is a courtesy message to make sure you're all aware that at the
PTG we decided to try to convert all of nova-compute to privsep for the
Queens release. This will almost certainly have an impact on out of tree
drivers, although I am hoping the fall out is minimal.
A change like this
One thing I'd like to explore is what the functional difference between a
rebuild and a delete / create cycle is. With a rebuild you get to keep your
IP I suppose, but that could also be true of floating IPs for a delete /
create as well.
Operationally, why would I want to inject a new keypair? Th
to discuss anything in flight for Queens, what
> we're working on, and have a chance to ask questions of operators/users for
> feedback. For example, we plan to add vGPU support but it will be quite
> simple to start, similar with volume multi-attach.
>
> 4. Michael Still had an i
I think new-keypair-on-rebuild makes sense for some forms of key rotation
as well. For example, I've worked with a big data ironic customer who uses
rebuild to deploy new OS images onto their ironic managed machines.
Presumably if they wanted to do a keypair rotation they'd do it in a very
similar
Greetings,
I hope everyone travelling to the Sydney Summit is enjoying jet lag just as
much as I normally do. Revenge is sweet! My big advice is that caffeine is
your friend, and to not lick any of the wildlife.
On a more serious note, I want to give a checkpoint for the Nova privsep
transition i
The privsep session doesn't appear to be in that list. Did it get dropped
or something?
Michael
On Wed, Nov 1, 2017 at 12:04 AM, Thierry Carrez
wrote:
> Hi everyone,
>
> Etherpads for the Forum sessions in Sydney can be found here:
>
> https://wiki.openstack.org/wiki/Forum/Sydney2017
>
> If you
On Mon, Nov 6, 2017 at 1:26 PM, Dan Smith wrote:
> > I hope everyone travelling to the Sydney Summit is enjoying jet lag
> > just as much as I normally do. Revenge is sweet! My big advice is that
> > caffeine is your friend, and to not lick any of the wildlife.
>
> I wasn't planning on licking an
Hi,
a really really long time ago (think 2011), we added support in Nova for
configuring the mkfs commands that are run for new ephemeral disks using
the virt_mkfs command. The current implementation is in
nova/virt/disk/api.py for your reading pleasure.
I'm battling a little with how to move thi
That does work for me, except it means I'll still need to port it to
privsep to hit my goal of no rootwrap in Queens. I can live with that.
Michael
On Wed, Nov 8, 2017 at 4:54 PM, Matt Riedemann wrote:
> On 11/8/2017 12:24 PM, Michael Still wrote:
>
>> Hi,
>>
>>
Thanks for this summary. I'd say the cinder-booted IPA is definitely of
interest to the operators I've met. Building new IPAs, especially when
trying to iterate on what drivers are needed is a pain so being able to
iterate faster would be very useful. That said, I guess this implies
booting more th
Hi,
I'm out of my depth a little here. I've done the following:
- installed kubernetes
- followed the deploy guide for kolla-kubernetes [1]
- except where I didn't because I had to fix it [2]
I can download an openrc and even send a "nova boot" that looks like it
works. However, I have this c
Do we continue to support the previous two releases as stable branches?
Doesn't that mean we double the amount of time we need to keep older CI
setups around? Isn't that already a pain point for the stable teams?
Michael
On Wed, Dec 13, 2017 at 8:17 AM, Thierry Carrez
wrote:
> Hi everyone,
>
>
Sorry for the slow reply, I've spent the last month camping in a tent and
it was wonderful.
The privsep transition isn't complete in Nova, but it was never intended to
be in Queens. We did get further than we envisaged and its doable to finish
off in Rocky.
That said, I feel like we have a nice e
So, is now a good time to mention that "Quamby" is the name of a local
prison?
Michael
On Fri, Jul 15, 2016 at 7:50 PM, Eoghan Glynn wrote:
>
>
> > (top posting on purpose)
> >
> > I have re-started the Q poll and am slowly adding all of you fine folks
> > to it. Let's keep our fingers crosse
On 16 Jul 2016 1:27 PM, "Thomas Herve" wrote:
>
> On Fri, Jul 15, 2016 at 8:36 PM, Fox, Kevin M wrote:
> > Some specific things:
> >
> > Magnum trying to not use Barbican as it adds an addition dependency.
See the discussion on the devel mailing list for details.
> >
> > Horizon discussions at th
On Tue, Jul 26, 2016 at 4:44 PM, Fox, Kevin M wrote:
[snip]
The issue is, as I see it, a parallel activity to one of the that is
> currently accepted into the Big Tent, aka Containerized Deployment
[snip]
This seems to be the crux of the matter as best as I can tell. Is it true
to say that th
On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
wrote:
> It's time to make sure we have all of our active technical contributors
> (ATCs) identified for Newton.
>
> Following the Foundation bylaws [1] and TC Charter [2], Project
> teams should identify contributors who have had a significant impac
On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann
wrote:
> Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > On Thu, Aug 11, 2016 at 2:24 AM, Doug Hellmann
> > wrote:
> >
> > > It's time to make sure we have all of our active technical contributors
> > > (ATCs) identified for
On Thu, Aug 11, 2016 at 7:38 AM, Doug Hellmann
wrote:
> Excerpts from Michael Still's message of 2016-08-11 07:27:07 +1000:
> > On Thu, Aug 11, 2016 at 7:12 AM, Doug Hellmann
> > wrote:
> >
> > > Excerpts from Michael Still's message of 2016-08-11 07:01:37 +1000:
> > > > On Thu, Aug 11, 2016 at
On Fri, Aug 19, 2016 at 1:00 AM, Matt Riedemann
wrote:
> It's that time of year again to talk about killing this job, at least from
> the integrated gate (move it to experimental for people that care about
> postgresql, or make it gating on a smaller subset of projects like oslo.db).
>
> The post
We're still ok with merging existing ones though?
Michael
On Fri, Aug 19, 2016 at 5:18 AM, Jay Pipes wrote:
> Roger that.
>
> On 08/18/2016 11:48 AM, Matt Riedemann wrote:
>
>> We have a lot of open changes for the centralize / cleanup config option
>> work:
>>
>> https://review.openstack.org/#
So, if this is about preserving CI time, then its cool for me to merge
these on a US Sunday when the gate is otherwise idle, right?
Michael
On Fri, Aug 19, 2016 at 7:02 AM, Sean Dague wrote:
> On 08/18/2016 04:46 PM, Michael Still wrote:
> > We're still ok with merging existi
Its a shame so many are -2'ed. There is a lot there I could have merged
yesterday if it wasn't for that.
Michael
On Mon, Aug 22, 2016 at 9:00 PM, Sean Dague wrote:
> On 08/22/2016 12:10 AM, Michael Still wrote:
>
>> So, if this is about preserving CI time, then it
Sorry for being slow on this one, I've been pulled into some internal
things at work.
So... Talking to Matt Riedemann just now, it seems like we should continue
to pass through the user authentication details when we have them to the
plugin. The problem is what to do in the case where we do not (w
Riedemann
wrote:
> On 8/30/2016 4:36 PM, Michael Still wrote:
>
>> Sorry for being slow on this one, I've been pulled into some internal
>> things at work.
>>
>> So... Talking to Matt Riedemann just now, it seems like we should
>> continue to pass through the
On Thu, Sep 1, 2016 at 11:58 AM, Adam Young wrote:
> On 08/31/2016 07:56 AM, Michael Still wrote:
>
> There is a quick sketch of what a service account might look like at
> https://review.openstack.org/#/c/363606/ -- I need to do some more
> fiddling to get the new option group
Heya,
I've been playing with bifrost to help me manage some lab machines. I must
say the install process was well documented and smooth, so that was a
pleasure. Thanks!
That said, I am struggling to get a working node enrolment. I'm resisting
using the JSON file / ansible playbook approach, becau
Replying to a single email because I am lazier than you.
I would have included logs, except /var/log/ironic on the bifrost machine
is empty. There are entries in syslog, but nothing that seems related (its
all periodic task kind of stuff).
However, Mark is right. I had an /etc/ironic/ironic.conf
management
> and power interfaces were not enabled. The patch should address that but
> please let us know if there are further issues.
> Mark
>
>
> On 4 Mar 2018 7:59 p.m., "Michael Still" wrote:
>
> Replying to a single email because I am lazier than you.
&g
I was thinking about this the other day... How do you de-register instances
from freeipa when the instance is deleted? Is there a missing feature in
vendordata there that you need?
Michael
On Fri, Nov 11, 2016 at 2:01 AM, Rob Crittenden wrote:
> Wanted to let you know I'm working on a nova meta
onic, or setting
> [default] log_dir to the same in ironic.conf.
>
> I'm surprised it's not logging to a file by default.
>
> Mark
>
> On 4 Mar 2018 8:33 p.m., "Michael Still" wrote:
>
>> Ok, so I applied your patch and redeployed. I now get a list of
_dir variable to /var/log/ironic, or setting
>> [default] log_dir to the same in ironic.conf.
>>
>> I'm surprised it's not logging to a file by default.
>>
>> Mark
>>
>> On 4 Mar 2018 8:33 p.m., "Michael Still" wrote:
>>
>>
Heya,
I've just stumbled across Tatu and the design presentation [1], and I am
wondering how you handle cleaning up instances when they are deleted given
that nova vendordata doesn't expose a "delete event".
Specifically I'm wondering if we should add support for such an event to
vendordata someh
gt;
> best,
> Pino
>
>
> On Thu, Mar 15, 2018 at 3:42 PM, Michael Still wrote:
>
>> Heya,
>>
>> I've just stumbled across Tatu and the design presentation [1], and I am
>> wondering how you handle cleaning up instances when they are deleted given
>
aving an interface for vendordata that gets deletes would be quite nice.
> Right now for novajoin we listen to the nova notifications for updates and
> deletes; if this could be handled natively by vendordata, it would simplify
> our codebase.
>
> BR
>
> On Fri, Mar 16, 2018 at
Thanks to jichenjc for fixing the pep8 failures I was seeing on master. I'd
decided they were specific to my local dev environment given no one else
was seeing them.
As I said in the patch that fixed the issue [1], I think its worth
exploring how these got through the gate in the first place. Ther
itchell, wrote:
> On Wed, 2018-04-04 at 07:54 +1000, Michael Still wrote:
> > Thanks to jichenjc for fixing the pep8 failures I was seeing on
> > master. I'd decided they were specific to my local dev environment
> > given no one else was seeing them.
> >
> > As
Hi,
https://review.openstack.org/#/c/523387 proposes adding a z/VM specific
dependancy to nova's requirements.txt. When I objected the counter argument
is that we have examples of windows specific dependancies (os-win) and
powervm specific dependancies in that file already.
I think perhaps all th
Heya,
https://review.openstack.org/#/c/527658 is a z/VM patch which introduces
their support for config drive. They do this by attaching a tarball to the
instance, having pretended in the nova code that it is an iso9660. This
worries me.
In the past we've been concerned about adding new filesyste
The more I think about it, the more I dislike how the proposed driver also
"lies" about it using iso9660. That's definitely wrong:
if CONF.config_drive_format in ['iso9660']:
# cloud-init only support iso9660 and vfat, but in z/VM
# implementation, can't link a disk
Internet: jiche...@cn.ibm.com
> > Phone: +86-10-82451493
> > Address: 3/F Ring Building, ZhongGuanCun Software Park, Haidian
> > District, Beijing 100193, PRC
> >
> > Inactive hide details for Matt Riedemann ---04/12/2018 08:46:25 AM---On
> > 4/11/2018 5:09 PM, Mi
I'm confused about the design of AE to be honest. Is there a good reason
that this functionality couldn't be provided by cloud-init? I think there's
a lot of cost in deviating from the industry standard, so the reasons to do
so have to be really solid.
I'm also a bit confused by what seems to be s
I was asked yesterday for a guide on how to write new escalated methods
with oslo privsep, so I wrote up a blog post about it this morning. It
might be useful to others here.
http://www.madebymikal.com/how-to-make-a-privileged-call-with-oslo-privsep/
I intend to write up how to add privsep to a n
Hi,
further to last week's example of how to add a new privsep'ed call in Nova,
I thought I'd write up how to add privsep to a new OpenStack project. I've
used Cinder in this worked example, but it really applies to any project
which wants to do things with escalated permissions.
The write up is
I think a good start would be a concrete list of the places you felt you
needed to change upstream and the specific reasons for each that it wasn't
done as part of the community.
For example, I look at your nova fork and it has a "don't allow this call
during an upgrade" decorator on many API call
On Mon, Nov 28, 2016 at 4:37 PM, Jay Pipes wrote:
[Snip]
>
> I don't see any compelling reason not to work with the Nova and Ironic
> projects and add the functionality you wish to see in those respective
> projects.
>
Jay, I agree and I don't. First off, I think improving our current projects
+1, I'd value him on the team.
Michael
On Sat, Dec 3, 2016 at 2:22 AM, Matt Riedemann
wrote:
> I'm proposing that we add Stephen Finucane to the nova-core team. Stephen
> has been involved with nova for at least around a year now, maybe longer,
> my ability to tell time in nova has gotten fuzzy
Hi,
radar was an antique effort to import some outside-OpenStack code that did
CI reliability dashboarding. It was never really a thing, and has been
abandoned over time.
The last commit that wasn't part of a project wide change series was in
January 2015.
Does anyone object to me following the
I'd be remiss if I didn't point out that the nova LXC driver is much better
supported than the nova-docker driver.
Michael
On Thu, Dec 29, 2016 at 8:01 PM, Esra Celik
wrote:
>
> Hi Sam,
>
> nova-lxc is not recommended in production [1]. And LXD is built on top of
> LXC AFAIK. But I will investi
So...
Our python3 tests hate [1] my exception handling for continued vendordata
implementation [2].
Basically, it goes a bit like this -- I need to move from using requests to
keystoneauth1 for external vendordata requests. This is because we're
adding support for sending keystone headers with th
t Riedemann" wrote:
>
> On 1/3/2017 8:48 PM, Michael Still wrote:
>
>> So...
>>
>> Our python3 tests hate [1] my exception handling for continued
>> vendordata implementation [2].
>>
>> Basically, it goes a bit like this -- I need to move from usin
I think #3 is the right call for now. The person we had working on privsep
has left the company, and I don't have anyone I could get to work on this
right now. Oh, and we're out of time.
Michael
On Thu, Jan 26, 2017 at 3:49 PM, Matt Riedemann wrote:
> The patch to add support for ephemeral stor
401 - 500 of 510 matches
Mail list logo
