Earlier  
Posted Nick Remark
#openstack-nova - 2017-09-05
13:50:43 jaypipes efried: that's it. nothing more.
13:50:59 efried Associating for programmatic or human consumption?
13:51:23 jaypipes efried: right now, mostly programmatic.
13:51:35 jaypipes efried: it's currently how we handle shared resources.
13:51:48 efried So placement aggregates can overlap.
13:52:00 efried I seem to recall asking this very question in Boston :)
13:52:04 efried And the answer was yes
13:52:06 stephenfin mriedem: Could you take another look at this this week? https://review.openstack.org/#/c/412356/
13:52:16 edleafe efried: placement can't select based on nova host agg
13:52:19 jaypipes efried: in the future, I envision aggregates being associated to each other via a distance attribute. In other words, agg A and agg B are distance 1 apart. agg X and agg A are distance 4 apart, etc.
13:52:33 edleafe efried: that's done in the scheduler filters
13:52:35 jaypipes efried: this will provide us a way to model affinity and anti-affinity concerns in placement.
13:53:03 jaypipes efried: yep, aggregates (either placement or Nova host aggregate) can overlap.
13:53:44 efried jaypipes So it also makes sense that a nested resource provider will be implicitly aggregated with its parent.
13:54:23 efried ...and by extension, with its "siblings" and "cousins"...
13:55:14 jaypipes efried: yes. I was planning on making a constraint that only root provider UUIDs could be associated with an aggregate.
13:56:55 mriedem stephenfin: replied
13:57:02 stephenfin ta
13:57:04 mriedem stephenfin: if we're going to play fast and loose we should at least have a release note
13:58:51 bhagyashris jaypipes: Thanks for your inputs :)
13:59:02 stephenfin mriedem: 'upgrade' section?
13:59:26 mriedem stephenfin: yeah i suppose
14:03:20 sean-k-mooney efried: hehe that is more my email client enforcing it then i doing it intentionally but thanks in any case.
14:04:32 openstackgerrit Stephen Finucane proposed openstack/nova master: rbd: Remove unnecessary 'encode' calls https://review.openstack.org/412356
14:04:49 stephenfin sean-k-mooney: I'd suggest using something like Evolution but don't - it's buggy af :(
14:06:00 sean-k-mooney stephenfin: currently im still using outlook because im too lazy to figure out how to get tunderbird to work with our exchange servers. but since you helped me to get inline respconces to text only mail working i think it does the job well enough
14:06:25 stephenfin mriedem: Done. The important bit is that this will only affect users running under Python 3
14:07:04 stephenfin sean-k-mooney: Heh, I actually blogged that when I left Intel https://that.guru/blog/sane-outlook/
14:07:13 stephenfin one of my very few posts. I should probably use that more
14:08:14 sean-k-mooney oh cool i should send that to sdake
14:09:06 sean-k-mooney sdake: you were asking how i got outlook to work with inline plain text before. stephens blog should help https://that.guru/blog/sane-outlook/
14:10:21 sean-k-mooney stephenfin: speanking of blogs in need to set min up again ...
14:10:26 bauzas mriedem: could you please tell me again which series to review ? I now have a new laptop and I don't find it
14:10:30 sdake sean-k-mooney the problem is the line doesn't break in replies
14:10:52 sdake sean-k-mooney therefore one cnnot reply inline
14:11:01 bauzas mriedem: I mean, the bug series about the problems with allocations
14:11:08 sdake stephenfin does your solution fix thta?
14:11:19 sdake sean-k-mooney everyting I've read says its an outlook bug and microsoft doesn't care
14:11:38 stephenfin sdake: Afraid not, I'd to guess what 80 characters looked like
14:11:39 sdake it has to dowith the way word is integrated into outlook
14:11:55 mriedem bauzas: starts here https://review.openstack.org/#/c/499678/3
14:12:00 bauzas mriedem: ta
14:12:03 bauzas CC'ing
14:12:10 stephenfin MS don't care for plain text. If you use outlook.com and try to switch to plain text, you suddenly can't paste links
14:12:16 mriedem bauzas: and https://review.openstack.org/#/c/498861/
14:12:17 sdake stephenfin there is a bar on the left side of replies, - it has nothign to do with 80 chars however the bar can't be broken - if there are 4 layers of replies, there is no way to "put a new reply" in
14:12:35 stephenfin It formats them as HTML
14:12:44 bauzas mriedem: will reviewing them in the next hour
14:12:47 bauzas thanks
14:12:49 sean-k-mooney sdake: this is what it looks like when i reply http://lists.openstack.org/pipermail/openstack-dev/2017-September/121804.html
14:13:14 stephenfin sdake: Ah, I remember that, though not what I did to resolve it
14:13:37 sdake i am on outlook 2016
14:13:44 sdake 2016 is where is broke - it worked on 2013 and prior
14:13:53 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Add VersionedObjectPrintable mixin https://review.openstack.org/493082
14:13:54 bauzas FWIW, I now have again an Entry button \o/
14:14:04 sdake it even worked briefly for 2016
14:14:08 sdake sean-k-mooney are ou using 2016 outlook?
14:14:26 stephenfin sdake: Maybe it's a feature, heh
14:14:27 sean-k-mooney sdake: no still on 2013 i am afraid
14:14:37 stephenfin For what it's worth, I ended up using Mutt for everything except openstack-dev in the end (ovs-dev, patchwork, dpdk-dev etc.)
14:14:39 sdake sean-k-mooney if you want a sane mail client don't upgrade
14:14:59 sdake i just use gmail for mailing lists - since i can actually reply
14:15:06 openstackgerrit Rodolfo Alonso Hernandez proposed openstack/os-vif master: Migration from ``ip`` commands to ``pyroute2`` https://review.openstack.org/484386
14:15:27 sean-k-mooney sdake: if i do an os reinstall or upgrade ill just setup tunderbird. but since outlook is not currently broken im not going to change it
14:15:48 stephenfin Exchange is still an excellent protocol (at least from a usability perspective), but the lack of things like auto-wrap in Outlook makes it tough to work with
14:15:59 stephenfin sean-k-mooney: Good luck. That is also terrible, IMO
14:17:03 sean-k-mooney stephenfin: well i have been usingin it since i created my first email account at home so im used to it. it works for me.
14:18:04 stephenfin sean-k-mooney: Ah, then you're not too badly off. I thought it was ugly as sin and calendering with Gmail was seriously broken. Evolution would be excellent if it just weren't so damn buggy :(
14:20:25 sean-k-mooney im currently in a "its not broke so im not going to fix it" mode with my apps and workflow. eventully ill upgrading things when i have too.
14:22:21 sean-k-mooney its kindo fo like openstack. our dev cloud has been running on newton rc1 for almost a year. it is now finally beging to have issue so im going to go strait to stable pike once kolla-ansible make its release but while it was working no need to upgrade it
14:24:33 openstackgerrit Matt Riedemann proposed openstack/nova master: Moving more utils to ServerResourceAllocationTestBase https://review.openstack.org/499539
14:24:34 openstackgerrit Matt Riedemann proposed openstack/nova master: Refactor ServerMovingTests for non-move tests https://review.openstack.org/498596
14:24:34 openstackgerrit Matt Riedemann proposed openstack/nova master: Test resource allocation during soft delete https://review.openstack.org/495159
14:33:29 sdake stephenfin i used thunderbird for 10 years - your correct it is awful :)
14:34:05 sdake if i relaly feel like osme pain I use mac mail for responding to mailing lists and outlook for reading
14:34:24 sdake wish i could find a mail client that worked with exchange that was good
14:34:40 sdake there is this rockin mac client, however, it lacks exchange support......
14:34:52 sdake in other words, its useless :)
14:36:37 openstackgerrit Matt Riedemann proposed openstack/nova master: Remove compatibility code for flavors https://review.openstack.org/460377
14:37:09 sean-k-mooney stephenfin: by the way, you mentioned before that we can associate multiple email accounts with a singel openstack account correct? do you have a link to how to do this. if not ill just google it
14:38:13 stephenfin sean-k-mooney: Sure. Sec
14:38:55 stephenfin sean-k-mooney: So I _think_ you do it from Launchpad. Go to https://launchpad.net/ and click your user in the top right
14:40:12 stephenfin That'll bring you to your profile. Emails are listed on the left. IIRC, this gets propagated to Gerrit
14:41:45 dansmith hope you guys don't mind me interrupting the email chat to talk about nova...
14:42:05 dansmith mriedem: so the people working on skip level upgrades pointed out that our ironic flavor migration thing will be a problem for them,
14:42:11 sean-k-mooney ok ill give that a try and if it doesnt work ill ask the infra guys next week.
14:42:29 dansmith which is correct, and a little contrary to the promises we've been making about being able to do offline upgrades with nova-manage
14:42:36 sean-k-mooney dansmith: sorry :)
14:42:46 dansmith so I'm trying to think about the best way to make that doable without compute running
14:42:48 dansmith sean-k-mooney: :)
14:43:25 dansmith mriedem: I'm thinking that the best plan would just be a dedicated subcommand for this specific case since it's kinda weird
14:43:28 mriedem dansmith: well, we can do some purely db intensive stuff in nova-manage
14:44:01 dansmith mriedem: yeah, but we need to know which instances are ironic and not, so I'm kinda thinking that maybe we should make a dedicated command that takes an ironic compute's hostname and migrates instances that are on that compute
14:44:11 dansmith which makes it not really fit the online-data-migrations model
14:44:23 dtantsur mriedem: hey! when do you folks plan on finalizing your PTG schedule? I specifically wonder about the scheduling discussion, as we have a couple of topics there
14:44:25 mriedem we can figure out the ironic nodes via the hypervisor_type on the compute_nodes table right?
14:44:37 mriedem dtantsur: it's something i need to work on this week
14:44:40 dansmith mriedem: we can yeah
14:44:52 mriedem it's pretty open ended atm, except for thursday morning being cinder time
14:45:58 dtantsur mriedem: we have a few topics depending on the scheduling discussion outcome to an extent. so I guess Wed would work better, probably afternoon.

Earlier   Later